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?
Release : 13.5
Component : OPS/MVS