|
...or you could even export the job date from the service program and only call the procedure if the exported job date is blank... Maybe give even better performance... But I think we're probably going overboard here :-) Just use the PSDS! On 9/8/06, Barbara Morris <bmorris@xxxxxxxxxx> wrote:
The RPG runtime calls an API to get the job number for the PSDS. I would just use the PSDS, but if you need to get the job name/user/number often, you could have a service program in a named activation group with a procedure that just returns the job info from its PSDS. The PSDS would only get initialized once per job, so the cost of getting the job info would basically be the cost of making the call to the procedure, for all except the first call in the job.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
