Previous Topic: Option 01: Replace a File Control IDNext Topic: Change the File Name


Prevent an AEIL Abend

The following screen shows that CA InterTest for CICS has halted the demo program at an automatic breakpoint before an AEIL abend could occur.

CA InterTest for CICS V9.1 - PROTSYM FILE ABEND DETECTED BREAKPOINT COMMAND ===> Program= COBDEMO Option # Stmt # Margin= 01 Search= ------------------------------------------------------------------------------- _____ RECORD-KEY | 00000000000000000000000000000000000000 ---------+--------------------------------------------------------------------- 000711*EXEC CICS STARTBR DATASET('PROTH') RIDFLD(RECORD-KEY) 000712* END-EXEC. A ==> Call 'DFHEI1' using by content x'060cb000070020a000f0f0f3f9f3 ==> ==> CICS abend intercepted. Abend code = AEIL. EXEC CICS request was ==> STARTBR. Now stopped AFTER the CALL. ==> ==> Press PF1 for a detailed description. ==> _ 000714- '404040' by content 'PROTH ' by content x'0000' by content _ 000715 x'0000' by reference RECORD-KEY end-call. 000716 _ 000717 MOVE +1 TO SUB. 000718*EXEC CICS READNEXT DATASET('PROTH') 000719* SET(ADDRESS OF RECORD-AREA) 000720* LENGTH(REC-LEN) RIDFLD(RECORD-KEY) END-EXEC. _ 000721 Call 'DFHEI1' using by content x'060ef400070100b000f0f0f3f9f6

The abend that CA InterTest for CICS prevented would have resulted from the EXEC CICS STARTBR command. CA InterTest for CICS highlighted the CALL statement that is part of the generated EXEC CICS STARTBR command.

What is the problem?

The data set name PROTH is wrong; it should be PROTHLF.

How can it be fixed?

CA InterTest for CICS lets you dynamically correct the file name and continue testing. The following section explains how this is done.