OA44317: AE OA42100 FIX COMPLETION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Client noticed that a single session in a clustered environment
  recovered to a different consistency time compared to the rest
  of the sessions.  This happened after an ANTC5415E cluster
  error:
  
  ANTC5415E CLUSTER ERROR FOR CLUSTER(cluster) MSESSION(msession)
  
  MHLQ(SYS1), RC=4304 REAS=0004 SRVC=5020
  

Local fix

• F ANTAS000,CREFRESH after all XRECOVER's are finished.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Extended Remote Copy (XRC)          *
  *                 XRECOVER command.                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: New functionality has been added to     *
  *                      the XRECOVER command of Extended        *
  *                      Remote Copy (XRC).                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• New functionality and documentation is described below.
  
  The following updates will be reflected in a future revision
  of the z/OS DFSMS Advanced Copy Services manual (SC23-6847):
  
  TSO Command Reference:
  
  In the XRECOVER Recovering data on the recovery system section
   the following text will be added or amended:
  
  Use the XRECOVER command to bring data on the XRC recovery
  system to a consistent, recoverable state in the event of a
  disaster to the primary system.
  
  The first command at the recovery site must be the XRECOVER
  command. You will receive a "session not active" message if you
  issue another XRC command before an XSTART or XRECOVER command
  has completed.
  
  When you issue the XRECOVER command to each individual XRC
  session, it determines the common consistency time to which all
  coupled sessions can be recovered. All appropriate updates are
  then applied to the target XRC session to reach that consistency
  time.
  
  Issue the XRECOVER command on the recovery system to complete
  the updating of all journal data to the secondary (target)
  volumes. The secondary volume serial numbers of volume pairs in
  the duplex or seqcheck state are changed to match ("clipped to")
  the primary volume serial number. The secondary volume serial
  numbers of suspended volume pairs are also clipped, provided
  that the pairs have completed initial volume synchronization
  prior to being suspended. For SESSIONTYPE(XRC), the XRC recovery
  function must continue to have access to the appropriate
  journal, control, and state data sets that were in use at the
  time of the failure, or when the XRC session ended. A migration
  session requires only the state data set.
  
  If the XRC session has either been suspended or ended normally
  by a command, and the FORCE keyword has not been specified on
  the XRECOVER command, processing will compare the internal
  timestamps of the State and Control data sets of the XRC session
  being recovered with the internal timestamps of the Master and
  Cluster data sets to ensure that the delta between them is less
  than the DEADSESSIONDELAY PARMLIB value plus 15 seconds.
  Additionally, if the XRC session is coupled, processing will
  check that the number of volumes being included in the XRECOVER
  matches the number of volumes expected to be recovered in the
  coupled/clustered environment.  The purpose of these checks
  is to ensure that the correct Control data sets are being used
  for the XRECOVER. If either of the previous two comparisons are
  unsuccessful, XRECOVER processing stops with a return code 4198
  and a report is issued indicating the failure.
  
  Next, XRECOVER applies the journaled data to update secondary
  volumes that were suspended while XRC was writing the last
  consistency group when the XRC session was active. XRC attempts
  to apply all outstanding data to the secondary volumes so that
  these volumes are consistent with the rest of the session.
  
  If the suspended volumes can be made consistent, XRC then
  changes the volume status from SUS to RCV and clips the
  secondary. If the XRC session has continued to apply consistency
  groups, then the volume will stay in SUS status. XRC relabels
  the secondary volumes to the primary volume serial numbers,
  provided that the volume pair had completed initial volume
  synchronization prior to the recovery action.
  
  You can also issue the XRECOVER command to recover a group of
  interlocked coupled sessions to the same consistency time.
  
  In order to provide master session consistency, CXRC applies
  updates to volumes on the sessions that are behind to allow them
  to advance to the forward session. CXRC will forward-recover
  volumes that are suspended because of an error and that have the
  necessary journal data available. It will not forward-recover
  volumes that are suspended because of an XSUSPEND command.
  
  Finally, the XRECOVER command automatically generates a recovery
  report. The report includes the last applied timestamp that
  defines the recovered, consistent state for all volumes. The
  XRECOVER command also automatically generates an XQUERY MASTER
  report for coupled sessions.
  
  Note: Do not issue the XRECOVER command to an active XRC
  session. If a session is active when you issue the XRECOVER
  command, XRC rejects the command. You must first issue an
  XSUSPEND or XEND command for the session, and then make all
  primary volumes offline to the SDM system. The XRECOVER command
  that follows the XSUSPEND or XEND command relabels each eligible
  secondary volume with the primary volume serial number.
  
  XRECOVER command syntax
   (Add new, optional keywords CHECK and FORCE to the second line
  of the command syntax.)
  
  Optional parameters:
  CHECK Specifies that only XRECOVER Enhanced Checking is to be
  executed and XRECOVER CHECK report will be issued.
  This keyword is mutually exclusive with the FORCE keyword.
  
  FORCE Specifies that the XRECOVER Enhanced Checking is to be
  skipped.
  This keyword is mutually exclusive with the CHECK keyword.
  
  XRECOVER command example
   (Add the following XRECOVER examples):
   XRECOVER session CHECK
   XRECOVER session FORCE HLQ(SYS1) MHLQ(MSESSHLQ)
  
  ANTRQST Command Reference section:
  
  REQUEST=XRECOVER
  FORCE=YES|NO
     is the name (RS-type), or address in
     register (2)-(12), of an optional 3
     character input field containing a keyword
     that indicates whether or not to bypass
     CHECK processing.  The value is left
     justified and padded on the right with
     blanks.  If the field contains binary
     zeros the default will be taken.  Coding
     FORCE=YES is mutually exclusive with
     the CHECK=YES keyword.
  
     NO indicates that enhanced consistency
     checking will take place.
  
     YES indicates that enhanced consistency
     checking will be bypassed.
  
     DEFAULT: NO
  
  CHECK=YES|NO
     is the name (RS-type), or address in
     register (2)-(12), of an optional 3
     character input field containing a keyword
     that indicates if an XQUERY  XRECOVER_CHECK
     report should be generated and XRECOVER
     processing skipped.
     The value is left justified and padded on
     the right with blanks.  If the field
     contains binary zeros the default will be
     taken.  Coding CHECK=YES is mutually
        exclusive with the FORCE=YES keyword.
  
        NO indicates that report will not be
        produced.
  
        YES indicates that report will be
        produced.
        DEFAULT: NO
  
  ANTXREXX Command Reference section:
  
  XRECOVER (XRC recover)
  FORCE(YES|NO)
     is the name of an optional CHAR(3) input
     field containing a keyword that indicates
     whether or not to bypass CHECK processing.
     The value is left justified and padded on
     the right with blanks.  If the field
     contains binary zeros the default will be
     taken.  FORCE(YES) is mutually
     exclusive with CHECK(YES).
  
     NO indicates that enhanced consistency
     checking will take place.
  
     YES indicates that enhanced consistency
     checking will be bypassed.
  
     DEFAULT: NO
  
  CHECK(YES|NO)
     is the name of an optional CHAR(3) input
     field containing a keyword that indicates
     if an XQUERY XRECOVER_CHECK report
     should be generated and XRECOVER
     processing skipped.
     The value is left
     justified and padded on the right with
     blanks.  If the field contains binary
     zeros the default will be taken. CHECK(YES)
     is mutually exclusive with FORCE(YES).
  
     NO indicates that report will not be
     produced.
  
     YES indicates that report will be
     produced.
  
     DEFAULT: NO
  
  
  The following updates will be reflected in a future revision
  of z/OS MVS System Messages, Volume 1(ABA-AOM)(SA38-0668):
  
  In the ANT messages chapter add the following new messages:
  
  ANTQ8276I SOURCE    -------TIMESTAMP--------  -----DELTA-----
  Explanation: This message provides the XRECOVER CHECK report
  header information. This header message is associated with
  ANTQ8225I, ANTQ8226I, ANTQ8227I and ANTQ8228I. The details of
  the fields are provided by ANTQ8226I.
  Source: Extended remote copy (XRC).
  System action: XRC functions are active.
  System programmer response: None.
  
  ANTQ8226I session_id   timestamp  delta  *(or)blank
  Explanation: This message provides the output associated with
  the header lines produced by message ANTQ8276I
  for the XRECOVER CHECK report.
  session_id -
  The name of XRC session, Master session, Cluster session or data
  set that produced the timestamp being reported.
  timestamp -
  The current date and time of the data set being reported.
  Format is: yyyy.ddd hh:mm:ss.pppppp
  delta -
  The time delta between the State data set of the XRC session
  being recovered and the data set being reported.
  Format is:  hh:mm:ss.pppppp
  * or blank -
  If the time delta between the XRC State data set and the data
  set being reported is greater than the DEADSESSIONDELAY plus 15
  seconds, an asterisk (*) will be displayed at the end of this
  message indicating that this is the reason for the XRECOVER
  CHECK failure.  Message ANTQ8227I reports the value for
  DEADSESSIONDELAY plus 15 seconds.
  Source: Extended remote copy (XRC).
  System action: XRC functions are active.
  System programmer response: None.
  
  ANTQ8225I SESSION/MASTER/CLUSTER NAME(session_id)
     HLQ/MHLQ(hlq/mhlq value) sessiontype/blank
  Explanation: This message provides sub-header information for
  the ANTQ8226I detail message of the XRECOVER_CHECK report.
  SESSION indicates that this header is for the XRC session being
  recovered.  MASTER indicates that this header is for the Master
  session associated with the XRC session being recovered.
  CLUSTER indicates that this header is for the Cluster session
  associated with the XRC session being recovered. HLQ reports the
  high level qualifier of the XRC session being recovered.  MHLQ
  reports the high level qualifier of the Cluster or Master
  session associated with the XRC session being recovered.
  session_id -
  The name of the XRC session, Master session, or Cluster session
  being reported.
  hlq/mhlq value -
  The high level qualifier of the XRC session or Master/Cluster
  session being reported.
  sessiontype/blank -
  If the SESSION insert is included in the message, the type of
  XRC session (XRC/MIGRATE) will be included.
  Source: Extended remote copy (XRC).
  System action: XRC functions are active.
  System programmer response: None.
  
  ANTQ8227I DEADSESSIONDELAY+15(value)
  Explanation: This message provides additional summary
  information for the XRECOVER CHECK report.
  value -
  This field reports the value of the DEADSESSIONDELAY PARMLIB
  entry plus 15 seconds.
  Source: Extended remote copy (XRC).
  System action: XRC functions are active.
  System programmer response: None.
  
  ANTQ8228I SESSION VOLUMES=session_volume_count COUPLED
     VOLUMES=coupled_volume_count   *(or)blank
  Explanation: This message provides additional summary
  information for the XRECOVER CHECK report.
  session_volume_count -
  The volume count from the current XRC session.
  coupled_volume_count -
  The number of volumes expected to be recovered.  This count
  comes from the Cluster or Master data set.
  * or blank -
  If the comparison between the session_ and coupled_volume_count
  is different, an asterisk (*) will be displayed at the end of
  this message  indicating that this is the reason for the
  XRECOVER CHECK failure.
  Source: Extended remote copy (XRC).
  System action: XRC functions are active.
  System programmer response: None.
  
  ANTR8125I XRECOVER CHECK ENDED FOR SESSION(session_id) WITH
     HLQ(hlq)
  Explanation: This message provides sub-header information for
  the ANTQ8226I detail message of the XRECOVER_CHECK
  report.
  session_id -
  The XRC session that the XRECOVER command was issued to.
  hlq -
  The high level qualifier for the XRC session that the XRECOVER
  command was issued to.
  Source: Extended remote copy (XRC).
  System action: XRC functions are active.
  System programmer response: None.
  
  
  In the SDM Return Codes section add the following NEW return and
  reason codes:
  
  4197 A failure occurred during XRECOVERs Enhanced Checking
  preventing further processing.
  Possible errors include allocation failure or volume count
  processing error.
  
  4198 During XRECOVER processing, one of two comparisons failed.
  The reason for the
  failure is indicated in the XRECOVER_CHECK report.
  The following are the reason codes indicated with this return
  code:
  Reason Code     Description
   1  XRC session was not coupled
   2  XRC session was coupled
  
  4199 The System Data Mover attempted to retrieve a list of data
  mover sessions from a storage subsystem, but received invalid
  data.
  KEYWORDS: D/T2105 D/T2107 XRC/K
  KEYWORDS: D/T2105 D/T2107 XRC/K
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  OA42100

• APAR is sysrouted TO one or more of the following:

  UA72319 UA72320

Modules/Macros

• ANTCVXIT ANTCVXPR ANTCVXT2 ANTS4007 ANTS4017 ANTS4925 ANTTREXA
  ANTXIQRY ANTXIRCV ANTXISTA ANTXJRIN ANTXSMID
  

Fix information

• Fixed component name

  SYSTEM DATA MOV

• Fixed component ID

  5695DF117

Applicable component levels

• RD10 PSY UA72008

     UP14/02/28 P F402

• R210 PSY UA72009

     UP14/02/28 P F402

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.