3.4.1 Registering transmission information onto a transmission card
You register transmission information onto a transmission card.
This subsection describes two methods, one that uses the Registration And Execution Of Transmission Requests window and one that uses the ftsregc command. Alternatively, you can edit an existing transmission card and register it as a new transmission card.
- Organization of this subsection
(1) Using the Registration And Execution Of Transmission Requests window
To register transmission information onto a transmission card:
-
In the Registration And Execution Of Transmission Requests window, from the Edit menu, choose Register, or select an existing transmission card, and then from the Edit menu, choose Register.
The Register Transmission Information dialog box appears.
Figure 3‒9: Register Transmission Information dialog box -
Specify the items and then click Register.
You can register multiple sets of transmission information until you click Cancel.
-
After you have finished with the registration, click Cancel.
The following table lists and describes each item in the Transmission Information dialog box.
Item |
Setting |
---|---|
Transmission card name ((1 to 20-byte character string)) |
Specifies a name for the transmission information. If you link to JP1/AJS3, make sure that the specified transmission card name does not contain any spaces. This item is mandatory. |
Remote host name ((1 to 256-byte character string)) |
Specifies the host name or IP address of the remote host. When you specify an IP address, you can specify an IPv4 or IPv6 address. This item is mandatory. |
Port number ((1 to 65,535)) <<21>> |
Specifies the port number of the remote host. If this item is omitted, 21 is assumed.
|
Remote user name ((1 to 80-byte character string)) |
Specifies the name of the login user at the transmission target. This must be a login user name that has been registered. This item is mandatory. |
Password ((0 to 80-byte character string)) |
Specifies the password registered for the login user. If the password was omitted during the registration process, leave this item blank. |
Send/receive type |
Specifies the transmission type:
|
Transmission mode |
Specifies the transmission mode according to the file to be transmitted.
|
Size check |
Specifies whether to check the size of a transmitted file for errors after file transmission. If a file's transmission data size does not match between the sending and receiving ends, a transmission error results. For the size check to be enabled, the remote FTP host must be JP1/FTP (version 06-00 or later) or uCosminexus Service Platform (version 08-53 or later). |
Output type |
Specifies how to output files after transmission:
|
Compression mode |
Specifies whether to compress the transmitted files. About the compression specification:
|
Single/Multiple-file transmission |
Specifies whether transmission is to be of a single file or multiple files.
|
Local file name |
Specification depends on the transmission type, as described below. This item is mandatory.
If you send multiple files, specify a directory for the remote file name. If the specified directory contains a file with the same name as the local file name, that file will be overwritten. If there is no file with the same name, a new file will be created. If Single/Multiple-file transmission is set to Automatic switch or Multiple-file, no wildcard character can be used in the specification of a directory name. If a directory name contains a wildcard character, you must set Single/Multiple-file transmission to Single-file.
|
Remote file name |
Specification depends on the transmission type, as described below. This item is mandatory.
If you receive multiple files, specify a directory for the local file name. Files with the same names as the remote files will be created in the specified directory.
|
Program to start at normal end ((0 to 256-byte character string)) |
Specifies the full path name of a program to start automatically at the client when transmission terminates normally. You can also specify arguments to pass as transmission information to the program when the program starts. For details about the arguments, see Parameter keywords in 3.3.1 Registering auto-start programs. |
Program to start at abnormal end ((0 to 256-byte character string)) |
Specifies the full path name of a program to start automatically at the client when transmission terminates abnormally. You can also specify arguments to pass as transmission information to the program when the program starts. For details about the arguments, see Parameter keywords in 3.3.1 Registering auto-start programs. |
FTP command ((0 to 300-byte character string)) |
Specifies an FTP command to be executed prior to transmission after connection is established with the host. To specify multiple commands, separate them with a semicolon (;). Example: CWD /home/user1;SITE xxxx You can specify only commands that do not establish a data connection. Whether the specified commands can be executed at the FTP server depends on the FTP server. When the FTP server is JP1/FTP:
About the specification of FTP commands:
|
Comment ((0 to 80-byte character string)) |
Specifies any comment. Because the comment is displayed in the log information, this option is useful for setting a memo about the transmission. A comment is not passed to the transmission target. |
- Note about the specification of "Program to start at normal end" and "Program to start at abnormal end"
-
If an argument contains the character \, be aware that some programs might interpret this character as an escape symbol.
- Standard input/output
-
The standard input/output is closed. You can allocate the standard input/output to files. For details, see the JP1FTS_AUTO_STDIO environment variable listed in Table 3-2 in 3.1.3 Using environment variables to define a JP1/FTP environment.
- Environment for the process
-
The JP1/FTP daemon environment is used, not the environment of the user executing the transmission.
- How to start programs when multiple files are transmitted
-
If a wildcard is used to transmit multiple files, an auto-start program is started as many times as there are file transmissions. Information is inherited to the auto-start program separately for each transmission. The transmission information cannot all be inherited to the auto-start program at once.
(2) Using the ftsregc command
The following figure shows an example of using a command to register new transmission information:
- This example registers the following information:
-
-
-TC: The transmission card name is card1.
-
-TH: The connection-target host name is host1.
-
-TU: The login user name is accounting.
-
-TT: The send/receive type is SEND.
-
-TY: The transmission mode is BINARY.
-
-TL: The local file name is /temp/file1.
-
-TR: The remote file name is /temp/file2.
-
The following figure shows an example of a command that registers transmission information using an existing transmission card:
- This example registers the following information:
-
-
The name of the existing transmission card that is being used is card1.
-
-TC: The name specified for the new transmission card is card2.
-
-TH: The connection-target host name is host1.
-
-TU: The login user name is accounting.
-
-TT: The send/receive type is SEND.
-
-TY: The transmission mode is BINARY.
-
-TL: The local file name is /temp/file1.
-
-TR: The remote file name is /temp/file2.
-
For details about the ftsregc command, see ftsregc - registers, changes, deletes, and displays transmission information in 6. Commands.