Operations › Initialization › OPSLOG Browse Initialization › Initialization Using Data-in-virtual Maintenance

Initialization Using Data-in-virtual Maintenance

z/OS treats VSAM linear data sets as private paging data sets that belong to an individual user. Their content is mapped into the virtual storage or data space storage of the address space that uses them. The term for this type of data set usage is data-in-virtual (DIV). In the OPSLOG case the data is always mapped in a data space.

We strongly recommend that you store your OPSLOG automation events in at least one VSAM linear data set. There are multiple ways to do so. The preferred way is to use the following ADDRESS OPSCTL statements in your initial REXX exec:

• OPSLOG DEFINE
• OPSLOG ACTIVATE

You may also use ADDRESS OPSDYNAM to allocate an OPSLOG data set in the initial REXX exec or allocate such a data set and supply a //OPSLOG DD statement for it in the CA OPS/MVS JCL procedure.

Note: For more information, see the Installation Guide.

The CA OPS/MVS use of DIV maintenance for its OPSLOG data set has these operational implications:

• If there is not enough DASD space allocated to the OPSLOG data set, then the CA OPS/MVS MAP request abends. This means that CA OPS/MVS will not complete initialization. If this abend occurs, then take any of these actions:
  • Use the OPSPARM command in your initialization parameters to reduce the value of the BROWSEMAX parameter. The BROWSEMAX parameter specifies the maximum number of automation events CA OPS/MVS stores in its OPSLOG.
  • Increase the size of the OPSLOG data set by first deleting it, and then re-allocating it through VSAM access method services. When you re-allocate it, make sure that its size can handle the number of messages indicated by the BROWSEMAX parameter.
  • Remove the //OPSLOG DD statement from the CA OPS/MVS JCL procedure. As a result, CA OPS/MVS keeps all automation event data in the virtual storage of its extended private area. This may cause an ASM slot shortage.
• If CA OPS/MVS begins using a VSAM linear data set as its OPSLOG data set but the data set is later destroyed, then this message appears:

  OPS0154S ANY EXISTING OPSLOG BROWSE DATA DISCARDED
  

  When message OPS0154S appears, any automation events placed in the OPSLOG data set during previous CA OPS/MVS executions are lost. CA OPS/MVS then treats the data set as though it is newly allocated. Message OPS0154S can appear when:

  • The relative byte address that is used the most in the data set is greater than 0, yet CA OPS/MVS could not find a valid OPSLOG Browse header block at the beginning of the file.
  • The file has a valid header block, but the block indicates that the size of a message block on the file does not match the size of the message blocks CA OPS/MVS intends to create.
  • The size of the file stored in the header block does not match the size required by the value you specified for the BROWSEMAX parameter at CA OPS/MVS startup. If the value of the BROWSEMAX parameter is less than the size of the file stored in the header block, then CA OPS/MVS ignores the BROWSEMAX parameter value and uses the existing value instead. To reduce the size of the OPSLOG, you must stop CA OPS/MVS, delete the OPSLOG DIV data set, allocate a new OPSLOG data set, and then restart CA OPS/MVS using a smaller BROWSEMAX value.