Recently we were at a DR test. And all the restores were running very
well. Until we ran into a tape that was multi-volume. Whenever we tried
to go to the second tape the restore would abend with a user 833.
15.48.10 JOB04956 IOS000I F911,A5,IOE,3F,0E00,,**,021413,TSUAW6OE
098
We
When using BLP, there's really no such thing as a multi-volume tape data
set - especially if the tape actually contains standard labels.
You MIGHT be able to concatenate volume 1 and volume 2. Perhaps something
like this:
//DUMPIN DD DSN=DOES.NOT.MATTER,DISP=OLD,LABEL=(2,BLP),UNIT=3490,
//
Recently we were at a DR test. And all the restores were running very
well. Until we ran into a tape that was multi-volume. Whenever we tried
to go to the second tape the restore would abend with a user 833.
15.48.10 JOB04956 IOS000I F911,A5,IOE,3F,0E00,,**,021413,TSUAW6OE
098
Thanks for your help I'll see if I can find any more information on this
on Monday. It was very obvious that this was the first time this had ever
gone multivolume. The tapes are created SL tapes so my thinking was that
once the TMC was up and running on this system I could restore them as
You could have simply specified the actual LABEL=(n,SL),
VOL=(11,22) (and EXPDT=98000 to skip TMS processing) in your
restore JCL. It is always easier to read standard label tapes using
standard label processing. TMS is not necessary to do this. It does not
matter what TMS shows in
, 2006 3:40 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: problems with multi volume, restore using FDR
Thanks for your help I'll see if I can find any more information on this
on Monday. It was very obvious that this was the first time this had ever
gone multivolume. The tapes are created SL tapes so
6 matches
Mail list logo
