Note on usage
Function: Modify attributes of remote directories
User group: FT user
Functional description
You can use ftmoddir to modify the following attributes of a directory in a remote system:
Directory name
Access rights (not if the partner system is a Windows system or the partner is an FTP partner)
Format
ftmoddir -h |
<partner 1..200>![<file name 1..512>]
[ <transfer admission 8..67> | @n | @d |
<user ID 1..67>[,[<account 1..64>][,[<password 1..64>]]] ]
[ -fnc=t | -fnc=c ]
[ -p=[<management password 1..64>] ]
-nf=<new file name 1..512> | -am=@rw | -am=@ro
Description
-h
Displays the command syntax on the screen. Entries after the -h are ignored.
partner![file name]
Specifies the directory and partner system for the attribute modification operation.
partner
partner is 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”.
file name
Name of the directory whose attributes are to be modified. The name can be either absolute or relative to the remote login authorization. If the file name in the remote system has been predefined in an admission profile, it must not be specified here.
If the partner system is running openFT (BS2000) then the name of a PLAM library can also be specified here.
transfer admission | @n | @d |
user ID[,[account][,[password]]]
Before you can modify the attributes of a file on a remote system, you must first identify yourself at the system. To do this, you need an authorization in the syntax used at the remote system. You can specify this transfer admission
as an FTAC transfer admission if FTAC is used in the remote system,
or as a login/LOGON authorization in the syntax used by the remote system (user ID, possibly together with account or password).
For details, see section “Entering the authorization data for the partner system” .
@n for transfer admission
By entering @n you specify that the remote system requires no login authorization.
@d for transfer admission
If you specify @d (blanked) then the transfer admission is queried on the screen after the command has been sent. Your input is invisible to prevent unauthorized persons from seeing the transfer admission.
A binary password or binary transfer admission must be specified in hexadecimal format, see section “Entering commands”.
password not specified
If you omit a password which is required for authorization then it is queried on the screen after the command has been sent. Your input is invisible to prevent unauthorized persons from seeing the password.
Please note that you still have to enter the commas, for example:
ftmoddir partner!file user-id,,
or
ftmoddir partner!file user-id,account,
neither transfer admission nor user ID specified
This has the same effect as @d, i.e. the transfer admission is queried on the screen after the command has been sent. openFT always interprets your (hidden) input as a transfer admission and not as a user ID.
-fnc=t | -fnc=c (file name coding)
specifies the encoding mode for the remote directory names (file name, new file name).
t (transparent, default value)
Specification of the remote directory names in transparent mode (compatible to the previous versions).
c (character)
Specification of the directory names in character mode. The names are interpreted according to the character code of the remote system, i.e. for Unix partners according to the openFT operating parameter option (ftmodo -fnccs) that has been set there.
-fnc=c is only permitted for partners as of openFT V12.1.
-p=[management password]
If the directory is protected by a password in the remote system then you must specify this here.
The password must be specified in hexadecimal format, see section “Entering commands”. This is of relevance in the case of a connection with openFT (BS2000) since it is possible to define hexadecimal passwords in BS2000.
management password not specified
If you specify -p= then the password is queried on screen after the command has been sent. Your input is invisible to prevent unauthorized persons from seeing the password.
-nf=new file name
Specifies the new name for the directory file name in the partner system. The name file name then loses its validity. New file name may be specified either absolutely or relative to the remote login authorization.
-nf not specified
The directory name is unchanged.
-am=@rw | -am=@ro
Modifies the access rights to the directory file name in the remote system.
If the partner system is a Windows system, you cannot change the access rights. For Unix or BS2000 systems you can specify either @rw or @ro:
@rw
means that the access right is read-write.
@ro
means that the access right is read-only.
-am not specified
No change is made to the access right definitions.
Examples
The directory d:\dir in the remote Windows system win1 is to be moved to d:\users\dir, the transfer admission is ChangeDirwin:
ftmoddir win1!d:\\dir ChangeDirwin -nf=d:\\users\\dirThe directory /home/user1/current in the remote Unix system ux1 is to be renamed to /home/user1/previous, the transfer admission is ChangeDirux:
ftmoddir ux1!/home/user1/current ChangeDirux --nf=/home/user1/previous