> -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of GAVIN Darren * OPS EAS > Sent: Friday, January 04, 2008 2:50 PM > To: [email protected] > Subject: Re: JCL parms > > > John, > > Or better yet an enhancement by IBM to the JES Sub System > itself so that > it pushes the JCL Variables into Environment Variables as soon as the > Job first fires up. > > Also I think LE adds a routine for Environment Variables as > well called > CEEENV at Z/OS levels 1.7 and later. > > Darren
That would not be JES[23], but the initiator. Again, it appears that JCL variables (SET) do not exist in any form available to the initiator. But IBM would be the one to be in the position to "make it so!", possibly via SJF like they did the OUTPUT JCL statement. Of course, in this case, IBM should supply an API. I like the environment variable route myself, especially since it would be "transparent" to batch initiated UNIX programs (including JAVA / JZOS), which are used to looking at environment variables. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. ---------------------------------------------------------------------- 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
