IBM Support

PI50592: DB2 ADMIN NEW FUNCTION TO ALLOW CM BATCH TO OPERATE AGAINST MULTIPLE CHANGES AT ONCE.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • DB2 ADMIN NEW FUNCTION TO ALLOW CM BATCH TO OPERATE AGAINST
    MULTIPLE CHANGES.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the DB2 Administration and DB2      *
    *                 Object Comparison Tool for z/OS who          *
    *                 want to use the Change Management            *
    *                 Batch (CM Batch) interface to analyze        *
    *                 and run multiple target changes.             *
    ****************************************************************
    * PROBLEM DESCRIPTION: Prior to this enhancement, the multi-   *
    *                      target function has the ability to      *
    *                      import a change onto multiple target    *
    *                      systems in one instance.  However,      *
    *                      in order to apply each of these         *
    *                      changes to the target system            *
    *                      catalogs, the changes need to be        *
    *                      "analyzed" and "run" one at a time.     *
    *                                                              *
    *                      The purpose of this enhancement         *
    *                      is to enable Analyze or Run of a        *
    *                      multi-target change via CM batch.       *
    *                      This will pick up all target changes    *
    *                      registered on the local subsystem       *
    *                      for analysis or run where the           *
    *                      multi-target change also resides.       *
    *                      Target changes that do not reside       *
    *                      on the local subsystem will be          *
    *                      skipped for processing.                 *
    *                                                              *
    *                      After completion of the multi-target    *
    *                      analyze or run process, a report        *
    *                      will be generated to show a summary     *
    *                      of successful or failed target          *
    *                      changes. Changes will be displayed      *
    *                      in the following two categories:        *
    *                                                              *
    *                      1. Successful entries:                  *
    *                                                              *
    *                         Includes all successful changes.     *
    *                         STATUS=ANALYZED for the Analyze      *
    *                         process and STATUS=COMPLETE          *
    *                         for the Run process.                 *
    *                                                              *
    *                      2. Skipped, Failed or Running entries   *
    *                                                              *
    *                          Includes all unsuccessful changes.  *
    *                          In case of failure, the DD card     *
    *                          containing more details will be     *
    *                          displayed.                          *
    *                                                              *
    *                      Another report is also generated to     *
    *                      display the change statements as        *
    *                      registered for the multi-target change. *
    *                      This is an optional report that is      *
    *                      written out into "STMTRPT" DD within    *
    *                      CM Batch job ADBCMBAT when the user     *
    *                      specifies the following CM batch        *
    *                      parameter:                              *
    *                                                              *
    *                      "display_mtc_statements"                *
    *                                                              *
    *                      The display_mtc_statements parameter    *
    *                      specifies whether the change            *
    *                      statements registered for multi-target  *
    *                      changes are displayed when analyzing    *
    *                      and running of a multi-target change.   *
    *                                                              *
    *                      Note: These are the change statements   *
    *                      on the central system where a multi-    *
    *                      target change is registered. On each    *
    *                      target system, these statements will    *
    *                      have variations based on masks applied. *
    *                                                              *
    *                      Values:                                 *
    *                      Y Display the multi-target change       *
    *                        statements                            *
    *                      N Do not display the multi-target       *
    *                        change statements.                    *
    *                                                              *
    *                      Default:                                *
    *                      N                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Prior to this enhancement, the multi-target function has the
    ability to import a change onto multiple target systems in
    one instance.  However, in order to apply each of those changes
    to the target system catalogs, the changes need to be
    "analyzed" and "run" one at a time.
    
    The purpose of this enhancement is to enable Analyze or
    Run of a multi-target change via CM batch.  This will pick
    up all target changes registered on the local subsystem
    for analysis or run where the multi-target change also
    resides.  Target changes that do not reside on the local
    subsystem will be skipped for processing.
    
    After completion of multi-target analyze or run process, a
    report will be generated to show a summary of successful or
    failed target changes. Changes will be displayed in the
    following two categories:
    
    1. Successful entries:
    
       Includes all successful changes. STATUS=ANALYZED for the
       Analyze process and STATUS=COMPLETE for the Run
       process.
    
    2. Skipped, Failed or Running entries:
    
        Includes all unsuccessful changes. In case of failure,
        the DD card containing more details will be displayed.
    
    Another report is also generated to display the change
    statements as registered for the multi-target change.
    This is an optional report that is written out into "STMTRPT"
    DD within CM Batch job ADBCMBAT when the user specifies
    the following CM batch parameter:
    
    "display_mtc_statements"
    
    The display_mtc_statements parameter specifies whether
    the change statements registered for multi-target changes
    are displayed when analyzing and running of a multi-target
    change.
    
    Note: These are the change statements on the central
    system where a multi-target change is registered. On each
    target system these statements will have variations based
    on masks applied.
    
    Values:
    Y Display the multi-target change statements.
    N Do not display the multi-target change statements.
    
    Default:
    N
    

Problem conclusion

Temporary fix

Comments

  • Enhancements are delivered.
    ×**** PE15/12/08 PTF IN ERROR. SEE APAR PI53708  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PI50592

  • Reported component name

    DB2 ADMIN TOOL

  • Reported component ID

    568851500

  • Reported release

    B20

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-10-15

  • Closed date

    2015-10-26

  • Last modified date

    2016-02-02

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

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

    UI32385

Modules/Macros

  •    ADBCCM   ADBCMBAT ADBCMBSS ADB2000  ADB9000
    

Fix information

  • Fixed component name

    DB2 ADMIN TOOL

  • Fixed component ID

    568851500

Applicable component levels

  • RB20 PSY UI32385

       UP15/10/29 P F510

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCVQTD","label":"IBM Db2 Administration Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
02 February 2016