Question about SYSVIEW and SYSVUSER procedures

book

Article ID: 145142

calendar_today

Updated On:

Products

CA SYSVIEW Performance Management

Issue/Introduction

Comparing R150 and R142, SYSVIEW and SYSVUSER procedures now execute new programs:

R142    //SYSVUSER EXEC PGM=GSVXASCT,REGION=0M,TIME=1440,

R150    //SYSVUSER EXEC PGM=GSV$USER,REGION=0M,TIME=1440,


R142    //SYSVIEW  EXEC PGM=GSVXASCT,REGION=0M,TIME=1440,

R150    //SYSVIEW  EXEC PGM=GSV$MAIN,REGION=0M,TIME=1440,


GSVXASCT was the program for both procedures with SYSVIEW 14.2.  Now they are unique.  Does this change anything with the procedure startup order? 

Does anything change from this perspective?  GSVXASCT is still a valid load module of SYSVIEW 15.0. 

Trying to review the manuals for what the changes are, but they do not reference the new programs doing a search. 

The documentation still references GSVXASCT as the program the procedures run.

 

Cause

It was changed in Feature PTF SO06572 (CA SYSVIEW 15.0 FEATURE PTF 10), this is why this change was not seen in the Release Notes.

Environment

SYSVIEW 14.2 & 15.0 & 16.0 - z/OS supported releases - 

Resolution

Installing SYSVIEW 15.0 from complete GA pax file, or install 16.0, the generated procedures in SAMPJCL have a different PGM= value than they did prior. 

However, there is no functional difference using the new names or the old name GSVXASCT.  The three new PGM values are simply load module ALIAS of GSVXASCT. 

It was just a way to more easily externally identify SYSVIEW from SYSVUSER from SYSVAUX.

 

PROC      old PGM=   new PGM=

--------  ---------  -----------------

SYSVIEW   GSVXASCT   GSV$MAIN

SYSVUSER  GSVXASCT   GSV$USER

SYSVAUX   GSVXASCT   GSV$AUX