When C2POLICE STC is started, it terminates with error CKR1484
C2POLICE is started, but ends with the following message indicated in the sysout:
CKR1484 12 IPv4 AF_INET DGRAM UDP socket call for syslog failed RC 112 temporarily unavailable, reason 112B 00B6x file system suspended"
If Alert destination types of either SNMP, QRadar Unix syslog or ArcSight CEF via syslog are selected, C2POLICE requires the services of z/OS Unix and TCP/IP to be available for creating sockets.
Diagnosing the problem
C2POLICE starts, and immediately ends. Upon inspection of the STC sysout, message CKR1484 is shown.
Resolving the problem
Place C2POLICE far enough down in the IPL sequence to ensure that both OMVS and TCPIP have been initialized so that they are available at C2POLICE start up.
Further information can be found in the Security zSecure Suite: CARLa-Driven Components Installation and Deployment Guide, Chapter 12 Setting up zSecure Alert, Post-installation tasks, section Starting the zSecure Alert address space.:
"Start zSecure Alert soon after each IPL, using your Automated Operation software or PARMLIB member COMMNDxx. However, do not start zSecure Alert before OMVS is fully initialized. The following message indicates that OMVS is fully initialized:
BPXI004I OMVS INITIALIZATION COMPLETE
The wait is required because zSecure Alert requires TCP/IP services."
|Security||IBM Security zSecure Alert for ACF2|
|Security||IBM Security zSecure Alert for RACF|
More support for:
IBM Security zSecure Alert
Software version: Version Independent
Operating system(s): z/OS
Software edition: Enterprise
Reference #: 1382789
Modified date: 20 March 2018
Translate this page: