OA31761: HSM DATASET BACKUP TAPE PROCESSING ALLOCATES AND ADDVOLS A TAPE BUT DOESN'T WRITE ANYTHING TO IT. SYSROUTED TO OA32684 .

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

  • In an DUPLEX dataset backup environment where there aren't
    enough devices to satisfy all dataset backup task requirements,
    a dataset backup task can request an original tape allocation
    that doesn't get satisfied until all dataset backup requests are
    completed.  When this happens, a tape is allocated and addvol'd
    as a backup tape but nothing is written to it.  It ends up in
    the HSM backup tape inventory as an EMPTY with no alternate
    volume assigned.
    

Local fix

  • Ensure there are enough tape devices available to satisfy all
    HSM backup processing requirements.  If the problem occurs and
    an empty backup tape is created, mark the tape full with:
    
         HSEND DELVOL volser BACKUP(MARKFULL)
    
    The tape should recycle and be returned to scratch during the
    next recycle process.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: z/OS V1R6  users of DFSMShsm's in a          *
    *                 backup duplex environment using the          *
    *                 DSBACKUP function.                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: During BACKDS processing, an original   *
    *                      tape is  allocated and addvol'd as a    *
    *                      backup tape but nothing is written to   *
    *                      it.  It ends up in the HSM backup tape  *
    *                      inventory as an EMPTY with no           *
    *                      alternate volume assigned.              *
    *                      .                                       *
    *                      Additional Symptoms:                    *
    *                      IEF878I                                 *
    *                      ARC0381A                                *
    *                      ARC0951I                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In a DUPLEX data set backup environment,  the original  backup
    tape was successfully allocated.  However, no devices were
    available to satisfy the allocation for the alternate tape.
    MSGIEF878I and MSGARC0381A were both eventually replied
    to with 'cancel'.   MSGARC0951I was issued and the backup of
    the data set continued in simplex mode.  The original tape was
    mounted and addvol'd for the backup.  However, by that time,
    there were no longer any data sets to be backed up.
    They had already been backed up by another task.   Backup in
    this task ended and the empty original tape remained in the
    HSM backup tape inventory as EMPTY with no alternate volume
    assigned.
    

Problem conclusion

  • DFSMShsm has been changed to correct this problem. The
    original tape is now marked full if no alternate is created
    and the volume is empty.  This will allow it to be picked up
    by Recycle and returned to scratch.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA31761

  • Reported component name

    DFSMSHSM, ISMF

  • Reported component ID

    5695DF170

  • Reported release

    1J0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-01-26

  • Closed date

    2010-04-08

  • Last modified date

    2010-04-26

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

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

    UA53531 OA32684

Modules/Macros

  •    ARCSELBV
    

Fix information

  • Fixed component name

    DFSMSHSM, ISMF

  • Fixed component ID

    5695DF170

Applicable component levels

  • R1J0 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

z/OS family

Software version:

1J0

Operating system(s):

MVS, z/OS

Reference #:

OA31761

Modified date:

2010-04-26

Translate my page

Machine Translation

Content navigation