IBM Support

VM65291: SMAPI NOT HANDLING ENSEMBLE-MANAGED SERVER REMOVAL

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • On the Hardware Management Console (HMC), when attempting
    to use the Unified Resource Manager (URM, z/Manager) to choose
    z/VM virtual servers to manage, no virtual servers are
    displayed.  This occurs after a virtual server which had
    previously been ensemble managed is deleted from the system
    (ie, CP directory).  The problem is caused by SMAPI's handling
    of it's internal file ENSBMNGD NOTEBOOK.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the z/VM System Management          *
    *                 Application Programming Interface (SMAPI)    *
    *                 including zEnterprise environments when      *
    *                 managed by the Unified Resource Manager.     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION: APPLY PTF                                    *
    ****************************************************************
         On the Hardware Management Console (HMC), when attempting
    to use the Unified Resource Manager (URM, z/Manager) to choose
    z/VM virtual servers to manage, no virtual servers are
    displayed.  This occurs after a virtual server which had
    previously been ensemble managed is deleted from the system
    (ie, CP directory).
         The problem is in DMSSSMEM EXEC, which handles the zManager
    request to indicate images that are being managed by zManager.
    The code does not handle the case in which an image (virtual
    machine) which is marked as being ensemble-managed is deleted
    from the CP directory.  DMSSSMEM's processing maintains the list
    of emsemble-managed images in file ENSBMNGD NOTEBOOK.  When
    processing this file, the code fails when processing the image
    that has been deleted from the CP directory.
    

Problem conclusion

  • DMSSSMEM $EXEC has been updated.  The code no longer fails
    when a userid found in file ENSBMNGD NOTEBOOK does not exist in
    the CP directory.  Instead, the code logs an entry in the SMAPI
    LOG and then continues to process the other userids in ENSBMNGD
    NOTEBOOK.  Also, the code has been updated to correct several
    entries written to the SMAPI LOG.
    

Temporary fix

  • FOR RELEASE ES-CMS-620-BASE :
    PREREQ: NONE
    CO-REQ: NONE
    IF-REQ: NONE
    

Comments

APAR Information

  • APAR number

    VM65291

  • Reported component name

    VM CMS

  • Reported component ID

    568411201

  • Reported release

    620

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-06

  • Closed date

    2013-02-12

  • Last modified date

    2015-12-22

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

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

    UM33911

Modules/Macros

  • DMSSSMEM
    

Fix information

  • Fixed component name

    VM CMS

  • Fixed component ID

    568411201

Applicable component levels

  • R620 PSY UM33911

       UP13/02/12 P 1501

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"620","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
22 December 2015