You'd need more visibility to the spooling blocks than any published API gives you. A spool file's SFB points to a SPM (spool management block) on disk, which then points to its data blocks (and potentially more SPM blocks). I suspect, though I don't know, that something like VM:Spool reads the SPOL-allocated areas directly to go after files, which is why it needs full-volume references to all your spool volumes. It would be an interesting exercise. -- Mike Harding z/VM System Support
The IBM z/VM Operating System <[email protected]> wrote on 11/02/2010 10:45:05 AM: > From: Bob Bates <[email protected]> > To: [email protected] > Date: 11/02/2010 10:45 AM > Subject: Spool file locations > Sent by: The IBM z/VM Operating System <[email protected]> > > 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. >
