DFHIIxxxx messages

Start of changeDFHII0001End of change
Start of changeapplid An abend (code aaa/bbbb) has occurred at offset X'offset' in module modname.End of change
Start of change
Explanation:

An abnormal end (abend) or program check has occurred in module modname. This implies that there may be an error in the CICS code. Alternatively, unexpected data has been input, or storage has been overwritten.

The code aaa/bbbb is a 3-digit hexadecimal MVS code (if applicable), followed by a 4-digit alphanumeric CICS code. The MVS code is a system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The CICS code is an abend code or a number referring to a CICS message (for example, AKEA is a CICS abend code; 1310 refers to message DFHTS1310).

End of change
Start of change
System action:

An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case CICS could be terminated by the caller ( for example, the domain manager, DFHDMDM). A message is issued to this effect.

Message DFHME0116 is normally produced containing the symptom string for this problem.

End of change
Start of change
User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

Look up the MVS code, if there is one, in the relevant MVS codes manual.

Next, look up the CICS alphanumeric code. This tells you, for example, whether the error was a program check, an abend, or a runaway, and may give you some guidance concerning user response.

If module modname is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.

If you cannot run without the full use of module modname you should bring CICS down in a controlled shutdown.

You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHIICP, DFHIIDM, DFHIIMM, DFHIIRH, DFHIIRP, DFHIIRQ, DFHIIRR, DFHIIXMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeaaa/bbbb,End of changeStart of changeX'End of changeStart of changeoffset', End of changeStart of changemodnameEnd of change

Start of changeDFHII0002End of change
Start of changeapplid A severe error (code X'code') has occurred in module modname.End of change
Start of change
Explanation:

An error has been detected in module modname. The code X'code' is the exception trace point ID which uniquely identifies what the error is and where the error was detected.

End of change
Start of change
System action:

An exception entry (code X'code' in the message) is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case, CICS could be terminated by the caller (for example, the domain manager, DFHDMDM). A message is issued to this effect.

Message DFHME0116 is normally produced containing the symptom string for this problem.

End of change
Start of change
User response:

This indicates a possible error in CICS code. The severity of its impact depends on the importance of the function being executed at the time of the error.

CICS may not have been terminated. If the message occurs once and module modname is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.

If the message recurs or if you cannot run without the full use of module modname, you should bring CICS down in a controlled shutdown.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHIICP, DFHIIDM, DFHIIMM, DFHIIRH, DFHIIRP, DFHIIRQ, DFHIIRR DFHIIXMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changecode',End of changeStart of changemodnameEnd of change

Start of changeDFHII0004End of change
Start of changeapplid A possible loop has been detected at offset X'offset' in module modname.End of change
Start of change
Explanation:

A CICS function is taking more time to process than CICS expects. A possible loop has been detected in module modname at offset X'offset'. This is the offset of the instruction which was executing at the time when the error was detected.

End of change
Start of change
System action:

An exception entry is made in the trace table.

A system dump is taken unless you have specifically suppressed the dump (by a user exit program at the XDUREQ exit, in the dump table or by global system dump suppression). CICS processing continues unless you have specified in the dump table that CICS should terminate.

Message DFHME0116 is normally produced containing the symptom string for this problem.

End of change
Start of change
User response:

If CICS has not been terminated, it is necessary to decide whether the problem is serious enough to bring CICS down.

Since some CICS functions can use a lot of CPU time, this message may have been caused by a long-running function, and there may not be an error. Usually, CICS purges a CICS function which exceeds the runaway task time interval that you have specified in the ICVR system initialization parameter. This means that execution of module modname is terminated and CICS continues.

If you have specified system initialization parameter ICVR=0 and you consider that module modname is looping, you must terminate CICS in order to terminate the runaway function.

If CICS has terminated module modname, and you consider that it was not a runaway, you should increase the value of the ICVR system initialization parameter. You have to close down CICS at a suitable time to do this permanently. You can change the ICVR time interval temporarily online using the CEMT transaction.

If raising the ICVR time does not solve the problem, you may need further assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHIICP, DFHIIDM, DFHIIMM, DFHIIRH, DFHIIRP, DFHIIRQ, DFHIIRR DFHIIXMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeX'offset', End of changeStart of changemodnameEnd of change

Start of changeDFHII0100 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver invoked the security URM urmname which denied permission for the request.End of change
Start of change
Explanation:

The IIOP Request Receiver received a request and called the security URM urmname. However, the URM set the return code to prevent the request being processed.

End of change
Start of change
System action:

Exception trace point 0124 is issued. Outstanding replies are processed. A systemException of NO_PERMISSION is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Determine why the URM denied permission for the client client_ip_addr.

Data 2 in the exception trace point entry contains the first 1024 bytes of the GIOP request.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipservice, End of changeStart of changeurmnameEnd of change

Start of changeDFHII0101 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver received a request with an invalid object key.End of change
Start of change
Explanation:

The IIOP Request Receiver received a GIOP header which contains an invalid object key.

End of change
Start of change
System action:

Trace point 020E is issued under some circumstances. Exception trace point 0127 is issued. Outstanding replies are processed. A systemException of INV_OBJREF is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Use the exception trace to determine why the objectKey is invalid.

Data 2 in the exception trace point entry contains the first 1024 bytes of the GIOP request.

If the user key portion of the object key is invalid trace point 020E indicates the failing field.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0102 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver is unable to send a request to the request processor.End of change
Start of change
Explanation:

The IIOP Request Receiver received a GIOP request but is unable to send the request to the ORB via a Request Stream.

End of change
Start of change
System action:

Exception trace point 012A is issued. Outstanding replies are processed. A systemException of COMM_FAILURE is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Use trace to determine why the RZSO SEND_REQUEST failed.

Data 2 in the exception trace point entry contains the first 1024 bytes of the GIOP request.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0103 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver is unable to receive a reply from the request processor.End of change
Start of change
Explanation:

The IIOP Request Receiver received a GIOP request and sent it to the ORB via a Request Stream. A reply was expected but the request receiver was unable to receive it.

End of change
Start of change
System action:

Exception trace point 012B is issued. Outstanding replies are processed. A systemException of INTERNAL is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Use trace to determine why the RZSO LISTEN_REPLY failed.

Data 2 in the exception trace point entry contains the first 1024 bytes of the GIOP request.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0104 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver received a request on a connection whose TCPIPSERVICE specified AUTHENTICATE(CERTIFICATE) but no CERTIFICATE_USERID is available.End of change
Start of change
Explanation:

The IIOP Request Receiver received a GIOP request; however, the TCPIPSERVICE tcpipservice specified AUTHENTICATE(CERTIFICATE) but the client has not provided a client certificate that maps to a valid userid in the external security manager. This may be for one of the following reasons:

End of change
Start of change
System action:

Exception trace point 0125 is issued. Outstanding replies are processed. A systemException of NO_PERMISSION is sent to the client. The socket is closed and the transaction is terminated.

End of change
Start of change
User response:

Ensure that the client has a valid certificate. Install the certificate in the external security manager with the TRUSTED attribute and which maps to a valid userid. If the security manager is the IBM OS/390 Security Server (RACF), this can be done with the RACDCERT command.

Data 2 in the exception trace point entry contains the first 1024 bytes of the GIOP request.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0105 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver received a request but the userid userid supplied by the URM urmname is not authorised.End of change
Start of change
Explanation:

The IIOP Request Receiver received a GIOP request, the URM specified in the TCPIPSERVICE tcpipservice was called and returned a different userid. However, this userid is not valid.

End of change
Start of change
System action:

Exception trace point 0126 is issued. Outstanding replies are processed. A systemException of NO_PERMISSION is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Determine why the URM urmname returned an invalid userid.

Data 2 in the exception trace point entry contains the first 1024 bytes of the GIOP request.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipservice, End of changeStart of changeurmname, End of changeStart of changeuseridEnd of change

Start of changeDFHII0106 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver find request stream failed.End of change
Start of change
Explanation:

The IIOP Request Receiver received a GIOP request; however, the attempt to find a Request Stream failed.

End of change
Start of change
System action:

Outstanding replies are processed. A systemException of COMM_FAILURE is sent to the client. The socket is closed and the transaction is terminated.

End of change
Start of change
User response:

Use trace and the previous DFHII0002 message to determine why program DFHIIRH failed to find a Request Stream.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0107 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver is unable to receive a reply from the request processor. Request ID: req_idEnd of change
Start of change
Explanation:

The IIOP Request Receiver received a GIOP request and sent it to the ORB via a Request Stream. A reply was expected but the request receiver was unable to receive it. The failure to receive the request could be caused by a transport failure or by the failure of the Request Processor. req_id is the requestId of the request expecting the reply.

End of change
Start of change
System action:

Exception trace point 012D is issued. A systemException of COMM_FAILURE or INTERNAL is sent to the client. The Request Receiver attempts to continue.

End of change
Start of change
User response:

Use trace to determine why the RZSO RECEIVE_REPLY failed.

Data 2 in the exception trace point entry contains the first 1024 bytes of the GIOP request.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipservice, End of changeStart of changereq_idEnd of change

Start of changeDFHII0108 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver was notified that a reply could not be delivered for requestId req_id. Reason: {Request Processor ABEND. | Request Stream closed. | Timeout. | Undefined.}End of change
Start of change
Explanation:

The IIOP Request Receiver request streams notify gate was called with a status that indicated that the reply was not available. The reply was for requestId req_id. The reason is set from the notify status.

End of change
Start of change
System action:

Exception trace point 013A is issued. A systemException of COMM_FAILURE or INTERNAL is sent to the client. The request receiver task attempts to continue.

End of change
Start of change
User response:

If the reason is TIMEOUT then determine why the Request Processor was unable to respond within the RTIMOUT time specified in the DFHCICSI profile. Otherwise use trace to determine why the Request Processor abended or why the Request Stream closed abnormally.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipservice, End of changeStart of changereq_id, End of changeStart of change{1=Request Processor ABEND., End of changeStart of change2=Request Stream closed.,End of changeStart of change3=Timeout., End of changeStart of change4=Undefined.}End of change

Start of changeDFHII0109 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver received a request with an OTS PropagationContext with a null coordinator.End of change
Start of change
Explanation:

The IIOP Request Receiver received a GIOP request. The request handler found an OTS PropagationContext with a null coordinator in the transaction context within the request header.

End of change
Start of change
System action:

Exception trace point 0148 is issued. Outstanding replies are processed. A systemException of INVALID_TRANSACTION is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Trace point II 0212 data 1 contains the transaction sequence (the contents of the transaction context - for a maximum of 512 bytes).

If the transaction context originated in WebSphere Application Server Advanced Edition, you should use the WebSphere administration console to set the command line option com.ibm.ejs.jts.jts.ControlSet.nativeOnly=false for the relevant server to cause it to propagate interoperable transaction contexts.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0110 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver received a request with no object key. Reason(X'pointId').End of change
Start of change
Explanation:

The IIOP Request Receiver received a GIOP header with no object key in the request or locate request header. The actual problem with the request or locate header depends on the reason pointid which is the II exception trace point id issued with the message:

013C
The addressing dispositon value is invalid. From GIOP 1.2 the addressing disposition within the target address should be a 2 byte value of 0, 1 or 2 indicating whether a KeyAddr, ProfileAddr or ReferenceAddr follows. This means that CICS cannot find an object key.
013D
The addressing dispositon value is 2 but a 0 value for profile number indicates that there are no tagged profiles and thus no object key.
013E
The addressing dispositon value is 2 and one or more tagged profiles exist. However the object key is in the tagged internet profile (profileId = 00000000) which is not present.
End of change
Start of change
System action:

Exception trace point 013C, 013D or 013E is issued. Outstanding replies are processed. A systemException of INV_OBJREF is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Use the exception trace to determine why the request or located request header is invalid.

Data 2 in the exception trace point entry contains the first 1024 bytes of the GIOP request.

The Common Object Request Broker: Architecture and Specification manual contains the definition of the request and locate request header.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipservice, End of changeStart of changeX'End of changeStart of changepointIdEnd of changeStart of change'End of change

Start of changeDFHII0200 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver SOCB notify gate is unable to attach transaction transaction.End of change
Start of change
Explanation:

The socket domain received a request for a TCPIP service which specified PROTOCOL(IIOP). However, the socket notify gate in the Request Receiver was unable to attach the transaction specified in the TCPIP service definition.

End of change
Start of change
System action:

Exception trace point 012E is issued.

End of change
Start of change
User response:

Check the definitions in the TCPIP service and the specified transaction.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipservice, End of changeStart of changetransactionEnd of change

Start of changeDFHII0201 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver received an invalid GIOP header.End of change
Start of change
Explanation:

The IIOP Request Receiver received a GIOP header with the magic field (first 4 bytes) not equal to 'GIOP'.

End of change
Start of change
System action:

Exception trace point 0106 is issued. Outstanding replies are processed. A messageError is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Determine why the GIOP header was sent with an incorrect magic field.

Data 2 in the exception trace point entry contains the GIOP header.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0202 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver received a GIOP header for an unsupported version. Supported version is GIOP sup_version. Received version is GIOP rec_version.End of change
Start of change
Explanation:

The IIOP Request Receiver received a GIOP header with an invalid GIOP version. This CICS supports up to GIOP sup_version. The version of the received message is GIOP rec_version.

End of change
Start of change
System action:

Exception trace point 0108 is issued. Outstanding replies are processed. A systemException is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

If this CICS region is part of a logical server which is being upgraded from one release to another, ensure that all regions within the logical server advertise the lowest level of GIOP supported across the logical server. Please see the Migration Guide of the most recent level of CICS for further advice.

Ensure that IORs published for use with this CICS region are at GIOP version sup_version and that the client ORB is using the IOR correctly.

Data 2 in the exception trace point entry contains the GIOP header.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipservice, End of changeStart of changesup_version, End of changeStart of changerec_versionEnd of change

Start of changeDFHII0204 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver received a fragment when none was expected.End of change
Start of change
Explanation:

The IIOP Request Receiver received a messageType of fragment; however, the 'more fragments' flag was not set in the previous message.

End of change
Start of change
System action:

Exception trace point 010F is issued. Outstanding replies are processed. A messageError is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Determine why the client sent a fragment when one was not expected.

Data 2 in the exception trace point entry contains the first 1024 bytes of the GIOP request.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0205 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver received a messageType of messageError.End of change
Start of change
Explanation:

The IIOP Request Receiver received a messageType of messageError.

End of change
Start of change
System action:

Exception trace point 0120 is issued. Outstanding replies are processed. A messageError is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Determine why the client sent a messageError. If it was in response to a message from the server, determine the message in error.

Data 2 in the exception trace point entry contains the GIOP Header.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0206 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver received a messageType of reply or locateReply which is not supported.End of change
Start of change
Explanation:

The IIOP Request Receiver received a messageType of reply or locateReply which is not supported by this Request Receiver.

End of change
Start of change
System action:

Exception trace point 0121 is issued. Outstanding replies are processed. A messageError is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Determine why the client sent a reply.

Data 2 in the exception trace point entry contains the GIOP Header.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0207 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver received a messageType of closeConnection which is not supported.End of change
Start of change
Explanation:

The IIOP Request Receiver received a messageType of closeConnection which is not supported by this Request Receiver.

End of change
Start of change
System action:

Exception trace point 0122 is issued. Outstanding replies are processed. A messageError is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Determine why the client sent a closeConnection.

Data 2 in the exception trace point entry contains the GIOP Header.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0208 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver received a GIOP header with an invalid messageType.End of change
Start of change
Explanation:

The IIOP Request Receiver received a GIOP header with an invalid message type.

End of change
Start of change
System action:

Exception trace point 0123 is issued. Outstanding replies are processed. A messageError is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Determine why the client sent GIOP header with an unknown messageType.

Data 2 in the exception trace point entry contains the GIOP Header.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0209 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver is unable to parse a request header.End of change
Start of change
Explanation:

The IIOP Request Receiver received a GIOP request header which it is unable to parse correctly.

End of change
Start of change
System action:

Exception trace point 0214 or 0215 is issued followed by Exception trace point 0128. Outstanding replies are processed. A messageError is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Determine why the request header is apparently invalid.

If exception trace point 0214 is issued then DFHIIRH was unable to parse the service contexts in the request header.

If exception trace point 0215 is issued then DFHIIRH found a length in the request header that was greater than the length of the whole buffer. The length is contained in data 1.

Data 2 in the exception trace point 0128 contains the first 1024 bytes of the request.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0210 EEnd of change
Start of changedate time applid The request receiver is unable to run the security URM: module. Reason(X'reason')End of change
Start of change
Explanation:

The IIOP Request Receiver attempted to invoke the security URM module but failed with a code supplied as reason.

End of change
Start of change
System action:

Exception trace point 0209 is issued. Outstanding replies are processed. A messageError is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Possible causes of the problem and an indication of how to solve them are given in the following list of reason code meanings:

Reason
Meaning and solution
1
The user exit program should be linked with AMODE(31). Ensure that the user exit is linked to the correct AMODE.
2
The user exit program has no PPT entry. Ensure that the PPT entry for the user exit program exists and is valid.
3
The user exit program could not be loaded. Ensure that the user exit program is contained in one of the data sets concatenated in the DFHRPL DD statement and has the correct name.
4
The user exit program has abended. This is a possible error within the user exit program. Check for any abend codes that may have been issued.
5
The user exit program is not enabled. CICS may have disabled the program due to an earlier error or the program may have been defined as disabled.
6
CICS is unable to load the user exit program for some other reason. Use trace to determine why the DFHPGLU call failed.
End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRHEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changemodule, End of changeStart of changeX'End of changeStart of changereasonEnd of changeStart of change'End of change

Start of changeDFHII0212 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver socket receive timed out. Replies outstanding: replies. Fragments in progress: fragmentsEnd of change
Start of change
Explanation:

The IIOP Request Receiver issued a socket receive request which timed out. There are replies replies outstanding. There are fragments fragments in progress.

End of change
Start of change
System action:

Exception trace point 010B or 010D is issued. Outstanding replies are NOT processed. A messageError is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Determine if the SOCKETCLOSE time in the TCPIP service definition is adequate and change it if necessary.

Data 2 in the exception trace point entry contains the first 1024 bytes of the request already received.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipservice, End of changeStart of changereplies, End of changeStart of changefragmentsEnd of change

Start of changeDFHII0213 EEnd of change
Start of changedate time applid The request receiver request streams notify gate was driven but the task no longer exists for request_id X'req_id' .End of change
Start of change
Explanation:

The IIOP Request Receiver Request Stream's notify gate was driven to indicate that a reply is ready, but the task no longer exists. The reply was for requestId req_id.

End of change
Start of change
System action:

Exception trace point 0139 is issued.

End of change
Start of change
User response:

Determine why the task no longer exists. It may have been purged or may not have expected a reply and so terminated.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changereq_idEnd of changeStart of change'End of change

Start of changeDFHII0214 EEnd of change
Start of changedate time applid The request receiver request streams notify gate was driven but the resume for the task failed for request_id X'req_id' .End of change
Start of change
Explanation:

The IIOP Request Receiver Request Stream's notify gate attempted to resume a task when a reply was available, but the resume failed. The task may have been force purged. The reply was for requestId req_id.

End of change
Start of change
System action:

Exception trace point 0138 is issued.

End of change
Start of change
User response:

Determine why the resume failed.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changereq_idEnd of changeStart of change'End of change

Start of changeDFHII0215 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver socb_notify_gate was driven but the resume for the task failed.End of change
Start of change
Explanation:

The IIOP Request Receiver socket notify gate attempted to resume a task after new data or some other socket activity occurred, but the resume failed. This would occur if the Request Receiver task was force purged.

End of change
Start of change
System action:

Exception trace point 0137 is issued.

End of change
Start of change
User response:

Determine whether the task was purged - this can be determined by examining the DSSR RESUME exit trace point for an exception of TASK_CANCELLED. If the task was not purged examine the DSSR RESUME exit trace point to see why the resume failed.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0216 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver asynchronous socket receive failed with an IO error.End of change
Start of change
Explanation:

The IIOP Request Receiver socket notify gate was driven with an action code of ERROR because an outstanding asynchronous socket receive request ended with an IO error.

End of change
Start of change
System action:

Exception trace point 013B is issued. The socket is closed and the request receiver is terminated.

End of change
Start of change
User response:

Determine why an IO error occurred on this port.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0217 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver received a GIOP header with an invalid length.End of change
Start of change
Explanation:

The IIOP Request Receiver received a GIOP header and attempted to receive the number of bytes specified in the header, however, that number of bytes was not available.

End of change
Start of change
System action:

Exception trace point 0107 is issued. Outstanding replies are processed. A messageError is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Determine why the GIOP header was sent with an incorrect length field.

Data 2 in the exception trace point entry contains the GIOP header.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0218 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver socket first receive timed out.End of change
Start of change
Explanation:

The IIOP Request Receiver issued a socket receive request for the first time following a newly opened connection. The receive request timed out after a CICS defined interval. If a client opens a TCPIP connection with CICS then it must be followed by the request within 30 seconds. CICS purges the request after this time to prevent clients from sending in connection requests that are not followed by the request itself and possibly causing CICS to reach the maximum number of tasks (mxt) limit.

End of change
Start of change
System action:

Exception trace point 0144 is issued. A messageError is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Determine which client is sending in a connection request to a TCPIP service defined with protocol IIOP, without also sending in the request.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0219 EEnd of change
Start of changedate time applid The request handler is unable to create or join a request stream because it is unable to reach the target for transaction tranid.End of change
Start of change
Explanation:

The IIOP request handler attempted to create or join a request stream for transaction tranid The transaction specifies a REMOTESYSTEM which cannot be contacted. This might be because IRC is not open or the target system is unavailable.

If the caller is the Request Receiver, message DFHII0106 follows this message. DFHII0106 shows the client ip address and TCPIPSERVICE name of the client.

If tranid is specified as 'n/a' then the request handler was attempting to JOIN a request stream but the transaction id is not available to the request handler.

If the caller was a request processor and a JOIN was being attempted the request processor may attempt to send the request via an outbound TCPIP request stream.

End of change
Start of change
System action:

Exception trace point 020B is issued if create failed. Exception trace point 020A is issued if join failed. If the caller is the Request Receiver a systemError is sent to the client, the socket is closed and the transaction terminated. If the caller is the Request Processor a systemError is sent to the client and the transaction is terminated.

End of change
Start of change
User response:

Determine the remote system name from the tranid definition. Ensure that IRC is open and the IRC connection named is in service.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRHEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranidEnd of change

Start of changeDFHII0220 EEnd of change
Start of changedate time applid The request handler is unable to create or join a request stream because remote system specified in transaction tranid cannot be reached.End of change
Start of change
Explanation:

The IIOP request handler attempted to create or join a request stream for transaction tranid. The transaction specifies a REMOTESYSTEM which cannot be found. The transaction was specified in a Request Model TRANSID parameter.

If the caller is the Request Receiver, message DFHII0106 follows this message. DFHII0106 shows the client ip address and TCPIPSERVICE name of the client.

End of change
Start of change
System action:

Exception trace point 020B is issued if create failed. Exception trace point 020A is issued if join failed. If the caller is the Request Receiver a systemError is sent to the client and the socket is closed and the transaction terminated. If the caller is the Request Processor a systemError is sent to the client and the transaction is terminated.

End of change
Start of change
User response:

Either install the relevant MRO connection or change the REMOTESYSTEM for transaction tranid to the required MRO connection that is installed.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRHEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranidEnd of change

Start of changeDFHII0221 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The Request Receiver failed to receive a request due to a socket error.End of change
Start of change
Explanation:

The IIOP Request Receiver attempted to receive a request from a socket, but the socket domain found an error.

End of change
Start of change
System action:

Exception trace point 010A is issued.

End of change
Start of change
User response:

Check for an earlier DFHSO message which describes the cause of this failure.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0222 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The Request Receiver received a request which indicated that a fragment is expected. This is not supported for GIOP 1.1 and earlier.End of change
Start of change
Explanation:

The IIOP Request Receiver received a GIOP 1.1 (or earlier) header with the 'fragment expected' bit on. CICS does not support fragments for GIOP 1.1.

End of change
Start of change
System action:

Exception trace point 0149 is issued.

End of change
Start of change
User response:

Find why the client is sending fragments.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0223 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The Request Receiver is unable to obtain storage.End of change
Start of change
Explanation:

The IIOP Request Receiver attempted to obtain storage from the storage manager domain.

End of change
Start of change
System action:

Exception trace point 0130 is issued.

End of change
Start of change
User response:

Find why the CICS system is short on storage. It may be necessary to limit the number of CIRR tasks by using the TRANCLASS mechanism on the TRANSACTION definition for CIRR or by lowering the MAXACTIVE parameter in the existing TRANCLASS. If this is not desirable then you may need to increase the EDSALIM specified in the System Initialization Table.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0224 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The Request Receiver received a request. Processing cannot continue because a security check has failed.End of change
Start of change
Explanation:

The IIOP Request Receiver received a request which contained a security context. The security check failed due to the reason stated in an earlier DFHII06xx message.

End of change
Start of change
System action:

Exception trace point 0150 is issued.

End of change
Start of change
User response:

Use the TCPIP service name and client ip address from this message and find the earlier DFHII06xx message to determine the cause of the failure.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0225 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The Request Receiver received a request without a valid security context for TCPIPSERVICE AUTHENTICATION({none | basic | asserted | unused | certificate}).End of change
Start of change
Explanation:

The IIOP Request Receiver received a request. The TCPIPSERVICE defined an authentication parameter specified in the message. However, no valid security context was found for that protocol.

End of change
Start of change
System action:

Exception trace point 0151 is issued.

End of change
Start of change
User response:

Determine whether the authentication parameter specified in the TCPIPSERVICE is wrong or whether the client sent a request with an invalid security context.

  1. There might be no security context at all.
  2. There might be a security context but of the wrong type.
  3. There might be a security context but with an unsupported version.
  4. There might be a basic authentication security context which contains a mechanism other than 'SSL' in ASCII.

Use trace to examine the request header found in trace point II 0132. There may be several of these. The GIOP Header is traced first and this is followed by the request header and body of the request. Trace level 1 traces the first 512 bytes. If the security context occurs after 512 bytes you need II trace level 1 and 2 set.

This probably occurs on the first request for the connection but may occur for subsequent requests.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipservice, End of changeStart of change{1=none, End of changeStart of change2=basic, End of changeStart of change3=asserted, End of changeStart of change4=unused, End of changeStart of change5=certificate}End of change

Start of changeDFHII0226End of change
Start of changedate time applid client_ip_addr tcpipservice The Request Receiver is unable to send a reply to the client.End of change
Start of change
Explanation:

The IIOP Request Receiver had recieved a request from the client and was attemting to send the client a reply. However the request receiver received an exception from the socket domain.

End of change
Start of change
System action:

Exception trace point 010E is issued.

End of change
Start of change
User response:

Find why the client is unable to receive the reply. This may be because the client has been turned off or because the request was cancelled by an operator action.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0227 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver socket has been closed. Replies outstanding: replies. Fragments in progress: fragmentsEnd of change
Start of change
Explanation:

The IIOP Request Receiver received a socket closed notification from the client and at least one of the requests was for GIOP 1.2 or above. There are replies replies outstanding from the request processor to earlier requests or locate requests.

There are fragments fragmented requests or locateRequests started.

End of change
Start of change
System action:

Exception trace point 014A is issued. Outstanding replies are processed, but not sent on to the client. The transaction is terminated.

End of change
Start of change
User response:

Determine why the client closed the socket when there were still replies or fragments in progress.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipservice, End of changeStart of changereplies, End of changeStart of changefragmentsEnd of change

Start of changeDFHII0228 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver socket has been closed.End of change
Start of change
Explanation:

The IIOP Request Receiver received a socket closed notification from the client and at least one of the requests was for GIOP 1.2 or above. At GIOP 1.2 or above the request reciever expects to receive a connectionClose request and not a socket close for an orderly shutdown. There are no replies outstanding.

End of change
Start of change
System action:

Exception trace point 014B is issued. The transaction is terminated.

End of change
Start of change
User response:

Determine why the client closed the socket before sending a closeConnection request.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0229 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver received a GIOP fragment with no preceeding request for requestId: requestIdEnd of change
Start of change
Explanation:

The IIOP Request Receiver received a fragment. However no GIOP request or locateRequest has been received for the fragment with the requestId requestId specified.

End of change
Start of change
System action:

Exception trace point 0152 is issued. Outstanding replies are processed. A messageError is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Determine why the client sent a fragment with no request. In GIOP 1.2 and above fragments contain a request header that just consists of the requestID. This should be consistant for all the fragments for the request or locate request being received including the first.

Fragments can be in progress for more than one request at a time.

Data 2 in the exception trace point entry contains the first fragment's GIOP header and request header.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipservice, End of changeStart of changerequestIdEnd of change

Start of changeDFHII0230 EEnd of change
Start of changedate time applid The request processor request streams notify gate was driven but the task no longer exists.End of change
Start of change
Explanation:

The IIOP Request Processor Request Stream's notify gate was driven to indicate that a reply or request is ready, but the task no longer exists.

End of change
Start of change
System action:

Exception trace point 070F is issued.

End of change
Start of change
User response:

Determine why the task no longer exists. The task may have been purged or may not have expected a reply and so terminated.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0231 EEnd of change
Start of changedate time applid The request processor request streams notify gate was driven but the resume for the task failed.End of change
Start of change
Explanation:

The IIOP Request Processor Request Stream's notify gate attempted to resume a task when a reply or request was available, but the resume failed.

End of change
Start of change
System action:

Exception trace point 0710 is issued.

End of change
Start of change
User response:

Determine why the resume failed. The task may have been purged.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0232 EEnd of change
Start of changedate time applid The request processor is unable to receive a request from the request receiver.End of change
Start of change
Explanation:

The IIOP Request Processor issued a Request Stream receive request to receive a request from the Request Receiver but the receive failed.

End of change
Start of change
System action:

Exception trace point 0709 is issued. See the system action for the DFHII1nnn message that is issued after this message.

End of change
Start of change
User response:

Use trace to determine why the RZTA RECEIVE_REQUEST failed. Look for earlier Request Stream(RZ) trace and messages.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0233 EEnd of change
Start of changedate time applid The request processor is unable to receive a reply from a target ORB.End of change
Start of change
Explanation:

The IIOP Request Processor attempted to receive a reply from a target ORB but the receive failed.

End of change
Start of change
System action:

Exception trace point 070B is issued. See the system action for the DFHII1nnn message that is issued after this message.

End of change
Start of change
User response:

Use trace to determine why the receive reply failed.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0234 EEnd of change
Start of changedate time applid The request processor is unable to send a reply to the request receiver.End of change
Start of change
Explanation:

The IIOP Request Processor issued a Request Stream send reply to send a reply to the Request Receiver but the send failed.

End of change
Start of change
System action:

Exception trace point 070A is issued. See the system action for the DFHII1nnn message that is issued after this message.

End of change
Start of change
User response:

Use trace to determine why the RZTA SEND_REPLY failed. Look for earlier Request Stream (RZ) trace and messages.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0235 EEnd of change
Start of changedate time applid The request processor is unable to send a request to a target ORB.End of change
Start of change
Explanation:

The IIOP Request Processor attempted to send a request to a target ORB but the send failed.

End of change
Start of change
System action:

Exception trace point 070C is issued. See the system action for the DFHII1nnn message that is issued after this message.

End of change
Start of change
User response:

Use trace to determine why the send request failed. Look for earlier Request Stream (RZ) trace and messages.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0236 EEnd of change
Start of changedate time applid The request processor is unable to receive a reply or a request from a target ORB or the request receiver.End of change
Start of change
Explanation:

The IIOP Request Processor attempted to await the arrival of a request from the Request Receiver or a reply from a target ORB but the attempt failed.

End of change
Start of change
System action:

Exception trace point 070D is issued. See the system action for the DFHII1nnn message that is issued after this message.

End of change
Start of change
User response:

Use trace to determine whether an RZLN LISTEN was for a reply or or a request. The 3 tokens in the RZLN LISTEN request will assist in this. The RZLN LISTEN exception will identify the reason for the failure.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0237 EEnd of change
Start of changedate time applid The request handler is unable to create or join a request stream because transaction tranid is not installed.End of change
Start of change
Explanation:

The IIOP request handler attempted to create or join a request stream for transaction tranid which is not installed. The transaction was specified in a Request Model TRANSID parameter.

If the caller is the Request Receiver, message DFHII0106 follows this message. DFHII0106 shows the client ip address and TCPIPSERVICE name of the client.

End of change
Start of change
System action:

Exception trace point 020B is issued if create failed. Exception trace point 020A is issued if join failed. If the caller is the Request Receiver a systemError is sent to the client and the socket is closed and the transaction terminated. If the caller is the Request Processor a systemError is sent to the client and the transaction is terminated.

End of change
Start of change
User response:

Either add an RDO definition for tranid with a program name of DFJIIRP or change the matching RDO Request Model that specifies a TRANSID of tranid to a transaction that is defined with a program of DFJIIRP.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRHEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranidEnd of change

Start of changeDFHII0238 EEnd of change
Start of changedate time applid The request processor received a request with an invalid header.End of change
Start of change
Explanation:

The IIOP Request Processor issued a receive_request to receive data from a Request Receiver but the data received did not start with the GIOP magic characters.

End of change
Start of change
System action:

Exception trace point 0719 is issued. See the system action for the DFHII1nnn message that is issued after this message.

End of change
Start of change
User response:

Use trace to determine why a valid GIOP header was not received.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0239 EEnd of change
Start of changedate time applid A request processor request does not contain a valid cicsTaskTrackingContext.End of change
Start of change
Explanation:

The IIOP Request Processor either received a request from the request receiver or was about to send a request. However, the request does not contain a valid cicsTaskTrackingContext.

End of change
Start of change
System action:

Exception trace point 0725 is issued if the context is missing. Exception trace point 0714 is issued if the request handler was unable to parse the request.

The transaction is abended.

End of change
Start of change
User response:

Use trace to determine whether the request had just been received from a Request Receiver (DFHIIRP RECEIVE_REQUEST) or whether it had been built by the ORB and was about to be sent (DFHIIRP INVOKE). Data3 in both trace points contain the request.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0240 EEnd of change
Start of changedate time applid The request processor received a reply with an invalid header.End of change
Start of change
Explanation:

The IIOP Request Processor attempted to receive a reply from a target ORB but the data received did not start with the GIOP magic characters.

End of change
Start of change
System action:

Exception trace point 071B is issued. See the system action for the DFHII1nnn message that is issued after this message.

End of change
Start of change
User response:

Use trace to determine why a valid GIOP header was not received.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0241 EEnd of change
Start of changedate time applid The request processor received a reply fragment with an invalid header.End of change
Start of change
Explanation:

The IIOP Request Processor issued a receive_reply to receive a fragment from target ORB but the data received did not start with the GIOP magic characters.

End of change
Start of change
System action:

Exception trace point 071C is issued. See the system action for the DFHII1nnn message that is issued after this message.

End of change
Start of change
User response:

Use trace to determine why a valid GIOP fragment header was not received.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0242 EEnd of change
Start of changedate time applid The request processor did not receive a reply fragment.End of change
Start of change
Explanation:

The IIOP Request Processor issued a receive_reply to receive a fragment from a target ORB but the data received did not have a GIOPMessageType of GIOPFragment.

End of change
Start of change
System action:

Exception trace point 071D is issued. See the system action for the DFHII1nnn message that is issued after this message.

End of change
Start of change
User response:

Use trace to determine why a valid GIOP fragment was not received.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0243 EEnd of change
Start of changedate time applid The request processor received a messageError reply.End of change
Start of change
Explanation:

The IIOP Request Processor attempted to receive a reply from a target ORB but the data received had a GIOPMessageTYpe of GIOPMessageError.

End of change
Start of change
System action:

Exception trace point 0720 is issued. See the system action for the DFHII1nnn message that is issued after this message.

End of change
Start of change
User response:

Use trace to determine why a GIOPMessageError was received.

Determine whether the original request was in error or whether the target ORB incorrectly sent a messageError.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0244 EEnd of change
Start of changedate time applid The request processor received an invalid GIOPMessageType.End of change
Start of change
Explanation:

The IIOP Request Processor attempted to receive a reply from a target ORB. The data received had a known GIOPMessageType but is not valid when sent from a server.

End of change
Start of change
System action:

Exception trace point 0721 is issued. See the system action for the DFHII1nnn message that is issued after this message.

End of change
Start of change
User response:

Use trace to determine why the target ORB sent an invalid GIOPMessageType.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0245 EEnd of change
Start of changedate time applid The request processor received an unknown GIOPMessageType.End of change
Start of change
Explanation:

The IIOP Request Processor attempted to receive a reply from a target ORB but the data received had an unknown GIOPMessageType.

End of change
Start of change
System action:

Exception trace point 0722 is issued. See the system action for the DFHII1nnn message that is issued after this message.

End of change
Start of change
User response:

Use trace to determine why the target ORB sent an unknown GIOPMessageType.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0246 EEnd of change
Start of changedate time applid The request processor received an unexpected GIOPFragment.End of change
Start of change
Explanation:

The IIOP Request Processor attempted to receive a reply from a target ORB. The data received had a GIOPMessageType of GIOPFragment but no earlier GIOPHeader was received with the 'more fragments to follow' bit on.

End of change
Start of change
System action:

Exception trace point 0723 is issued. See the system action for the DFHII1nnn message that is issued after this message.

End of change
Start of change
User response:

Use trace to determine why the target ORB sent a GIOPFragment without sending an earlier message indicating that a fragment is to follow.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0247 EEnd of change
Start of changedate time applid The request processor is unable to receive a {reply from a target ORB | request from the Request Receiver}. Reason: {ABEND. | Request Stream closed. | Timeout.}End of change
Start of change
Explanation:

The IIOP Request Processor attempted to await the arrival of a request from the Request Receiver or a reply from a target ORB but was notified that the data was not available. Reason is set from the notify status.

End of change
Start of change
System action:

Exception trace point 070E is issued. See the system action for the DFHII1nnn message that is issued after this message.

End of change
Start of change
User response:

Use trace to determine why the failure occurred. Trace point 070E Data 3 contains listen_data which contains the Request Stream token. The listen_data also contains the requestID of the request expecting a reply if the notification was for a reply.

A reason of ABEND indicates that the request stream detected an abend in the Request Receiver or target ORB.

A reason of Request Stream closed indicates that the Request Stream closed abnormally.

A reason of TIMEOUT when failing to receive a request, indicates that the RTIMOUT value in the profile for the Request Processor transaction has been exceeded.

A reason of TIMEOUT when failing to receive a reply, indicates that the RTIMOUT value in the DFHCICSI profile has been exceeded.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=reply from a target ORB,End of changeStart of change2=request from the Request Receiver}, End of changeStart of change{1=ABEND., End of changeStart of change2=Request Stream closed., End of changeStart of change3=Timeout.}End of change

Start of changeDFHII0248 EEnd of change
Start of changedate time applid The request processor may have been started invalidly.End of change
Start of change
Explanation:

The IIOP Request Processor program DFHIIRP was unable to find its current request stream. This may be because a transaction specifying DFJIIRP was initiated from the wrong place.

End of change
Start of change
System action:

See the system action for the DFHII1nnn message that is issued after this message.

End of change
Start of change
User response:

Use trace to find which transaction caused DFJIIRP to be called and find where it was initiated. If it was not initiated by the request stream domain then it may have been initiated from a terminal which is not allowed. Another possibility is that an IIOP TCPIPSERVICE definition mistakenly has a transaction parameter of CIRP where it should have CIRR or the customer equivalents. If, however, it was initiated by the request stream domain then further investigation of the trace is needed.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0249 EEnd of change
Start of changedate time applid The Request Processor received a reply which indicated that a fragment is expected. This is not supported for GIOP 1.1 and earlier.End of change
Start of change
Explanation:

The IIOP Request Processor received a GIOP 1.1 (or earlier) reply header from a target orb with the 'fragment expected' bit on. CICS does not support fragments for GIOP 1.1.

End of change
Start of change
System action:

Exception trace point 0727 is issued.

End of change
Start of change
User response:

Find why the target ORB is sending fragments.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0250 EEnd of change
Start of changedate time applid The request processor received an invalid reply fragment.End of change
Start of change
Explanation:

The IIOP Request Processor issued a receive_reply to receive a fragment from a target ORB but the reply header did not contain the same requestId as the first fragment.

End of change
Start of change
System action:

Exception trace point 0728 is issued. See the system action for the DFHII1nnn message that is issued after this message.

End of change
Start of change
User response:

Use trace to determine why the requestId changed. Each fragment within a reply should contain the same requestId.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0251 EEnd of change
Start of changedate time applid client_ip_addr tcpipservice The request receiver received a GIOP fragment whose length is not divisible by 8.End of change
Start of change
Explanation:

The IIOP Request Receiver received a request or locate request which indicated that further fragments are to follow. However, the length of the GIOP header plus the length of the message is not divisible by 8.

End of change
Start of change
System action:

Exception trace point 0135 is issued. Outstanding replies are processed. A messageError is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Determine why the client sent a fragment that contained an invalid length. In GIOP 1.2 and above each fragment except the last must have a total length that is divisible by 8.

Data 2 in the exception trace point entry contains the first fragment's GIOP header and request header.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclient_ip_addr, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHII0252 EEnd of change
Start of changedate time applid The request processor received a fragmented reply whose length is not divisible by 8.End of change
Start of change
Explanation:

The IIOP Request Processor issued a receive_reply to receive a fragment from target ORB but the message_length plus the length of the GIOP header was not divisible by 8.

End of change
Start of change
System action:

Exception trace point 071E is issued. See the system action for the DFHII1nnn message that is issued after this message.

End of change
Start of change
User response:

Use trace to determine why the client ORB sent a fragment with an invalid length.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0300 EEnd of change
Start of changedate time applid The CICS ORB failed to find the requested plugin plugin.End of change
Start of change
Explanation:

The CICS ORB attempted to instantiate the requested plugin class plugin but the ORB could not find this class on the current classpath.

End of change
Start of change
System action:

The plugin is not loaded.

End of change
Start of change
User response:

Examine the value set for the classpath in the JVM profile being used from the XDFHENV dataset. The pathname for the requested plugin must be present in the classpath.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.DebugRequestInterceptorEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changepluginEnd of change

Start of changeDFHII0301 EEnd of change
Start of changedate time applid The CICS ORB plugin plugin has thrown exception exception.End of change
Start of change
Explanation:

The CICS ORB caught an exception thrown from plugin plugin.

End of change
Start of change
System action:

The ORB attempts to continue processing the user application.

End of change
Start of change
User response:

Either contact the plugin vendor for further assistance or catch the exception in the body of your plugin.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.DebugRequestInterceptorEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeplugin, End of changeStart of changeexceptionEnd of change

Start of changeDFHII0401 IEnd of change
Start of changedate time applid REQUESTMODEL rqmodelname has been installed.End of change
Start of change
Explanation:

This is an audit log message indicating that REQUESTMODEL rqmodelname has been added to the system using the INSTALL command.

End of change
Start of change
System action:

The system continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIMMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changerqmodelnameEnd of change

Start of changeDFHII0402 IEnd of change
Start of changedate time applid REQUESTMODEL rqmodelname has been discarded.End of change
Start of change
Explanation:

This is an audit log message indicating that REQUESTMODEL rqmodelname has been removed from the system using the DISCARD command.

End of change
Start of change
System action:

The system continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIMMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changerqmodelnameEnd of change

Start of changeDFHII0501 EEnd of change
Start of changedate time applid The II command processor is unable to run program DFJIIRP.End of change
Start of change
Explanation:

DFHIICP has been called to link to program DFJIIRP however the link failed.

End of change
Start of change
System action:

The system continues normally.

End of change
Start of change
User response:

If there is a DFHSJ message indicating that there is a jvmprofile problem then take the neccessary action. If there is a DFHPG message refering to DFJIIRP then take the necessary action.

This message could also occur if you are attempting to operate on resources requiring a JVM, for example CORBASERVERs or DJARs, from within a JVM program.

Otherwise use trace to determine why the DFHPGLE link failed or examine the DFJIIRP program definition. For instance the DFJIIRP program definition might be disabled.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIICPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHII0601 EEnd of change
Start of changedate time applid The request receiver received a request with a basic authentication security context. The request is rejected because {the userid is too long | the password is too long | of an invalid msgType |the sessionId already exists | the sessionId is not found | of a malformed context |unused | the version is invalid}.End of change
Start of change
Explanation:

The IIOP Request Receiver received a request which contained a basic authentication security context. DFHIIRS was processing the security context but found the error identified in the message.

End of change
Start of change
System action:

Exception trace point in the range II 0900-09FF is issued. Message DFHII0223 is issued. Outstanding replies are processed. A systemException containing a modified security context and a string of MARSHAL or INTERNAL is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Use trace to examine the security context contained within the client causing the violation.

Message DFHII0223 contains the TCPIP service name and the client IP address.

Determine whether the source of the problem is within the client sending the context or within this CICS system.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRSEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=the userid is too long,End of changeStart of change2=the password is too long, End of changeStart of change3=of an invalid msgType, End of changeStart of change4=the sessionId already exists,End of change Start of change5=the sessionId is not found, End of changeStart of change6=of a malformed context, End of changeStart of change7=unused, End of changeStart of change8=the version is invalid}End of change

Start of changeDFHII0602 EEnd of change
Start of changedate time applid The request receiver received a request with a basic authentication security context. The request is rejected because {the ESM inactive | CICS security is inactive | of an unknown ESM error |the command is not authorised | the password is not authorised | the userid is undefined | the password has expired |the userid has been revoked | of a userid format error | the applid is not authorised | of an unexpected return code}.End of change
Start of change
Explanation:

The IIOP Request Receiver received a request which contained a basic authentication security context. DFHIIRS was processing the security context but found the error identified in the message.

End of change
Start of change
System action:

Exception trace point in the range II 0900-09FF is issued. Message DFHII0223 is issued. Outstanding replies are processed. A systemException containing a modified security context and a string of NO_PERMISSION, MARSHAL or INTERNAL is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

If the problem is caused by a security violation determine which client caused the problem.

If the problem is an operational one take the necessary steps to allow the security process to work.

Message DFHII0223 contains the TCPIP service name and the client IP address.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRSEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=the ESM inactive, End of changeStart of change2=CICS security is inactive, End of changeStart of change3=of an unknown ESM error,End of changeStart of change4=the command is not authorised, End of changeStart of change5=the password is not authorised, End of changeStart of change6=the userid is undefined, End of changeStart of change7=the password has expired,End of changeStart of change8=the userid has been revoked, End of changeStart of change9=of a userid format error, End of changeStart of change10=the applid is not authorised, End of changeStart of change11=of an unexpected return code}End of change

Start of changeDFHII0603 EEnd of change
Start of changedate time applid The request receiver received a request with an asserted identity security context. The request is rejected because {of an invalid msgType | the userid is too long | of an invalid credType |it contains an invalid length | the version is invalid}.End of change
Start of change
Explanation:

The IIOP Request Receiver received a request which contained an asserted identity security context. DFHIIRS was processing the security context but found the error identified in the message.

End of change
Start of change
System action:

Exception trace point in the range II 0900-09FF is issued. Message DFHII0223 is issued. Outstanding replies are processed. A systemException containing a modified security context and a string of MARSHAL or INTERNAL is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

Use trace to examine the security context contained within the client causing the violation.

Message DFHII0223 contains the TCPIP service name and the client IP address.

Determine whether the source of the problem is within the client sending the context or within this CICS system.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRSEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=of an invalid msgType,End of changeStart of change2=the userid is too long, End of changeStart of change3=of an invalid credType, End of changeStart of change4=it contains an invalid length,End of change Start of change5=the version is invalid}End of change

Start of changeDFHII0604 EEnd of change
Start of changedate time applid The request receiver received a request with an asserted identity security context. The request is rejected because {CICS security is inactive | the userid is undefined | the userid is not determined | the ESM is inactive | the ESM is not present |the command is not authorised | the XSRC resource is not found | the XSRC class is not found | the XSRC resource name is invalid | the USAD reason is not expected | the XSRC reason is not expected}.End of change
Start of change
Explanation:

The IIOP Request Receiver received a request which contained an asserted identity security context. DFHIIRS was processing the security context but found the error identified in the message.

End of change
Start of change
System action:

Exception trace point in the range II 0900-09FF is issued. Message DFHII0223 is issued. Outstanding replies are processed. A systemException containing a modified security context and a string of NO_PERMISSION, MARSHAL or INTERNAL is sent to the client. The socket is closed and the transaction terminated.

End of change
Start of change
User response:

If the problem is caused by a security violation determine which client caused the problem.

If the problem is an operational one take the necessary steps to allow the security process to work.

Message DFHII0223 contains the TCPIP service name and the client IP address.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changeDFHIIRSEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=CICS security is inactive,End of changeStart of change2=the userid is undefined, End of changeStart of change3=the userid is not determined, End of changeStart of change4=the ESM is inactive,End of changeStart of change5=the ESM is not present, End of changeStart of change6=the command is not authorised, End of changeStart of change7=the XSRC resource is not found, End of changeStart of change8=the XSRC class is not found, End of change Start of change9=the XSRC resource name is invalid, End of changeStart of change10=the USAD reason is not expected, End of changeStart of change11=the XSRC reason is not expected}End of change

Start of changeDFHII1000 EEnd of change
Start of changedate time applid className methodName internal error desc.End of change
Start of change
Explanation:

An internal logic error desc was detected in method methodName of class className of the IIOP RequestProcessor.

End of change
Start of change
System action:

An II domain exception trace entry is made and a system dump requested. The RequestProcessor terminates abnormally.

End of change
Start of change
User response:

Use the trace and dump to determine the cause of the problem. If the problem persists you may need to contact your IBM support representative.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.RequestProcessorEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeclassName, End of changeStart of changemethodName,End of changeStart of changedescEnd of change

Start of changeDFHII1001 EEnd of change
Start of changedate time applid Severe error: desc, resulting from: th.End of change
Start of change
Explanation:

A severe error, identified by the string desc, was detected by the IIOP RequestProcessor. This is usually related to a Java Throwable, th.

End of change
Start of change
System action:

An II domain exception trace entry is made and a system dump requested. The RequestProcessor terminates abnormally.

End of change
Start of change
User response:

Use the trace, dump and any previous messages to determine the cause of the problem. If the problem persists you may need to contact your IBM support representative.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.RequestProcessorEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedesc, End of changeStart of changethEnd of change

Start of changeDFHII1002 EEnd of change
Start of changedate time applid Failure e obtaining data for LogicalServer serverName.End of change
Start of change
Explanation:

An EJ domain INQUIRE_LOGICAL_SERVER command for this RequestProcessor's LogicalServer was issued by the setAttributesFromIILS method during RequestProcessor initialization. The call resulted in error e.

End of change
Start of change
System action:

An II domain exception trace is issued and RequestProcessor initialization is terminated.

End of change
Start of change
User response:

Ensure that a CORBASERVER definition for LogicalServer serverName is available in the CICS region.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.LogicalServerImplEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changee, End of changeStart of changeserverNameEnd of change

Start of changeDFHII1003 EEnd of change
Start of changedate time applid LogicalServerPlugin load failure e for class className.End of change
Start of change
Explanation:

The LogicalServerPluginRegistry received exception e attempting to instantiate LogicalServerPlugin class className. A possible cause of this error is that the class is missing from the trusted middleware classpath, TMCLASSPATH, for this RequestProcessor program. This could be due to a missing, corrupt or inaccessible CICS jar file.

End of change
Start of change
System action:

An II domain exception trace is made and RequestProcessor initialization is terminated because the LogicalServerPlugin classes are required for proper execution of a CICS RequestProcessor.

End of change
Start of change
User response:

Use the message and/or trace to determine the class in error and ensure that it is available to the RequestProcessor on the TMCLASSPATH.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.LogicalServerPluginRegistryEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changee, End of changeStart of changeclassNameEnd of change

Start of changeDFHII1004 EEnd of change
Start of changedate time applid Exception e creating object of class javaClassName for OMG interface interfaceName.End of change
Start of change
Explanation:

The create_object method of the CICS CosLifeCycle GenericFactory implementation determined that an object of class javaClassName could implement OMG interface interfaceName, but it failed to instantiate such an object.

Common causes of this message are:-

End of change
Start of change
System action:

An II domain exception trace is issued and a CosLifeCycle::NoFactory exception is returned to the caller.

End of change
Start of change
User response:

Correct the CLASSPATH and/or class implementation as necessary and/or inspect the exception data recorded in the trace dataset.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.cso._GenericFactoryImplEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changee, End of changeStart of changejavaClassName, End of changeStart of changeinterfaceNameEnd of change

Start of changeDFHII1005 EEnd of change
Start of changedate time applid Exception e creating object of class className.End of change
Start of change
Explanation:

CorbaStatelessManager, the servant manager for CORBA stateless objects, failed to instantiate or register an object of class className due to exception e. A possible cause of this message is that the named class cannot be found on the application CLASSPATH for this RequestProcessor program.

End of change
Start of change
System action:

An II domain exception trace is issued and a CORBA::OBJECT_NOT_EXIST exception is returned to the caller.

End of change
Start of change
User response:

Correct the CLASSPATH if necessary and/or inspect the exception data recorded in the trace dataset.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.cso.CorbaStatelessManagerEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changee, End of changeStart of changeclassNameEnd of change

Start of changeDFHII1006 EEnd of change
Start of changedate time applid Exception e writing IOR file fileName.End of change
Start of change
Explanation:

The command processor for CORBA stateless objects was invoked during a CORBA server publish operation to make the GenericFactory IOR file available. An attempt to write to file fileName from method writeToFile in class PublishLogicalServerCommand failed with exception e.

End of change
Start of change
System action:

An IILS_EXCEPTION with reason IILS_SHELF_ACCESS_ERROR is returned to the caller.

End of change
Start of change
User response:

Correct the HFS access available to the CICS job and reissue publish.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.cso.PublishLogicalServerCommandEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changee, End of changeStart of changefileNameEnd of change

Start of changeDFHII1007 EEnd of change
Start of changedate time applid Unknown object adapter oa in object key.End of change
Start of change
Explanation:

The CICS ObjectResolver implementation, RootOAImpl, has received an ObjectKey from the ORB containing an unrecognisable ObjectAdapter name oa. This could be caused by invalid input data or a CICS code error.

End of change
Start of change
System action:

An II domain exception trace is made and a system dump requested. The ObjectResolver throws NoSuchObjectException to the ORB which returns CORBA::OBJECT_NOT_EXIST to the client.

End of change
Start of change
User response:

Use the trace and dump to determine the cause of the problem. Data-2 in the exception trace entry contains the UserKey part of the ObjectKey. Data-3 in the exception trace entry contains the ObjectAdapter name extracted from it. This ObjectAdapter name should either be an internal CICS adapater name, beginning with the letters DFH, or be the name of the CORBASERVER, padded as necessary with EBCDIC blanks, for which this RequestProcessor is active.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.oa.RootOAImplEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeoaEnd of change

Start of changeDFHII1008 EEnd of change
Start of changedate time applid Exception e creating UserKey.End of change
Start of change
Explanation:

The CICS ObjectResolver implementation, RootOAImpl, received an unexpected exception e creating a UserKey object from the input byte array. The byte array is passed to the ObjectResolver by the ORB. It is the object resolver defined part of the ObjectKey known as the UserKey. The constructor of the UserKey class was unable to map the byte array into the fields of a UserKey object. This could be caused by invalid input data or a CICS code error.

End of change
Start of change
System action:

An II domain exception trace is made and a system dump requested. The ObjectResolver throws NoSuchObjectException to the ORB which returns CORBA::OBJECT_NOT_EXIST to the client.

End of change
Start of change
User response:

Use the trace and dump to determine the cause of the problem. Data-2 in the exception trace entry contains the UserKey part of the ObjectKey. Data-3 in the exception trace entry contains a stack trace of the exception.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.oa.RootOAImplEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeeEnd of change

Start of changeDFHII1009 EEnd of change
Start of changedate time applid Failure dr issuing IIRP invoke.End of change
Start of change
Explanation:

An unexpected failure dr occurred issuing an IIRP invoke request on an outbound RequestStream.

End of change
Start of change
System action:

An II domain exception trace entry is made. For an Exception response, the CICSSourceOutputStream throws a java.io.IOException and a CORBA::COMM_FAILURE is returned to the client. For Disaster or Invalid responses, a system dump will have already been requested by IIRP. The CICSSourceOutputStream throws a com.ibm.cics.iiop.RequestProcessorRuntimeException and the RequestProcessor terminates abnormally.

End of change
Start of change
User response:

Use trace and dump to determine the cause of the failure. If the problem persists you may need to contact your IBM support representative.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.orb.CICSSourceOutputStreamEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedrEnd of change

Start of changeDFHII1010 EEnd of change
Start of changedate time applid Failure dr receiving request from IIRP.End of change
Start of change
Explanation:

An unexpected failure dr occurred receiving a request from the RequestStream of which this RequestProcessor is the target.

End of change
Start of change
System action:

An II domain exception trace entry is made. For an Exception response, the CICSTargetInputStream throws a java.io.IOException. For Disaster or Invalid responses, a system dump will have already been requested by IIRP. The CICSTargetInputStream throws a com.ibm.cics.iiop.RequestProcessorRuntimeException. In both cases, the RequestProcessor terminates abnormally since it cannot reply to the client.

End of change
Start of change
User response:

Use trace and dump to determine the cause of the failure. If the problem persists you may need to contact your IBM support representative.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.orb.CICSTargetInputStreamEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedrEnd of change

Start of changeDFHII1011 EEnd of change
Start of changedate time applid Failure dr sending a reply to IIRP.End of change
Start of change
Explanation:

An unexpected failure dr occurred sending a reply to the RequestStream of which this RequestProcessor is the target.

End of change
Start of change
System action:

An II domain exception trace entry is made. For an Exception response, the CICSTargetOutputStream throws a java.io.IOException. For Disaster or Invalid responses, a system dump will have already been requested by IIRP. The CICSTargetOutputStream throws a com.ibm.cics.iiop.RequestProcessorRuntimeException. In both cases, the RequestProcessor terminates abnormally since it cannot reply to the client.

End of change
Start of change
User response:

Use trace and dump to determine the cause of the failure. If the problem persists you may need to contact your IBM support representative.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.orb.CICSTargetOutputStreamEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedrEnd of change

Start of changeDFHII1012 EEnd of change
Start of changedate time applid Failure dr receiving reply from IIRP.End of change
Start of change
Explanation:

An unexpected failure dr occurred receiving a reply from an outbound RequestStream.

End of change
Start of change
System action:

An II domain exception trace entry is made. For an Exception response, the CICSSourceInputStream throws a java.io.IOException and a CORBA::COMM_FAILURE is returned to the client. For Disaster or Invalid responses, a system dump will have already been requested by IIRP. The CICSSourceInputStream throws a com.ibm.cics.iiop.RequestProcessorRuntimeException and the RequestProcessor terminates abnormally.

End of change
Start of change
User response:

Use trace and dump to determine the cause of the failure. If the problem persists you may need to contact your IBM support representative.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.orb.CICSSourceInputStreamEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedrEnd of change

Start of changeDFHII1013 EEnd of change
Start of changedate time applid Failure dr establishing connection to host host port port.End of change
Start of change
Explanation:

An unexpected failure dr occurred attempting to create an outbound RequestStream to host host port port. If the response is Exception and the reason is Service_Not_Available, but the hostname is valid then this may be an error caused by a name server failure. This may be a transient failure or a configuration error.

End of change
Start of change
System action:

An II domain exception trace entry is made. For an Exception response, the CICSConnection causes a CORBA::COMM_FAILURE to be returned to the client. For Disaster or Invalid responses, a system dump will have already been requested by RZ domain. The CICSConnection throws a com.ibm.cics.iiop.RequestProcessorRuntimeException and the RequestProcessor terminates abnormally.

End of change
Start of change
User response:

Use trace and dump to determine the cause of the failure. If the problem persists you may need to contact your IBM support representative.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.orb.CICSConnectionEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedr, End of changeStart of changehost, End of changeStart of changeportEnd of change

Start of changeDFHII1014 EEnd of change
Start of changedate time applid Invalid SSL type connSsl used for connection to CORBASERVER serverName, with SSL serverSsl.End of change
Start of change
Explanation:

The SSL type connSsl received in a CICSConnectionContext does not match the SSL parameter serverSsl configured for the target CORBASERVER serverName. The data in a CICSConnectionContext is derived from the TCPIPSERVICE in the listener region, by the RequestReceiver. This problem can occur if the CORBASERVER definition is ALTERed but not PUBLISHed, that is, IORs from a previous configuration are still in use.

End of change
Start of change
System action:

An II domain exception trace entry is made, a com.ibm.cics.iiop.RequestProcessorRuntimeException is thrown and the RequestProcessor terminates abnormally.

End of change
Start of change
User response:

Ensure that the IORs in use match the currently active CORBASERVER definitions.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.LogicalServerImplEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeconnSsl, End of changeStart of changeserverName, End of changeStart of changeserverSslEnd of change

Start of changeDFHII1015 EEnd of change
Start of changedate time applid Invalid port number connPort used for sslType connection to CORBASERVER serverName, with PORT port, SSLPORT sslPort.End of change
Start of change
Explanation:

The listenerPort connPort received in a CICSConnectionContext does not match the port configured for the target CORBASERVER serverName. If the connection type in use, sslType, is SSL_NO, it should match the CORBASERVER PORT port. If the connection type in use, sslType, is SSL_YES, or SSL_CLIENTCERT, it should match the CORBASERVER SSLPORT parameter sslPort. The data in a CICSConnectionContext is derived from the TCPIPSERVICE in the listener region, by the RequestReceiver. This problem can occur if the CORBASERVER definition is ALTERed but not PUBLISHed, that is, IORs from a previous configuration are still in use.

End of change
Start of change
System action:

An II domain exception trace entry is made, a com.ibm.cics.iiop.RequestProcessorRuntimeException is thrown and the RequestProcessor terminates abnormally.

End of change
Start of change
User response:

Ensure that the IORs in use match the currently active CORBASERVER definitions.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.LogicalServerImplEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeconnPort, End of changeStart of changesslType, End of changeStart of changeserverName, End of changeStart of changeport, End of changeStart of changesslPortEnd of change

Start of changeDFHII1016 EEnd of change
Start of changedate time applid Failure obtaining JNDI context for CORBASERVER serverName, prefix jndiPrefix at level prefixPart. Exception exc was received.End of change
Start of change
Explanation:

An exception exc was returned during creation of the JNDI Context for publication of an object reference from CORBASERVER serverName to the name server. A JNDI context is created during a DJAR or CORBASERVER PUBLISH operation. Objects are published to the subcontext defined by the JNDI prefix jndiPrefix attribute of the CORBASERVER, or to the Initial, or root, Context if no JNDI prefix value is given. The prefixPart value gives the level in the context hierarchy at which the error occurred. This problem may occur if CICS is unable to access the name server. It could also occur if some object, for example a bean, had been published previously with the same fully qualified name as that of the JNDI prefix, that is named jndiPrefix. It can occur if using a LDAP nameserver if the JNDI prefix is particularly long.

End of change
Start of change
System action:

No objects are published to JNDI.

End of change
Start of change
User response:

Check that the JNDI System properties for this PROGRAM are specified correctly and that the name server is active. If you need to change a System property, it is also necessary to reinstall the target CORBASERVER. If there is a naming conflict, either retract the previously published object or alter the JNDIPREFIX parameter of the CORBASERVER and reINSTALL it. If using a LDAP nameserver then CICS can encounter problems with very long JNDI prefixes being specified for CorbaServers since they can violate the schema in use on the LDAP server. If this message indicates a LDAP schema violation has occurred then it is advisable to shorten your JNDI prefix. Retry the PUBLISH operation.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.LogicalServerImplEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeserverName, End of changeStart of changejndiPrefix,End of changeStart of changeprefixPart, End of changeStart of changeexcEnd of change

Start of changeDFHII1017 EEnd of change
Start of changedate time applid Badly formed JNDI prefix: prefix in CORBASERVER serverName. The JNDI NameParser threw exception exc.End of change
Start of change
Explanation:

An exception exc was returned by the JNDI NameParser during validation of the JNDI prefix prefix. defined for CORBASERVER serverName. This operation is performed during a DJAR or CORBASERVER PUBLISH operation.

End of change
Start of change
System action:

No objects are published to JNDI.

End of change
Start of change
User response:

Correct the JNDI prefix defined for the target CORBASERVER, reinstall the CORBASERVER and reissue the PUBLISH command.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.LogicalServerImplEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeprefix, End of changeStart of changeserverName, End of changeStart of changeexcEnd of change

Start of changeDFHII1018 EEnd of change
Start of changedate time applid Failed to bind CORBA stateless GenericFactory for CORBASERVER serverName to JNDI subcontext jndiPrefix as jndiName. Exception exc was received.End of change
Start of change
Explanation:

An exception exc was returned by JNDI during a rebind of the CICS org.omg.CosLifeCycle GenericFactory implementation for CORBASERVER serverName to the JNDI subcontext at jndiPrefix.. This operation is performed during a CORBASERVER PUBLISH operation.

End of change
Start of change
System action:

The GenericFactory object is not published to JNDI.

End of change
Start of change
User response:

Ensure the JNDI name server is available to CICS, reinstall the CORBASERVER and reissue the PUBLISH command.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.cso.PublishLogicalServerCommandEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeserverName, End of changeStart of changejndiPrefix,End of changeStart of changejndiName, End of changeStart of changeexcEnd of change

Start of changeDFHII1019 IEnd of change
Start of changedate time applid CORBA stateless GenericFactory for CORBASERVER serverName bound to JNDI subcontext jndiPrefix as jndiName.End of change
Start of change
Explanation:

The CICS org.omg.CosLifeCycle GenericFactory implementation for CORBASERVER serverName was successfully rebound to the JNDI subcontext at jndiPrefix.. This operation is performed during a CORBASERVER PUBLISH operation.

End of change
Start of change
System action:

The CORBASERVER PUBLISH completes normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.cso.PublishLogicalServerCommandEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeserverName, End of changeStart of changejndiPrefix,End of changeStart of changejndiNameEnd of change

Start of changeDFHII1020 EEnd of change
Start of changedate time applid Failed to create HFS shelf shelfName for CORBASERVER serverName.End of change
Start of change
Explanation:

An attempt to create shelf shelfName for CORBASERVER serverName failed. This operation is performed during a CORBASERVER INSTALL operation.

End of change
Start of change
System action:

The CORBASERVER is not installed.

End of change
Start of change
User response:

Ensure CICS has the required HFS access, and that a directory of this name does not already exist, and reinstall the CORBASERVER.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.cso.AddLogicalServerCommandEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeshelfName, End of changeStart of changeserverNameEnd of change

Start of changeDFHII1021 EEnd of change
Start of changedate time applid Failed to unbind CORBA stateless GenericFactory for CORBASERVER serverName from JNDI subcontext jndiPrefix. Exception received exc.End of change
Start of change
Explanation:

An exception exc was returned by JNDI during an unbind of the CICS org.omg.CosLifeCycle GenericFactory implementation for CORBASERVER serverName from the JNDI subcontext at jndiPrefix.. This operation is performed during a CORBASERVER RETRACT operation.

End of change
Start of change
System action:

The GenericFactory object is not retracted from JNDI.

End of change
Start of change
User response:

Ensure the JNDI name server is available to CICS and that the CORBASERVER has not been retracted from another AOR.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.cso.RetractLogicalServerCommandEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeserverName, End of changeStart of changejndiPrefix,End of changeStart of changeexcEnd of change

Start of changeDFHII1022 IEnd of change
Start of changedate time applid CORBA stateless GenericFactory for CORBASERVER serverName unbound from JNDI subcontext jndiPrefix.End of change
Start of change
Explanation:

The CICS org.omg.CosLifeCycle GenericFactory implementation for CORBASERVER serverName was successfully unbound from the JNDI subcontext at jndiPrefix.. This operation is performed during a CORBASERVER RETRACT operation.

End of change
Start of change
System action:

The CORBASERVER RETRACT completes normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.cso.RetractLogicalServerCommandEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeserverName, End of changeStart of changejndiPrefixEnd of change

Start of changeDFHII1023 EEnd of change
Start of changedate time applid Failed to delete GenericFactory IOR file fileName from the shelf of CORBASERVER serverName.End of change
Start of change
Explanation:

The command processor for CORBA stateless objects was invoked during a CORBASERVER RETRACT operation to delete the GenericFactory IOR file. It was unable to delete the file, named fileName. This problem may occur if the CICS job has insufficient HFS access.

End of change
Start of change
System action:

The RETRACT continues normally.

End of change
Start of change
User response:

Ensure CICS has sufficient HFS access and reissue retract.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.cso.RetractLogicalServerCommandEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changefileName, End of changeStart of changeserverNameEnd of change

Start of changeDFHII1024 IEnd of change
Start of changedate time applid JNDI subcontext subcontext destroyed during processing of CORBASERVER serverName with prefix jndiPrefix.End of change
Start of change
Explanation:

During processing of CORBASERVER serverName, the subcontext components of the JNDI prefix prefixName were removed from the name server. This will occur during CORBASERVER RETRACT processing for those parts of the subcontext that are completely emptied by the RETRACT.

End of change
Start of change
System action:

Processing continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.LogicalServerImplEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changesubcontext, End of changeStart of changeserverName,End of changeStart of changejndiPrefixEnd of change

Start of changeDFHII1025 EEnd of change
Start of changedate time applid Failed to delete HFS shelf shelfName for CORBASERVER serverName.End of change
Start of change
Explanation:

An attempt to delete shelf shelfName for CORBASERVER serverName failed. The shelf is a directory on this region's HFS. This operation is performed during a CORBASERVER DISCARD operation.

End of change
Start of change
System action:

The CORBASERVER is discarded.

End of change
Start of change
User response:

If a directory of this name does not exist on HFS, this is probably due to a previous install failure and may be ignored. If a directory of this name does exist, check that CICS has the required HFS access and delete the directory manually; it will need to be removed before the CORBASERVER can be reinstalled.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.cso.DeleteLogicalServerCommandEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeshelfName, End of changeStart of changeserverNameEnd of change

Start of changeDFHII1026 EEnd of change
Start of changedate time applid CORBASERVER serverName not installed.End of change
Start of change
Explanation:

A definition for CORBASERVER serverName could not be found in this CICS region. This condition can occur if an Enterprise Bean or IIOP method request is received before the CORBASERVER to which the target object relates is installed. Another possible reason for the condition is that the referenced CORBASERVER is no longer valid and an old object reference is being used by the client.

End of change
Start of change
System action:

The request is rejected with a CORBA exception.

End of change
Start of change
User response:

Install the CORBASERVER or update the object reference (IOR) and retry the request.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.RequestProcessorEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeserverNameEnd of change

Start of changeDFHII1027 IEnd of change
Start of changedate time applid CORBA stateless GenericFactory for CORBASERVER serverName written to the shelf as fileName.End of change
Start of change
Explanation:

The command processor for CORBA stateless objects was invoked during a CORBA server PUBLISH operation to make the GenericFactory IOR file available. The file was written to the HFS shelf of CORBASERVER serverName as file fileName.

End of change
Start of change
System action:

The PUBLISH operation continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.cso.PublishLogicalServerCommandEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeserverName, End of changeStart of changefileNameEnd of change

Start of changeDFHII1028 WEnd of change
Start of changedate time applid Name server not defined for CORBASERVER serverName being initialized for PROGRAM pgmName.End of change
Start of change
Explanation:

No name service system properties are defined for PROGRAM pgmName.

End of change
Start of change
System action:

The ORB configured for CORBASERVER serverName in this JVM will not be able to access JNDI. JNDI requests from objects in CORBASERVER serverName will fail if they are issued from a program using, or reusing, this JVM.

End of change
Start of change
User response:

If objects in this CORBASERVER need to use JNDI, define the name service in the com.ibm.cics.ejs.nameserver property, or set the com.ibm.CORBA.InitialReferencesURL property, in the system properties file available to PROGRAM pgmName. The system properties file is defined in the JVMPROPS parameter of the PROGRAM's JVMPROFILE. The CORBASERVER should then be DISCARDed and reINSTALLed.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.orb.ORBFactoryEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeserverName, End of changeStart of changepgmNameEnd of change

Start of changeDFHII1029 IEnd of change
Start of changedate time applid CORBA stateless GenericFactory file fileName deleted from the shelf of CORBASERVER serverName.End of change
Start of change
Explanation:

The command processor for CORBA stateless objects was invoked during a CORBA server RETRACT operation to delete the GenericFactory IOR file. File fileName was deleted from the HFS shelf of CORBASERVER serverName.

End of change
Start of change
System action:

The RETRACT operation continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.cso.RetractLogicalServerCommandEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changefileName, End of changeStart of changeserverNameEnd of change

Start of changeDFHII1030 WEnd of change
Start of changedate time applid CORBA stateless GenericFactory for CORBASERVER serverName not found at JNDI subcontext jndiPrefix.End of change
Start of change
Explanation:

During CORBASERVER RETRACT, an attempt is made to unbind the CICS org.omg.CosLifeCycle GenericFactory implementation from the name server. When this was attempted during RETRACT of CORBASERVER serverName, the GenericFactory was not found at JNDI subcontext jndiPrefix. It is likely that the CORBASERVER has been RETRACTed from another CICS region, or the name server has been cleared, since the last CORBASERVER PUBLISH.

End of change
Start of change
System action:

The CORBASERVER RETRACT completes normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.cso.RetractLogicalServerCommandEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeserverName, End of changeStart of changejndiPrefixEnd of change

Start of changeDFHII1031 EEnd of change
Start of changedate time applid Unable to obtain JNDI InitialContext jndiPrefix for CORBASERVER serverName.End of change
Start of change
Explanation:

CICS failed to obtain the JNDI InitialContext for CORBASERVER serverName whose jndiPrefix is defined as jndiPrefix. This can occur if the name server is unavailable or incorrectly configured.

End of change
Start of change
System action:

The JNDI operation fails.

End of change
Start of change
User response:

Ensure the name server is available to CICS and correctly configured. Attempt the operation again.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.LogicalServerImplEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changejndiPrefix, End of changeStart of changeserverNameEnd of change

Start of changeDFHII1032 IEnd of change
Start of changedate time applid JNDI subcontext subContext created during processing of CORBASERVER serverName .End of change
Start of change
Explanation:

During processing of CORBASERVER serverName, the sub context subcontext was created on the name server. This will occur during CORBASERVER PUBLISH processing for any parts of the subcontext that did not previously exist.

End of change
Start of change
System action:

Processing continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.LogicalServerImplEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changesubContext, End of changeStart of changeserverNameEnd of change

Start of changeDFHII1033 IEnd of change
Start of changedate time applid JNDI subcontext subContext for CORBASERVER serverName not found during RETRACT.End of change
Start of change
Explanation:

JNDI sub context subContext, defined for CORBASERVER serverName, was not found on the name server during a RETRACT operation. Since the subcontext does not exist, there is nothing to retract for this CORBASERVER, so no further JNDI processing is required.

End of change
Start of change
System action:

IILS RETRACT processing continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.cso.RetractLogicalServerCommandEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changesubContext, End of changeStart of changeserverNameEnd of change

Start of changeDFHII1034 EEnd of change
Start of changedate time applid No write access to file fileName for creation of shelf shelfName.End of change
Start of change
Explanation:

An attempt to create shelf shelfName failed because CICS is unable to modify file fileName. This operation is performed during a CORBASERVER INSTALL operation.

End of change
Start of change
System action:

Message DFHII1020 is also issued. The CORBASERVER is not installed.

End of change
Start of change
User response:

Ensure CICS has the required HFS access, and reinstall the CORBASERVER.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.cso.AddLogicalServerCommandEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changefileName, End of changeStart of changeshelfNameEnd of change

Start of changeDFHII1035 WEnd of change
Start of changedate time applid GenericFactory IOR file fileName not found on the shelf of CORBASERVER serverName.End of change
Start of change
Explanation:

The command processor for CORBA stateless objects was invoked during a CORBASERVER RETRACT operation to delete the GenericFactory IOR file. The file, named fileName. did not exist. This is probably because the CORBASERVER was not PUBLISHed from this CICS region, or had already been RETRACTed.

End of change
Start of change
System action:

The RETRACT continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.cso.RetractLogicalServerCommandEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changefileName, End of changeStart of changeserverNameEnd of change

Start of changeDFHII1036 WEnd of change
Start of changedate time applid Unexpected ORB creation within the scope of CORBASERVER serverName for PROGRAM pgmName.End of change
Start of change
Explanation:

A second or subsequent ORB is being created within a CORBASERVER environment. ORB initialization has detected that CORBASERVER serverName is currently active and, therefore, that ORB initialization is unexpected. This can occur if an application object issues ORB.init, either explicitly, or implicitly from, for example, a non-CICS JNDI initial context factory. This warning message is issued because the ORB being created will be limited to the functionality available to a CICS Java application ORB, for example:

End of change
Start of change
System action:

ORB initialization continues.

End of change
Start of change
User response:

If this situation has occurred inadvertently, through usage of the incorrect naming context factory, check that the javax.naming.Context.INITIAL_CONTEXT_FACTORY Property, java.naming.factory.initial, has not been overridden. It should be allowed to default to com.ibm.ejs.ns.jndi.CNInitialContextFactory. This property can be set as a system property by an authorized application, or in the system properties file available to PROGRAM pgmName. The system properties file is defined in the JVMPROPS parameter of the PROGRAM's JVMPROFILE. The Property can also be passed as a parameter to the InitialContext constructor.

If this situation has occurred inadvertently, through explicit usage of ORB.init, it would normally be preferable for an application to gain access to the ORB that has already been created for the CORBASERVER. CORBA objects can obtain such a reference using the org.omg.CORBA.portable.ObjectImpl _orb() method.

EJB objects can obtain a reference to the current ORB by issuing a JNDI lookup of 'java

String ORBStr = "java org.omg.CORBA.ORB curORB = (org.omg.CORBA.ORB) initCtx.lookup(ORBStr);

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.orb.ORBEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeserverName, End of changeStart of changepgmNameEnd of change

Start of changeDFHII1037 EEnd of change
Start of changedate time applid CORBASERVER serverName has received a request with AUTHTYPE authType. The attrName attribute in the request has a value of (value1) which does not match the value (value2) configured for the CORBASERVER.End of change
Start of change
Explanation:

A request has been received for a connection to CORBASERVER serverName with AUTHTYPE authType. However, there is a mismatch between one of the attributes in the request and the corresponding attribute of the configured CORBASERVER or TCPIPSERVICE. The attribute will be one of:-

  1. TCPIPSERVICE name.
  2. Port number.
  3. SSL type.
End of change
Start of change
System action:

An II domain exception trace entry is made, a com.ibm.cics.iiop.RequestProcessorRuntimeException is thrown and the RequestProcessor terminates abnormally.

End of change
Start of change
User response:

Ensure that the attributes of the TCPIP services in the AOR region match those of the Listener region. If any attributes have changed, reinstall the changed definitions and republish the relevant DJAR/CORBASERVER to ensure that the IORs in use match the currently active CORBASERVER and TCPIPSERVICE definitions.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.LogicalServerImplEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeserverName, End of changeStart of changeauthType,End of changeStart of changeattrName, End of changeStart of changevalue1, End of changeStart of changevalue2End of change

Start of changeDFHII1038 EEnd of change
Start of changedate time applid CORBASERVER serverName does not have a TCPIPSERVICE configured for AUTHTYPE authType.End of change
Start of change
Explanation:

A CICSConnectionContext has been received which contains an authentication type for which no TCPIPSERVICE is configured for this CORBASERVER. The data in a CICSConnectionContext is derived from the TCPIPSERVICE in the listener region, by the RequestReceiver.

End of change
Start of change
System action:

An II domain exception trace entry is made, a com.ibm.cics.iiop.RequestProcessorRuntimeException is thrown and the RequestProcessor terminates abnormally.

End of change
Start of change
User response:

Ensure that a TCPIPSERVICE is configured for the appropriate authentication type. Ensure that the attributes of the TCPIP services in the AOR region match those of the Listener region. If any attributes have changed, republish the relevant DJAR/CORBASERVER to ensure that the IORs in use match the currently active CORBASERVER and TCPIPSERVICE definitions.

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.LogicalServerImplEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeserverName, End of changeStart of changeauthTypeEnd of change

Start of changeDFHII1050 WEnd of change
Start of changedate time applid Maximum version of GIOP has not been specified. Defaulting to GIOP 1.1 .End of change
Start of change
Explanation:

The maximum version of the General Inter-ORB Protocol (GIOP) has not been configured or is invalid.

The maximum GIOP version is included in all CORBA object references exported by CICS. You can use the CICS Resource Manager for Enterprise Beans (RMEB) to discover which version of GIOP your published enterprise beans currently advertise.

CICS can support up to GIOP version 1.2 . GIOP support in CICS TS 2.2 was limited to a maximum of GIOP version 1.1 . If you have a distributed CorbaServer which contains both CICS TS 2.2 and newer CICS regions, it is important that the newer CICS regions do not advertise support for anything beyond GIOP 1.1 .

You can set the maximum version of GIOP that CICS will use by setting the following environment variable in the CICS JVM properties file: com.ibm.cics.iiop.MaxGIOPMinorVersion=<n> where <n> is either 1 or 2 representing GIOP 1.1 or GIOP 1.2 .

It is recommended that all regions be set to use GIOP 1.2 . GIOP 1.1 should only be set as the maximum supported version of GIOP if the CICS region is participating in a CorbaServer which includes CICS TS 2.2 regions.

End of change
Start of change
System action:

CICS defaults to compatibility mode for CORBA requests; the maximum version of GIOP advertised in published object references is GIOP 1.1 .

End of change
Start of change
User response:

You can suppress this message by telling CICS the maximum GIOP version to use via the MaxGIOPMinorVersion property (see above).

End of change
Start of change
Destination:

CIIL

End of change
Modules:

Start of changecom.ibm.cics.iiop.LogicalServerImplEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

[[ Contents Previous Page | Next Page Index ]]