ATB211E

Explanation
 A log name mismatch was detected during an exchange
log name request by luname3 during conversation
allocation processing between luname1 and luname2 or
during a resynchronization exchange between luname1 and luname2 to
bring distributed units of recovery to a consistent state after a
session or system failure.
 reason further
describes the cause of the log name mismatch.
 In the message
text:  luname1
The name of the LU that initiated the log name exchange
luname2
The name of the LU that is the target of the exchange log name
luname3
The name of the LU that detected the mismatch
reason
One of the following:  PARTNER XLN REPLY LOG NAME DOES NOT MATCH LOCAL LOG
The log name sent by the partner LU in reply to the exchange log
name request does not match what is stored by the local LU in its
log.
ABNORMAL REPLY RECEIVED FROM PARTNER LU
The initiator of an exchange log name transaction received an
abnormal reply from the partner LU.  The most likely cause of this
abnormal reply is a mismatch between the log name sent by the local
LU in the exchange log name GDS variable, and the log name for the
initiator LU stored in the partner's log.
PARTNER XLN REQUEST LOG NAME DOES NOT MATCH LOCAL LOG
The log name sent by the initiator LU in the exchange log name
request does not match what is stored by the local LU in its log.

System action
 If this message is issued during APPC/MVS resynchronization
processing to resolve incomplete units of recovery, resynchronization
does not continue. Resynchronization will be attempted 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 log name mismatch
can be resolved.
 Symptom records are written to the logrec
data set to record the error condition and record diagnostic data.

Operator response
 Ensure that the local system has restarted
with the correct system logs, including the correct RRS log group
name (GNAME parameter specified on the RRS cataloged procedure).
 Contact
the operator for the partner system to ensure that the partner system
restarted with the correct system logs.
 Make sure to provide
the complete text of message ATB227I, if it is issued.

System programmer response
 The cause of the log name mismatch
may be due to:  The incorrect system log being used on the local or partner system.
An internal error in APPC/MVS logging or in the logging function
of the partner system.

 If an incorrect system log caused the problem, attempt
to correct the log name mismatch problem on the partner system using
the partner system's local log name mismatch recovery procedures.
For complete information on resolving this problem, see the description
of how to handle log name mismatch in z/OS MVS Planning: APPC/MVS Management. 

Module
 ATBPCRS

Source
 APPC/MVS

Routing Code
 2

Descriptor Code
 4

Automation
 Ensure that the local system
has restarted with the correct system logs, including the correct
RRS log group name (GNAME in the cataloged procedur both on this and
on the partner system. Also make sure to note message ATB227I, if
it is issued.