OPS4627S DD_OPSLOG data set failed to activate and will continue as an in-storage replacement

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

The following errors appear when starting OPSMAIN:

OPS0164I Allocating OPSLOG data set data-set-name (OPLG0001)
OPS9999T BOSTTST BOST FIELDS 11.05.00 X'00000000'                              
*OPS4627S OPSLOG data set failed to activate and will continue as an in-storage. 

Also, the OPSVIEW panel 4.13 shows "in-storage-replacement" instead an actual OPSLOG dataset name

 

Environment

OPS/MVS

Cause

There was an attempt to use an OPSLOG dataset initialized with a pre-12.3 release of OPS/MVS. The release is indicated in the message OPS9999T as below:

OPS9999T BOSTTST BOST FIELDS 11.05.00 X'00000000'   

In this case the old release as 11.5

Resolution

A new, empty OPSLOG dataset must be allocated with any OPS/MVS release after 12.3 if the old one was allocated by any previous release.

- Use the member DEFDIV of the CCLXCNTL library as a model to allocate the new OPSLOG dataset

- The old data cannot be copied to the new OPSLOG dataset

- The amount of space required is dependent on the value of BROWSEMAX. The estimated size for each BROWSEMAX value can be found in the link below of the OPS/MVS documentation:

Address DASD Requirements for OPSLOG Messages