If, as discussed earlier, the JCL/SET variables were snap-shotted into a ASASYMBM table for each jobstop, then it would be easy to write a shell command to grab them, or perhaps have this done automatically by COZBATCH. Of course they might be useful for any program, but the synergy with running Posix shells in batch is obvious.
Kirk Wolf Dovetailed Technologies http://dovetail.com On Tue, Sep 22, 2009 at 8:57 AM, Paul Gilmartin <[email protected]>wrote: > On Tue, 22 Sep 2009 14:44:08 +0100, Andy Robertson wrote: > > > > http://home.clara.net/andywrobertson/mvsinstasm.html > > > >The facility does not create a POSIX environment variable but just a > single > >string held in the name/token pairs of the job. > > > Can that string contain the values of JCL symbols? > > >............................................. > > > >What I would like, or at least could use, would be some "new" JCL > statement > >or function which would create an POSIX environment variable which would > be > >"global" to the job. This would let me use the oe_env_np() UNIX call in my > >program. This would be conceptually similar to an EXEC, except that it > >wouldn't really run a program. ... > > > Would this be preferable to being able to call BPXBATCH (or COZBATCH) > with a very long PARM string containing multiple EXPORT commands? > > -- 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 > ---------------------------------------------------------------------- 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
