Previously, I used CA-Opera (an automation tool).  When the DSNJU003
message came out, it kicked off a batch rexx job to make a copy of the
archive (I added .DISBKUP as the low-level qualifier).  It also added
the archive dsn to a GDG.  When it was time to take all the tapes
offsite, a job (using a lot of rexx and some COBOL) found the image
copies and archive copy tapes that were needed, generated recovery jcl
(including jcl to rebuild the BSDS with the "copy" archives), and create
a tape pull list.

It's much simpler for me now.  We use BMC's Paclog and archive to dasd.
When it's time to take the tapes offsite, I issue a DFDSS backup of the
archive logs that have been created that day.  I use a LOT fewer tapes
now.

Let me know if you want more detail.

Tina Hilton
Thomson Consumer Electronics
hiltont AT tce DOT com

> -----Original Message-----
> From: Robert Hall [SMTP:robert.hall AT occ.treas DOT gov]
> Sent: Tuesday, July 14, 1998 12:07 PM
> To:   DB2-L AT AMERICAN DOT EDU
> Subject:      Archive Log Files
>
> Hello,
>
> I have a pretty basic question.   How do people out there in DB2 Land
> (MVS/OS390) make duplicates of the archive logs for offsite recovery
> purposes?
>
> Currently, we have a user written COBOL program that based on an
> IDCAMS
> LISTCAT input stream, generates JCL to make additional copies of any
> archive logs created since the last time the program was run.    The
> program creates JCL that can have multiple gener steps to copy each
> new
> archive log(s) and BSDS to a different HLQ.   The generated JCL is
> then
> copied to the internal reader for execution.  The copies of the
> archive
> logs are shipped offsite (based on the different HLQ of the copied
> datasets.)
>
> The problem is that I need to change the program to generate JCL with
> IF
> statements (instead of COND=);  all the JCL is hard coded in the
> working
> storage section of the program and can't be changed easily because the
> program reuses certain data elements in multiple places (hard to
> explain.....trust me changing it will be U G L Y).   I want to come up
> with
> a way so that any future modifications to the JCL will be simpler.
>
> I know that I can rewrite the program (preferably using SAS instead of
> COBOL), but do I have any other options?  Is there any way to get DB2
> to
> kick off a copy job after the archive log tapes have been created?
> I've
> considered using CA7 with a dataset creation trigger, but 7 can be a
> beast.
>  Basically,  I want a quad copy option (instead of just dual copy).
>
> In the V5 Admin Guide, page 4-89 says: "....If you use dual logging,
> you
> can specify on installation panel DSNTIPA that one copy of the archive
> log
> go to tape and another to DASD.  ......   The tape can be used as a
> backup
> or can be sent to a remote site in preparation for disaster recovery"
> BUT,
> on page 4-133, the AG says under 1.a: "Do not use dual logging for the
> purpose of taking COPY2 of the archive to the recovery site.  If the
> first
> archive becomes unreadable, then the second copy is requested.   DB2
> will
> wait indefinitely until the second copy is mounted, which can create
> logistical problems".    What gives?   Does page 4-133 only apply to
> dual
> copy when both copies are tapes?
>
>
> TIA,
> Robert