H. Notes about Operation
-
During file transmission, lock processing is not performed on the corresponding files.
-
The default is that files of 2 gigabytes or more cannot be transmitted. If you use the JP1FTS_LARGEFILE environment variable, you can transmit a file of up to a maximum size of 4 gigabytes minus 1 byte. If you use the JP1FTS_LARGEFILE2 environment variable, you can eliminate the limitations on file size altogether. 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.
-
/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
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
IP address for data connection
IP address for control connection
3
Server
IP address for control connection
IP address that accepted the connection
4
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.