Multi Page/Spool Directory Defs

2010-10-05 Thread George Henke/NYLIC
My Level 1l PAGE and SPOOL disks have only the first volume defined in the Directory. * USER $PAGE$ NOLOG MDISK A03 3390 000 END 540PAG R * USER $SPOOL$ NOLOG MDISK B01 3390 000 END 540SPL R * Yet, Q ALLOC PAGE and SPOOL recognize a second volume for each: q alloc page

Re: Multi Page/Spool Directory Defs

2010-10-05 Thread Mark Pace
The entries for $PAGE$ $SPOOL$ are place holders so DIRMaint won't accidentally allocate space on these volumes and so that a DIRMap will show the space as used. I would update the $PAGE$ and $SPOOL$ entries to reflect the correct usage. Q ALLOC scans the disk allocation map to determine what

Re: Multi Page/Spool Directory Defs

2010-10-05 Thread Dave Jones
Hi, George. Yes, this is how it should be.kinda:-) The $PAGE$ and $SPOOL$ user ids in the USER DIRECT file are place-holders where you can (if you want to) list your PAGE and SPOOL areas. That way, the page and spool areas will appear in such reports as produced by DIRMAP and DISKMAP. In

Re: Multi Page/Spool Directory Defs

2010-10-05 Thread Scott Rohling
Perhaps others can expound upon the 'why' of these users in the directory -- but they bear no relationship to the actual paging or spool space in use by the system.I consider them 'place holder' users which you can use to define overlay minidisks for your system volumes. One reason I can

Re: Multi Page/Spool Directory Defs

2010-10-05 Thread Frank M. Ramaekers
...@listserv.uark.edu] On Behalf Of George Henke/NYLIC Sent: Tuesday, October 05, 2010 9:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Multi Page/Spool Directory Defs My Level 1l PAGE and SPOOL disks have only the first volume defined in the Directory. * USER $PAGE$ NOLOG

Re: Multi Page/Spool Directory Defs

2010-10-05 Thread gclovis
Subject:Re: Multi Page/Spool Directory Defs Sent

Re: Multi Page/Spool Directory Defs

2010-10-05 Thread Brian Nielsen
As others have mentioned, they are placeholders to prevent directory managment software from allocating minidisks on them. What I also noticed was that your PAGE space is a mix of DASD sizes. Check out the recent thread discussing the pitfalls of doing so. You might want to fix that on your

Re: Multi Page/Spool Directory Defs

2010-10-05 Thread George Henke/NYLIC
tyvm for this heads up. Brian Nielsen bniel...@sco.idaho.gov Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 10/05/2010 12:45 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Multi Page/Spool Directory Defs

Re: Multi Page/Spool Directory Defs

2010-10-05 Thread George Henke/NYLIC
@LISTSERV.UARK.EDU cc Subject Re: Multi Page/Spool Directory Defs As others have mentioned, they are placeholders to prevent directory managment software from allocating minidisks on them. What I also noticed was that your PAGE space is a mix of DASD sizes. Check out the recent thread

Re: Multi Page/Spool Directory Defs

2010-10-05 Thread Ray Waters
/Spool Directory Defs My Level 1l PAGE and SPOOL disks have only the first volume defined in the Directory. * USER $PAGE$ NOLOG MDISK A03 3390 000 END 540PAG R * USER $SPOOL$ NOLOG MDISK B01 3390 000 END 540SPL R * Yet, Q ALLOC PAGE and SPOOL recognize a second volume for each: q alloc

Re: Multi Page/Spool Directory Defs

2010-10-05 Thread McKown, John
Company.SM From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of George Henke/NYLIC Sent: Tuesday, October 05, 2010 11:49 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Multi Page/Spool Directory Defs What is the best way to access