IBM Support

VM65653: DFSMS MOVE FOR AN IDENTITY USER MIGHT FAIL.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DFSMS MOVE for an IDENTITY user where the MDISK is defined in
    the SUBCONFIG fails.
    Directory statements for IDTEST
      IDENTITY IDTEST xxxxxxxx 1M 4M G
      INCLUDE SYSUSERS
      BUILD ON FRZVMA USING SUBCONFIG IDTEST-1
      *DVHOPT LNK0 LOG1 RCM1 SMS0 NPW1 LNGAMENG PWC20140919 CRC
    Directory statements for IDTEST-1
      SUBCONFIG IDTEST-1
      MDISK 0191 3390 13912 1 ZVM001 MR
      *DVHOPT LNK0 LOG1 RCM1 SMS0 NPW1 LNGAMENG PWC20140919 CRC?<
    
    DFSMS request:
      dfsms move idtest 191 group gpool (targetsize 5
    
    FSMD1M0505E Internal error from routine 8216, return code = 1
    FSMD1M0505E Internal error from routine 42, return code = 8
    FSMEMD4100E DFSMS MOVE Request identifier 21 (IDTEST 191)
    failed
    .
    The same DFSMS MOVE is working fine for an IDENTITY user where
    the MDISK was NOT defined in the SUBCONFIG.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DFSMS Function Level 221 installations   *
    *                 using the Minidisk Move capability of DFSMS. *
    ****************************************************************
    * PROBLEM DESCRIPTION: DFSMS Minidisk move will fail if the    *
    *                      user minidisk being moved or the        *
    *                      DGTSRV01 500 and 5FF minidisks are      *
    *                      defined in a SUBCONFIG.                 *
    ****************************************************************
    * RECOMMENDATION: APPLY PTF                                    *
    ****************************************************************
    The minidisk move capability of DFSMS was never updated to
    handle SUBCONFIG's in a user directory.  DFSMS uses VMUDQ from
    CP to query the directory to find the users minidisk.  If the
    minidisk is defined in a SUBCONFIG this will fail.
    

Problem conclusion

  • DFSMS has been updated to take advantage of a new capability in
    CP in the VMUDQ interface to query the directory for minidisks
    in a SUBCONFIG.  VMUDQ will return the correct information to
    DFSMS no matter whether the minidisk is defined in a SUBCONFIG,
    an IDENT, or a USER entry.  In addtion DFSMS will now issue the
    proper commands to DirMaint to move a minidisk no matter whether
    the minidisk is in a SUBCONFIG, an IDENT, or a USER entry.
    CP APAR VM65877 is required to use this new support.
    
    Note: The DFSMS Minidisk move function cannot be used to
    initiate a MOVE from one SSI member on behalf of a minidisk
    in another SSI member.  The command must be initiated on the
    local SSI member to move a minidisk, including one defined
    in a subconfig.
    In addition, the userid parameter must point to a user ID
    or identiy on the local SSI member and cannot point to a
    subconfig name.
    -----------------
    In addition DGTQDIRM EXEC is an EXIT.  The input to this EXIT
    has changed in the following way.
    To support SubConfig's in the USER DIRECTORY the DirMaint input
    commands to DGTQDIRM EXEC for MMDISK, AMDISK, RMDISK, and
    DMDISK have changed.  If you are going to manipulate a minidisk
    that resides in a SubConfig DirMaint requires you to use
    the SubConfig name in the *MDISK commands instead of the IDENT
    name.  To accommodate this the input to DGTQDIRM has been
    updated.  It will now contain an extra input parameter for the
    AMDISK, RMDISK, and DMDISK commands and two extra input
    parameters for the MMDISK command.  These extra input
    parameters will contain the SubConfig name where the minidisk
    resides or if the minidisk is not in a SubConfig it will
    contain the IDENT name or USER name.
    --------------
    MMDISK
    SMSG DIRMAINT MMDISK FROM username1 mdisk1 TO username2 mdisk2
    Becomes
    SMSG DIRMAINT MMDISK FROM username1 mdisk1 TO username2 mdisk2
                                             subconfig1 subconfig2
    
    AMDISK
    SMSG DIRMAINT AMDISK username 0567  X  VBLK 4096  360  volid
    Becomes
    SMSG DIRMAINT AMDISK username 0567  X  VBLK 4096  360 volid
                                                      subconfig
    
    DMDISK
    SMSG DIRMAINT DMDISK username 0567  NOCLEAN
    Becomes
    SMSG DIRMAINT DMDISK username 0567  NOCLEAN  subconfig
    
    RMDISK
    SMSG DIRMAINT RMDISK username mdisk   3380  startingextent
                                                 length $$$$$$
    Becomes
    SMSG DIRMAINT RMDISK username mdisk   3380  startingextent
                                       length $$$$$$ subconfig
    

Temporary fix

Comments

APAR Information

  • APAR number

    VM65653

  • Reported component name

    IBM DIRMAINT-VM

  • Reported component ID

    5749DVH00

  • Reported release

    221

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-11-14

  • Closed date

    2016-12-15

  • Last modified date

    2022-02-10

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

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

    UM35002

Modules/Macros

  • DGTQDIRM FSMDPBDL FSMDPBPB FSMDPLNK FSMDPMDC FSMDPMDM FSMDPMQD
    FSMDPS1C FSMDPS1M FSMDPS2C FSMDPS2M FSMDPS3C FSMDPS3M FSMDPS4C
    FSMDPS4M FSMDPS5M FSMDPS6M FSMEPMDK FSMEPMMD FSMEPMWC FSMHXINF
    FSMHXRCP FSMZMDSI FSMZMDST FSMZSRVI VM65653
    

Fix information

  • Fixed component name

    DFSMS/VM

  • Fixed component ID

    570611601

Applicable component levels

  • R221 PSY UM35002

       UP17/01/06 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.

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

Document Information

Modified date:
11 February 2022