× 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.



How often will the submitting job submit jobs? Will the "shared" data change for each submitted job? Does it matter if the submitting job changes the data after submitting a job or should it behave exactly like the LDA where the submitted job's data is a copy of the submitting job's data? Knowing the answers to these questions will help with us come up with solutions. For now, I'll just take a stab at it.

How about using an index (user index)? You can key it by the 26-byte submitter's job name and any other information that is appropriate. If you need to have it behave exactly like the LDA where the submitted job (that would be each submitted job, if many are submitted) gets its own copy of the data, perhaps you could put in a timestamp as part of the key. The submitted job could access the index entry by partial key (the submitter's job ID), deleting the record as it accesses it (you can choose to receive the contents of an index entry when you delete it). That way the second job will access the second copy of the index entry.

Or, if the key is 52 bytes (the submitter's job ID plus 26 blanks) then the submitted job can update (insert with update) the index record, changing the second 26-bytes to its job ID. In this case, the submitter should insert the index entry with blanks in the second 26 bytes. Each submitted job would then initially access the record using the submitter's job ID and 26 blanks as the search argument. The submitted job should delete the index entry at some point before it ends, unless you want the data for historical and/or troubleshooting purposes.

Of course, if you are submitting many jobs in a short period of time this might be problematic if the data for each job is different and the submitted jobs accessed the index out of order of submission.



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Sunday, July 29, 2012 17:08
To: Rpg400 Rpg400-L
Subject: Seeking inspiration ...

I have a series of programs that need to be able to share some basic information.

Solution must have similar characteristics to the LDA in as much as it must be available to any batch job submitted from code running in interactive or web mode,

BUT there are some limitations:

1) Adding additional parameter(s) is not an option

2) Using the LDA is not an option (other software thinks it "owns" it)

3) Does not involve the use of a file if at all possible.

Everything I have thought of so far falls apart somewhere along the path - so I'm hoping someone else here has dealt with a similar issue and can stop me from going round in circles with this one.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com



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.