Accumulation Environment Settings
This topic explains how to register the information that is required to accumulate the transferred data in HULFT-HUB Server.
You can view and modify this information on the Management screen.
List of Fields
1. Server
<Table> Accumulation Environment Settings for Server
| No. | Field Name | Default Value | Setting Value | Specification | Remarks | |
|---|---|---|---|---|---|---|
| A1 | Accumulation Block Threshold | 100.0 | From 1.0 to 999,999.9 | Mandatory | ||
| A2 | Unit of Accumulation Block Threshold | MB | MB, GB, TB | Mandatory | ||
| A3 | Accumulated Data Deletion Threshold check box | Off | On or Off | Mandatory | ||
| A4 | Accumulated Data Deletion Threshold | 0.0 | From 1.0 to 999,999.9 | Mandatory | ||
| A5 | Unit of Accumulated Data Deletion Threshold | MB | MB, GB, TB | Mandatory | ||
| A6 | Accumulation Condition | Accumulate Only When Unable to Transfer | *1 | Mandatory | ||
| A7 | Continuation Condition | Continue to Transfer and Accumulate when Error Occurs | *1 | Mandatory | ||
| A8 | Accumulated File Deletion Condition | Delete Immediately after Transfer or Delivery is Complete | *1 | Mandatory | ||
| A9 | Storage Expiration Date | Period | *1 | Mandatory | ||
| A10 | Period | Number | 1 |
days: From 0 to 999 weeks: From 1 to 99 months: From 1 to 99 |
Mandatory | |
| A11 | Unit | weeks | days, weeks, months | Mandatory | ||
| A12 | Every Week | Day of the Week | Sun | Sun, Mon, Tue, Wed, Thu, Fri, Sat | Mandatory | |
| A13 | Every Month | Day | 1 | From 1 to 31, End | Mandatory | |
| A14 | week | 1st | 1st, 2nd, 3rd, 4th, Final | Mandatory | ||
| A15 | Day of the Week | Sun | Sun, Mon, Tue, Wed, Thu, Fri, Sat | Mandatory | ||
| A16 | Expiration Check Time | 00:00 | From 00:00 to 23:59 | Mandatory | Set in HH:MM format | |
| A17 | Transfer Result Notification to Sending Side When Accumulation is Complete | Always Return as Transfer Complete | *1 | Mandatory | ||
| A18 | Verify Data | No | *1 | Mandatory | ||
| A19 | Stored Generation File | No Generation File | *1 | Mandatory | ||
| A20 | Stored Generation File Count | Mandatory | ||||
| A21 | When a Client is Reinstated | Do Not Deliver Automatically | *1 | Mandatory | ||
| A22 | When Client Startup is Detected | Do Not Deliver Automatically | *1 | Mandatory | ||
| A23 | Prohibiting Overtaking | No | *1 | Mandatory | ||
| A24 | Handling of Send Request When Undelivered Data Does Not Exist | Relay to Sending Side | *1 | Mandatory | ||
*1: Select an option from the list that is shown on the screen.
2. Host
<Table> Accumulation Environment Settings for Host
| No. | Field Name | Default Value | Setting Value | Specification | Remarks |
|---|---|---|---|---|---|
| B1 | Capacity Settings check box | Off | On or Off | Mandatory | |
| B2 | Accumulation Block Threshold | 0.0 | From 1.0 to 999,999.9 | Mandatory | |
| B3 | Unit of Accumulation Block Threshold | MB | MB, GB, TB | Mandatory | |
| B4 | Accumulated Data Deletion Threshold check box | Off | On or Off | Mandatory | |
| B5 | Accumulated Data Deletion Threshold | 0.0 | From 1.0 to 999,999.9 | Optional | |
| B6 | Unit of Accumulated Data Deletion Threshold | MB | MB, GB, TB | Optional | |
| B7 | Max. Capacity for Accumulation | 0.0 | 0.0, from 1.0 to 999,999.9 | Mandatory | |
| B8 | Unit of Max. Capacity for Accumulation | MB | MB, GB, TB | Mandatory | |
| B9 | When a Client is Reinstated | Do Not Deliver Automatically | *1 | Mandatory | |
| B10 | When Client Startup is Detected | Do Not Deliver Automatically | *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 the server |
| Specification | Whether the specification is mandatory or optional when you update the management information record on a screen |
Explanation of Each Field
1. Server
(A1) Accumulation Block Threshold
This field specifies the maximum accumulation capacity for the entire HULFT-HUB Server.
If the accumulation capacity exceeds the setting value after accumulation is complete, accumulation is blocked.
If another accumulation is executed while accumulation is blocked, an error occurs.
(A2) Unit of Accumulation Block Threshold
This field specifies the unit for the Accumulation Block Threshold.
(A3) Accumulated Data Deletion Threshold check box
This sets whether to specify the Accumulated Data Deletion Threshold.
Turn this function on/off to specify whether to automatically delete data according to the accumulated data capacity. Turn this function on when you specify an Accumulated Data Deletion Threshold.
<Table> Setting Values for the Accumulated Data Deletion Threshold check box
| On-screen Options |
Description |
|---|---|
| The check box is not selected | HUB dose not automatically delete data according to the accumulated data capacity. |
| The check box is selected | HUB automatically delete data according to the accumulated data capacity. |
(A4) Accumulated Data Deletion Threshold.
This field specifies the maximum accumulation capacity for entire HULFT-HUB Server.
You cannot specify a value that exceeds the accumulation block threshold.
If the accumulation would result in the total size of accumulated data exceeding the accumulated data deletion threshold, older accumulated data is deleted to make room for the accumulation of new data. For details about older accumulated data, refer to the explanation of the management of accumulated data capacity in HULFT-HUB Manual.
(A5) Unit of Accumulated Data Deletion Threshold
This field specifies the unit for the accumulated data deletion threshold.
This field specifies whether or not the server accumulates transfer data during transfer.
<Table> Setting Values for Accumulation Condition
| On-screen Options |
Description |
|---|---|
| Never Accumulate | Data is never accumulated regardless of whether the transfer processing is successful or unsuccessful. |
| Accumulate Only When Unable to Transfer | 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 | Accumulation and transfer of data start simultaneously. |
| Deliver after Accumulation | Data is transferred after the accumulation of transferred data completes successfully. |
This field specifies the continuation or cancellation of processing if an error occurs during transfer or accumulation.
<Table> Setting Values for Continuation Condition
| On-screen Options |
Description |
|---|---|
| Continue to Transfer and Accumulate when Error Occurs | 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 | If an error occurs during transfer, the transfer processing is cancelled. The Accumulation processing continues. |
| Continue to Transfer when Accumulation Error Occurs | If an error occurs during accumulation, the Accumulation processing is cancelled. The transfer processing continues. |
| Cancel Transfer and Accumulation when Error Occurs | If an error occurs during transfer or accumulation, both the transfer processing and the Accumulation processing are cancelled. |
(A8) Accumulated File Deletion Condition
This field specifies the timing for the deletion of the accumulated or delivered data.
<Table> Setting Values for Accumulated File Deletion Condition
| On-screen Options |
Description |
|---|---|
| Do Not Delete | The data will not be automatically deleted. You must delete the data manually. |
| Delete Immediately after Transfer or Delivery is Complete | Accumulated data is deleted after delivery completes successfully. |
| Delete when Specified Period has Elapsed after Accumulation is Complete | 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 | 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. |
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' or 'Delete when Specified Period has Elapsed after Delivery is Complete.'
For details about the storage period, refer to HULFT-HUB Manual.
<Table> Setting Values for Storage Expiration Date
| 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. |
Specify this field when the Storage Expiration Date is set as 'Period.'
Specify the period to store data in combination with the setting that is described in "(A10) 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.
Specify this field when the Storage Expiration Date is set as 'Period.'
Specify the period to store data in combination with the setting that is described in "(A9) Period_Number."
<Table> Setting Values for Period_Unit
| On-screen Options |
Description |
|---|---|
| days | Specify the storage period in days |
| weeks | Specify the storage period in weeks |
| months | Specify the storage period in months |
(A12) 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.
<Table> Setting Values for Every Week_(Day of the Week)
| 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 |
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.
| - From 1 to 31 | Delete the data on the specified day. | |
| - End | Delete the data on the last day of the month. |
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 "(A14) Every Month_(Day of the Week)" to delete data for which the storage expiration date has passed.
<Table> Setting Values for Every Month_week
| 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 |
(A15) 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 "(A13) Every Month_week" to delete data for which the storage expiration date has passed.
<Table> Setting Values for Every Month_(Day of the Week)
| 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 |
This field specifies the time for checking the storage expiration date for the accumulated or delivered data.
(A17) 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,' 'Transfer and Accumulate Concurrently,' or 'Deliver after Accumulation.'
<Table> Setting Values for Transfer Result Notification to Sending Side When Accumulation Is Complete
| On-screen Options |
Description |
|---|---|
| Always Return as Transfer Complete | 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 | 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. |
This field specifies whether or not to verify data.
Data verification is a function that generates a hash value from the sending data during transfer and compares that hash value with the hash value that is generated from the receiving data to check the integrity of the transfer data.
<Table> Setting Values for Verify Data
| On-screen Options |
Description |
|---|---|
| No | Do not verify data when the relevant server accumulates data. |
| Yes | Verify data when the relevant server accumulates data. |
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.
<Table> Setting Values for Stored Generation File
| On-screen Options |
Description |
|---|---|
| No Generation File | Do not create generation files based on the Stored Generation File Count. |
| Limit to Number of Stored Generations | 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 | 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. |
(A20) Stored Generation File Count
This field specifies the maximum number of generations when the Stored Generation File is other than 'No Generation File.'
(A21) When a Client is Reinstated
This field shows whether or not the server automatically issues the Deliver Request when a delivery destination client is reinstated.
<Table> Setting Values for When a Client is Reinstated
| On-screen Options |
Description |
|---|---|
| Deliver Automatically | The server issues the Deliver Request when the client is reinstated. |
| Do Not Deliver Automatically | The server does not issue the Deliver Request even if the client is reinstated. |
(A22) When Client Startup is Detected
This field shows whether or not the server automatically issues the Deliver Request when the server detects that the status of a delivery destination client has changed from not operating to operating.
<Table> Setting Values for When Client Startup is Detected
| On-screen Options |
Description |
|---|---|
| Deliver Automatically | The server issues the Deliver Request when the server detects startup of the client. |
| Do Not Deliver Automatically | The server does not issue the Deliver Request even if the server detects startup of the client. |
This field specifies whether or not to prohibit overtaking of transfer data.
<Table> Setting Values for Prohibiting Overtaking
| On-screen Options |
Description |
|---|---|
| No | Overtaking is not prohibited. Although the order of transfer data may become reversed, the simultaneous processing of multiple transfers is allowed. |
| Yes | Overtaking is prohibited. The order of transfer data is maintained. |
(A24) 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.
<Table> Setting Values for Handling of Send Request When Undelivered Data Does Not Exist
| On-screen Options |
Description |
|---|---|
| Relay to Sending Side | Relay the Send Request to the host on the sending side. |
| Treat as Error | End the Send Request as an error. |
2. Host
(B1) Capacity Settings check box
Specify whether to set the following fields for each host.
- Accumulation Block Threshold
- Max. Capacity for Accumulation
- Accumulated Data Deletion Threshold
If each feald is not specified, capacity management is not performed for each host.
<Table> Setting Values for the Capacity Settings check box
| On-screen Options |
Description |
|---|---|
| The check box is not selected | Do not specify the Capacity Setting for each host. |
| The check box is selected | Specify the Capacity Setting for each host. |
(B2) Accumulation Block Threshold
This field specifies the maximum accumulation capacity for each host on the sending side.
If the accumulation capacity exceeds the setting value for this field after accumulation is complete, accumulation is blocked.
If another accumulation is executed while accumulation is blocked, an error occurs.
A value which exceeds Accumulation Block Threshold for the server cannot be specified.
(B3) Unit of Accumulation Block Threshold
This field specifies the unit for the Accumulation Block Threshold.
(B4) Accumulated Data Deletion Threshold check box
This field specifies the Accumulated Data Deletion Threshold for each host.
Turn this function on/off to specify whether to automatically delete data according to the accumulated data capacity for each host. Turn this function on when you specify an Accumulated Data Deletion Threshold for each host.
<Table> Setting Values for the Accumulated Data Deletion Threshold check box
| On-screen Options |
Description |
|---|---|
| The check box is not selected | HUB does not automatically delete data according to the accumulated data capacity of each host. |
| The check box is selected | HUB automatically deletes data according to the accumulated data capacity of each host. |
(B5) Accumulated Data Deletion Threshold
This field specifies the maximum accumulation capacity for each host on the sending side.
If the accumulation would result in the total size of accumulated data exceeding the accumulated data deletion threshold, older accumulated data is deleted to make room for the accumulation of new data.
A value which exceeds Accumulation Block Threshold for each send host cannot be specified.
(B6) Unit of Accumulated Data Deletion Threshold
This field specifies the unit for the accumulated data deletion threshold.
(B7) Max. Capacity for Accumulation
This field specifies the byte count that can be accumulated in a single processing for each host on the sending side.
If the accumulation would result in the total size of the accumulated data exceeding the maximum capacity for accumulation, an error occurs. If you specify '0.0' for this field, the Max. Capacity for Accumulation limitation is not applied.
(B8) Unit of Max. Capacity for Accumulation
This field specifies the unit for the Max. Capacity for Accumulation.
(B9) When a Client is Reinstated
This field shows whether or not the server automatically issues the Deliver Request when a delivery destination client is reinstated.
<Table> Setting Values for When a Client is Reinstated
| On-screen Options |
Description |
|---|---|
| Defer to System Setting | Defer to the setting of the When a Client is Reinstated for the server that accumulates the data. |
| Deliver Automatically | The server issues the Deliver Request when the client is reinstated. |
| Do Not Deliver Automatically | The server does not issue the Deliver Request even if the client is reinstated. |
(B10) When Client Startup is Detected
This field shows whether or not the server automatically issues the Deliver Request when the server detects that the status of a delivery destination client has changed from not operating to operating.
<Table> Setting Values for When Client Startup is Detected
| On-screen Options |
Description |
|---|---|
| Defer to System Setting | Defer to the setting of the When Client Startup is Detected for the server that accumulates the data. |
| Deliver Automatically | The server issues the Deliver Request when the server detects startup of the client. |
| Do Not Deliver Automatically | The server does not issue the Deliver Request even if the server detects startup of the client. |