However, you do need to understand that stacking files needed for
recovery purposes on a tape already containing recovery data does put
the previous data at greater risk. Mechanical drives and physical tapes
have the potential at each tape mount for a failure that can result in
loss of all data on the tape, and if you do enough stacking on a regular
basis it is inevitable you will eventually have such a failure. Our
long-term experience with DFHSM and CA-Vtape on 3590E drives confirms
this exposure.
If you do stack datasets in this fashion you want to be sure there is a
duplexed copy of the data somewhere (possibly on another stacked tape)
that you can fall back to, just to cover that eventuality and prevent
data loss.
Robert A. Rosenberg wrote:
At 14:47 -0500 on 03/30/2007, Pommier, Rex R. wrote about Re: 3490 off
maintenance June 30 2007:
And, before somebody tells me to just append the logs to a
larger capacity tape, I can't. We have a purchased package that
requires each of the log files to be in a separate dataset for nightly
processing.
Which does not preclude stacking them up onto the same tape by just
upping the File-Sequence-Number for each backup. So long as the files
are cataloged, the tape will spin to the correct dataset when opened for
input to your program. It is not that hard to write a program that will
keep track of the last FileSeq used and do an update to the JFCB (or do
the catalog) before using it for the open (or open the newly cataloged
Dataset as DISP=MOD in the next step).
...
--
Joel C. Ewing, Fort Smith, AR [EMAIL PROTECTED]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
