Why we receive the message GSVC312E starting CICS ?
search cancel

Why we receive the message GSVC312E starting CICS ?

book

Article ID: 46759

calendar_today

Updated On:

Products

SYSVIEW Performance Management NXBRIDGE - SYSVIEW/ENDEVOR

Issue/Introduction

The CICSTHRS member in parmlib contains the 'DEFINE IPCNCONN' and 'DEFINE IPCNSERV' sentences to define the  CICS IP Connections. Why, if the definitions in the CICSTHRS are correct, we receive the following messages starting the CICS Stc?

GSVC312E exception definition for ipcnconn failed. Invalid name  
GSVC312E exception definition for ipcnserv failed. Invalid name

Environment

Release:
Component: SYSVW

Resolution

This message (For variables IPCNCONN and IPCNSERV )  appears when the release of CICS is older or equal to 6.4   (CICS TS 3.1). The variables IPCNCONN and IPCNSERV are only valid for releases of CICS higher than 6.4 

If you use the Sysview command CVARS and search the word IPCNCONN you will see that the column C64 for the variables IPCNCONN and IPCNSERV is empty. This means that the variables are not valid for CICS 6.4. In order to avoid the messages GSVC312E you should update the CICSTHRS member to add )IF and )ENDIF sentences before and after the definition of these variables. 

Something like: 

)IF CICS GE 65 
DEFINE IPCNCONN ARG1 * STATE INSERVICE STATUS NORMAL
DEFINE IPCNCONN ARG1 * STATE OUTSERVICE STATUS WARNING
DEFINE IPCNSERV ARG1 * STATE ACQUIRED STATUS NORMAL
DEFINE IPCNSERV ARG1 * STATE OBTAINING STATUS HIGH
DEFINE IPCNSERV ARG1 * STATE RELEASED STATUS WARNING
DEFINE IPCNSERV ARG1 * STATE FREEING STATUS WARNING
)ENDIF