Initialization problems

If Policy Agent does not complete initialization, or fails to install any policies in one or more stacks, run it with the -d 1 startup option, and check the log file for error conditions. If Policy Agent fails to initialize, message EZZ8434I is issued to the console. Check the log file for the specific error encountered.

Table 1 lists some common Policy Agent initialization problems.

Table 1. Common Policy Agent initialization problems
Problem	Cause/action	Symptom
Policy Agent started from a user ID without superuser authority	Policy Agent must be started from a superuser	EZZ8434I message, along with messages in the log file indicating that superuser authority is required and showing an exit code value of 27.
Policy Agent not authorized to security product	Policy Agent must be authorized to a security product profile. See z/OS Communications Server: IP Configuration Guide for details about setting up the proper authorization.	EZZ8434I message, along with messages in the log file indicating that the user is not authorized to start Policy Agent and showing an exit code value of 18.
When the SERVAUTH class is active, either: INITSTACK security product profile is not defined Policy Agent not permitted to the INITSTACK security product profile.	See Common AT-TLS startup errors for how to handle this startup error.	EZZ4248E message, and in the Policy Agent log file you see the SYSERR message that indicates that the socket could not open with errno= Resource temporarily unavailable., errno2=74610296.
Unable to read configuration file	The correct configuration file must be specified. See z/OS Communications Server: IP Configuration Guide for the search order used to locate the main configuration file. The file must exist. The permission bits must be correctly set for a z/OS® UNIX file system file. Because multiple configuration files might be configured, you might need to check these files also.	EZZ8434I message, along with messages in the log file indicating that the configuration file could not be opened and showing an exit code value of 1.
Unable to load one or more dynamic link libraries (DLLs) needed when Policy Agent is configured as a policy client	Policy Agent must have access to several DLLs at run time when configured as a policy client. These are needed to access PAPI functions and to establish an SSL connection to the policy server. Policy Agent accesses the DLLs using the LIBPATH environment variable. Check that the LIBPATH environment variable is specified, and that it contains the directory in which the DLLs reside. This is normally /usr/lib.	EZZ8780I message, along with messages in the log file indicating problems loading one or more of the following DLLs: papi.dll GSKSSL GSKCMS31