Administering transaction monitoring

You can close, open, and control the logging level for transaction monitoring log messages. If you change the logging level, the changed value overrides the value set in the Gateway daemon configuration file.

Use the /F <jobname> command with the RMEXIT option to manage the request monitoring exits running in the Gateway daemon:

  • CLOSE – Closes the log file, enabling the file to be manually archived. File closure is not supported if you use MVS DD destinations. Use the following command to close:
    /F <JOBNAME>,APPL=RMEXIT,CMD=CH51_CLOSE
    The output will be as follows:
    {"Type":"CH51", "datetime":"05/31/24 07:51:11:165", "message":"CH51 Command [CH51_CLOSE] received"}
{"Type":"CH51", "datetime":"05/31/24 07:51:11:165", "message":"CH51 log <CH51_file_path>/ch51.log now closed"}
  • OPEN – Opens the log file if the file was previously closed. Use the following command to open:
    /F <JOBNAME>,APPL=RMEXIT,CMD=CH51_OPEN
    The output will be as follows:
    {"Type":"CH51", "datetime":"05/31/24 07:55:44:926", "message":"CH51 Command [CH51_OPEN] received"}
  • Logging control – Controls the output of log messages for transaction monitoring.
    Table 1. Action required for different logging levels
    Command Level Action
    CH51_0 No logging or level 0 (zero) Disable all output, and open the file if it is closed.
    CH51_1 Logging level 1 Log the return flows, and open the file if it is closed.
    CH51_2 Logging level 2 Log the input and return flows, and open the file if it is closed.
    CH51_3 Logging level 3 Log the input and return flows; add the xid, UOW, and trngrpid tracking tokens; and then open the file if it is closed.
For example, to enable level 1 logging, run the following command on z/OS:
/F <JOBNAME>,APPL=RMEXIT,CMD=CH51_1
The output will be as follows:
{"Type":"CH51", "datetime":"05/31/24 07:38:05:025", "message":"CH51 Command [CH51_1] received - level 1 output enabled"}