ftmodp

Note on usage

Function: Modify FT profiles

User group: FTAC user and FTAC administrator

Functional description

ftmodp stands for "modify profile".

The FTAC administrator can use this command to change or to privilege FT profiles of other users.

The ADM administrator can use this command to change ADM profiles (i.e. FT profiles which have the property "access to remote administration server", corresponding to -ff=c ).

You can use this command to modify your FT profiles. If an FT profile has been privileged, you can use ftmodp to remove its privileged status or change the transfer admission.

The timestamp is updated when a profile is modified.

Note for the FTAC administrator

• In the event that the FTAC administrator does not have FT administrator privileges the same time, then admission profiles of other users are blocked after a modification (except after -priv=y). This can be by-passed by entering -ua=user ID,password. If the user later changes his/her password, the profile will no longer be usable without further modification.

• The FTAC administrator can modify multiple profiles simultaneously specifying @a for the profile name and @a for the transfer admission in the -s option (and @a for the user ID if desired).

  Exception: user ID, profile name and transfer admission can be modified only for one profile at a time.

Format

ftmodp -h |

<profile name 1..8> | @s | @a
[ -s=[<transfer admission> | @a | @n ]

[,<user ID> | @a | @adm] ]

[ -ua=[ <user ID> ],[<password> | @n ] ]
[ -nn=<profile name 1..8> ]
[ -tad= | -tad=<transfer admission> | -tad=@n ]
[ -v=y | -v=n ][ -d=yyyymmdd | -d= ]
[ -u=pr | -u=pu ][ -priv=y | -priv=n ]
[ -iml=y | -iml=n ]
[ -iis=y | -iis=n ][ -iir=y | -iir=n ]
[ -iip=y | -iip=n ][ -iif=y | -iif=n ]
[ -ff= | -ff=[t][m][p][r][a][l] | -ff=c ]
[ -dir=f | -dir=t | -dir=ft ]
[ -pn=<partner 1..200>,...,<partner(50) 1..200> | -pn= ]
[ -pna=<partner 1..200>,...,<partner(50) 1..200> ]
[ -pnr=<partner 1..200>,...,<partner(50) 1..200> ]
[ -fn=<file name 1..512> | -fn=] [ -fnp=<file name prefix 1..511> ]
[ -ls= | -ls=@n | -ls=<command1 1..1000> ]
[ -lsp= | -lsp=<command2 1..999> ][ -lss= | -lss=command3 1..999> ]
[ -lf= | -lf=@n | -lf=<command4 1..1000> ]
[ -lfp= | -lfp=<command5 1..999>][-lfs= | -lfs=<command6 1..999> ]
[ -wm=o | -wm=n | -wm=e | -wm=one ]
[ -c= | -c=y | -c=n ]
[ -cm= | -cm=y | -cm=n ]
[ -txt=<text 1..100> | -txt= ]

Description

-h

Displays the command syntax on the screen. Entries after the -h are ignored.

profile name

specifies the name of the FT profile you wish to modify. To see the profile names you have already assigned, you can issue the ftshwp command (without options).

@s for profile name

@s allows you to change the properties of the standard admission profile of the user ID.

The options -v, -d and -u are ignored with a standard admission profile.

@a for profile name

modifies all FT profiles that come into question at once, unless you select a specific profile with the option -s.

If you specify ftmodp profile name without any other parameters, you force the timestamp of the profile to be updated.

-s=[transfer admission | @n | @a][,user ID | @a | @adm]

is used to specify selection criteria for the FT profile to be modified.

transfer admission

specifies the transfer admission of the FT profile to be modified. You must specify a binary transfer admission in hexadecimal format, see section “Entering commands”.

@a for transfer admission

modifies either the FT profile specified with profile name (see above) or (if no profile name was specified) all the profiles that come into question.

If you specify @a as a user, you must specify a login name for user ID (not @a). Otherwise, an error message is received.

@n for transfer admission

selects all FT profiles without transfer admission.

transfer admission not specified

causes to query the transfer admission on the screen after the command is entered. Your entry is not displayed to prevent unauthorized persons from seeing the transfer admission. To exclude the possibility of typing errors, the program prompts you to enter the transfer admission a second time. If you just press <ENTER>, this has the same effect as specifying @a.

,user ID

As user, you can only enter your own login name here.

As the FTAC administrator, you can specify any login name here.

@a for user ID

allows each user to modify only profiles belonging to his or her own login name. If @a is specified here, a transfer admission must be specified for transfer admission (not @a). Otherwise, an error message is received.

If you specify @a as the FTAC administrator, you can modify the FT profiles for any login names.

@adm for user ID

For the FTAC and ADM administrator only.

If you specify @adm as the FTAC or ADM administrator, you can modify ADM profiles (corresponding to -ff=c).
However, you can neither change this property (-ff=c) nor the user ID (-ua option).

user ID not specified

modifies only profiles belonging to the user's own login name, regardless of who issues the command.

-s not specified

if @a is specified for profile name, all the FT profiles belonging to the login name under which the ftmodp command is entered are modified. Otherwise, the FT profile with the specified name is modified.

-ua=[user ID],[password | @n]

-ua is only meaningful for the FTAC administrator. With -ua, the FTAC administrator can assign one FT profile of any login name to another login name, see example 2.

user ID

As user, you can only specify your own login name here.

As the FTAC administrator, you can specify any login name here.

user ID not specified

The user ID is taken from the login authorization under which ftmodp is entered.

,password

specifies the password for a login name. A binary password must be specified in hexadecimal format, see section “Entering commands”. The FT profile for the login name is valid only so long as the password password is valid for the login name. When the password is changed, the profile can no longer be used (not locked!).

@n for password

Can only be specified by the FTAC administrator! In this case, the FTAC administrator cannot specify any transfer admission for the FT profile if he/she does not have FT administrator privileges. An existing transfer admission will be automatically deleted in this case.

The password is specified by the owner of the admission profile.

comma only (,) no password specified

causes FTAC to query the password on the screen after the command is entered. Your entry is not displayed to prevent unauthorized persons from seeing the transfer admission.

user ID only (without comma and password) specified

means that the profile is valid for all passwords of the specified login name user ID. When an FT request refers to this admission profile, FTAC uses the password valid at that moment. This prevents you from having to modify the admission profile if the password is changed.

-ua not specified

the login name of this FT profile remains unchanged.

-nn=profile name | @s

-nn can be used to assigns a new name to one of your FT profiles.

@s for profile name

Makes the admission profile the standard admission profile for the user ID. If the admission profile previously had a transfer admission, you must also specify -tad=@n.

-nn not specified

leaves the profile name unchanged.

-tad=[transfer admission | @n]

allows you as FTAC user to modify the transfer admission of one of your own FT profiles. As the FTAC administrator, you can also modify the transfer admissions for other login names if you have FT administrator privileges.

If the modified admission profile is a standard admission profile (ftmodp @s or -nn=@s), only -tad=@n is permitted.

transfer admission

The transfer admission must be unique within your system so that there are no conflicts with transfer admissions defined by other FTAC users for other access permissions. A binary transfer admission must be specified in hexadecimal format, see section “Entering commands”. If the transfer admission you select has already been assigned, FTAC rejects the ftmodp command and issues the message

Transfer admission already exists.

@n for transfer admission

disables the old transfer admission.

@n must be specified if you convert an admission profile that has a transfer admission to a standard admission profile using -nn=@s.

transfer admission not specified

-tad= causes FTAC to prompt you to enter the transfer admission after the command has been entered. Your entry is not displayed to prevent unauthorized persons from seeing the transfer admission. To exclude the possibility of typing errors, the program expects you to enter the transfer admission a second time as an entry check.

The transfer admission is not queried when a standard admission profile is changed. The following message is issued: Transfer admission of standard

profile must be @n.

-tad not specified

does not modify the transfer admission of the FT profile.

-v=y | -v=n

-v defines the status of the transfer admission.

y

the transfer admission is not disabled (it is valid).

n

transfer admission is disabled (it is not valid).

-v is ignored if the modified profile is a standard admission profile.

-v not specified

the transfer admission status remains unchanged.

-d=[yyyymmdd]

-d specifies the period during which the transfer admission can be used. The FT profile is disabled when this period has expired.

You can specify an eight-digit date (e.g. 20170602 for June 2, 2017). The transfer admission can no longer be used after 00:00 hours on the specified day. The largest possible value that can be specified for the date is 20380119 (January 19, 2038).

yyyymmdd not specified

when -d= is specified, the previous setting is cancelled, i.e. the time restriction is removed from the transfer admission.

-d is ignored if the modified profile is a standard admission profile.

-d not specified

the previous time restriction defined for the transfer admission remains unchanged.

-u=pr | -u=pu

using -u, you can control how FTAC reacts when someone attempts to assign an existing transfer admission to an FT profile. Normally, the transfer admission must be disabled immediately, by designating it as private.

Transfer admissions that do not require as much protection, can be designated as public. This means that they are not disabled even when a user attempts to assign another transfer admission of the same name.

Possible values:

pr (default value)

the transfer admission is disabled as soon as someone with another login name attempts to specify a transfer admission of the same name (private).

In this case, the -u parameter is set to no time restriction at the same time.

pu

the transfer admission is not disabled, even if someone attempts to specify a transfer admission of the same name (public).

-u is ignored if the modified profile is a standard admission profile.

-u not specified

the previous setting remains unchanged.

-priv=y | -priv=n

This option is used by the FTAC administrator to grant privileged status to an FT profile.

As a normal FTAC user, you can only withdraw an existing privilege. y is not permitted.

y

grants privileged status to the FT profile. The FT administrator's entries in the admission set are ignored for requests executed with a privileged FT profile, i.e., if the user uses the -iml, -iis, -iir, -iip or -iif options in the FT profile, both the user' s entries (MAX. USER LEVELS) and the administrator' s entries (MAX. ADM LEVELS) are ignored.

n

withdraws the privileged status, if it had been granted, from the FT profile.

-priv not specified

does not modify the privileged status of the FT profile.

-iml=y | -iml=n

-iml (ignore max. level) is used to specify whether the FT profile is to be restricted by the values in the admission set. The user can override the entries he/she made himself or herself (the MAX. USER LEVELS) for requests using this FT profile. If the FT profile is also privileged by the FTAC administrator, the entries made by the FTAC administrator (the MAX. ADM LEVELS) can also be ignored. This FT profile would then allow inbound basic functions to be used which are disabled in the admission set.

y

allows the values in the admission set to be ignored.

n

restricts the functionality of the profile to the values in the admission set.

-iml not specified

causes the values specified in the profile for the basic functions to apply unchanged.

-iis=y | -iis=n

-iis (ignore inbound send) allows the value for the basic function inbound send in the admission set to be ignored (see -iml for details).

y

allows the basic function inbound send to be used even if it is disabled in the admission set. At the same time, component "display file attributes" of the basic function inbound file management can be used (see table at -iif).

Specifying this option is enough as long as the basic function inbound send was disabled by the user, but if it was disabled by the FTAC administrator, it is also necessary that he/she grant privileged status to the FT profile.

n

restricts the profile to the value in the admission set for the basic function inbound send.

-iis not specified

causes the values specified in the profile for the basic function inbound send to apply unchanged.

-iir=y | -iir=n

-iir (ignore inbound receive) allows the value for the basic function inbound receive in the admission set to be ignored see -iml for details).

y

allows the basic function inbound receive to be used even if it is disabled in the admission set. At the same time, subcomponents of the basic function inbound file management can also be used (see table at -iif).

Specifying this option is enough as long as the basic function inbound receive was disabled by the user, but if it was disabled by the FTAC administrator, it is also necessary that he/she grant privileged status to the FT profile.

n

restricts the profile to the value in the admission set for the basic function inbound receive.

-iir not specified

causes the values specified in the profile for the basic function inbound receive to apply unchanged.

-iip=y | -iip=n

-iip (ignore inbound processing) allows the value for the basic function inbound followup processing + preprocessing + postprocessing in the admission set to be ignored
(see -iml for details).

y

allows the basic function inbound follow-up processing + preprocessing + postprocessing to be used even if it is disabled in the admission set. Specifying this option is enough as long as the function was disabled by the user, but if it was disabled by the FTAC administrator, it is also necessary that he/she grant privileged status to the FT profile.

n

restricts the profile to the value in the admission set for the basic function inbound follow-up processing + preprocessing + postprocessing.

-iip not specified

causes the values specified in the profile for the basic function inbound follow-up processing + preprocessing + postprocessing to apply unchanged.

-iif=y | -iif=n

-iif (ignore inbound file management) allows the values for the basic function inbound file management in the admission set to be ignored (see -iml for details).

y

allows the basic function inbound file management to be used even if it is disabled in the admission set.

Specifying this option is enough as long as the basic function inbound file management was disabled by the user, but if it was disabled by the FTAC administrator, it is also necessary that he/she grant privileged status to the FT profile.

n

restricts the profile to the value in the admission set for the basic function inbound file management.

The following table shows which subcomponents of the file management can be used under which conditions.

Inbound file management function	Values of the admission set or extension in profile
Display file attributes	Inbound Send (IBS) enabled
Modify file attributes	Inbound Receive (IBR) and Inbound File Management (IBF) enabled
Rename files	Inbound Receive (IBR) and Inbound File Management (IBF) enabled
Delete files	Inbound Receive (IBR) enabled and Write mode = overwrite in profile
Display directories	Inbound File Management (IBF) enabled
Create, rename and delete directories	Inbound File Management (IBF) enabled and direction = from partner in profile

-iif not specified

causes the values specified in the profile for the basic function inbound file management to apply unchanged.

-ff=[t][m][p][r][a][l] | -ff=c

-ff defines the FT function for which the FT profile can be used. With the exception of c, these letters can be combined in any way (tm, mt, mr, ...). c must not be combined with other values. Please observe the note concerning the description of -ff=c.

t (transfer)

The FT profile can be used for the file transfer functions "Transfer files", "Display file attributes", and "Delete files".

m (modify file attributes)

The FT profile can be used for the file transfer functions "Display file attributes" and "Modify file attributes".

p (processing)

The FT profile can be used for the file transfer functions "File Preprocessing" or "File Postprocessing". The FT function "Transfer files" must also be permitted.

Specification of p has no significance for profiles with a file name prefix (-fnp=) or a file name (-fn=) since, in this case, the first character of the file name or file name prefix decides whether the profile can only be used for preprocessing and postprocessing ("|") or only for file transfer/file management (no "|").

The use of follow-up processing is not controlled by -ff=, but by -lf= and -ls=.

r (read directory)

The FT profile can be used for the file transfer functions "Display directories" and "Display file attributes".

a (administration)

The admission profile is allowed to be used for the "remote administration" function. This means that it authorizes a remote administration server to access the local openFT instance. To do this, the associated transfer admission must be configured in the remote administration server.

-ff=a may only be specified by the FT administrator or FTAC administrator.

l (logging)

The admission profile is allowed to be used for the "Receive ADM traps" function. This allows another openFT instance to send its ADM traps to the remote administration server via this profile. This specification only makes sense if the local openFT instance is flagged as a remote administration server (ftmodo -admcs=y command).

-ff=l may only be specified by the FT administrator.

c (client access)

The admission profile is allowed to be used for the "access to remote administration server" function (ADM profile). This allows a remote administrator on a remote computer to use this profile to access the local remote administration server and issue remote administration requests. The local openFT instance must be flagged as a remote administration server (ftmodo -admcs=y command).

-ff=c may only be specified by the ADM administrator.

The value c must not be combined with any other value. In addition, an FT profile created with -ff=c cannot be changed into a FT profile using the other FT functions (t, m, p, r, a or l) and vice versa.

No function specified

Specifying -ff= allows you to undo any specification with regard to the functions. All file transfer functions are then permitted (corresponds to tmpr), but not the remote administration functions (a, c) and ADM trap functions (l).

-ff not specified

The previous specification with respect to the functions remains unchanged.

-dir=f | -dir=t | -dir=ft

specifies for which transfer direction(s) the FT profile may be used. Possible values for the direction: f, t, ft, tf.

f

allows data transfer only from a partner system to the local system.

t

allows data transfer only from the local system to the remote system. It is thus not possible to create, rename or delete directories.

ft, tf

transfer direction is not restricted in the profile.

-dir not specified

leaves the transfer direction entries in the FT profile unchanged.

-pn=[partner1[,partner2, ...] ]

You use -pn to specify that this admission profile is to be used only for FT requests which are processed by a certain partner system. You can specify the name of the partner system in the partner list or the address of the partner system. For details on address specifications, see section “Specifying partner addresses”.

You can specify more than one partner system (maximum 50) with a maximum total of 1000 characters.

partner1[,partner2, ...] not specified

-pn= cancels a previous restriction defined for partner systems so that the FT profile can be used by every partner system.

-pna=partner1[,partner2, ...]

-pna adds one or more partner system(s) to the list of permitted partner systems. Up to 50 partner systems can be entered in the list (max. 1000 characters).

If the list has been empty up to now, then the profile is limited to the specified partner system(s).

-pnr=partner1[,partner2, ...]

-pnr deletes one or more partner system(s) from the list of permitted partner systems.

Please note: As soon as you delete the last partner remaining in the list, the profile can be used by every partner system.

-pn, -pna and -pnr not specified

causes the entries for permitted partner systems to apply unchanged.

-fn=[file name]

-fn specifies which file(s) under your login name may be accessed using this FT profile. If you specify a fully qualified file name, only the file with this name can be transferred.

If the file name ends with %unique or %UNIQUE, this string is replaced by a string which changes for each new call on file transfer or file management requests, see section “Entering commands”.

If file name starts with a "|" (pipe character) then it is interpreted as a preprocessing or postprocessing command, see also section “Preprocessing and postprocessing”.

file name not specified

-fn= allows you to cancel a file name entry. This also applies to a prefix assigned with -fnp. The FT profile then permits unrestricted access to all files.

-fn not specified

leaves the file name entries in the FT profile unchanged.

-fnp=file name prefix

restricts access to a set of files whose names begin with the same prefix. FTAC adds the character string specified as file name prefix to the file name in the request and attempts to transfer the file with the expanded name.

Example:

• Unix systems: If this option is specified as -fnp=scrooge/ and the request contains the file name stock, the file is transferred as scrooge/stock.

• Windows systems: If this option is specified as -fnp=scrooge\ and the request contains the file name stock, the file is transferred as scrooge\stock.

In this way, you can designate the files you have released for openFT. If the -fnp option was used to specify a prefix, the file name specified in the request must not contain a directory separator (Unix systems: "/", Windows systems: "\").This disables (unintentionally) changing directories specifying ../ or ..\. You should also ensure that there is no chance for a symbolic link to cause a jump to another place in the file tree. 

%unique or %UNIQUE cannot be used for a file name prefix. In the case of a file transfer or file management request, the user can use a file name ending with %UNIQUE (or %UNIQUE.suffix or %unique or %unique.suffix) to generate a unique file name with the prefix specified here. 

A file name prefix which starts with the | character indicates that the admission profile can only be used for file transfer with preprocessing and postprocessing, since the file name created using the prefix and the name specified for the ncopy or ft command also starts with the | character. In this case, no follow-up commands may be specified. 

Exception on Windows systems:The filename prefix under Windows starts with |cmd /c or |&cmd /c. 

file name prefix can be up to 511 bytes in length. 

-fn= allows you to cancel a file name prefix entry, see above. 

Notes on profiles with preprocessing or postprocessing

• On Unix systems, the shell metacharacters | ; & < > and "newline" may only be specified if they are enclosed in '...' (single quotes) or "..." (double quotes) or if each of them is escaped with "\" (backslash). The character ` (accent grave) and the string $( (dollar+open bracket) may only be specified if they are enclosed in '...' (single quotes) or if they are specified directly after a backslash ("\").

• The following strings may not be specified for the name entered in the ncopy or ft command:

  • .. (two dots)

  • .\ (dot + backslash)

  • .' (dot + single quote, only for Unix systems)

  This makes it impossible to navigate to higher-level directories.

• Special cases

  • You must specify a file name or file name prefix which starts with the string "|ftexecsv " for admission profiles which are to be used exclusively for the ftexec command.

  If a command prefix is also to be defined, you must specify it as follows:

  -fnp="|ftexecsv -p= command prefix "

  (e.g.: -fnp="|ftexecsv -p=\"ftshwr \"")

  The same restrictions apply to the command string of the ftexec call as to the filename prefix during preprocessing and postprocessing.

  • For admission profiles that are only to be used for getting monitoring data, specify the filename prefix "|*FTMONITOR ". The functions of the profile must permit File Preprocessing (-ff=tp). For details, see the ftcrep command, Examples.

-fnp not specified

leaves the file name prefix entries in the FT profile unchanged.

-ls= | -ls=@n | -ls=command1

specifies follow-up processing which is to be performed under your login name in the event that file transfer is successful. If -ls is specified, no success follow-up processing may be requested in the file transfer request. Specifying -ls only makes sense if you also make an entry for -lf (see below) to preclude the possibility that an intentionally unsuccessful request can circumvent the -ls entry. If you have defined a prefix for the file name with -fnp and plan follow-up processing for this file, you must specify the complete file name here.

@n for command1

If you enter -ls=@n, no follow-up processing is then permitted in the FT profile in the event that file transfer is successful.

command1 not specified

-ls= allows you to cancel a follow-up-processing entry. The FT profile then no longer restricts success follow-up processing in the local system. This is also a way to cancel a prefix for the follow-up processing defined with -lsp.

For details on follow-up processing, please refer to section “Commands for follow-up processing”.

-ls not specified

leaves the entries in the FT profile for follow-up processing in the event that file transfer is successful unchanged.

-lsp=[command2]

-lsp defines a prefix for follow-up processing in the local system in the event that file transfer is successful. FTAC then adds the character string command2 to the follow-up processing specified in the FT request and attempts to execute the resulting command.

Example:

• Unix systems: If this option is specified as -lsp='lpr ' and the request specifies file1.txt as follow-up processing, FTAC executes lpr file1.txt as follow-up processing.

• Windows systems: If this option is specified as -lsp="print " and the request specifies file1.txt as follow-up processing, FTAC executes print file1.txt as follow-up processing.

Please also bear in mind the information provided on the -ls option!

You can cancel an existing prefix by specifying -ls=.

command2 not specified

-lsp= cancels the entry in the FT profile for a follow-up processing prefix after successful file transfer.

For details on follow-up processing, please refer to section “Commands for follow-up processing”.

-lsp not specified

leaves the prefix entries in the FT profiles for follow-up processing in the event that file transfer is successful unchanged.

-lss=[command3]

-lss defines a suffix for follow-up processing in the local system in the event that file transfer is successful. FTAC then appends the character string command3 to the followup processing specified in the FT request and attempts to execute the resulting command.

Example:

• Unix systems: If this option is specified as -lss= ' file2.txt ' and the request specifies lpr as follow-up processing, FTAC executes lpr file2.txt as follow-up processing.

• Windows systems: If this option is specified as -lss=" file2.txt" and the request specifies print as follow-up processing, FTAC executes print file2.txt as follow-up processing.

Please also bear in mind the information provided on the -ls option!

For details on follow-up processing, please refer to section “Commands for follow-up processing”.

command3 not specified

-lss= cancels the entry in the FT profile for a follow-up processing suffix after successful file transfer.

-lss not specified

leaves the suffix entries in the FT profiles for follow-up processing in the event that file transfer is successful unchanged.

-lf= | -lf=@n | -lf=command4

-lf specifies follow-up processing to be executed under your login name if the file transfer is aborted due to an error. If -lf is specified, no failure follow-up processing may be requested in the FT request. Making an -lf entry only makes sense if you also make an entry for -ls (see above) to preclude the possibility that a successful request can circumvent the -lf entry. If you have defined a prefix for the file name with -fnp and plan follow-up processing for this file, you must specify the complete file name here.

@n for command4

-lf=@n is specified, no follow-up processing is then permitted in the FT profile in the event of an unsuccessful file transfer.

command4 not specified (-lf= )

-lf= allows you to cancel an entry for follow-up-processing in the event that file transfer is unsuccessful. The FT profile then no longer restricts failure follow-up processing in the local system. This is also a way to cancel a prefix defined with -lfp.

For details on follow-up processing, please refer to section “Commands for follow-up processing”.

-lf not specified

leaves the entries in the FT profiles for failure follow-up processing after unsuccessful file transfer unchanged.

-lfp=[command5]

defines a prefix for follow-up processing in the local system in the event that file transfer is unsuccessful. FTAC then adds the character string command5 to the follow-up processing specified in the FT request and attempts to execute the resulting command.

Example:

• Unix systems: If this option is specified as -lfp='lpr ' and the request specifies error.txt as follow-up processing, FTAC executes lpr error.txt as follow-up processing.

• Windows systems: If this option is specified as -lfp="print " and the request specifies error.txt as follow-up processing, FTAC executes print error.txt as followup processing.

Please also bear in mind the information provided on the -lf option!

You can cancel an existing prefix by specifying -lf=.

For details on follow-up processing, please refer to section “Commands for follow-up processing”.

command5 not specified

-lfp= cancels the follow-up processing prefix in the FT profile in the event of unsuccessful file transfer.

-lfp not specified

leaves the prefix entries in the FT profiles for follow-up processing in the event of unsuccessful file transfer unchanged.

-lfs=[command6]

-lfs defines a suffix for follow-up processing in the local system in the event that file transfer is unsuccessful. FTAC then appends the character string command6 to the follow-up processing specified in the FT request and attempts to execute the resulting command.

Example:

• Unix systems: If this option is specified as -lfs= ' error.txt ' and the request specifies lpr as follow-up processing, FTAC executes lpr error.txt as follow-up processing.

• Windows systems: If this option is specified as -lfs=" error.txt" and the request specifies print as follow-up processing, FTAC executes print error.txt as follow-up processing.

Please also bear in mind the information provided on the -lf option!

command6 not specified

-lfs= cancels the follow-up processing suffix in the FT profile in the event of unsuccessful file transfer.

For details on follow-up processing, please refer to section “Commands for follow-up processing”.

-lfs not specified

leaves the suffix entries in the FT profile for a follow-up processing in the event of unsuccessful file transfer unchanged.

-wm=o | -wm=n | -wm=e | -wm=one

-wm specifies which write modes may be used in the file transfer request and what they effect.

o (overwrite)

In the FT request of openFT or FTAM partners, only -o or -e may be entered for write mode. The receive file is overwritten if it already exists, and is created if it does not yet exist.

With FTP partners, -n may also be entered if the file does not yet exist.

n (no overwrite)

In the FT request -o, -n or -e may be entered for write mode. The receive file is created if it does not yet exist. If the receive file already exists, the request is not executed.

e (extend)

In the FT request only -e may be entered for write mode, i.e. the receive file is extended by appending the transferred file to the end if the receive file already exists. The receive file is created if it does not yet exist.

one

means that the FT profile does not restrict the write mode.

-wm not specified

leaves the write-mode entries in the FT profile unchanged.

-c= | -c=y | -c=n

Using -c, you can determine whether data encryption is required or forbidden. If the setting in the profile does not correspond to the setting in the request, the request is denied. The setting is not valid for file management requests, since there is no data encryption for these requests.

y

Only requests with data encryption may be processed using this profile.

n

Only requests without data encryption may be processed using this profile.

neither y nor n specified

-c= resets the current setting. Requests with and without data encryption are both accepted.

-c not specified

The encryption option remains unchanged.

-cm= | -cm=y | -mc=n

Using -cm, you can determine whether file(s) and/or directory list attributes encryption is required or forbidden. If the setting in the profile does not correspond to the setting in the request, the request is denied.

y

Only requests with file(s) and/or directory list attributes encryption may be
processed using this profile.

n

Only requests without file(s) and/or directory list attributes encryption may be processed using this profile.

neither y nor n specified

-cm= resets the current setting. Requests with and without file(s) and/or directory list attributes encryption are both accepted.

-cm not specified

The encryption option remains unchanged.

-txt=text | -txt=

-txt allows you to enter a new comment in the FT profile (up to 100 characters).

text not specified

-txt= deletes an existing comment.

-txt not specified

an existing comment remains unchanged.

As soon as you modify an admission profile, the timestamp is also updated. The timestamp is output with ftshwp -l (LAST-MODIF). The timestamp is also updated if you do not change the properties of the profile, i.e. if you enter ftmodp without any parameters.

CAUTION!If you use the -ff=p, -fn, -fnp, -ls, -lsp, -lss, -lf, -lfp or -lfs options, you must remember

• that a file name restriction can be bypassed by renaming the file unless followup processing is also restricted;

• that follow-up processing must always be restricted for both successful and unsuccessful file transfer and, if necessary, equivalent restrictions must exist for any permitted preprocessing;

• that prefixes for the file names and follow-up processing must be matched to one another;

• that no symbolic links should occur in the part of your file tree that is referenced by the file name prefix;

• that restrictions applied to preprocessing or follow-up processing can be circumvented if it is possible to replace this command with, for example, a "Trojan horse".

Examples

1. The transfer admission in the goldmrep FT profile created in the Examples of the ftcrep command, is to be changed to forScrooge. The transfer direction is no longer to be restricted. The profile is to be used to transfer any files with the prefix mine/ (Unix systems) or mine\ (Windows systems). Follow-up processing is to be prohibited entirely.

   The following command has to be entered:

   Unix systems:

   ftmodp goldmrep -tad=forScrooge -dir=tf\

    -fnp=mine/ -ls=@n -lf=@n

   Windows systems:

   ftmodp goldmrep -tad=forScrooge -dir=tf

     -fnp=mine\ -ls=@n -lf=@n

2. The FTAC administrator has FT administrator privilege and wants to assign the profile test01 with owner user1 to the login name user2. To do this, there are the following possibilities:

• ftmodp test01 -s=@a,user1 -ua=user2

The profile can be used immediately.

• ftmodp test01 -s=@a,user1 -ua=user2,@n

The profile can be used only after user2 has activated it via ftmodp test01 -ua=user2, for example. Since no password is specified in -ua the password currently valid is taken.