ATB210E

Explanation
 This message is issued during an exchange log
name transaction when the local LU or partner LU has detected a warm/cold
log status mismatch. An exchange log name transaction is initiated
following a session failure or at first session initiation after system
restart.
 In the message text:  luname1
The name of the logical unit that initiated the log name exchange
luname2
The name of the logical unit that is the target of the exchange
log name
luname3
The name of the logical unit that detected the exchange log name
error.
reason
One of the following:  COLD LOG STATUS REJECTED BY INITIATOR
The initiator of an exchange log name transaction rejected the
local LU cold-log status because the initiating LU has incomplete
units of work on its log that require resynchronization with the local
LU.
RESYNC WORK EXISTS WITH THE PARTNER LU
The initiator of an exchange log name transaction detected that
the partner LU has reported a cold-log status. The cold-log status
is rejected because the initiating LU has incomplete units of work
on its log that require resynchronization with the partner LU.
COLD LOG STATUS REJECTED BY PARTNER
The partner in an exchange log name transaction rejected the initiator
LU cold-log status because the partner LU has incomplete units of
work on its log that require resynchronization with the initiating
LU.
RESYNC WORK EXISTS WITH THE INITIATOR LU
The partner in an exchange log name transaction detected that
the initiating LU has reported a cold-log status. The cold-log status
is rejected because the partner LU has incomplete units of work on
its log that require resynchronization with the initiating LU.

System action
 If this message is issued during APPC/MVS resynchronization
processing to resolve incomplete units of recovery, resynchronization
does not continue. If APPC/MVS is the initiator of resynchronization
processing, APPC/MVS will attempt resynchronization again automatically
at a later time.
 If this message is issued during an exchange
log name interchange preceding a protected conversation allocate or
inbound attach request, the protected conversation between the local
and partner LU is not allocated. No protected conversations between
the local and partner LU will be allocated until the warm/cold mismatch
can be resolved.
 Symptom records are written to the logrec
data set to record the error condition and record diagnostic data.

Operator response
 Notify the system programmer.

System programmer response
 For complete information on resolving
this problem, see the description of how to handle warm/cold mismatch
in z/OS MVS Planning: APPC/MVS Management. 

Module
 ATBPCRS

Source
 APPC/MVS

Routing Code
 2

Descriptor Code
 4