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?
What release of CA OPS/MVS are you currently running?
First introduced in release 12.2 and available in release 12.3 as well, there is a new OPSLOG Archive process that does utilize a Started Task and is designed to archive the data contained in your current live OPSLOG DIV VSAM dataset.
Let us know if you are interested to know more about this new method to see if it can replace your current process.
We're between 12.2 and 12.3 now
Guess I'll take a look at the Archive documentation
Since you have systems running release 12.2 consider review the following URL link for the new OPSLOG Archive:
For your release 12.3 either switch in the versions link at the top of the page or just visit this URL:
Michael, as you probably are fully aware under release 12.3 you are required to resize the OPSLOG DIV dataset to host OPSLOG data. The following KD article should help you anticipate this requirement and act upon it:
Finally, and since youa re using this channel to communicate with Customer Support and the rest of the user community, consider visiting and review this ongoing discussion as two subjects are being discussed you might be interested on:
Let us know Michael once you review all this references if you have more questions.
Hope this all helps you adopt the new OPSLOG Archive feature.