The exchange lognames process
The protocols that control the communication of syncpointing commit and backout decisions depend on information in the system log.
- A cold/warm log mismatch. A cold/warm log mismatch is caused by
the loss of log data at one partner when the other has resynchronization work
outstanding. Note: The term “cold start” is used in the SNA Peer Protocols documentation, and by other products that communicate with CICS® TS for z/OS® to describe the cause of a loss of log data.
“Cold start” is also used in CICS TS for z/OS messages and interfaces to describe the action of a partner system that results in a loss of log data for CICS TS for z/OS.
However, in CICS TS for z/OS, a loss of log data for connected systems is caused by an initial start (not by a cold start), or by a SET CONNECTION NORECOVDATA command.
- A lognames mismatch. A lognames mismatch is caused by a corruption
of logname data. This can occur due to:
- A system logic error
- An operational error—for example, a failure to perform an initial start when upgrading from a back-level CICS release to CICS Transaction Server for z/OS.
The exchange lognames process is defined by the APPC architecture. For a full description of the concepts and physical flows, see the SNA Peer Protocols manual. MRO and IPIC use a similar protocol to APPC, with the important difference that after the erasure of log information at a partner, they allow new work to begin whatever the condition of existing work. On APPC synclevel 2 sessions, no further work is possible until action has been taken to delete any outstanding resynchronization work.
After a partner system has been reconnected, you can use the INQUIRE CONNECTION PENDSTATUS command to check whether there is any outstanding resynchronization work that has been invalidated by the erasure of log information at the partner. A status of 'PENDING' indicates that there is. To check whether APPC connections are able to execute new synclevel 2 work, use the INQUIRE CONNECTION XLNSTATUS command. A status of 'XNOTDONE' indicates that the exchange lognames process has not completed successfully, probably because of a loss of log data.
- None. If there is no resynchronization work outstanding on the local system, the loss of log data has no effect.
- Keep outstanding resynchronization work (which may include UOWs which were indoubt when communication was lost) for investigation.
- Delete outstanding resynchronization work; any indoubt UOWs are committed or backed out according to the ACTION option of the associated transaction definition, and any decisions remembered for the partner are forgotten.
- Automatically, using the XLNACTION option of the connection definition. To delete resynchronization work as soon as the loss of log data by the partner is detected, use XLNACTION(FORCE).
- Manually, using the SET UOW and SET CONNECTION PENDSTATUS(NOTPENDING) commands.