DFHZNxxxx messages

Start of change
DFHZN2130
date time applid A unit of work has been shunted but the connection with the remote system does not support the shunt protocols. Resources on the remote system may be out of sync with those on this CICS after the UOW is resynchronized. Failure date mm/dd/yy failure time hh:mm:ss remote system netname transaction tranid task number trannum operator terminal termid user userid network UOW netuowid local UOW X'localuow'.
Explanation:

This message is preceded by message DFHAC2231. An application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. The coordinator of the syncpoint is not this CICS system but is remote.

Transaction tranid has lost contact with its coordinator system during the indoubt period.

System action:

In accordance with the transaction definition, the unit of work is not completed. It is allowed to wait for resynchronization with the coordinator system. The transaction is abnormally terminated with abend code ASP1. The unit of work is shunted to await the return of the coordinator system.

As part of this processing, CICS has attempted to pass on the shunt request to another partner system. However, this partner does not support the shunting protocols, and so this partner may backout or commit changes to its resources independently of this shunted unit of work.

User response:

Following resynchronization with the coordinator system, determine whether the remote function shipped resources are out of synchronization. The action to take depends on local procedures and the design of the application program. For example, it may be possible to rerun the application but only making updates to remote resources. Refer to the CICS® Intercommunication Guide for information on design considerations in a distributed environment.

Destination:

CSMT

Modules:

DFHCR2U

XMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, netname, tranid,trannum, termid, userid, netuowid, X'localuow'

End of change
Start of changeDFHZN2131End of change
Start of changedate time applidEnd of changeStart of change Intersystem session failure during CICS synclevel one commit. Local resources may be out of sync with those on the remote system. Failure date End of changeStart of changemm/dd/yyEnd of changeStart of change failure timeEnd of change Start of changehh:mm:ssEnd of changeStart of change remote system End of changeStart of changenetnameEnd of changeStart of change transactionEnd of change Start of changetranidEnd of changeStart of change task number End of changeStart of changetrannumEnd of changeStart of change operator terminalEnd of change Start of changetermidEnd of changeStart of change user End of changeStart of changeuseridEnd of changeStart of change network UOW End of changeStart of changenetuowidEnd of changeStart of change local UOW X'End of changeStart of changelocaluowidEnd of changeStart of change'.End of change
Explanation:

A CICS application has been using APPC synclevel 1 to process remote function shipped resources. The application took a syncpoint, either implicitly or explicitly, and this has caused all local resources and synclevel 2 partners to be committed. However, a session failure occurred at a critical time during the synclevel 1 commit processing, and the synclevel 1 function shipped resources may have committed successfully or may have backed out.

System action:

CICS synclevel 1 commit processing continues, with the intention of committing as many synclevel 1 resources as possible. For APPC synclevel 1, CICS does not attempt to resolve the situation any further.

On completion of the syncpoint, CICS abends the user task.

User response:

Determine whether the remote function shipped resources are out of synchronization. The action to take depends on local procedures and the design of the application program. For example, it may be possible to rerun the application but only making updates to remote resources. Refer to the CICS Intercommunication Guide for information on design considerations in a distributed environment.

Destination:

CSMT

Modules:

Start of changeDFHCR2UEnd of change

Start of changeXMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, netname, tranid,trannum, termid, userid, netuowid, X'localuowid'End of change

Start of changeDFHZN2132End of change
Start of changedate time applidEnd of changeStart of change Rollback received in response to CICS synclevel one commit. Local resources are out of sync with those on the remote system. Failure date End of changeStart of changemm/dd/yyEnd of changeStart of change failure timeEnd of change Start of changehh:mm:ssEnd of changeStart of change remote system End of changeStart of changenetnameEnd of changeStart of change transactionEnd of change Start of changetranidEnd of changeStart of change task number End of changeStart of changetrannumEnd of changeStart of change operator terminalEnd of change Start of changetermidEnd of changeStart of change user End of changeStart of changeuseridEnd of changeStart of change network UOW End of changeStart of changenetuowidEnd of changeStart of change local UOW X'End of changeStart of changelocaluowidEnd of changeStart of change'.End of change
Explanation:

A CICS application has been using APPC synclevel 1 to process remote function shipped resources. The application took a syncpoint, either implicitly or explicitly, and this has caused all local resources and synclevel 2 partners to be committed. However, when a commit message was sent to a synclevel 1 function shipped resource, the resource voted to backout.

System action:

Synclevel 1 commit processing continues with the intention of committing as many synclevel 1 resources as possible. For APPC synclevel 1, CICS does not attempt to resolve the situation any further.

On completion of the syncpoint, CICS abends the user task.

User response:

The action to take depends on local procedures and the design of the application program. For example, it may be possible to rerun the application but only making updates to remote resources. Refer to the CICS Intercommunication Guide for information on design considerations in a distributed environment.

Destination:

CSMT

Modules:

Start of changeDFHCR2UEnd of change

Start of changeXMEOUT Parameters: date, time,applid, mm/dd/yy, hh:mm:ss, netname, tranid,trannum, termid, userid, netuowid, X'localuowid'End of change

DFHZN2133
date time applid Error detected during CICS synclevel one commit. Reason code rc. Local resources may be out of sync with those on the remote system. Failure date mm/dd/yy failure time hh:mm:ss remote system sysid transaction tranid task number trannum operator terminal termid user userid network UOW netuowid local UOW X'localuowid'.
Explanation:

A CICS application has been using APPC synclevel 1 to process remote function shipped resources. The application took a syncpoint, either implicitly or explicitly, and this has caused all local resources and synclevel 2 partners to be committed. However, when a commit message was sent to a synclevel 1 function shipped resource, the reply indicated that an error has occurred. The reason code provides details of the error and has the following values:

01
Protocol violation by partner system - unexpected FMH data
02
Protocol violation by partner system - unexpected syncpoint message data
03
Abend received
04
Deadlock or read timeout.
System action:

CICS synclevel 1 commit processing continues, with the intention of committing as many synclevel 1 resources as possible.

For reason code 01, a transaction dump with dump code ASPI is taken. For reason code 02, a transaction dump with dump code ASPJ is taken. On completion of the syncpoint, CICS abends the user task.

User response:

The action to take depends on local procedures.

For reason codes 01 and 02, examine the dump to determine what message data was received from the partner. This information is held in one of the terminal input/output areas. A failure in the communication system might have caused corruption of the data.

Reason code 03 indicates that the partner system has sent an abend. There is an error in the partner system which may need to be investigated.

Reason code 04 indicates that the partner system took too long to respond to the synclevel 1 commit. There could be a problem with the remote system, or the communication system. It may be necessary to increase the deadlock timeout or read timeout values to prevent this recurring.

Destination:

CSMT

Modules:

Start of changeDFHCR2UEnd of change

Start of changeXMEOUT Parameters: date, time,applid, rc, mm/dd/yy, hh:mm:ss, sysid, tranid, trannum, termid, userid, netuowid,X'localuowid'End of change

DFHZN2200
date time applid FREE IMPLICIT failed during syncpoint processing for session session id , remote system netname. Transid transid. The original abend code was abend code.
Explanation:

A DFHTC FREE IMPLICIT request for a non-principal facility MRO session has failed.

System action:

CICS writes an exception trace entry with code '0D86' before issuing a DFHTC FREE DETACH request for the session.

User response:

If the task was purged by the operator causing abend AZI9 or a read timeout occurred causing abend AZIG this error may be expected and no further action may be necessary.

Otherwise this failure may represent an error. To investigate further set up a system dump table entry for system dump code ZN2200. You may need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Destination:

CSMT

Modules:

DFHCRIU

XMEOUT Parameters: date, time,applid, session id, netname, transid, abend code

DFHZN2701
date time applid Log data sent on ISC session is xxxxxxxx
Explanation:

This is an informational message. The transaction is communicating with a logical unit type LU6.2. It has sent an FMH (function management header) which carries log data.

System action:

The transaction continues processing.

User response:

None.

Destination:

CSNE

Modules:

DFHZERH

XMEOUT Parameters: date, time,applid, xxxxxxxx

[[ Contents Previous Page | Next Page Index ]]