DFSMS/VM DirMaint 1.5.0 Requirements


Product Number: 5706-116 FL 221

The following should be carefully reviewed and followed if DirMaint 1.5.0 (product number 5748-XE4) will be the CP directory manager when using DFSMS/VM minidisk management services.

  • DFSMS APAR's VM59612 and VM62140 must be applied.
  • Verify DirMaint's EXTENT CONTROL contains the following:
    1. The AUTOBLOCK section contains:
      
           3380  800 540 1 CKD
           3380  512 690 1 CKD
           3380 1024 465 1 CKD
           3380 2048 270 1 CKD
           3380 4096 150 1 CKD
      
    2. The DEFAULTS section contains:
      
           3380 885
      
      or any number larger than 2 plus the number of DGTSRVnn ids.
    3. Make sure the REGIONS section does not contain an entry for volume $$$$$$, or if present, the device type is 3380.
    4. Make sure the EXCLUDE section contains entries for each minidisk management server virtual machine's (DGTSRVnn) 0500 and 05FF minidisks, for example:
      
           DGTSRV01 500
           DGTSRV01 5FF
      
    If any changes are made to the EXTENT CONTROL file, issue the DIRM RLDEXTN command.
  • Verify DirMaint's CONFIGnn DATADVH contains the following:
    • UPDATE_IN_PLACE=YES
    • EXTENT_CHECK=ON
    • ONLINE=IMMED
    • RUNMODE=OPERATIONAL
    If any changes are made to the CONFIGnn DATADVH file, issue the DIRM RLDDATA command.
  • The following DirMaint commands must be issued by the DirMaint administrator for each minidisk server virtual machine (DGTSRVnn):
    
    DIRM AUTHFor DGTSRVnn CMDSet P CMDLevel 150A
    DIRM AUTHFor DGTSRVnn CMDSet P CMDLevel 140A
    
  • The following DirMaint command must be issued from each minidisk server virtual machine (DGTSRVnn):
    
    DIRM NEEDPass NO
    
  • Review the DirMaint EXTENT CONTROL file requirements if a DFSMS MOVE command fails with the following DirMaint messages:
    
    DVHADZ2222E An invalid device type value has been specified.
    DVHADZ2270E DIRMaint for DGRSRVnn RMDISK 500 >>> 3380 <<< 1 2 $$$$$$
    
    or
    
    DVHALC3534E All candidate areas exhibited a device type different
                from the device type specified on the allocation request.