IBM Support

VM65861: SMAPI FAILS TO START AFTER LOHCOST_ENABLED CHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After updating configuration variable LOHCOST_Enabled in
    the SMAPI server configuration file, DMSSICNF COPY, from
    LOHCOST_Enabled = LOHCOST_DIRECTORY + LOHCOST_GROUP
    to
    LOHCOST_Enabled = LOHCOST_DIRECTORY
    the SMAPI server environment fails to initialize.  The following
    REXX errors are seen on the VSMGUARD server console:
                                                                   .
    11:46:26    122 +++ logData = ,  'EXIT  DMSSLCCI Cache
    initialization complete rc='drc +
    11:46:26 grc
    11:46:26 DMSREX476E Error 41 running DMSSLCCI EXEC, line 122:
    Bad arithmetic conversion
    11:46:26    566 +++            rc = DMSSLCCI()
    11:46:26 DMSREX475E Error 40 running DMSWSSMI EXEC, line 566:
    Incorrect call to routine
    11:46:26     78 +++ myret = DMSWSSMI(Server_DCSS)
    11:46:26 DMSREX475E Error 40 running PROFILE EXEC, line 78:
    Incorrect call to routine
                                                                   .
    With the default LOHCOST_Enabled value as shipped in DMSSICNF
    COPY, SMAPI starts successfully.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the z/VM System Management          *
    *                 Application Programming Interface (SMAPI)    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION: APPLY PTF                                    *
    ****************************************************************
         After updating configuration variable LOHCOST_Enabled in
    the SMAPI server configuration file, DMSSICNF COPY, from
    LOHCOST_Enabled = LOHCOST_DIRECTORY + LOHCOST_GROUP
    to
    LOHCOST_Enabled = LOHCOST_DIRECTORY
    the SMAPI server environment fails to initialize.  The following
    REXX errors are seen on the VSMGUARD server console:
                                                                   .
    11:46:26    122 +++ logData = ,  'EXIT  DMSSLCCI Cache
    initialization complete rc='drc +
    11:46:26 grc
    11:46:26 DMSREX476E Error 41 running DMSSLCCI EXEC, line 122:
    Bad arithmetic conversion
    11:46:26    566 +++            rc = DMSSLCCI()
    11:46:26 DMSREX475E Error 40 running DMSWSSMI EXEC, line 566:
    Incorrect call to routine
    11:46:26     78 +++ myret = DMSWSSMI(Server_DCSS)
    11:46:26 DMSREX475E Error 40 running PROFILE EXEC, line 78:
    Incorrect call to routine
                                                                   .
    With the default LOHCOST_Enabled value as shipped in DMSSICNF
    COPY, SMAPI starts successfully.
         The REXX errors are due to code in DMSSLCCI EXEC:
                                                                   .
    If BITAND(LOHCOST_Enabled,LOHCOST_DIRECTORY)=LOHCOST_DIRECTORY
    Then Do
      drc = DirectoryCacheInit()
    End
    If BITAND(LOHCOST_Enabled,LOHCOST_GROUP)=LOHCOST_GROUP
    Then Do
      grc = GroupCacheInit()
    End
    ...
    logData = ,
      'EXIT  DMSSLCCI Cache initialization complete rc='drc + grc
                                                                   .
    After changing the value of LOHCOST_Enabled in DMSSICNF COPY
    from the shipped value of
    LOHCOST_Enabled = LOHCOST_DIRECTORY + LOHCOST_GROUP
    to
    LOHCOST_Enabled = LOHCOST_DIRECTORY
    the variable grc in DMSSLCCI EXEC does not get assigned a value
    which causes the
    DMSREX476E Error 41 running DMSSLCCI EXEC, line 122: Bad
               arithmetic conversion
    error.  Neither variable drc nor grc are initialized to an
    initial value.
    

Problem conclusion

  • DMSSLCCI $EXEC has been updated.  Because DMSSLCCI is
    called by only DMSWSGRD EXEC and DMSWSGRD ignores the return
    code returned by DMSSLCCI, the return codes returned from the
    DirectoryCacheInit and GroupCacheInit function calls really
    serve no purpose.  Because of this, the return codes, the values
    of which are held in variables drc and grc, have been removed
    from the logdata that is written to the SMAPI log and are no
    longer returned on the Return statement.
    

Temporary fix

  • FOR RELEASE ES-CMS-620-BASE :
    PREREQ: VM65323 VM65162
    CO-REQ: NONE
    IF-REQ: NONE
    FOR RELEASE ES-CMS-630-BASE :
    PREREQ: VM65803
    CO-REQ: NONE
    IF-REQ: NONE
    

Comments

APAR Information

  • APAR number

    VM65861

  • Reported component name

    VM CMS

  • Reported component ID

    568411201

  • Reported release

    630

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-12

  • Closed date

    2016-08-09

  • Last modified date

    2016-12-02

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

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

    UM34861 UM34862

Modules/Macros

  • DMSSLCCI
    

Fix information

  • Fixed component name

    VM CMS

  • Fixed component ID

    568411201

Applicable component levels

  • R620 PSY UM34861

       UP16/08/09 I 1000

  • R630 PSY UM34862

       UP16/08/09 P 1602

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":"630","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
02 December 2016