VM65746: QSYSOWN OUTPUT CONTAINS INCORRECT MESSAGES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• On z/VM 6.2.0 and z/VM 6.3.0, the QSYSOWN utility
  incorrectly results in numerous
  No allocation map for system owned volume:
  messages at the end of its output.  For example:
                                                                 .
  ** Informational/Warning Messages:
   No allocation map for system owned volume: """".
   No allocation map for system owned volume: """""".
   No allocation map for system owned volume: ""ﾮ""".
   No allocation map for system owned volume: ""&"".
   No allocation map for system owned volume: "".
   No allocation map for system owned volume: """".
   No allocation map for system owned volume: "�Yy"".
   No allocation map for system owned volume: ""￷""".
   No allocation map for system owned volume: LC.
   No allocation map for system owned volume: ""ﾗﾛ"".
   No allocation map for system owned volume: ""ﾗ{"".
   No allocation map for system owned volume: M630"".
  
   No allocation map for system owned volume: """""".
   No allocation map for system owned volume: """""".
   Ready; T=0.05/0.08 19:35:05
                                                                 .
  This problem does not occur on z/VM 5.4.0.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the z/VM QSYSOWN utility        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION: APPLY PTF                                    *
  ****************************************************************
       On z/VM 6.2.0 and z/VM 6.3.0, the QSYSOWN utility
  incorrectly results in numerous
  No allocation map for system owned volume: xxxxxx.
  messages at the end of its output.  The xxxxxx in the message is
  junk and is not a real volume on the system.  The problem does
  not occur on z/VM 5.4.0.
       This problem was caused by the size of CP's CPVOL
  (HCPCPVOL - System Volume List Entry) control block having been
  increased from X'38' bytes to X'50' bytes in z/VM 6.2.0 to
  accommodate new SSI-related information but DTRYQSO ASSEMBLE,
  which processes the QSYSOWN utility, was not updated to handle
  the new size of the control block.  Thus, when the DTRYQSO code
  loops through the entries in the CPVOL (SYSOWN) list, it does
  not increment correctly to the beginning of the next volume in
  the list.
  

Problem conclusion

• DTRYQSO ASSEMBLE has been updated to correctly loop
  through the entries in the CPVOL (SYSOWN) list.
  

Temporary fix

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

Comments

APAR Information

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

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

  UM34661 UM34662

Modules/Macros

• DTRYQSO
  

Fix information

• Fixed component name

  VM CMS

• Fixed component ID

  568411201

Applicable component levels

• R620 PSY UM34661

     UP15/08/19 I 1000

• R630 PSY UM34662

     UP15/08/19 I 1000

• R540 PSN

     UP

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.