OSI/FTAM Configuration and Management Manual

What’s New in This Manual
OSI/FTAM Configuration and Management Manual—421944-001
xiv
Manual Changes
•
High-PIN processes. By default, FTAM processes now run at a high PIN. If you
want the APLMGR to run at a low PIN, you must specify this in the RUN
command. For initiator and responder processes, you can specify the attribute
HIGHPIN OFF in the SCF ADD PROCESS or ALTER PROCESS command. For
more information, see the OSI/FTAM and OSI/APLMGR SCF Reference Manual.
•
TCP/IP software and hardware requirements. Table 1-1 on page 1-14 now
includes the communications controller requirements for NonStop TCP/IP wide area
networks (WANs). Table 1-2
on page 1-14 includes the product number (T9551) for
NonStop TCP/IP.
•
Increased FPDU size. Tandem FTAM can send and receive FTAM protocol data
units (FPDUs) up to 16 kilobytes (KB) in length.
•
Changes in responder ownership can affect the execution of the following
nonsensitive commands, which cannot be executed through the APLMGR process
but must be sent directly to the responder: TRACE PROCESS and STATS
PROCESS or STATS SU with the RESET option. See the note on page 2-7
.
•
Recompiling responder object files. If applications using the Tandem responder
access SQL tables as FTAM-2 files, you must use NonStop SQL to recompile the
responder object files. See Recompiling Responder Object Files Using NonStop
SQL on page 3-42.
•
FILCONF changes. As of the D42 release, changes to the FILCONF file allow you
to make the default values of virtual filestore (VFS) parameters configurable.
FILCONF changes also now enable the FTAM responder to recognize filenames
other than Guardian filenames. See Configuring FTAM to Make Use of FILCONF
and D42 Changes on page 3-44.
•
Opens field in detailed STATUS SU command display. The Opens field displays
the number of associations that have a particular subdevice open. This field was not
described in earlier editions of this manual. See page 4-23 for a sample display of
the STATUS SU (Detail) command and an explanation of the Opens field.
•
Nativization. The D43 product version of OSI/FTAM is nativized to utilize the
features of RISC processors. This improves its performance in terms of end-to-end
throughput and percentage of CPU utilization.
•
Reconfiguring TPDUSIZE for TCP/IP and PAM. The default value of
TPDUSIZE is 512 bytes, which is appropriate if the data-value parameter in your
application’s calls to FTM_DATA_REQ_ and FTM_DATA_IND_ is small (less than
450 bytes per call). However, if your application is using a larger data-value size,
you should reconfigure the TPDUSIZE attribute to take advantage of blocked I/O
operations. For PAM-based (or TLAM-based) configurations, increase the value of
TPDUSIZE to 8192 bytes; for TCP/IP-based configurations, increase it to 65531
bytes. See Reconfiguring OSI/AS Subsystem Attributes
on page 5-16.
•
FTAM manuals and related manuals. The titles of some of the manuals that
describe FTAM, OSI/AS, OSI/TS, underlying subsystems, and related products have
changed. See FTAM Manuals on page xviii and Related Manuals on page xx. Also
included are descriptions of manuals for the PAM and NonStop TCP/IP subsystems.