Top Secret r15.0 is Starting as a Subsystem; *TSS9069W TSS Started as a Subsystem, JES Sysout Unavailable; *TSS2069I Subsystem TSS is Active

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

After upgrading to Top Secret Release 15.0, Top Secret is starting as a Subsystem without making any changes to the normal IPL process. Starting Top Secret as a subsystem is an optional enhancement to the product.

Environment

Release: TOPSEC00200-15-Top Secret-Security
Component:

Resolution

If Top Secret is starting as a Subsystem you will see the following messages:

*TSS9069W TSS Started as a Subsystem, JES Sysout Unavailable.
*TSS2069I Subsystem TSS is Active.

Since we are now establishing a subsystem with the name TSS, the Top Secret started task will need to change to a different name to force it to run under the JES Subsystem. Modify commands and Stop commands will still use F TSS or P TSS respectively. There will be no changes in the way Top Secret works.