Re: [DB2EUG] db2 archive log

[Pierrre Saint-Jacques]

See answers inserted in your question Hope this Helps, Pierre. Nidhi Jain wrote: I guess there are two questions that i do not know the answer of and haven't been able to find it anywhere ;- 1. How do you check whether userexit is runnign properly, i meant can you do a ps -ef| grep exit something like that? The exit is called when a log file becomes full.  2. What if you have to change the path of the archive log? do you have to recompile the binary again? how would you know the default location of the archive log directory path set in the userexit? The exit must be called DB2UEXT2 (not case sensitive) and must be executable (exe, kshell script, Win Batch file, REXX, whatever you prefer).  The samples supplied in /sqllib/samples/c are C source code: cdisk is for archive to disk, ctape is for archive to tape, cadsm is for archive to TSM, ..) If you need to change the archive path and you've used the sample then of course you'll have to modify and recompile.  There is no default in the sample, just an example.  You  must  identify a target archive path. The samples offer you the option of identifying an audit path that you can use to check  how your exit works. Nidhi -----Original Message----- From: Carla Cristina Alonzo Duclós [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 23, 2003 4:23 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [DB2EUG] db2 archive log Hello, I don't see anything about ARCHIVE LOG in the DB2 V7.2 documentation, so it looks like the command is only available in DB2 V8. You must also be using linear (recovery) logging, and not circular logging, in order to archive log files at all. Actually, exist archive log in DB2 7.2 In the book, SC09-2951-01 - Command Reference - Version 7, we can find the command archive log. In V8, ARCHIVE LOG is a command in that tells the database to close the current log file in order to make the file safe for transport. It would probably be less confusing if IBM had named the command CLOSE CURRENT LOGFILE, which is what it really does. Unless you have defined a user exit that processes each logfile after it is closed, the database does nothing more than close the logfile and leave it in its current location (the log directory). The command close current I don´t know yet. I will looking for it on Command Reference Guide. Hope this helps, It helps a lot. :) Thanks, Carla -- Pierre Saint-Jacques, IBM Certified Solutions Expert - Administration SES Consultants Inc. 514-737-4515