tyvm, really sweet. So we can "have our cake and eat it too".
If I understand what you are saying. The real volser is on cylinder 0. But since we define minidisks from cylinder 1 to whatever, the minidisk, virtual disk, volser is defined on cylinder 1. Since DDR never really cares about or writes the last cylinder, though it complains, we can DDR to the minidisk, virtual disk, just as we would a to real disk and all is copacetic, at least as long as IBM does not mess with this. (Hope Alan is not listening). And so we can indeed have duplicate volsers, in name only, at 2nd Level, that are not really duplicate. Not bad. Not bad at all . . . peter.w...@ttc.ca Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> 10/01/2010 03:58 PM Please respond to The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Applying Maintenance - Best Practice With the disks for your second level system defined like this: MDISK 0100 3390 1 END TVM001 MR MDISK 0101 3390 1 END TVM002 MR MDISK 0102 3390 1 END TVM003 MR MDISK 0103 3390 1 END TVM004 MR MDISK 0104 3390 1 END TVM005 MR MDISK 0105 3390 1 END TVM006 MR MDISK 0106 3390 1 END TVM007 MR MDISK 0107 3390 1 END TVM008 MR The real labels are TVM001 to TVM008, while the ‘virtual’ labels starting on cylinder one can be anything your like, even duplicates of production volume labels. Just do a DDR restore to device 100 while logged on to the second level user. DDR will complain about the volume being too small, but will restore from the beginning of the backup. Since the last cylinder on the backup is empty, it doesn’t matter that volume 100 is one cylinder short. Peter -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of George Henke/NYLIC Sent: October 1, 2010 15:51 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Applying Maintenance - Best Practice ty for this information, but I do not follow how the last cylinder of any pack on the IIS being unused allows you to name the real packs anything you want while still retaining the default names for the 2nd Level system. Could you explain in a little more detail? Jeff Gribbin <jeff.grib...@gmail.com> Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> 10/01/2010 01:35 PM Please respond to The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Applying Maintenance - Best Practice Just in case this helps ... If your test system will never be IPLed 1st-level, are you aware that IBM deliberately does not allocate the last cylinder of any pack (3390-3 or 3390-9) that is part of an Initial Installation System? (That is, 540RES, etc.) because the last cylinder is not used, these packs can all be accommodate d using minidisks that begin at real cylinder 1 - allowing you to name the real packs whatever you wish and still retain the default names for your virtual second-level packs. I am trying to encourage IBM to make this information more obvious and well-known but for some reason they feel reluctant so to do. However, I have had a clear indication (in reply to a Reader's Comment) that they intend to continue to do this so I think it's fairly safe to go ahead on the assumption that the last cylinder of a, 'default installation' volume wil l not be referenced. In my view this approach makes much more sense than fiddling around with real volsers - I am a great believer in keeping all guests away from real cylinder zero except when this is absolutely unavoidable. Regards Jeff The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot be guaranteed on the Internet. The sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on the basis of information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is property of the TTC and must not be altered or circumvented in any manner.
