VMSSL Minidisk Verification Fails in Some Environments

 
 APAR Identifier ...... PQ76745      Last Changed ........ 03/08/26
 VMSSL MINIDISK VERIFICATION FAILS IN SOME ENVIRONMENTS
 
 Symptom ...... IN INCORROUT         Status ........... CLOSED  PER
 Severity ................... 4      Date Closed ......... 03/08/18
 Component .......... 5735FAL00      Duplicate of ........
 Reported Release ......... 430      Fixed Release ............ 999
 Component Name TCP/IP V2 FOR V      Special Notice
 Current Target Date ..              Flags
 SCP ...................
 Platform ............
 
 Status Detail: SHIPMENT - Packaged solution is available for
                           shipment.
 
 PE PTF List:
 
 PTF List:
 Release 3A0   : UQ79474 available 03/08/26 (1000 )
 Release 420   : UQ79475 available 03/08/26 (1000 )
 Release 430   : UQ79476 available 03/08/26 (1000 )
 
 Parent APAR:
 Child APAR list:
 
 ERROR DESCRIPTION:
 The VM SSL server fails to initialize when certain virtual
 devices are accessible to the SSL server machine.
 
 For example, if a 'F201' device is available to the SSLSERV
 user ID and a valid '201' device is designated as the IPLDEVICE
 for the SSL Linux guest, the following messages are reported at
 server initialization:
 
  DTCSSL2445E IPLDEVICE "201" cannot be used
  DTCSSL2426E Disk 201 is not linked.
 
 Further investigation shows that the VMSSL EXEC does not
 properly account for and handle a mixture of 3- and 4-digit
 device numbers.
 
 LOCAL FIX:
 
 PROBLEM SUMMARY:
 ****************************************************************
 * USERS AFFECTED: All users of the z/VM TCP/IP SSL Server      *
 ****************************************************************
 * PROBLEM DESCRIPTION: SSL Server disk checking erroneously    *
 *                      reports availability or link status     *
 *                      errors for IPLDEVICE and TRANSDEVICE    *
 *                      minidisks under certain conditions.     *
 ****************************************************************
 * RECOMMENDATION: APPLY PTF                                    *
 ****************************************************************
 When the device addresses for the Linux IPL (IPLDEVICE) and
 environment transition (TRANSDEV) minidisks are obtained, the
 VMSSL EXEC does not convert a given 3-digit device number to an
 equivalent 4-digit device number.  Because of this,
 verification logic for these devices can fail when certain
 other virtual devices are also accessible to the SSL server.
 
 For example, when 'IPLDEVICE 201' is specified, the device
 number '201' is not converted to '0201'.  When other 'x201'
 devices are also accessible to the SSL server, device number
 '201' is not properly isolated by the logic within "IsDiskRW"
 routine, and the 201 disk is erroneously reported as not being
 linked.
 
 This problem can occur for any IPLDEVICE or TRANSDEVICE device
 number that is expressed using less than four digits, or when
 defaults for either of these operands are used.
 
 PROBLEM CONCLUSION:
 This problem has been resolved by ensuring that all device
 numbers provided for the IPLDEVICE and TRANSDEVICE operands are
 converted to suitable 4-digit device addresses prior to use
 (through the addition of leading zeros, when necessary).  In
 addition, the defaults coded for the IPLDEVICE and TRANSDEVICE
 operands have been changed from '201' to '0201', and '203' to
 '0203', respectively.
 
 As part of these changes, logic within the "PlaceOnDisk"
 routine has been updated to adjust QUERY DISK command output,
 to allow for the correct comparison of certain data fields with
 a given 4-digit virtual device number.
 
 TEMPORARY FIX:
 
 COMMENTS:
 
 MODULES/MACROS:   VMSSL
 
 SRLS:      NONE
 
 RTN CODES:
 
 CIRCUMVENTION:
 
 MESSAGE TO SUBMITTER: