Hi Randy, A little late in the day but thought I'm add this to the discussion.
Your results posted below show that you are running with the initial allocation of spool space that comes off the tape when you first install z/VM 4.4. As you have already found out, this is enough to get you going, but often needs to be expanded before starting a bunch of service machines which may open console logs that eventually need more than the basic amount that comes off the tapes. And as someone else has already pointed out, the reason you have lots of spool consumed but very few spool files in evidence is that the system has automatically allocated space for a dump, just in case VM should crash, and that space is allocated in the spool. The CP command Q DUMP will show you how many pages are preallocated in spool to your dump files. If you wish to, you can turn off the dump allocation by using the CP command SET DUMP OFF You can turn them back on with CP SET DUMP DASD On an active system the size of the dump file can vary up and down if you are using the SPXTAPE command to offload spool files for spool backups. CP will use some of the dump space to keep track of the files it is dumping (can you tell I've "been there, got the ETR t-shirt"). CP will give back the pages used by SPXTAPE when your system gets busy, or you can turn off the dumps and turn them back on again (SET DUMP OFF and SET DUMP DASD) to free them up right away. Rather than do this after every spool offload, I added another volume of spool space. But I found once I went into production the normal amount of spool usage by users, combined with the way the dump allocation expanded and contracted (almost like the system was breathing!) when I did my daily spool offloads, meant I was still seeing high alloc values, and I ended up adding a second spool volume dedicated to DUMPs. Adding a second of third spool volume isn't too hard (just scary) and can be done without an IPL (even scarier), if you are careful about the way you add them. I know I kept console logs from when I did this, and can share them if you like to see what I did. Ron -----Original Message----- From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Randy Dray Sent: Saturday, November 05, 2005 11:43 AM To: [email protected] Subject: Q ALLOC SPOOL ???? Hello List, I issued a Q ALLOC SPOOL at vm console logged on as MAINT. q alloc spool EXTENT EXTENT TOTAL PAGES HIGH % VOLID RDEV START END PAGES IN USE PAGE USED ------ ---- ------ ------ ------ ------ ------ ---- 440RES 0600 79 256 32040 26765 31680 83% ------ ------ ---- SUMMARY 32040 26765 83% USABLE 32040 26765 83% Its used states 83%. I q rdr all and got abunch of files. Backed them up and then purged them off. I did the same for PRT files. Purged them all off. DID NOT have any pun files. QUESTION: MY q alloc spool still hasn't moved off 83%. I thought that % used would have dropped to almost nothing. would thier be other files that Its looking at that I cant see by doing a q rdr all or a q prt all???? recap at this point q prt all OWNERID FILE CLASS RECORDS CPY HOLD DATE TIME NAME TYPE OPERATOR 0011 T CON 00000049 001 NONE OPEN- 0009 TCPIP 0002 T CON 00000007 001 NONE OPEN- 0009 MAINT 0024 T CON 00000060 001 NONE OPEN- 0009 Ready; T=0.01/0.01 11:36:24 q rdr al HCPCQF003E Invalid option - AL Ready(00003); T=0.01/0.01 11:36:35 q rdr all OWNERID FILE CLASS RECORDS CPY HOLD DATE 0PERATNS 0001 D SYS 00000000 001 NONE OPEN- SYS OPERATNS 0002 D SYS 00000000 001 NONE OPEN- SYS MAINT 0021 T CON 00000060 001 NONE 11/05 10:05:35 MAINT 0022 T CON 00000063 001 NONE 11/05 10:39:22 Thanks Randy Dray Systems Programmer Morton Buildings Inc. Morton IL (309) 263-6397 __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
