GSVX447E (MAIN) Configuration error : Option name not found
search cancel

GSVX447E (MAIN) Configuration error : Option name not found

book

Article ID: 254130

calendar_today

Updated On:

Products

SYSVIEW Performance Management

Issue/Introduction

After applying the z/OS 2.5 compatibility maintenance PTFs  (LU02875,LU04328) with their pre/co req PTFs and adding the new parms in the source config member (GSVXGSVX) the following messages appear when Sysview is started pointing to the updated source config member (GSVXGSVX).   

[NOTE:   The following errors can occur on any release if changes were implemented by engineering - For example, similar messages have also appeared in R17.0]

 

01.17.35 STC01014  GSVX445E (MAIN) Configuration member: GSVXGSVX
01.17.35 STC01014  GSVX446E (MAIN) Configuration option: Dsn-Site-XMLLIB                  NONE
01.17.35 STC01014  GSVX447E (MAIN) Configuration error : Option name not found
01.17.35 STC01014  GSVX445E (MAIN) Configuration member: GSVXGSVX
01.17.35 STC01014  GSVX446E (MAIN) Configuration option: Dsn-System-CSI                   NONE
01.17.35 STC01014  GSVX447E (MAIN) Configuration error : Option name not found
01.17.35 STC01014  GSVX445E (MAIN) Configuration member: GSVXGSVX
01.17.35 STC01014  GSVX446E (MAIN) Configuration option: Dsn-System-XMLLIB                HLQ.SYSVIEW.R16M0.CNM4XML
01.17.35 STC01014  GSVX447E (MAIN) Configuration error : Option name not found
01.17.35 STC01014  GSV2566E (MAIN) System configuration member GSVXGSVX contained 3 errors
01.17.35 STC01014  GSVX205E (MAIN) Nucleus load failed, reason 24 set up failed for system configuration
01.17.35 STC01014  GSVX572E (MAIN) MAIN task initialization failed
01.17.35 STC01014  IEF404I SYSVIEW - ENDED - TIME=01.17.35
01.17.35 STC01014  $HASP395 SYSVIEW  ENDED - RC=0004

 

Sysview ends with RC=0004.

No problem starting Sysview using the old Config member.

 

Environment

Release : 16.0 specific to the above; however, similar messages can potentially occur with other releases

Resolution

Check that the CNM4BLOD library used by Sysview (In STEPLIB or LinkList) is the one where the maintenance was applied.   

Also look for obsolete parms in the members of the PARMLIB and remove accordingly.       

A reload will not be necessary if SYSVIEW is already up and operational.   However, to pick up the changes, SYSVIEW will need to be started with a COLD start upon the next recycle.