TSSXTEND Utility With WHOHAS With Top Secret

Products

• Top Secret
• Top Secret - LDAP

Issue/Introduction

When copying the security file using the TSSXTEND utility in Top Secret, the WHOHAS option can be specified to automatically clean up broken pointers identified in the TSSFAR RESOURCE output. However, after running a TSSXTEND WHOHAS, there are still broken pointers which are listed at the end of the TSSXTEND report. TSSFAR and TSSXTEND still show that there are broken pointers. 

Environment

z/os

Cause

TSSXTEND WHOHAS has limitations when correcting broken pointer issues. 

Resolution

TSSXTEND WHOHAS has limitations when correcting broken pointer issues. The broken pointers that cannot be repaired will be reported in the TSSXTEND WHOHAS output.

• If the problem is for an owned resource, the resource should be removed from the acid and, optionally, added back. You can UNDERCUT it to a different acid or UNDERCUT it temporarily to a different acid and then UNDERCUT it back to the original acid.
  For example, there is a broken pointer showing DEPTA owns DSN(ABC.), but TSS LIST(DEPTA) DATA(OWN) doesn't show the ownership and TSSXTEND with WHOHAS did not correct this. The following can be done:
  TSS ADD(DEPTB) DSN(ABC.) UNDERCUT NOPERMIT
  TSS ADD(DEPTA) DSN(ABC.) UNDERCUT NOPERMIT
  TSS LIST(DEPTA) DATA(OWN) to confirm DEPTA correctly owns DSN(ABC.)
  
  
  
• If the problem is for a permitted resource, the resource can be revoked from the acid and, optionally, permitted back.
  For example, there is a broken pointer showing USERA is permitted UPDATE access to DSN(ABC.XYZ), but TSS LIST(USERA) DATA(XAUTH) doesn't show the permission and TSSXTEND with WHOHAS did not correct this. The following can be done:
  TSS REVOKE(USERA) DSN(ABC.XYZ) 
  TSS PERMIT(USERA) DSN(ABC.XYZ) ACCESS(UPDATE)
  TSS LIST(USERA) DATA(XAUTH) RESCLASS(DATASET) to confirm USERA is permitted UPDATE access to DSN(ABC.XYZ)