search cancel

TSS MODIFY command to switch native UNIX security to HFSSEC for UNIX security

book

Article ID: 202870

calendar_today

Updated On:

Products

Top Secret

Issue/Introduction

Migrating from using HFSSEC security to native UNIX security questions.  

If the system options at IPL, comes up HFSSEC(OFF)
 
If there is an immediate issue and  need to back out and issue 
TSS MODIFY(HFSSEC(ON)) .
 
Would the HFSSEC class start to be honored for security authorization, or does
the user need to "logoff" before HFSSEC is honored for that user?
 
If the user was a started task acid, would that started task have to be stopped and
re-started before HFSSEC resources  to be honored for access authorization?   
 
 

Environment

Release : 16.0

Component : CA Top Secret for z/OS

Resolution

Would the HFSSEC class start to be honored for security authorization, or does
the user need to "logoff" before HFSSEC is honored for that user?

Answer:
The user does not need to signoff and back on, when TSS MODIFY HFSSEC command is issued.
 
If the user was a started task acid, would that started task have to be stopped and
re-started before HFSSEC resources  to be honored for access authorization?   

Answer:
No just like a signon user (TSO, CICS, etc)  the  permissions are in storage, when the HFSSEC value is ON, 
Top Secret will start  accessing them.