Updating TSSPARM dynamically or at IPL only?

book

Article ID: 140826

calendar_today

Updated On:

Products

CA Top Secret CA Top Secret - LDAP

Issue/Introduction

There is a need to update TSSPARM for a new product called SailPoint.
Are there any risks with dynamically updating TSSPARM with the following and adding
the updates to TSSPARM for the next IPL?


There is a policy that updates to TSSPARM should only be done with an IPL.


Dynamic Commands:
    TSS MODIFY FAC(USER11=NAME=CTSA)                              
    TSS MODIFY FAC(CTSA=PGM=CTS)                                  
    TSS MODIFY FAC(CTSA=SHRPRF,ASUBM,NOABEND,MULTIUSER)           
    TSS MODIFY FAC(CTSA=LUMSG,NOSTMSG,SIGN(M),NORNDPW,NOXDEF)     
    TSS MODIFY FAC(CTSA=NOAUDIT,WARNPW,ACTIVE,NOTSOC)             
    TSS MODIFY FAC(CTSA=MODE=FAIL)
TSSPARM Update:
FAC(USER11=NAME=CTSA)                        
FAC(CTSA=PGM=CTS)                            
FAC(CTSA=SHRPRF,ASUBM,NOABEND,MULTIUSER)     
FAC(CTSA=LUMSG,NOSTMSG,SIGN(M),NORNDPW,NOXDEF)
FAC(CTSA=NOAUDIT,WARNPW,ACTIVE,NOTSOC)       
FAC(CTSA=MODE=FAIL) 

Environment

Release : 16.0

Component : CA Top Secret for z/OS

Resolution

There is no problem at all dynamically adding the FACILITY settings via the TSS MODIFY commands.

If the changes need to be permanent the changes should be put in the TSSPARM file.

Or they will get lost at an IPL, that is the only risk.