You can make changes to your security scheme and then activate those changes without cycling a CV. After changing security definitions using the #SECRTT macro and reassembling the RHDCSRTT module, you issue existing DCMT commands to vary the RHDCSRTT nucleus module to new copy and reload it.
Benefit
You can respond to changes in your security environment without bringing down a system and cycling a CV. For example, you can change the security mapping for a resource type or you can make changes to category and activity definitions.
What Gets Refreshed
When you reload the RHDCSRTT module, the following security definitions are refreshed and any changes you made to them are immediately implemented:
Signon Security Changes Not Immediately Implemented
Signon and system group security definitions are not refreshed when RHDCSRTT is reloaded; users signed on to the system remain signed on even after the reload. Any changes made to signon and system group security for users signed on to a system when a reload is done, do not take place until those users sign off of the system and then sign on again.
Example
After you change a security scheme and modify the RHDCSRTT module, perform the following to activate the changes:
The following example shows these commands.
dcmt vary nucleus module rhdcsrtt n c VARY NUCLEUS MODULE RHDCSRTT NEW COPY IDMS DC283001 V104 USER:ABBTH01 NUCLEUS MODULE RHDCSRTT MARKED TO NEW COPY
VARY NUCLEUS RELOAD IDMS DC283003 V104 USER:ABBTH01 NUCLEUS MODULE RHDCSRTT RELOADED IDMS DC283004 V104 USER:ABBTH01 CSA/NUCLEUS VECTOR TABLE UPDATED FOR NUCLEUS MODULE RHDCSRTT IDMS DC283007 V104 USER:ABBTH01 SECURITY TABLES REFRESHED SUCCESSFULLY
Note: For more information about the DCMT VARY NUCLEUS command, see the CA IDMS System Tasks and Operator Commands Guide.
|
Copyright © 2014 CA.
All rights reserved.
|
|