How to have two ISET statements for CA SYSVIEW in CA GSS?

book

Article ID: 50878

calendar_today

Updated On:

Products

CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA Cross Enterprise Application Performance Management (APM) CA SYSVIEW Performance Management NXBRIDGE - SYSYVIEW/ENDEVOR

Issue/Introduction

Description:

If your IMODs are currently in the CA SYSVIEW supplied ISET, how can you specify two ISET statements for CA SYSVIEW in CA GSS and have your own ISET as recommended by CA?

Many customers actually create their own IMODs. It is in the customer's best interest to keep their locally-written IMODs in a separate dataset. The reason for this is when a new release of CA SYSVIEW is shipped it is distributed with a new IMOD data set. This way, locally-written IMODS will not be overwritten.

Solution:

Supposing in GSS PARMLIB member RUNPARM you have coded:

INCLUDE SYSVTWO

and in GSS PARMLIB member SYSVTWO you have coded:

ISET    SYSVTWO  DSN CA.SYSVIEW.IMODLIB SSID ISRB FORCE LOAD

Then to specify a site-specific library change member SYSVTWO to something like:

ISET    SYSVTWO  DSN CA.SYSVIEW.IMODLIB SSID ISRB FORCE LOAD  <- CA SYSVIEW supplied ISET
ISET    YORIMOD  DSN YOUR.IMODLIB SSID ISRB FORCE LOAD        <- your own ISET

Environment

Release: FAQSO.00200-12.5-SYSVIEW-Performance Management
Component: