I've used it as sort of a documentation "tool" and to also as a place
holder. That way when you run DISKMAP or DIRMAP it shows up in the report
and therefore you know the space has been allocated. Placing the mdisk
statement in $PAGE$ in no way means that $PAGE$ will use it. Of course
if you log on to $PAGE$ and try to format that space, you'll be in a world
of hurt. Therefore define them as read only.
You can also do this for $T-DISK$ and $SPOOL$
Hope that helps.
Steve G.
Mary Anne Matyaz <[EMAIL PROTECTED]>
Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
03/27/2007 11:58 AM
Please respond to The IBM z/VM Operating System
To: IBMVM@LISTSERV.UARK.EDU
cc:
Subject: $PAGE$ Question
Hello list. In the past I have added several page volumes to several VM
systems, never having updated the user known as $PAGE$ in user direct that
appears to have the first Page volume in there. Since I am working fine
right now, I am hesitant to add the second volume to this userid. I have
searched the manuals and only find $PAGE$ in Running Guest Operating
Systems and that as part of a user direct listing.
So my question is, what is the benefit from having my page volumes in this
userid. I guess a second question would be, where is 'adding a page
volume' documented? I only found it in the cookbook.
Thanks!
Mary Anne
