Thanks to all who responded. I will voice my opinion when I get access to the JES2 SHARE Requirements Database.
___________________________________________ Jim Petersen MVS - Lead Systems Engineer Home Depot Technology Center 1300 Park Center Drive, Austin, TX 78753 www.homedepot.com email: [EMAIL PROTECTED] 512-977-2615 direct 512-977-2930 fax 210-859-9887 cell This message may contain confidential information. The information contained in this message and any attachments are intended solely for the use of the addressee(s) named above. If you are not the intended recipient, any disclosure, copying, distribution or other use of the contents of this message is strictly prohibited. If you have received this email in error, please notify the sender immediately by email and delete all copies of this message -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Robert A. Rosenberg Sent: Wednesday, May 09, 2007 4:59 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: $HASP443 message At 13:24 -0500 on 05/09/2007, Rick Fochtman wrote about Re: $HASP443 message: >-----------------------<snip>---------------------------- > >>Yes. Thanks to both of you for responding. I found the error of my >>ways and did a $tspooldef and changed it to ALLOWED. Now I have >>another question. Is there a command which I can use to cause a spool >>volume to quit being used but redistribute what is on it to the >>remaining spool volumes? >> >> >-----------------------<unsnip>------------------------- >You can stop it from accepting new datasets by the $PSPOOL command, but >there's no command to remove its contents and distribute them to >another volume. > >Sure would be nice, though............. This type of thing would not be that hard to do with a User Written Command. The simple way would be to scan the output (and input?) queue to spot who is allocated on the Volume. The command can then just set the job to be spool offloaded. This will clean off all but executing (and pending execution) jobs. You then repopulate the queues via Spool Reload. The "Better" way would be to read the data and rewrite it freeing up the old allocation (Since doing this correctly is so complex, the SPOOL OFFLOAD/RELOAD route is simpler IMO). As to doing the redistribute on-the-fly, I'd check the JES2 Mods tape since I have the vague impression that I saw such a mod on it in the past. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
