On OpenVMS when using TCP/IP transport, you will need to define
PMDF-X400 as a TCP/IP service. For the various supported TCP/IP
packages, define a service at a TCP port, agreed upon with the remote
MTA configuration. The default TCP port used by X.400 over TCP is 102.
Specify the command procedure PMDF_COM:x400_slave.com for
DEC TCP/IP Services. For the other three TCP/IP products, specify the
executable PMDF_EXE:x400_slave.exe.
Also, if you are using a version of a TCP/IP package that supports DECnet/OSI directly listening on port 102 itself (such as MultiNet V4.1 rev A), and if you want to use port 102 for PMDF-X400, then you must configure DECnet/OSI without OSI over IP using DEC's @SYS$MANAGER:NET$CONFIGURE ADVANCED utility.
41.5.2.1 TGV MultiNet service definition
Use the MultiNet Server Configuration Utility to add the new TCP
service as follows:
$ MULTINET CONFIGURE/SERVER MultiNet Server Configuration Utility 3.2(32) [Reading in configuration from MULTINET:SERVICES.MASTER_SERVER] SERVER-CONFIG>ADD X400 [Adding new configuration entry for service "X400"] Protocol: [TCP] TCP Port number: 102 Program to run: PMDF_EXE:x400_slave.exe [Added service X400 to configuration] [Selected service is now X400] SERVER-CONFIG>RESTART
41.5.2.2 DEC TCP/IP service definition
Use the UCX Management Utility to add the new TCP service as follows:
UCX> SET SERVICE X400 - _UCX> /FILE = PMDF_COM:x400_slave.com - _UCX> /PROCESS_NAME = PMDF-X400 - _UCX> /USER_NAME = PMDF - _UCX> /PROTOCOL = TCP - _UCX> /PORT = 102 - _UCX> /LIMIT = 4 UCX> ENABLE SERVICE X400 UCX> SET CONFIGURATION ENABLE SERVICE X400 UCX> EXIT
41.5.2.3 Process Software TCPware service definition
Use the TCPware NETCU utility to define the X.400 service. In addition
to performing the definition interactively now, add the command to the
site-dependent server definitions file,
TCPWARE:servers.com, so that the definition will be in
place after future system reboots.
For TCPware V5.1 and later, define the service as follows:
$ RUN TCPWARE:netcu NETCU> ADD SERVICE 102 bg_tcp - _NETCU> /USERNAME = PMDF - _NETCU> /PROCESS_NAME = "PMDF-X400" - _NETCU> /INPUT = PMDF_COM:x400_slave.com
For TCPware V5.0 and earlier, define the service as follows:
$ RUN TCPWARE:netcu NETCU> ADD SERVICE 102 STREAM PMDF_EXE:x400_slave.exe - _NETCU> /PROCESS_NAME = "PMDF-X400" - _NETCU> /NOAUTHORIZE - _NETCU> /NOINPUT - _NETCU> /NOOUTPUT - _NETCU> /ERROR = nla0: - _NETCU> /PRIORITY = 4 - _NETCU> /PRIVILEGES = (all) - _NETCU> /UIC = [1,3] - _NETCU> /AST_LIMIT = 100 - _NETCU> /BUFFER_LIMIT = 32768 - _NETCU> /ENQUEUE_LIMIT = 400 - _NETCU> /EXTENT = 8192 - _NETCU> /FILE_LIMIT = 200 - _NETCU> /IO_BUFFERED = 30 - _NETCU> /IO_DIRECT = 30 - _NETCU> /MAXIMUM_WORKING_SET = 2048 - _NETCU> /PAGE_FILE = 60000 - _NETCU> /QUEUE_LIMIT = 100 - _NETCU> /RESOURCE_WAIT - _NETCU> /SUBPROCESS_LIMIT = 2 - _NETCU> /WORKING_SET = 1024
41.5.2.4 Wollongong PathWay service definition
Add a service definition for PMDF-X400 to the PathWay Access
servers.dat database as follows:
# # PMDF-X400 # service-name X400 program PMDF_EXE:x400_slave.exe socket-type SOCK_STREAM socket-options SO_ACCEPTCONN | SO_KEEPALIVE socket-address AF_INET , 102 working-set 1024 maxservers 4 priority 4 INIT TCP_Init LISTEN TCP_Listen CONNECTED TCP_Connected SERVICE Run_Program