Josef_Scharl_103

How to activate a trace in z/OS CallAPI?

Discussion created by Josef_Scharl_103 on Nov 18, 2016

For activating a trace at the z/OS CallAPI – program UCXBM25C – two modification in the JCL are necessary:

  1. Add the parameter “TRACE=Y” in the PARM parameter string of the EXEC statement.
  2. Add an additional DD statement “TRACE”. For example with “SYSOUT=*”.

Here an example JCL:

 

//CALLA112 JOB ,'J.SCHARL',NOTIFY=&SYSUID
//UCCALL   EXEC PGM=UCXBM25C,REGION=65M,
// PARM='INI=UC4SCJ.UC412.UCXJM25C.INI(CP001) TRACE=Y'
//STEPLIB  DD DSN=UC4SCJ.UC412.UCXJM25.LOAD,DISP=SHR
//SYSIN    DD DISP=SHR,DSN=UC4SCJ.UC4.SCRIPT(SEND#MSG)
//SYSPRINT DD SYSOUT=*
//SYSOUT   DD SYSOUT=*
//TRACE    DD SYSOUT=*
//

 

pc409efg2rlc.png

The trace output can be found in the JES spool file “TRACE” of the job:

qbww7bxbkopd.png


Outcomes