Applying traces to a started task

1 Likes

Applying traces to a started task

Simon Exton explains how to add traces to a started task

Tags:

Labels:

How To-Best Practice
Videos
Comment List
Anonymous
Parents
  • Reformatting Jeff's earlier response:

     

    1) Issue the following MVS modify commands to enable started task tracing:

    /F stcname,TRACE,YES,CMN

    /F stcname,TRACE,YES,SER

    /F stcname,TRACE,ON,U=userid

    /F stcname,NETTRACE,ON,U=userid,SIZE=4096

    /F stcname,HLXTRACE,ON,EXIT=*,USER=*

    2) Recreate the problem.

    3) Once recreated, immediately disable all the traces by replacing 'YES' with 'NO' and 'ON' with 'OFF' in each of the above modify commands.

    4) Send Support a copy of: a) ALL of the output generated by the Server and HLLX (if active) started tasks (i.e. JESMSGLG,JESJCL, SERPRINT, etc.). Please ensure that any downloaded output files have a record length of at least 161 to avoid truncating the trace data.

Comment
  • Reformatting Jeff's earlier response:

     

    1) Issue the following MVS modify commands to enable started task tracing:

    /F stcname,TRACE,YES,CMN

    /F stcname,TRACE,YES,SER

    /F stcname,TRACE,ON,U=userid

    /F stcname,NETTRACE,ON,U=userid,SIZE=4096

    /F stcname,HLXTRACE,ON,EXIT=*,USER=*

    2) Recreate the problem.

    3) Once recreated, immediately disable all the traces by replacing 'YES' with 'NO' and 'ON' with 'OFF' in each of the above modify commands.

    4) Send Support a copy of: a) ALL of the output generated by the Server and HLLX (if active) started tasks (i.e. JESMSGLG,JESJCL, SERPRINT, etc.). Please ensure that any downloaded output files have a record length of at least 161 to avoid truncating the trace data.

Children
No Data
Related Discussions
Recommended