How Sysview determines the JES level

Article Id: 50346

Status: Published

Updated On: 14-02-2018 07:22

Legacy Id: TEC553461

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:

A JES Configuration module MUST be assembled and linked for EACH system that you intend to use CA SYSVIEW.

Solution:

You will need to rerun the INST0020 job to assemble and link Jes Configuration modules for EACH system that uses CA SYSVIEW.
The module name (e.g.: JES2111) that you specify in the JES member must match with the name specified in the job INST0020 on the SET MODULE= statement

Environment:

Release:
Component: CA90S