On Tue, 9 Oct 2018 12:53:45 +0000, Beesley, Paul <[email protected]> wrote: As far as I remember, specifying no volcount at all lets you write up to five volumes. If you need more - specifying volcount 6 will let you write up to 20 volumes, because DFSMS lets you have 5 volumes plus another whole multiple of 15 volumes per each "extension". So, if you expect 21 volume or more, up to 35 inclusive - you have to specify the vocount as 21.
>Did something change with VOLCOUNT parameter handling between z/OS 2.1 and 2.3? >We have a job that uses 21 tapes to backup an application's datasets, and has >this parameter: VOL=(,RETAIN,,20), > >Following the upgrade to 2.3 at the weekend, this job failed S837-08, >indicating it has run out of tape volumes, which is quite correct. >However, looking back at the previous runs, they all have used 21 tapes. So >they should really have abended as well, but all worked ok. > >Hence, wondering if something has changed in volume count processing, or >whether there was a bug in 2.1 which was fixed in 2.3. >Would appreciate any suggestions before I face the Spanish inquisition who are >claiming that my upgrade broke their job. > >Paul > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
