IBM Support

Enable syslog for TSAMP / RSCT / DB2

Question & Answer


Question

How do I setup syslog in such a way as to capture all relevant messages and errors from TSAMP and RSCT sub-systems, and the DB2 automation scripts ?

Answer

The RSCT and TSAMP daemon messages use the following facility and priorities to log to the syslog:
daemon:info
daemon:notice

The DB2 start/stop/monitor scripts use the following facility and priorities to log their messages to syslog:
user:info
user:debug


Therefore the following entry in the /etc/syslog.conf file would cover all and includes archiving every 24 hours with a history of 14 days:

*.debug /var/log/syslog.out rotate time 1d files 14

IMPORTANT: You will need to manually create the log file if it does not already exists before then refreshing the syslogd subsystem to pick up the changed configuration:


1. Create the new syslog output file:

touch /var/log/syslog.out



2. Restart syslogd to pick up the changes to its config file (/etc/syslog.conf)

refresh -s syslogd



Note: syslogs must be enabled on each server explicitly.

If you are using syslog-ng, refer to the following technote instead:
 
http://www.ibm.com/support/docview.wss?uid=swg21675952

[{"Product":{"code":"SSRM2X","label":"Tivoli System Automation for Multiplatforms"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"2.3;3.1;3.2;3.2.1;3.2.2;4.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

tsa;tsamp;db2;db2luw;rsct;

Document Information

Modified date:
14 July 2020

UID

swg21302886