OA25585: IEC711I WITH MOD,PASS ON MULTI-VOLUME DATASET AND MULTIPLE JOBS

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • When running two or more jobs which are mod'ing onto the
    same dataset with DISP=(MOD,PASS), there is a serialization
    problem which CAN lead to the second (or subsequent) job's not
    knowing about any ADDITIONAL volumes which were created in the
    previous job.  That is, if the dataset becomes multi-volume (or
    if it already was multi-volume and one or more additional
    volumes are added) the volume serial numbers of the additional
    volume(s) MIGHT not be known to the next job. Possible symptoms
    of this problem are:
           - msgIEC710I - ANOTHER VOLUME EXPECTED   or
           - msgIEC711I - RDBACK - NOT LAST VOLUME OF DATA SET
           - msgIEC151I - abendA13 rc18
    Note that this can only occur when the dataset is PASSed
    from the last (or only) step of the job.  Prior steps that
    PASS the dataset cannot have this problem occur.
    
    The following sequence of events illustrates how the problem
    might be seen:
    
    1. A job or STC (jobA) is started specifying DISP=(MOD,PASS)
       for DSN=dsnX, in the last (or only) step of the job/STC.
    2. While jobA is running, a second job/STC (jobB), which ALSO
       specifies DISP=(MOD,PASS) is started and has to wait for the
       tape dataset until jobA releases the ENQ for both SYSDSN and
       SYSZVOLS.  (IEF861I, IEF863I, and IEF099I will probably be
       issued; IEF690I might also be issued)
    3. While jobB is waiting for the tape dataset, jobA continues
       to MOD onto the last volume of the dataset and eventually
       fills it up and requests a new ouput tape volume.
    4. When jobA is finished, jobB calls for a mount of what WAS
       the last volume of the dataset when jobA started, because
       jobB is not aware of the new tape volume which was written
       on by jobA.
    5. JobB will issue either IEC710I, IEC711I, or IEC151I.
          a. If IEC710I or IEC711I is issued, the data on the
             skipped volume(s) will be lost unless somone notices
             that the message was issued.
          b. If IEC151I is issued, the job will abend and no data
             will be lost.
    
    Additional Keywords:
         multivol multivolume, IEC151I, volser
         msgIEF861I, msgIEF863I, msgIEF099I, msgIEF690I
    
    Note that is has ALWAYS been possible to encounter this
    serialization issue, but this is the first time it has ever
    been reported.
    

Local fix

  • Change DISP=(MOD,PASS) to DISP=(MOD,KEEP) in the last
    step of a job.
    .
    *******************************
    * Projected Closing Code: FIN *
    *******************************
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All HBB7720 and above environments that      *
    *                 use JCL with DISP=(,PASS) coded in the       *
    *                 last step of the job.                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: When a job has a DD with DISP=(,PASS)   *
    *                      specified in the last step of the       *
    *                      job, and the dataset is extended to     *
    *                      another volume, another job that        *
    *                      uses the same dataset may see           *
    *                      messages MSGIEC710I, MSGIEC711I,        *
    *                      or MSGIEC151I, or ABENDA13 RSN18.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a job contains a DD that specifies DISP=(,PASS), and
    extends to an additional volume, the dataset will be
    recataloged.  Normally, this recataloging is performed at
    the end of the job step, while the dataset is still
    serialized, unless this is the last step of the job, in
    which case the recataloging is done during end of job
    processing, after the dataset serialization is released.
    
    If another job attempts to use the same dataset before the
    dataset has been recataloged with the updated volume list,
    one (or more) of MSGIEC710I, MSGIEC711I, MSGIEC151I, or
    ABENDA13 RSN18 may be issued.
    

Problem conclusion

Temporary fix

Comments

  • This APAR is being closed FIN with concurrence from the
    submitting customer.  This means that a solution to this APAR
    is expected to be delivered from IBM in a release (if any)
    to be available within the next 24 months.
    

APAR Information

  • APAR number

    OA25585

  • Reported component name

    5752 ALLOC/UNAL

  • Reported component ID

    5752SC1B4

  • Reported release

    720

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-06-25

  • Closed date

    2008-07-08

  • Last modified date

    2008-07-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

  • R720 PSN

       UP

  • R730 PSN

       UP

  • R740 PSN

       UP

  • R750 PSN

       UP



Document information


More support for:

z/OS family

Software version:

720

Operating system(s):

MVS, z/OS

Reference #:

OA25585

Modified date:

2008-07-08

Translate my page

Content navigation