Read History Information

Operation Name

Function Overview

Read HULFT transferring history information when executed from HULFT Script Trigger.

Properties

For information about using variables, refer to "variables".

Basic settings

Item name	Required/Optional	Use of Variables	Description	Remarks
Name	Required	Not available	Enter a name that is used on the script canvas.

Test execution settings

Item name	Required/Optional	Use of variables	Description	Remarks
Values for test execution	Required	-	Set values to be assigned to component variables on test execution.	Refer to “Available component variables” for values to assign. “Values for test execution” will be applied only on test execution. When running from HULFT Script Trigger, data retrieved from HULFT will be used.
Values for test execution/Component variable name	Required	Not available	A component variable name is displayed.
Values for test execution/Value for test execution	Optional	Available	Set a value to assign.	Default value will have been set for some of [Value for test execution]. Set the value which you need.

Comment

Item name	Required / Optional	Use of Variable	Description	Remarks
Comment	Optional	Not available	You can write a short description of this adapter. The description will be reflected in the specifications.

Schema

Input Schema

None.

Output Schema

None.

Mass Data Processing

Mass data processing is not supported.

PSP Usage

PSP is not supported.

Available component variables

Component variable name	Description	Remarks
HS_TRANSFER_CATEGORY	The category of transmission history is stored.	In case of sending, "SEND" is stored. In case of receiving, "RECEIVE" is stored.
HS_FILEID	File ID is stored.	For details on the item, please refer to the HULFT documents.
HS_HOSTNAME	Host name is stored.	For details on the item, please refer to the HULFT documents.
HS_STATUS_CODE	The last three digits of completion code is stored.	For details on the specifications of completion codes, please refer to the HULFT documents.
HS_STATUS	Completion code is stored.	For details on the item, please refer to the HULFT documents.
HS_DETAIL	Detail error code is stored.	For details on the item, please refer to the HULFT documents.
HS_FILENM	Transmitted file name is stored.	For details on the item, please refer to the HULFT documents. Example:c:\work\test.txt
HS_FS_FILE_PATH	Path mounted HS_FILENM with file systems is stored.	Example:/tmp/hstrigger/cs000xxx/test.txt
HS_FS_FILE_PARENT	Parent directory of HS_FS_FILE_PATH is stored.	Example:/tmp/hstrigger/cs000xxx
HS_FS_FILE_NAME	File name of HS_FILENM, HS_FS_FILE_PATH is stored.	Example:test.txt
HS_DATASIZE	Data size is stored.	For details on the item, please refer to the HULFT documents.
HS_COUNT	Record number is stored.	For details on the item, please refer to the HULFT documents.
HS_SDATE	Starting date is stored.	For details on the item, please refer to the HULFT documents.
HS_STIME	Starting time is stored.	For details on the item, please refer to the HULFT documents.
HS_EDATE	Ending date is stored.	For details on the item, please refer to the HULFT documents.
HS_ETIME	Ending time is stored.	For details on the item, please refer to the HULFT documents.
HS_TRANSTYPE	Transmission type is stored.	For details on the item, please refer to the HULFT documents.
HS_MSG0	Message ($MSG0) is stored.	For details on the item, please refer to the HULFT documents.
HS_MSG1	Message ($MSG1) is stored.	For details on the item, please refer to the HULFT documents.
HS_MSG2	Message ($MSG2) is stored.	For details on the item, please refer to the HULFT documents.
HS_MSG3	Message ($MSG3) is stored.	For details on the item, please refer to the HULFT documents.
HS_MSG4	Message ($MSG4) is stored.	For details on the item, please refer to the HULFT documents.
HS_MSG5	Message ($MSG5) is stored.	For details on the item, please refer to the HULFT documents.
HS_MSGL0	Extension message 0($MSGL0) is stored.	For details on the item, please refer to the HULFT documents.
HS_MSGL1	Extension message 1($MSGL1) is stored.	For details on the item, please refer to the HULFT documents.
message_category	When an error occurs, its corresponding categories of the message code is stored.	The value defaults to null.
message_code	Stores its corresponding message code of occured error.	The value defaults to null.
message_level	When an error occurs, its corresponding severity of the message code is stored.	The value defaults to null.
error_type	When an error occurs, its corresponding types of the message code is stored.	The value defaults to null. Error is represented in the format depicted below. Example:"java.io.FileNotFoundException" The message may vary depending on version.
error_message	When an error occurs, its corresponding error message is stored.	The value defaults to null. The message may vary depending on version.
error_trace	When an error occurs, its corresponding trace information is stored.	The value defaults to null. The message may vary depending on version.

Specification Limitation

Does not implement temporal mount, if the transmitted file path is not absolute path, or the parent directory does not exist.
In this case, the following component variables become null.
- "HS_FS_FILE_PATH"
- "HS_FS_FILE_PARENT"
- "HS_FS_FILE_NAME"

Component variable type is character string type. If you prefer to treat as numeric values in conditional branches, you need to assign to the script values of decimal digit type.

Main exceptions

Exception name	Cause	Solution
java.io.FileNotFoundException	Files that history information is output from HULFT Script trigger do not exist.	A script might be executed from a trigger other than HULFT Script Trigger. Run it from HULFT Script Trigger.

Notes

This adapter works on the assumption that it is executed from HULFT Script Trigger.