AC4

Explanation
JES3 encountered an error while processing an IATXCNDB
service call which specified (or defaulted to) ABEND=YES. The abend
reason code identifies the specific error. Code
Explanation
00
Operation was successfully performed.
04
The OPERATION requested is not supported by the IATXCNDB macro.
08
An invalid IATXCNDB parameter list was passed to the IATCNDB module.
The eyecatcher in the parameter list is not 'YCNDB '
0C
An invalid IATXCNDB parameter list was passed to the IATCNDB module.
The version indicator in the parameter list was not equal to the the
current version.
10
The input IATYCNDB (INCNDB parameter) passed to the IATXCNDB INITIALIZE
service did not have 'CNDB' as its eyecatcher.
14
The console id and console name parameters were passed to the
INITIALIZE service.  These parameters are mutually exclusive.
18
An error return (>4) was received from the call to CONVCON by
the IATXCNDB INITIALIZE operation.
1C
The IATYCNDB was successfully initialized, but the console name/ID
passed to the INITIALIZE routine was not found in the JES3 console
table.  The IATYCNDB has been initialized with a "non-JES3" console
type and the console ID and console name passed on the IATXCNDB invocation
and returned by MCS.
20
The input IATYCNDB (CNDB parameter) address passed to the IATXCNDB
TRANSFER service was zero.
24
The input IATYCNDB (CNDB parameter) passed to the IATXCNDB TRANSFER
service did not have 'CNDB' as its eyecatcher.
28
The output IATYCNDB (OUTCNDB parameter) address passed to the
IATXCNDB TRANSFER service was zero.
2C
The IATYCNDB passed to the VERIFY service did not have 'CNDB'
as its eyecatcher.
30
An error return (>4) was received from the call to CONVCON by
the IATXCNDB service VERIFY operation.
34
The IATYCNDB was successfully converted to an IATYCNDB at the
current release level, but the console name in the down level CNDB
was not found in the JES3 console table.  The IATYCNDB has been initialized
with a "non-JES3" console type and the console ID returned by MCS.
38
The input IATYCNDB (CNDB parameter) address passed to the IATXCNDB
TRANSCONSID service was zero.
3C
The input IATYCNDB (CNDB parameter) passed to the IATXCNDB TRANSCONSID
service did not have 'CNDB' as its eyecatcher.
40
The output IATYCNDB (OUTCNDB parameter) address passed to the
IATXCNDB TRANSCONSID service was zero.
44
The input IATYCNDB (CNDB parameter) address passed to the IATXCNDB
TRANSROUT service was zero.
48
The input IATYCNDB (CNDB parameter) passed to the IATXCNDB TRANSROUT
service did not have 'CNDB' as its eyecatcher.
4C
The output IATYCNDB (OUTCNDB parameter) address passed to the
IATXCNDB TRANSROUT service was zero.
50
The input IATYCNDB (CNDB parameter) address passed to the IATXCNDB
EXTRACTCONSID service was zero.
54
The input IATYCNDB (CNDB parameter) passed to the IATXCNDB EXTRACTCONSID
service did not have 'CNDB' as its eyecatcher.
58
The OUTCONSID address passed to the IATXCNDB EXTRACTCONSID service
was zero.
5C
The input IATYCNDB (CNDB parameter) address passed to the IATXCNDB
EXTRACTCONSNAME service was zero.
60
The input IATYCNDB (CNDB parameter) passed to the IATXCNDB EXTRACTCONSNAME
service did not have 'CNDB' as its eyecatcher.
64
The OUTCONSNAME address passed to the IATXCNDB EXTRACTCONSNAME
service was zero.
68
The input IATYCNDB (CNDB parameter) address passed to the IATXCNDB
EXTRACTCONSTYPE service was zero.
6C
The input IATYCNDB (CNDB parameter) passed to the IATXCNDB EXTRACTCONSTYPE
service did not have 'CNDB' as its eyecatcher.
70
The OUTCONSTYPE address passed to the IATXCNDB EXTRACTCONSTYPE
service was zero.
74
The input IATYCNDB (CNDB parameter) address passed to the IATXCNDB
EXTRACTROUT service was zero.
78
The input IATYCNDB (CNDB parameter) passed to the IATXCNDB EXTRACTROUT
service did not have 'CNDB' as its eyecatcher.
7C
The OUTROUT address passed to the IATXCNDB EXTRACTROUT service
was zero.
80
The input IATYCNDB (CNDB parameter) address passed to the IATXCNDB
UPDATE service was zero.
84
The input IATYCNDB (CNDB parameter) passed to the IATXCNDB UPDATE
service did not have 'CNDB' as its eyecatcher.
88
An attempt was made to pass the CONSID and CONSNM parameters to
the IATXCNDB service for an UPDATE operation. These parameters are
mutually exclusive.
8C
An error return (>4) was received from the call to CONVCON by
the IATXCNDB UPDATE operation.
90
The IATYCNDB was successfully updated, but the console name/ID
passed to the UPDATE routine was not found in the JES3 console table.
 The IATYCNDB has been Updated with a "non-JES3" console type and
the console ID and console name passed on the IATXCNDB invocation
and returned by MCS.
94
The input IATYCNDB (CNDB parameter) address passed to the IATXCNDB
RESET service was zero.
98
The input IATYCNDB (CNDB parameter) passed to the IATXCNDB RESET
service did not have 'CNDB' as its eyecatcher.
A8
The input IATYCNDB (CNDB parameter) address passed to the IATXCNDB
EXTRACTCART service was zero.
AC
The input IATYCNDB (CNDB parameter) passed to the IATXCNDB EXTRACTCART
service did not have 'CNDB' as its eyecatcher.
B0
The OUTROUT address passed to the IATXCNDB EXTRACTCART service
was zero.

System action
The IATXCNDB request processing is ended.

System programmer response
To determine the error, perform the
following: If called from the JES3 main task, locate the ACALL and RETURN
trace entry for the IATXCNDB macro.
Register 1 of the ACALL trace entry contains the address of the
parameter list used by the IATXCNDB macro.  The parameter list is
mapped by a DSECT generated from an IATXCNDB MF=L call.
Use the trace table to locate the module that issued the IATXCNDB
macro.  Register 14 of the ACALL entry in the trace table contains
the return address and register 10 contains the base register.
When IATXCNDB is invoked from a user's address space, the caller
issued a BASSM R14,R15 from the IATXCNDB macro.  The registers are
then saved on the linkage stack by IATCNDB via 'BAKR R14,R0'.
Use the abend reason code to identify the cause of the error.
Correct the parameter list in the module that issued the IATXCNDB
macro.

Source
JES3