On Sun, Nov 10, 2024 at 10:51:22PM +0200, Steff Gladstone wrote:
> What is the best way of modifying JCL after the job has been
> submitted, in order to conditionally add another DDNAME to a JOB STEP? Or
> perhaps adding parameters to the PARM string on the EXEC statement.
questions:
1. When is "after the job has been submitted"?
Is this the submit command or internall reader?
(ie: could you make your modifications by having your own submit
command or intercepting the normal one?)
2. Do these modifications have to occur to steps inside procedures?
(hard to do at the submit point).
I'd think twice (or more) about what the real requirements are before
following this path. Likely whatever you are trying could be done
via some other way. Whatever is going to use that DD could instead
talk to some STC or something...
> We were thinking of using the IEFUSI exit point, allocating a file
> dynamically before the main program of the job-step is attached.
https://www.ibm.com/docs/en/zos/2.1.0?topic=exits-iefusi-step-initiation-exit
Says that IEFUSI is before the step starts so it's runs as part of
the initator. So that added DD would be usable by the initator but not
likely by the job step. It says that both dynamic allocation or putting
the DD in the initator procedure is ok. Since we don't know what you
are really trying to do it isn't clear if this works or not.
Anyway, another exit you might consider is the converter interpreter
internal text exit, however this doesn't allow adding JCL statements
but likely could modify EXEC parm values.
https://www.ibm.com/docs/en/zos/2.4.0?topic=processing-modifying-converter-interpreter-text
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
