Warm/cold log status mismatch

If, during an exchange log name transaction, the local LU or partner LU detects a warm/cold log status mismatch, APPC/MVS issues operator message ATB210E. Messages ATB70052I and ATB80129I may be returned to the TP.

The log status mismatch may be caused by:

The wrong level of log data at the local or partner LU, or
A cold log start at one of the partners. In this case, you might consider manually forcing some units of work at the warm partner to resolve the problem.

If the cold log status is valid for one of the logical units, and if the warm partner is an APPC/MVS managed logical unit of work, then to resolve the warm/cold mismatch, take one of the following actions against the warm partner (listed in order of increasing potential disruption):

Restart the warm APPC/MVS LU after removing all interests for the APPC/MVS LU using the RRS ISPF panels.
Attention: Before removing incomplete logical units of work, determine whether the incomplete logical units of work can be manually forced or discarded without resynchronization being performed.
1. Delete the LU from the APPC/MVS configuration by issuing a SET command for a parmlib member with an LUDEL statement for the LU.
2. Remove all interests for the cold status partner using the RRS ISPF panels. This prevents APPC/MVS from carrying out any resynchronization to the cold status partner for the removed incomplete logical units of work.
  The LU is known to RRS as a resource manager. The resource manager naming convention for APPC/MVS LUs is:
```
ATB.network-qualified-network-name.IBM
```
  where fully-qualified-name is the fully-qualified name of the local LU, For example, if the fully-qualified name is IBMUSM00.Z0C4AP03, the resource manager name to be specified on the RRS ISPF panels is:
```
ATB.IBMUSM00.Z0C4AP03.IBM
```
  For information on using the RRS ISPF panels, see z/OS MVS Programming: Resource Recovery.
3. Add the LU to the APPC/MVS configuration by issuing a SET command for a parmlib member with an LUADD statement for the LU. The APPC/MVS LU will now restart (however, this will be without incomplete logical units of work).
4. Attempt to initiate a protected conversation between the affected LUs.
Important: The following action affects all protected conversations. Take this action only if the previous action does not resolve the problem.
Delete and redefine the APPC/MVS LU log stream. This will erase APPC/MVS's knowledge of all partners' log information and syncpoint capabilities, not just the cold status partner affected by the problem. For specific information on adding the log stream correctly, see Defining a Log Stream for APPC/MVS.
Important: The following action affects all resource managers, including all syncpoint LUs, and any other resource managers that are registered with RRS. Take this action only if the previous actions do not resolve the problem.
Cold start RRS. See z/OS MVS Programming: Resource Recovery.