OSI/AS Programming Manual

Before Running Your Application Program
APS Procedures Programming Concepts
2–24 056783 Tandem Computers Incorporated
Before Running Your
Application Program
Before your application establishes a connection, your system manager (or whoever is
responsible for system management at your installation) should make the preparations
summarized below. The Tandem OSI/AS Configuration and Management Manual
provides detailed instructions for performing these tasks.
The system manager must register your application by including the following
information in the Management Information Base (MIB):
The OSI address of your application.
The OSI address of each remote application with which you wish to initiate
connections. Note that an application that is not in the information base can
always attempt to initiate a connection with your application.
The name you assign to your application, if any, and the names you assign to
any remote applications you wish to refer to by name.
Note The OSI address and the application name are optional, but you must supply one or the other for your
application and for each remote application with which you wish to initiate connections. If you supply
both, the address will be used and the application name will be ignored.
The system manager must set up access points and processes, as follows:
The local TSEL (transport selector) must be configured, and the TAPS process
serving it must be started.
The local NSAP (network service access point) must be configured with an
SNPA (subnetwork point of attachment), and the TSP (transport service
provider) process serving it must be started.
In some cases, a remote NSAP must be configured with an SNPA. For details,
refer to the SCF Reference Manual for Tandem OSI/TS or the Tandem OSI/TS
Management Programming Manual.
The local SNPA must be configured, and the NSP (network service provider)
process serving it must be started.
If you are using ACSE, you can configure any application entity titles for your
application and for each of the remote applications with which it
communicates.
Note that the TAPS process uses the MAXCONNECTIONS attribute to determine the
maximum amount of data that it can send to the underlying TSP process in a single
write. This allows the TAPS process to conserve file-system space. Larger values of
MAXCONNECTIONS will result in a smaller maximum write size.