OPSMVS - OPSNOTIFY - 'Primary OPSLOG is not the current LIVE OPSLOG'
Article ID: 51224
Updated On:
Products
Issue/Introduction
Client notices an OPSNOTIFY - 'Primary OPSLOG is not the current LIVE OPSLOG' WTO message upon OPS startup.
OPSNOTIFY OPSLOG monitor application status message:
*******************************************************
* *
* Primary OPSLOG is not the current LIVE OPSLOG. *
* *
* Notify primary OPS/MVS support. *
*******************************************************
Environment
OPS/MVS
Cause
Upon OPS/MVS initialization, the primary OPSLOG is to be the designated live OPSLOG. The rule OPS3445O will trigger the OPS3445O OPS/REXX program to verify the status of the live OPSLOG. An error or warning alert will be generated by the program if the primary OPSLOG is not the current live OPSLOG. The same message can appear if the rule OPS3445O was modified and the backup_DD_log variable points to the primary OPSLOG.
)Init
/*--------------------------------------------------------------------*/
/* Define the DD name of the primary and backup OPSLOG data sets. */
/*--+----1----+----2----+----3----+----4----+----5----+----6----+----7*/
primary_DD_log = 'OPSLOG'
backup_DD_log = 'OPSLOG2' <- Should not point to the primary OPSLOG
Additionally, an error or warning will be generated if the backup OPSLOG is not in a switchable status (not ACTIVE). The default logic of this application assumes that the primary designated OPSLOG will always be the live OPSLOG upon OPS/MVS initialization. It would be up to the client to change this default logic if not suitable for their site-specfic configuration.
Resolution
This message indicates the currently live OPSLOG is not the primary OPSLOG. This means the message OPS3445O occurred and the OPSLOG was switched to the secondary OPSLOG.
The solution can be found in the comments section of the rule OPS3445O:
'Primary OPSLOG is not the current LIVE OPSLOG'
Upon OPS/MVS initialization a query of the
primary OPSLOG found that it is not the current
live OPSLOG. The default logic of this application
assumes that the primary designated OPSLOG will
always be the live OPSLOG upon OPS/MVS
initialization. Determine if an archive of the
designated primary OPSLOG is needed, and then
perform a RESET and SETLIVE against it via the
OPSVIEW 4.13 panels.
Feedback
