Some years back, we converted the OPSLOG archive member (ARCHJOB) from a batch job to started task. To date, that's worked fine since we primarily used just the one OPSLOG. We've now moved up to defining and utilizing a secondary log (OPSLOG2) across all our systems, which is great, but it raises an issue with our archive process.The triggering messages indicate the log to archive. As long as we're using the primary log, we're golden. If we swap over to the alternate for any period of time and then wish to archive that log, well, we're out of luck
So, has anyone else converted their archive process to a started task? If so, how did you handled passing the log name into the started task? Do you run two forms of the started task and trigger the appropriate one based on the log?
-Michael