Explanation
In the message text:
- entity
- This indicates what kind of XRC entity the message refers to.
The valid values are:
- SESSION
- The message refers to an XRC session.
- CLUSTER
- The message refers to a XRC cluster.
The coupled XRC session session_id has
not interlocked with the master session msession_id whose
master high-level qualifier is mhlq. A session
is in interlock status when its consistency time is before the master
journal time, and its journal time is after the master journal time.
See
message ANTQ8247I for the explanation of the interlock delay delay_time.
The reason for issuing this message can be:
- The session does not meet the interlock criteria, and the session
has at least one nonsuspended volume pair in the session. This session
or another coupled session in the master session has detected a delay
in mainline data mover processing might cause the non-interlocked
state.
- An interlocked session associated with the master session is not
active. If you previously ended or suspended all coupled sessions
in a master session, when you restart these sessions, you receive
this message after you add volumes to each restarted sessions if all
coupled interlocked sessions in the master session have not been restarted.
If you restart all sessions before you add any volumes to the coupled
sessions, you will not receive this message.
- All existing interlocked sessions are idle (not receiving any
write updates), and the delay_time for session session_id is
greater than 10 seconds. An update must be made
to at least one primary volume in the session for interlock to occur.
System action
XRC functions are active.
System programmer response
Do one of the following:
- In most cases, XRC can self-correct this state. However, if the
situation persists, look for message ANTX8117I for this session, or
one of the other coupled sessions in the master session, indicating
the particular delay that have caused this session to become non-interlocked.
- Remove nonstarted coupled sessions from the master session by
issuing the XCOUPLE PURGE command.
- Update a primary volume in the non-interlocked
session. Note that if the entity is CLUSTER, issue XSTATUS CLUSTER
command to determine the session_id of the non-interlocked
session.
Source
Extended remote copy (XRC).
Routing code
Descriptor code