Each SNADS node must be configured to know about the PMDF-XGS transport bridge and about every host or mail system on the PMDF side which is to be directly addressable from the SNADS side. That is, at a minimum, each SNADS node must be configured to believe that the PMDF-XGS transport bridge is another SNADS node and that the PMDF system is a SNADS node reachable through the PMDF-XGS transport bridge. Once the PMDF system is reachable from SNADS, then any host or mail system reachable by PMDF may be made reachable from SNADS via aliased or embedded addressing; however, it is usually preferable to add additional routing information to the SNADS nodes to allow direct addressing from SNADS of other commonly addressed hosts or mail systems. The PMDF-XGS transport bridge looks to other SNADS nodes just like an AS/400 running OV/400. Other systems reachable through PMDF appear to the SNADS nodes as remote AS/400 systems.
The simplest way set up the SNADS nodes is to define directory
information on each of the SNADS nodes so that users *ANY
at PMDFnodeDGN, and users *ANY at
othersystemreachedthroughPMDF, are all at the
PMDF-XGS transport bridge (which appears to be another SNADS node), and
then to define to the SNADS nodes how to send mail to the PMDF-XGS
transport bridge. PMDFnodeDGN is technically the
PMDF node's DGN, from the SNADS point of view; however, as we consider
the PMDF node's REN to be the same as its DGN, it is the same value as
the PMDF node's REN (and thus effectively is the PMDF node name from
the SNADS point of view).
There are three parts to configuring an AS/400 node to connect to PMDF-XGS. On each AS/400 node, you must add directory information specifying that the user location for the PMDF system (and any other system reachable through PMDF that you wish to add) is on the PMDF-XGS transport bridge; see Section 42.6.2.1 . You must inform each AS/400 node how to route distributions to the PMDF-XGS transport bridge; see Section 42.6.2.2 . And you must configure the SNA connection; see Section 42.6.2.3 .
42.6.2.1 Adding directory information to an AS/400 node
For an AS/400 node, user locations are defined by issuing the command
WRKDIR for each SMTP node, and filling in the resulting screens as
shown in Figure 42-9 .
Figure 42-9 Defining SMTP Hosts to OV/400
ADD NEW DIRECTORY ENTRY USER userid..................: *ANY address.................: PMDFnodeDGN SYSTEM system name.............: bridgeREN system group............: ........ Indirect user.............: N Print personal mail.......: N ---------------------------------------- ADD NEW DIRECTORY ENTRY USER userid..................: *ANY address.................: anothersystemreachedthroughPMDF SYSTEM system name.............: bridgeREN system group............: ........ Indirect user.............: N Print personal mail.......: N ---------------------------------------- ADD NEW DIRECTORY ENTRY USER userid..................: *ANY address.................: yetanothersystemreachedthroughPMDF SYSTEM system name.............: bridgeREN system group............: ........ Indirect user.............: N Print personal mail.......: N ---------------------------------------- ...
42.6.2.2 Adding routing information on an AS/400 node
Each AS/400 node needs to be told how to route messages to the PMDF-XGS
transport bridge. Exactly where a particular AS/400 node should route a
distribution eventually intended for the PMDF-XGS transport bridge will
depend upon the topology of your SNADS network. The SNADS node directly
adjacent to the PMDF-XGS transfer system will need a new entry pointing
to the PMDF-XGS transport bridge; a SNADS node which is not adjacent to
the PMDF-XGS transport bridge, but which presumably does already have
an entry specifying how to get to the SNADS node which is adjacent to
the PMDF-XGS transport bridge, will also need a new entry for the
PMDF-XGS transport bridge similar to its current entry for a SNADS node
which is adjacent to the PMDF-XGS transport bridge.
Figure 42-10 Defining the route to the OS/2 transport bridge on an adjacent AS/400 node
ROUTING TABLE ENTRY
Destination system
Name / Group............: bridgeREN
Description...............: PMDF-XGS OS/2 transport bridge
Service level
Fast:
Queue name............: queuename
Maximum hops..........: *DFT
Status:
Queue name............: queuename
Maximum hops..........: *DFT
Data high:
Queue name............: queuename
Maximum hops..........: *DFT
Data low:
Queue name............: queuename
Maximum hops..........: *DFT
If the AS/400 node is adjacent to the PMDF-XGS transport bridge, then
it will need a new routing table entry along the lines of
Figure 42-10 . Here OS2systemname is the name
of the PMDF-XGS transport bridge and where
queuename is the queue name you will use for the
SNA link, as described in Section 42.6.2.3 .
If the AS/400 node is not adjacent to the PMDF-XGS transport bridge, then it will need a new routing table entry on how to get to the PMDF-XGS transport bridge similar to its current routing table entry on how to get to a SNADS node that is adjacent to the PMDF-XGS transport bridge. So to add the necessary routing information on an AS/400 node, first inspect the routing table entry for how to get to a node adjacent to the PMDF-XGS transport bridge. Then add a similar entry for the PMDF-XGS transport bridge itself.
For instance, if the routing table entry on an AS/400 node on how to get to a SNADS node adjacent to the PMDF-XGS transport bridge is as shown in Figure 42-11 ,
Figure 42-11 Existing routing table entry on an AS/400 node not adjacent to the PMDF-XGS transport bridge
ROUTING TABLE ENTRY
Destination system
Name / Group............: SNADSnodeadjacenttobridge
Description...............: node adjacent to the PMDF-XGS OS/2 system
Service level
Fast:
Queue name............: queuename
Maximum hops..........: *DFT
Status:
Queue name............: queuename
Maximum hops..........: *DFT
Data high:
Queue name............: queuename
Maximum hops..........: *DFT
Data low:
Queue name............: queuename
Maximum hops..........: *DFT
SNADSnodeadjacenttobridge is the name of a
SNADS node which is adjacent to the PMDF-XGS transport bridge and
queuename is the name of the queue for that
connection, then you will need to add a similar routing table entry for
the PMDF-XGS transport bridge. This new routing information for the
PMDF-XGS PMDF-XGS transport bridge can be added using the command
CFGDSTSVR, selecting "Routing Table Entry" and filling in the
information as in Figure 42-12 . Here bridgeREN
is the name of the PMDF-XGS transport bridge and
queuename should be the same queue as used in
Figure 42-11 . Note that you are not defining a new route; just
telling the AS/400 system to use the same route for mail bound for the
PMDF-XGS transport bridge as is used for mail bound for the SNADS node
adjacent to the PMDF-XGS transport bridge.
Figure 42-12 New routing table entry on an AS/400 node not adjacent to the PMDF-XGS transfer system
ROUTING TABLE ENTRY
Destination system
Name / Group............: bridgeREN
Description...............: PMDF-XGS OS/2 transport bridge
Service level
Fast:
Queue name............: queuename
Maximum hops..........: *DFT
Status:
Queue name............: queuename
Maximum hops..........: *DFT
Data high:
Queue name............: queuename
Maximum hops..........: *DFT
Data low:
Queue name............: queuename
Maximum hops..........: *DFT
42.6.2.3 Defining the SNA link on an adjacent AS/400 system
On an AS/400 system which is adjacent to the PMDF-XGS transport bridge,
the SNA link to the PMDF-XGS transport bridge must be defined. Such a
link is exactly the same as is required for a 5250 terminal session. So
if you normally define 5250 sessions statically on the AS/400, then you
can define the PMDF-XGS transport bridge exactly as you would any
terminal controller or OS/2 based emulator. If you normally allow your
5250 sessions to autoconfigure, then no steps are required to configure
the SNA connection to the PMDF-XGS transport bridge. In either case you
have to configure the AS/400 so that it can send the distributions
bound for the PMDF-XGS transport bridge over the right SNA session.
This is done using the command CFGDSTSRV, and selecting Routing Table
Entry and Distribution Queue Entry.
The routing table entry step may have been performed earlier, as described in Section 42.6.2.2 ; see in particular Figure 42-10 . The routing table entry tells SNADS that distributions bound for a particular node are to be put in a particular queue, and then the distribution queue entry tells SNADS how to send the distribution entries from a queue. So note that the queue name in the routing table entry must match the queue name in the distribution queue entry. Apart from that, the precise queue name used is not significant outside the AS/400, and it is common to use the same name for the queue as for the node at the other end of the link.
Figure 42-13 shows a distribution queue entry for an AS/400 node adjacent to the PMDF-XGS transport bridge; such an entry may be defined using the command CFGDSTSRV and selecting "Distribution Queue Entry".
Figure 42-13 Defining the AS/400 Distribution Queue for the OS/2 transfer system
DISTRIBUTION QUEUE
Queue name...............: queuename
Queue type...............: *SNADS
Remote location name.....: bridgeCPname
Mode name................: #BATCH
Remote net ID............: *LOCATTR
Local location name......: *LOCATTR
Normal priority
Send time:
From/to..............: 00:00 23:59
Force................: : :
Send depth.............: 1
High priority
Send time:
From/to..............: 00:00 23:59
Force................: : :
Send depth.............: 1
Normal priority
Send time:
From/to..............: 00:00 23:59
Force................: : :
Send depth.............: 1
queuename is the name chosen for the
distribution queue, matching that used in the routing table entry, and
where bridgeCPname is the SNA name of the
PMDF-XGS transport bridge, i.e., the Local Node Name
configured in Communications Manager on the PMDF-XGS transport bridge
system; see Section 42.6.3.1.1 .