DFHIRxxxx messages

DFHIR2122
date time applid Intersystem session recovery. Database changes found to be synchronized. Original failure details: Time=time. Remote system=sysid. Intersystem terminal=termid. Transaction=tranid. Task number=taskno. Operator terminal=termid. Operator=operid. Unit of work ID=uowid
Explanation:

An error occurred on an intersystem session recovery which has now been successfully recovered and resynchronized. This message is normally issued as a follow-up to message DFHRM0107, (which may have been issued at the time of the failure if the session failed at a critical time during syncpoint processing).

System action:

Processing continues.

User response:

None.

Destination:

CSMT

Modules:

DFHCRR

XMEOUT Parameters: date, time,applid, time, sysid, termid, tranid, taskno, termid,operid, uowid

DFHIR2123
date time applid Intersystem session recovery. Data base changes found to be out of sync. Original failure details: Time=time. Remote system=sysid. Intersystem terminal=termid. Transaction=tranid. Task number=taskno. Operator terminal=termid. Operator=operid. Unit of work ID=uowid
Explanation:

This message is issued as a follow-up to message DFHRM0107. The original failure information provides a cross-reference.

System action:

Processing continues.

User response:

Take user-defined action to resynchronize the local and remote databases.

Destination:

CSMT

Modules:

DFHCRR

XMEOUT Parameters: date, time,applid, time, sysid, termid, tranid, taskno, termid,operid, uowid

DFHIR2124
date time applid Intersystem session recovery. Error when data base changes may be out of sync. Original failure details: Time=time. Remote system=sysid. Intersystem terminal=termid. Transaction=tranid. Task number=taskno. Operator terminal=termid. Operator=operid. Unit of work ID=uowid
Explanation:

This message is issued as a follow-up to message DFHRM0107. During session recovery, the system was unable to determine whether database changes were out of synchronization.

System action:

Processing continues.

User response:

Make the necessary database enquiries to detect whether changes are synchronized. If they are not, take user-defined action to resynchronize the databases.

Destination:

CSMT

Modules:

DFHCRR

XMEOUT Parameters: date, time,applid, time, sysid, termid, tranid, taskno, termid,operid, uowid

DFHIR2321
applid MRO/IRC Communication being Terminated. Session(s) with the following Netname(s) are still Active:
Explanation:

CICS is attempting to close MRO/IRC communication. This message is normally followed by the netname of each session that is still active, and additionally for EXCI sessions, the jobname, stepname, procname and MVS ID of the batch program communicating on that session.

For EXCI sessions, a netname of GENERIC indicates a generic pipe. For the batch job information to appear in the message, at least one DPL request must have been issued on that session.

Note:
In some circumstances the message is not followed by any netnames. This can occur if CICS is using the cross-system coupling facility (XCF) to communicate across CECs, and CICS is unable to deliver an earlier message to XCF because, for example, the XCF buffer is full.
System action:

CICS issues IRC STOP IMMEDIATE to force close the remaining session(s). This message is reissued at 30 second intervals, or until the last session is closed.

User response:

None, unless the delay in closedown appears abnormally long. If this is the case, investigate why the session(s) are still active. Take appropriate action to allow the session(s) to close. If no netnames are displayed, investigate why XCF is unable to accept a message from CICS.

Destination:

Console

Modules:

DFHZDSP

XMEOUT Parameter: applid

DFHIR3747
applid CONNECTION connid with protocol(EXCI) has been connected to by a NON-BATCH system. Connection set out of service.
Explanation:

A CICS connection has been defined with the protocol EXCI and an attempt has been made to connect to it by a non-batch system.

There are two possible explanations for this message:

System action:

CICS sets the connection out of service.

User response:

Investigate and correct the relevant connection definitions and set back in service.

Destination:

Console

Modules:

DFHCRNP

XMEOUT Parameters: applid, connid

DFHIR3748
date time applid Initial start of connected system sysid, netname netname, protocol pppp was detected.
Explanation:

A new logname was received during the MRO bind process from the connected system. This indicates that the connected system has restarted with a start type of INITIAL, since it last communicated with this CICS. If the message-issuing system has any resynchronization data relating to units of work from a previous usage of the connection, this data is kept but cannot be used by the system for automatic resynchronization.

System action:

New MRO work for the connection is not inhibited.

User response:

Examine the resynchronization information kept by the system from the previous usage of the connection using the

EXEC CICS INQUIRE UOWLINK RESYNCSTATUS

command (or the equivalent CEMT command) for the named connection in order to locate UOWLINKs with a RESYNCSTATUS of COLDSTART. You can use this information to resolve manually any indoubt units of work that existed on this system or the connected system. When the information is no longer of use, issue the

EXEC CICS SET CONNECTION PENDSTATUS(NOTPENDING)

command (or the CEMT equivalent) for the named connection to discard the resynchronization data relating to the previous usage. Note that any new resynchronization data generated for the newly established connection is still kept.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHCRR

XMEOUT Parameters: date, time,applid, sysid, netname, pppp

DFHIR3750
applid Unable to stop interregion communication session during startup recovery.
Explanation:

A request has been received as the result of an abnormal termination to stop the interregion communication session during the startup recovery process. This request has failed.

System action:

The session remains active.

User response:

If the session must be stopped, you may have to re-IPL. (To diagnose the underlying problem, contact your IBM Support Center.)

Destination:

Console

Modules:

DFHCRNP

XMEOUT Parameter: applid

DFHIR3751
applid Unable to stop interregion communication session during shutdown.
Explanation:

A request has been received (by means of system termination, abnormal termination, or master terminal) to stop the interregion communication session during the shutdown process. This request has failed.

System action:

The session remains active.

User response:

If the session must be stopped, you may have to re-IPL. (To diagnose the underlying problem, contact your IBM Support Center.)

Destination:

Console

Modules:

DFHSTP

XMEOUT Parameter: applid

DFHIR3760
applid Unable to break lines with interregion communication. (Modname: modname)
Explanation:

A request has been made to shut down the interregion session. This has caused module DFHZCX to issue a request to the interregion communication program to terminate the association between CICS and the interregion communication program, but the request failed because of a system error.

System action:

Any running batch (database sharing) programs are left in the wait state, and should be canceled. Any CICS tasks (in other CICS systems) that are in communication with this system are also left in the wait state. These other CICS systems should issue CEMT SET CONNECTION(sysid) OUTSERVICE PURGE, where sysid is the CONNECTION name of the system for which DFHIR3760 was issued. Also, any attempt to restart the interregion session (in the current or any subsequent CICS session) fails.

User response:

To run further batch CICS interregion communication, you must re-IPL. You will need further assistance to resolve the underlying problem. See CICS® Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHZIS2, DFHSTP

XMEOUT Parameters: applid, modname

DFHIR3762
date time applid Inter-region activity now complete
Explanation:

A CEMT SET INTERREGION COMMUNICATION (IRC) CLOSED request was issued at the master terminal. The IRC session is now complete.

System action:

Processing continues.

User response:

None.

Destination:

CSMT

Modules:

DFHCRNP

XMEOUT Parameters: date, time,applid

DFHIR3765
UNABLE TO STOP INTERREGION COMMUNICATION SESSION AFTER SYSTEM ABEND.
Explanation:

A request has been received (by means of system termination, abnormal termination, or master terminal) to stop the interregion session. This request has failed.

System action:

The session remains active.

User response:

If the session must be stopped, you may have to re-IPL. You will need further assistance to resolve the underlying problem. See CICS Problem Determination Guide for guidance on how to proceed.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHCRC

DFHIR3767
applid The interregion startup program DFHCRSP is not present.
Explanation:

Module DFHCRSP is required to start an IRC session, but is missing from the CICS program library or has no installed program definition.

System action:

The IRC session is not started.

User response:

Install DFHCRSP definition (group DFHISC) and/or supply module DFHCRSP

Destination:

Console

Modules:

DFHSIJ1

XMEOUT Parameter: applid

DFHIR3771
applid Unable to start interregion communication because (E)STAE macro failed.
Explanation:

CICS issued an ESTAE macro that did not execute successfully, probably because storage for a ESTAE control block (SCB) was not available. For more information about the SCB, refer to the MVS/ESA System Programming Library: Application Development Guide.

System action:

The IRC session is not started.

User response:

Correct the cause of (E)STAE failure.

Destination:

Console

Modules:

DFHSIJ1

XMEOUT Parameter: applid

DFHIR3772
applid Error while attempting to start interregion communication.
Explanation:

CICS has evidence that the IRC session has already started. This is probably because the previous session could not be stopped (see messages DFHIR3760 and DFHIR3765).

Note:
The session, although apparently started, is not in a usable state.
System action:

The IRC session is not started.

User response:

Perform another IPL.

Destination:

Console

Modules:

DFHSIJ1

XMEOUT Parameter: applid

DFHIR3773
applid Unable to start interregion communication because the APPLID option has a blank value.
Explanation:

Either the default value of applid (on DFHTCT TYPE=INITIAL, DFHSIT, override) must be used, or a value which is not a null value must be used.

System action:

The IRC session is not started.

User response:

Correct the applid value.

Destination:

Console

Modules:

DFHSIJ1

XMEOUT Parameter: applid

DFHIR3775
applid Unable to start interregion communication because short on storage.
Explanation:

Main storage is required to start the IRC session, but the storage is not available.

System action:

The IRC session is not started.

User response:

Wait until the storage condition has eased, then issue CEMT SET IRC OPEN command at the master terminal.

Destination:

Console

Modules:

DFHSIJ1

XMEOUT Parameter: applid

DFHIR3776
applid Unable to start interregion communication because another CICS system of the same name is active.
Explanation:

A CICS system is named by its applid value. If two CICS systems have the same applid value, the interregion communication SVC cannot distinguish between the systems.

Note:
This situation may arise if a previous interregion communication (IRC) session could not be stopped; see message DFHIR3760. In this case, the IRC SVC would consider that the new session conflicted with the old (unstoppable) session.
System action:

The IRC session is not started.

User response:

Use a different generic applid for each CICS system.

Destination:

Console

Modules:

DFHSIJ1

XMEOUT Parameter: applid

DFHIR3777
applid The interregion communication table is full
Explanation:

The interregion communication SVC’s user table is full.

System action:

The IRC session is not started.

User response:

When there are fewer batch-sharing programs running, issue CEMT SET IRC OPEN at the master terminal.

Start of changeA common cause of this error is that the MAXGROUP or MAXMEMBER parameters are set too low in an XCF Sysplex environment. Check the values of MAXGROUP and MAXMEMBER and, if necessary, raise to suit your environment. For more information see the CICS Transaction Server for z/OS® Installation GuideEnd of change

If this does not resolve the problem you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHSIJ1

XMEOUT Parameter: applid

DFHIR3778
applid Insufficient storage is available for interregion communication blocks.
Explanation:

There is insufficient key 0 storage for the IRC control blocks. Storage is required from the CICS region but from outside the CICS DSA.

System action:

The IRC session is not started.

User response:

Ensure that sufficient storage is available. See the CICS Performance Guide for further guidance on how to determine the CICS DSA size limits in relation to the REGION size.

Destination:

Console

Modules:

DFHSIJ1

XMEOUT Parameter: applid

DFHIR3779
applid Insufficient storage is available for interregion communication subsystem blocks.
Explanation:

There is insufficient storage for the control blocks required by IRC. Storage is required from the CICS region but from outside the CICS DSA.

System action:

The IRC session is not started.

User response:

Ensure that sufficient storage is available. See the CICS Performance Guide for further guidance on how to determine the CICS DSA size limits in relation to the REGION size.

Destination:

Console

Modules:

DFHSIJ1

XMEOUT Parameter: applid

Start of change
DFHIR3780
applid Unable to start interregion communication. Return code=X'retcode', Reason code=X'rsncode'.
Explanation:

CICS attempted to establish itself as a user of the interregion communication (IRC) services, but the attempt failed.

System action:

The IRC session is not started.

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

User response:

The return code and reason code (if any) correspond to a number of possible errors. The four byte return code field displays the following information starting with the high order byte:

See Interregion Control Blocks (IRC) in the CICS Data Areas manual for a complete list of return codes and error qualifiers. (The names of all the return codes and error qualifiers start with IRERR and IRERQ respectively.)

Start of changeThe return codes should be referenced from the documentation for the version of CICS that supplied the IRP program in use rather than the version of CICS that issued the message.End of change

Check that the following requirements are satisfied:

If the message is issued when all of these conditions have been met, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHSIJ1

XMEOUT Parameters: applid, X'retcode', X'rsncode'

End of change
Start of changeDFHIR3781End of change
Start of changeapplid Unable to start interregion communication because task CSNC cannot be attached.End of change
Start of change
Explanation:

Definitions for CSNC or DFHCRNP have not been installed, or DFHCRNP is missing from the CICS program library.

End of change
Start of change
System action:

The IRC session is not started.

End of change
Start of change
User response:

Make CSNC or DFHCRNP available.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHSIJ1End of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

DFHIR3783
date time applid Transaction transid termid termid - Connected transaction abended with message xxxx
Explanation:

Transaction transid was connected to a transaction in another CICS system, through an MRO link. This other transaction has abnormally terminated with the given message, causing the local transaction to abnormally terminate.

System action:

The transaction abnormally terminates.

User response:

Correct the cause of the abend in the connected transaction.

Destination:

CSMT

Modules:

DFHZCX

XMEOUT Parameters: date, time,applid, transid, termid, xxxx

DFHIR3784
applid A severe error (code X'code') has occurred in module DFHCRR. Connection conname (if non-blank) has been set out of service.
Explanation:

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

System action:

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

The connection conname (if any) being processed at the time of error is set out of service, to prevent the error from recurring repeatedly.

CICS will continue unless you have specified in the dump table that CICS should terminate. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Find and fix the source of the error before setting the connection back in service.

Notify the system administrator. This failure indicates a serious error in CICS. If you have not requested termination in the dump table, you may want to terminate CICS. For further information about CICS exception trace entries, see the CICS Problem Determination Guide.

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

Destination:

Console

Modules:

DFHCRR

XMEOUT Parameters: applid, X'code',conname

DFHIR3785
applid Interregion control task CSNC abend. Interregion activity will be abnormally terminated.
Explanation:

CSNC is abnormally terminated.

System action:

CSNC is abnormally terminated with a system dump. All tasks using MRO links to other systems are abnormally terminated. CICS also abends all tasks in other CICS regions (including CICS shared data base batch regions) that are currently communicating with this system.

User response:

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

Following this abend it is not possible to use IRC within this CICS system. CICS must be restarted before IRC can be used.

Destination:

Console

Modules:

DFHCRNP

XMEOUT Parameter: applid

DFHIR3786
applid Unable to start interregion communication because module DFHSCTE could not be found.
Explanation:

The IRC module DFHIRP attempted to load DFHSCTE, but the module was not in the LPA.

System action:

The interregion communication session is not started.

User response:

Ensure that DFHSCTE is available.

Destination:

Console

Modules:

DFHSIJ1

XMEOUT Parameter: applid

Start of changeDFHIR3788End of change
Start of changedate time applid Unexpected failure (return code=X'retcode', reason code=X'rsncode') trying to establish connection to system sysidEnd of change
Start of change
Explanation:

CICS could not establish a link to system sysid, even though system sysid is available for communication.

The most common value of code X'retcode' returned by the interregion communication SVC is X'68'. This means that no connection to the requesting region has been defined in the target region.

The four byte return code field displays the following information starting with the high order byte:

See Interregion Communication Control Blocks in the CICS Data Areas manual for a complete list of return codes and error qualifiers. (The names of all the return codes and error qualifiers start with IRERR and IRERQ respectively.)

A possible reason for this message is that the applid of the system on which the message appears does not match the NETNAME on any of the system entries defined in system sysid.

This error may also occur when connections are being created dynamically. In this case, the mismatch is transient and will eventually be resolved when the connection creation process running on the remote CICS region completes.

End of change
Start of change
System action:

If the mismatch is transient, the connection is established.

If there is a definition error, the connection is not established. Any existing connections are not affected.

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

End of change
Start of change
User response:

If the mismatch is transient, a connection should be established. This can be verified by querying the connection status using CEMT.

If an applid or a NETNAME mismatch has occurred, correct the error and retry.

Start of changeIf the problem persists you may need to re-ipl your system.End of change

If a mismatch is not the cause of the error, you may need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHCRNPEnd 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 changeretcode', End of changeStart of changeX'End of changeStart of changersncode',End of changeStart of changesysidEnd of change

DFHIR3789
date time applid SEND/RECEIVE mismatch between TCT system entries for this system and system sysid
Explanation:

System action:

As many sessions as possible are established.

User response:

Alter one or both DFHTCT entries.

Destination:

CSMT

Modules:

DFHCRNP

XMEOUT Parameters: date, time,applid, sysid

DFHIR3790
date time applid Unable to connect to system sysid for security reasons
Explanation:

The TYPE=SYSTEM entry in system sysid’s DFHTCT entry for this system contained a SECURITYNAME operand that did not match the real external security ID of this system, or the ID was unknown to IRC.

System action:

The connection is not established.

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

User response:

Discuss with the system programmer responsible for system sysid.

Destination:

CSMT

Modules:

DFHCRNP

XMEOUT Parameters: date, time,applid, sysid

DFHIR3791
applid Unable to start interregion communication because ISC=NO has been specified.
Explanation:

IRC facilities are not available because ISC=NO has been specified.

System action:

The interregion communication session is not started.

User response:

Run with a value other than NO in the ISC operand of DFHSIT or system initialization overrides.

Destination:

Console

Modules:

DFHSIJ1

XMEOUT Parameter: applid

DFHIR3793
applid Unable to start interregion communication because a severe error has occurred in the recovery manager.
Explanation:

IRC facilities are not available because an internal request issued to recovery manager has failed.

System action:

The interregion communication session is not started.

User response:

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

Destination:

Console

Modules:

DFHSIJ1

XMEOUT Parameter: applid

DFHIR3794
date time applid Interregion usage of MVS CSA storage has reached nnnn bytes for this IPL
Explanation:

The maximum number of MVS CSA bytes used so far in this IPL by the CICS interregion communication facility (for interregion buffers), is nnnn.

System action:

Processing continues.

User response:

None.

Destination:

CSMT

Modules:

DFHZCX

XMEOUT Parameters: date, time,applid, nnnn

DFHIR3795
ABNORMAL TERMINATION - STATUS CODE DHxx
Explanation:

The IMS high-level programming interface (HLPI) has found a condition caused by a programming error, or DL/I has returned a status code to HLPI that indicates an error. xx is the status code.

System action:

The batch program abnormally terminates with abend code 3795.

User response:

Correct the error and try again. See the IMS Application Programming: DL/I Calls or the Application Programming: EXEC DLI Commands for an explanation of the IMS status code.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDRPG

DFHIR3796
date time applid Transaction tranid termid termid - A connected transaction sent issue abend with following message: xxxxxx
Explanation:

Transaction tranid was connected to a transaction in another CICS system via an MRO link. The other transaction sent an ISSUE-ABEND flow with a message.

System action:

Processing continues.

User response:

Examine the information in the included message to determine the circumstances and what action to take.

Destination:

CSMT

Modules:

DFHZIS1.

XMEOUT Parameters: date, time,applid, tranid, termid, xxxxxx

DFHIR3798
applid IRC Not Started. Unable to load Interregion Communication Work Exit DFHIRW10.
Explanation:

As part of interregion communication initialization, an attempt is made to establish an internal work exit mechanism. This attempt has failed.

The most likely reason for the failure is that the interregion communication work exit module, DFHIRW10, cannot be loaded. This module should appear in an APF authorized library in the STEPLIB concatenation for the CICS region, in the linklist, or in the LPA.

System action:

The attempt to initiate the interregion communication facility (via the IRCSTRT DFHSIT or override option or via the CEMT SET IRC OPEN command) fails. CICS continues.

User response:

Ensure that the interregion communication work exit module, DFHIRW10, is available to be loaded.

Destination:

Console

Modules:

DFHSIJ1

XMEOUT Parameter: applid

DFHIR3799
applid Unable to start interregion communication because DFHIRP services are down level.
Explanation:

The version of DFHIRP being used is at a lower level than that of the caller wishing to make use of interregion communication.

System action:

The interregion communication session is not started.

User response:

If IRC is required, update the level of the DFHIRP module in the LPA such that it matches the level of the latest CICS version in use. If IRC is not required, run with system initialization override option IRCSTRT=NO.

Destination:

Console

Modules:

DFHSIJ1, DFHDRPF

XMEOUT Parameter: applid

[[ Contents Previous Page | Next Page Index ]]