ftcredir

Note on usage

Function: Create remote directories

User group: FT user

Functional description

You use ftcredir to create a new directory on a remote system. This is only possible if the remote system supports this function.

Format

ftcredir -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>] ]

Description

-h

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

partner![file name]

Specifies what directory is to be created on what computer.

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 that is to be created. You can specify the name absolutely or relative to the remote login authorization. If the name in the remote system is predefined by an admission profile then it may not be specified here.

If openFT (BS2000) is running on a partner system then an empty PLAM library is created.

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 and/or password).

For details, see section “Entering the authorization data for the partner system” .

@n for transfer admission

With @n you specify that the remote system does not demand a 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, e.g.:

ftcredir partner!file identification,,

or

ftcredir partner!file identification,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 name (file name).

t (transparent, default value)

Specification of the directory name for the remote system in transparent mode (compatible to the previous versions).

c (character)

Specification of the directory name for the remote system in character mode. The name is 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 you want to create a new directory in a password-protected PLAM library then you must specify the password here.

The password can also 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.

Examples

1. In the remote Unix system ux1, you want to create the directory dir1. The identification in ux1 is protected via the transfer admission userremote.

   ftcredir ux1!dir1 userremote

2. In the remote Windows system win1, you want to create the directories dir1\dir2 and dir2 is to be a subdirectory of dir1. Neither of these directories exists yet. The directories are to be created in the existing directory exdir under the ID jerry with the password secret.

   To do this, you enter the following commands:

   ftcredir win1!exdir/dir1 jerry,,secret

   ftcredir win1!exdir/dir1/dir2 jerry,,secret

   The first command is necessary because if you only entered the second command (ftcredir win1!exdir/dir1/dir2 jerry,,secret) then the directory dir1 will not yet exist in the remote system and you will see the error message:

   Remote system: Higher-level directory not found

3. In the remote BS2000 system bs2, you want to create the PLAM library user.lib, the ID is jimbs2 with the account j123456 and the password jimpass.

   ftcredir bs2!user.lib jimbs2,j123456,jimpass