The PMDF TEST/CHANNEL X400 utility can be used to test the
    configuration of the X400_LOCAL channel and verify that it can
    successfully connect to the remote MTA. Network configuration
    errors and validation problems will be reported by the utility.

    Any file can be specified for transfer via the /TRANSFER
    qualifier. However, if the file does not contain P1/P2/P22
    information valid to the remote X.400 MTA, then the behavior
    is undefined. Some X.400 MTAs, such as PMDF-X400 and HP's Message
    Router X.400 Gateway, MRX, will accept any data and generate an
    error at a later stage in processing. Other MTAs, such as PP and
    EAN will abort the network connection as soon as they detect that
    the incoming data is invalid.

    If PMDF TEST/CHANNEL X400 does not complete the connection
    successfully, it will indicate whether it is having trouble
    making the network connection itself or the network connection
    is rejected due to validation failure. If the former, make sure
    that the remote TSAP address is correctly specified for this MTA.
    If the latter, then check the MTA names and passwords. Remember
    that each MTA validates the name and password sent by the other
    MTA. Both sides of the connection must pass validation or the
    connection will be terminated with a validation failure error.
    Log or trace information on the remote MTA can prove invaluable
    when tracing validation failures or problems with messages being
    rejected.

    An additional level of detail, showing every I/O operation as
    well as every byte of data sent and received on the network
    connection, can be enabled by defining the logical name PMDF_
    UNIXLIB_TRACE before running PMDF TEST/CHANNEL X400. The
    equivalence value for the logical name may be a filename or the
    reserved word "TTY". In the latter case, trace output will be
    directed to the process's SYS$OUTPUT. For example:

    $ DEFINE PMDF_UNIXLIB_TRACE TTY

    followed by a PMDF TEST/CHANNEL X400 command will result in all
    of the test output as well as a complete trace of all data sent
    and received. The additional level of detail afforded by I/O
    tracing may be required should you need to work with Process
    Software support personnel to solve a problem.