Here ya go Steve. I set this up following the archive procedure for 12.1. I am finding that this method is still my preferred method for 12.2 as well since the auto-archive process forces you to choose number of messages or a time to archive. Since I still want to use the archive trigger to archive when we have those days that our cup runneth over I set the auto archive up to handle this based on message number. I then left the 12.1 swap-archive process in place. Here is my allocations and process I use:
Parameters
BROWSEMAX 4000000 MESSAGES
BROWSEMAXINUSE 4000000 MESSAGES
BROWSEARCHIVEDSN GDG Base with 90 Generations
OPSLOG Allocation
These may be a little overkill but better to be safe than sorry
OPSLOG1 3200 Cylinders
OPSLOG2 3200 Cylinders
OPSLOGA 3200 Cylinders - Backup log just incase something gets screwed up with 1 or 2.
Archive Logs
Approx 400 Cylinders each
1. Created a GDG base containing 90 generations.
2. Set BROWSEARCHIVEDSN to GDG
3. Created TOD rule to swap the log.
(I had to hard code a primary and secondary log here because determining which log was currently writing information seemed to be problematic. I also coded it over a year ago so it could possibly use a rework now that I have more knowledge but we only use two logs and I haven't had to change their DD's at all.)
4. The swap generates message OPS4626O which then triggers a rule (ARCHMSG3 provided by CA).
5. This rule goes on to run ARCHSUB which then performs the archive.