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 think of is to be able to LINK and obtain ability to read or write (for example - to update allocation table - or to backup the volume). Also for protection of these areas so they show as allocated.
DIRMAINT also uses some 'dummy' entries for these areas to prevent allocating mindisks in non-PERM areas. So, on systems where I use DIRMAINT -- I typically ignore these dummy users and don't try to keep up with them. It's up to you whether you want to maintain these users and what minidisk addresses you want to use. Scott Rohling On Tue, Oct 5, 2010 at 8:52 AM, George Henke/NYLIC < george_he...@newyorklife.com> wrote: > > 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 > EXTENT EXTENT TOTAL PAGES HIGH % > VOLID RDEV START END PAGES IN USE PAGE USED > ------ ---- ---------- ---------- ------ ------ ------ ---- > 540PAG 10BA 1 3338 600840 198644 395999 33% > 540PG2 12CD 1 10016 1761K 184565 364318 10% > ------ ------ ---- > SUMMARY 2347K 383209 15% > USABLE 2347K 383209 15% > Ready; T=0.01/0.01 10:49:47 > q alloc spool > EXTENT EXTENT TOTAL PAGES HIGH % > VOLID RDEV START END PAGES IN USE PAGE USED > ------ ---- ---------- ---------- ------ ------ ------ ---- > 540SPL 106C 1 3338 600840 506931 600840 84% > 540SP2 101B 1 3338 600840 597514 600840 99% > ------ ------ ---- > SUMMARY 1174K 1079K 91% > USABLE 1174K 1079K 91% > Ready; T=0.01/0.01 10:49:56 > > Is this how is should be? >
