Send File
Operation name
Send File
Function overview
Requests a Send File for a single file.
This operation is for HULFT Transfer Application.
Properties
For details on use of variables, refer to Variables.
Basic settings
|
Item name |
Required/Optional |
Use of variables |
Description |
Remarks |
|---|---|---|---|---|
|
Name |
Required |
Not available |
Enter a name to use on the script canvas. |
|
Required settings
|
Item name |
Required/Optional |
Use of variables |
Description |
Remarks |
|---|---|---|---|---|
|
Send config |
Required |
Not available |
Select a send configuration. |
|
Comment
|
Item name |
Required/Optional |
Use of variables |
Description |
Remarks |
|---|---|---|---|---|
|
Comment |
Optional |
Not available |
You can write a short description of this connector. |
|
Schemas
Input schema
None.
Output schema
None.
Transaction
Transaction isn't supported.
Parallel Stream Processing
PSP isn't supported.
Available component variables
|
Component variable name |
Description |
Remarks |
|---|---|---|
|
exit_status |
The termination status of the Send File command (utlsend) after the command runs is stored. |
|
|
message |
The message used when the Send File command (utlsend) terminates unsuccessfully is stored. |
|
|
message_category |
When an error occurs, the category of the message code corresponding to the error is stored. |
|
|
message_code |
When an error occurs, the code of the message code corresponding to the error is stored. |
|
|
message_level |
When an error occurs, the severity of the message code corresponding to the error is stored. |
|
|
error_type |
When an error occurs, the error type is stored. |
|
|
error_message |
When an error occurs, the error message is stored. |
|
|
error_trace |
When an error occurs, the trace information for the error is stored. |
|
Message codes, exception messages, and limitations
|
Connector |
Message code |
Exception message |
Limitations |
|---|---|---|---|
| Messages and limitations of the HULFT connector |
|
|
|
