HULFT saves the file after the sending ends successfully. Lock the file while sending is in progress. HULFT deletes the file after the sending ends successfully. After the sending ends successfully, HULFT clears the file and the size of the file becomes 0 bytes. Keep (K):ĭo not lock the file while sending is in progress. Specify the mode for exclusive control of the Send file applied during the sending, and the handling of the file in the case where the sending ends successfully. This setting is valid when the host on the receiving side is a Type MF-IBMi host and you specify sending-side conversion. Omitting this field sets 'Autoconfiguration' (0). Specify the EBCDIC Set for the receiving-side host (remote host). Specify Type-EBCDIC Code Set that is used for the conversion of single-byte codes Send the file without carrying out code conversion EBCDIC Set (CODESET) Specify the option for code conversion of the send target file Sending Side (S):Ĭarry out code conversion on the host on the sending side Receiving Side (R):Ĭarry out code conversion on the host on the receiving side No Conversion (N): This field can be set only if 'DEFLATE' (3) is specified for Compression Preference. When Transfer Type is set to "BINARY" (B) and Compression Preference is set to "Vertical" (2)Ĭompression level for DEFLATE compression When Transfer Type is set to "BINARY" (B) and Compression Preference is set to "Horizontal" (1) You cannot omit this field in the following cases: The higher the value, the faster the processing speed (however, if you set a higher value, compression will require more memory). Processing unit of records when compressing binary files Compression Preference (COMP)Ĭompression type that is used when a file is transferred None (N):ĭEFLATE compression Compression Unit (COMPSIZE) When Transfer Type is specified as 'FORMAT' (F), the format ID is mandatory, and when Transfer Type is specified as 'MULTIFORMAT' (M), the multi format ID is mandatory. ID of the record in which the format or formats of the Send file is registeredįor details on format IDs, refer to Format Information.įor details on multi format IDs, refer to Multi Format Information. Multi format data Format/Multi Format ID (FMTID) ![]() ![]() Transfer Type (TRANSTYPE)ĭata type of the file to send FORMAT (F): For details, refer to the explanation of networked files in Administration Manual. In HULFT8 Server grade environments, you can specify a file that uses network resources. Specify a file to send (called Send file, or send target file) that is stored on a Windows operating system. This type of cipher key must be set when Forced Strong Key Mode (strongkeymode) is set to "Enabled (1)" in the System Environment Settings. This type of cipher key can be set when Forced Strong Key Mode (strongkeymode) is set to "Disabled (0)" in the System Environment Settings. When you do not specify this field, the default value will be set.Īvailable only when Transfer Type (TRANSTYPE) is set to 'FORMAT' (F) or 'MULTIFORMAT' (M). ![]() ![]() (when Forced Strong Key mode is enabled) (*5)įor the HULFT Management Console, click a setting value on the pulldown list.įor the HULFT Management Console, click a setting value on the pulldown list. (when Forced Strong Key mode is disabled) (*4) Table 2.1 List of Send Management Information Fields Optional fields and mandatory fields for registration by running commands with parameter files may differ from those for registration using the HULFT Management Console.įor details on optional fields and mandatory fields for the registration by running commands with parameter files, refer to Management Information Batch Registration command. In the table below, the check marks in the Optional column indicate the fields considered optional during registration from the HULFT Management Console.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |