OSI/FTAM Configuration and Management Manual

Planning, Installing, and Configuring Tandem FTAM
OSI/FTAM Configuration and Management Manual—421944-001
3-37
Determining Access to Tandem Responders
In a production environment, you might want to set the value to 1, so that you can see all
protocol errors:
ADD PROCESS $AMGR.#FTAMI.FTI2, NAME $FTI2, COMNAME "FTMI2", &
THRESHOLD 1
You also can use this attribute for troubleshooting. A large number of protocol errors
may indicate potential FTAM software or interoperability problems. For more
information on handling these types of problems, see Section 6, FTAM Troubleshooting
.
Determining Access to Tandem Responders
As described in Security of Files in a Tandem Responder’s Virtual Filestore (VFS) on
page 3-19, you can handle the security of files in a Tandem responder’s VFS in one of
two ways:
•
You can require remote FTAM initiators to provide an initiator identity and filestore
password in order to access any files in the VFS.
•
You can configure a default initiator identity and filestore password to be used for
any remote initiator that does not provide an initiator identity and filestore
password.
To require all remote initiators to provide an initiator identity and filestore password,
omit the DEFUSER attribute when you configure your VFS profiles, as in the following
command:
ADD PROFILE $AMGR.#VFS.VFS1, COMNAME "APPL1A"
To configure a default initiator identity and filestore password, specify the desired
defaults in the DEFUSER attribute, as in the following command:
ADD PROFILE $AMGR.#VFS.VFS1, COMNAME "APPL1A", &
DEFUSER "FNET.CNFG,FTMUSER"
Note that if a remote application specifies an initiator identity and filestore password,
the application-supplied values override the configured defaults.