Ok here is a follow up question. If I set the ARCHIVETRIGGER parm to 00:00 it sets the archive to occur at midnight each night. What about archiving a log that is getting close to its message limit? part of the reason I implemented the ARCHIVE process was to keep OPSLOGS from filling up. 90% of the time, midnight is a suitable but every now and then we get a ton of messages, like when someone turns on a trace, and the log fills up much quicker. How does the archive process handle that now if I want to do both a time and message count?
EDIT: After looking over my previous process, it appears that we could set it up this way:
Set ARCHIVETRIGGER to some number of messages. Allow the ARCHIVE process to do its thing when the log reaches said number.
Also perform a SWAP from one OPSLOG to another. This triggers message OPS4*3O which I have a rule that catches this event and runs the archive REXX.
While this process still currently works, will it continue to work in the future? I saw the time added to the ARCHIVE Trigger parm and hoping that the new process handled both a log filling up and a point in time archive.