On 29-Oct-2015 15:16 -0500, Steinmetz, Paul wrote:
Actually, if there is a better solution, I really need the last
command (RNMOBJ) with parameters called in job abc.
IMO the best solution is to let the code doing the RNMOBJ to deal
with whatever needs to be done. The code doing the RNMOBJ surely knows
what was coded on the parameters.
There is no guarantee that a Rename Object request message will even
be visible in an active joblog; the other job may have ended already,
the rename object may have bee invoked instead of the RNMOBJ command,
logging CL commands in a CLP is optional [Log Commands (LOG)
specification], logging CL commands in a job is optional [Log CL Program
(LOGCLPGM) specification] though LOG(*YES) overrides that, and if the
request is not in a compiled object [and is instead *EXEC or via REXX or
some other CL interpreter] then those logging settings do not even
apply. But even forcibly specifying *YES for the LOG() parameter of a
compiled CL is not necessarily helpful, as the message(s) could have
The auditing of command strings and intercepting the command with the
change command exit program are potential alternatives.