H. Notes about Operation

By default, while transmitting a file, JP1/FTP does not perform processing on the file being transmitted exclusively. Therefore if you edit or delete a file during transmission, the results of the transmission will be incorrect. The results of the transmission will also be incorrect if the same file is sent and received at the same time. You can use the environment variable JP1FTS_FILE_EXCLUSION to perform processing on the file exclusively.
The default is that files of 2 gigabytes or more cannot be transmitted. If you use the JP1FTS_LARGEFILE2 environment variable, you can eliminate the limitations on file size altogether. However, the actual possible size of transmitted files depends on the system. For details about the environment variables, see 3.1.3 Using environment variables to define a JP1/FTP environment.
If file transmission is interrupted, such as by forced termination of file receive processing or by a transmission error, an incomplete file might be created. If overwrite receive processing is interrupted, the original file cannot be restored.
JP1/FTP handles NFS files as a single UNIX file. Therefore, you can use NFS files only in an environment that supports them as UNIX files and within the supported operation range.

Even if transmission processing is successful, the contents of a transmitted file might not be written correctly due to problems specific to NFS, their settings, and the environment configuration.
If you use secondary groups at the client (ON is set in the JP1FTS_CSUPPLEGROUP environment variable), the maximum number of secondary groups is 63 (this is a system limitation). If you exceed this value, an error occurs during transmission.

The permitted maximum number of secondary groups at the server depends on the system.
If you use a network relay device (such as a router or a firewall) that performs IP address translation (such as Network Address Translation (NAT) or IP masquerading), file transmission via the device might fail due to use of the FTP protocol. Make sure that the device in use supports the FTP protocol.

Note

The specifications of checking for the PORT command in 09-00 and the PASV command in 10-00 have been improved. These improvements can sometimes cause a problem to occur when an IP address is not properly translated. If this happens, revise the IP address translation settings so that it is properly translated, or change the specifications of checking for the PORT and PASV commands by referring to Table 3-2.
/etc/hosts, /etc/services, and /etc/passwd require ordinary user's read permissions.

In the case of a transmission that uses a wildcard file name, there is no limit to the total number of files that can be expanded or the sum of the total lengths of the expanded path names at the client, but there are such limitations at the server. The length of the path name of each expanded file includes the termination characters (NULL characters).

Table H‒1: Maximum number of files that can be expanded and maximum value for the sum of the lengths of the path names (server)
Platform	JP1/FTP version	Maximum number of files	Maximum value for the sum of the lengths of the path names
HP-UX	07-00 or earlier	3,412	20,475
HP-UX	07-10 or later	341,332	2,047,995
Solaris	--	174,761	1,048,571
AIX	--	4,095	24,571
Linux	--	21,844	131,067

Legend:: --: No limitations based on version

In the event log, the timestamps might not be sorted in ascending order.

When definitions for a multiple IP address environment are not used, JP1/FTP uses the IP addresses shown in the table below.

Table H‒2: IP addresses used by JP1/FTP
No.	Usage		IP address to be used
1	Client	IP address for control connection	IP address that is assigned automatically by the OS
2	Client	IP address for data connection	IP address for control connection
3	Server	IP address for control connection	IP address that accepted the connection
4	Server	IP address for data connection	IP address for control connection
5	IP address of the Operations-Manager Agent		Physical IP address (IP address corresponding to the host name that is returned by an OS command (such as `hostname`)
6	IP address of the Operations-Manager Console		IP address that is assigned automatically by the OS

When an auto-start program starts after the end of a transmission, the standard input/output and error output are closed. This applies at both the server and the client. If you want to open them, you must specify settings in such a manner that files are allocated to the standard input/output and error output. For details about how to specify the settings, see 3.1.3 Using environment variables to define a JP1/FTP environment.
To register an auto-start program, the user must have read permissions as well as execution (search) permissions for all the directories that constitute the real path of the file or directory that is to be registered.
Provided below are notes about using JP1/FTP in a cluster system configuration (in an HA configuration that supports node switching). For details about the definition of JP1/FTP in an environment where logical addresses are used, see 3.15 Using JP1/FTP in a multiple IP address environment. A cluster system is the same as what is referred to as a node switching system in the JP1 manuals.
- Failover is not supported.
- Physical IP addresses must be enabled (IP addresses corresponding to the host names that are returned by an OS command, such as hostname).
- JP1/FTP services can be started and stopped by using cluster software.
- When JP1/FTP is run as the FTP server, file transmission is supported whether the FTP client specifies a local IP address or a physical IP address as the connection target.
- When JP1/FTP is run as the FTP client, re-transmission initiated by a method such as automatic retries of file transmission is not performed in the event of a failure.
- FTP custom jobs can be used to perform file transmission.
The following notes apply when the environment definition for a multiple IP address environment is not used:
- When JP1/FTP is run as the FTP client, the IP address for connection is usually a physical IP address because it is assigned automatically by the OS.
- JP1 events are sent to the physical IP address (IP address corresponding to the host name that is returned by an OS command, such as hostname).
- When JP1/FTP is run as the FTP server, the physical host name (host name returned by an OS command, such as hostname) is set in message 220, which is returned when control connection is established.
Before changing the system time, stop all JP1/FTP daemons and commands. To reset the system time, you must initialize the transmission logs.

The procedure for resetting the system time is as follows:

1. Stop all JP1/FTP daemons and commands.

2. Back up the log information file and event log files to a directory of your choice.

3. Change the system time.

4. Initialize the log information. For details on how to initialize the log information, see G. Log Information Deletion Tool.

5. Delete the event log files.

6. Start the JP1/FTP daemons and commands.
When the FTP client receives (get) a file from the FTP server and an error occurs in the FTP client after the FTP server sends the file normally, differences between the files in the FTP server and in the FTP client occur. Similar differences will occur during execution of operations with the size check option.
On the JP1/FTP client, if you want to receive files by specifying wildcard characters, a local file name is generated from the list of file path names received in response to the NLST command. As a result, depending on the format of the list of file path names received from the destination FTP server, the file might not be able to be transmitted normally. The list of file path names supported by JP1/FTP is based on the RFC 959 (FILE TRANSFER PROTOCOL). In addition, of the file path names in the list, those that are supported by JP1/FTP must meet all of the following conditions:
- The format of the first part of the file path name must be the same as the format of the file path name specified for the remote file name. Alternatively, if the file path name specified for the remote file name is a relative path and begins with "./", the format of the first part of the file path name must be the same as the format of the file path name (excluding "./" or ".\") specified for the remote file name.
- If the list of file path names includes blank lines, all file path names must be listed before the first blank line.
Examples are shown below.

In these examples, the configuration of directories on an FTP server is as shown below.

Example 1

On the JP1/FTP client, the file path name specified for the remote file name is "/dir1/*" and the list of file path names is as follows:
```
/dir1/file11
file12
/dir1/dir11/file111
 
/dir1/dir12:
file121
 
/dir1/dir13:
file131
```
In this case, the supported file path names are "/dir1/file11" and "/dir1/dir11/file111" only.

Example 2

On the JP1/FTP client, if the file path name specified for the remote file name is "./dir1/*" or ".\dir1\*", the following file path names in the list of file path names are supported:
```
./dir1/file11
.\dir1\file11
dir1/file11
dir1\file11
./dir1/dir11/file111
.\dir1\dir11\file111
```
Note

Depending on the FTP server, a list of file path names might include directory path names. In such cases, if the above conditions are met, the JP1/FTP client sends the RETR command with the path name as the parameter. As a result, the FTP server usually returns an error response, and file transmission terminates abnormally.
Files transmitted via an IPv6 address are not compatible with IPv4-mapped addresses.
The typical implementation of JP1/FTP is to create transmission information when setting up the environment, and then actually transmit files after operation is started. As a result, the ftsregc command is typically only used when setting up the environment, and not during normal operation.

Note the following:
- Do not transmit files and delete transmission information at the same time. (This also applies to Operations-Manager Console operations.) If you transmit files and delete transmission information at the same time, the transmission might fail even if the deleted transmission card is different from the transmission card used for the files you are transmitting.
- The ftsregc command is resource-intensive.
- If transmission information is fixed during operation, instead of executing the ftsregc command, we recommend using ftstran command arguments to specify the fixed transmission information.
If a character defined in the definition file for prohibited characters (/var/opt/jp1_fts/sys/ftsmetachars) is specified in an argument for the LIST, NLST, or STAT command, execution of the command fails. Likewise, if a file name specified as an argument for the LIST, NLST, or STAT command contains a character defined in the definition file for prohibited characters, execution of the command fails. Also, in the cases below, a file cannot be transmitted.

Examples of when a file cannot be transmitted:
- The LIST, NLST, or STAT command is executed as an extension of an FTP client file transmission command (get, put, etc.), and the specified file name contains a prohibited character.
- From a JP1/FTP client, the STAT command is specified in an FTP command, which is within transmission information, and a prohibited character is contained in the argument (the file name).
- From a JP1/FTP client, the following is specified for transmission information, and a remote file name is specified that contains a prohibited character:
  
  - "Receive" is specified for "Send/receive type".
  
  - "Multiple-file" is specified for "Single/multiple-file transmission".
Characters can be removed from the definition file, but since the characters are special metacharacters of the shell, they are all prohibited characters. Characters can also be added. One line of up to 255 1-byte characters can be defined. The file can also be blank.
- The contents of the definition file for prohibited characters (/var/opt/jp1_fts/sys/ftsmetachars):
  
  &();`|
If disk space becomes insufficient during file reception, a timeout might occur on the sending side.

To Page Top