Thanks Mike, the write up described exactly what I am trying to do. I've got it and playing with it now.
Bob Bates [email protected] This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -----Original Message----- From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of Mike Walter Sent: Tuesday, November 02, 2010 12:58 PM To: [email protected] Subject: Re: Spool file locations Take a peek at SPFPACK EXEC on the IBM VM Download page: http://www.vm.ibm.com/download/packages/descript.cgi?SPFPACK If you need more info, I wrote the following enhancements, the EXEC of which I'd be happy to share: 19981016 Mike Walter -Change binary flags variable names to begin with '?' (discriminate from counters) -Misc. changes to improve speed. -Issued suggestion to use CHKFILES for 1st dasdrc=1009 or 1014 -Accept TargTrk operand -Accept TargCyl and TargTrk in hex as xnnnn xnn or hnnnn hnn -Obtain tracks/cyl from ReadDevCharacteristic -Add 'DETAIL' option. -Add APPEND option. Default to ERASE. -Ensure '*' at start of stacked items in case EXEC fails (don't leave trash in stack) -Add begmsg and endmsg to outfile. Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. "Bob Bates" <[email protected]> Sent by: "The IBM z/VM Operating System" <[email protected]> 11/02/2010 12:45 PM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject Spool file locations Greeting all creative folks, I am looking at trying to get some spool volumes removed from a system. I have them drained and they are slowly being evacuated, which is great. However, I would like to be able to see what spool files are on a specific volume. I figure there has to be a pointer somewhere that says this file has blocks on volume x at cchh, volume y at cchh, etc chaining through all its records where x and y are probably the slot numbers from the CPOWNED list, which is what I really want. There must be a way to find it. Years ago (before VM:Spool) I wrote something using Diag D8 so I could see the largest files on the spool and the user occupying the most space but it doesn?t give me the location that I can figure out. Any ideas? Bob Bates Operating Systems Engineer, z/VM and Linux on System z Enterprise Hosting Services, Mainframe/Midrange Services Wells Fargo Bank | 4056 Old Denton Rd | Carrollton, TX 75007 MAC T5369-011 Tel 469-892-6660 | Cell 214-907-5071 [email protected] This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
