Job Management Partner 1/Automatic Job Management System 3 Messages 1

2.2 Messages beginning with KAVS (Messages about the scheduler)

This section lists the messages that begin with KAVS (Messages about the scheduler).

When using JP1/AJS3 in a compatible ISAM configuration, see the JP1/AJS2 manuals.

Supplementary note

Messages that begin with KAVS also include messages about the queueless job execution facility.

KAVS0100-E
Illegal option (option) exists.

An invalid option was specified.

(S)

Cancels command execution.

(O)

Correct the option, and then re-execute the command.

KAVS0101-E
Value for option (option) is not specified.

The option does not contain any value.

(S)

Cancels command execution.

(O)

Specify a value for the option, and then re-execute the command.

KAVS0102-E
Extra argument(s) exist.

An unnecessary argument(s) was specified.

(S)

Cancels command execution.

(O)

Delete the unnecessary argument(s), and then re-execute the command.

KAVS0103-E
Invalid value for option (option).

The option contains an invalid value.

(S)

Cancels command execution.

(O)

Correct the value for the option, and then re-execute the command.

KAVS0104-E
Option (option) appears twice or more.

The same option was specified more than once.

(S)

Cancels command execution.

(O)

Specify the option only once, and then re-execute the command.

KAVS0105-E
Jobnet name not specified.

A jobnet name is missing.

(S)

Cancels command execution.

(O)

Specify the jobnet name, and then re-execute the command.

KAVS0106-E
Cannot treat as Jobnet.: name

The system cannot handle name as a jobnet.

For a jobnet entered for release (release target jobnet), there might be no jobnet definition whose status is Being applied.

(S)

Cancels command execution. If you specify more than one jobnet (including specifications of regular expression), the system continues command execution.

(O)

When name is displayed, specify a unit name that the system can handle as a unit, and then re-execute the command.

When name is not displayed, check the jobnet name for invalid characters. Delete the invalid characters, and then re-execute the command.

The invalid characters are:

(

)

, (comma)

: (colon)

; (semicolon)

=

/

Space character

For a jobnet entered for release, use the ajsrelease command or JP1/AJS3 - View to display the release list information and check for a jobnet definition in Being applied status. If such a jobnet definition is not found, use the ajslocaldate command to change the time to a time that there is a jobnet definition in Being applied status, and then delete the relevant jobnet.

KAVS0107-E
Scheduler service has not started.

The scheduler service has not started.

(S)

Cancels command execution.

(O)

Start the scheduler service using the jajs_spmd command, and then re-execute the command.

KAVS0108-E
Only super user or administrator can execute.

A user who does not have superuser privileges or is not logged on as a member of the Administrators group attempted to execute a command.

(S)

Cancels command execution.

(O)

Execute the command as a superuser or an administrator.

If the UAC function is enabled in Windows, the administrator must re-execute the command.

KAVS0110-E
Jobnet (jobnet-name) is in execution.

The jobnet is being executed.

(S)

Cancels command execution.

(O)

Wait for the jobnet to terminate the execution, and then re-execute the command.

KAVS0111-E
Unit name not specified.

A unit name is missing.

(S)

Cancels command execution.

(O)

Specify a unit name, and then re-execute the command.

KAVS0112-E
Cannot treat as Unit.: name

The system cannot handle name as a unit.

(S)

Cancels command execution. If you specify more than one unit (including specifications of regular expression), the system continues command execution.

(O)

When name is displayed, specify a unit name that the system can handle as a unit, and then re-execute the command.

When name is not displayed, check the jobnet name for invalid characters. Delete the invalid characters, and re-execute the command.

The invalid characters are:

(

)

, (comma)

: (colon)

; (semicolon)

=

/

Space character

KAVS0113-E
No authority for Unit (unit-name).

You do not have an authority for the unit.

(S)

Cancels command execution.

(O)

Execute the command with the authority for the unit.

KAVS0115-E
Unit (unit-name) already registered as Jobnet.

The unit has already been registered as a jobnet. The probable causes are:

A relationship change option is specified for the registered unit.

A jobnet connector information change option is specified for the planning group that contains the registered unit.

A jobnet connector information change option is specified for the registered unit.

(S)

Cancels command execution.

(O)

Unregister the unit, and then re-execute the command. To specify relationship change options in the ajschgnet command and specify a suspended jobnet as the unit name, re-execute the command with the -S option.

KAVS0116-E
Cannot specify these options together.

You attempted to use options that cannot be simultaneously specified.

(S)

Cancels command execution.

(O)

Check the specified options, and re-execute the command with options that can be specified together.

KAVS0117-E
Job name not specified.

A job name is missing.

(S)

Cancels command execution.

(O)

Specify a job name, and then re-execute the command.

KAVS0119-E
Cannot use - in use by other user.: unit-name or file-name

Operation is impossible because another user is using the job, jobnet or job group that you attempted to execute with a command. Alternatively, another user is using the file that you attempted to manipulate.

(S)

Cancels command execution.

(O)

Wait for the other user to complete using the job, jobnet or job group and then re-execute the command.

KAVS0123-E
Cannot read configuration definition parameter - no authorization.

You cannot enter the configuration definition parameter.

(S)

Cancels command execution.

(O)

Correct the configuration definition parameter, and then re-execute the command.

KAVS0125-E
Cannot open specified file (file-name).: maintenance-information

The file could not be opened. The probable causes are:

There is no access permission for the specified file.

A file that does not exist is specified.

An attempt was made to create a file with the same name as an existing file.

A read-only file is specified.

A file being used is specified.

Invalid characters are specified for a file name or directory name.

A directory is specified.

There is not enough free space on the file system or device to which you attempted to write a file.

The number of files that can be handled by the process or system exceeds the maximum.

Memory is insufficient.

(S)

Cancels command execution.

(O)

Correct the information about the file, and then re-execute the command.

KAVS0126-E
Operand value exceeds prescribed length.

The value of the operand exceeds the prescribed length.

(S)

Cancels command execution.

(O)

Correct the value of the option, and then re-execute the command.

KAVS0127-E
Specified file (file-name) does not exist.

The file does not exist.

(S)

Cancels command execution.

(O)

Correct the file name or create the file. Then, re-execute the command.

KAVS0129-E
Jobnet (jobnet-name) is not executing.

The jobnet is not being executed.

(S)

Cancels command execution.

(O)

Re-execute the command while executing the jobnet.

KAVS0130-E
Specified Jobnet (jobnet-name) is not registered.

The jobnet is not registered.

(S)

Cancels command execution.

(O)

Register the jobnet, and then re-execute the command.

KAVS0132-E
Job error information directory (directory-name) does not exist.

The job error information directory specified in the JOBINFDIR environment setting parameter does not exist.

(S)

Cancels command execution.

(O)

Create the job error information directory, and then re-execute the command.

For details on the environment setting parameters, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVS0135-E
Job error information directory name (directory-name) is invalid.

An invalid job error information directory name was specified in the environment setting parameter.

The specification of the JOBINFDIR environment setting parameter is invalid. The probable cause is:

The directory specified in the environment setting parameter is invalid.

(S)

Cancels command execution.

(O)

Correct the job error information directory name, and then re-execute the command.

For details on the setting of the job error information directory name, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVS0141-E
Cannot operate specified Jobnet (unit-name) under current condition.

The jobnet is in an inoperable status.

The probable causes are:

An attempt was made to re-execute a jobnet that has not been executed.

An attempt was made to re-execute a job that was not placed in the termination status.

With the hold option specified, an attempt was made to re-execute a root jobnet that was being executed.

An attempt was made to re-execute a root jobnet that was both being executed and contained in the remote jobnet.

(S)

Cancels command execution.

(O)

Specify the name of a unit in a state that enables the command to be executed, and then re-execute the command.

For details on re-execution, see 4.5.11 Rerunning a job or jobnet in the Job Management Partner 1/Automatic Job Management System 3 Overview.

KAVS0143-E
Cannot execute - currently in process of restriction.

Immediate execution registration and re-execution is impossible because the command has been restricted.

(S)

Cancels command execution.

(O)

Release the status of execution suppression or restricted termination. Then, re-execute the command.

KAVS0144-E
No authority for Job (job-name).

The job does not have any authority.

(S)

Terminates command execution. If you specify more than one job (including specifications of regular expression), the system continues command execution.

(O)

Execute the command with the authority for the job.

KAVS0145-E
Cannot treat as Job.: unit-name

A command that can only be executed for jobs is being executed for a unit other than a job.

(S)

Cancels command execution. If you specify more than one job (including specifications of regular expression), the system continues processing.

(O)

Specify a job name as the unit name, and then re-execute the command.

KAVS0146-E
Options (option) are specified too many times.

Too many options were specified.

(S)

Cancels command execution.

(O)

Check the number of options that can be specified concurrently, and then re-execute the command.

KAVS0150-E
Backup information directory name (directory-name) is too long.

The backup information directory name is specified using a character string of more than 255 bytes.

(S)

Cancels command execution.

(O)

Specify a backup information directory name that has less than 256 bytes, and then re-execute the command.

KAVS0157-E
A relation in opposite direction already exists among elements in the specified Unit (unit-name).

The unit has already been associated in the opposite direction.

(S)

Cancels command execution.

(O)

Recheck the value of the relationship change option, and then re-execute the command.

KAVS0158-E
Invalid value for option (option) on specified Unit (unit-name).

The relationship change option specified for the unit contains an error.

(S)

Cancels command execution.

(O)

Recheck the value of the relationship change option, and then re-execute the command.

KAVS0159-W
Option (option) has been ignored which is incompatible with the Unit (unit-name).

The system invalidates an option that cannot be specified for the unit.

(S)

Continues processing.

KAVS0161-I
Unit does not found for selected option.: unit-name

The probable causes are:

There is no unit for the specified unit name that meets the selected option.

You do not have permission to reference the higher-level unit of the specified unit.

A unit that is inapplicable to the command is specified.

For a jobnet entered for release (release target jobnet), there might be no jobnet definition whose status is Being applied.

(S)

Cancels command execution.

(O)

Correct the error, and then re-execute the command.

For a jobnet entered for release, use the ajsrelease command or JP1/AJS3 - View to display the release list information and check for a jobnet definition in Being applied status. If such a jobnet definition is not found, use the ajslocaldate command to change the time to a time when a jobnet definition in Being applied status exists, and then delete the relevant jobnet.

KAVS0162-E
Invalid scheduler service name.: service-name

An invalid scheduler service name is specified in the -F option or the AJSCONF environment variable.

(S)

Cancels command execution.

(O)

Correct the scheduler service name, and then re-execute the command.

For details on the environment variables, see A.1 Notes on defining environment variables in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

KAVS0166-E
Cannot create a plan for the specified period.: jobnet-name

A plan cannot be created for the specified period of time.

(S)

Cancels processing.

(O)

Recheck the schedule definition of the jobnet, and then re-execute the command.

KAVS0167-E
Specified registration number is not found.: jobnet-name

The registration number has not been registered.

(S)

Cancels processing.

(O)

Correct the registration number or register the jobnet. Then, re-execute the command.

KAVS0168-E
Invalid information in definition schedule file (schedule-information-file-name). (sentence: sentence-number, information: information-number)

An invalid parameter was specified in the schedule information file.

(S)

Cancels command execution.

(O)

Check the contents of the schedule information file according to 4.4 Creating a schedule information file in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2. Then, re-execute the command.

KAVS0169-E
Cannot operate - Jobnet has been shutdown.: jobnet-name

The jobnet is blocked. The probable causes are:

The unit defined in the calendar to be viewed does not exist.

The unit defined in the exclusive schedule does not exist.

(S)

Terminates processing.

(O)

Unregister the blocked jobnet, and then check and re-register the schedule definition. Re-execute the command as required.

KAVS0170-E
No authority for schedule definition file (schedule-information-file-name).

You do not have permission for the schedule information file.

(S)

Terminates processing.

(O)

Execute the command with the authority for the schedule information file.

KAVS0171-E
Temporary directory (directory-name) does not exist.

The temporary file directory specified in the AJSTMPDIR environment setting parameter does not exist.

(S)

Terminates processing.

(O)

Correct the temporary file directory name or create the temporary file directory. Then, re-execute the command.

For details on the settings, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVS0172-E
Temporary directory name (directory-name) is invalid.

The specification of the AJSTMPDIR environment setting parameter contains an error. The probable causes are:

The temporary file directory name is not specified.

The temporary file directory name is more than 180 bytes.

A file name is specified for the temporary file directory name.

Invalid characters are used in a directory name.

(S)

Terminates processing.

(O)

Correct the temporary file directory name specified in the environment setting for the scheduler service, restart the scheduler service, and then re-execute the command.

In Windows, the invalid characters for a directory name are:
\ / ; * ? " < > | : ,

In UNIX, the invalid characters for a directory name are:
\ / ; * ? " < > | space . & ' ` ~ ( )

KAVS0173-E
No authority to use temporary directory (directory-name).

You do not have the required permissions for the temporary file directory specified in the AJSTMPDIR environment setting parameter.

(S)

Terminates processing.

(O)

Execute the command with the authority for the temporary file directory.

KAVS0175-E
Schedule definition file (file-name) contains undefined unit(s).

The schedule information file contains an undefined execution schedule of the unit.

(S)

Cancels command execution.

(O)

Specify the schedule information file for the unit specified in the command, and then re-execute the command.

KAVS0176-E
Table name is invalid.

The configuration definition file contains an invalid table name.

(S)

Cancels command execution.

(O)

Correct the table name in the configuration definition file, and then re-execute the command.

KAVS0177-E
Database type is invalid.

You cannot use the database.

(S)

Terminates processing.

(O)

Correct the database type, and then re-execute the command.

If you want to specify advanced settings and perform a data migration to a standard configuration in an environment in which multiple scheduler services are set up, make sure that the JP1/AJS3 database setup has been completed for all the scheduler services. Then, re-execute the jajs_migrate command with the -S option specified.

KAVS0178-E
Tables already exist.

Tables have been created.

(S)

Cancels command execution.

(O)

You do not have to use the ajssetup command to set up the database again because the tables have already been created. If you want to re-create them, delete the files under the directory storing the database, and then re-execute the command.

KAVS0179-E
Specified Scheduler service not exist.

The scheduler service does not exist.

(S)

Terminates processing.

(O)

Correct the scheduler service name, and then re-execute the command.

KAVS0180-E
Specified execution ID was not found.: execution-ID

The execution ID has not been registered.

(S)

Terminates processing.

(O)

Correct the execution ID, and then re-execute the command.

KAVS0181-E
Execution ID cannot be appointed.

The execution ID cannot be specified.

(S)

Terminates processing.

(O)

You do not need to specify the execution ID.

KAVS0182-E
Logical host name cannot be appointed.

The logical host name cannot be specified.

(S)

Terminates processing.

(O)

You cannot execute the command remotely. Execute the command on the desired host without specifying the logical host name.

KAVS0183-E
Unit name (unit-name) is too long.

The unit name is specified using a character string of more than 930 bytes.

(S)

Terminates processing.

(O)

Specify the unit name using no more than 930 bytes, and then re-execute the command.

KAVS0184-E
Invalid execution ID.: execution-ID

An invalid execution ID was specified.

(S)

Terminates processing.

(O)

Correct the execution ID, and then re-execute the command.

KAVS0185-E
Cannot operate - wait for activation condition.: unit-name

Processing is impossible because of the start-condition wait status.

(S)

Terminates processing.

(O)

Specify a unit which is not in the start-condition wait status, and then re-execute the command.

KAVS0186-E
Package file name not specified.

A package file name is missing.

(S)

Terminates processing.

(O)

Specify a package file name, and then re-execute the command.

KAVS0187-E
Invalid host name.: host-name

An invalid host name is specified.

(S)

Terminates processing.

(O)

Correct the host name, and then re-execute the command.

KAVS0188-E
Contradiction in options (option) value for the Unit (unit-name).

The values of options for the unit are inconsistent.

(S)

Cancels command execution.

(O)

Recheck the value of the option indicated in option in the message, and then re-execute the command.

KAVS0189-E
Database file install directory is invalid.: directory-name return-code

The specification in the AJSDBDIRECTORY environment setting parameter contains an error.

(S)

Abnormally terminates the service.

(O)

Check the directory specified for AJSDBDIRECTORY environment setting parameter, correct the setup, and then restart the service.

For details on the directory settings, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVS0190-E
The scheduler service (service-name) is not defined on the host (host-name).

The scheduler service is not defined for the execution target host. The probable causes are:

The specified host name is invalid.

The specified scheduler service name is invalid.

(S)

Terminates processing.

(O)

If you executed the ajssetup command, correct the specified host name (specified in the JP1_HOSTNAME environment variable or the -mh option) or the scheduler service name (specified in the AJSCONF environment variable or the -F option). Then re-execute the command.

For other commands, correct the specified host name (specified in the JP1_HOSTNAME environment variable) or the scheduler service name (specified in the AJSCONF environment variable or the -F option), and then re-execute the command.

For details about the environment variables, see 1.4 Environment variables in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVS0191-E
Cannot communicate with scheduler service.

Communication with the scheduler service was disabled because the service stopped during communication with the scheduler service or other reasons.

(S)

Terminates processing.

(O)

Make sure that the scheduler service is running. Determine the cause of the error, and then re-execute the command.

KAVS0192-E
Failed to make tables.: return-code

The file could not be created due to insufficient system resources.

(S)

Terminates processing.

(O)

Recheck the settings of the kernel parameters for semaphores and shared memory. Then, re-execute the ajssetup command.

For details about the kernel parameters, see Release Notes.

KAVS0193-E
Cannot use - Unit (unit-name) is in the suspend state.

The unit is suspended and cannot be used.

(S)

Cancels command execution.

(O)

Release the unit from the suspended state, and then re-execute the command.

KAVS0194-E
Cannot use - Unit (unit-name) is not in the suspend state.

The unit is not suspended and cannot be used.

(S)

Cancels command execution.

(O)

Unregister the execution of the unit or suspend the unit, and then re-execute the command.

KAVS0198-E
Cannot use - Unit (unit-name) is currently setting or releasing the suspend setting.

Another user is suspending the unit or releasing it from the suspended state. You cannot use the unit.

(S)

Cancels command execution. If you specify more than one unit (including specifications of regular expression), the system continues command execution.

(O)

Wait until the processing terminates, and then retry.

KAVS0199-E
Cannot use because the suspend function is ineffective.: unit-name

This operation could not be performed because the suspend function has not been set up for use.

(S)

Cancels command execution. If you specify more than one unit (including specifications of regular expression), the system continues command execution.

(O)

Perform setup with ajssetup -m so that the suspend function can be used, and then re-execute the command.

KAVS0200-I
Scheduler service started. (scheduler-service-name)

The scheduler service has started.

(S)

Continues processing.

KAVS0201-I
Scheduler service ended. (scheduler-service-name)

The scheduler service has terminated.

(S)

Terminates the scheduler service.

KAVS0202-E
Log daemon ended abnormally. (code: code)

The log daemon terminated abnormally.

(S)

Cancels the processing of the log daemon, but continues the operation by the scheduler service.

(O)

Contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS0203-I
Log file (scheduler-log-file-name-before-replacement) has been changed to scheduler-log-file-name-after-replacement.

The size of the scheduler log file exceeded the size that the configuration definition parameter specifies. The scheduler log file will be replaced.

(S)

Continues processing.

(O)

Make a backup scheduler log file as required.

KAVS0204-E
Scheduler service (scheduler-service-name) ended (name: process-name, code: return-code), but Scheduler service restart.

The scheduler service has abnormally terminated so it has restarted.

(S)

Continues processing.

(O)

Contact the system administrator, and collect data. For details, see 1.2.3 To the system administrators.

KAVS0208-E
Scheduler service is active.

The scheduler service has already started.

(S)

Terminates processing.

KAVS0209-E
Scheduler service is inactive.

The scheduler service has already stopped.

(S)

Terminates processing.

KAVS0210-I
Local time has been changed from local-date-and-time-before-change to local-date-and-time-after-change.

The local date and time of the scheduler service has been changed.

(S)

Terminates processing.

KAVS0211-W
Standstill of last scheduler service (process-name) was incomplete.

The previous termination of the scheduler service was incomplete. The running job may have been incorrectly stopped. Check the job status.

(S)

Continues startup of the service.

(O)

Check the execution status of jobs for any problem.

KAVS0213-I
The job-execution suppression option is set for the scheduler service (scheduler-service-name).

The job execution suppression option is set, preventing the job from being executed.

(S)

Continues processing.

(O)

Use ajsalter -s none to release the job execution suppression, and continue operation.

KAVS0214-I
The generation management sub-daemon (scheduler-service-name) started.

This message indicates that the generation management sub-process has started.

(S)

Continues processing.

KAVS0215-I
The generation management sub-daemon (scheduler-service-name) ended.

This message indicates that the generation management sub-process has ended.

(S)

Continues processing.

KAVS0216-E
The generation management sub-daemon (scheduler-service-name) ended abnormally. (code: code)

Since the generation management sub-process ended abnormally, the schedule control process (ajsschd) deletes jobnet registration information.

(S)

Continues processing.

(O)

Take actions according to the messages output before and after this error message.

KAVS0217-E
The generation management sub-daemon (scheduler-service-name) ended abnormally, so the generation management sub-daemon will now restart.

Since the generation management sub-process ended abnormally, it will be restarted.

(S)

Continues processing.

(O)

Take actions according to the messages output before and after this error message.

KAVS0218-E
The database is still being accessed, so the cold start of the scheduler service (scheduler-service-name) ended abnormally.

Since the scheduler service for which a cold start was attempted was still accessing the database, database registration information could not be deleted and the cold start of the scheduler could not be performed. The possible causes are:

JP1/AJS3 - View is connected to the object scheduler service.

A JP1/AJS3 command is executing on the object scheduler service.

(S)

Cancels processing.

(O)

Execute the jajs_hstd_stop command to stop the ajsinetd process temporarily, and sever all active connections from JP1/AJS3 - View, and then execute the jajs_hstd command to start the ajsinetd process. For details on the jajs_hstd and jajs_hstd_stop commands, see 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1. If any other command is being executed, wait until its execution ends or cancel processing.

Remove the process that is accessing the database. Then, use the jajs_spmd command with the -cold and -n jajs_schd options specified to perform a cold start of the object scheduler service again.

KAVS0219-E
Startup will now stop due to a stop request to the scheduler service. (scheduler-service-name)

Startup processing will stop because another user issued a stop request to the scheduler service.

(S)

Cancels command execution.

(O)

If you want to start the scheduler service, re-execute the command.

KAVS0220-I
Scheduler log output process started.

The scheduler log output process has started.

(S)

Continues processing.

KAVS0221-I
Scheduler log output process ended.

The scheduler log output process has ended.

(S)

The scheduler log output process has ended.

KAVS0222-E
Host name (host-name) is too long.

A host name is specified using a character string of more than 32 bytes.

(S)

Terminates processing.

(O)

Specify a host name that has fewer than 33 bytes, and then re-execute the command. For details on the jajs_migrate command, if it has been executed, see jajs_migrate in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVS0230-E
Connection to database has been reset.

The system has detected a database disconnection, and will stop the scheduler service.

(S)

Stops the scheduler service.

(O)

See the database message output to Windows event log or the syslog to correct the setting so that the scheduler service can be connected to the database, and then start the scheduler service.

KAVS0231-W
Cannot read job-status reporting port information, service name=service-name

Information for the service name indicated in the message cannot be read. The system assumes 20245 as the port number and starts the scheduler service.

(S)

Continues processing.

(O)

Check the services file, correct the service name, and then restart.

For details on the ports that JP1/AJS3 uses, see A.1 Tables of port numbers in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVS0232-W
Cannot read host name information.: maintenance-information-1 maintenance-information-2

Since information about the local host cannot be obtained, nothing will be set for the host name in termination messages for judgment jobs and OR jobs.

(S)

Continues processing.

(O)

Recheck the settings of JP1/Base host name information (JP1_HOSTNAME environment variable) and the network settings. Use the hostname command to make sure that the local host name is set correctly. Correct the settings, and then restart the scheduler service.

KAVS0240-I
Monitoring of a jobnet's start conditions started. (name: jobnet-name: execution-ID)

The jobnet starts the monitoring of the start condition. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS0241-I
Monitoring of a jobnet's start conditions ended. (name: jobnet-name: execution-ID, status: status)

The jobnet terminated the monitoring of the start condition. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter. The character strings displayed in status and their meanings are as follows:

u: The monitoring could not be started.

c: The monitoring canceled.

i: The monitoring was interrupted.

n: The monitoring normally terminated.

(S)

Continues processing.

KAVS0242-I
The execution request of the event job started. (name : jobnet-name : execution-ID)

The execution request of the event job starts. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS0243-E
Cannot terminate the jobnet(jobnet-connector-name : execution-ID) - jobnet for the connection destination is not registered.

Although execution of the jobnet connector started, the jobnet connector cannot be terminated because the connection-destination jobnet is not registered for execution.

(S)

Places the jobnet connector into Running + Abend status.

(O)

Check the connection-destination jobnet according to the definition of the jobnet connector displayed in the message, and then register that jobnet for execution.

KAVS0244-E
Cannot start the jobnet for the connection destination(jobnet-name : execution-ID) - jobnet connector is not registered.

Execution of the connection-destination jobnet cannot be started because the root jobnet for which the jobnet connector corresponding to the connection-destination jobnet is defined has not been registered for execution.

(S)

Places the connection-destination jobnet into Wait for start time status.

(O)

Check the jobnet connector according to the definition of the connection-destination jobnet displayed in the message, and then register the root jobnet for which the jobnet connector is defined for execution.

KAVS0245-W
The execution result (execution-ID : execution-ID) of the jobnet (jobnet-name) was deleted to create a new generation.

One generation of the execution result was deleted so that creating a new generation would not cause the number of jobnet generations to exceed the limit. For a jobnet with starting conditions, the execution result of generations that derived from the deleted generation being monitored were also deleted.

(S)

Continues processing.

KAVS0246-E
The system failed to delete the execution result (execution-ID : execution-ID) of the jobnet (jobnet-name).: maintenance-information

The system could not delete the execution result of one generation.

(S)

Continues processing.

(O)

Take actions according to the Windows event log or syslog message output immediately before this error message.

KAVS0247-E
An attempt to delete the execution result (execution-ID : execution-ID) of the jobnet (jobnet-name), which has a start condition, failed. : maintenance-information

The system failed to delete the execution-result generation of a jobnet that has a start condition because memory was insufficient. Also, the oldest generation of execution results was deleted. The system continues processing of the jobnet that has a start condition without aborting.

(S)

The system deletes the oldest generation of the execution results and continues processing.

(O)

Check the following settings.

In UNIX, see Release Notes, and make sure that the value of the kernel parameter for memory is greater than the estimated value.

Check the status of the process that was running when the error occurred to make sure that the amount of memory available is greater than the estimated value.

To confirm the status of the deleted generation of the execution result, refer to the scheduler logs.

KAVS0248-I
End of a Job delayed. (name: job-name: execution-ID)

End of a job is delayed. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS0249-W
The scheduler services stopped before execution of the job(job-name : execution-ID) began.

The scheduler service stopped before the job was placed in Running status. As a result, if execution of the job begins on the agent, the job status changes to Running when the scheduler service is started. This might cause a delay during delay detection for the required execution time for a job.

(S)

Continues processing.

(O)

Use the ajsshow command to check the execution start time or end time of the job executed on another host, and check whether the job has been running for a long time, exceeding the required execution time.

KAVS0251-I
maintenance-information

A queueless job started execution. For details on maintenance information, see C.2 Log entries output by the queueless agent service in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

(S)

Continues processing.

KAVS0252-I
maintenance-information

The queueless job terminated normally. For details on maintenance information, see C.2 Log entries output by the queueless agent service in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

(S)

Continues processing.

KAVS0253-E
maintenance-information

The queueless job terminated abnormally. For details on maintenance information, see C.2 Log entries output by the queueless agent service in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

(S)

Continues processing.

(O)

Determine the cause of the error by checking the integrated trace log or the detailed log of the job, correct the cause of the error, and then restart the appropriate job.

KAVS0254-W
maintenance-information

The queueless job completed with a warning. For details on maintenance information, see C.2 Log entries output by the queueless agent service in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

(S)

Continues processing.

(O)

Determine the cause of the error by checking the integrated trace log or the detailed log of the job, correct the cause of the error, and then restart the appropriate job.

KAVS0260-I
Jobnet started. (name: jobnet-name: execution-ID)

The jobnet starts. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS0261-I
Jobnet ended normally. (name: jobnet-name: execution-ID)

The jobnet has normally terminated. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS0262-E
Jobnet ended abnormally. (name: jobnet-name: execution-ID)

The jobnet has abnormally terminated.

(S)

Continues processing. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(O)

Check the execution status of the units contained in the jobnet to examine the cause of the unsuccessful execution, and then take action to correct it.

KAVS0263-I
Job started.(name: jobnet-name: execution-ID, host: host-name, JOBID: job-number)

The job starts.

(S)

Continues processing. execution-ID , host-name, and job-number appear if you specified yes for the LOGINFOALL environment setting parameter.

KAVS0264-I
Job ended normally. (name: job-name: exception-ID, host: host-name, code: code, JOBID: job-number)

The job has normally terminated. execution-ID , code, and job-number appear if you specify yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS0265-E
Job ended abnormally. (name: job-name: exception-ID, status: status, code: code, host: host-name, JOBID: job-number)

The job has abnormally terminated.

The character strings displayed in status and their meanings are as follows:

a: An error was detected.

f: The job could not be started.

c: The job forcibly terminated.

?: Unknown status.

For details, see the Execution Result Details dialog box.

execution-ID and job-number appear if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

(O)

Examine the cause of the error and take action to correct it. If you cannot determine the cause of the error, collect data and then contact the system administrator (see 1.2.3 To the system administrators).

If code 128 is displayed for a PC job, the job may have terminated abnormally due to a desktop heap that is too small.

See 4.2.3 Changing the JP1/AJS3 service settings (Windows only) in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide and, if necessary, check the account of the JP1/AJS3 service. You must also take measures such as checking the number of concurrent jobs or the startup processes for the entire system to prevent errors caused by a desktop heap that is too small.

This message also appears when you start the JP1/AJS3 service after executing the jpomanevreset command without the -e option. In this case, however, ignore the message because it is output as a result of terminating an event job by resetting the event.

KAVS0266-I
To submit Job again, it is canceled. (name: job-name: exception-ID, JOBID: job-number)

When the scheduler service stops, a job that has been queued by job execution control is canceled.

execution-ID and job-number appear if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Cancels the job that has been queued by job execution control and returns the job status to Wait for prev. to end. Then, the job is resubmitted and placed in the Now queuing status. Note, however, that if the previous unit ended abnormally, the job is not resubmitted, but is placed in the Not executed + Ended status.

KAVS0267-I
All Jobnet entries canceled. (scheduler-service-name)

All jobnet entries have been forcibly canceled.

(S)

Continues the cold-start process for the scheduler service.

(O)

If necessary, inform the jobnet owner, that registration was canceled.

KAVS0268-W
Jobnet ended with warning. (name: jobnet-name: execution-ID)

The jobnet has terminated with a warning. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

(O)

Check the execution status of the units contained in the jobnet to examine the cause of the unsuccessful execution, and then take action to correct it.

KAVS0269-W
Job ended with warning. (name: job-name: exception-ID, code: code, host: host-name, JOBID: job-number)

The job has terminated with a warning. The job has terminated with a warning. execution-ID and job-number appear if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

(O)

Examine the cause of the warning and take action to correct it. For details on the job execution results, check the Execution Result Details dialog box for JP1/AJS3 - View.

KAVS0270-I
Jobnet cannot be executed while being held. (name: jobnet-name: execution-ID)

The jobnet cannot be executed while being held. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

(O)

Release the jobnet from being held as required.

KAVS0271-I
Job cannot be executed while being held. (name: jobnet-name: execution-ID)

The job cannot be executed while being held. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

(O)

Release the job from being held as required.

KAVS0272-E
Jobnet (jobnet-name: execution-ID) cannot be executed - error (maintenance-information) occurred.

The error indicated by maintenance-information occurred. The jobnet cannot be executed. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Blocks the jobnet.

(O)

See the message output before this message to examine the cause of the error and correct it. Then, unregister the blocked jobnet and reregister it.

KAVS0273-E
Jobnet (jobnet-name: execution-ID) cannot be scheduled - error (maintenance-information) occurred.

The error, that prevented processing, indicated by maintenance-information occurred. The jobnet cannot be scheduled. The probable cause is that a unit which does not exist is specified in Exclusive schedule or Refer to a calendar of another job group in the schedule definition of the jobnet. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Blocks the jobnet.

(O)

Make sure that the settings for Exclusive schedule and Refer to a calendar of another job group in the schedule definition of the jobnet are correct. If they are correct, see the message output before this message to examine the cause of the error and correct it.

Then, unregister the blocked jobnet and reregister the jobnet.

KAVS0274-E
The number of jobnets for execution registration exceeded the limit. (Jobnet: jobnet-name, code: code)

The number of jobnets for execution registration exceeded the limit. The jobnet cannot be scheduled.

(S)

Does not schedule the jobnets.

(O)

Unregister unnecessary jobnets and then reregister the jobnets.

KAVS0275-I
Start of a Jobnet delayed. (name: jobnet-name: execution-ID)

The jobnet is delayed starting. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS0276-I
End of a Jobnet delayed. (name: jobnet-name: execution-ID)

The jobnet is delayed stopping. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS0277-I
Start time for next execution schedule has been reached. (name: jobnet-name: execution-ID)

Since the start time for the next execution schedule was reached or because the start condition was satisfied, an attempt was made to start a new jobnet during execution of another jobnet. However, the multiple startup was not specified. The new jobnet was queued.

Alternatively, a timeout occurred for the jobnet for which start conditions were set.

execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

(O)

Take action according to your operation.

For details on actions to be taken for a jobnet for which start conditions were set, see 9.1.1 Stopping a jobnet that is monitoring start conditions in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

KAVS0278-I
Job submit started. (name: jobnet-name: execution-ID)

Submission of the job starts. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues processing.

KAVS0279-E
Jobnet ended with execution-deferred status. (name: jobnet-name: execution-ID)

The jobnet terminated with the execution-deferred status. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter.

(S)

Continues performing the scheduler control process.

KAVS0289-E
Manager's host name not specified.

The execution manager for the remote jobnet is not specified.

(S)

Abnormally terminates the remote jobnet.

(O)

Correctly specify the execution manager for the remote jobnet, and then register the remote jobnet for execution.

KAVS0291-E
Specified host name does not exist.: host-name

The specified host name does not exist.

(S)

For job execution: Abnormally terminates the job (as unsuccessful startup) and continues processing.

For command execution: Cancels executing the command.

(O)

Specify the correct host name and then retry.

KAVS0297-E
Cannot create directory or file (directory-name or file-name).: maintenance-information-1 maintenance-information-2 maintenance-information-3

A directory or a file could not be created due to a cause such as no access permission for the temporary file directory.

(S)

Cancels processing.

(O)

Make sure that you have update permission for the temporary file directory.

If this error occurs when you register a root jobnet for a fixed execution from JP1/AJS3 - View, another user may also be registering a jobnet for a fixed execution. Wait until the other user finishes the fixed execution registration, and then re-execute the fixed execution registration.

KAVS0300-E
Unit does not exist.

The cause may be either of the following:

Another user deleted the specified unit.

The calendar information about the jobnet schedule for execution registration does not contain the specified job group.

(S)

Terminates processing.

(O)

Re-open the window.

KAVS0301-E
No authorization.

You do not have authorization for the unit (including the lower-level unit) or the associated file (such as the standard error output file). Alternatively, memory became insufficient during user mapping for the JP1 user specified in the JP1_USERNAME environment variable, preventing the authorization check for the unit.

(S)

Terminates processing.

(O)

Execute processing with the authorization.

KAVS0304-E
In use by other user.

Another user is using the unit.

(S)

Terminates processing.

(O)

Wait for the other user to complete using the unit, and then retry.

KAVS0311-E
Invalid Unit definition.

An invalid definition is made for the unit.

(S)

Cancels processing. If you specify more than one unit definition file name, the system continues processing.

(O)

Specify the unit definition file correctly, and then re-execute the command.

For details about how to set up unit definition files, see 4. Creating Information Definition Files in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVS0314-E
File processing count exceeds the limit.

The number of files to be processed exceeded the limit.

(S)

Cancels processing.

(O)

Close unnecessary windows and dialog boxes, and delete unnecessary files to increase available free space. Then re-execute the operation.

In UNIX, check the following items in the kernel parameters:

Maximum number of files allowed to be open for a process or system

Maximum number of file descriptors allowed (a limit value related to the file system)

Also see Release Notes, and change the settings for the file system.

KAVS0315-E
Not enough space in file system.

The file system does not have sufficient space.

(S)

Cancels processing.

(O)

Close unnecessary windows and dialog boxes, and delete unnecessary files to increase available free space. Then re-execute the operation.

In UNIX, check the following items in the kernel parameters:

Maximum number of files allowed to be open for a process or system

Maximum number of file descriptors allowed (a limit value related to the file system)

Also see Release Notes, and change the settings for the file system.

KAVS0317-E
Lock resources count exceeds the limit.

The number of file lock resources exceeded the limit that the system can process.

(S)

Terminates processing.

(O)

Close unnecessary windows and dialog boxes, and delete unnecessary files to increase available free space. Then re-execute the operation.

In UNIX, check the following items in the kernel parameters:

Maximum number of files allowed to be open for a process or system

Maximum number of file descriptors allowed (a limit value related to the file system)

Also see Release Notes, and change the settings for the file system.

KAVS0318-E
System resources became insufficient.

A shortage of system resources occurred.

(S)

Terminates processing.

(O)

Close unnecessary windows or dialog boxes. Then, retry.

In UNIX, check the following items in the kernel parameters:

Maximum number of files allowed to be open for a process or system

Maximum number of file descriptors allowed (a limit value related to the file system)

For details about the kernel parameters, see Release Notes.

KAVS0319-E
Files not exist or cannot access files by insufficient system resources.: maintenance-information

The system cannot access files for one of the following reasons:

A lock file or ISAM file does not exist.

The directory specified in the AJSTMPDIR environment setting parameter does not exist.

The target backup box or backup file was deleted by the ajsbkudel command while the Backup or Restore dialog box was displayed in JP1/AJS3 - View.

System resources are insufficient.

(S)

Terminates processing.

(O)

Make sure that a lock file or ISAM file exists in the database directory specified in the AJSDBDIRECTORY environment setting parameter. If the file does not exist, set up the scheduler service. If the file exists, make sure that the directory for temporary files specified in the AJSTMPDIR environment setting parameter exists.

If the target backup box or backup file was deleted by the ajsbkudel command while the Backup or Restore dialog box was displayed in JP1/AJS3 - View, close the Backup or Restore dialog box in JP1/AJS3 - View, and then redisplay it.

For any other case, recheck the settings of the semaphores and shared memory in the kernel parameters.

For details about the kernel parameters, see Release Notes.

KAVS0322-E
Cannot operate - Scheduler service has not started.

Processing is impossible because the specified scheduler name is incorrect or the scheduler service has not started.

Alternatively, processing using the terminal service is impossible because Windows Terminal Service is not linked.

(S)

Terminates processing.

(O)

Check the specified scheduler name and start the JP1/AJS3 service, and then retry. If this message appears during execution of a remote jobnet, start the scheduler service specified in either of the following items on the host where the remote jobnet was executed: the REMNETSERVICENAME environment setting parameter. Then, retry.

For the following commands, start the JP1/AJS3 service, and then retry.

ajsalter

ajschgstat

ajsentry

ajsintrpt

ajskill

ajsleave

ajsplan

ajsrelease

ajsrerun

ajsstart

ajsstop

ajssuspend

Alternatively, re-execute the operation in an environment that does not use the terminal service.

KAVS0358-E
Cannot operate - JP1/AJS service has not started. (logical host=logical-host-name)

Operation is impossible because the JP1/AJS3 service has not started.

(S)

Terminates processing.

(O)

Start the JP1/AJS3 service, and then re-execute the command.

KAVS0369-E
Cannot operate - version is different.

Processing is impossible because the version of JP1/AJS3 that manages the unit to be processed does not match that of JP1/AJS3 on the operating side.

(S)

Continues processing.

(O)

Contact a user who has superuser privileges or is logged on as a member of the Administrators group to check the version.

KAVS0435-E
Environment file name length exceeds 255 bytes.

The length of the environment variable file name exceeded 255 bytes.

(S)

Cancels processing.

(O)

Specify an environment variable file name that is less than 256 bytes, and then retry.

KAVS0439-E
Complete Unit name is too long.

The full name of the specified unit exceeded the limit.

The limits are as follows:

Job name and recovery job name
930 bytes or less

Other names than above
899 bytes or less

(S)

Cancels processing.

(O)

Specify the full unit name within the limit, and then retry.

KAVS0470-E
Among the generations registered in the specified period, there is no generation whose registration can be canceled. (unit-name)

There is no information registered in the specified period. This prevented the registration from being canceled.

(S)

Cancels command execution.

(O)

Check the period specified for canceling the registration, and then re-execute the command.

KAVS0475-I
There is no log record that satisfies the specified conditions.

Information cannot be output because there is no log record that satisfies the specified conditions.

(S)

Cancels command execution.

(O)

Correctly specify the conditions, and then re-execute the command.

KAVS0476-E
Invalid format in the specified scheduler log file. (line:line-number)

An invalid format log record was found in the line indicated in line-number in the specified scheduler log file.

(S)

Continues processing from the next line of the line indicated in line-number.

(O)

Check the contents of the scheduler log file and, if necessary, re-execute the command.

KAVS0477-E
Scheduler log file name not specified.

A scheduler log file name is not specified.

(S)

Cancels command execution.

(O)

Specify a scheduler log file name, and then re-execute the command.

KAVS0478-E
Scheduler log file name is too long.

A scheduler log file name is specified using a character string of more than 255 bytes.

(S)

Cancels command execution.

(O)

Specify a scheduler log file name that has fewer than 256 bytes, and then re-execute the command.

KAVS0500-E
Scheduler service has already started.

The scheduler service has already started.

(S)

Cancels command execution.

(O)

Use the jajs_spmd_status command to check the status of the process.

Also make sure that the procedures for adding and deleting a scheduler service and a logical host are correct. For details on the procedures, see 6.1.1 Settings for starting multiple scheduler services in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1, 8.2 Setting up the operating environment for cluster system operation in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1, 14.1.1 Settings for starting multiple scheduler services in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1, and 16.2 Setting up the operating environment for cluster system operation in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVS0530-I
JP1/AJS2 Monitor service started.

ajsinetd process starts.

(S)

Continues processing.

KAVS0531-I
JP1/AJS2 Monitor service stopped.

ajsinetd process terminates.

(S)

Terminates the ajsinetd process.

KAVS0532-I
JP1/AJS2 Monitor service started accepted processing. (From: IP-address, To: logical-host-name, JP1-user-name, PID: process-ID)

ajsinetd process starts the processing that is accepted. The monitor server that ajsinetd accepted from IP-address has started on logical-host-name.

(S)

Continues processing.

KAVS0533-I
JP1/AJS2 Monitor service ended accepted processing. (From: IP-address, To: logical-host-name, JP1-user-name, PID: process-ID)

ajsinetd process terminated the processing that was accepted. The monitor server that ajsinetd accepted from IP-address and started on logical-host-name has terminated.

(S)

ajsinetd process terminated the processing that was accepted.

KAVS0534-I
JP1/AJS2 - View has been connected to the scheduler service (scheduler-service-name). (JP1-user-name (OS-user-name), process-ID)

JP1/AJS3 - View was connected to the scheduler service.

(S)

Continues processing.

KAVS0535-I
JP1/AJS2 - View has been disconnected from the scheduler service(scheduler-service-name). (JP1-user-name (OS-user-name, process-ID)

JP1/AJS3 - View was disconnected from the scheduler service.

(S)

JP1/AJS3 - View disconnects from the scheduler service.

KAVS0540-Q
Ok to change the local time? (y:OK/n:NO)

This message checks whether you want to change the local date and time.

(S)

Waits for a response.

(O)

Enter y to change the local date and time.

Enter n not to change the local date and time.

KAVS0541-E
Specified local time is not acceptable.

The local date and time to be changed was specified outside the range (between the year 1994 and 2036).

(S)

Cancels processing.

(O)

Set the local date and time within the range from the year 1994 to 2036.

KAVS0545-I
The shift processing of JP1/AJS3 to a standard composition has started.

The migration processing of JP1/AJS3 to the standard configuration has started.

(S)

Continues processing.

KAVS0546-I
The shift processing of JP1/AJS3 to a standard composition ended normally.

The migration processing of JP1/AJS3 to the standard configuration terminated normally.

(S)

Terminates command processing normally.

KAVS0547-E
The shift processing of JP1/AJS3 to a standard composition ended abnormally.

The migration processing of JP1/AJS3 to the standard configuration terminated abnormally.

(S)

Cancels processing.

(O)

Correct the error and then retry.

KAVS0548-I
The shift processing of JP1/AJS3 to a standard composition has already been completed.

The migration processing of JP1/AJS3 to the standard configuration has already been completed.

(S)

Cancels command execution.

KAVS0549-E
Because the JP1/AJS3 service has started, the shift processing of JP1/AJS3 to a standard composition has been discontinued.
The migration processing of JP1/AJS3 to the standard configuration has been canceled because the JP1/AJS3 service has started. In UNIX, shared memory information might not have been deleted after the JP1/AJS3 service was stopped.

(S)

Cancels processing.
(O)

Stop the JP1/AJS3 service, and then retry.

In UNIX, stop the JP1/AJS3 service, and execute the ajsshmdel command. The path to the ajsshmdel command is /opt/jp1ajs2/bin/ajsshmdel.

The following are examples of executing the command:
For sh:
/opt/jp1ajs2/bin/ajsshmdel >/dev/null 2>&1
For csh:
/opt/jp1ajs2/bin/ajsshmdel >&/dev/null
KAVS0550-E
An error occurred in the shift processing of JP1/AJS3 to the standardized configuration. : maintenance-information-1 maintenance-information-2

An error occurred during migration processing of JP1/AJS3 to the standard configuration.

(S)

Cancels processing.

(O)

Take action according to the information output in the detailed information, and then retry.

KAVS0582-E
Specified data format is not acceptable for the environment variable.: environment-variable-name

An invalid environment variable was specified.

(S)

Cancels command execution.

(O)

Correct the environment variable, and then re-execute the command.

For details on the environment variables, see 1.4 Environment variables in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

KAVS0600-E
Valid calendar definition options not specified.

The calendar definition does not contain the required option.

(S)

Cancels command execution.

(O)

Specify the option in the calendar definition, and then re-execute the command.

KAVS0601-E
Date information file (file-name) does not exist.

The date information file does not exist.

(S)

Continues command execution. Cancels the processing of the uncreated file.

(O)

Create the date information file, and then re-execute the command.

KAVS0602-E
Illegal date (date) specified.

An illegal date was specified.

(S)

Continues command execution. The system invalidates the illegal date.

(O)

Correct the date, and then re-execute the command.

KAVS0603-E
Illegal character exists in option string (option-character-string).

The option or the date information file contains an illegal character.

(S)

Continues command execution. The system invalidates the illegal character.

(O)

Correct the character in the option or in the date information file. Then, re-execute the command.

KAVS0604-E
Cannot read date information file (file-name) - error occurred.

An error occurred during input into the date information file.

(S)

Continues command execution. The system invalidates the file where the error occurred.

(O)

Check the specified date information file (open day information file, closed day information file, cancellation day information file, or calendar information file) to correct the cause of the error, and then re-execute the command.

KAVS0605-E
Cannot read date information file (file-name) - no authority.

The date information file does not have any access permission.

(S)

Continues command execution. The system invalidates the file for which you have no access permission.

(O)

Set access permission for the specified date information file (open day information file, closed day information file, cancellation day information file, or calendar information file), and then re-execute the command.

KAVS0620-Q
Ok to clear Unit (unit-name) ? (y:OK/n:NO)

This message checks whether you want to clear the unit.

(S)

Waits for a response.

(O)

Enter y to clear the unit.

Enter n not to clear the unit.

KAVS0621-E
Cannot delete - Unit (unit-name) is registered.

The specified unit cannot be deleted because it is contained in a registered root jobnet or a registered jobnet.

(S)

Cancels command execution.

(O)

Unregister the unit, and then re-execute the command. To delete jobnets and jobs defined in a suspended root jobnet, re-execute the command with the -S option.

KAVS0622-E
Cannot delete - Unit (unit-name) has registered Jobnet.

The unit that contains a registered jobnet cannot be deleted.

(S)

Cancels command execution.

(O)

Unregister the jobnet, and then re-execute the command.

KAVS0623-E
Cannot delete - Unit (unit-name) is running.

You cannot delete the running unit.

(S)

Cancels command execution.

(O)

Waits for the processing of the unit to terminate, and then re-execute the command.

KAVS0630-E
Cannot copy - Unit (unit-name) is already registered.

The output destination unit cannot be copied because it has already been registered.

(S)

Cancels command execution.

(O)

Unregister the output destination unit, and then re-execute the command. To copy jobnets and jobs into a suspended root jobnet, re-execute the command with the -S option.

KAVS0631-E
Cannot move - Unit (unit-name) is already registered.

The output destination unit cannot be moved because it has already been registered.

(S)

Cancels command execution.

(O)

Unregister the output destination unit, and then re-execute the command. To move jobnets and jobs into a suspended root jobnet, re-execute the command with the -S option.

KAVS0632-E
Cannot move - Unit (unit-name) contains a registered Jobnet.

The output destination unit cannot be moved because it contains a registered jobnet.

(S)

Cancels command execution.

(O)

Unregister the output destination unit, and then re-execute the command. To move jobnets and jobs into a suspended root jobnet, re-execute the command with the -S option.

KAVS0633-E
Cannot move - Unit of the same name (unit-name) exists.

A unit that with the same name already exists in the move-destination.

(S)

Cancels command execution.

(O)

Change the unit name, and then re-execute the command.

KAVS0634-E
Cannot copy - Unit of the same name (unit-name) exists.

A unit with the same name already exists in the copy-destination.

(S)

Cancels command execution.

(O)

Change the unit name, and then re-execute the command.

KAVS0635-E
Cannot copy - Unit (unit-name) does not exist.

An attempt was made to copy more than one unit. However, copying was impossible because the destination unit does not exist.

(S)

Cancels command execution.

(O)

Create the destination unit, and then re-execute the command.

KAVS0636-E
Cannot move - Unit (unit-name) does not exist.

An attempt was made to move more than one unit. However, moving was impossible because the destination unit does not exist.

(S)

Cancels command execution.

(O)

Create the destination unit, and then re-execute the command.

KAVS0637-E
Output Unit name not specified.

An output unit name is missing.

(S)

Cancels command execution.

(O)

Specify the output destination unit name in the -o option, and then re-execute the command.

KAVS0638-E
Cannot treat as output Unit.: unit-name

The unit indicated in unit-name cannot be handled as an output destination unit.

(S)

Cancels command execution.

(O)

Recheck the conditions for the unit that you attempted to copy or move, and then re-execute the command.

KAVS0639-E
Cannot copy the Unit (unit-name) - currently used by another user.

Another user is using the unit, preventing it from being copied.

(S)

Cancels command execution.

(O)

Wait for the other user to complete using the unit, and then re-execute the command.

KAVS0640-E
Cannot move the Unit (unit-name) - currently used by another user.

Another user is using the unit, preventing it from being moved.

(S)

Cancels command execution.

(O)

Wait for the other user to complete using the unit, and then re-execute the command.

KAVS0641-E
No authority to use output Unit (unit-name).

The output unit does not have any authority, preventing it from being defined. The probable causes are:

You do not have update permission for the output destination unit.

You do not have reference permission for units above the output destination unit.

(S)

Cancels command execution.

(O)

Re-execute the command as a user who has update permission for the output destination unit or who has reference permission for the upper-level unit of the output destination unit.

KAVS0647-E
A unit other than a jobnet in the planning-group cannot be moved.: unit-name

An attempt was made to move a unit other than the jobnet or the remote jobnet into the planning group.

(S)

Terminates processing. If you specify more than one unit, the system continues processing of the units of the jobnet or the remote jobnet.

(O)

Check whether the output destination is the planning group. Correct the unit name, and then re-execute the command.

KAVS0648-E
A unit other than a jobnet in the planning-group cannot be copied.: unit-name

An attempt was made to copy a unit other than the jobnet or the remote jobnet into the planning group.

(S)

Terminates processing. If you specify more than one unit, the system continues processing of the units of the jobnet or the remote jobnet.

(O)

Check whether the output destination is the planning group. Correct the unit name, and then re-execute the command.

KAVS0650-E
Invalid specification in the Unit definition parameter file (file-name). (sentence: sentence-number)

The unit definition parameter file contains an invalid specification. A cause may be one or more of the following:

The unit definition parameter has an invalid syntax.

The unit definition parameter file contains the combination of parameters that cannot be specified simultaneously.

A parameter that must be specified together is missing.

The hierarchical limit was exceeded.

The number of definition units reached the limit.

An attempt was made to create a job group, planning group, or manager unit in a jobnet.

An attempt was made to create a unit in a job, manager unit or start condition unit.

The root jobnet contains an invalid parameter.

An attempt was made to create more than 32 event jobs in the start condition.

An invalid combination of associated definitions was specified.

An attempt was made to create a unit other than an event job or a unit having the recovery attribute in the start condition.

A unit contained in the remote jobnet used a function not supported by the version of the manager where the jobnet is to be executed.

The custom job contains an invalid parameter. If 0 is output for sentence-number in the message, identify the unit that contains the error from the unit name indicated in file-name concurrently with the file name.

(S)

Cancels command execution. If you specify more than one unit definition parameter file name, the system continues processing.

(O)

For a unit definition file, see 4.1 Creating a unit definition file in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2 and check the unit definition parameter file, and then re-execute the command.

KAVS0651-E
Cannot define - Unit (unit-name) is already registered.

The unit contains the registered jobnet, preventing a unit from being defined.

(S)

Cancels command execution. If you specify more than one unit definition file name, the system continues processing.

(O)

Unregister the unit, and then re-execute the command.

KAVS0652-E
Cannot define - Unit of the same name (unit-name) exists.

A unit with the same name already exists in the definition-destination, preventing it from being defined.

(S)

Cancels command execution. If you specify more than one unit definition file name, the system continues processing.

(O)

Change the unit name, and then re-execute the command.

KAVS0653-E
Cannot treat as definition Unit.: unit-name

unit-name cannot be the definition-destination unit. The possible causes are:

The unit specified as the definition-destination does not exist.

The type of the unit specified as the definition-destination is one of the following:
- Job
- Manager jobnet
- Manager job group

(S)

Cancels command execution.

(O)

Correctly specify the definition-destination unit, and then re-execute the command.

KAVS0654-E
Cannot use the unit (unit-name) - currently used by another user.

Another user is using the unit, preventing it from being defined.

(S)

Cancels command execution.

(O)

Wait for the other user to complete using the unit, and then re-execute the command.

KAVS0655-E
Not authorized to access the definition parameter file (file-name).

The unit definition file does not have any access permission.

(S)

Cancels command execution. If you specify more than one unit definition file name, the system continues processing.

(O)

Set the access permission for the unit definition file, and then re-execute the command.

KAVS0656-Q
Ok to update Unit (unit-name) ? (y:OK/n:NG)

This message checks whether you want to update the unit.

(S)

Waits for a response.

(O)

Enter y to update the unit.

Enter n not to update the unit.

KAVS0657-E
Cannot treat as a unit definition parameter file.: file-name

The file was specified in a format that the unit definition parameter file cannot use, preventing it from being analyzed.

(S)

Cancels command execution. If you specify more than one unit definition parameter file name, the system continues processing.

(O)

Specify the file in the format that the unit definition parameter file can use, and then re-execute the command.

KAVS0658-E
Cannot define Unit (unit-name).

It is impossible to define the unit because of the following reasons:

An attempt was made to define a job group in a jobnet.

An attempt was made to define a unit in a job.

An attempt was made to define the start condition (.CONDITION) in a unit other than the root jobnet.

The number of units that can be defined in a unit exceeded the limit (map-size).

The number of event jobs that can be defined in the start condition (.CONDITION) exceeded the limit (32).

The number of hierarchies exceeded the limit.

The length of the full name of the unit exceeded the limit (930 bytes).

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVS0659-E
No authority to use definition unit (unit-name).

The definition unit does not have any authority, preventing it from being defined.

(S)

Cancels command execution.

(O)

Execute the command with the authority for the definition unit.

KAVS0660-E
Unit (unit-name) left over.

An error occurred while creating the units. An attempt to delete them was unsuccessful, and some of them could not be deleted.

(S)

Cancels command execution.

(O)

Use the ajsdelete command to delete the remaining units.

KAVS0661-E
Cannot define - Unit (unit-name) is running.

You cannot forcibly update the running unit.

(S)

Cancels command execution.

(O)

Wait for the unit to terminate execution, and then re-execute the command.

KAVS0665-E
A unit other than a jobnet in the planning-group cannot be defined.: unit-name

An attempt was made to define a unit other than a jobnet or remote jobnet into the planning group.

(S)

Terminates processing.

(O)

Check whether the definition destination is the planning group. Correct the unit name, and then re-execute the command.

KAVS0670-E
Definition is invalid. (Jobnet: jobnet-name)

Schedule definition information about the jobnet contains errors. The possible causes are:

The specified job group does not exist in the calendar to be referenced.

The specified jobnet does not exist in the exclusive schedule.

(S)

Cancels the execution of the schedule control process.

(O)

Specify schedule definition information about the jobnet correctly.

For details on how to reference a calendar of other job groups and an explanation of exclusive schedules, see 3.3.2 Defining a schedule in the manual Job Management Partner 1/Automatic Job Management System 3 Overview.

KAVS0671-E
Error occurred in file (file-name).: return-code

The following errors occurred during creation of the definition information file in the host where the remote jobnet was executed.

The disk does not have any free space.

An I/O error occurred in the disk.

The file was deleted.

(S)

Abnormally terminates the remote jobnet.

(O)

Determine the cause of the error, and then re-execute the command.

KAVS0681-E
Jobnet (jobnet-name) already registered.

The jobnet has already been registered.

(S)

Cancels command execution.

(O)

Specify another jobnet, and then re-execute the command.

KAVS0682-E
Registerable Jobnet number exceeds the limit.

The number of jobnets to be registered exceeded the limit.

(S)

Cancels command execution.

(O)

Unregister unnecessary jobnets, and then retry.

KAVS0683-E
Specified Jobnet (jobnet-name) cannot be registered.

The jobnet cannot be registered because of the following reasons:

The effective registration date expired.

The registration date exceeded the execution start date, but the process cycle or an alternate method is missing.

The execution start date is a holiday, but the process cycle is missing.

The next execution date is the year 2037 or later.

(S)

Cancels command execution.

(O)

Remove the cause of the error, and then re-execute the command.

KAVS0684-E
Exclusion Jobnet definition of Jobnet (jobnet-name) is invalid.

A jobnet or local jobnet that is not in the same hierarchy was defined.

(S)

Terminates processing.

(O)

Define a jobnet other than the main jobnet in the same hierarchy, and then re-execute the command.

KAVS0685-E
Calendar definition of Jobnet (jobnet-name) is invalid.

The calendar definition contains invalid information.

(S)

Cancels command execution.

(O)

Correct the calendar information, and then re-execute the command.

For details about the format of the calendar definition, see ajscalendar in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

KAVS0686-E
None of the start definitions of the Jobnet (jobnet-name) are defined.

None of the start dates is defined.

(S)

Terminates processing.

(O)

Define the start dates, and then re-execute the command.

KAVS0694-E
Permission for the file (file-name) is lacking, so a jobnet-end wait is impossible.

The jobnet-end wait option (-w) cannot be used, since the jobnet-end wait file does not have update permission.

(S)

Cancels command processing.

(O)

The jobnet-end wait file is AJSNETWT.LCK in the directory storing the database. Give update permission to the file, and then reenter the command.

KAVS0695-E
The file (file-name) does not exist, so a jobnet-end wait is impossible.

The jobnet-end wait option (-w) cannot be used because of the following reasons.

The jobnet-end wait file cannot be allocated because the service has not started.

(S)

Cancels command processing.

(O)

Check whether the service has started.

If it has not started, start the JP1/AJS3 service and reenter the command.

KAVS0696-E
The jobnet-end wait count exceeded the limit, so the operation cannot be performed.

The maximum number of jobnet-end waits that can be executed concurrently was exceeded. The jobnet-end wait option (-w) cannot be used.

(S)

Cancels command processing.

(O)

Wait for termination of other running ajsentry or ajsplan commands with the -w option, and then reenter the command.

If there are no other ajsentry or ajsplan commands with the -w option running, you will need to restart the JP1/AJS service.

KAVS0697-E
The jobnet registration method is incorrect.: unit-name

The root jobnet under the planning group can only be defined by the ajsentry command with the -p option.

(S)

Cancels command execution. If you specify more than one unit, the system continues processing of the units of the other jobnets.

(O)

Check the unit to register and the command option, correct the error, and then re-execute the command.

KAVS0698-E
A new generation of the jobnet (jobnet-name) could not be created because the number of jobnet generations has reached the system limit.

The system attempted to delete one generation of execution results so that the number of jobnet generations would not exceed the limit at the following times: when a jobnet is registered for fixed execution by specifying a period or date and when an execution a schedule is added in the temporary change of the schedule. The system, however, could not create a new generation because no generations were provided with the execution results.

(S)

Cancels processing.

(O)

The number of jobnet generations (excluding generations created when starting conditions are satisfied) cannot exceed 8,000.

To register a jobnet for fixed execution by specifying a date or to add an execution schedule in the temporary change of the schedule, re-execute the operation after one or more generations being executed end.

When registering jobnets for fixed execution by specifying a period, note that generations up to 8,000 have been registered.

For generations that exceed 8,000, re-execute the registration after the number of generations that have been executed enables more generations to be registered.

KAVS0699-E
A new generation of the jobnet (jobnet-name) could not be created because the system failed to delete an execution result.

The system attempted to delete one generation of execution results so that the number of jobnet generations would not exceed the limit at the following times: when a jobnet is registered for fixed execution by specifying a period or date and when an execution a schedule is added in the temporary change of the schedule. The system, however, could not create a new generation because it failed to delete the execution result.

(S)

Cancels processing.

(O)

Take action according to the Windows event log or the syslog message output immediately before this error message

KAVS0700-W
A unit was deleted during the command processing.

The specified unit no longer exists. It may have been deleted, or moved.

(S)

Cancels command execution. If you specify more than one unit (including specifications of regular expression), the system continues command execution.

(O)

Check whether the specified unit exists. Specify the unit, and then re-execute the command.

KAVS0701-E
A unit that is the target of the operation was not found.: unit-name

If you execute the command with the -x option or with yes or auto specified for the AJSAUTOJUDGE environment variable and you omit the root jobnet name under the planning group, the unit of the target generation cannot be found because of one of the following reasons:

There is no unit with the specified path name among the target units that have been automatically selected.

You do not have permission to reference the target units that have been automatically selected or the higher-level units of those units.

(S)

Cancels command execution. If you specify more than one unit, the system continues processing of the units of the other jobnets.

(O)

Correct the error, and then re-execute the command.

KAVS0702-E
An execution generation that is the target of the operation was not found.: unit-name

If you execute the command with the -x option or with yes or auto specified for the AJSAUTOJUDGE environment variable and you omit the root jobnet name under the planning group, the target generation cannot be found because of one of the following reasons:

When executing the ajsplan command, there is no unit to execute for the next time.

When executing the ajskill, ajsintrpt, ajschgstat, or ajsrerun command, there is no unit that has started execution.

The target generation was lost during command processing because of one of the following reasons:
1. The target generation was deleted because the number of logs to keep was specified.
2. The execution has stopped.
3. The target generation was unregistered.

(S)

Cancels command execution. If you specify more than one unit, the system continues processing of the units of the other jobnets.

(O)

Check the status of the target unit, and then re-execute the command.

KAVS0710-E
There is no permission for the Unit ID (unit-ID).

You do not have permissions for the unit with the specified unit ID.

The probable causes are:

You do not have permissions for the unit with the specified unit ID.

You do not have reference permissions for units above the unit with the specified unit ID.

(S)

Cancels command execution. If you specify more than one unit ID, the system continues processing of another unit ID.

(O)

Execute the command as a user who has permissions for the unit with the unit ID.

KAVS0711-E
There is an error in the specified Unit ID (unit-ID).

The unit ID is specified incorrectly.

(S)

Cancels command execution. If you specify more than one unit ID, the system continues processing of another unit ID.

(O)

Correctly specify the unit ID, and then re-execute the command.

KAVS0712-E
The specified Unit ID (unit-ID) does not exist.

A unit with the specified unit ID does not exist.

(S)

Cancels command execution. If you specify more than one unit ID, the system continues processing of another unit ID.

(O)

Specify the unit ID of an existing unit, and then re-execute the command.

KAVS0715-I
The command or JP1/AJS2 - View operation started. (Operation name : command-name)

The command or the operation initiated from JP1/AJS3 - View has started.

(S)

Continues processing.

KAVS0716-I
The command or JP1/AJS2 - View operation ended. (Operation name : command-name)

The command or the operation initiated from JP1/AJS3 - View has terminated.

(S)

Continues processing.

KAVS0720-E
Specified execution start date is before current date.

The execution start date is earlier than the current date.

(S)

Cancels command execution.

(O)

Specify an execution start date later than the current date, and then re-execute the command.

KAVS0721-I
Specified Jobnet (jobnet-name) does not accept temporary change in plan.

The plan of the jobnet has not been temporarily changed.

(S)

Cancels command execution.

(O)

Specify another jobnet, and then re-execute the command.

KAVS0722-E
Specified Jobnet (jobnet-name) has already terminated.

The execution of the jobnet has terminated.

(S)

Cancels command execution.

(O)

Specify the jobnet being executed, and then re-execute the command.

KAVS0723-E
Specified Jobnet (jobnet-name) has already accepted temporary change in plan.

The plan of the jobnet has temporarily changed.

(S)

Cancels command execution.

(O)

Specify a jobnet whose plan has not been changed, and then execute the command.

KAVS0724-E
No further plan in specified Jobnet (jobnet-name).

There are no future plans for the jobnet. The plan of the jobnet cannot be temporarily changed or its suspend attribute cannot be changed.

(S)

Cancels command execution.

(O)

Specify a jobnet that has a future plan, and then re-execute the command.

KAVS0729-E
Cannot change plan temporarily - specified execution start date of Jobnet (jobnet-name) is different from that of higher Jobnet.

The execution start date of the jobnet differs from the next execution date of an upper-level jobnet. The plan could not be temporarily changed.

(S)

Cancels command execution.

(O)

Specify the same execution start date for the jobnet as that of the upper-level jobnet, and then re-execute the command.

KAVS0731-E
Options are needed.

No options are specified.

(S)

Cancels command execution.

(O)

Specify the required options, and then re-execute the command.

KAVS0732-E
Cannot temporarily change the plan on the specified start date.: unit-name

The start date and time is in the year 2037 or later. The plan cannot be temporarily changed.

(S)

Cancels command execution.

(O)

Specify the start date and time in the year 2036 or earlier, and then re-execute the command.

KAVS0740-E
Jobnet (jobnet-name) is already suspended.

An attempt was made to suspend the jobnet that was already suspended.

(S)

Cancels command execution.

(O)

As required, use the ajssuspend command with the -C option to release the jobnet from the suspended state, and then re-execute the ajssuspend command with the -S option.

KAVS0741-E
Jobnet (jobnet-name) is not suspended.

An attempt was made to release the suspended state on the jobnet that was no longer suspended.

(S)

Cancels command execution.

(O)

As required, use the ajssuspend command with the -S option to suspend the jobnet, and then re-execute the ajssuspend command with the -C option.

KAVS0742-E
Cannot use - Jobnet (jobnet-name) is now monitoring.

You cannot suspend the jobnet that is monitoring the start condition.

(S)

Cancels command execution.

(O)

Wait for the jobnet to terminate the monitoring of the start condition, and then re-execute the command.

KAVS0743-E
Cannot suspend - Jobnet (unit-name) is now running.

You cannot suspend the specified jobnet because it is being executed.

(S)

Cancels command execution.

(O)

Wait for the jobnet execution to terminate, and then re-execute the command. Alternatively, re-execute the command with the -n option specified.

KAVS0763-E
Cannot hold rerun - specified Jobnet (unit-name) already running.

The jobnet is being executed. It cannot be re-executed for suspending.

(S)

Cancels command execution.

(O)

Wait for the jobnet to complete the execution, and then re-execute the command.

KAVS0764-E
Specified Unit (unit-name) cannot rerun.

The unit cannot be re-executed. The probable causes are:

The status of the job or nested jobnet that you attempted to rerun is one of the following: Now running, Running + Abend, Running + Warning, Wait for prev. to end, Wait for start time, or Being held.

The job or the nested jobnet that you attempted to rerun has the recovery attribute, and the status of the preceding job or jobnet is Ended normally or Ended with warning.

The job or the nested jobnet that you attempted to rerun is a judgment job or a subordinate unit for a judgment job.

The upper-level jobnet of the job or the nested job that you attempted to rerun has no schedule.

(S)

Cancels command execution.

(O)

Make sure that the unit is in a status that allows re-execution, and then re-execute the command.

For details on re-execution, see 9.11 Re-executing jobnets and jobs in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

KAVS0771-E
Job (unit-name) condition verify error.

The status of the job does not match the condition. The probable causes are:

Although exit is specified in the -t option, the end code is not set.

The status of the unit differs from the status specified in the -v option.

he combination of statuses is indicated as impossible to change in Table 2-3 or Table 2-4 in ajschgstat in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

(S)

Cancels command execution.

(O)

Correct the condition, and then re-execute the command.

KAVS0780-E
Specified Jobnet (jobnet-name) has no information for display.

The jobnet does not contain any information to be displayed.There might be no information to be output for the display period. Alternatively, there might be no more information to be displayed because the unit specified in the command was executed during command execution.

(S)

Cancels processing for the target unit. If you specify multiple units (including specifications of regular-expressions), the system continues processing from the next unit.

(O)

Take the following actions:

Specify another jobnet, and then re-execute the command.

Change the period, if any, specified in the command, and then re-execute the command.

Make sure that any unit specified in the command will not be executed during command execution, and then re-execute the command.

KAVS0781-E
Invalid formatting directives are specified.

Invalid format directives are specified.

(S)

Cancels command execution.

(O)

Correct the format directives, and then re-execute the command.

KAVS0783-E
Specified user does not exist.

User mapping in the target JP1/Base has failed for the user who registered the remote jobnet.

(S)

Abnormally terminates the remote jobnet.

(O)

Recheck the settings of the target JP1/Base, and specify a user defined in the user mapping. Then register the remote jobnet for execution.

KAVS0784-E
Cannot output the result information with the option "-g 0".

The -g 0 option was specified with the -l option. The -l option is the default option.

(S)

Cancels command execution.

(O)

Re-execute the command without specifying the -g 0 option with the -l option.

KAVS0785-E
Insufficient options specified.

The required option is missing.

(S)

Cancels command execution.

(O)

Specify the option, and then re-execute the command.

KAVS0787-E
Cannot execute - the system management daemon is busy.

The processing request by the following commands cannot be executed because the system management daemon is busy:

The command that starts the scheduler service

The command that stops the scheduler service

(S)

Terminates command execution.

(O)

Use the jajs_spmd_status command to make sure that the service has either started or stopped, and then re-execute the command.

KAVS0800-E
Job (job-name) is not executing.

The job that was not being executed has been forcibly canceled.

(S)

Terminates command execution.

(O)

Specify the job being executed, and then re-execute the command.

KAVS0829-I
Reporting the effective information of JP1/AJS has started.

Output of the operating information for the JP1/AJS3 service has started.

(S)

Continues processing.

KAVS0830-I
Reporting the effective information of JP1/AJS has terminated.

Output of the operating information for the JP1/AJS3 service has terminated.

(S)

Terminates processing.

KAVS0831-I
Cannot get View connection information because the JP1/AJS2 service is not started.

JP1/AJS3 - View connection information cannot be obtained because the JP1/AJS3 service has not started.

(S)

Terminates processing.

(O)

Start the JP1/AJS3 service, and then re-execute the command.

KAVS0832-I
The View connection information output is complete.

Output of the JP1/AJS3 - View connection information has terminated.

(S)

Terminates command processing.

KAVS0849-I
Failed to put SNMP trap.: maintenance-information

The SNMP trap could not be issued. The probable causes are:

The SNMP service has not been installed.

A community name for SNMP trap authentication is not set.

An attempt to send an SNMP trap has failed.

(S)

Terminates processing.

(O)

Recheck the SNMP service settings, and then re-execute the command.

For details on the SNMP service settings, see A.2 Setup for linking HP NNM (for a Windows host) in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide or A.3 Setup for linking HP NNM (for a UNIX host) in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.

KAVS0850-E
Specified backup box (backup-box-name) already exists.

The backup box has already been created.

(S)

Terminates processing.

(O)

Check the backup box name, and then re-execute the command.

KAVS0851-E
Specified backup box (backup-box-name) does not exist.

The backup box name does not exist.

(S)

Terminates processing.

(O)

Correct the backup box name, and then re-execute the command.

KAVS0852-E
Cannot use backup box (backup-box-name) - in use by other user.

Another user is using the backup box, preventing it from being processed.

(S)

Terminates processing.

(O)

Wait for the other user to complete using the backup box, and then retry.

KAVS0853-E
No authority to use backup box (backup-box-name).

The backup box does not have any authority.

(S)

Terminates processing.

(O)

Execute the process with the authority for the backup box.

KAVS0854-E
Specified backup file (backup-file-name) already exists.

The backup file has already been created.

(S)

Cancels command execution.

(O)

Check the backup box name, and then re-execute the command.

KAVS0855-E
Specified backup file (backup-file-name) does not exist.

The backup file does not exist.

(S)

Terminates processing.

(O)

Check the backup file name, and then retry.

KAVS0856-E
No authority to use backup file (backup-file-name).

The backup file does not have any authority.

(S)

Terminates processing.

(O)

Execute the processing with the authority for the backup file.

KAVS0857-E
Cannot treat as backup file.: backup-file-name

backup-file-name cannot be a backup file.

(S)

Cancels command execution. If you specify more than one backup file, the system continues processing.

(O)

Correct the backup file name, and then re-execute the command.

KAVS0858-E
Backup box name not specified.

A backup box name is missing.

(S)

Cancels command execution.

(O)

Specify the backup box name, and then re-execute the command.

KAVS0863-E
Interprocess communication failed.: maintenance-information-1 maintenance-information-2 maintenance-information-3

Interprocess communication failed due to one of the following:

The JP1/AJS3 service has not started.

ajsinetd process at the connection destination has not started.

An error occurred during communication with the JP1/Base event service.

(S)

Terminates processing if the JP1/AJS3 service or ajsinetd process at the connection destination has not started.

If an errot occurred during communication with the JP1/Base event service, the system follows the specification of the EVENTRETRY environment setting parameter to output subsequent events, and continues processing.

If you specified yes for the EVENTRETRY environment setting parameter, the system connects to the JP1/Base event service to output the next events.

If you omitted the EVENTRETRY environment setting parameter or specified no for this parameter, the system blocks the output of events until the JP1/AJS3 service restarts.

(O)

Examine the cause of the error, and then re-execute the command.

If the JP1/AJS3 service at the connection destination has not started, start the appropriate service.

If the ajsinetd process has not started, execute the jajs_hstd command to start it. For details on the jajs_hstd command, see jajs_hstd in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

If the message "Failed to put Event." is displayed in maintenance-information-1 and you omitted the EVENTRETRY environment setting parameter or specified no for it, check the status of the JP1/Base event service, and then restart the JP1/AJS3 service.

KAVS0864-E
Connection was reset during interprocess communication.

The connection was reset during inter-process communication because the JP1/AJS3 service stopped, JP1/AJS3 - View at the connection source stopped during processing in JP1/AJS3 - Manager, or the execution of a command to manipulate units stopped during remote execution of that command.

(S)

Terminates processing.

(O)

Examine the cause of the error, and then re-execute the command.

KAVS0865-E
A timeout occurred during interprocess communication.

A timeout occurred during the requested processing.

The probable causes are:

A large jobnet was being executed.

Many JP1/AJS3 commands were being executed.

For a request to another host, that host has not started.

For a request to another host, the network has a problem.

(S)

Terminates processing.

(O)

If a large jobnet is being executed or if many JP1/AJS3 commands are being executed, wait until the relevant processing terminates, and then re-execute the operation. If a timeout occurred during a request to another host, enable communication with other hosts, and then re-execute the operation.

KAVS0866-E
Remote connection failed.: maintenance-information-1 maintenance-information-2

The connection destination host cannot be connected during remote connection due to a network error or routing error.

(S)

Terminates processing.

(O)

Examine the cause of the error, and then re-execute the command.

KAVS0867-E
Remote jobnet ended abnormally - error occurred.: return-code

An unrecoverable error occurred during execution of a remote jobnet.

(S)

Abnormally terminates the remote jobnet.

(O)

Take action according to the message that was output immediately before this message or as indicated in the Execution Result Details dialog box for the remote jobnet, and then retry. If no message was output, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVS0868-E
The user could not be authenticated at the specified host.: host-name maintenance-information-1

The user could not be authenticated at the specified host. Alternatively, a memory was insufficient during user mapping for the JP1 user name, preventing authentication using user mapping.

(S)

Terminates processing.

(O)

Correct the setting of the user information for the specified host, and then re-execute the command.

If maintenance-information-1 indicates 12,0,0x00000002, correct the setting of JP1/Base user mapping.

If maintenance-information-1 begins with 11,, make sure that the OS user password set in JP1/Base is correct and that the OS user account is not locked out.

If the settings are correct or if the error persists, memory may be insufficient.

Check the shared memory usage for the host indicated in host-name. In UNIX, recheck the memory setting in the kernel parameters.

For details about the kernel parameters, see Release Notes, and the explanation of kernel parameters in the Job Management Partner 1/Base User's Guide.

KAVS0869-E
Invalid data was received.: (IP-address) maintenance-information-1 maintenance-information-2

Invalid data was received from the connection source indicated in IP-address.

(S)

Stops communication.

KAVS0870-I
Saving unit (unit-name) to backup box (backup-box-name).

The backup command starts processing.

(S)

Continues processing.

KAVS0872-E
Unit (unit-name) already saved.

An attempt was made to back up the unit that has the same name as the unit that has already been backed up.

(S)

Cancels processing.

(O)

Check the backup file, delete the backup file as required, and then re-execute the command.

KAVS0873-E
Backup box (backup-box-name) is full.

The number of backup files in the backup box exceeded 1024.

(S)

Cancels processing.

(O)

Change the backup box or delete unnecessary backup files. Then, re-execute the command.

KAVS0874-Q
OK to update backup file (backup-file-name) ? (y:OK/n:NO)

This message checks whether you want to update the backup file.

(S)

Waits for a response.

(O)

Enter y to update the backup file.

Enter n not to update the backup file.

KAVS0875-Q
OK to clear backup box (backup-box-name) ? (y:OK/n:NO)

This message checks whether you want to delete the backup box.

(S)

Waits for a response.

(O)

Enter y to delete the backup box.

Enter n not to delete the backup box.

KAVS0876-Q
OK to clear backup file (backup-file-name) ? (y:OK/n:NO)

This message checks whether you want to delete the backup file.

(S)

Waits for a response.

(O)

Enter y to delete the backup file.

Enter n not to delete the backup file.

KAVS0877-E
A backup box could not be made.: maintenance-information-1 maintenance-information-2

A backup box could not be created because of the following causes.

The backup information directory does not have authorization.

The disk does not have sufficient free space for creating the backup box.

(S)

Terminates processing.

(O)

Remove the cause of the error, and then re-execute the command.

KAVS0880-I
Restoring unit (unit-name) to unit (unit-name).

The recovery command starts processing.

(S)

Continues processing.

KAVS0885-E
Restoration unit (unit-name) does not exist.

The restoration unit does not exist, preventing it from being restored.

(S)

Cancels unit restoration.

(O)

Create the restoration unit or correct the restoration unit. Then, re-execute the command.

KAVS0887-E
Cannot use restoration unit (unit-name) - in use by other user.

Another user is using the restoration unit, preventing it from being restored.

(S)

Cancels unit restoration.

(O)

Wait for the other user to complete using the restoration unit, and then re-execute the command.

KAVS0889-E
An error occurred in the process that starts the remote jobnet (service-name:jobnet-name:execution-ID). : maintenance-information

An error occurred during processing to transfer the definition of a remote jobnet to be registered for execution from the manager host where the jobnet was defined to the manager host where the jobnet is to be executed.

The probable causes are:

A communication error has occurred between the manager host where the jobnet is defined and the manager host on which the jobnet is to be executed.

A memory shortage (including a desktop heap that is too small in Windows) has occurred on the manager host where the jobnet is defined or on the manager host where the jobnet is to be executed.

The scheduler service has not started on the manager host where the jobnet is to be executed.

An error occurred in the user mapping for the manager host where the jobnet is to be executed or for the manager host where the jobnet is defined.

(S)

Places the remote jobnet in the Ended abnormally status on the manager host where the jobnet is defined.

(O)

Check the status of the manager host where the jobnet is defined and the manager host where the jobnet is to be executed, and then correct the cause of the error.

The jobnet might have been registered for execution on the manager host where the jobnet is to be executed. Check whether the jobnet has been executed, and then take one of the following actions as necessary.

When the jobnet has been executed on the manager host where it was to be executed:
Use a scheduler log to make sure that execution of the jobnet has ended. Then, on the manager host where the jobnet is defined, re-execute the operation according to the jobnet end status to recover the job.

When the jobnet has not been executed on the manager host where it was to be executed:
On the manager host where the jobnet is defined, re-execute the operation from the remote jobnet in the Ended abnormally status.

KAVS0890-E
An error occurred in the process that notifies the defined manager host of the start of the remote jobnet (service-name:jobnet-name:execution-ID). : maintenance-information

An error occurred when the manager host where the jobnet was to be executed notified the manager host where the jobnet was defined that the remote jobnet had started.

The probable causes are:

A communication error has occurred between the manager host where the jobnet is defined and the manager host on which the jobnet is to be executed.

A memory shortage (including a desktop heap that is too small in Windows) has occurred on the manager host where the jobnet is defined or on the manager host where the jobnet is to be executed.

The scheduler service has not started on the manager host where the jobnet is defined.

An error occurred in the user mapping for the manager host where the jobnet is defined.

(S)

Cancels the start notification processing, and continues remote jobnet execution.

(O)

Although the start notification is unsuccessful, it does not affect execution of the remote jobnet.

Note, however, that an end notification might fail for the same reason. Correct the cause of the error on the manager host where the jobnet is defined and the manager host where the jobnet is to be executed.

If the KAVS0891-E message is output for the target jobnet after this message, end notification has failed.

Recover the status of the remote jobnet according to the operator action provided in the KAVS0891-E message.

KAVS0891-E
An error occurred in the process that notifies the defined manager host of the end of the remote jobnet (service-name:jobnet-name:execution-ID). : (recovery-information-1 recovery-information-2 recovery-information-3 recovery-information-4 recovery-information-5 recovery-information-6) maintenance-information

An error occurred when the manager host on which the jobnet was to be executed notified the manager host where the jobnet was defined that the remote jobnet had ended.

The probable causes are:

A communication error has occurred between the manager host where the jobnet is defined and the manager host on which the jobnet is to be executed.

A memory shortage (including a desktop heap that is too small in Windows) has occurred on the manager host where the jobnet is defined or on the manager host where the jobnet is to be executed.

The scheduler service has not started on the manager host where the jobnet is defined.

An error occurred in the user mapping for the manager host where the jobnet is defined.

(S)

Cancels the end notification processing.

(O)

Correct the cause of the error on the manager host where the jobnet is defined and the manager host where the jobnet is to be executed.

If the status of the remote jobnet on the manager host where the jobnet is defined is Now running, perform the following recovery procedure to place the remote jobnet in the end status:

Make sure that the scheduler service has started on the manager host where the jobnet is defined.

On the manager host where the jobnet is defined, move to the work folder and execute the following command.
To execute this command, you must have logged on as a member of the Administrators group (in Windows) or as a user with superuser privileges (in UNIX).
In Windows:
JP1/AJS3-installation-folder\tools\ajsremnetrcv.bat
recovery-information-1 recovery-information-2 recovery-information-3
recovery-information-4 recovery-information-5 recovery-information-6
> .\ajsremnetrcv.log
In UNIX:
/opt/jp1ajs2/tools/ajsremnetrcv
recovery-information-1 recovery-information-2 recovery-information-3
recovery-information-4 recovery-information-5 recovery-information-6
> ./ajsremnetrcv.log

Make sure that the remote jobnet is placed in the end status.
If the remote jobnet has not been placed in the end status, collect the following data and then contact the system administrator:
- An error message, if any, output by the ajsremnetrcv command
- ajsremnetrcv.log

Delete the ajsremnetrcv.log file.

Supplementary note

The ajsremnetrcv command is designed for emergency recovery, and cannot be used for any purpose except the recovery procedure described above. Accordingly, the description of this command is not included in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1 and Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVS0892-E
An error occurred in the process that deletes the definition of the remote jobnet (service-name:jobnet-name:execution-ID) transferred to the executing manager host. : (executing-manager-host-name job-group-name-on-the-executing-manager-host) maintenance-information

An error occurred during processing to delete the remote jobnet definition transferred to the manager host where the jobnet is to be executed.

The probable causes are:

A communication error has occurred between the manager host where the jobnet is defined and the manager host on which the jobnet is to be executed.

A memory shortage (including a desktop heap that is too small in Windows) has occurred on the manager host where the jobnet is defined or on the manager host where the jobnet is to be executed.

The scheduler service has not started on the manager host where the jobnet is to be executed.

An error occurred in the user mapping for the manager host where the jobnet is to be executed.

The remote jobnet has not been executed on the manager host where it is to be executed because, for example, the remote jobnet has no execution schedules or has been placed in Skipped so not exe. status.

(S)

Cancels the processing to delete the remote jobnet definition.

(O)

Correct the cause of the error on the manager host where the jobnet is defined and the manager host where the jobnet is to be executed. However, no action is required for the error message displayed when the remote jobnet has not been executed on the target manager host because the remote jobnet has no execution schedules or has been placed in Skipped so not exe. status.

After the cause of the error is corrected, unregistration or deletion of the jobnet might not have finished. Unregister the jobnet from the displayed job group on the manager host where the jobnet is to be executed. Then delete the job group.

If you delete a suspended remote jobnet, the jobnet name is indicated as a number. However, no operational problems occur because processing is performed normally on the manager host where the jobnet is defined. Unregister the jobnet and delete the job group as described above.

KAVS0893-E
An error occurred in the process that kills the remote jobnet (service-name:jobnet-name:execution-ID). : maintenance-information

An error occurred during processing to forcibly terminate the remote jobnet.

The probable causes are:

A communication error has occurred between the manager host where the jobnet is defined and the manager host on which the jobnet is to be executed.

A memory shortage (including a desktop heap that is too small in Windows) has occurred on the manager host where the jobnet is defined or on the manager host where the jobnet is to be executed.

The scheduler service has not started on the manager host where the jobnet is to be executed.

An error occurred in the user mapping for the manager host where the jobnet is to be executed.

The jobnet on the manager host where the jobnet is to be executed has already terminated.

(S)

Cancels the processing to forcibly terminate the remote jobnet.

(O)

Correct the cause of the error on the manager host where the jobnet is defined and the manager host where the jobnet is to be executed. Check the status of the applicable jobnet, and then forcibly terminate it if necessary.

If you cancel the registration or delete the definition after the forced termination, the jobnet name might be indicated as a number. However, there is no problem because the remote jobnet has ended on the manager host where it was to be executed.

KAVS0898-E
The suspend function is set up already.

The suspend function is already set up. Execution of the ajssetup -m command is unnecessary.

(S)

Terminates processing.

KAVS0900-W
Minor error occurred.: maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

An error that allows processing to continue occurred.

(S)

Continues processing.

(O)

If the maintenance information contains the character string SPMD communication error, check whether the jajs_spmd process is operating normally.

This error message might be output when a system error occurs and the jajs_spmd process terminates first. In such a case, there is no problem with the operation, despite the output of the message.

For any other case, follow the instructions given in the messages output before and after this one.

KAVS0901-E
I/O error occurred.: maintenance-information-1 maintenance-information-2 maintenance-information-3

An I/O error occurred during processing such as inputting into or outputting from a file.

(S)

Cancels the processing for the file where the error occurred, and continues the process. If the I/O error of the system file prevented processing, the system cancels the process.

(O)

Take action according to the error information in the Windows event log or syslog output by the OS, and other OS-specific error information. If you cannot take corrective action, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS0902-E
Insufficient memory occurred.: maintenance-information-1 maintenance-information-2 maintenance-information-3

A memory shortage occurred.

(S)

Cancels the processing during which insufficient memory was detected. If insufficient memory was detected during allocation of memory for a key component that could not continue processing, the system aborts the process.

(O)

Check the following settings:

In UNIX, see Release Notes, and make sure that the value of the kernel parameter for memory is greater than the estimated value.

Check the status of the process that was running when the error occurred to make sure that the amount of memory available is greater than the estimated value.

If necessary, re-execute the processing for which memory was insufficient.

KAVS0903-E
System error occurred.: maintenance-information-1 maintenance-information-2 maintenance-information-3 system-error-message

A system error occurred during processing.

(S)

Terminates the process where the error occurred.

(O)

Take action according to the error information in the Windows event log or syslog output by the OS, and other OS-specific error information. If you cannot take corrective action, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS0904-E
Unexpected error occurred in JP1/AJS2.: maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

An unexpected error occurred during processing.

(S)

Terminates the processing where the error occurred.

(O)

Take action according to the message that was output before or after this error message. If you cannot take corrective action, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVS0905-E
Failed to output message (message-id).: maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

An attempt was made to output a message because an error occurred, but the message could not be output.

(S)

Cancels the process where the error occurred.

(O)

Take action according to the displayed message and the system error message.

KAVS0907-E
No more space in file (file-name).

There is no free space in the file system or the device to which writing the file was attempted.

(S)

Cancels the process where the error occurred.

(O)

Delete unnecessary files to make free space. Output the user file to another file system or device.

KAVS0909-E
Shared memory is not available.: maintenance-information-1 maintenance-information-2

Shared memory, which is one of the system resources, cannot be obtained, or required shared memory does not exist.

(S)

Terminates the process where the error occurred.

(O)

If the size of the system's shared memory is insufficient, increase the value in the kernel parameter. If the shared memory necessary for running the scheduler service has been deallocated, you need to restart the scheduler service.

KAVS0915-E
Resource lack occurred : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

A resource is insufficient. The insufficient resource is indicated in maintenance information.

(S)

Cancels processing.

(O)

Re-estimate the resources according to Release Notes.

KAVS0920-W
Message process failed to initialize.(maintenance-information)

The message output could not be initialized.

(S)

The message is output without text. If HNTR_Initialize Failure is indicated in maintenance-information, the message is not output to the integrated trace log.

(O)

Check whether the resources are sufficient. Also check the running status of Hitachi Network Objectplaza Trace Monitor.

In UNIX, recheck the following items in the kernel parameters:

Maximum number of files allowed to be open for a process or system

Maximum number of file descriptors allowed (a limit value related to the file system)

For details about the kernel parameters, see Release Notes. Then, change the settings for the file system. If you cannot determine the cause of the error, collect data, and then contact the system administrator (see 1.2.3 To the system administrators).

KAVS0921-W
Connection to scheduler service has been reset.: maintenance-information

Interprocess communication for the scheduler service was disconnected due to termination of the connected process or other reasons.

(S)

Terminates processing.

(O)

This message may also be output when the scheduler service is terminated forcibly. Determine the cause of the error according to the message and from the contents of operations before and after the message is output, and then take action.

KAVS0930-E
Exclude error occurred.: maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

A lock error occurred.

(S)

Terminates processing.

(O)

The probable causes are as follows. Take action according to the cause of the error. If an error message was output before or after this message, also see the instructions given by that message.

Cause 1

During reorganization of ISAM files or when the ajsdbcond command with the -l option specified was executed, the ISAM files could not be locked because there were processes accessing the ISAM files.

Action

The scheduler service might be running or the unit might have been referenced or updated from JP1/AJS3 - View, a command that operates units, or a related product. Stop the scheduler service and make sure that the unit is not being referenced or updated. Then, retry the operation that resulted in the error.

For details about reorganizing ISAM files, see 10.3 Reorganizing a database when QUEUE jobs and submit jobs are used in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

Cause 2

When the OS is AIX and the ISAM lock table split function is used, the ISAM lock table cannot be allocated.

Action

Stop all the related JP1 services, set ON for the EXTSHM environment variable, and then retry the operation that resulted in the error.

Cause 3

The status of the ISAM lock table has become invalid.

Action

Delete the ISAM lock table, and then retry the operation that resulted in the error.

Cause 4

JP1/AJS3 could not access the ISAM files because they were locked by another product such as backup software or anti-virus software.

Action

Make sure that no other products are accessing the ISAM files, and then retry the operation that resulted in the error.

Cause 5

A deadlock occurred when an embedded database was being used.

Action

The deadlock status is canceled automatically. If necessary, retry the operation that resulted in the error.

If an error message still appears after the above actions are taken, contact the system administrator and then collect data (see 1.2.3 To the system administrators).

KAVS0931-E
Condense failed.: maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

The database could not be reorganized.

(S)

Terminates processing.

(O)

Examine the cause of the error, and then reorganize the database of the scheduler service.

The probable causes are:

The disk does not have sufficient free space required for performing automatic reorganization.

The number of open files for a process or system reached the maximum.
Check the process running status of the machine and wait until the number of running processes is reduced. Then, re-execute the command.

Memory was insufficient.
If necessary, recheck and correct the values of the kernel parameters for memory.
For details on the kernel parameters, see Release Notes.

If you cannot determine the cause of the error, collect data, and then contact the system administrator (see 1.2.3 To the system administrators).

KAVS0932-E
Error occurred during database access.: maintenance-information-1 maintenance-information-2 maintenance-information-3

An error occurred while accessing the database.

(S)

Terminates processing.

(O)

The probable causes are as follows. Take action according to the cause of the error. If an error message was output before or after this message, also see the instructions given by that message.

Cause 1

Database files were corrupted due to a disk error, CPU error, or other hardware error.

Action

Reorganize the scheduler database or job execution environment database . If the reorganization does not correct the error, you must re-create the database.

For details about reorganizing ISAM files, see 10.3 Reorganizing a database when QUEUE jobs and submit jobs are used in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

For details about re-creating ISAM files, see 2.12 Troubleshooting problems related to invalid ISAM files in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

Cause 2

Database files were corrupted because the primary node and secondary node in a cluster configuration accessed the database at the same time.

Action

Same as for Cause 1.

Cause 3

When an embedded database is used as the scheduler database, the embedded database has already stopped by the time the JP1/AJS3 service stopped.

Action

If the JP1/AJS3 service has stopped, there is no problem caused by this error. Do not stop the embedded database first.

Cause 4

When ISAM is used for the scheduler database in a cluster configuration, because sync was not specified for the ISAMWRITEMODE environment setting parameter for the scheduler service, the status of ISAM files becomes inconsistent during failover.

Action

Reorganize the scheduler database. If the reorganization does not correct the error, you must re-create the database.

Cause 5

Database files were corrupted because a disk operation was performed during JP1/AJS3 operation.

Action

Same as for Cause 1.

Cause 6

The file sizes that can be handled on the OS are restricted

Action

Check the estimated file size in the kernel parameter, and set the appropriate value. For details about estimating the kernel parameters, see Release Notes.

Cause 7

The size of the ISAM file used for the scheduler database or job execution environment database reached 2 GB.

Action

Decrease the size of the ISAM file according to 9.3 Notes on the JP1/AJS3 database in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

Cause 8

Database files were corrupted because the OS was stopped unexpectedly due to power interruption while JP1/AJS3 was running or for any other reason.

Action

Same as for Cause 1.

Cause 9

If an access from JP1/AJS3 - View causes an error, the OS user who is mapped to the JP1 user who logs in to JP1/AJS3 - View does not have update permission for the scheduler database.

Action

Check permission for accessing the scheduler database directory and scheduler database files, and set the access permissions appropriately.

Cause 10

If an embedded database is used for the scheduler database, the embedded database is not running.

Action

Start the embedded database, and then restart the scheduler service that is using the embedded database as the scheduler database.

Cause 11

When an unexpected failover occurs in a cluster configuration due to OS power failure or OS error, the status of ISAM files becomes inconsistent.

Action

Same as for Cause 1.

KAVS0933-W
RDBUSER (user-name) has connect privilege.

The user specified in the RDBUSER environment setting parameter has sufficient privileges to connect to the database.

The user password may have been changed with the ajssetup command. If the password has been changed, user authentication may fail and the database cannot be accessed.

(S)

Since an existing user was found, the system resets the password as described below by manipulating the ajssetup command:

When the RDBPASSWORD environment setting parameter is specified, the password is reset to the value of RDBPASSWORD.

When the RDBPASSWORD environment setting parameter is not specified, the password is reset to a value scrambled from the RDBUSER environment setting parameter.

(O)

Check whether any problem occurred due to changes in the settings for the user connecting to the DBMS. For details on the environment setting parameters, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVS0934-E
The specified tablespace or RDAREA does not exist.

The table area or RDAREA specified in the ajssetup command did not exist. The table could not be created.

(S)

Cancels command execution.

(O)

Specify the correct table area or RDAREA in the argument of the ajssetup command, and then retry.

KAVS0935-E
The specified tablespace or RDAREA is invalid.

The table area or RDAREA specified in the ajssetup command was invalid. The table could not be created.

(S)

Cancels command execution.

(O)

Specify the correct table area or RDAREA in the argument of the ajssetup command, and then retry.

KAVS0936-E
The schema is already defined.

The schema is already defined and cannot be created.

(S)

Cancels command execution.

(O)

The schema has already been defined, so you do not need to use the ajssetup command to set up the schema again. If you want to discard and re-create the existing schema, delete it on the DBMS and then re-execute the ajssetup command.

KAVS0940-E
Event Action Manager is busy.: maintenance-information maintenance-information maintenance-information maintenance-information

The event/action control manager is busy. Events cannot be processed.

(S)

Cancels operations for event monitoring and start conditions.

(O)

Wait a while and then retry. If the retry does not correct the error, collect data and then contact the system administrator (see 1.2.3 To the system administrators).

KAVS0941-E
No event job in start condition.: jobnet-name

An attempt was made to start the execution of a jobnet whose icon was not registered in the start condition.

(S)

Cancels monitoring of the jobnet.

(O)

Define the event icon in the start condition or delete the start condition.

KAVS0942-W
Connection to job status notification process has been reset.

The status report process was disconnected because the status report process stopped during communication with the job-completion wait process.

(S)

Stops the scheduler service.

(O)

If the KAVU6101-I message is output before and after this message, this message is output at the end of the status report process and there is no problem. If the KAVU6101-I message is not output before and after this message, collect the internal trace log and then contact the system administrator.

KAVS0943-E
Cannot connect to job status notification process.: maintenance-information-1 maintenance-information-2 maintenance-information-3

The status report process could not be connected. The scheduler service cannot start.

(S)

Stops the scheduler service.

(O)

Use the messages that are output before and after this message to determine the cause of the unsuccessful connection, and then take action.

Also make sure that the port number for job status notification is set correctly in the services file. The default for the status notification port is 20245. Correct the cause of the error and then start the scheduler service.

KAVS0944-E
The error occurred during initialization processing of the job execution function(scheduler-service-name) : maintenance-information

An error occurred during initialization processing of job execution control.

(S)

Stops the scheduler service.

(O)

Use the system error messages that are output before and after this message to determine the cause of the error, and take corrective action. After correcting the error, restart the scheduler service. If you cannot determine the cause of the error from the messages, collect data and then contact the system administrator (see 1.2.3 To the system administrators).

KAVS0945-E
A scheduler daemon ended abnormally. (name: daemon-process-name, code: end-code, maintenance-information-1, maintenance-information-2)

The scheduler service(daemon) terminated abnormally.

(S)

Terminates the scheduler service.

(O)

Use the system error messages that are output before and after this message to determine the cause of the error. Then take action. If you cannot determine the cause of the error from the messages, collect data and then contact the system administrator (see 1.2.3 To the system administrators).

KAVS0946-E
The error occurred during scheduler service(scheduler-service-name) start processing. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

An error occurred during startup of the scheduler service.

(S)

Terminates the scheduler service.

(O)

If you specified the setting that automatically restarts the scheduler service when it terminated abnormally, the scheduler service is restarted automatically. When the scheduler service is restarted, the KAVS0946-E message appears again. If an attempt to start the scheduler service has failed, correct the cause of the error according to the instructions given by the message that was output immediately before this message. Then restart the scheduler service indicated in scheduler-service-name.

If a KAVS0903-E message was output immediately before this message, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS0947-E
The error occurred during initialization processing of the Event Action Manager(scheduler-service-name) : maintenance-information

An error occurred during initialization processing of the event/action control manager.

(S)

Stops the scheduler service.

(O)

Use the system error messages that are output before and after this message to determine the cause of the error, and take corrective action. After correcting the error, restart the scheduler service. If you cannot determine the cause of the error from the messages, collect data and then contact the system administrator (see 1.2.3 To the system administrators).

KAVS0950-E
An error (maintenance-information) occurred so the jobnet (root-jobnet-name) cannot be executed according to schedule.

An error occurred when the root jobnet is scheduled to wait for the start time. The jobnet is in the wait status but it cannot be executed. If this root jobnet exists under the planning group, all other root jobnets under the same planning group may not be started correctly.

(S)

The scheduler service stops processing of the root jobnet in which the error occurred. However, the service itself does not stop and continues other processing.

(O)

Unregister the root jobnet in which the error occurred, and then register it again. If the root jobnet exists under the planning group, unregister all the other root jobnets under the same planning group, and then register them again.

KAVS0965-E
Specification of the exclusion schedule specified in the jobnet(jobnet-name-2) inside the jobnet(jobnet-name-1) includes an error.

The definition of the exclusion schedule specified in the jobnet or nested jobnet contains an error.

(S)

Cancels allocation of the schedule for the jobnet.

(O)

Specify the correct jobnet name in the exclusive-schedule definitions, and allocate the schedule with temporary change specified. Alternatively, re-register the jobnet.

KAVS0966-E
Specification of the reference calendar specified in the jobnet(jobnet-name-2) inside the jobnet(jobnet-name-1) includes an error.

The definition of the reference calendar specified in the jobnet or nested jobnet contains an error.

(S)

Cancels allocation of the schedule for the jobnet.

(O)

Specify the correct job group name in the reference calendar definitions, and allocate the schedule with temporary change specified. Alternatively, re-register the jobnet.

KAVS0970-E
Failed in the execution resumption processing after releasing the Suspend setting.: maintenance-information-1

Recovery from the suspended to the active state failed (suspended state was released).

(S)

Continues processing.

(O)

Contact the system administrator, and collect data (see 1.2.3 To the system administrators). Correct the cause of the error, and then unregister the jobnet and register it again.

KAVS0971-E
The error occurred during suspension processing.: maintenance-information-1

An error occurred during suspension processing.

(S)

Cancels the requested processing.

(O)

Contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS0980-E
The database table structures are incompatible.

The database table structures used for the scheduler service are not compatible.

(S)

Terminates processing.

(O)

Use the current version of the ajssetup command with the -t option specified to re-create the table.

KAVS0981-E
The table is not found.

The database table is not found.

(S)

Terminates processing.

(O)

Check the values of the TABLENAMEPREFIX and TABLENAMEPOSTFIX environment setting parameters.

If there are no tables, use the ajssetup command with the -t option specified to create the table.

KAVS0982-E
Could not connect to the database because the upper limit of a server setting was exceeded.

The limit defined in the database server was exceeded. The database could not be connected.

(S)

Terminates processing.

(O)

Stops other processes connected to the database, or re-set the limit of the database. Then, retry.

KAVS0983-E
Could not connect to the database because the username or password was invalid.

Connection was attempted using an invalid user name or password. The database could not be connected.

(S)

Terminates processing.

(O)

Set the correct user name and password, and then retry.

KAVS0984-E
Could not connect to the database because a required permission was lacking.

The user without permission for the database attempted connection. The database could not be connected.

(S)

Terminates processing.

(O)

Specify the user who has permission for the database, and then retry.

KAVS0985-E
Could not connect to the database.

The database could not be connected.

(S)

Terminates processing.

(O)

Check whether the database is running.

KAVS0987-E
A permission required to operate the database is lacking.

You do not have permission to operate the database.

(S)

Terminates processing.

(O)

Specify a user who has appropriate permission, and then retry.

KAVS0988-E
Insufficient tablespace or RDAREA.

The table area or RDAREA does not have any free space.

(S)

Terminates processing.

(O)

Reorganize the table area or RDAREA or expand the area to make a free area, and then retry.

Detailed error messages for the database will be output to the Windows event log or syslog. For an embedded database, the message KFPH00211-I appears.

For details on how to reorganize databases, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVS0989-E
The permission for ISAM files is insufficient.

The appropriate permission for ISAM files is insufficient.

(S)

Terminates processing.

(O)

Give appropriate permission for the ISAM files, and then retry.

KAVS0990-E
Failed to load libraries.

The library required for JP1/AJS3 could not be loaded .

(S)

Terminates processing.

(O)

Correct the environment setting and configuration definition for the linked programs, and re-execute the command.

If the library for linkage with the DBMS could not be loaded, the KAVS0932-E message containing the library name is output to the Windows event log or syslog. Make sure that the DBMS product is installed correctly and environment settings are correct.

For all the OS users using JP1/AJS3, also make sure that the following environment variables that indicate the library loading paths contain the library path for the DBMS product. These environment variables also required for starting the JP1/AJS3 services. When you are using JP1/AJS3 or the JP1/Base startup script, jajs_start, or jajs_start.cluster, also make sure that the environment variables are set up.

In Windows: PATH

In HP-UX: SHLIB_PATH

In Solaris: LD_LIBRARY_PATH

In AIX: LIBPATH

KAVS0991-E
Not supported on related programs (program-name).

program-name does not support the requested function.

If this error message appears when using the ajsdbcond command with the -L option specified, you need to install JP1/Base version 06-71 or later versions.

(S)

Cancels command processing.

(O)

Check the supported version of a prerequisite program, and upgrade the version of the program.

KAVS0992-E
There is no permission for object-name.: maintenance-information-1, maintenance-information-2, maintenance-information-3

You do not have permission to manipulate the object.

(S)

Terminates processing.

(O)

Obtain the right permission required to manipulate the object indicated in the message, and then re-execute the command.

KAVS0993-E
Invalid database backup file.

The possible causes are:

The name of the database backup file is specified incorrectly.

You attempted to move the database between different tables.

You attempted to move the database between different platforms.

The export process was not performed correctly.

(S)

Cancels command processing.

(O)

Correct the errors, and then re-execute the command.

KAVS0994-E
Record existed in specified database table.

The database table at the import destination contains a record.

(S)

Cancels command processing.

(O)

Re-execute the command with the -c option specified. Executing the command with the -c option deletes all the records in the specified table and then imports the records in the specified database backup file. Once the records are deleted, they cannot be restored.

If you cannot confirm that the records in the table at the import destination are completely unnecessary, back up those records with the ajsdbexport command and then re-execute the import command.

KAVS0996-E
Error exist in option.

The specified option contains errors.

(S)

Cancels command processing.

(O)

Recheck the specified option value.

KAVS0997-E
The scheduler service failed to start.: maintenance-information-1 maintenance-information-2

The scheduler service could not be started with the jajs_spmd or ajsstart command.

(S)

Cancels command processing.

(O)

The cause of the failure to start the scheduler service has been output to the Windows event log or syslog. See the information stored in the above file, and take proper action.

KAVS0998-E
The system will wait because the database could not be connected. (Scheduler service : scheduler-service-name, Waittime : maximum-wait-time, Host : host-name)

The database could not be connected within the specified maximum wait time.

(S)

Terminates processing.

(O)

Check whether the database is running.

For details about how to check this, see the manual for the appropriate database.

If the database is starting, recheck the value of the maximum wait time.

KAVS0999-W
The database could not be connected within the specified time. (Scheduler service : scheduler-service-name, Waittime : maximum-wait-time, Host : host-name)

The system will wait because the database could not be connected.

(S)

Retries the connection after a predefined period of time.

(O)

Check whether the database is running. For details on how to do this, see the documentation for the appropriate database.

KAVS1002-E
AJS daemon ended abnormally. (name: daemon-process-name, code: end-code)

The scheduler service abnormally terminated.

(S)

Terminates processing.

(O)

Take action according to the message output before this message.

KAVS1003-E
Invalid specification in configuration definition. (item-name)

The environment setting parameters contains an invalid specification.

(S)

Terminates processing.

(O)

Specify the value indicated by item-name correctly, and then re-execute the command.

For details on the output item names, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVS1004-E
Scheduler service does not exist.

The scheduler service does not exist.

(S)

Terminates processing.

(O)

Specify the correct name of the AJS service to be processed, and then re-execute the command.

In addition, check the following:

The environment settings for the started JP1/AJS3 service (on a physical or logical host) contain scheduler service settings.

The scheduler service name specified in the environment settings for the started JP1/AJS3 service (on a physical or logical host) is the same as the name of a scheduler service in a different JP1/AJS3 service (on a physical or logical host).

KAVS1005-E
Cannot connect to Access Control Server.

The access control server could not be connected.

(S)

Terminates processing.

(O)

Check whether the authentication server name is correct, and whether the authentication server is running on the host of the specified authentication server.

Make sure that the authentication server is running and connected, and then re-execute the command.

KAVS1006-W
Change of Logical Host or Scheduler Service is incomplete.

Changes made in the logical host for the configuration definition or the scheduler service is not applied to the operation information.

(S)

Continues processing.

(O)

Take actions according to the following procedure.

Stop all the processes of the running JP1/AJS3 (including services and commands).

Make sure that the JP1/AJS2 services have stopped on all logical and physical hosts.
In Windows, in Control Panel or Administrative Tools, double-click Services, and make sure that the services have stopped. Then go to step 4.
In UNIX, use the jajs_spmd_status command to make sure that the JP1/AJS3 service has stopped. After making sure that the services have stopped, go to step 3.

Execute the ajsshmdel command.

Restart JP1/AJS3.

For details on the ajsshmdel command, see 14.1.1 Settings for starting multiple scheduler services in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

KAVS1007-E
Host name cannot be resolved. (logical-host-name)

The logical host name could not be resolved.

(S)

Cancels processing.

(O)

Check the settings of the JP1_HOSTNAME environment variable or the hosts file to resolve the logical host name, and then retry.

KAVS1008-E
An error exists in the certification server setting of the host (host-name). (login point IP address: IP-address)

The settings of the certification server contain an error on the host at the connection destination indicated in IP-address.

(S)

Terminates processing.

(O)

Recheck the settings of the certification server on the host at the connection destination, and correct the errors. In addition, check whether the IP address of the connection (login) destination matches that of the host that you attempted to connect to.

KAVS1009-W
The connection from host (IP address:IP-address, JP1 user name:JP1-user-name) to host (logical-host) was refused.

A connection being established from the host indicated in IP-address to the host indicated in logical-host was refused because user mapping or user authentication in JP1/Base performed for the user indicated in JP1-user-name failed.

(S)

Cancels the connection and waits for the next request.

KAVS1100-I
The command (command-name) ended normally.

The command terminated normally.

(S)

The command terminated normally.

KAVS1101-E
Illegal option (option) exists.

An invalid option is specified.

(S)

Cancels command execution.

(O)

Specify the correct option and then re-execute the command.

KAVS1102-E
Value for option (option) is not specified.

No value is specified for an option that requires a value.

(S)

Cancels command execution.

(O)

Specify the value for the option and then re-execute the command.

KAVS1103-E
The specified value (value) is already used with other logical hosts or another scheduler service.

The specified value is already used for another logical host or another scheduler service.

(S)

Cancels command execution.

(O)

Specify a unique value, and then re-execute the command.

KAVS1104-W
The specified directory or file (file-name or directory-name) does not exist.

The specified file or directory does not exist.

(S)

Continues the command processing.

(O)

After the command terminates, create the file or directory.

KAVS1105-E
There is an error in the value specified in an environmental parameter (parameter).

An invalid value is specified in the environment setting parameter.

(S)

Cancels command execution.

(O)

Specify the correct value and then re-execute the command.

KAVS1106-E
Option (option) appears twice or more.

The same option is specified more than once.

(S)

Cancels command execution.

(O)

Specify the indicated option only once, and then re-execute the command.

KAVS1107-E
The specified definition key cannot be set.

The specified definition key cannot be set.

(S)

Cancels command execution.

(O)

Specify the correct definition key and then re-execute the command

KAVS1108-E
An environmental parameter that cannot be set in the specified definition key has been specified.

An environment setting parameter that cannot be set in the specified definition key is specified.

(S)

Cancels command execution.

(O)

Specify the correct environment setting parameter and then re-execute the command.

KAVS1109-E
Insufficient options specified.

Required options are not specified.

(S)

Cancels command execution.

(O)

Specify the required options and then re-execute the command.

KAVS1110-E
Invalid value for option (option).

An invalid value is specified for the option.

(S)

Cancels command execution.

(O)

Specify the correct value for the option and then re-execute the command.

KAVS1111-E
This function cannot be used with the compatible ISAM configuration.

This function cannot be used with the compatible ISAM configuration.

(S)

Cancels command execution.

(O)

Use a function that can be used with the compatible ISAM configuration.

KAVS1112-E
The specified directory (directory-name) does not exist.

The specified directory does not exist.

(S)

Cancels command execution.

(O)

Specify the correct directory name and then re-execute the command.

KAVS1113-E
The specified logical host does not exist (host-name).

The specified logical host does not exist.

(S)

Cancels command execution.

(O)

Specify the correct host and then re-execute the command

KAVS1114-E
The specified scheduler service does not exist (scheduler-service-name).

The specified scheduler service does not exist.

(S)

Cancels command execution.

(O)

Specify the correct scheduler service name, and then re-execute the command.

KAVS1115-E
Failed to create shared directory (directory-name).

An attempt to create a shared directory has failed.

(S)

Cancels command execution.

(O)

Make sure that the following jp1ajs2 directory indicated in the message does not already exist.

In Windows:

specified-shared-directory-name\JP1AJS2

In UNIX:

specified-shared-directory-name/jp1ajs2

If the jp1ajs2 directory exists, make sure that the specified shared directory name is correct. If it is correct, make sure that the jp1ajs2 directory is not needed, delete it, and then re-execute the command (do not delete a shared directory).

If the jp1ajs2 directory does not exist, check whether you have permission to update the specified shared directory

KAVS1116-E
The specified logical host cannot be omitted.

The logical host specification cannot be omitted.

(S)

Cancels command execution.

(O)

Specify the logical host and then re-execute the command.

KAVS1117-E
The configuration definition of the logical host (host-name) does not exist.

The configuration definition of the logical host does not exist.

(S)

Cancels command execution.

(O)

Specify the correct logical host, and then re-execute the command.

KAVS1118-E
Scheduler service is active.

The scheduler service is running.

(S)

Cancels command execution.

(O)

Stop the scheduler service and then re-execute the command.

KAVS1119-Q
OK to rename Scheduler service from (scheduler-service-name) to (scheduler-service-name)? (Y: OK/N: NO)

This message confirms whether or not you want to continue to rename the scheduler service.

(S)

Waits for a response.

(O)

Enter y to continue processing to rename the scheduler service. Enter n to cancel the processing.

KAVS1120-Q
OK to delete Scheduler service (scheduler-service-name)? (Y: OK/N: NO)

This message confirms whether or not you want to continue to delete the scheduler service.

(S)

Cancels command execution.

(O)

Enter y to continue processing to delete the scheduler service. Enter n to cancel the processing.

KAVS1122-E
An attempt to read the pattern file (file-name) failed.

An attempt to read the pattern file used by the command has failed.

(S)

Cancels command execution.

(O)

Check whether read or higher permission has been given for the file shown in the message. If the permission is not set, give read or higher permission for the file, and then re-execute the command.

If the file does not exist, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

The file shown in the message is stored in the following directory:

In Windows:

JP1/AJS3-installation-folder\conf

In UNIX:

/etc/opt/jp1ajs2/conf

KAVS1123-E
Failed to rename scheduler service.

An attempt to rename the scheduler service has failed.

(S)

Cancels command execution.

(O)

Check the status of the target scheduler service specified in the command. The most probable cause of the error is that the target scheduler service is running.

Take action according to the message that was output before or after this error message.

After correcting the error, re-execute the command.

KAVS1124-E
Failed to delete scheduler service.

An attempt to delete the scheduler service has failed.

(S)

Cancels command execution.

(O)

Check the status of the target scheduler service specified in the command. The probable causes are:

The target scheduler service is running.

The embedded database is not running.

Take action according to the message that was output before or after this error message.

After correcting the error, re-execute the command.

KAVS1126-E
An error occurred during scheduler service addition or deletion processing. (maintenance-information)

An attempt to set up or remove the embedded database by executing the command has failed.

(S)

Cancels command execution.

(O)

Correct the error according to the cautionary notes for the executed command, and then re-execute the command.

KAVS1127-E
An attempt to access the log file (file-name) failed.

An attempt to access the log file has failed.

(S)

Cancels command execution when the log file is being opened.

If this message appears during writing to the log file, the system continues command processing

(O)

If this message appears when the log file is being opened, check whether write permission is given for the file shown in the message. If the permission is not set, give write permission for the file and then re-execute the command.

If this message appears during writing to the log file, the system continues command processing without writing log information into the log file. If this message appears, log information will not be written to the log file in subsequent processing until the command terminates.

The file shown in the message is stored in the following directory:

In Windows Server 2008 (when JP1/AJS3 is installed in a folder that is not to be virtualized) or Windows Server 2003:
JP1/AJS3-installation-folder\log

In Windows Server 2008 (when JP1/AJS3 is installed in a folder that is to be virtualized):
%ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\log
(The default for %ALLUSERSPROFILE% is system-drive\ProgramData.)

In UNIX:
/var/opt/jp1ajs2/log

KAVS1130-E
An attempt to read the configuration definition information failed.

An attempt to obtain the configuration definition has failed.

(S)

Cancels command execution.

(O)

Contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS1131-E
Cannot use this option(option-name) with the compatible ISAM configuration.

This option cannot be used with the compatible ISAM configuration.

(S)

Cancels command execution.

(O)

Use an option that can be used with the compatible ISAM configuration.

KAVS1132-I
Processing was canceled.

Command processing was canceled.

(S)

Terminates command execution.

KAVS1133-W
An attempt to set scheduler service information (setting-name) has failed.

The scheduler service setting before the change could not be set in the scheduler service after the change.

(S)

Continues command processing.

(O)

After the command terminates, check the setting name indicated in the message, and specify either of the following for the new scheduler service:

If Local date and time is indicated in setting-name, use the ajslocaldate command to specify the AJS local date and time.

If Suspend feature is indicated in setting-name, use the ajssetup command to set up the suspend feature.

KAVS1200-E
The value of the option (option-name) exceeds the value specified for the environment setting parameter (parameter-name) of the scheduler service (service-name).

The value specified in the option to the command is larger than the value specified in the environment-setting parameter of the scheduler service.

(S)

Cancels command execution. However, the system continues processing if two or more units (including specifications by regular expressions) are specified.

(O)

Specify the option value correctly, and then re-execute the command.

In addition, change the value of the environment setting parameter indicated in parameter-name, and then re-execute the command.

When the environment setting parameter indicated in parameter-name is "MAXSAVEGEN"
Check and, if necessary, change the value of the MAXSAVEGEN environment setting parameter. For details on the settings, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVS1300-I
An attempt to obtain a host name failed.: maintenance-information-1, maintenance-information-2, maintenance-information-3

The host name could not be obtained.

(S)

Continues processing.

(O)

Check the execution target host (setting of the JP1_HOSTNAME environment variable, for example).

KAVS1301-I
An attempt to obtain the name of the directory for backup information failed.: maintenance-information-1, maintenance-information-2, maintenance-information-3

The directory name for output of the wait information file could not be obtained.

(S)

Continues processing.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the permission environment of the started user is correct.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVS1302-I
An attempt to obtain the name of the directory for installation of JP1/AJS2 failed.: maintenance-information-1, maintenance-information-2, maintenance-information-3

The JP1/AJS3 installation directory name could not be obtained.

(S)

Continues processing.

(O)

Check the following:

Check whether system resources are sufficient.

Check whether the permission environment of the started user is correct.

Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.

KAVS1400-E
The status of the jobnet (jobnet-name) whose start condition was being monitored could not be confirmed. (execution-ID)

The status of the jobnet of which the start condition is being monitored could not be confirmed.

(S)

The monitoring of the jobnet will now end.

(O)

Register the jobnet for execution again. If you use the cluster, check whether the directory name for output of the wait information file is set correctly.

This message also appears when you start the JP1/AJS3 service after executing the jpomanevreset command without the -e option. In this case, however, ignore the message because it is output as a result of terminating the monitoring of a start condition by resetting the event.

KAVS1401-E
A notice of a start in the maintenance mode from scheduler service to Event Action Manager failed.: maintenance-information

The scheduler service could not notify the event/action control manager of the activation of the maintenance mode. So events occurring in maintenance mode may not be detected.

(S)

Continues the maintenance mode activation process.

(O)

Deactivate maintenance mode immediately, determine the cause from the message output before this error message, and then remove the cause of the error. Then, re-execute the maintenance command.

KAVS1420-I
A jobnet with a preset start condition (name: jobnet-name: execution-ID) will wait for the termination of its monitoring status generation(execution-ID-of-the-monitoring-generation).

When the time that the jobnet with a start condition starts monitoring of the start condition is reached, the previous monitoring generation was still running. According to the setting of Concurrent exec. of monitoring gen., the jobnet waits in Wait for start time status until the monitoring generation terminates. After the monitoring generation has terminated, the waiting generation starts monitoring of the start condition.

(S)

Lets the jobnet in Wait for start time status wait for the monitoring generation to terminate. When the monitoring generation has terminated, the jobnet starts monitoring of the start condition.

(O)

Perform either of the following according to the needs of the operation.

To immediately start monitoring:

Kill the current monitoring generation.

To wait for the monitoring generation to terminate and start monitoring:

No action is required. Note, however, that if the timeout period expires while the jobnet is waiting for the monitoring jobnet to terminate, the jobnet will be placed into Skipped so not exe. status.

KAVS1500-I
Database condensing of the scheduler service (service-name) started. start-date-and-time

The database reorganization of the scheduler service started.

(S)

Continues the database reorganization.

KAVS1501-I
Database condensing of the scheduler service (service-name) ended normally. start-date-and-time - termination-date-and-time (required-time)

The database reorganization of the scheduler service has normally terminated.

(S)

Normally terminates the database reorganization.

KAVS1502-E
Database condensing of the scheduler service (service-name) ended abnormally. start-date-and-time - termination-date-and-time (required-time)

The database reorganization of the scheduler service terminated abnormally.

(S)

Terminates the database reorganization.

(O)

Use the database reorganization log file and the Windows event log or syslog to examine the cause of the error, and then reorganize the ISAM database of the scheduler service.

KAVS1503-I
The ISAM unused area size of the scheduler service (service-name) is size-in-megabytes.

The size of the unused area of the ISAM file of the scheduler service is output.

(S)

Outputs the size of the unused area of the ISAM file.

KAVS1504-W
The ISAM unused area size of the scheduler service (service-name) is size-in-megabytes, which exceeds the size-in-megabytes threshold value.

The size of the unused area of the ISAM file of the scheduler service reached the specified size for that area.

(S)

Cancels command execution.

(O)

Reorganize the ISAM file of the scheduler service.

KAVS1510-I
CONDENSE: ISAM reorganization-statistics

The status of the ISAM file of the scheduler service which is being reorganized is output to the database reorganization log.

This message contains the following information:

The start date and time, termination date and time, and required time

The size of the unused area and the total file size of the ISAM file before and after the database reorganization

(S)

The status of the ISAM file is output to the ISAM reorganization log.

KAVS1512-E
The size of ISAM file exceeded the maximum size (2-Gigabyte).

The size of the files composing the ISAM table exceeded the upper limit (2 gigabytes) during database access.

(S)

Terminates processing.

(O)

The database cannot be accessed because the size of the ISAM files exceeded 2 gigabytes. Reduce the size of the ISAM files by unregistering or deleting units unnecessary for operation or by reducing the number of days for storing job information in the job execution environment.

KAVS1513-E
An error occurred during command processing.: maintenance-information

An error occurred when JP1/AJS3 and OS commands were executed in a script.

(S)

Check whether the script execution environment is correct. Set the environment correctly, and then re-execute the script.

(O)

Terminates processing.

KAVS1514-E
An attempt to read the configuration definition failed. (item-name : return-code)

An attempt to read the configuration definition has failed.

(S)

Assumes the default and continues processing.

(O)

If the system assumes an unexpected value, correct the cause of the error and then reissue the request. The probable cause of the error is insufficient memory. Use the integrated trace log to check whether a log indicating insufficient memory was output at the same time when the error occurred. If the log indicating insufficient memory was output, recheck the memory estimate. If other unnecessary applications are running, stop them. If the cause of the error is not insufficient memory, collect the internal trace log and then contact the system administrator.

KAVS1515-E
Invalid specification in configuration definition. (item-name : return-code)

The configuration definition contains an invalid specification.

(S)

Assumes the default and continues processing.

(O)

Correctly specify the value indicated by item-name.

The output item names are described in 2. Environment Setting Parameters in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVS1516-E
Construction is invalid.(maintenance-information)

The configuration is invalid.

(S)

Cancels processing.

(O)

The installation or migration of JP1/AJS3 might not have finished. Either install JP1/AJS3 again or make sure that migration has been performed correctly.

KAVS1517-E
An error occurred during an attempt to acquire the configuration definition of the host (host-name). (service-name:item-name)

An attempt to obtain the environment setting parameter value for the host indicated in host-name has failed.

If service-name appears, an attempt to obtain the environment setting parameter value for the scheduler service indicated in service-name on the host indicated in host-name has failed.

If nothing is indicated in host-name, the physical host name is assumed.

(S)

The JP1/AJS3 service terminates abnormally if this message is output during startup of the JP1/AJS3 service.

The scheduler service terminates abnormally if this message is output during startup of the scheduler service.

(O)

Check the integrated trace log to identify the service (process) that output this message.

If a command output this message, make sure that the correct logical host name and scheduler service name are specified for the arguments.

If a process other than a command output this message, set up the environment again for the host indicated in host-name and the scheduler service indicated in service-name, and then restart the JP1/AJS3 service.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

To identify the name of the service (process) that output this message, check the AP name that is output to the integrated trace log concurrently with this message. For details about the output content of the integrated trace log file, see 1.2.1(2) Integrated trace log in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KAVS1518-E
Invalid specification in configuration definition of the host (host-name). (service-name:item-name)

An invalid value is specified for the environment setting parameter for the host indicated in host-name.

If service-name appears, an invalid value is specified for the environment setting parameter for the scheduler service indicated in service-name on the host indicated in host-name.

If nothing is indicated in host-name, the physical host name is assumed.

(S)

The JP1/AJS3 service terminates abnormally if this message appears during startup of the JP1/AJS3 service.

The scheduler service terminates abnormally if this message appears during startup of the scheduler service.

(O)

Set the value indicated in item-name correctly.

For details about output item names, see2. Environment Setting Parameters in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2

KAVS1570-I
Adapter command (maintenance-information-1) started.

The adapter command started.

The following information is shown in maintenance-information.

maintenance-information-1: The adapter command name and the specified option value

maintenance-information-2: The directory in which the backup file is stored

(S)

The adapter command started.

KAVS1571-I
Adapter command (maintenance-information-1) ended. (maintenance-information-2)

The adapter command ended.

The following information is shown in maintenance-information.

maintenance-information-1: The adapter command name

maintenance-information-2: The return value of the adapter command

(S)

The adapter command started.

KAVS1572-W
Adapter command (maintenance-information-1) canceled.

The adapter command was canceled.

The following information is shown in maintenance-information.

maintenance-information-1: Adapter command name

(S)

The adapter command was canceled.

KAVS1600-E
The specified unit name is invalid.

The status could not be acquired because of one of the following reasons after you specified the unit name.

The unit does not exist.

You have no permission for the unit.

The unit exists under the manager job group, manager jobnet, or the root jobnet. The status of the unit is unavailable.

This message is output to the Information text area in the Detail Information - [object-type] dialog box. For details about this dialog box, see 16.3.5 Detail Information - [object-type] dialog box in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

(S)

Stops acquiring the status of the unit.

(O)

Specify the name of the unit whose status is available and for which you have permission.

KAVS1601-E
Requests to the specified unit could not be processed.

The request is not supported for the unit. The status could not be acquired.

This message is output to the Information text area in the Detail Information - [object-type] dialog box. For details about this dialog box, see 16.3.5 Detail Information - [object-type] dialog box in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

(S)

Stops acquiring the status of the unit.

(O)

Specify the name of the unit whose status is available.

KAVS1602-E
Maintenance is being performed, so status obtainment is not possible.

The status could not be obtained because database maintenance was in progress.

This message is output to the Information text area in the Detail Information - [object-type] dialog box. For details about this dialog box, see 16.3.5 Detail Information - [object-type] dialog box in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

(S)

Terminates the status acquisition processing for the specified unit.

(O)

Wait until maintenance finishes, and then re-execute the operation.

KAVS1703-E
The command executed during reorganization of the scheduler service (service-name) database ended abnormally.: Jischk -l3 table-name : return code = return-code-from-Jischk (Please look at maintenance--log-file-name)

While maintenance was being performed by the jajs_maintain command, invalid data was detected by the Jischk command, which verifies consistency between ISAM files. For details of the error message output by Jischk, see the maintenance log file.

(S)

Cancels command execution. If there are any tables in the service still being processed, the system continues command execution.

(O)

Collect data and then contact the system administrator.

KAVS1704-E
The command executed during reorganization of the scheduler service (service-name) database ended abnormally.: Jisext table-name table-name.back: return code = return-code-from-Jisext

While maintenance was being performed with the jajs_maintain command, an error occurred in the Jisext command, which extracts data from ISAM files.

(S)

Cancels command execution. If there are any tables in the service still being processed, the system continues command execution.

(O)

Execute the command as a superuser or an administrator. Check whether the service is starting, there is a process that is using the file, or the disk has sufficient free space. Then, re-execute the command.

KAVS1705-E
The command executed during reorganization of the scheduler service (service-name) database ended abnormally.: Jisconv -t SI-table-name.back table-name_NEW: return code = return-code-from-Jisconv

While maintenance was being performed with the jajs_maintain command, an error occurred for the Jisconv command, which re-creates ISAM files from extracted data.

(S)

Cancels command execution. If there are any tables in the service still being processed, the system continues command execution.

(O)

Execute the command as a superuser or an administrator. Check whether the disk has sufficient free space, and re-execute the command. If you cannot determine the cause of the error, collect data and then contact the system administrator.

KAVS1706-E
An attempt to create a backup directory during reorganization of the scheduler service (service-name) database failed. (directory-name): return code = return-code

While maintenance was being performed with the jajs_maintain command, the working directory could not be created.

(S)

Cancels command execution. If there are other services being processed, the system continues command execution.

(O)

Check whether you have the permission to write into the directory for the temporary file for the scheduler service or the disk has sufficient free space.

KAVS1707-E
An attempt to copy files for backing up and recovering ISAM files during reorganization of the scheduler service (service-name) database failed. (table-name): return code = return-code

While maintenance was being performed with the jajs_maintain command, the file to back up and recover ISAM files could not be copied.

(S)

Cancels command execution. If there are any tables in the service still being processed, the system continues command execution.

(O)

Check whether the disk has sufficient free space, and then re-execute the command.

KAVS1709-E
An attempt to rename files for recovering ISAM files during reorganization of the scheduler service (service-name) database failed. (table-name): return code = return-code

While maintenance was being performed with the jajs_maintain command, the file to recover ISAM files could not be renamed.

(S)

Cancels command execution. If there are any tables in the service still being processed, the system continues command execution.

(O)

Check whether you have the permission to write into the directory for the database of the scheduler service.

KAVS1713-E
An attempt to start the scheduler service (service-name) failed.: maintenance-information

While the jajs_maintain command was performing maintenance, the scheduler service could not be started.

The probable causes are:

More than one jajs_maintain command was executed at the same time for the scheduler service.

The scheduler service was started during execution of the jajs_maintain command.

(S)

Cancels command execution. If, however, any other services remain unexecuted, the system continues command execution.

(O)

Wait until the jajs_maintain command terminates. Then manually start the scheduler service that could not be started. If an error message was output before or after this message, also see the instructions given by that message.

KAVS1714-E
An attempt to start the script for reorganizing the scheduler service (service-name) table (table-name) failed.: maintenance-information

While the jajs_maintain command was performing maintenance, the script to reorganize tables could not be started.

(S)

Cancels command execution. If, however, any other service has not been processed, the system continues command execution.

(O)

Memory may have become insufficient, or the number of started processes may have reached the limit to the number of processes that the system can start.

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 to 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).

KAVS1715-E
The script for reorganizing the scheduler service (service-name) table (table-name) failed.: maintenance-information

While the jajs_maintain command was performing maintenance, the script to reorganize tables ended abnormally because of an unexpected error.

(S)

Cancels command execution. If, however, the running service has unprocessed tables, the system continues command execution.

(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 (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 (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.

(S)

Cancels command execution.

(O)

Log off from programs such as JP1/AJS3 - View or JP1/AJS3 Console to make sure that there are no processes accessing the database.

KAVS1719-I
The maintenance processing of the scheduler service ended normally.

The maintenance of the scheduler service ended normally.

(S)

Performs a normal termination of the maintenance of the scheduler service.

KAVS1720-E
The maintenance processing of the scheduler service ended abnormally.: maintenance-information

The maintenance of the scheduler service ended abnormally. The probable causes are:

The disk does not have sufficient free space.
If parallel execution is enabled, sufficient free space is required on the disk of the system.

The number of open files for a process or system reached the maximum.
Check the process running status of the machine and wait until the number of running processes is reduced. Then, re-execute the command.

Memory was insufficient.
In UNIX, recheck the settings of the kernel parameters for memory.
For details on the kernel parameters, see Release Notes.

(S)

Performs an abnormal termination of the maintenance of the scheduler service.

(O)

See the maintenance log file and the Windows event log or syslog to determine the cause of the abnormal termination of the maintenance process according to the output error message, and then take the corrective action. Then re-execute the maintenance process.

If you cannot determine the cause of the error, collect data and then contact the system administrator (see 1.2.3 To the system administrators).

KAVS1721-I
The jajs_maintain command started.(maintenance-information)

The jajs_maintain command started.

(S)

Starts the jajs_maintain command.

KAVS1722-I
jajs_maintain command ended normally.

The jajs_maintain command ended normally.

(S)

Performs a normal termination of the jajs_maintain command.

KAVS1723-E
jajs_maintain command ended abnormally.

The jajs_maintain command ended abnormally.

(S)

Terminates the jajs_maintain command.

(O)

Check the following items to determine the cause of the abnormal termination of the maintenance process. Then, re-execute the maintenance process.

When -show is specified
The status could not be acquired probably because the operation of the job execution environment was starting or stopping. Wait for a while and then re-execute the command.

When -r start is specified
The job execution environment or scheduler service that you attempted to recover may have been maintained. Check the status of the job execution environment or scheduler service you must recover, and then re-execute the command.

When -m manager or -m scheduler is specified
Take action according to the message that is output to standard error at the same time as this message, and then re-execute the command.

KAVS1724-E
The scheduler service control file does not exist.

A file necessary for executing the command has not been created.

(S)

Cancels command execution.

(O)

Take the following actions:

Check whether the specified scheduler service name contains errors.

Check whether the specified scheduler service has been set up. If the specified scheduler service has not been set up yet, set it up by executing the ajssetup command.

If this message was output after you upgraded the version, start the JP1/AJS3 service. Starting the JP1/AJS3 service creates control files for all the scheduler services on the physical or logical object host.

If a cluster system is used, you must start the JP1/AJS3 service once when a failover occurs for the first time.

KAVS1725-E
An error occurred in the processing accompanying the reconfiguration of the job execution environment.: maintenance-information-1 (maintenance-information-2)

An error occurred in processing involved in the reorganization of the job execution environment.

(S)

Continues processing.

(O)

The system may have failed to reorganize the job execution environment. Correct the cause of the error according to the instructions given by the KAVU message corresponding to one of the following messages indicated in maintenance-information-1, and then re-execute the maintenance command. For details about messages beginning with KAVU, see 1.1 Messages beginning with KAVU (Messages about the job execution control) in the manual Job Management Partner 1/Automatic Job Management System 3 Messages 2.

An attempt to acquire the database information failed.
See KAVU0500-E.

Memory became insufficient.
See KAVU0922-E.

A logical contradiction occurred.
See KAVU0923-E.

The manager cannot be connected.
See KAVU0945-E.

The IP address could not be acquired from the manager host name.
See KAVU0946-E.

Starting or stopping is being processed.
See KAVU0950-E.

No response from the manager.
See KAVU0953-E.

The command could not be executed because of internal factor at the manager.
See KAVU0954-E.

Memory became insufficient at the manager.
See KAVU0966-E.

A fatal error occurred in the manager.
See KAVU0968-E.

A logical contradiction occurred in the manager.
See KAVU0969-E.

That request is not supported by the requested manager.
See KAVU0970-E.

The execution environment is invalid.
See KAVU0972-E.

KAVS1726-I
The scheduler service (scheduler-service-name) was shifted to maintenance mode.

The scheduler service was put into maintenance mode.

(S)

Continues processing.

KAVS1727-I
The scheduler service (scheduler-service-name) was stopped.

The scheduler service was stopped.

(S)

Continues processing.

KAVS1728-I
The scheduler service (scheduler-service-name) has already stopped.

(S)

Continues processing.

KAVS1729-I
The start request of the scheduler service (scheduler-service-name) was executed.

A request to start the scheduler service was made.

(S)

Continues processing.

KAVS1730-I
The maintenance mode of the scheduler service (scheduler-service-name) was canceled.

Maintenance mode was canceled for the scheduler service .

(S)

Continues processing.

KAVS1731-E
Back up scheduler database (unit information only).

The system started the backup process only for the unit definition table of the scheduler service.

(S)

Continues processing.

KAVS1732-E
Succeeded in backup of a scheduler service ISAM file.

The system backed up the ISAM files for the scheduler service successfully.

(S)

Continues processing.

KAVS1733-E
Backup directory (backup-directory-name).

The system displays the backup directory name.

(S)

Continues processing.

KAVS1734-E
-F option is not specified.

The -F option is missing.

(S)

Cancels command execution.

(O)

Specify scheduler-service-name in the -F option, and then re-execute the command.

KAVS1735-E
Need to rerun this command.

You need to re-execute this command.

(S)

Cancels command execution.

(O)

See the message output together with this message, and then take proper action.

KAVS1736-E
Backup failed. Command ended abnormally.: ajsgtroot -F service-name option : return code = return-value-from-ajsgtroot-command

The ajsgtroot command could not be executed.

(S)

Cancels command execution.

(O)

Check whether configuration definition information about the specified scheduler service is defined correctly.

KAVS1737-E
Database type of (scheduler-service-name) is not ISAM.

The type of the database that the specified scheduler service is to manipulate is not ISAM.

(S)

Cancels command execution.

(O)

Specify the name of a scheduler service that can manipulate a database of the ISAM type, and then re-execute the command.

KAVS1738-E
Specified name is not directory (directory-name).

The value specified as the database directory name for the specified scheduler service is not a directory. Alternatively, the value specified as the recovery source directory is not a directory.

(S)

Cancels command execution.

(O)

Check whether configuration definition information is defined correctly.

KAVS1739-E
Backup failed. Failed to make directory (directory-name).: return code = return-value-from-mkdir

Since the backup directory could not be created, the ISAM files for the scheduler service could not be backed up.

(S)

Cancels command execution.

(O)

If you specified the -b option, check whether the parent directory of the specified directory has write permission and is a directory. If you did not specify the -b option, check whether the directory of the scheduler service backup destination has write permission and is a directory.

KAVS1740-E
Cannot access backup directory (directory-name).

You cannot access the backup directory.

(S)

Cancels command execution.

(O)

If you specified the -b option, check whether the specified directory has write permission.

KAVS1741-E
Backup failed. Failed to copy (file-name).: return code = return-value-from-cp

Since the file could not be copied, the ISAM files for the scheduler service could not be backed up.

(S)

Cancels command execution.

(O)

Check whether the backup directory has write permission. If you want to make a backup in the backup directory by overwriting data, check whether the files you have write permission for stored in the backup directory.

Check also whether the disk has free space.

Take actions according to the error message of the cp command output together with this message.

KAVS1742-E
Backup failed. Failed to compare (file-name).: return code = return-value-from-cmp

Since the system could not compare files, it could not back up the ISAM files for the scheduler service.

(S)

Cancels command execution.

(O)

The system could not compare the files at the backup source and the backup destination. The database for the scheduler service may have been updated. Take actions according to the error message of the cmp command output together with this message.

KAVS1751-E
Restoring scheduler database (unit information only).

The system restores the unit definition table for the scheduler service.

(S)

Continues processing.

KAVS1752-E
Succeeded in restoring of a scheduler service ISAM file.

The system recovered the unit definition table for the scheduler service successfully.

(S)

Continues processing.

KAVS1753-E
Restore failed. Command ended abnormally.: ajsgtroot -F service-name option : return code = return-value-from-ajsgtroot-command

Since the system could not execute the ajsgtroot command, restoration failed.

(S)

Cancels command execution.

(O)

Check whether configuration definition information about the specified scheduler service is defined correctly.

KAVS1754-E
Cannot access database directory (directory-name).

You cannot access the database directory.

(S)

Cancels command execution.

(O)

If you have specified the -b option, check whether the specified directory has write permission.

KAVS1755-E
A file (file-name) is not found.

The file is not found.

(S)

Cancels command execution.

(O)

The unit definition table for the scheduler service is not stored in the directory specified as the recovery source directory.

KAVS1756-E
Failed to delete ISAM file (file-name).: return code = return-value-from-rm

The system could not delete the ISAM file.

(S)

Cancels command execution.

(O)

Take actions according to the error message of the rm command output together with this message.

KAVS1757-E
Restore failed. Failed to copy (file-name).: return code = return-value-from-cp

The ISAM file could not be copied.

(S)

Cancels command execution.

(O)

Check whether the database directory has write permission.

Check also whether the disk has free space.

Take action according to the error message of the cp command output together with this message.

KAVS1758-E
Restore failed. Failed to compare (file-name) : return code = return-value-from-cmp

The ISAM file could not be copied.

(S)

Cancels command execution.

(O)

Check whether the disk has free space. Take action according to the error message of the cmp command output together with this message.

KAVS1759-E
Restore failed. Command ended abnormally.: command-name option : return code = return-value-from-command

The system could not execute the command, so restoration failed.

(S)

Cancels command execution.

(O)

Check whether the command shown in command-name can be executed in the current environment, and take action according to the error message output together with this message.

KAVS1770-I
The adapter command setup has started.

Adapter command setup has started.

(S)

Continues processing.

KAVS1771-I
The adapter command setup completed normally.

Adapter command setup ended normally.

(S)

Continues processing.

KAVS1772-I
The adapter command unsetup has started.

Adapter command unsetup has started.

(S)

Continues processing.

KAVS1773-I
The adapter command unsetup completed normally.

Adapter command unsetup ended normally.

(S)

Continues processing.

KAVS1774-E
The logon account does not have permission to setup.

Since you do not have permission to execute the command, you cannot execute it.

(S)

Cancels command execution.

(O)

Re-execute the command as a user with permission to execute it.

KAVS1775-E
The argument arguments is incorrect.

The command argument is invalid.

(S)

Cancels command execution.

(O)

Check the command arguments, and then re-execute the command.

KAVS1776-E
There are too many command arguments.

Too many arguments are specified in the command.

(S)

Cancels command execution.

(O)

Check the command arguments, and then re-execute the command.

KAVS1777-E
Setup and unsetup cannot be specified simultaneously.

You cannot perform setup and unsetup at the same time.

(S)

Cancels command execution.

(O)

Check the command arguments, and then re-execute the command.

KAVS1778-E
A duplicated command argument cannot be specified.

You cannot specify a command argument more than once.

(S)

Cancels command execution.

(O)

Check the command arguments, and then re-execute the command.

KAVS1779-E
JP1/Base is not installed, so the adapter command setup failed.

Since a JP1/Base product has not been installed, the system could not set up the adapter command.

(S)

Cancels command execution.

(O)

Check whether related products have been installed.

KAVS1780-E
The JP1/Base installation location is unobtainable.

The system could not obtain the JP1/Base installation location.

(S)

Cancels command execution.

(O)

Check whether the related products have been installed.

KAVS1781-E
The adapter-command adapter command does not exist.

The adapter command does not exist.

(S)

Cancels command execution.

(O)

Check whether the adapter command exists.

KAVS1782-E
The adapter command configuration file storage directory does not exist.

The directory containing the adapter command configuration file does not exist.

(S)

Cancels command execution.

(O)

Check whether the directory containing the adapter command configuration file exists.

KAVS1783-E
An attempt to delete the configuration-file adapter command configuration file failed.

The system could not delete the adapter command configuration file.

(S)

Cancels command execution.

(O)

Check whether the adapter command configuration file exists and what its access permission is.

KAVS1784-E
An attempt to setup an adapter command failed.

The system could not set up the adapter command.

(S)

Cancels command execution.

KAVS1785-E
The adapter-command-configuration-file adapter command configuration file does not exist.

The adapter command configuration file does not exist.

(S)

Continues processing.

KAVS1786-E
An unexpected error occurred.

An unexpected error occurred.

(S)

Cancels command execution.

(O)

Contact the system administrator.

KAVS1790-E
An error occurred in the processing which acquires the process state of job execution environment. : maintenance-information

An error occurred during the processing for acquiring the operating status of the job execution environment.

(S)

Cancels command execution.

However, if the -shown option is specified in the jajs_maintain command, the system continues processing.

(O)

Correct the cause of the error according to the instructions given by the KAVU message corresponding to one of the following messages indicated in maintenance-information-1, and then re-execute the maintenance command. For details about messages beginning with KAVU, see 1.1 Messages beginning with KAVU (Messages about the job execution control) in the manual Job Management Partner 1/Automatic Job Management System 3 Messages 2.

An attempt to acquire the database information failed.
See KAVU0500-E.

Memory became insufficient.
See KAVU0922-E.

A logical contradiction occurred.
See KAVU0923-E.

The manager cannot be connected.
See KAVU0945-E.

The IP address could not be acquired from the manager host name.
See KAVU0946-E.

Starting or stopping is being processed.
See KAVU0950-E.

No response from the manager.
See KAVU0953-E.

The command could not be executed because of internal factor at the manager.
See KAVU0954-E.

Memory became insufficient at the manager.
See KAVU0966-E.

A fatal error occurred in the manager.
See KAVU0968-E.

A logical contradiction occurred in the manager.
See KAVU0969-E.

That request is not supported by the requested manager.
See KAVU0970-E.

The execution environment is incorrect.
See KAVU0972-E.

KAVS1791-E
An error occurred in the processing which usually requires operation of job execution environment. :maintenance-information

An error occurred in the processing for a request made to the job execution environment for performing normal operation.

(S)

Cancels command execution.

(O)

Correct the cause of the error according to the instructions given by the KAVU message corresponding to one of the following messages indicated in maintenance-information-1, and then re-execute the maintenance command. For details about messages beginning with KAVU, see 1.1 Messages beginning with KAVU (Messages about the job execution control) in the manual Job Management Partner 1/Automatic Job Management System 3 Messages 2.

An attempt to acquire the database information failed.
See KAVU0500-E.

Memory became insufficient.
See KAVU0922-E.

A logical contradiction occurred.
See KAVU0923-E.

The manager cannot be connected.
See KAVU0945-E.

The IP address could not be acquired from the manager host name.
See KAVU0946-E.

Starting or stopping is being processed.
See KAVU0950-E.

No response from the manager.
See KAVU0953-E.

The command could not be executed because of internal factor at the manager.
See KAVU0954-E.

Memory became insufficient at the manager.
See KAVU0966-E.

A fatal error occurred in the manager.
See KAVU0968-E.

A logical contradiction occurred in the manager.
See KAVU0969-E.

That request is not supported by the requested manager.
See KAVU0970-E.

The execution environment is invalid.
See KAVU0972-E.

KAVS1801-I
The queueless agent will now start.

The queueless agent service starts.

(S)

The queueless agent service starts.

KAVS1802-I
The queueless agent will now stop.

The queueless agent service ends.

(S)

Terminates the queueless agent service.

KAVS1803-E
The queueless agent abnormally ended.

The queueless agent service ended abnormally.

(S)

The queueless agent service ended abnormally.

(O)

Take action according to the instructions given by the message that was output immediately before this message.

KAVS1804-I
The queueless agent will now terminate.

The queueless agent service accepted a request for forced termination of the ajsqlstop command.

(S)

Terminates the queueless agent service.

KAVS1805-E
The port (port-name) cannot be used because another user is already using the port.

The service that output this message cannot start because the port indicated in port-name is being used.

(S)

Terminates the service that output this message.

(O)

Take either of the following actions, and then restart the service that output this message :

Use the netstat command or another means to identify the process that is using the port indicated in port-name, and stop that process. To stop the process, use Task Manager in Windows and use the kill command in UNIX.

Edit the services file to change the port number used by the service that output this message.

To identify the name of the service that output this message, check the AP name that is output to the integrated trace log concurrently with this message.

For details about the output content of the integrated trace log file, see 1.2.1(2) Integrated trace log in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KAVS1806-I
The user mapping cache was cleared. : process-name

The user-mapping cache indicated in process-name was cleared.

(S)

Cleared the user-mapping cache indicated in process-name.

KAVS1807-E
The maximum number of waiting jobs has been reached, so the job (job-name) cannot be accepted.

The system cannot accept the job indicated in job-name because both the maximum number of concurrently executable jobs and the maximum number of waiting jobs have been reached.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Use JP1/AJS3 - View to make sure that the number of queueless jobs waiting for execution for the queueless agent service has not reached the maximum number of waiting jobs. Make sure that the number of waiting queueless jobs is within the maximum, and re-execute the queueless job indicated in job-name that caused an error.

The current setting of the maximum number of concurrently executable jobs and the maximum number of waiting jobs might not suit the current operation. Review the values and then change them if necessary.

The maximum number of concurrently executable jobs is set in the AJSQL_JOBMAX environment setting parameter, and the maximum number of waiting jobs is set in the AJSQL_JOBWAITMAX environment setting parameter. For details, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVS1808-E
The maximum number of waiting jobs in the class (class-name) has been reached, so the job (job-name) cannot be accepted.

The queueless job indicated in job-name cannot be accepted because both the maximum number of concurrently executable jobs and the maximum number of waiting jobs for the class indicated in class-name have been reached.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Use JP1/AJS3 - View to make sure that the number of queueless jobs waiting for execution for the queueless agent service's class indicated in class-name has not reached the maximum number of waiting jobs. Make sure that the number of waiting queueless jobs is within the maximum, and re-execute the queueless job indicated in job-name that caused an error.

The current setting of the maximum number of concurrently executable jobs and the maximum number of waiting jobs for the class indicated in class-name might not suit the current operation. Review the values and then change them if necessary.

For the class, the maximum number of concurrently executable jobs is set in the AJSQL_CJOBMAX environment setting parameter, and the maximum number of waiting jobs is set in the AJSQL_CJOBWAITMAX environment setting parameter. For details, see 6.4.1 Executing jobs with a class specified in a queueless job environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 14.4.1 Executing jobs with a class specified in a queueless job environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

KAVS1809-E
The request is to an unattached host (host-name), so the job (job-name) cannot be accepted.
The queueless job indicated in job-name could not be accepted because the job execution request was issued to the unattached host indicated in host-name.

(S)

Places the queueless job indicated in job-name into Failed to start status.
(O)

Execute the ajsqlattach command to attach the host indicated in host-name, and then re-execute the queueless job indicated in job-name that resulted in the error.
Example: In this example, the command attaches the logical host Lhost.

Execute the ajsqlattach command as follows:
 
ajsqlattach -h Lhost
 
For details on the ajsqlattach command, see ajsqlattach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
KAVS1810-E
The specified class (class-name) does not exist, so the job (job-name) cannot be accepted.

The queueless job indicated in job-name cannot be accepted because the class indicated in class-name does not exist.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Take the following actions:

Check whether the correct host name and class name are specified for Target host. Correct the invalid host name or class name, and then re-execute the queueless job indicated in job-name that resulted in the error.

Execute the ajsqlstatus command to make sure that the class indicated in class-name is on the host specified for Target host.
Example: In this example, the command outputs detailed information for the logical host Lhost.
Execute the ajsqlstatus command as follows:

ajsqlstatus -h Lhost

For details on the ajsqlstatus command, see ajsqlstatus in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

If the class indicated in class-name does not exist, create the class and then re-execute the queueless job indicated in job-name that resulted in the error. For details about how to create a class, see 6.4.1 Executing jobs with a class specified in a queueless job environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 14.4.1 Executing jobs with a class specified in a queueless job environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).

KAVS1811-E
Memory is insufficient, so the job (job-name) cannot be accepted.

The queueless job indicated in job-name cannot be accepted due to insufficient memory.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Check the amount of memory available by using Task Manager in Windows or the top command or another means in UNIX.

Wait until the memory necessary for job execution can be allocated, and then re-execute the queueless job indicated in job-name that resulted in the error.

KAVS1812-E
The configuration definition of the logical host (logical-host-name) does not exist.

The environment of the logical host indicated in logical-host-name is not set up.

(S)

Continues processing if the error occurred during startup of a queueless agent service. However, the logical host is not handled as the host where the job is executed.

The system cancels processing if the error occurred during execution of a command.

(O)

Set up the environment for the logical host indicated in logical-host-name, and then restart the queueless agent service. If the error occurred during execution of a command, make sure that the correct logical host name is specified in the argument.

KAVS1813-E
An error occurred during an attempt to acquire the configuration definition of the logical host (logical-host). (function=maintenance-information-1, code=maintenance-information-2)

An attempt to acquire the environment setting parameter value for the logical host indicated in logical-host failed.

(S)

If a queueless agent service output this message during startup, the system terminates the queueless agent service abnormally. If this message is output during processing to attach the logical host, the system cancels the attach processing.

If a command related to queueless job execution control output this message, the system cancels command execution.

If the queueless cluster process output this message during startup, the system cancels processing to attach the logical host and continues startup.

(O)

Check the integrated trace log to identify the service (process) that output this message.

If the queueless agent service output this message, set up the environment again for the physical host and the logical host indicated in logical host-name, and then restart the queueless agent service.

If a command related to queueless job execution output this message, make sure that the correct logical host name is specified in the argument.

If a queueless cluster process output this message, set up the environment again for the logical host indicated in logical-host-name, and then restart the JP1/AJS3 service.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

To identify the name of the service (process) that output this message, check the AP name that is output to the integrated trace log concurrently with this message. For details about the output content of the integrated trace log file, see 1.2.1(2) Integrated trace log in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

KAVS1814-E
The host name is invalid. : maintenance-information-1 (maintenance-information-2) maintenance-information-3

The host name indicated in maintenance-information-1 is invalid. Possible causes are:

The manager host name indicated in maintenance-information-1 cannot be resolved to the IP address.

The environment settings for the host name indicated in maintenance-information-1 contain errors.

If nothing is indicated in maintenance-information-1, the physical host name is assumed.

(S)

If a queueless agent service output this message during startup, the system terminates the queueless agent service abnormally. If this message is output during processing to attach the logical host, the system cancels the attach processing. If this message is output during execution or forced termination of a queueless job, the system continues processing.

If the queueless file transfer service output this message during startup, the system terminates the queueless file transfer service abnormally.

(O)

Take the following actions:

Make sure that the host name indicated in maintenance-information-1 is set in the hosts and jp1hosts files.

If this message is output during processing to forcibly terminate the queueless job, you must stop the program manually by using Task Manager in Windows or the kill command or another means in UNIX.

KAVS1815-E
An attempt to write to the status file (status-file-name) failed.: maintenance-information-1 (maintenance-information-2)

An attempt to write to the status file indicated in status-file-name and managed for one logical host for the queueless agent service has failed.

(S)

Continues processing.

(O)

Take one of the following actions:

If No such file or directory is indicated in maintenance-information-1, the status file indicated in status-file-name might have been deleted. If the file does not exist, restart the queueless agent service, or detach the logical host containing the status file indicated in status-file-name that resulted in the error, and then attach it again.

If Permission denied is indicated in maintenance-information-1, write permission for the status file indicated in status-file-name might have been changed. Change the permission so that the user who started the queueless agent service and the OS user who executes the queueless job can write to the status file indicated in status-file-name. Then, restart the queueless agent service, or detach the logical host containing the status file indicated in status-file-name that resulted in the error, and then attach it again.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message. Also check the following probable causes, and then correct the error, if any.
- The disk does not have sufficient free space.
- Memory is insufficient.
- A directory having the same name as the status file has already been created in the directory in which the status file is to be created.
After correcting the error, restart the queueless agent service or detach the logical host containing the status file indicated in status-file-name that resulted in the error, and then attach it again.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

Examples:

In this example, the command detaches the logical host Lhost.
Execute the ajsqldetach command as follows:

ajsqldetach -h Lhost

For details on the ajsqldetach command, see ajsqldetach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

In this example, the command attaches the logical host Lhost.
Execute the ajsqlattach command as follows:

ajsqlattach -h Lhost

For details on the ajsqlattach command, see ajsqlattach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVS1816-E
An attempt to open the status file (status-file-name) failed.: maintenance-information-1 (maintenance-information-2)

Since the system could not open the status file indicated in status-file-name managed for each logical host for the queueless agent service, the system cannot use the status file for the logical host.

(S)

Terminates the queueless agent service abnormally if a queueless agent service output this message during startup. If this message is output during processing to attach the logical host, the system cancels the processing.

(O)

Take one of the following actions:

If No such file or directory is indicated in maintenance-information-1, the status file indicated in status-file-name might have been deleted. If the file does not exist, restart the queueless agent service, or detach the logical host containing the status file indicated in status-file-name that resulted in the error, and then attach it again.

If Permission denied is indicated in maintenance-information-1, write and read permissions for the status file indicated in status-file-name might have been changed. Change the permissions so that the user who started the queueless agent service and the OS user who executes the queueless job can read and write to the status file indicated in status-file-name. Then, restart the queueless agent service, or detach the logical host containing the status file indicated in status-file-name that resulted in the error, and then attach it again.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message. Also check the following probable causes, and then correct the error, if any.
- The disk does not have sufficient free space.
- Memory is insufficient.
- A directory having the same name as the status file has already been created in the directory in which the status file is to be created.
After correcting the error, restart the queueless agent service or detach the logical host containing the status file indicated in status-file-name that resulted in the error, and then attach it again.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

Examples:

In this example, the command detaches the logical host Lhost.
Execute the ajsqldetach command as follows:

ajsqldetach -h Lhost

For details on the ajsqldetach command, see ajsqldetach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

In this example, the command attaches the logical host Lhost.
Execute the ajsqlattach command as follows:

ajsqlattach -h Lhost

For details on the ajsqlattach command, see ajsqlattach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVS1817-E
IPC initialization failed, so the job (job-name) cannot be executed. (maintenance-information-1)

The queueless job indicated in job-name cannot be executed due to one of the following causes:

An attempt to acquire the IP address from the name of the host on which the queueless job indicated in job-name was executed has failed (a wrong IP address was acquired).

A communication error occurred.

Memory is insufficient.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Take one of the following actions, and then re-execute the queueless job indicated in job-name that resulted in the error.

In the DNS, hosts file, or jp1hosts file, correctly specify the host name and IP address of the host that executes queueless jobs.

Use the ping command or another means to check the network status and correct the network failure.

Use Task Manger in Windows or the top command or another means in UNIX to make sure that memory is sufficient.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1818-E
An error occurred during internal file (file-name) processing, so the job (job-name) cannot be executed.: maintenance-information-1 (maintenance-information-2)

The queueless job indicated in job-name cannot be executed because an error occurred during processing of the internal file indicated in file-name used for execution of the queueless job.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Correct the error as follows, and then re-execute the queueless job indicated in job-name that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, make sure that the directory path specified in the internal file in file-name exists.

If Permission denied is indicated in maintenance-information-1, make sure that read and write permissions for the directory path to the internal file indicated in file-name are set for the user who started the queueless agent service and the OS user who executes the queueless job.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message. Also check the following probable causes, and then correct the error, if any.
- The disk does not have sufficient free space.
- Memory is insufficient.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1819-E
The specified work path (path-name) is invalid, so the job (job-name) cannot be executed.: maintenance-information-1 (maintenance-information-2)

The queueless job indicated in job-name cannot be executed because an attempt to access the work path indicated in path-name or the current directory has failed.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Make sure that the directory path specified in the work path indicated in path-name exists. Alternatively, make sure that the user who started the queueless agent service and the OS user who executed the queueless job can read and write to the work path indicated in path-name. Then, re-execute the queueless job indicated in job-name that resulted in the error.

KAVS1820-E
Memory is insufficient, so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed because of insufficient memory.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Check the amount of memory available by using Task Manager in Windows or the top command or another means in UNIX.

Wait until the memory necessary for executing the queueless job indicated in job-name that resulted in the error can be allocated, and then re-execute the queueless job.

KAVS1821-E
An iconv_open error occurred, so character conversion is not possible.: maintenance-information-1 (maintenance-information-2)

The system does not convert the character set because it could not make preparations for character set conversion.

(S)

Continues processing.

(O)

To convert the character sets, check the character settings and then restart the queueless agent.

KAVS1822-E
The file (file-name) does not exist on the transmission source host (host-name), so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed because the file indicated in file-name does not exist on the manager host indicated in host-name.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Take either of the following actions, and then re-execute the queueless job indicated by job-name that resulted in the error:

Make sure that the file to be transferred (file-name) exists on the transmission source host (host-name).

Make sure that the name of the file to be transferred (file-name) has no more than 254 characters (if the job is a PC job).

KAVS1823-E
No access permission is granted for the file (file-name) on the transmission host (host-name), so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed because there is no access permission for the file indicated in file-name on the manager host indicated in host-name.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

A directory path name might have been specified in the file indicated in file-name. If a directory path name is specified, specify the file name for File to transfer, and then re-execute the queueless job indicated in job-name that resulted in the error.

KAVS1824-E
An error occurred in the file (file-name) on the transmission source host (host-name), so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed because an attempt to read the file indicated in file-name on the manager host indicated in host-name has failed.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Give permission for reading the file indicated in file-name to the user who started the queueless file transfer service, and then re-execute the queueless job indicated in job-name that resulted in the error.

KAVS1825-E
An error occurred in the transmission file (file-name), so the job (job-name) cannot be executed.: maintenance-information-1 (maintenance-information-2)

The queueless job indicated in job-name cannot be executed because an error occurred in the file indicated in file-name on the manager host indicated in host-name.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, the directory path specified in the destination file indicated in file-name does not exist. Make sure that the directory path exists.

If Permission denied is indicated in maintenance-information-1, an attempt to create the destination file indicated in file-name has failed. To ensure that this destination file can be created, set permissions so that the user who started the queueless agent service and the mapped OS user can read and write to the file or directory path.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1826-E
An IPC error occurred during file transmission, so the job (job-name) cannot be executed.: maintenance-information-1 (maintenance-information-2 maintenance-information-3)

The queueless job indicated in job-name cannot be executed due to a communication error that occurred during file transmission.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Execute the ping or jp1ping command on both the manager host and agent host to make sure they can communicate normally, and then re-execute the queueless job indicated in job-name that resulted in the error.

In addition, correct the error according to the information indicated in maintenance-information-1, and then re-execute the queueless job indicated in job-name that resulted in the error.

If you cannot correct the problem, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS1827-E
The job (job-name) cannot be executed because the processing is restricted.

The queueless job indicated in job-name cannot be executed because the queueless agent service is performing restricted processing.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Restart the queueless agent service, and then re-execute the queueless job indicated in job-name that resulted in the error.

KAVS1828-E
The specified priority value is invalid. (job-name)

If you have specified an execution priority of 4 or 5 for a UNIX job, you need the superuser privileges.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Change the OS user who executes the queueless job indicated in job-name to a superuser, or change the execution order to 1, 2, or 3. Then, re-execute the queueless job indicated in job-name that resulted in the error.

KAVS1829-E
A system call (function-name) error occurred in the Queueless Agent service. : maintenance-information-1 maintenance-information-2

A system call error occurred in the queueless agent service.

(S)

Cancels the service startup processing or the requested processing.

(O)

When function-name is GetProcAddress(Wow64DisableWow64FsRedirection) and maintenance-information-2 is 127, the DISABLE_FS_REDIRECTION environment setting parameter has been set on an OS that is not Windows Server 2003 (x64) Service Pack 1 or later. This environment setting parameter is defined in the execution environment settings file for queueless jobs.
Do not set this parameter on an OS that is not Windows Server 2003 (x64) Service Pack 1 or later.
For details about DISABLE_FS_REDIRECTION, see 6.6.2 Disabling file system redirection when jobs are executed in a WOW64 environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

When function-name is CreateDesktop, maintenance-information-2 is 8, and the AJSQL_CREATEWINDOWSTATION environment setting parameter is set to yes, there are too many OS users for the jobs to be executed.
Take action according to 6.4.3 Preventing a queueless job from ending abnormally with return value 128 in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.
For details on AJSQL_CREATEWINDOWSTATION, see 6.4.3 Preventing a queueless job from ending abnormally with return value 128 in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

For other cases, ask the system administrator to collect data (1.2.3 To the system administrators).

KAVS1830-E
The job (job-name) cannot be executed because the length of the string (string-before-conversion) after variable substitution is too long.: string-after-conversion

If there are substitutions made for the variables used in the job definition, the length of some definition items might exceed the maximum. In such a case, the queueless job indicated in job-name cannot be executed.

The following shows the maximum length for each definition item after substitutions for the variables.

Executable file name (for PC jobs only): 767 bytes

Script file name (for UNIX jobs only): 767 bytes

Parameter: 1535 bytes

Command statement (for UNIX jobs only): No limit

Standard input file name: 767 bytes

Standard output file name: 767 bytes

Standard error output file name: 767 bytes

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Edit the job definition so that the lengths of the items do not exceed their maximums after substitutions for the variables, and then re-execute the queueless job indicated in job-name that resulted in the error

KAVS1831-E
An attempt to attach the logical host (logical-host) has failed.
An attempt to attach the logical host indicated in logical-host failed when the queueless agent service was started, when the ajsqlattach command was executed, or when a queueless cluster process was started.

(S)

The queueless agent service cancels processing for attaching the logical host, and continues processing.

The system terminates the ajsqlattach command abnormally.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.
(O)

The probable causes are that the shared disk is not mounted or disk space is insufficient. Take action according to the message that was output to the integrated trace log before or after this message.

After correcting the error, execute the ajsqlattach command to re-attach the logical host that resulted in the error.

If this message appears during startup of a queueless cluster process, correct the error, and then restart the JP1/AJS3 service and re-attach the logical host that resulted in the error.
Example: In this example, the command attaches the logical host.

Execute the ajsqlattach command as follows:
 
  ajsqlattach -h Lhost
 
For details on the ajsqlattach command, see ajsqlattach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
KAVS1832-E
Reception processing timed out during TCP/IP communication. (name-of-host-to-be-connected, job-name, maintenance-information)

A wait for a response timed out.

Possible causes are as follows:

The CPU load on the host to be connected is very high.

System resources are insufficient.

(S)

If the error occurred when an attempt was made to start the queueless job, the system places the queueless job indicated in job-name into Failed to start status.

If the error occurred when an attempt was made to terminate the queueless job, the system places the queueless job indicated in job-name into ended abnormally status.

(O)

Check the CPU load on the host to be connected and the system resource limit in the kernel parameter settings, and then re-execute the queueless job indicated in job-name that resulted in the error.

If the problem cannot be corrected, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1833-E
An error occurred in the standard input file (file-name).: maintenance-information-1 (maintenance-information-2)

An error occurred during access to the standard input file.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, the standard input file indicated in file-name does not exist. Make sure that the standard input file indicated in file-name exists, and then re-execute the job.

If Permission denied is indicated in maintenance-information-1, an attempt to read the standard input file indicated in file-name has failed. Set appropriate permissions for the file and directory path so that the mapped OS user can read the standard input file indicated in file-name. Then re-execute the job.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1834-E
An error occurred in the standard output file (file-name).: maintenance-information-1 (maintenance-information-2)

An error occurred during access to the standard output file.

(S)

Places the queueless job into Failed to start status.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, the standard output file indicated in file-name does not exist. Make sure that the standard output file indicated in file-name exists, and then re-execute the job.

If Permission denied is indicated in maintenance-information-1, an attempt to read or write to the standard output file indicated in file-name has failed. Set appropriate permissions for the file and directory path so that the mapped OS user can read and write to the standard output file indicated in file-name. Then re-execute the job.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1835-E
An error occurred in the standard error output file (file-name).: maintenance-information-1 (maintenance-information-2)

An error occurred during access to the standard error output file.

(S)

Places the queueless job into Failed to start status.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, the standard error output file indicated in file-name does not exist. Make sure that the standard error output file indicated in file-name exists, and then re-execute the job

If Permission denied is indicated in maintenance-information-1, an attempt to read or write to the standard error output file indicated in file-name has failed. Set appropriate permissions for the file and directory path so that the mapped OS user can read and write to the standard error output file indicated in file-name. Then re-execute the job.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1836-E
An error occurred in the environment variable file (file-name).: maintenance-information-1 (maintenance-information-2)

An error occurred during access to the environment variable file.

(S)

Places the queueless job into Failed to start status.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, the environment variable file indicated in file-name does not exist. Make sure that the environment variable file indicated in file-name exists, and then re-execute the job.

If Permission denied is indicated in maintenance-information-1, an attempt to read the environment variable file indicated in file-name has failed. Set appropriate permissions for the file and directory path so that the mapped OS user can read the environment variable file indicated in file-name, and then re-execute the job.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1837-E
A JP1/AJS2 environment setting is incorrect. (logical host=logical-host-name, label=environment-setting-parameter-name)
The value set in the JP1/AJS3 environment settings for the logical host indicated in logical-host-name is incorrect.

(S)

Continues processing the default value of the label indicated in environment-setting-parameter-name.
(O)

Correct the value set in the label indicated in environment-setting-parameter-name on the host indicated logical-host-name. Then, for the physical host, restart the queueless agent service. For a logical host, execute the ajsqlattach command to attach the host indicated in logical-host-name.

If this message appears during startup of a queueless cluster process, correct the value of the label indicated in environment-setting-parameter-name, and then restart the JP1/AJS3 service.
Example: In this example, the command attaches the logical host.

Execute the ajsqlattach command as follows:
 
  ajsqlattach -h Lhost
 
For details on the ajsqlattach command, see ajsqlattach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
KAVS1838-E
An attempt to read the status file (file-name) failed.: maintenance-information-1 (maintenance-information-2)

An attempt to read the status file indicated in file-name that is managed for one logical host for the queueless agent service has failed.

(S)

Does not write the end status of the queueless job to the status file indicated in file-name that resulted in the error.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, the status file indicated in status-file-name does not exist. Make sure that the file indicated in status-file-name exists.

If Permission denied is indicated in maintenance-information-1, an attempt to read the status file indicated in file-name has failed. Check whether appropriate permissions are set for the file and directory path so that the OS user who started the queueless agent service can read the status file indicated in file-name.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1839-E
An error occurred during acquisition of the judgment file (file-name).: maintenance-information-1 (maintenance-information-2)

An error occurred during the acquisition of information from the judgment file indicated in file-name.

(S)

Places the queueless job into Failed to start or Ended abnormally status.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, the judgment file indicated in file-name does not exist. Make sure that the judgment file indicated in file-name exists, and then re-execute the job.

If Permission denied is indicated in maintenance-information-1, an attempt to read the judgment file indicated in file-name has failed. Set appropriate permissions for the file and directory path so that the mapped OS user can read the judgment file indicated in file-name. Then re-execute the job.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1840-E
There are too many characters in a line of the environment variable file (file-name).

There are too many characters in a line of the environment variable file indicated in file-name.

(S)

Places the queueless job into Failed to start status.

(O)

Check and correct the contents of the environment variable file so that each line is no more than 1,023 bytes, and then re-execute the job.

KAVS1841-E
Too many processes exist, so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed because too many processes are running on the system.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

The maximum number of processes that can run concurrently on the system might have been exceeded. Use the ps command or another means to check the number of processes running on the system. Make sure that the number of processes are within the maximum, and then re-execute the queueless job indicated in job-name that resulted in the error.

The maximum number of processes specified in the kernel parameter might not suit the current operation. Check the value for the entire system, and then change the value if necessary.

For details about how to estimate the kernel parameters for JP1/AJS3, see 3.2.5 Estimating the values for kernel parameters in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide

KAVS1842-E
Job result information cannot be sent because an internal file (file-name) error occurred.: maintenance-information-1 (maintenance-information-2)

The system could not report the contents of the result file to the manager host because an error occurred during processing of the internal file indicated in file-name that is used for execution of the queueless job.

(S)

Places the queueless job into Failed to start status if this message appears before the queueless job is started.

Places the queueless job into Ended abnormally status if this message appears after the queueless job is started.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If Permission denied is indicated in maintenance-information-1, an attempt to create, read, or write to the internal file indicated in file-name has failed. Set appropriate permissions for the directory path that has the internal file so that the user who started the queueless agent service and the mapped OS user can read or write to the internal file indicated in file-name.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message. Also check the following probable causes, and then correct the error, if any.
- The disk does not have sufficient free space.
- Memory is insufficient.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1843-E
User mapping failed on the remote ftp host (host-name), so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed due to unsuccessful user mapping on the manager host indicated in host-name.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

A message indicating the cause of the error that occurred in the queueless job indicated in job-name is output to the integrated trace log on the manager host indicated in host-name. Take action according to the instructions given by the message.

KAVS1844-E
An error occurred on the remote ftp host (host-name), so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed due to unsuccessful file transmission from the manager host indicated in host-name to the agent host.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

A message indicating the cause of the error that occurred in the queueless job indicated in job-name is output to the integrated trace log on the manager host indicated in host-name. Take action according to the instructions given by the message.

KAVS1845-E
An IPC error occurred during the result notification.: system-error-message (maintenance-information-1, maintenance-information-2)

The system could not report the contents of the result file to the manager host because a communication error occurred.

(S)

Places the queueless job into ended abnormally status.

(O)

Execute the ping and jp1ping commands to make sure that the agent host can communicate with the manager host indicated in host-name, and that the queueless file transfer service is running on this manager host. Then, re-execute the queueless job that resulted in the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1846-E
The job definition (job-name) is invalid.

The same name is assigned to the standard output file and the standard error output file, and different items are specified for additional information to be written.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Recheck the job definition statement and correct the job definition. Then, execute the job.

KAVS1847-W
A job that was waiting for execution was forcibly terminated.

This message is output when a queueless job that is waiting for execution is forcibly terminated.

(S)

Places the queueless job into Failed to start status.

KAVS1848-W
The job (job-name) was forcibly terminated. (process-ID)

This message indicates that the queueless job indicated in job-name was forcibly terminated.

(S)

Forcibly terminates the queueless job indicated in job-name.

KAVS1849-W
The job (job-name) was aborted. (process-ID)

This message indicates that the queueless job indicated in job-name was aborted.

(S)

Aborted the queueless job indicated in job-name.

KAVS1850-E
The logical host (host-name) is ignored because the number of logical hosts set for the queueless agent exceeds the limit.

The logical host indicated in host-name cannot be attached because the number of logical hosts attached to the queueless agent service has reached the maximum, that is, 9.

(S)

Continues processing.

(O)

A maximum of 9 logical hosts can be attached to the queueless agent service concurrently.

Execute the ajsqldetach command to detach an unneeded logical host, and then execute the ajsqlattach command to attach the logical host indicated in host-name again.

Examples:

In this example, the command detaches the logical host Lhost.
Execute the ajsqldetach command as follows:

ajsqldetach -h Lhost

For details on the ajsqldetach command, see ajsqldetach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

In this example, the command attaches the logical host Lhost.
Execute the ajsqlattach command as follows:

ajsqlattach -h Lhost

For details on the ajsqlattach command, see ajsqlattach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVS1851-I
The file transmission service will now start.

The queueless file transmission service starts.

(S)

Starts the queueless file transfer service.

KAVS1852-I
The file transmission service will now stop.

The file transmission service ends.

(S)

Terminates the queueless file transfer service.

KAVS1853-I
The file transmission service will now terminate.

The queueless file transfer service aborted because a forced termination request was accepted.

(S)

Terminates the queueless file transfer service.

KAVS1854-E
The file transmission service abnormally ended.

The queueless file transfer service ended abnormally.

(S)

Terminates the queueless file transfer service.

(O)

Take action according to the instructions given by the message that was output immediately before this message, and then restart the queueless file transfer service.

KAVS1855-W
Character code conversion failed. : maintenance-information-1 (maintenance-information-2)

Character set conversion failed, causing the following problems:

Data displayed in the Execution Result Details dialog box contains unreadable characters.

The file specified as the transfer destination file uses an invalid character set.

(S)

Continues processing.

(O)

Contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVS1861-E
The file transmission failed.

File transmission failed due to a communication failure between the manager host and the agent host during file transfer.

(S)

Continues job execution.

(O)

Execute the ping and jp1ping commands to make sure that the manager host and the agent host can communicate normally with each other. Then, re-execute the queueless job that resulted in the error.

If you cannot correct the problem, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS1862-I
The queueless cluster process (logical-host-name) will now start.

The queueless cluster process for the logical host (logical-host-name) will now start.

(S)

Starts the queueless cluster process indicated in logical-host-name.

KAVS1863-I
The queueless cluster process (logical-host-name) has started.

The queueless cluster process for the logical host (logical-host-name) has started.

(S)

Starts the queueless cluster process indicated in logical-host-name.

KAVS1864-E
The queueless cluster process (logical-host-name) ended abnormally.: maintenance-information-1 (maintenance-information-2) maintenance-information-3

The queueless cluster process for the logical host (logical-host-name) terminated abnormally.

(S)

Terminates the queueless cluster process indicated in logical-host-name.

(O)

The probable causes of the abnormal termination of the queueless cluster process are:

The logical host name contains more than 255 bytes.

Memory was insufficient during startup of the process.

An attempt to attach the logical host has failed.

An attempt to detach the logical host has failed.

If maintenance-information-2 is invalid hostname, the logical host name contains 256 or more bytes. Set a logical host name that contains 255 or fewer bytes.

If maintenance-information-2 is attach failed or detach failed, an attempt to attach or detach the logical host has failed. Take action according to the instructions given by the message that was output immediately before this message.

If maintenance-information-2 is insufficient memory, memory is insufficient. Take action according to the instructions given by the message that was output immediately before this message.

For other cases, contact the system administrator and collect data (see 1.2.3 To the system administrators).

KAVS1865-E
File transmission is impossible because an attempt to create the process failed.: maintenance-information-1 (maintenance-information-2)

File transmission is impossible because an attempt to create a worker process for queueless file transmission has failed due to too many processes running on the system.

(S)

Cancels execution of the worker process for queueless file transmission.

(O)

The maximum number of processes that can run concurrently on the system might have been exceeded. Use the ps command or another means to check the number of processes running on the system. Make sure that the number of processes are within the maximum, and then re-execute the queueless job indicated in job-name that resulted in the error.

The maximum number of processes specified in the kernel parameter might not suit the current operation. Check the value for the entire system, and then change the value if necessary.

For details about how to estimate the kernel parameters for JP1/AJS3, see 3.2.5 Estimating the values for kernel parameters in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide

KAVS1866-E
The file transmission failed due to insufficient memory.

The file cannot be transmitted because memory became insufficient during transmission.

(S)

Cancels execution of the worker process for queueless file transmission.

(O)

Check the amount of memory available by using Task Manager in Windows or the top command or another means in UNIX.

Wait until the memory necessary for file transfer can be allocated, and then re-execute the queueless job that resulted in the error.

KAVS1867-E
The file transmission service of the host (host-name) cannot be connected, so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed because the queueless file transfer service on the manager host indicated in host-name cannot be connected.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Execute the ping and jp1ping commands to make sure that the agent host can communicate with the manager host indicated in host-name, and that the queueless file transfer service is running on this manager host. Then, re-execute the queueless job that resulted in the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1868-E
The FTP host (host-name) is unknown, so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed because the manager host name indicated in host-name cannot be resolved to the IP address.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

To ensure that the manager host name indicated in host-name can be resolved to the IP address on the agent host, check whether the manager host IP address is set correctly in the hosts and jp1hosts files and the DSN settings. Then, re-execute the queueless job indicated in job-name that resulted in the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1869-E
The FTP server of the host (host-name) cannot be reached, so the job (job-name) cannot be executed.

The queueless job indicated in job-name cannot be executed because communication with the manager host indicated in host-name has failed.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Execute the ping and jp1ping commands to make sure that the agent host can communicate with the manager host indicated in host-name. Then, re-execute the queueless job that resulted in the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1870-E
The file transmission service of the host (host-name) cannot be connected, so an attempt to report the result failed.: job-name

An attempt to report the job execution results failed because the queueless file transfer service on the manager host indicated in host-name could not be connected.

(S)

Places the queueless job indicated in job-name into ended abnormally status.

(O)

Execute the ping and jp1ping commands to make sure that the agent host can communicate with the manager host indicated in host-name, and that the queueless file transfer service is running on this manager host. Then, re-execute the queueless job that resulted in the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1871-E
The manager host (host-name) is unknown, so an attempt to report the result failed.: job-name

An attempt to report the job execution results failed because the manager host indicated in host-name could not be connected due to unsuccessful resolution of the manager host name indicated in host-name to the IP address.

(S)

Places the queueless job indicated in job-name into ended abnormally status.

(O)

To ensure that the manager host name indicated in host-name can be resolved to the IP address on the agent host, check whether the manager host name and IP address are set in the hosts and jp1hosts files or DSN. Then, re-execute the queueless job indicated in job-name that resulted in the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1872-E
The host (host-name) of the manager is unknown, so an attempt to report the result failed.: job-name

An attempt to report the job execution results failed because communication with the manager host indicated in host-name has failed.

(S)

Places the queueless job indicated in job-name into ended abnormally status.

(O)

The manager host IP address set in the hosts or jp1hosts file or DSN might be incorrect. Make sure that the correct IP address is set. In addition, execute the ping and jp1ping commands to make sure that the agent host can communicate with the manager host indicated in host-name. Then, re-execute the queueless job that resulted in the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1873-E
The specified file (file-name) cannot be opened.

The file indicated in file-name cannot be opened.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

The probable causes that prevented the file indicated in file-name from being opened are:

Free disk space is insufficient.

Memory is insufficient.

The file indicated by file-name does not exist.

Access permission that allows the queueless agent service account or the user executing the job to write to or read the directory is not set for the directory in which the file is to be created.

A directory having the same name as the file has already been created in the directory in which the status file is created.

The name of the file indicated by file-name has 255 or more characters.

Make sure that the above conditions are not satisfied, and then re-execute the queueless job that resulted in an error.

KAVS1874-E
You do not have permission for the specified file (file-name)..

An attempt was made to execute a queueless job with the indicated file (file-name) specified, but the queueless agent service account was not allowed to access the file. Alternatively, the specified character string (file-name) was a folder name.

(S)

Places the queueless job into Failed to start status.

(O)

For the specified file (file-name), set an appropriate access permission that allows the queueless agent service account to read or write to the file, and then re-execute the queueless job that resulted in an error.

If a folder name was specified, re-execute the queueless job with a file name specified.

KAVS1875-E
The class name is too long. (class-name) (logical host =logical-host)

The class name indicated in class-name specified in the environment setting parameter for the logical host is too long.

(S)

Continues startup processing of the queueless agent service, or the processing to attach the logical host. However, the class is not registered as a class for which the job is executed.

(O)

Define the class name indicated in class-name that caused the error by using no more than 63 bytes, and then restart the queueless agent service. Alternatively, detach the logical host that caused the error, and then attach it again.

KAVS1876-E
The class (class-name) already exists. (logical host =logical-host)

A class with the same name (class-name) is already set in the environment setting parameter for the logical host indicated in logical-host.

(S)

Continues startup of the queueless agent service.

(O)

Make sure that there is no duplicate class name for the logical host, and then restart the queueless agent service. Even if you do not restart the queueless agent service, however, the class can be used as a class for which the job is executed.

KAVS1877-E
Memory is insufficient, so the class (class-name) cannot be used. (logical host =logical-host)

The class indicated in class-name cannot be used due to insufficient memory.

(S)

Cancels creation of the class and continues startup processing of the queueless agent service, or the processing to attach the logical host.

(O)

Check the amount of memory available by using Task Manager in Windows or the top command or another means in UNIX.

Wait until the memory necessary for using the class can be allocated, and then restart the queueless agent service. Alternatively, detach the logical host that caused the error, and then attach it again.

KAVS1878-E
The class (class-name) cannot be created because a JP1/AJS2 environment setting is incorrect. (logical host=host-name, label=environment-setting-parameter-name)

An attempt to create the class indicated in class-name has failed due to an invalid value of an environment setting parameter in the JP1/AJS3 environment setting.

(S)

Cancels creation of the class and continues startup processing of the queueless agent service or the processing to attach the logical host.

(O)

Correct the value set in the label indicated in environment-setting-parameter-name on the host indicated in logical-host-name. Then, restart the queueless agent service or detach the logical host that caused the error, and then attach it again.

KAVS1879-E
An error occurred in the file (file-name).

An error occurred during processing of the file indicated in file-name.

(S)

Places the queueless job into Failed to start status.

(O)

Possible causes of the error in the file (file-name) are as follows:

Free disk space is insufficient.

Memory is insufficient.

There is no write permission for the directory in which the file is created.

A directory having the same name as the file has already been created in the directory in which the status file is created.

The file name (file-name) has 255 or more characters.

Make sure that the above conditions are not satisfied, and then re-execute the queueless job that resulted in an error.

KAVS1881-E
An error occurred in the check processing of user mapping. (logical host=logical-host-name, function=maintenance-information-1, code=maintenance-information-2)

Processing failed because user mapping was not set up correctly.

(S)

Places the queueless job into Failed to start status.

(O)

An attempt to set up the logical host indicated in logical-host-name might have failed or the environment might have been corrupted. See the integrated trace log to check whether an error messages have been output. If an error message was output, correct the error according to the instructions given by the message, and then restart the queueless agent service and re-execute the queueless job that resulted in the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1882-E
The user mapping definition of the JP1 user (JP1-user-name) on the host (host-name) was not found. (logical host =logical-host-name)

The user mapping definition for the JP1 user indicated in JP1-user-name on the manager host indicated in host-name is not found.

(S)

Places the queueless job into Failed to start status.

(O)

Make sure that the JP1 user indicated in JP1-user-name is defined in the user mapping information for the logical host, and then re-execute the queueless job that resulted in the error.

For details about the user mapping settings, see 3.1.1 Setting up JP1/Base in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (in Windows) or 12.1.1 Setting up JP1/Base in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (in UNIX).

KAVS1883-E
The JP1 user (JP1-user-name) on the host (host-name) cannot be mapped to the OS user (OS-user-name). (logical host =logical-host-name)

The JP1 user indicated in JP1-user-name on the manager host indicated in host-name cannot be mapped to the OS user indicated in OS- user-name.

(S)

Places the queueless job into Failed to start status.

(O)

The OS user indicated in OS-user-name has not been mapped to the JP1 user indicated in JP1-user-name. On the agent host, make sure that the OS user indicated in OS-user-name has been mapped to the JP1 user indicated in JP1-user-name, and then re-execute the queueless job that resulted in the error.

For details about the user mapping settings, see 3.1.1 Setting up JP1/Base in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (in Windows) or 12.1.1 Setting up JP1/Base in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (in UNIX).

KAVS1884-E
The OS user (user-name) was not found in the passwd file.

The OS user who attempted to execute the job was not registered in the passwd file (/etc/passwd).

(S)

Places the queueless job into Failed to start status.

(O)

Make sure that the OS user mapped to the JP1 user exists, and then re-execute the queueless job that resulted in the error.

KAVS1885-E
An attempt to open the file (file-name) failed.: maintenance-information-1 (maintenance-information-2)

An attempt to open the file indicated in file-name has failed.

(S)

If a queueless agent service output this message during startup, the system cancels startup of the service.

If this message is output during startup of a queueless job, the system places the queueless job into Failed to start status.

If this message is output during termination of a queueless job, the system places the queueless job into Ended abnormally status.

(O)

Correct the error as follows, and then restart the queueless agent service or re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, make sure that the directory path specified in the internal file in file-name exists.

If Permission denied is indicated in maintenance-information-1, make sure that read and write permissions for the directory path to the internal file indicated in file-name are set for the user who started the queueless agent service and the OS user who executes the queueless job.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message. Also check the following probable causes, and then correct the error, if any.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1886-E
A socket communication error occurred.: maintenance-information-1 (maintenance-information-2, maintenance-information-3)

An error occurred during socket communication.

(S)

Places the queueless job into Failed to start status if this message is output during execution of a queueless job. If this message is output during execution of the command related to queueless job execution control, the system terminates the command abnormally.

(O)

Take action according to the message output after this message.

KAVS1887-E
Invalid data was received. (IPCID= IP-address)

The system received invalid data from the connection source shown in IP-address.

(S)

Continues processing.

(O)

Determine the connection source from the IP address, and check that the connection source does not have a problem.

KAVS1888-E
An error occurred during the reading of the passwd file.: maintenance-information-1 (maintenance-information-2)

An error occurred during a read from the password file.

(S)

Places the queueless job into Failed to start status.

(O)

Make sure that the OS user who is mapped during execution of the queueless job exists. Also make sure that appropriate permission is set so that the user who started the queueless agent service can read the passwd file (/etc/passwd). Then, re-execute the queueless job that resulted in the error.

KAVS1889-E
An attempt to read the file (file-name) failed.: maintenance-information-1 (maintenance-information-2)

An attempt to read the file indicated in file-name has failed.

(S)

Places the queueless job into Failed to start status.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, the file indicated in file-name does not exist. Make sure that the file indicated in file-name exists.

If Permission denied is indicated in maintenance-information-1, an attempt to read the file indicated in file-name has failed. Set appropriate permissions for the file and directory path so that the user who started the queueless agent service and the mapped OS user can read the file indicated in file-name.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1890-E
An attempt to write to the file (file-name) failed.: maintenance-information-1 (maintenance-information-2)

An attempt to write to the file indicated in file-name has failed.

(S)

Places the queueless job into Ended abnormally status.

(O)

Correct the error as follows, and then re-execute the queueless job that resulted in the error.

If No such file or directory is indicated in maintenance-information-1, make sure that the directory path output to the file indicated in file-name exists.

If Permission denied is indicated in maintenance-information-1, make sure that read and write permissions for the directory path to the file indicated in file-name are set for the user who started the queueless agent service and the OS user who executes the queueless job.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message. Also check the following probable causes, and then correct the error, if any.
- The disk does not have sufficient free space.
- Memory is insufficient.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1891-E
An attempt to open the socket failed.: maintenance-information-1 (maintenance-information-2)

The socket could not be initialized.

(S)

Terminates the service for which this message is output.

(O)

Memory might be insufficient. Check the amount of memory available by using Task Manager in Windows or the top command or another means in UNIX, and then restart the service that could not be started.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1892-E
The shared memory size is invalid. (size=size)

The shared-memory size is invalid.

(S)

Terminates the queueless agent service.

(O)

Take either of the following actions, and then restart the queueless agent service:

Reduce the maximum number of concurrently executable jobs according to the shared memory size that is currently set.

Increase the shared memory size set in the kernel parameter according to the maximum number of concurrently executable jobs.

The maximum number of concurrently executable jobs is set in the AJSQL_JOBMAX environment setting parameter. For details, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

For details about how to estimate the kernel parameters used in JP1/AJS3, see 3.2.5 Estimating the values for kernel parameters in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVS1893-E
Too many shared memories exist on the system.

The queueless agent service cannot use shared memory because the system has used too many segments of shared memory.

(S)

Terminates the queueless agent.

(O)

Calculate the number of shared-memory segments required for the system, and modify the value of the kernel parameter to the appropriate value. Then, restart the queueless agent service.

For details about how to estimate the size of shared memory required for JP1/AJS3 operation, see 3.2.5 Estimating the values for kernel parameters in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVS1894-E
The number of shared memory attaches is invalid.

Shared memory cannot be attached to the queueless agent service.

(S)

Terminates the queueless agent service.

(O)

Set 1 or a greater value for the kernel parameter so that shared memory can be attached to the queueless agent service. Then, restart the queueless agent service.

KAVS1896-E
A log file (file-name) error occurred.: maintenance-information-1 (maintenance-information-2)

An error occurred during processing required to open or write to the log file indicated in file-name,

(S)

If this message is output during startup of a queueless agent service, the system continues startup of the service. However, no log data is output to the log file indicated in file-name.

If this message is output during execution of a queueless job, the system continues queueless job execution. However, no log data about the queueless job is output to the log file indicated in file-name.

(O)

Take one of the following actions:

If No such file or directory is indicated in maintenance-information-1, the log file indicated in file-name might have been deleted. Check whether the log file exists. If it does not exist, restart the queueless agent service.

If Permission denied is indicated in maintenance-information-1, write and read permissions for the log file indicated in file-name might have been changed. Change the permissions so that the user who started the queueless agent service and the OS user who executes the queueless job can read and write to the log file indicated in file-name. Then, restart the queueless agent service.

If any message other than the above is indicated in maintenance-information-1, correct the error according to the message, and then restart the queueless agent service.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1897-E
An attempt to start the job (job-name).

An attempt to start the queueless job indicated in job-name has failed due to an internal error.

(S)

Places the queueless job indicated in job-name into Failed to start status or Ended abnormally status.

(O)

Re-execute the queueless job indicated in job-name that resulted in the error. If an attempt to start the queueless job fails again, restart the queueless agent service, and then re-execute the queueless job indicated in job-name that resulted in the error.

Note that if the the UAC function is enabled in Windows, the OS user who executes the job might not have administrator permissions. Execute the job as the OS user who has administrator permissions.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1898-I
The connection was reset by the peer.

The connection between the queueless agent service and the queueless job request process or between the queueless agent service and the queueless file transfer service was reset.

(S)

Continues processing.

(O)

If the connection was reset due to an error, a message indicating the cause of the error was output before this message. Take action according to the instructions given by that message.

KAVS1900-W
The queueless job request process (scheduler-service-name:identification-number) abnormally ended.: maintenance-information

This message indicates that the queueless job request process ended abnormally.

(S)

Attempts to restart the queueless request process until the abnormal end count reached the threshold. When the threshold is reached, the system blocks the queueless request process.

KAVS1901-I
The queueless job request process (scheduler-service-name:identification-number) was rebooted.

This message indicates that the queueless job request process restarted.

(S)

Restarted the queueless job request process.

KAVS1902-W
An attempt to reboot the queueless job request process (scheduler-service-name:identification-number) failed.: maintenance-information

The system could not restart the queueless job request process. The possible causes include system resources becoming insufficient because more than one queueless job request process was started.

(S)

Terminates the queueless job request process.

(O)

Determine the cause of the failure to restart the queueless job request process according to the messages output before and after this message. Then, take proper action.

KAVS1903-E
The queueless job request process (scheduler-service-name:identification-number) was blocked because the maximum number of abnormally ended queueless job request abends was exceeded.

Since the number of times the queueless job request process ended abnormally exceeded the threshold, the queueless job request process is blocked.

(S)

Blocked the queueless job request process because the threshold value was exceeded.

(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).
We recommend that you first make sure that other jobs have terminated by releasing job restrictions, and then restart the scheduler service.

KAVS1904-E
All the queueless job request processes of the scheduler service (scheduler-service-name) are blocked.

All the queueless job request processes on the scheduler service terminated abnormally. The probable cause is insufficient system resources due to startup of multiple queueless job request processes.

(S)

Stops the scheduler service.

(O)

Examine the cause of the error according to the KAVS1903-E message that was output before this message. Correct the cause of the error, and then restart the scheduler service.

KAVS1905-W
The value specified for the maximum number of queueless job request processes in the environment setting parameter is outside the effective range. The default value (concurrently-executable-job-limit) is assumed and processing is continued.

The value of the QUEUELESSMULTIREQ environment setting parameter is outside the valid range.

(S)

Assumes the value specified in maximum-number-of-concurrently-executable-job-limit, and continues processing.

(O)

Correct the value of the concurrently-executable-job-limit, and then restart the scheduler service. For details on the environment setting parameters, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVS1906-E
Initialization of a queueless job request process failed.: maintenance-information

The system could not initialize a queueless job request process.

(S)

Stops the scheduler service.

(O)

Determine the cause of the failure to initialize the queueless job request process according to the messages output before and after this message. Then, take proper action.

KAVS1907-E
The starting of a queueless job request process failed.: maintenance-information

The system could not start the queueless job request process. The possible causes include system resources becoming insufficient because more than one queueless job request process was started.

(S)

Stops the scheduler service.

(O)

Determine the cause of the failure to start the queueless job request process according to the messages output before and after this message. Then, take proper action.

KAVS1908-W
An attempt to acquire the queueless job function linkage option failed.: maintenance-information

The system could not obtain an environment setting parameter because the queueless job function linkage option specified in the environment setting parameter was invalid or because of some other error.

(S)

Starts the scheduler service without using the queueless job function. A queueless job, if any, executed in this condition ends in the Failed to start state.

(O)

Use the ajsqlsetup command to set up the queueless job function, and then restart the scheduler service.

If the queueless job function has been set up correctly, determine the cause of the error according to the messages output before and after this message. Then, take proper action.

For details on the ajsqlsetup command, see ajsqlsetup in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVS1909-E
The queueless job (job-name) cannot be executed.

The queueless job cannot be executed. The possible causes are:

The queueless job function has not been set up correctly.

The maximum number of concurrently-executable queueless job request processes is set to 0.

(S)

Sets the status of the queueless job to Failed to start.

(O)

Use the ajsqlsetup command to set up the queueless job execution environment, and then restart the scheduler service. If the QUEUELESSMULTIREQ environment setting parameter is set to 0, specify a value in the range from 1 to 8. Then, restart the scheduler service.

For details on the ajsqlsetup command, see ajsqlsetup in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVS1920-E
An error occurred during the starting of the queueless job request process (scheduler-service-name:identification-number).: maintenance-information

An error occurred when the queueless job request process was started.

(S)

Stops the queueless job request process.

(O)

Determine the cause of the failure to start the queueless job request process according to the messages output before and after this message. Then, take proper action.

KAVS1921-E
An attempt to connect with a queueless job execution agent (agent-name) failed.: maintenance-information

The system could not connect to the queueless job execution agent.

(S)

Sets the status of that job to Failed to start if the execution of a queueless job is requested.

If the status of a queueless job is inquired, the system sets the status of that job to Unknown end status.

If an operation on a job is requested, the system invalidates that operation.

(O)

Check that the queueless job execution agent has started correctly, and then re-execute the queueless job.

KAVS1922-W
The connection with the queueless job execution agent (agent-name) was closed.: maintenance-information

The connection to the queueless job execution agent was severed.

(S)

Reconnects the queueless job execution agent.

(O)

Determine the cause of the error according to the messages output by the manager and the agent. Then, take proper actions.

KAVS1923-E
A queueless job function cannot be used, processing to the job (job-name) cannot be performed.

The system cannot use a queueless job function, so it cannot process the job. The possible causes are:

The queueless job function has not been set up correctly.

The maximum number of concurrently-executable queueless job request processes is set to 0.

(S)

Sets the status of the job to Unknown end status.

(O)

Use the ajsqlsetup command to set up the queueless job execution environment, and then restart the scheduler service. If the QUEUELESSMULTIREQ environment setting parameter is set to 0, specify a value in the range from 1 to 8. Then, restart the scheduler service.

For details on the ajsqlsetup command, see ajsqlsetup in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVS1924-E
An attempt to reconnect with a queueless job execution agent (agent-name) failed.: maintenance-information

An attempt to reconnect with a queueless job execution agent has failed.

(S)

Places the job that was running on the relevant queueless job execution agent into Unknown end status status.

(O)

Determine the cause of the error from the messages on the manager and agent, and then take appropriate action.

KAVS1925-E
An attempt to forcibly terminate a queueless job (job-name) failed.

A communication error occurred while a queueless job was being forcibly terminated. Forced termination failed.

(S)

Stops forced termination of the job.

(O)

Retry forced termination of the job.

KAVS1926-E
A class name is specified for the execution destination host name of a Jobnet.

A class name is specified as the target host name of a jobnet.

(S)

Places the job into Failed to start status.

(O)

Remove the class name specified as the target host name, from the jobnet that includes this job.

KAVS1927-E
The queueless job definition is invalid.

The definition of the queueless job is invalid.

(S)

Places the job into Failed to start status.

(O)

Review the job definition.

When macro variables are used, the length of a definition item might exceed the maximum after substitution of macro variables.

Make sure that the lengths of the definition items do not exceed the maximum after substitution, and re-execute the job.

KAVS1928-I
The job at the agent (agent-name) was forcibly terminated.

The running job was forcibly terminated.

(S)

Cancels the requested processing.

KAVS1929-I
The communication with the queueless job execution agent (agent-name) was restored.

Communication with the queueless job execution agent indicated by agent-name has been restored.

(S)

If the message KAVS1922-W was output before this message, you need to check the status of the queueless job that was requested to be executed by the relevant agent. If the message KAVS1930-W was output, re-send the execution, forcible termination, or confirmation request that failed to be sent previously.

KAVS1930-W
Could not connect with the queueless job execution agent (agent-name). Reconnection processing started. : maintenance-information

The queueless job execution agent indicated by agent-name could not be connected, so the re-connection processing started.

If this message is output, the probable causes are:

A network error has occurred (for example, the manager or agent host has not been connected to the LAN).

The agent host name cannot be resolved.

The load for the agent is high, so the connection request cannot be processed.

There was insufficient memory available.

The port number (jplajs2qlag) on the agent for queueless job execution has been set incorrectly.

The queueless job execution agent or the agent host itself has stopped.

(S)

Performs reconnection processing to resend the request for execution, forcible termination, or confirmation, which failed to be sent previously. After this message is output, the system manages the agent as an error agent. The system queues requests to the error agent, and then performs the re-connection processing in the same order as requested.

Although the timeout period for re-connection processing depends on the OS, the maximum period for terminating re-connection processing is specified by the environment setting parameter (REQDAGTRECONNECTTIMEOUT) for which the timeout period of communication recovery processing is set.

The system attempts re-connection twice every 60 seconds, but if the connection cannot be recovered, the system outputs the following error messages in accordance with the processing request, and finally the request is terminated:

Job execution request : KAVS1931-E

Job forcible termination request : KAVS1932-E

Job confirmation request : KAVS1933-E

If reconnection is successful, the system outputs the KAVS1929-I message and then resends the queued requests in sequence to recover from the error.

(O)

Check the logs for the manager host and the agent host, and the network status.

Remove the cause of the connection error.

KAVS1931-E
Could not send the job execution request because an attempt to reconnect with the queueless job execution agent (agent-name) failed. : maintenance-information

Communication with the queueless job execution agent as indicated by agent-name was not recovered, so an attempt to send the job execution request failed.

(S)

Terminates the job execution request, and then sets the job status to Failed to start.

(O)

Check the logs for the manager host and the agent host, and the network status.

Remove the cause of the connection error, and then re-request the job execution if necessary.

KAVS1932-E
Could not forcibly terminate the job (job-name) because an attempt to reconnect with the queueless job execution agent (agent-name) failed. : maintenance-information

Communication with the queueless job execution agent indicated by agent-name has not recovered, so an attempt to request forcible termination of a job has failed.

(S)

Terminates the forcible job termination request.

(O)

Check the logs for the manager host and the agent host, and the network status.

Remove the cause of the connection error, and then re-request the job execution if necessary.

KAVS1933-E
Could not confirm the job status because an attempt to reconnect with the queueless job execution agent (agent-name) failed. : maintenance-information

Communication with the queueless job execution agent indicated by agent-name has not been recovered, so an attempt to check the job status failed.

(S)

Terminates the job status check request, and then sets the job status to Unknown end status.

(O)

Check the logs for the manager host and the agent host, and the network status.

Remove the cause of the connection error, and then re-request the job execution if necessary.

KAVS1939-E
The macro variable (macro-variable-name) has not been inherited.

The macro variable has not been inherited.

(S)

Places the job in the Failed to start status.

(O)

The macro variable name has not been inherited from the preceding job. Recheck the jobnet definition, and then re-execute the job.

KAVS1940-E
An attempt to initialize the job-ID acquisition processing failed.: maintenance-information

An error occurred when the job ID acquisition process was initialized.

(S)

Cancels the initialization of the job ID acquisition process.

(O)

Contact the system administrator, and determine the cause of the error according to maintenance-information. If you cannot determine the cause, collect data (see 1.2.3 To the system administrators).

KAVS1941-E
The user does not have permission to access the job-ID management file. (file-name)

The right permission is not specified for the job ID management file.

(S)

Cancels the initialization of the job ID acquisition process.

(O)

Specify the right permission for the job ID management file. Alternatively, use the ajsqlsetup command to re-create a job ID management file.

For details on the ajsqlsetup command, see ajsqlsetup in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVS1942-E
The job-ID management file (file-name) data is invalid.

The data in the job ID management file is invalid.

(S)

Cancels the initialization of the job ID acquisition process.

(O)

Use the ajsqlsetup command to re-create a job ID management file. Then, restart the scheduler service by a cold start.

For details on the ajsqlsetup command, see ajsqlsetup in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVS1943-E
The job-ID management file (file-name) does not exist.

The job ID management file does not exist.

(S)

Cancels the initialization of the job ID acquisition process.

(O)

Use the ajsqlsetup command to re-create a job ID management file. Then, restart the scheduler service by a cold start.

For details on the ajsqlsetup command, see ajsqlsetup in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVS1952-E
An attempt to acquire the port information of the queueless agent service failed. (service name: service-name)

The system cannot read information about the port to be connected.

(S)

Cancels command execution.

(O)

Define port information correctly, and then re-execute the command.

KAVS1953-E
The status file specified by the queueless agent environment setup cannot be accessed.
An attempt to open or access the status file has failed due to one of the following causes:

The disk does not have sufficient free space.

Memory is insufficient.

The user who started the queueless agent service does not have read permission for the status file.

The user who started the queueless agent service does not have write permission for the directory in which the status file is to be created.

A directory having the same name as the status file has already been created in the directory in which the status file is to be created.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.
(O)

If this message appears during command execution, correct the error and then re-execute the command.

If this message is output for the queueless cluster process, correct the error and then restart the JP1/AJS3 service on the logical host that caused the error.
Example: In this example, the command attaches the logical host Lhost:

Execute the ajsqlattach command as follows:
 
  ajsqlattach -h Lhost
 
For details on the ajsqlattach command, see ajsqlattach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
KAVS1954-E
The number of already registered logical hosts has reached the maximum, so additional registration is not possible.

A new logical host cannot be attached because the number of logical hosts attached to the queueless agent service has reached the maximum, that is, 10.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

(O)

Execute the ajsqldetach command to detach the logical host on which no queueless job is being executed, and then execute the ajsqlattach command to re-attach the logical host that caused the error.

If the logical hosts are attached directly from the queueless cluster process, restart the JP1/AJS3 service on the logical host that caused the error.

Examples:

In this example, the command detaches the logical host Lhost.
Execute the ajsqldetach command as follows:

ajsqldetach -h Lhost

For details on the ajsqldetach command, see ajsqldetach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

In this example, the command attaches the logical host Lhost.
Execute the ajsqldetach command as follows:

ajsqlattach -h Lhost

For details on the ajsqlattach command, see ajsqlattach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVS1955-E
The specified host (host-name)has already been attached.

The specified host indicated in host-name has already been attached.

(S)

Cancels command execution.

(O)

Execute the ajsqlstatus command to check the status of the host indicated in host-name. If the host indicated in host-name has been detached, execute the ajsqlattach command to attach this host.

Examples:

In this example, the command outputs detailed information for the logical host Lhost.
Execute the ajsqlstatus command as follows:

ajsqlstatus -h Lhost

For details on the ajsqlstatus command, see ajsqlstatus in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

In this example, the command attaches the logical host Lhost.
Execute the ajsqlattach command as follows:

ajsqlattach -h Lhost

For details on the ajsqlattach command, see ajsqlattach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVS1956-E
An attempt to read the configuration definition failed.
An attempt to read the environment setting parameter has failed.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.
(O)

Check whether the host name and IP address of the host that executes queueless jobs are registered correctly in the DNS, hosts file, or jp1hosts file. At the same time, make sure that memory is sufficient, and then execute the ajsqlattach command to re-attach the logical host that caused the error. If the logical hosts are attached from the queueless cluster process, restart the JP1/AJS3 service on the logical host that caused the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

Example: In this example, the command attaches the logical host Lhost.

Execute the ajsqlattach command as follows:
 
  ajsqlattach -h Lhost
 
For details on the ajsqlattach command, see ajsqlattach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
KAVS1957-E
The number of simultaneous job executions is invalid.

The maximum number of concurrently executable jobs is invalid.

(S)

Cancels command execution.

(O)

Specify a value in the range from 0 to 1,024 for the maximum number of concurrently executable jobs, and then re-execute the command.

KAVS1958-E
The number of jobs waiting for execution is invalid.

The maximum number of jobs waiting for execution is invalid.

(S)

Cancels command execution.

(O)

Specify a value in the range from 0 to 102,400 for the maximum number of jobs waiting for execution, and then re-execute the command.

KAVS1959-E
An attempt to acquire the port information for file transmission failed. (service name: service-name)

The system cannot read information about the port to be connected.

(S)

Cancels command execution.

(O)

Define port information correctly, and then re-execute the command.

KAVS1960-E
Specify the logical host name when you specify the class name.

A logical-host name and a class name are not specified together.

(S)

Cancels command execution.

(O)

When you specify a logical host name in the command, specify the logical host name and a class name together, and then re-execute the command.

KAVS1961-E
The candidate host (host-name) is not attached.

The specified logical host indicated in host-name is not attached.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

(O)

Make sure that the target host indicated in host-name exists. If the host indicated in host-name does not exist, create it.

KAVS1962-E
The command cannot be executed because the target host (host-name) is being detached.
The command cannot be executed, because the target host indicated in host-name is being detached.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

If the processing to detach the logical host has been canceled, the system abnormally terminates the queueless cluster process.
(O)

If this message is output when the ajsqlattach command is executed, execute the ajsqlstatus command to make sure that the target host indicated in host-name has already been detached. Then re-execute the ajsqlattach command.

If this message is output when the queueless cluster process is being started, execute the ajsqlstatus command to make sure that the target host indicated in host-name has already been detached. Then restart the JP1/AJS3 service on the target host indicated in host-name.

If this message is output when the queueless cluster process is being stopped or when the ajsqldetach command is executed, no action is required.
Example: In this example, the command outputs detailed information for the logical host Lhost.

Execute the ajsqlstatus command as follows:
 
  ajsqlstatus -h Lhost
 
For details on the ajsqlstatus command, see ajsqlstatus in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
KAVS1963-E
A job (job-name) was not executed because the target host (host-name) will be detached.
The queueless job indicated in job-name that is waiting for execution cannot be executed because the attached target host indicated in host-name is being detached.

(S)

Places the queueless job indicated in job-name into Failed to start status.
(O)

Execute the ajsqlattach command to attach the target host indicated in host-name, and then re-execute the queueless job indicated in job-name that is placed into Failed to start status.
Example: In this example, the command attaches the logical host Lhost.

Execute the ajsqlattach command as follows:
 
  ajsqlattach -h Lhost
 
For details on the ajsqlattach command, see ajsqlattach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
KAVS1964-E
A job (job-name) was not executed because queueless agent will now stop.

The queueless job indicated in job-name that is waiting for execution cannot be executed because the queueless agent service will stop.

(S)

Places the queueless job indicated in job-name into Failed to start status.

(O)

Restart the queueless agent service, and then re-execute the queueless job indicated in job-name that is placed into Failed to start status.

KAVS1965-I
The queueless log file (file-name-before-change) has been changed to file-name-after-change.

The queueless log file will be switched to a new queueless log file, because its current size has exceeded the maximum specified in an environment parameter.

(S)

Continues processing.

(O)

If necessary, back up the current queueless log file.

KAVS1966-I
The queueless cluster process (logical-host-name) received a forced termination request from the start daemon.

The queueless cluster process on the logical host (logical-host-name) received a forced termination request from the JP1/AJS3 startup process (jajs_spmd).

(S)

Forcibly terminates the running queuless job on the logical host, and then detaches the logical host indicated in the message. The queueless cluster process stops when the logical host has been detached.

KAVS1967-I
The queueless cluster process (logical-host-name) received a planned termination request from the start daemon.

The queueless cluster process on the logical host (logical-host-name) received a planned termination request from the JP1/AJS3 startup process (jajs_spmd).

(S)

Waits until the running queuless job on the logical host terminates, and then detaches the logical host indicated in the message. The queueless cluster process stops when the logical host has been detached.

KAVS1968-I
The queueless cluster process (logical-host-name) received a restriction stop request from the start daemon.

The queueless cluster process on the logical host (logical-host-name) received a restrictive termination request from the JP1/AJS3 startup process (jajs_spmd).

(S)

Forcibly terminates the running queuless job on the logical host, and then detaches the logical host indicated in the message. The queueless cluster process stops when the logical host has been detached.

KAVS1969-I
The queueless cluster process (logical-host-name) will now stop.

The queueless cluster process on the logical host (logical-host-name) will now terminate.

(S)

Terminates the queueless cluster process indicated in logical-host-name.

KAVS1970-I
The queueless cluster process (logical-host-name) has ended.

The queueless cluster process on the logical host (logical-host-name) has terminated.

(S)

Terminated the queueless cluster process indicated in logical-host-name.

KAVS1971-E
An execution file (file-name) was not found, so the job (job-name) execution was not possible.

The system could not execute the queueless job indicated in job-name because the executable file indicated in file-name was not found.

(S)

Places the queueless job indicated in job-name in the Failed to start status.

(O)

Make sure that the executable file indicated in file-name exists and that the file name has no more than 254 characters, and then re-execute the queueless job (job-name) that failed to start.

KAVS1972-E
The execution file (file-name) was invalid, so the job (job-name) execution was not possible.

The system could not execute the queueless job indicated in job-name because the executable file indicated in file-name was invalid.

(S)

Places the queueless job indicated in job-name in the Failed to start status.

(O)

Make sure that the executable file indicated in file-name can be executed, and then re-execute the queueless job that is placed into Failed to start status.

KAVS1973-E
The resources required for execution are insufficient, so the job (job-name) execution was not possible.

The system could not execute the queueless job indicated in job-name because resources necessary for execution were insufficient.

(S)

Places the queueless job indicated in job-name in the Failed to start status.

(O)

The probable causes of the error in the queueless job indicated in job-name are:

Memory was insufficient.

The disk did not have sufficient free space.

The size of the desk top heap was insufficient.

Correct the cause of the error, and then re-execute the queueless job that is placed into Failed to start status.

KAVS1974-E
The job (job-name) could not be executed because the user does not have the required permission for execution.

The system could not execute the queueless job indicated in job-name because the account of the queueless agent service did not have permissions required for executing the queueless job.

(S)

Places the queueless job indicated in job-name in the Failed to start status.

(O)

Specify permissions required for executing the job in the account of the queueless agent service, and then re-execute the queueless job that is placed into Failed to start status.

For details about permissions that must be set for the account, see 4.2.3 Changing the JP1/AJS3 service settings (Windows only) in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

KAVS1975-E
The disk capacity was insufficient, so a job (job-name) could not be performed. : maintenance-information

The system could not execute the queueless job indicated in job-name because the required disk space was not available.

(S)

Places the queueless job indicated in job-name in the Failed to start status.

(O)

Allocate sufficient free space on the disk, and then re-execute the queueless job indicated in job-name that is placed into Failed to start status.

KAVS1976-E
No right is granted to access the execution file (file-name).

The queueless job could not be executed because the OS user who executed the queueless job indicated in job-name did not have access permission for the executable file indicated in file-name.

(S)

Places the queueless job in the Failed to start status.

(O)

Make sure that the OS user who executes the queueless job has read and execution permissions for the executable file indicated in file-name, and then re-execute the queueless job that is placed into Failed to start status.

KAVS1977-E
No free space is available on the disk.: (maintenance-information-1) (maintenance-information-2)

The directory or file indicated in maintenance-information-1 cannot be created due to insufficient free space on the disk.

(S)

Does not create a directory or file indicated in maintenance-information-1.

(O)

Check the space available on the disk, and then re-execute the processing that caused the error.

KAVS1978-E
The forced termination of a job(job-name) failed. (process-ID) (maintenance-information-1)

An attempt to forcibly terminate or cancel the queueless job indicated in job-name has failed

(S)

Continues processing.

(O)

Retry forced termination of the queueless job indicated in job-name. If the forced termination fails again, manually terminate the queueless job indicated in job-name by using Task Manager in Windows or the kill command or another means in UNIX from the process-ID.

KAVS1979-E
The job is of a format that the destination execution host (host-name) cannot accept.

Since an attempt was made to execute a PC job on a UNIX host or execute a UNIX job on a Windows host, the attempt to execute the job on the agent host indicated in host-name has failed.

(S)

Places the queueless job in the Failed to start status.

(O)

As the host on which the job is to be executed, specify a Windows host for a PC job or specify a UNIX host for a UNIX job. Then, re-execute the queueless job that resulted in the error.

KAVS1980-I
The detach processing for the logical host (host-name) has been changed from planned detach to forced detach.

The detach processing for the logical host indicated in host-name has been changed from planned detach to forced detach.

(S)

Performs forced detach processing.

KAVS1981-I
The logical host (host-name) was attached.

The system accepted a request from the ajsqlattach command or queueless cluster process and attached the logical host indicated in host-name.

(S)

Enables the queueless job to be executed on the logical host indicated in host-name.

KAVS1982-I
The logical host (host-name) was detached.

The system accepted a request from the ajsqldetach command or queueless cluster process and detached the logical host indicated in host-name.

(S)

Prevents the queueless job from being executed on the logical host indicated in host-name.

KAVS1983-I
The execution environment settings are (execution-environment, Number of simultaneously executable jobs=number-of-simultaneously-executable-jobs, Number of jobs waiting for execution=number-of-jobs-waiting-for-execution).

The system accepted a request from the ajsqlalter command and updated the environment for the host indicated in host-name.

(S)

Updates the environment for the host indicated in host-name. If the maximum number of concurrently executable jobs and the maximum number of jobs waiting for execution remain unchanged, the system outputs the values specified before the changes were made.

KAVS1984-I
maintenance-information

A request for submitting a queueless job was accepted. For details about maintenance information, see C.2 Log entries output by the queueless agent service in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

(S)

Continues processing.

KAVS1985-E
The setup of the queueless job execution environment could not be updated.: maintenance-information-1 maintenance-information-2 maintenance-information-3

The system could not update the settings of the queueless job execution environment because the ajsqlsetup command could not be executed.

(S)

Cancels command execution.

(O)

If the ajsqlsetup command is executed in the terminal service environment that is running in application execution mode, an error occurs and this message is output. Execute the ajsqlsetup command in the following procedure:

Open the command prompt and execute the change user command with the /query option specified.
Check the execution result to make sure that the current execution mode is application execution mode.

Execute the change user command with the /install option specified to change the execution mode to application installation mode.

Execute the ajsqlsetup command.

Execute the change user command with the /execute option specified to return the execution mode to application execution mode.

For details on the change user command, see Windows Help.

For other cases, the cause of the error might be insufficient memory or insufficient disk space. Correct the error and then re-execute the ajsqlsetup command.

If you cannot correct the problem, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

For details on the ajsqlsetup command, see ajsqlsetup in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVS1986-E
Access permission for the services file is not granted, so the port information cannot be registered.

Setup of the queueless agent service is canceled because you did not have permission to write to the services file and could not register port information.

(S)

Cancels command execution.

(O)

Check whether the OS user who executed the command has logged on as a member of the Administrators group (in Windows) or has superuser privileges (in UNIX), and has write permission for the services file. Then re-execute the command.

KAVS1987-I
The service (service-name) stopped.

This message indicates that the system will stop the service indicated in service-name.

(S)

Stops the service indicated in service-name.

KAVS1988-E
The specified class name (class-name) does not exist.

The specified class name indicated in class-name does not exist.

(S)

Cancels command execution.

(O)

Specify an existing class name, and then execute the command.

KAVS1989-E
The operation is not possible because the service (service-name) is not running.

The service indicated in service-name has not started, so command operation cannot be performed.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

If the processing to detach the logical host has been canceled, the system abnormally terminates the queueless cluster process.

(O)

Check that the service has started, and then execute the command.

If the service has started, wait a while and then retry the operation. If the retry does not correct the error, contact the system administrator and collect data (see 1.2.3 To the system administrators).

You can use either of the following methods to check whether the service has started:

In Windows:

In Control Panel or Administrative Tools, double-click Services, and check the status of the service.

In UNIX:

Use the ps command to make sure that the service for the process exists.

For details about the process that you should check, see B.3 Processes (for UNIX) in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

If this message is output when the queueless cluster process is being started, wait until the service has started, and then take either of the following actions to attach the logical host:

Restart the JP1/AJS3 service.

Use the ajsqlattach command to attach the logical host.

If this message is output when the queueless cluster process is being stopped, no action is necessary because the service has already stopped.

KAVS1990-E
An error occurred during the communication with the service (service-name) because a network access error occurred.: maintenance-information

A network access error occurred during communication with the service indicated in service-name.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

If the processing to detach the logical host has been canceled, the system abnormally terminates the queueless cluster process.

(O)

Execute the ping and jp1ping commands to make sure that communication with the service indicated in service-name is possible. If communication is impossible, make sure that the host name and IP address of the host that executes queueless jobs are registered correctly in the DNS, hosts file, or jp1hosts file.

After taking the above actions, re-execute the command that resulted in the error. If the error occurred when the queueless cluster process was being started, restart the JP1/AJS3 service.

If the error occurred when the queueless cluster process was being stopped, execute the ajsqldetach command to detach the logical host that caused the error.

If you cannot correct the problem, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1991-E
A communication timeout occurred during the communication with the service (service-name).: maintenance-information

A communication timeout error occurred during communication with the service indicated in service-name.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

If the processing to detach the logical host has been canceled, the system abnormally terminates the queueless cluster process.

(O)

A timeout might have occurred due to high load on the network or machine. Use Task Manager in Windows or the top command or another means in UNIX to check the status of the network and machine. Then re-execute the command that resulted in the error.

If the error occurred when the queueless cluster process was being started, restart the JP1/AJS3 service.

If the error occurred when the queueless cluster process was being stopped, execute the ajsqldetach command to detach the logical host that caused the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1992-E
The connection was reset during the communication with the service (service-name).: maintenance-information

The connection was reset during communication with the service.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

If the processing to detach the logical host has been canceled, the system abnormally terminates the queueless cluster process.

(O)

The connection might have been disconnected due to a network failure. Execute the ping and jp1ping commands to make sure that communication with the service indicated in service-name is possible. If the connection is impossible, check the communication environment to correct the cause of the error. Then, re-execute the command that resulted in the error.

If the error occurred when the queueless cluster process was being started, restart the JP1/AJS3 service.

If the error occurred when the queueless cluster process was being stopped, execute the ajsqldetach command to detach the logical host that caused the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1993-E
A buffer shortage occurred during the communication with the service (service-name).: maintenance-information

The available buffer became insufficient during communication with the service.

(S)

Cancels command execution.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

If the processing to detach the logical host has been canceled, the system abnormally terminates the queueless cluster process.

(O)

The probable causes of the error include high load on the network and insufficient memory. Check the status of the network and memory, and then re-execute the command that resulted in the error.

If the error occurred when the queueless cluster process was being started, restart the JP1/AJS3 service.

If the error occurred when the queueless cluster process was being stopped, execute the ajsqldetach command to detach the logical host that caused the error.

If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS1994-E
Database file install directory is invalid.: (directory-name) (return-code)

The directory path specified in AJSDBDIRECTORY is incorrect. Alternatively, if the primary node of a cluster is being set up, the shared disk may have not been mounted.

(S)

Cancels command execution.

(O)

Check the directory path specified in AJSDBDIRECTORY. If this message appears during setup of the primary node of a cluster, check whether the shared disk has been mounted.

After completing the above checks, re-execute the setup command.

KAVS1995-E
The command ended because an attempt to get the detailed information of the queueless agent service failed.

The command ended, because an attempt to acquire the detailed information for the queueless agent service has failed.

(S)

Cancels command execution.

(O)

Resolve the problem, following the instructions given in the message that was output before this one. Then, re-execute the command.

KAVS1996-I
The system has been switched from planned detach to forced detach, and the target host (host-name) has been detached. The command will now end.

The command will terminate because the detach mode has changed from planned detach to forced detach and the target host (host-name) has been detached.

(S)

Terminates the command.

KAVS1997-E
No authority for file(file-name).

The OS user who executed the command does not have permission to read or write the file indicated in file-name.

(S)

Cancels command execution.

(O)

Assign read or write permission for the file indicated in file-name to the OS user who executed the command, and then re-execute the command.

KAVS1998-E
The command cannot be executed because the processing is restricted.
One of the following services is being stopped, so the system cancels the command:

Queueless agent service

Queueless file transfer service

Check manager service

Check agent service

(S)

Cancels the command.

For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.

If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter.

For details about AJSQL_CLUSTERREQ, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

If the processing to detach the logical host has been canceled, the system abnormally terminates the queueless cluster process.
(O)

Restart the service, and then re-execute the command.

If this message is output when the queueless cluster process is being started, execute the ajsqlstatus command to make sure that the target host indicated in host-name has stopped, and then restart the JP1/AJS3 service on the target host indicated in host-name.

If this message is output when the queueless cluster process is being stopped or when the ajsqldetach command is executed, no action is required.
Example: In this example, the command outputs detailed information for the logical host Lhost.

Execute the ajsqlstatus command as follows:
 
  ajsqlstatus -h Lhost
 
For details on the ajsqlstatus command, see ajsqlstatus in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
KAVS2030-I
Scheduler service (logical-host-name:scheduler-service-name) export started.

Export of the scheduler service will now start.

(S)

Continues processing.

KAVS2031-I
Scheduler service (logical-host-name:scheduler-service-name) export ended normally.

Export of the scheduler service terminated normally.

(S)

Continues processing.

KAVS2032-E
Scheduler service (logical-host-name:scheduler-service-name) export ended abnormally. maintenance-information

Export of the scheduler service terminated abnormally.

(S)

Cancels processing.

(O)

Take action according to the message that was output before or after this error message.

KAVS2033-I
Scheduler service (logical-host-name : scheduler-service-name) import started.

Import of the scheduler service will now start.

(S)

Continues processing.

KAVS2034-I
Scheduler service (logical-host-name : scheduler-service-name) import ended normally.

Import of the scheduler service terminated normally.

(S)

Continues processing.

KAVS2035-W
Scheduler service (logical-host-name : scheduler-service-name) import ended with warning. maintenance-information

Import of the scheduler service terminated with warning.

(S)

Continues processing even though some information cannot be transferred.

(O)

Take action according to the message that was output before or after this error message.

KAVS2036-E
Scheduler service (logical-host-name : scheduler-service-name) import ended abnormally. maintenance-information

Import of the scheduler service terminated abnormally.

(S)

Cancels processing.

(O)

Take action according to the message that was output before or after this error message.

KAVS2037-I
Table (table-name) export started.

Export of the table will now start.

(S)

Continues processing.

KAVS2038-I
Table (table-name) export ended.

Export of the table terminated.

(S)

Continues processing.

KAVS2039-I
Table (table-name) import started.

Import of the table will now start.

(S)

Continues processing.

KAVS2040-I
Table (table-name) import ended.

Import of the table terminated.

(S)

Continues processing.

KAVS2041-E
Environment setting parameters could not be obtained. maintenance-information

The environment setting parameters cannot be obtained.

(S)

Cancels processing.

(O)

Correct the error in the environment settings according to the message that was output before or after this error message, and then re-execute the command.

KAVS2045-I
number-of-items items were exported.

Export of the number of items indicated in number-of-items is completed.

(S)

Continues processing.

KAVS2046-I
number-of-processed-items out of total-number-of-items items were imported.

Export of the number of items indicated in number-of-items-processed in total-number-of-items is completed.

(S)

Continues processing.

KAVS2101-E
Embedded service is inactive.

The embedded database is not running.

(S)

Cancels command execution.

(O)

Make sure that the embedded database has started. Execute the ajsembdbstatus -s ust command to check the status of the embedded database.

KAVS2102-E
Starting/terminating the embedded service.

The embedded database is being started or stopped.

(S)

Cancels command execution.

(O)

Check the start or stop status of the embedded database. Execute the ajsembdbstatus -s ust command to check the status of the embedded database.

KAVS2103-E
Embedded service is active.

The embedded database is running.

(S)

Cancels command execution.

(O)

Make sure that the embedded database has stopped. Execute the ajsembdbstatus -s ust command to check the status of the embedded database.

KAVS2104-E
Embedded service is not set up.

The embedded database has not been set up. Either the embedded database has not been set as the scheduler service database, or the setup ID specified in -id is invalid.

(S)

Cancels command execution.

(O)

Check whether the value of the setup ID specified in -id is correct. Alternatively, use the ajsstatus command to check whether the embedded database has been set as the scheduler service database.

KAVS2105-E
Specified file group (log-file-group-name) does not exist.

The specified log file group does not exist. The log file group name specified in the -g option of the ajsembdboplog command is incorrect.

(S)

Cancels command execution.

(O)

Recheck the specified log file group.

KAVS2106-E
Failed to unload.

An unloading attempt failed. The log file group specified in the ajsembdboplog -g command is being used. Alternatively, the directory specified in the ajsembdbrorg -d command does not have sufficient free space.

(S)

Cancels command execution.

(O)

Execute the ajsembdbstatus -s prc command to make sure that the command you executed has stopped, and then retry.

If the ajsembdboplog command is being executed, use the ajsembdbstatus -l command to make sure that the specified log file group is not being used.

If the ajsembdbrorg command is being executed, check the amount of free space in the directory specified in -d.

KAVS2107-E
Failed to reload.

A reloading attempt failed. This message appears when the embedded database does not have sufficient space during execution of the ajsembdbrorg -k reld command.

(S)

Cancels command execution.

(O)

Execute the ajsembdbstatus -s prc command to make sure that the command you executed has stopped, and then retry.

When unloaded data is reloaded, the embedded database allocates the space required for the operation, sometimes resulting in a shortage of free space in the area that was used before unloading. If this problem occurs, execute the ajsembdbreclaim command to reclaim area that has become invalid, and then re-execute the command. If the ajsembdbreclaim command is unable to reclaim enough area, you must add area.

KAVS2108-E
Invalid Embedded service definition.

The environment of the embedded database does not permit execution of the command. To execute the ajsembdboplog -r -t command, ajsembdbbuild -bl must have been specified for this environment.

(S)

Cancels command execution.

(O)

Check the environment of the embedded database on which you want to execute the command. If ajsembdbbuild -bl was not specified when the environment was created, consider creating the environment of the embedded database again.

KAVS2109-E
Specified file (file-name) exists.

An attempt to create a file has failed. This message appears when an existing file is specified in the -o option of the ajsembdboplog command.

(S)

Cancels command execution.

(O)

Either change the specified file name or delete the existing file, and then re-execute the command.

KAVS2113-E
Failed to read the configuration definition.

An attempt to read the configuration definition has failed. The configuration definition required for operation of the embedded database has not been set. This message appears when the embedded practical directory for the scheduler database cannot be acquired during execution of a data collection tool.

(S)

Cancels command execution.

(O)

Use the ajsstatus command to check whether the embedded database is set as the scheduler service database. If the embedded database is set as the scheduler service database, check whether the setup ID has been set. If the setup ID is not set correctly, use the jbssetcnf command to set it.

KAVS2114-E
Cannot create directory or file (directory-name or file-name).

An attempt to create a directory or file has failed because you do not have permissions for the directory. This message appears when you do not have permissions for the following directories during execution of a data collection tool:

In Windows:

%TEMP%\jp1ajs2\backlog

In UNIX:

/tmp/jp1ajs2/trouble/

(S)

Cancels command execution.

(O)

Assign permissions on the specified directory, and then retry.

KAVS2115-E
Embedded service is not installed.

The embedded database is not installed. The embedded database registered with the setup ID specified in -id might have been uninstalled. Alternatively, the environment might have been deleted.

(S)

Cancels command execution.

(O)

Check the environment of the embedded database registered with -id. If the embedded database has been uninstalled, install the embedded database and set it up. After setup, re-set the embedded database as the scheduler service database.

If the environment of the embedded database has been deleted, set up the embedded database and then re-set the embedded database as the scheduler service database.

KAVS2116-E
There is an error in the specified option.
detailed-information
USAGE

The specified option contains an error.

One of the following is indicated in detailed-information:

Options (option) are needed.
The mandatory or necessary option was not found.

Illegal option (option) exists.
An invalid option is specified.

Extra option (option) exist.
An extra option is specified.

Invalid value for option (option).
The value of the option is invalid.
If -F is indicated in (option), the logical host specified for the -mh option might be invalid. If either or both of -F or -mh is not specified, check the following:
- If -F is not specified, check the AJSCONF environment variable or the DEFAULTSERVICENAME environment setting parameter.
- If -mh is not specified, check the JP1_HOSTNAME environment variable.

Value of option (option) exceeds prescribed length.
The value of the option exceeds the prescribed length.

Value of option (option) is not specified.
The value of the option is not specified.

Option (option) appears twice or more.
The option indicated in option is specified more than once.

No unload file.
There is no unload file.

Cannot specify these options (option) together.
Options that cannot be specified together are specified.

(S)

Cancels command execution.

(O)

Check the option and then retry.

KAVS2117-E
An error has occurred in the command-name command. maintenance-information

An error occurred during execution of the command.

(S)

Cancels command execution.

(O)

See the message output in the maintenance information.

KAVS2118-Q
Could not stop the embedded service. Continue process? (y/n)

This message asks you whether you want to continue the processing. If you continue the processing while the embedded database is not stopped, an error occurs and the processing is canceled.

(S)

Waits for a response.

(O)

Execute the ajsembdbstatus -s command to check the status of the embedded database. Make sure that the embedded database has stopped, and then enter y to continue the processing. To cancel the processing, enter n.

If you enter anything other than y or n, the processing is canceled as if you had entered n.

KAVS2119-E
Specified directory (directory-name) does not exist.

The directory part of the output destination file name specified in the -o option of the ajsembdboplog command contains an error.

(S)

Cancels command execution.

(O)

Check and, if necessary, correct the output destination file name (full path specification) specified in the -o option, and then re-execute the command.

KAVS2120-E
A log group cannot add.

A log file group cannot be added because the number of log file groups created will exceed the maximum. For details on the maximum number of log file groups that can be created, see ajsembdbaddlog in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

(S)

Cancels command execution.

(O)

Check the number of log files.

KAVS2121-E
Database file already exists.

The file name of the file for the database area you attempted to create already exists. The file name already exists in the directory specified in the -d option of the ajsembdbaddlog or ajsembdbaddarea command.

(S)

Cancels command execution.

(O)

Re-execute the command.

KAVS2122-E
A temporary file already exists.

A temporary file that has the same name as the file that you attempted to create by using the embedded database operation command already exists.

(S)

Cancels command execution.

(O)

Re-execute the command.

KAVS2123-E
Embedded DB version is invalid.

The version of the embedded database must be a prerequisite version for JP1/AJS3.

(S)

Cancels command execution.

(O)

Upgrade the version of the embedded database to a prerequisite version for JP1/AJS3.

KAVS2124-E
Failed in construction of EmbedDB server.

An attempt to construct an embedded database server has failed.

(S)

Cancels command execution.

(O)

Take action according to the instructions given by the message that was output before this message. Then execute the ajsembdbunset command with the -i option specified to delete the environment of the embedded database, and then execute the ajsembdbbuild command. For details about the error messages and the applicable actions, see Actions to be taken if an error occurs in the ajsembdbbuild in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

KAVS2125-E
Cannot create directory or file.

The directory or file cannot be created because, for example, you do not have access permission for the embedded database practical directory.

(S)

Cancels command execution.

(O)

Check whether you have write permission for the embedded database practical directory. Also check whether the disk has sufficient free space.

KAVS2126-E
Embedded setup environment already exists.

The specified embedded database practical directory has already been associated with another setup ID.

(S)

Cancels command execution.

(O)

Make sure that the specified embedded database practical directory is associated correctly.

Use the ajsembdbidlist command to check the association between the embedded database practical directory and the setup ID.

KAVS2127-E
An error has occurred in the command (command-name). : maintenance-information

An error occurred in the command for the embedded database.

(S)

Terminates processing.

(O)

If an attempt to install JP1/AJS3 has failed, take appropriate action for the code and message indicated in maintenance-information according to the 2.8.8(4) Action to be taken if an error occurs during embedded database setup in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

This message is also output to the Windows event log or syslog if execution of the ajsembdbbuild command has failed. In this case, take appropriate action for the message output to the standard output according to the action to be taken when an error occurs in the ajsembdbbuild command.

KAVS2128-E
Failed to set up embedded service. : func code=function-code error code=error-code
An attempt to set up the embedded database has failed.

(S)

Terminates processing.
(O)

If an attempt to install JP1/AJS3 has failed, take the following action, and then uninstall JP1/AJS3 and install it again.

If an attempt to uninstall JP1/AJS3 has failed, take the following action, and then uninstall JP1/AJS3 again.

If this message containing the same function code appears repeatedly, back up the following directory below the JP1/AJS3 installation directory, and then contact the system administrator:

Action

For func code=1:

If the KAVS2127-E message was output before this message, take action according to the instructions given by the KAVS2127-E message.

If the KAVS2127-E message was not output, uninstall JP1/AJS3 and then install it again.

For func code=2:

Review the environment where JP1/AJS3 is to be installed.

Make sure that there is sufficient memory and disk space.

For func code=3:

Take action according to the instructions given by the KAVS2127-E message that was output before this message.

For func code=4:

Review the environment where JP1/AJS3 is to be installed.

Make sure that there is sufficient memory and disk space.
For func code=5:

Information about the embedded database that has already been uninstalled might remain in the JP1/AJS3 common definition information. Execute all the following commands to delete the common definition information:
 
jbsunsetcnf -i -h JP1_DEFAULT -c JP1AJS2 -n EMBDBINSTALL
jbsunsetcnf -i -h JP1_DEFAULT -c JP1AJS2 -n EMBDB
jbsunsetcnf -i -h JP1_DEFAULT -c JP1AJS2 -n EMBDBPORT
 
For details on the jbsunsetcnf command, see the Job Management Partner 1/Base User's Guide.
For func code=6:

Take action for the output error code according to 2.8.9(1) Action to be taken if a JP1/AJS3 - Manager installation error occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

For func code=7:

Take action for the output error code according to 2.8.9(2) Action to be taken if a JP1/AJS3 - Manager uninstallation error occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

Note that this message is also output to the Windows event log or syslog if execution of the following commands has failed:

jajs_setup command

jajs_setup_cluster command

ajsembdbuninstl command

In this case, take appropriate action for the message output to the standard output according to the action to be taken when an error occurs in each command.
KAVS3400-I
An error occurred while adding the JP1/AJS2 Check Manager service. : code=return-value api=API-name err=API-return-value

An error occurred while the JP1/AJS3 Check Manager service was being added.

(S)

Terminates setup processing.

(O)

Memory or free space on the disk may be insufficient. Terminate unnecessary applications or delete unnecessary files to make more free space available. Then re-execute the setup command.

KAVS3401-I
An error occurred while deleting the JP1/AJS2 Check Manager service. : code=return-value api=API-name err=API-return-value

An error occurred while the JP1/AJS3 Check Manager service was being deleted.

(S)

Terminates setup processing.

(O)

Memory or free space on the disk may be insufficient. Terminate unnecessary applications or delete unnecessary files to make more free space available. Then re-execute the setup command.

KAVS3402-I
The JP1/AJS2 Check Manager service will now start.

JP1/AJS3 Check Manager service will now start.

(S)

Continues processing.

KAVS3403-I
The JP1/AJS2 Check Manager service will now stop.

The JP1/AJS3 Check Manager service will now stop.

(S)

Stops the JP1/AJS3 Check Manager service.

KAVS3404-I
An error occurred while adding the JP1/AJS2 Check Agent service. : code=return-value api=API-name err=API-return-value

An error occurred while the JP1/AJS3 Check Agent service was being added.

(S)

Terminates setup processing.

(O)

Memory or free space on the disk may be insufficient. Terminate unnecessary applications or delete unnecessary files to make more free space available. Then re-execute the setup command.

KAVS3405-I
An error occurred while deleting the JP1/AJS2 Check Agent service. : code=return-value api=API-name err=API-return-value

An error occurred while the JP1/AJS3 Check Agent service was being deleted.

(S)

Terminates setup processing.

(O)

Memory or free space on the disk may be insufficient. Terminate unnecessary applications or delete unnecessary files to make more free space available. Then re-execute the setup command.

KAVS3406-I
The JP1/AJS2 Check Agent service will now start.

The JP1/AJS3 Check Agent service will now start.

(S)

Continues processing.

KAVS3407-I
The JP1/AJS2 Check Agent service will now stop.

The JP1/AJS3 Check Agent service will now stop.

(S)

Stops the JP1/AJS3 Check Agent service.

KAVS3408-I
The function for pre-checking definitions is not enabled.

Operation is impossible because the definition pre-check function is not enabled in JP1/AJS3 - Manager.

(S)

Cancels processing.

(O)

Enable the definition pre-check function in JP1/AJS3 - Manager.

KAVS3409-I
An attempt to connect to the Check Agent service (agent-name) has failed. : maintenance-information

An attempt to connect the check agent service has failed.

(S)

Assumes the pre-checking of definitions for the agent to be an error, and continues processing for other check agent services.

(O)

Make sure that the check agent service has started normally on the agent where the error occurred, and then pre-check the definitions again.

KAVS3410-I
The connection with the check agent service (agent-name) was closed. : maintenance-information

The connection with the check agent service was closed.

(S)

Assumes the pre-checking of definitions for the agent to be an error, and continues processing for other check agent services.

(O)

Examine the cause of the error according to the messages on the manager and on the agent, take corrective action, and then pre-check the definitions again.

KAVS3411-I
Definitions are being pre-checked elsewhere, so execution is not possible.

Execution is impossible because definitions are being pre-checked elsewhere.

(S)

Terminates processing.

(O)

Wait until the pre-checking of definitions being performed elsewhere terminates, and then re-execute the command.

KAVS3412-I
The host name, scheduler service name, or execution ID cannot be specified for the unit name. : unit-name

You cannot specify a host name, scheduler service name, or execution ID as a unit name.

(S)

Terminates processing.

(O)

Delete the specified host name, scheduler service name, and execution ID, and then re-execute the command.

KAVS3413-I
An attempt to connect to the check manager service has failed. : maintenance-information

An attempt to connect to the check manager service has failed.

(S)

Cancels execution of the command.

(O)

Make sure the check manager service is running normally, and then pre-check the definitions again.

KAVS3414-I
The Check Agent ended abnormally.

The check agent service terminated abnormally.

(S)

Terminates the check agent service.

(O)

Take action according to the instructions given by the message that was output immediately before this message.

KAVS3415-I
JP1/AJS2 Check Agent will now terminate.

A request to forcibly terminate the ajschkstop command was accepted.

(S)

Terminates the check agent service.

KAVS3416-I
The configuration definition of the logical host (logical-host-name) does not exist.

The environment for the logical host indicated in logical-host-name has not been set up.

(S)

Continues processing if the error occurred during startup of a check agent service. However, the logical host is not handled as the host where the job was executed. The system cancels processing if the error occurred during execution of a command.

(O)

Set up the environment for the logical host indicated in logical-host-name, and then restart the check agent service. If the error occurred during execution of a command, make sure that the correct logical host name is specified in the argument.

KAVS3417-I
An error occurred during an attempt to acquire the configuration definition of the logical host (logical-host). (function=maintenance-information-1, code=maintenance-information-2)

An attempt to acquire the value of the environment setting parameter for the logical host indicated in logical-host-name has failed.

(S)

Continues processing if the error occurred during startup of a check agent service. However, the logical host is not handled as the host where the job was executed. The system cancels processing if the error occurred during execution of a command.

(O)

Make sure that the correct value is set in the environment setting parameter for the logical host indicated in logical-host, and then restart the check agent service. If the error occurred during execution of a command, make sure that the correct logical host name is specified in the argument.

KAVS3418-I
Memory is insufficient, so the job (job-name) cannot be accepted.

The job cannot be accepted due to insufficient memory.

(S)

Cancels checking of the job.

(O)

Wait until the required amount of memory for checking the job becomes available, and then pre-check the definitions again.

KAVS3419-I
An iconv_open error occurred, so character conversion is not possible. : maintenance-information-1 (maintenance-information-2)

The character set will not be converted because the preparation for conversion has failed.

(S)

Continues processing.

(O)

To convert the character set, check the settings of the character set and then restart the check agent.

KAVS3420-I
Too many processes exist, so the job (job-name) cannot be checked.

The job indicated in job-name cannot be checked because there are too many processes.

(S)

Cancels checking of the job.

(O)

Wait until the number of processes decreases so that the check is available, and then pre-check the definitions again.

KAVS3421-I
The shared memory size is invalid. (size=size)

The size of shared memory is invalid.

(S)

Terminates the check agent service.

(O)

Recheck the settings of the semaphores and shared memory, and then pre-check the definitions again.

KAVS3422-I
Too many shared memories exist on the system.

The system has too many units of shared memory.

(S)

Terminates the check agent.

(O)

Contact the system administrator. The number of shared memory identifiers exceeded the maximum defined by the system. Recheck the kernel parameters, and then re-execute the command.

KAVS3423-I
The number of shared memory attaches is invalid.

The number of shared memory attaches is invalid.

(S)

Terminates the check agent.

(O)

Contact the system administrator. The number of shared memory segments attached to the process exceeded the maximum defined by the system. Recheck the kernel parameters, and then re-execute the command.

KAVS3424-I
The setup of the function for pre-checking definitions execution environment could not be updated. : maintenance-information-1 maintenance-information-2 maintenance-information-3

The execution environment settings for the definition pre-check function could not be updated because the ajschksetup command failed.

(S)

Cancels execution of the command.

(O)

The setup environment may be invalid. Make sure that the setup of JP1/AJS3 has been completed normally, and then re-execute the command.

KAVS3425-I
An attempt to acquire port information of the check agent service has failed. (service name: service-name)

Port information of the port to be connected cannot be read.

(S)

Cancels execution of the command.

(O)

Define port information correctly, and then re-execute the command.

KAVS3426-I
The function for pre-checking definitions log file (file-name-before-change) has been changed to file-name-after-change.

Since the size of the definition check log file exceeds the value specified in the environment setting parameter, the definition check log file will be replaced with another.

(S)

Continues processing.

(O)

As required, back up the definition check log file.

KAVS3427-I
JP1/AJS2 Check Manager will now terminate.

The check manager service terminated abnormally.

(S)

Terminates the check manager service.

(O)

Take action according to the instructions given by the message that was output immediately before this message. If a message beginning with KAVS34 that indicates the cause of the error was not output immediately before this message, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).

KAVS3428-I
Failed in the request transmission of the definition check function in JP1/AJS2 Check Agent(agent-name). :maintenance-information

An attempt to issue a request for pre-checking definitions made to the JP1/AJS3 Check Agent indicated in agent-name has failed.

(S)

Assumes the pre-checking of definitions for the agent to be an error, and continues processing for other check agent services.

(O)

Make sure that the check agent service has started normally on the agent host where the error occurred, and then pre-check the definitions again.

KAVS3429-I
The connection with JP1/AJS2 Check Agent(agent-name) is disconnected because there is no response from JP1/AJS2 Check Agent(agent-name).(time)

No response was sent from the check agent for the period of time indicated in time (unit: seconds). The connection with the check agent indicated in agent-name will be released.

(S)

Assumes the pre-checking of definitions for the agent to be an error, and continues processing for other check agent services.

(O)

Examine the cause of the error according to the messages on the manager and on the agent, take corrective action, and then pre-check the definitions again.

KAVS3430-I
The value (item-name), specified in the environment settings parameter (parameter-name) of the definitioncheck function, is out of range. The default value (default) will be assumed and processing will continue.

Since the value specified in the environment setting parameter for the definition pre-check function is outside the valid range, the system assumes the default and continues processing.

(S)

Continues processing, assuming the value indicated in default.

(O)

Set the value in the environment setting parameter correctly, and then restart JP1/AJS3 Check Manager or JP1/AJS3 Check Agent.

KAVS3431-I
The definitioncheck function error detected while processing process-name. (maintenance-information-1, maintenance-information-2)

An error was detected during processing within the definition pre-check function.

(S)

Continues processing.

(O)

Take action according to the instructions given by the KAVS message corresponding to the information indicated in maintenance-information-1 and maintenance-information-2, and then pre-check the definitions again.

KAVS3432-I
An error has occurred in JP1/AJS2 for the connection host. (connected-host-name)

An error occurred in JP1/AJS3 on the connection host for one of the following reasons:

The ajsinetd process is not running on the connection host.

JP1/AJS3 - Manager on the connection host does not support execution order control for root jobnets.

An error occurred during communication with JP1/AJS3 on the connection host.

(S)

Continues processing.

(O)

Take action to correct the error on the connection host, and then perform a definition pre-check again.

KAVS3433-I
Processing is cancelled due to failure to acquire agent information by using the function for pre-checking definitions. : host-name maintenance-information-1 maintenance-information-2 maintenance-information-3

Processing is canceled because an attempt to acquire agent information by using the definition pre-check function has failed.

The probable causes are:

The JP1/AJS3 service is not running on the host indicated in host-name.

The agent management daemon on the host indicated in host-name terminated abnormally.

(S)

Cancels processing to check the unit subject to the definition pre-check.

(O)

Check whether the JP1/AJS3 service is running on the host indicated in host-name.

If you cannot correct the error by starting the JP1/AJS3 service, restart the JP1/AJS3 service and the JP1/AJS3 Check Manager service on the host indicated in host-name, and then perform the definition pre-check again.

KAVS3910-E
Interprocess communication failed. : maintenance-information-1 maintenance-information-2 maintenance-information-3

Interprocess communication failed.

(S)

Connects to the JP1/Base event service the next time that an event is output (if yes is specified in the COMMANDEVENT environment setting parameter).

(O)

Determine the cause of the error, and then re-execute the command.

If the JP1/Base event service has stopped, start it.

If a message Failed to put Event. is displayed in maintenance-information-1 and you omitted the COMMANDEVENT environment setting parameter or specified no for it, check the status of the JP1/Base event service, and then restart the JP1/AJS3 service.

KAVS4091-E
The wrong request was received. (maintenance-information)

The job submit process received invalid information.

(S)

Continues processing.

KAVS4092-I
Communication with a command process was disconnected. (maintenance-information)

Communication with the command process at the processing-request source was severed.

(S)

Continues processing.

KAVS4200-E
Failed to write the file created during unit (unit-name) execution. : maintenance-information

An attempt to write to the database from the file that is created during execution of the unit has failed. As a result, the following problems may occur when a service is started in the disaster mode:

The Execution Result Details dialog box for the unit indicated in unit-name does not display a message.

The macro variables are not inherited correctly during execution of a unit that follows the unit indicated in unit-name.

(S)

Continues execution of the unit.

(O)

Determine the cause of the error from the error message that was output before this message, and correct the cause of the error. Then specify the unit indicated in unit-name and retry.

KAVS4201-E
Failed to save the macro variable specified during jobnet (jobnet-name) execution registration. Execution registration cancelled. : maintenance-information-1 maintenance-information-2

The system cancels execution registration because the system failed to save the macro variable that was specified when the jobnet was registered for execution.

(S)

Cancels processing.

(O)

Determine the cause of the error from the error message that was output before this message, and correct the cause of the error. Then re-register the jobnet.

KAVS4202-E
File creation failed during creating a generation of jobnet (jobnet-name). Generation creation (execution-ID) is canceled. : maintenance-information-1 maintenance-information-2

The system cancels creation of a new generation because an attempt to inherit the macro variables or to record the execution ID of the new generation failed during creation of the new jobnet generation.

(S)

Cancels processing.

(O)

Determine the cause of the error from the error message that was output before this message, and correct the cause of the error. If an attempt to register the jobnet for execution has failed, re-register the jobnet. If the jobnet has been registered for execution successfully and this message appears before the jobnet is executed, the action to take differs depending on the registration method. Take appropriate action as follows:

Fixed execution with the period specified (including the case in which a schedule information file is used):

Make sure that the generations have been created in the specified period, and then add the generations that have not been created. If many generations have not been created yet, cancel all registrations of the relevant jobnet, and then re-register them.

Fixed execution with the number of future generations specified, or planned execution:

No generations will be created after the generation whose creation is canceled. Cancel all registrations of the relevant jobnet, and then re-register them.

Irrespective of the registration method, when the start condition is used and this message appears during execution, the jobnet is placed in the Monitor terminated status. If this message appears when you temporarily change the plan or add a registration, re-execute the same operation.

KAVS4203-E
Deletion of an unnecessary macro variable failed during creating a generation of jobnet (jobnet-name). Generation creation (execution-ID) is canceled. : maintenance-information-1 maintenance-information-2

The system cancels creation of a new generation because an attempt to delete an unnecessary macro variable file or record failed during creation of the new generation of the jobnet.

(S)

Cancels processing.

(O)

Determine the cause of the error from the error message that was output before this message, and correct the cause of the error. If an attempt to register the jobnet for execution has failed, re-register the jobnet. If the jobnet has been registered for execution successfully and this message appears before the jobnet is executed, the action to take differs depending on the registration method. Take appropriate action as shown below:

Fixed execution with the period specified (including the case where a schedule information file is used):

Make sure that the generations have been created in the specified period, and then add the generations that are not created. If many generations have not been created yet, cancel all registrations of the relevant jobnet, and then re-register them.

Fixed execution with the number of future generations specified, or planned execution:

No generations will be created after the generation whose creation is canceled. Cancel all registrations of the relevant jobnet, and then re-register them.

Irrespective of the registration method, when the start condition is used and this message appears during execution, the jobnet is placed in the Monitor terminated status. If this message appears when you temporarily change the plan or add a registration, re-execute the same operation.

KAVS4204-E
Failed to delete unnecessary file or record for unit (jobnet-name:execution-ID) : maintenance-information-1 maintenance-information-2

An attempt to delete unnecessary macro variables or job error information for the unit has failed. An unnecessary file remains, or an unnecessary record remains in the database.

(S)

Continues processing.

(O)

Determine the cause of the error from the error message that was output before this message, and correct the cause of the error. If an attempt to cancel registration of the generation has failed, cancel the registration again without executing or re-executing the jobnet. If registration of a generation is successfully canceled, or if this error message appears during creation of a new generation, during execution of a generation, or during deletion of suspended units, an unnecessary file for the unit remains. If this error message appears often, check the amount of space on the disk.

KAVS4209-W
An error has occurred while restructuring JP1/AJS2 control file from an EmbedDB.

An error occurred during restructuring of a file, such as the standard error output file under the job information storage folder, for one of the following reasons:

You do not have update permission for the job information storage folder and the files in that folder.

The file system does not have sufficient free space.

(S)

Continues processing.

(O)

If this error message appears, the following may occur.

After operation starts, a job using a queue terminates abnormally.

The Execution Result Details dialog box for the job prior to its being restructured does not display a message.

Jobs and jobnets using the inherited information and macro variables of the event job before the restructuring are not re-executed correctly.

KAVS4211-E
The JP1/AJS2 service is not inactive.

The specified command cannot be executed because the JP1/AJS3 service has not stopped.

(S)

Cancels processing.

(O)

Stop the JP1/AJS3 service, and then re-execute the command.

KAVS4601-E
Cannot treat as jobnet for the connection destination. : unit-name

An option that can be specified only for the connection-destination jobnet is specified for a unit that is not the connection-destination jobnet.

(S)

Cancels command execution. However, the system continues processing if you specify multiple jobs.

(O)

Specify the connection-destination jobnet name, and then re-execute the command.

KAVS4602-E
Invalid information relating to jobnet connector. : unit-name

The execution order control information specified in the unit definition contains an error.

The probable causes are:

The unit containing the execution order control information is created in a unit that is not either of the following:
- A planning group
- A root jobnet (except for a root jobnet under a planning group)

Although a root jobnet or planning group is specified so that connection with a jobnet connector is not established, one of the following information items is specified:
- A value is specified for Jobnet Connector.
- Synchro is specified for Exec. order method.
- Other service is specified for Connection range.
- A value is specified for Connection host.
- A value is specified for Connection service.

Although a root jobnet, planning group, or jobnet connector is specified so that linkage between scheduler services is not established, one of the following information items is specified:
- A value is specified for Connection host.
- A value is specified for Connection service.

Although a root jobnet, planning group, or jobnet connector is specified so that linkage between scheduler services is established, the connection service name is not specified.

(S)

Cancels command execution.

(O)

Check the unit definition, and then execute the command.

KAVS4603-E
Cannot hold rerun jobnet connector. : unit-name

The jobnet connector cannot be rerun because it cannot be placed in the hold state.

(S)

Cancels command execution. However, the system continues processing if you specify multiple jobs.

(O)

Re-execute the command without the hold option (-h) specified.

KAVS4607-E
Cannot define jobnet connector in a registered unit. : unit-name

A unit containing a jobnet connector cannot be defined as a registered unit.

(S)

Cancels command execution.

(O)

Check the unit definition and execute the command.

KAVS4608-E
Cannot delete the unit(unit-name) - jobnet connector exist.

When you delete the registered unit information, a unit that contains a jobnet connector cannot be deleted. To delete the jobnet connector and the unit that contains the jobnet connector, first unregister the unit.

(S)

Cancels command execution.

(O)

Check the registration status of the unit, and then re-execute the command.

KAVS4609-E
Cannot copy the unit(unit-name) - jobnet connector exist.

When you copy unit information to a registered unit, a unit that contains a jobnet connector cannot be copied. To copy the jobnet connector and the unit that contains the jobnet connector to a registered unit, first unregister the copy-destination unit.

(S)

Cancels command execution.

(O)

Check the registration status of the unit, and then re-execute the command.

KAVS4610-E
Cannot move the unit(unit-name) - jobnet connector exist.

When you move unit information to a registered unit, a unit that contains a jobnet connector cannot be moved. To move the jobnet connector and the unit that contains the jobnet connector to a registered unit, first unregister the destination unit.

(S)

Cancels command execution.

(O)

Check the registration status of the unit, and then re-execute the command.

KAVS4611-E
Cannot define the unit(unit-name) - jobnet connector exist.

When you create a unit by overwriting a registered unit with existing unit information that has the same name, a unit that contains a jobnet connector cannot be created. To overwrite the registered unit having the same name as the jobnet connector and the unit that contains the jobnet connector, first unregister the unit to be overwritten.

(S)

Cancels command execution.

(O)

Check the registration status of the unit, and then re-execute the command.

KAVS4612-E
Jobnet connector(unit-name) can only be copy into jobnet.

You cannot copy a jobnet connector into a unit other than a jobnet.

(S)

Cancels command execution.

(O)

Check the copy destination of the unit, and then re-execute the command.

KAVS4613-E
Jobnet connector(unit-name) can only be move into jobnet.

You cannot move a jobnet connector into a unit other than a jobnet.

(S)

Cancels command execution.

(O)

Check the destination of the unit, and then re-execute the command.

KAVS4614-E
A unit including jobnet connector can only be define in jobnet. : unit-name

When you define a unit that contains a jobnet connector, you cannot specify a unit other than a jobnet for the unit under which the unit is to be created.

(S)

Cancels command execution.

(O)

Check the location in which the unit is to be created, and then re-execute the command.

KAVS4615-E
Cannot operate - Condition exist in the jobnet for the connection destination. : unit-name

Operation is impossible because a start condition is defined in the connection-destination jobnet.

(S)

Terminates processing. However, if multiple units are specified, the system continues processing of other units.

(O)

Change the unit configuration, and then re-execute the command.

KAVS4616-E
Cannot operate - Jobnet connector exist in the jobnet for the connection destination. : unit-name

Operation is impossible because a jobnet connector is defined in the connection-destination jobnet.

(S)

Terminates processing. However, if multiple units are specified, the system continues processing of other units.

(O)

Change the unit configuration, and then re-execute the command.

KAVS4617-E
Cannot operate - Jobnet connector exist in the condition. : unit-name

Operation is impossible because a jobnet connector is defined in the jobnet with start conditions.

(S)

Terminates processing. However, if multiple units are specified, the system continues processing of other units.

(O)

Change the unit configuration, and then re-execute the command.

KAVS4618-E
Cannot operate - Condition exist in the planning group for the connection destination. : unit-name

Operation is impossible because a start condition is defined in the connection-destination planning group.

(S)

Terminates processing. However, if multiple units are specified, the system continues processing of other units.

(O)

Change the unit configuration, and then re-execute the command.

KAVS4619-E
Cannot operate - Jobnet connector exist in the planning group for the connection destination. : unit-name

Operation is impossible because a jobnet connector is defined in the connection-destination planning group.

(S)

Terminates processing. However, if multiple units are specified, the system continues processing of other units.

(O)

Change the unit configuration, and then re-execute the command.

KAVS4620-E
Cannot operate - Root remote jobnet exist in the planning group for the connection destination. : unit-name

Operation is impossible because a jobnet connector is defined in the connection-destination planning group.

(S)

Terminates processing. However, if multiple units are specified, the system continues processing of other units.

(O)

Change the unit configuration, and then re-execute the command.

KAVS4621-E
Cannot operate - Jobnet for the connection destination exist in the planning group for the connection destination. : unit-name

Operation is impossible because a connection-destination jobnet is defined in the connection-destination planning group.

(S)

Terminates processing. However, if multiple units are specified, the system continues processing of other units.

(O)

Change the unit configuration, and then re-execute the command.

KAVS4624-E
The release ID has already been used.

Release entry is impossible because release information having the same release ID already exists.

(S)

Cancels command execution.

(O)

Change the release ID, and then re-execute the command.

KAVS4625-E
The type cannot be specified for the release target jobnet. : maintenance-information

Specification of the release target jobnet contains an error.

The type of the unit specified as the release source or release target might be one of the following:

Other than a root jobnet

Remote jobnet

Recovery jobnet

Manager jobnet

Root jobnet in a planning group

(S)

Cancels command execution.

(O)

Check the release target jobnet, and then re-execute the command.

KAVS4626-E
The same unit cannot be specified for the release source jobnet and the release target jobnet.

The same unit cannot be specified as the release source and release target jobnets.

(S)

Cancels command execution.

(O)

Change the release source or release target jobnet, and then re-execute the command.

KAVS4627-E
(unit-name) is not the release target jobnet.

An attempt was made to cancel the release or view the release information for a jobnet that has not been entered for release.

(S)

Cancels command execution.

(O)

Check the unit for which you want to cancel the release or view the release information, and then re-execute the command.

KAVS4628-E
The state of release wait, delete wait, or release entry wait does not exist. : unit-name

An attempt was made to cancel the release of a jobnet definition whose status was not Release wait, Delete wait, or Release entry wait.

(S)

Cancels command execution.

(O)

Check the unit for which you want to cancel the release, and then re-execute the command.

KAVS4629-E
The type cannot be specified for the release source jobnet. : maintenance-information

The specification of the release source jobnet contains an error.

The type of the unit specified as the release source or release target might be one of the following:

Other than a root jobnet

Remote jobnet

Recovery jobnet

Manager jobnet

Root jobnet in a planning group

Unit entered for release

(S)

Cancels command execution.

(O)

Check the release source jobnet, and then re-execute the command.

KAVS4630-E
The state of release wait, delete wait, or release entry wait does exist. : unit-name, release-ID

Release entry is impossible because there is a jobnet definition whose status is Release wait, Delete wait, or Release entry wait.

(S)

Cancels command execution.

(O)

Check the release information for the unit you want to enter for release, and then re-execute the command.

KAVS4631-W
The jobnet definition for the applied where the generation did not exist could not be deleted.

Release entry terminated normally, but a jobnet definition that had no generation and whose status was Applied could not be deleted.

(S)

Continues processing.

The jobnet definition in Applied status remains in the database.

(O)

The jobnet definition in Applied status that could not be deleted will be deleted automatically when release entry is performed next time.

Because the cause of the failure was output to the previous message, correct the problem according to the instructions given by that message.

KAVS4632-E
A generation beginning on the release date or later exists.

Release entry or release cancellation cannot be performed because there is a generation that has been generated for fixed execution registration with a period or a date specified after the release date.

(S)

Cancels command execution.

(O)

Cancel registration of the generation generated for fixed execution registration after the release date, and then re-execute the command.

KAVS4633-E
The release time is incorrect.

Release entry cannot be performed if a time earlier than the current time is specified.

(S)

Cancels command execution.

(O)

Specify a time later than the current time, and then re-execute the command.

KAVS4634-E
A definition release being applied does not exist.

The command cannot be executed because a jobnet definition whose status is Being applied does not exist.

(S)

Cancels command execution.

(O)

Make sure that a jobnet definition whose status is Being applied exists, and then re-execute the command.

KAVS4635-E
Cannot operate - Outside the release period.

Operation that extends beyond the release date cannot be performed.

(S)

Cancels command execution.

(O)

Check the release date of the target unit, and then re-execute the command.

KAVS4636-E
Cannot operate - A remote jobnet exists in the specified unit.

A unit containing a remote jobnet cannot be entered for release.

(S)

Cancels command execution.

(O)

Check the definition of the release target unit, and then re-execute the command.

KAVS4638-E
Cannot operate - A jobnet connector exists in the specified condition unit.

Operation is impossible because the release target or release source jobnet is a jobnet with start conditions that contain a jobnet connector.

(S)

Cancels command execution.

(O)

Check the definition of the release target or release source jobnet, and then re-execute the command.

KAVS4639-E
Cannot operate - A condition exists in the specified jobnet for the connection destination.

Operation is impossible because a jobnet with start conditions is specified as the connection-destination jobnet for the release target or release source jobnet.

(S)

Cancels command execution.

(O)

Check the definition of the release target or release source jobnet, and then re-execute the command.

KAVS4640-E
Cannot operate - A jobnet connector exists in the specified jobnet for the connection destination.

Operation is impossible because a jobnet connector is contained in the connection-destination jobnet for the release target or release source jobnet.

(S)

Cancels command execution.

(O)

Check the definition of the release target or release source jobnet, and then re-execute the command.

KAVS4643-E
Cannot operate - Compatible V8 constitution.

Release operation is impossible in the V8 compatible configuration.

(S)

Cancels command execution.

(O)

Change the configuration to the standard configuration, and then re-execute the command.

KAVS4645-E
Cannot move - The moving destination of unit (unit-name) is invalid.

The released unit can be moved only to immediately below the job group.

(S)

Cancels command execution.

(O)

Check the destination, and then re-execute the command.

KAVS4646-E
An unnecessary jobnet was defined. Resolve the problem, cancel the release, and then entry the release again.

An unnecessary jobnet definition was created. After correcting the problem, cancel the release and then perform the release entry again.

(S)

Cancels command execution.

(O)

Take action according to the the instructions given by the message that was output immediately before this message. You also need to cancel the release because a jobnet definition whose status is Release entry wait or Delete wait has been created. After canceling the release, perform release entry again.

KAVS4647-E
Cannot operate - The version is different.

Operation is impossible because the version of JP1/AJS that manages the target unit and the version of JP1/AJS that performs the operation do not match.

(S)

Cancels processing.

(O)

Check the versions as a user who has logged on as a member of the Administrators group or who has superuser privileges.

KAVS4648-E
Scheduler service has not started.

The scheduler service is not running.

(S)

Cancels processing.

(O)

Start the scheduler service, and then retry the operation.

KAVS4649-E
Cannot communicate with scheduler service.

During communication with the scheduler service, a situation that prevents communication with the scheduler service occurred because, for example, the service was stopped.

(S)

Cancels processing.

(O)

Check whether the scheduler service is running. After checking the cause of the error, retry the operation.

KAVS4650-E
Cannot operate - Jobnet has been shutdown.

The status of the specified jobnet is Shutdown.

The probable causes are:

The unit defined in the calendar to be referenced does not exist.

The unit defined in the exclusive schedule does not exist.

(S)

Cancels processing.

(O)

Unregister the jobnet in Shutdown status, review the schedule definition, and then retry the operation.

KAVS4651-E
Registerable Jobnet number exceeds the limit.

The number of jobnets that can be registered exceeds the limit.

(S)

Cancels processing.

(O)

Unregister unnecessary jobnets, and then retry the operation.

KAVS4654-E
A unit was deleted during the processing.

A unit was deleted during processing.

(S)

Cancels processing.

(O)

Check whether the specified unit exists, and then retry the operation.

KAVS4655-E
In use by other user.

Another user is using the unit.

(S)

Cancels processing.

(O)

Wait until the other user ends the use of the unit, and then retry the operation.

KAVS4656-E
No authority for Unit.

You do not have authority for the unit.

(S)

Cancels processing.

(O)

Execute the command as a user who has the required authority for the unit.

KAVS4657-E
A unit type that cannot be added is specified in the jobnet where release entry is complete.

A unit type that cannot be added to a jobnet entered for release is specified. The specified unit type might be one of the following:

Jobnet connector

Remote jobnet

Start condition

(S)

Cancels command execution.

(O)

Check the unit type and then re-execute the command.

KAVS4699-I
Because the scheduler service is not an ISAM database, the reconfiguration is not performed.

Reorganization is not performed because the scheduler service database is not ISAM.

(S)

Continues processing.

KAVS4700-E
The jobnet connector (jobnet-name:execution-ID) ended abnormally because it failed to connect to the connection destination jobnet.

The jobnet connector cannot be executed because an attempt to connect to the connection-destination jobnet has failed.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

The jobnet cannot be re-executed if the error occurred during re-execution or if relationships are not established between generations of a jobnet for which a jobnet connector is defined and those of its connection-destination jobnet. Re-execute the subsequent unit of the jobnet connector.

If the error occurred during processing other than re-execution, take action according to the error message that was output to the integrated trace log before of after this message. After correcting the error, re-execute the jobnet connector.

KAVS4701-E
The jobnet for the connection destination(jobnet-name:execution-ID) ended abnormally because it failed to connect to jobnet connector.

The connection-destination jobnet cannot be executed because an attempt to connect to the jobnet connector has failed.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Take action according to the error message that was output to the integrated trace log before or after this message. After correcting the error, re-execute the connection-destination jobnet

KAVS4702-E
Cannot execute the jobnet connector(jobnet-name) because the jobnet name of the connection destination is not specified.

The jobnet connector cannot be executed because the connection-destination jobnet name is not specified.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

Specify the connection-destination jobnet name, and then re-execute the jobnet connector.

KAVS4703-E
Cannot execute the jobnet connector(jobnet-name) because the jobnet name of the connection destination is invalid.

The jobnet connector cannot be executed because the specified connection-destination jobnet is invalid. The probable causes are:

The unit specified for the connection-destination jobnet does not exist.

The type of the unit specified for the connection-destination jobnet is invalid.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

Correct the error, and then re-execute the jobnet connector.

KAVS4704-E
Cannot execute the jobnet connector (jobnet-name) because the jobnet for the connection destination is not defined to connect.

The jobnet connector cannot be executed because connection is not established from the connection-destination jobnet. The probable causes are:

The execution order control is not set for the connection-destination jobnet.

The jobnet connector is not specified for the connection-destination jobnet.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

Correct the error, and then re-execute the jobnet connector.

KAVS4705-E
Cannot execute the jobnet for the connection destination(jobnet-name) because the jobnet connector name is not specified.

The connection-destination jobnet cannot be executed because the jobnet connector name is not specified.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Specify the jobnet connector name, and then re-execute the connection-destination jobnet.

KAVS4706-E
Cannot execute the jobnet for the connection destination(jobnet-name) because the jobnet connector name is invalid.

The connection-destination jobnet cannot be executed because the specified jobnet connector is invalid. The probable causes are:

The unit specified for the jobnet connector does not exist.

The type of the unit specified for the jobnet connector is invalid.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Correct the error, and then re-execute the connection-destination jobnet.

KAVS4707-E
Cannot execute the jobnet for the connection destination(jobnet-name) because the jobnet connector is not defined to connect.

The connection-destination jobnet cannot be executed because connection is not established from the jobnet connector. The probable cause is:

The connection-destination jobnet is not specified for the jobnet connector.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Correct the error, and then re-execute the jobnet connector.

KAVS4708-E
An attempt of job status notification from the jobnet for the connection destination(jobnet-name:execution-ID) has failed. : maintenance-information

The status of the jobnet connector might be incorrect because the connection-destination jobnet failed to send a status notification to the jobnet connector.

(S)

Continues processing.

(O)

Take action according to the Windows event log, syslog, or integrated trace log message that was output immediately before this message.

Note that the relationship between the jobnet connector and the connection-destination jobnet might have been invalid. In this case, the status of the jobnet connector might not have been changed correctly according to the status of the connection-destination jobnet. If necessary, manually change the status of the jobnet connector.

KAVS4710-E
Cannot use the controlling execution order of Root jobnet between scheduler services. (scheduler-service-name) : maintenance-information

The jobnet connector or the connection-destination root jobnet cannot be executed. The probable causes are:

The RJCUSE environment setting parameter is not set to yes.

The scheduler service inter-communication control process has stopped.
The jobnet connector or connection-destination root jobnet for which execution was attempted terminates abnormally after a KAVS4701-E or KAVS4700-E message is output, respectively.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Check the value of the RJCUSE environment setting parameter. For details on the environment setting parameters, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

If the scheduler service inter-communication control process has stopped, restart the JP1/AJS3 service.

KAVS4711-E
Cannot execute the jobnet connector (jobnet-name) because the connection host name of the jobnet of the connection destination is invalid.

The jobnet connector cannot be executed because the connection host name specified for the connection-destination jobnet is invalid. The probable cause is:

The connection host name specified for the connection-destination jobnet does not match the host name for the jobnet connector.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

Correct the error, and then re-execute the jobnet connector.

KAVS4712-E
Cannot execute the jobnet connector (jobnet-name) because the connection service name of the jobnet of the connection destination is invalid.

The jobnet connector cannot be executed because the connection service name specified for the connection-destination jobnet is invalid. The probable cause is:

The connection service name specified for the connection-destination jobnet does not match the scheduler service of the jobnet connector.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

Correct the error, and then re-execute the jobnet connector.

KAVS4713-E
Cannot execute the jobnet connector (jobnet-name) because the connection range of the jobnet of the connection destination is invalid.

The jobnet connector cannot be executed because the connection range specified for the connection-destination jobnet is invalid. The probable cause is:

The connection range specified for the connection-destination jobnet does not match the connection range for the jobnet connector.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

Correct the error, and then re-execute the jobnet connector.

KAVS4714-E
Cannot execute the jobnet of the connection destination (jobnet-name) because the connection host name of the jobnet connector is invalid.

The connection-destination jobnet cannot be executed because the connection host name specified for the jobnet connector is invalid. The probable cause is:

The connection host name specified for the jobnet connector does not match the host name specified for the connection-destination jobnet.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Correct the error, and then re-execute the connection-destination jobnet.

KAVS4715-E
Cannot execute the jobnet of the connection destination (jobnet-name) because the connection service name of the jobnet connector is invalid.

The connection-destination jobnet cannot be executed because the connection service name specified for the jobnet connector is invalid. The probable cause is:

The connection service name specified for the jobnet connector does not match the scheduler service for the connection-destination jobnet.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Correct the error, and then re-execute the connection-destination jobnet.

KAVS4716-E
Cannot execute the jobnet of the connection destination (jobnet-name) because the connection range of the jobnet connector is invalid.

The connection-destination jobnet cannot be executed because the connection range specified for the jobnet connector is invalid. The probable cause is:

The connection range specified for the jobnet connector is different from the connection range for the connection-destination jobnet.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Correct the error, and then re-execute the connection-destination jobnet.

KAVS4720-E
An attempt to connect to the process controlling communication between scheduler services has failed. (scheduler-service-name) : maintenance-information

An attempt to connect to the scheduler service inter-communication control process has failed.

(S)

If the number of reconnections has not reached the threshold, the system outputs a KAVS4722-I message and then starts reconnection processing. If the reconnection is successful, the system outputs a KAVS4723-I message.

If the number of reconnections has reached the threshold, the system outputs a KAVS4724-E message and sets reduced mode for the execution order control for root jobnets between scheduler services.

(O)

Take action according to the message that was output before or after this error message.

KAVS4721-E
The connection with the process controlling communication between scheduler services was closed. (scheduler-service-name) : maintenance-information

The connection with the scheduler service inter-communication control process has been disconnected.

(S)

If the number of reconnections has not reached the threshold, the system outputs a KAVS4722-I message and then starts reconnection processing. If the reconnection is successful, the system outputs a KAVS4723-I message.

If the number of reconnections has reached the threshold, the system outputs a KAVS4724-E message and sets reduced mode for the execution order control for root jobnets between scheduler services.

(O)

Take action according to the message that was output before or after this error message.

KAVS4722-I
Reconnection processing with the process controlling communication between scheduler services started. (scheduler-service-name)

Reconnection processing with the scheduler service inter-communication control process will now start.

(S)

Starts the reconnection processing with the scheduler service inter-communication control process.

KAVS4723-I
Reconnect to the process has finished. (scheduler-service-name)

The scheduler service inter-communication control process is reconnected.

(S)

Continues operation.

KAVS4724-E
The number of times the process controlling communication between scheduler services has Reconnection has exceeded the threshold. Therefore,the process controlling communication between scheduler services has been Reconnection processing blocked. (scheduler-service-name)

Reconnection was attempted because disconnection of communication with the scheduler service inter-communication control process was detected, but the connection could not be established before the number of times reconnection was attempted exceeded the threshold. Therefore, the reconnection processing is canceled.

(S)

Continues processing in reduced mode for the execution order control for root jobnets between processing scheduler services. The system abnormally terminates the running jobnet connector for which Other service is specified for Connection range and any connection-destination jobnet whose status is Wait for start time.

Any jobnet connector or connection-destination jobnet for which execution is attempted in reduced mode for the execution order control also terminates abnormally.

(O)

To control the execution order for root jobnets between scheduler services, restart the scheduler service to cancel reduced mode for the execution order control.

KAVS4725-E
An IPC error occurred in the process controlling communication between scheduler services. (scheduler-service-name) : maintenance-information

An error occurred in the scheduler service inter-communication control process. The probable causes are:

Connection between the scheduler service inter-communication control process and another process is disconnected.

The number of connections that the scheduler service inter-communication control process uses for communication has exceeded the maximum.

The scheduler service inter-communication control process failed to resolve the host name.

The scheduler service specified for the connection service name for the jobnet connector or connection-destination jobnet is not running.

The scheduler service inter-communication control process is not running on the host specified for the connection host name for the jobnet connector or connection-destination jobnet.

(S)

Continues processing.

(O)

Take action according to the message that was output before or after this error message.

If no such message was output, check whether the scheduler service inter-communication control process is running on the host specified for the connection host name, or whether the scheduler service specified for the connection service name is running.

KAVS4730-E
Cannot execute the jobnet connector (jobnet-name) because it failed to resolved to the local host name(host:host-name).

The jobnet connector cannot be executed because an attempt to resolve the local host name has failed.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

Check whether the name of the host for which the jobnet connector has been defined is set correctly in the hosts and jp1hosts files.

Correct the settings, and then re-execute the jobnet connector.

KAVS4731-E
Cannot execute the jobnet connector (jobnet-name) because it failed to resolved to the connection host name of the jobnet of the connection destination.

The jobnet connector cannot be executed because an attempt to resolve the connection host name specified for the connection-destination jobnet has failed.

(S)

Places the jobnet connector into Ended abnormally status.

(O)

Check whether the host specified for the connection host name for the connection-destination jobnet is set correctly in the hosts and jp1hosts files for the host for which the connection-destination jobnet has been defined.

Correct the settings, and then re-execute the jobnet connector.

KAVS4732-E
Cannot execute the jobnet (jobnet-name) of the connection destination because it failed to resolved to the local host name (host:host-name).

The connection-destination jobnet cannot be executed because an attempt to resolve the local host name has failed.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Check whether the name of the host for which the connection-destination jobnet has been defined is set correctly in the hosts and jp1hosts files.

Correct the settings, and then re-execute the connection-destination jobnet.

KAVS4733-E
Cannot execute the jobnet (jobnet-name) of the connection destination because it failed to resolved to the connection host name of the jobnet connector.

The connection-destination jobnet cannot be executed because an attempt to resolve the connection host name specified for the jobnet connector has failed.

(S)

Places the connection-destination jobnet into Ended abnormally status.

(O)

Check whether the host specified for the connection host name for the jobnet connector is set correctly in the hosts and jp1hosts files for the host for which the jobnet connector has been defined.

Correct the settings, and then re-execute the connection-destination jobnet.

KAVS4750-E
Because of the incomplete description of jobnet(name:unit-name, release ID:release-ID),jobnet(name:unit-name, release ID:release-ID) cannot be scheduled.

A generation could not be created because the jobnet schedule definition contained an error.

(S)

The system operates as follows when a jobnet is registered for execution.

If the jobnet registered for execution is displayed in the message as a jobnet that cannot be scheduled, the registration fails.

If the jobnet displayed in the message as a jobnet that cannot be scheduled has already been registered for execution, the system handles the jobnet as follows:
- If the jobnet is registered for planned execution, the system places the jobnet into Shutdown status.
- If the jobnet is registered for fixed execution, the system does not create a next execution schedule.

(O)

If the status of the jobnet definition that has the release ID indicated in release-ID is Release wait, follow the procedure below:

Unregister the jobnet indicated in unit-name.

Cancel the release for the jobnet indicated in unit-name.

Correct the error in the schedule definition.

Enter the corrected jobnet definition for release again for the jobnet indicated in unit-name.

If the status of the jobnet definition that has the release ID indicated in release-ID is Being applied, follow the procedure below:

Unregister the jobnet indicated in unit-name.

Correct the error in the schedule definition.

Re-register the jobnet indicated in unit-name for execution.

If a jobnet with an invalid definition does not have release information, *** is displayed in release-ID for the jobnet. In this case, take the same action as for a jobnet definition whose status is Being applied.

KAVS4751-W
Since the new generation(execution-ID) is created to change the jobnet definition of the generation(unit-name:execution-ID), information of the temporary change in plan before the definition change is lost.

If an operation that switches a jobnet definition and creates new generations is performed, information about the changes made by using Change Plan before the jobnet definition is switched will be lost.

(S)

Continues processing.

(O)

Use information such as the scheduler log to check the changes made by using Change Plan for the generations before the jobnet definition is switched, and then make these changes again for the new generations after the jobnet definition is switched.

If the release entry or release cancellation switches a jobnet definition, *** appears in execution-ID in the message because all generations after the release date are re-created. If necessary, use information such as the schedule log to apply the changes that were made by using Change Plan to the generations that are created after the release date.

KAVS4752-E
The generation(execution-ID) of the jobnet(unit-name) is in invalid status because an error occurred during change processing of the jobnet definition. : maintenance-information-1 maintenance-information-2

An attempt to delete the generations of the old definition has failed during switching of the jobnet definition. As a result, part of the jobnet execution registration information is missing.

(S)

Cancels processing.

(O)

Correct the problem according to the message that was output immediately before this message.

If the message appears when one of the following operations is performed, take appropriate action as shown below.

If the message appears during release entry for the jobnet indicated in the message, cancel the execution registration of the jobnet, cancel the release, and then perform the release entry again. After the release entry is performed, re-register the jobnet for execution.

If the message appears during release cancellation for the jobnet indicated in the message, cancel the execution registration of the jobnet, and then retry the release cancellation. After the release cancellation is performed, re-register the jobnet for execution.

If the message appears while execution is being prohibited for the jobnet indicated in the message, cancel the execution registration of the jobnet, re-register it for execution, and then prohibit execution of unnecessary schedules.

If the message appears when an operation other than the above is performed, cancel the execution registration of the jobnet, and then re-register it for execution.

KAVS4822-I
Execution registration information of the unit (unit-name) was not output, because its registration method is not supported for export.

The registered execution-schedule information for jobnets was not exported because the target unit was registered for immediate execution.

(S)

Continues command processing.

KAVS4823-E
The unit (unit-name) cannot be registered for execution, because it does not exist in the execution registration information file.

The specified unit did not exist in the registered execution-schedule information for jobnets file.

(S)

Continues command processing.

(O)

Check the specified unit name, and then execute the command.

KAVS4824-E
The unit (unit-name) cannot be imported, because you are not the user who exported it.

An attempt to import the registered execution-schedule information for jobnets has failed because the user who registered the unit to which the registered execution-schedule information for jobnets was exported is different from the user who performed the import.

(S)

Cancels command execution.

(O)

Check the user who executes the command, and then execute the command.

If multiple users have registered the root jobnet for fixed execution, only a user who has logged on as a member of the Administrators group (in Windows) or has superuser privileges (in UNIX) can perform the import.

KAVS4826-E
Invalid information in execution registration information file (file-name). (sentence-number:n)

The jobnet registered execution-schedule information file is coded incorrectly.

The probable causes are:

Invalid information is entered.

The unit name specified for UNIT= exceeds 930 bytes.

A host name or execution ID is specified for the unit name specified for UNIT=.

A value other than s is specified for ENTRY=.

A left-side value is not specified for the format.

A right-side value is enclosed in double quotation marks (") or single quotation marks (').

(S)

Cancels command execution.

(O)

Check the contents of the jobnet registered execution-schedule information file, and then execute the command.

KAVS4827-E
More than one jobnet is specified.

More than one unit is specified.

(S)

Cancels command execution.

(O)

Specify only one unit, and then re-execute the command.

KAVS4828-E
I/O error occurred. :maintenance-information

An I/O error occurred during input or output processing for a file.

(S)

Cancels processing for the file in which the error occurred, and then terminates the command.

(O)

Take action as shown below.

In Windows:

See the Windows event log and take action according to the output message. If you cannot take corrective action, contact the system administrator.

In UNIX:

See the syslog and take action according to the output message. If you cannot take corrective action, contact the system administrator.

KAVS4829-E
Specified file name (file-name) is too long.

A file name is specified using a character string of more than 255 bytes.

(S)

Cancels command execution.

(O)

Specify a file name that has fewer than 256 bytes, and then re-execute the command.

KAVS4830-E
Execution registration information of some units could not be exported. : maintenance-information

Registered execution-schedule information for jobnets could not be output because command execution failed.

(S)

Cancels command execution.

(O)

Take action according to the instructions given by the error message that was output before this message. Alternatively, the setup environment might be invalid. Make sure that the JP1/AJS3 setup is completed correctly, and then re-execute the command.

KAVS4832-E
An error occurred while processing the unit (unit-name). : maintenance-information

An error occurred during processing for the target unit.

(S)

Continues the command.

(O)

Take action according to the instructions given by the error message that was output before this message. See the output command line and take corrective action for the problem. Then re-execute the command.

KAVS4833-I
Information that is temporarily changed in the plan for the unit (unit-name) is not exported.

A unit in which changes were made by using Change Plan is exported. The information that is changed by using Change Plan is not exported.

(S)

Continues the command.

(O)

Any information that was changed by using Change Plan is not exported. Before you attempt to import the registered execution-schedule information for jobnets, change the plan again.

KAVS4834-E
The upcoming schedule for the specified jobnet (unit-name) was being created, and therefore the execution registration information could not be exported.

The registered execution-schedule information for jobnets could not be exported because the next schedule for the specified jobnet was being created.

(S)

Continues the command.

(O)

Make sure that the jobnet is not running or is not undertaking an operation such as execution registration, and then re-execute the command.

If you are going to export many units at one time, export them in several operations.

KAVS4835-E
The registration information file contains a unit that does not exist.

The jobnet registered execution-schedule information file contains a unit that does not exist.

(S)

Continues the command.

(O)

Check the definition of the unit name indicated in maintenance-information. Alternatively, delete unnecessary unit information from the schedule information section for the unit indicated in maintenance-information for the jobnet registered execution-schedule information file.

KAVS4836-E
The specified unit (unit-name) can not be exported either because it does not exist or execution registration has not been performed.

The unit could not be exported. The probable causes are:

A unit that does not exist is to be exported.

A unit other than a root jobnet is to be exported.

(S)

Continues the command.

(O)

The specified unit does not exist or is not registered for execution. Check the status of the unit, and then re-execute the command.

KAVS4837-I
There is no information to be exported.

As a result of executing the command, there is no information that can be exported.

(S)

Terminates the command.

(O)

The registered execution-schedule information for jobnets was not output because the unit for the specified unit does not exist or because the specified unit does not exist.

KAVS4838-E
Units that exist in different scheduler services cannot be specified at the same time (unit-name).

Processing was canceled because units that exist in different scheduler services were specified at the same time.

(S)

Terminates the command.

(O)

Specify the units only in the same scheduler service, and then export them.

KAVS4839-I
Registration information for the unit (unit-name) was not output because either the unit has not been registered or there is no future schedule.

The registered execution-schedule information for jobnets was not output because a root jobnet that has not been registered or had no future schedule was specified.

(S)

Continues the command.

(O)

Specify a root jobnet that has a scheduled generation.

KAVS4900-I
The process controlling communication between scheduler services has started.

This message reports that the scheduler service inter-communication control process has started.

(S)

Continues processing.

KAVS4901-I
The process controlling communication between scheduler services has terminated.

This message reports that the scheduler service inter-communication control process has terminated.

(S)

Continues processing.

KAVS4902-W
The process (host:host-name, PID:process-ID) controlling communication between scheduler services has terminated abnormally (maintenance-information).

The scheduler service inter-communication control process terminated abnormally.

(S)

Cancels processing of the scheduler service inter-communication control process.

(O)

Restart the scheduler service inter-communication control process until the number of times this process terminates abnormally reaches the threshold. When the threshold is reached, block the scheduler service inter-communication control process.

KAVS4903-I
The management process for the process controlling communication between scheduler services has started.

This message reports that the management process for the scheduler service inter-communication control process has started.

(S)

Continues processing.

KAVS4904-I
The management process for the process controlling communication between scheduler services has terminated.

This message reports that the management process for the scheduler service inter-communication control process has terminated.

(S)

Continues processing.

KAVS4905-E
The management process for the process controlling communication between scheduler services has terminated abnormally (maintenance-information).

The management process for the scheduler service inter-communication control process terminated abnormally.

(S)

Cancels processing of the management process for the scheduler service inter-communication control process.

(O)

Take action according to the Windows event log or syslog message that was output immediately before this message. If you cannot correct the problem, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS4906-W
The value (item-name), specified in the environment settings parameter (parameter-name), is out of range. The default value (default) will be assumed and processing will continue.

Because the value specified for the environment setting parameter is invalid, the system assumes the default value to continue processing.

(S)

Assumes the value indicated in default and continues processing.

(O)

Correct the value of the environment setting parameter, and then restart the JP1/AJS3 service.

KAVS4907-W
The number of connections for the process (host:host-name) controlling communication between scheduler services has exceeded the maximum value, and therefore the connection could not be made with the connection destination host (host:host-name or IP-address).

The connection could not be established because the number of connections for the scheduler service inter-communication control process has exceeded the maximum.

(S)

Continues processing.

Note that you cannot use the execution order control for root jobnets between processing scheduler services until the number of connections has dropped below the maximum.

Also note that either of the following occurs until a KAVS4918-I message is output.

The connection-destination jobnet for which Synchro is specified for Exec. order method is placed into Ended abnormally status.

The jobnet connector is placed into Ended abnormally status.

(O)

After the KAVS4918-I message is output, re-execute the jobnet connector or connection-destination jobnet that could not be connected.

In addition, re-estimate the value of the GWMAXCONNECTION environment setting parameter according to 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

KAVS4908-E
The process(host:host-name) controlling communication between scheduler services failed to communicate with a process (name:process-name) of the same host. : maintenance-information

The scheduler service inter-communication control process failed to communicate with a process of the same host.

For a process that is started for each scheduler service, the process name is output in the scheduler-service-name:process-name format.

(S)

Terminates communication with the process indicated in the message.

(O)

Take action according to the Windows event log or syslog message that was output immediately before this message. If no such message was output, check whether the process indicated in the message is running.

If you cannot correct the problem, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS4909-E
The process(host:host-name) controlling communication between scheduler services failed to communicate with the process (host:host-name or IP-address) controlling communication between scheduler services at the communication destination. : maintenance-information

The scheduler service inter-communication control process failed to communicate with the scheduler service inter-communication control process at the communication destination.

(S)

Terminates communication with the scheduler service inter-communication control process at the communication destination.

(O)

Take action according to the Windows event log or syslog message that was output immediately before this message. If no such message was output, check whether the scheduler service inter-communication control process indicated in the message is running.

If you cannot correct the problem, contact the system administrator, and collect data (see 1.2.3 To the system administrators).

KAVS4910-E
An error occurred during the communication with the process (host:host-name or IP-address name:process-name) because a network access error occurred. : maintenance-information

A network access error occurred during communication with the process.

For the process that is started for each scheduler service, the process name is output in the scheduler-service-name:process-name format.

(S)

Terminates communication.

(O)

Check the environment for communication with the process.

KAVS4911-E
A communication timeout occurred during the communication with the process (host:host-name or IP-address name:process-name). : maintenance-information

A communication timeout occurred during communication with the process.

For the process that is started for each scheduler service, the process name is output in the scheduler-service-name:process-name format.

(S)

Terminates communication.

(O)

Check the environment for communication with the process.

KAVS4912-E
A buffer shortage occurred during the communication with the process (host:host-name or IP-address name:process-name). : maintenance-information

A buffer shortage occurred during communication with the process.

For the process that is started for each scheduler service, the process name is output in the scheduler-service-name:process-name format.

(S)

Terminates communication.

(O)

Check the environment for communication with the process.

KAVS4913-E
The port number could not be obtained. Confirm whether the service name is defined correctly.

An attempt to acquire the port number used by the scheduler service inter-communication control process has failed

(S)

Terminates the scheduler service inter-communication control process.

(O)

Check whether the service name and the port number for jp1ajs2gw are set correctly in the services file. If the port number is correctly defined, memory or disk space might be insufficient. Terminate unnecessary applications, and then restart the JP1/AJS3 service.

KAVS4914-E
The connection was reset while the process (host:host-name) controlling communication between scheduler services was communicating with the process (host:host-name or IP-address) controlling communication between scheduler services at the communication destination. : maintenance-information

The connection was reset while the scheduler service inter-communication control process was communicating with the scheduler service inter-communication control process at the communication destination. The probable causes are:

The JP1/AJS3 service on the destination host has stopped.

An error occurred on the scheduler service inter-communication control process at the communication destination.

The scheduler service inter-communication control process at the communication destination terminated abnormally.

(S)

Terminates communication with the scheduler service inter-communication control process at the communication destination.

(O)

If necessary, check whether the scheduler service inter-communication control process is running on the destination host.

KAVS4915-I
The process (host:host-name) controlling communication between scheduler services has restarted.

This message reports that the scheduler service inter-communication control process has restarted.

(S)

Restarts the scheduler service inter-communication control process.

KAVS4916-W
The process (host:host-name) controlling communication between scheduler services failed to start (maintenance-information).

An attempt to start the scheduler service inter-communication control process has failed. A probable cause is insufficient system resources.

(S)

Terminates the scheduler service inter-communication control process.

(O)

Check the reason for the unsuccessful startup of the scheduler service inter-communication control process according to the message that was output before or after this message, and then take appropriate action.

KAVS4917-E
The number of times the process (host:host-name) controlling communication between scheduler services has terminated abnormally has exceeded the threshold. Therefore, the process controlling communication between scheduler services has been blocked.

The scheduler service inter-communication control process was blocked because the number of times this process terminated abnormally has exceeded the threshold.

(S)

Blocked the scheduler service inter-communication control process because the threshold was exceeded.

(O)

Memory might be insufficient, or the maximum number of processes that can be started in the system might have been reached.

In UNIX, review the settings of the kernel parameters related to memory and processes, and then re-set the values. For details about the kernel parameters, see 3.2.5 Estimating the values for kernel parameters in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide. For details about how to estimate the size of memory used, see 3.2.3 Estimating the size of memory used in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

Check the status of the processes that were running when the error occurred, and make sure that the amount of memory available is greater than the estimated value.

If you cannot determine the cause of the error, collect data and then contact the system administrator (see 1.2.3 To the system administrators).

KAVS4918-I
The number of connections for the process (host: host-name)controlling communication between scheduler services is below the maximum value.

Because the number of connections for the scheduler service inter-communication control process is below the maximum value, execution order control for root jobnets between different scheduler services is now possible.

(S)

Continues processing.

[Contents][Back][Next]

[Trademarks]