OA59161: New Function - Enhanced SMSHONOR Support

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• New Function - Enhanced SMSHONOR Support
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All system-managed tape users                                *
  * ( D/T3957 D/T3584 and D/TMTL ).                              *
  * This APAR extends the original SMSHONOR                      *
  * support available through the                                *
  * JCL UNIT parameter (keyword SMSHONOR)                        *
  * and the Dynamic Allocation (SVC 99) text                     *
  * unit (DALSMSHR) to the tape storage group                    *
  * construct and enablement through the SMS                     *
  * ACS routines.                                                *
  * .                                                            *
  * Though the original SMSHONOR support is                      *
  * available for JES3-managed tape devices,                     *
  * the SMSHONOR enhancement provided by                         *
  * this APAR is not available if the JES3                       *
  * subsystem is active and will be ignored.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Enable SMSHONOR through policy                               *
  * management and the SMS ACS routines.                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * For full support (z/OS V2R3 and above) APAR                  *
  * OA59161 (OAM) will bring in the support                      *
  * from SMS (OA59162) and MVS Allocation                        *
  * (OA59163).                                                   *
  ****************************************************************
  Original SMSHONOR Support
  -------------------------
  With SMSHONOR Allocation will use the list of eligible devices
  returned by SMS and the devices specified on the UNIT parameter
  and will choose a device using the intersection of the two
  lists. So, if a single device is specified, and that device is
  one of the eligible devices returned by SMS, MVS Allocation
  will allocate to the device specified. And if an esoteric is
  specified on the UNIT parameter (one or more devices), MVS
  Allocation will allocate from the intersection of the two
  lists. Devices that are not in both lists will be ignored.
  For more information on the SMSHONOR keyword, refer to z/OS
  MVS JCL Reference. Note, the behavior above can also be
  requested through the DALSMSHR text unit on a dynamic
  Allocation (SVC 99) request.
  .
  Without the use of SMSHONOR, for a system-managed tape request,
  by default, the JCL UNIT specification is ignored. This enables
  the SMS ACS routines to steer the allocation request to a set
  of eligible libraries and devices and enables MVS Allocation to
  randomize across the eligible devices. This is the preferred
  and recommended way to use the system-managed tape support.
  There may be times, however, when it is beneficial to direct an
  allocation request to a specific device or set of devices.
  This can be useful for diagnostic purposes to capture a dump
  or a trace of a failing device.
  .
  Enhanced SMSHONOR Support
  -------------------------------------------------
  With the original support discussed above, JCL or application
  changes were needed to use the support.  With this enhanced
  support, SMSHONOR can also be requested through the tape
  storage group construct and enabled through the SMS ACS
  routines.
  .
  The string "SMSHONOR=" will be searched (as part of the
  storage group description) to determine if the allocation
  request should be limited.  What follows the "=" sign can be a
  device number (3 or 4 hexadecimal digits) or a 1-8 character
  esoteric (consisting of alphanumeric, $, #, or @ characters).
  When specifying a 4-digit device number, a preceding slash (/)
  is required and is optional for a 3-digit device number.
  The string "SMSHONOR=" can appear anywhere within the
  120-character description field.
  .
  For a scratch allocation, if more than one tape storage group
  is assigned through the SMS ACS routines, usage of SMSHONOR must
  be consistent across all of the storage groups (SMSHONOR must
  then be specified for all of the assigned storage groups and
  what is specified for the value must also be consistent across
  the storage groups).
  .
  For a specific allocation, the storage group assigned to the
  volume will be checked to see if SMSHONOR is associated with
  that tape storage group.  If it is, the device or esoteric
  associated with that storage group will be used for subsequent
  allocations of that volume.
  .
  Enabling this support through SMS policies enables customers
  to use their ACS routines (and the assignment of tape storage
  groups) to then direct certain workloads to a limited set of
  devices thus leaving the full set of devices to other (perhaps
  more critical) workloads providing a device fencing capability.
  
  .
  As with the original support, MVS Allocation will then allocate
  a device using the intersection of the two lists.  Unlike the
  original support, if an issue is detected, rather than fail the
  allocation request, MVS Allocation will ignore the SMSHONOR
  request and allocate an eligible device in the storage group and
  
  return with a warning.  A new health check will also be provided
  that records these warnings.  However, if all of the devices in
  the intersected list are busy, as with
  any allocation request, it will go into allocation recovery.
  Refer to IEFA114I for the warning conditions that will be
  detected, and in those cases, the allocation will proceed with
  the eligible device pool list returned by SMS.  An SMSHONOR
  specification on the UNIT parameter will take precedence.
  .
  Unlike the original support, specification of SMSHONOR through
  SMS policies is only supported if the JES3 subsystem is not
  active. If the JES3 subsystem is active, specification of
  SMSHONOR will be ignored.  Which also means that if the JES3
  subsystem is active, and the devices are not JES3 managed,
  specification of SMSHONOR is also ignored.
  .
  Display SMS Storage Group Command
  -----------------------------------------------------------
  The DISPLAY SMS,STORGRP(xxxxxxxx),DETAIL command is enhanced
  to display the SMSHONOR-related information associated with
  a tape storage group.  The following line is displayed
  at the end of the CBR1130I message if SMSHONOR is associated
  with the specified storage group:
  SMSHONOR xxxxxxxx
  .
  SMSHONOR xxxxxxxx
  Device number or esoteric optionally specified in the
  description field of the tape storage group definition.
  If "SMSHONOR" is not specified in the description field,
  the additional line is not displayed.  Use of SMSHONOR
  limits the devices used on the allocation request.
  .
  MVS Allocation Changes
  ----------------------------------------------------------
  For details on the new MVS Allocation message IEFA114I and the
  new ALLOC_SMSHONOR_STATE health check refer to
  MVS Allocation APAR (OA59163).
  .
  Coexistence Considerations
  -----------------------------------------------------------
  There are no coexistence considerations with this support.
  If a customer has an SCDS with mixed levels of z/OS, with
  and without this support, use of the SMSHONOR specification
  in the tape storage group description will be ignored on the
  down-level systems.
  .
  CBRTVI Miscellaneous Changes
  ----------------------------------------------------------
  With Release 4.2 of the TS7700 Virtualization Engine, support
  was added for a cloud object store.  OAM had very minor changes
  (refer to OA55481).  With those changes, a new bit was added
  to indicate whether a cloud object store instance exists
  for the logical volume.  That new bit is accounted for in
  the DISPLAY SMS,VOLUME command; however, it was not accounted
  for in the CBRXLCS FUNC=QVR support (in the CBRTVI mapping
  macro). Without this new support installed, the cloud bit is
  returned in reserved space in the mapping macro.  With this
  support, we are defining the bit TVICLOUD, in the CBRTVI
  mapping macro.  This bit follows TVILWORM in the mapping.
  

Problem conclusion

Temporary fix

Comments

APAR Information

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

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

  OA59162 OA59163 UJ04134 UJ04135

Modules/Macros

• CBRBLDPS CBRLCSPL CBRSMGM1 CBRBLDPN CBRCTCPG CBRFDG   CBRSMGU1
  CBRTVI
  

Fix information

• Fixed component name

  OBJECT ACCESS M

• Fixed component ID

  5695DF180

Applicable component levels

• R240 PSY UJ04135

     UP20/10/23 P F010  

• R230 PSY UJ04134

     UP20/10/23 P F010  

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.