TSS WHOHAS UID(0) Output Shows ACIDs That Do Not Have UID(0)

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:

The output of a TSS WHOHAS UID(0) command shows ACIDs that do not have UID(0) when listed (TSS LIST(acid) DATA(ALL) ). Why does this happen and what can be done to correct this?

Solution:

To clean up these broken pointers, issue the following for the ACID:
TSS ADD(acid) UID(0)
TSS REM(acid) UID(0)
Then reissue the TSS WHOHAS UID(0) command to confirm the broken pointers have been corrected.

This type of error can occur if an ACID with a UID is deleted and the UID was not removed before deleting the ACID and then a TSS WHOHAS UID(0) is not done before creating a new ACID that reuses the ACID number that the previously deleted ACID was using. So to prevent the potential for this to occur, either remove the UID on the ACID before deleting it and/or issue TSS WHOHAS UID(0) on a regular basis.

Environment

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