How to get additional Debug information in case of a problem

Document ID : KB000048132
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

This Technical Document shows which additional debugging usually should be turned on in case of a problem.

Often we ask to turn on LOGLVL='+T' when requesting DEBUG logs from customers.
But, this is not what can give us the needed information in most of the cases.
In most of the cases, it's better to turn on MSM_LOGLEVEL="-debug" (uncommented).
It will not cause any additional issue, if you activate both options.

Solution:

Here is a explanation of all types of debugs that can be turned on:

  1. For debugging CA CSM startup problems (JVM, Tomcat,…)

    Set LOGLVL='+T',
    Default: LOGLVL='+I',
    Has no effect on CA CSM DEBUG messages that are in code.
    +I prints these types of messages: JVMJZBL1001N and JVMJZBL1053I
    +T print the same as +I and also these: JVMJZBL1036D and JVMJZBL2999T

  2. For turning on debug for CA CSM Java and C/C++ code

    Uncomment line MSM_LOGLEVEL="-debug" in CSM Runtime.SAMPLIB(MSMLIB), specified at the STDENV DD statement in the MSMTCSRV
    Default: all MSM_LOGLEVEL are commented

    This one should be activated almost every time.

  3. For turning on trace for MVSUTIL package

    Uncomment line MVSUTIL_LOGLEVEL=8 in RUN.SAMPLIB(MSMLIB) and comment out line MVSUTIL_LOGLEVEL=7
    Default: MVSUTIL_LOGLEVEL=7

    In most cases does not have to be activated.
    Only activate in specific cases when instructed by CA Technologies Sustaining Engineering.

All of above debugging options will produce large amount of lines in the CA CSM Tomcat log and should only turned on in case of a problem to produce diagnostics.
CA CSM speed is decreased once the debugging is activated.
Restart of MSMTC is in all three cases required to activate/deactivate.