G. Notes about Operation

You must start JP1/FTP commands, GUIs, and tools as administrator.

An administrator is a user who satisfies the following conditions:
- If User Account Control (UAC) is enabled:
  
  Administrator or a user who has been elevated to an administrator account
- If User Account Control (UAC) is disabled:
  
  User who has Administrators permissions
To start JP1/FTP from another linked product, the administrator must be executing that linked product. Otherwise, startup of JP1/FTP might fail.
Files are locked while they are engaged in file transmission (lock processing is performed). During send processing, such files can be read, but they are write-protected. During receive processing, the files are protected from both read and write operations.
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 files on network drives as a single Windows file. Therefore, you can use files on a network drive only in an environment that supports them as Windows 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 network drives, their settings, and the environment configuration.
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 in the manual.

JP1/FTP uses the IP addresses shown in the table below.

Table G‒1: 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

Provided below are notes about using JP1/FTP in a cluster system configuration (in an HA configuration that supports system switching). For details about the definition of JP1/FTP in an environment where logical addresses are used, see 3.11 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.
Class-3 and class-4 characters are not supported.
Before you change the system time, stop all JP1/FTP services and GUIs. 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 services and GUIs.

2. Back up the log information file to a desired directory.

3. Change the system time.

4. Initialize the transmission results. For details about the initialization method, see F.1 FTSTRANINIT.BAT and FTSMGRINIT.BAT - initialize results.

5. Start the JP1/FTP services and GUIs.
If only the drive name is specified in the specification of a root directory, operations might not execute correctly.

Example

(Incorrect) C:

(Correct) C:\
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.
The maximum number of concurrent transmissions is 60. A connection request that causes the number of transmissions to exceed 64 is rejected.
There is no limit on the size of transmission files. The size of files that can be transmitted is dependent on the system limits.
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 either "./" or ".\", 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.
If you stop the JP1/FTP Server or Client service during a file transmission or right after a file transmission, be sure to stop the JP1/FTP Log service as well. Not doing so might make it so that log information cannot be collected for subsequent file transmissions.
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 edit or delete transmission information at the same time. (This applies to GUI operations as well.)
- 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.
Only one session is required to use Remote Desktop to remotely perform operations. (This is the same as when the console is used to perform operations.)
The beginning of messages such as "System call error occurred." output to the Event log are displayed in Japanese when the OS language is Japanese, and in English for all other OS language settings. Note that the JP1/FTP language setting is not taken into account.
The maximum path name size JP1/FTP can handle is 259 bytes.

To Page Top