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

book

Article ID: 3970

calendar_today

Updated On:

Products

CA Cleanup CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server 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 Top Secret CA Top Secret - LDAP CA 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.