Operations › Initialization › OPSLOG Initialization › In-Storage OPSLOGs

In-Storage OPSLOGs

An in-storage OPSLOG exists only in a data space associated with the main OPS/MVS address space. You can have a number of in-storage OPSLOGs. The data in the data space is not automatically saved to disk (although it may be archived) and its data is discarded when the OPSLOG is deactivated or the product terminates.

You must verify that your paging configuration can support the virtual storage used by the in-storage OPSLOG. This is usually not an issue if the BROWSEMAX value associated with the in-storage OPSLOG is relatively small. However, for a large in-storage OPSLOG you may need to add paging space, additional page data sets, or both to support the extra virtual storage use.

During OPSLOG initialization:

• All of the main address space allocations are checked.
• Any ddnames that begin with the character string OPSLOG are automatically defined and activated. These definitions cannot be deleted.
• If no OPSLOG ddnames are found and no OPSLOG was defined in the initial REXX exec using ADDRESS OPSCTL OPSLOG, then an in-storage OPSLOG is automatically defined through the BROWSEMAX parameter value, activated, and used as the live OPSLOG.

  Note: A live OPSLOG is the log currently being updated with new events as they occur in the system. There can be only one live OPSLOG.