IBM Support

PI42007: ENHANCE DSNTWLMB AND DSN_WLM_APPLENV TO REMOVE WLM AE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Enhance DSNTWLMB and DSN_WLM_APPLENV to remove WLM AE
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 11 for z/OS users of the             *
    *                 DB2-supplied stored procedure                *
    *                 SYSPROC.DSN_WLM_APPLENV or the               *
    *                 batch program DSNTWLMB.                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: SYSPROC.DSN_WLM_APPLENV and DSNTWLMB    *
    *                      have the capability to add a WLM        *
    *                      application environment to an existing  *
    *                      WLM service definition, but do not      *
    *                      have the capability to remove a WLM     *
    *                      application environment.                *
    ****************************************************************
    * RECOMMENDATION: Apply PTF                                    *
    ****************************************************************
    SYSPROC.DSN_WLM_APPLENV and DSNTWLMB are enhanced to support
    the removal of a WLM application environment from an
    existing WLM service definition and install the modified
    service definition, with a further option to activate it.
    

Problem conclusion

Temporary fix

Comments

  • SYSPROC.DSN_WLM_APPLENV and DSNTWLMB are enhanced to support
    the removal of a WLM application environment from an
    existing WLM service definition and install the modified
    service definition, with a further option to activate it.
    
    To remove a WLM application environment using DSNTWLMB,
    set the ACTION parameter to REMOVE or REMOVE_IF_EXISTS
    or REMOVE_ACTIVATE or REMIFEXISTS_ACTIVATE, and set the
    SYSIN WLMNAME parameter to the name of the WLM application
    environment to be removed. If REMOVE_ACTIVATE or
    REMIFEXISTS_ACTIVATE is specified, set the POLICY parameter
    to the service policy to be activated or to 'ACTIVE' if the
    current active service policy is used.
    
    To remove a WLM application environment using DSN_WLM_APPLENV,
    set the input ACTION parameter to REMOVE or REMOVE_IF_EXISTS
    or REMOVE_ACTIVATE or REMIFEXISTS_ACTIVATE, and set the WLMNAME
    option in the input WLMOPTIONS parameter to the name of the
    WLM application environment to be removed. If REMOVE_ACTIVATE
    or REMIFEXISTS_ACTIVATE is specified, set the input POLICYID
    parameter to the service policy to be activated or to
    'ACTIVE' if the current active service policy is used.
    
    If REMOVE or REMOVE_IF_EXISTS is specified, the specified WLM
    application environment is removed from an existing WLM service
    definition, the modified service definition is installed, but
    the service policy is not activated. The removed WLM
    application environment becomes unavailable on the next
    activation of the service policy.
    
    If REMOVE_ACTIVATE or REMIFEXISTS_ACTIVATE is specified, the
    specified WLM application environment is removed from an
    existing WLM service definition, the modified service
    definition is installed, and the service policy is activated.
    
    If REMOVE or REMOVE_ACTIVATE is specified, a return code
    of 8 is returned by both DSNTWLM and DSN_WLM_APPLENV if the
    WLM application environment to be deleted does not exist.
    On the other hand, if REMOVE_IF_EXISTS or REMIFEXISTS_ACTIVATE
    is specified, a return code of 4 is returned by both DSNTWLM
    and DSN_WLM_APPLENV if the WLM application environment to be
    deleted does not exist.
    

APAR Information

  • APAR number

    PI42007

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    B10

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-05-29

  • Closed date

    2016-04-20

  • Last modified date

    2016-06-02

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

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

    UI36562

Modules/Macros

  • DSNTIJRW DSNTWLMB DSNTWLMS
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RB10 PSY UI36562

       UP16/05/05 P F605

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":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 June 2016