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


Article ID: 20018


Updated On:


CA Cleanup CA Datacom CA DATACOM - AD 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



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?


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.


Release: TOPSEC00200-15-Top Secret-Security