If
an exceptional condition occurs during execution of a CICS application program,
and if program does not check the exceptional condition, CICS will by default
terminates the task. This kind of termination is known as abnormal termination
and CICS will issue the abnormal termination (ABEND) code, which is associated
with the exceptional condition on subject.
This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.
AEIT
ENDFILE condition not handled
AEIN
DUPREC condition not handled
AEIM
NOTFND condition not handled
AEIL
FILENOTFOUND condition not handled
AEIO
DUPKEY condition not handled
AEIP
INVREQ condition not handled
The possible reasons are:
1 You cannot change the value of primary key using REWRITE.
If you try to do so, CICS will assume that you are trying
to update a record without a READ with UPDATE option. This
will cause an INVREQ error to occur.
2 You did not provide STARTBR command before issuing
READNEXT/READPREV.
3 Incase of STARTBR/RESETBR,we usually specify GENERIC and
KEYLENGTH. KEYLENGTH must be numeric, half word Binary and
less than the length of RIDFLD field's length.
AEIQ
IOERR condition not handled
AEIR
NOSPACE condition not handled
AEIS
NOTOPEN condition not handled
AEIU
ILLOGIC condition not handled
AEIV
LENGERR condition not handled
AEIW
QZERO condition not handled
AEIZ
ITEMERR condition not handled
AEI0
PGMIDERR condition not handled
AEI9
MAPFAIL condition not handled
AEYH
QIDERR condition not handled
ASRA
The task has terminated abnormally because of a program check
AICA
A task has been executing for longer than the runaway time interval (defined by the ICVR operand on the system initialization table macro, DFHSIT) without giving up control. The runaway task condition indicates a possible loop in the application.
ABMG
The user has requested a basic mapping support (BMS) service that was not specified at system generation, or at initialization
This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.
AEIT
ENDFILE condition not handled
AEIN
DUPREC condition not handled
AEIM
NOTFND condition not handled
AEIL
FILENOTFOUND condition not handled
AEIO
DUPKEY condition not handled
AEIP
INVREQ condition not handled
The possible reasons are:
1 You cannot change the value of primary key using REWRITE.
If you try to do so, CICS will assume that you are trying
to update a record without a READ with UPDATE option. This
will cause an INVREQ error to occur.
2 You did not provide STARTBR command before issuing
READNEXT/READPREV.
3 Incase of STARTBR/RESETBR,we usually specify GENERIC and
KEYLENGTH. KEYLENGTH must be numeric, half word Binary and
less than the length of RIDFLD field's length.
AEIQ
IOERR condition not handled
AEIR
NOSPACE condition not handled
AEIS
NOTOPEN condition not handled
AEIU
ILLOGIC condition not handled
AEIV
LENGERR condition not handled
AEIW
QZERO condition not handled
AEIZ
ITEMERR condition not handled
AEI0
PGMIDERR condition not handled
AEI9
MAPFAIL condition not handled
AEYH
QIDERR condition not handled
ASRA
The task has terminated abnormally because of a program check
AICA
A task has been executing for longer than the runaway time interval (defined by the ICVR operand on the system initialization table macro, DFHSIT) without giving up control. The runaway task condition indicates a possible loop in the application.
ABMG
The user has requested a basic mapping support (BMS) service that was not specified at system generation, or at initialization
No comments:
Post a Comment