Setting trace levels by editing RKANPARU(KppENV)

One of the simplest ways to set trace levels for an agent or monitoring server is to edit the rhilev.rte.RKANPARU(KppENV) member.

The following examples show how to set RAS1 tracing for monitoring agents in OMEGAMON AI for CICS on z/OS.

• This example sets RAS1 tracing for OMEGAMON AI for CICS TG. To write all available CICS® TG monitoring agent messages to the RKLVLOG, edit the KGWENV member and add (UNIT:KGW ALL) to the default KBB_RAS1=ERROR setting as shown:

  KBB_RAS1=ERROR (UNIT:KGW ALL)

• This example sets RAS1 tracing for OMEGAMON AI for CICS on z/OS agents. To write all available CICS monitoring agent messages, edit the KC5ENV member and add (UNIT:KCP ALL) to the default KBB_RAS1=ERROR. To write all available CICSplex monitoring agent messages, edit the KC5ENV member and add (UNIT:KCE ALL) to the default KBB_RAS1=ERROR setting. You can set RAS1 tracing to write all available messages for both monitoring agents by adding the combination of keywords to the default KBB_RAS1=ERROR setting as shown:

  KBB_RAS1=ERROR (UNIT:KCP ALL) (UNIT:KCE ALL)

After you update a KppENV member, you must stop and restart the address space for the settings to take effect. After that, the settings remain in effect for the life of the address space. To end the trace, you must edit the file again to reset the trace level, and stop and restart the address space.