HP 3000 Manuals HP 3000 Manuals
Mapping HP Desk Addresses onto Addresses on a Foreign System
There are two methods of mapping HP Desk addresses onto addresses on a
foreign system. They are the same methods used with Foreign Service
Connection (FSC). The two methods are:
* Foreign addresses
* Foreign aliases
Foreign Addresses
This method allows users to send messages from HP Desk through the
gateway to anyone, whether they are configured on HP Desk or not. The
foreign address can be up to 512 characters long.
Although this method allows users to send messages to people who are not
configured on HP Desk, to use it they have to type the foreign address
every time they want to include it in a Distribution List. This is
inconvenient for the user and can be a source of mistakes.
The need for users to type the foreign address each time they want to
send a message can be eliminated by configuring the foreign address at
the same time you configure the HP Desk name and mailnode. The foreign
address must be configured on the user's home computer (the computer
where he or she is defined as residing on a local node).
Foreign Address Aliasing
This allows HP Desk users to send messages to and receive messages from
users on non-HP Desk systems as if they were HP Desk users.
You configure the foreign system user as an HP Desk user on a mailnode
which resides on a gateway. You then assign him an alias which is his
address on the foreign system. For example:
Suppose there is a user, Pierre Kervella who is defined as KERVELLAP on
another manufacturer's computer. He is configured on the UNIX27 node
of your gateway. He is configured on your machine as Pierre
Kervella/UNIX27, where /UNIX27 is the mailnode routed through the gateway
to the other manufacturer's computer. When a message to him from an HP
Desk user reaches the gateway, the HP Desk address is replaced by the
address used for him on the other manufacturer's machine, that is
KERVELLAP.
The advantages of foreign address aliasing are:
* Your HP Desk users don't need to know about the foreign addresses
of the recipients of their messages.
* If you are part of a local network, the foreign alias only has to
be configured on the gateway computer.
* You can configure a number of associated foreign aliases for one
user. This allows your users to receive and reply to messages
from a number of foreign systems.
* You can also use HP Desk as a routing system and enable users on,
say an IBM PROFS system, to send messages to and receive messages
from users on say an IBM DISOSS system.
The disadvantage of foreign address aliasing is that initially
configuring the dummy HP Desk users and their associated foreign
addresses could be a large task depending on how many users are involved.
For this reason, it is best to restrict the use of foreign address
aliases to those people whom your HP Desk users send messages to and
receive messages from on a regular basis.
If you decide to use foreign address aliasing, your users can still
include explicitly declared foreign addresses in their Distribution
Lists. Either or both will be passed to or from HP Desk, depending on
Session Profile options.
Using the Transaction File to Supply and Receive Addresses and Aliases
Both foreign addresses and foreign aliases can be up to 512 bytes long.
If a user wants to use both these addressing methods it creates very
large Transaction File lengths resulting in a wastage of disc space. HP
Desk therefore provides a way for users to configure whether they want to
use foreign addresses, foreign aliases or both, and what length these
fields will be.
This configuration is done using the sp_extra_user_info field of the
session profile file. This is explained in Chapter 8 of this manual.
Although users may use both foreign addressing and foreign aliasing, it
is more usual to select just one addressing method.
The information provided in the sp_extra_user_info field of the Session
Profile file is used to interpret all the name and address information
contained in a submitted Transaction File (the tt_from, tt_to, tt_cc,
tt_bcc and other transaction records). In other words, you may tailor
the format of these transaction records to suit your application.
For example:
Suppose an sp_extra_user_info transaction record is included in a Session
Profile file with both foreign addresses and aliases supplied as follows:
Byte Position Contents
1 - 4 0
5 - 8 100100 (sp_extra_user_info)
9 - 16 0
17 - 20 1 (Foreign address alias)
21 - 24 20 (Maximum length of alias)
25 - 28 10 (Foreign address)
29 - 32 100 (Maximum length of address)
This means that the definition of the tt_to transaction, for example,
becomes:
Byte Position Contents
1 - 152 As described in Chapter 8 . These fields include the
HP Desk name and address of the recipient
153 - 172 Foreign alias
173 - 272 Foreign address
273 on Not used
To illustrate this further, here is an example of using foreign aliasing
with HPDGateSend and HPDGateReceive:
Suppose an HP Desk user, Andy Jogia, sends a message to David
Johnson/EXTERN/01. EXTERN/01 is routed through an Intrinsics gateway,
IGATE which is serviced by an Intrinsics application. David
Johnson/EXTERN/01 is aliased at IGATE to EXT_NAME_321.
The application provides a Session Profile file when it signs on to IGATE
which includes the following sp_extra_user_info transaction record.
Byte Position Contents
1 - 4 0
5 - 8 100100 (sp_extra_user_info)
9 - 12 0
13 -16 0
17 - 20 1 (Foreign address aliases)
21 - 24 20 (Maximum length of alias)
25 on 0 filled
When the application does an HPDGateReceive, and is given a Transaction
File holding the message from Andy Jogia, the Transaction File will
include a tt_to transaction record for recipient David Johnson as
follows:
Byte Position Contents
1 - 4 0
5 - 8 21100 (tt_to)
9 - 20 0
21 - 24 0 (Deliver to this user)
25 - 36 0
37 - 72 "Johnson"
73 - 108 "David"
109 - 144 spaces
145 - 152 EXTERN01
153 - 172 EXT_NAME_321 (left justified and space filled on the
right)
NOTE In this example the HP Desk name and node of David Johnson may not
be needed for the gateway application although HPDGateReceive will
always supply these fields even when foreign aliases are in use.
If David Johnson wanted to send a message back to Andy Jogia, using the
same Session Profile file as before, the Transaction File supplied to
HPDGateSend could include the following tt_creator transaction:
Byte Position Contents
1 - 4 0
5 - 8 10000 (tt_creator)
9 - 36 0 filled
37 - 152 spaces
153 - 172 EXT_NAME_321
HPDGateSend will translate the foreign alias EXT_NAME_321 into David
Johnson/EXTERN/01. When Andy Jogia receives the message at his HP Desk
terminal, the sender will be defined as David Johnson/EXTERN/01.