Bill
You will have to issue the archive requests manually. Look at the
ARCHIVE.LOG file for the list of parm that are required and just change the
logfile name.
Hope this helps
_____________________________________________
Dale M. McInnis IBM Toronto Lab
Senior Technical Manager, DB2 UDB Backup, Data Protection and Recovery
Email: [EMAIL PROTECTED]
Phone: (416) 448-2397, Fax: (416) 448-4414, T/L: 778-2397
|--------+-------------------------------->
| | BILL.GALLAGHER@phoenix|
| | wm.com |
| | Sent by: |
| | [EMAIL PROTECTED]|
| | a.best.com |
| | |
| | |
| | 07/31/2001 08:52 AM |
| | Please respond to |
| | db2eug |
| | |
|--------+-------------------------------->
>-----------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: DB2EUG: UDB and Archive Logging (USEREXIT)
|
|
|
|
|
>-----------------------------------------------------------------------------------------------------------|
We've been using archive logging and the "db2uext2" user exit for archiving
our log files to TSM for quite some time with pretty good success.
However, yesterday something stopped working and the db2uext2 exit started
failing. We stopped and restarted the instance, which seems to have
cleared up the problem as new archive logs started getting archived to TSM.
But all the older log files for which the userexit failed are still
residing on disk, and are not being archived to TSM. This is causing us
space problems for these file systems.
Does anybody know how I can get the exit to be called again in order to
force these older log files to get archived to TSM so that we can free up
space?
Thanks,
Bill Gallagher, DBA
Phoenix Life Insurance
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see
http://people.mn.mediaone.net/scottrmcleod
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
