Transfer Test

The Transfer Test function checks the file transfer operation while suppressing functions that affect business operation, such as job execution or output of logs. The test does not affect business operation, so you can check the file transfer operation in the actual operating environment.

Use the Transfer Test function to check the following:

Whether a transfer can be performed or not
In the case of a transfer error, the cause of the error, determined from the Status code (when output of the Send Log and the Receive Log are not suppressed)
Code Conversion result for the Receive file, and the data size (when creation of the Receive file is not suppressed)
Estimates of the time required for the transfer and the transfer rate (when output of the Send Log and the Receive Log are not suppressed)
Compression ratio (when output of the Send Log is not suppressed)

Note

You can use the Transfer Test function if HULFT8 or higher is installed. If checking the operation of file transfers using both the host on the sending side and the host on the receiving side, HULFT8 or higher must be installed on both sides.

Figure 2.49 Transfer Test Function

Functions that can be suppressed during a Transfer Test

The following operations can be suppressed using the Transfer Test function. Specify the functions you want to suppress in the System Environment Settings. Refer to System Environment Settings for details.

Execution of Pre-send Job
Execution of Post-send Job
Execution of Post-receive Job
Creation of Receive file
Output of Send Log and Receive Log

Note

When the sending-side host is in Test-priority mode and a file is transferred during the test operation in conjunction with the receiving-side host, pre-send jobs are not suppressed, even if you set the pre-send jobs to be suppressed in the System Environment Settings.
When you transfer a file in test operation from the sending-side host to the receiving-side host in Test-Priority mode, even if you specify the suppression of the following functions in the System Environment Settings, these functions may not be suppressed:
- Execution of Post-send Job
- Execution of Post-receive Job
- Output of Send Log and Receive Log
When you set the output of receive files to be suppressed in the System Environment Settings, in Transfer Test, you cannot check the operations that assume the existence of the receive files such as subsequent jobs. Even if the transfer ends successfully in test operation, the transfer may fail in normal operation.

The receive file names are passed to subsequent jobs and logs in a similar manner when receive files are created. However, even if you specify the generational management of a receive file, the file name without a generational management number is output in logs.

Operation during file transfer

HULFT8 file transfer is carried out in either of the following:

Normal operation

In normal operation, functions that affect business operation, such as jobs and log outputs, are executed according to the settings.
Test operation

In test operation, execution of functions that affect business operation, such as jobs and log outputs, are suppressed according to the settings. Specify the functions you want to suppress in the System Environment Settings.

Whether to execute file transfer in normal operation or in test operation can be specified with Transfer Preference (ttmode) in the System Environment Settings.

For Transfer Preference, specify either of the following:

Test-run Mode

This mode is used to execute file transfer in test operation.
Test-priority Mode

This mode is used to execute file transfer in test operation if either the host on the sending side or the host on the receiving side is in Test-run Mode.

To execute file transfer in normal operation, specify 'Test-priority Mode' on both the host on the sending side and the host on the receiving side.

How file transfer is executed may vary for each host depending on the combination of the transfer preferences that are set for the host on the sending side and the host on the receiving side.

The combinations of transfer preferences and how file transfer is executed on each host are shown in the following table.

Table 2.24 Combination of Transfer Preferences and How the Host Operates
			Sending Host
			HULFT8				Lower than HULFT8
			Use HULFT7 Comm. Mode is 'No'		Use HULFT7 Comm. Mode is 'Yes'		-
			Test-priority Mode	Test-run Mode	Test-priority Mode	Test-run Mode	-
Receiving Host	HULFT8	Test-priority Mode	Sending Host: Normal operation Receiving Host: Normal operation	Sending Host: Test operation Receiving Host: Test operation	Sending Host: Normal operation Receiving Host: Normal operation	Sending Host: Test operation (2) Receiving Host: (3)	Sending Host: Normal operation Receiving Host: Normal operation
	HULFT8	Test-run Mode	Sending Host: Test operation (*4) Receiving Host: Test operation	Sending Host: Test operation Receiving Host: Test operation	Sending Host: Normal operation (Error) (4) Receiving Host: (1)	Sending Host: Test operation (2) Receiving Host: (3)	Sending Host: Normal operation (Error) Receiving Host: (*1)
	Lower than HULFT8	-	Sending Host: Normal operation Receiving Host: Normal operation	Sending Host: Test operation (2) Receiving Host: (3)	Sending Host: Normal operation Receiving Host: Normal operation	Sending Host: Test operation (2) Receiving Host: (3)	Sending Host: Normal operation Receiving Host: Normal operation

-	:	Not Available
*1	:	An error (Status Code=517) occurs on the host on the receiving side.
*2	:	The result on the host on the sending side varies depending on the setting of Result Handling of Receiving (ttrcvomit) in the System Environment Settings.
*3	:	HULFT does not transfer files to the host on the receiving side.
*4	:	You cannot suppress the execution of the pre-send job. The pre-send job is executed before the sending-side host switches to the test operation after the sending-side host connects to the receiving-side host.

Note

If a transfer error occurs in test operation, HULFT treats the Send file for which transfer failed as unsent, or places it in the Resend Queue.

In this case, delete the unnecessary unsent records or the unnecessary records from the Resend Queue.
Note that it is not possible to distinguish error messages that are output in test operation from those that are output in normal operation.