Re: Possible new SYSTEM symbols in JCL.
Discussions on this, and other forums, and SHARE requirements finally drove IBM to change the APF authorization of link list and to prevent user key CSA. If change is really desired, submit a SHARE requirement. Dennis Roach GHG Corporation Lockheed Martin Mission Services Flight Design and Operations Contract NASA/JSC Address: 2100 Space Park Drive LM-15-4BH Houston, Texas 77058 Mail: P.O. Box 58487 Mail Code H4C Houston, Texas 77258 Phone: Voice: (281)336-5027 Cell: (713)591-1059 Fax:(281)336-5410 E-Mail: dennis.ro...@lmco.com All opinions expressed by me are mine and may not agree with my employer or any person, company, or thing, living or dead, on or near this or any other planet, moon, asteroid, or other spatial object, natural or manufactured, since the beginning of time. > -Original Message- > From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On > Behalf Of DanD > Sent: Wednesday, April 29, 2009 1:49 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: Possible new SYSTEM symbols in JCL. > > - Original Message - > From: "Ted MacNEIL" > > this one has gone on for years and has produced nothing new under the > sun. > > I wouldn't say NOTHING Ted. > Maybe nothing from IBM but Shane wrote an IEFUJV exit that updates > variables > on the SET JCL statement and I expanded it to add a whole bunch of > DATE/TIME > related symbols (as well as other symbols). > Of course, as these are all done at reader time it's up to the > installation > to make their own decision whether these symbols are valid or not for > their > site. > > As for the original poster... > I've added &ZJOBID. and sent a new version of file 452 to Sam. It > should be > on the updates section of the CBT site in a few days. > > DanD > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
>I wouldn't say NOTHING Ted. Semantics! It's produced NOTHING from IBM. That was my point! - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
- Original Message - From: "Ted MacNEIL" this one has gone on for years and has produced nothing new under the sun. I wouldn't say NOTHING Ted. Maybe nothing from IBM but Shane wrote an IEFUJV exit that updates variables on the SET JCL statement and I expanded it to add a whole bunch of DATE/TIME related symbols (as well as other symbols). Of course, as these are all done at reader time it's up to the installation to make their own decision whether these symbols are valid or not for their site. As for the original poster... I've added &ZJOBID. and sent a new version of file 452 to Sam. It should be on the updates section of the CBT site in a few days. DanD -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
I have a utility that will also generate JCL, based on a model, that can perform substitutions of such things as RACF UID, jobname, jobnumber, etc. but I'm not sure if it will satisfy the need of the OP. If he'll contact me offlist, I'll try and share a copy with him and he can make his own decision. Scott T. Harder wrote: Wow Cool ! Will check it out. All the best, Scott T. Harder -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu]on Behalf Of Clement Clarke Sent: Wednesday, April 29, 2009 10:17 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Possible new SYSTEM symbols in JCL. The Jol Universal Command language (which can be used as a replacement for JCL and Clists, and which can run jobs in Batch or TSO) has quite a few symbolic variables preset. Furthermore, User Exits or Macros can be used to set additional Symbolics at startup, or later. Symbolic Variables can be tested, or changed, and full arithmetic expressions (similar to PL/I) can be performed on them. These are some of the Symbolic Variables that are set at startup: %SYSDATE The current date in Julian format e.g. 09290 %DAY MONDAY, TUESDAY, etc. %MONTH JANUARY, FEBRUARY, etc. %MONTHNO 01, 02 Through 12 %DAYNO 01 through 31 %YEAR 2009, 2010, etc. %HOURS 0 through 23 %MINS 0 through 59 %SECS 0 through 59 %SYSUIDSystem user identification %SYSPREF Dataset prefix %SYSPFKProgram function key number from PANELs %SYSTEMMFT, MVT, VS1, VS2, VM, etc. %SPOOL HASP, ASP, JES1, JES2, JES3, or Blank Jol is a free form scripting language similar to PL/I and Rexx. It is available for Z/OS and a Windows version can create JCL to be submitted to the mainframe. Clement Clarke Scott T. Harder wrote: John, You are not the only one. I've always found it frustrating that &SYSUID is the only available symbol/variable that is available for use in batch. Seems to me that there should be many more. Aside from the temp data set names you can use - and this is no news to everyone - we have to hardcode EVERYTHING in JCL. IBM should start to look at JCL like more of a scripting language, IMO, and provide a lot more of what you originally posted about. All the best, Scott T. Harder -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html Looking for insurance? Click to compare and save big. http://thirdpartyoffers.netzero.net/TGL2241/fc/BLSrjpYVv6vtKLTM9AIrKwmPYyaMZnK8PMtei4cMfUGcJF3rxBIdmnfl9Ak/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- Rick -- Remember that if you're not the lead dog, the view never changes. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
Bingo. All the best, Scott T. Harder -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu]on Behalf Of Paul Gilmartin Sent: Wednesday, April 29, 2009 12:28 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Possible new SYSTEM symbols in JCL. On Wed, 29 Apr 2009 22:16:55 +0800, Clement Clarke wrote: >The Jol Universal Command language (which can be used as a replacement >for JCL and Clists, and which can run jobs in Batch or TSO) has quite a >few symbolic variables preset. >... >Jol is a free form scripting language similar to PL/I and Rexx. > >It is available for Z/OS and a Windows version can create JCL to be >submitted to the mainframe. > Does this imply that on z/OS it does not submit JCL? Does it perform DSN ENQs en masse to preclude the possibility of deadlock? Can it be used to create multi-file tapes? To do this reasonably, one needs (analogues of) VOL=REF and RETAIN, available in JCL but not in TSO. >> You are not the only one. I've always found it frustrating that &SYSUID is >> the only available symbol/variable that is available for use in batch. >> Seems to me that there should be many more. Aside from the temp data set >> names you can use - and this is no news to everyone - we have to hardcode >> EVERYTHING in JCL. IBM should start to look at JCL like more of a scripting >> language, IMO, and provide a lot more of what you originally posted about. >> I'm the third one. Alas, what we want is contrary to the design objectives of JCL, which needs to perform a static assessment of resources required by a job in order to avoid deadlocks and preventable locking of idle resources. The suggestions frequently made here that the ambiguities between Reader values, Converter values, and Execution values could be resolved by providing multiple symbols are naive (or perhaps sarcastically rhetorical): given the need for static assessment, probably only the first, certainly not the last, is technically feasible. But granted that much, the wish most frequently expressed here is for time and date to incorporate in data set names. For this purpose, the Reader time would be widely useful; it corresponds closely to the tailoring, scripting, exit, and periodically updated INCLUDE member circumventions that many of us have used. We're adults. If new system symbols were available in batch JCL such as RDRTIME and RDRDATE with the obvious mnemonic value, we're capable of understanding that if a job lingers in the input queue for 6 months, those variables will have old values, not current ones, even as we understand the similar behavior of our tailoring etc. circumventions. As an analogy, SDSF allows me to sort on a job's submit time, start time, or completion time. In fact, I've chosen the first because it is notionally closest to my concept of chronological order. Users should be given a choice between the hazards of DYNALLOC and the exaggerated (in my view) uncertainties of static time variables. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html Hit it out of the park with a new bat. Click now! http://thirdpartyoffers.netzero.net/TGL2241/fc/BLSrjpYan8tO2gQZaPWx7sTfaMsI0yN1VNDipZpYI6PAdiRyHiJg14zpL8k/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
>We're adults. Yes, we are. And, as such, we should accept that IBM is not going to change their stance regarding SYSTEM Symbols in (Batch) JCL. And, we should move on and find other things to crab about; this one has gone on for years and has produced nothing new under the sun. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
On Wed, 29 Apr 2009 22:16:55 +0800, Clement Clarke wrote: >The Jol Universal Command language (which can be used as a replacement >for JCL and Clists, and which can run jobs in Batch or TSO) has quite a >few symbolic variables preset. >... >Jol is a free form scripting language similar to PL/I and Rexx. > >It is available for Z/OS and a Windows version can create JCL to be >submitted to the mainframe. > Does this imply that on z/OS it does not submit JCL? Does it perform DSN ENQs en masse to preclude the possibility of deadlock? Can it be used to create multi-file tapes? To do this reasonably, one needs (analogues of) VOL=REF and RETAIN, available in JCL but not in TSO. >> You are not the only one. I've always found it frustrating that &SYSUID is >> the only available symbol/variable that is available for use in batch. >> Seems to me that there should be many more. Aside from the temp data set >> names you can use - and this is no news to everyone - we have to hardcode >> EVERYTHING in JCL. IBM should start to look at JCL like more of a scripting >> language, IMO, and provide a lot more of what you originally posted about. >> I'm the third one. Alas, what we want is contrary to the design objectives of JCL, which needs to perform a static assessment of resources required by a job in order to avoid deadlocks and preventable locking of idle resources. The suggestions frequently made here that the ambiguities between Reader values, Converter values, and Execution values could be resolved by providing multiple symbols are naive (or perhaps sarcastically rhetorical): given the need for static assessment, probably only the first, certainly not the last, is technically feasible. But granted that much, the wish most frequently expressed here is for time and date to incorporate in data set names. For this purpose, the Reader time would be widely useful; it corresponds closely to the tailoring, scripting, exit, and periodically updated INCLUDE member circumventions that many of us have used. We're adults. If new system symbols were available in batch JCL such as RDRTIME and RDRDATE with the obvious mnemonic value, we're capable of understanding that if a job lingers in the input queue for 6 months, those variables will have old values, not current ones, even as we understand the similar behavior of our tailoring etc. circumventions. As an analogy, SDSF allows me to sort on a job's submit time, start time, or completion time. In fact, I've chosen the first because it is notionally closest to my concept of chronological order. Users should be given a choice between the hazards of DYNALLOC and the exaggerated (in my view) uncertainties of static time variables. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
Wow Cool ! Will check it out. All the best, Scott T. Harder -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu]on Behalf Of Clement Clarke Sent: Wednesday, April 29, 2009 10:17 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Possible new SYSTEM symbols in JCL. The Jol Universal Command language (which can be used as a replacement for JCL and Clists, and which can run jobs in Batch or TSO) has quite a few symbolic variables preset. Furthermore, User Exits or Macros can be used to set additional Symbolics at startup, or later. Symbolic Variables can be tested, or changed, and full arithmetic expressions (similar to PL/I) can be performed on them. These are some of the Symbolic Variables that are set at startup: %SYSDATE The current date in Julian format e.g. 09290 %DAY MONDAY, TUESDAY, etc. %MONTH JANUARY, FEBRUARY, etc. %MONTHNO 01, 02 Through 12 %DAYNO 01 through 31 %YEAR 2009, 2010, etc. %HOURS 0 through 23 %MINS 0 through 59 %SECS 0 through 59 %SYSUIDSystem user identification %SYSPREF Dataset prefix %SYSPFKProgram function key number from PANELs %SYSTEMMFT, MVT, VS1, VS2, VM, etc. %SPOOL HASP, ASP, JES1, JES2, JES3, or Blank Jol is a free form scripting language similar to PL/I and Rexx. It is available for Z/OS and a Windows version can create JCL to be submitted to the mainframe. Clement Clarke Scott T. Harder wrote: > John, > > You are not the only one. I've always found it frustrating that &SYSUID is > the only available symbol/variable that is available for use in batch. > Seems to me that there should be many more. Aside from the temp data set > names you can use - and this is no news to everyone - we have to hardcode > EVERYTHING in JCL. IBM should start to look at JCL like more of a scripting > language, IMO, and provide a lot more of what you originally posted about. > > All the best, > Scott T. Harder > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html Looking for insurance? Click to compare and save big. http://thirdpartyoffers.netzero.net/TGL2241/fc/BLSrjpYVv6vtKLTM9AIrKwmPYyaMZnK8PMtei4cMfUGcJF3rxBIdmnfl9Ak/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
The Jol Universal Command language (which can be used as a replacement for JCL and Clists, and which can run jobs in Batch or TSO) has quite a few symbolic variables preset. Furthermore, User Exits or Macros can be used to set additional Symbolics at startup, or later. Symbolic Variables can be tested, or changed, and full arithmetic expressions (similar to PL/I) can be performed on them. These are some of the Symbolic Variables that are set at startup: %SYSDATE The current date in Julian format e.g. 09290 %DAY MONDAY, TUESDAY, etc. %MONTH JANUARY, FEBRUARY, etc. %MONTHNO 01, 02 Through 12 %DAYNO 01 through 31 %YEAR 2009, 2010, etc. %HOURS 0 through 23 %MINS 0 through 59 %SECS 0 through 59 %SYSUIDSystem user identification %SYSPREF Dataset prefix %SYSPFKProgram function key number from PANELs %SYSTEMMFT, MVT, VS1, VS2, VM, etc. %SPOOL HASP, ASP, JES1, JES2, JES3, or Blank Jol is a free form scripting language similar to PL/I and Rexx. It is available for Z/OS and a Windows version can create JCL to be submitted to the mainframe. Clement Clarke Scott T. Harder wrote: John, You are not the only one. I've always found it frustrating that &SYSUID is the only available symbol/variable that is available for use in batch. Seems to me that there should be many more. Aside from the temp data set names you can use - and this is no news to everyone - we have to hardcode EVERYTHING in JCL. IBM should start to look at JCL like more of a scripting language, IMO, and provide a lot more of what you originally posted about. All the best, Scott T. Harder -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.287 / Virus Database: 270.12.7/2085 - Release Date: 04/28/09 18:02:00 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
"John McKown" wrote in message news:.. . > On Tue, 28 Apr 2009, Gary Green wrote: > > > John, > > > > Not certain if this helps but I have some Rexx code which I execute in > > batch. This particular Rexx will take input file(s) and process each line > > from each input file and resolve any symbolics it finds and then passes the > > input line to a specific output DD name. I use the standard system > > symbolics and a few of my own. > > > > The output file is then passed down to another step in the job which never > > knows where the SYSIN control cards came from. > > > > Works like a champ. > > > > Perhaps you could put something together like this? I would offer to pass > > it along but I would need permission first. (new employer) > > > > > > Gary Green > > Never use a 2x4 when a 2x6 will do just as well! > > Thanks for the offer. I could do that myself. As I said in an earlier > post, I'm being very lazy and was just wondering if anybody else thought > these symbols would be helpful. Apparently I'm the only one who would. > It's not a big deal. > John, I didn't say these symbols are not helpful. I only said that discussing things that IBM is not going to deliver anyway is dull and pointless -;). Kees. > -- > Trying to write with a pencil that is dull is pointless. > > Maranatha! > John McKown > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
John, You are not the only one. I've always found it frustrating that &SYSUID is the only available symbol/variable that is available for use in batch. Seems to me that there should be many more. Aside from the temp data set names you can use - and this is no news to everyone - we have to hardcode EVERYTHING in JCL. IBM should start to look at JCL like more of a scripting language, IMO, and provide a lot more of what you originally posted about. All the best, Scott T. Harder -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu]on Behalf Of John McKown Sent: Wednesday, April 29, 2009 7:32 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Possible new SYSTEM symbols in JCL. On Tue, 28 Apr 2009, Gary Green wrote: > John, > > Not certain if this helps but I have some Rexx code which I execute in > batch. This particular Rexx will take input file(s) and process each line > from each input file and resolve any symbolics it finds and then passes the > input line to a specific output DD name. I use the standard system > symbolics and a few of my own. > > The output file is then passed down to another step in the job which never > knows where the SYSIN control cards came from. > > Works like a champ. > > Perhaps you could put something together like this? I would offer to pass > it along but I would need permission first. (new employer) > > > Gary Green > Never use a 2x4 when a 2x6 will do just as well! Thanks for the offer. I could do that myself. As I said in an earlier post, I'm being very lazy and was just wondering if anybody else thought these symbols would be helpful. Apparently I'm the only one who would. It's not a big deal. -- Trying to write with a pencil that is dull is pointless. Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html Be your own boss today with Contractor Training. Click here. http://thirdpartyoffers.netzero.net/TGL2241/fc/BLSrjpYbjI6nfMHQ88gcW8G9z1I2teBevVFwukILQmsm0t7z492K2U5t65i/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
On Tue, 28 Apr 2009, Gary Green wrote: > John, > > Not certain if this helps but I have some Rexx code which I execute in > batch. This particular Rexx will take input file(s) and process each line > from each input file and resolve any symbolics it finds and then passes the > input line to a specific output DD name. I use the standard system > symbolics and a few of my own. > > The output file is then passed down to another step in the job which never > knows where the SYSIN control cards came from. > > Works like a champ. > > Perhaps you could put something together like this? I would offer to pass > it along but I would need permission first. (new employer) > > > Gary Green > Never use a 2x4 when a 2x6 will do just as well! Thanks for the offer. I could do that myself. As I said in an earlier post, I'm being very lazy and was just wondering if anybody else thought these symbols would be helpful. Apparently I'm the only one who would. It's not a big deal. -- Trying to write with a pencil that is dull is pointless. Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
"Ted MacNEIL" wrote in message news:<1576110636-1240944676-cardhu_decombobulator_blackberry.rim.net-355 6344...@bxe1305.bisx.prod.on.blackberry>... > >The only one that I can think of is a case where a job is NJE transmitted to another > site and receives a different job number. > >In that case, I think the job number should be the job number at the execution site. > > This is exactly why IBM refuses to open up system symbols to Batch. > > Why should it be the execution site, I can see reasons for submitting site, or worse, printing site, if different. > > There are so many 'correct' resolutions for system symbols, that IBM has erred on the side of the 'principle of least astonnishment'. > > I don't know what is really right, but I do know I don't want to be involved in determining what it is if it's every opened up! > > - That's exactly the reason for my first reaction: whatever we argue, IBM will never deliver it, so it is useless to discuss this direction to solve your problems. As we could read, there are other beautiful, well working solutions available. Kees. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
Hi Gary, Sounds awesome! If you can share, that would be gr8. All the best, Scott T. Harder -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu]on Behalf Of Gary Green Sent: Tuesday, April 28, 2009 8:06 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Possible new SYSTEM symbols in JCL. John, Not certain if this helps but I have some Rexx code which I execute in batch. This particular Rexx will take input file(s) and process each line from each input file and resolve any symbolics it finds and then passes the input line to a specific output DD name. I use the standard system symbolics and a few of my own. The output file is then passed down to another step in the job which never knows where the SYSIN control cards came from. Works like a champ. Perhaps you could put something together like this? I would offer to pass it along but I would need permission first. (new employer) Gary Green Never use a 2x4 when a 2x6 will do just as well! -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of John McKown Sent: Tuesday, April 28, 2009 12:47 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Possible new SYSTEM symbols in JCL. On Tue, 28 Apr 2009 11:36:31 -0500, Rick Fochtman wrote: >John, geting the JOBNAME shouldn't be too much of a problem; the value >could be set at conversion time. Getting the job number might be more >of a problem, since JES would have to get involved here. > >You might wanty to consider an Assember routine that will query JES2 >for job number and your ASCB for the job name. Then do a dynamic >allocation of the HFS/ZFS file and create the appropriate JCL, then >pump it through the internal reader for your PERL step. Consider using >the DYNAM routine from the CBTTAPE to do the allocation. > >-- >Rick I could do the above. If I did not feel so tired that even typing this email is difficult (ongoing medical condition). I guess what I should really do if I want any "new system symbols" is simply write a JES2 exit 2 to insert a bunch of // SET symbol=value cards immediately after the JOB card. But that is way too much trouble too. And, in any case, that would violate our standard of "No mods, no exits, no customization! Plain vanilla or death!" -- John -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html Click to receive credit card help and get out of debt fast. http://thirdpartyoffers.netzero.net/TGL2241/fc/BLSrjpYVrpdTMHlKJSw5OlO4vzyAkFUH7EjESB8el9A6NOv7Ndmkc3VBwDe/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
John, Not certain if this helps but I have some Rexx code which I execute in batch. This particular Rexx will take input file(s) and process each line from each input file and resolve any symbolics it finds and then passes the input line to a specific output DD name. I use the standard system symbolics and a few of my own. The output file is then passed down to another step in the job which never knows where the SYSIN control cards came from. Works like a champ. Perhaps you could put something together like this? I would offer to pass it along but I would need permission first. (new employer) Gary Green Never use a 2x4 when a 2x6 will do just as well! -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of John McKown Sent: Tuesday, April 28, 2009 12:47 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Possible new SYSTEM symbols in JCL. On Tue, 28 Apr 2009 11:36:31 -0500, Rick Fochtman wrote: >John, geting the JOBNAME shouldn't be too much of a problem; the value >could be set at conversion time. Getting the job number might be more >of a problem, since JES would have to get involved here. > >You might wanty to consider an Assember routine that will query JES2 >for job number and your ASCB for the job name. Then do a dynamic >allocation of the HFS/ZFS file and create the appropriate JCL, then >pump it through the internal reader for your PERL step. Consider using >the DYNAM routine from the CBTTAPE to do the allocation. > >-- >Rick I could do the above. If I did not feel so tired that even typing this email is difficult (ongoing medical condition). I guess what I should really do if I want any "new system symbols" is simply write a JES2 exit 2 to insert a bunch of // SET symbol=value cards immediately after the JOB card. But that is way too much trouble too. And, in any case, that would violate our standard of "No mods, no exits, no customization! Plain vanilla or death!" -- John -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
Gil, Of course you know very well that this use of "cp" is not documented :-) Kirk On Tue, Apr 28, 2009 at 11:16 AM, Paul Gilmartin wrote: > On Tue, 28 Apr 2009 10:51:55 -0500, Kirk Wolf wrote: >> >>In this example, why not just use a temporary MVS dataset with >>DISP=PASS into the Unix step? >> >>Then use: >> >>fromdsn //DD:MYTEMP | process >> >>or: >> >>cp //DD:MYTEMP /dev/fd1 | process >> > Where is that last construct documented as supported? > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
If you check out CBT file 452 you'll find an IEFUJV that does the "// SET
XYZ=&ZJOBNAME. " that you're looking for.
If you give me a few minutes I'll add &ZJOBID.
Dan
John McKown wrote:
I've just ran into a situation where I could really use some new
"system symbols" in JCL. In a batch job, we can basically only use
&SYSUID in the
JCL. I could use two more, and I don't think that they would
introduce any problems. They would be &SYSJOBNA which would be the
job name, and &SYSJOBNU which would be the "job number" (like
JOB12345). My basic use for these
would be an attempt to have an "almost unique" dataset name or UNIX
PATH
name generated with these values. I do some really weird stuff (as is
likely already known). My application in this one case was for
something like:
//LISTCAT EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
LISTC LVL(some.qual) ALL OUTFILE(O)
//O DD PATH='/u/myid/sysout/&SYSJOBNA..&SYSJOBNU',
// PATHDISP=(KEEP,KEEP),
// FILEDATA=TEXT,
// PATHMODE=(SIRUSR,SIWUSR),
// PATHOPTS=(OCREAT,OTRUNC,OWRONLY)
//*
//PROCESS EXEC COZBATCH,
// PARM='/jobname=&SYSJOBNA jobnumber=&SYSJOBNU'
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//STDIN DD *
. /etc/profile
. ~/.profile
cd ~/myid/sysout
process <${jobname}.${jobnumber}
/*
//
The "process" was actually a Perl script which did some messaging of
the LISTCAT output for me.
In any case, does this sound reasonable? Am I overlooking a case where
either of these system symbols could be "indeterminate"? The only one
that I can think of is a case where a job is NJE transmitted to
another site and receives a different job number. In that case, I
think the job number should
be the job number at the execution site.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
>The only one that I can think of is a case where a job is NJE transmitted to >another site and receives a different job number. >In that case, I think the job number should be the job number at the execution >site. This is exactly why IBM refuses to open up system symbols to Batch. Why should it be the execution site, I can see reasons for submitting site, or worse, printing site, if different. There are so many 'correct' resolutions for system symbols, that IBM has erred on the side of the 'principle of least astonnishment'. I don't know what is really right, but I do know I don't want to be involved in determining what it is if it's every opened up! - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
On Tue, 28 Apr 2009 11:36:31 -0500, Rick Fochtman wrote: >John, geting the JOBNAME shouldn't be too much of a problem; the value >could be set at conversion time. Getting the job number might be more of >a problem, since JES would have to get involved here. > >You might wanty to consider an Assember routine that will query JES2 for >job number and your ASCB for the job name. Then do a dynamic allocation >of the HFS/ZFS file and create the appropriate JCL, then pump it through >the internal reader for your PERL step. Consider using the DYNAM routine >from the CBTTAPE to do the allocation. > >-- >Rick I could do the above. If I did not feel so tired that even typing this email is difficult (ongoing medical condition). I guess what I should really do if I want any "new system symbols" is simply write a JES2 exit 2 to insert a bunch of // SET symbol=value cards immediately after the JOB card. But that is way too much trouble too. And, in any case, that would violate our standard of "No mods, no exits, no customization! Plain vanilla or death!" -- John -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
I've just ran into a situation where I could really use some new "systemsymbols" in JCL. In a batch job, we can basically only use &SYSUID in the JCL. I could use two more, and I don't think that they would introduce any problems. They would be &SYSJOBNA which would be the job name, and &SYSJOBNU which would be the "job number" (like JOB12345). My basic use for these would be an attempt to have an "almost unique" dataset name or UNIX PATH name generated with these values. I do some really weird stuff (as is likely already known). My application in this one case was for something like: - In any case, does this sound reasonable? Am I overlooking a case where either of these system symbols could be "indeterminate"? The only one that I can think of is a case where a job is NJE transmitted to another site and receives a different job number. In that case, I think the job number should be the job number at the execution site. - John, geting the JOBNAME shouldn't be too much of a problem; the value could be set at conversion time. Getting the job number might be more of a problem, since JES would have to get involved here. You might wanty to consider an Assember routine that will query JES2 for job number and your ASCB for the job name. Then do a dynamic allocation of the HFS/ZFS file and create the appropriate JCL, then pump it through the internal reader for your PERL step. Consider using the DYNAM routine from the CBTTAPE to do the allocation. -- Rick -- Remember that if you’re not the lead dog, the view never changes. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
That makes sense. I guess you could use an MVS temporary dataset, and then "tee" it into an HFS file in your shell script But hey, submit a requirement for new system symbols ;-) More important, IMO, would be to have JCL PROC/SET symbols be saved in a ASASYMBM symbol table (not necessarily the primary system symbol table). Then, programs like Unix shells could use them. But we have discussed that to death I guess... Kirk Wolf Dovetailed Technologies FWIW - our free "catsearch" shell command can also be used to process catalogs from a shell script. It uses IGGCSI00 and F1 DSCBs under the covers, and supports things like tab-delimited output. http://dovetail.com/docs/coz/dsp-ref_catsearch.html On Tue, Apr 28, 2009 at 11:09 AM, John McKown wrote: > On Tue, 28 Apr 2009 10:51:55 -0500, Kirk Wolf wrote: > >>John, >> >>In this example, why not just use a temporary MVS dataset with >>DISP=PASS into the Unix step? >> >>Then use: >> >>fromdsn //DD:MYTEMP | process >> >>or: >> >>cp //DD:MYTEMP /dev/fd1 | process >> >>Kirk Wolf >>Dovetailed Technologies > > That's a possibility. I was wanting a "permanent" UNIX file. But I could do > it some other way, I guess. I guess I was wanting to easily relate the UNIX > file to the creating job for some reason. > > -- > John > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
On Tue, 28 Apr 2009 10:51:55 -0500, Kirk Wolf wrote:
>
>In this example, why not just use a temporary MVS dataset with
>DISP=PASS into the Unix step?
>
>Then use:
>
>fromdsn //DD:MYTEMP | process
>
>or:
>
>cp //DD:MYTEMP /dev/fd1 | process
>
Where is that last construct documented as supported?
>> The "process" was actually a Perl script which did some messaging of the
>> LISTCAT output for me.
>>
could you use the new-fangled Rexx "address TSO LISTCAT" and pipe
the output into "process"? I recognize that "address TSO" imposes
some unpleasant restrictions on the use of descriptors.
Fortunately, the following works for me:
foo=`rexx "address TSO 'LISTCAT level('userid()'.TEST)'"`
-- gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
On Tue, 28 Apr 2009 10:51:55 -0500, Kirk Wolf wrote: >John, > >In this example, why not just use a temporary MVS dataset with >DISP=PASS into the Unix step? > >Then use: > >fromdsn //DD:MYTEMP | process > >or: > >cp //DD:MYTEMP /dev/fd1 | process > >Kirk Wolf >Dovetailed Technologies That's a possibility. I was wanting a "permanent" UNIX file. But I could do it some other way, I guess. I guess I was wanting to easily relate the UNIX file to the creating job for some reason. -- John -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
John,
In this example, why not just use a temporary MVS dataset with
DISP=PASS into the Unix step?
Then use:
fromdsn //DD:MYTEMP | process
or:
cp //DD:MYTEMP /dev/fd1 | process
Kirk Wolf
Dovetailed Technologies
On Tue, Apr 28, 2009 at 9:28 AM, John McKown wrote:
> I've just ran into a situation where I could really use some new "system
> symbols" in JCL. In a batch job, we can basically only use &SYSUID in the
> JCL. I could use two more, and I don't think that they would introduce any
> problems. They would be &SYSJOBNA which would be the job name, and
> &SYSJOBNU
> which would be the "job number" (like JOB12345). My basic use for these
> would be an attempt to have an "almost unique" dataset name or UNIX PATH
> name generated with these values. I do some really weird stuff (as is likely
> already known). My application in this one case was for something like:
>
> //LISTCAT EXEC PGM=IDCAMS
> //SYSPRINT DD SYSOUT=*
> //SYSIN DD *
> LISTC LVL(some.qual) ALL OUTFILE(O)
> //O DD PATH='/u/myid/sysout/&SYSJOBNA..&SYSJOBNU',
> // PATHDISP=(KEEP,KEEP),
> // FILEDATA=TEXT,
> // PATHMODE=(SIRUSR,SIWUSR),
> // PATHOPTS=(OCREAT,OTRUNC,OWRONLY)
> //*
> //PROCESS EXEC COZBATCH,
> // PARM='/jobname=&SYSJOBNA jobnumber=&SYSJOBNU'
> //STDOUT DD SYSOUT=*
> //STDERR DD SYSOUT=*
> //STDIN DD *
> . /etc/profile
> . ~/.profile
> cd ~/myid/sysout
> process <${jobname}.${jobnumber}
> /*
> //
>
> The "process" was actually a Perl script which did some messaging of the
> LISTCAT output for me.
>
> In any case, does this sound reasonable? Am I overlooking a case where
> either of these system symbols could be "indeterminate"? The only one that I
> can think of is a case where a job is NJE transmitted to another site and
> receives a different job number. In that case, I think the job number should
> be the job number at the execution site.
>
> --
> John
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
Job number can change if the job is NJE'd to another system. -Original Message- I didn't get the idea that IBM was adverse to __NEW__ system symbols in batch JCL. Just that they had stated that &SYSUID was the only one of the current system symbols which could be used. The reason given here was that all the other system symbols were "indeterminate" (such as "when is the variable resolved"?). The two symbols that I mentioned should not have this problem. But, if nobody is interested, then let's just let the thread die here. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
On Tue, 28 Apr 2009 16:34:06 +0200, Vernooy, C.P. - SPLXM wrote: > > >"John McKown" wrote in message >news:... >> I've just ran into a situation where I could really use some new >"system >> symbols" in JCL. In a batch job, > >John, > >What's the use or (re)discussing system symbols in batch JCL? >Whatever arguments we come up with, the symbols aren't going to come, >are they? > >Kees. I didn't get the idea that IBM was adverse to __NEW__ system symbols in batch JCL. Just that they had stated that &SYSUID was the only one of the current system symbols which could be used. The reason given here was that all the other system symbols were "indeterminate" (such as "when is the variable resolved"?). The two symbols that I mentioned should not have this problem. But, if nobody is interested, then let's just let the thread die here. -- John -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Possible new SYSTEM symbols in JCL.
"John McKown" wrote in message news:... > I've just ran into a situation where I could really use some new "system > symbols" in JCL. In a batch job, John, What's the use or (re)discussing system symbols in batch JCL? Whatever arguments we come up with, the symbols aren't going to come, are they? Kees. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Possible new SYSTEM symbols in JCL.
I've just ran into a situation where I could really use some new "system
symbols" in JCL. In a batch job, we can basically only use &SYSUID in the
JCL. I could use two more, and I don't think that they would introduce any
problems. They would be &SYSJOBNA which would be the job name, and &SYSJOBNU
which would be the "job number" (like JOB12345). My basic use for these
would be an attempt to have an "almost unique" dataset name or UNIX PATH
name generated with these values. I do some really weird stuff (as is likely
already known). My application in this one case was for something like:
//LISTCAT EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
LISTC LVL(some.qual) ALL OUTFILE(O)
//O DD PATH='/u/myid/sysout/&SYSJOBNA..&SYSJOBNU',
// PATHDISP=(KEEP,KEEP),
// FILEDATA=TEXT,
// PATHMODE=(SIRUSR,SIWUSR),
// PATHOPTS=(OCREAT,OTRUNC,OWRONLY)
//*
//PROCESS EXEC COZBATCH,
// PARM='/jobname=&SYSJOBNA jobnumber=&SYSJOBNU'
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//STDIN DD *
. /etc/profile
. ~/.profile
cd ~/myid/sysout
process <${jobname}.${jobnumber}
/*
//
The "process" was actually a Perl script which did some messaging of the
LISTCAT output for me.
In any case, does this sound reasonable? Am I overlooking a case where
either of these system symbols could be "indeterminate"? The only one that I
can think of is a case where a job is NJE transmitted to another site and
receives a different job number. In that case, I think the job number should
be the job number at the execution site.
--
John
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
