Status codes related to the system

300  Insufficient memory

Description:

Memory insufficient for the application.

Measure:

Terminate other unnecessary applications, then retry the attempt.

301  Unable to open file

Description:

Cannot open the file.

Measure:

The directory may not exist, the work file generation path may not exist, or permission may not be granted.
Check the environment.

302  A file read error

Description:

Unable to read the file.

Measure:

Errors in the socket stream and specified file name, operating system failure, and the like may have occurred.
Check the environment.

303  A file write error

Description:

Unable to write in the file.

Measure:

Errors in the socket stream, operating system failure, and the like may have occurred.
Check the environment.

304  A file seek error

Description:

File seek error.

Measure:

An access error to the file occurred.
Check the presence, permission, and lock state of the file.

305  A link file error

Description:

Failure in linking to the file.

Measure:

An access error to the file occurred.
Check the presence, permission, and lock state of the file.

306  A remove file error

Description:

Deletion of the file (work file and the like) failed.

Measure:

An access error to the file occurred.
Check the presence, permission, and lock state of the file.

307  Disk full

Description:

The disk has become out of free space or the memory has become insufficient while writing data to the disk.

Measure:

Delete unnecessary files on the disk where you intend to create data. Make sure that there is enough free space, and retry the attempt.

308  A disk access error

Description:

Failure in input and output of the disk or file.

Measure:

Check the contents, path, and permission of the file, then retry the attempt.

309  A process error

Description:

An error occurred in operations related to processes such as generation of a process and inter-process communication.

Measure:

The operating system environment is in unstable condition. Restarting the HULFT system is required.
Check whether there are any invalid operations in other processes.

310  A socket error

Description:

An error occurred in operations related to the socket such as socket generation and connect.

Measure:

Check the network environment. Check the specified host name and port number for an error.

311  A signal set error

Description:

An error occurred when setting the signal.

Measure:

HULFT is in unstable condition.
Stop and restart all services.

312  Interrupt

Description:

The process is interrupted by the user or by the system.

Measure:

HULFT is interrupted by other processes, or HULFT is in unstable condition.
Restart HULFT.

313  Hang up

Description:

For some reasons, the process stopped responding.

Measure:

HULFT or the operating system environment is in unstable condition. Restart the system.

314  Killed

Description:

HULFT was forcibly terminated.

Measure:

HULFT or the operating system environment is in unstable condition. Restart the system.

315  A bus error

Description:

For some reasons, a bus error occurred in the process.

Measure:

HULFT is in unstable condition. Restart HULFT.

316  Segmentation fault

Description:

A segmentation violation occurred in the process.

Measure:

HULFT is in unstable condition. Restart HULFT.

317  Quit

Description:

The process was ended by the user or the system.

Measure:

HULFT is interrupted by other processes, or HULFT is in unstable condition.
Restart HULFT.

318  Broken pipe

Description:

An error occurred in the socket or in the pipe.

Measure:

A problem may have occurred on the remote host or in the communication path.
In the case of command execution by the Observe system, the error might be caused by an unsuccessful end or a startup failure of the utility.

319  A duplication error

Description:

Failure due to the duplicate file descriptor.

Measure:

An error occurred in the HULFT system.
Restart HULFT.

320  Illegal time address

Description:

Acquisition of the system time failed.

Measure:

An error occurred in the HULFT system.
Restart HULFT.

321  A child process error

Description:

An error may have occurred in a child process.

Measure:

The Detail Code indicates the Status Code of the child process.
With this code, find descriptions of the Status Code of the command or the utility that has been started.

322  No password name

Description:

The owner name of the Receive Management Information has not been registered in the password file.

Measure:

Register an owner name or retry the attempt using the owner name that is currently registered.

323  No group name

Description:

The group name of the Receive Management Information has not been registered in the group file.

Measure:

Register a group name or retry the attempt using the group name that is currently registered.

324  Unable to change owner

Description:

The owner or group file could not be modified.

Measure:

The service of HULFT could not change the information of the target file.
HULFT service should have the root permission.

325  Unable to change mode

Description:

The permission of the file could not be changed.

Measure:

The service of HULFT could not change the information of the target file. HULFT service should have the root permission. When HULFT does not have the root permission, the file can be changed by a HULFT owner who possesses the required startup permissions.

326  Unable to set user id

Description:

User ID of the process could not be changed.

Measure:

The service of HULFT could not change the information of the target file. HULFT service should have the root permission.

327  Unable to set group id

Description:

Group ID of the process could not be changed.

Measure:

The service of HULFT could not change the information of the target file.
HULFT service should have the root permission.

328  Unable to set process group

Description:

Process group could not be changed.

Measure:

The service of HULFT could not change the information of the target file.
HULFT service should have the root permission.

329  A file move error

Description:

An error occurred while moving the file.

Measure:

Secure enough free capacity on the disk, then retry the attempt.

330  A file copy error

Description:

The copying of the file failed.

Measure:

Secure enough free capacity on the disk, then retry the attempt.

331  A file lock error

Description:

Locking of the file failed.

Measure:

HULFT or other systems may have denied the access to the file.
After a while, retry the attempt.

332  A get hostname error

Description:

The Receive daemon or the Observe daemon failed to acquire the connection source host name.

Measure:

Check the host management file (/etc/hosts) or the domain name server environment of UNIX system.

333  Timeout

Description:

Timeout is detected in the socket communication by the Send daemon, the Receive daemon, and the Observe daemon.

Measure:

Check that there is no error on the line.

334  A multi format information error

Description:

An error in the content of the Multi Format Information.

Measure:

Check the content of the data, the Multi Format Information, and the Format Information.

335  Locked by another process

Description:

The file has already been locked by other process.

Measure:

After a while, retry the transfer.

336  A shared library load error

Description:

Load of the common library failed.

Measure:

When the encryption exit routine is used, check whether or not the common library is in the specified location.
When the SAN transfer is used, check whether or not the common library that is required for the SAN transfer is in the specified location.

338  Received data is too long.

Description:

The received data is too long.

Measure:

An error may have occurred while receiving data.
Retry the transfer.

339  Receive data is corrupt.

Description:

The received data is corrupt.

Measure:

An error may have occurred while receiving data.
Retry the transfer.

340  A gaiji/user table initialize error

Description:

Initialization of the custom character table or user code table failed. No EBCDIC user table may be available due to an unsupported combination of Code Set for Transfer.

Measure 1:

For regular transfer, check the custom character table and user code table required for the type of code conversion configured in the Send Management Information. Also, check that the following combination of code sets is one that can be used with the EBCDIC user table.

• The remote host's code set specified as Code Set for Transfer (KCODETYPE) in the Host Information

• Code Set for Transfer (cs4trnsfr) specified in the System Environment Settings

Measure 2:

For instant transfer, check that the following combination of code sets is one that can be used with the EBCDIC user table:

• Code Set for Transfer (cs4trnsfr) specified in the System Environment Settings on the remote host

• Code Set for Transfer (cs4trnsfr) specified in the System Environment Settings on the local host

341  A character code conversion error

Description:

An error occurred during character code conversion.

Measure:

Make sure that the code set specified for Code Set for Transfer (cs4trnsfr) in the System Environment Settings is correct.

350  A HULFT linkage error

Description:

An error occurred while interfacing with HULFT exchanger.

Measure:

Refer to the Detail Code.

512  Receive cancel

Description:

The processing was stopped by the cancel command from the receiving host.

Measure:

none.

513  A receive checkpoint error

Description:

The Checkpoint Resend File cannot be acknowledged, because Registration Mode in the Receive Management Information is specified to 'N: New Creation,' still the file already exists.

Measure:

Take either of the following measures:

• Issue a request without executing Checkpoint Resend File.

• Delete Receive file.

• Change the setting of the Registration Mode in the Receive Management Information to 'R: Replace.'

514  Post-receive Job abend 

Description:

The Post-receive Job ended abnormally.

Measure 1:

Check the contents of the job.

Measure 2:

When you execute Receiving to cloud storage and "Successful Job Completion" is set in Notification, even if the execution of a Successful job fails, Error Handling is not executed. Keep this in mind when executing Resend and when re-executing a job.

515  Post-receive Job timeout 

Description:

The Receive processing ended unsuccessfully due to the timeout of the Post-receive Job.

Measure:

Set a longer Job Timeout and restart the Receive daemon, then retry the transfer.

516  Maximum connection count exceeded. 

Description:

The number of connections to the Receive daemon on the receiving host exceeds the value specified in Receive Multiplex Level.

Measure:

Increase the set value of Receive Process Multiplex Level, or retry the transfer after a while.

517  Sending host doesn't support Trans. test

Description:

The sending host does not support the Transfer Test function.

Measure:

Check whether or not the version of the sending host supports the Transfer Test function.

525  An end telegram receive error

Description:

Termination status of the receiving host could not be acquired.
Receiving may have terminated successfully on the receiving host.

Measure:

Check the Status Code on the receiving host.

526  Success, but send possibly failed.

Description:

Waiting for socket closing on the sending host failed.

Measure:

The network may have been disconnected. The receiving host terminated unsuccessfully, whereas the sending host may have terminated successfully.
Check the environments on both sides.

530  Data size or record disagreement

Description:

A data count error occurred.

Measure:

An inconsistency in the transfer record count is detected. Check the contents and attributes of the Send file and the Receive file. When encryption exit routine is used, check whether or not Cipher Key is specified properly.

531  A user cipher function error

Description:

An error occurred in executing a user external encrypting function.

Measure:

An error occurred during the execution of an encryption exit routine.
Check the exit routine operation. When this error occurred, the code assigned to the Detail Code is the return value of the function created by the user.

535  A data verification error

Description:

An error occurred in data verification.

Measure:

During communication, this transfer data may have been destroyed or the data have lost their pieces. Check the state of network, then retry the verification.

536  A data verification version error

Description:

An error occurred in data verification.

Measure:

The sending host does not support data verification, or the host does not support the data verification type specified in the Receive Management Information. Review the version of the sending host and the setting of Verify Data in the Receive Management Information.

538  Host name does not exist.

Description:

The requestor host name is not registered in the Host Information.

Measure:

Check that the connection from the requestor host is correct. When it is correct, register the requestor host in the Host Information.

539  Refused Service

Description:

Refused the service from the requestor host.

Measure:

Check that the request from the requestor host is correct. If it is correct, check and change the settings of Requestor Host Authorization under Security in the Host Information.

540  A protocol version error

Description:

The specified function is not available in processing with HULFT on the remote host.

Measure 1:

Check that none of File ID, Format ID, and Multi Format ID is specified in 9 bytes or more.

Measure 2:

Check that 'XML' is not set to Interface DBID in the Send Management Information on the sending host.

541  A request type error

Description:

A request has been made to a wrong system in HULFT. A request for the Send File might have been made to the Observe system. Otherwise, a request for the Send Request might have been made to the Receive system and so on.

Measure:

Check whether or not the setting of Receive Port No. and Observe Port No. on the Requestor host is correct.

542  Wrong protocol

Description:

HULFT received unexpected data.

Measure 1:

Specify 'Y' (Yes) for the Use HULFT7 Comm. Mode in the Host Information, then retry the transfer.

Measure 2:

Check whether the data have been sent by HULFT or not.

543  Code Set Combination error

Description:

The combination of the following two code sets is not supported.

1. The code set specified for Code Set for Transfer (cs4trnsfr) in the System Environment Settings on the local host

2. The code set specified for Code Set for Transfer (KCODETYPE) in the Host Information on the local host

Measure:

Check supported combinations of code sets.

544  Combination Error with EBCDIC Set

Description:

The combination of the following two code sets is not supported.

1. The EBCDIC set specified for EBCDIC Set in the Send Management Information or the Receive Management Information on the local host

2. The EBCDIC set specified for EBCDIC Set (KCODETYPE) in the Host Information on the local host

Measure:

Check supported combinations of code sets.

545  strongkeymode error

Description:

Failed to communicate in the Forced Strong Key mode.

Measure:

Check that all of the following conditions are met on the destination host:

• Forced Strong Key mode is enabled

• HULFT Ver.8.4.0 or higher is installed

• HULFT8 Cipher Option(AES) is installed

546  cipher key length mismatch

Description:

Length of the cipher key registered in management information is invalid.

Measure:

If Forced Strong Key mode is enabled, use a cipher key of 64 digits hexadecimal character string.

If Forced Strong Key mode is disabled, use a cipher key of 0 or 8 to 20 bytes alphanumeric character string.

590  Force stop command accept (Snd)

Description:

The Send process has been ended by the termination synchronization command of the Cluster Utilities (forced termination mode).

Measure:

No countermeasure.

591  Force stop command accept (Rcv)

Description:

The Receive process has been ended by the termination synchronization command of the Cluster Utilities (forced termination mode).

Measure:

No countermeasure.

592  Force stop command accept (Obs)

Description:

The Observe process has been ended by the termination synchronization command of the Cluster Utilities (forced termination mode).

Measure:

No countermeasure.

603  Get cancel from the Send process

Description:

The processing has been stopped by the cancel command from the sending host.

Measure:

none.

604  Receive host doesn't support Trans. test

Description:

Unable to complete the Transfer Test including the receiving host, because the host does not support the Transfer Test function.

Measure:

Take either of the following measures:

• Check whether or not the version of the receiving host supports the Transfer Test.

• Set the Result Handling of Receiving (ttrcvomit) in the System Environment Settings to '1.'