System Environment Settings
This topic explains how to register the environment settings for the client.
You can view and modify this information on HULFT-HUB Manager Management screen.
| [Note] | |
| • | The screen structures vary depending on the version and host type of the client. |
| • | For versions lower than HULFT-HUB Server Ver.3.9, if the client is HULFT Ver.8.4 or higher and the Forced Strong Key Mode is set to 'Enabled' in the System Environment Settings, connection with the client is not supported. Therefore, it is not possible to view or update the System Environment Settings for that client. |
List of Fields
1. Startup
<Table> System Environment Settings (Startup)
| No. | Field Name | Default Value | Setting Value | Specification | Remarks |
|---|---|---|---|---|---|
| A1 | Work File Generation Path | *1 | Alphanumeric characters | Mandatory | Within 200 bytes |
| A2 | FIFO Path | *1 | Alphanumeric characters | Mandatory | Within 200 bytes *2 |
| A3 | Send Daemon Communication Method | Socket | *3 | Mandatory | *4 |
| A4 | Command Acknowledge Port No. | 32000 | From 1 to 65535 | *5 | |
| A5 | Receive Port No. | 30000 | From 1 to 65535 | Mandatory | *6 |
| A6 | Request Acknowledge Port No. | 31000 | From 1 to 65535 | Mandatory | *6 |
| A7 | Send Process Multiplex Level | 10 | From 1 to 9999 | Mandatory | |
| A8 | Receive Process Multiplex Level | 0 | From 0 to 9999 | Mandatory | 0: No Limit |
| A9 | Pid File Generation Path | *1 | Alphanumeric characters | Mandatory | Within 200 bytes |
| *1: | This is the path that you specified when you installed HULFT8 for UNIX/Linux. |
| *2: | This can be specified when the client is less than Ver.8.4. |
| *3: | Select an option from the list that is shown on the screen. |
| *4: | This can be specified when the client is Ver.8.4 or higher. |
| *5: | If the client is Ver.8.4 or higher and "Socket" is specified in Send Daemon Communication Method, this is mandatory; if "UNIX Domain Socket Path" is specified, you cannot specify a value for this field. |
| *6: | This is located in the Basic Settings of the Registered Client settings on the Management screen. |
2. Code Conversion
<Table> System Environment Settings (Code Conversion)
| No. | Field Name | Default Value | Setting Value | Specification | Remarks |
|---|---|---|---|---|---|
| B1 | Code Set for Transfer (cs4trnsfr) | *1 | *2 | Mandatory | *3 *4 |
| B2 | Standard for Japanese | 83JIS | *2 | Mandatory | *3 *5 |
| B3 | Tab Code Mode | Space | *2 | Mandatory | |
| B4 | KEIS Em-size Space Mode | Mode 0 | *2 | Optional | |
| B5 | External Character Table Mode | No | *2 | Mandatory | |
| B6 | Process when External character has not been Registered | Default Value | *2 | Mandatory | |
| B7 | Code Conversion Mode | Mode 0 | *2 | Mandatory | |
| B8 | Instant Transfer Code Conversion | Receiving side | *2 | Mandatory | *6 |
| *1: | This is the language that you specified when you installed HULFT8 for UNIX/Linux. |
| *2: | Select an option from the list that is shown on the screen. |
| *3: | This is located in the Basic Settings of the Registered Client settings on the Management screen. |
| *4: | The field name is 'Kanji Code Type' when the client is lower than Ver.8.1. |
| This field is shown as 'Kanji Code Type' in the Registered Client settings on the Management screen, regardless of version. | |
| *5: | The field name is 'JIS Year' when the client is lower than Ver.8.1. |
| This field is shown as 'JIS Year' in the Registered Client settings on the Management screen, regardless of version. | |
| *6: | This can be specified when the client is Ver.8.4 or higher. |
3. Attribute Conversion
<Table> System Environment Settings (Attribute Conversion)
| No. | Field Name | Default Value | Setting Value | Specification | Remarks |
|---|---|---|---|---|---|
| C1 | Pack Zone Conversion | Mode 0 | *1 | Mandatory | |
| C2 | Sign for ASCII | Mode 1 | *1 | Mandatory | |
| C3 | Sign for EBCDIC | Mode 1 | *1 | Mandatory | |
| C4 | X Type Conversion | Mode 0 | *1 | Mandatory |
| *1: | Select an option from the list that is shown on the screen. |
4. Send and Receive
<Table> System Environment Settings (Send and Receive)
| No. | Field Name | Default Value | Setting Value | Specification | Remarks |
|---|---|---|---|---|---|
| D1 | Encryption Scheme | HULFT Encryption Scheme | *1 | Mandatory | |
| D2 | Receive Open Mode | Mode 1 | *1 | Mandatory | |
| D3 | Transfer Group Check | No | *1 | Mandatory | |
| D4 | Dynamic Parameter Specification | Enable Dynamic Specification | *1 | Mandatory | |
| D5 | Message Dynamic Parameter Specification | Always Replace Messages and Variables | *1 | Mandatory | |
| D6 | Send Transfer Error Recovery | Unsuccessful Mode | *1 | Mandatory | |
| D7 | Criteria to Delete Resend Queue | Mode 1 | *1 | Mandatory | |
| D8 | Receive File Max. Size | 0 |
From 0 to (*3) |
Mandatory | |
| D9 | Local Host Name | *2 |
Alphanumeric characters and specific symbols (*4) |
Mandatory | |
| D10 | Receive Multiplex Level Over Retry | Do Not Retry | *1 | Mandatory |
| *1: | Select an option from the list that is shown on the screen. |
| *2: | This is the host name that you specified when you installed HULFT8 for UNIX/Linux. |
| *3: | 9,223,372,036,854,769,999 |
| *4: | The only symbols allowed are '-' (hyphen) and '.' (period). |
5. Communication
<Table> System Environment Settings (Communication)
| No. | Field Name | Default Value | Setting Value | Specification | Remarks |
|---|---|---|---|---|---|
| E1 | Connect Retry Count | 5 | From 0 to 9999 | Mandatory | |
| E2 | Connect Retry Interval | 20 | From 0 to 9999 | Mandatory | Unit: second |
| E3 | Auto Resend Retry Count | 0 | From 0 to 9 | Mandatory | |
| E4 | Socket Timeout | 3600 | From 10 to 259200 | Mandatory | Unit: second |
| E5 | Socket Buffer Size for Data Sending | 0 |
0, from 4096 to 2147483647 |
Mandatory | Unit: byte |
| E6 | Socket Buffer Size for Data Receiving | 0 |
0, from 4096 to 2147483647 |
Mandatory | Unit: byte |
| E7 | Request Acknowledge Timeout | 86400 | From 10 to 259200 | Mandatory | Unit: second |
| E8 | IP Version | 4 | *1 | Mandatory | |
| E9 | Framed Message Transfer Type | Send and Receive Speed Priority Mode | *1 | Mandatory |
| *1: | Select an option from the list that is shown on the screen. |
6. Security
<Table> System Environment Settings (Security)
| No. | Field Name | Default Value | Setting Value | Specification | Remarks |
|---|---|---|---|---|---|
| F1 | Management Screen Security | Disabled | *1 | Mandatory | |
| F2 | Request Acknowledge Host Check | No | *1 | Mandatory | *2 |
| F3 | Operation Log Output Option | Do Not Output | *1 | Mandatory | |
| F4 | Operation Log Auto Switch Size | 0 | From 0 to 9999 | Optional | Unit: MB (0: No Limit) |
| F5 | Operation Log Switch Generation Count | 9999 | From 2 to 9999 | Mandatory | |
| F6 | HULFT Manager Password Check | No | *1 | Mandatory | |
| F7 | Allow Send Request/Resend Request from Unregistered Host | Yes | *1 | Mandatory | *3 |
| F8 | Allow Post-receive Job Result Inquiry from Unregistered Host | Yes | *1 | Mandatory | *3 |
| F9 | Allow Job Result Notification Request from Unregistered Host | Yes | *1 | Mandatory | *3 |
| F10 | Allow Remote Job Execution Request from Unregistered Host | Yes | *1 | Mandatory | *3 |
| F11 | Allow Instant Transfer from Unregistered Host | Yes | *1 | Mandatory | *3 |
| F12 | Allow Instant Transfer Receiving Root Directory | "itr" directory sibling of HULPATH (*4) | Optional | Within 256 bytes *3 | |
| F13 | Forced Strong Key Mode | Disabled | *5 | *6 |
| *1: | Select an option from the list that is shown on the screen. |
| *2: | This can be specified when the client is less than Ver.8.4. |
| *3: | This can be specified when the client is Ver.8.4 or higher. |
| *4: | HULPATH is the directory where the Environment Settings file used by HULFT is stored. |
| *5: | Allows browsing only |
| *6: | Displayed if the client is Ver.8.4 or higher |
7. Global
<Table> System Environment Settings (Global)
| No. | Field Name | Default Value | Setting Value | Specification | Remarks |
|---|---|---|---|---|---|
| G1 | Date Format | *1 | *2 | Mandatory | |
| G2 | HULFT Operation Language | *1 | *2 | Mandatory |
| *1: | This is the value that you specified when you installed HULFT8 for UNIX/Linux. |
| *2: | Select an option from the list that is shown on the screen. |
8. Transfer Test
<Table> System Environment Settings (Transfer Test)
| No. | Field Name | Default Value | Setting Value | Specification | Remarks |
|---|---|---|---|---|---|
| H1 | Transfer Preference | Test-priority Mode | *1 | Mandatory | |
| H2 | Result Handing of Receiving | Always Terminate Transfer with Error | *1 | Mandatory | |
| H3 | Output Receive File | No | *1 | Mandatory | |
| H4 | Execute Pre-send Job | No | *1 | Mandatory | |
| H5 | Execute Post-send Job | No | *1 | Mandatory | |
| H6 | Execute Post-receive Job | No | *1 | Mandatory | |
| H7 | Output Results to Transfer Logs | Yes | *1 | Mandatory |
| *1: | Select an option from the list that is shown on the screen. |
9. Others
<Table> System Environment Settings (Others)
| No. | Field Name | Default Value | Setting Value | Specification | Remarks |
|---|---|---|---|---|---|
| I1 | Utility Timeout | 60 | From 10 to 259200 | Mandatory | Unit: second |
| I2 | Job Timeout | 999999 | From 10 to 259200 | Mandatory | Unit: second |
| I3 | Log Switch Count | 0 | From 0 to 999999 | Mandatory | Unit: record |
| I4 | Status Display Selection | Display All | *1 | Mandatory | |
|
I5 |
HULFT Identifier | Alphanumeric characters | Optional | Within 8 bytes | |
| I6 | Trace Output Version | *2 | *1 | Mandatory | |
| I7 | Trace Output Mode | Output Only Unsuccessful Log Records | *1 | Mandatory | *3 |
| I8 | Log Size Reduction Mode | Output full log | *1 | Mandatory | *4 |
| I9 | Trace Output File Name |
HULPATH/trace (*5) |
Alphanumeric characters | Mandatory | Within 256 bytes |
| I10 | Trace Output File Size | 10 | From 1 to 1024 | Mandatory | Unit: MB |
| I11 | HULFT Script Port No. | *6 | From 1 to 65535 | Optional | *7 |
| I12 | Output to Trace Logs | *1 | Mandatory | *4 | |
| I13 | Output to System Logs | *1 | Mandatory | *4 |
| *1: | Select an option from the list that is shown on the screen. |
| *2: | The trace log (V8 header) is output when the client is less than Ver.8.4. |
| The trace log (V8.4 header) is output when the client is Ver.8.4 or higher. | |
| *3: | This can be specified when the client is less than Ver.8.4. |
| *4: | This can be specified when the client is Ver.8.4 or higher. |
| *5: | HULPATH is the directory where the Environment Settings file used by HULFT is stored. |
| *6: | When the client is less than Ver.8.4, if the HULFT Script Option is included in the HULFT product configuration, this value is "7700"; if the HULFT Script Option is not included in the HULFT product configuration, a default value will not be set. |
| When the client is Ver.8.4 or higher, you cannot set a default value, regardless of the HULFT product configuration. | |
| *7: | Can be specified when the client is Ver.8.1 or higher. |
10. Inter-HULFT Settings
<Table> System Environment Settings (Inter-HULFT Settings)
| No. | Field Name | Default Value | Setting Value | Specification | Remarks |
|---|---|---|---|---|---|
| J1 | Path to Inter-HULFT Common Environment | Optional | Within 200 bytes | ||
| J2 | Local File Lock Mode | Mode 0 | *1 | Mandatory |
| *1: | Select an option from the list that is shown on the screen. |
| [Legend] | |
| Default Value | Default value that is set when you install HULFT |
| Specification | Whether the specification is mandatory or optional when you update the management information record on a screen |
Explanation of Each Field
The following describes each field in the Startup settings.
(A1) Work File Generation Path
This field specifies the directory for the work file that HULFT creates temporarily.
HULFT processes data to be sent or received and creates a work file temporarily to contain the data, when necessary. Therefore, confirm that there is sufficient unused area in the partition when configuring this setting.
This field specifies the directory for the fifo file that is used when a request is issued to the Send system.
| [Note] | This field can be specified when the client is less than Ver.8.4. |
(A3) Send Daemon Communication Method
This field specifies whether to use a normal socket or a UNIX domain socket when starting the Send Daemon.
<Table> Setting Values for Send Daemon Communication Method
| On-screen Options |
Description |
|---|---|
| Socket | Use a normal socket |
| UNIX Domain Socket Path | Use a UNIX domain socket |
| [Note] | This field can be specified when the client is Ver.8.4 or higher. |
(A4) Command Acknowledge Port No.
This field specifies the port number that the Send daemon uses to acknowledge requests.
Ensure that this port number is not the same as a port number that is reserved by the operating system, or a port number that is used by another HULFT daemon.
| [Remarks] | If the client is Ver.8.4 or higher and "UNIX Domain Socket" is specified in the Send Daemon Communication Method, this field is not used and you cannot change the setting values. |
This field specifies the port number at which the Receive daemon waits and accepts data sent from another host.
Ensure that this port number is not the same as a port number that is reserved by the operating system, or a port number that is used by another HULFT daemon.
| [Remarks] | If you want to view and modify this field on the Management screen, you can find it in the Registered Client Information. |
(A6) Request Acknowledge Port No.
This field specifies the port number at which the Request Acknowledge daemon acknowledges requests from another host.
Ensure that this port number is not the same as a port number that is reserved by the operating system, or a port number that is used by another HULFT daemon.
| [Remarks] | If you want to view and modify this field on the Management screen, you can find it in the Registered Client Information. |
(A7) Send Process Multiplex Level
This field specifies the maximum number of Send processes that can be run simultaneously by the Send daemon.
The load on the system and lines grows heavier as the number of simultaneous Send processing increases. Set a value that is appropriate for the conditions of the system that you are currently using.
(A8) Receive Process Multiplex Level
This field specifies the maximum number of Receive processes that can be started simultaneously.
When the number of instances of the Receive processing exceeds the value that you set for this field, HULFT does not acknowledge instances of the Receive processing that exceed the value. Set a value that is appropriate for the conditions of the system that you are currently using.
This field specifies the directory for the Send daemon pid file that is generated when the Send daemon is started.
The following describes each field in the Code Conversion settings.
(B1) Code Set for Transfer (cs4trnsfr)
This field specifies the code set of the system on which HULFT is operating.
<Table> Setting Values for Code Set for Transfer (cs4trnsfr)
| On-screen Options |
Description |
|---|---|
| EUC-JP | EUC-JP |
| SHIFT-JIS | SHIFT-JIS |
| UTF-8 | UTF-8 |
| GB18030 | GB18030 |
For details on the Code Set for Transfer (cs4trnsfr), refer to Code Conversion Manual for the client.
| [Remarks] | To view and modify this field on the Management screen, use the JIS Year in the Basic Settings, which is in the Registered Client settings. |
This field specifies the JIS year of the Kanji code type of the system on which HULFT is operating.
<Table> Setting Values for Standard for Japanese
| On-screen Options |
Description |
|---|---|
| 78JIS | 78 JIS |
| 83JIS | 83 JIS |
| [Remarks] | To view and modify this field on the Management screen, use the JIS Year in the Basic Settings, which is in the Registered Client settings. |
This field specifies whether to handle a tab code (0x09) as a space code (0x20) or as a tab code (0x09) during text transfer to a EBCDIC-type host with sending side conversion.
<Table> Setting Values for Tab Code Mode
| On-screen Options |
Description |
|---|---|
| Space | Handle as a space code |
| Tab | Handle as a tab code |
This field specifies the conversion rules for KEIS em-size (double-byte) space codes.
<Table> Setting Values for KEIS Em-size Space Mode
| On-screen Options |
Description |
|---|---|
| Mode 0 | Convert em-size (double-byte) space codes to 0x4040 |
| Mode 1 | Convert em-size (double-byte) space codes to 0xA1A1 |
(B5) External Character Table Mode
This field specifies how to handle external character table conversion.
<Table> Setting Values for External Character Table Mode
| On-screen Options |
Description |
|---|---|
| No | Convert all external character codes to '□' without using the external character table. |
| Yes | Refer to the external character table, and convert external character codes as appropriate. |
| Priority | Give priority to the external character table, and convert codes as appropriate. |
For details about the external character table, refer to Administration Manual for the client.
(B6) Process when External Character has not been Registered
This field specifies the handling of codes which are not listed in JIS Level 1 and JIS Level 2, nor registered in the external character table.
<Table> Setting Values for Process when External character has not been Registered
| On-screen Options |
Description |
|---|---|
| Default Value | Convert to the default code |
| Error | Treat as an external character conversion error |
This field specifies how to handle conversion of external characters.
<Table> Setting Values for Code Conversion Mode
| On-screen Options |
Description |
|---|---|
| Mode 0 | Convert external characters with the destination code of conversion at a fixed length (other than UTF-8 code) |
| Mode 1 | Convert external characters with the destination code of conversion at a variable length |
(B8) Instant Transfer Code Conversion
This field specifies whether to perform the code conversion of the Send files on the sending side host or the receiving side host.
<Table> Setting Values for Instant Transfer Code Conversion
| On-screen Options |
Description |
|---|---|
| Sending side | Code conversion by the host on the sending side |
| Receiving side | Code conversion by the host on the receiving side |
| [Note] | This field can be specified when the client is Ver.8.4 or higher. |
The following describes each field in the Attribute Conversion settings.
This field specifies the conversion rules for Signed Internal Decimal (P) and Signed External Decimal (S) during format transfer or multi format transfer.
<Table> Setting Values for Pack Zone Conversion
| On-screen Options |
Description |
|---|---|
| Mode 0 | For details on pack zone conversion rules, refer to Code Conversion Manual for the client. |
| Mode 1 | |
| Mode B | |
| Mode F | |
| Mode 9 | |
| Mode S | |
| Mode N |
This field specifies the sign part when Signed Internal Decimal (P) and Signed External Decimal (S) are converted to ASCII data during format transfer or multi format transfer.
This setting becomes effective when you specify 'Mode S' for the Pack Zone Conversion.
<Table> Setting Values for Sign for ASCII
| On-screen Options |
Zone | Sign | |
|---|---|---|---|
| Positive | Negative | ||
| Mode 1 | 3 | 4 | 5 |
| Mode 2 | 3 | 3 | 7 |
This field specifies the sign part when Signed Internal Decimal (P) and Signed External Decimal (S) are converted to EBCDIC data during format transfer or multi format transfer.
This setting becomes effective when you specify 'Mode S' for the Pack Zone Conversion.
<Table> Setting Values for Sign for EBCDIC
| On-screen Options |
Zone | Sign | |
|---|---|---|---|
| Positive | Negative | ||
| Mode 1 | F | C | D |
| Mode 2 | F | F | D |
This field specifies the conversion rules for Character (X) during format transfer or multi format transfer.
<Table> Setting Values for X Type Conversion
| On-screen Options |
Description |
|---|---|
| Mode 0 | Carry out the same code conversion as Mixing of Kanji and Characters (M Type) |
| Mode 1 | Handle as a single byte code |
For details on Character (X), refer to Code Conversion Manual.
The following describes each field in the Send and Receive settings.
This field specifies the scheme that is used for encryption.
<Table> Setting Values for Encryption Scheme
| On-screen Options |
Description |
|---|---|
| HULFT Encryption Scheme | Use HULFT Encryption Scheme |
| Other Encryption Scheme | Incorporate an encryption exit routine, and use another encryption scheme |
For details about encryption exit routines, refer to Administration Manual for the client.
This field specifies how to handle exclusive control of the file to be received.
<Table> Setting Values for Receive Open Mode
| On-screen Options |
Description |
|---|---|
| Mode 0 | Treat as an error if the Receive file is locked |
| Mode 1 | Wait until the lock is released |
This field specifies how to handle the checking of the transfer group for receiving.
This processing checks the host name for the client on the sending side and the host name registered for the Transfer Group in the Receive Management Information, and can output an error if the host name is not registered.
<Table> Setting Values for Transfer Group Check
| On-screen Options | Description |
|---|---|
| No | Do not check |
| Check Only When Transfer Group is Registered | Check when the Transfer Group ID is set in the Receive Management Information, and do not check when the Transfer Group ID is not set |
| Always Check and Give Error When Transfer Group is Not Registered | Check when the Transfer Group ID is set in the Receive Management Information, and handle the host name as an error when the Transfer Group ID is not set |
(D4) Dynamic Parameter Specification
This field specifies whether to allow dynamic change of file names, transfer group IDs, and host names with the Send File command (utlsend).
<Table> Setting Values for Dynamic Parameter Specification
| On-screen Options |
Description |
|---|---|
| Disable Dynamic Specification | Do not allow dynamic specification in parameters of file name, transfer group ID, or host name |
| Enable Dynamic Specification | Allow dynamic specification in parameters of file name, transfer group ID, or host name |
(D5) Message Dynamic Parameter Specification
This field specifies how to handle messages that HULFT receives.
<Table> Setting Values for Message Dynamic Parameter Specification
| On-screen Options | Description |
|---|---|
| Never Replace Messages and Variables | Do not replace with messages for any of the management information |
| Replace Only in Send Management Information and Receive Management Information | Replace the content of the Send Management Information and in the Receive Management Information, but do not replace the Job Information |
| Replace Only in Job Information and Mail Interface Information | Do not replace the content of the Send Management Information and in the Receive Management Information, but replace the Job Information |
| Always Replace Messages and Variables | Replace with message for all the management information |
(D6) Send Transfer Error Recovery
This field specifies how to handle the situation when clearing or deleting the Send file ends unsuccessfully.
HULFT clears or deletes the Send file when the Send processing or the Receive processing has ended successfully.
<Table> Setting Values for Send Transfer Error Recovery
| On-screen Options |
Description |
|---|---|
| Unsuccessful Mode | Treat as unsuccessful end and execute the unsuccessful job |
| Successful Mode | Treat as successful end and execute the successful job |
(D7) Criteria to Delete Resend Queue
This field specifies the criteria for deleting records from the Resend Queue when the Send processing is requested for a file ID that already exists in the Resend Queue and when transfer ends unsuccessfully.
<Table> Setting Values for Criteria to Delete Resend Queue
| On-screen Options |
Description |
|---|---|
| Mode 1 | Delete the record with the same file ID and host name |
| Mode 2 | Delete the record with the same file ID, host name, and file name |
This field specifies the maximum size for a file that can be received by the Receive processing.
When your UNIX system does not support the file system of 2GB or more, specify '2147483647.'
| [Note] | The setting of this field is disabled in either of the following cases; where the product version of the client on the sending side is lower than HULFT5 or where direct transfer from Mainframe is carried out. |
This field specifies the host name when you intend to use a name that is different from the node name (host name) of UNIX/Linux system, which is usually used as the local host name, due to an administrative reason on the side of remote host and the like.
(D10) Receive Multiplex Level Over Retry
This field specifies whether to retry a connection if an error occurs due to exceeding of the Receive Multiplex Level during socket connection to the host on the receiving side.
<Table> Setting Values for Receive Multiplex Level Over Retry
| On-screen Options |
Description |
|---|---|
| Check box not selected | Treat as an error without retrying a connection |
| Check box selected | Retry a connection |
HULFT uses the Connect Retry Count and the Connect Retry Interval for the retry count and the wait time for reconnecting.
The following describes each field in the Communication settings.
This field specifies the number of times to try reconnecting if socket connection to the host on the receiving side fails.
When '0' is specified, reconnection is not carried out.
This field specifies the interval to wait to try reconnecting to the host on the receiving side if socket connection fails.
Specify the wait time before HULFT carries out auto resending, in seconds.
This field specifies the number of times to try auto resending when a communication error occurs during the Send processing and the Receive processing.
If you specify '0,' HULFT does not attempt auto resending.
This field specifies the time-out duration before communication is stopped due to no response from the remote host.
If you set '999999,' HULFT waits for a response without any time limit.
(E5) Socket Buffer Size for Data Sending
This field specifies the sending size that is applied in socket communication.
If you specify '0,' HULFT applies the value that is configured in the environment (operating system).
| [Note] | If the maximum socket buffer size for the operating system is changed to a value smaller than HULFT Socket Buffer Size for Data Sending after the Send daemon is started, the Send processing will end unsuccessfully. |
(E6) Socket Buffer Size for Data Receiving
This field specifies the receiving size that is applied in socket communication.
If you specify '0,' HULFT applies the value that is configured in the environment (operating system).
| [Note] | If the maximum socket buffer size for the operating system is changed to a value smaller than HULFT Socket Buffer Size for Data Receiving after the Send daemon is started, the Send processing will end unsuccessfully. |
(E7) Request Acknowledge Timeout
This field specifies the time-out duration when communication during the Request Acknowledge processing is interrupted due to no response from the remote host.
If you set '999999,' HULFT waits for a response without any time limit.
This field specifies the version of the IP protocol for socket communication.
<Table> Setting Values for IP Version
| On-screen Options |
Description |
|---|---|
| 4 | Use IPv4 when connecting to the remote host; use only IPv4 when being connected |
| 4/6 | Use IPv4 first when connecting to the remote host, try with IPv6 if connection fails; use both IPv4 and IPv6 when being connected |
| 6/4 | Use IPv6 first when connecting to the remote host, try with IPv4 if connection fails; use both IPv4 and IPv6 when being connected |
| 6 | Use IPv6 when connecting to the remote host; use both IPv4 and IPv6 when being connected |
(E9) Framed Message Transfer Type
This field specifies the data transfer method.
<Table> Setting Values for Framed Message Transfer Type
| On-screen Options |
Description |
|---|---|
| Error Detection Priority Mode | Always transfer data in the Error Detection Priority Mode |
| Send Speed Priority Mode | Transfer data in the Transfer Speed Priority Mode for sending, and transfer data in the Error Detection Priority Mode for receiving |
| Receive Speed Priority Mode | Transfer data in the Error Detection Priority Mode for sending, and transfer data in the Transfer Speed Priority Mode for receiving |
| Send and Receive Speed Priority Mode | Always transfer data in the Transfer Speed Priority Mode |
The following describes each field in the Security settings.
(F1) Management Screen Security
This field specifies whether to use the Management Screen Security function.
<Table> Setting Values for Management Screen Security
| On-screen Options |
Description |
|---|---|
| Disabled | Disable the Management Screen Security function |
| Enabled | Enable the Management Screen Security function |
(F2) Request Acknowledge Host Check
This field specifies how to handle requests from hosts that are not registered in the Host Information.
Specify how HULFT behaves if the host that is issuing a request is not registered in the Host Information when a service request is acknowledged. This applies to the following services: the Send Request (SEND), the Resend Request (RESEND), the Post-receive Job Result Inquiry Request (HULJOB), the Job Execution Result Notification (HULSNDRC), and the Remote Job Execution (HULRJOB).
<Table> Setting Values for Request Acknowledge Host Check
| On-screen Options |
Description |
|---|---|
| No |
Do not perform the Request Acknowledge Host Check (Acknowledge requests from hosts that are not registered in the Host Information) |
| Yes |
Perform the Request Acknowledge Host Check (Reject requests from hosts that are not registered in the Host Information) |
| [Note] | This field can be specified when the client is less than Ver.8.4. |
| For Ver.8.4 or later, specify the following fields for each service. | |
| • Allow Send Request/Resend Request from Unregistered Host | |
| • Allow Post-receive Job Result Inquiry from Unregistered Host | |
| • Allow Job Result Notification Request from Unregistered Host | |
| • Allow Remote Job Execution Request from Unregistered Host |
(F3) Operation Log Output Option
This field specifies whether to output the operation log records.
<Table> Setting Values for Operation Log Output Option
| On-screen Options |
Description |
|---|---|
| Do Not Output | Do not output the operation log records |
| File Access Log | Output only the File Access Log records |
| Command Execution Log | Output only the Command Execution Log records |
| Output Both | Output both the File Access Log records and the Command Execution Log records |
(F4) Operation Log Auto Switch Size
This field specifies the maximum size of the Operation Log file in MBs.
If the size of the Operation Log file exceeds this value, the file output till then is renamed to be backed up. The backup file is created in the same output directory as the Operation Log file.
If you specify '0' for this field, HULFT does not automatically switch the Operation Log files.
For details, refer to Administration Manual for the client.
(F5) Operation Log Switch Generation Count
This field specifies how many generations of backup files of the Operation Log file should be kept when the Operation Log file is switched. When the number of backup files exceeds this value through automatic or manual switching, the Operation Log file is overwritten sequentially from the oldest file.
Specifying a value other than '0' in the Operation Log Auto Switch Size (oplchangesize) enables this field.
If you omit this specification, HULFT-HUB sets '9999.'
For details, refer to Administration Manual for the client.
(F6) HULFT Manager Password Check
This field specifies whether to check the user and the password, when HULFT Manager tries to connect to the application.
<Table> Setting Values for HULFT Manager Password Check
| On-screen Options |
Description |
|---|---|
| No | Do not check the password |
| Yes | Check the password |
(F7) Allow Send Request/Resend Request from Unregistered Host
Specify how HULFT behaves if the host that is issuing a request is not registered in the Host Information when the Send Request (SEND) or the Resend Request (RESEND) is acknowledged.
<Table> Setting Values for Allow Send Request/Resend Request from Unregistered Host
| On-screen Options |
Description |
|---|---|
| No | Reject Send Request/Resend Request from hosts that are not registered in the Host Information |
| Yes | Acknowledge Send Request/Resend Request from hosts that are not registered in the Host Information |
| [Note] | This field can be specified when the client is Ver.8.4 or higher. |
| For a version earlier than Ver.8.4, specify Request Acknowledge Host Check. |
(F8) Allow Post-receive Job Result Inquiry from Unregistered Host
This field specifies how HULFT behaves if the host that is issuing a request is not registered in the Host Information when Post-receive Job Result Inquiry (HULJOB) is acknowledged.
<Table> Setting Values for Allow Post-receive Job Result Inquiry from Unregistered Host
| On-screen Options |
Description |
|---|---|
| No | Reject the Post-receive Job Result Inquiry request from hosts that are not registered in the Host Information |
| Yes | Acknowledge the Post-receive Job Result Inquiry request from hosts that are not registered in the Host Information |
| [Note] | This field can be specified when the client is Ver.8.4 or higher. |
| For a version earlier than Ver.8.4, specify Request Acknowledge Host Check. |
(F9) Allow Job Result Notification Request from Unregistered Host
This field specifies how HULFT behaves if the host that is issuing a request is not registered in the Host Information when a Job Execution Result Notification (HULSNDRC) request is acknowledged.
<Table> Setting Values for Allow Job Result Notification Request from Unregistered Host
| On-screen Options |
Description |
|---|---|
| No | Reject Notify Job Results from hosts that are not registered in the Host Information |
| Yes | Acknowledge Notify Job Results from hosts that are not registered in the Host Information |
| [Note] | This field can be specified when the client is Ver.8.4 or higher. |
| For a version earlier than Ver.8.4, specify Request Acknowledge Host Check. |
(F10) Allow Remote Job Execution Request from an Unregistered Host
Specify how HULFT behaves if the host that is issuing a request is not registered in the Host Information when a Remote Job Execution (HULRJOB) request is acknowledged.
<Table> Setting Values for Allow Remote Job Execution Request from Unregistered Hosts
| On-screen Options |
Description |
|---|---|
| No | Reject Remote Job Execution requests from hosts that are not registered in the Host Information |
| Yes | Acknowledge Remote Job Execution requests from hosts that are not registered in the Host Information |
| [Note] | This field can be specified when the client is Ver.8.4 or higher. |
| For a version earlier than Ver.8.4, specify Request Acknowledge Host Check. |
(F11) Allow Instant Transfer from Unregistered Host
This field specifies how HULFT behaves if an Instant Transfer from a host that is not registered in the Host Information is acknowledged.
<Table> Setting Values for Allow Instant Transfer from Unregistered Host
| On-screen Options |
Description |
|---|---|
| No | Reject Instant Transfer from hosts that are not registered in the Host Information |
| Yes | Acknowledge Instant Transfer from hosts that are not registered in the Host Information |
| [Note] | This field can be specified when the client is Ver.8.4 or higher. |
(F12) Allow Instant Transfer Receiving Root Directory
Specify the root directory in or under which receive files are stored in instant transfer.
When the save destination for the receive file is specified on the sending-side host, this directory or a subdirectory of this directory must be specified. If another directory is specified, a transfer error occurs.
If a save destination is not specified for the receive file on the sending-side host, the receive file is stored in the directory specified in this field.
| [Note] | This field can be specified when the client is Ver.8.4 or higher. |
This field specifies whether to enable Forced Strong Key Mode.
<Table> Setting Values for Forced Strong Key Mode
| On-screen Options |
Description |
|---|---|
| Disabled | Disable Forced Strong Key Mode |
| Enabled | Enable Forced Strong Key Mode |
| [Remarks] | You cannot modify this field in HULFT-HUB Manager. |
| For details, refer to Administration Manual for the client. |
| [Note] | This field is displayed when the client is Ver.8.4 or higher. |
The following describes each field in the Global settings.
This field specifies the date format that HULFT uses.
After you change the setting, restart HULFT to change the Date Format of HULFT Management screen, various logs, command input/output, and environment variables.
| On-screen Options |
Description |
|---|---|
| YMD | Use the YYYY/MM/DD date format |
| MDY | Use the MM/DD/YYYY date format |
| DMY | Use the DD/MM/YYYY date format |
This field specifies the language in which HULFT operates.
After you change the setting, restart HULFT Management screen to change the language of the management screen.
| On-screen Options |
Description |
|---|---|
| JPN | HULFT operates in Japanese |
| ENG | HULFT operates in English |
The following describes each field in the Transfer Test settings.
For details about the Transfer Test function, refer to Administration Manual for the client.
This field specifies whether HULFT operates in Test-priority Mode or Test-run Mode.
<Table> Setting Values for Transfer Preference
| On-screen Options |
Description |
|---|---|
| Test-priority Mode | HULFT operates in normal operation if the remote host is in Test-priority Mode, and operates in test operation if the remote host is in Test-run Mode |
| Test-run Mode | HULFT operates in test operation |
(H2) Result Handing of Receiving
In test operation, HULFT cannot carry out transfer confirmation for the client on the receiving side if the client on the receiving side does not support the Transfer Test function. This field specifies whether to treat that case as an unsuccessful end or a successful end.
<Table> Setting Values for Result Handing of Receiving
| On-screen Options |
Description |
|---|---|
| Always Terminate Transfer with Error | Give a transfer error when confirmation cannot be carried out for the client on the receiving side |
| Give Success When No Problem Detected on Sending Host | If the client on the sending side is normal, give a successful end even if confirmation cannot be carried out for the client on the receiving side |
This field specifies whether to output the Receive file in test operation.
<Table> Setting Values for Output Receive File
| On-screen Options |
Description |
|---|---|
| No | Do not output the Receive file |
| Yes | Output the Receive file |
This field specifies whether to execute the Pre-send Job in test operation.
<Table> Setting Values for Execute Pre-send Job
| On-screen Options |
Description |
|---|---|
| No | Do not execute the Pre-send Job |
| Yes | Execute the Pre-send Job |
This field specifies whether to execute the Post-send Job in test operation.
<Table> Setting Values for Execute Post-send Job
| On-screen Options |
Description |
|---|---|
| No | Do not execute the Post-send Job |
| Yes | Execute the Post-send Job |
This field specifies whether to execute the Post-receive Job in test operation.
<Table> Setting Values for Execute Post-receive Job
| On-screen Options |
Description |
|---|---|
| No | Do not execute the Post-receive Job |
| Yes | Execute the Post-receive Job |
(H7) Output Results to Transfer Logs
This field specifies whether to output the Send Log records and the Receive Log records in test operation.
<Table> Setting Values for Output Results to Transfer Logs
| On-screen Options |
Description |
|---|---|
| No | Do not output the Send Log records and the Receive Log records |
| Yes | Output the Send Log records and the Receive Log records |
The following describes each field in the Others settings.
This field specifies the time-out duration when one of the following utilities issues a request to HULFT daemons:
- utlsend
- utlrecv
- utlscan
- utlschange
- utlkillsnd
- utlalivecheck
- utltriggerconf
If you set '999999,' HULFT waits for a response without any time limit.
This field specifies the job time-out.
This setting is valid for the execution of the Pre-send Job, the successful job on the receiving side when the Notification is 'Successful Job Completion,' and remote jobs. For the execution of other jobs, HULFT waits without any time limit for the job to end.
If you set '999999,' HULFT waits for the job to end without any time limit.
For details about cases where the Job Timeout is valid, refer to Administration Manual for the client.
This field specifies the timing for the auto deletion of the Send Log records, the Receive Log records, and the Request Acknowledge Log records.
When the number of log records in each log file exceeds the specified value, log file switching is carried out.
If you specify '0' for this field, HULFT does not carry out log file switching.
This field specifies the types of transfer status that are displayed on the Send and Receive Status List screen.
<Table> Setting Values for Status Display Selection
| On-screen Options |
Description |
|---|---|
| Display Only Send | Display only the Send status |
| Display All | Display the Send status and Receive status |
This field specifies the character string that identifies which HULFT system has output the Operation Log records and the trace log records when multiple HULFT systems are running in the same environment.
If you specify a string that is 9 bytes or more, an error occurs and the default value (empty character string) is set.
If you do not specify this field, nothing is displayed.
This field specifies the version of the log file that is used to output the operation status for the Send processing, the Receive processing, and the Request Acknowledge processing.
<Table> Setting Values for Trace Output Version
| On-screen Options |
Description |
|---|---|
| Output the TraceLog(V6 header) and message log | Output the trace log (V6 header) and the message log |
| Output the TraceLog(V7 header) | Output the trace log (V7 header) |
| Output the TraceLog(V8 header) | Output the trace log (V8 header) |
| Output the TraceLog(V8.4 header) (*1) | Output the trace log (V8.4 header) |
| *1: | This option can be specified when the client is Ver.8.4 or higher. |
The content output to the trace log may differ depending on the settings of Output to Trace Log (tracelog).
The content output to the System Log may differ depending on the settings of Output to System Log (syslog).
For details about the Log Output function, refer to Error Codes and Messages for the client.
This field specifies the mode of the log file that is used to output the operation status for the Send processing, the Receive processing, and the Request Acknowledge processing.
<Table> Setting Values for Trace Output Mode
| On-screen Options |
Description |
|---|---|
| Do Not Output | Do not output the trace log records |
| Output Only Unsuccessful Log Records | Output the unsuccessful-type trace log records |
| Output All Log Records | Output all the trace log records |
For details about the Log Output function, refer to Error Codes and Messages for the client.
| [Note] | This field can be specified when the client is Ver.8.4 or higher. |
This field specifies whether to output the message part of the log.
<Table> Setting Values for Log Size Reduction Mode
| On-screen Options |
Description |
|---|---|
| Output full log | Output the message part. |
| Output only common headers | Do not output the message part. |
For details about the Log Output function, refer to Error Codes and Messages for the client.
| [Note] | This field can be specified when the client is Ver.8.4 or higher. |
| However, when the Trace Output Version is V6 Output Mode or V7 Output Mode, even if you specify "Output only common headers", the message part is output. |
This field specifies the name of the output file when HULFT outputs the trace log records.
Specify alphanumeric characters within 256 bytes.
When the client is less than Ver.8.4
You cannot omit this field if you specify "Output Only Unsuccessful Log Records" or "Output All Log Records" for the Trace Output Mode.
When the client is Ver.8.4 or higher
You cannot omit this field if any of the message level check boxes (Information, Warning, or Error) in Output to Trace Logs is selected.
For details about the Log Output function, refer to Error Codes and Messages.
This field specifies the timing for switching the trace output file in MBs.
HULFT creates a backup when the trace output file reaches the specified size.
The backup file is always overwritten.
The backup file name is the file name of the trace output file with the '.bak' extension added.
This field specifies the port number that is used if you have installed HULFT Script.
Ensure that this port number is not the same as a port number that is reserved by the operating system, or a port number that is used by another HULFT daemon.
For details, refer to HULFT Script Manual.
This field specifies whether to output records to the trace log for each message level.
<Table> Setting Values for Output to Trace Logs
| On-screen Options |
Description |
|---|---|
| The check box is selected | Output to the trace log |
| The check box is not selected | Do not output to the trace log |
The message level that you can specify are as follows:
- Information
- Warning
- Error
For details about the message level, refer to Error Codes and Messages.
| [Note] | This field can be specified when the client is Ver.8.4 or higher. |
This field specifies whether to output records to the System Log for each level of message.
<Table> Setting Values for Output to System Logs
| On-screen Options |
Description |
|---|---|
| The check box is selected | Output to system logs |
| The check box is not selected | Do not output to system logs |
The types of messages that you can specify are as follows:
- Information
- Warning
- Error
For details about the message level, refer to Error Codes and Messages.
| [Note] | This field can be specified when the client is Ver.8.4 or higher. |
The following describes each field in the Inter-HULFT Settings.
You can configure the Inter-HULFT Settings for clients on which HULFT8 for UNIX/Linux-Enterprise is installed.
(J1) Path to Shared Environment by HULFT Products
This field is used to carry out exclusive control for the same files as HULFT that is installed on another host, in an environment where HULFT8 for UNIX/Linux-Enterprise is installed. You must specify a path that indicates the same directory for all HULFT systems that carry out exclusive control of the same files.
If you omit this specification, HULFT-HUB sets 'HULPATH.' For details about HULPATH, refer to Administration Manual for the client.
This field specifies the lock system to be used for local files when HULFT8 for UNIX/Linux-Enterprise is installed.
<Table> Setting Values for Local File Lock Mode
| On-screen Options |
Description |
|---|---|
| Mode 0 | Do not use networked file locking for local files |
| Mode 1 | Use networked file locking for local files |
For details about networked file locking, refer to Administration Manual for the client.