Troubleshooting the Key Manager Library

Use the <mix#> HI <value> command to control debug options. The <value> is a bit mask, with each bit controlling different debug options as follows:

  • Bit 0, value 1: Trace Key Manager library procedures

  • Bit 1, value 2: Trace Key Manager I/O calls (not currently used)

  • Bit 2, value 4: Take a programdump on error (not currently used)

  • Bit 3, value 8: Trace socket router calls (not currently used)

  • Bit 4, value 16: Write diagnostics to sumlog, instead of to a trace file

Combine values to set multiple debug options. For example, use 17 (= 1+16) to trace Key Manager library procedures to the sumlog.

The trace file is titled: *KMAPI/MMDDYY/HHMMSS/<job number>/<mix number>/nnnTRACEFILE

You can use switches to set some debug options during initialization. The debug options are controlled by the following switches:

  • SW1: Take a programdump on error (not currently used)

  • SW2: Write diagnostics to sumlog, instead of to a trace file

  • SW4: Trace Key Manager library procedures

  • SW8: Trace Key Manager I/O calls (not currently used)

For example,

MODIFY *SYSTEM/KMAPI/SUPPORT; SW2; SW4

results in the Key Manager library initializing with procedure tracing to the sumlog.