Sharing the zSecure Alert configuration file C2PCUST.
This procedure describes how to work with a shared zSecure Alert configuration file.
Resolving the problem
When you share the zSecure Alert configuration file between 2 or more systems you can use 1 system to update the C2PCUST configuration file.
Use the zSecure ISPF User Interface to update the configuration file, select/unselect, add, modify or delete alerts.
You do not have to stop the zSecure Alert started task C2POLICE.
When the modifications to the Alert configuration are done, do a Verify of the Alert configuration.
A Verify is to check the Alert configuration for errors and to make sure a Refresh can be done.
After a successful Verify do a Refresh of the Alert configuration.
The Refresh actually builds the production configuration.
If the Refresh is successful you are asked to do a refresh of the configuration in the C2POLICE task on the system where you have performed the configuration update.
If you skip this action the Alert configuration will be refreshed at the "environment refresh" interval which is specified in the Alert configuration. Use Browse on panel SE.A.A of the configuration to check the refresh interval value.
You can do a manual refresh of the Alert configuration on all systems with the operator command
F C2POLICE,REFRESH on each system. This will activate the new configuration immediately.
If you change any of the Alert configuration values like number of buffers, buffer size or intervals you need to issue the following command on all systems to activate these values:
|Security||IBM Security zSecure Alert for RACF||z/OS|
More support for:
IBM Security zSecure Alert for ACF2
zSecure Alert for ACF2
Software version: Version Independent
Operating system(s): z/OS
Reference #: 1426629
Modified date: 01 February 2017
Translate this page: