PMDF System Manager's Guide

If messages are enqueued correctly (received into the PMDF_QUEUE: area) but not delivered, you should first check that processing jobs are being submitted and executed on the correct batch or Process Symbiont queue.

Channel jobs by default are submitted to the MAIL$BATCH queue; most sites choose to configure the MAIL$BATCH queue as a generic queue feeding several execution queues. (Some sites can also choose to use alternate queues in addition to MAIL$BATCH. So normally, you should expect to see channel jobs executing in MAIL$BATCH, or its execution queues if MAIL$BATCH is a generic queue, and perhaps additional channel jobs pending in MAIL$BATCH if all queue processing slots are already occupied processing other channel jobs. And if you are using additional queues, you should expect to see channel jobs moving through those other queues as well.

The DCL SHOW QUEUE command can be used to show any currently processing jobs in execution queues, or the PMDF PROCESS utility will also show currently executing PMDF jobs (as well as resident PMDF server processes, as discussed in Section 35.2.4 above).

When a message is moving through PMDF, you can stop a processing queue with a command such as

$ STOP/QUEUE/NEXT MAIL$BATCH

and then look to see if the correct job has been submitted. If a job has not been submitted or the job exits immediately without attempting delivery, then verify that the queue name matches that listed by PMDF TEST/REWRITE. If accounting is enabled on your system, then you can use the ACCOUNTING utility to display the exit status of the batch job. Problems can be due to improper definition of PMDF logical names or incorrect ownership of the PMDF_LOG: directory. The directory should be owned by the PMDF account, if you have one, or the SYSTEM account if you do not.