Preface. For details of the new functions, please refer to the operation manual.

Size: px

Start display at page:

Download "Preface. For details of the new functions, please refer to the operation manual."

Griselda Tucker
5 years ago
Views:

2 Preface Thank you for using the HULFT for WindowsNT. The present release incorporates the addition of different new functions, and improvements on the existing functions. This paper explains the functions either added or changed in the HULFT WindowsNT Ver. 2 through Ver List of additional functions : It shows the newly added functions 2. List of improved functions : It states the improved functions among those having been mounted in the old versions. 3. List of incompatibility : It shows the functions changed from those of the old versions, and functions subjected to some restrictions. It also shows incompatibility that occurring in up-versioning to Ver. 5. For up-versioning from Ver. 2, see this section. 4. Communication with HULFT4 : It gives caution details for the mixed existence of Ver. 5 and the old versions in the operation environment. For details of the new functions, please refer to the operation manual. Saison Information Systems Co., Ltd. October 2001

3 1.List of additional functions (1) Multi format transfer If a record having multiple numbers of formats in one file exists, it is possible to transfer the file by designating the record key (e.g. data type) and the format Header Record Data Record1 Data Record1 : Data Record2 Data Record2 Transfer is possible even if multiple formats exist in one file. (2) Multiple file transfer It is possible to transfer multiple numbers of files collectively in one receive or send. It is also possible to have multiple numbers of files of different data types. Host A Host B Join Extract File Transfer File (3) EBCDIC user code conversion table Code conversion can be made according to the definition table set independently by a user, when making the code conversion between ASCII and EBCDIC, in addition to the conventional EBCDIC Kana, EBCDIC Lower case, EBCDIC ASCII, EBCDIC ASPEN, and EBCDIC IBM standard. Up to three user definition tables can be registered. 1

4 (4) Treatment of Shift code when converting code When performing text transfer, format transfer, and Multi format transfer to the mainframe and an office computer, it is possible to select whether or not a shift code is added to full-size characters. (For the format and the Multi format, this is effective when the item type is X or M.) (5) Previous job execution It is possible, when receiving a send request, to activate the job registered in the job activation information. Request Acknowledge Send request DB Pre-send job execution Extracted data Send processing (6) Receive completion notification Since in the old version the file transfer was handled as completed before the post-receive job was activated, it was not possible for the sending side to know the result of the post-receive job. Starting with Ver. 5, it has become possible to select whether the transfer is finished before activation of the postreceive job, or whether the transfer is finished at the time when execution of the post-receive job has been completed, thus making it possible to even know the execution result of the post-receive job. Send Receive P attern1 (previous specifications) Send Log Log output Results Job execution Send Receive P attern2 Send Log Log output Job execution Results 2

5 (7) Remote job execution New functions and incompatibility manual It is possible to activate the job registered in the job execution information in the requested host. HOST A HOST B Execution request JOB-ID Request acknowledge Job execution User application Status Confirmation Status (8) Management information list, related list display ID registered in each management information section used in the HULFT can be displayed in a table. (9) Clearing send queue files when activating the send process If an unsent file exists when the send process is activated, the undistributed file can be deleted. (10) Clearing resend queue files when activating the send process If a file waiting for resend exists when the send process is activated, resend file status file can be deleted. (11) Receive multiplex level setting Load on the machine during receive can be suppressed by setting the receive multiplex. (12) HULFT API provided Affinity with the user application has been enhanced by making such API functions as log retrieval, requests for send and receive, and notification of job status, which are used frequently in the HULFT. Moreover, it is possible to use HULFT API in the application created by Visual Basic or C. (13) UNICODE conversion Utility was added to perform code conversion between SHIFT-JIS and UNICODE. 3

6 (14) Renewal of management screen The management screen has been changed from the single window to the multi-window, making it possible to refer to multiple numbers of management information simultaneously, to set values by using drag and drop, and enhancing greatly the user interface. In addition, different utilities were unified into the management screen, making the unified control possible. (15) Selection of request acknowledge log outputs Contents outputted into the request acknowledge log can be selected by service unit. (16) Display of format information list Contents of the designated format information can be displayed on prompt. (17) Job observation When send has been made, results of the jobs executed in the subsequent job on the receiving side can be referred to from the management screen. (18) Encryption It is possible to encrypt the data when transferring the files. It is also possible to transfer the files without encryption. 4

7 (19) Mail interface The user can be notified of the results of receive/send after the receive/send have been completed. The receive/send files can also be transmitted as attachment files. Receive process Receive thread File Transfer Following job Mail Interface Mail Management file (20) Outputting messages to event log Messages displayed to the console can be outputted to the event log. This function makes it possible to monitor the operation status from WindowsNT in remote areas. Messages outputted to the event log can be selected from three kinds, information, warning and error. 5

8 2.List of improved functions (1) Increase in maximum transfer size In order to achieve improvement in the transfer speed in Ver. 5, improvements of the following items were made: 1. Efficiency improvement in transfer data The maximum value, which multiplied transfer block length by number of transfer blocks, was expanded from 32,767 bytes to 65,520 bytes. 2. Socket buffer size The upper limit for the socket buffer size was increased from 32,767 bytes to 65,520 bytes. (2) Compression for binary transfer Data can now be transferred compressed also when BINARY is selected from Ver. 5 as the transfer pattern, thus making it possible to reduce the transfer time, and decrease traffic on LAN. (3) Transfer of files larger than 2GB Files larger than 2GB can be transferred. (4) Log transfer rate, data size, record count, display digit count extension LAN with 100 Mbps now proliferates, and data size has been increased recently. Therefore, the number of internal digits and number of indication digits has increased so that no size errors can occur even if the HULFT is used under these environments. (5) Dynamic use of external character table In preparing the external character conversion exit routine with the old version, a source code for the exit routine should have been prepared, requiring building work called compilation. Starting with Ver. 5.0, building work is no longer necessary by using the external character table file, allowing the external character conversion to be made easily. The external character conversion table registration work also uses the control screen, facilitating the registration. (6) Registration of all management information comments The comment input domain was added to the transfer group information and the format information. (7) Improvement in processing of binary 8 byte data during CSV conversion When performing the CSV conversion with the old version, the data of binary 8 bytes were converted once to the floating decimal point, which tended to cause an error. In Ver. 5, this processing has been improved so that no error will occur. 6

9 (8) Improvement in processing of tab code conversion New functions and incompatibility manual When transferring tab codes (0x09) to a general purpose computer or an office computer using the old version, the codes were converted into the space (0x40). In Ver. 5, it is possible to perform conversion into codes other than the space by combining the codes with the user code tables. (9) Specifying wildcards in the management information parameter file creation command Wild cards can be designated during ID by using the management information parameter file preparation command (utligen. exe). (10) Increase of maximum number of hosts in transfer group In the old version, the maximum number of hosts that could be registered in the transfer group information was 48. In Ver. 5, it has been expanded to 1000 hosts maximum. (11) Lock control for data receive file In the case where a receive file is being used in another process, retry can be performed by setting the number and interval of the open retry. (12) Control of SYSLOG file It will become possible to set the maximum value for the SYSLOG file. File sizes can be controlled even without performing deletion of the SYSLOG file after the HULFT has been shut down, as has been done conventionally. (13) Selection of automatic module start-up In the old version, in cases where the automatic activation of a module was selected, all the modules such as data send, receive, and request acknowledge were activated. In Ver. 5, a module that is required to be activated can be selected. (14) Setting accounts to processes Because setting the accounts has become possible to each process such as send and receive, the network drive can be utilized even under conditions where the Allow service to interact with desktop in setting the service. 7

10 3.List of incompatibility (1) Change of file formats The formats for the following control and log files were changed. Therefore, conversion work is required before use. For the conversion work, refer to the Conversion_manual. pdf in the document folder. - Send log file - Receive log file - Receive information file (2) Error codes Error codes have been added. For details of the error codes, refer to the Appendix 3: Error Codes in the HULFT common operation manual. (3) External character exit routine In the old version, building work for the execution file was required if a external character exit routine was added. In Ver. 5, the building work has been eliminated by preparing a external character conversion table file. Therefore, if the external character exit routine is used, conversion work is required to convert it into the external character conversion table file. For the conversion method, refer to the Conversion_manual. pdf in the document folder. (4) Internet connection If the HULFT V5 is introduced, files cannot be transferred by using the HULFT FireWall Ver. 1. If there is a schedule to introduce or up-version to the HULFT Ver. 5 in any one of the HULFT that goes through the HULFT FireWall, up-version the HULFT FireWall too into Ver. 5. [Comment] The HULFT FireWall Ver. 5 also supports transfer among the HULFT Ver. 4. Incompatibility will not occur when up-versioning from the HULFT FireWall Ver. 1 to Ver. 5. * The English edition of the HULFT FireWall is not provided. (5) Connection from HULFT Manager of Ver. 2 or earlier Connection from HULFT Manager of Ver. 2 or earlier is not supported. It is necessary to up-version the HULFT Manager to Ver. 5. (6) Subsequent jobs When job activation after receive or send has failed, no output has been made to the log file. In the HULFT V4 or HULFT V5, output is made to the log file in such a case as no designated job ID existing in the job execution information. In this case, date, hours, and others are all 9. 8

11 (7) Receive/send status display The contents displayed by the status display command (utlsdisp, ultrdisp) of the receive/send system have been changed. For the contents that are displayed, refer to the operation manual. (8) File size check at resend request If the size of a send file in the previous error recorded in the resend waiting list file at the resend request differs from the size of a send file that is going to perform resend, the resend processing is an error. (9) Setting send unit The send thread finish timing has been changed to prior to execution of the job after send as default value. In addition, it is possible to select whether the send thread finish timing is before execution of the job after send, or after the job has been completed, by setting the system operation environment. (10) Setting HULPATH The HULPATH has been set to the environment variable of the system. Starting Ver. 5, the HULPATH is described in the INI file. The file name is %Windir% HULFT. INI. (11) Locking data receive file Locking has been processed as an error in the receive with the old versions, if the receive file is in use. With Ver. 5, it has become possible to select whether to wait until it is opened if the receive file is in use in the HULFT processing, or to deal with it as an error immediately. If a user application other than the HULFT is using the receive file, an opening process is performed based on Retry Count on Open receive file and Retry Interval Open receive file, and if it is opened during that processing, the processing shall be continued, and if it is not opened, the processing shall be treated as an error. (12) Number of CSV display digits With the number of display digits specified in the HULFT V4, there have been cases when it was not possible to display the digits if decimals were included. Therefore, the HULFT V5 has improved the specified number of display digits. For the difference in the specified number of display digits, for HULFT4 refer to the CSV Format Receive Environment Settings(Target) of the [HULFT System Operation]-[Receive Process]-[ Receive Process Description]-[CSV Format Receive] in the on-line help, and for HULFT5, refer to the Common operation manual

12 4. Communication with HULFT4 1) The following is an explanation of how new functions operate in environments in which both HULFT 4 and HULFT 5 exist in combination. Send Receive HULFT5 HULFT4 Binary compression Transferred without compression Multi format Successful job completion Cannot be specified HULFT5 Remote job execution Cannot be specified Previous job Transfer block size Send file size Shift code treatment Only on the sending side Binary compression Cannot be specified Cannot be specified Multi format Cannot be specified Cannot be specified Successful job completion Cannot be specified HULFT4 Remote job execution Cannot be requested Cannot be requested Previous job Cannot be specified Cannot be specified Transfer block size Cannot be specified Cannot be specified Send file size Shift code treatment Cannot be specified Cannot be specified (1) Binary compression When specifying data transfer by binary compression to a lower level version, transfer is executed without binary compression. (2) Multi format transfer When specifying multi-format transfer to a lower-level version, a version error is returned and the transfer is not executed. (3) Successful job completion The function of receive completion notification for transfers from lower-level versions operates normally. If successful job completion is specified, notification of the completion of the transfer is sent at the time of successful job completion. (4) Remote job execution When specifying remote job execution to lower-level versions, it is indicated as service not registered at the source host and the job is not executed. 10

13 (5) Previous jobs New functions and incompatibility manual When sending to lower-level versions, a pre-send job is executed at the time of send request acknowledge from the lower-level version. (6) Transfer block size When specifying the value, which multiplied transfer block length by transfer block count is greater than 32,767, a version error is returned and the transfer is not executed. (7) Send file size When sending a file larger than 2GB to a lower-level version, a version error is returned and the transfer is not executed. The transfer of files larger than 2GB from lower-level versions is not supported. (8) Shift code treatment When the treatment of Shift code to lower-level versions is set to be cut and data is transferred with the receiving host conversion, a version error is returned and the transfer is not executed. 2) HULFT FireWall File transfer via the HULFT FireWall Ver. 1 is not possible. If even one Ver. 5 is included in the HULFT that goes through the HULFT FireWall, the HULFT FireWall must also be up-versioned to Ver. 5. * The English edition of HULFT FireWall is not provided. 11

Revision Upgrade Notification

[Product List] Revision Upgrade Notification Product Name Version HULFT for Windows Type WIN2-E 6.3.5 [Target OS] Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008 [Function