PMDF System Manager's Guide

This section lists options for enabling debugging of various PMDF facilities.

DEQUEUE_DEBUG (0 or 1)

This option specifies whether or not debugging output from PMDF's dequeue facility QU is produced. If enabled with a value of 1, this output will be produced on all channels that use the QU routines. The default value of 0 disables this output.

POST_DEBUG (0 or 1)

This option specifies whether or not debugging output is produced by PMDF's periodic delivery job. If enabled with a value of 1, this output will be produced in the post.log file. The default value of 0 disables this output. On UNIX, when debugging the periodic delivery job it can also be useful to set the PMDF tailor option PMDF_POST_VERIFY=1, to cause the delivery job script to echo which steps it has performed to the log file.

RETURN_DEBUG (0 or 1)

The RETURN_DEBUG option enables or disables debugging output in the nightly message bouncer batch job. A value of 0 disables this output (the default) while a value of 1 enables it. Debugging output, if enabled, appears in the output log file, if such a log file is present. However, on OpenVMS, the output log file is customarily discarded once the batch job terminates; thus to retain the output log file for inspection, the usual approach is to set RETURN_DEBUG and then use the SET ENTRY DCL command to modify the batch job itself to preserve the log file. On UNIX, the presence of an output log file is controlled by the crontab entry for the return job; see the appropriate edition of the PMDF Installation Guide for more details. On NT, the presence of an output log file is controlled by the Scheduler entry that schedules the running of the PMDF return job. On UNIX and NT, when debugging the periodic return job it can also be useful to set the PMDF tailor option (UNIX) or Registry entry (NT) PMDF_RETURN_VERIFY=1, to cause the delivery job script to echo which steps it has performed to the log file.