revision upgrade notification - hulft...search a log file of which size is 4g bytes or larger from...

HULFT for Windows Ver.6.3.5

Revision Upgrade Notification

[Product List]

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 Improvements] ○ HULFT

M/ment No. Contents Target Ver.

146 Improvement in the read processing speed of the Send Control file From 6.1.1B

to 6.3.4

176 Improvement in the result output processing of the Joined File Break command(utlbreak) and the Joined File Display command(utldspfil)

From 5.0.5to 6.3.4

190 Improvement in the Log Search function API(hulrlog) to be able to search a log file of which size is 4G bytes or larger

From 5.0.5to 6.3.4

191 Improvement in the log list display commands to be able to output and display log files of which size is 2G bytes or larger

From 5.0.5to 6.3.4

192 Improvement in the Multiple Receive File Data Extract command(utlstore) to be able to output additional content, even when the size of the output file exceeds 4G bytes

From 5.0.5to 6.3.4

193 Improvement in the Job Execution Result Notification command(hulsndrc) to be able to output additional content, even when the size of the Job Notification Log file exceeds 4G bytes

From 5.0.5to 6.3.4

[Bug List] ○ HULFT • C on omm


506 The signed part in the S type data(signed external decimal data) is not checked.

From 6.1.1Bto 6.3.4

• HULFT Service M/ment No. Contents Target Ver.

370 Failure in backing up the Console Log clears the existing Console Log. From 5.0.5to 6.3.4

494

When failing to write to the Console Log, HULFT either outputs the message to event log in a different manner from the specification in the ‘Output to Event Logs(eventlog)’ or even does not output the event log in some cases.

From 5.0.5to 6.3.4

513 When the size of the Console Log file exceeds 4G bytes, HULFT overwrites to prepend additional content onto the log file.

From 5.0.5to 6.3.4

HUL6-PC-HULE-005-E-01 Saison Information Systems CO.,LTD. 1/29


• Send Function


486

While having specified ‘1: Use other encryption scheme’ for the ‘Encryption Scheme(ciphertype)’ in the System Environment Settings, specifying ‘Binary’ for the ‘Transfer Type’ and selecting either ‘Horizontal’ or ‘Vertical’ for the ‘Compression Level’ in the Send Management Information leaks memory in some cases, when sending.

From 6.1.1Bto 6.3.4

497

Multiple sending of the File ID of which specification of the ‘Send File Mode’ in the Send Management Information is ‘Delete’ together with other File IDs that can execute sending normally may cause abnormal termination of the Send process in some cases.

From 6.1.1Bto 6.3.4

514

When failing to clear a Send file, HULFT terminates abnormally in some cases, despite of the setting ‘1: Handle it as a normal end and execute the successful job’ in the ‘Send Transfer Error Recovery(enderrmode).’

From 6.1.1Bto 6.3.4

515 Activating the Send process while having many unsent files placed on the Resend Queue causes abnormal termination of the Send process in some cases.

From 6.3.2to 6.3.4

• R ve Function eceiM/ment No. Contents Target Ver.

499 Despite the presence of the invalid value(NULL) in data, receiving the Multi Format Transfer of which Field Type includes any of X, M, or N type in CSV format is not treated as an error.

From 5.0.5to 6.3.4

521 When the receiving of the file of which size is 4G or larger in the CSV format is carried out, HULFT ends in error in some cases.

From 5.0.5to 6.3.4

525 When the transfer of the Receive file of which file size is 1 byte smaller than 4G(namely, 42,949,672,965 bytes) is carried out, HULFT ends in error in some cases.

From 5.0.5 to 6.3.4

• R st Acknowledge Function equeM/ment No. Contents Target Ver.

493 When HULFT fails to open the Mail Interface Information file, memory leaks.

From 5.0.5 to 6.3.4

510

When the Post-receive Job Result Inquiry Request(HULJOB) is issued for a transfer of which log record count in the job execution log at the receiving side is 0, Error code 741 is set in the Request Acknowledge Log.

From 6.3.2to 6.3.4

519

Registering a character string that includes ‘=’ for the ‘Title’ on the Mail Interface Information Update screen and reopening the update screen displays either the ‘Title’ that is left blank or the ‘Title’ without ‘=.’

From 5.0.5to 6.3.4



• U tility


419 When the Multiple File Join command(utljoin) is executed, an output file is created despite the absence of the available input file.

From 5.0.5to 6.3.4

487 An error occurs in some cases when a leap-year date(20080229 and the like) is specified for the parameter of date of the targeted list display(-from, -to) in the Send and Receive Log List Display command.

From 5.0.5 to 6.3.4

488 At the time of executing the Send File command(utlsend), when HULFT fails to read the System Environment Settings(hulenv.cnf), ‘0’(Normal end) is set to the Status code, though it is supposed to be an error.

From 6.1.1Bto 6.3.4

490

While having already started or terminated HULFT service, when ‘-c start’ or ‘-c stop’ is specified for the parameter of HULFT Startup/Termination command(utlsvcctl) and then execute it, an error does not occur.

From 6.3.2to 6.3.4

491

Specifying the parameter of ‘-m delete’ in the Service Registration/Deletion command(utlservice) without having stopped HULFT service is supposed to cause an error, however HULFT contrarily sets ‘0’(Normal end) to the Status code.

From 5.0.5to 6.3.4

507 When HULFT fails to secure memory at the time of executing the Send File command(utlsend), inappropriate error message, which is different from the message of the failure in securing memory, is displayed.

From 6.1.1Bto 6.3.4

511

When characters are specified in the parameters of which valid value is numeral in the Unsent Status Queue Change command(utlschange), the Multiple Receive File Data Delete command(utlstore), and the Alert Notification command(utlalert), an error does not occur.

From 5.0.5to 6.3.4

526 A parameter error does not occur in spite of specifying a parameter of the synchronous transfer( -sync) of the Send File command up to the letter ‘s’ that is followed by any characters other than ‘ync.’

From 6.1.1Bto 6.3.4

• M ement Screen anagM/ment No. Contents Target Ver.

508 Pressing [Receive Side Job] on the Send Detail Information Inquiry screen clears the displayed contents in some cases.

From 6.3.2 to 6.3.4

528 On the Mail Interface Information List screen, when HULFT fails to open the Mail Interface Information file, memory leaks.

From 5.0.5to 6.3.4

529


From 5.0.5 to 6.3.4

• Installer M/ment No. Contents Target Ver.

522 When single-byte spaces are included in the specification of the installation folder, HULFT fails to start up service in some cases.

From 6.3.2to 6.3.4

• Others M/ment No. Contents Target Ver.

459 With insufficient system resources, when the Send/Receive and the Request Acknowledge processes are continuously being carried out, the CPU Usage for the processes reaches 100% in some cases.

From 5.0.5to 6.3.4



“Target Version”

If the “Target Version” includes Ver.5, the improvement or measure for the bugs may have been provided as a revision upgrade of HULFT Ver.5. Otherwise, a measure will be taken in the future.

For more information about the improvements and bugs, refer to the following improvement report and bug report.



[Improvement Report] ○ HULFT

146 Improvement in the read processing speed of the Send Control file

In the issuance of the same number of Send File, the transfer processing time when issuing single Send File at a time one after another takes longer than the processing time when issuing multiple Send File at a time.

Example)


Multiple Send File Acknowledged at a time

100 + 100

Total count: 200

Transfer Processing Time

Send Acknowledge thread A

Send Acknowledge thread A

Transfer Processing Time

100 transfers completed ↑


Send Acknowledge thread B

Total count: 100


Single Send File Acknowledged at a time

In normal operation, transfer processing time of 100 transfers of single Send File acknowledged at a time is now shorter than the processing time of 200 transfers of multiple Send File acknowledged at a time, because the number of the former is smaller than the latter. Therefore, the transfer process time is shortened. The read processing time of the Send Control file(sddreqcp.dat) when acknowledging single Send File at a time has been improved. Accordingly, the transfer processing time is now in proportion to the number of Send File that is acknowledged, regardless of the multiplex level of the acknowledgement of Send File.

176 Improvement in the result output processing of the Joined File Break command(utlbreak) and the Joined File Display command(utldspfil)

When the result output of the Joined File Break command(utlbreak) and the Joined File Display command(utldspfil) are redirected to be output to files, the output contents used to be truncated in the middle in some cases. This improvement allows HULFT to output the contents without truncation even at the time of redirection.


190 Improvement in the Log Search function API(hulrlog) to be able to search a log file of which size is 4G bytes or larger

The Log Search function API(hulrlog) has been improved to be able to search a log file of which size is 4G or larger.

191 Improvement in the log list display commands to be able to output and display log files of which size is 2G bytes or larger

With this improvement, log files of which size is 2G bytes or larger can be output and displayed with the following log list display commands: According with this improvement, the Status code of each command is changed. • Send and Receive Log List Display command(utllist)

When the file size of the Send log or Receive log is 0 byte, the error message and the Status code are changed as follows: Before) utllist: The specified file does not exist. (Status code: 109) After) utllist: The relevant data does not exist. (Status code: 81)

• Request Acknowledge Log List Display command(utlobslist) When the file size of the Request Acknowledge Log list is 0 byte, the error message and the Status code are changed as follows: Before) utlobslist: The specified file does not exist. (Status code: 109) After) utlobslist: The relevant data does not exist. (Status code: 81)

192 Improvement in the Multiple Receive File Data Extract command(utlstore) to be able to output additional content, even when the size of the output file exceeds 4G bytes

In this improvement made to the Multiple Receive File Data Extract Command(utlstore), additional content can be output by specifying –m parameter, even when the output file size of the data to be extracted specified by –o parameter exceeds 4G bytes.

193 Improvement in the Job Execution Result Notification command(hulsndrc) to be able to output additional content, even when the size of the Job Notification Log file exceeds 4G bytes

The Job Execution Result Notification command(hulsndrc) has been improved to be able to output additional content, even when the size of the Job Notification Log file of the Job Execution Result Notification command(hulsndrc), which is defined in the Request Acknowledge Definition file(service.dat), exceeds 4G bytes. *Any designation can be specified as the name of the Job Notification Log file. The default name is ‘hulsndrc.dat.’



[Bug Report] ○ HULFT • Common

506 The signed part in the S type data(signed external decimal data) is not checked.

[1] Phenomenon

With ‘MODE 9’ set to the ‘Pack Zone Conversion’ in the System Environment Settings, at the time of either the Format Transfer or the Multi Format Transfer, the transfer ends normally, despite invalid signed part included in the S type data.

[2] Target Version

Ver. 6.1.1B to 6.3.4 [3] Occurrence condition

[Sending] This phenomenon occurs when all of the following conditions are fulfilled: • ‘MODE9’(pschg=9) is set to the ‘Pack Zone Conversion’ in the System Environment

Settings. • Either ‘FORMAT’ or ‘MULTIFORMAT’ is set to the ‘Transfer Type’ of the Send

Management Information. • Invalid signed part is included in the S type data. • ‘Sending side’ is set to the ‘Code Conversion’ of the Send Management Information.

[Receiving] This phenomenon occurs when all of the following conditions are fulfilled: • ‘MODE9’(pschg=9) is set to the ‘Pack Zone Conversion’ in the System Environment

Settings. • Either ‘FORMAT’ or ‘MULTIFORMAT’ is set to the ‘Transfer Type’ of the Send

Management Information. • Invalid signed part is included in the S type data. • ‘Receiving side’ is set to the ‘Code Conversion’ of the Send Management Information.

[4] Alternate method

None [5] After modification

The signed part in the S type data is checked, and the transfer ends abnormally if the signed part is invalid. The Status codes of the abnormal end are as follows: • For the sending side conversion;

452: An error occurred during code conversion for data. • For the receiving side conversion;

408: An error occurred during code conversion for received data.



• HULFT Service

370 Failure in backing up the Console Log clears the existing Console Log.

[1] Phenomenon

When backing up the Console Log(hulcon.log) fails, the Console Log is cleared without returning any error messages.

[2] Target Version

Ver. 5.0.5 to 6.3.4 [3] Occurrence condition

This phenomenon occurs when all of the following conditions are fulfilled: • ‘1: Back up the log file’ is set to the ‘Console Log Backup’ in the System Environment

Settings. • The Console Log is in a state where the backup process fails (such as the access

permission to the file is not granted.) [4] Alternate method


When backing up the Console Log fails, HULFT does not clear the existing Console Log but adds the following message to the Console Log:

‘X002130 Backup of SYS log failed.’



494 When failing to write to the Console Log, HULFT either outputs the message to event log in a different manner from the specification in the ‘Output to Event Logs(eventlog)’ or even does not output the event log in some cases.

[1] Phenomenon

When an error occurs at the time of writing to the Console Log, the content of the error message used to be overwritten by the message of X002060. For this reason, whether to output to the event log has been determined in a different manner from the specification in the ‘Output to Event Logs’ in the System Environment Settings.

Example)

Where an error occurred during the output of the error message ‘I010212 Starting service,’ while having specified ‘eventlog=100’ for the ‘Output to Event Logs’:

The content of the message is overwritten by X002060, which prevents the message from being output, because the flag for the message level ‘X’ has been set to ‘0: Do not output to event logs’ in the ‘Output to Event Logs,’ at the point of outputting to the event Log.

In normal operation, where the message level is ‘I’ and ‘1: Output to event logs’ is specified for the ‘Output to Event Logs,’ the message is output to the event log.

[Remarks] In HULFT, error messages are classified into the following levels: I: Information

W: Warning E: Error X: Critical Error

[2] Target Version


• The following are some patterns where the error message(X002060) is output, despite the specification not to output to the Event Log in the System Environment Settings:

• Where outputting the error message ranked ‘I’ to the Console Log is failed; Either ‘001’ or ‘011’ is specified for the ‘Output to Event Logs(eventlog).’

• Where outputting the error message ranked ‘W’ to the Consol Log is failed; Either ‘001’ or ‘101’ is specified for the ‘Output to Event Logs(eventlog).’

• The following are some patterns where the error message is overwritten by the content of X002060, despite the specification to output to the Event Log in the System Environment Settings:

• Where outputting the error message ranked ‘I’ to the Console Log is failed; Either ‘101’ or ‘111’ is specified for the ‘Output to Event Logs(eventlog).’

• Where outputting the error message ranked ‘W’ to the Console Log is failed; Either ‘011’ or ‘111’ is specified for the ‘Output to Event Logs(eventlog).’

• Where outputting the error message ranked ‘E’ or ‘X’ to the Console Log is failed; Either ‘001,’ ‘011,’ ‘111,’ or ‘101’ is specified for the ‘Output to Event Logs(eventlog).’



• The following are some patterns where the error message is not output, despite the

specification to output to the Event Log in the System Environment Settings: • Where outputting the error message ranked ‘I’ to the Console Log is failed;

Either ‘100’or ‘110’ is specified for the ‘Output to Event Logs(eventlog).’ • Where outputting the error message ranked ‘W’ to the Condole Log is failed;

Either ‘010’ or ‘110’ is specified for the ‘Output to Event Logs(eventlog).’



The event logs are output in the same manner specified in the ‘Output to Event Logs’ in the System Environment Settings.



513 When the size of the Console Log file exceeds 4G bytes, HULFT overwrites to prepend additional content onto the log file.

[1] Phenomenon

While outputting the Console Log, when the file size exceeds 4G bytes, HULFT does not append the additional content but overwrites the log file to prepend the content onto the file.

[2] Target Version

Ver.5.0.5 to 6.3.4 [3] Occurrence condition

This phenomenon occurs when the file size of the Console Log exceeds 4G bytes. [4] Alternate method


HULFT now appends the additional content, even when the file size of the Console Log exceeds 4G bytes.



• Send Function

486

While having specified ‘1: Use other encryption scheme’ for the ‘Encryption Scheme(ciphertype)’ in the System Environment Settings, specifying ‘Binary’ for the ‘Transfer Type’ and selecting either ‘Horizontal’ or ‘Vertical’ for the ‘Compression Level’ in the Send Management Information leaks memory in some cases, when sending.

[1] Phenomenon

While having specified ‘1: Use other encryption scheme’ for the ‘Encryption Scheme(ciphertype)’ in the System Environment Settings, specifying ‘Binary’ for the ‘Transfer Type’ and selecting either ‘Horizontal’ or ‘Vertical’ for the ‘Compression Level’ in the Send Management Information to execute sending causes memory leak when the Encryption/Decryption function(hul_usrcipher) returns an error.

[2] Target Version

Ver.6.1.1B to 6.3.4 [3] Occurrence condition

This phenomenon occurs all of the following conditions are fulfilled: • ‘1: Use other encryption scheme’(ciphertype=1) is set to the ‘Encryption Scheme’ in the

System Environment Settings. • ‘BINARY’ is set to the ‘Transfer Type’ of the Send Management Information. • ‘Horizontal’ or ‘Vertical’ is set to the ‘Compression Level’ of the Send Management

Information. • When sending, the Encryption/Decryption function(hul_usrcipher) returns an error.



The memory leak does not occur, even when all of the above mentioned occurrence concisions are fulfilled.



497

Multiple sending of the File ID of which specification of the ‘Send File Mode’ in the Send Management Information is ‘Delete’ together with other File IDs that can execute sending normally may cause abnormal termination of the Send process in some cases.

[1] Phenomenon

While the Send files have been under exclusive control by the mutex object, sending the File ID of which specification of the ‘Send File Mode’ in the Send Management Information is ‘Delete’ together with other File IDs that can execute sending normally may cause abnormal termination in the Send process, which outputs any of the following messages:

‘X308006 (288) Error occurred when canceling lock on unsent file. (When delete failed)’

‘X308006 (6) Error occurred when canceling lock on unsent file. (When delete failed)’

‘X308002 (6) Error occurred when writing unsent file.’

‘E340005 Unable to lock resend list file. (Host Name of Send Destination =*** file ID=***)’

‘E334006 Reading of the Send file failed. (Host Name of Send Destination=*** file ID=***)’

(Error code==702,00006) [2] Target Version


This phenomenon occurs when multiple sending with other File IDs that can execute sending normally is carried out while all of the following conditions have been fulfilled: • ‘Deletion’ is set to the ‘Send File Mode’ of the Send Management Information. • The Send file specified in the above Send Management Information is exclusively

controlled by the mutex object. [4] Alternate method


The abnormal termination does not occur, even when all of the above mentioned occurrence conditions are fulfilled.



514 When failing to clear a Send file, HULFT terminates abnormally in some cases, despite of the setting ‘1: Handle it as a normal end and execute the successful job’ in the ‘Send Transfer Error Recovery(enderrmode).’

[1] Phenomenon

Failure in clearing a Send file handles the state as an abnormal termination and executes the unsuccessful job in some cases, despite the specification of ‘1: Handle it as a normal end and execute the successful job.’

[2] Target Version


This phenomenon occurs when all of the following conditions are fulfilled: • ‘Clear’ is set to the ‘Send File Mode’ of the Send Management Information. • ‘1: Handle it as a normal end and execute the successful job’(enderrmode=1) is set to the

‘Send Transfer Error Recovery’ in the System Environment Settings. • Clearing the Send file fails.



HULFT now ends the process normally and executes the successful job.

515 Activating the Send process while having many unsent files placed on the Resend Queue causes abnormal termination of the Send process in some cases.

[1] Phenomenon

With specifying ‘0: Do not delete’ for the ‘Clear Unsent File(delreqcpfile)’ in the System Environment Settings, activating the Send process while having many unsent files placed on the Resend Queue causes abnormal termination of the Send process in some cases.

[2] Target Version


This phenomenon occurs when all of the following conditions are fulfilled: • ‘0: Do not delete’(delreqcpfile = 0) is set to the ‘Clear Unsent File’ in the System

Environment Settings. • The number of unsent files is 298 or more.



The Send process does not end abnormally, even when the Send process is activated under the above mentioned occurrence conditions.



• Receive Function

499 Despite the presence of the invalid value(NULL) in data, receiving the Multi Format Transfer of which Field Type includes any of X, M, or N type in CSV format is not treated as an error.

[1] Phenomenon

Despite the presence of the invalid value(NULL) in data, receiving the Multi Format Transfer of which Field Type includes any of X, M, or N type in CSV format is not treated as an error. The content of the CSV output is truncated at the position of NULL.

[Remarks] As for the Format Transfer, an error occurs. [2] Target Version


This phenomenon occurs when all of the following conditions are fulfilled: • The Field Type of the Multi Format Transfer includes any of X, M, or N type. • There is a NULL in the format data of which Field Type is any of X, M, or N type. • The receiving is in CSV format.



When all of the above mentioned conditions are fulfilled, the processing to check the presence of an invalid value in the receiving data has been added.

Under above circumstances, the following message is now output and an error on the receiving side (Status code: 185) occurs:

‘E145009: Unable to use NULL in character string type (Record No=***, Format No=**, Field No=**, Field name=***).’



521 When the receiving of the file of which size is 4G or larger in the CSV format is carried out, HULFT ends in error in some cases.

[1] Phenomenon

When the receiving of the file of which size is 4G or larger in the CSV format is carried out, HULFT ends in error in some cases, outputting the following message:

‘E146006: Receive file seek error. (source host name=***, file ID=***)’

(Error code=183, 00000) [2] Target Version


This phenomenon occurs when the receiving in the CSV format is carried out with all of the following conditions fulfilled: • ‘MULTIFORMAT’ is set to The ‘Transfer Type’ of Send Management Information and

‘CSV’ is set to the ‘Interface DBID.’ • The file size of the Send file is 4G bytes or larger, and the key field exists at the position

that is 1 byte smaller than 4G bytes in size. (namely, 42,949,672,965th bytes) [4] Alternate method


The receiving in CSV format is carried out normally, even when all of the above mentioned occurrence conditions are fulfilled.



525 When the transfer of the Receive file of which file size is 1 byte smaller than 4G(namely, 42,949,672,965 bytes) is carried out, HULFT ends in error in some cases.

[1] Phenomenon

When the transfer of the Receive file of which file size is 1 byte smaller than 4G bytes (namely, 42,949,672,965 bytes) is carried out, HULFT ends in error in some cases, outputting the following message.

‘E109040: Error occurred when obtaining the Receive file size. (Sending Host Name=***, File ID=***)’

(Error code = 708, 00000) [2] Target Version


This phenomenon occurs when any of the following conditions are fulfilled: • Sending of the Receive file of which file size is 1 byte smaller than 4G(namely,

42,949,672,965 bytes) is carried out, while having specified ‘TEXT’ for the ‘Transfer Type’ in the Send Management Information and ‘Append’ for the ‘Registration Mode’ in the Receive Management Information, respectively.

• Checkpoint Resend File of the Receive file of which file size is 1 byte smaller than 4G bytes(namely, 42,949,672,965 bytes) is carried out, while having specified ‘TEXT’ for the ‘Transfer Type’ in the Send Management Information.



The transfer process is carried out normally, even when any of the above mentioned occurrence conditions are fulfilled.



• Request Acknowledge Function

493 When HULFT fails to open the Mail Interface Information file, memory leaks.

[1] Phenomenon

When HULFT fails to open the Mail Interface Information file(Mail ID.mal), memory leaks in the Request Acknowledge process(hulobs.exe).

[2] Target Version


Under the state in which HULFT fails to open the Mail Interface Information file(the state such as no access permission to the file is granted, the file does not exist, and the like), this phenomenon occurs when the Mail Interface Information Update screen was opened via the following products: • HULFT Manager • HULFT-HUB Manager • HULFT Manger for Web



Memory does not leak, even when the above mentioned occurrence condition is fulfilled.

510 When the Post-receive Job Result Inquiry Request(HULJOB) is issued for a transfer of which log record count in the job execution log at the receiving side is 0, Error code 741 is set in the Request Acknowledge Log.

[1] Phenomenon

The request processing of the Post-receive Job Result Inquiry Request(HULJOB) itself ends normally, even when the log record count in the job execution log at the receiving side is 0. However, the following error code is set to the Status code of the Request Acknowledge Log file:

‘741: Relevant record does not exist.’ [2] Target Version


This phenomenon occurs when HULFT acknowledges the Post-receive Job Result Inquiry Request(HULJOB) of the transfer of which log record count in the job execution log at the receiving side is 0.



The Status code ‘0,’ which indicates successful completion, is set to the Request Acknowledge Log, even when the log record count in the job execution log at the receiving side is 0.



519 Registering a character string that includes ‘=’ for the ‘Title’ on the Mail Interface Information Update screen and reopening the update screen displays either the ‘Title’ that is left blank or the ‘Title’ without ‘=.’

[1] Phenomenon


[2] Target Version


This phenomenon occurs when character strings that include ‘=’ are registered for the ‘Title’ on the Mail Interface Information Update screen of the Mail Interface Information Update screen via the following products: • HULFT Manager • HULFT-HUB Manager • HULFT Manager for Web



The character strings that include ‘=’ are displayed correctly, even when the above mentioned occurrence condition is fulfilled.



• Utility

419 When the Multiple File Join command(utljoin) is executed, an output file is created despite the absence of the available input file.

[1] Phenomenon

While having specified asterisk(*) for the parameter of input filename(-infile) under the state that there is no available input file, execution of the Multiple File Join command(utljoin) creates an output file, despite the absence of the available input file.

[2] Target Version


This phenomenon occurs when all of the following conditions are fulfilled: • Asterisk(*) is specified for the parameter of the input filename(-infile) of the Multiple

File Join command(utljoin) and then it is executed. • No file exists in the directory for which asterisk(*) is specified.



An output file is not created, even when all of the above mentioned occurrence conditions are fulfilled.

487 An error occurs in some cases when a leap-year date(20080229 and the like) is specified for the parameter of date of the targeted list display(-from, -to) in the Send and Receive Log List Display command.

[1] Phenomenon

An error occurs in some cases when a leap-year date(20080229 and the like) is specified for the parameter of date of the targeted list display(-from, -to) in the Send and Receive Log List Display command. ‘utllist: Incorrect Date’

[2] Target Version


This phenomenon occurs in some cases when a leap-year date is specified for the parameter of the date of the targeted list display(-from, -to) for the Send and Receive Log List Display command.



The error does not occur, even when a leap-year date is input.



488 At the time of executing the Send File command(utlsend), when HULFT fails to read the System Environment Settings(hulenv.cnf), ‘0’(Normal end) is set to the Status code, though it is supposed to be an error.

[1] Phenomenon

At the time of executing the Send File command(utlsend), when HULFT fails to read the System Environment Settings(hulenv.cnf), ‘0’(Normal end) is set to the Status code, though it is supposed to be an error.

Also, ‘0’ is set to the Status code when HULFT fails to read HULFT system file(hulft.sys). [2] Target Version


This phenomenon occurs when the Send File command(utlsend) is executed, while any of the following conditions is fulfilled:

• The System Environment Settings file(hulenv.cnf) does not exist, or the permission to read the file is not granted.

• HULFT system file(hulft.sys) does not exist, or the permission to read the file is not granted.



When HULFT fails to read the System Environment Settings(hulenv.cnf), the following Status code is set. ‘211: Get Hulenv.cnf Error.’

Also, when HULFT fails to read HULFT system file(hulft.sys), the following Status code is set: ‘141: Can’t get option information(%d).’



490 While having already started or terminated HULFT service, when ‘-c start’ or ‘-c stop’ is specified for the parameter of HULFT Startup/Termination command(utlsvcctl) and then execute it, an error does not occur.

[1] Phenomenon

While having already started HULFT service, when ‘-c start’ is specified for the parameter of HULFT Startup/Termination command(utlsvcctl) and then execute it, an error does not occur.

Also, while having already terminated HULFT service, when ‘-c stop’ is specified for the parameter of HULFT Startup/Termination command(utlsvcctl) and then execute it, an error does not occur.

[2] Target Version


[At the time of service startup] This phenomenon occurs when all of the following conditions are fulfilled: • HULFT service has already been started. • ‘-c start’ is specified for the parameter of HULFT Startup/Termination

command(utlsvcctl) to execute. [At the time of service termination] This phenomenon occurs when all of the following conditions are fulfilled: • HULFT service has already been terminated. • ‘-c stop’ is specified for the parameter of HULFT Startup/Termination

command(utlsvcctl) to execute. [4] Alternate method


Errors occur with outputting the following messages:

‘Service is already started.’

‘Service is already stopped.’



491 Specifying the parameter of ‘-m delete’ in the Service Registration/Deletion command(utlservice) without having stopped HULFT service is supposed to cause an error, however HULFT contrarily sets ‘0’(Normal end) to the Status code.

[1] Phenomenon

Specifying the parameter of ‘-m delete’ in the Service Registration/Deletion command(utlservice) without having stopped HULFT service is supposed to cause an error, however HULFT contrarily sets ‘0’(Normal end) to the Status code.

[2] Target Version


This phenomenon occurs when all of the following conditions are fulfilled: • HULFT service has already been started. • ‘-m delete’ is specified for the parameter of HULFT Service Registration/Deletion

command (utlservice). [4] Alternate method


‘2182’ is set to the Status code.

507 When HULFT fails to secure memory at the time of executing the Send File command(utlsend), inappropriate error message, which is different from the message of the failure in securing memory, is displayed.

[1] Phenomenon

When HULFT fails to secure memory at the time of executing the Send File command(utlsend), the following message is output in stead of displaying the message of the failure in securing memory:

‘utlsend: Write Error(128).’

*The above message is output when HULFT fails to write to the Resend Queue file. [2] Target Version


This phenomenon occurs when the Send File command(utlsend) is executed with insufficient system resources.



When HULFT fails to secure memory, the following message is output:

‘utlsend: Memory Error(127)’



511


[1] Phenomenon


Example) utlschange -h ***** -f ***** -p la0

As shown in the example, specifying ‘la0,’ which is a string that includes characters, for the parameter of -p does not cause an error, instead the application behaves in the same way as the specification of ‘1.’

[2] Target Version


[Unsent Status Queue Change Command] This phenomenon occurs when characters are specified in any of the following parameters:

p, -I, -bl, -bc [Multiple Receive File Data Delete Command] This phenomenon occurs when characters are specified in the following parameter:

-c [Alert Notification Command] This phenomenon occurs when characters are specified in any of the following parameters:

-p, -w, -rc, -rt [4] Alternate method


When characters are specified in the parameters of which valid value is numeral in each command, the error occurs, and the usage is output. The output Status codes are as follows: • Unsent Status Queue Change command;

The Status code is ‘99.’ • Multiple Receive File Data Deletion command;

The Status code is ‘65.’ • Alert Notification command;

The Status code is ‘65.’



526 A parameter error does not occur in spite of specifying a parameter of the synchronous transfer( -sync) of the Send File command up to the letter ‘s’ that is followed by any characters other than ‘ync.’

[1] Phenomenon

Specifying a parameter of the synchronous transfer( -sync) of the Send File command up to the letter ‘s’ that is followed by any characters other than ‘ync’ does not cause a parameter error.

[2] Target Version


This phenomenon occurs when any of the following conditions is fulfilled: • Specify the parameter up to the letter ‘s’ and execute the Send File command.

Example) utlsend –f FILE –s • Specify the parameter up to the letter ‘s’ that is followed by any characters other than

‘ync,’ and then execute the Send File command. Example) utlsend –f FILE –sy utlsend –f FILE –s123 utlsend –f FILE ‘-sync –w 3600’



The parameter error occurs and the usage is output.



• Management Screen

508 Pressing [Receive Side Job] on the Send Detail Information Inquiry screen clears the displayed contents in some cases.

[1] Phenomenon

After pressing [Previous] or [Next] on the Send Detail Information Inquiry screen, while having displayed the Receiving Side Job Status by pressing [Receive Side Job], pressing [Receive Side Job] again on the Send Detail Information Inquiry screen clears the on-screen field contents of the Send Acknowledge Date and the File Name in some cases.

[2] Target Version


This phenomenon occurs when all of the following conditions are fulfilled:

1. [Previous] or [Next] on the Send Detail Information Inquiry screen is pressed.

2. [Receive Side Job] is pressed.

3. [Receive Side Job] is pressed again. [4] Alternate method


The on-screen field contents of the Send Acknowledge Date and the File Name are not cleared, even when all of the above mentioned occurrence conditions are fulfilled.

528 On the Mail Interface Information List screen, when HULFT fails to open the Mail Interface Information file, memory leaks.

[1] Phenomenon

On the Mail Interface Information List screen, when HULFT fails to open the Mail Interface Information file, memory leaks in the Management Screen process(hulwin.exe).

[2] Target Version


Under the state in which HULFT fails to open the Mail Interface Information (the state such as no access permission to the file is granted, the file does not exist, and the like), this phenomenon occurs when the Mail Interface Information Update screen is opened.



Memory does not leak, even when above mentioned occurrence condition is fulfilled.



529 Registering a character string that includes ‘=’ for the ‘Title’ on the Mail Interface Information Update screen and reopening the update screen displays either the ‘Title’ that is left blank or the ‘Title’ without ‘=.’

[1] Phenomenon

When character strings that include ‘=’ for the title of the mail interface information update screen are registered, and then the update screen is reopened, the title block is left blank, or ‘=’ is not displayed on the screen.

[2] Target Version


This phenomenon occurs when registering a character string that includes ‘=’ are registered for the ‘Title’ on the Mail Interface Information Update screen.



The character strings that include ‘=’ are displayed correctly, even when the above mentioned occurrence condition is fulfilled.



• Installer

522 When single-byte spaces are included in the specification of the installation folder, HULFT fails to start up service in some cases.

[1] Phenomenon

After the installation of HULFT while having specified the installation path of which indication includes a single-byte space, where there is a file of which path is identical to the path of the installation folder up to the single-byte space, starting service fails with outputting following message:

‘It has failed to start the service. error code=193’

Example)

After the installation of HULFT while having specified ‘C:\HULFT Family\hulft6\binnt’ for the installation folder, create a file of which name is ‘HULFT’ just below the C drive. (Create the circumstance that there is a file of which path is ‘C:\HULFT.’ The path should be identical to the path of the installation folder up to the single-byte space.)

Starting service causes the error in question under above mentioned circumstance. [2] Target Version


This phenomenon occurs when the service is started while all of the following conditions are fulfilled: • The path of which indication includes a single-byte space is specified for the installation

folder, and then HULFT is installed. • There is a file of which path is identical to the path of the above installation folder up to

the single-byte space. [4] Alternate method


The service is started normally, even when all of the above mentioned occurrence conditions are fulfilled.



• Others

459 With insufficient system resources, when the Send/Receive and the Request Acknowledge processes are continuously being carried out, the CPU Usage for the processes reaches 100% in some cases.

[1] Phenomenon

Under the circumstance of insufficient system resources, an attempt to execute socket operation by the Send/Receive and the Request Acknowledge processes and the like, which use socket, causes an error in some cases.

When the error occurs, HULFT carries out retry of the socket operation. However, HULFT continues to retry due to the failure in the processing, which uses up the CPU in some cases.

[2] Target Version


Under the circumstance of insufficient system resources, this phenomenon occurs when socket operation is continuously carried out.

Example) Under the circumstance of insufficient resources, the Send process is continuously carried out while having increased the Send Process Multiplex Level.



The CPU is not used up, even when the above occurrence condition is fulfilled.


revision upgrade notification - hulft...search a log file of which size is 4g bytes or larger from...

Documents