OA33022: NEW FUNCTION - V1R13 TOLERATION

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• new function
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: OAM object support customers.                *
  ****************************************************************
  * PROBLEM DESCRIPTION: APAR OA33022 provides coexistence       *
  *                      support to allow systems at z/OS V1R10  *
  *                      (HDZ1A10) and above to coexist in an    *
  *                      OAMplex with a z/OS V1R13 (HDZ1D10)     *
  *                      level system. This APAR is required on  *
  *                      the lower level systems to tolerate new *
  *                      support introduced in z/OS V1R13, or    *
  *                      for backout of the new function.        *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• KEYWORDS: R13COEXS/K ZOS0201C/K ZOS0202C/K
  

Temporary fix

Comments

• This APAR enables pre-V1R13 level systems to coexist in an
  OAMplex with one or more members at the V1R13 level.
  This PTF needs to be installed prior to bringin a V1R13 level
  system into the OAMplex. This PTF should be installed even if
  new function introduced in R13 is not exploited.
  
  There are 2 new features introduced in OAM in V1R13 that
  necitate coexistence PTFs be applied to pre-V1R13 level
  systems:  (1) Disk sublevel support, and (2) extended
  expiration criteria.
  
  (1) Disk Sublevel Support
  In z/OS V1R13, OAM expanded the its storage hierarchy to
  include a new disk sublevel. Disk Sublevel 1 (DSL1) consists
  of traditional OAM/DB2 tables, and Disk Sublevel 2 (DSL2)
  consists of a new zFS or NFS file system level.
  
  Pre-V1R13 level systems have no concept of Disk Sublevel 2.
  
  The OAM Sublevel parameter of the SMS Storage Class definitions
  is ignored on pre-V1R13 level systems when the SMS Storage Class
  is pointing to DISK (ie: Initial Access Response Seconds  value
  is 0). In other words, the same Storage Class that results in a
  given object being written to the file system sublevel on z/OS
  V1R13, will result in the object being written to the DB2
  sublevel on a pre-V1R13 level system.
  
  - DSL1 equates to the Disk Sublevel 1 tier of the OAM storage
  hierarchy where the object data resides in DB2, and
  - DSL2 equates to the Disk Sublevel 2 tier of the OAM storage
  hierarchy where the object data resides in file system.
  
  Primary objects that already reside in or are recalled to DSL2
  will not be accessible from the pre-V1R13 systems. Therefore
  the following outlines the expected behavior of pre-V1R13
  systems relative to objects that reside in DSL2 (ODLOCFL='E'
  or ODLOCFL='2'):
  
  ================================================================
  FUNCTION          BEHAVIOR ON PRE-V1R13 LEVEL SYSTEM
  ================================================================
  - OSREQ STORE:  Object stored to DSL1 (DB2)
                  (Note: pre-V1R13 level systems do not
                   recognize the OAM Sublevel parameter of the
                   SMS Storage Class construct when the Storage
                   Class is associated with the OAM Disk tier.
                   Therefore, any Storage Class definition
                   associated to the OAM Disk tier defaults to
                   DSL1 (DB2) on a pre-V1R13 level system).
  
  - OSREQ RETRIEVE:  View=Primary: Fails 80xx0100
                     View=Backup|Backup2:  Successful
  
  - OSREQ QUERY:  Successful but Estimated Retrieval Time = -1
  
  - OSREQ CHANGE:  Fails 80xx0100
  
  - OSREQ DELETE:  Fails 80xx0100
  
  - OSMC Storage Group Cycle:
  (Includes Backups,
  Transitions,Expiration):  DSL2 objects skipped w/ CBR9225I,
                            objects with valid locations are
                            processed.
  
  - OSMC DASD Space Manager: DSL2 objects skipped w/ CBR9225I,
                             objects with valid locations are
                             processed.
  
  - OSMC Move Volume Utility:  MOVEVOL of backup and primary
                               volumes is successful.
  
  - OSMC Object Recovery:  Fails w/ CBR9842I
  
  - OSMC Volume Recovery:  There is no change in Volume Recovery
                           processing of primary volumes (volser
                           in ODLSLOC column of object directory).
  
                           Volume Recovery of backup volumes
                           (volser in ODBKLOC or ODBK2LOC) are
                            processed as follows:
                            -- If a previous primary copy of the
                               object does not exist on tape or
                               optical (ie: ODLSLOC is blank) then
                               DSL2 objects skipped w/ CBR9225I.
                               Objects with valid locations are
                               processed.
                            -- If a previous primary copy of the
                               object does exist on tape or
                               optical ie: ODLSLOC is non-blank,
                               then DSL2 objects are recovered to
                               a new backup volume from the volume
                               in ODLSLOC.
  
  - Object Recall to Disk RECALL: is not initiated for objects
                                  with invalid locations.
                                  (Note1: direct OSREQ RETRIEVE
                                   of DSL2 objects will fail and
                                   therefore no RECALL will be
                                   scheduled.
                                   Note2: A successful OSREQ
                                   RETRIEVE w/ VIEW=BACKUP|BACKUP2
                                   of a DSL2 object could result
                                   in RECALL being scheduled, but
                                   the RECALL will be failed w/
                                   CBR9890I.)
  
  - OSMC Write to DSL2
  (ie: transitions or recalls):  OSMC will write to DSL1 (DB2).
                                 (Note: pre-V1R13 level systems
                                  do not recognize the OAM
                                  Sublevel parameter of the SMS
                                  Storage Class construct when
                                  the Storage Class is associated
                                  with the OAM Disk tier.
                                  Therefore, any Storage Class
                                  definition associated to the OAM
                                  Disk tier defaults to DSL1 (DB2)
                                  on a pre-V1R13 level system).
  ================================================================
  ================================================================
  (2) In z/OS V1R13, OAM also supports the new expanded values
  for SMS Management Class expiration criteria. Pre-V1R13
  Management Class values for expiration criteria of 9999 days
  are expanded to 93000 days in V1R13.
  
  On z/OS V1R13 level systems, this line item:
  - increases the expiration criteria associated with an SMS
  Management Class from 9999 to 93000
  - increases the max valid value of the OSREQ RETPD keyword
  from  32767 to 93000
  - increases the max valid value of the OSREQ EVENTEXP keyword
  from 32767 to 93000
  
  On pre-V1R13 level systems:
  - the expiration criteria associated with an SMS Management
  Class remains at 9999
  - the max valid value of the OSREQ RETPD keyword remains
  at 32767
  - the max valid value of the OSREQ EVENTEXP keyword remains
  at 32767
  
  This implies that an SMS Management Class can be defined in
  ISMF on a z/OS V1R13 system with an expiration criteria of
  93000 days from create.  Objects processed using this
  Management Class on a V1R13 level system will use the 93000
  expiration criteria, however, if an object is processed using
  this same Management Class on a pre-V1R13 level system; the
  expiration criteria will be interpreted as 9999 days from
  create.
  ================================================================
  

APAR Information

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

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

  UA59506 UA59507 UA59508 OA36331

Modules/Macros

• CBRCPSED CBRCTCB  CBRHDASD CBRHDDEL CBRHOBJP
  CBRHOPCB CBRHORCL CBRHRCVR CBRHROUT CBRHSMSI CBRICHA  CBRIDEL
  CBRIQUE  CBRIRET  CBRPCB   CBRSMES9 CBRSMGM9 CBRSMGU9
  

Fix information

• Fixed component name

  OBJECT ACCESS M

• Fixed component ID

  5695DF180

Applicable component levels

• RA10 PSY UA59506

     UP11/04/22 P F104

• RB10 PSY UA59507

     UP11/04/22 P F104

• RC10 PSY UA59508

     UP11/04/22 P F104

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.