OPSLOG Archive System Events

Any of the following events can trigger the OPSLOG archive job to run:

When the number of OPSLOG records reaches the level you define through the ARCHIVETRIGGER parameter, CA OPS/MVS issues the OPS4403O message and the ARCHMSG rule is enabled to intercept this message
After a restart of an OPS/MVS subsystem where the previous archive was not completed for any reason, CA OPS/MVS issues the OPS0125O message and the ARCHMSG2 rule is enabled to intercept this message.
After an OPSLOG switch, as a result of an ADDRESS OPSCTL “OPSLOG SETLIVE(logname)” command, CA OPS/MVS issues the OPS4626O message and the ARCHMSG3 rule is enabled to intercept this message.

Notes:

The OPS4403O message is not WTOd; it is sent directly to the OPSLOG of the issuing subsystem and, for automation purposes, is sent to the AOF of that subsystem.
It is not absolutely necessary to enable the ARCHMSG2 rule. Not enabling it will not impact the ability of the system to archive all OPSLOG records.
The OPS4626O message is WTOd after the log switch occurs, by the internal monitor task.

Important: The previously live OPSLOG must not be reset or inactivated prior to the completion of this archive.

Any of the above events can cause the following process to execute:

The ARCHMSG, ARCHMSG2 and ARCHMSG3 rules schedule an OPS/REXX exec, ARCHSUB, to run in an OSF TSO server passing two arguments: (1) the log name of the OPSLOG to be archived and (2) the name of the data set and member containing the skeleton archive JCL.
The ARCHSUB REXX exec reads the skeleton JCL, modifies it by inserting the log name passed to it, and submits the JCL to run.
The archive job executes the OPS/REXX program ARCHTRCK to perform the archive.
Once the BROWSEARCHIVEDSN parameter has been verified, the OPSLOG archive tracking global variables are set. These variables use the global stem GLOBAL0.
After gathering or setting the above data, the ARCHTRCK program builds the OPSLOG archive creation control statement (discussed in detail on the following pages) and invokes archive-creation program OPARLGCR. The OPARLGCR program runs using the ADDRESS LINKMVS host environment of OPS/REXX in the ARCHTRCK program.
The ARCHSECG, ARCHSECP and ARCHSEC8 security rules must be enabled (you may want to customize these rules based on your security requirements) to allow the OPS/REXX programs used by the archive batch job to access/update global variables and read product parameter information.
After the OPARLGCR program completes, the global variables of the OPSLOG archive tracking system are updated by the ARCHADEN subroutine.