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 ______________________________________________________________________ >From what I understand, any "variables" set using the SET JCL command are simply used for textual replacements during JCL conversion and are not available at execution time via any API. What might be nice would be an extention of the UNIX "Environment Variable" concept so that they can be set via JCL, then accessed via the UNIX APIs already in z/OS. // ENVVAR name=value or maybe //name ENVVAR value Or, to be more UNIX'y //name EXPORT value // EXPORT name=value // UNSET name //name SETENV value // SETENV name=value // SETENV name= The EXPORT and UNSET are for the Bourne Shell people. The SETENV is for the tcsh shell people. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology ---------------------------------------------------------------------- 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
