Translation table created by user
The location of the translation table created by the user is specified differently for FTP clients than for
FTP servers.
If you are configuring an FTP server you will enter
the fully qualified MVS data set or zFS file name.
If you are configuring an FTP client, you specify only a low level qualifier (LLQ) of the data set.
The client will look for your translation table in data set 'user_id.your_llq.TCPXLBIN'. If not found it
will look for 'hlq.your_llq.TCPXLBIN'.
Example
If you specify a value of 'MYTRANS', FTP will look for data set 'user_id.MYTRANS.TCPXLBIN'.
The client design allows for different login user IDs to use different translation tables.
When configuring an FTP server
Input can be either a fully-qualified MVS data set or an zFS file name.
Syntax rules
If input is Fully qualified MVS data set
- Qualified name can contain up to 44 characters, including periods.
- Qualified name consists of one or more indexes separated by a period.
- Each index can contain up to 8 characters. The first character of an index
must be alphabetic or national. Each subsequent character must be alphanumeric,
national, - or {.
- Optional member name can be 1-8 characters. The first character of a member
name must be alphabetic or national. Each subsequent character must be
alphanumeric, national, or {.
- Total length of name cannot exceed 50 characters.
If input is zFS file name
- Must start with a forward slash
- 1-50 case-sensitive characters
- Each directory or file must begin with one or more adjacent forward slashes
- Every character after the last forward slash must be alphanumeric or > + & ! $ - / | _ < ? ` : # @ % ' " ~ { } [ ] \ * ( ) , . =
When configuring an FTP client
Syntax rules
- Must be 1 - 8 characters
- The first character must be alphabetic or national ($, #, @).
- Subsequent characters must be alphanumeric, national or -.