TSS MODIFY(STATUS) Shows ADMINBY(NO), But Top Secret Doc Refers To "NOADMBY"

Products

• Top Secret
• Top Secret - LDAP
• Top Secret - VSE

Issue/Introduction

The output of a TSS MODIFY(STATUS) command shows ADMINBY(NO), but the Top Secret documentation refers to "NOADMBY".

Do both parameters mean the same thing?

Resolution

Yes. In the Top Secret parameter file, ADMINBY or NOADMBY can be specified.

NOADMBY is the default, so if nothing is set, it will use NOADMBY.

Specifying ADMINBY(YES) will display as ADMINBY on the TSS MODIFY(STATUS) output. ADMINBY(NO) will display as NOADMNBY.

When ADMINBY is enabled, Top Secret will record information in the ACID security records to indicate the following:

• Administrative ACID who performed the change
  
  
• Date, time, and system SMFID where the change was performed

ADMINBY data is stored when:

• An ACID is CREATEd
  
  
• FACILITY is ADDed
  
  
• Resources are PERMITted.

This information will be displayed, when the acid is listed. For example:

 TSS LIST(acid) DATA(ALL) 
 .              
 .                          
 .             
 XA DATASET = TEST.DATASET                                  OWNER(xxxxxxx ) 
    ACCESS  = READ                                                         
    ADMIN BY= BY(yyyyyyy )    SMFID(ssss)   ON(07/16/2008)  AT(09:48:51)  
 .                                                                         
 .      
 .            

The line with:

'ADMIN BY= BY(yyyyyyy ) SMFID(ssss) ON(07/16/2008) AT(09:48:51) '
is the administration by information.

• 'yyyyyyy' is the acid that issued the permit.
  
  
• 'ssss' is the system id where the permit was performed.

If NOADMBY is set, this information is not recorded on the acid and the 'ADMIN BY= ...' line will not show up in the TSS LIST output.

If ADMINBY was set at some point and is changed to NOADMBY, the 'ADMIN BY= ...' lines will not show up in the TSS LIST output.