The section shows the details of how the sample site shown in Figure 4-1 would be configured.
Configuration of the SNADS nodes.

1. Add directory information on the adjacent DISOSS node BLUE for the PMDF OpenVMS system naples.example.com and other systems reached via PMDF. Add this directory information with commands:

   ADD USERTYPE='REMOTE' DDN='NAPLES' SA='*' RGN=' ' REN='BRIDGE'. ADD USERTYPE='REMOTE' DDN='MILAN' SA='*' RGN=' ' REN='BRIDGE'.

   
   

2. Add routing information on the adjacent DISOSS node BLUE for how to send distributions to the OS/2 transport bridge BRIDGE. Add this routing information with the command:

   ADD RGN=' ' REN='BRIDGE' TRANSID='DSVE' SSL='*' QUEUE=BRID

   Here BRID is the CICS name for the LU for the BRIDGE system, matching the name used during the CICS configuration step described below in step 3.
   

3. Define the SNA link in VTAM and CICS on the adjacent DISOSS node APPLE. The exact specifications required will depend upon what is already defined at a site. For instance, suppose that the control point name of the node BRIDGE, as specified as the SNA node name given in the Communications Manager definition on BRIDGE, is NECTAR. And suppose that CICBLUE is the VTAM application name (APPL) for where DISOSS is running. Then an appropriate VTAM definition might look something like:

   LKNECTAR PU ADDR=04, CPNAME=NECTAR XID=YES,RESSCB=2 NECTAR LU LOCADDR=0, DLOGMOD=#BATCH, LOGAPPL=CICBLUE ... CICAPPLE APPL ACBNAME(CICBLUE)

   here LKNECTAR is the PU name given to the node BRIDGE (which need not match any definition on BRIDGE itself). Other parameters can be specified, similar to those for a 3270 connection from BRIDGE to BLUE. A corresponding CICS definition must be created with the commands

   CEDA DEFINE GROUP(abc) CONNECTION(BRID)

   and

   CEDA DEFINE GROUP(abc) SESSION (xyz)

   yielding screens

   CEDA DEFine BRID Group DEscription ==> PARTNER LU CONNECTION IDENTIFIERS Netname ==> NECTAR INDsys ==> REMOTE ATTRIBUTES REMOTESystem ==> REMOTEName ==> CONNECTION PROPERTIES ACessmethod ==> Vtam Vtam|IRc|INdirect|Xm Protocol ==> Appc Appc | Lu61 SInglesess ==> No Yes | No DAtastream ==> User User|3270|SCs|Strf|Lms RECordformat ==> U U | Vb OPERATIONAL PROPERTIES + AUtoconnect ==> No No | Yes | All INService ==> Yes Yes | No SECURITY SEcurityname ==> ATtachsec ==> Local Local|Identify|Verify |Persistent|Hixidpe BINDPassword ==> PASSWORD NOT SPECIFIED BINDSecurity ==> No No | Yes

   and

   CEDA DEFine Sessions : xyz Group : abc DEscription ==> SESSIONS for PARTNER LU SESSION IDENTIFIERS Connection ==> BRID SESSName ==> NETnameq ==> MOdename ==> #BATCH SESSION PROPERTIES Protocol ==> Appc Appc | Lu61 MAximum ==> 002 , 000 0-999 RECEIVEPfx ==> RECEIVECount ==> 1-999 SENDPfx ==> SENDCount ==> 1-999 SENDSize ==> 1920 1-30720 RECEIVESize ==> 1920 1-30720 + AUtoconnect ==> No No | Yes | All INService ==> Yes Yes | No SECURITY SEcurityname ==> ATtachsec ==> Local Local|Identify|Verify |Persistent|Hixidpe BINDPassword ==> PASSWORD NOT SPECIFIED BINDSecurity ==> No No | Yes

   
   

4. Add directory information on additional DISOSS nodes for the PMDF system naples.example.com and other systems reached via PMDF. On the node INDIGO, add this directory information with the commands:

   ADD USERTYPE='REMOTE' DDN='NAPLES' SA='*' RGN=' ' REN='BRIDGE'. ADD USERTYPE='REMOTE' DDN='MILAN' SA='*' RGN=' ' REN='BRIDGE'.

   
   

5. Add routing information on additional DISOSS nodes for how to send distributions to the PMDF-XGS transport bridge BRIDGE. On a DISOSS node such as INDIGO, there should already be a routing table entry describing how to send distributions to BLUE, the SNADS node adjacent to the OS/2 transport bridge. Add a similar entry for the OS/2 transport bridge itself. For instance, if the routing table entry on INDIGO on how to send to BLUE is:

   ADD RGN=' ' REN='BLUE' TRANSID='DSVE' SSL='*' QUEUE='QCOX'.

   then add a similar routing table entry:

   ADD RGN=' ' REN='BRIDGE' TRANSID='DSVE' SSL='*' QUEUE='QCOX'.

   
   

6. Add directory information on additional AS/400 nodes. On the nodes AZULE and LAPIS in turn, issue the WRKDIR command for each of NAPLES and MILAN in turn, filling in the resulting screens along the lines of:

   ADD NEW DIRECTORY ENTRY USER userid..................: *ANY address.................: NAPLES SYSTEM system name.............: BRIDGE system group............: ........ Indirect user.............: N Print personal mail.......: N ---------------------------------------- ADD NEW DIRECTORY ENTRY USER userid..................: *ANY address.................: MILAN SYSTEM system name.............: BRIDGE system group............: ........ Indirect user.............: N Print personal mail.......: N ---------------------------------------- ADD NEW DIRECTORY ENTRY USER userid..................: *ANY address.................: CUPID SYSTEM system name.............: BRIDGE system group............: ........ Indirect user.............: N Print personal mail.......: N ----------------------------------------

   
   

7. Add routing information on additional AS/400 nodes for how to send distributions to NAPLES, a.k.a. naples.example.com. Suppose the existing routing table entry on node AZULE for routing to BLUE is:

   ROUTING TABLE ENTRY Destination system Name / Group............: BLUE Description...............: node adjacent to XGS bridge Service level Fast: Queue name............: FUJI Maximum hops..........: *DFT Status: Queue name............: FUJI Maximum hops..........: *DFT Data high: Queue name............: FUJI Maximum hops..........: *DFT Data low: Queue name............: FUJI Maximum hops..........: *DFT

   Then on AZULE issue the command CFGDSTSVR, select "Routing Table Entry" and create the new routing table entry for routing to BRIDGE:

   ROUTING TABLE ENTRY Destination system Name / Group............: BRIDGE Description...............: PMDF-XGS transport bridge Service level Fast: Queue name............: FUJI Maximum hops..........: *DFT Status: Queue name............: FUJI Maximum hops..........: *DFT Data high: Queue name............: FUJI Maximum hops..........: *DFT Data low: Queue name............: FUJI Maximum hops..........: *DFT

   Suppose that on the node LAPIS, which routes messages to BLUE by way of AZULE, that the existing routing table entry for routing to BLUE is:

   ROUTING TABLE ENTRY Destination system Name / Group............: BLUE Description...............: node adjacent to XGS bridge Service level Fast: Queue name............: YELLOW Maximum hops..........: *DFT Status: Queue name............: YELLOW Maximum hops..........: *DFT Data high: Queue name............: YELLOW Maximum hops..........: *DFT Data low: Queue name............: YELLOW Maximum hops..........: *DFT

   Then on LAPIS, issue the command CFGDSTSVR, select "Routing Table Entry", and create the new routing table entry for routing to BRIDGE:

   ROUTING TABLE ENTRY Destination system Name / Group............: BRIDGE Description...............: PMDF-XGS transport bridge Service level Fast: Queue name............: YELLOW Maximum hops..........: *DFT Status: Queue name............: YELLOW Maximum hops..........: *DFT Data high: Queue name............: YELLOW Maximum hops..........: *DFT Data low: Queue name............: YELLOW Maximum hops..........: *DFT

   
   
   Configuration of the PMDF-XGS transport bridge.

8. Configure TCP/IP on the PMDF-XGS transport bridge. We suppose that the site is using OS/2 Warp Connect. If TCP/IP has not already been configured on the OS/2 system, perform the normal TCP/IP configuration using the IBM-supplied "TCP/IP configure" program. Then perform the following additional steps. On the PMDF-XGS transport bridge OS/2 system, edit the file \mpts\etc\hosts and if it is not already defined, define the hostname localhost as

   127.0.0.1 localhost

   Edit the file \mpts\bin\setup.cmd and if it is not already present, add the line

   ifconfig lo 127.0.0.1

   Use the configuration notebook to configure adding and starting an SNMP daemon supporting the dpi interface; you want the line

   start /min snmpd -dpi shm -dpi tcp

   added to the \mpts\bin\tcpstart.cmd
   

9. Configure the SNA connection on the PMDF-XGS transport bridge. On the PMDF-XGS transport bridge, run the Communications Manager setup program, cmsetup.exe. Assume that the example.com site uses GROLY as the Network ID for (all) its SNADS nodes. In the local node definition, enter GROLY as the Network ID, enter NECTAR as the Local Node name, and enter 05D and 00000 as the Local Node ID. Assume that you are using a LAN connection between the PMDF-XGS transport bridge and the adjacent SNADS node, and that the LAN address of that adjacent SNADS node is 123456789012, and assume that the VTAM name of the adjacent BLUE node is CPBLUE. In the SNA connection definition, enter GROLY as the Partner Network ID, CPBLUE as the Partner Node Name, and 123456789012 as the LAN Destination Address. In the partner LU definition, enter CPBLUE as the Network ID, CICBLUE as the LU Name, and LOCAL as the Alias. In the symbolic destination definition, enter LOCAL as the Symbolic Destination Name and Partner LU Alias, enter X'21'002 as the Partner TP, enter NONE as the Security, and enter #BATCH as the Mode Name. In the transaction program defaults definition, delete the * value from Directory For Inbound Attaches. Having used Communications Manager for this configuration, a Node Definition File should now be present in Communications Manager's cmlib directory, looking like:

   DEFINE_LOCAL_CP FQ_CP_NAME(GROLY.NECTAR ) CP_ALIAS(NECTAR) NAU_ADDRESS(INDEPENDENT_LU) NODE_TYPE(EN) NODE_ID(X'05D00000') NW_FP_SUPPORT(NONE) HOST_FP_SUPPORT(YES) MAX_COMP_LEVEL(NONE) MAX_COMP_TOKENS(0); DEFINE_LOGICAL_LINK LINK_NAME(LINK0001) FQ_ADJACENT_CP_NAME(GROLY.CBLUE ) ADJACENT_NODE_TYPE(LEARN) DLC_NAME(IBMTRNET) ADAPTER_NUMBER(0) DESTINATION_ADDRESS(X'12345678901204') ETHERNET_FORMAT(NO) CP_CP_SESSION_SUPPORT(NO) SOLICIT_SSCP_SESSION(NO) ACTIVATE_AT_STARTUP(YES) USE_PUNAME_AS_CPNAME(NO) LIMITED_RESOURCE(USE_ADAPTER_DEFINITION) LINK_STATION_ROLE(USE_ADAPTER_DEFINITION) MAX_ACTIVATION_ATTEMPTS(USE_ADAPTER_DEFINITION) EFFECTIVE_CAPACITY(USE_ADAPTER_DEFINITION) COST_PER_CONNECT_TIME(USE_ADAPTER_DEFINITION) COST_PER_BYTE(USE_ADAPTER_DEFINITION) SECURITY(USE_ADAPTER_DEFINITION) PROPAGATION_DELAY(USE_ADAPTER_DEFINITION) USER_DEFINED_1(USE_ADAPTER_DEFINITION) USER_DEFINED_2(USE_ADAPTER_DEFINITION) USER_DEFINED_3(USE_ADAPTER_DEFINITION); DEFINE_PARTNER_LU FQ_PARTNER_LU_NAME(GROLY.CICBLUE ) PARTNER_LU_ALIAS(LOCAL) PARTNER_LU_UNINTERPRETED_NAME(CICBLUE ) MAX_MC_LL_SEND_SIZE(32767) CONV_SECURITY_VERIFICATION(NO) PARALLEL_SESSION_SUPPORT(YES); DEFINE_PARTNER_LU_LOCATION FQ_PARTNER_LU_NAME(GROLY.CICBLUE ) WILDCARD_ENTRY(NO) FQ_OWNING_CP_NAME(GROLY.CPBLUE ) LOCAL_NODE_NN_SERVER(NO); DEFINE_DEFAULTS IMPLICIT_INBOUND_PLU_SUPPORT(YES) DEFAULT_MODE_NAME(BLANK) MAX_MC_LL_SEND_SIZE(32767) DEFAULT_TP_OPERATION(NONQUEUED_AM_STARTED) DEFAULT_TP_PROGRAM_TYPE(BACKGROUND) DEFAULT_TP_CONV_SECURITY_RQD(NO) MAX_HELD_ALERTS(10); DEFINE_CPIC_SIDE_INFO SYMBOLIC_DESTINATION_NAME(LOCAL ) PARTNER_LU_ALIAS(LOCAL ) MODE_NAME(#BATCH ) SNA_SERVICE_TP_NAME(X'21',002); START_ATTACH_MANAGER;

   
   

10. Configure the programs on the PMDF-XGS transport bridge. If you have not yet installed the PMDF-XGS programs on the PMDF transport bridge system, then do so now. The installation procedure will also ask you configuration questions and will generate a xgs.cmd in accordance with your answers. Suppose that your CD-ROM drive is D: and that you are running the PMDF-XGS transport bridge installation procedure install.cmd directly off the PMDF distribution CD-ROM, and that you want to install the PMDF-XGS transport bridge programs in the directory C:\xgs.

    [D:\other\os2\xgs]install.cmd PMDF / SNADS server installation Where do you want the code installed [C:\XGS]? C:\XGS ... PMDF / SNADS server configuration tool configuring control element The active components introduce themselves to the control process using a TCP/IP conversation. What port is to be used for this conversation [9990]? 9990 The control process needs an SNMP community name to register the Gateway MIB. What community name is going to be used [public]? public One or more SNADS receive processes can be configured How many receive processes should be run [1]? 1 The receive processes need to connect to the PMDF MTA What is the TCP/IP hostname of the machine running PMDF? apollo.example.com What port is the SNADS receive process on the PMDF machine listening on Port number [9993]? 9993 What is the SNADS name of the Gateway? bridge What is the maximum document size to be accepted by the Gateway [10000000]? 10000 000 What is the TCP/IP host name of the syslog host [localhost]? localhost What directory is to be used to store captured SNADS distributions [.\capture]? .\capture There can be several SNADS send processes. Each listens on a separate port and is typically used to send to a different SNADS node. What port number should the first SNADS send process use [9994]? 9994 What port number should the next SNADS send process use? (press enter to end) make sure that c:\xgs is added to the libpath in config.sys [C:\other\os2\xgs]

    The resulting xgs.cmd file will be:

    start xcontrol public 9990 start recvsrv apollo.example.com 9993 BRIDGE 10000000 localhost 9990 .\capture start sendsrv 9994 localhost 9990 .\capture

    Run the xgs.cmd procedure. Shadow the xgs.cmd icon to the system's "Startup" folder so that it will be autostarted.
    

11. Configure PMDF-XGS on the PMDF system. Use the PMDF-XGS configuration utility to generate suitable PMDF configuration files.

    $ PMDF CONFIGURE XGS PMDF-XGS configuration utility, Version 5.1 ... SNADS name of this PMDF system known to the SNADS world []? APOLLO TCP/IP name of the OS/2 system acting as the bridge []? bridge.example.com SNADS REN name of the OS/2 system acting as the bridge []? BRIDGE TCP/IP port number the sendsrv on the OS/2 system listens on [9994]? 9994 TCP/IP port number the snads_slave program listens on [9993]? 9993 SNADS REN name of the SNADS system immediately adjacent to the OS/2 bridge []? BLUE Domain name corresponding to previous SNADS system []? blue.example.com. SNADS RGN name of the SNADS system immediately adjacent to the OS/2 bridge [none]? Name of a SNADS system to which PMDF will route mail [RETURN if no more]? INDIGO Domain name corresponding to previous SNADS system []? indigo.example.com Name of a SNADS system to which PMDF will route mail [RETURN if no more]? AZULE Domain name corresponding to previous SNADS system []? azule.example.com Name of a SNADS system to which PMDF will route mail [RETURN if no more]? LAPIS Domain name corresponding to previous SNADS system []? lapis.example.com Name of a SNADS system to which PMDF will route mail [RETURN if no more]? [RETURN] Domain name of an SMTP system from which PMDF will route mail []? milan.example.com Domain name of an SMTP system from which PMDF will route mail []? [RETURN] ...

    The resulting xgs.chans file will have a channel definition

    snads_local defragment 733 header_733 maxheaderaddrs 1 \ addrsperfile 256 charset7 US-ASCII charset8 ISO-8859-1 SNADS-DAEMON NAPLES

    and the xgs.rules file will have rewrite rules

    INDIGO $U%indigo.example.com $U%INDIGO@SNADS-DAEMON$E$F indigo.example.com $U%INDIGO@SNADS-DAEMON$Qsnads_local indigo.example.com $U%indigo@SNADS-DAEMON AZULE $U%AZULE.example.com azule.example.com $U%AZULE@SNADS-DAEMON$E$F azule.example.com $U%AZULE@SNADS-DAEMON$Qsnads_local azule.example.com $U%banana.example.com@SNADS-DAEMON LAPIS $U%lapis.example.com lapis.example.com $U%LAPIS@SNADS-DAEMON$E$F lapis.example.com $U%LAPIS@SNADS-DAEMON$Qsnads_local lapis.example.com $U%lapis.example.com@SNADS-DAEMON BLUE $U%lapis.example.com blue.example.com $U%BLUE@SNADS-DAEMON$E$F blue.example.com $U%BLUE@SNADS-DAEMON$Qsnads_local blue.example.com $U%blue.example.com@SNADS-DAEMON milan $U%milan.example.com$Msnads_local

    and the snads_local_option. file will be

    ADJACENT_NODE_REN=BLUE BRIDGE_HOST=bridge.example.com BRIDGE_PORT=9994 BRIDGE_REN=BRIDGE

    and the dispatcher_xgs.cnf file will be

    [service=SNADS] port=9993 image=PMDF_EXE:SNADS_SLAVE.EXE logfile=PMDF_LOG:SNADS_SLAVE.LOG

    As the xgs.checklist directs, edit your pmdf.cnf file to insert or activate references to xgs.chans and xgs.rules and edit your dispatcher.cnf file to activate the reference to dispatcher_xgs.cnf and edit your PMDF alias file to insert the alias to be directed to the addressing channel.
    

12. If you are using a compiled configuration, recompile and reinstall it. Restart the PMDF Service Dispatcher.
    
13. Try sending a test message from PMDF to SNADS, and another test message from SNADS to PMDF.