System Shutdown Order With CA Top Secret At End Of Day

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:

When using an automation tool to pilot our system, what is the order to shutdown the operating system at the end of day?

Solution:

The consensus is what follows:

If you don't want the $$$LOG$$ file, you shutdown JES, CA Top Secret and then the AT (Automation Tool). This is with OPTION(78) active in CA Top Secret.

If the AT gets violations being shutdown last, then the order to shutdown should be: JES, the AT and then CA Top Secret . The AT caused a security check to occur and CA Top Secret was no longer up. So, we need to shut it down before CA Top Secret. If SA390 didn't cause a security check to occur, then it could be shutdown after CA Top-Secret.

If you want the $$$LOG$$ file, then the shutdown order should be: CA Top Secret, JES, and then the AT.

If the AT gets violations with this order, shutdown the AT first, TSS and then JES, because the AT is causing a security check to occur and TSS needs to be up to process that check.

Environment

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