OSI/FTAM Programming Guide

HP NonStop OSI/FTAM Programming Guide—528612-001
1-1
1
Introduction to NonStop OSI/FTAM
Networks that consist of equipment provided by different vendors and following
different protocols are increasingly common, and in such networks, heterogeneous file
transfer and access is one of the most important and obvious computing requirements.
For instance:
•
Many kinds of applications require batch transfer of files: a file produced by an
application on one system is moved to another system for processing by an
application there.
•
In online transaction processing applications, an application on one type of system
might need information stored on another system. In this case, the application
needs access to the contents of a remote file.
•
In manufacturing or system management applications, it is often important to be
able to download software or control information from a controlling device to one or
more other devices.
•
Some file-transfer applications could almost be considered messaging
applications: information must be transferred from one location to another but is
too large or too costly to transfer through a messaging network.
Figure 1-1 on page 1-2 represents a (fictional) network in which several of these types
of file transfer and access exist. A chain of department stores uses NonStop systems
at its regional headquarters and its warehouses to handle applications for which
reliability and data integrity are crucial. Each retail store has an IBM AS400 computer
for point-of-sale applications. The headquarters, the warehouses, and the stores are all
connected by communications lines. Here are a few examples of transactions between
different types of systems in the network:
•
At the end of each day, sales figures from the stores are uploaded to headquarters
as a bulk file transfer.
•
In connection with sales on specific items, a pricing application at the headquarters
updates price records in store databases.
•
Occasionally, applications at the headquarters download information to the stores:
new warranty forms, pricing instructions for new lines of merchandise, or new
versions of software, reflecting feature enhancements or policy changes.
•
As necessary, an inventory control application at the headquarters sends order
information to external suppliers. These electronic data interchange (EDI)
messages can sometimes be too large or costly (in terms of resource use) to be
sent through a messaging system.
•
When a customer requests an item not in stock at the store, a clerk can send a
request to one or more warehouses to determine whether the item is in inventory
there.