I. 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.
-
You can transmit a maximum of 64 files concurrently. However, you can use the ftsutil command to change the maximum number of concurrent transmissions. For details about the ftsutil command, see ftsutil - changes and displays environment information in 6. Commands. JP1/FTP rejects any transmission or connection attempt that would result in the maximum number of concurrent transmissions being exceeded. A connection request received at the server that would exceed the maximum number of concurrent transmissions is not output to the system log. For details about rejection of transmission, see G. Transmission Rejection Messages.
-
JP1/FTP does not recognize NFS files. It treats such a file 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.
Due to problems specific to NFS, its settings, and the environment configuration, the contents of a transmitted file might not be written correctly even if transmission is successful.
-
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.
-
In HP-UX, an API library that supports multiple threads supports kernel threads for HP-UX 11.0 or later. It does not support the preceding threads, such as DCE threads.
-
An API library that supports multiple threads supports only POSIX threads.
-
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 that the Operations-Manager Console functions cannot be used in an environment where IP addresses are translated.
-
The Operations-Manager function cannot be used in an environment in which IP addresses are converted between Operations-Manager Console and Operations-Manager Agent. Furthermore, the IP address used by Operations-Manager Console to connect to Operations-Manager Agent must be the same as that of the physical host (the host returned by the hostname command) on the Operations-Manager Agent side.
-
The default fonts of the desktop environment in use (such as CDE) are used for the characters in JP1/FTP's GUI windows (excluding the Operations-Manager Console). Consequently, the characters in the GUI windows might become garbled in some desktop environments. In this case, specify a font capable of displaying Japanese as the default font. For details about the default font specification, check the desktop environment you are using.
-
/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 I‒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
-
In the event log, the timestamps might not be sorted in ascending order.
-
The Operations-Manager functions are supported even if the JP1/FTP versions for the Operations-Manager Console and the Operations-Manager Agent are different.
-
When definitions for a multiple IP address environment are not used, JP1/FTP uses the IP addresses shown in the table below.
Table I‒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.
-
A process that is started as an auto-start program after the end of a transmission inherits the JP1/FTP daemon environment. The environment defined for the transmitting user (environment defined for each user by a method such as a profile) is not inherited. This applies at both the server and the client.
-
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).
-
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.
-
In AIX, if an old version of HACMP (4.4 or earlier) is used, the IP address of the service adapter is changed from the boot IP address to the service IP address during HACMP startup. This disables the physical host, thereby disabling JP1/FTP. In such a case, add an adapter to each node and set the physical host for the added adapter to enable the physical host.
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.
-
-
In Solaris, the installation directory has changed in version 09-00 and later. The following notes apply to upgrading:
-
During upgrade installation from a version earlier than 09-00, the definition files are migrated automatically to the new directory. Note that user-created files in a directory other than /usr/lib/jp1_fts/sys, /usr/lib/jp1_fts/trace, or /usr/lib/jp1_fts/work are not migrated. If necessary, move those files to new directories after you have finished the installation. Delete any unneeded files after the installation.
-
Before starting the installation, we recommend that you back up data such as definition files.
-
During upgrade installation from a version earlier than 09-00, symbolic links are created under /usr/bin/jp1_fts and /usr/lib/jp1_fts for the previous version of commands and shared libraries to achieve compatibility with the previous environment. These symbolic links are not created during a new installation.
-
If you are using user-created tools to manipulate and reference definition files, update the paths of those tools to the new paths.
-
If you have specified the path for the event log file in the ftslog.conf definition file, update it to the new path.
-
startup is updated. The previous /usr/lib/jp1_fts/scripts/startup is moved automatically to /etc/opt/jp1_fts/startup during the installation. Update /etc/opt/jp1_fts/startup to the new path by referencing /etc/opt/jp1_fts/startup.model. Also update /etc/opt/jp1_fts/stop in the same manner.
-
If you have been using the API library, update the old library path to the new path in user programs that have been compiled by a version earlier than 09-00, and then recompile the user programs.
-
-
Changing the system time during operation does not cause a problem. However, if the new date and time are later than the actual date and time, the most recent transmission log will remain displayed at the top until the new time is reached, because the log information is always displayed in reverse chronological order.