HP 3000 Manuals HP 3000 Manuals
Gateway Operations
The Foreign Service Connection (FSC) and External File Transfer (EFT) are
explained in more detail in HP DeskManager Customization.
Outgoing Messages
Messages to be delivered to EFT/FSC mailnodes are held in MPE files on
your system. These files usually reside in HPMAIL.HPOFFICE but you can
change this if you wish (See Chapter 11 for more information.)
To initiate delivery of these EFT/FSC messages, you need to run the
external application program designed to transport EFT/FSC messages to
and from the foreign system.
You might find it useful to restrict the availability of the FSC gateway
to, say, 15 minutes every hour. This is because every time the Master
Truck connects to a gateway, it opens a message (E) file. If the gateway
is always open, you will have a large number of E files containing one,
or maybe two messages. However, if the gateway is only available for
short periods of time, all of the messages which are waiting for the
gateway to open will be written to a single E file. If too many E files
are created, they might overflow the Directory.
In order to ease the administration of the interface to the foreign
system, and make recovery easier should it become necessary, you can
specify an MPE group in which to keep the message and contents (C) files
to be sent through the FSC gateway.
The group must be in the HPOFFICE account. It is a good idea to make
this the same group as the one in which the IPC file through which HP
Desk communicates with the external application is kept.
Furthermore, the group must already exist within the HPOFFICE account and
must allow WRITE and SAVE capabilities for the external application
program.
Incoming Messages
When you receive incoming EFT/FSC messages on your computer, information
about the files in which the incoming messages reside is held in IPC
files according to the format of the gateway through which the messages
are received:
HP Desk Internal format EFTIPCIN.MAILDB.HPOFFICE
(EFT)
ARPA Standard or ARPA ARPAIPC.MAILDB.HPOFFICE
Compressed format (FSC)
ARPA Reference format AREFIPC.MAILDB.HPOFFICE
(FSC)
To bring the messages into HP Desk, you should use whichever of the
following operator commands relates to the type of truck you wish to
enable:
MAILEFTON EFT Truck
MAILFSCARPAON FSC ARPA Truck
MAILFSCAREFON ARPA Reference Truck
Further details on these commands can be found in the Chapter 20 .
Distribution of Incoming FSC Messages
The FSC Truck on a gateway computer constructs an HP Desk Distribution
List from the information contained in the ARPA header of an incoming
message. If this information is insufficient to resolve the intended
recipient, a copy of the message is sent to the Default User on the
gateway mailnode. The information might be insufficient if the address
or user name is unrecognizable by HP Desk.
The minimum addressing information that must be provided by the foreign
system in the FROM, TO, CC or BCC entries of the message header is a
surname. Any additional names, or address information, will assist HP
Desk to ensure correct distribution.
Generally, the HP Desk Distribution List retains all the information
given in the message header, to assist in the resolution of the intended
recipients. The only exception to this is that no unique combination of
name and address will be duplicated in the HP Desk Distribution List. If
such duplication occurs in the message header, only the last occurrence
will appear in the HP Desk reconstruction. Similarly, the Default User
will receive only one copy of the message regardless of the number of
names or addresses that HP Desk is unable to resolve.
The Default User performs the same function for FSC messages as the
General Delivery does for messages sent over data communication lines.
This is why it is a good idea to configure General Delivery as the
Default User. As with General Delivery, you should check the Default
User at least once a day for new mail. You should resolve any
unrecognizable names and addresses, and forward the messages to their
intended recipients.
The Default User has to resolve the names and/or addresses from the
information available to them in the message header and reconstructed
Distribution List. Whenever a message is delivered to General Delivery,
a list of "lost" addressees for the local node is displayed. The person
responsible for General Delivery can use the BURST command to print one
copy of the message for each lost user on the list.
The following table shows the delivery decisions made by HP Desk for
various combinations of name and address. A name or address (location or
mailnode) is recognizable if it is correctly configured on the gateway
computer. In any other case the name or address is unrecognizable. HP
Desk always examines the address first when establishing the validity of
a name/address combination; consequently if an address is given but is
not recognized by HP Desk, the name will not be tested. However if no
address is given, HP Desk will test the name and, if this can be
recognized, adds the appropriate address.
Information in Each Entry of Distribution List Message sent to
Name Present? Address Present?
--------------------------------------------------------------------------------------
NO NO Default User
YES (Unrecognized or YES (Unrecognized or
malformed) malformed) Default User
YES (Malformed) YES (Recognized) Default User
YES (Unrecognized or NO
recognized but
duplicate) Default User
YES (Recognized and unique) NO Specified name at
configured
address
YES (Matches a configured YES or NO HP Desk name and
foreign address for address
a specified gateway) corresponding
to the configured
foreign address
YES (Unrecognized) YES (Remote node) Specified name at
specified address
YES (Unrecognized) YES (Local node) Message will go to
General Delivery
for that node
YES (Recognized) YES (Recognized) Specified name at
specified address
--------------------------------------------------------------------------------------
If a foreign system delivers a message with an apparently unrecognizable
foreign address field, it will try to match the address with one of the
locations and sublocations in the HP Desk database. If the initial
characters of the foreign address do not appear to correspond to a
configured mailnode, a copy of the message is sent to the Default User.
Use of Distribution Lists by Foreign Systems
The FSC Trucks can recognize and process an HP Desk distribution list
specified by a foreign system in the ARPA header of a message. The name
of the list must be preceded by a colon within the quotes, but in all
other respects the format will be as for an ordinary TO, CC or BCC entry.
For example:
TO : ":MANAGERS" @ []
indicates that the message is intended for all the names that appear in
an HP Desk Distribution List known as "MANAGERS". Since the individual
addresses are contained within the list, no address is required in the
message header, so that this field can be left empty (that is, just type
[] as in the example above). If the named list is found, all the names
in that list will be added to the TO category of addressees for the
message, regardless of the categories within the Distribution List.
HP Desk checks the Default User's List Area for the Distribution List.
If it cannot find the list it checks the Public Distribution Lists which
the Default User has access to. If the named list cannot be found, or if
more than one list of that name is found, a single copy of the message is
delivered to Default User.
The names and contents of HP Desk Distribution Lists to be used by
foreign systems must be agreed between the HP Desk Administrator for the
gateway machine and his counterpart on the foreign system.
Acknowledgments
In the case of EFT nodes, acknowledgment levels 2 to 5 are maintained
since these are treated as HP Desk messages. Level 1 is assumed as soon
as the message is placed in the E file and a record has been placed in
the gateway IPC file.
In the case of FSC nodes, acknowledgment level 1 is generated within the
HP Desk system in the usual way. Other levels of acknowledgment depend
on the cooperation and capability of the foreign system involved. Every
FSC message contains in its ARPA header, the information a foreign system
needs if it is to return a meaningful acknowledgment to HP Desk. Full
details are given in the manual HP DeskManager Customization.