Why do I get Error "GSV2570E (API.xxxGSSA) NSS-PC processing failed, SGAT block not found or invalid"?

Document ID : KB000046958
Last Modified Date : 14/02/2018
Show Technical Document Details

Symptom

After Converting to z/OS 2.1, GSSA is not working correctly, and we are getting these error messages: 

IEE252I MEMBER GSVXGSVX FOUND IN SYS1.PARMLIB 
GSV2570E (API.SP2GSSA) NSS-PC processing failed, SGAT block not found or invalid 
GSVX205E (API.SP2GSSA) Nucleus load failed 
. . . .
. . . .
SCM9001I System Condition Monitor 14.0 starting 
SCM0001I System Condition Monitor ISET = SYSVIEWE 
SCM0002I System Condition Monitor PARMLIB = SYSVIEW.NOTFOUND 
IEE252I MEMBER GSVXGSVX FOUND IN SYS1.PARMLIB 
GSV2570E (API.SP2GSSA) NSS-PC processing failed, SGAT block not found or invalid 
GSVX205E (API.SP2GSSA) Nucleus load failed  

 

Environment: 

CA Common Services for z/OS 14.1
CA SYSVIEW Performance Management 14 0 

Cause:

The SYSVIEW main address space started task was NOT started before CA GSS.

 

Resolution:

You must start the SYSVIEW address space if you are going to be issuing any type of command 
against SYSVIEW, including REXX, GSS, etc.., 



Additional Information: 

Regarding the GSV2570E SGAT message:
Prior to r13.5, S
YSVIEW required that an MVS subsystem be defined and then we would anchor everything off of that. 

This architecture changed with SYSVIEW r13.5.
 
In release 13.5, we created the SGAT (System Global Anchor Table) and store it's address in the CAAT,
an IBM control block reserved for CA
 products.  

 

The SGAT can only be built by starting the SYSVIEW or SYSVUSER address space.


Once an SGAT is built it will be present in memory until the next IPL.