IBM Support

OA55525: IEC608I DADSM FUNCTION DISABLED THE VTOC INDEX ON DBCE,VOLSER,20DIAG=0820040B

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • IEC608I received during the creation or extend of a data set.
    Diag codes 0820040B (create and extend to a new volume) and
    0853040B, 0854040B, 0855040B (extend).
    ----------------------------------------------------------------
    The diag codes (0820040B, 0853040B, 0854040B and 0855040B) mean:
    - DSCB is not format-0 DSCB and VERIFY=YES.
    
    This essentially means that the VTOC Index believes a given DSCB
    to be available for use, but when the check was made to ensure
    the DSCB was available (FMT0 DSCB), it was not a FMT0 DSCB
    (generally referred to as an orphan).
    
    It has been determined that the potential for the orphan
    scenario has been around for years, but is now being
    discovered repeatedly and frequently than before because of a
    missing function in DFSMS 2.3 which was recovered by OA55296.
    The missing function resulted in an exposure of orphan FMT-3s
    not being cleaned up and corrupted VTOC as a result.
    The act of disabling a VTOC Index does not generally impact
    anything other than performance of VTOC access.
    Therefore it is wise to run an ICKDSF job to convert the VTOC
    to an IX format VTOC as soon as possible.
    
    Currently, we are unable to determine the reason the DSCB was
    marked available in the VTOC Index and not 'converted' to a FMT0
    DSCB in the VTOC.
    
    Therefore the scope of this APAR's mission has shifted to
    providing the RAS necessary to help clients identify and correct
    consistent issues with VTOCs and their Indexes.
    
    If your site experiences this scenario, please perform the
    following;
    
    a) DFDSS Print of the VTOC and VTOC Index with the following
    SYSIN
    //SYSIN    DD *
        PRINT INDYNAM(volser)
        PRINT INDYNAM(volser) DS(SYS1.VTOCIX.llq)
    b) Confirm the PTF for OA55296 is applied and 'active'
    c) Run an ICKDSF job with the following SYSIN
     - REFORMAT DDNAME(VOLDD) VERIFY(volser) REFVTOC
    d) If the VTOC is not in IX format following step 'c', run
    ICKDSF
     - BUILDIX  DDNAME(VOLDD) IX
    e) DFDSS Print of the VTOC and VTOC Index with same SYSIN
    f) 'Log' this volume as having gone through this process with a
    date
    
    If the results of this procedure do not result in a IX format
    VTOC, please terse and ftp the DFDSS output from steps 'a' and
    'e' above along with the ICKDSF joblogs.
    

Local fix

  • Use ICKDSF to rebuild the VTOC Index.  However, ensure the PTF
    for OA55296 is applied prior to doing so.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    *  Users of data set allocation                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    *  New Function: Provide ability to retry                      *
    *                      the allocation after it has first       *
    *                      failed on a disabled-index VTOC device  *
    *                      with the diagnostic code(xxxxxx0B or    *
    *                      STAT011) described in the error         *
    *                      description.                            *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    *  Refer to the error description.                             *
    ****************************************************************
    If users code this keyword, RETRY(STAT011) in the DEVSUPxx
    parmlib member, DADSM allocation will detect the failed
    allocation on the disabled-index VTOC due to the described
    diagnostic codes(STAT011), convert the disabled-index VTOC to
    non-index VTOC(OSVTOC), and restart the allocation one more
    time.
    

Problem conclusion

  • Refer to ++HOLD(DOC) for details.
    KEYWORDS: D/T2105 D/T2107
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA55525

  • Reported component name

    DEVICE MGMT SER

  • Reported component ID

    5695DF133

  • Reported release

    230

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / Pervasive / Xsystem

  • Submitted date

    2018-05-16

  • Closed date

    2018-11-02

  • Last modified date

    2019-06-19

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

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

    OA56084 UA97847 UA97849 UA97850 OA56903

Modules/Macros

  • IGG0299A IGG0553C IGG0325E IGG0325F IGG0325A IECEXTWA IGGDAC02
    IGG0290A ICVCMM00 ICVAFPL  IGG0553E IGG0553G IFG0DEVS IECALLWA
    IGG0425P IEAVNP16
    

Publications Referenced
SA23138030SA38067330SA38067430  

Fix information

  • Fixed component name

    DEVICE MGMT SER

  • Fixed component ID

    5695DF133

Applicable component levels

  • R230 PSY UA97847

       UP18/11/08 P F811  

  • R220 PSY UA97850

       UP18/11/08 P F811  

  • R210 PSY UA97849

       UP18/11/08 P F811  

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":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"230","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
19 June 2019