Previous | Next | Contents | Index |
If PMDF processing jobs run properly but the message stays in the
message queue directory, you can examine the log files to see what is
happening. All log files are created in the directory
/pmdf/log
. Log file name formats for various PMDF
processing jobs are shown in Table 36-1.
File name | Log file contains | |
---|---|---|
channel_master.log-
uniqueid
|
Output of master program (usually client) for
channel
|
|
channel_slave.log-
uniqueid
|
Output of slave program (usually server) for
channel
|
|
dispatcher.log-
uniqueid
|
Dispatcher logging, if the Dispatcher DEBUG option has been set | |
job_controller.log-
uniqueid
|
Job controller logging, if the Job Controller option DEBUG=1 has been set | |
server-name_server.log-
uniqueid
|
Logging for server
server-name
|
|
server-name_thread.log-
uniqueid
|
Per thread errors for
server-name
|
|
+ |
post.log-
uniqueid
|
Log output for the periodic PMDF delivery job |
+ |
return.log-
uniqueid
|
Log output for the periodic PMDF message bouncer job |
cron
; Process Software recommends
using crontab
entries that specify a log file of the name
shown.
Channel log files are not created unless an error occurs or unless
debugging output is enabled for the channel with the
master_debug
channel keyword or slave_debug
channel keyword. See Section 2.3.4.86 for more information.
Each new log file is created with a unique id to avoid overwriting an
earlier log written by the same channel. You can use the pmdf
find
utility to aid in finding the desired "version"
of a log file. You can purge back older log files using the pmdf
purge
command.
Previous | Next | Contents | Index |