Send Management Information
This topic explains how to register the file information for the file to be sent.
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
| [Note] | 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, update, or newly register the management information for that client. |
List of Fields
1. Send Management Information
<Table> List of Fields for Send Management Information
| No. | Field Name | Default Value | Setting Value | Specification | Remarks | Transfer | Distribute |
|---|---|---|---|---|---|---|---|
| A1 | File ID | Alphanumeric characters and "_" *1 | Mandatory | Within 50 bytes | Outside the panel | ✓ | |
| A2 | Mainframe DSN | Alphanumeric characters | Mandatory | Within 44 bytes *2 | Basic Settings | ✓ | |
| A3 | Volume Serial | Alphanumeric characters | Optional | Within 6 bytes | Basic Settings | ✓ | |
| A4 | Work Volume Serial | Alphanumeric characters | Optional | Within 6 bytes | Basic Settings | ✓ | |
| A5 | Transfer Mode | Work File | *3 | Mandatory | Basic Settings | ✓ | |
| A6 | Transfer Type | TEXT | *3 | Mandatory | Basic Settings | ✓ | |
| A7 | Compression Preference | None | *3 | Mandatory | Basic Settings | ✓ | |
| A8 | Code Conversion | Sending Side | *3 | Mandatory | Basic Settings | ✓ | |
| A9 | Pre-send Job ID | Alphanumeric characters and "_" *1 | Optional | Within 50 bytes | Basic Settings | ✓ | |
| A10 | Successful Job ID | Alphanumeric characters and "_" *1 | Optional | Within 50 bytes | Basic Settings | ✓ | |
| A11 | Unsuccessful Job ID | Alphanumeric characters and "_" *1 | Optional | Within 50 bytes | Basic Settings | ✓ | |
| A12 | Format/Multi Format ID | Alphanumeric characters and "_" *1 | Optional | Within 50 bytes *4 | Basic Settings | ✓ | |
| A13 | Interface DBID | Alphanumeric characters | Optional | 3 bytes *4 | Basic Settings | ✓ | |
| A14 | Transfer Group ID | *5 | Alphanumeric characters and "_" *1 | Mandatory | Within 50 bytes | Outside the panel | ✓ |
| A15 | Comment | Half-width characters *6 | Optional | Within 60 bytes | Outside the panel | ✓ | |
| A16 | UNIT Quantity | 1 | From 1 to 59 | Mandatory | Extension Settings | ✓ | |
| A17 | Capacity | CYL | *3 | Mandatory | Extension Settings | ✓ | |
| A18 | 1ST Extent | 5 | From 1 to 9999 | *7 | Extension Settings | ✓ | |
| A19 | Secondary | 3 | From 0 to 9999 | *7 | Extension Settings | ✓ | |
| A20 | UNIT | Alphanumeric characters | Optional | Within 8 bytes | Extension Settings | ✓ | |
| A21 | Sequence Number | From 1 to 9999 | Optional | Extension Settings | ✓ | ||
| A22 | Transfer Interval | 0 | From 0 to 32768 | Mandatory | Unit: 10 msec | Extension Settings | ✓ |
| A23 | Transfer Block Length | 0 | 0, from 128 to 65520 | Mandatory | Unit: byte | Extension Settings | ✓ |
| A24 | Transfer Block Count | 0 | 0, from 1 to 99 | Mandatory | Extension Settings | ✓ | |
| A25 | Send File Mode | Keep | *3 | Mandatory | Extension Settings | ✓ | |
| A26 | Transfer Priority | 50 | From 1 to 256 | Mandatory | Extension Settings | ✓ | |
| A27 | EBCDIC Set | Autoconfiguration | *3 | Mandatory | Extension Settings | ✓ | |
| A28 | Subsequent Character | No Cut | *3 | Mandatory | Extension Settings | ✓ | |
| A29 | Shiftcode Mode | Cut | *3 | Mandatory | Extension Settings | ✓ | |
| A30 | Cipher Key | *8 | *8 | *8 | Extension Settings | ✓ | |
| A31 | Sending with RDW | No | *3 | Mandatory | Extension Settings | ✓ |
| *1: | If the Controlling Server is HULFT-HUB Server that is lower than Ver.3.10, you cannot use "_". |
| *2: | The length that you can specify varies depending on host type. For details, refer to Operation Manual for the client. |
| *3: | When you configure settings on the screen, select an option from the list that is shown on the screen. |
| *4: | You can configure this setting when you select 'FORMAT' (F) or 'MULTIFORMAT' (M) for the Transfer Type. |
| *5: | When you register a Transfer definition in HULFT-HUB Manager, the field is automatically set. |
| *6: | You cannot specify lowercase alphabetic characters. |
| *7: | This field is optional if you have selected 'OMIT' (A) for the Capacity. |
| *8: | The value that can be specified for Cipher Key differs depending on the value specified for Forced Strong Key Mode in the System Environment Settings of the client. |
| - Forced Strong Key Mode is "Disabled": 8 to 20 alphanumeric characters (Optional). | |
| - Forced Strong Key Mode is "Enabled": 64-character hexadecimal text string (0-9, A-F) (Mandatory). |
2. Additional information other than Send Management Information
You can view both the Send Management Information and the following additional information on each screen where you edit Transfer definitions.
<Table> List of Fields for Additional Information other than Send Management Information
| No. | Field Name | Default Value | Setting Value | Specification | Remarks | Transfer | Distribute |
|---|---|---|---|---|---|---|---|
| B1 | Host Name | Alphanumeric characters | *1 | Outside the panel | - | ||
| B2 | File Alias *2 | Alphanumeric characters | Optional | Within 256 bytes | Outside the panel | ✓ | |
| B3 | Batch Distribution ID | Alphanumeric characters | *1 | - | ✓ | ||
| B4 | Business Group ID | *2 | Mandatory | - | ✓ |
| *1: | You are allowed only to view this field on the screen. |
| *2: | This information is shown as 'Alias' on the Collecting and Distributing System Management Information screen. |
| *3: | When you configure settings on the screen, select an option from the list that is shown on the 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 |
| 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 Send Management 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. Send Management Information
This field specifies the ID to identify the file to be sent.
| [Note] | "_INSTANT_TRANSFER_" cannot be specified in File ID. "_INSTANT_TRANSFER_" is a file ID exclusively for Instant Transfer. |
This field specifies the data set name for the file to be sent, which is stored on Mainframe.
Specify this field according to the naming rules for data set names for Mainframe.
If you specify a Partitioned Organization file, specify the member name in parentheses.
If you specify a generation file, specify the relative generation number in parentheses.
Do not enclose the file names within single quotation marks (').
| [Note] | There is a slight difference in the types of data sets that you can specify based on the host type used. For details, refer to Operation Manual for the client. |
This field specifies the serial number of the volume where the Send file is stored.
Specify this field according to the naming rules for the volume serial number for Mainframe.
If you omit the Volume Serial, HULFT will treat the file as cataloged.
| [Note] | There is a slight difference in specification method based on the types of data sets and the host type used. For details, refer to Operation Manual for the client. |
This field specifies the volume serial number for the Send work file.
Specify this field according to the naming rules for the volume serial number for Mainframe.
If you omit this field, the location where HULFT creates the work file differs according to the Work Volume Mode (WORKVOLMODE) in the System Environment Settings. For details about the Work Volume Mode, refer to Administration Manual for the client.
| [Note] | You cannot view or update the System Environment of HULFT for Mainframe in HULFT-HUB Manager. Confirm the settings on the client. |
This field specifies the transfer mode when HULFT transmits the Send file.
<Table> Setting Values for Transfer Mode
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Direct | D | Directly transfer the Send file without creating a work file |
| Work File | W | Create a work file based on the Send file, and transfer the work file |
This field specifies the transfer data format for the file to be sent.
<Table> Setting Values for Transfer Type
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| FORMAT | F | Format data |
| BINARY | B | Binary data |
| TEXT | T | Text data |
| MULTIFORMAT | M | Multi format data |
This field specifies the compression preference when the file is transferred.
<Table> Setting Values for Compression Preference
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| None | N | No compression |
| Horizontal | 1 | Compression within each record |
| Vertical | 2 | Compression across records |
| DEFLATE | 3 | DEFLATE compression |
This field specifies the host that carries out code conversion for the file to be sent.
<Table> Setting Values for Code Conversion
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Sending Side | S | Sending side conversion |
| Receiving Side | R | Receiving side conversion |
| No Conversion | N | No conversion |
This field specifies the ID of the job that HULFT starts before the Send processing is carried out.
For details about the Job ID, refer to Job Information.
If you omit this field, HULFT does not start the job.
This field specifies the ID of the job that HULFT starts when the sending of the file ends successfully.
For details about the Job ID, refer to Job Information.
If you omit this field, HULFT does not start the job.
This field specifies the ID of the job that HULFT starts when the sending of the file ends unsuccessfully.
For details about the Job ID, refer to Job Information.
If you omit this field, HULFT does not start the job.
This field specifies the registered ID for format or multi format of the file to be sent.
For details about the Format ID, refer to Format Information.
For details about the Multi Format ID, refer to Multi Format Information.
If the Transfer Type is 'FORMAT' (F), the format ID is required; if the Transfer Type is 'MULTIFORMAT' (M), the multi format ID is required.
This field specifies the interface on the host on the receiving side for sending data.
| - CSV: | Carry out CSV conversion of the Receive file on the host on the receiving side |
To receive the file in CSV format on the host on the receiving side (UNIX, Linux, Nonstop, Windows), specify 'CSV.'
If you omit this field, HULFT does not carry out receiving in CSV format.
To interface, select 'FORMAT' (F) or 'MULTIFORMAT' (M) for the Transfer Type.
This field specifies the ID for which the sending destination host for the file to be sent is registered.
For details about the Transfer Group ID, refer to Transfer Group Information.
| [Note] | For Transfer definitions that are registered on the Transfer Information screen in HULFT-HUB Manager, HULFT-HUB automatically selects as default values the transfer group IDs (for transfer groups that are registered on the client side) that include the host on the receiving side that is selected in the transfer map. If there is no relevant transfer group ID, HULFT-HUB automatically sets an 8-character transfer group ID that starts with 'HB.' |
This field specifies the comment regarding the file to be sent.
This field specifies the unit quantity for the Send work file when you use multiple volumes.
If you set '2' or more, you cannot specify the Work Volume Serial.
This field specifies the units of space for the Send work file.
<Table> Setting Values for Capacity
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| CYL | C (default value) | Cylinder |
| TRK | T | Track |
| OMIT | A | Omitted (Auto Calculation) |
If you select 'OMIT' (A), HULFT automatically calculates the values for the Capacity, the 1ST Extent, and the Secondary of the Send work file from the capacity of the Send file.
HULFT carries out the auto calculation of the capacity based on the attributes of the Send file, and therefore auto calculation is not possible if the Send file is created in a unit of capacity other than tracks or cylinders, or is a VSAM file.
In addition, note that capacity may become insufficient during the creation of a work file in the following cases:
-
For Partitioned Organization files
HULFT calculates the capacity of the work file based on the total size of the Partitioned Organization file.
-
When the device types for the Send file and for the work file are different
HULFT calculates the capacity based on the allocated capacity for the Send file.
This field specifies the primary space amount for the Send work file.
If you select 'CYL' (C) or 'TRK' (T) for the Capacity, be sure to specify this field.
This field specifies the incremental amount for the Send work file.
If you select 'CYL' (C) or 'TRK' (T) for the Capacity, be sure to specify this field.
This field specifies the name of the unit where the Send file is stored.
If you omit this field, HULFT will use the unit name that you specified for the Unit Group Name of Send and Receive File (INIT-UNIT) in the System Environment Settings.
In addition, if you omit the specification for the Volume Serial, HULFT acquires the unit name from the catalog and ignores the specified unit name and the Unit Group Name of Send and Receive File (INIT-UNIT) in the System Environment Settings.
| [Note] | You cannot view or update the System Environment of HULFT for Mainframe in HULFT-HUB Manager. Confirm the settings on the client. |
This field specifies the sequence number on the tape device volume where the Send file is stored.
If you omit the Sequence Number and send data from a tape volume, HULFT will send the data for sequence number 1.
This field specifies the interval from the end of the transfer of one block (Transfer Block Length) to the transfer of the next block.
This allows files to be transferred without monopolizing the network (intermittent transfer).
This field specifies the length of one block for transfer.
You cannot set this value so that the product of the Transfer Block Length and the Transfer Block Count exceeds '65520.'
This field specifies the number of blocks per transfer.
You cannot set this value so that the product of the Transfer Block Length and the Transfer Block Count exceeds '65520.'
This field specifies whether to apply the exclusive control during sending of the Send file, and the processing when the sending of the file ends successfully.
<Table> Setting Values for Send File Mode
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Keep | K | Do not lock during sending or when creating the Send work file, and save the file after the processing ends successfully |
| Clear | C | Lock during sending or when creating the Send work file, and make the file a 0-byte file after the processing ends successfully |
| Delete | D | Lock during sending or when creating the Send work file, and delete the file after the processing ends successfully |
| Lock | L | Lock during sending or when creating the Send work file, and save the file after the processing ends successfully |
<Table> Relationship between Send File Mode and Transfer Mode
| Direct Transfer | Work File Transfer | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| During Sending | After Completion | Remarks | *1 | Work File | During Sending | After Completion | Remarks | |||
| During Creation | After Creation | |||||||||
|
Send File Mode
|
Keep | Not lock |
Keep (Not delete) |
|
- | Not lock | - | Not lock |
Keep (Not delete) |
|
| Clear | Lock |
Make the file a 0-byte file
|
*2 | B | Lock |
Make the file a 0-byte file
|
- | - | *2 | |
| A | Lock | - | Lock |
Make the file a 0-byte file
|
||||||
| Delete | Lock | Delete | *3 | B | Lock | Delete | - | - | *3 | |
| A | Lock | - | Lock | Delete | ||||||
| Lock | Lock |
Keep (Not delete) |
- | Lock | - | Lock |
Keep (Not delete) |
|||
| *1: | Specification for the Post-send Clear Mode (CLEARMODE) in the System Environment Settings |
| B: Clear or delete the Send file after creating the Send work file | |
| A: Clear or delete the Send file after the successful end of the Send processing | |
| *2: | If you specify the Successful Job ID, HULFT makes the file a 0-byte file before it starts the job. |
| *3: | If you specify the Successful Job ID, HULFT deletes the file before it starts the job. |
If you select 'Clear' (C) or 'Delete' (D) for the Work File Transfer, HULFT behaves differently depending on the Post-send Clear Mode in the System Environment Settings. If you set the Post-send Clear Mode to 'B,' HULFT deletes the Send file and all records after it creates the Send work file, regardless of whether the Send processing is successful or unsuccessful. If you set the Post-send Clear Mode to 'A,' HULFT deletes the Send file and all records after the Send processing ends successfully.
If you set anything other than 'Keep' (K) for the Send File Mode, HULFT cannot carry out multicasting that transmits from HULFT on the sending side to all transfer destinations (client-side multicasting function).
However, if for the Work File Transfer you set 'B' for the Post-send Clear Mode and 'Clear' (C) or 'Delete' (D) for the Send File Mode, it is possible to carry out multicasting that is not via HULFT-HUB Server (Peer to Peer).
| [Note] | |
| - | If the Send file is VSAM or Partitioned Organization, you cannot specify 'Clear' (C) or 'Delete' (D). |
| - | For sending side conversion during the Work File Transfer, EBCDIC-EBCDIC conversion is not possible. |
| - | You cannot view or update the System Environment of HULFT for Mainframe in HULFT-HUB Manager. Confirm the settings on the client. |
This field specifies the priority in the queue for transferring files.
Greater priority is given to smaller numeric values.
If there is more than one transfer processing in the queue, you can start the Send processing for the file you want to send first by setting a lower value for the transfer priority.
If you omit this specification in the CSV file for Collecting and Distributing System Management Information, HULFT-HUB sets '50.'
This field specifies the EBCDIC code system (encoding code scheme) that is used for single byte code conversion.
<Table> Setting Values for EBCDIC Set
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Autoconfiguration | 0 (default value) | Autoconfiguration |
| Katakana | A | EBCDIC Katakana |
| Lower Case | B | EBCDIC Lower Case |
| ASCII | C | EBCDIC ASCII |
| ASPEN | D | EBCDIC ASPEN |
| Japan (Latin) for IBM | E | Japan (Latin) for IBM |
| Japan (Latin) Extended for IBM | F | Japan (Latin) Extended for IBM |
| NEC Katakana | G | NEC Katakana |
| Japan (Katakana) Extended for IBM | H | Japan (Katakana) Extended for IBM |
| User Table 1 | V | User Table 1 |
| User Table 2 | W | User Table 2 |
| User Table 3 | X | User Table 3 |
| [Remarks] |
'ASPEN' (D) and 'NEC Katakana' (G) are not recommended. If you specify 'ASPEN' (D) or 'NEC Katakana' (G), the files may not be converted. Use a different code set. |
This field specifies how HULFT handles trailing spaces and NULLs (X'00') in the file to be sent.
<Table> Setting Values for Subsequent Character
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Null Cut | 0 | Cut trailing NULLs |
| Space Cut | S | Cut trailing spaces |
| Both | A | Cut trailing spaces and NULLs |
| No Cut | N | Do not cut trailing spaces or NULLs |
You can select only 'No Cut' (N) if you selected 'BINARY' (B), 'FORMAT' (F), or 'MULTIFORMAT' (M) for the Transfer Type.
This field specifies how to handle shift codes when HULFT carries out Code Conversion for a code set that does not use shift codes.
<Table> Setting Values for Shiftcode Mode When Kanji Code Type is 'IBM Kanji'
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Cut | C | Delete shift codes and convert the data |
| Space | S | Replace shift codes with spaces |
This field specifies the key for encrypting data.
Security is applied to the file to be sent. Set the same cipher key that has been set in the Receive Management Information on the remote host.
This field specifies whether to add a Record Descriptor Word (RDW) for each variable-length record when data is sent.
<Table> Setting Values for Sending with RDW
| On-screen Options |
Values in CSV File |
Description |
|---|---|---|
| Yes | Y | Add RDW and send |
| No | N | Send without adding RDW |
| [Note] | You cannot specify this field if you set anything other than 'BINARY' (B) for the Transfer Type. |
2. Additional information other than Send Management Information
This additional information is displayed together with the Send Management Information on each screen where you edit Transfer definitions. You can view and modify each field on screens in HULFT-HUB Manager.
| [Note] | You cannot view this additional information on the Management screen on the client (HULFT) side. |
This field shows the host name of the client on which the Send Management Information is registered.
| [Remarks] | You can view this field only on the Transfer Information screen (cannot be modified). |
This field specifies the alias for the file to be sent.
It is recommended that you assign a unique name in the Send Management Information so that each file ID that is displayed on screens in HULFT-HUB Manager can be easily identified.
| [Remarks] | This information is shown as 'Alias' on the Collecting and Distributing System Management Information screen. |
This field shows the Batch Distribution Information ID with which the Send Management Information is registered as distribution data.
| [Remarks] | You can view this field on the Collecting and Distributing System Management Information screen (cannot be modified). |
This field specifies the Business Group ID that uses this Send Management Information.
| [Remarks] | You can view this field on the Collecting and Distributing System Management Information screen. |
Points to be Noted When Configuring Settings
1. Replacement message
You can replace variables with the messages that you specify when issuing the Send Request on the host on the receiving side, or with the messages that are specified when issuing the Send File, by specifying variables from '&MSG0' to '&MSG5' or from '&MSGL0' to '&MSGL1' in the following fields (Message Transmission function):
- Mainframe DSN
- Volume Serial
- Work Volume Serial
- Pre-send Job ID
- Successful Job ID
- Format ID
- Multi Format ID
- UNIT
- Transfer Group ID
| [Note] | |
| - | You can edit the Transfer Group ID only on the Collecting and Distributing System Management Information screen. On the Transfer Information screen, you can select only an ID that has been set automatically by HULFT-HUB Manager or an existing transfer group ID, and therefore you cannot carry out replacement with message. |
| - | For details about the Message Transmission function, refer to Administration Manual for the client. |
| - | Depending on the language settings on the remote host, replacement with message may not be carried out correctly and transfer may fail. For details, refer to Administration Manual. |
| - | You can use '&' instead of '$' as the first character of environment variables. The hexadecimal code for '$' is 0xE0. |
2. Transfer Block Length and Transfer Block Count
If you set '0' for both the Transfer Block Length and the Transfer Block Count, HULFT system automatically sets the size of the transfer unit (the product of the Transfer Block Length and the Transfer Block Count).
However, if you specify '0' for only the Transfer Block Length or for only the Transfer Block Count, an error occurs.
For details, refer to Administration Manual for the client.
3. Code Conversion
If the sending side client and receiving side client are both running HULFT Ver. 8.4 or higher, even if the user specifies "Sending Side" (S) in Code Conversion, receiving side conversion might switch automatically. In addition, even if "Receiving Side" (R) is specified in Code Conversion, sending side conversion might switch automatically. This is called "automatic switching of sending side conversion and receiving side conversion". For details, refer to the explanation for sending side conversion and receiving side conversion in the client Code Conversion Manual.
However, for transfers performed via HULFT-HUB Server Ver.3.8, automatic switching of code conversion does not function.
4. Automatic Setting of EBCDIC Set
If you specify 'Autoconfiguration' (0) for the EBCDIC Set, the type of EBCDIC that is actually used depends on the combination of the Kanji Code Type that is set in the Registered Client Information on both the client on the sending side and the client on the receiving side, as shown below.
<Table> Values When EBCDIC Set is Set to 'Autoconfiguration' (0)
| Kanji Code Type of Sending Client | Kanji Code Type of Receiving Client | EBCDIC to Be Used |
|---|---|---|
| IBM Kanji | Optional | Japan (Latin) Extended for IBM (F) |