Enqueue Names needed for CA Top Secret?

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

Question:

Are there any special Enqueue Names that need to be defined for CA Top Secret?

 

Answer:

Nothing needs to be defined to MIM or GRS for CA Top Secret.

CA Top Secret does all of it's Enqueuing locally, except for the Security File, and CA Top Secret doesn't issue any Hardware Reserves.

If sharing a Security File, and 'System A' has the Lock on the Security File, 'System B' knows this by a Header Record in the Security File. At that point, 'System B' will try again after a short delay. Also, if something else has a Hardware Reserve on the same Pack that the CA Top Secret Security File is on, CA Top Secret will wait until the Reserve is 'off'. If it turns out to be a long amount of time, CA Top Secret will issue the TSS123A message, stating what System has held the Lock and for how long for.

Environment

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