Messages and limitations of the HULFT connector
For operations, refer to HULFT (the top page for operations).
Message code list of HULFT category
The following message codes correspond to errors that occur in HULFT Connector.
This message code is output when an undefined error occurs.
|
Cause |
Solution |
|---|---|
|
An undefined error occurred. |
Check the error message or the help of the operation in which the error has occurred. |
Corresponding error
-
None
This message code is output when a timeout error occurs during Synchronous Transfer.
|
Cause |
Solution |
|---|---|
|
A timeout error has occurred during Synchronous Transfer. |
Check the setting of Timeout (Sec.). |
Corresponding error
-
None
This message code is output when the execution of Send File fails.
|
Cause |
Solution |
|---|---|
|
Failed to execute Send File. |
Check the settings of Transfer Service, Send Config, and Send File Name and run the script in debug mode. Check the error message that is output as the execution log. |
Corresponding error
-
None
This message code is output when the values that are entered on the screen are invalid.
|
Cause |
Solution |
|---|---|
|
The values that are entered on the screen are invalid. |
Check the parameters that are entered on the screen. |
Corresponding error
-
None
This message code is output when a connection error to the transfer dispatch occurs.
|
Cause |
Solution |
|---|---|
|
A connection error to the transfer dispatch occurred. |
Contact the system administrator. |
Corresponding error
-
None
This message code is output when the host name for the transfer dispatch is unknown.
|
Cause |
Solution |
|---|---|
|
The host name for the transfer dispatch is unknown. |
Contact the system administrator. |
Corresponding error
-
None
This message code is output when an undefined error occurs.
|
Cause |
Solution |
|---|---|
|
An undefined error occurred. |
Check the error message or the help of the operation in which the error has occurred. |
Corresponding error
-
None
This message code is output when the execution of Send File fails.
|
Cause |
Solution |
|---|---|
|
This error occurs when the execution of Send File fails or when obtaining the send results fails. |
Check the error message or the help of the operation in which the error has occurred. |
Corresponding error
-
HulftTransferException
Exception messages of HULFT category
|
Exception name |
Cause |
Solution |
|---|---|---|
|
java.io.IOException |
Process creation failed. |
The path to bin for HULFT may not be set properly due to incorrect resource settings. |
|
HulftRuntimeExecutionException |
The Status Code is not "0" after a command runs. |
For details, check the message that is output in a log and also refer to manuals for HULFT. |
|
InvalidPropertyConfigurationException |
The property configuration is invalid. |
Check each property setting for the presence of any of the following states:
|
|
InvalidPropertyConfigurationException |
<Property name> is invalid. |
Specify a valid <Property name>. |
|
InputDataNotFoundException |
Input data isn't specified. |
Specify Input data or draw data flow. |
|
HulftTransferException |
The cause differs according to each error message. |
Check the contents of the error message. |
Limitations of HULFT category
Specification limits
-
You can't run the Resend File command.
-
This connector runs various HULFT commands. Therefore, start up the server with user permission that allows reading and writing of files in the installation location of HULFT.
Alternatively, set access permissions so that the server can read and write files in the installation location of HULFT.
Send Files - Dynamic (HULFT Transfer App)
Specification limits
-
None.
Notes
-
An exception may occur if the send results can't be obtained due to reasons such as the input data not existing or a HULFT Transfer App service not being specified.
-
In the case below, execution_id may become null.
-
A parameter specified in the input schema, such as the transfer name, has an invalid value
-
The execution of Send File doesn't finish successfully