ATB206E

Explanation
 This message is issued during APPC/MVS resynchronization
processing or exchange log name processing when an error is detected
by luname1 in the data sent by luname2 during
the transaction exchange.
 In the message text:  luname1
The name of the logical unit that detected the protocol violation.
luname2
The name of the logical unit that generated the protocol violation.
description-of-protocol-violation
One of the following:  COMPARE STATES GDS VARIABLE NOT RECEIVED
During a resynchronization exchange, the partner did not send
a Compare States GDS variable reply containing the state of the logical
unit of work at the partner LU.
UNEXPECTED DATA RECEIVED FROM INITIATOR
Unexpected data was received from a partner who was initiating
a cold-start exchange log name transaction.
DEALLOCATE ABEND OF CONVERSATION NOT RECEIVED
A deallocation of the exchange log name or resynchronization transaction
conversation from the initiator was expected, but not received.
UNEXPECTED STATUS DATA RECEIVED FROM PARTNER
Unexpected status data was received from a partner who was replying
to an exchange log name or resynchronization transaction initiated
by the local LU.
NO DATA RECEIVED FROM THE PARTNER
During a resynchronization or exchange log name transaction exchange,
the partner responded but failed to send GDS variable data containing
the state of the partner LU.
UNEXPECTED DATA RECEIVED FROM PARTNER
Unexpected data was received from a partner who was replying to
an exchange log name or resynchronization transaction initiated by
the local LU.
INVALID STATUS DATA RECEIVED FROM THE PARTNER
Status data that was invalid for the reply was received by the
initiator of the exchange log name or resynchronization transaction.
NO DATA RECEIVED FROM THE INITIATOR
The initiator of the SNA service TP request failed to send GDS
variable data describing the request.
TOO MUCH DATA RECEIVED FROM THE INITIATOR
The initiator of the SNA service TP request sent more than the
expected amount of GDS variable data for the request.
INVALID STATUS DATA RECEIVED FROM THE INITIATOR
Status data that was invalid for the request was received by the
partner of the exchange log name or resynchronization transaction.
SYNCPT CAPABILITIES NEGOTIATION NOT ALLOWED
The partner attempted to negotiate syncpt capabilities while there
was outstanding resynchronization work to be performed between the
local and partner LUs.
UNEXPECTED COLD START REQUEST RECEIVED
A cold-start exchange log name request was received from a partner
LU while sessions were still active between the local and partner
LUs. The request was rejected.
SYNCPT CAPABILITIES DO NOT MATCH
The syncpt capabilities sent in an exchange log name GDS variable
for a warm-start exchange do not match the capabilities previously
negotiated by the the local and partner LUs.

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 warm/cold mismatch
can be resolved.

Operator response
 Contact the operator at LU luname2 to
determine the cause of the error.

System programmer response
 Examine the logrec data set of the
local LU's system. When a protocol violation is detected during the
transaction exchange of Exchange Log Names GDS variables or Compare
States GDS variables, APPC/MVS records diagnostic information pertaining
to the protocol violation made by the partner LU system. APPC/MVS
sends message ATB70051I or ATB70056I to the partner system as log
data when deallocating the resynchronization conversation abnormally.

Module
 ATBPCRS

Source
 APPC/MVS

Routing Code
 Hardcopy only

Descriptor Code
 4

Automation
 Trap and suppress the first
four occurrences of this message for the same luname2. Notify the
system programmer of the fifth occurrence and display the message.