Updating OPSLOG ARCHIVETRIGGER parameter but no actual change

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

Dynamically changed the ARCHIVETRIGGER value to 300000 but the change is not effective unless OPS/MVS subsystem is shut down and restarted.

After a re-start the process works as expected.

The question is: Short of cycling OPSMVS to avoid an outage, is there an option to restart the OPSLOG subtask to refresh and recognize the ARCHIVETRIGGER changes?

  

Environment

OPS/MVS

Resolution

Every time the value of the ARCHIVETRIGGER parameter is changed it is necessary to issue the command:

F OPSS,RESTART(ARCH)

In the example above, OPSS, is the OPS subsystem id.

Additional Information

 RELOAD Modules and RESTART Components