OSI/FTAM Configuration and Management Manual

Planning, Installing, and Configuring Tandem FTAM
OSI/FTAM Configuration and Management Manual—421944-001
3-44
Installing the Basic Components
•
Tandem FTAM does not retrieve application entity titles (AE titles) from the APPL
ENTRY configuration. If you are using the Tandem initiator and the remote FTAM
implementation expects to be sent local and/or remote AE titles, you can specify the
AE titles in your application, and the initiator will send the AE titles you specify. If
you do not specify AE titles in your application, the initiator will send the National
Institute of Science and Technology (NIST) default AE titles for local and remote
addresses. The default for both the local and remote AP title is {1 3 9999 1 7}. The
defaults for the AE-Qualifier are 0 for the local and 1 for the remote.
The Tandem responder does not return an AE title.
•
If the remote FTAM implementation expects to be sent an application entity title
(AE title) for the local system, you must provide the appropriate AE title for FTAM
in the APPL ENTRY configuration. According to the NIST stable agreements, this
AE title is
{ iso(1) identified-organization(3) oiw(14) ftamsig(5)
ftam-nil-ap-title(7) }
which would be specified in the SCF ADD ENTRY command:
{ 1, 3, 14, 5, 7 }
For an example OSI/AS configuration that supports the Example FTAM Configuration
on page 3-38, see Command File to Configure Tandem FTAM Addresses in OSI/AS on
page A-10. See Configuring FTAM Application Entities on page 3-59 for illustrations of
how application entities are configured for an FTAM initiator and responder.
Configuring FTAM to Make Use of FILCONF and D42 Changes
As of the D42 release, changes to the FILCONF file allow you to make the default
values of virtual filestore (VFS) parameters (such as string-significance,
maximum-string-length, and universal-class) configurable. If you want to
make use of FILCONF changes, add a DEFINE by name FTAMCONF before starting
the APLMGR:
ADD DEFINE =FTAMCONF, FILE $VOL.SUBVOL.FTAMCONF
where FTAMCONF is the name of the file that contains the VFS parameter default
values.
Changes to the FILCONF file also now enable the Tandem FTAM responder to
recognize filenames other than Guardian filenames. To make use of this feature, add a
DEFINE _ZOSF_FIXED_AS_UNSTRUCT before starting the APLMGR:
ADD DEFINE =_ZOSF_FIXED_AS_UNSTRUCT_, FILE $XX.YY.ZZ
D42 changes require the presence of an external translation application. A sample
translation application is provided with the FTAM subsystem in the file named
EXCTRAN1 and is installed as described in Appendix C, FTAM Software Files
.