Hello,
at my place we get both sms & nonsms disk volumes on one stack volume and have
done for yonks; sms volumes first, then nonsms; we run maxdumptasks(4) (default
is 2 if not specified) and stack(40).
Where we have two dumpclasses (e.g sysdaily & weekly) which coincide on a given
dumping day, it (a) does not stack different dumpclass on the same tape and (b)
we have 2 packs in both dumpclasses and it dumps onto seperate tapes from the
other packs in the same dumpclasses.
Thats how it is here. The packs are dumped about 2 hours into a 3+ hour
process.
Sysdaily only does 12 volumes so its not like the 2 on there own just happen to
concide with filling a tape with 40 and they're next.
If you run a hsend list dumpvolume ods('my.output.dataset') i'm betting the
volumes you're interested in are in different dumpclasses.
heres an extract from and old one of mine:-
EF3023 UNEXP POR3590 WEEKLY 2013/08/10 Y
001 PFDB01 N 2013/07/20 21:55:57
002 PFDB02 N 2013/07/20 21:58:13
EF5140 EXPIR POR3590 SYSDAILY 2013/07/22 Y
001 PFDB01 N 2013/07/20 21:55:57
002 PFDB02 N 2013/07/20 21:58:13
regards
Dave
***********************************************************************************************
z/OS 1/12 and above offer the ability for stack(255)
HTH,
Each DUMPCLASS specifies DAY(n) determining the day of the week it runs,
UNIT(3590-1), and STACK(99) to "fill up" a tape. TAPEUTILIZATION specifies 97%
of a 3590-1. AUTODUMPSTART specifies a three hour window of which no more than
15 minutes is being used.
</snip>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
