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).
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.
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.
Console
DFHIICP, DFHIIDM, DFHIIMM, DFHIIRH, DFHIIRP, DFHIIRQ, DFHIIRR,
DFHIIXM
XMEOUT Parameters:
applid,
aaa/bbbb,
X'
offset',
modname
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.
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.
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.
Console
DFHIICP, DFHIIDM, DFHIIMM, DFHIIRH, DFHIIRP, DFHIIRQ, DFHIIRR
DFHIIXM
XMEOUT Parameters:
applid,
X'
code',
modname
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.
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.
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.
Console
DFHIICP, DFHIIDM, DFHIIMM, DFHIIRH, DFHIIRP, DFHIIRQ, DFHIIRR
DFHIIXM
XMEOUT Parameters:
applid,
X'offset',
modname
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.
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.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice,
urmname
The IIOP Request Receiver received a GIOP header which contains an invalid object key.
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.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
The IIOP Request Receiver received a GIOP request but is unable to send the request to the ORB via a Request Stream.
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.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
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.
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.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
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:
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.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
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.
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.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice,
urmname,
userid
The IIOP Request Receiver received a GIOP request; however, the attempt to find a Request Stream failed.
Outstanding replies are processed. A systemException of COMM_FAILURE is sent to the client. The socket is closed and the transaction is terminated.
Use trace and the previous DFHII0002 message to determine why program DFHIIRH failed to find a Request Stream.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
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.
Exception trace point 012D is issued. A systemException of COMM_FAILURE or INTERNAL is sent to the client. The Request Receiver attempts to continue.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice,
req_id
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.
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.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice,
req_id,
{1=Request Processor ABEND.,
2=Request Stream closed.,
3=Timeout.,
4=Undefined.}
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.
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.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
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:
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.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice,
X'
pointId
'
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.
Exception trace point 012E is issued.
Check the definitions in the TCPIP service and the specified transaction.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice,
transaction
The IIOP Request Receiver received a GIOP header with the magic field (first 4 bytes) not equal to 'GIOP'.
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.
Determine why the GIOP header was sent with an incorrect magic field.
Data 2 in the exception trace point entry contains the GIOP header.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
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.
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.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice,
sup_version,
rec_version
The IIOP Request Receiver received a messageType of fragment; however, the 'more fragments' flag was not set in the previous message.
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.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
The IIOP Request Receiver received a messageType of messageError.
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.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
The IIOP Request Receiver received a messageType of reply or locateReply which is not supported by this Request Receiver.
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.
Determine why the client sent a reply.
Data 2 in the exception trace point entry contains the GIOP Header.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
The IIOP Request Receiver received a messageType of closeConnection which is not supported by this Request Receiver.
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.
Determine why the client sent a closeConnection.
Data 2 in the exception trace point entry contains the GIOP Header.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
The IIOP Request Receiver received a GIOP header with an invalid message type.
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.
Determine why the client sent GIOP header with an unknown messageType.
Data 2 in the exception trace point entry contains the GIOP Header.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
The IIOP Request Receiver received a GIOP request header which it is unable to parse correctly.
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.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
The IIOP Request Receiver attempted to invoke the security URM module but failed with a code supplied as reason.
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.
Possible causes of the problem and an indication of how to solve them are given in the following list of reason code meanings:
CIIL
DFHIIRH
XMEOUT Parameters:
date,
time,
applid,
module,
X'
reason
'
The IIOP Request Receiver issued a socket receive request which timed out. There are replies replies outstanding. There are fragments fragments in progress.
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.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice,
replies,
fragments
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.
Exception trace point 0139 is issued.
Determine why the task no longer exists. It may have been purged or may not have expected a reply and so terminated.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
X'
req_id
'
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.
Exception trace point 0138 is issued.
Determine why the resume failed.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
X'
req_id
'
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.
Exception trace point 0137 is issued.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
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.
Exception trace point 013B is issued. The socket is closed and the request receiver is terminated.
Determine why an IO error occurred on this port.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
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.
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.
Determine why the GIOP header was sent with an incorrect length field.
Data 2 in the exception trace point entry contains the GIOP header.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
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.
Exception trace point 0144 is issued. A messageError is sent to the client. The socket is closed and the transaction terminated.
Determine which client is sending in a connection request to a TCPIP service defined with protocol IIOP, without also sending in the request.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
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.
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.
Determine the remote system name from the tranid definition. Ensure that IRC is open and the IRC connection named is in service.
CIIL
DFHIIRH
XMEOUT Parameters:
date,
time,
applid,
tranid
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.
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.
Either install the relevant MRO connection or change the REMOTESYSTEM for transaction tranid to the required MRO connection that is installed.
CIIL
DFHIIRH
XMEOUT Parameters:
date,
time,
applid,
tranid
The IIOP Request Receiver attempted to receive a request from a socket, but the socket domain found an error.
Exception trace point 010A is issued.
Check for an earlier DFHSO message which describes the cause of this failure.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
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.
Exception trace point 0149 is issued.
Find why the client is sending fragments.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
The IIOP Request Receiver attempted to obtain storage from the storage manager domain.
Exception trace point 0130 is issued.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
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.
Exception trace point 0150 is issued.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
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.
Exception trace point 0151 is issued.
Determine whether the authentication parameter specified in the TCPIPSERVICE is wrong or whether the client sent a request with an invalid security context.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice,
{1=none,
2=basic,
3=asserted,
4=unused,
5=certificate}
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.
Exception trace point 010E is issued.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
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.
Exception trace point 014A is issued. Outstanding replies are processed, but not sent on to the client. The transaction is terminated.
Determine why the client closed the socket when there were still replies or fragments in progress.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice,
replies,
fragments
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.
Exception trace point 014B is issued. The transaction is terminated.
Determine why the client closed the socket before sending a closeConnection request.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
The IIOP Request Receiver received a fragment. However no GIOP request or locateRequest has been received for the fragment with the requestId requestId specified.
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.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice,
requestId
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.
Exception trace point 070F is issued.
Determine why the task no longer exists. The task may have been purged or may not have expected a reply and so terminated.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
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.
Exception trace point 0710 is issued.
Determine why the resume failed. The task may have been purged.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
The IIOP Request Processor issued a Request Stream receive request to receive a request from the Request Receiver but the receive failed.
Exception trace point 0709 is issued. See the system action for the DFHII1nnn message that is issued after this message.
Use trace to determine why the RZTA RECEIVE_REQUEST failed. Look for earlier Request Stream(RZ) trace and messages.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
The IIOP Request Processor attempted to receive a reply from a target ORB but the receive failed.
Exception trace point 070B is issued. See the system action for the DFHII1nnn message that is issued after this message.
Use trace to determine why the receive reply failed.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
The IIOP Request Processor issued a Request Stream send reply to send a reply to the Request Receiver but the send failed.
Exception trace point 070A is issued. See the system action for the DFHII1nnn message that is issued after this message.
Use trace to determine why the RZTA SEND_REPLY failed. Look for earlier Request Stream (RZ) trace and messages.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
The IIOP Request Processor attempted to send a request to a target ORB but the send failed.
Exception trace point 070C is issued. See the system action for the DFHII1nnn message that is issued after this message.
Use trace to determine why the send request failed. Look for earlier Request Stream (RZ) trace and messages.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
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.
Exception trace point 070D is issued. See the system action for the DFHII1nnn message that is issued after this message.
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.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
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.
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.
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.
CIIL
DFHIIRH
XMEOUT Parameters:
date,
time,
applid,
tranid
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.
Exception trace point 0719 is issued. See the system action for the DFHII1nnn message that is issued after this message.
Use trace to determine why a valid GIOP header was not received.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
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.
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.
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.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
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.
Exception trace point 071B is issued. See the system action for the DFHII1nnn message that is issued after this message.
Use trace to determine why a valid GIOP header was not received.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
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.
Exception trace point 071C is issued. See the system action for the DFHII1nnn message that is issued after this message.
Use trace to determine why a valid GIOP fragment header was not received.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
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.
Exception trace point 071D is issued. See the system action for the DFHII1nnn message that is issued after this message.
Use trace to determine why a valid GIOP fragment was not received.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
The IIOP Request Processor attempted to receive a reply from a target ORB but the data received had a GIOPMessageTYpe of GIOPMessageError.
Exception trace point 0720 is issued. See the system action for the DFHII1nnn message that is issued after this message.
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.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
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.
Exception trace point 0721 is issued. See the system action for the DFHII1nnn message that is issued after this message.
Use trace to determine why the target ORB sent an invalid GIOPMessageType.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
The IIOP Request Processor attempted to receive a reply from a target ORB but the data received had an unknown GIOPMessageType.
Exception trace point 0722 is issued. See the system action for the DFHII1nnn message that is issued after this message.
Use trace to determine why the target ORB sent an unknown GIOPMessageType.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
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.
Exception trace point 0723 is issued. See the system action for the DFHII1nnn message that is issued after this message.
Use trace to determine why the target ORB sent a GIOPFragment without sending an earlier message indicating that a fragment is to follow.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
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.
Exception trace point 070E is issued. See the system action for the DFHII1nnn message that is issued after this message.
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.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid,
{1=reply from a target ORB,
2=request from the Request Receiver},
{1=ABEND.,
2=Request Stream closed.,
3=Timeout.}
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.
See the system action for the DFHII1nnn message that is issued after this message.
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.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
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.
Exception trace point 0727 is issued.
Find why the target ORB is sending fragments.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
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.
Exception trace point 0728 is issued. See the system action for the DFHII1nnn message that is issued after this message.
Use trace to determine why the requestId changed. Each fragment within a reply should contain the same requestId.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
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.
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.
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.
CIIL
DFHIIRR
XMEOUT Parameters:
date,
time,
applid,
client_ip_addr,
tcpipservice
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.
Exception trace point 071E is issued. See the system action for the DFHII1nnn message that is issued after this message.
Use trace to determine why the client ORB sent a fragment with an invalid length.
CIIL
DFHIIRP
XMEOUT Parameters:
date,
time,
applid
The CICS ORB attempted to instantiate the requested plugin class plugin but the ORB could not find this class on the current classpath.
The plugin is not loaded.
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.
CIIL
com.ibm.cics.iiop.DebugRequestInterceptor
XMEOUT Parameters:
date,
time,
applid,
plugin
The CICS ORB caught an exception thrown from plugin plugin.
The ORB attempts to continue processing the user application.
Either contact the plugin vendor for further assistance or catch the exception in the body of your plugin.
CIIL
com.ibm.cics.iiop.DebugRequestInterceptor
XMEOUT Parameters:
date,
time,
applid,
plugin,
exception
This is an audit log message indicating that REQUESTMODEL rqmodelname has been added to the system using the INSTALL command.
The system continues normally.
None.
CIIL
DFHIIMM
XMEOUT Parameters:
date,
time,
applid,
rqmodelname
This is an audit log message indicating that REQUESTMODEL rqmodelname has been removed from the system using the DISCARD command.
The system continues normally.
None.
CIIL
DFHIIMM
XMEOUT Parameters:
date,
time,
applid,
rqmodelname
DFHIICP has been called to link to program DFJIIRP however the link failed.
The system continues normally.
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.
CIIL
DFHIICP
XMEOUT Parameters:
date,
time,
applid
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.
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.
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.
CIIL
DFHIIRS
XMEOUT Parameters:
date,
time,
applid,
{1=the userid is too long,
2=the password is too long,
3=of an invalid msgType,
4=the sessionId already exists,
5=the sessionId is not found,
6=of a malformed context,
7=unused,
8=the version is invalid}
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.
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.
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.
CIIL
DFHIIRS
XMEOUT Parameters:
date,
time,
applid,
{1=the ESM inactive,
2=CICS security is inactive,
3=of an unknown ESM error,
4=the command is not authorised,
5=the password is not authorised,
6=the userid is undefined,
7=the password has expired,
8=the userid has been revoked,
9=of a userid format error,
10=the applid is not authorised,
11=of an unexpected return code}
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.
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.
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.
CIIL
DFHIIRS
XMEOUT Parameters:
date,
time,
applid,
{1=of an invalid msgType,
2=the userid is too long,
3=of an invalid credType,
4=it contains an invalid length,
5=the version is invalid}
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.
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.
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.
CIIL
DFHIIRS
XMEOUT Parameters:
date,
time,
applid,
{1=CICS security is inactive,
2=the userid is undefined,
3=the userid is not determined,
4=the ESM is inactive,
5=the ESM is not present,
6=the command is not authorised,
7=the XSRC resource is not found,
8=the XSRC class is not found,
9=the XSRC resource name is invalid,
10=the USAD reason is not expected,
11=the XSRC reason is not expected}
An internal logic error desc was detected in method methodName of class className of the IIOP RequestProcessor.
An II domain exception trace entry is made and a system dump requested. The RequestProcessor terminates abnormally.
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.
CIIL
com.ibm.cics.iiop.RequestProcessor
XMEOUT Parameters:
date,
time,
applid,
className,
methodName,
desc
A severe error, identified by the string desc, was detected by the IIOP RequestProcessor. This is usually related to a Java Throwable, th.
An II domain exception trace entry is made and a system dump requested. The RequestProcessor terminates abnormally.
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.
CIIL
com.ibm.cics.iiop.RequestProcessor
XMEOUT Parameters:
date,
time,
applid,
desc,
th
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.
An II domain exception trace is issued and RequestProcessor initialization is terminated.
Ensure that a CORBASERVER definition for LogicalServer serverName is available in the CICS region.
CIIL
com.ibm.cics.iiop.LogicalServerImpl
XMEOUT Parameters:
date,
time,
applid,
e,
serverName
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.
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.
Use the message and/or trace to determine the class in error and ensure that it is available to the RequestProcessor on the TMCLASSPATH.
CIIL
com.ibm.cics.iiop.LogicalServerPluginRegistry
XMEOUT Parameters:
date,
time,
applid,
e,
className
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:-
An II domain exception trace is issued and a CosLifeCycle::NoFactory exception is returned to the caller.
Correct the CLASSPATH and/or class implementation as necessary and/or inspect the exception data recorded in the trace dataset.
CIIL
com.ibm.cics.iiop.cso._GenericFactoryImpl
XMEOUT Parameters:
date,
time,
applid,
e,
javaClassName,
interfaceName
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.
An II domain exception trace is issued and a CORBA::OBJECT_NOT_EXIST exception is returned to the caller.
Correct the CLASSPATH if necessary and/or inspect the exception data recorded in the trace dataset.
CIIL
com.ibm.cics.iiop.cso.CorbaStatelessManager
XMEOUT Parameters:
date,
time,
applid,
e,
className
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.
An IILS_EXCEPTION with reason IILS_SHELF_ACCESS_ERROR is returned to the caller.
Correct the HFS access available to the CICS job and reissue publish.
CIIL
com.ibm.cics.iiop.cso.PublishLogicalServerCommand
XMEOUT Parameters:
date,
time,
applid,
e,
fileName
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.
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.
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.
CIIL
com.ibm.cics.iiop.oa.RootOAImpl
XMEOUT Parameters:
date,
time,
applid,
oa
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.
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.
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.
CIIL
com.ibm.cics.iiop.oa.RootOAImpl
XMEOUT Parameters:
date,
time,
applid,
e
An unexpected failure dr occurred issuing an IIRP invoke request on an outbound RequestStream.
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.
Use trace and dump to determine the cause of the failure. If the problem persists you may need to contact your IBM support representative.
CIIL
com.ibm.cics.iiop.orb.CICSSourceOutputStream
XMEOUT Parameters:
date,
time,
applid,
dr
An unexpected failure dr occurred receiving a request from the RequestStream of which this RequestProcessor is the target.
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.
Use trace and dump to determine the cause of the failure. If the problem persists you may need to contact your IBM support representative.
CIIL
com.ibm.cics.iiop.orb.CICSTargetInputStream
XMEOUT Parameters:
date,
time,
applid,
dr
An unexpected failure dr occurred sending a reply to the RequestStream of which this RequestProcessor is the target.
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.
Use trace and dump to determine the cause of the failure. If the problem persists you may need to contact your IBM support representative.
CIIL
com.ibm.cics.iiop.orb.CICSTargetOutputStream
XMEOUT Parameters:
date,
time,
applid,
dr
An unexpected failure dr occurred receiving a reply from an outbound RequestStream.
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.
Use trace and dump to determine the cause of the failure. If the problem persists you may need to contact your IBM support representative.
CIIL
com.ibm.cics.iiop.orb.CICSSourceInputStream
XMEOUT Parameters:
date,
time,
applid,
dr
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.
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.
Use trace and dump to determine the cause of the failure. If the problem persists you may need to contact your IBM support representative.
CIIL
com.ibm.cics.iiop.orb.CICSConnection
XMEOUT Parameters:
date,
time,
applid,
dr,
host,
port
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.
An II domain exception trace entry is made, a com.ibm.cics.iiop.RequestProcessorRuntimeException is thrown and the RequestProcessor terminates abnormally.
Ensure that the IORs in use match the currently active CORBASERVER definitions.
CIIL
com.ibm.cics.iiop.LogicalServerImpl
XMEOUT Parameters:
date,
time,
applid,
connSsl,
serverName,
serverSsl
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.
An II domain exception trace entry is made, a com.ibm.cics.iiop.RequestProcessorRuntimeException is thrown and the RequestProcessor terminates abnormally.
Ensure that the IORs in use match the currently active CORBASERVER definitions.
CIIL
com.ibm.cics.iiop.LogicalServerImpl
XMEOUT Parameters:
date,
time,
applid,
connPort,
sslType,
serverName,
port,
sslPort
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.
No objects are published to JNDI.
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.
CIIL
com.ibm.cics.iiop.LogicalServerImpl
XMEOUT Parameters:
date,
time,
applid,
serverName,
jndiPrefix,
prefixPart,
exc
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.
No objects are published to JNDI.
Correct the JNDI prefix defined for the target CORBASERVER, reinstall the CORBASERVER and reissue the PUBLISH command.
CIIL
com.ibm.cics.iiop.LogicalServerImpl
XMEOUT Parameters:
date,
time,
applid,
prefix,
serverName,
exc
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.
The GenericFactory object is not published to JNDI.
Ensure the JNDI name server is available to CICS, reinstall the CORBASERVER and reissue the PUBLISH command.
CIIL
com.ibm.cics.iiop.cso.PublishLogicalServerCommand
XMEOUT Parameters:
date,
time,
applid,
serverName,
jndiPrefix,
jndiName,
exc
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.
The CORBASERVER PUBLISH completes normally.
None.
CIIL
com.ibm.cics.iiop.cso.PublishLogicalServerCommand
XMEOUT Parameters:
date,
time,
applid,
serverName,
jndiPrefix,
jndiName
An attempt to create shelf shelfName for CORBASERVER serverName failed. This operation is performed during a CORBASERVER INSTALL operation.
The CORBASERVER is not installed.
Ensure CICS has the required HFS access, and that a directory of this name does not already exist, and reinstall the CORBASERVER.
CIIL
com.ibm.cics.iiop.cso.AddLogicalServerCommand
XMEOUT Parameters:
date,
time,
applid,
shelfName,
serverName
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.
The GenericFactory object is not retracted from JNDI.
Ensure the JNDI name server is available to CICS and that the CORBASERVER has not been retracted from another AOR.
CIIL
com.ibm.cics.iiop.cso.RetractLogicalServerCommand
XMEOUT Parameters:
date,
time,
applid,
serverName,
jndiPrefix,
exc
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.
The CORBASERVER RETRACT completes normally.
None.
CIIL
com.ibm.cics.iiop.cso.RetractLogicalServerCommand
XMEOUT Parameters:
date,
time,
applid,
serverName,
jndiPrefix
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.
The RETRACT continues normally.
Ensure CICS has sufficient HFS access and reissue retract.
CIIL
com.ibm.cics.iiop.cso.RetractLogicalServerCommand
XMEOUT Parameters:
date,
time,
applid,
fileName,
serverName
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.
Processing continues.
None.
CIIL
com.ibm.cics.iiop.LogicalServerImpl
XMEOUT Parameters:
date,
time,
applid,
subcontext,
serverName,
jndiPrefix
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.
The CORBASERVER is discarded.
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.
CIIL
com.ibm.cics.iiop.cso.DeleteLogicalServerCommand
XMEOUT Parameters:
date,
time,
applid,
shelfName,
serverName
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.
The request is rejected with a CORBA exception.
Install the CORBASERVER or update the object reference (IOR) and retry the request.
CIIL
com.ibm.cics.iiop.RequestProcessor
XMEOUT Parameters:
date,
time,
applid,
serverName
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.
The PUBLISH operation continues.
None.
CIIL
com.ibm.cics.iiop.cso.PublishLogicalServerCommand
XMEOUT Parameters:
date,
time,
applid,
serverName,
fileName
No name service system properties are defined for PROGRAM pgmName.
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.
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.
CIIL
com.ibm.cics.iiop.orb.ORBFactory
XMEOUT Parameters:
date,
time,
applid,
serverName,
pgmName
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.
The RETRACT operation continues.
None.
CIIL
com.ibm.cics.iiop.cso.RetractLogicalServerCommand
XMEOUT Parameters:
date,
time,
applid,
fileName,
serverName
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.
The CORBASERVER RETRACT completes normally.
None.
CIIL
com.ibm.cics.iiop.cso.RetractLogicalServerCommand
XMEOUT Parameters:
date,
time,
applid,
serverName,
jndiPrefix
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.
The JNDI operation fails.
Ensure the name server is available to CICS and correctly configured. Attempt the operation again.
CIIL
com.ibm.cics.iiop.LogicalServerImpl
XMEOUT Parameters:
date,
time,
applid,
jndiPrefix,
serverName
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.
Processing continues.
None.
CIIL
com.ibm.cics.iiop.LogicalServerImpl
XMEOUT Parameters:
date,
time,
applid,
subContext,
serverName
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.
IILS RETRACT processing continues.
None.
CIIL
com.ibm.cics.iiop.cso.RetractLogicalServerCommand
XMEOUT Parameters:
date,
time,
applid,
subContext,
serverName
An attempt to create shelf shelfName failed because CICS is unable to modify file fileName. This operation is performed during a CORBASERVER INSTALL operation.
Message DFHII1020 is also issued. The CORBASERVER is not installed.
Ensure CICS has the required HFS access, and reinstall the CORBASERVER.
CIIL
com.ibm.cics.iiop.cso.AddLogicalServerCommand
XMEOUT Parameters:
date,
time,
applid,
fileName,
shelfName
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.
The RETRACT continues normally.
None.
CIIL
com.ibm.cics.iiop.cso.RetractLogicalServerCommand
XMEOUT Parameters:
date,
time,
applid,
fileName,
serverName
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:
ORB initialization continues.
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);
CIIL
com.ibm.cics.iiop.orb.ORB
XMEOUT Parameters:
date,
time,
applid,
serverName,
pgmName
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:-
An II domain exception trace entry is made, a com.ibm.cics.iiop.RequestProcessorRuntimeException is thrown and the RequestProcessor terminates abnormally.
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.
CIIL
com.ibm.cics.iiop.LogicalServerImpl
XMEOUT Parameters:
date,
time,
applid,
serverName,
authType,
attrName,
value1,
value2
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.
An II domain exception trace entry is made, a com.ibm.cics.iiop.RequestProcessorRuntimeException is thrown and the RequestProcessor terminates abnormally.
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.
CIIL
com.ibm.cics.iiop.LogicalServerImpl
XMEOUT Parameters:
date,
time,
applid,
serverName,
authType
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.
CICS defaults to compatibility mode for CORBA requests; the maximum version of GIOP advertised in published object references is GIOP 1.1 .
You can suppress this message by telling CICS the maximum GIOP version to use via the MaxGIOPMinorVersion property (see above).
CIIL
com.ibm.cics.iiop.LogicalServerImpl
XMEOUT Parameters:
date,
time,
applid