/sys$common/syshlp/HELPLIB.HLB  —  PMDF  TEST  /CHANNEL

1  –  X400

    Test X.400 channel connection.

    Syntax

      PMDF TEST/CHANNEL  X400

    Command Qualifiers             Defaults

    /MTA=mta-id                    See text
    /TRANSFER=file-spec            See text

1.1  –  Restrictions

    This utility is supplied only with the PMDF-X400 optional layered
    product.

1.2  –  Parameters

 X400

    The string parameter X400 is required.

1.3  –  Description

    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.

1.4  –  Command Qualifiers

1.4.1    /MTA

       /MTA=mta-id

    Specifies the MTA to connect to when PMDF-X400 is configured for
    more than one remote MTA. This qualifier is only applicable when
    PMDF-X400 has been configured to support more than one remote
    MTA. The mta-id value must be an MTA identification as defined in
    the X400-MTAID database. Note that in a single MTA configuration,
    as generated by the PMDF CONFIGURE X400 utility, there is no MTA
    identification nor X400-MTAID database.

1.4.2    /TRANSFER

       /TRANSFER=file-spec

    Use RTS to transfer the specified file, file-spec. If no file is
    given it will default to NLA0: and transfer 0 bytes of data. Note
    that transferring 0 bytes of data by specifying /TRANSFER is not
    the same as transferring nothing, which is the behavior when this
    qualifier is not present.

1.5  –  Examples

  $ PMDF TEST/CHANNEL X400
  23:12:57.74: RTS rts_send: initializing
  23:12:57.85: RTS Transfer mode is NORMAL 1988
  23:12:57.85: RTS rts_send: preparing for RTS transfer to MTA
  23:12:57.85: RTS rts_send: found cached connection, slot = 0
  23:12:57.85: RTS rts_
 send: no cached connection, opening new connection
  23:12:57.85: RTS88 Local host is NAPLES.EXAMPLE.COM
  23:12:57.85: RTS88 Connecting to "MTA"/"MTA"/"X400-88"
    /Internet=OTHERMTA.EXAMPLE.COM
  23:12:57.85: RTS88.Request user-data: MTA-
 NAME [MyMTA]     PASSWORD [secret]
  23:12:57.89: RTS88 Called presentation address: "MTA"/"MTA"/"X400-
 88"
    /Internet=12.34.56.78
  23:12:57.90: RTS88 Calling presentation address: "MTA"/"MTA"/"PMDF-
 X400"/
  23:12:58.55: RTS.Response user-data: MTA-
 NAME [OtherMTA]     PASSWORD []
  23:12:58.55: RTS rts_send: Connection successful sd = 4
  23:12:58.57: RTS rts_send: new connection cached, slot = 0
  23:12:58.57: X400 TEST: RTS test successful!
  23:12:58.57: RTS rts_disconnect_all
  23:12:58.57: RTS disconnecting slot 0
  23:12:58.57: RTS88 rts88_disconnect: closing sd 4
  23:12:58.57: RTS88.CloseRequest

      This example shows testing an outgoing X.400 connection for a
      configuration with an PMDF_TABLE:X400_LOCAL_OPTION. file of:

      MODE=1988-NORMAL
      LOCAL_MTANAME="MyMTA"
      LOCAL_PASSWORD="secret"
      LOCAL_ADDR="MTA"/"MTA"/"PMDF-X400"
      REMOTE_MTANAME="OtherMTA"
      REMOTE_PASSWORD=""
      REMOTE_ADDR="MTA"/"MTA"/"X400-88"/Internet=OTHERMTA.EXAMPLE.COM
Close Help