JES TYPE And LEVEL When Starting CA Top Secret Before JES

Products

• Cleanup
• Datacom
• DATACOM - AD
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• 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
• Top Secret
• Top Secret - LDAP
• Top Secret - VSE

Issue/Introduction

Description:

If CA Top Secret is started before JES2 via SUB=MSTR, TYPE=2 (or JES2) and LEVEL=SP n.n.n must be added to the CA Top Secret parameter file. Does this mean these parameters will need to be updated every time JES2 is upgraded?

Solution:

If CA Top Secret is started before JES, both TYPE and LEVEL (or RELEASE) should be specified in the JES control option in the CA Top Secret parameter file. If the wrong TYPE and/or LEVEL are specified, it should still be ok. If no TYPE and/or LEVEL are specified, a TSS9112E-UNABLE TO DETERMINE JES LEVEL message will be issued. In addition, certain offsets may not be set properly.

Sometimes the next level of JES uses the same LEVEL= as the previous JES level, but most of the time, yes the LEVEL= parameter should be updated with every JES2 upgrade. TYPE= will stay the same.

Environment

Release:
Component: AWAGNT