IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Diagnosing problems with PAGENT and AT-TLS

To help with problem determination with PAGENT and AT-TLS, activate tracing and logging.

PAGENT has its own log file with the default name /tmp/pagent.log, which contains messages about loading AT-TLS rules. Invalid rules are rejected, and errors are written to the PAGENT log file. You can specify different levels of logging in the PAGENT configuration file by using the statement LogLevel. LogLevel 511 gives the most verbose logging.

The TCP/IP stack and the AT-TLS service log messages use SYSLOGD. The AT-TLS level of tracing is specified by using the advanced options in the connectivity rules. The highest (more verbose) level of tracing is 255.

The name and location of the log files are specified in the configuration file of the SYSLOGD (/etc/syslog.conf). The following example shows a configuration that can be used during testing:

*.* /var/log/%Y/%m/%d/errors

This syslogd configuration creates log files with names like /var/log/2010/03/20/errors. Every time syslogd is restarted, it creates a directory based on the current date. A good procedure is to restart syslogd once a day at midnight.

For more information, see the Diagnosing Policy Agent problems chapter of the z/OS® Communications Server IP Diagnosis Guide on the z/OS library web page.

bp22830_.htm |

Last updated Friday, 21 July 2017