Maybe I should rephrase my question. I put too much emphasis on the idea of a temporary dataset.
What I am really looking for is a way of maintaining a piece of information that is created in one job step and is accessible to all succeeding job-steps. A type of memory that is getmained in one job step and persists till the end of the last job step, would be perfect. If it was possible to create a name-token with the life of the entire job, that would be perfect. But it would disappear by itself without the last job-step having to be "aware" that it was the last job-step and without being responsible to delete it. Any ideas? On Thu, 21 Nov 2024 at 15:40, Steff Gladstone <[email protected]> wrote: > Hi, > > Without specifying a file (temporary or otherwise) statically in the JCL > of a job, how can I create a temporary data record in an earlier step of > the job and have it persist and be accessible by all succeeding steps of > the job (and then be deleted by the system at the end of the job)? > > Am I correct in understanding that I cannot dynamically allocate a > temporary file with DISP=PASS? > > Thanks, > Steff Gladstone > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
