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

Products

• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• Datacom/AD
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware
• Compress Data Compression for MVS
• Compress Data Compression for Fujitsu
• Cross Enterprise Application Performance Management (APM)
• SYSVIEW Performance Management
• NXBRIDGE - SYSVIEW/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: