That's probably what I want to do eventually. I'm trying to learn how
to do this so I can test maintenance somewhere before putting it on
production (which is my only option at the moment).
Anne D. Crabtree
System Programmer
WV Dept of Administration - OT
304-558-5914 ext 8885
Fax 304-558-1351
>>> [EMAIL PROTECTED] 3/8/2007 8:11 AM >>>
You could put 510W01 in your 2nd level directory but it would be a
minidisk on the real 510W01 volume.
If you have enough DASD you could define minidisks on your 1st level
machine from cylinder 1 to END for 510RES & 510W01. Then logon on to
your 2nd level machine and restore DDR backups from your real 510RES &
510W01. This way you could have a complete running 2nd level
system with little effort.
/Fran Hensler at Slippery Rock University of Pennsylvania USA for 43
years
[EMAIL PROTECTED] +1.724.738.2153
"Yes, Virginia, there is a Slippery Rock"
On Thu, 8 Mar 2007 08:06:24 -0500 Anne Crabtree said:
>I was confused as to whether I should put VM2CKP in the DIRECTORY
stmt
>as opposed to 510W01. I'm just not sure I set everything up right.
>
>Anne D. Crabtree
>System Programmer
>WV Dept of Administration - OT
>304-558-5914 ext 8885
>Fax 304-558-1351
>
>>>> [EMAIL PROTECTED] 3/8/2007 7:49 AM >>>
>Anne -
>
>You would use the 12FF disk for your 2nd level directory.
>
>In fact you could not write the directory to 510W01 even if you
>wanted to. 510W01 is not defined in your 2nd level machine.
>
>/Fran Hensler at Slippery Rock University of Pennsylvania USA for 43
>years
> [EMAIL PROTECTED] +1.724.738.2153
> "Yes, Virginia, there is a Slippery Rock"
>
>On Thu, 8 Mar 2007 07:36:28 -0500 Anne Crabtree said:
>>I'm trying to set up a second level vm system following directions
in
>>"Z/VM Running Guest Operating Systems" Chapters 6 and 7. Here's my
>>directory entry on first level:
>>
>>USER VMTEST VMTEST 64M 128M BG
>> MACHINE ESA 2
>> OPTION TODENABLE
>> ACCOUNT 1 VMTEST
>> IPL CMS
>> SPECIAL 400 3270
>> CONSOLE 009 3215 T
>> SPOOL 00C 2540 READER *
>> SPOOL 00D 2540 PUNCH A
>> SPOOL 00E 1403 A
>> LINK MAINT 0190 0190 RR
>> LINK MAINT 019D 019D RR
>> LINK MAINT 019E 019E RR
>> MDISK 191 3390 217 0070 510W01 MR
>> MDISK 1000 3390 287 0035 510W01 MR
>> MDISK 12FF 3390 322 0070 510W01 MR
>>
>>I'm confused when I logon as VMTEST and create the USER DIRECT.
>>In DIRECTORY stmt, should it be:
>>DIRECTORY 12FF 3390 VM2CKP or do I have to use 510W01 since that's
>>the real volid where 12FF is? User OPERATOR looks like this:
>>USER OPERATOR AB12CD 32M 64M ABCDEFG
>> IPL 190 PARM AUTOCR
>> MACHINE ESA 4
>> ACCOUNT DEPT0001 BIN001
>> SPOOL 00C RDR A
>> SPOOL 00D PUN A
>> SPOOL 00E 4248 A
>> CONSOLE 01F 3270 T
>> * R/W disks
>> MDISK 191 3390 000 END VMT191 WR ALL
>> MDISK 1000 3390 000 END IPLDSK WR ALL
>> MDISK 12FF 3390 000 END VM2CKP WR ALL
>> * R/O disks
>> MDISK 190 3390 000 END MNT190 RR ALL
>> MDISK 19D 3390 000 END MNT19D RR ALL
>> MDISK 19E 3390 000 END MNT19E RR ALL
>>
>>In SYSTEM CONFIG, I have:
>>Checkpoint Volid VM2CKP From Cylinder 1 for 2,
>>Warmstart Volid VM2CKP From Cylinder 3 for 2
>>CP_Owned Slot 1 VM2CKP
>>
>>but since VM2CKP is a label not an actual volume, I'm not sure if I
>did
>>it right.
>>
>>I was trying to send this question to my buddy Phil at Velocity, but
>it
>>keeps coming back as undeliverable so I thought someone else could
>>probably clear this up for me.
>>Thanks!
>>
>>
>>
>>
>>Anne D. Crabtree
>>System Programmer
>>WV Dept of Administration - OT
>>304-558-5914 ext 8885
>>Fax 304-558-1351
