Reason codes for response: USER_ERROR

401
INVALID_CALL_TYPE
Explanation:

An invalid call-type parameter value is specified on this EXCI request.

System action:

The request is rejected.

User response:

Check your EXCI client program and ensure the call_type parameter specifies the appropriate value for the EXCI call, as follows.

1
Initialize_User
2
Allocate_Pipe
3
Open_Pipe
4
Close_Pipe
5
Deallocate_Pipe
6
DPL
402
INVALID_VERSION_NUMBER
Explanation:

The version_number parameter does not specify a value of 1 or 2.

System action:

The request is rejected.

User response:

Check the client application program and ensure that all EXCI calls specify the value of 1 or 2 for the version number.

403
INVALID_APPL_NAME
Explanation:

The user_name parameter consists of all blank characters (X'40').

System action:

The call is rejected.

User response:

Change the application program to specify a valid, non-blank user name.

404
INVALID_USER_TOKEN
Explanation:

The client application program has issued an EXCI request using a user token that is unknown to the external CICS® interface.

System action:

The request is rejected.

User response:

The Initialize_User call returns a 4-byte token that must be used on all further requests for the that user. Check the client application program and correct the error to ensure that the correct token is passed.

405
PIPE_NOT_CLOSED
Explanation:

A Deallocate_Pipe request has been issued against a pipe that has not yet been closed.

System action:

The external CICS interface ignores the request and the pipe remains open.

User response:

Check the client application program, and ensure that the Deallocate_Pipe request is intended. If so, issue a Close_Pipe request for the pipe before issuing the Deallocate_Pipe request.

406
PIPE_NOT_OPEN
Explanation:

A DPL call has been issued on a pipe that is not open.

System action:

The external CICS interface rejects the DPL request.

User response:

Check the client application program, and ensure that an Open_Pipe request is issued before using the pipe on a DPL request. If an Open_Pipe has been issued by the application program, check that it has not been closed inadvertently before all the DPL requests have been made.

407
INVALID_USERID
Explanation:

A DPL request has been issued with a USERID parameter that consists of all blanks.

System action:

The DPL request is rejected.

User response:

Check the EXCI client program and ensure that the DPL request passes a valid USERID parameter. If you don't want to specify a userid, code the call parameter list with a null address for userid. If you pass a null address, the external CICS interface passes the userid under which the client application program is running (the batch region's userid).

408
INVALID_UOWID
Explanation:

A DPL request has been issued with a uowid parameter that has invalid length fields.

System action:

The DPL request is rejected.

User response:

Check the client application program and ensure that the DPL request passes a valid uowid parameter. If you don't want to specify a unit of work id, code the call parameter list with a null address for uowid, in which case the external CICS interface generates a unit of work id for you.

409
INVALID_TRANSID
Explanation:

A DPL request has been issued with a transid parameter that consists of all blanks.

System action:

The DPL request is rejected.

User response:

Check the client application program and ensure that the transid parameter is specified correctly or has not been overwritten in some way. If you don't want to specify your own transid, code the call parameter list with a null address for transid, in which case the external CICS interface uses the default CICS mirror transaction, CSMI.

410
DFHMEBM_LOAD_FAILED
Explanation:

During Initialize_User processing, the external CICS interface attempted to load the main message module in preparation for issuing external CICS interface messages, and the load of this module failed.

System action:

The Initialize_User call is rejected. The return code from the MVS™ load macro (R15) is returned in the subreason field-1. The external CICS interface handles the error, and returns the abend (R0) that would have occurred in the subreason field-2.

User response:

Using the MVS return code, determine why the load failed. The most likely reason is that the message module, DFHMEBMX, is not in any library included in the STEPLIB of the batch job. Ensure the CICSTS31.CICS.SDFHEXCI library is included in the STEPLIB concatenation, and restart the client application program.

411
DFHMET4E_LOAD_FAILED
Explanation:

The load of message module, DFHMET4E, has failed. During Initialize_User processing, the external CICS interface attempted to load its message table in preparation for issuing messages. The load of this module failed.

System action:

The Initialize_User call is rejected. The return code from the MVS load macro (R15) is returned in the subreason field-1. The external CICS interface handles the error, and returns the abend (R0) that would have occurred in the subreason field-2.

User response:

Using the MVS reason code, determine why the load failed. The most likely reason is that the message table, DFHMET4E, is not in any library included in the STEPLIB of the batch job. Ensure the CICSTS31.CICS.SDFHEXCI library is included in the STEPLIB concatenation, and restart the client application program.

412
DFHXCURM_LOAD_FAILED
Explanation:

During Initialize_User processing, the external CICS interface attempted to load the user-replaceable module, DFHXCURM. The load of this module failed.

System action:

The Initialize_User call is rejected. The return code from the MVS load macro (R15) is returned in the subreason field-1. The external CICS interface handles the error, and returns the abend (R0) that would have occurred in the subreason field-2.

User response:

Using the MVS reason code, determine why the load failed. The most likely reason is that module DFHXCURM is not in any library included in the STEPLIB of the batch job. Ensure the library containing the module is included in the STEPLIB concatenation, and restart the client application program.

413
DFHXCTRA_LOAD_FAILED
Explanation:

During Initialize_User processing, the external CICS interface attempted to load the trap module (DFHXCTRA). The load of this module has failed.

System action:

The Initialize_User call is rejected. The return code from the MVS load macro (R15) is returned in the subreason field-1. The external CICS interface handles the error, and returns the abend (R0) that would have occurred in the subreason field-2.

User response:

Using the MVS reason code, determine why the load failed. The most likely reason is that DFHXCTRA is not in any library included in the STEPLIB of the batch job. Ensure the library containing the module is included in the STEPLIB concatenation, and restart the client application program.

414
IRP_ABORT_RECEIVED
Explanation:

Whilst processing a DPL request, an error occurred in the CICS server region, resulting in an abort FMH7 flow being returned to the external CICS interface.

System action:

A message is returned to the client application program. This is the message that would have been issued to the terminal if the server program had been initiated from a terminal. A pointer to the message is returned to the client application program in the message pointer field of the EXCI return area. See the description of the EXCI return areas for the exact definition of the message format. The pipe is put into a "must close" state.

User response:

Use the message to determine the cause of the error. A typical example is where the server transaction cannot be attached, either because is disabled, or it has not been defined, or because of a security failure. Correct the problem, close and reopen the pipe, and reissue the DPL request.

415
INVALID_CONNECTION_DEFN
Explanation:

A DPL request has been rejected by CICS because the target connection is not defined for use by an external CICS client application program.

System action:

The DPL request is rejected and the pipe is put into a "must close" state.

User response:

The most likely reason for this is that the connection definition in the CICS server region has been defined incorrectly as a CICS-to-CICS MRO connection, instead of an EXCI connection. Ensure that PROTOCOL(EXCI) is specified on the appropriate CONNECTION and SESSIONS resource definitions. You must close and reopen the pipe before reissuing the DPL request.

416
INVALID_CICS_RELEASE
Explanation:

A DPL request has been rejected by the target CICS server region because it doesn't recognize the request.

System action:

The DPL call is rejected and the pipe is put into a "must close" state.

User response:

The most likely reason for this is that the client application program has specified a target CICS server region that does not support the external CICS interface. CICS regions earlier than CICS for MVS/ESA 4.1 do not recognize EXCI call requests. Correct the problem, close and reopen the pipe and then reissue the DPL request.

417
PIPE_MUST_CLOSE
Explanation:

A DPL request has been issued on a pipe that is in a "must close" state.

System action:

The DPL request is rejected.

User response:

Some EXCI errors are serious enough to require that the pipe be closed and reopened in order to restore the pipe to a point where it can be used for further DPL requests. Others, more minor errors, allow further calls without closing and reopening the pipe. A previous error on this pipe has been of the more serious variety and the pipe is now in a "must close" state. Close and reopen the pipe and reissue the DPL request.

418
INVALID_PIPE_TOKEN
Explanation:

An Open_Pipe, Close_Pipe, Deallocate_Pipe, or DPL request has been issued, but the pipe token passed on the call is either not a valid pipe, or is not a valid pipe allocated for this user (that is, there is mismatch between the user token and the pipe token).

System action:

The call is rejected.

User response:

Ensure that the pipe token has not been overwritten and is being passed correctly on the call. Also ensure there is no mismatch between the user token and the pipe token.

419
CICS_AFCB_PRESENT
Explanation:

An Initialize_User request has been issued on a TCB that has already been used by CICS or by CICS batch shared database. The external CICS interface cannot share a TCB with CICS, ensuring that a CICS application program cannot issue EXCI requests.

System action:

The Initialize_User request is rejected.

User response:

To use the external CICS interface, you must create a new TCB (or daughter TCB), and issue the EXCI calls under that unique TCB.

420
DFHXCOPT_LOAD_FAILED
Explanation:

During Initialize_User processing, the external CICS interface attempted to load its options module, DFHXCOPT. The load of this module failed.

System action:

The Initialize_User call is rejected. The return code from the MVS load macro (R15) is returned in the subreason field-1. The external CICS interface handles the error, and returns the abend (R0) that would have occurred in the subreason field-2.

User response:

Using the MVS reason code, determine why the load failed. The most likely reason is that DFHXCOPT is not in any library included in the STEPLIB of the batch job. Correct the problem and restart the client application program.

421
RUNNING_UNDER_AN_IRB
Explanation:

The EXCI call is issued under an MVS IRB, which is not permitted.

System action:

The call is rejected.

User response:

Determine why the call was issued under an IRB and change the client application program.

422
SERVER_ABENDED
Explanation:

Whilst processing a DPL request, the CICS server application program abended without handling the error.

System action:

The server application program is abended and backout out. The abend code is returned in the abend code field of the EXCI return area.

User response:

Determine why the server program abended and fix the problem.

423
SURROGATE_CHECK_FAILED
Explanation:

A DPL request has been issued specifying a USERID parameter. The userid specified was subject to a surrogate user security because SURROGCHK=YES is specified in the EXCI options table, DFHXCOPT. The surrogate user check failed. The surrogate security check verifies whether the EXCI batch region's userid is authorized as a surrogate of the userid specified on the DPL call.

System action:

The DPL call is rejected. The MVS external security manager's return code and reason code are returned in subreason field-1 and field-2. For RACF®, these documented in the External Security Interface (RACROUTE) Macro Reference for MVS.

User response:

If you want surrogate user checking, ensure that the EXCI batch region's userid has READ access to the profile userid.DFHEXCI in the SURROGAT general resource class, where userid is the userid specified on the DPL call.

If you don't want surrogate user security checking, specify SURROGCHK=NO in the DFHXCOPT options table.

See Surrogate user checking for more information.

424
RRMS_NOT_SUPPORTED
Explanation:

A DPL request omitting the SYNCONRETURN option has been made on a system that is not running OS/390® Release 5 (or a later, upward-compatible, release).

System action:

The call is rejected.

User response:

Ensure that the batch program is run on a system that is running the correct level of OS/390.

425
UOWID_NOT_ALLOWED
Explanation:

A DPL request omitted the SYNCONRETURN option, but specified a value of UOWID. This combination of parameters is not permitted on a DPL request.

System action:

The DPL_Request is rejected.

User response:

Check the client application program and ensure that the correct combination of parameters is used on the DPL call.

426
INVALID_TRANSID2
Explanation:

A DPL request has been issued with a transid2 parameter that consists of all blanks.

System action:

The DPL request is rejected.

User response:

Check the client application program and ensure that the transid2 parameter is specified correctly or has not been overwritten in some way.

427
INVALID_CCSID
Explanation:

A DPL request has been issued with a ccsid parameter that specifies an invalid value.

System action:

The DPL request is rejected.

User response:

Check the client application program and ensure that the ccsid parameter is specified correctly or has not been overwritten in some way.

428
INVALID_ENDIAN
Explanation:

A DPL request has been issued with a endian parameter that specifies an invalid value.

System action:

The DPL request is rejected.

User response:

Check the client application program and ensure that the endian parameter is specified correctly or has not been overwritten in some way.

[[ Contents Previous Page | Next Page Index ]]