Explanation
The data in the message is explained as follows:
- sessionid
- Session ID name. This message will present the data for each session
using the following order method:
- 1st order
- Interlock status (descending, Y then N)
- 2nd order
- Session status in the following order: ACT, END, RCV, ARV, SUS,
UNK
- 3rd order
- Journal delta (ascending)
- sessiontype
- Type of the current session. Possible session type values are:
- C
- session is a cluster
- sessionstatus
- Status of the current session. The following definitions describe
the possible session status values:
- ACT
- Session is active.
- ARV
- Session has initiated recovery processing.
- END
- Session is ended.
- RCV
- Session has completed recovery processing, including clipping
all eligible secondaries to their respective primary volume serials.
- SUS
- Session is suspended.
- UNK
- Status of session is unknown. The master data set has not been
updated within the CTIMEOUT interval.
- volumestatus
- Status of the current volume. The following definitions describe
the possible volume status values:
- (blank)
- Session has at least one active volume or session is inactive.
- AVS
- All volumes in session are suspended by command or an error event
not affecting the coupled session operation.
- ERR
- For ERRORLEVEL(SESSION) sessions, all volumes in this session
or all volumes in all sessions in a cluster session are suspended
due to an error that affects the coupled operation.
- SYM
- For ERRORLEVEL(SESSION) sessions, one of the following
situations caused all volumes in the session or all volumes in all
sessions in a cluster session to be suspended:
- An error or errors occurred on a coupled session or a session
in a cluster session that affects coupled operations (sympathetic
suspend). Refer to previous XRC messages, particularly ANTC8402W,
to determine the errors that occurred.
- A dump was requested for a coupled session that forced a delay
in coupled processing. If an error occurred in a coupled session,
causing the dump to be requested, the session in error can show either
a volumestatus of ERR or SYM.
- NOV
- Session is coupled but has no volumes.
- initstatus
- Recoverability status.
- Y
- Session can be recovered to a consistent time with other sessions.
- N
- Session cannot be recovered to a consistent time with other sessions.
- commandstatus
- Current command status.
- PND
- Session-level master command is pending for this session.
- CAN
- Session-level master command has been canceled for this session
by command or by error.
- (blank)
- No session-level master command is pending.
- journaldeltatime
- The time difference between the latest journaled data on this
session and the master journal time. A delta of 00:00:00.000000 indicates
that this session is the pacesetter for determining the master journal
time. A divergence in journal times with little divergence of recovery/advance
times can indicate a significantly slower primary or journal performance
than other sessions. You can reduce the window of nonrecoverable data
across the coupled sessions by addressing bottlenecks during that
session or by balancing the workload across sessions.
- =00:00:00.000000
- Session journal time is same as master journal time. This indicates
that this session is the pacesetter for the master journal/recoverable
time.
- +aa:aa:aa.aaaaaa
- Session journal time is greater than the master journal time.
This is the most common case for all active, interlocked sessions
except for the pacesetter.
- -bb:bb:bb.bbbbbb
- Session journal time is less than the master journal time.
- (blank)
- Session has established no journal time, or journal time cannot
be determined. This occurs for the following reasons:
- There are no volumes in session (volumestatus is
NOV).
- There have never been any updates to volumes in session.
- The master session recoverable time indicates NO_TIME_AVAILABLE
on message ANTQ8308I. In this case, there are no interlocked sessions.
- The session is inactive (sessionstatus is neither
ACT nor UNK).
- recoverydeltatime
- The time difference between the consistency time on this session
and the master recoverable time; it indicates the amount of data that
will need to be applied during recovery processing. This applies only
to interlocked sessions, which can be recovered to that common recoverable
time. A large recovery/advance delta can indicate a significantly
slower secondary performance than other sessions. You can reduce the
amount of data needed to be applied during recovery processing to
bring the coupled sessions to a consistent state by addressing bottlenecks
on that session or by balancing the workload across sessions. If a
master command has been executed, the delta will appear as zeros,
because recovery or advance processing does not apply updates past
the command time.
- =00:00:00.000000
- All data necessary to bring the session to a consistent time with
other coupled sessions has been applied.
- +aa:aa:aa.aaaaaa
- Amount of data to be applied during recovery processing to bring
this session to a consistent time with other coupled sessions. This
will not apply to non-interlocked sessions. If the session is idle,
this value indicates the amount of time the XRECOVER or XADVANCE command
will increase the session consistency time to indicate that the session
is in a consistent state with the master session.
- (blank)
- Session is not interlocked and therefore is not recoverable to
the master recoverable time.
System action
XRC functions are active.
System programmer response
See z/OS DFSMS Advanced Copy Services for
examples of XQUERY command output. If the command was accepted and
this message was not displayed on either the system console log or
by the user ID specified by the MSGROUTEID parameter, see message
ANTT0099I.
Source
Extended remote copy (XRC).