IBM SC34-6814-04 User Manual

Page 100

Advertising
background image

UEP_FC_DUPLICATE_KEY_CODE

Address of a 1-byte output area indicating whether the request
found more than one record for the supplied key. The possible
values are:
v

UEP_FC_DUPLICATE KEY

v

UEP_FC_NOT_DUPLICATE KEY

UEP_FC_ACCMETH_RETURN_CODE

Address of a 4-byte output area in which access-method-
dependent information is to be returned when either of the
responses UEP_FC_REASON_ACCMETH_REQUEST_ERROR or
UEP_FC_REASON_IO_ERROR is returned.

The returned value is placed in bytes 2–5 of the EIBRCODE.

UEP_FC_RESPONSE

Address of a 1-byte output area containing the response after a
request has completed:

UEP_FC_RESPONSE_OK

Processing has completed without errors.

UEP_FC_RESPONSE_EXCEPTION

Processing has completed with an error condition. The
reason is set in UEP_FC_REASON.

UEP_FC_RESPONSE_DISASTER

An error has occurred which prevents processing from
completing. Typically, this is as a result of a DISASTER
response from an XPI function call, or corruption of data
addressed from UEPGAA or UEPTSTOK.

If you set this response, the caller of file control will assume
that first-failure data capture has been performed. If you are
percolating a DISASTER response from an XPI request,
first-failure data capture will have been performed already; if
not, you should attempt to capture sufficient information to
successfully diagnose the error. The DFHDUDUX
SYSTEM_DUMP XPI function may be suitable for this
purpose.

UEP_FC_RESPONSE_INVALID

The exit program was invoked with an invalid parameter list,
indicating a CICS internal logic error. Note that an invalid
parameter list that indicates an application error should give
an EXCEPTION response.

UEP_FC_RESPONSE_PURGED

An XPI function call has received a PURGED response.
Setting this response is equivalent to setting the
UERCPURG return code, except that any changes to the
parameter list are honored.

UEP_FC_REASON

Address of a 1-byte output area containing, after a request has
completed with an EXCEPTION response, the reason. The possible
reasons are:
v

UEP_FC_REASON_ACCMETH_REQUEST_ERROR

v

UEP_FC_REASON_DELETE_AFTER_READ_UPDATE

v

UEP_FC_REASON_DELETE_BEFORE_READ_UPDATE

v

UEP_FC_REASON_DUPLICATE_READ_UPDATE

78

Customization Guide

Advertising