I tested this on one of our test machines: nothing gets lost when a DASD is relabeled *and* the label change is applied to SYSTEM CONFIG too. CP does indeed prompts for a FORCE start. SPFPACK confirmed that I had files on the relabeled pack. 13:27:17 The directory on volume VMBRS1 at address F1BC has been brought online. 13:27:17 HCPWRM9200E System recovery failure; configuration error. 13:27:17 HCPASK9205A HCPASK9205A Invalid warm start data encountered. HCPASK9205A No files have been deleted yet. HCPASK9205A To change to a FORCE start, enter FORCE. HCPASK9205A To stop processing, enter STOP. 13:27:35 FORCE 13:27:36 HCPWRS2513I HCPWRS2513I Spool files available 415 13:27:37 HCPWRS2512I Spooling initialization is complete. 13:27:37 DASD F532 dump unit CP IPL pages 6611 13:27:37 HCPAAU2700I System gateway VMKBMB01 identified. 13:27:37 z/VM Version 5 Release 3.0, Service Level 0701 (64-bit),
2008/3/28, Schuh, Richard <[EMAIL PROTECTED]>: > The Oracle or one of its agents has spoken. Thanks, John. > > Would marking the disk as draining in the config file prevent the loss > of anything caused by the timing of the detection of the difference that > you describe? > > Another question, would backing up only files that are at least > partially contained on the disk be sufficient? We are talking about a > spool system that normally fluctuates between 7000 and 18000 files, many > of them quite large, and we are stuck with old tape technology (3 tapes > to contain a DDR of a 3390-03). It would be my luck that it would be the > higher number when my scheduled time arrived so that backing up the > entire spool would take quite a bit of time. > > I envision a process like this: > > Before IPL (all can be done while the system is running) > 1. DRAIN the disk, including update of SYSTEM CONFIG to indicate that it > was to be drained or draining at IPL. > 2. Use SPFACK to identify files that have at least 1 block on the pack. > 3. PURGE unnecessary files. > 4. Use SPXTAPE DUMP/LOAD to move the remaining files to the other spool > volumes. > 5. Reliable the pack. > 6. Update the system config with the new volser. The pack would be left > in the draining state. > > After IPL > 1. FORCE start. > 2. Update system config so that the disk is no longer draining. > 3 Start the device. > > Would that be safe enough? If so, it would minimize the down time, which > is a major consideration. I would also schedule the IPL to coincide with > already scheduled activities that require the system to be down. > > > Regards, > Richard Schuh > > > > > -----Original Message----- > > From: The IBM z/VM Operating System > > [mailto:[EMAIL PROTECTED] On Behalf Of John Franciscovich > > Sent: Thursday, March 27, 2008 2:09 PM > > To: IBMVM@LISTSERV.UARK.EDU > > Subject: Re: CPOWNED Devices > > > > >I've renamed spool volumes several times, four or more years > > ago, but a > > >force start was required. I don't recall whether it was > > VM/ESA or z/VM. > > >I would recommend a spool backup before attempting it. And > > if it is for > > >a production system, then schedule enough time to reload spool, if > > >necessary. > > > > A FORCE start will be required since the new CP_Owned list > > does not match the CP_Owned list that was saved in the > > checkpoint area when you shut down your system. > > > > The spool files are restored from the warmstart area during > > IPL, so they should be ok. You do risk losing information > > that was saved in the checkpoint area that hasn't been > > processed by the time the difference in the CP_Owned list is detected. > > > > In any event, I agree that a spool file backup is a good idea > > before attempting this change. > > > > John Franciscovich > > z/VM Development > > > -- Kris Buelens, IBM Belgium, VM customer support
