An include statement will associate a file or structure with a management
class, but how do you make it archive rather than backup?
Jeff Bach
Home Office Open Systems Engineering
Wal-Mart Stores, Inc.
WAL-MART CONFIDENTIAL
-----Original Message-----
From: George Lesho [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, November 20, 2001 12:33 PM
To: [EMAIL PROTECTED]
Subject: Re: Informix TDP expire/expiring Onbar log files
Joel, Not sure what you mean by an "onbar log". Are you talking
about the
Informix logical logs? If so, put them in an "archive" management
class/copy group along with your database backups. Each logical log
has a
unique file name so efforts to expire them if you use backup type
management class/copy groups can be frustrating. As an archive, they
will
expire in a finite number of days (pre copy group rules for the mgmt
class). Since you didn't mention how you did your backups, I can't
help you
with how to pin the archive management class to the backup. I use
SQL
BackTrack for Informix
and they do it when you build one of their "backup pools" (not to be
confused with TSM stgpools). If you are not using BMC SBTI for a
"storage
manager" and are only using TSM, then you may be able to do it in an
incl
statement. Not sure how TDP for Informix does it...
George Lesho
AFC Enterprises
Joel Fuhrman <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 11/19/2001
05:46:34 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: George Lesho/Partners/AFC)
Fax to:
Subject: Informix TDP expire/expiring Onbar log files
I'm looking for a script or method to expire onbar logs. If you
have one,
would you please share it.
Back in January 1999, Christoph Martin shared a routine with the
adsm list
which would expire a file. I wrapped his routine in a perl script
which
selected the old log file. This worked great until Tivoli
"improved" the
backup library, added it to the TDP line and started charging the
big bucks
for it. Now Christoph's routine fails with the error:
*** BSAInit failed: (12) An entry in the environment structure is
invalid
I've tried rebuilding it with the newest API but that didn't help.
**********************************************************************
This email and any files transmitted with it are confidential
and intended solely for the individual or entity to
whom they are addressed. If you have received this email
in error destroy it immediately.
**********************************************************************
