Re: automating journal file concatenation

Discussion created by ca.portal.admin on Feb 16, 2010
we tried this for 5 years - but we had to abandon - throughout the day
on especially on heavy CVs - the offload + append job would take longer
and longer to run as the aggrgate would get bigger and bigger (this was
tape which was probably a mistake) - at times all journals would fill
becuase it took to long to run one offload job and they were of course

we now offload journals and logs as they fill - and then run an idcams
to get the GDGs created during the day and build a daily tape and then
delete the GDGs just merged


Petra LaFrese wrote:
We use a much simpler method. When offloading journals, we add the
offloaded journal file to an aggregate journal file. Once a day in the
evening backup job, we dump the aggregate file to tape and then
the aggregate file so we essentially have a day's worth of journals on
one tape. It is not exactly a real-time day because of when the job is
run, but since it is run at about the same time every day, it is what
could call a 'processing' day.

Hope this helps,
IDMS 3rd-party providers forum


Re: automating journal file concatenation
"We don't do this anymore. It's just too much with 60+ journals a day on
one Production CV and 40+ a day on the other.
We keep all journals 3 days, after that, there's no going back so what's
the point.
We have flashcopy backups every day, plus Real Time Global Mirroring,
so, in our evaluation of the various recovery scenarios, when balanced
against the daily overhead and aggravation of merging tapes never to be
accessed again, the ROI just isn't there.
I think the rationale for merging tapes was both to provide a daily
recovery tape and to free up tapes in the library -- but cpu and IO is
precious to us and tapes are cheap -- especially with VTS.