Hi Anne, Linking to a first level minidisk will create a DASD device on your second level system (1913 in your example below). After you IPL your second level system, do this:
VARY ON 1913 (in case it isn't already online) ATTACH 1913 ESAMON (to attach it to userid ESAMON, substitute any other userid of course). Of course, don't try to write to that disk......... :) -Mike -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Anne Crabtree Sent: Thursday, July 26, 2007 12:26 PM To: [email protected] Subject: z/vm 5.1 to 5.3 question I have successfully installed, ipl'd, etc z/vm 5.3 second level on a z/vm 5.1 system... Am now trying to customize the USER DIRECT to match current. (for instance, velocity software users!) I do not have tape drives at my disposal during the week. I put links in the USER DIRECT for VMTEST53 on first level, for instance: LINK ESAMON 191 1913 RR When I sign on to VMTEST53 prior to ipl and do 'Q V ALL', I can see 1913, but when I ipl, I can't access 1913...it doesn't exist. I know that I am missing part of the puzzle. I want to copy the contents of ESAMON 191 from first to second level. Do I need a minidisk in VMTEST53 for 510RES (where ESAMON 191 disk is)? I was nervouse to refer to 510RES at all even though it would be RR... Anne D. Crabtree System Programmer WV Dept of Administration - OT 304-558-1494 Fax 304-558-1441
