OA26431: IGD306I IGD17040I IGD17103I 0425006B 041A041D IEC143I IEC032I IEC070I RC56 RC4 RSN107 RC68 RSN20 RC213 RSN04 RC37 RSN08 BCS

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When an SMS managed PDS dataset is created and a fragmented
    volume is selected SMS can fail with the following messages:
    
    IGD17040I ERROR IN DADSM PROCESSING ON VOLUME SYSV09
              FOR DATA SET SYS4.CANDLE.OMDB2.HKMV310.F7
              HISTORIC RETURN CODE IS 56
              DIAGNOSTIC INFORMATION IS 0425006B
    
    IGD306I UNEXPECTED ERROR DURING IGGDAC02 PROCESSING
            RETURN CODE 4 REASON CODE 107
            THE MODULE THAT DETECTED THE ERROR IS IGDVTSDA
            SMS MODULE TRACE BACK - VTSDA VTSCM VTSCR SSIRT
    
    0425006B means:
    
    Verify space requested is available.  Not enough space in first
    extent for directory.
    
    The customer that reported this problem attempted to create a
    PDS on a volume that could satisfy the total primary space
    request but the largest extent of the volume was not large
    enough for the directory.
    
    ADDITIONAL SYMPTOMS:
    1. This problem can occur on any file type ... non-VSAM or VSAM
       create or extend processing.
    2. This occurs when there is insufficient space as indicated by
       DADSM.  A catalog entry is created but the dataset is not
       allocated although the joblog and an SMSTRACE may indicate
       that the allocation was successful.
    3. Dadsm diagnostic code 041A041D was received for a non-VSAM
       data set.
    4. abend213 rc4 (rc04)
    
    Additional Search Keywords:
         msgIGD306I msgIGD17040I msgIGD17103I diag0425006B
         msgIEC143I msgIEC032I   msgIEC070I   diag041A041D
         orphaned
    

Local fix

  • If the problem was experienced during dataset creation:
    -------------------------------------------------------
    1) Issue a DEL NOSCR to delete the catalog entry for the
    failed allocation:
    
    //DELNSCR JOB ........
    //STEP1  EXEC PGM=IDCAMS
    //SYSPRINT DD SYSOUT=*
    //SYSIN    DD *
              DELETE                         -
                MY.ORPHAN.DATASET            -
                NOSCRATCH
    
    2) Request the ++APAR from level 2 and apply it.
    
    3) Re-submit the job.
    
    
    If the problem was experienced during dataset extend:
    -------------------------------------------------------
    1) Run a LISTCAT and identify all the volumes that have a BCS
    entry in the catalog:
    
    //LISTCAT  JOB .......
    //STEP1    EXEC PGM=IDCAMS
    //SYSPRINT DD SYSOUT=*
    //SYSIN    DD *
      LISTCAT  -
               ENT(BROKEN.VSAM.DATASET) -
               ALL
    /*
    
    Example output of a volser BCS entry:
    VOLSER------------SMS001
    
    2) Verify the dataset actually exisits on that volume using
    ISPF 3.4 and specifing both volume serial and dataset name:
    
    *******
    ISRUDLP                     Data Set List Utility
    Option ===>
    
    blank Display data set list         P Print data set list
        V Display VTOC information     PV Print VTOC information
    
    Enter one or both of the parameters below:
       Dsname Level . . . BROKEN.VSAM.DATASET
       Volume serial  . . SMS001
    *******
    
    3) Remove the BCS entries for the volumes in which the dataset
    does not reside with an ALTER RVOL:
    
    //REMVOLS JOB .......
    //STEP1   EXEC PGM=IDCAMS
    //SYSPRINT DD  SYSOUT=*
    //SYSIN    DD *
           ALTER BROKEN.VSAM.DATASET RVOL(SMS001)
    
    4) Request the ++APAR from level 2 and apply it.
    
    5) Re-submit the job.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of DFSMS 1.8.0 only.               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Allocation and extend of VSAM or        *
    *                      non-VSAM data sets may fail with one of *
    *                      the following symptoms. Non-VSAM        *
    *                      allocations may fail with a IEC143I     *
    *                      213-04 OPEN failure. Non-VSAM extends   *
    *                      to new volumes may fail with an IEC032I *
    *                      E37-08 message. VSAM new data set       *
    *                      allocations may fail with a IGD17103I   *
    *                      (68-20) message. VSAM extend to new     *
    *                      volumes may fail with an IEC070I        *
    *                      message.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This problem only exists in DFSMS V1R8. For non-VSAM new data
    set allocations, a CATALOG entry may be created even though no
    space has been allocated to this data set. This CATALOG entry
    would need to be deleted. For non-VSAM extends to new volumes,
    the CATALOG entry may have been updated to reflect an additional
    volume although no space was successfully obtained on this
    volume. For VSAM new data set allocations will not result in a
    CATALOG entry being created. For VSAM EXTENDs to new volumes the
    CATALOG entry may have been updated to reflect a new volume. The
    AMS ALTER command may be used to delete the additional volumes
    in the CATALOG.
    

Problem conclusion

  • The code has been fixed to allocate VSAM and non VSAM data sets
    properly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA26431

  • Reported component name

    STORAGE MGMT SU

  • Reported component ID

    5695DF101

  • Reported release

    180

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-09-08

  • Closed date

    2008-09-17

  • Last modified date

    2009-01-03

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

    OA24603

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

    UA43714

Modules/Macros

  • IGDVTSDA
    

Fix information

  • Fixed component name

    STORAGE MGMT SU

  • Fixed component ID

    5695DF101

Applicable component levels

  • R180 PSY UA43714

       UP08/12/10 P F812

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.



Rate this page:

(0 users)Average rating

Document information


More support for:

z/OS family

Software version:

180

Operating system(s):

MVS, z/OS

Reference #:

OA26431

Modified date:

2009-01-03

Translate my page

Machine Translation

Content navigation