If a procedure in the AUTOLOG list also has a PORT statement reserving
a TCP or UDP port but does not have a listening connection on that
port, TCP/IP periodically attempts to cancel that procedure and start
it again.
Guideline: Do not use AUTOLOG to start
the Policy Agent if any listening connections are used. The Policy
Agent is unlike typical servers, and performs functions outside the
realm of listening for connections from other applications. Sometimes
during normal operation of the Policy Agent, listening connections
are unavailable for short periods of time. When listening connections
are unavailable, it is possible that the AUTOLOG timer could restart
the Policy Agent.
Policy Agent optionally listens on one or more of the following
ports:
- The pagentQosListener port (usually defined in the /etc/services
file as port 1700). This happens only when the PolicyPerfMonitorForSDR
statement is configured for a given TCP/IP stack.
- The port defined or specified by default on the ClientConnection
statement, which is used to listen for remote policy client connections
on all TCP/IP stacks.
- The port defined or specified by default on the ServicesConnection
statement, which is used to listen for services requester connections
on a single TCP/IP stack. For information about the ServicesConnection statement and specifying
which stack to use to listen for these connections, see z/OS Communications Server: IP Configuration
Reference.
If you want to start Policy Agent with AUTOLOG, you must take one
of the following actions:
In addition, when the PolicyPerfMonitorForSDR statement is being
used, if the pagentQosCollector port (usually defined in the /etc/services
file as port 1701) is reserved in the PORT list it should always be
specified with the NOAUTOLOG parameter, because this port is never
used as a listening port. For example:
PORT
1701 TCP PAGENT NOAUTOLOG
Tip: When Policy Agent is not listening on any ports,
you can use the autostart feature of AUTOLOG as previously described.
However, the monitoring and automatic restart features of AUTOLOG
are unavailable because AUTOLOG must listen to a TCP or UDP connection.
If you fail to take one of the above actions, Policy Agent will
be periodically canceled and restarted by TCP/IP.