Job-level environment variables carry request context down the IBM i call stack
IT Jungle's Guru shows SYSTOOLS.PUTENV and SYSTOOLS.GETENV setting a job-level variable that any program deeper in the same job can read, with no new parameters threaded through the stack. Have the door set one when a request comes from an agent, so the program that would write stages the change for a person instead, and clear it at transaction end so a stale flag never leaks into the next request.
Built In.
The best of the log, every two weeks. One idea, one proof, one next step.
Built In.
The best of the log, every two weeks. One idea, one proof, one next step.
References do not imply endorsement. The link goes to the original source; the words are ours. Silver Lake Financial Group and Alder & Pine Home, where mentioned, are fictitious demonstration companies.