Hitachi

JP1 Version 12 for Windows Systems JP1/File Transmission Server/FTP Description, Reference and Operator's Guide


3.1.1 Defining an environment for JP1/FTP

The default values are set during installation. We recommend that you change these values only if necessary.

To use the Environment Definition dialog box to define an environment for JP1/FTP:

  1. Change settings as desired in the Environment Definition dialog box, and then click OK.

    After you have changed the settings, restart all services.

    The following table lists and describes each item in the Environment Definition dialog box.

    Table 3‒1: Items in the Environment Definition dialog box

    Item

    Setting

    No. of file transmissions to log

    ((0 to 100,000))

    <<2,000>>

    Specifies the number of log entries to retain. One file transmission is counted as one entry. When the number of files transmitted exceeds the number of entries being retained, the oldest information is overwritten.

    Because the size of one entry is 1,500 bytes, the required file size equals number of retained entries x 1,500 bytes.

    Increasing the number of log entries to be retained:

    If you increase the number of log entries to be retained, it might take longer to display logs, depending on the CPU and hardware performance as well as on the amount of memory that is installed. If you want to retain log information over a long period of time, we recommend that you copy the log information file (JP1/FTP-installation-directory\history) and then store the copy.

    Default

    Clicking this button resets all environment definition settings to their default values.

    Size of protocol trace file

    ((4 to 3,000 KB))

    <<50 KB>>

    Specifies the size of a file to be used to collect FTP protocol trace information. The protocol trace files enable you to check the operation of commands at the FTP level. When the amount of trace information for a file exceeds the specified file size, the oldest information is overwritten.

    You need 120 files, each of the specified size.

    You can use a text editor such as Notepad to view the trace files.

    Size of module trace file

    ((4 to 3,000 KB))

    <<50 KB>>

    Specifies the size of a file to be used to collect module trace information. Module traces are collected as maintenance information. When the amount of trace information for a module trace file exceeds the specified file size, the oldest information is overwritten.

    You need 132 files, each of the specified size.

    The module trace files cannot be viewed.

    Size of Access log file

    ((0 to 100 MB))

    <<0 MB>>

    Specifies the size of the file to be used to store access logs. When the amount of access log information exceeds the specified size, the old information is backed up and a new file is created. If there already is a backup file, that file is overwritten.

    You can use a text editor such as Notepad to view the access log file.

    No. of retries (When connecting to a host)

    Retry interval (When connecting to a host)

    Specifies the number of and interval for retries in the event connection for file transmission cannot be established (for a reason such as busy status). Retries are attempted whenever a connect system call results in one of the following error codes:

    When attempting to establish control connection:

    WSAECONNREFUSED (10061)

    When attempting to establish data connection:

    WSAEADDRINUSE (10048)

    • No. of retries (When connecting to a host) ((0 to 100,000)) <<5>>

      If you specify 0, no retries will be attempted.

    • Retry interval (When connecting to a host) ((0 to 86,400 seconds)) <<2 seconds>>

      If you specify 0, retries are attempted immediately (without any interval between retry attempts).

    Size of TCP/IP window

    ((0 to 65,535 bytes))

    <<32,768 bytes>>

    Specifies the size of the socket buffer for sending and receiving (SO_SNDBUF and SO_RCVBUF). If the specified value is 0, the system's default value is used.

    This size is not the window size when transmissions are actually performed.

    Note that various factors affect transmission efficiency, such as the line speed, usage status, and CPU performance. Specify a value that is appropriate for the system being used.

    Time-limit waiting to send data

    ((1 to 3,600 seconds))

    <<60 seconds>>

    Specifies the amount of time to wait for the sending buffer to become available after a package has been sent during data transmission. If the buffer is still not available when the specified amount of time elapses, the transmission terminates abnormally.

    Time-limit waiting to receive data

    ((1 to 3,600 seconds))

    <<60 seconds>>

    Specifies the amount of time to wait for a packet to be received during data reception (a packet is transmitted by a remote target). If no data is received after the specified amount of time has elapsed, the transmission terminates abnormally.

    Server/Client

    • Size of sending buffer/Size of receiving buffer ((512 to 65,535 bytes)) <<4,096 bytes>>

      Specifies the size of the buffer (memory) for file transmission (sending) at both the server and the client.

      You might want to change this value if the amount of memory is limited or when you want to improve transmission efficiency. Note that various factors affect transmission efficiency, such as the line speed, usage status, and CPU performance. Specify a value that is appropriate for the system being used.

      The memory size that should be allocated for the transmission buffer equals maximum number of concurrent transmissions x specified buffer size. Buffers for sending and receiving are not allocated at the same time. Allocation occurs only during transmission.

    • Time-limit for idle connection ((30 to 7,200 seconds)) <<900 seconds>>

      If there is no request from the client for a specific period of time, the server releases the connection with the client. This item specifies the amount of time before the connection is to be released.

    Directory for log

    ((2 to 230-byte character string))

    <<JP1/FTP installation directory>>

    Specifies the directory in which to create the log information files (history) and the trace information output directory (trace). The specified directory must be on the local drive.

    If you change this setting, the previous files and directory are retained. If you no longer need those files and directory, delete them.

    Link with JP1/IM

    Specifies that JP1 events are to be issued. If you select this item, JP1 events will be issued when the service status changes and when transmission ends. If you link to JP1/IM, you can monitor the status on JP1/IM. For details about linkage with JP1/IM, see 5.2 Linking to JP1/IM.

    The default is that this item is not selected.

    Output transmission result to NT event log

    Specifies whether to output file transmission results (normal or abnormal termination) and the start of file transmission to the event log.

    If you select this item, event IDs 33, 34, and from 24 to 27 are output. All other event IDs are always output to the event log, regardless of this setting.

    The default is that this item is not selected.

    Restrict access

    Specifies whether a user who logs in to the server is allowed to access only the home directory specified during user registration and the files under that home directory. Because the highest directory becomes the root directory of each drive, no access between drives is permitted. This setting applies to all users.

    When Restrict access is selected, the system's root directory becomes the root directory for the absolute path names of files and directories that are displayed and set. However, if you register the absolute path name format beforehand, you can change the root directory for absolute path names to the home directory. For details about how to change the root directory for absolute path names to the home directory, see 3.13 Function for using the access control function to change the root directory for absolute path names.

    The default is that this item is not selected.

Note

If the value set in the Environment Definition dialog box in No. of file transmissions to log, Size of protocol trace file, and Size of module trace file is smaller than the current value for that item, the corresponding information files are deleted when the service is restarted. This means that the information existing before the restart will be deleted. The log information is backed up to the file log-information-directory\FTSLOGSAVE.