IBM Support

VM65323: SMAPI WRONGLY USES LOHCOST DURING LOHCOST INIT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During SMAPI initialization, the SMAPI directory caching
    database (LOHCOST) is also initialized.  During LOHCOST
    initialization, all SMAPI requests normally fulfilled with data
    from LOHCOST should be routed instead to the directory manager.
    Currently, SMAPI worker servers do not properly recognize that
    LOHCOST initialization is in progress.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the z/VM System Management          *
    *                 Application Programming Interface (SMAPI)    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION: APPLY PTF                                    *
    ****************************************************************
         During SMAPI initialization, the SMAPI directory caching
    database (LOHCOST) is also initialized.  During LOHCOST
    initialization, all SMAPI requests normally fulfilled with data
    from LOHCOST should be routed instead to the directory manager.
    However, currently, the SMAPI worker servers are not properly
    recognizing that LOHCOST initialization is in progress.
    

Problem conclusion

  • DMSSLCCI $EXEC and DMSSIDM $EXEC have been updated.  A new
    file, LOHCOST INIT, has been implemented on the SMAPI server
    data directory (VMSYS:VSMWORK1.DATA, by default) to track when
    LOHCOST initialization is in progress.  DMSSLCCI $EXEC has been
    updated to updates the LOHCOST INIT file with a value of '1'
    when LOHCOST initialization is in progress and with a value of
    '0' when LOHCOST initialization is not in progress.  DMSSIDM
    $EXEC has been updated to check the value in the LOHCOST INIT
    file.  If the value in the file is '1', then SMAPI API calls
    bypass LOHCOST.  If any other value or if the LOHCOST INIT file
    doesn't exist, SMAPI API calls process the request through
    LOHCOST.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    VM65323

  • 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-03-26

  • Closed date

    2013-04-16

  • Last modified date

    2013-12-30

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

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

    UM33979

Modules/Macros

  • DMSSIDM  DMSSLCCI
    

Fix information

  • Fixed component name

    VM CMS

  • Fixed component ID

    568411201

Applicable component levels

  • R620 PSY UM33979

       UP13/04/17 P 1302

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:
30 December 2013