11.4.4 Handling Error Information Displayed in the User-Reply Functionality
This section explains the information output by the error messages listed below when the user-reply functionality is used and describes the appropriate actions to be taken in response to the messages. When the adshcollect command is used to collect user-reply functionality information, you must execute the command with the administrator permission.
-
KNAX7402-E
-
KNAX7460-E
-
KNAX7461-E
-
KNAX7462-E
- Organization of this subsection
(1) Error information displayed in the KNAX7402-E message and how to respond to it
|
Error number |
Meaning |
Corrective action |
|---|---|---|
|
1 |
An unimplemented API call was made. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
2 |
An attempt to reference shared memory failed. The user-reply functionality's management daemon or service might not be running. |
Operator Check that the job environment file settings are correct. The SPOOL_DIR parameter cannot be specified in a job environment file. In addition, contact a user with an administrator role on the machine and confirm the following:
User with an administrator role on the machine Confirm the following:
If the problem persists, contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
3 |
The amount of unused memory space is insufficient. |
Contact a system administrator. If you are a system administrator, re-estimate the amount of memory required. |
|
4 |
An invalid argument was passed. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
5 |
A data inconsistency was detected. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
6 |
An unsupported character encoding was specified. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
7 |
An underflow occurred. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
8 |
An overflow occurred. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
9 |
The order of API calls was not valid. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
10 |
An inconsistency occurred in the status of an internal object. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
11 |
Access to a resource was denied. |
Check that you have write permission for the log directories specified in the environment file and the log files under them. |
|
12 |
A specified file does not exist. |
Check that you have write permission for the log directories specified in the environment file and the log files under them. |
|
13 |
A file could not be opened. |
Check that you have write permission for the log directories specified in the environment file and the log files under them. |
|
14 |
Memory mapping could not be created for a file. |
Check that you have write permission for the log directories specified in the environment file and the log files under them. |
|
15 |
An error occurred in reading from a file. |
Check that you have read permission for the log directories specified in the environment file and the log files under them. |
|
16 |
An error occurred in writing to a file. |
Check that you have write permission for the log directories specified in the environment file and the log files under them. |
|
17 |
An error occurred in seek processing on a file. |
Check that you have write permission for the log directories specified in the environment file and the log files under them. |
|
18 |
An error occurred in flush processing on a file. |
Check that sure you have write permission for the log directories specified in the environment file and the log files under them. |
|
19 |
An error occurred in renaming a file. |
Check that sure you have write permission for the log directories specified in the environment file and the log files under them. |
|
20 |
An error occurred in copying a file. |
Check that you have write permission for the log directories specified in the environment file and the log files under them. |
|
21 |
An error occurred in deleting a file. |
Check that you have write permission for the log directories specified in the environment file and the log files under them. |
|
22 |
An attempt to create a directory failed. |
Check that you have write permission for the log directories specified in the environment file and the log files under them. |
|
23 |
An interprocess lock failed. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
24 |
An attempt was made to use a function that was disabled by the user program. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
25 |
An attempted overwrite was prohibited by the user program. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
400 |
A parameter was not valid. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
404 |
A reply-request message was deleted by the adshchmsg command, or shared memory could not be referenced. |
If you are the operator, contact a user with an administrator role on the machine and check the following:
If you are a user with an administrator role on the machine, check that the user-reply functionality's management daemon or service is running. If the problem persists, contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
409 |
Reply-request messages from the same PID were output. |
The reply-request message might have been output simultaneously in multiple threads. Check and, if necessary, revise the application. |
|
503 |
The number of reply-waiting events exceeded the maximum. |
Check and, if necessary, revise the value of the USERREPLY_WAIT_MAXCOUNT parameter. |
(2) Error information displayed in the KNAX7460-E, KNAX7461-E, and KNAX7462-E messages and how to respond to it
|
Error number |
Meaning |
Corrective action |
|---|---|---|
|
10 |
A parameter was not valid. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
11 |
The order is which functions were issued was not valid. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
30 |
A specified attribute was already registered. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
32 |
The maximum number of extended event attributes that can be registered has been exceeded. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
33 |
The total size of all extended event attributes that can be registered has been exceeded. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
40 |
A connection to the event service could not be established. |
Check that the JP1/Base event service has started on the local host. |
|
43 |
An input/output error occurred. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
50 |
A JP1/Base library could not be found. |
Install JP1/Base and re-execute the job. |
|
51 |
There is not enough memory. |
Contact a system administrator. If you are a system administrator, re-estimate the amount of memory required. |
|
52 |
The number of open files has reached the maximum. |
Contact a system administrator. If you are a system administrator, re-estimate the number of FDs that can be opened. |
|
60 |
A JP1 event has not been initialized. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |
|
70 |
A system error occurred. |
Contact a system administrator. If you are a system administrator, collect information in accordance with 10. Troubleshooting, and then find a workaround or take corrective action. |