Since PMDF checks both the CONVERSIONS and SCRIPT mapping tables at the same time, it can happen that both the conversion and script channels are enabled. Since PMDF can queue a message to only one of these channels, it chooses the channel whose mapping table appears first in the mappings file.

The conversion and script channels can both be run, one after the other, by setting up the channels' mapping tables correctly.

For example, the following mapping tables cause the script channel to run first, followed by the conversion channel.

SCRIPT IN-CHAN=tcp_local;OUT-CHAN=l;SCRIPT Yes IN-CHAN=tcp_local;OUT-CHAN=msgstore;SCRIPT Yes IN-CHAN=*;OUT-CHAN=*;SCRIPT No CONVERSIONS IN-CHAN=script;OUT-CHAN=l;CONVERT Yes IN-CHAN=script;OUT-CHAN=msgstore;CONVERT Yes IN-CHAN=*;OUT-CHAN=*;CONVERT No