6.2.1 Messages common to all JP1/AJS3 for EAP functions : Job Management Partner 1/Automatic Job Management System 3 for Enterprise Applications Description, User's Guide and Reference

KAJM0001-I

Usage:format

Display of a command format was requested.

KAJM0002-E

Invalid option. (option:option)

An invalid option was specified.

S:: The system aborts command execution.
O:: Specify the correct option and execute the command again.

KAJM0003-E

Argument must be specified for this option. (option:option)

No argument was specified for the option.

S:: The system aborts command execution.
O:: Specify an argument for the option and execute the command again.

KAJM0004-E

Value of option is invalid. (option:option)

The value specified for the option is invalid.

S:: The system aborts command execution.
O:: Specify the correct argument for the option and execute the command again.

KAJM0005-E

Option is duplicated. (option:option)

An option that cannot be duplicated has been specified twice.

S:: The system aborts command execution.
O:: Specify the option correctly and execute the command again.

KAJM0006-E

Required option is missing.

A required option was not specified.

S:: The system aborts command execution.
O:: Specify the required option and execute the command again.

KAJM0007-E

Mutually-exclusive options are specified.

Some of the specified options are mutually exclusive.

S:: The system aborts command execution.
O:: Correct the option specification and execute the command again.

KAJM0008-E

In the release of the R/3 system at the connection destination, this option is not supported. (release:release, option:option)

The specified option is invalid on the R/3 system you connect to.

S:: The system aborts command execution.
O:: Check if the specified option is supported by the appropriate R/3 system release.

KAJM0009-E

In the release of the R/3 system at the connection destination, this command is not supported. (release:release)

An attempt was made to execute a command that is not supported by the target R/3 system.

S:: The system aborts command execution.
O:: Check the release of the target R/3 system.

KAJM0010-W

The file that defines the environment contains an invalid key or section name. (section: section-name, key: key-name)

The environment setup file contains an invalid value entry.

S:: The system ignores the invalid value in the environment setup file and continues to execute the command.
O:: Ignore the warning or correct the contents of the environment setup file and execute the command again.

KAJM0011-W

The file that defines the environment contains an error in a key value. (section: section-name, key: key-name)

The environment setup file contains an incorrect key value.

S:: The system uses the default value specified by the conf.model file and continues with command execution.
O:: Ignore the warning or correct the contents of the environment setup file and execute the command again.

KAJM0012-W

The file that defines the environment contains a duplicated key or section name. (section: section-name, key: key-name)

The environment setup file contains duplicate values.

S:: The system uses the first-specified value and continues with command execution.
O:: Ignore the warning or correct the contents of the environment setup file and execute the command again.

KAJM0013-W

The file that defines the environment contains an invalid string.

The environment setup file contains an invalid character string.

S:: The system ignores the invalid character string and continues with command execution.
O:: Ignore the warning or correct the contents of the environment setup file, and execute the command again.

KAJM0014-E

This option cannot be used because the RFC library corresponding to the extended password is not set. (option: option)

An attempt was made to execute a command with the -p2 option specified (or with Use an extended password selected during execution from a custom job) without an RFC library having been set for the extended password.

S:: The system aborts command execution.
O:: Use the jr3chrfc command to set an RFC library for the extended password, and then execute the command again.

KAJM0020-E

The default information file for the R/3 connection contains an invalid key or section name. (section: section-name, key: key-name)

The R/3 default connection destination information file (r3defcon file) contains an incorrect value.

S:: The system aborts command execution.
O:: Correct the contents of the R/3 default connection destination information file (r3defcon file) and execute the command again.

KAJM0021-E

The default information file for the R/3 connection contains an error in a key value. (section: section-name, key: key-name)

The R/3 default connection destination information file (r3defcon file) contains an incorrect key value.

S:: The system aborts command execution.
O:: Correct the contents of the R/3 default connection destination information file (r3defcon file) and execute the command again.

KAJM0022-E

The default information file for the R/3 connection contains a duplicated key or section name. (section: section-name, key: key-name)

The R/3 default connection destination information file (r3defcon file) contains duplicate values.

S:: The system aborts command execution.
O:: Correct the contents of the R/3 default connection destination information file (r3defcon file) and execute the command again.

KAJM0023-E

The default information file for the R/3 connection lacks a required section or key.

The R/3 default connection destination information file (r3defcon file) does not contain a required key name entry or section name entry.

S:: The system aborts command execution.
O:: Correct the contents of the R/3 default connection destination information file (r3defcon file) and execute the command again.

KAJM0024-E

The default information file for the R/3 connection contains mutually-exclusive sections or keys.

The R/3 default connection destination information file (r3defcon file) contains mutually exclusive key name entries or section name entries.

S:: The system aborts command execution.
O:: Correct the contents of the R/3 default connection destination information file (r3defcon file) and execute the command again.

KAJM0025-E

The default information file for the R/3 connection contains an invalid string.

The R/3 default connection destination information file (r3defcon file) contains an invalid character string.

S:: The system aborts command execution.
O:: Correct the contents of the R/3 default connection destination information file (r3defcon file) and execute the command again.

KAJM0026-E

The key specified in the default information file for the R/3 connection cannot be used because the RFC library corresponding to the extended password is not set. (section: section-name, key: key-name)

An attempt was made to execute a command with the Passwd2 key specified for the R/3 default connection destination information file without an RFC library having been set for the extended password.

S:: The system aborts command execution.
O:: Use the jr3chrfc command to set an RFC library for the extended password, and then execute the command again.

KAJM0100-E

Insufficient memory.

System memory was insufficient during command execution.

S:: The system aborts command execution.
O:: Ensure that sufficient system memory is available, and execute the command again.

KAJM0101-E

File cannot be accessed. (file: filename)

The file could not be accessed.

S:: The system aborts command execution.
O:: Ensure that the file indicated by filename can be accessed with the command-executing user's permission.

KAJM0102-E

There is not enough free space for creating or extending a file. (file: filename)

Disk space was insufficient during command execution.

S:: The system aborts command execution.
O:: Check for available space on the disk that is selected for the creation or extension of the indicated file.

KAJM0103-W

File that defines the environment cannot be accessed. (file: filename)

The environment setup file could not be accessed.

S:: The system uses the default value specified by the conf.model file and continues with command execution.
O:: Ensure that an environment settings file exists and can be accessed with the command-executing user's permission.

KAJM0104-W

Trace file cannot be accessed. (file: filename)

The trace file could not be accessed.

Another possibility is that the temporary file used for outputting trace files could not be accessed.

A temporary directory is used when outputting trace files.

Under Windows, the folder specified by the TMP environment variable is used. In the TMP environment variable, specify a folder that can be accessed using the permissions of the user executing the command (if the default JP1/AJS service account is used when a JP1/AJS job is executed, the folder specified in the TMP system environment variable is used).

S:

The system continues with command execution. However, trace information output may not be sent to the trace file.

O:

Ensure that the trace file can be accessed with the permissions of the user executing the command.

Altenatively, ensure that the folder specified by the TMP environment variable as the temporary folder for outputting trace files can be accessed with the permissions of the user executing the command.

KAJM0105-E

Failed to access the default information file for the R/3 connection. (file: filename)

The R/3 default connection destination information file (r3defcon file) could not be accessed.

S:: The system aborts command execution.
O:: Ensure that the R/3 default connection destination information file (r3defcon file) exists and can be accessed with the command-executing user's permission.

KAJM0106-W

There is not enough free space for creating or extending a trace file. (file: filename)

Disk space was insufficient while trace information was being output to the trace file.

S:: The system continues with command execution. However, the trace information may not be sent to the trace file.
O:: Check for available space on the disk containing the trace file.

KAJM0107-E

After the character code conversion, the length of the character string exceeded the range that can be specified for the option. (option: option, number of bytes after the conversion: number-of-bytes-after-the-conversion)

After the character code conversion, the length of the character string exceeded the range that can be specified for the option.

(S): The system aborts command execution.
(O): Ensure that the specified argument is within the range that can be specified for the character string after the Shift-JIS conversion. If number-of-bytes-after-the-conversion is 4,096, the number of bytes after the conversion is 4,096 bytes or more.

KAJM0108-E

An attempt to convert the character code failed. Execution will be terminated.

An attempt to convert the character code failed.

(S): The system aborts command execution.
(O): Ensure that the character code for the specified argument matches the LANG environment variable.

KAJM0109-W

An attempt to convert the character code failed. Check the contents of the job log.

An attempt to convert the character code for the job log failed.

(S): The system continues with command execution.
(O): Check the contents of the relevant job log on the SAP system. If part of the job log contents controls subsequent jobs, ensure that the conversion does not affect subsequent processing.

KAJM0110-W

An attempt to convert the character code failed.

(S)

The system continues with command execution.

(O)

Take either of the following actions.

If there is a subsequent message:

An attempt to convert the character code for the subsequent message failed. Check the contents of the subsequent message.
If this message is output after the SAP system information is displayed by the jr3bjrep and jr3bjsho commands:

An attempt to convert the character code failed because the displayed SAP system information contains a character code that does not belong to the Shift-JIS encoding supported by the command. Check the information on the SAP system.

KAJM0112-E

Preparation for character code conversion failed.

The required combination of character code conversion does not exist.

(S)

The system aborts command execution.

(O)

Ensure that there are a sufficient number of files to be opened by checking the kernel parameter regarding the number of files, and then execute the command again.

If the status still does not recover, gather the information needed to investigate the cause of the problem, and then contact the system administrator.

KAJM0113-E

An attempt to load the RFC library failed. (file: file-name, reason: cause, function: function-name, maintenance code: maintenance-code)

An error occurred while the RFC library was being loaded.

The following information is output to individual items in the message:

file-name: Absolute path to the RFC library
cause: Text that indicates the cause of the error

no such file(s): The file or files do not exist.

invalid library(ies): The library or libraries are invalid.

the CRT libraries are not installed: The necessary CRT libraries are not installed.

system error: A system error occurred.
function-name: Name of the API of the OS in which the error occurred
maintenance-code: Error code returned from the API of the OS

(S)

The system aborts command execution.

(O)

For the RFC library that was output to file-name in the message, remove the cause that was output to cause in the message, and then execute the command again.

The following shows how to handle individual causes that can be output to cause in the message:

no such file(s)

Ensure that the RFC library obtained from the provider is located in the path that was output to file-name in the message. If any problem exists, follow the procedures described in 2.4 SAP NetWeaver RFC Library setup to locate the correct RFC library.
invalid library(ies)

Ensure that the RFC library that was output to file-name in the message is correct. (Ensure that the library corresponds to the OS and architecture of the running environment, and that the version of the library is the required version for operating the product.) If any problem exists, follow the procedures described in 2.4 SAP NetWeaver RFC Library setup to locate the correct RFC library.
the CRT libraries are not installed

Ensure that the C runtime library required for RFC library operation has been installed. If any problem exists, follow the procedures described in 2.4 SAP NetWeaver RFC Library setup to locate the correct C runtime library.
system error

Collect maintenance information, and then contact the system administrator.

If the problem still remains after performing the procedure above, collect the maintenance information, and then contact the system administrator.

For details about the version of the RFC library required for using the product and how to obtain the RFC library, see the product manual or Release Notes.

KAJM0114-E

An attempt to load the RFC library failed. (file: file-name, function: function-name, maintenance code: maintenance-code, maintenance message: maintenance-message)

An error occurred while the RFC library was being loaded.

The following information is output to individual items in the message:

file-name: Absolute path to the RFC library
function-name: Name of the API of the OS in which the error occurred
maintenance-code and maintenance-message: Error code returned from the API of the OS (0 might be always output, depending on the OS), and the corresponding error message

(S)

The system aborts command execution.

(O)

The RFC library obtained from the provider is located in the path that was output to file-name in the message. Check whether the library is correct (whether it corresponds to the OS and architecture of the running environment, or whether the version is the required version for operating the product). If there is a problem, remove the problem, and then execute the command again.

If the problem still remains after performing the procedure above, collect the maintenance information, and then contact the system administrator.

For details about the versions of the RFC library required for operating the product, and how to obtain the RFC library, see the manual or Release Notes.

KAJM0115-E

The RFC library version is invalid. (file: file-name, version: major-version.minor-version.patch-level)

The version of the RFC library is not the version required for operating the product.

In file-name in the message, the absolute path to the RFC library is output. In major-version.minor-version.patch-level in the message, the version information of the RFC library is output.

(S)

The system aborts command execution.

(O)

In the path that was output to file-name in the message, store the RFC library whose version is required for operating the product, and then execute the command again.

For details about the versions of the RFC library required for operating the product, and how to obtain the RFC library, see the manual or Release Notes.

KAJM0116-E

The sapnwrfc.ini file cannot be accessed. (file: file-name, maintenance code: maintenance-code)

An attempt to access the sapnwrfc.ini file failed.

In file-name in the message, the absolute path to the sapnwrfc.ini file is output. In maintenance-code in the message, an error code returned from the API of the OS is output.

(S)

The system aborts command execution.

(O)

Ensure that the sapnwrfc.ini file output to file-name in the message exists, and that the file can be accessed with the permissions of the user executing the command.

If the sapnwrfc.ini file does not exist, create the file in one of the search folders for the sapnwrfc.ini file, and then execute the command again. If you do not have a permission required to execute the command, obtain the permission, and then execute the command again.

KAJM0600-E

You do not have permission to execute the command.

An attempt to execute the command was made by a user who does not have Administrator permissions.

If the user account control function (UAC) of the OS is enabled, execute the command from the command prompt of the standard role.

This message is output for the Windows version only.

S:

The system aborts command execution.

O:

Have a user who has Administrator permissions execute the command again.

If the user account control function (UAC) of the OS is enabled, execute the command at the command prompt using Administrator permissions.

KAJM0601-I

The RFC library setting was changed.

The RFC library setting was successfully changed by executing the jr3chrfc command.

S:: The command ends normally.

KAJM0602-E

An attempt to open the RFC library status management file has failed. (file: filename, maintenance code: maintenance-code)

An unrecoverable error occurred when opening the RFC library status management file.

For filename in the message, the absolute path to the RFC library status management file is output. For maintenance-code in the message, the API error code returned by the OS is output.

S:: The system aborts command execution.
O:: Verify that the path to the RFC library status management file is correct, and then execute the command again. If the status still does not recover, delete the RFC library status management file, use the jr3chrfc command to set up the file again, and then execute once more the command that caused the error.

KAJM0603-E

An attempt to lock the RFC library status management file has failed. (file: filename, maintenance code: maintenance-code)

The possible causes of the error are as follows:

During installation or patch execution, or while an RFC library setting was being changed using the jr3chrfc command, the JP1/AJS3 for EAP command that references the RFC library settings was executed.
During execution of the JP1/AJS3 for EAP command that references the RFC library settings, an RFC library setting was changed using the jr3chrfc command.

For filename in the message, the absolute path to the RFC library status management file is output. For maintenance-code in the message, the API error code returned by the OS is output.

S:: The system aborts command execution.
O:: After changing or referencing the RFC library setting is completed, execute the command again. If the status still does not recover, delete the RFC library status management file, use the jr3chrfc command to set up the file again, and then execute once more the command that caused the error.

KAJM0604-E

An attempt to read the RFC library status management file has failed. (file: filename, maintenance code: maintenance-code)

An unrecoverable error occurred while reading the RFC library status management file.

For filename in the message, the absolute path to the RFC library status management file is output. For maintenance-code in the message, the API error code returned from the OS is output.

S:: The system aborts command execution.
O:: Verify that the path to the RFC library status management file is correct, and then execute the command again. If the status still does not recover, delete the RFC library status management file, use the jr3chrfc command to set up the file again, and then execute once more the command that caused the error.

KAJM0605-E

An attempt to write to the RFC library status management file has failed. (file: filename, maintenance code: maintenance-code)

During a change to an RFC library setting using the jr3chrfc command, an unrecoverable error occurred while writing to the RFC library status management file.

For filename in the message, the absolute path to the RFC library status management file is output. For maintenance-code in the message, the API error code returned by the OS is output.

S:: The system aborts command execution.
O:: Verify that the path to the RFC library status management file is correct and that there is available space on the disk, and then execute the command again. If the status still does not recover, delete the RFC library status management file, use the jr3chrfc command to set up the file again, and then execute once more the command that caused the error.

KAJM0606-E

The contents of the RFC library status management file are invalid. (file: filename)

The RFC library status management file contains an error.

For filename in the message, the absolute path to the RFC library status management file is output.

S:: The system aborts command execution.
O:: Use the jr3chrfc command to set up the RFC library setting again, and then execute the command. If the status still does not recover, delete the RFC library status management file, use the jr3chrfc command to set up the file again, and then execute once more the command that caused the error.

KAJM0607-E

There is not enough free space to copy the RFC library file. (source: filename, target: filename)

Disk space ran out while the RFC library file was being copied.

For filename in the inserted source paragraph, the absolute path to the RFC library file of the copy source is output. For filename in the inserted target paragraph, the absolute path to the copy destination RFC library file is output.

This message is output when an RFC library setting is changed using the Windows version of the jr3chrfc command.

S:: The system aborts command execution.
O:: Delete unnecessary files to free up some disk space at the copy destination, and then execute the jr3chrfc command again.

KAJM0608-E

The RFC library file cannot be copied. (source: filename, target: filename, maintenance code: maintenance-code)

An error that is not attributable to a lack of disk space occurred while the RFC library file was being copied.

For filename in the inserted source paragraph, the absolute path to the RFC library file of the copy source is output. For filename in the inserted target paragraph, the absolute path to the copy destination RFC library file is output. For maintenance-code in the message, the API error code returned from the OS is output.

This message is output when an RFC library setting is changed using the Windows version of the jr3chrfc command.

S:: The system aborts command execution.
O:: Delete the file at the copy destination, and then execute the command again.

KAJM0609-E

The symbolic link file cannot be created. (file: filename, maintenance code: maintenance-code)

An error occurred during creation of the symbolic link file.

For filename in the message, the absolute path to the symbolic link file the system is attempting to create is output. For maintenance-code in the message, the API error code returned from the OS is output.

This message is output when an RFC library setting is changed using the UNIX version of the jr3chrfc command.

S:: The system aborts command execution.
O:: Delete the symbolic link file, and then execute the command again.

KAJM0700-E

An attempt to open the RFC library status management file has failed. (file: filename, maintenance code: maintenance-code, maintenance message: maintenance-message)

An unrecoverable error occurred when opening the RFC library status management file.

For filename in the message, the absolute path to the RFC library status management file is output. For maintenance-code and maintenance-message in the message, the API error code returned from the OS and the corresponding error message are output.

S:: The system terminates installation or patch execution.
O:: Check whether the path to the RFC library status management file is correct, and then perform installation or patch execution. If the status still does not recover, delete the RFC library status management file and then perform installation or patch execution. After that, use the jr3chrfc command to set up the RFC library status management file again.

KAJM0701-E

An attempt to lock the RFC library status management file has failed. (file: filename, maintenance code: maintenance-code, maintenance message: maintenance-message)

Installation or patch execution was performed while using a JP1/AJS3 for EAP command to reference or change an RFC library setting.

For filename in the message, the absolute path to the RFC library status management file is output. For maintenance-code and maintenance-message in the message, the API error code returned from the OS, and the corresponding error message are output.

S:: The system terminates installation or patch execution.
O:: After changing or referencing the RFC library setting is completed, perform installation or patch execution again. If the status still does not recover, delete the RFC library status management file and then perform installation or patch execution. After that, use the jr3chrfc command to set up the RFC library status management file again.

KAJM0702-E

An attempt to read the RFC library status management file has failed. (file: filename, maintenance code: maintenance-code, maintenance message: maintenance-message)

An unrecoverable error occurred while reading the RFC library status management file.

For filename in the message, the absolute path to the RFC library status management file is output. For maintenance-code and maintenance-message in the message, the API error code returned from the OS, and the corresponding error message are output.

S:: The system terminates installation or patch execution.
O:: Check whether the path to the RFC library status management file is correct, and then perform installation or patch execution. If the status still does not recover, delete the RFC library status management file and then perform installation or patch execution. After that, use the jr3chrfc command to set up the RFC library status management file again.

KAJM0703-E

The contents of the RFC library status management file are invalid. (file: filename)

The RFC library status management file contains an error.

For filename in the message, the absolute path to the RFC library status management file is output.

S:: The system terminates installation or patch execution.
O:: Delete the RFC library status management file and then perform installation or patch execution. After that, use the jr3chrfc command to set up the RFC library status management file again.

KAJM0704-E

There is not enough free space to copy the RFC library file. (source: filename, target: filename)

Disk space ran out while the RFC library file was being copied.

For filename in the source message, the absolute path to the RFC library file of the copy source is output. For filename in the target message, the absolute path to the copy destination RFC library file is output.

S:: The system terminates installation or patch execution.
O:: Delete unnecessary files to free up some disk space at the copy destination, and then perform installation or patch execution again.

KAJM0705-E

The RFC library file cannot be copied. (source: filename, target: filename, maintenance code: maintenance-code, maintenance message: maintenance-message)

An error that is not attributable to a lack of disk space occurred while the RFC library file was being copied.

For filename in the source message, the absolute path to the RFC library file of the copy source is output. For filename in the target message, the absolute path to the copy destination RFC library file is output. For maintenance-code and maintenance-message in the message, the API error code returned from the OS and the corresponding error message are output.

S:: The system terminates installation or patch execution.
O:: Delete the RFC library status management file, and then perform installation or patch execution again.

KAJM0801-E

Cannot connect to the R/3 system. (address: destination-name, host: host-name, system No.: system-number)

A communication error occurred before RFC connection with the R/3 system was established.

Immediately after this message, the name of the function where the error occurred and a KAJM0802-E error message providing detailed information are output.

The possible causes of the error are as follows:

The RFC connection information is incorrect (for example, the system number is incorrect and the host name cannot be resolved).
The R/3 system is inactive.
The R/3 system is too busy to accept an RFC request.
The network settings are incorrect.

S:

The system attempts to reconnect to the R/3 system if retry is specified.

If retry is not specified, the system aborts command execution.

O:

Consider specifying retry if no retry is specified (version 07-00 and earlier do not retry by default).

KAJM0802-E

Operation : function

detailed-information ...

An error occurred when the RFC API (communication function provided by SAP) was called.

A message appears that indicates the name of the function where the error occurred and detailed information about the RFC API error. The meaning of the values in the message is as follows:

code: Integer for the RFC return code
group: Integer for identifying key
key: Code for identifying the error (127 bytes or less)
message: Text that describes the error (511 bytes or less)
abapMsgClass: ABAP message class (20 bytes or less)
abapMsgType: ABAP message type (1 byte or less)
abapMsgNumber: ABAP message number (3 bytes or less)
abapMsgV1: Detail field of the ABAP message (text of 50 bytes or less)
abapMsgV2: Detail field of the ABAP message (text of 50 bytes or less)
abapMsgV3: Detail field of the ABAP message (text of 50 bytes or less)
abapMsgV4: Detail field of the ABAP message (text of 50 bytes or less)

For these values, the values of the members in the RFC_ERROR_INFO structure are specified without changes. This structure stores RFC API error information. (For details about the RFC, see the manual for the SAP system.)

<Supplement>

This message is output as a detailed message of KAJM0801-E, KAJM0803-E, and KAJM0804-E.
The number of bytes for the detailed information about the RFC API error indicates the size in which \0 is not included.

S:

The system aborts command execution.

O:

Identify the cause of the error and correct the problem.

KAJM0803-E

A communication error occurred with the R/3 system. (address: destination-name, host: host-name, system No.: system-number)

An error occurred when JP1/AJS3 for EAP called the RFC API (communication function provided by SAP).

Immediately after this message, the name of the function in which the error occurred and a KAJM0802-E error message providing detailed information are output.

The possible causes of the error are as follows:

The R/3 system is inactive.
The R/3 system is too busy to accept an RFC request.
The network settings are incorrect.

S:: If the communication error occurred while establishing communication or monitoring the end of a job and retry is specified, the system attempts to reconnect to the R/3 system. If the error occurred in other circumstances or if no retry is specified, the system aborts command execution.
O:: Consider specifying retry if no retry is specified (version 07-00 and earlier do not retry by default).

KAJM0804-E

Cannot log on to the R/3 system. (client: client, user: user-name, language: language-name)

A logon error occurred when JP/AJS3 for EAP attempted to establish an RFC connection with the R/3 system.

Immediately after this message, a KAJM0802-E message appears indicating the name of the function where the error occurred and providing detailed information about the error.

The possible causes of the error are as follows:

The RFC connection information is incorrect (for example, a non-existent user or incorrect password is specified).
The user is locked out.
The user was not granted the S_RFC permission correctly.
An extended password containing lower-case characters is defined in the SAP system based on SAP NetWeaver 7.0 and later, but connection information (-p option or Passwd key of the r3defcon file) that does not correspond to the extended password is specified.

S:: The system aborts command execution.
O:: Check the logon information used to log on to the R/3 system specified by the command.

KAJM0805-I

Now recovering connection with the R/3 system. (address: destination-name, host: host-name, system No.: system-number, retry-time: retry-time-in-minutes min., retry-count: number-of-retries times)

The connection with the R/3 system is now being recovered.

retry-time in the message is output when the RetryTime key specified in the command section of the environment setup file is valid. number-of-retries in the message is output when the RetryCount key in the command section of the environment setup file is valid.

S:: JP1/AJS3 for EAP reconnects with the R/3 system. If reconnection is performed within the retry-time or number-of-retries limit, JP1/AJS3 for EAP continues command processing. Otherwise, the system aborts command execution.

KAJM0806-I

Connection was recovered with the R/3 system. (address: destination-name, host: host-name, system No.: system-number)

JP1/AJS3 for EAP has reconnected with the R/3 system.

KAJM0807-E

Time-out occurred in the connection with the R/3 system. (address: destination-name, host: host-name, system No.: system-number)

JP1/AJS3 for EAP could not restore a connection with the R/3 system within the specified reconnection retry time.

S:: The system aborts command execution.
O:: Read the messages that are 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 retry time (RetryCount key or RetryTime key in the command section of the environment setup file) is appropriate.

KAJM0810-E

The external management interface is not supported. (interface: interface-name, version: version)

The external management interface version of the destination R/3 system does not agree with the version asumed by JP1/AJS3 for EAP.

For interface-name and version in the message, the interface name and version of the external management interface are output. However, the version is not output if the version of the external management interface is not set.

S:

The system aborts command execution.

O:

Check the external management interface version of the destination R/3 system.

Note: The interface name and version number are provided with the message only when they can be determined.

KAJM0811-E

Cannot log on to an external management interface. (interface: interface-name, version: version)

An attempt to log on to the R/3 system external management interface was denied (BAPI error).

The possible causes of the error are as follows:

The connection destination R/3 system does not support the interface.
The user was not granted the S_XMI_PROD permission correctly.

S:

The system aborts command execution.

O:

Check the following:

Check whether the release and patch level of SAP Basis (SAP WebAS) of the connection destination R/3 system satisfy the prerequisites.
Check whether the user specified in the R/3 logon information is authorized to log on to the external management interface.

Note: The interface name and version number are provided with the message only when they can be determined.

KAJM0812-E

Error occurred at the external management interface. (interface: interface-name, version: version)

The R/3 system external management interface returned an error. Immediately after this message, a KAJM0813-E message appears indicating the name of the function where the error occurred and the exception code.

S:

If more than one process was requested, the system continues with the subsequent process.

O:

Check the R/3 system log to identify the cause of the error, fix the problem, and then execute the command again.

Note: The interface name and version number are provided with the message only when they can be determined.

KAJM0813-E

Function: function, Exception: exception

detailed-information

A general-purpose module of the R/3 system returned an error.

The name of the function where the error occurred and the exception code are output.

For BAPI, the detailed information about the external management interface error is output after Detail. The language used for the message depends on the language (-l option specification value) specified during logon to the SAP BW system. The meaning of the values in the message is as follows:

Type: One of the following characters (one byte) that indicates the importance of the message

S: Normal

E: Error

W: Warning

I: Information

A: Forced termination
Id: Message class (20 bytes or less)
Number: Error code for identifying the error (three bytes or less)
Message: Description of the error (220 bytes or less)
LogNo: Log number for identifying the application log (20 bytes or less)
LogMsgNo: Message number for identifying the message output to the application log (six bytes or less)

For these values, the values of the members in the BAPIRET2 structure that contains the BAPI error are specified without changes. For details about BAPI, see the R/3 system documentation. For details about the specifications of the BAPI that is called, see the object navigator (SE80) documentation of the R/3 system, the BAPI browser documentation (BAPI), or the R/3 documentation.

S:: If more than one process was requested, the system continues with the subsequent process. If only one process is requested, the system aborts the process.
O:: Check the R/3 system log to identify the cause of the error, fix the problem, and then execute the command again.

KAJM0820-E

There is no authority to perform this operation.

The specified R/3 user is not authorized to execute this operation.

S:: If more than one process was requested, the system continues with the subsequent process.
O:: If more than one process was requested, the system continues with the subsequent process. If only one process was requested, the system aborts the process.

KAJM0830-W

Failed to change an audit-level.

The audit level was not changed.

S:: The system continues processing without changing the audit level.
O:: Check the R/3 system log and other relevant information to investigate the cause of the problem.

KAJM0900-E

Command terminated abnormally. (command: command-name)

An error occurred in JP1/AJS3 for EAP during command processing.

S:: The system aborts command execution.
O:: Gather the information needed to investigate the cause of the problem, and then contact the system administrator.

KAJM0901-E

The user canceled the command. (command: command-name)

Command processing was aborted due to a Ctrl-C signal sent from the user or for some other reason during command execution.

S:: The system aborts command execution.

KAJM0902-E

The product is not installed correctly.

JP1/AJS3 for EAP is not correctly installed.

S:: The system aborts command execution.
O:: Reinstall JP1/AJS3 for EAP.

KAJM0990-E

The evaluation period of (p.p.name) Trial Version expired.

An attempt was made to execute the command after the trial version had expired.

S:: The system aborts command execution.

KAJM0992-E

The product information could not be acquired. (Detailed information: function-name, return-value)

Command execution failed because of insufficient resources or because the environment is invalid.

S:

The system aborts command execution.

O:

Check whether system resources are insufficient.

If so, secure sufficient resources, and then execute the command again. If the problem cannot be resolved, uninstall and then reinstall JP1/AJS3 for EAP, and then execute the command again. If the problem is still not resolved, collect data, and then contact the system administrator.