IBM Support

PI81811: UNLOAD FROM LIST GENERATES PUNCHDS ON TAPE WITH INCORRECT SEQUENCE.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • UNLOAD from list, the UNLDDS & PUNCHDS are all stacked on tape,
    according to DSNU1038I UNLDDS is stacked in SYS00001 seq 1,
    PUNCHDS is stacked to SYS00002 seq 1. But LISCAT against PUNCH
    dataset shows FSEQN=3.
    
    INCLUDE TABLESPACE TESTDB.TESTTS  PARTLEVEL 3
    INCLUDE TABLESPACE TESTTD.TESTTS
    
    
    DSNU1038I   103 02:21:53.46 DSNUGDYN - DATASET ALLOCATED.
    TEMPLATE=UNLDDS
    DDNAME=SYS00001, FILE SEQUENCE=0001
    DSN=CNBB.TESTDB.TESTTS.UN.P00003.P170301
    <-- FSEQN------------------1
    
    DSNU251I    103 02:21:53.62 DSNUULPB - UNLOAD PHASE STATISTICS -
    NUMBER OF RECO TESTDB.TESTTS PART 3
    DSNU1038I   103 02:21:54.67 DSNUGDYN - DATASET ALLOCATED.
    TEMPLATE=PUNCHDS
    DDNAME=SYS00002, FILE SEQUENCE=0001
    DSN=CNBB.TESTDB.TESTTS.PU.P00003.P170301
    <-- FSEQN------------------3
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 11 for z/OS users of the UNLOAD      *
    *                 utility using a LIST and TEMPLATE to place   *
    *                 the PUNCHDDN data set on tape.               *
    ****************************************************************
    * PROBLEM DESCRIPTION: UNLOAD LIST with TEMPLATE placing       *
    *                      PUNCHDDN on TAPE with STACK may catalog *
    *                      a data set with the wrong file sequence *
    *                      number on that tape.                    *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available.         *
    ****************************************************************
    User ran an UNLOAD LIST with PUNCHDDN allocated by TEMPLATE to
    tape, with the STACK keyword to place more than one file on the
    tape.
    
      LISTDEF UNLDLIST
      INCLUDE TABLESPACE DB1.TS1 PARTLEVEL 4
      INCLUDE TABLESPACE DB1.TS2
      TEMPLATE UNLDDS DSN CNBB.&DB..&TS..UN.P&PART..P170321
          UNIT TAPE RETPD=100 VOLCNT(99) STACK YES
      TEMPLATE PUNCHDS DSN CNBB.&DB..&TS..PU.P&PART..P170321
          UNIT TAPE RETPD=100 VOLCNT(99) STACK YES
      UNLOAD LIST UNLDLIST PUNCHDDN PUNCHDS UNLDDN UNLDDS
    
    The PUNCHDDN data set for the table space partition 4 was
    incorrectly cataloged as file sequence number 4 on the tape
    instead of file sequence number 1.
    
    Incorrect logic in UNLOAD was passing the partition number
    instead of the file sequence number when issuing the catalog
    request.
    

Problem conclusion

  • UNLOAD has been changed to pass the correct file sequence number
    when cataloging the data set.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI81811

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-18

  • Closed date

    2017-06-22

  • Last modified date

    2017-06-22

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

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

    PI82019 UI48244

Modules/Macros

  •    DSNUULGL
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RB10 PSY

       UP



Document information

More support for: DB2 for z/OS

Software version: B10

Reference #: PI81811

Modified date: 22 June 2017


Translate this page: