IBM Support

II09476: OEM UCBVOLI OVERLAY OF ZERO'S CAUSES VARIOUS ABENDS AND MSG'S

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • OEM code overlays UCB volser (UCBVOLI) with Zeros (zero).
    See Z-page for OEM vendor and fix.  Resulting messages are:
    msgIGD07002I VOLUME vvvvvv NOT AVAILABLE
    msgDSR1502 SYSTEM 0C4 ABEND OCCURED AT OFFSET X'03B2' IN MODULE
               DSR0060 (abend0C4)
    msgIGD306I UNEXPECTED ERROR DURING IEFAB4C0 PROCESSING
               RETURN CODE 0 REASON CODE 306 (rc0 rsn306)
    Note:  At DF/SMS R110 the msgIGD306I is issued with rc0 and
           rsn0.  At DFSMS R120 (R1B0) the msgIGD306I is issued
           with rc0 and rsn306.
    THE MODULE THAT DETECTED THE ERROR IS IGDVTSVA
    SMS MODULE TRACE BACK - VTSVA VTSCR SSIRT
    SYMPTOM RECORD CREATED, PROBLEM ID IS IGD01588
    *IEA405E WTO BUFFER SHORTAGE - 80% FULL
    *IEA404A SEVERE WTO BUFFER SHORTAGE - 100% FULL
    msgIGD17058I DELETE/RENAME FAILED, APPROPRIATE UCB UNAVAILABLE
                 FOR vvvvvv
    DATA SET IS SYS96138.T104728.RA000.CASECONT.TEMP02.H01 HISTORIC
    CODE IS 8 DIAGNOSTIC INFORMATION IS 04280039 (rc8 rsn04280039)
    
    IGD306I UNEXPECTED ERROR DURING IGGDAS02 PROCESSING
    RETURN CODE 4 REASON CODE 57 (rc4 rsn57)
    THE MODULE THAT DETECTED THE ERROR IS IGDVTSDA
    SMS MODULE TRACE BACK - VTSDA VTSDL DSP00 SSIRT
    SYMPTOM RECORD CREATED, PROBLEM ID IS IGD01388
    .
    The overlay is a four byte overlay of binary zeroes (the last
    two bytes of UCBVOLI plus UCBSTAB and UCBDMCT).  The original
    cause of the overlay is that someone wasn't using the proper
    initialization values when accessing the storage pointed to by
    TCTIOTBL.  Normally SMS will allow extra space for multi-volume
    requests by using DUMMYs, but in this case there wasn't enough
    space in the table to hold all the entries for each required
    device (because the OEM had invalidly added devices), and the
    table is spilled over into other storage -- an allocation
    control block called the GQUE.  Allocation picked up a bogus
    address from this control block and updated a UCB, which was
    not its intent.
    Additional Symptoms:  See also the NOTE in OW19266.
         MsgIEF457I display shows truncated VOLSER and VOLSTATE.
    E.g.:
            IEE457I 06.55.09 UNIT STATUS 502
            UNIT TYPE STATUS        VOLSER     VOLSTATE
            0D38 3390 O             HMW2           /RSDNT
    instead of:
            IEE457I 09.36.35 UNIT STATUS 735
            UNIT TYPE STATUS        VOLSER     VOLSTATE
            0D38 3390 O             HMW223     PRIV/RSDNT
    

Local fix

  • See Scratch Pad for OEM name and fix information.
    Also, a Vary ONLINE of the drive with the incorrect volser
    should correct the situation.
    

Problem summary

Problem conclusion

Temporary fix

Comments

  • info apar
    

APAR Information

  • APAR number

    II09476

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    1996-05-30

  • Closed date

    1996-05-30

  • Last modified date

    1997-01-08

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
08 January 1997