Send Management Information
Register the File Information for the Send file. There are two ways to register the information.
-
Registration using either of the following two screens
-
Send Management Information Update (Basic) screen
-
Send Management Information Update (Extension) screen
=> Refer to Using the Send Management Information
-
-
Registration specifying a definition card and using the Management Information Batch Registration program (XRSYSINF)
=> Refer to Registration and modification of management information
(1) Field List
'Optional' in the chart below refers to whether or not the field is optional for registration on the HULFT Management Console. Optional parameters for batch registration may differ from optional fields on the HULFT Management Console.
For details on optional parameters for batch registration, refer to Registration and modification of management information.
Field Name |
When Defaulted |
Setting |
Optional |
Remarks |
||
---|---|---|---|---|---|---|
Screen |
File |
|||||
File ID |
SNDFILE |
|
Alphanumeric characters |
- |
Within 50 bytes |
|
Mainframe DSN |
DSNAME |
|
Alphanumeric characters |
- |
Within 44 bytes |
|
Comment |
COMMENT |
|
Alphanumeric characters, half-width Katakana |
✓ |
Within 60 bytes |
|
Send Management Information Update (Basic) screen |
||||||
|
Volume Serial |
VOL |
|
Alphanumeric characters |
✓ |
Within 6 bytes |
Transfer Mode |
DIRECT |
W |
D, W |
✓ |
|
|
Work Volume Serial |
WORK-VOL |
|
Alphanumeric characters |
✓ |
Within 6 bytes |
|
Capacity |
CYL|TRK|OMIT |
C |
C, T, O |
✓ |
|
|
1ST Extent |
CYL|TRK |
5 |
From 1 to 9999 |
✓ |
|
|
Secondary |
CYL|TRK |
3 |
From 0 to 9999 |
✓ |
|
|
UNIT Quantity |
UNIT-CNT |
1 |
From 1 to 59 |
✓ |
|
|
Transfer Type |
TRANSTYPE |
|
F, B, T, M |
- |
(*1) |
|
Multi/Format ID |
FMTID |
|
Alphanumeric characters |
✓ |
Within 50 bytes |
|
Compression Preference |
COMP |
|
N, 1, 2 |
- |
(*1) |
|
Code Conversion |
CODE-CONV |
|
S, R, N |
- |
(*1) |
|
EBCDIC Set |
CODESET |
0 |
0, A to H, V to X |
✓ |
|
|
Send File Mode |
CLEAR |
K |
K, C, D, L |
✓ |
|
|
Transfer Group ID |
GRPID |
|
Alphanumeric characters |
- |
Within 50 bytes |
|
Pre-send Job ID |
PRE-JOB |
|
Alphanumeric characters |
✓ |
Within 50 bytes |
|
Successful Job ID |
JOBID |
|
Alphanumeric characters |
✓ |
Within 50 bytes |
|
Unsuccessful Job ID |
AB-JOBID |
|
Alphanumeric characters |
✓ |
Within 50 bytes |
|
Send Management Information Update (Extension) screen |
||||||
|
Interface DBID |
DBID |
|
CSV |
✓ |
Only the string 'CSV' (*2) |
Transfer Interval |
INTERVAL |
0 |
From 0 to 32768 |
✓ |
Unit: 10 milliseconds |
|
Transfer Priority |
TRANSPRTY |
50 |
From 1 to 256 |
✓ |
|
|
Transfer Block Length |
BLOCKLEN |
0 |
0, from 128 to 65520 |
✓ |
Unit: byte |
|
Transfer Block Count |
BLOCKNUM |
0 |
From 0 to 99 |
✓ |
|
|
Shiftcode Mode |
SHIFT-CODE |
(*3) |
C, S, Y, N |
✓ |
(*3) |
|
Subsequent Character |
PAD |
N |
0, S, A, N |
✓ |
|
|
UNIT |
UNIT |
|
Alphanumeric characters |
✓ |
Within 8 bytes |
|
Sequence Number |
VSEQNO |
|
From 1 to 9999, |
✓ |
|
|
Sending with RDW |
SND-RDW |
N |
Y, N |
✓ |
|
|
Cipher Key |
PASSWORD or PW |
|
Alphanumeric characters |
✓ |
From 8 to 20 bytes |
|
Cipher Key |
PW |
|
Hexadecimal character string |
- |
64 digits |
✓ |
: |
Optional |
- |
: |
Mandatory |
*1 |
: |
If you use the Management Information Batch Registration program (XRSYSINF) to register the information, you can default the parameter. If you default the parameter, HULFT sets one of the following:
|
|||||||||
*2 |
: |
You can specify this field if you specify 'F' (FORMAT) or 'M' (MULTI FMT) for the Transfer Type. |
|||||||||
*3 |
: |
Values that can be specified and values that are set when the specification is omitted vary, depending on the setting of the Code Set for Transfer (CS4TRNSFR) in the System Environment Settings.
|
|||||||||
*4 |
: |
This type of cipher key can be set when Forced Strong Key Mode (STRONGKEYMODE) is set to "0" (Disabled) in the System Environment Settings. |
|||||||||
*5 |
: |
This type of cipher key must be set when Forced Strong Key Mode (STRONGKEYMODE) is set to "1" (Enabled) in the System Environment Settings. |
(2) Specification of each field
The following explains the fields specified in the Send Management Information. Strings within brackets () are the tags of parameter names to be defined in a definition card for the Management Information Batch Registration program (XRSYSINF).
- File ID (SNDFILE)
-
This field specifies the ID to identify the Send file.
Specify alphanumeric characters within 50 bytes.
- Mainframe DSN (DSNAME)
-
This field specifies the data set name of the Send file that is stored on mainframes.
Specify the name according to the data set naming conventions for mainframes.
- Comment (COMMENT)
-
This field specifies the comment on the Send file.
Send Management Information Update (Basic) screen
- Volume Serial (VOL)
-
This field specifies the serial number of the volume that stores the Send file.
Specify the volume serial number according to the volume serial number naming conventions for mainframes.
- Transfer Mode (DIRECT)
-
This field specifies the transfer mode that HULFT uses when it sends the Send file.
- D (Direct):
-
Transfer the Send file directly without creating a work file
- W (Work File):
-
Create a work file from the Send file and then carry out transfer
Defaulting this field sets 'W' (Work File).
- Work Volume Serial (WORK-VOL)
-
This field specifies the volume serial number of the Send work file.
Specify the volume serial number according to the volume serial number naming conventions for mainframes.
- Capacity (CYL|TRK|OMIT)
-
This field specifies the space unit for the Send work file.
- C:
-
Cylinder
- T:
-
Track
- O:
-
Omit (automatically calculated)
Defaulting this field sets 'C' (Cylinder).
- 1ST Extent (CYL|TRK)
-
This field specifies the first extent for the Send work file.
Defaulting this field sets '5.'
- Secondary (CYL|TRK)
-
This field specifies the secondary extent for the Send work file.
Defaulting this field sets '3.'
- UNIT Quantity (UNIT-CNT)
-
This field specifies the multiple volume unit quantity for the Send work file.
Defaulting this field sets '1.'
- Transfer Type (TRANSTYPE)
-
This field specifies the transfer data type of the Send file.
- F (FORMAT):
-
Format data
- B (BINARY):
-
Binary data
- T (TEXT):
-
Text data
- M (MULTI FMT):
-
Multi format data
- Format/Multi Format ID (FMTID)
-
This field specifies the ID of the record in which the Format or Multi Format of the Send file is registered.
For details on the Format ID, refer to Format Information.
For details on the Multi Format ID refer to Multi Format Information.
If you set 'F' (FORMAT) for the Transfer Type (TRANSTYPE), specify a Format ID.
If you set 'M' (MULTI FMT) for the Transfer Type, specify a Multi Format ID.
- Compression Preference (COMP)
-
This field specifies the compression type used when a file is transferred.
- N:
-
None
- 1:
-
Horizontal (Compression within each record)
- 2:
-
Vertical (Compression across records)
- Code Conversion (CODE-CONV)
-
This field specifies the code conversion type used for the Send file.
- S (Sending Side):
-
Convert the file on the sending host
- R (Receiving Side):
-
Convert the file on the receiving host
- N (No Conversion):
-
Send the file without conversion
- EBCDIC Set (CODESET)
-
This field specifies the Type-EBCDIC Code Set on the local host that HULFT uses to convert single byte codes.
- 0:
-
Autoconfiguration
- A:
-
EBCDIC Katakana
- B:
-
EBCDIC Lowercase
- C:
-
EBCDIC-ASCII
- D:
-
EBCDIC-ASPEN
- E:
-
Japan (Latin) for IBM
- F:
-
Japan (Latin) Extended for IBM
- G:
-
NEC Katakana
- H:
-
Japan (Katakana) Extended for IBM
- V:
-
User Table 1
- W:
-
User Table 2
- X:
-
User Table 3
Defaulting this field sets '0' (Autoconfiguration).
This setting is valid when the host on the receiving side is a Type MF-IBMi host and you specify sending-side conversion.
- Send File Mode (CLEAR)
-
This field specifies exclusive control of the Send file during the Send processing and handling of the file when the Send processing ends successfully.
- K (Keep):
-
Do not lock the file during the Send processing or during creation of a Send work file. HULFT saves the file after the Send processing ends successfully.
- C (Clear):
-
Lock the file during the Send processing or during creation of a Send work file. After the Send processing ends successfully, HULFT clears the file and the size of the file becomes 0 bytes.
- D (Delete):
-
Lock the file during the Send processing or during creation of a Send work file. HULFT deletes the file after the Send processing ends successfully.
- L (Lock):
-
Lock the file during the Send processing or during creation of a Send work file. HULFT saves the file after the Send processing ends successfully.
Defaulting this field sets 'K' (Keep).
- Transfer Group ID (GRPID)
-
This field specifies the ID of the record in which the send destinations of the Send file are registered.
For details on the Transfer Group ID, refer to Transfer Group Information.
- Pre-send Job ID (PRE-JOB)
-
This field specifies the Job ID of the job that HULFT activates before the Send processing.
For details on the Job ID, refer to Job Information.
If you default this field, the job is not executed.
- Successful Job ID (JOBID)
-
This field specifies the Job ID of the job that HULFT activates when the Send processing ends successfully.
For details on the Job ID, refer to Job Information.
If you default this field, the job is not executed.
- Unsuccessful Job ID (AB-JOBID)
-
This field specifies the Job ID of the job that HULFT activates when the Send processing ends unsuccessfully.
For details on the Job ID, refer to Job Information.
If you default this field, the job is not executed.
Send Management Information Update (Extension) screen
- Interface DBID (DBID)
-
This field specifies the method of interface with the data to send, which is used on the host on the receiving side.
- CSV:
-
Convert the Receive file into CSV format on the host on the receiving side
When you want to receive the Receive file in CSV format on the receiving host (UNIX, Linux, NonStop, or Windows), specify "CSV".
If you default this parameter, HULFT does not carry out receiving in CSV format.
When you use the Interface function, specify 'F' (FORMAT) or 'M' (MULTI FMT) for the Transfer Type.
- Transfer Interval (INTERVAL)
-
This field specifies the interval between when HULFT has finished transferring a block and when HULFT begins transferring the next block.
Defaulting this field sets '0.'
- Transfer Priority (TRANSPRTY)
-
This field specifies the priority in the queue when HULFT starts the file transfer.
The lower the value, the higher the priority. Defaulting this field sets '50.'
- Transfer Block Length (BLOCKLEN)
-
This field specifies the length of one block for transfer.
You cannot set values for the Transfer Block Length (BLOCKLEN) and the Transfer Block Count (BLOCKNUM) the product of which exceeds 65520. Defaulting this field sets '0.'
- Transfer Block Count (BLOCKNUM)
-
This field specifies the number of blocks per transfer.
You cannot set values for the Transfer Block Length (BLOCKLEN) and the Transfer Block Count (BLOCKNUM) the product of which exceeds 65520. Defaulting this field sets '0.'
- Shiftcode Mode (SHIFT-CODE)
-
This field specifies how HULFT handles shift codes when HULFT sends data to a host.
- C (Cut):
-
Delete shift codes and convert to shortened data
- 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 the specification is omitted vary, depending on the setting of the Code Set for Transfer (CS4TRNSFR) in the System Environment Settings.
Setting of Code Set for Transfer (CS4TRNSFR)
Values That Can Be Set
Value When Specification Is Omitted
I (IBM Kanji)
-
C (Cut)
-
S (Space)
C (Cut)
8 (UTF-8)
-
Y (Add)
-
N (Do not add)
Y (Add)
- Subsequent Character (PAD)
-
This field specifies how to handle trailing spaces and NULLs (X'00') in the data that is read from the Send file.
- 0 (Cut Off NULL):
-
Cut trailing NULLs
- S (Cut Off Spaces):
-
Cut trailing space codes
- A (Both Cut):
-
Cut both trailing space codes and trailing NULLs
- N (No Cut-off):
-
Do not cut trailing space codes or trailing NULLs
If the Transfer Type (TRANSTYPE) is a type other than 'T' (TEXT), only 'N' (No Cut-off) can be set.
Defaulting this field sets 'N' (No Cut-off).
- UNIT (UNIT)
-
This field specifies the unit name of the unit that stores the Send file.
- Sequence Number (VSEQNO)
-
This field specifies the sequence number on the tape volume that stores the Send file.
- Sending with RDW (SND-RDW)
-
This field specifies whether or not to add the Record Descriptor Word (RDW) to the transfer data.
- N (No):
-
Sending without RDW
- Y (Yes):
-
Sending with RDW
When you enable sending with RDW, set 'B' (BINARY) for the Transfer Type. Defaulting this field sets 'N' (No).
For details, refer to Administration Manual.
- Cipher Key (PASSWORD or PW) (when Forced Strong Key mode is disabled)
-
This field specifies the key that HULFT uses when HULFT encrypts the data.
You can apply security to the Send file. Specify the same cipher key as the Cipher Key specified in the Receive Management Information on the remote host.
If you default this field, HULFT does not encrypt the file.
- Cipher Key (PW) (when Forced Strong Key mode is enabled)
-
This field specifies the key that HULFT uses when HULFT encrypts the data.
You can apply security to the Send file. Specify the same cipher key as the Cipher Key specified in the Receive Management Information on the remote host.
Make sure that you specify Cipher Key. If the receiving-side host is not in Forced Strong Key mode, a transfer error occurs.
(3) Points to be noted when specifying
File ID
You cannot specify "_INSTANT_TRANSFER_" for File ID (SNDFILE).
Mainframe DSN
Do not enclose the file names within single quotations (').
For details on files that HULFT can send, refer to Administration Manual.
Specify the relative generation number for the generation data set and the member name for the partitioned data set (PDS) within brackets.
Volume Serial
If you default the Volume Serial (VOL), HULFT regards the file as cataloged.
When you specify the following types of files for the Mainframe DSN (DSNAME), do not specify the Volume Serial (VOL):
-
VSAM file
-
Generation data set (specified using a relative generation number)
If all the following conditions are fulfilled, the send file is deleted but the catalog information is not:
-
The Volume Serial (VOL) is specified
-
'D' (Delete) is specified for the Send File Mode (CLEAR)
-
The Send file exists on a non-SMS-managed volume
Work Volume Serial
If you default the Work Volume Serial (WORK-VOL), the volume on which the Send work file is created varies depending on the setting of the Work Volume Mode (WORKVOLMODE) in the System Environment Settings, as follows:
Work Volume Mode (WORKVOLMODE) |
Volume on which Send Work File Is Created |
---|---|
0 (Work volume for the system) |
A volume that is defined as a volume with the storage attribute |
1 (Same volume as the Send file) |
The same volume as the Send file |
Capacity
If you specify 'O' (Omit) for the Capacity (CYL|TRK|OMIT), HULFT automatically calculates the following values for the Send work file based on the capacity of the Send file:
-
Capacity (CYL|TRK|OMIT)
-
1ST Extent (CYL|TRK)
-
Secondary (CYL|TRK)
Automatic calculation of capacity is carried out based on the size of the Send file.
-
Case where the file is a multi-volume file
HULFT does not obtain the number of volumes in use from the Send file.
Therefore, you must specify the number of volumes that are used by the Send file for the UNIT Quantity (UNIT-CNT).
-
Case where the file is a partitioned data set (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 size of the Send work file, and specify an appropriate value for the Work Volume Serial (WORK-VOL).
-
Case where the device type is different for the Send file and the Send work file
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, HULFT does not carry out automatic calculation of capacity in the following cases:
-
Case where the Send file is created in a unit of capacity other than tracks or cylinders
-
Case where the Send file is a VSAM file
UNIT Quantity
The value of the UNIT Quantity (UNIT-CNT) has the following restrictions:
-
Case where you specify '2' or more for the UNIT Quantity (UNIT-CNT)
You cannot specify the Work Volume Serial (WORK-VOL).
-
Case where you create the Send work file on an SMS-managed volume
The multi-volume file is created according to the setting of UNIT Quantity (UNIT-CNT).
However, when UNIT Quantity (UNIT-CNT) 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 remote host runs a version lower than HULFT Ver.8.4 and "8" (UTF-8) is specified for Code Set for Transfer (CS4TRNSFR) in the System Environment Settings, because the code conversion is not possible on HULFT for zOS, specify "R" (Receiving Side) and carry out the conversion on the receiving-side host.
-
When both the sending-side host and the receiving-side host are Ver.8.4 or higher, the code converting side may switch to the receiving-side even if you specify "S" (Sending Side) for Code Conversion (CODE-CONV), or switch to the sending-side even if you specify "R" (Receiving Side) for Code Conversion (CODE-CONV). For details, refer to the explanation of the sending-side conversion and the receiving-side conversion in Code Conversion Manual.
EBCDIC Set
If you specify any of the following values, you must register the corresponding EBCDIC user table in advance:
-
V (User Table 1)
-
W (User Table 2)
-
X (User Table 3)
For details on the registration of EBCDIC user tables, refer to Administration Manual.
In order to specify any of the above, there are conditions that must be met. Even if the conditions for specification are met, an error may occur during sending. For details, refer to Code Conversion Manual.
Send File Mode
-
When you specify 'C' (Clear) or 'D' (Delete) for this field, note the following points:
-
You cannot specify a VSAM file or a partitioned data set (PDS) for the Send file.
-
When you use the Work File Transfer, the timing of clearance or deletion of the Send file varies depending on the setting of the Post-send Clear Mode (CLEARMODE) in the System Environment Settings.
-
When you specify 'B' for the Post-send Clear Mode (CLEARMODE)
The Send file will be cleared or deleted after the Send work file is created. It does not matter whether the Send processing ends successfully or not.
-
When you specify 'A' for the Post-send Clear Mode (CLEARMODE)
The Send file will be cleared or deleted after the Send processing ends successfully.
-
-
You cannot carry out multicasting.
However, if all the following conditions are fulfilled, you can carry out multicasting:
-
'W' (Work File Transfer) is specified for the Transfer Mode (DIRECT)
-
'B' is specified for the Post-send Clear Mode in the System Environment Settings
-
-
-
When you specify 'L' (Lock) for this field, you cannot carry out multicasting.
Transfer Block Length and Transfer Block Count
If you specify '0' for both the Transfer Block Length (BLOCKLEN) and the Transfer Block Count (BLOCKNUM), HULFT system automatically sets the size of the transfer unit (Transfer Block Length x Transfer Block Count).
Note that if your specify '0' for only the Transfer Block Length (BLOCKLEN) or only the Transfer Block Count (BLOCKNUM), an error occurs.
Shiftcode Mode
When you send files with the following settings, the record length after code conversion varies depending on the setting of the Shiftcode Mode for Send Files (RECLEN) in the System Environment Settings:
-
'S' (Sending Side) for the Code Conversion (CODE-CONV)
-
'C' (Cut) for the Shiftcode Mode (SHIFT-CODE)
-
'T' (TEXT) for the Transfer Type (TRANSTYPE)
For details on code conversion rules, refer to Code Conversion Manual.
UNIT
If you default the UNIT (UNIT), HULFT uses the value specified for the UNIT Name of Send Files and Receive Files (INIT-UNIT) in the System Environment Settings.
If you default the Volume Serial (VOL), HULFT obtains the value for the UNIT (UNIT) from the catalog. The following are not used, even if specified:
-
UNIT (UNIT)
-
UNIT Name of Send Files and Receive Files (INIT-UNIT)
Sequence Number
If you send a file on a tape volume without specifying the Sequence Number (VSEQNO), HULFT sends the file with 1 as the sequence number.
Replacement Message
Listed below are the fields for which you can carry out replacement with message.
If you specify '&MSG0' to '&MSG5' or '&MSGL0' to '&MSGL1' for the following fields, the values of the fields are replaced with messages that you specified when you executed the Send File or the Send Request:
-
Mainframe DSN (DSNAME)
-
Volume Serial (VOL)
-
Work Volume Serial (WORK-VOL)
-
UNIT (UNIT)
-
Transfer Group ID (GRPID)
-
Pre-send Job ID (PRE-JOB)
-
Successful Job ID (JOBID)
-
Format ID (FMTID)
-
Multi Format ID (MFMTID)
HULFT may not be able to carry out replacement with message correctly and the transfer may fail, depending on the language settings on the remote host.
For points to be noted on message transmission, refer to Administration Manual.
Operation when 'Autoconfiguration' is specified for EBCDIC Set
When you specify '0' (Autoconfiguration) for the EBCDIC Set, the value of the EBCDIC Set that is actually used in single-byte code conversion is determined for each transfer as follows:
Code Set for Transfer of Local Host (*1) |
EBCDIC Set |
---|---|
I (IBM Kanji) |
F (Japan (Latin) Extended for IBM) |
8 (UTF-8) |
(*2) |
*1 |
: |
The Code Set for Transfer of the local host is the value that you specify for the Code Set for Transfer (CS4TRNSFR) in the System Environment Settings. |
*2 |
: |
In this combination of settings, because HULFT for zOS cannot carry out sending-side conversion, the EBCDIC Set is not used. |
Restrictions on use of tape volumes
There are several restrictions that apply when you carry out the Send processing on a tape volume. For details on restrictions, refer to Restrictions on use of tape volumes.
Sending files in SMS-managed environment
There are several points to be noted when you carry out the Send processing in an SMS-managed environment.
For the operation of HULFT in an SMS-managed environment, refer to Administration Manual.