In addition to immediate channel jobs created automatically when messages are first submitted into PMDF, or to manually created delivery jobs as described above in Section 35.2.7, PMDF also has periodic jobs that perform clean up tasks, and retry delivery of previously undelivered messages.
$ SHOW QUEUE/ALL MAIL$BATCH
Figure 35-2 Output of SHOW QUEUE/ALL MAIL$BATCH on a Basic PMDF System
$ SHOW QUEUE/ALL MAIL$BATCH Generic server queue MAIL$BATCH Entry Jobname Username Blocks Status ----- ------- -------- ------ ------ 153 PMDF delivery SYSTEM 11 Holding until 18-NOV-2010 15:13 (1) 56 PMDF message bouncer SYSTEM 12 Holding until 19-NOV-2010 00:30 (2)
Figure 35-3 Output of SHOW QUEUE/ALL MAIL$BATCH on a System With Optional Jobs
$ show queu/all mail$batch Generic server queue MAIL$BATCH Entry Jobname Username Blocks Status ----- ------- -------- ------ ------ 95 PMDF delivery SYSTEM 14 Holding until 18-NOV-2010 15:52:00 (1) 810 PMDF message bouncer SYSTEM 14 Holding until 19-NOV-2010 00:30:00 (2) 399 PMDF PC Post SYSTEM 8 Holding until 18-NOV-2010 13:05:03 (3) 811 PMDF popstore message bouncer SYSTEM 5 Holding until 19-NOV-2010 00:30:00 (4)
The two holding jobs indicated in the figures as (1) and
(2) should always be present during normal operation of
PMDF. They run periodically and resubmit themselves automatically. If
you are using the PMDF popstore, you should also see a popstore return
job, (4), either holding or running (perhaps in an
execution queue, if MAIL$BATCH is a generic queue). If you are using
PMDF-LAN channels, then depending on just how you have configured it
you can also see an additional job, the PMDF PC post job,
(3); if you are using DECUS UUCP and have defined the
PMDF_DO_RETURN_VN logical so that
pmdf_submit_jobs.com also submits the DECUS UUCP message
bouncer job, then you should see that job as well.
PMDF_POST_INTERVALlogical name. If the PMDF delivery job is lost, messages that are not immediately deliverable will tend to collect in the queue and never be retried. In addition, channels marked with the
periodicchannel keyword, which defers immediate delivery, will not function reliably.
noticeschannel keyword. If the PMDF message bouncer job is not running, messages that cannot be delivered will sit in the message queue indefinitely and no notification will be sent to either the sender or the local Postmaster.
If one or both of the PMDF delivery job and the PMDF message bouncer
job is not present in the queue, (or if one of the other periodic jobs
that your site uses is missing), it should be resubmitted using the
pmdf_submit_jobs.combe executed as part of your normal system startup procedure to ensure that the basic PMDF periodic jobs are properly submitted and holding.