Re: Offload Process to change dasd types for spool
On Tue, 15 Apr 2008 17:56:29 -0700, Skip Robinson [EMAIL PROTECTED] wrote: Hot start is not adequate. Each member of the MAS will allocate 'things' on (often) every spool volume. This depends on your SPOOLDEF FENCE settings. But the default will cause the behavior you indicated. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
Offload Process to change dasd types for spool
Hi guys, I am embarking on the task of to develop OFFLOAD, in order to make easy the process of change dasd types for spool (type 3 to type 9). Actually we are doing it by draining volumes, and replacing them as they drain, but it's becoming increasingly difficult, and time consuming. Someone can say me if already did successfully this task and tell me the followed process?. Also might be useful some instructive to execute OFFLOAD's process towards volume. I apologize for my poor english. Thanks. -- 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
Re: Offload Process to change dasd types for spool
Angel, What are you running JES2 or JES3 and at what level. There are some slight differences. Lizette --- snip I am embarking on the task of to develop OFFLOAD, in order to make easy the process of change dasd types for spool (type 3 to type 9). Actually we are doing it by draining volumes, and replacing them as they drain, but it's becoming increasingly difficult, and time consuming. Someone can say me if already did successfully this task and tell me the followed process?. Also might be useful some instructive to execute OFFLOAD's process towards volume. I apologize for my poor english. Thanks. [] --- UnSnip -- 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
Re: Offload Process to change dasd types for spool
My heartfelt advice on OFFLOAD is *not* to use it if RELOAD is your final goal. I've heard of several career-threatening OFFLOAD adventures over the years in what amounts to WRITE-ONCE-READ-NEVER. It's not really the fault of the function itself, but you can easily fall into depths of confusion. In my experience, OFFLOAD/RELOAD takes 'difficult' to a new plateau. When we moved from Mod-3 volumes to Mod-9 not long ago, the process was fairly simple if somewhat leisurely: 1. Ensure adequate resources for a larger spool. You can do this dynamically with nondisruptive commands. Even if you have to enlarge your checkpoint, you can do it via the Reconfiguration Dialog. 2. Make sure you have LARGEDS=ALLOWED on SPOOLDEF. This is also dynamic. 3. Add as many Mod-9 volumes as needed to hold your expected quantity of spool data. 4. Start and format the new volumes. 5. Put the old volumes in DRAIN status. 6. Wait for the old volumes to actually drain. You will need one IPL across the MAS, but you can IPL one system at a time at any comfortable pace. 7. Some old data will go away naturally: printed, transmitted to another node, aged off by class, etc. 8. There will always be some data at the end that you have to purge manually because no one wants it. We found years-old (!) jobs that somehow never had purged. Once the last job on a spool volume is gone, the volume goes drained and can be varied offline. This process takes longer in theory than OFFLOAD/RELOAD, but in practice is quicker than finding a new job. ;-) . . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [EMAIL PROTECTED] Angel Tamayo [EMAIL PROTECTED] .COM To Sent by: IBM IBM-MAIN@BAMA.UA.EDU Mainframe cc Discussion List [EMAIL PROTECTED] Subject .EDU Offload Process to change dasd types for spool 04/15/2008 04:32 PM Please respond to IBM Mainframe Discussion List [EMAIL PROTECTED] .EDU Hi guys, I am embarking on the task of to develop OFFLOAD, in order to make easy the process of change dasd types for spool (type 3 to type 9). Actually we are doing it by draining volumes, and replacing them as they drain, but it's becoming increasingly difficult, and time consuming. Someone can say me if already did successfully this task and tell me the followed process?. Also might be useful some instructive to execute OFFLOAD's process towards volume. -- 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
Re: Offload Process to change dasd types for spool
6. Wait for the old volumes to actually drain. You will need one IPL across the MAS, but you can IPL one system at a time at any comfortable pace. Not being a JES expert, I have a Y question. Why is the IPL required? Isn't a hot start adequate? Enquiring minds need to know. - Too busy driving to stop for gas! -- 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
Re: Offload Process to change dasd types for spool
Hot start is not adequate. Each member of the MAS will allocate 'things' on (often) every spool volume. Those things stay there through the life of the current IPL. Besides started task segments, you get chunks of syslog and various control blocks. You need a warm start--IPL--to relinquish the allocated spool track groups. Ted MacNEIL [EMAIL PROTECTED] CATo Sent by: IBM IBM-MAIN@BAMA.UA.EDU Mainframe cc Discussion List [EMAIL PROTECTED] Subject .EDU Re: Offload Process to change dasd types for spool 04/15/2008 05:49 PM Please respond to IBM Mainframe Discussion List [EMAIL PROTECTED] .EDU 6. Wait for the old volumes to actually drain. You will need one IPL across the MAS, but you can IPL one system at a time at any comfortable pace. Not being a JES expert, I have a Y question. Why is the IPL required? Isn't a hot start adequate? Enquiring minds need to know. - Too busy driving to stop for gas! -- 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
Re: Offload Process to change dasd types for spool
Hot start is not adequate. Each member of the MAS will allocate 'things' on (often) every spool volume. Those things stay there through the life of the current IPL. Besides started task segments, you get chunks of syslog and various control blocks. You need a warm start--IPL--to relinquish the allocated spool track groups. Okay. Thanks. As I said, not a JES expert. But, now I understand. - Too busy driving to stop for gas! -- 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
Re: Offload Process to change dasd types for spool
Also note that my advice was for JES2, which I assumed was the OP's environment. JES3, as Lizette pointed out, is a different animal and may require different care and feeding. Ted MacNEIL [EMAIL PROTECTED] CATo Sent by: IBM IBM-MAIN@BAMA.UA.EDU Mainframe cc Discussion List [EMAIL PROTECTED] Subject .EDU Re: Offload Process to change dasd types for spool 04/15/2008 05:59 PM Please respond to IBM Mainframe Discussion List [EMAIL PROTECTED] .EDU Hot start is not adequate. Each member of the MAS will allocate 'things' on (often) every spool volume. Those things stay there through the life of the current IPL. Besides started task segments, you get chunks of syslog and various control blocks. You need a warm start--IPL--to relinquish the allocated spool track groups. Okay. Thanks. As I said, not a JES expert. But, now I understand. -- 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
Re: Offload Process to change dasd types for spool
Skip Robinson wrote: Also note that my advice was for JES2, which I assumed was the OP's environment. JES3, as Lizette pointed out, is a different animal and may require different care and feeding. The same general procedure will work: Add new large volumes, drain old small volumes, remove old volumes after they are no longer in use. Spool offload -- so-called Dump Job in JES3 -- should also work. -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- 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
Re: Offload Process to change dasd types for spool
I have been answering some of Angels questions off list. They are running JES2 V1.8. Here is what I have provided so far Angel, I prefer tape to dasd, less chance for data loss due to space issues. In the JES2 V1.8 Commands book there is a specification for the VOLUME that can be added to the $TOFF commands. Volume=volume The volume serial (5-6 characters) of a volume containing a spool data set. If Volume is also specified in the WS= list, only those jobs that reside on one or more of the specified volume(s) can be selected for dumping. You may specify up to 4 volumes. Multiple entries must be separated by commas and the list must be enclosed in parentheses. If volume is not a criterion for job selection, specify a null parameter of (Volume=()) and do not specify Volume in the WS= list. You must specify the empty parentheses (). You also need to make sure that the jobs on that volume are not being held. Some jobs can have a hold on sysout which remains on spool until that hold portion is also gone. It maybe that the reason the spool volume is not drained is because of output that has not completely purged. In SDSF one of the displays I like to do is in the ST panel for all jobs. Then sort on QUE column. Then look for $MASCOM just scroll back from there. You may find some jobs that have not completed output processing and are in OUTPUT que. So you volume may not be draining for those jobs that have OUTPUT in the QUE column PREFIX=* DEST=(ALL) OWNER=* SORT=Queue/A SYSNAME= NP JOBNAME JobID Owner Prty Queue C Pos DB2DWLMX STC06960 DB2DWLMX 15 EXECUTION DC0PWLMX STC06991 DC0PWLMX 15 EXECUTION DC0PWLMC STC07037 DC0PWLMC 15 EXECUTION BPXAS STC07047 OMVSKERN 15 EXECUTION DC0PWLMC STC07091 DC0PWLMC 15 EXECUTION DC0PWLMC STC07154 DC0PWLMC 15 EXECUTION TKW9486C JOB01950 KW94869 1 OUTPUT C TKW9486B JOB02847 KW94869 1 OUTPUT C TMA14 JOB05088 MA14359 1 OUTPUT Y T571A1F JOB00644 XX571A1 1 OUTPUT D TSAM4 JOB09581 SK15491 1 OUTPUT 8 --- NOTICE THE OUTPUT in the QUEUE column This needs to be released to complete processing TDBH8Q STC06788 TDBH8Q 1 OUTPUT TSJM003 JOB01201 SM14440 1 OUTPUT D SK15491X JOB05186 ENDAUTH 1 OUTPUT K TBECKYAA JOB06031 RB09772 1 OUTPUT 8 SASRPT1A JOB04390 CB16159 1 OUTPUT Z BMCMPA01 JOB00636 CB16159 1 OUTPUT Z TROS STC04932 TROS 1 OUTPUT BRETTRMF JOB05418 BS41590 1 OUTPUT Z BRETTRMF JOB05428 BS41590 1 OUTPUT Z TSAM4 JOB05810 SK15491 1 OUTPUT 8 The other command that is good is $DJOBQ,SPL=(V=xx) $D JQ,SPOOL=(V=DCSPL1) $HASP890 JOB(DSP2010) 243 $HASP890 JOB(DSP2010) STATUS=(AWAITING HARDCOPY),CLASS=A, $HASP890 PRIORITY=1,SYSAFF=(ANY),HOLD=(NONE), $HASP890 SPOOL=(VOLUMES=(DCSPL1),TGS=1, $HASP890 PERCENT=0.0008) $HASP890 JOB(DSP3110) 244 $HASP890 JOB(DSP3110) STATUS=(AWAITING HARDCOPY),CLASS=A, $HASP890 PRIORITY=1,SYSAFF=(ANY),HOLD=(NONE), $HASP890 SPOOL=(VOLUMES=(DCSPL1,2,3,4,5,6,7), --- Notice the multiple SPOOL volumes used $HASP890 TGS=32,PERCENT=0.0274) $HASP890 JOB(DSP3115) 245 $HASP890 JOB(DSP3115) STATUS=(AWAITING HARDCOPY),CLASS=A, $HASP890 PRIORITY=1,SYSAFF=(ANY),HOLD=(NONE), $HASP890 SPOOL=(VOLUMES=(DCSPL1,5),TGS=2, $HASP890 PERCENT=0.0017) This will show you what jobs are on that specific volume and if they are on other volumes as well. Hope this helps. Lizette -- 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
