| Previous | Next | Contents | Index |
While diagnosing a PMDF delivery problem it can be useful to run a PMDF delivery job by hand, particularly after enabling debugging output for one or more channels; see Section 2.3.4.86 for details on enabling debugging. The command
$ @PMDF_COM:submit_master channel-name |
channel-name This is the
same submit logic used when messages are accepted from VMS MAIL by PMDF
for immediate delivery. If debugging is enabled for the channel in
question, then submit_master.com will create a log file in
PMDF_LOG: as described in Table 35-1.
$ @PMDF_COM:master channel-name |
channel-name in the currently active process,
with output directed to your terminal. This can be more convenient than
submitting a job, particularly if you suspect problems with job
submission itself.
In addition to channel-name both
master.com and submit_master.com will accept
several other parameters:
$ @PMDF_COM:master channel-name [poll [since-time]] $ @PMDF_COM:submit_master channel-name [poll [queue-name [since-time]]] |
channel-name
|
Required parameter specifying the channel. This determines which
messages will be attempted and what channel master program will be
executed. Channels known to your PMDF configuration appear as channel
block names in your
pmdf.cnf file.
|
poll
|
Optional parameter is a keyword specifying either
poll,
nopoll, or
ignore.
nopoll is the default and avoids executing the channel
program if there are no messages awaiting outbound delivery. If the
channel supports it,
poll will execute the channel master program to pick up
messages from a remote slave.
ignore is used only by the G3_TO_FAX channel and causes
time stamp checking to be bypassed.
|
queue-name
|
Optional parameter specifying the queue for submission. Applies to
submit_master.com only.
|
since-time
|
Optional parameter specifying an OpenVMS date/time. Only messages queued after this date/time will be processed. |
| Previous | Next | Contents | Index |