ANTQ8213I
prim_vol sec_vol errorlevel synch_% sta cmd op timestamp

Explanation

This message provides the output associated with the header lines produced by messages ANTQ8211I and ANTQ8212I for the XQUERY command requesting a volume report.
prim_vol –
The primary volume serial being reported.
sec_vol –
The secondary volume serial being reported.
errorlevel –
The error level for the primary and secondary volume pair. For each volume pair reported, the error level is either explicitly specified on a previous XADDPAIR command, or defaulted from the XSTART command for the session. The valid values in this field are:
  • VOLUME – Volume-level recovery
  • SESSION – Session-level recovery
  • (group_name) – Group-level recovery
  • (blank) – No error level for the volume (such as a utility volume)
synch_% –
Provides the approximate percentage of the volume pair that has completed synchronization or resynchronization. For example, a volume pair that is reported with synch_% of 80% means that 80% of the data on the secondary volume is synchronized with the primary volume at the reported session consistency time. Thus, 20% of the data must be copied in order to place the volume pair in a fully synchronized state.
This field can contain any of the following:
  • nn – Where nn ranges from 00 to 99. This is the approximate percentage of the volume pair that is synchronized. If nn is 00, the volume synchronization process can not yet have started. If the percentage does not change as expected on subsequent XQUERY commands, it can be because the storage control has exceeded its internal threshold value and has temporarily stopped the copy activity. When the activity level again falls below the threshold value (default of X'500'), the storage control resumes processing the volume copy.
  • ** – A synch percentage cannot be determined because of one of the following conditions:
    • There was a prior suspension before the volume pair reached duplex
    • None of the volume pairs in this session were updated since the pair reached duplex
    • A previously canceled session was restarted and the consistency time for previously duplex volume pairs (which are now suspended because of a restart of the session) cannot be determined.
  • (blank) – The volume pair is in duplex or seqcheck state. The volume pair is completely synchronized and consistent as of the reported session consistency time.
  • "--" – The field is not applicable to this volume pair.
sta –
The current status information associated with the volume pair. The valid status states are:
  • cpy – The conditions that can pause volume synchronization or resynchronization are met according to the values of HaltThreshold and HaltAnyInit for the session. When the residual count is below the HaltThreshold value, the volume synchronization or resynchronization will resume for the volume, and the volume status will be changed to CPY. See z/OS DFSMS Advanced Copy Services for the explanations of HaltThreshold and HaltAnyInit.
  • CPY – Copy. Volume pair being synchronized or re-synchronized.
  • DUP – Duplex. Volume pair in duplex state at time of report.
  • NIS – Not in session. Volume pair is not part of the session.
  • pnd – The conditions that can pause pending volume synchronization or resynchronization are met according to the values of HaltThreshold and HaltAnyInit for the session. When the residual count is below the HaltThreshold value, the pending volume synchronization or resynchronization will resume for the volume, and the volume status will be changed to PND. See z/OS DFSMS Advanced Copy Services for the explanations of HaltThreshold and HaltAnyInit.
  • PND – Pending. Volume pair waiting to be synchronized or re-synchronized.
  • RCV – Recovered. Volume pair has been successfully recovered.
  • RST – Restarted. Volume pair is scheduled for resynchronization because of a recoverable error.
  • SUS – Suspended. Volume pair is suspended.
  • SEQ – Seqcheck. Volume pair can be inconsistent relative to other volume pairs on different storage controls.
  • UTL – Utility volume. Volume is used as a path to the storage control.
  • * – Blocked. An asterisk appended to the value in the sta field indicates that the specified primary volume is currently being blocked. Request a detail volume report for additional information about the blocking status.
cmd –
The latest pending command issued for the volume pair. The pending command is not executed until the time specified in the timestamp field is reached. This field can contain any of the following:
  • (blank) – No pending command for the volume pair.
  • DEL – Pending XDELPAIR command for the volume pair.
  • SUS – Pending XSUSPEND command for the volume pair.
op –
The keyword option selected when the cmd was issued for this volume pair. This field can contain any of the following:
  • (blank) – No pending time for the volume pair.
  • AT – Pending ATTIME time for the volume pair.
  • DR – Pending DRAIN time for the volume pair.
  • IM – Pending IMMEDIATE time for the volume pair.
timestamp –
The time associated with the volume pair. The interpretation of the timestamp field is based upon a combination of the status and command fields described below. The timestamp is always a universal time, coordinated (UTC) format associated with the application systems connected to the primary storage controls. The field is not a data mover system timestamp. The timestamp field can be any of the following:
  • (blank) – There are no outstanding commands pending for the volume pair. If the volume pair is in DUP state, the volume pair is consistent up to the session-specified timestamp reported in message ANTQ8231I.
  • (timestamp) – The timestamp reported is given in UTC format. If the volume pair has a status of SUS, the data on the suspended volume pair is consistent up to the time reported. If the volume pair has a pending command (indicated by a command in the cmd field), the timestamp reported is the target time for the pending command.
  • NO_TIME_AVAILABLE – A consistency time for this suspended volume pair cannot be determined because of one of the following reasons:
    • There was a prior suspension before the volume pair reached duplex
    • None of the volume pairs in this session has been updated since the pair reached duplex
    • A previously canceled session was restarted and the consistency time for previously duplex volume pairs (which are now suspended because of restart of the session) cannot be determined.

System action

XRC functions are active.

System programmer response

The information reported by the XQUERY command is provided for the volumes requested by the command. It is point-in-time information based on the volume status at the time the command processes the volume. See z/OS DFSMS Advanced Copy Services for examples of XQUERY command output. If the command has been accepted and this message has not been displayed either at the system console log or at the user ID specified by the MSGROUTEID parameter, see message ANTT0099I.

Source

Extended remote copy (XRC).

Parent topic: ANT messages