DFHRXxxxx messages

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

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

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

End of change
Start of change
System action:

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

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

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

End of change
Start of change
User response:

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

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

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

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

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

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

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRXDMEnd of change

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

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

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

End of change
Start of change
System action:

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

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

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

End of change
Start of change
User response:

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

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

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

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

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRXDMEnd of change

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

Start of changeDFHRX0100IEnd of change
Start of changeapplid RX domain initialization has started.End of change
Start of change
Explanation:

This is an informational message indicating the start of RX domain initialization.

End of change
Start of change
System action:

Initialization continues.

End of change
Start of change
User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRXDMEnd of change

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

Start of changeDFHRX0101IEnd of change
Start of changeapplid RX domain initialization has ended.End of change
Start of change
Explanation:

RX domain initialization has completed successfully.

End of change
Start of change
System action:

Initialization continues.

End of change
Start of change
User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRXDMEnd of change

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

Start of changeDFHRX0102End of change
Start of changeapplid Errors were encountered during initialization of the RX domain. Domain initialization has ended.End of change
Start of change
Explanation:

Errors have been detected by the Resource Recovery Services (RX) domain during CICS initialization. Accompanying messages describe the nature of the errors.

End of change
Start of change
System action:

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.

End of change
Start of change
User response:

If your CICS system will not use any services that depend on Resource Recovery Services, no action is necessary. Otherwise, you will need to shut CICS down, and restart it once the problems identified by the earlier messages have been corrected.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRXDMEnd of change

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

Start of changeDFHRX0103End of change
Start of changeapplid An unexpected return code X'rc' was received from RRMS service xxxxxxxx.End of change
Start of change
Explanation:

An unexpected return code was received when CICS issued a request to Recoverable Resource Management Services (RRMS). The name of the RRMS service included in the message indicates the component of RRMS as follows:

CRGxxxx
Registration Services
CTXxxxx
Context Services
ATRxxxx
Resource Recovery Services (RRS)

This message may indicate a problem with RRMS.

End of change
Start of change
System action:

CICS continues, but - depending on the service and the return code - CICS services that depend on RRMS may not be available. Further messages will provide more information.

End of change
Start of change
User response:

Record the name of the RRMS service and the return code. RRMS return codes are documented in GC28-1793 OS/390 MVS Programming: Resource Recovery.

If you are unable to determine the cause of the problem from this information, you may need assistance from IBM. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRXDM, DFHRXUWEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changerc',End of changeStart of changexxxxxxxxEnd of change

Start of changeDFHRX0104IEnd of change
Start of changeapplid The Resource Recovery Services (RRS) exit manager aaaaaaaaaaaaaaaa is now available.End of change
Start of change
Explanation:

This message is issued when CICS discovers that a Resource Recovery Services (RRS) exit manager is available. The insert aaaaaaaaaaaaaaaa is the name of the exit manager.

End of change
Start of change
System action:

CICS begins restart processing with RRS.

End of change
Start of change
User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRXDMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeaaaaaaaaaaaaaaaaEnd of change

Start of changeDFHRX0105IEnd of change
Start of changeapplid The Resource Recovery Services (RRS) exit manager aaaaaaaaaaaaaaaa is now unavailable.End of change
Start of change
Explanation:

This message is issued when CICS discovers that a Resource Recovery Services (RRS) exit manager is unavailable. The insert aaaaaaaaaaaaaaaa is the name of the exit manager. Transactions which use RRS to coordinate their updates cannot be successfully executed.

End of change
Start of change
System action:

CICS continues. Message DFHRX0104 will be issued when the exit manager becomes available once more.

End of change
Start of change
User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRXDMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeaaaaaaaaaaaaaaaaEnd of change

Start of changeDFHRX0106IEnd of change
Start of changeapplid Restart processing with Resource Recovery Services (RRS) is beginning.End of change
Start of change
Explanation:

This message is issued when CICS begins restart processing with Resource Recovery Services (RRS).

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRXDMEnd of change

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

Start of changeDFHRX0107IEnd of change
Start of changeapplid Restart processing with Resource Recovery Services (RRS) has ended.End of change
Start of change
Explanation:

This message is issued when restart processing with Resource Recovery Services (RRS) ends. If RRS has become unavailable during restart processing (indicated by message DFHRX0105) restart processing may be incomplete.

End of change
Start of change
System action:

CICS continues. If RRS has become unavailable, CICS will resume restart processing when RRS becomes available once more.

End of change
Start of change
User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRXDMEnd of change

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

Start of changeDFHRX0108End of change
Start of changedate time applid Log name mismatch with Resource Recovery Services. Expected Log name logname. Received Log name logname.End of change
Start of change
Explanation:

During the exchange of log names with Resource Recovery Services (RRS), which occurred when RRS restarted, this system’s memory of RRS’s log name did not match the log name retrieved from RRS. RRS may have performed a cold start.

End of change
Start of change
System action:

CICS execution continues. Units of work that are awaiting resynchronization with RRS will not be resolved automatically.

End of change
Start of change
User response:

The associated units of work may need to be resolved by using CEMT SET UOW. The message should not recur.

End of change
Start of change
Destination:

Console and Transient Data Queue CSMT

End of change
Modules:

Start of changeDFHRXDMEnd 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 changelogname, End of changeStart of changelognameEnd of change

Start of changeDFHRX0109End of change
Start of changedate time applid Invalid pass token received on connection sysid session termid.End of change
Start of change
Explanation:

A batch program using the extended External CICS Interface (EXCI) has issued a DPL request which does not include the SYNCONRETURN option. However, the value of the pass token received from the batch region does not match that which was lodged with Recoverable Resource Management Services (RRMS) in the batch region.

End of change
Start of change
System action:

DFHRXUW provides console message DFHRX0002, and possibly a system dump (depending on the options in the dump table). The transactional DPL request will not be processed, and the batch job which issued the request may be suspended until it times out.

End of change
Start of change
User response:

Investigate why the pass token was incorrect. It is possible that an unauthorized user has attempted to guess the value of the pass token in order to influence the outcome of a Unit of Work that has expressed interest in an RRMS Unit of Recovery.

If you are satisfied that there has been no attempt to interfere with the pass token, 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:

Console and Transient Data Queue CSCS

End of change
Modules:

Start of changeDFHRXUWEnd 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 changesysid, End of changeStart of changetermidEnd of change

Start of changeDFHRX0110End of change
Start of changeapplid Restart processing with Resource Recovery Services (RRS) was attempted on the wrong system.End of change
Start of change
Explanation:

Resource Recovery Services (RRS) has rejected a request to begin restart processing because there is incomplete recoverable work associated with this CICS applid on another system in the sysplex.

End of change
Start of change
System action:

CICS execution continues, but CICS services that depend upon RRS will not be available until the problem is corrected.

End of change
Start of change
User response:

If your CICS system will not use any services that depend on RRS, no action is necessary. Otherwise, close CICS down and restart it on the correct system in the sysplex. Use the RRS ISPF panels to scan the RRS Resource Manager Data log in order to find the correct system on which to restart CICS.

If, for some reason, you cannot restart CICS on another system in the sysplex, you can take the following steps. However, if you do so, resources may be out of synchronization:

  1. Use the RRS Unit of Recovery list panels to force completion of the incomplete recoverable work
  2. Restart CICS or RRS
  3. Force any CICS units of work that are awaiting resolution from RRS.
End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRXDMEnd of change

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

Start of changeDFHRX0111End of change
Start of changeapplid Resource Recovery Services (RRS) has lost logged data. Resynchronization information may be missing.End of change
Start of change
Explanation:

While attempting to recover resynchronization information from its logs, Resource Recovery Services (RRS) has discovered that some data is missing. This is due to a problem with the RRS log streams.

End of change
Start of change
System action:

CICS restart processing with RRS continues, but RRS may not be able to provide a decision for all indoubt units or work. In these cases, updates to local resources will be committed or backed out according to the ACTION attribute in the corresponding transaction definition.

The Recovery Manager domain will issue one of the following messages for each unit of work affected, indicating the outcome:

End of change
Start of change
User response:

Use the information provided in the Recovery Manager message to decide what action is needed. You may need to take steps to resynchronize resources in local and remote systems.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHRXDMEnd of change

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

[[ Contents Previous Page | Next Page Index ]]