List of Send Management Information fields

Basic Settings

Mainframe DSN

Data set name (DSN) of file to send (called Send file, or send target file) that is stored on a mainframe

Specify according to the data set naming conventions for Mainframe.

Transfer Type

Data type of the file to send

FORMAT:

Format data

BINARY:

Binary data

TEXT:

Text data

MULTIFORMAT:

Multi Format data

Format/Multi Format ID

Registered ID to represent the format or multi format of the file to send

For details on format IDs, refer to List of Format Information fields.

For details on multi format IDs, refer to List of Multi Format Information fields.

If Transfer Type is 'FORMAT,' specify the format ID.

If Transfer Type is 'MULTIFORMAT,' specify the multi format ID.

Compression Preference

Compression type that is used when a file is transferred

None:

No compression

Horizontal:

Compression within records

Vertical:

Compression across records

Code Conversion

Specify the option for code conversion of the send target file

Sending Side:

Sending side

Receiving Side:

Receiving side

No Conversion:

No conversion

EBCDIC Set

Specify Type-EBCDIC Code Set that is used for conversion of single-byte codes on the host on the sending side

• Autoconfiguration

• Katakana

• Lower Case

• ASCII

• ASPEN

• Japan (Latin) for IBM

• Japan (Latin) Extended for IBM

• NEC Katakana

• Japan (Katakana) Extended for IBM

• User Table 1

• User Table 2

• User Table 3

Omitting this field sets 'Autoconfiguration.'

This setting is valid when the host on the receiving side is a Type MF-IBMi host and when you specify sending-side conversion.

Send File Mode

Specify the mode for exclusive control of the Send file applied during the sending, and the handling of the file in the case where the sending ends successfully.

Keep:

Do not lock the file while sending is in progress and save the file after sending ends successfully.

Clear:

Lock the file while sending is in progress and clear the file to 0 byte after sending ends successfully

Delete:

Lock the file while sending is in progress and delete the file after sending ends successfully

Lock:

Lock the file while sending is in progress and save the file after sending ends successfully

Omitting this field sets 'Keep.'

Volume Serial

Serial number of the volume that stores the Send file

Specify according to the volume serial number naming conventions for Mainframe.

Transfer Mode

Transfer mode that HULFT uses when it sends the Send file

Direct:

Directly transfer the Send file without creating a work file

Work File:

Create a work file from the Send file, and then transfer the Send file

Omitting this field sets 'Work File.'

Work Volume Serial

Volume serial number of the Send work file

Specify according to the volume serial number naming conventions for Mainframe.

Capacity

Space unit for the Send work file

CYL:

Cylinder

TRK:

Track

OMIT:

Omitted (automatically calculated)

Omitting this field sets 'CYL.'

1ST Extent

First extent for the Send work file

Omitting this field sets '5.'

Secondary

Secondary extent for the Send work file

Omitting this field sets '3.'

UNIT Quantity

Multiple volume unit quantity for the Send work file

Omitting this field sets '1.'

Transfer Group ID

ID of the record in which the send destinations of the Send file are registered

For details on transfer group IDs, refer to List of Transfer Group Information fields.

Pre-send Job ID

ID of the job to be executed before the Send processing starts

For details on job IDs, refer to List of Job Information fields.

When this field is omitted, the job is not started.

Successful Job ID

ID of the job to be started when the Send processing ends successfully

For details on job IDs, refer to List of Job Information fields.

When this field is omitted, the job is not started.

Unsuccessful Job ID

ID of the job to be started when the Send processing ends unsuccessfully

For details on job IDs, refer to List of Job Information fields.

When this field is omitted, the job is not started.

Extension Settings

Interface DBID

Format of sent data used as interface on the receiving side

CSV:

Convert the Receive file into CSV format on the host on the receiving side

To receive the Receive file in CSV format on the host on the receiving side (for UNIX, Linux, NonStop, or Windows), specify "CSV".

When you omit this field, files will not be received in CSV format.

When you use the Interface function, specify 'FORMAT (F)' or 'MULTIFORMAT (M)' for Transfer Type (TRANSTYPE).

Transfer Interval

Interval between when HULFT has finished transferring a block and when HULFT begins transferring the next block

Omitting this field sets '0.'

Transfer Priority

Priority in queue when starting the file transfer

A smaller number means a higher priority. Omitting this field sets '50.'

Transfer Block Length

Length of data used to transfer one block

The product of the values for Transfer Block Length and Transfer Block Count cannot exceed 65520. Omitting this field sets '0.'

Transfer Block Count

Number of blocks per transfer

The product of the values for Transfer Block Length and Transfer Block Count cannot exceed 65520. Omitting this field sets '0.'

Shiftcode Mode

How HULFT handles shift codes when HULFT sends data to a host

C (Cut):

Convert to the shortened data by removing shift codes

S (Space):

Convert shift codes into space codes

Y (Add):

Add shift codes

N (Do not add):

Do not add shift codes

Values that can be specified and values that are set when this field is defaulted vary depending on the host type of the destination host and the setting of Code Set for Transfer (CS4TRNSFR) in the System Environment Settings on the destination host.

Host Type	Setting of Code Set for Transfer	Values That Can Be Specified	Value That Is Set When the Field Is Defaulted
HULFT for zOS	I (IBM Kanji)	C (Cut) S (Space)	C (Cut)
	8 (UTF-8)	Y (Add) N (Do not add)	Y (Add)
HULFT for MSP	(*1)	C (Cut) S (Space)	C (Cut)
HULFT for XSP	(*1)	C (Cut) S (Space)	C (Cut)

*1

:

When connecting to HULFT for MSP or HULFT for XSP, you cannot set Code Set for Transfer (CS4TRNSFR).

Subsequent Character

Handling of trailing space and NULL (X'00') characters in the data read from Send files

Cut off NULL:

Cut the trailing null characters

Cut Off Spaces:

Cut the trailing space characters

Both:

Cut the trailing space and null characters

No Cut-off:

Do not cut the trailing space and null characters

If Transfer Type is something other than 'TEXT,' you can specify only 'No Cut-off.'

Omitting this field sets 'No Cut-off.'

UNIT

Unit name of the unit that stores the Send file

Sequence Number

Sequence number on the tape volume that stores the Send file

Sending with RDW

Specify whether to add the Record Descriptor Word (RDW) to the transfer data.

Yes:

Sending with RDW

No:

Sending without RDW

When you send a file with RDW, specify 'BINARY' for Transfer Type. Omitting this field sets 'No.'

For details, refer to Administration Manual for the destination host.

Cipher Key (when Forced Strong Key mode is disabled)

Key used when data is encrypted in an encryption algorithm

You can apply security to the file to be sent. Specify the same cipher key as is specified in the Receive Management Information on the remote host.

If this field is omitted, the file is not encrypted.

Cipher Key (when Forced Strong Key mode is enabled)

Key used when data is encrypted in an encryption algorithm

You can apply security to the file to be sent. Specify the same cipher key as is specified in the Receive Management Information on the remote host.

File ID

You cannot specify "_INSTANT_TRANSFER_" for File ID.

Mainframe DSN

Do not enclose file names within single quotations (').

For details about files that can be sent, refer to Administration Manual for the destination host.

Use parentheses when specifying the relative generation number for data sets by generation, and the member names of partitioned data sets (PDS).

Volume Serial

If Volume Serial is omitted, files are considered to be cataloged.

If you specify the following file for Mainframe DSN, do not specify Volume Serial:

• VSAM file

• Data set by generation (specified by relative generation number)

If all of the following conditions are met, the Send file is deleted. However, the catalog information is not deleted.

• Volume Serial is specified

• 'Delete' is specified for Send File Mode

• The Send file exists on a non-SMS-managed volume

UNIT

If you omit UNIT, the value set for UNIT Name of Send Files and Receive Files (INIT-UNIT) in the System Environment Settings is used.

If Volume Serial is omitted, the value for UNIT is obtained from the catalog. The following values are not used even if they are set:

• UNIT

• UNIT Name of Send Files and Receive Files (INIT-UNIT)

Send File Mode

• If you specify 'Clear' or 'Delete,' be sure to note the following:

  • You cannot set a VSAM file or partitioned data set (PDS) as a Send file.

  • If you execute Work File Transfer, the timing for clearing or deleting Send files will vary according to the value you set for Post-send Clear Mode (CLEARMODE) in the System Environment Settings.

    • If you set 'B' for Post-send Clear Mode

      Send files are cleared or deleted after the Send work file is created. This occurs regardless of whether the Send processing ends successfully or unsuccessfully.

    • If you set 'A' for Post-send Clear Mode

      Send files are cleared or deleted after the Send processing ends successfully.

  • Multicasting is not possible.

    However, multicasting is possible if all of the following conditions are met:

    • 'Work File' is specified for Transfer Mode

    • 'B' is specified for Post-send Clear Mode in the System Environment Settings

  • If you specify sending-side conversion for Work File Transfer, single-byte code conversion is not possible during transfer between EBCDIC and EBCDIC.

• If 'Lock' is specified, multicasting is not possible.

Work Volume Serial

If Work Volume Serial is omitted, the volume where the Send work file is created will vary as shown below based on Work Volume Mode (WORKVOLMODE) in the System Environment Settings.

Capacity

If you specify 'OMIT' for Capacity, the following values for the Send work file will be calculated automatically from the Send file capacity:

• Capacity

• 1ST Extent

• Secondary

Automatic calculation of capacity is carried out based on the capacity of the Send file.

• For multi-volume files

  HULFT does not obtain the number of volumes in use from the Send file.

  Therefore, you must specify the number of volumes used by the Send file for UNIT Quantity.

• For partitioned data sets (PDS)

  HULFT calculates the size of the Send work file based on the size of the entire partitioned data set (PDS). Therefore, HULFT may create a Send work file that is larger than the size of the Send file.

  Consider the capacity of the Send work file and specify an appropriate value for Work Volume Serial.

• When the device types of Send file and Send work file are different

  HULFT does not consider the device type when it carries out automatic calculation of capacity.

  Therefore, an insufficient-space error for the Send work file or the work volume may occur.

However, capacity is not calculated automatically in the following circumstances:

• If the Send file is allocated in a unit of capacity other than track or cylinder

• If the Send file is a VSAM file

Sequence Number

If you omit Sequence Number and send files stored in the tape volume, the file with sequential number '1' is sent.

UNIT Quantity

The value specified for UNIT Quantity will vary in the situations described below.

• If you specify '2' or greater for UNIT Quantity

  You cannot specify Work Volume Serial.

• If the Send work file is created on an SMS-managed volume

  A multi-volume file is created according to the setting of UNIT Quantity.
  However, when UNIT Quantity is specified as "1", the multi-volume file is created according to the setting for "volume count" of the SMS data class.

Code conversion

• When the receiving-side host runs a version of HULFT for Mainframe that is lower than Ver.8.4 and "8" (UTF-8) is specified for Code Set for Transfer in the System Environment Settings on the receiving-side host, you cannot specify "Receiving Side".

• When both the sending-side host and the receiving-side host are Ver.8.4 or higher, code conversion may switch to the receiving-side even if you specify "Sending Side" for Code Conversion, or code conversion may switch to the sending-side even if you specify "Receiving Side" for Code Conversion. For details, refer to the explanation about the sending-side conversion and the receiving-side conversion in Code Conversion Manual.

Transfer Block Length and Transfer Block Count

If you specify '0' for both Transfer Block Length and Transfer Block Count, HULFT system automatically sets the size of the transfer unit (Transfer Block Length x Transfer Block Count).

However, if you specify '0' for only one of either Transfer Block Length or Transfer Block Count, an error occurs.

Replacement Message

You can replace variables with messages in the fields that are listed below.

Specify '&MSG0' to '&MSG5' or '&MSGL0' to '&MSGL1' in the following fields to replace the strings with messages that you specify when you issue the Send File or when you issue the Send Request:

• Mainframe DSN

• Volume Serial

• Work Volume Serial

• UNIT

• Transfer Group ID

• Pre-send Job ID

• Successful Job ID

• Format ID

• Multi Format ID

HULFT may not be able to replace the variables with the messages correctly and the transfer may fail, depending on the language settings on the host on the receiving side.

For points to be noted on message transmission, refer to Administration Manual for the destination host.

Restrictions on using tape volumes

There are several restrictions that apply when you carry out the Send processing on a tape volume. For details on these restrictions, refer to Operation Manual for the destination host.

Shiftcode Mode

If you use the following settings for sending, the record length after code conversion varies according to the value specified for Shiftcode Mode for Send Files (RECLEN) in the System Environment Settings:

• 'Sending Side' for Code Conversion

• 'Cut' for Shiftcode Mode

• 'TEXT' for Transfer Type

For details on shift code conversion, refer to Code Conversion Manual for the destination host.

Code Conversion

When the destination host is HULFT8 for zOS and '8' (UTF-8) is specified for Code Set for Transfer (CS4TRNSFR) in the System Environment Settings, the Code Conversion is not possible on HULFT for zOS. In this case, specify 'R' (Receiving Side) to carry out conversion on the receiving side.

EBCDIC Set

If you specify any of the following values, you must register an EBCDIC user table:

• User Table 1

• User Table 2

• User Table 3

For details on the registration of EBCDIC user tables, refer to Administration Manual for the destination host.

Note that certain conditions must be met when you specify any of the above values. In addition, even if the conditions for specification are met, an error may occur during sending. For details, refer to Code Conversion Manual for the destination host.

Operation when 'Autoconfiguration' is specified for EBCDIC Set

When you specify '0' (Autoconfiguration) for EBCDIC Set, the value of the EBCDIC Set that is actually used in single-byte code conversion is determined for each transfer as follows: