PK67755: ENHANCEMENTS TO THE DB2 SUBSYSTEM ANALYSIS AND SETUP PROCESSING

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This APAR will add the following enhancements:
  
  1) Message ARYR014E text does not display the correct
  information for backup methods
  
  If an invalid backup method is input from the DB2 Subsystem
  Analysis and Setup part of RE, the text for error message
  
  ARYR014 E is:
  
  ARYR014E -Invalid value. Backup method should be (I)bm, (E)mc,
  (F)lash or (D)b2.
  
           It should be:
  ARYR014E -Invalid value. Backup method should be (B)cv, (S)nap,
  (F)lash or (D)b2.
  
          The help panel for this error is also incorrect.
  
  2) Subsystem Setup Information panel ARY#SSID always displays a
  value for Analysis Recommended: Y even when it is N
  
  3) MVS User Catalog not identified correctly in subsystem
  analysis when multi-level alias is being used When a MVS system
  has multi-level alias active, and the DB2 system has a BSDS,
  active log, or an archive log that is using a multi-level alias,
  RE is not properly identifying the MVS user catalog associated
  with those datasets in both the subsystem analysis, and the
  validation of the system backup.
  
  4) BSDS not updated when renaming active logs while the DB2
  subsystem was inactive When going to Subsystem Setup Information
  for a DB2 subsystem that is active, the online panels allow you
  to rename the BSDS. and then doesn't change the name or give an
  error message. Just the message "no rows to display" where we
  should have seen the output of the BSDS update jobs.
  
  5) Not all data sharing members are automatically stopped when
  moving DB2 data If the DB2 data is moved from one volume to
  another on a data sharing system, the generated JCL has a step
  to stop the DB2 SSID but not the other SSID's of the data
  sharing group. Since the other member were not stopped, the job
  failed when it tried to move the DB2 directory data sets.
  
  6) Alter STOGROUP generated incorrectly when moving DB2 data to
  a SMS managed target volume
  
  7) Volumes listed as in a SMS pool when they are not SMS managed
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Recovery Expert for Z/OS.       *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR will add the following        *
  *                      enhancements:                           *
  *                      1. Message ARYR014E text does not       *
  *                      display the correct information for     *
  *                      backup methods. If an invalid backup    *
  *                      method is input from the DB2 Subsystem  *
  *                      Analysis and Setup part of RE, the      *
  *                      text for error message.                 *
  *                      ARYR014 E is:                           *
  *                      ARYR014E -Invalid value. Backup method  *
  *                      should be (I)bm, (E)mc, (F)lash or      *
  *                      (D)b2.                                  *
  *                      It should be:                           *
  *                      ARYR014E -Invalid value. Backup method  *
  *                      should be (B)cv, (S)nap, (F)lash or     *
  *                      (D)b2.                                  *
  *                      2. Subsystem Setup Information panel    *
  *                      ARY#SSID always displays a value for    *
  *                      Analysis Recommended: Y even when it    *
  *                      is N.                                   *
  *                      3. MVS User Catalog not identified      *
  *                      correctly in subsystem analysis when    *
  *                      multi-level alias is being used When a  *
  *                      MVS system has multi-level alias        *
  *                      active, and the DB2 system has a BSDS,  *
  *                      active log, or an archive log that is   *
  *                      using a multi-level alias, RE is not    *
  *                      properly identifying the MVS user       *
  *                      catalog associated with those datasets  *
  *                      in both the subsystem analysis, and     *
  *                      the validation of the system backup.    *
  *                      4. BSDS not updated when renaming       *
  *                      active logs while the DB2 subsystem     *
  *                      was inactive When going to Subsystem    *
  *                      Setup Information for a DB2 subsystem   *
  *                      that is active, the online panels       *
  *                      allow you to rename the BSDS. and then  *
  *                      doesn't change the name or give an      *
  *                      error message. Just the message         *
  *                      "no rows to display" where we should    *
  *                      have seen the output of the BSDS        *
  *                      update jobs.                            *
  *                      5. Not all data sharing members are     *
  *                      automatically stopped when moving DB2   *
  *                      data If the DB2 data is moved from one  *
  *                      volume to another on a data sharing     *
  *                      system, the generated JCL has a step    *
  *                      to stop the DB2 SSID but not the other  *
  *                      SSID's of the data sharing group. Since *
  *                      the other member were not stopped, the  *
  *                      job failed when it tried to move the    *
  *                      DB2 directory data sets.                *
  *                      6. Alter STOGROUP generated incorrectly *
  *                      when moving DB2 data to a SMS managed   *
  *                      target volume.                          *
  *                      7. Volumes listed as in a SMS pool      *
  *                      when they are not SMS managed.          *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

• APPLY the PTF.
  

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:

Modules/Macros

• ARY#OBEX
  

Fix information

• Fixed component name

  DB2 REC EXPERT

• Fixed component ID

  5697H7400

Applicable component levels

• R210 PSY UK38633

     UP08/08/07 P F808

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.