CICS - COMANDOS API - Appendix A. EXEC interface block (EIB) fields


Volta a página anterior

Volta ao Menu Principal


Desenvolvido por DORNELLES Carlos Alberto - Analista de Sistemas - Brasília DF.

CICS - COMANDOS API - Appendix A. EXEC interface block (EIB) fields

This information describes the fields of the EXEC Interface Block (EIB).
An application program can read all the fields in the EIB of the associated task by name, but must not change the contents of any of them.

For each field, the contents and format (for each of the application programming languages, COBOL, C, C++, or PL/I) are given.
All fields contain zeros in the absence of meaningful information.
Fields are listed in alphabetic sequence.

EIBAID
This EIB field contains the attention identifier (AID) that is associated with the last terminal control or Basic Mapping Support (BMS) input operation from a display device such as a terminal.

For COBOL: PIC X(1)
For C or C++ : cics_char_t eibaid;
For PL/I: CHAR(1)

EIBATT
This EIB field indicates that the request/response unit (RU) contains attach header data (X'FF').

For COBOL: PIC X(1)
For C or C++ : cics_char_t eibatt;
For PL/I: CHAR(1)

EIBCALEN
This EIB field contains the length of the communication area that has been passed to the application program from the last program, using the COMMAREA and LENGTH options.
If no communication area is passed, this field contains zeros.

For COBOL: PIC S9(4) COMP
For C or C++ : cics_ushort_t eibcalen;
For PL/I: FIXED BIN(15)

EIBCOMPL
This EIB field indicates, on a terminal control RECEIVE or CONVERSE command, whether the data is complete (X'FF').
If the NOTRUNCATE option has been used on the RECEIVE or CONVERSE command, CICS retains data in excess of the amount that is requested via the LENGTH or MAXLENGTH option. EIBRECV is set to indicate that further RECEIVE or CONVERSE commands are required.
EIBCOMPL is not set until the last of the data has been received.

EIBCOMPL is always set when a RECEIVE or CONVERSE command without the NOTRUNCATE option is executed.

For COBOL: PIC X(1)
For C or C++ : cics_char_t eibcompl;
For PL/I: CHAR(1)

EIBCONF
This EIB field indicates that the conversational partner has issued a CONFIRM request (X'FF') and that a response is required.

For COBOL: PIC X(1)
For C or C++ : cics_char_t eibconf;
For PL/I: CHAR(1)

EIBCPOSN
This EIB field contains the cursor address (position) that is associated with the last terminal control or Basic Mapping Support (BMS) input operation from a display device such as a terminal.

For COBOL: PIC S9(4) COMP
For C or C++ : cics_ushort_t eibcposn;
For PL/I: FIXED BIN(15)

EIBDATE
This EIB field contains the date the task is started (this field is updated by the ASKTIME command).
The date is in packed decimal form (0CYYDDD+) where C shows the century with values 0 for the 1900s and 1 for the 2000s.
For example, the dates 31 December 1999 and 1 January 2000 have EIBDATE values of 0099365 and 0100001 respectively.

For COBOL: PIC S9(7) COMP-3
For C or C++ : cics_char_t eibdate [4];
For PL/I: FIXED DEC(7,0)

EIBDS
This EIB field contains the symbolic identifier of the last file that was referenced by a file control request.

For COBOL: PIC X(8)
For C or C++ : cics_char_t eibds [8];
For PL/I: CHAR(8)

EIBEOC
This EIB field is set to X'FF' after a successful advanced program-to-program communications (APPC) RECEIVE or CONVERSE; otherwise it is not set.
An APPC conversation allows a program to send data to, and receive data from, a program that is running in a remote system.
Programming that uses APPC conversations is called Distributed Transaction Programming (DTP). For guidance information on DTP, refer to the TXSeries for Multiplatforms Intercommunication Guide.

For COBOL: PIC X(1)
For C or C++ : cics_char_t eibeoc;
For PL/I: CHAR(1)

EIBERR
This EIB field indicates that an abnormal condition has occurred (X'FF') on an APPC conversation.
The error code is in EIBERRCD.

For COBOL: PIC X(1)
For C or C++ : cics_char_t eiberr;
For PL/I: CHAR(1)

EIBERRCD
This EIB field when EIBERR is set, contains the error code that has been received.
The following values can be returned in the first two bytes of EIBERRCD:
  • X'0824' SYNCPOINT ROLLBACK was requested.
  • X'0864' ISSUE ABEND was received.
  • X'0889' ISSUE ERROR was received.
  • X'A000' The conversation was lost.

Hex values returned with EIBERRCD and their meanings

X'080F6051' The partner transaction failed security check.
X'08240000' The partner transaction or system has issued SYNCPOINT ROLLBACK.
X'084B6031' The partner system is temporarily unable to start the partner transaction.
X'084C0000' The partner system cannot start the partner transaction.
X'08640000' The Partner transaction has sent ISSUE ABEND.
X'08640001' The Partner system has sent ISSUE ABEND.
X'08890000' An ISSUE ERROR command has been received.
X'10086021' The partner transaction's name is not recognized by the partner system.
X'10086031' PIP data was specified but the remote process does not support it.
X'10086032' The PIP data sent with the CONNECT PROCESS was incorrectly specified.
X'10086034' The partner system does not support mapped conversations.
X'10086041' The partner transaction does not support the synchronization level requested on the CONNECT PROCESS.

For COBOL: PIC X(4)
For C or C++ : cics_char_t eiberrcd [4];
For PL/I: CHAR(4)

EIBFMH
This EIB field indicates that the user data just received or retrieved contains an FMH (X'FF').
This cannot arise in TXSeries for Multiplatforms, which always sets this field toX'00'.

For COBOL: PIC X(1)
For C or C++ : cics_char_t eibfmh;
For PL/I: CHAR(1)

EIBFN
This EIB field contains a code that identifies the last CICS command to be issued by the task (updated when the requested function has been completed).

For COBOL: PIC X(2)
For C or C++ : cics_char_t eibfn [2];
For PL/I:CHAR(2)

EIBFN code that contains the last CICS command to be used

Código Comando Código Comando Código Comando Código Comando Código Comando
0202 ADDRESS 0204 HANDLE CONDITION 0206 HANDLE AID 0208 ASSIGN 020A IGNORE CONDITION
020C PUSH HANDLE 020E POP HANDLE 0402 RECEIVE 0404 SEND 0406 CONVERSE
040C WAIT TERMINAL 041E ISSUE SIGNAL 0420 ALLOCATE 0422 FREE 042C WAIT CONVID
042E EXTRACT PROCESS 0430 ISSUE ABEND 0432 CONNECT PROCESS 0434 ISSUE CONFIRMATION 0438 ISSUE ERROR
0436 ISSUE PREPARE 043E EXTRACT ATTRIBUTES 0602 READ 0604 WRITE 0606 REWRITE
0608 DELETE 060A UNLOCK 060C STARTBR 060E READNEXT 0610 READPREV
0612 ENDBR 0614 RESETBR 0802 WRITEQ TD 0804 READQ TD 0806 DELETEQ TD
0A02 WRITEQ TS 0A04 READQ TS 0A06 DELETEQ TS 0C02 GETMAIN 0C04 FREEMAIN
0E02 LINK 0E04 XCTL 0E06 LOAD 0E08 RETURN 0E0A RELEASE
0E0C ABEND 0E0E HANDLE ABEND 1002 ASKTIME 1004 DELAY 1008 START
100A RETRIEVE 100C CANCEL 1204 ENQ 1206 DEQ 1208 SUSPEND
1402 JOURNAL 1404 WAIT JOURNAL 1602 SYNCPOINT 1802 RECEIVE MAP 1804 SEND MAP
1806 SEND TEXT 1812 SEND CONTROL 1A02 TRACE 1A04 ENTER 1C02 DUMP
4A02 ASKTIME ABSTIME 4A04 FORMATTIME 4C02 INQUIRE FILE 4C04 SET FILE 4E02 INQUIRE PROGRAM
4E04 SET PROGRAM 5002 INQUIRE TRANSACTION 5004 SET TRANSACTION 5202 INQUIRE TERMINAL 5204 SET TERMINAL
5206 INQUIRE NETNAME 5402 INQUIRE SYSTEM 5802 INQUIRE CONNECTION 5804 SET CONNECTION 5C02 INQUIRE TDQUEUE
5C04 SET TDQUEUE 5E02 INQUIRE TASK or INQUIRE TASK LIST 5E04 SET TASK 6002 INQUIRE JOURNALNUM 6004 SET JOURNALNUM
7002 INQUIRE STATISTICS 7004 SET STATISTICS 7006 PERFORM STATISTICS RECORD 7008 COLLECT STATISTICS 7402 SIGNON
7404 SIGNOFF 7406 VERIFY PASSWORD 7408 CHANGE PASSWORD 820C FEPI REQUEST PASSTICKET 820E FEPI AP NOOP
8210 FEPI ALLOCATE PASSCONVID|POOL 8212 FEPI CONVERSE FORMATTED 8214 FEPI CONVERSE DATASTREAM 8216 FEPI EXTRACT CONV 8218 FEPI EXTRACT FIELD
821A FEPI EXTRACT STSN 821C FEPI EXTRACT FREE 821E FEPI ISSUE 8220 FEPI RECEIVE FORMATTED 8222 FEPI RECEIVE DATASTREAM
8224 FEPI SEND FORMATTED 8226 FEPI SEND DATASTREAM 8228 FEPI START 840E FEPI SP NOOP 8422 FEPI INQUIRE PROPERTYSET
8428 FEPI INSTALL PROPERTYSET 8430 FEPI DISCARD PROPERTYSET 8442 FEPI INQUIRE NODE 8444 FEPI SET NODE|NODELIST 8448 FEPI INSTALL NODELIST
844A FEPI ADD POOL 844C FEPI DELETE POOL 8450 FEPI DISCARD NODELIST 8462 FEPI INQUIRE POOL 8464 FEPI SET POOL|POOLLIST
8468 FEPI INSTALL POOL 8470 FEPI DISCARD POOL 8482 FEPI INQUIRE TARGET 8484 FEPI SET TARGET|TARGETLIST 8488 FEPI INSTALL TARGETLIST
8490 FEPI DISCARD TARGETLIST 84A2 FEPI INQUIRE CONNECTION 84A4 FEPI SET CONNECTION

EIBFREE
This EIB field indicates that the application program cannot continue using the facility.
The receiver must issue a FREE command for the conversation.

For COBOL: PIC X(1)
For C or C++ : cics_char_t eibfree;
For PL/I: CHAR(1)

EIBLABEL
This field, which is used for COBOL programs only, is used to contain values that relate to handled conditions or abends. The values are:
  • 0: RETURN or XCTL
  • 1: Abend
  • 2 to nn: A value that identifies a label for a handled condition or abend
EIBNODAT
This EIB field indicates that no data has been sent by the remote application (X'FF').
A message has been received from the remote system that conveyed only control information.
For example, if the remote application executed a SEND command with a WAIT option, any data would be sent across the link.
If the remote application then executes a SEND INVITE command without using the FROM option to transmit data at the same time, it would be necessary to send the INVITE instruction across the link by itself.
In this case, the receiving application finds EIBNODAT set.
The use of this field is restricted to application programs that are holding conversations across APPC links only.

For COBOL: PIC X(1)
For C or C++ : cics_char_t eibnodat;
For Pl/I: CHAR(1)

EIBRCODE
This EIB field contains the CICS response code that is returned after the function that was requested by the last CICS command to be issued by the task has been completed.

For a normal response, this field contains hexadecimal zeros (X'00').
For COBOL programs only, almost all the information that is in this field can be used within application programs by the HANDLE CONDITION command.

For COBOL: PIC X(6)
For C or C++ : cics_char_t eibrcode [6];
For PL/I: CHAR(6)

The following list shows the EIBRCODE values that correspond to the conditions that can occur for each group of commands (as indicated by byte 0 of EIBFN), together with the names of the associated conditions.

For some conditions, further information is provided in EIBRCODE.
This is indicated by a note that follows the list of values.

For some commands (for example, INQUIRE and SET), byte 3 of EIBRCODE contains the hexadecimal equivalent of the value in EIBRESP.
Any further information that relates to conditions that are occurring on these commands can be found in EIBRESP2 rather than EIBRCODE. The RESP2 values are given in the descriptions of the individual commands.

Table 25. EIBRCODE values and corresponding conditions

EIBFN EIBRCODE Conditions EIBFN EIBRCODE Conditions EIBFN EIBRCODE Conditions EIBFN EIBRCODE Conditions
02 -- E0 -- -- -- -- -- INVREQ 04 -- D0 -- -- -- -- -- SYSIDERR 3 04 -- D3 -- -- -- -- -- SYSBUSY 04 -- D5 -- -- -- -- -- NOTALLOC
04 -- EB -- -- -- -- -- CBIDERR 04 -- E0 -- -- -- -- -- INVREQ 4 04 -- E1 -- -- -- -- -- LENGERR 5 04 -- E5 -- -- -- -- -- SIGNAL
04 -- F1 -- -- -- -- -- TERMERR 06 -- D0 -- -- -- -- -- SYSIDERR 3 06 -- D1 -- -- -- -- -- ISCINVREQ 06 -- D6 -- -- -- -- -- NOTAUTH
06 -- E1 -- -- -- -- -- LENGERR 06 -- 0C -- -- -- -- -- NOTOPEN 06 -- 0D -- -- -- -- -- DISABLED 06 -- 0F -- -- -- -- -- ENDFILE
06 -- 01 -- -- -- -- -- FILENOTFOUND (or DSIDERR) 06 -- 02 -- -- -- -- -- ILLOGIC 1 06 -- 08 -- -- -- -- -- INVREQ 06 -- 80 -- -- -- -- -- IOERR 1
06 -- 81 -- -- -- -- -- NOTFND 06 -- 82 -- -- -- -- -- DUPREC 06 -- 83 -- -- -- -- -- NOSPACE 06 -- 84 -- -- -- -- -- DUPKEY
08 -- C0 -- -- -- -- -- QBUSY 08 -- D0 -- -- -- -- -- SYSIDERR 3 08 -- D1 -- -- -- -- -- ISCINVREQ 08 -- D6 -- -- -- -- -- NOTAUTH
08 -- E1 -- -- -- -- -- LENGERR 08 -- 01 -- -- -- -- -- QZERO 08 -- 02 -- -- -- -- -- QIDERR 08 -- 04 -- -- -- -- -- IOERR
08 -- 08 -- -- -- -- -- NOTOPEN 08 -- 10 -- -- -- -- -- NOSPACE 1A -- E0 -- -- -- -- -- INVREQ 10 -- D0 -- -- -- -- -- SYSIDERR 3
10 -- D1 -- -- -- -- -- ISCINVREQ 10 -- D6 -- -- -- -- -- NOTAUTH 10 -- E1 -- -- -- -- -- LENGERR 10 -- E9 -- -- -- -- -- ENVDEFERR
10 -- FF -- -- -- -- -- INVREQ 10 -- 01 -- -- -- -- -- ENDDATA 10 -- 04 -- -- -- -- -- IOERR 10 -- 11 -- -- -- -- -- TRANSIDERR
10 -- 12 -- -- -- -- -- TERMIDERR 10 -- 20 -- -- -- -- -- EXPIRED 10 -- 81 -- -- -- -- -- NOTFND 12 -- E1 -- -- -- -- -- LENGERR
12 -- 32 -- -- -- -- -- ENQBUSY 14 -- D6 -- -- -- -- -- NOTAUTH 14 -- 01 -- -- -- -- -- JIDERR 14 -- 02 -- -- -- -- -- INVREQ
14 -- 05 -- -- -- -- -- NOTOPEN 14 -- 06 -- -- -- -- -- LENGERR 14 -- 07 -- -- -- -- -- IOERR 14 -- 09 -- -- -- -- -- NOJBUFSP
16 -- 01 -- -- -- -- -- ROLLEDBACK 18 -- 01 -- -- -- -- -- INVREQ 18 -- 04 -- -- -- -- -- MAPFAIL 18 -- 08 -- -- -- -- -- INVMPSZ2 2
4A -- -- -- -- 01 -- -- ERROR 4C -- -- -- -- 0C -- -- FILENOTFOUND (or DSIDERR) 4C -- -- -- -- 10 -- -- INVREQ 4C -- -- -- -- 11 -- -- IOERR
4C -- -- -- -- 15 -- -- ILLOGIC 4C -- -- -- -- 46 -- -- NOTAUTH 4C -- -- -- -- 53 -- -- END 4E -- -- -- -- 01 -- -- ERROR
4E -- -- -- -- 1B -- -- PGMIDERR 4E -- -- -- -- 10 -- -- INVREQ 4E -- -- -- -- 15 -- -- ILLOGIC 4E -- -- -- -- 46 -- -- NOTAUTH
4E -- -- -- -- 53 -- -- END 5C -- -- -- -- 10 -- -- INVREQ 5C -- -- -- -- 11 -- -- IOERR 5C -- -- -- -- 15 -- -- ILLOGIC
5C -- -- -- -- 2C -- -- QIDERR 5C -- -- -- -- 46 -- -- NOTAUTH 5C -- -- -- -- 53 -- -- END 5E -- -- -- -- 10 -- -- INVREQ
5E -- -- -- -- 5B -- -- TASKIDERR 50 -- -- -- -- 1C -- -- TRANSIDERR 50 -- -- -- -- 10 -- -- INVREQ 50 -- -- -- -- 15 -- -- ILLOGIC
50 -- -- -- -- 46 -- -- NOTAUTH 50 -- -- -- -- 53 -- -- END 52 -- -- -- -- 0B -- -- TERMIDERR 52 -- -- -- -- 01 -- -- ERROR
52 -- -- -- -- 10 -- -- INVREQ 52 -- -- -- -- 15 -- -- ILLOGIC 52 -- -- -- -- 53 -- -- END 58 -- -- -- -- 10 -- -- INVREQ
58 -- -- -- -- 15 -- -- ILLOGIC 58 -- -- -- -- 35 -- -- SYSIDERR 58 -- -- -- -- 53 -- -- END 60 -- -- -- -- 10 -- -- INVREQ
60 -- -- -- -- 11 -- -- IOERR 60 -- -- -- -- 15 -- -- ILLOGIC 60 -- -- -- -- 2B -- -- JIDERR 60 -- -- -- -- 46 -- -- NOTAUTH
60 -- -- -- -- 53 -- -- END 70 -- -- -- -- 0D -- -- NOTFND 70 -- -- -- -- 10 -- -- INVREQ 70 -- -- -- -- 46 -- -- NOTAUTH
0A -- D0 -- -- -- -- -- SYSIDERR 3 0A -- D1 -- -- -- -- -- ISCINVREQ 0A -- D6 -- -- -- -- -- NOTAUTH 0A -- E1 -- -- -- -- -- LENGERR
0A -- 01 -- -- -- -- -- ITEMERR 0A -- 02 -- -- -- -- -- QIDERR 0A -- 04 -- -- -- -- -- IOERR 0A -- 08 -- -- -- -- -- NOSPACE
0A -- 20 -- -- -- -- -- INVREQ 0C -- E1 -- -- -- -- -- LENGERR 0C -- E2 -- -- -- -- -- NOSTG 0E -- D0 -- -- -- -- -- SYSIDERR 3
0E -- D6 -- -- -- -- -- NOTAUTH 0E -- E0 -- -- -- -- -- INVREQ 0E -- 01 -- -- -- -- -- PGMIDERR

Notas(R):

1
When ILLOGIC or IOERR occur during file control operations, further information is provided in EIBRCODE as follows:
-- xx xx xx xx -- error code

Bytes 1 and 2 indicate the major component that detected the error;
bytes 3 and 4 indicate an error code that belongs to that component.

The following are CICS generated EIBRCODE values:

  • -- 01 23 90 01 --
    RRN zero or negative was used.

  • -- 01 23 90 02 --
    An RRN value was used that is greater than the maximum RRN value that is defined for the file.

  • -- 01 23 90 03 --
    The file has been redefined on the file manager after it was opened.

  • -- 01 23 90 04 --
    Key segment is not defined.

  • -- 01 23 90 05 --
    A variable length field was specified when the file was created on the filemanager, but it was not the last field.

  • -- 01 23 90 06 --
    A variable length relative record file was specified.
    This is ignored on TXSeries for Multiplatforms.

  • -- 01 23 90 07 --
    A file with a record length greater than 65535 bytes was opened.

  • -- 01 23 11 08 --
    A variable length field was specified in an index.
    This is ignored on TXSeries for Multiplatforms.

  • -- 01 23 90 09 --
    The record length that is specified on a write or rewrite to a variable length file is less than the maximum keyspan of the file and its alternate indexes.

  • -- 01 23 90 0A --
    The implicit key that was specified on a rewrite was not the same as the key read in on a read update command.

  • -- 01 23 90 0B --
    For a variable length ESDS file, the length that was rewritten was different from the length read.

  • -- 01 23 90 0C --
    Record not found in ESDS file.
2
When INVMPSZ occurs during BMS operations, byte 3 of EIBRCODE contains the terminal code.

3
When SYSIDERR occurs, further information is provided in byte 1 of EIBRCODE, as follows:
  • D0 04 -- -- -- --
    Modename is not found or invalid.

  • D0 08 -- -- -- --

    SYSID is out of service.


  • D0 0C -- -- -- --
    SYSID definition error.
4
When INVREQ occurs during APPC conversations, further information is provided in byte 3 of EIBRCODE as follows:
  • -- -- 00 08 -- --
    FREE command: Conversation is in wrong state.

  • -- -- 00 0C -- --
    CONNECT PROCESS command: SYNCLVL 2 has been requested, but cannot be supported on the conversation that is in use.

  • -- -- 00 14 -- --
    SEND command: CONFIRM option has been specified, but conversation is SYNCLVL 0.

  • -- -- 00 20 -- --
    An invalid command has been issued for the APPC conversation type that is in use.
5
When LENGERR occurs during terminal control operations, further information is provided in byte 1 of EIBRCODE as follows:
  • E1 00 -- -- -- --
    Input data is overlong and has been truncated.

  • E1 04 -- -- -- --
    On output commands, an invalid (FROM)LENGTH has been specified, either less than zero or greater than 32767.

  • E1 08 -- -- -- --
    On input commands, an invalid (TO)LENGTH has been specified that is greater than 32767.
EIBRECV
This EIB field indicates that the application program is to continue eceiving data from the facility by executing RECEIVE commands (X'FF').

For COBOL: PIC X(1)
For C or C++ : cics_char_t eibrecv;
For PL/I: CHAR(1)


EIBREQID
This EIB field contains the request identifier that is assigned to an interval control command by CICS; this field is not used when a request identifier is specified in the application program.

For COBOL: PIC X(8)
For C or C++ : cics_char_t eibreqid [8];
For PL/I: CHAR(8)

EIBRESP

This EIB field contains a 32-bit binary number that corresponds to the condition that has occurred.
These numbers are listed in Table 26 (in decimal) for the conditions that can occur on local requests during execution of the commands described in CICS API command reference.

For COBOL: PIC S9(8) COMP
For C or C++ : cics_slong_t eibresp;
See Data types used in C or C++.
For PL/I: FIXED BIN(31)

Table 26. RESP values in decimal

Dec Hex Condition Dec Hex Condition Dec Hex Condition Dec Hex Condition Dec Hex Condition
00 X'00' NORMAL 01 X'01' ERROR 11 X'0B' TERMIDERR 12 X'0C' FILENOTFOUND (or DSIDERR) 13 X'0D' NOTFND
14 X'0E' DUPREC 15 X'0F' DUPKEY 16 X'10' INVREQ 17 X'11' IOERR 18 X'12' NOSPACE
19 X'13' NOTOPEN 20 X'14' ENDFILE 21 X'15' ILLOGIC 22 X'16' LENGERR 23 X'17' QZERO
24 X'18' SIGNAL 25 X'19' QBUSY 26 X'1A' ITEMERR 27 X'1B' PGMIDERR 28 X'1C' TRANSIDERR
29 X'1D' ENDDATA 31 X'1F' EXPIRED 36 X'24' MAPFAIL 38 X'26' INVMPSZ 42 X'2A' NOSTG
43 X'2B' JIDERR 44 X'2C' QIDERR 45 X'2D' NOJBUFSP 53 X'35' SYSIDERR 54 X'36' ISCINVREQ
55 X'37' ENQBUSY 56 X'38' ENVDEFERR 59 X'3B' SYSBUSY 61 X'3D' NOTALLOC 62 X'3E' CBIDERR
69 X'45' USERIDERR 70 X'46' NOTAUTH 81 X'51' TERMERR 82 X'52' ROLLEDBACK 83 X'53' END
84 X'54' DISABLED 91 X'5B' TASKIDERR

EIBRESP2
This EIB field contains more detailed information that can help explain why the condition that is indicated by EIBRESP has occurred.
For TXSeries for Multiplatforms, this field contains meaningful values for SET commands only. The relevant values are documented with each command as applicable.

For COBOL: PIC S9(8) COMP
For C or C++ : cics_slong_t eibresp2;
See Data types used in C or C++.
For PL/I: FIXED BIN(31)

Table 27 gives, in general terms, the meaning of the RESP2 values that are used by FEPI.
These values are used in the EVENTVALUE area of CICS transient data queue records and returned by the RESP2 option of CICS commands.
For details of the error conditions and related RESP2 values for each CICS command, see the CICS command definitions

Table 27. RESP2 values

1 INQUIRE START, NEXT, or END command not valid here:

START - Browse of this resource type already in progress
NEXT - INQUIRE START not issued
END - INQUIRE START not issued.
2 All resource definitions have been retrieved.
10 Command bypassed by user exit.
11 FEPI not installed or not active.
12 CICS shutting down, command not allowed.
13 FEPI not available.
14 FEPI busy or cannot get storage.
15 Unknown command.
16 Internal problem.
17 FEPI cannot get storage for user exit parameters.
18 Command failed because of operator or system action.
30 POOL name not known.
31 POOL name out of service.
32 TARGET name not known.
33 TARGET name out of service.
34 TARGET name required but not specified.
35 Pool name is unsuitable for temporary conversations.
It hasCONTENTION(LOSE) or INITIALDATA(INBOUND) but no begin-session handler.
36 No suitable session available and in service.
40 [FROM]FLENGTH value is negative, zero, or more than MAXFLENGTH value for pool.
41 ESCAPE value not valid.
50 Inbound data with 'begin bracket' to be received.
51 Attention identifier (AID) not valid.
52 Cursor position not valid.
53 Code points in formatted data not valid.
54 Attribute positions or values in send data not valid.
55 Key stroke escape sequence in send data not valid.
56 Field validation (mandatory fill, mandatory enter, trigger)failed.
57 Input is inhibited.
58 VTAM SEND failed.
59 DBCS data rules violated.
60 MAXFLENGTH value negative, or greater than MAXFLENGTH value for pool.
61 FLENGTH value negative or greater than 128.
62 TRANSID name not valid.
63 TERMID name not valid.
70 FIELDLOC or FIELDNUM value negative or not valid.
71 VTAM RECEIVE failed.
72 RECEIVE FORMATTED processing found invalid, or unexpected data while interpreting the 3270 data steam for a WRITE, ERASE/WRITE, ERASE/WRITE ALTERNATE, or WRITE STRUCTURED FIELD command code.
80 CONTROL value not valid.
81 VALUE not valid: omitted when required; included when not required; or unsuitable for specified CONTROL.
82 SENSEDATA option omitted when required, or specified when not required.
90 Definite response type did not match what was required.
91 Only NORMALRESP or EXCEPTRESP allowed at this point in conversation.
92 Response to STSN SET was not positive.
93 Only STSN allowed at this point in conversation.
94 Only STSN or NORMALRESP allowed at this point in conversation.
95 CONTROL value not allowed at this point in conversation.
100 Not authorized to issue command.
110 SERVSTATUS value not valid.
111 ACQSTATUS value not valid.
115 POOL name not known.
116 TARGET name not known.
117 NODE name not known.
118 Unknown connection (TARGET and NODE names known, but not in a common POOL).
119 Request failed for one or more items in list. Detailed errors reported to TD queue for monitor to handle.
130 TARGETNUM value negative, zero, or not valid.
131 NODENUM value negative, zero, or not valid.
132 POOLNUM value negative, zero, or not valid.
140 DEVICE value not valid.
141 CONTENTION value not valid.
142 INITIALDATA value not valid.
143 UNSOLDATACK value not valid.
144 MSGJRNL value not valid.
145 DEVICE value not supported.
146 MSGJRNL value not supported.
150 FORMAT value not valid or unsuitable for specified device.
153 STSN name not valid or STSN unsuitable for specified device.
154 BEGINSESSION value not valid.
155 UNSOLDATA value not valid.
156 EXCEPTIONQ value not valid.
157 FJOURNALNUM value not valid.
158 MAXFLENGTH value not valid.
159 ENDSESSION name not valid.
160 PROPERTYSET name not valid.
162 POOL name not valid.
163 NODE name not valid.
164 TARGET name not valid.
167 APPL name not valid.
170 PROPERTYSET name already exists.
171 PROPERTYSET name not known.
172 POOL name already exists.
173 NODE name already exists in specified POOL.
174 TARGET name already exists in specified POOL.
175 Connection already exists.
176 VTAM OPEN NODE failed.
177 VTAM APPLID already known.
178 FJOURNALNAME value not valid.
179 NODE name already exists in another POOL.
180 TARGET limit exceeded for specified POOL
182 Session unbound, unrecoverable.
183 Session unbound, recoverable.
184 Session unbound, error.
185 Session unbound, bind coming.
186 Session unbound.
187 Lost terminal.
188 CLEANUP, abnormal.
189 CLEANUP.
190 UNBIND error.
191 SETUP error.
192 SSCP error.
193 SLU error.
194 PLU error.
195 BIND error.
196 CINIT error.
197 REQSESS error.
198 REQSESS inhibited.
199 REQSESS not available.
210 Option not valid for SLU P.
211 Option not valid for SLU 2.
212 Wrong data format for conversation.
213 Command has timed out.
214 CICS shutting down, conversation should be ended.
215 Session lost.
216 Error occurred on previous SEND command.
220 SEND or CONVERSE command not allowed at this point inconversation.
221 RECEIVE command not allowed at this point in conversation.
223 START command not allowed at this point in conversation.
224 Only ISSUE or FREE allowed at this point in conversation.
230 SNA CLEAR command received.
231 SNA CANCEL command received.
232 SNA CHASE command received.
233 Exception response received.
234 Exception request received.
240 Conversation ID unknown or not owned by task.
241 TIMEOUT value negative or not valid.
250 Passticket not built successfully.
251 CICS ESM interface not initialized.
252 Unknown return code in ESMRESP from the ESM.
253 Unrecognized response from CICS security modules.
254 Function unavailable.
259 No signed-on user.

EIBRLDBK
This EIB field indicates that the remote transaction has sent SYNCPOINT ROLLBACK in response to a SYNCPOINT request (X'FF').
The transaction that issued the SYNCPOINT command has been rolled back.

For COBOL: PIC X(1)
For C or C++ : cics_char_t eibrdbk;
For PL/I: CHAR(1)

EIBRSRCE
This EIB field contains the symbolic identifier of the resource that is being accessed by the last API command to be issued by the task.
Refer to Table 28.
(n represents the number of characters.)

Table 28. EIBRSRCE that specifies resource being accessed

Type of Command Resource n
Temporary storage control TS queue name 8
Terminal control Terminal identifier or APPC conversation identifier (see note) 4
Transient data control TD queue name 4
Note:
In TXSeries for Multiplatforms, APPC conversation identifiers are unprintable.

For COBOL: PIC X(8)
For C or C++ : cics_char_t eibrsrce [8];
For PL/I: CHAR(8)

EIBSIG
This EIB field indicates that the conversation partner has issued an ISSUE SIGNAL command (X'FF').

For COBOL: PIC X(1)
For C or C++ : cics_char_t eibsig;
For PL/I:, CHAR(1)


EIBSYNC
This EIB field indicates that CICS syncpointing is in progress and that the application should issue a SYNCPOINT command.

For COBOL: PIC X(1)
For C or C++ : cics_char_t eibsync;
For PL/I: CHAR(1)


EIBSYNRB
This EIB field indicates that CICS syncpointing is in progress and that the application program should issue a SYNCPOINT ROLLBACK command (X'FF').
This field is set only in application programs that are holding a conversation on an APPC link.

For COBOL: PIC X(1)
For C or C++ : cics_char_t eibsynrb;
For PL/I: CHAR(1)


EIBTASKN
This EIB field contains the task number that is assigned to the task byc CICS.
This number appears in trace entries that are generated while the task is in control.

For COBOL: PIC S9(7) COMP-3
For C or C++ : cics_char_t eibtaskn [4];
For PL/I: FIXED DEC(7,0)


EIBTIME
This EIB field contains the time at which the task is started (this field is updated by the ASKTIME command).
The time is in packed decimal form (0HHMMSS+).

For COBOL: PIC S9(7) COMP-3
For C or C++ : cics_char_t eibtime [4];
For PL/I: FIXED DEC(7,0)


EIBTRMID
This EIB field contains the name of the principal facility that is associated with the task.
For a back-end transaction, it is the conversation identifier (CONVID).
This name must be acquired if the program states explicitly the CONVID for the principal facility.

For COBOL: PIC X(4)
For C or C++ : cics_char_t eibtrmid [4];
For PL/I: CHAR(4)


EIBTRNID
This EIB field contains the symbolic transaction identifier of the task.

For COBOL: PIC X(4)
For C or C++ : cics_char_t eibtrnid [4];
For PL/I: CHAR(4)


© Copyright IBM Corp.