Registered Client Information
This topic explains how to register the information that is required by HULFT-HUB Server in order to manage, monitor, and connect clients.
You can view and modify this information on the following screens:
- Client Registration dialog box (new registration)
- Management screen (modification)
List of Fields
1. Registered Client Information
<Table> List of Fields for Registered Client Information
| No. | Field Name | Default Value | Setting Value | Specification | Remarks |
|---|---|---|---|---|---|
| A1 | Host Name | Alphanumeric characters | Mandatory | Within 44 bytes *1 | |
| A2 | Domain Name | Alphanumeric characters | Optional | Within 44 bytes *1 | |
| A3 | Service Name | Alphanumeric characters | Optional | Within 100 bytes | |
| A4 | Alias | Alphanumeric characters | Optional | Within 256 bytes | |
| A5 | Product Type | HULFT7 | *2 | Mandatory | |
| A6 | JIS Year | 83JIS | *2 | Mandatory | *5 |
| A7 | Notify User Details | No *3 | *2 | Optional | |
| A8 | Forced Strong Key Mode | Disabled *3 | *2 | Mandatory | |
| A9 | Host Type | *2 | Mandatory | ||
| A10 | Kanji Code Type | *2 | Mandatory | *6 | |
| A11 | Switch to HUB Transfer | Do Not Switch *3 | *2 | Mandatory | |
| A12 | Outside of Control | Controlled *3 | *2 | Mandatory | |
| A13 | Server Retry at Receive Multiplex Level Over | Retry *4 | *2 | Mandatory | |
| A14 | Receive Port No. | 30000 | From 1 to 65535 | Mandatory | |
| A15 | Request Acknowledge Port No. | 31000 | From 1 to 65535 | Mandatory | |
| A16 | User Name | Alphanumeric characters | Optional | Within 20 bytes | |
| A17 | Password | Alphanumeric characters | Optional | Within 14 bytes | |
| A18 | Connect ID | Alphanumeric characters | Optional | Within 16 bytes | |
| A19 | Transfer Multiplex Level by Destination |
16 |
From 1 to 100 |
Mandatory | Mainframe only |
| A20 | Monitor Receive Activities | Yes | *2 | Mandatory | |
| A21 | Monitor Request Acknowledge Activities | Yes | *2 | Mandatory | |
| A22 | Comment | Alphanumeric characters | Optional | Within 60 bytes | |
| A23 | Notification Host Name | Alphanumeric characters | Optional | Within 68 bytes |
| *1: | Specify the host name and the domain name so that the total length of those settings is within 44 bytes. |
| During registration of the client, specify the Host Name and the Domain Name separately. After registration of the client, HULFT-HUB displays 'Host Name.Domain Name' as the host name. | |
| *2: | Select an option from the list that is shown on the screen. |
| *3: | The check box is not selected. |
| *4: | The check box is selected. |
| *5: | When the client is HULFT Ver.8.1 or higher, this field is displayed as Standard for Japanese on the Registered Client setting screen. |
| *6: | When the client is HULFT Ver.8.1 or higher, this field is displayed as Code Set for Transfer on the Registered Client setting screen. |
2. Additional Information other than Registered Client Information (Controlling Server)
<Table> List of Fields for Additional Information other than Registered Client Information (Controlling Server)
| No. | Field Name | Default Value | Setting Value | Specification | Remarks |
|---|---|---|---|---|---|
| B1 | Host Name | *1 | *2 | ||
| B2 | Service Name | *1 | *2 |
| *1: | You are allowed only to view this field on the screen. |
| *2: | This field is available only when you view or update the Registered Client Information on the Management screen. |
| [Legend] | |
| Default Value | Value that is set for the field when you create a new management information record on a screen |
| Specification | Whether the specification is mandatory or optional when you update the management information record on a screen |
Explanation of Each Field
1. Registered Client Information
This field specifies the host name of the client. Assign a name that is unique in the managed HULFT-HUB network, because it will be used on the screens and in the log records in HULFT-HUB Manager.
You cannot include : or / in the host name.
Specify the host name so that the total length of the strings for the Host Name and the Domain Name is within 44 bytes.
Domain name of the client
Specify the domain name so that the total length of the strings for the Host Name and the Domain Name is within 44 bytes.
| [Remarks] | Although you specify a host name and a domain name separately when registering a client on the Client Registration dialog box, after registration, HULFT-HUB system recognizes 'Host Name.Domain Name' as the host name. On each screen other than the Client Registration dialog box in HULFT-HUB Manager, HULFT-HUB shows 'Host Name.Domain Name' for the Host Name. |
Service name of the client
HULFT-HUB uses this name to identify clients with the same host name.
This field specifies the service name that is used to distinguish the relevant client from other HULFT instances or HULFT-HUB Server instances that are operating on the same host. You do not have to specify this field if the relevant client is the only client that is operating on the same host.
If you specify this field, assign a name that is unique on the host.
If you omit this field, HULFT-HUB identifies the client only by the host name.
You cannot include : or / in the service name.
| [Note] | |
| • | You can use the service name to distinguish HULFT or HULFT-HUB Server from other HULFT instances or HULFT-HUB Server instances on the same host only when 'Format with Port No.' is specified for the Notification Host Name for Transfer via HUB (HostNameNotice) in the System Environment Settings of HULFT-HUB Server. When 'Format with Port No. for Controlled Clients Only' or 'Format without Port No.' is specified, do not allow multiple HULFT instances or HULFT-HUB Server instances to coexist on the same host. |
| • | If you register HULFT for Windows in HULFT-HUB Server, it is not necessary to match the Service Name in the Registered Client Information and the HULFT service name that operates on the actual client (Windows). |
This field specifies the alias for 'Host Name + Service Name.'
It is recommended that you assign a unique name in the managed HULFT-HUB network so that the client that is displayed as 'Host Name + Service Name' on screens in HULFT-HUB Manager can be easily identified.
This field specifies the product type of the client.
| On-screen Options | Product Name |
|---|---|
| HULFT10 |
HULFT10 for zOS HULFT10 for Linux/AIX HULFT10 for Windows HULFT10 for IBMi |
| HULFT8 |
HULFT8 for zOS HULFT8 for MSP HULFT8 for XSP HULFT8 for UNIX/Linux HULFT8 for Windows HULFT8 for IBMi |
| HULFT7 |
HULFT7 for zOS HULFT7 for MSP HULFT7 for XSP HULFT7 for UNIX/Linux HULFT7 for Windows HULFT7 for i5OS |
This field specifies the JIS year for the Kanji code on the client.
| On-screen Options |
Description |
|---|---|
| 78JIS | JIS 1978 |
| 83JIS | JIS 1983 |
If you specify "Yes", you can notify the account information of HULFT-HUB Manager to the client.
For the operation log of the current client, the login account for HULFT-HUB Server is stored on User ID (Management screen), and the user ID on the operating system on which HULFT-HUB Manager is operating is stored on User ID (OS).
The default value is "No".
Specification of Forced Strong Key Mode for Client
You can set this field only for Client outside of Control (with Relay).
| On-screen Options |
Description |
|---|---|
| Check box selected | Enable Forced Strong Key Mode |
| Check box not selected | Disable Forced Strong Key Mode |
This field specifies the host type of the client.
| On-screen Options |
Description |
|---|---|
| Mainframe | Mainframe |
| Linux | Linux/UNIX/NonStop |
| Windows | Windows operating system |
| IBMI | IBMi |
The host type that you can specify varies depending on the setting value for the Product Type. The table below shows combinations of product type and host type.
| Product Type | Host Type | |||
|---|---|---|---|---|
| Mainframe | UNIX | Windows | IBMi | |
| HULFT10 | ✓ | ✓ | ✓ | ✓ |
| HULFT8 | ✓ | ✓ | ✓ | ✓ |
| HULFT7 | ✓ | ✓ | ✓ | ✓ |
| [Legend] | |
| ✓: | Can be specified |
| Blank: | Cannot be specified |
This field specifies the Kanji code type of the client.
| On-screen Options |
Description |
|---|---|
| JEF | JEF |
| IBM Kanji | IBM Kanji |
| EUC-JP | EUC |
| SHIFT-JIS | SHIFT-JIS |
| UTF-8 | UTF-8 |
| GB18030 | GB18030 |
| IBM Simplified Chinese | IBM Simplified Chinese |
The Kanji code type that you can specify varies depending on the setting for the Host Type. The table below shows combinations of host type and Kanji code type.
| Kanji Code Type | Host Type | |||
|---|---|---|---|---|
| Mainframe | UNIX | Windows | AS/400 | |
| JEF | ✓ | - | - | - |
| IBM Kanji | ✓ | - | - | ✓ |
| EUC-JP | - | ✓ | - | - |
| SHIFT-JIS | - | ✓ | ✓ | - |
| UTF-8 | *3 | *1 | *2 | *3 |
| GB18030 | - | *2 | *2 | - |
| IBM Simplified Chinese | - | - | - | *2 |
| *1: | Can be specified in HULFT7 or higher |
| *2: | Can be specified in HULFT8 Ver.8.1 or higher |
| *3: | Can be specified in HULFT8 Ver.8.1 or higher, and lower than HULFT10 Ver.10.0 |
| [Legend] | |
| ✓: | Can be specified |
| Blank: | Cannot be specified |
This field specifies whether HULFT-HUB replaces the content of the Transfer Group Information and the Host Information, in order to switch from file transfer carried out by clients that are connected directly to file transfer via HULFT-HUB Server.
Use the Switch to HUB Transfer check box to configure this setting.
| On-screen Options |
Description |
|---|---|
| Check box selected | Switch to transfer via HUB (replace the content of the Transfer Group Information and the Host Information) |
| Check box not selected | Do not switch to transfer via HUB (do not replace the content of the Transfer Group Information and the Host Information) |
For details about the switching rules, refer to "Points to be Noted When Configuring Settings."
This field is shown only during new registration.
This field specifies whether a client is outside of the control of the relevant HULFT-HUB system.
Use the Outside of Control check box to configure this setting.
| On-screen Options |
Description |
|---|---|
| Check box selected | Client outside of Control |
| Check box not selected | Client under Control |
If the client is outside of control, you can use the radio buttons to select 'With Relay' or 'Without Relay.' The default value is 'Without Relay.'
The default value is Client under Control (not selected).
(A13) Server Retry at Receive Multiplex Level Over
This field specifies whether HULFT-HUB Server that relays transfer retries a connection or not if an error occurs because the Receive Multiplex Level has been exceeded during socket connection to the host on the receiving side during file transfer.
| On-screen Options |
Description |
|---|---|
| Check box selected | Retry a connection |
| Check box not selected | Treat as an error without retrying a connection |
You cannot specify this field for a Client outside of Control.
HULFT-HUB uses the Connect Retry Count (SocketRetryMax) and the Connect Retry Interval (SocketRetryInterval) of the server (Controlling Server) to which the client is registered for the retry count and the wait time for reconnecting.
For details about the Connect Retry Count (SocketRetryMax) and the Connect Retry Interval (SocketRetryInterval), refer to System Environment Settings (HULFT-HUB Server).
| [Note] | If you have not specified the Accumulation processing for transfer via HULFT-HUB Server, HULFT-HUB applies the Server Retry at Receive Multiplex Level Over when a Receive Process Multiplex Level error occurs on the client on the receiving side. Note that in this case HULFT-HUB counts even transfers that are carried out between clients and not via HULFT-HUB Server toward the Receive Process Multiplex Level. |
This field specifies the Receive port number of the client.
Ensure that this port number is not the same as a port number that is reserved by the operating system, a port number that is used by another application, or the port number that is specified for the Request Acknowledge Port No.
| [Note] | |
| - | If multiple clients with the same host name are started in the same system, you cannot specify the same port number for the clients. |
| - | You cannot specify the same port number as the Request Acknowledge Port No. |
(A15) Request Acknowledge Port No.
This field specifies the Request Acknowledge port number of the client.
Ensure that this port number is not the same as a port number that is reserved by the operating system, a port number that is used by another application, or the port number that is specified for the Receive Port No.
| [Note] | |
| - | If multiple clients with the same host name are started in the same system, you cannot specify the same port number for the clients. |
| - | You cannot specify the same port number as the Receive Port No. |
This field specifies the user name that HULFT-HUB uses to connect to a client that has Password Check set.
For details on the Password Check, refer to Administration Manual for the client.
| [Note] | You cannot specify this field for a Client outside of Control. |
This field specifies the password that HULFT-HUB uses to connect to a client that has Password Check set.
For details on the Password Check, refer to Administration Manual for the client.
| [Note] | You cannot specify this field for a Client outside of Control. |
This field specifies the name to identify the target host when you use the XML Conversion Information settings.
You cannot omit this field if you use the XML Conversion Information settings.
| [Note] | |
| - | You cannot specify this field for a Client outside of Control. |
| - | If you use HULFT Manager, specify the same Connect ID. |
(A19) Transfer Multiplex Level by Destination
This field specifies the Receive Multiplex Level of the client.
You can set this field only if the client runs HULFT for Mainframe.
This is treated the same way as the Receive Process Multiplex Level in the System Environment Settings in HULFT for UNIX, HULFT for IBMi, and HULFT for Windows, and is used for management of the multiplex level by host.
(A20) Monitor Receive Activities
This field specifies whether to monitor the Receive activities of the client.
| On-screen Options |
Description |
|---|---|
| Yes | Monitor the Receive activities |
| No | Do not monitor the Receive activities |
If you specify 'Yes,' HULFT-HUB monitors regularly according to the setting value for the Client Activity Monitoring Interval (HealthCheckInterval).
For details about the Client Activity Monitoring Interval (HealthCheckInterval), refer to System Environment Settings (HULFT-HUB Server).
(A21) Monitor Request Acknowledge Activities
This field specifies whether to monitor the Request Acknowledge activities of the client.
| On-screen Options |
Description |
|---|---|
| Yes | Monitor the Request Acknowledge activities |
| No | Do not monitor the Request Acknowledge activities |
If you specify 'Yes,' HULFT-HUB monitors regularly according to the setting value for the Client Activity Monitoring Interval (HealthCheckInterval).
For details about the Client Activity Monitoring Interval (HealthCheckInterval), refer to System Environment Settings (HULFT-HUB Server).
This field specifies the comment regarding the client.
This field specifies the host name that is notified to the client as the name of the remote host for the file transfer.
If you omit this field, HULFT-HUB sends notification of the host name that you specified for the Host Name in a format with or without a Port No. according to the Notification Host Name for Transfer via HUB (HostNameNotice) in the System Environment Settings of HULFT-HUB Server.
| [Note] | |
| - | You cannot specify this field for a Client outside of Control (without Relay). |
| - | If you specify the Notification Host Name when you register a new client, do not select the Switch to HUB Transfer check box. |
2. Additional information other than Registered Client Information
This additional information is displayed together with the Registered Client Information on each screen where you can edit the Registered Client Information.
This field shows the host name of HULFT-HUB Server (Controlling Server) to which the client is registered.
This field is available only in the Registered Client Information that is displayed in the Management Information frame on the Management screen.
This field shows the service name of HULFT-HUB Server (Controlling Server) to which the client is registered.
This field is available only in the Registered Client Information that is displayed in the Management Information frame on the Management screen.
Points to be Noted When Configuring Settings
1. Checking for duplicate host name and port number
Assign host names, domain names, and service names for hosts so that the following combinations of those names are unique in your HULFT-HUB system:
| - Host Name | |
| - Host Name.Domain Name | |
| - Host Name:Service Name | |
| - Host Name.Domain Name:Service Name |
2. Rules for switching to HUB Transfer
HULFT-HUB automatically registers the Host Information and replaces the Transfer Group Information in order to switch the transfer method from transfer between clients to transfer via HULFT-HUB Server.
HULFT-HUB registers the Host Information that has PROXY information set, so that file transfer can be carried out via HULFT-HUB Server for hosts that have a host name of 44 bytes or less.
The host name varies depending on the Notification Host Name for Transfer via HUB (HostNameNotice) setting in the System Environment Settings for HULFT-HUB Server.
| Notification Host Name for Transfer via HUB (HostNameNotice) | Host Name in Host Information |
|---|---|
| Format with Port No. | Host Name_Receive Port No. |
| Format with Port No. for Controlled Clients Only | |
| Format without Port No. | Host Name |
During the replacement of the Transfer Group Information, HULFT-HUB will modify the defined host name if the following conditions are met:
- All hosts that belong to the transfer group must be registered on the Structure Diagram.
- Host name must be 44 bytes or less.
Host names for the Transfer Group Information that meet these conditions are replaced as indicated in the table above.
For details, refer to Route Batch Modification.