The System Condition Monitor (SCM) requires the installation of the CA GSS component of the CA Common Services for Z/OS.
Starting the GSSA started task I get the following messages:
SCMDRIVE (00096) SCM9001I System Condition Monitor 14.2 starting
SCMDRIVE (00096) SCM0001I System Condition Monitor ISET = SYSVIEWE
SCMDRIVE (00096) SCM0102I Monitoring entries built via parmlib definitions: 0
SCMDRIVE (00252) System Condition Monitor - interval = 60
SCMDRIVE (00258) Sysname Type Name Interval ImodName Parms
SCMDRIVE (00096) SCM0103W No monitoring entries created. System Condition Monitor will terminate.
SCMDRIVE (00096) SCM9999I System Condition Monitor has terminated
It's as if GSS procedure don't know the parmlib file.
CA GSS communicates with CA SYSVIEW through the application program interface GSVXAPIE and the SYSVIEW load library that contains the module GSVXAPIE must be available to the GSS proc (in LINKLIST or concatenated in the STEPLIB of the GSS proc).
If the library containing the GSVXAPIE module is not accessible to GSS then the communication between GSS and Sysview will not be produced.
The GSS member of CNM4BSAM contains samples of the parameters that should be coded in the RUNTIME member used by GSSA Stc..
In the GSS member you can see the following:
*----------------------------------------------------------------------*
* Define the CA SYSVIEW ADDRESS environment (API) *
*----------------------------------------------------------------------*
* The SYSVIEW load library that contains the module GSVXAPIE *
* must be APF authorized and be available to the GSS proc. *
* The dataset can be in the LINKLIST or concatentated in the *
* STEPLIB of the GSS proc. *
*----------------------------------------------------------------------*
Add the sysview.CNM4BLOD (that contains the module GSVXAPIE) to LINKLIST or to the STEPLIB of the GSS proc.
Information about required CA Common Services for z/OS components