CICS monitor is not active (SV 14.2)

[Deactivated User]

Hello,
I am dbdc  guy primary, so sysview is new for me. I want ask about SYSVIEW monitor for CICS. I take new customer, with no documentation about sysview configuration or previous installation and so on… We have SYSVIEW V14.2, . CICS monitor not works: ( CICS004W*CICS monitor is not active) , but it seems that somebody tried setup it.

 I first check how it looks like in SYSVIEW in cics list: all cices has this information:
ExecStage:EXECUTING  Status:NOSTART   RowStat:NORMAL

So then I check how it looks like in CICS. SYSVIEW group is in CSD and is installed, GSVCGSVS program is in PLT table and CNM4BLOD in RPL. Also monitoring is on (MN=ON). During startup of cics appeared only this  message ,no any error or warning:

 
GSVC720I CA SYSVIEW for CICS request started     

GSVC713I Starting transaction GSVI               

GSVC720I CA SYSVIEW for CICS request complete    

....

GSVC716I Resource definition Type=TDQUEUE Object=GSVS defined       

GSVC720I CA SYSVIEW for CICS request started                        

GSVC716I Resource definition Type=PROGRAM Object=GSVCAPMX defined   

GSVC716I Resource definition Type=PROGRAM Object=GSVCAPMS defined   

GSVC716I Resource definition Type=PROFILE Object=GSVXALTS defined   

GSVC716I Resource definition Type=TCLASS Object=GSVCGSVS defined    

GSVC716I Resource definition Type=TCLASS Object=GSVCGSVI defined    

GSVC712I Resource definitions have been created                     

GSVC713I Starting transaction GSVI                                  

GSVC720I CA SYSVIEW for CICS request complete  

 

So on side of CICS seems everything ok.

 

So I continue to SYSVIEW side.

I didn't found any error or warning in SYSVIEW output. I checked if CICS option is enabled:

In GSVXGSVX member of Libarary GSVXSCFG is

Option-CICS                      Yes 

 

This information is also in output of running SYSVIEW. So CICS option is turned on in SYSVIEW.

 

Next I checked, if CICSDATA and CICSLOGR subtask. And thay are configured in sysview:

 

Command ASADMIN:

SYSVIEW  *        *        ACTIVE         

.        CICSDATA CICSDATA ACTIVE 

.        CICSLOGR          MODEL  

.        CICSLOGR CICLOG0P ACTIVE 

.        CICSLOGR CICLOG0T ACTIVE 

  

Jobname  Task     Id       Status  

SYSVUSER *        *        ACTIVE         

.        CICS     CICS     ACTIVE 

 

 And in used by sysview, LGLOGS:

 Name              Status

CICLOG0P.SYSD     ACTIVE

CICLOG0P.TRAN     ACTIVE

CICLOG0P.TSUM     ACTIVE

CICLOG0P.XLOG     ACTIVE

CICLOG0T.SYSD     ACTIVE

CICLOG0T.TRAN     ACTIVE

CICLOG0T.TSUM     ACTIVE

CICLOG0T.XLOG     ACTIVE

  

So I don't have any idea how to check it in sysview. So I tried found installation jobs(migration from 14.1 to 14.2)

I found some SAMPJCL library, but there is not notes. And I am not sure if previous SYSVIEW support team used those Libraries. It not help me. I see only option :  start all instalation jobs for CICS part : INST0052, INST0053, INST0060, INST0061, CICSMAPS 
but not sure if it is good idea.

This problem is outside of my knowledge.Probably previous support team missed some step during migration, or disable this CICS monitor some non-standard way. 

Honestly I don't know what next. Do you have any proposal how check what is wrong or any hint? 

[Todd J. Gagle]

Jan,

The GSVC messages that you have included are all the result of the GSVS transaction or GSVCGSVS program in the PLT.
This process will start the GSVI transaction which initializes the SYSVIEW for CICS data collector in the CICS region.
 
You need to determine if the GSVI transaction is executing.
The transaction GSVI runs as a system transaction and therefore will not be displayed using CEMT I TASK.
When GSVI starts additional messages will be written to the joblog such as the following:

GSVC024I (GSVI) CA SYSVIEW Performance Management
GSVC001I (GSVI) CA SYSVIEW for CICS Release 16.0.00 Build 0990
GSVC002I (GSVI) Copyright (C) 2019 CA Technologies, Inc.
GSVC003I (GSVI) z/OS Release = 2.3.0 System name = CA31
GSVC004I (GSVI) CICS Release = 7.2.0 HCI7200
GSVC050I (GSVI) System configuration options loaded for SSID SYSV
GSVC034I (GSVI) WARM start has been initiated
GSVC027I (GSVI) (GSVI) Services Userid = SYSVDEV
GSVC025I (GSVI) (GSVS) Initialization Tranid = GSVS
GSVC025I (GSVI) (GSVT) Initialization Tranid = GSVT
GSVC025I (GSVI) (GSVI) Initialization Tranid = GSVI

During the initialization process, additional SYSOUT ddnames will be created.
The ddname GSVCLOG will contain detailed initialization information.

You may want to view the ddname MSGUSR for additional information.

Since you did not mention the messages above, I have to believe that the transaction GSVI is not executing.
I would encourage you to open a support case at: https://casupport.broadcom.com/


Todd

------------------------------
Architect of Software Engineering, Team SYSVIEW
Broadcom
------------------------------

[Deactivated User]

Hi Todd,
I check CICSes output and all has SYSView ddname:
DDNAME StepName ProcStep
GSVCGSVS CICS RUN

And some CICSes has only those messages in this GSVGSVS log:
********************************* TOP OF DATA **********************************
2019/06/28 06:00:19.832 GSVC720I CA SYSVIEW for CICS request started
2019/06/28 06:00:19.846 GSVC713I Starting transaction GSVI
2019/06/28 06:00:19.847 GSVC720I CA SYSVIEW for CICS request complete
******************************** BOTTOM OF DATA ********************************

and some has more messages:

********************************* TOP OF DATA **********************************
GSVC716I Resource definition Type=TDQUEUE Object=GSVS defined
GSVC720I CA SYSVIEW for CICS request started
GSVC716I Resource definition Type=PROGRAM Object=GSVCAPMX defined
GSVC716I Resource definition Type=PROGRAM Object=GSVCAPMS defined
GSVC716I Resource definition Type=PROFILE Object=GSVXALTS defined
GSVC716I Resource definition Type=TCLASS Object=GSVCGSVS defined
GSVC716I Resource definition Type=TCLASS Object=GSVCGSVI defined
GSVC712I Resource definitions have been created
GSVC713I Starting transaction GSVI
GSVC720I CA SYSVIEW for CICS request complete
******************************** BOTTOM OF DATA ********************************


Also I check program directly in CICS and it was runnin onec.
I PROGRAM(GSVCGSVS)
STATUS: RESULTS - OVERTYPE TO MODIFY
Prog(GSVCGSVS) Leng(0000020832) Ass Pro Ena Pri Ced
Resc(0000) Use(0000000001) Bel Cex Ful Qua Cic Nat

but I will try do new definition of CICS resources and install that, because it look like that during migration process it wasn't done. 

[Todd J. Gagle]

It appears that the GSVI transaction is not getting started.
This could be due to security or other items.

The DDNAME GSVCGSVS is the output of the GSVCGSVS startup program typically run in PLT.
The startup process can also be started manually.
You may want to try this and see if you get a different result.
From a CICS terminal, enter the transaction: GSVS
This will issue a start for the GSVI transaction.

You check the GSVCGSVS program using CEMT.
Also check: CEMT I PROGRAM(GSVCGSVI)

You can execute the GSVS transaction under CEDF debugging.  This could help find the issue.
The contents of the DDNAME MSGUSR may also provide some insight to errors.

You can also use the transaction CEDX GSVI.
This would trap the execution of GSVI if it starts.

Give these ideas a try.

------------------------------
Todd J. Gagle
Architect of Software Engineering, Team SYSVIEW
Broadcom
------------------------------

[Deactivated User]

hello,
I tried start monitoring manually by tran : GSVS and also by GSVT RESTART
always same result - messages from cics output after restart:
GSVC715I CA SYSVIEW for CICS termination started
GSVC714I Request parms: GSVT RESTART
GSVC720I CA SYSVIEW for CICS request started
GSVC714I COMMAREA parms: GSVT RESTART
GSVC713I Starting transaction GSVI
GSVC720I CA SYSVIEW for CICS request complete

I check programs and it seems that GSVS transaction don't start GSVI, because GSVCGSVI program not run:
STATUS: RESULTS - OVERTYPE TO MODIFY
Prog(GSVCGSVI) Leng(0000035256) Ass Pro Ena Pri Ced
Resc(0000) Use(0000000000) Bel Cex Ful Qua Cic
Prog(GSVCGSVS) Leng(0000020832) Ass Pro Ena Pri Ced
Resc(0000) Use(0000000007) Bel Cex Ful Qua Cic
Prog(GSVCGSVT) Leng(0000012264) Ass Pro Ena Pri Ced
Resc(0000) Use(0000000001) Bel Cex Ful Qua Cic

so I try investigate it by CEDF transaction, but it was problem because GSVS has several pages of execution Inquire commands Like this:
EXEC CICS INQUIRE TDQUEUE
TDQUEUE ('GSVS')
NOHANDLE

STATUS: COMMAND EXECUTION COMPLETE
EXEC CICS INQUIRE PROGRAM
PROGRAM ('GSVCGSVI')
NOHANDLE

STATUS: ABOUT TO EXECUTE COMMAND
EXEC CICS INQUIRE PROGRAM
PROGRAM ('GSVCGSVT')
NOHANDLE

STATUS: ABOUT TO EXECUTE COMMAND
EXEC CICS INQUIRE PROGRAM
PROGRAM ('GSVCEXIT')
NOHANDLE

......


so I try PF4  (SUPPRESS DISPLAYS - Suppresses all EDF displays until the next stop condition occurs.), but it jump to end and just display message:
GSVC700I CA SYSVIEW for CICS initialization started

and nothing more. Probably I didn't use CEDF correctly, because I don't use it much.

I don't know why transaction GSVS not start tran GSVI and their program. Any Ideas?

[Todd J. Gagle]

Jan,

I would encourage you to open a support case. We will be able to provide the best support using this means.

A couple things to try:

1. Attempt to start the GSVI transaction manually. This will fail, but it might provide the clue that we need. The GSVI transaction must be started indirectly using the GSVS transaction. If you issue the GSVI directly from a terminal, you should receive the following message:

GSVC702I Please use transaction GSVS to initialize CA SYSVIEW for CICS

2. The GSVS transaction will issue an asynchronous start for the GSVI transaction. Based on messages, I believe that this is occurring. We could validate using CEDF
Issue CEDF
Then issue GSVS
Set stop condition of EXEC CICS START

------------------------------
Todd J. Gagle
Architect of Software Engineering, Team SYSVIEW
Broadcom
------------------------------

[Deactivated User]

hello,
Problem is solved. It was security problem. All definition in CICS and sysview was right. We have transaction security turn on and external security manager is ACF2 ( not RACF ). I don't know, why we didn't receive any warnings. But when we tried temporary disable security verification for GSVS,GSVT,GSVI transaction in our test cics, everything works fine. Thanks for help.