Transfer Information
This topic explains how to register information on HULFT-HUB Server in order to relay file transfers and carry out multicasting.
You can view and modify this information on the following screens:
- Transfer Information screen
- Collecting and Distributing System Management Information screen
You can also import and export this information on the following screen:
- Collecting and Distributing System Management Information screen
List of Fields
<Table> List of Fields for Transfer Information (Relay/Multicasting Settings)
| No. | Field Name | Default Value | Setting Value | Specification | Remarks | Transfer | Distribute |
|---|---|---|---|---|---|---|---|
| A1 | Transfer Type | *5 | ✓ | Advanced Settings | |||
| A2 | File ID | *1 | ✓ | Outside the panel | |||
| A3 | Transfer Source Host Name *3 | *1 | ✓ | Outside the panel | |||
| A4 | File Alias *4 | Alphanumeric characters | Optional | Within 256 bytes | ✓ | Outside the panel | |
| A5 | When Multicasting is Unsuccessful | Defer to System Environment Settings | *2 | Mandatory | ✓ | Advanced Settings | |
| A6 | Criterion for Unsuccessful Multicasting | Defer to System Environment Settings | *2 | Mandatory | ✓ | Advanced Settings | |
| A7 | Comment | Alphanumeric characters | Optional | Within 60 bytes | ✓ | Advanced Settings | |
| A8 | Sending Side Destination Type | Auto Arrangement | *2 | Mandatory | *5 | Advanced Settings | |
| A9 | Business Group ID | *2 | Mandatory | - | Outside the panel |
| *1: | You are allowed only to view this field on the screen. |
| *2: | When you configure settings on the screen, select an option from the list that is shown on the screen. |
| *3: | This information is shown in the fields 'Transfer Source Host Name' and 'Transfer Source Service Name' on the Collecting and Distributing System Management Information screen. |
| *4: | This information is shown as 'Alias' on the Collecting and Distributing System Management Information screen. |
| *5: | On the Transfer Information screen, you are only allowed to view this setting. (To modify this setting, use the [Route Settings] menu.) |
<Table> List of Fields for Transfer Information (Accumulation Settings)
| No. | Field Name | Default Value | Setting Value | Specification | Remarks | Transfer | Distribute | |
|---|---|---|---|---|---|---|---|---|
| B1 | Accumulation Condition | Defer to System Setting | *1 | Mandatory | ✓ | Accumulation Settings | ||
| B2 | Continuation Condition | Defer to System Setting | *1 | Mandatory | ✓ | Accumulation Settings | ||
| B3 | Accumulated File Deletion Condition | Defer to System Setting | *1 | Mandatory | ✓ | Accumulation Settings | ||
| B4 | Transfer Result Notification to Sending Side When Accumulation is Complete | Defer to System Setting | *1 | Mandatory | ✓ | Accumulation Settings | ||
| B5 | Verify Data | No | *1 | Mandatory | ✓ | Accumulation Settings | ||
| B6 | Storage Expiration Date | Period | *1 | Mandatory | ✓ | Accumulation Settings | ||
| B7 | Period | Number | 1 |
days: From 0 to 999 weeks: From 1 to 99 months: From 1 to 99 |
Mandatory | ✓ | Accumulation Settings | |
| B8 | Unit | weeks | days, weeks, months | Mandatory | ✓ | Accumulation Settings | ||
| B9 | Every Week | (Day of the Week) | Sun | Sun, Mon, Tue, Wed, Thu, Fri, Sat | Mandatory | ✓ | Accumulation Settings | |
| B10 | Every Month | (Day) | 1 | From 1 to 31, End | Mandatory | ✓ | Accumulation Settings | |
| B11 | week | 1st | 1st, 2nd, 3rd, 4th, Final | Mandatory | ✓ | Accumulation Settings | ||
| B12 | (Day of the Week) | Sun | Sun, Mon, Tue, Wed, Thu, Fri, Sat | Mandatory | ✓ | Accumulation Settings | ||
| B13 | Stored Generation File | Defer to System Setting | *1 | Mandatory | ✓ | Accumulation Settings | ||
| B14 | Stored Generation File Count | 0 | From 1 to 9999 | Mandatory | ✓ | Accumulation Settings | ||
| B15 | Prohibiting Overtaking | Defer to System Setting | *1 | Mandatory | ✓ | Accumulation Settings | ||
| B16 | Handling of Send Request When Undelivered Data Does Not Exist | Defer to System Setting | *1 | Mandatory | ✓ | Accumulation Settings | ||
| *1: | When you configure settings on the screen, select an option from the list that is shown on the screen. |
<Table> List of Fields for Transfer Information (Job Flow Setting)
| No. | Field Name | Default Value | Setting Value | Specification | Remarks | Transfer | Distribute |
|---|---|---|---|---|---|---|---|
| C1 | Post-accumulation Successful Job Flow ID | Alphanumeric characters | Optional | Within 16 bytes | ✓ | Job Flow Setting | |
| C2 | Post-accumulation Unsuccessful Job Flow ID | Alphanumeric characters | Optional | Within 16 bytes | ✓ | Job Flow Setting | |
| C3 | Completion Notification | Accumulation Complete | *1 | Mandatory | ✓ | Job Flow Setting |
| *1: | When you configure settings on the screen, select an option from the list that is shown on the screen. |
<Table> List of Fields for Transfer Information (Extension Settings)
| No. | Field Name | Default Value | Setting Value | Specification | Remarks | Transfer | Distribute |
|---|---|---|---|---|---|---|---|
| D1 | Transfer Interval | 0 | From 0 to 32760 | Mandatory | - | Extension Settings | |
| D2 | SndHostPort | From 1 to 65535 | Optional | - | Extension Settings | ||
| D3 | EBCDIC Set | A | *1 | Mandatory | - | Extension Settings | |
| D4 | Cipher Key | Alphanumeric characters | *2 | *2 *3 | - | Extension Settings | |
| D5 | Receive Host Type | Unix | *1 | Optional | - | Extension Settings | |
| D6 | Receive Transfer Code Set | UTF-8 | *1 | Optional | - | Extension Settings |
| *1: | When you configure settings on the screen, select an option from the list that is shown on the screen. |
|
*2: |
The value that can be specified for the Cipher Key differs depending on whether the file transfer is performed in Forced Strong Key Mode. - Forced Strong Key Mode is "Enabled": 64-character hexadecimal text string (0-9, A-F) (Mandatory). - Forced Strong Key Mode is "Disabled": 8 to 20 alphanumeric characters (Optional). |
| *3: | On the Collecting and Distributing System Management Information screen, Forced Strong Key Mode is displayed if the sending side is a server outside of control. The user must specify whether to enable or disable the Forced Strong Key Mode. |
| [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 |
| Transfer | Transfer Information screen |
| Distribute | Collecting and Distributing System Management Information screen |
| ✓ | Availability of the field |
Explanation of Each Field
The following describes the fields that are configured in the Transfer Information.
For a field for which you select an option from the list, the following shows both the options that are displayed on the screen and the values that are described in the CSV file to be used for Collecting and Distributing System Management Information.
1. Relay/Multicasting Settings
This field shows the transfer mode on HULFT-HUB Server.
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Relay | 0 | Relay the transfer of data. |
| HUB Multicasting | 1 | Carry out multicasting from HUB. |
| HULFT Multicasting with HUB Relay | 2 | Carry out multicasting from HULFT via HUB. |
If you create a Transfer definition on the Transfer Information screen in HULFT-HUB Manager, HULFT-HUB automatically sets this field when you determine the route on the transfer map.
This field specifies the ID to identify the files to be transferred.
(A3) Transfer Source Host Name
This field specifies the host name of the client or of the server that is at the starting point of the transfer.
This field specifies the alias for the file to be transferred.
(A5) When Multicasting is Unsuccessful
This field specifies how HULFT-HUB Server handles the Send processing for the other transfer destination hosts if an error occurs when transferring data to one or more of the transfer destination hosts during multicasting.
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Cancel | 0 | Immediately cancel multicasting. |
| Continue | 1 | Cancel only transfers to hosts on which transfer errors are detected, and continue the processing for other hosts. |
| Defer to System Environment Settings | 2 | Use the values for the When Multicasting is Unsuccessful (MulticastError) in the System Environment Settings of HULFT-HUB Server. |
If you create a new record of information on the Transfer Information screen, 'Defer to System Environment Settings' is set as the default value.
| [Note] | |
| • | If you carried out the accumulation of data on HULFT-HUB Server, the When Multicasting is Unsuccessful is disabled because transfers to the host on the receiving side are delivered from HULFT-HUB Server. |
| • | If a no-communications timeout occurs with the connection destination host, an error may be notified on the transfer source host. |
| In this case, because the transfer ends abnormally on the transfer source host, the transfer is canceled regardless of the value of this field. |
(A6) Criterion for Unsuccessful Multicasting
This field specifies the criterion when HULFT-HUB Server sends notification of a transfer error to the host on the sending side if an error occurs when transferring data to one or more hosts during multicasting.
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| When Error Occurs in All Transfers | 0 | Send notification of a transfer error when file transfer fails to all transfer destination hosts. |
| When Error Occurs at One of Multicasting Destinations | 1 | Send notification of a transfer error when file transfer fails with one or more transfer destination hosts. |
| Defer to System Environment Settings | 2 | Use the values for the When Multicasting is Unsuccessful (MulticastError) in the System Environment Settings of HULFT-HUB Server. |
If you create a new record of information on the Transfer Information screen, 'Defer to System Environment Settings' is set as the default value.
This field is enabled when you specify 'Continue' (1) for the When Multicasting is Unsuccessful.
| [Note] | If a no-communications timeout occurs with the connection destination host, an error may be notified on the transfer source host. In this case, because the transfer ends abnormally on the transfer source host, the value of this field does not apply. |
This field specifies the comment for the transfer conditions.
(A8) Sending Side Destination Type
This field shows the type of route settings when you configure routing via HULFT-HUB Server.
The type of transfer destination host when viewed from the sending side client varies depending on the route settings.
If the route setting is 'Auto Arrangement,' the transfer destination host is a client. If the route setting is 'Manual Arrangement,' the transfer destination host is a server.
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Auto Arrangement | 0 | Route setting is 'Auto Arrangement.' (Transfer destination host is a client.) |
| Manual Arrangement | 1 | Route setting is 'Manual Arrangement.' (Transfer destination host is a server.) |
If you create a Transfer definition on the Transfer Information screen in HULFT-HUB Manager, HULFT-HUB automatically sets this field when you determine the route on the transfer map.
This field specifies the Business Group ID to which this Transfer Information belongs.
| [Remarks] | You can view this field on the Collecting and Distributing System Management Information screen. |
2. Accumulation Settings
This field specifies whether or not the server accumulates transfer data during transfer.
If you have already set 'Accumulate Only' (4) on a different server within the same definition, you cannot select 'Accumulate Only' (4).
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Never Accumulate | 0 | Data is never accumulated regardless of whether the transfer processing is successful or unsuccessful. |
| Accumulate Only When Unable to Transfer | 1 | Data is accumulated when the transfer processing does not start. If the transfer processing starts successfully, data is not accumulated even if an error occurs during transfer. |
| Transfer and Accumulate Concurrently | 2 | Accumulation and transfer of data start simultaneously. |
| Deliver after Accumulation | 3 | Data is transferred after the accumulation of transferred data completes successfully. |
| Accumulate Only | 4 | Transfer data is accumulated on the server, and delivered if there is a Deliver Request. |
| Defer to System Setting | 5 | This is dependent on the setting value for the Accumulation Condition in the server's Accumulation environment settings. |
| [Note] | If you specify the Post-accumulation Successful Job Flow ID and the Post-accumulation Unsuccessful Job Flow ID, you can specify only 'Accumulate Only' (4) for the Accumulation Condition. |
This field specifies the continuation or cancellation of processing if an error occurs during transfer or accumulation.
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Continue to Transfer and Accumulate when Error Occurs | 1 | If an error occurs during transfer or accumulation, the processing for which an error did not occur continues. |
| Continue to Accumulate when Transfer Error Occurs | 2 | If an error occurs during transfer, the transfer processing is cancelled. The Accumulation processing continues. |
| Continue to Transfer when Accumulation Error Occurs | 3 | If an error occurs during accumulation, the Accumulation processing is cancelled. The transfer processing continues. |
| Cancel Transfer and Accumulation when Error Occurs | 4 | If an error occurs during transfer or accumulation, both the transfer processing and the Accumulation processing are cancelled. |
| Defer to System Setting | 5 | This is dependent on the setting value for the Continuation Condition in the server's Accumulation environment settings. |
(B3) Accumulated File Deletion Condition
This field specifies the timing for the deletion of the accumulated or delivered data.
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Do Not Delete | 0 | The data will not be automatically deleted. You must delete the data manually. |
| Delete Immediately after Transfer or Delivery is Complete | 1 | Accumulated data is deleted after delivery completes successfully. |
| Delete when Specified Period has Elapsed after Accumulation is Complete | 2 | After the accumulation of data is completed successfully, the data is deleted when the date that is specified for the Storage Expiration Date has passed. |
| Delete when Specified Period has Elapsed after Delivery is Complete | 3 | After the delivery of data is completed successfully, the data is deleted when the date that is specified for the Storage Expiration Date has passed. |
| Defer to System Setting | 4 | This is dependent on the setting value for the Accumulated File Deletion Condition in the server's Accumulation environment settings. |
(B4) Transfer Result Notification to Sending Side When Accumulation is Complete
This field specifies the way to notify transfer results to the host on the sending side at the completion of accumulation when the setting of the Accumulation Condition is 'Accumulate Only When Unable to Transfer' (1), 'Transfer and Accumulate Concurrently' (2), or 'Deliver after Accumulation' (3).
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Always Return as Transfer Complete | 0 | When accumulation of data is complete, always send notification that transfer is complete to the host on the sending side. |
| Defer to Transfer Results for Receive Host | 1 | If there is an error during the transfer of data to the host on the receiving side, even if accumulation of data is complete, send notification that a transfer error occurred to the host on the sending side. If the transfer of data to the host on the receiving side is successful, send notification that transfer is complete to the host on the sending side. |
| Defer to System Setting | 2 (default value) | This is dependent on the setting value for the Transfer Result Notification to Sending Side When Accumulation is Complete in the server's Accumulation environment settings. |
This field specifies whether or not to verify data of the file to be received.
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| No | 0 | Do not verify data |
| Yes | 1 | Verify data |
This field specifies the storage expiration date for the accumulated or delivered data.
Specify this field if the Accumulated File Deletion Condition setting is 'Delete when Specified Period has Elapsed after Accumulation is Complete' (2) or 'Delete when Specified Period has Elapsed after Delivery is Complete' (3).
For details about the Storage Expiration Date, refer to the explanation of the storage period for accumulated data in HULFT-HUB Manual.
| On-screen Options |
Description |
|---|---|
| Period | Data is deleted if the specified period has passed. |
| Every Week | Once a week, on the specified day of the week, data for which the storage expiration date has passed is deleted. The storage period is at least 1 week but less than 2 weeks. |
| Every Month | Once a month, on the specified day of the week or day of the month, data for which the storage expiration date has passed is deleted. The storage period is at least 1 month but less than 2 months. |
| [Remarks] | For details about the format of the CSV file to use when importing or exporting information on the Collecting and Distributing System Management Information screen, refer to Format of Transfer Information. |
Specify this field when the Storage Expiration Date is set as 'Period.'
Specify the period for storing data in combination with the setting that is described in "(B8) Period_Unit."
If you specify the Period_Unit as 'days,' set a numeric value from 0 to 999.
If you specify the Period_Unit as 'weeks' or 'months,' set a numeric value from 1 to 99.
| [Remarks] | For details about the format of the CSV file to use when importing or exporting information on the Collecting and Distributing System Management Information screen, refer to Format of Transfer Information. |
Specify this field when the Storage Expiration Date is set as 'Period.'
Specify the period for storing data in combination with the setting of the Period_Number.
| On-screen Options |
Description |
|---|---|
| days | The value for the Period_Number is number of days. |
| weeks | The value for the Period_Number is number of weeks. |
| months | The value for the Period_Number is number of months. |
| [Remarks] | For details about the format of the CSV file to use when importing or exporting information on the Collecting and Distributing System Management Information screen, refer to Format of Transfer Information. |
(B9) Every Week_(Day of the Week)
Specify this field when the Storage Expiration Date is set as 'Every Week.'
Specify a day of the week to delete data for which the storage expiration date has passed.
| On-screen Options |
Description |
|---|---|
| Sun | Delete data every Sunday |
| Mon | Delete data every Monday |
| Tue | Delete data every Tuesday |
| Wed | Delete data every Wednesday |
| Thu | Delete data every Thursday |
| Fri | Delete data every Friday |
| Sat | Delete data every Saturday |
| [Remarks] | For details about the format of the CSV file to use when importing or exporting information on the Collecting and Distributing System Management Information screen, refer to Format of Transfer Information. |
Specify this field when the Storage Expiration Date is set as 'Every Month.'
Specify a day of the month to delete data for which the storage expiration date has passed.
| On-screen Options |
Description |
|---|---|
| From 1 to 31 | Delete the data on the specified day. |
| End | Delete the data on the last day of the month. |
| [Remarks] | For details about the format of the CSV file to use when importing or exporting information on the Collecting and Distributing System Management Information screen, refer to Format of Transfer Information. |
Specify this field when the Storage Expiration Date is set as 'Every Month.'
Specify a week of the month that is used in combination with the setting that is described in "(B10) Every Month_(Day of the Week)" to delete data for which the storage expiration date has passed.
| On-screen Options |
Description |
|---|---|
| 1st | Delete data on the specified day of the 1st week of the month. |
| 2nd | Delete data on the specified day of the 2nd week of the month. |
| 3rd | Delete data on the specified day of the 3rd week of the month. |
| 4th | Delete data on the specified day of the 4th week of the month. |
| Final | Delete data on the last occurrence of the specified day of the month. |
| [Remarks] | For details about the format of the CSV file to use when importing or exporting information on the Collecting and Distributing System Management Information screen, refer to Format of Transfer Information. |
(B12) Every Month_(Day of the Week)
Specify this field when the Storage Expiration Date is set as 'Every Month.'
Specify a day of the week that is used in combination with the setting that is described in "(B9) Every Month_week" to delete data for which the storage expiration date has passed.
| On-screen Options |
Description |
|---|---|
| Sun | Delete data on Sunday of the specified week. |
| Mon | Delete data on Monday of the specified week. |
| Tue | Delete data on Tuesday of the specified week. |
| Wed | Delete data on Wednesday of the specified week. |
| Thu | Delete data on Thursday of the specified week. |
| Fri | Delete data on Friday of the specified week. |
| Sat | Delete data on Saturday of the specified week. |
| [Remarks] | For details about the format of the CSV file to use when importing or exporting information on the Collecting and Distributing System Management Information screen, refer to Format of Transfer Information. |
This field specifies how the server behaves if the data that was transferred to the server has the same file ID as existing data that is within the storage period.
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| No Generation File | 0 | Do not create generation files based on the Stored Generation File Count. |
| Limit to Number of Stored Generations | 1 | Create generation files only for the number that is specified for the Stored Generation File Count. If the number of files reaches the value specified for the Stored Generation File Count, the data with the oldest Accumulation Date and Time of all the accumulated data with the same file ID (including undelivered data) is deleted in order to make room to store new data. |
| Limit to Number of Undelivered Generations | 2 | If the amount of undelivered data reaches the value specified for the Stored Generation File Count, the Accumulation processing is cancelled and an Accumulation error is given. The transfer data is not stored. |
| Defer to System Setting | 3 (default value) | This is dependent on the setting value for the Stored Generation File in the server's Accumulation environment settings. |
(B14) Stored Generation File Count
Specify this field when either 'Limit to Number of Stored Generations' (1) or 'Limit to Number of Undelivered Generations' (2) is set for the field that is described in "(B12) Stored Generation File."
Specify an integer from 1 to 9999.
This field specifies whether or not to prohibit overtaking of transfer data that has the same file ID.
The order for transfer data that is maintained when overtaking is prohibited is the order in which the Accumulation processing of the data started.
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| No | 0 | Overtaking is not prohibited. Although the order of transfer data may become reversed, the simultaneous processing of multiple transfers is allowed. |
| Yes | 1 | Overtaking is prohibited. The order of transfer data is maintained. |
| Defer to System Setting | 2 (default value) | This is dependent on the setting value for the Prohibiting Overtaking in the server's Accumulation environment settings. |
| [Note] | If another accumulation server exists within the same definition, you must configure the same settings for all servers. |
(B16) Handling of Send Request When Undelivered Data Does Not Exist
This field specifies the handling of the Send Request if undelivered accumulated data does not exist.
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Relay to Sending Side | 0 | Relay the Send Request to the host on the sending side. |
| Treat as Error | 1 | End the Send Request as an error. |
| Defer to System Setting | 2 (default value) | This is dependent on the setting value for the Handling of Send Request When Undelivered Data Does Not Exist in the server's Accumulation environment settings. |
3. Job Flow Setting
(C1) Post-accumulation Successful Job Flow ID
This field specifies the ID of the Job Flow that is started when the accumulation of data ends successful.
Specify a Job Flow ID that is defined on the server that accumulates data.
A Wait for Accumulation (Start Type) or Wait for Accumulation (Trigger Type) job step that is set to receive the accumulation completion notification from the relevant file ID must be defined in the Job Flow with the specified Job Flow ID. If there is no relevant Job Flow ID, an error occurs.
(C2) Post-accumulation Unsuccessful Job Flow ID
This field specifies the ID of the Job Flow that is started when the accumulation of data ends unsuccessful.
Specify a Job Flow ID that is defined on the server that accumulates data.
A Wait for Accumulation (Start Type) or Wait for Accumulation (Trigger Type) job step that is set to receive the accumulation completion notification from the relevant file ID must be defined in the Job Flow with the specified Job Flow ID. If there is no relevant Job Flow ID, an error occurs.
This field specifies the timing for sending the accumulation completion notification to the host on the sending side when the Job Flow starts.
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Accumulation Complete | 0 (default value) | Send notification of successful completion to the host on the sending side when accumulation occurs. |
| Job Flow Complete | 1 | Send notification of successful completion to the host on the sending side when the Job Flow is complete. |
4. Extension Settings
This field specifies a transfer interval for delivery of the accumulated data. (Unit: msec)
Request acknowledge port No. of sending side client
This field specifies the EBCDIC Set of the client on the receiving side.
Configurable values vary depending on the client version on the receiving side.
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Katakana V6.0~ | A | EBCDIC Katakana (*1) |
| Lower Case V6.0~ | B | EBCDIC Lower Case (*1) |
| ASCII V6.0~ | C | EBCDIC ASCII (*1) |
| ASPEN V6.0~ | D | EBCDIC ASPEN (*1) |
| Japan (Latin) for IBM V6.0~ | E | Japan (Latin) for IBM (*1) |
| Japan (Latin) Extended for IBM V6.0~ | F | Japan (Latin) Extended for IBM (*1) |
| NEC Katakana V6.0~ | G | NEC Katakana (*1) |
| Japan (Katakana) Extended for IBM V7.3~ | H | Japan (Katakana) Extended for IBM (*2) |
| User Table 1 V6.0~ | V | User Table 1 (*1) |
| User Table 2 V6.0~ | W | User Table 2 (*1) |
| User Table 3 V6.0~ | X | User Table 3 (*1) |
| Simplified Chinese Extended V8.1~ | I | Simplified Chinese Extended (*3) |
| Kana | 1 | EBCDIC Katakana (*4) |
| Lower Case | 2 | EBCDIC Lower Case (*4) |
| ASCII | 3 | EBCDIC ASCII (*4) |
| ASPEN | 4 | EBCDIC ASPEN (*4) |
| Japan (Latin) for IBM | 5 | Japan (Latin) for IBM (*4) |
| Japan (Latin) Extended for IBM | 6 | Japan (Latin) Extended for IBM (*4) (*5) |
| User Table 1 | 6 | User Table 1 (*4) (*6) |
| 7 | User Table 1 (*4) (*5) | |
| User Table 2 | 7 | User Table 2 (*4) (*6) |
| 8 | User Table 2 (*4) (*5) | |
| User Table 3 | 8 | User Table 3 (*4) (*6) |
| 9 | User Table 3 (*4) (*5) |
| *1: | This can be specified when the version of the client on the receiving side is Ver.6.0 or higher. |
| *2: | This can be specified when the version of the client on the receiving side is Ver.7.3 or higher. |
| *3: | This can be specified when the version of the client on the receiving side is Ver.8.1 or higher. |
| *4: | This can be specified when the version of the client on the receiving side is lower than Ver.6.0. |
| *5: | This can be specified when the client on the receiving side is HULFT for i5OS. |
| *6: | This can be specified when the client on the receiving side is not HULFT for i5OS. |
This field specifies the cipher key that is used during delivery of the accumulated data.
Specify the same string as the Cipher Key for the Send Management Information.
On the Collecting and Distributing System Management Information screen, Forced Strong Key Mode is displayed if the sending side is a server outside of control. The setting for the Forced Strong Key Mode on the sending client that is a client of the server outside of control cannot be acquired by HULFT-HUB Server. Therefore, the user specifies whether to enable or disable the Forced Strong Key Mode.
This field specifies the host type of the client on the receiving side.
This field is mandatory if HULFT Multicasting via HUB is used and the receiving client is HULFT Ver.8.4 or higher, and not used in other situations.
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Mainframe | H | Mainframe |
| Unix | U | UNIX |
| WindowsNT | N | Windows |
| AS/400 | A | AS/400 |
(D6) Receive Transfer Code Set
This field specifies the code set for transfer on the receiving client.
This field is mandatory if HULFT Multicasting via HUB is used and the receiving client is HULFT Ver.8.4 or higher, and not used in other situations.
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| SHIFT-JIS | S | SHIFT-JIS |
| EUC-JP | E | EUC-JP |
| JEF | J | JEF |
| IBM Kanji | I | IBM Kanji |
| UTF-8 | 8 | UTF-8 |
| GB18030 | G | GB18030 |
| IBM Simplified Chinese | C | IBM Simplified Chinese |