IBM Support

VM66874: Z/VM 7.4 DIRMAINT: LOADDEV ALT - FEATURE 01 FIX 00

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • This is the APAR for z/VM 7.4 DirMaint Feature Pack 1.  As such
    it contains the following new function:
    
    This feature is to support the addition, modification, and
    deletion of the LOADDEV ALTERNATE statements in DirMaint.
    The addition of LOADDEV ALTERNATE statements introduces support
    for up to three alternate paths for a SCSI Device, thereby
    extending the capability to handle multiple paths for IPLing the
    guest.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of z/VM DirMaint.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION: APPLY PTF                                    *
    ****************************************************************
    The objective of this enhancement is to enable DirMaint and
    SMAPI to support the addition, modification, and deletion of
    the LOADDEV ALTERNATE statement. It ensures a clear and
    structured way to handle alternate paths for a virtual
    machine.
    
    Enhanced LOADDEV Support: This enhancement enhances the
    current DirMaint LOADDEV command to support the ALTERNATE
    keyword. The addition of LOADDEV ALTERNATE statements
    introduces support for up to three alternate paths for a SCSI
    Device, thereby extending the capability to handle multiple
    paths for IPLing the guest.
    
    Managing LOADDEV Changes: Previously,
    DirMaint LOADDEV support relied solely on the unique operands to
    determine whether a statement should be added or replaced. With
    LOADDEV ALTERNATE, both the virtual device address and operand
    are considered to determine the directory statement to be
    updated.
    

Problem conclusion

Temporary fix

Comments

  • The following changes have been made to DirMaint:
    * Device Type Specification: LOADDEV statements are
      categorized as either ECKD or SCSI, ensuring consistency
      within the statement. This enhancement allows an alternate
      port name for the SCSI device type only.
    * Handling modification and deletion of statement: DirMaint
      has been using a unique value of each operand (e.g. DEVICE,
      LUN, PORTNAME, SCPDATA, etc) to determine whether to add or
      modify an existing LOADDEV statement. For alternate
      statements the design extends this logic and considers the
      portname operand with the virtual device address to uniquely
      identify the statement.
    * Limits and Prioritization: The support allows a maximum of
      three alternate statements per stanza and retains the order
      of the addition and modification of alternate statements to
      manage prioritization.
    * Support for Query and delete: The design supports query and
      delete operations for alternate statements by specifying the
      virtual device address and portname operand. It also supports
      an operand "ALL" to query and delete all relevant statements.
    * Directory Entry format for ALTERNATE statement will look like:
      LOADDEV ALTERNATE vaddr PORTNAME hhhhhhhhhhhhhhhh.
       Here, vaddr is a four digit virtual device address and
       hhhhhhhhhhhhhhhh is the 16 digit hexadecimal portname value.
      The user can perform various operations like add, modify,
      query, and delete for ALTERNATE statements.
    * Example DirMaint commands,
       DIRM LOADDEV ALTERNATE <vaddr> PORTNAME <portname>
       DIRM LOADDEV ? ALTERNATE
       DIRM LOADDEV ? ALTERNATE ALL
       DIRM LOADDEV ? ALTERNATE <vaddr>
       DIRM LOADDEV DELETE ALTERNATE
       DIRM LOADDEV DELETE ALTERNATE ALL
       DIRM LOADDEV DELETE ALTERNATE <vaddr>
    
    NOTE:
    Once the APAR is applied the DirMaint command file must be
    updated to enable the new LOADDEV ALTERNATE support.
    
    To allow the new LOADDEV ALTERNATE option to be recognized
    by DirMaint the 150CMDS SAMPDVH file has been changed to
    use the new DVHLDDEV EXEC instead of the DVHGSTWO EXEC.
    The 150CMDS DATADVH file is a user tailorable file
    and is not automatically updated by the service process.
    However, when the APAR is applied the 150CMDS SAMPDVH file
    is updated and can be used to create the new 150CMDS
    DATADVH file or update the installation's version of
    the file.
    
    The APAR service updated copy of the file, 150CMDS SAMPDVH,
    can be found on the 7VMDIR40 2C2 samples minidisk or, in
    a SFS installation, in the VMPSFS:7VMDIR40.DIRM.SAMPLE
    directory.
    
    To allow DirMaint to recognize the LOADDEV ALTERNATE option,
    the updated copy of the 150CMDS SAMPDVH file needs to be
    copied to the DIRMAINT 11F 'D' disk as 150CMDS DATADVH.
    If the installation has modified the 150CMDS DATADVH file
    then the line that begins with "LOADDEV" in the 150CMDS
    SAMPDVH file can be used to replace the LOADDEV line in
    the customized 150CMDS DATADVH file. Once the 150CMDS
    DATADVH file is updated, issue:
    
    DIRM RLDDATA
    
    The RLDDATA command will put the updated file into
    Production.
    
    The following messages are added by this support:
      DVH3433, DVH3434
    
    The following z/VM 7.4 publications are updated to
    reflect this support:
    GC24-6282-74: Directory Maintenance
                  Facility Messages
    SC24-6281-74: Directory Maintenance Facility
                  Commands  Reference
    

APAR Information

  • APAR number

    VM66874

  • Reported component name

    IBM DIRMAINT-VM

  • Reported component ID

    5749DVH00

  • Reported release

    740

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2025-08-12

  • Closed date

    2025-10-02

  • Last modified date

    2025-10-06

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

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

Modules/Macros

  • DVHADZ   DVHAEZ   DVHBBLGT DVHBBXSR DVHBLDDP DVHGSTWO DVHLDDEV
    DVHMENUS DVHSLVL  DVHULVL  DVH3433  DVH3434  LOADDEV  150ASERV
    150CMDS  7VMDIR40
    

Publications Referenced
GC24628274SC24628174SC24632774  

Fix information

  • Fixed component name

    IBM DIRMAINT-VM

  • Fixed component ID

    5749DVH00

Applicable component levels

  • R740 PSY UV99453

       UP25/10/06 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":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SG27M"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"740","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
07 October 2025