CA OPS/MVS: How to determine the size of CA OPS/MVS OPSLOG DIV datasets? - Best Practice.


Article ID: 36552


Updated On:


CA OPS/MVS Event Management & Automation


Customers who wants to utilize CA OPS/MVS OPSLOG DIV datasets needs to determine how much space is required to accommodate their BROWSEMAX parameter value.  This article provides a formula to determine how much space is needed based on the value used in the BROWSEMAX parameter. The BROWSEMAX determines the maximum number of messages in the OPSLOG message area for any OPSLOG. The OPSLOG message area resides in a data space owned by the CA OPS/MVS main address space. The maximum size of a data space is around 2 GB.
Let's assume the following values for this example:
BROWSEMAX set to '500,000'
Device Type is a 3390-3
The OPSLOG Sizing formula is:
(BROWSEMAX * 436) + 40960 = nnn bytes
So, for our example:
(500000 * 436) + 40960 = 218040960 bytes or 0.21804096 GB.
Converting the gigabytes to Cylinders (depending on DASD model) gives us a total of 238.15 CYL. The CA OPS/MVS OPSLOG DIV dataset should be allocated with 239 cylinders.
To better understand the number of messages the OPSLOG dataset will store, we can take this value and compare it to the DASD Requirements for OPSLOG Messages Chart.  For a 3390 Device Type, you'll will see you are able to store at least 400,000 messages. The chart will show the additional amount of cylinders required if more OPSLOG messages need to be need to be stored.
Additional Information:

DASD Requirements for OPSLOG Messages



Release: PVLA2.00200-12.2-OPS/MVS-Event Management & Automation-for JES2