Mike Cunningham wrote:

Thanks Scott, I would be interested in seeing how to do this. I am on V5R4 and using ILE RPG and I have already code that is using the putenv API in one program and getting them back with the getenv in a second. Thinking if using this to replace the passing of parms on a PLIST to help reduce maintenance time.

Environment variables do have their uses, for sure.

I had PgmA that called PgmB that called PgmC. I needed to pass a 'parm' from A to C without changing B. That's a fairly simplified description of the scenario, but it mostly covers the point.

By adding a job environment variable in A, I had no problem picking it up in C, nor anywhere else I might've wanted it below B.

Handy when it fits.

Tom Liotta

-----Original Message-----

Sure. There's an array of pointers named 'environ' that's exported from
the ILE C runtime library. You can interrogate that array of pointers
to get a list of all of the job-level envvars.

If you need more information, tell me which language you'd like to code
this in, and which release you're using.


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.