VM66344: SMAPI WORKER SERVER STOPS ON INVALID DATA RECEPTION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Running a z/VM guest second level and trying to run the Systems
  Management API, System_Performance_Information_Query, the SMAPI
  VSMWORK1 worker server fails with a variety of REXX errors as
  shown below:
  .
     675 +++    return strip(format(data,5,2))
     465 +++ LPAROverheadTimePercent = , format5_2(convertFloat(
     getChars(SEGTPRC.LPENOVHD, ProcessorData)))"%"
     274 +++ rcodes = buildCPUdata()
  DMSREX475E Error 40 running DMSSPIQY EXEC, line 675: Incorrect
  call to routine
     182 +++       Reason = DMSSPIQY( authId, funcData.1,
     funcData.2 )
     182 +++     Interpret custom_cmd
  DMSREX475E Error 40 running DMSWSSMP EXEC, line 182: Incorrect
  call to routine
     194 +++    respData = DMSWSSMP(funcName, userId, targetId,
     reqLen, reqdata)
  DMSREX475E Error 40 running DMSWSWRK EXEC, line 194: Incorrect
  call to routine
  Server Error 12 20040
  Ready; T=0.14/0.16 07:02:15
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Anyone using the Systems Management API      *
  *                 System_Image_Performance_Query while running *
  *                 z/VM as a second level guest is affected by  *
  *                 this change.                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION: APPLY PTF                                    *
  ****************************************************************
  With SMAPI running on a second level z/VM guest, an attempt was
  made to invoke the System_Image_Performance_Query API. The SMAPI
  worker server where the API was run stopped running after
  encountering several REXX errors.  These errors occurred because
  data returned from the PERSMAPI server contained unexpected
  data.
  

Problem conclusion

• The LPAR overhead time percentage value monitor data is not
  valid when running z/VM as a second level guest. The
  System_Image_Performance_Query API code in DMSSPIQY has been
  updated to handle the non-value in the returned monitor data,
  thus avoiding the REXX errors reported here. A value of "N/A"
  is returned in this case.
  

Temporary fix

Comments

APAR Information

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

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

  UM35572 UM35573

Modules/Macros

• DMSSPIQY
  

Fix information

• Fixed component name

  VM CMS

• Fixed component ID

  568411201

Applicable component levels

• R640 PSY UM35572

     UP19/12/26 P 2001

• R710 PSY UM35573

     UP19/12/26 I 1000

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.