OA62126: AFTER APPLYING OA60030 CUSTOMERS CAN SEE THAT HSM IS PERFORMING AUTO FUNCTIONS ON LPARS THAT ARE NOT SUPPO 22/03/11 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• With OA60030 applied lpars that are explicitly defined in the
  SMS base configuration can be chosen to perform sysplex auto
  functions(Migration/Backup/Dump) that they shouldn't be
  performing.
  
  KNOWN IMPACT:
  HSM auto functions(Migration/Backup/Dump) could run on
  unexpected system in the SMSPlex.
  
  PE INFORMATION:
  USERS AFFECTED:
  Customers that have PTFs for OA60030 apllied.
  R240 PSY UJ04369 UP20/12/07 P
  R230 PSY UJ04368 UP20/12/07 P
  
  USER IMPACT:
  APAR OA60030 introduced a new problem.  HSM auto functions
  (Migration/Backup/Dump) could run on unexpected systems in the
  SMSPlex.  The code was previously working correctly and as
  documented in z/OS DFSMSdfp Storage Administration. Chapter 4.
  Under the title Migrate, Backup, and Dump Sys/Sys Group Name.
  Here's an excerpt of that info:
  DFSMShsm has the capability of processing each storage group for
  automatic space management, data availability management, and
  automatic dump processing. A system is eligible to perform
  processing when any of the following are conditions are met:
  - The name is blank, meaning any system can perform it.
  - The name specified is the name of the specific host system.
  - The name specified is the name of the system group to which
  the system belongs and the system is not individually defined
  by its system name in the configuration.
  DFSMShsm ignores storage groups for which you specify a
  different system name, and does not process DASD volumes that
  have already been processed. Do not specify a Sys/Sys Group Name
  unless processing of the storage group for the function must be
  performed only on that one host because that limits the
  capabilities of DFSMShsm to perform the request.
  

Local fix

• Contact HSM Level 2 for bypass instructions.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All DFSMShsm V2R3 and later who                              *
  * use both SYSTEM and SYS GROUP in their                       *
  * STORGRPs to determine where automatic                        *
  * DFSMShsm processing takes place.                             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Clients who use SYS GROUP in their                           *
  * STORGRP definitions incorrectly                              *
  * get automatic processing on SYSTEMs                          *
  * whose name is part of the SYS GROUP                          *
  * when both SYSTEM and SYS GROUP are                           *
  * specified in STORGRPs.                                       *
  *                                                              *
  * Using the example figure in                                  *
  * z/OS DFSMSdfp Storage Administration,                        *
  * SC23-6860-50, Chapter 1,                                     *
  * System grouping section, "sys1" was                          *
  * defined to run automatic backup for                          *
  * one STORGRP and "Maui" for other                             *
  * STORGPs.  The expectation was that                           *
  * the "Maui" STORGRPs would be backed                          *
  * up on "sys2" and "sys3," but                                 *
  * "sys1," "sys2," and "sys3" all                               *
  * backup "Maui's" STORGRPs.                                    *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Automatic Migration, Primary Space Management, Interval
  Migration, Automatic Backup, and Automatic Dump functions
  which use SYS GROUP in STORGRP definitions may have those
  functions performed in SYSTEMs which are specified in
  other STORGRPs.
  

Problem conclusion

• DFSMShsm has been modified to resolve the problem.
  

Temporary fix

• *********
  * HIPER *
  *********
   ****  HIPER  ******
  Apply ++APAR
  

Comments

APAR Information

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

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

  UJ07975 UJ07976 UJ07977

Modules/Macros

• ARCSMSVM
  

Fix information

• Fixed component name

  DFSMSHSM, ISMF

• Fixed component ID

  5695DF170

Applicable component levels

• R250 PSY UJ07977

     UP22/04/01 P F203 ­

• R240 PSY UJ07976

     UP22/04/01 P F203 ­

• R230 PSY UJ07975

     UP22/04/01 P F203 ­

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.