Re: Concatenating Uncataloged Data Sets w/CLIST (was Re: What is needed to run IPCS ...)
On Fri, 2 May 2008 19:26:34 -0500, Paul Gilmartin [EMAIL PROTECTED] wrote: In your circumstance, I'd be inclined to use MSG(WTP) rather than MSG(2). But I've already been wrong once today. YMMV. Yes, that would be a better option also. Thanks. No excuse except that I copied the code from somewhere else without thinking about it. Although if the ALLOCATE above worked I would never expect the CONCAT to fail and if the ALLOCATE failed I would see that. 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
Re: Concatenating Uncataloged Data Sets w/CLIST (was Re: What is needed to run IPCS ...)
On Fri, 2 May 2008 09:40:40 -0500, Mark Zelden wrote: You can't use VOLSER for an uncataloged concatenation with TSO ALLOCATE. The way I deal with that is to use BPXWDYN since it is supported. You can also use one of the CONCAT flavors floating around. Does anyone know another / better way? If better means reducing the parts count, you could eliminate the IPCSMIG Rexx glue by CALLing BPXWDYN directly from the CLIST. (Of course, I'd rewrite the whole thing in Rexx.) -- gil -- 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: Concatenating Uncataloged Data Sets w/CLIST (was Re: What is needed to run IPCS ...)
On Fri, 2 May 2008 12:03:01 -0500, Mark Zelden [EMAIL PROTECTED] wrote: On Fri, 2 May 2008 11:57:07 -0500, Paul Gilmartin [EMAIL PROTECTED] wrote: On Fri, 2 May 2008 09:40:40 -0500, Mark Zelden wrote: You can't use VOLSER for an uncataloged concatenation with TSO ALLOCATE. The way I deal with that is to use BPXWDYN since it is supported. You can also use one of the CONCAT flavors floating around. Does anyone know another / better way? If better means reducing the parts count, you could eliminate the IPCSMIG Rexx glue by CALLing BPXWDYN directly from the CLIST. (Of course, I'd rewrite the whole thing in Rexx.) You can't use TSOLIB from REXX or I *would* have the entire thing in REXX. You have to queue it to the stack and that won't execute until you leave the REXX. Which means using something up front to get the TSOLIB in place. Even more confusing Sorta missed part of what you wrote. Good point... I should be able to use CALL *(BPXWDYN) 'CONCAT DDLIST(MIGLIB,SIEAMIGE) MSG(2)' 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
Re: Concatenating Uncataloged Data Sets w/CLIST (was Re: What is needed to run IPCS ...)
On Fri, 2 May 2008 11:57:07 -0500, Paul Gilmartin [EMAIL PROTECTED] wrote: On Fri, 2 May 2008 09:40:40 -0500, Mark Zelden wrote: You can't use VOLSER for an uncataloged concatenation with TSO ALLOCATE. The way I deal with that is to use BPXWDYN since it is supported. You can also use one of the CONCAT flavors floating around. Does anyone know another / better way? If better means reducing the parts count, you could eliminate the IPCSMIG Rexx glue by CALLing BPXWDYN directly from the CLIST. (Of course, I'd rewrite the whole thing in Rexx.) You can't use TSOLIB from REXX or I *would* have the entire thing in REXX. You have to queue it to the stack and that won't execute until you leave the REXX. Which means using something up front to get the TSOLIB in place. Even more confusing 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
Re: Concatenating Uncataloged Data Sets w/CLIST (was Re: What is needed to run IPCS ...)
On Fri, 2 May 2008 12:10:49 -0500, Mark Zelden wrote: You can't use TSOLIB from REXX or I *would* have the entire thing in REXX. You have to queue it to the stack and that won't execute until you leave the REXX. Which means using something up front to get the TSOLIB in place. Even more confusing Thanks. YLSED. Sorta missed part of what you wrote. Good point... I should be able to use CALL *(BPXWDYN) 'CONCAT DDLIST(MIGLIB,SIEAMIGE) MSG(2)' In your circumstance, I'd be inclined to use MSG(WTP) rather than MSG(2). But I've already been wrong once today. YMMV. And I've sometimes had to mix metaphors in Rexx: several address TSO allocate ... (can't CALL *(BPXWDYN) 'alloc ...' because of the 100-char PARM limit), followed by CALL *(BPXWDYN) 'concat ...'. Ugh. -- gil -- 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