TSS WHOWNS RC 8 for Resources that Don't Exist

Products

• Top Secret
• Top Secret - LDAP

Issue/Introduction

When a WHOOWNS command is issued for a resclass with (*) requesting all ownerships for a resclass and none are found, an RC=8 is issued.  This is not an error situation, and therefore should be RC=4.  

ex. TSS WHOOWNS IBMFAC(*)

if no ownerships are found then 

 TSS0318E  RESOURCE NOT FOUND IN SECURITY FILE       
 TSS0301I  WHOOWNS  FUNCTION FAILED, RETURN CODE =  8
 READY                                               

It should be

 TSS0318E  RESOURCE NOT FOUND IN SECURITY FILE       
 TSS0301I  WHOOWNS  FUNCTION FAILED, RETURN CODE =  4
 READY                                               

 

 

Environment

Release : 16.0

Component : CA Top Secret for z/OS

Resolution

The RC 8 is not bug. It has been working like this for many years.

Changes would have to be considered an enhancement request.

Changing the RC from 8 to 4 might adversely affect existing client user applications since they are expecting a RC 8 for undefined resources when a TSS WHOOWNs is issued.


Please submit this idea on Ideation so it can be voted on and reviewed by Broadcom's development team and the Top Secret community. 

To request enhancement requests, please submit your idea to Ideation https://community.broadcom.com/ideation/allideas, so it can be voted on by the community and the Broadcom Top Secret development team..