Send text options (i5/OS and OS/400)

Options include:

ASCII

Use this option for text files and for files that you want to be converted from ASCII to EBCDIC. This is valid for SBCS languages, Traditional Chinese, and Korean. PC 1-byte codes are converted into EBCDIC codes. For DBCS, inserts shift in/shift out (SI/SO) characters into DBCS fields.

JISCII

This option is valid for Japanese DBCS sessions only and converts 1-byte codes to EBCDIC and 2-byte codes to IBM Kanji. JISCII inserts shift in/shift out (SI/SO) characters into DBCS fields.

UNICODE (encoding)

This option lets you send text files (saved in UNICODE) to the host and converts the data from UNICODE to EBCDIC. You can specify either UCS2 or UTF8 as the encoding option. If neither is specified, the default, UCS2, is used.

CRLF

Carriage Return and Line Feed. CRLF (x'0D0A') is removed from the end of each line. EOF (x'1A') is removed from the end of a file.

NOSO

This option is valid only for DBCS and only when used with the JISCII or ASCII option. NOSO prevents the conversion of SO (x'0E') and SI (x'0F') before and after the DBCS field. It also prevents the conversion of RS (x'1E') and US (x'1F') to SO (x'0E') and SI (x'0F').

APPEND

The transferred file will be appended to an existing host file that has the same name, if one exists. If APPEND is not specified, the transferred file overwrites the existing host file.

NEW

The transfer stops if the file already exists. This option can be used to protect against accidentally erasing an existing file.

DSTADDR(dstaddr)

This option specifies the destination address of the host to be used for the file transfer.

USERID(usr)

This option specifies the user ID to be used for the file transfer.

PASSWORD(pwd)

This option specifies the password to be used for the file transfer.

SRC

This option specifies the i5/OS or OS/400 file type to be used for the transfer. If the host file does not exist, then a new file is created with the file type "Source physical file". This option is applicable only for the files in the QSYS library file system.

DTA

This option specifies the i5/OS or OS/400 file type to be used for the transfer. If the host file does not exist, then a new file is created with the file type "Physical data file". This option is applicable only for the files in the QSYS library file system.

 

PROGRESS/NOPROGRESS

When sending or receiving files with Host File Transfer, a file progress indicator displays by default to track the progress of each file transfer.  Host On-Demand now allows you to control whether or not to display the progress indicator with the PROGRESS/NOPROGRESS options described below.

PROGRESS

Indicates that the file progress indicator will be visible for Files being sent or received from the host.

Note: If no option is entered the Progress indicator is visible for the file transfer.

NOPROGRESS

Indicates that the progress indicator will not be visible for the file transfer.

Notes:

• This option can be controlled on a per file definition.  
• If you want the NOPROGRESS option to be the default, enter this option under File Transfer Defaults.
• If an error occurs during the transmission, the File Transfer Status will be displayed.

 

LRECL(n)

This option specifies the logical record length when creating a file on the i5/OS or OS/400 operating system. It can have the following values:

• An integer from 1 through 32766 when Host File Type is set to Source physical file.
• An integer from 1 through 32754 when Host File Type is set to Physical data file.
• It is ignored when Host File Type is set to Save file.

Microsoft Internet Explorer users may see this error message in the java console while transferring files to the i5/OS or OS/400 operating system:

com.ms.SecurityExceptionEx[com/ibm/as400/access/SystemProperties/GetProperty]: Unable to access system property: com.ibm.as400.Trace.category You can ignore this message. If you want to remove the error message from the Java Console, you can update the Windows registry entry My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Java VM\classpath with the Host On-Demand server directory, for example, C:\Program Files\IBM\HostOnDemand\HOD\.