Send Files - Dynamic

Operation name

Send Files - Dynamic

Function overview

Requests a dynamic Send File for multiple files.

This operation is for HULFT Transfer Application.

You can use this to pass Send Files settings such as the transfer name to the input schema in the mapping canvas.

Properties

= Remarks =

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.

 

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

<?xml version="1.0"?>
<send_files>
  <send_file>
    <file_id>transfer name</file_id>
    <priority>priority</priority>
    <file_name>file name</file_name>
    <host_name>host name</host_name>
    <message0>message 0</message0>
    <message1>message 1</message1>
    <message2>message 2</message2>
    <message3>message 3</message3>
    <message4>message 4</message4>
    <message5>message 5</message5>
    <long_message0>long message 0</long_message0>
    <long_message1>long message 1</long_message1>
  </send_file>
</send_files>

Element name

Required/Optional

Description

Remarks

send_files

-

 

 

send_file

-

Repeats as many times as Send File was executed.

 

file_id

Required

Enter the transfer name of the file to be sent.

For details about each parameter, refer to "Send File command" in HULFT8 (https://www.hulft.com/help/en-us/HULFT-V8/UX-OPE/Content/HULFT_OPE/HULFTOpeCmd/SndFCmd.htm).

priority

Optional

Enter the priority for the file to be sent.

file_name

Optional

Enter the name of the file to be sent.

host_name

Optional

Enter the name of the remote host to which the file is to be sent.

message0

Optional

Input a message to be sent to the receiving host.

message2

Optional

message3

Optional

message4

Optional

message5

Optional

long_message0

Optional

Input a long message to be sent to the receiving host.

long_message1

Optional

Output schema

<?xml version="1.0"?>
<send_files>
  <send_file>
    <file_id>transfer name</file_id>
    <execution_id>execution ID</execution_id>
  </send_file>
</send_files>

Element name

Description

Remarks

send_files

 

 

send_file

Appears once for every time Send File is executed.

 

file_id

Outputs the transfer name of the file that was sent.

 

execution_id

Outputs the unique identifier that is issued for each execution of the send processing.

Outputs null if the execution of Send File fails.

Transaction

Transaction isn't supported.

Parallel Stream Processing

PSP isn't supported.

Available component variables

Component variable name

Description

Remarks

count

The number of times Send File was executed successfully is stored.

  • The default value is null.

message_category

When an error occurs, the category of the message code corresponding to the error is stored.

  • The default value is null.

message_code

When an error occurs, the code of the message code corresponding to the error is stored.

  • The default value is null.

message_level

When an error occurs, the severity of the message code corresponding to the error is stored.

  • The default value is null.

error_type

When an error occurs, the error type is stored.

  • The default value is null.

  • The format of the error type is as shown below.

    Example: java.io.FileNotFoundException

error_message

When an error occurs, the error message is stored.

  • The default value is null.

error_trace

When an error occurs, the trace information for the error is stored.

  • The default value is null.

Message codes, exception messages, and limitations

Connector

Message code

Exception message

Limitations

Messages and limitations of the HULFT connector

check

check

check