6.2.2 Messages specific to the job control function
-
KAJM1001-E
100 or more items of job step information were specified.
More than 99 items of job step information were specified.
- S:
-
The system aborts command execution.
- O:
-
Decrease the number of job step information items to 99 or fewer, and then execute the command again.
-
KAJM1002-E
Job name cannot be omitted.
The job name -jn job-name was not specified.
- S:
-
The system aborts command execution.
- O:
-
Specify the job name -jn job-name, and then execute the command again.
-
KAJM1003-E
Program name cannot be omitted.
Required job step information was not specified.
- S:
-
The system aborts command execution.
- O:
-
Specify the required job step information, and then execute the command again.
-
KAJM1004-E
Job count cannot be omitted.
No job count was specified. When monitoring job completion, make sure to specify a job count.
- S:
-
The system aborts command execution.
- O:
-
Specify the job count and then execute the command again.
-
KAJM1005-E
The name of the host that executes an external program cannot be omitted.
The host name was not specified by the job step information for external program execution.
- S:
-
The system aborts command execution.
- O:
-
Specify the host name and then execute the command again.
-
KAJM1006-E
The specified monitoring time is shorter than the monitoring interval.
The job completion monitoring time is shorter than the job monitoring interval setting.
- S:
-
The system aborts command execution.
- O:
-
Specify the correct value and then execute the command again.
-
KAJM1007-E
The specified archive parameter is incomplete.
If you specify Archive or Print and archive for Archiving mode, you must also specify Object type, Document type, and Information ID.
- S:
-
The system aborts command execution.
- O:
-
Revise Archiving mode and the archive parameters settings, and then execute the command again.
-
KAJM1009-E
To specify this option, a new version of the XBP interface is required. (option: option)
To specify the following options of the jr3bjsub or jr3bjrel command, you must enable the external management interface, which is XBP version 2.0 (XBP 2.0 interface):
-with_child, -class, -title, -dpt, -fmt, -text
For details, see the description of the jr3bjsub or jr3bjrel command in 4. Commands.
- S:
-
The system aborts command execution.
- O:
-
Enable the XBP 2.0 interface at the connection destination R/3 system. For details, see 2.2.8(1) Enabling the XBP 2.0 interface.
-
KAJM1010-E
The parent-child function is set to OFF in the connected SAP system.
Although completion monitoring for parent and child jobs (-with_child option) is specified, the parent and child function is disabled in the R/3 system.
- S:
-
The system aborts command execution.
- O:
-
Enable the parent and child function in the connection destination R/3 system.
For details, see 2.2.8 (2) Enabling the parent and child function.
-
KAJM1800-E
No job satisfies the specified conditions.
There is no job that meets the specified conditions.
- S:
-
The system aborts command execution.
- O:
-
Specify the correct job and then execute the command again.
-
KAJM1801-E
This program does not exist. (program: program-name)
The specified program is not defined in the R/3 system.
- S:
-
The system aborts command execution.
- O:
-
Check whether the program name specified in the command is valid for the R/3 system. If necessary, define the specified program for the R/3 system, and then execute the command again.
-
KAJM1802-E
A step required for execution is not defined.
The job step definition for the job is not complete.
- S:
-
The system aborts command execution. If more than one process was requested, the system continues with the subsequent process.
- O:
-
Check the job step information definition.
-
KAJM1803-E
The job has already finished.
The specified job has already ended.
- S:
-
The system aborts command execution. If more than one process was requested, the system continues with the subsequent process.
- O:
-
Check the job name and job count specified for the command.
-
KAJM1804-W
Failed to acquire an R/3 job log. (job name: job-name, job count: job-count)
Job log acquisition was not successful.
job-name and job-count in the message are output only for JP1/AJS2 for EAP 07-50 or later.
- S:
-
The system continues with command execution.
- O:
-
Check the messages that are output before this message and the R/3 system log to determine the cause of the error.
If KAJM0101-E was output immediately before this message, it is possible the path specified as the job log output destination contains an error.
Check with the JP1/AJS3 for EAP host as to whether any of the following factors exist:
-
A nonexistent folder or directory is specified.
-
The specified file is read-only (for the Windows version).
-
The user does not have command execution write permission for the specified file.
-
-
KAJM1805-E
The job log no longer exists.
The job log file for the specified job was not found in the R/3 system (it was illegally deleted). Another possibility is that the job log file for the job specified in the R/3 system has not been created.
- S:
-
The system aborts the job log acquisition/display operation. If more than one process was requested, the system continues with the subsequent process.
- O:
-
Execute the command again after execution of the specified job is completed. If the situation does not change when the command is executed again, contact the R/3 system administrator.
-
KAJM1806-E
Condition: Condition
Displays the condition for the preceding on-screen message.
-
KAJM1807-E
A log does not yet exist for the specified job.
A job log file for the specified job was not created in the R/3 system.
- S:
-
The system aborts the job log acquisition/display operation. If more than one process was requested, the system continues with the subsequent process.
- O:
-
Execute the command again after the specified job is completed. If the situation does not change when the command is executed again, contact the R/3 system administrator.
-
KAJM1808-E
Job log is empty.
The job log was not output to the job log file for the specified job.
- S:
-
The system aborts the job log acquisition/display operation. If more than one process was requested, the system continues with the subsequent process.
- O:
-
Wait for a while, and then execute the command again. If the situation does not change when the command is executed again, contact the R/3 system administrator.
-
KAJM1811-I
Job was created. (job name: job-name, job count: job-count)
The job was created in the R/3 system.
-
KAJM1812-E
Could not create the job. (job name: job-name, job count: job-count)
The job was not registered in the R/3 system.
- S:
-
The system aborts command execution.
- O:
-
Note any other on-screen messages, check the R/3 system log, and investigate the cause of the problem. If the job count is displayed, it is possible that an incomplete job (unexecutable job) may have been registered in the R/3 system.
-
KAJM1813-E
This variant does not exist. (variant: variant-name)
The specified variant was not found in the R/3 system.
- S:
-
The system aborts command execution.
- O:
-
Specify a correct variant name and then re-execute the command.
If this message appears even though a correct variant name has been specified, a variant without a name may be registered in the specified program.
If a variant without a name is registered, take either of the following actions:
-
Delete the variant without a name from the VARI table of the R/3 system.
-
Change the setting (change the value of the CheckLevel key in the command section of the environment setup file to 0) so that the validity of the ABAP program and the values specified for variants are not checked, and then re-execute the command.
If no variant without a name is registered, check the variant name and then re-execute the command.
-
-
KAJM1814-E
This program is not executable. (program: program-name)
The specified program cannot be executed.
- S:
-
The system aborts command execution.
- O:
-
Check the status of the program specified by the command and the variant information for the program.
-
KAJM1815-E
A variant required for executing this program is not specified. (program: program-name)
The variant required for the specified program was not specified when the job was registered.
- S:
-
The system aborts command execution.
- O:
-
Check whether the specified program runs normally without specifying variants.
If the program requires variants, specify the necessary variants and then re-execute the command.
If the program does not require variants, change the setting (change the value of the CheckLevel key in the command section of the environment setup file to 0) so that the validity of the ABAP program and the values specified for variants are not checked, and then re-execute the command.
-
KAJM1816-E
A program in ABAP cannot be assigned to a job step. (program: program-name)
The job step for executing the indicated ABAP program could not be assigned.
- S:
-
The system aborts command execution.
- O:
-
Review the job step information.
-
KAJM1817-E
An external program cannot be assigned to a job step. (program: program-name)
An external program was not assigned a job step for execution.
- S:
-
The system aborts command execution.
- O:
-
Review the job step information.
-
KAJM1818-E
No variant is defined to the program.(program: program-name)
No variant is defined for the specified program.
- S:
-
The system aborts command execution.
- O:
-
Check whether the specified program runs normally without specifying variants.
If the program requires variants, define the necessary variants in the program, specify the defined variants, and then re-execute the command.
If the program does not require variants, change the setting (change the value of the CheckLevel key in the command section of the environment setup file to 0) so that the validity of the ABAP program and the values specified for variants are not checked, and then re-execute the command.
-
KAJM1819-W
The incomplete job cannot be deleted. (job name: job-name, job count: Job-count)
JP1/AJS3 for EAP could not delete the job that was being created with an incomplete definition when registration of another job failed.
- S:
-
The system continues command execution without deleting the job indicated by job-name and job-count.
- O:
-
Execute the jr3bjdel command to delete the job indicated by job-name and job-count.
-
KAJM1820-E
The job was already released.
The specified job has already been released. You cannot release a job that has already been released.
- S:
-
If no job count was specified, the system continues processing subsequent jobs. If there is no subsequent job or if a job count was specified, the system aborts command execution.
- O:
-
Check the job name and job count specified by the command.
-
KAJM1821-I
Job was released. (job name: job-name, job count: job-count)
The specified job was released.
-
KAJM1822-E
No background work processes are free.
The R/3 system background work processes are not free.
- S:
-
If no job count was specified, the system continues processing subsequent jobs. If there is no subsequent job or if a job count was specified, the system aborts command execution.
- O:
-
Wait for a while, and then execute the command again.
-
KAJM1825-E
The job cannot be released. (job name: job-name, job count: job-count)
The specified job was not released.
- S:
-
The system aborts command execution.
- O:
-
Note the preceding on-screen messages, check the R/3 system log, and investigate the cause of the problem.
-
KAJM1830-I
Now monitoring job-end. (monitoring time: monitoring-time-in-minutes min.)
Job execution completion monitoring has been started.
- S:
-
The system continues with job execution completion monitoring.
-
KAJM1831-E
Job-end monitoring is canceled because a timeout occurred. (job name: job-name, job count: job-count)
Since the job did not end within the monitoring limit, job completion monitoring was terminated.
- S:
-
If an option for R/3 job cancellation was selected, the R/3 job is canceled when a timeout occurs. If the option for R/3 job cancellation was not selected, command execution is canceled when a timeout occurs.
- O:
-
Check the R/3 job status and, if necessary, abort R/3 job execution.
-
KAJM1832-I
Job has finished. (job name: job-name, job count: job-count, status: Finished)
The job has ended.
-
KAJM1833-W
The job was terminated. (job name: job-name, job count: job-count, status: Terminated)
Job execution was terminated in the R/3 system.
- O:
-
Investigate the cause of job execution termination from the information in the R/3 system's job logs.
-
KAJM1834-E
Could not monitor job-end. (job name: job-name, job count: job-count)
Job completion monitoring failed.
- S:
-
The system aborts command execution.
- O:
-
Note any preceding on-screen messages, check the R/3 system log, and investigate the cause of the problem.
Use the SAP front-end software to check the status of the R/3 job. Cancel the R/3 job if necessary.
-
KAJM1835-E
Job-end monitoring is canceled because a reconnection timeout occurred. (job name: job-name, job count: job-count)
Job completion monitoring has been canceled because the connection with the R/3 system could not be restored within the reconnection retry time.
- S:
-
The system aborts command execution.
- O:
-
Check the messages that were output before this message and the R/3 system log to determine the cause of the error. Check whether the value of the retry count or the retry time (RetryCount key or RetryTime key in the command section of the environment setup file) is appropriate.
Use the SAP front-end software to check the status of the R/3 job. Cancel the R/3 job if necessary.
-
KAJM1836-W
The job was intercepted. (job name: job-name, job count: job-count)
A job whose completion is being monitored by JP1 has been interrupted by the R/3 system.
An interrupt occurs when the following conditions are satisfied:
-
The XBP 2.0 interface is installed.
-
The interrupt function is enabled using the INITXBP2 report program.
-
Interrupt criteria that cause the job to be interrupted are set in the TBCICPT1 table.
- S:
-
The system continues command execution (continues completion monitoring for jobs, including the interrupted job).
- O:
-
Release the interrupted job again. (Completion monitoring by JP1 is not completed because the interrupted job is returned to Scheduled status by the R/3 system.)
-
-
KAJM1837-W
The job was deleted or state is unknown. (job name: job-name, job count: job-count)
A job whose completion is being monitoring by JP1 is deleted (or the status of the job is unknown).
If this message appears for a child job that is detected during completion monitoring of parent and child jobs, the parent job may have been set at registration so that it is automatically deleted at normal end.
- S:
-
The system continues completion monitoring and returns 1, indicating that the result of at least one job could not be checked.
- O:
-
Register the target job so that it will not be deleted during completion monitoring.
If this message appears when there are jobs in the R/3 system, check the R/3 system log for the cause.
-
KAJM1838-W
The job is not released. (job name: job-name, job count: job-count)
A scheduled child job was detected during job completion monitoring. The child job may have been registered without specifying the start attribute, or a user without release permissions may have registered the child job.
- S:
-
The system continues command execution (continues completion monitoring for jobs, including the scheduled job).
- O:
-
First, to complete completion monitoring, release the scheduled job.
Next, check whether the job start attribute is specified in the program that is specified for the parent job of the registered child job. If the authorized user of the ABAP program is changed using the -auth option, check whether the specified user has release permissions for the job.
If you do not require completion monitoring of jobs including this job, consider not specifying the -with_child option.
-
KAJM1840-I
The job was canceled. (job name: job-name, job count: job-count)
R/3 job execution was canceled.
-
KAJM1841-E
Job cannot be canceled because it is not active.
Although an attempt was made to cancel a job, it was not active.
- S:
-
If no job count was specified, the system continues processing subsequent jobs. If there is no subsequent job or if a job count was specified, the system aborts command execution.
- O:
-
Check the status of the job to be canceled. Execute the jr3bjcan command after the job becomes active.
-
KAJM1844-E
The job cannot be canceled. (job name: job-name, job count: job-count)
The specified job was not canceled.
- S:
-
The system aborts command execution.
- O:
-
Note any preceding on-screen messages, check the R/3 system log, and investigate the cause of the problem.
-
KAJM1845-E
Unable to determine available server from execution host.
The server on which the job is to be run cannot be determined from the host name assigned to the -tgh option.
- S:
-
The system aborts command execution.
- O:
-
Check whether the specified host name is correct, and whether a SAP instance is correctly allocated to the host.
The -tgh option is a compatible parameter of the job definition created for Releae 4.0 and earlier R/3 systems. To define a job for Release 4.5 and later R/3 systems, use the -tgs option.
-
KAJM1850-I
The job was deleted. (job name: job-name, job count: job-count)
The R/3 job specified by the jr3bjdel command was deleted.
-
KAJM1851-E
The job cannot be deleted. (job name: job-name, job count: job-count)
An attempt to delete the specified job failed.
- S:
-
The system aborts command execution.
- O:
-
Determine the cause by reading the messages that precede this one, and by checking the R/3 system log.
-
KAJM1852-E
The job cannot be deleted because it is active or ready.
The specified job is active or ready.
- S:
-
If no job count was specified, the system continues processing subsequent jobs. If no subsequent job exists or if a job count is specified, the system aborts command execution.
- O:
-
Check the status of the job to be deleted. When the job is finished or terminated, execute the jr3bjdel command. If you want to delete an active or ready job, wait until job execution ends or use the jr3bjcan command to cancel the job, and then delete it.
-
KAJM1870-I
The child job was detected. (job name: job-name, job count: job-count, child job name: child-job-name, child job count: child-job-count)
JP1/AJS3 for EAP detected a child job of a finished or terminated job during completion monitoring of parent and child jobs.
- S:
-
The system executes completion monitoring of the detected child job (completion monitoring is extended).
-
KAJM1871-W
The child job was undetectable. (job name: job-name, job count: job-count)
JP1/AJS3 for EAP failed to detect the child job of a job that is deleted. Immediately before this message, a KAJM0812-E or KAJM0813-E message appears indicating the cause of the error.
If this message appears for a child job that is detected during completion monitoring of parent and child jobs, the parent job may have been set at registration so that it is automatically deleted at normal end.
- S:
-
The system continues completion monitoring and returns 1 to indicate that the result of at least one job could not be checked.
- O:
-
Register the target job so that it will not be deleted during completion monitoring.
-
KAJM1872-W
The maximum number of monitored jobs was exceeded. (maximum number: maximum-number)
When maximum-number is 100, JP1/AJS3 for EAP can monitor the completion of one job that is released from JP1 and 99 child jobs generated during its execution.
- S:
-
The system does not detect any subsequent child jobs. The system continues completion monitoring and returns 1 to indicate that the result of at least one job could not be checked.
- O:
-
Divide jobs or take other measures to ensure that the number of jobs being monitored does not exceed the maximum limit.