Get debug logs of all opcodes without committing changes to database

Usually we came across situations where we need to get debug logs of some opcode without changing anything in account data . We can use below flist to get log by aborting the opcode transaction after successful execution .

We can use below flist for following purpose :

• To get search being invoked in OOTB/Custom opcode.
• To get the flow of function being called as part of concerned opcode.
• To get debug logs of opcode.
• To triage failure reason for particular action.

===============================================

r << XXX 1

0 PIN_FLD_POID           POID [0] 0.0.0.1 /plan 1 0

XXX

xop PCM_OP_TRANS_OPEN 65536 1

r << XXX 1

0 PIN_FLD_POID        POID [0] 0.0.0.1 /account 1 1

0 PIN_FLD_COMPONENT    STR [0] "CM"

0 PIN_FLD_LOGLEVEL     INT [0] 3

XXX

xop PCM_OP_INFMGR_SET_LOGLEVEL 0 1

r << XXX 1

.................put your flist here ...............

XXX

xop  put your opcode name here  0 1

r << XXX 1

0 PIN_FLD_POID        POID [0] 0.0.0.1 /account 1 1

0 PIN_FLD_COMPONENT    STR [0] "CM"

0 PIN_FLD_LOGLEVEL     INT [0] 1

XXX

xop PCM_OP_INFMGR_SET_LOGLEVEL 0 1

r << XXX 1

0 PIN_FLD_POID           POID [0] 0.0.0.1 /plan 1 0

XXX

xop PCM_OP_TRANS_ABORT 65536 1

======================================================

We can also increase dm log level for same transaction by including below opcode in same flow : 

=====================================================

r << XXX  1

0 PIN_FLD_POID POID [0] 0.0.0.2 /account 1 1

0 PIN_FLD_COMPONENT STR [0] "DM"

0 PIN_FLD_DEBUG_FLAG ARRAY [1] allocated 20, used 2

1     PIN_FLD_NAME STR [0] "DM_DEBUG"

1     PIN_FLD_FLAGS INT [0] 255

0 PIN_FLD_DEBUG_FLAG ARRAY [2] allocated 20, used 2

1     PIN_FLD_NAME STR [0] "DM_DEBUG2"

1     PIN_FLD_FLAGS INT [0] 4090

0 PIN_FLD_DEBUG_FLAG ARRAY [3] allocated 20, used 2

1    PIN_FLD_NAME STR [0] "DM_DEBUG3"

1    PIN_FLD_FLAGS INT [0] 65535

XXX

xop PCM_OP_INFMGR_SET_LOGLEVEL 0 1

=====================================================