× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Actually, the user index and data queue suggestions are both practical. You only have to create one object for all jobs that use this function. As the submitting jobs are either interactive or web pages, it's unlikely they would submit multiple jobs rapidly, so both of the options are viable. They're not as ideal as using an environment variable or the LDA, but as Jon has clearly stated that neither is viable for him, IMO using a user index or data queue are the only practical options left.


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Lazarus
Sent: Monday, July 30, 2012 11:29
To: RPG programming on the IBM i / System i
Subject: RE: Seeking inspiration ...

Don,

There are several restrictions in play:
1) The LDA cannot remain modified, at the point where any other program in the job stream requires the original values.

2) No parm changes can be made. Since the second job is submitted from the first, how would the submitter communicate to the submitted job which object to look at? This is true regardless of whether the mechanism is a *DTAARA, *FILE, *USRSPC, etc. QTEMPs aren't shared between jobs.

The only practical suggestions so far seem to be using an environment variable (which requires a change to the SBMJOB command string) or saving the LDA immediately before SBMJOB and restoring it immediately after the SBMJOB is executed.

-mark



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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.