Modifying the EID by exits XFCREQ and XFCREQC
It is not possible to modify the EID to make major changes to requests. It is not possible, for example, to change a WRITE request to a READ request. However, you can make minor changes to requests, such as to turn on the existence bit for SYSID so that the request can be changed into one that is shipped to a remote system.
The list that follows shows the bits in the EID that can be modified. Any attempt to modify any other part of the EID is ignored.
- FC_BITS1
-
- X'20'
- The existence bit for LENGTH, NUMREC, or (if the request is STARTBR, RESETBR, or ENDBR) REQID.
- X'08'
- The existence bit for KEYLENGTH.
- X'04'
- The existence bit for REQID if the request is READNEXT or READPREV.
- X'02'
- The existence bit for SYSID.
- FC_BITS2
-
- X'20'
- Token specified.
- FC_EIDOPT5
-
- X'04'
- MASSINSERT specified.
- FC_EIDOPT6
-
- X'40'
- GENERIC specified.
- X'20'
- GTEQ specified.
- X'10'
- UNCOMMITTED specified.
- X'08'
- CONSISTENT specified.
- X'04'
- REPEATABLE specified.
- X'02'
- UPDATE specified on READNEXT or READPREV.
- X'01'
- NOSUSPEND specified (on READ, READNEXT, READPREV, WRITE, DELETE, or REWRITE).
Bits in the EID should be modified in place. You should not modify the pointer to the EID: any attempt to do so is ignored by CICS®.
The EID is reset to its original value before return to the application program. That is, changes made to the EID are retained for the duration of the file control request only.
If more than one of UNCOMMITTED, CONSISTENT, or REPEATABLE is specified, CONSISTENT takes precedence over UNCOMMITTED, and REPEATABLE takes precedence over CONSISTENT and UNCOMMITTED.