IBM Support

VM66262: DIRMAP GAPFILE AND UNSORT OUTPUT FILES INCORRECT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DIRMAP command with GAPFILE and UNSORT options creates 'fn
    GAPFILE' and 'DIRECT UNSORT' files with wrong / missing fields.
         Running the DIRMAP command with the GAPFILE and UNSORT
    options against a z/VM directory can result in invalid 'fn
    GAPFILE' and 'DIRECT UNSORT' output files.  The 'fn GAPFILE'
    output file can have an incorrect device type value in field 2.
    For example, the field 2 value can be "33390" instead of "3390".
    And the 'DIRECT UNSORT' output file can have missing values for
    fields 4, 5 and 6 (start cylinder, end cylinder and number of
    cylinders, respectively).
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the DIRMAP command.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION: APPLY PTF                                    *
    ****************************************************************
         DIRMAP command with GAPFILE and UNSORT options creates 'fn
    GAPFILE' and 'DIRECT UNSORT' files with wrong / missing fields.
         Running the DIRMAP command with the GAPFILE and UNSORT
    options against a z/VM directory can result in invalid 'fn
    GAPFILE' and 'DIRECT UNSORT' output files.  The 'fn GAPFILE'
    output file can have an incorrect device type value in field 2.
    For example, the field 2 value can be "33390" instead of "3390".
    And the 'DIRECT UNSORT' output file can have missing values for
    fields 4, 5 and 6 (start cylinder, end cylinder and number of
    cylinders, respectively).
         In addition, two other problems exist with the DIRMAP
    command:
    - When the z/VM directory contain a profile statement which has
      an eight character name, the DIRMAP command with the LINKS
      option results in no space between the Linkid (field 3) and
      Vaddr (field 4) fields in the 'fn LINKMAP' output file.  For
      example,
    MAINT    019D :IBMEIGHT019D  RR  CS4RES 3390      1169      1460
    - When the DIRMAP command with the LINKS option results in the
      message
      *** Minidisk does not exist on system ***
      written to the 'fn LINKMAP' output file, the Member field
      (field 12) incorrectly contains eight null characters (X'00')
      instead blanks (X'40').
    

Problem conclusion

  •      In general, the problems were caused by incorrect output
    field definitions and how the output fields were populated.
    DTRYDIR ASSEMBLE has been updated.  The equates for fields ULEN,
    UDEV, USUB and UMEMB as offsets in the WRBUFF buffer, which is
    used to write records to the DIRECT UNSORT file, have been
    updated.  Similarly, the equates for fields LVAD, LACC, LVOL,
    LDVT, LSTA, LEND, LLEN, LSUB and LMEMB as WRBUFF offsets for
    the LINKMAP file have been updated.  Because the lengths of some
    fields in the DIRECT UNSORT file have been increased, the FSCB
    for the DIRECT UNSORT file has been updated so the LRECL
    (BSIZE) of the file has been increased to 90.  Code under labels
    EOF4, WRITE, JUSTACC, GAPF2, UNSORTWR, LINKHEAD and MDOUT was
    updated to correct field lengths on MVC, CLC and ED instructions
    as appropriate, and under label UNSORTWR, code was modified to
    change the order of how the fields are populated.  Lastly,
    under label TRYIDENT, code has been added to correctly
    initialize the MEMBER field to blanks.
    

Temporary fix

  • FOR RELEASE ES-CMS-640-BASE :
    PREREQ: VM65945 VM65491
    CO-REQ: NONE
    IF-REQ: NONE
    FOR RELEASE ES-CMS-710-BASE :
    PREREQ: NONE
    CO-REQ: NONE
    IF-REQ: NONE
    

Comments

APAR Information

  • APAR number

    VM66262

  • Reported component name

    VM CMS

  • Reported component ID

    568411201

  • Reported release

    640

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-02-28

  • Closed date

    2019-05-15

  • Last modified date

    2020-12-16

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

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

    UM35468 UM35469

Modules/Macros

  • DTRYDIR
    

Fix information

  • Fixed component name

    VM CMS

  • Fixed component ID

    568411201

Applicable component levels

  • R640 PSY UM35468

       UP19/05/22 P 2001

  • R710 PSY UM35469

       UP19/05/22 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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"640","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
12 January 2021