Specifications

(O)
Execute Jischk -l3 table-name to check whether a problem exists with the table whose reorganization ended
abnormally. For details about Jischk, see the Job Management Partner 1/Base User's Guide. After collecting the
result of Jischk, contact the system administrator (see 1.2.3 To the system administrators).
KAVS1716-E
An attempt to prepare for reorganization of the scheduler service (scheduler-service-name) database failed.:
maintenance-information
While the jajs_maintain command was performing maintenance, the system could not make preparations for
reorganizing tables.
(S)
Cancels command execution. If, however, any other services remain unexecuted, the system continues command
execution.
(O)
Memory may be insufficient. Alternatively, the number of processes started on the system may have reached the
maximum.
• In UNIX, check and correct the settings of the kernel parameters for memory and processes.
For details about how to estimate kernel parameters and the size of memory used, see Release Notes.
• Check the status of the process that was running when the error occurred. Then make sure that the amount of
memory available is greater than the estimated value.
• If you cannot determine the cause, collect data and then contact the system administrator (see 1.2.3 To the system
administrators).
KAVS1717-E
Maintenance is being performed, so execution is impossible. (maintenance-information)
Since maintenance is in progress, the specified command cannot be executed.
(S)
Cancels command execution.
(O)
Wait until maintenance ends, and then re-execute the command.
KAVS1718-E
The scheduler service (
scheduler-service-name) database connection exists, so shifting to the maintenance mode
is impossible.
The system could not enter maintenance mode because a process other than services connected to the database.
2. Messages
Job Management Partner 1/Automatic Job Management System 3 Messages 1
311