Setting OPSLOG ARCHIVETRIGGER & BROWSEMAX parms

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

Customer had set BROWSEMAX=400.000 and ARCHIVETRIGGER=500.000, so he lost LOG records because he did not archive all of his OPSLOG.  Also, we need to make sure we don't have a new OPSLOG created every couple of hours, because when that happens we do not retain a full month of OPSLOG data, and instead have only 25 days worth.   

 

Resolution

To correct this, you may either increase BROWSEMAX or decrease ARCHTRIGGER.

The following gives some thoughts, what would be preferable:

If you adapt BROWSEMAX and set it higher than ARCHTRIGGER, please note:
to change BROWSEMAX, you will need to reallocate the OPSLOG and recycle OPS
Browsemax should be balanced between the amount of messages, that you need for online viewing and the amount of storage devoted to keep the OPSLOG in.

Example:
The number of messages is limited to not exceeded 100.000 per OPSLOG:
OPSPRM('SET','BROWSEMAX','100000')

Set or modify this parameter...

1. Stop OPS/MVS.
   
   
2. Delete the OPSLOG DIV data set.
   
   
3. Allocate a new OPSLOG data set.
   
   
4. Restart OPS/MVS, using a different BROWSEMAX value.

Default value: 400.000
Recommendation: Set BROWSEMAX parameter to at least 800.000.
Larger sites may need to set this parameter even higher, potentially up to the maximum of 4.925.000, depending on the number of messages, you will log during one week and depending upon your console traffic.

Setting ARCHTRIGGER smaller than BROWSEMAX can be done with a command.
(and ARCHTRIGGER should be changed in OPSSPAxx accordingly in order to have this value remembered at next OPS start)

Example: The archive job is triggered after 300.000 messages:
OPSPRM('SET','ARCHIVETRIGGER','300000')

Set or modify this parameter...
Anytime

Default value: 0
Recommendation: This value should be smaller than (about half the size of) the value of the BROWSEMAX parameter so that the archive has time to complete before the OPSLOG wraps. - E.g.: If you have set BROWSEMAX = 1000000 then ARCHIVETRIGGER should be set around = 500000

We recommend setting ARCHIVETRIGGER to a number lower than BROWSEMAX is to have time to fix any problems with the archival task before the OPSLOG wraps. As your BROWSEMAX is 2500000, in theory you could set ARCHIVETRIGGER to 2400000 for example. However, depending on how fast 100,000 messages appear in your environment, if you the archival task fails for some reason you may not have time enough to fix it and run an archive.

On the other hand, if you set ARCHIVETRIGGER too low, you will have too many archives triggered.

Additional Information

Note:  Sizing of the OPSLOG can sometimes take some trial and error.   Review the section "Address DASD Requirements for OPSLOG Messages" in the manual for determining sizing requirements.  

Also, the BROWSEMAX parameter associated with an existing OPSLOG cannot be changed.    If you have to change the BROWSEMAX value for an existing OPSLOG: 

   Define a new OPSLOG, with the new BROWSEMAX value in your OPSSPAxx member.     

   Bring down OPS, then either delete or rename your current OPSLOG dataset.

   Allocate a new one with the same name. 

   Update the OPSSPAxx and change the BROWSEMAX value. 

   Restart OPS.  

Make sure the new OPSLOG, with the new BROWSEMAX gets defined in the OPSSPAxx member.