Previous Topic: Dump Analysis with CA SymDumpNext Topic: COBOL Advanced Demo Session


Example

Suppose a program not being monitored by CA InterTest for CICS abended with an ASRA. With CA SymDump for CICS, you can display the breakpoint at the statement that triggered the abend even though CA InterTest for CICS was not active in the region when the abend occurred.

CA InterTest for CICS V9.1 - PROTSYM FILE ABEND DETECTED DUMP ANALYSIS COMMAND ===> Program= COBDEMO Option # Stmt # Displacement= Margin= 01 Search= ------------------------------------------------------------------------------- _ 000477 CONTINUE-TASK. 000478**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED A ==> ADD +1 TO TASKNUM. ==> ==> ABEND/DUMP CODE: ASRA ==> ==> Press PF1 for a detailed description. ==> _ 000480 IF TASKNUM = 1 _ 000481 MOVE 'DMAPASR' TO MAPNAME. _ 000482 IF TASKNUM = 2 _ 000483 MOVE 'DMAPSUM' TO MAPNAME. _ 000484 IF TASKNUM GREATER 2 _ 000485 GO TO SEND-END-MSG. _ 000486 GO TO REWRITE-TSQ. _ 000487 REWRITE-TSQ. 000488*EXEC CICS WRITEQ TS 000489* REWRITE 000490* QUEUE(TSQ-NAME)

Now you can use CA SymDump to solve the problem. In this example, you might want to display the contents of TASKNUM, or you might want to inspect a file or look at the formatted trace table. CA SymDump provides all the tools you need to diagnose and resolve the dump.

Because CA SymDump for CICS works just like CA InterTest for CICS, there is no learning curve. For more information, see the User Guide.