TSS AND WLM

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

IBM recommends to affect the SYSSTC service class to RACF. What about TOP-SECRET?

Environment

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

Resolution

While we make no specific recommendations on this, the general idea is that TSS requires more services than any of the address spaces that need TSS services on a regular basis (such as CICS address spaces) but not necessarily as much as address spaces that do not (such as VTAM).

When we talk about requiring TSS services, we are mainly talking about signon activity.

Resource checking is done within an address space and usually does not require TSS services from the TSS address space.

In WLM terms, this is probably closer to the choice of running it as a separate WLM Service Class, although for the most part TSS will need more service than almost anything not in SYSTEM or SYSSTC.

Then, the TSS STC can be run in the SYSSTC WLM class.