VM65875: SMAPI API GET_DEVICE_DETAILS DOES NOT SUPPORT CUSTOM DASD SIZES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• During xCAT startup the process calls DIRM AMDISK 200 and seems
  to have a problem with the space defined for the DASDType
  3390-64K in DEFAULTS DATADVH. When customer has custom DASD
  types defined that replace 3390-32K, 3390-64K, 3390-27, or
  3390-54 sizes, SMAPI's Get_Device_Details API does not respect
  these custom sizes.
  
  This can cause trouble in any program that calls this API and
  directly causes failure during xCAT installation.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Any users operating with SMAPI and a custom  *
  *                 DASD profile for 3390 32K/64K models will be *
  *                 affected by this issue, as the code did not  *
  *                 take custom DASD sizes into account.         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION: APPLY PTF                                    *
  ****************************************************************
  When processing DASD details to
  return, the part would use hardcoded
  values for the sizes of 3390 32K/64K
  (also known as 3390 Mod 27or Mod 64).
  When users have devices of these
  types, but with custom sizes, the
  custom sizes would not be respected
  by the system, causing issues when
  the correct values are required.
  

Problem conclusion

• The problem was fixed by creating variables to hold potential
  custom sizes for 3390 Mod 27 and Mod 54 models. DirMaint's
  EXTENT CONTROL file is now checked for definitions that replace
  the original sizes, applying them to the check to ensure the
  correct 3390 model type is returned.
  

Temporary fix

Comments

• ×**** PE17/02/08 FIX IN ERROR. SEE APAR VM65995  FOR DESCRIPTION
  

APAR Information

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

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

  UM34967 UM34968

Modules/Macros

• DMSSJGDD
  

Fix information

• Fixed component name

  VM CMS

• Fixed component ID

  568411201

Applicable component levels

• R630 PSY UM35030

     UP17/02/13 I 1000

• R640 PSY UM34968

     UP17/04/28 P 1701

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.