|
Hi Jon -
On Tue, 31 Jul 2012 18:03:51 -0400, Jon Paris
<jon.paris@xxxxxxxxxxxxxx> wrote:
Thanks to everybody for the various suggestions - it has been an interesting (if frustrating) experience.
Here's another suggestion ...
A permanent file with two key fields and one or more non-key fields.
Key field 1 is the job identification of the submitting job (i.e. job
name plus user plus job number). Key field 2 is a timestamp keyed
descending. The non-key field(s) are whatever you need to store the
data you want to pass.
Before the SBMJOB takes place, the submitting job runs a program to
write a record to the file with the submitting job's identification,
the current timestamp, and the data to be passed.
The submitted job runs a program which gets the submitting job's
identification and the timestamp of when the submitted job was
submitted. It does a setll to the file with those two pieces of
information followed by a reade with just the job identification.
Unless someone changes the system date or time while the submitting
job is doing its thing, this should retrieve the record which contains
the data that this submitted job needs.
Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.
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.