IBM Support

II04686: UTILITY USAGE OF SYSUT1

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • NDOP866208 5740XYR00 R230 r310
    ABEND713 OR ABEND7EC ON DB2 LOAD IF SYSUT1 ON TAPE
    DB2 LOAD MAY OPEN THE SYSUT1 DATASET 3 TIMES:
    1) RELOAD PHASE (FOR OUTPUT)
    2) SORT PHASE (FOR INPUT)
    3) BUILD INDEX PHASE (FOR OUTPUT)
    IF SYSUT1 IS TAPE, THEN THE SECOND TIME THE DATASET IS OPENED
    FOR OUTPUT (STEP 3 ABOVE), WE GET ABEND7EC OR MSGIEC148I
    (IEC148I) ABEND713-04 (RC4 RC04).
    SPECIFYING DISCARDS PROCESSING CAUSES DISCARDS TO BE WRITTEN
    TO SYSERR RATHER THAN SYSUT1, THUS BYPASSING THE PROBLEM BY
    AVOIDING THE SECOND OPEN FOR OUTPUT.
    ---------------------------------------------------------------
    
    When running Utilities, Db2 generally reuses its Work Data Sets
    during the different phases ie. uses it both for INPUT and
    OUTPUT. During the LOAD Utility, SYSUT1 is used during the
    following phases:
    RELOAD phase -  Sysut1 opened for output - holds the index keys
    SORT phase   -  Sysut1 used as input
    BUILD phase  -  If error dataset is specified, index error
                    information is stored in SYSERROR.  If Discard
                    processing is not specified, SYSUT1 is opened
                    for output to hold the errors.
    INDEXVAL     -  SYSUT1 is used as input if Discard processing
                    is specified.
    ENFORCE      -  SYSUT1 is used for input and output. It is first
                    opened for output and error records describing
                    the Referential Integrity (RI) Constraint
                    violations are written to this data set.
                    After all keys are checked, the ENFORCE phase
                    then opens the SYSUT1 dataset for INPUT to
                    remove these violations.
    DISCARD      -  SYSUT1 is used as input.
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  •  CLOSING CAN FOR RETENTION PURPOSES.
    

APAR Information

  • APAR number

    II04686

  • Reported component name

    PB LIB INFO ITE

  • Reported component ID

    INFOPBLIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1990-12-10

  • Closed date

    1990-12-11

  • Last modified date

    1996-03-29

  • 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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"001","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
31 July 2023