My 2nd level system is similar to Tom's. The names are different, but the idea is the same. Our second level sysres becomes an alternate IPL volume that can be used if our real system's IPL volume should somehow get trashed.
Regards, Richard Schuh -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Tom Duerbusch Sent: Wednesday, August 22, 2007 1:00 PM To: [email protected] Subject: Re: MAINTENANCE USER VMTEST xxxxxx 64M 64M ABG POSIXINFO UID 308 MACHINE ESA OPTION MAINTCCW LNKEXCLU DEVMAINT ACCOUNT 1 SYSPROG IPL CMS SPE 01F 3270 SPE FCC0 3270 SPE 080 3270 CONSOLE 010 3270 * CONSOLE FCC0 3270 SPOOL 00C 3505 SPOOL 00D 3525 SPOOL 00E 4248 LINK MAINT 190 190 RR LINK MAINT 19D 19D RR LINK MAINT 19E 19E RR * DISK DRIVES DED 3706 3706 DED 3707 3707 DED 3708 3708 DED 3709 3709 DED 3628 3628 DED 3629 3629 DED 3630 3630 DED 363F 363F * OSA DIRECT DED 2019 2019 DED 201A 201A DED 201B 201B I use full packs (as I have them). Complete, separate system. Tom Duerbusch THD Consulting >>> Jon Brock <[EMAIL PROTECTED]> 8/22/2007 2:16 PM >>> This brings to mind a question I have had: how do y'all (as we way here) go about creating a second-level VM? Jon <snip> 1) create second level vm 2) apply maintenance 3) test 4) wait for maintenance window 5) backup system 6) apply maintenance 7) test <snip>
