Termination status of cluster exclusive utility
When a cluster exclusive utility (hulclustersnd, hulclusterrcv, hulclusterobs) has terminated successfully, it returns the exit code '0.' When the utility has terminated unsuccessfully, it returns an exit code other than '0.'
1 to 50
- Description:
-
Daemon terminated unsuccessfully.
- Measure:
-
The termination status of utility is the termination status of the target daemon. For details of the measures, refer to the measures described in "Termination Status upon Daemon Startup."
51 A file write error (writefilename).
- Description:
-
Failed to write to the file specified in the '-query' parameter of the hulenv inquiry command.
- Measure:
-
Check the permission for the specified file.
52 A file read error (readfilename).
- Description:
-
Failed to read the file specified in the '-set' parameter of the hulenv restore command.
- Measure:
-
Check the permission for the specified file.
53 tlogfile setting error.
- Description:
-
Failed to set the trace log setting by using the '-set' parameter of the hulenv restore command.
- Measure:
-
When you set '1' to any digit of the 3-digit number in Output to Trace Logs (tracelog), check the output file name specified in Trace Output File Name (tlogfile). Also check the permissions and status of the HULFT message file (tracemsg.dat).
54 A lock error.
- Description:
-
When the termination synchronous function was executed, the daemon experienced an error when acquiring the lock for the control file to monitor termination.
- Measure:
-
Check whether the control file is in a valid condition (with no access permission to the directory). The control file name is as follows:
For Send daemon: $HULPATH/.#hulclustersnd.lock For Receive daemon: $HULPATH/.#hulclusterrcv.lock For Observe daemon: $HULPATH/.#hulclusterobs.lock
55 The daemon has already acknowledged the termination request.
- Description:
-
Daemon has already acknowledged the termination request.
- Measure:
-
After the daemon terminates, restart it and issue a request.
56 The daemon is in the termination processing. The request cannot be acknowledged.
- Description:
-
Daemon is in the termination processing. The request cannot be acknowledged.
- Measure:
-
After the daemon terminates, restart it and issue a request.
57 [hulsndd] hulsndd.pid file rewrite error.
- Description:
-
Failed to restructure the pid file of the Send daemon.
- Measure:
-
When the utility terminates with this error code, the Send daemon (hulsndd) terminates unsuccessfully. Check the setting of Pid File Generation Path (piddir), and restart the Send daemon.
58 [hulsndd] sndpsnum set error.
- Description:
-
Failed to set the value for Send Process Multiplex Level (sndpsnum) by using the '-set' parameter of the hulenv restore command.
- Measure:
-
There may be insufficient memory. Check the environment.
97 Received request cannot be processed.
- Description:
-
A utility for the clustering function has requested the processing that the daemon cannot process.
- Measure:
-
Check that the revision level of the utility for the clustering function matches the level of the daemon.
100 Require timeout.
- Description:
-
A time-out occurred.
- Measure:
-
Specify a longer value for the time-out value that is specified with parameter '-timeout.'
101 HULFT is not Type-CL or HULFT Type-CL is not installed.
- Description:
-
HULFT version in use does not support clustering, or the version supporting clustering is not installed.
- Measure:
-
Check the product you purchased.
102 Usage
- Description:
-
A parameter error.
- Measure:
-
Check whether or not the entered parameter is correct.
103 An environmental error.
- Description:
-
An environmental error in HULFT.
- Measure:
-
Check whether the environment variables 'HULPATH' and 'HULEXEP' are set correctly.
104 hulenv.conf error.
- Description:
-
Access to the System Environment Settings file ($HULPATH/hulenv.conf) failed.
- Measure:
-
Check the permission for the System Environment Settings file. Also, check whether the environment variable 'HULPATH' is set correctly.
105 hul[sndd|rcvd|obsd] abnormal end.
- Description:
-
The daemon terminated unsuccessfully during standby in the start synchronization mode or the remote heartbeat mode with the start synchronization command ('-start' parameter).
- Measure:
-
An invalid signal may have been sent to the daemon. Check the environment.
106 A file open error.
- Description:
-
Failed to open the file for environment resetting by using the '-set' parameter of the hulenv restore command.
- Measure:
-
Check the permission for the specified file.
109 A lock error.
- Description:
-
An error occurred in the utility during lock acquisition to the control file for termination monitoring with the termination synchronous function.
- Measure:
-
Check whether the control file is in a valid condition (with no access permission to the directory). The control file name is as follows:
For Send daemon: $HULPATH/.#hulclustersnd.lock For Receive daemon: $HULPATH/.#hulclusterrcv.lock For Observe daemon: $HULPATH/.#hulclusterobs.lock
110 Fork failure.
- Description:
-
Failed to create the daemon startup process or monitoring process with the start synchronization command ('-start' parameter).
- Measure:
-
The number of processes may have exceeded the limit in your environment. Check the environment.
111 hulsndd is not running.
- Description:
-
The Send daemon is not started.
- Measure:
-
Start the Send daemon.
112 A FIFO interprocess communication error.
- Description:
-
Failed to communicate with the Send daemon.
- Measure:
-
The Send daemon may have not started or may not communicate properly.
If a utility ended with this exit code despite the active status of the Send daemon, restart the Send daemon.
113 A socket connect error.
- Description:
-
Failed to communicate with either the Send daemon, the Receive daemon, or the Observe daemon.
- Measure:
-
Either the Send daemon, the Receive daemon, or the Observe daemon may not have started or may not be communicating properly. If a utility ended with this exit code despite the active status of the daemon, restart the daemon.
114 A socket write error.
- Description:
-
Writing of the communication socket in the local host failed.
- Measure:
-
The operating system may be in unstable condition. Check the environment.
115 A socket read error.
- Description:
-
Reading of the communication socket in the local host failed.
- Measure:
-
The operating system may be in unstable condition. Check the environment.
116 A pipe open failure.
- Description:
-
Failed to open the pipe to monitor the start synchronization mode or the heartbeat mode, by using the '-set' parameter of the hulenv restore command.
- Measure:
-
The operating system may be in unstable condition. Check the environment.
117 An invalid tag.
- Description:
-
An invalid tag value was specified to be restored in the '-set' parameter of the hulenv restore command.
- Measure:
-
Set a valid value to the tag to restore in the System Environment Settings.
118 HULPATH invalid.
- Description:
-
A wrong value is specified for the environment variable 'HULPATH.'
- Measure:
-
Check the settings for the environment variable 'HULPATH.'
119 Cannot get max socksize of OS.
- Description:
-
Failed to acquire the maximum socket buffer size of the operating system.
- Measure:
-
The operating system may be in unstable condition. Check the environment.
120 Cannot get max socksize of OS.
- Description:
-
Failed to acquire the maximum socket buffer size of the operating system.
- Measure:
-
The operating system may be in unstable condition. Check the environment.
125 A fatal error.
- Description:
-
A fatal error occurred.
- Measure:
-
The operating system may be in unstable condition. Check the environment.