David Kreuter wrote:
Hi Ranga: Do your second level VM system packs start on real cylinder
0? z/VM will install just fine to a full pack minus one cylinder so I
recommend having your second level system use mdisks that start on
real cylinder 1.
I believe that is how we set it up. The DASD usage looks like this for
510RES
DASD USEDEXT VOLUME 510RES 510W01 510W02
GROUP REGION VOLUME START SIZE (END) OWNER ADDR
-------- -------- ------ ---------- ---------- ---------- -------- ----
* * 510RES 0 1 0 $ALLOC$ 0A01
* * 510RES 0 1113 1112 MAINT 0123
* * 510RES 0 1113 1112 SYSDUMP1 0123
* * 510RES 1 20 20 $DIRECT$ 0A04
................................................................
* * 510RES 3331 6 3336 MAINT 05A4
* * 510RES 3337 1 3337 P684096K 02C2
That comes to 3338 cyls for mod3.
I have some documentation that talks about J disk for 5VMDIR10 (dirmaint
guest) but I can not see it when I log into 5VMDIR10. I am not sure what
minidisk it equates to.
So you can label your 2nd level systems ZVM520 if you want to - and
label cylinder 0 something that makes your DASD managers happy.
David
Ranga Nathan wrote:
I need to relabel the volumes for my 2nd level z/VM, which is our
test environment. This is something coming from our z/OS sysprogs.
Is there any way to change all references to volume label using some
utility? If not where all would I need to change the volume labels?
I can think of SYSTEM CONFIG, extent control (dont remember how to
access this) and the directory entries.
The DASD at 2nd level does not share any DASD with level 1.
Appreciate your help.
--
__________________
Ranga Nathan
Work: 714-442-7591
