A.1 Reason Codes of Messages Beginning with KAVU
The table below lists the reason codes of messages beginning with KAVU (messages about the job execution control).
|
Reason code (hexadecimal) |
Description |
|---|---|
|
0x00010001 |
The monitoring process for job execution control has started twice. |
|
0x00010006 |
The monitoring process for job execution control could not acquire the environment setting parameter. |
|
0x00010007 |
The manager process for job execution control could not be started. |
|
0x00010008 |
The agent process for job execution control could not be started. |
|
0x0001000b |
The monitoring process for job execution control could not create a pipe. |
|
0xa0080002 |
The manager process for job execution control has started twice. |
|
0xa0080011 |
Memory became insufficient in the manager process for job execution control. |
|
0xe0090001 |
Memory became insufficient in the manager process for job execution control. |
|
0xe0090008 |
The user has no operator permission. |
|
0xa00a0005 |
The specified job is missing. |
|
0xe0021101 |
Memory became insufficient during TCP/IP communication for job execution control. |
|
0xe002110d |
The temporary file used for job execution control did not exist. |
|
0xe002110e |
You did not have access permission for the temporary file used for job execution control. |
|
0xe002110f |
The amount of free space on the disk was insufficient when the temporary file used for job execution control was being created. |
|
0xe0021110 |
The temporary file used for job execution control was locked and opened. |
|
0xe0021120 |
An attempt to acquire the logical host name or IP address has failed. |
|
0xe0021127 |
Reception failed due to a timeout during TCP/IP communication of job execution control. |
|
0xe00a0002 |
Memory became insufficient in the manager process for job execution control. |
|
0xe00a0003 |
The amount of free space in the disk became insufficient in the manager process for job execution control. |
|
0xe00a0007 |
Connection could not be made in the manager process for job execution control. |
|
0xe00a0008 |
The specified destination host is invalid. |
|
0xe00b0003 |
There is no path for storing the database for job execution control. |
|
0xe00b0004 |
The specified database table is missing. |
|
0xe00b0008 |
The database table for job execution control could not be locked. |
|
0xe00b0009 |
You have no permission to connect to the database table. |
|
0xe00b000a |
You have no access permission for the database table. |
|
0xe00b000f |
The semaphore's value became insufficient in the database process for job execution control. |
|
0xe00b0010 |
A disk error occurred in the database process for job execution control. |
|
0xe00b0011 |
The number of files to be opened was not enough in the database process for job execution control. |
|
0xe00b0016 |
The user name or password is invalid. |
|
0xe00b0017 |
The number of connections with the database exceeded the limit of the server. |
|
0xe00b0018 |
The database is not running. |
|
0x20100002 |
The agent process for job execution control has started twice. |
|
0x20100004 |
Memory became insufficient in the agent process for job execution control. |
|
0xe0800002 |
Memory became insufficient in the status notification process for job execution control. |
|
0xe080100a |
The status notification process for job execution control could not acquire the environment setting parameter. |
|
0xe080100b |
A bind error occurred in the status notification process for job execution control. |
|
0xe080100d |
The port number that is used for the status notification process for job execution control is invalid. |
|
0xe080100e |
The status notification process for job execution control has started twice. |