Entering the authorization data for the partner system

The authorization data can be specified via login/LOGON authorization or via FTAC transfer admission, see the following table:

System	FTAC transfer admission	Login name	Account number	Password
BS2000	8 - 32 character long C string or 15 - 64 character long X string	1 - 8 alphanumeric characters	1 - 8 alphanumeric characters	1 - 32 character long C string or 1 - 16 character long X string
Unix based	8 - 32 characters long C string (Unicode characters are also permitted) or 15 - 64 characters long X string	1 - 32 characters	Unix systems do not recognize any account numbers locally	Alphanumeric characters (the length is system dependent), a distinction is made between uppercase and lowercase
Windows	8 - 36 characters (Unicode characters are also permitted)	1 - 36 characters, possibly with leading domain name (DOM\)	Windows does not recognize any account numbers locally	8 - 32 character long C string or 15 - 64 character long X string
z/OS	8 - 32 character long C string or 15 - 64 character long X string	1 - 8 alphanumeric characters	max. 40 characters, uppercase, digits and special characters $, @, #	1 - 8 alphanumeric characters

Examples

If you do not possess FTAC transfer admission then you can specify the LOGON/login authorization for the individual platforms using the following syntax:

• BS2000 systems:

  userid,[account-number][,'password']

  You can omit the account number if the user has a default account number for the BS2000 timesharing mode and you want to use this default account number.

• Unix systems

  userid[,,password]

• Windows systems:

  userid[,,password]

  The user ID consists of a user name (In the case of local IDs, the "hostname\" must not be entered in front of the user ID.) or, if a user ID in a LAN Manager or Windows domain is accessed, it consists of the domain name followed by a backslash (\) and the user name.

• OS/390 and z/OS:

  userid,account-number[,password]

  The accounting number is optional with more recent z/OS versions.

• FTAM partner systems on which no file transfer product of the openFT product family is used:

  user-identity,[storage account],filestore-password

• In the case of other partner systems, your specifications depend on the conventions used in the partner system.

Inbound access using the default FTP client

If you wish to access an openFT server from a standard FTP client, you should note the following:

• Establishing a connection
  If the default listener port 21 is set on the openFT FTP server, enter the following from the shell (Unix systems), from the command prompt (Windows) or on command level (BS2000 and z/OS):

  ftp hostname

  hostname is the host name of the openFT FTP server.

  If a listener port other than 21 is set on the openFT FTP server, you need two commands to establish a connection:

  ftp

  ftp> open hostname port-number

• Login
  If you log in without an FTAC transfer admission, enter the login data interactively as usual (user ID and any password that is required and/or account number). If you log in using an FTAC transfer admission, enter the FTAC transfer admission under User and leave the Password empty.

  Example

  User: ftpuser1

  Password: (empty)

  With openFT FTP servers as of V11, you can enter the value $ftac under User and the FTAC transfer admission under Password.

  Example

  User: $ftac

  Password: ftpuser1