Hi Felipe Locci
in order to successful get the job sysout from Z/os runs you will need to provide an USER that is allowed to perform the action on Z/os side, that means the user defined on the API Environment utilized to get the initial Authentication token must map to an Existing Z/os Security system valid user. Our shop utilize a distinct user env for Z/os service calls.
Once you have that, you need to provide the correct "controlm" name and valid active job order id.
The correct CTM API service call is :
ctm run job:output::get <jobId> [runNo]
<jobId> is "<controlm name>:<job order id>"
"controlm name" is the name of the active gateway that connect to Z/Os Control-M.
runNo: defalult is last run.
I Hope You make it.
Hi Felipe, it seems that for mainframe you need to specify the JES JOBID.
When you look at a mainframe job output history it shows the JES JOBID:
The only way I can think to work around this is to perform a job:log::get and parse the response to identify the JOBNAME/JOBID.
I wonder if BMC would class this as a bug? As the job log clearly shows the RUN NUMBER=xxxxx details.