As noted throughout this guide, action/concurrency strings
are used as arguments to options for two commands within ftam, and
as arguments to options for several command-line FTAM commands.
The exact usage of an action/concurrency string in each of these
commands is covered in the section “Using FTAM File Protection” later is this chapter. However, the syntax
of the action/concurrency string is the same regardless of where
it appears.
As an example, the following fmv command uses the -z
option to satisfy access control and concurrency control on the
source and target files. Each use of the -z option is followed
by an action/concurrency string, which conveys the necessary information
to FTAM.
$ fmv myplan -z D=X.PassMeBy denver:FY91plan -z P=X.SupercedeMe |
The meaning of the action/concurrency strings in this example
will become clear as you progress through this section.
The general syntax for an action/concurrency string is as
follows:
action(s) [=conc_access|=.password|=conc_access.password]
[,action(s) [=conc_access|=.password|=conc_access.password]] ... |
The periods, commas, and equal-signs in the above
syntax are mandatory delimiters. As usual, the brackets ( "["
and "]" ) indicate information that may
be optional, depending on the situation. The vertical bar ( "|" )
separates valid choices within an optional argument.
Table 5-3 “Elements of an Action/Concurrency
String” describes the elements
of the action/concurrency string .
Table 5-3 Elements of an Action/Concurrency
String
Element | Description |
|---|
action(s) | A
valid file action code (or codes) from Table 5-1 “Possible File Actions”. |
conc_access | A
valid concurrency control lock code from Table 5-2 “Concurrency Control Locks”. You can specify more than one lock code
when inserting an access control element; however, you can only
specify one lock code in an action/concurrency string used to satisfy
access control. |
password | A password
associated with the file action; there may be no password. HP-UX
FTAM does not store passwords for file actions; this field is only
provided for users whose remote responders do support action passwords. |
The previous example is reproduced
below. Each element is labelled to indicate its function in the
command.
In this example, both the source and target files require
the application of the -z option to satisfy access control.
The source file (which is to be deleted during the move operation)
is protected against accidental deletion by having the
password (PassMeBy)
required on a delete action.
The target file (which is to be replaced during the move operation)
is protected against unauthorized replacement by having the password
(SupercedeMe)
required for a replace action
Printable version
