Problem:

What do I look for in a casauxta.rec trace file when trying to diagnose cobesdebug issues?

Resolution:

In the formatted trace file look for DbgReq(Start).  This is the point where the match criteria are checked against pending debug sessions. This should be followed by some DbgMatch entries showing the match criteria. You will only see DbgReq and DbgMatch entries in the trace if there has been a successful initialization which you will see in the trace as:

Pgm(casdbgfn) . . .

DbgIn (        )  xxx  xx  xxxxxx 1e 1e0083  xxxxxxx              

KCP SM-Lock . . . 

KCP Release Sem . . .

DbgEx            xxx  xx  xxxxxx 1e 1e0184  xxxxxxx                   

The string displayed in the DbgMatch entries is passed to the matcher program. If a match is found then the ID of the waiting debugger is returned and Enterprise Server calls CBL_DEBUG_START passing that ID. The CBL_DEBUG_START returns 1 when it didn't work which means that the process to be debugged didn't attach to the cobesdebug process.  This will be seen as DbgReqRsp(4).  If everything works then you will see DbgReqRsp(0). At the end of the debug session you should see DbgReq (Stop) and a further DbgReqRsp(0) to indicate everything worked.