10.3.1 Messages beginning with KNBB

The installation was interrupted because an attempt was made to install a JP1/AJS3 product on a platform that does not meet the applicable operating system requirements. The JP1/AJS3 product cannot be installed on this platform.

(S)

The system aborts the installation.

(O)

Check the applicable operating system for the JP1/AJS3 product and install it on that OS.

For information on the applicable operating system, see the release notes.

Installation was interrupted because an error occurred during installation.

The following factors may have caused the problem.

• Disc defect of Hitachi Integrated Installer

• If you are using the Hitachi Integrated Installer copied to a local disc, copying has failed.

(S)

The system aborts the installation.

(O)

If you have another Hitachi Integrated Installer disc, install JP1/AJS3 again using this disc.

If you are using the Hitachi Integrated Installer copied to a local disc, copy it again and install JP1/AJS3. Or, install JP1/AJS3 using the Hitachi Integrated Installer disc.

If the problem persists, collect the following data and contact your system administrator.

• Details of the operation performed

• Dialog displayed on the screen

• Installation log

If overwriting the installation or upgrading the installation, collect the following data as well.

• Execution results of the data collection tool

The installation was interrupted because the license management information failed to be set.

(S)

The system aborts the installation.

(O)

Collect the following data and contact your system administrator.

• Details of the operation performed

• Dialog displayed on the screen

• Installation log

If overwriting the installation or upgrading the installation, collect the following data as well.

• Execution results of the data collection tool

The installation could not be performed because the user who performed the installation does not have administrative privileges.

(S)

The system aborts the installation.

(O)

A user who has administrative privileges should install JP1/AJS3 products.

An error occurred during the setup that JP1/AJS3 automatically performs during installation.

The following factors may be the cause:

• The port number used by JP1/AJS3 for Cloud Service Applications is already being used by another program.

• Insufficient capacity on the system drive (%systemdrive%).

• Insufficient capacity on the destination drive for the installation.

(S)

The system aborts the installation.

(O)

Eliminate the cause and reinstall JP1/AJS3.

If the problem persists, collect the following data and contact your system administrator.

• Details of the operation performed

• Hard copy of the dialog box displayed on the screen

• Installation log

If overwriting the installation or upgrading the installation, collect the following data as well.

• Execution results of the data collection tool

The installation was interrupted because the file used in the installation could not be opened.

The following factors may be the cause:

• Insufficient capacity on the system drive (%systemdrive%)

• The folder set in the system environment variable TEMP does not have write or read permissions.

Note: The file name that caused the error is output to maintenance information.

(S)

The system aborts the installation.

(O)

Eliminate the cause and reinstall JP1/AJS3.

If the problem persists, collect the following data and contact your system administrator.

• Details of the operation performed

• Dialog displayed on the screen

• Click Properties and Security of the folder set in the system environment variable TEMP, and make a hard copy of the Security screen.

• Installation log

If overwriting the installation or upgrading the installation, collect the following data as well.

• Execution results of the data collection tool

The installation was interrupted because the file used in the installation could not be read.

The following factors may be the cause:

• The folder set in the system environment variable TEMP does not have read permissions.

Note: The file name that caused the error is output to maintenance information.

(S)

The system aborts the installation.

(O)

Eliminate the cause and reinstall JP1/AJS3.

If the problem persists, collect the following data and contact your system administrator.

• Details of the operation performed

• Dialog displayed on the screen

• Click Properties and Security of the folder set in the system environment variable TEMP, and make a hard copy of the Security screen.

• Installation log

If overwriting the installation or upgrading the installation, collect the following data as well.

• Execution results of the data collection tool

An error occurred during the unsetup process automatically performed by JP1/AJS3 during uninstallation.

The following factors may be the cause:

• An invalid value is set in the preferences file.

• Files required for uninstallation have been deleted.

(S)

The system aborts the installation.

(O)

If an invalid value is set in the preferences file, enter the correct value. Otherwise, overwrite the installation once and uninstall again.

If the problem persists, collect the following data and contact your system administrator.

• Details of the operation performed

• Make a hard copy of the dialog box displayed on the screen

• Execution results of the data collection tool

Installation failed because JP1/Base is not installed.

(S)

The system aborts the installation.

(O)

Install JP1/Base version meets the prerequisites, and then restart the installation of AJS3. For the required JP1/Base version, see the release notes.

The installation was interrupted because the version of JP1/Base installed does not meet the prerequisite requirements of the product.

(S)

The system aborts the installation.

(O)

Install JP1/Base version meets the prerequisites, and then restart the installation of AJS3. For the required JP1/Base version, see the release notes.

The system checks for files on the Hitachi Integrated Installer disc that cannot be found.

(S)

The system waits for the response.

(O)

If you wish to continue the installation, select Yes after inserting the Hitachi Integrated Installer disc into the drive.

If you do not wish to continue the installation, select No to terminate the installation.

If the problem persists after inserting the Hitachi Integrated Installer disc, collect the following data and contact your system administrator.

• Details of the operation performed

• Dialog displayed on the screen

• Installation log

If overwriting the installation or upgrading the installation, collect the following data as well.

• Execution results of the data collection tool

The system confirms that the product installation is on a platform that meets the applicable OS requirements.

(S)

The system waits for the response.

(O)

Click the Yes button to finish the installation.

field-name is not specified.

(S)

The system aborts the process.

(O)

Enter the value in field-name and try again.

The value was entered incorrectly in field-name.

(S)

The system aborts the process.

(O)

Re-enter the value of minimum-value - maximum-value in field-name.

Incorrect format value is specified in field-name.

(S)

The system aborts the process.

(O)

Re-enter the correct format value in field-name.

One of the following operations failed due to duplicate variable names:

• Registering a definition

• Displaying the confirmation screen

• Updating the confirmation screen

(S)

The system aborts the process.

(O)

After resolving the duplication, click the Register button, the Display confirmation screen button, or the Update button in the confirmation screen.

• If importing a definition file:

  The import failed because the format of the definition file being imported is invalid.

  If a value that cannot be entered is specified for the JSON key corresponding to an input or specified value on each screen, the text field will display the portion of the value that was successfully loaded^#, and checkboxes and radio buttons will be shown in their default states.

#: If the file contains characters that cannot be read properly by the Web browser, the characters will be garbled and displayed on the screen.

• If importing a variable information file:

  The import failed due to the invalid format of the variable information file.

(S)

The system aborts the process.

(O)

• If importing a definition file

  Before importing, make sure that the specified file is the one exported from the relevant definition. The file must meet the following conditions:

  - It is in JSON format.

  - It was exported from the relevant definition screen.

• If importing a variable information file

  Before importing, make sure that the specified file is a variable information file.

One of the following operations failed because the maximum number of variables that can be registered was exceeded:

• Registering the definition

• Displaying the confirmation screen

• Updating the confirmation screen

(S)

The system aborts the process.

(O)

After deleting some variables, click the Register button, the Display confirmation screen button, or the Update button in the confirmation screen.

The maximum values of variables that can be registered are as follows:

• Custom input items for JP1/AJS3 - View

  15 items

• Environment variables for the execution host

  32 items

Login failed because the value entered for the JP1 username or password was invalid.

(S)

The system aborts the process.

(O)

Make sure that the value entered is valid, and enter the JP1 username and password registered on the Access Control Server to which it is connected, and then log in.

This message reports that access to the JP1/AJS3 for Cloud Service Applications server application failed. The following factors may be the cause.

• An error occurred during the communication process with the HTTP server or application server.

• The HTTP server or application server is not running.

• The HTTP server or application server is busy.

• The HTTP server or application server is not ready to connect the network.

(S)

The system aborts the process.

(O)

• An error occurred during the communication process with the HTTP server or application server.

  Eliminate the cause of the errors and log in to JP1/AJS3 for Cloud Service Applications.

• The HTTP server or application server is not running.

  Check either the JP1/AJS3 CSA HTTP Server service or JP1/AJS3 CSA Web Application Server service is running. If it is stopped, restart it and log in again.

• The HTTP server or the application server is busy.

  It may be connected by retrying the connection.

• The network connection to the HTTP server or application server is not available.

  Check the network environment with the HTTP server or application server. If there is a firewall between the HTTP server or the application server, check the firewall settings. If the session has been terminated, log in again.

The system confirms that you want to log out from JP1/AJS3 for Cloud Service Applications.

(S)

The system waits for the response.

(O)

Click the OK button to log out or click the Cancel button to cancel.

The system confirms that you will delete the definition definition-name.

A definition-type displays one of the following:

• service linkage job definition

• service linkage monitoring job definition

• connection definition

• execution definition

• authentication definition

• object monitoring definition

(S)

Waits for a response.

(O)

Click the OK button to delete or click the Cancel button to cancel.

The system confirms whether to continue updating the definition if a service linkage job or service linkage monitoring job using the definition to be updated has been executed by JP1/AJS3 - Manager.

A definition-type displays one of the following:

• service linkage job definition

• authentication definition

• service linkage monitoring job definition

(S)

Waits for a response.

(O)

Click the OK button to update or click the Cancel button to cancel.

To identify JP1/AJS3 - Manager jobs, use the following method:

• Identify the job that uses the target definition from KNBB3034-I in the server jobs log of JP1/AJS3 for Cloud Service Applications.

• From the unit definition of JP1/AJS3 - Manager that defines the service linkage job, identify the job by checking either of the following parameters that indicate the service linkage job definition name or the authentication definition name.

  - env="AJS_CSA_DEFINFNAME=service-linkage-job-definition-name";

  - env="AJS_CSA_AUTHINFNAME=authentication-definition-name";

• From the unit definition of JP1/AJS3 - Manager that defines the service linkage monitoring job, identify the job by checking either of the following parameters that indicate the service linkage monitoring job definition name or the authentication definition name.

  - cprm="AJS_CSA_MONDEFINFNAME=service-linkage-monitoring-job-name";

  - cprm="AJS_CSA_AUTHINFNAME=authentication-definition-name";

A service linkage job or service linkage monitoring job using the definition to be deleted has been executed in JP1/AJS3 - Manager.

The system confirms whether you really want to delete the file or not, since deleting it may affect JP1/AJS3 - Manager jobs.

A definition-type displays one of the following:

• service linkage job definition

• authentication definition

• service linkage monitoring job definition

(S)

Waits for a response.

(O)

Click the OK button to delete or click the Cancel button to cancel.

To identify JP1/AJS3 - Manager jobs, use the following method:

• Identify the job that uses the target definition from KNBB3034-I in the server jobs log of JP1/AJS3 for Cloud Service Applications.

• From the unit definition of JP1/AJS3 - Manager that defines the service linkage job, identify the job by checking either of the following parameters that indicate the service linkage job definition name or the authentication definition name.

  - env="AJS_CSA_DEFINFNAME=service-linkage-job-definition-name";

  - env="AJS_CSA_AUTHINFNAME=authentication-definition-name";

• From the unit definition of JP1/AJS3 - Manager that defines the service linkage monitoring job, identify the job by checking either of the following parameters that indicate the service linkage monitoring job definition name or the authentication definition name.

  - cprm="AJS_CSA_MONDEFINFNAME=service-linkage-monitoring-job-definition-name";

  - cprm="AJS_CSA_AUTHINFNAME=authentication-definition-name";

Applications. The system confirms whether you really want to update the definition or not, since deleting it may affect the running job.

This definition is used in JP1/AJS3 for Cloud Service Applications job definitions. The system confirms whether you really want to update the definition or not, since this may affect the job running.

A job-definition-type displays one of the following:

• service linkage job definition

• service linkage monitoring job definition

• service linkage job definition or service linkage monitoring job definition

A definition-type displays one of the following:

• connection definition

• object monitoring definition

(S)

Waits for a response.

(O)

Click the OK button to update or click the Cancel button to cancel.

To confirm the operation using the definition, check the contents from the definition screen of the job definitions.

This definition is used for the job definitions for JP1/AJS3 for Cloud Service Applications. The system confirms whether you really want to delete the definition or not, since deleting it may affect the job running.

A job-definition-type displays one of the following:

• service linkage job definition

• service linkage monitoring job definition

• service linkage job definition or service linkage monitoring job definition

A definition-type displays one of the following:

• connection definition

• execution definition

• object monitoring definition

(S)

Waits for a response.

(O)

Click the OK button to delete or click the Cancel button to cancel.

To confirm the operation using the definition, check the contents from the definition screen of the job definitions.

The registration of the definition failed because the definition type has already been registered.

A definition-type displays one of the following:

• service linkage job definition

• service linkage monitoring job definition

• connection definition

• execution definition

• authentication definition

• object monitoring definition

(S)

The system aborts the process.

(O)

Change the definition name and click the Register button again.

The definition was registered successfully.

A definition-type displays one of the following:

• service linkage job definition

• service linkage monitoring job definition

• connection definition

• execution definition

• authentication definition

• object monitoring definition

(S)

Waits for a response.

The definition was deleted successfully.

A definition-type displays one of the following:

• service linkage job definition

• service linkage monitoring job definition

• connection definition

• execution definition

• authentication definition

• object monitoring definition

(S)

Waits for a response.

The logged-in session is already invalid. If necessary, export the definitions to temporarily save the definitions being created, then log in again.

The exported definitions can be imported to the screen by the import function of the corresponding definition screen.

(S)

The system aborts the process.

(O)

If necessary, export the definitions temporarily to save it being created, then log in again and retry the operation.

The operation failed because there is insufficient permission for the operation-target definition of the definition type.

A definition-type displays one of the following:

• service linkage job definition

• service linkage monitoring job definition

• connection definition

• execution definition

• authentication definition

• object monitoring definition

(S)

The system aborts the process.

(O)

Check the JP1 resource group settings of the operation-target definition, add the permissions, and then perform the operation.

After opening a registered authentication definition from the Home screen, it was deleted before registration. Since the previous value that had been registered has been deleted, input items that do not select Update Value will be registered as if they had not been entered.

Enter the original values, check the Update Value checkbox, and then confirm that the registration is ready.

(S)

The system continues.

(O)

Please confirm the value that was entered in the item that has been checked in Protect and register again.

Deletion and loading of the definition failed because the definition of the registered definition type has already been deleted.

A definition-type displays one of the following:

• service linkage job definition

• service linkage monitoring job definition

• connection definition

• execution definition

• authentication definition

• object monitoring definition

(S)

The system aborts the process.

(O)

Refresh the screen to display the latest definition list screen and then perform the operation.

The definition could not be specified because either the connection definition or the execution definition specified in the service linkage job definition was deleted, or the user does not have reference permissions.

The definition could not be specified because either the connection definition or the monitoring definition specified in the service linkage monitoring job definition was deleted, or the user does not have reference permissions.

A definition-type displays one of the following:

• connection definition

• execution definition

• object monitoring definition

(S)

The system aborts the process.

(O)

Register the definition, and then either reopen the definition, or import it to load the definition.

You will be redirected to the home screen because the browser's Back or Forward button was used.

(S)

The system aborts the process.

(O)

Retry the operation from the home screen.

Start Service (service).

(S)

Continues processing.

Service started successfully.

(S)

The system outputs the fact that the service has started to the log.

The start failed because an error occurred during the service startup process.

(S)

The system aborts the service startup process.

(O)

Before this message is displayed, the message indicating the error is output to the command log or the application server log. Take action according to the message that was output immediately before this message.

This message is output when the service attempting to start has already been started. Skip the startup process of the service that has already started and continue the process.

(S)

Continues processing.

This message is output when the service attempting to stop has already been stopped. Skip the stop process of the service that has already stopped and continue the process.

(S)

Continues processing.

The system stops the service.

(S)

Continues processing.

Service is terminated.

(S)

The system outputs to the log that the service has been terminated.

The system started the setup of JP1/AJS3 for Cloud Service Applications.

(S)

Continues processing.

The system successfully completed the setup of JP1/AJS3 for Cloud Service Applications.

(S)

Continues processing.

The system failed to setup JP1/AJS3 for Cloud Service Applications.

(S)

The system aborts command execution.

(O)

Before this message is displayed, the message indicating the error is output to the command log. Take action according to the message that was output immediately before this message.

The system started the unsetup of JP1/AJS3 for Cloud Service Applications.

(S)

Continues processing.

The system failed the unsetup of JP1/AJS3 for Cloud Service Applications.

(S)

Continues processing.

The system failed the unsetup of JP1/AJS3 for Cloud Service Applications.

(S)

The system aborts command execution.

(O)

Before this message is displayed, the message indicating the error is output to the command log. Take action according to the message that was output immediately before this message.

A system error occurred during processing. There may be a problem with the execution environment of the JP1/AJS3 CSA Web Application Server service.

(S)

The system aborts the process in which the error occurred.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

Insufficient memory was detected in the execution environment of the JP1/AJS3 CSA Web Application Server service.

(S)

The system aborts the process in which the error occurred.

(O)

Check the physical memory usage of the host where the JP1/AJS3 CSA Web Application Server service is running.

If the capacity of the available physical memory is insufficient, terminate unnecessary applications to increase the size of available physical memory. (For details of the required capacity of physical memory of JP1/AJS3 for Cloud Service Applications, see the release notes.)

An unexpected error occurred during processing. There may be a problem with the execution environment of the JP1/AJS3 CSA Web Application Server service.

(S)

The system aborts the process in which the error occurred.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

The system starts outputting settings data.

(S)

Continues processing.

The system finished outputting settings data.

(S)

Continues processing.

The startup process of the service failed because a timeout occurred during the startup process.

(S)

The system aborts the service startup process.

(O)

Eliminate the cause of the timeout, such as system startup or a temporarily high load, and execute the process again.

The stop process of the service failed because a timeout occurred during its stop process.

(S)

The system aborts the service stop processing.

(O)

Eliminate the cause of the timeout, such as system startup or a temporarily high load, and execute the process again.

The startup process of the service failed because an error occurred during the startup process. The following may be the cause.

• There is an error in the definition file.

• Timeout occurred.

• JP1/AJS3 CSA HTTP Server was started twice (when the service is operated by JP1/AJS3 CSA HTTP Server).

(S)

The system aborts the service startup process.

(O)

Eliminate the cause of the error and execute the process again.

The stop process of the service failed because an error occurred during its stop process. The following may be the cause.

• There is an error in the definition file.

• Timeout occurred.

(S)

The system aborts the service stop processing.

(O)

Eliminate the cause of the error and execute the process again.

This message is to report the progress of the service startup and stop processes.

(S)

The system outputs the progress of service startup and stop processes to the log.

This message is output when the initialization of the log, which is output by the setup process, has failed.

(S)

Continues processing.

(O)

The log may not be output during the setup process, but no action is required because the setup is complete.

This message is output when the initialization of the log, which is output by the unsetup process, has failed.

(S)

Continues processing.

(O)

The log may not be output during the unsetup process, but no action is required because the unsetup is complete.

The process was aborted because loading of the environment configuration file failed.

(S)

The system aborts the process in which the error occurred.

(O)

Make sure that the environment configuration file has the privilege to be loaded. If not, change the setting and execute again.

If the failure occurred when starting the service, stop the JP1/AJS3 CSA HTTP Server service, restart the JP1/AJS3 CSA Web Application Server service, and then start the JP1/AJS3 CSA HTTP Server service.

The process was aborted because an incorrect specification was made in the environment configuration file.

(S)

The system aborts the process in which the error occurred.

(O)

Set the environment configuration file correctly. If not, change the setting and execute again.

Make sure that the environment configuration file has the privilege to be loaded. If not, change the setting and execute again.

If the failure occurred when starting the service, stop the JP1/AJS3 CSA HTTP Server service, restart the JP1/AJS3 CSA Web Application Server service, and then start the JP1/AJS3 CSA HTTP Server service.

There is an incorrect setting in the logical host. The following may be the cause.

• The configured shared directory does not exist.

• The length of the name of the configured shared directory exceeds the maximum value.

(S)

The system aborts the process in which the error occurred.

(O)

Confirm that the configured shared directory is available.

The process was interrupted because commands were executed concurrently.

(S)

The system aborts the process in which the error occurred.

(O)

An error may occur when commands are executed at the same time. If an error occurs, execute the process again.

An error occurred during file input or output. The following may be the cause.

• The user does not have access privileges to the file.

• The file is being used by another process.

(S)

The system aborts the process in which the error occurred.

(O)

Eliminate the cause of the error and execute the process again.

The initialization of the integrated trace log and command log failed.

(S)

The system aborts the startup process for the JP1/AJS3 CSA Web Application Server service on Windows. Otherwise, the system continues the process.

(O)

If an error message related to the environment configuration file has been output before this message is displayed, take action according to the error message. Otherwise, collect the data by using the data collection tool and contact your system administrator.

Output of the integrated trace log failed. There may be a problem with the integrated trace function.

(S)

The system aborts the output of the integrated trace log and continues the process.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

Completion of the integrated trace log output process failed.

(S)

Continues processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

An inappropriate option is specified.

(S)

The system aborts command execution.

(O)

Specify the correct option and rerun the command.

A value was not specified for an option that requires a value.

(S)

The system aborts command execution.

(O)

Specify the value of the option and rerun the command.

The value of the option was specified incorrectly.

(S)

The system aborts command execution.

(O)

Specify the value of the option and rerun the command.

The same option is specified twice or more.

(S)

The system aborts command execution.

(O)

Correct the option specified twice or more to only once and rerun the command.

The incorrect argument is specified.

(S)

The system aborts command execution.

(O)

Correct the argument and rerun the command.

Access to the shared directory failed.

(S)

The system aborts command execution.

(O)

Check whether the specified shared directory exists. If it exists, check whether there are the reference privilege and the update privilege in the specified shared directory.

The creation of the shared directory failed.

(S)

The system aborts command execution.

(O)

Check that the jp1ajs3csa directory, which is displayed in the message, does not exist.

Windows:

specified-shared-directory-name\jp1ajs3csa

UNIX:

specified-shared-directory-name/jp1ajs3csa

If the jp1ajs3csa directory exists, confirm that the specified shared directory name is correct. If it is correct, confirm that the jp1ajs3csa directory is unnecessary, and delete it, then rerun the command (do not delete the shared directory).

If there is no jp1ajs3csa directory, confirm that the specified shared directory has update privileges.

The process was aborted because the logical host could not be found.

(S)

The system aborts command execution.

(O)

Check whether the specified logical host is defined in JP1/Base.

A user without superuser or administrator privileges tried to run the command.

(S)

The system aborts command execution.

(O)

A user with superuser or administrator privileges must run the command.

If the UAC function is enabled on Windows, a user with administrator privilege should rerun the command.

Start processing the command (command).

(S)

Continues processing.

The processing of the command (command) has ended normally.

(S)

The system outputs to the log that the command has ended normally.

The processing of the command (command) has ended abnormally.

(S)

The system outputs to the log that the command has ended abnormally.

(O)

Before this message is displayed, the message indicating the error is output to the standard error output. Investigate the cause based on those messages.

The evaluation version has exceeded its expiration date.

(S)

The system aborts the process of starting the JP1/AJS3 CSA Web Application Server service.

The setup process of JP1/AJS3 for Cloud Service Applications was not performed because its service has already been set up.

(S)

The system terminates the setup process.

(O)

Make sure that the JP1/AJS3 for Cloud Service Applications service has been set up.

An error occurred during the setup of the JP1/AJS3 for Cloud Service Applications service. There may be a problem with the execution environment of the JP1/AJS3 for Cloud Service Applications service.

(S)

The system terminates the setup process.

(O)

Run the setup command as an OS user with Administrator privileges. If the UAC function is enabled on Windows, a user with administrator privilege should rerun the command. There might be insufficient memory or disc capacity. Terminate unnecessary applications and rerun the setup command.

An error occurred during the setup of the JP1/AJS3 for Cloud Service Applications service.

(S)

The system terminates the setup process.

(O)

Run the setup command as an OS user with Administrator privileges. There might be insufficient memory or disc capacity. Terminate unnecessary applications and rerun the setup command.

The service is running, so you cannot perform set up.

(S)

The system terminates the setup process.

(O)

Check if the JP1/AJS3 for Cloud Service Applications service is stopped.

The command (command) process has ended with warning.

(S)

The system outputs that to the log the command has been terminated with warning.

(O)

Before this message is displayed, the message indicating the cause of the warning is output to the command log. Investigate the cause according to the log immediately before this message and take action as necessary.

Note that the command may output this message and stop the JP1/AJS3 CSA Web Application Server service even though no error or warning message is output. In this case, there is no action required for this message. This message is generated because some internal processes were already stopped, and it indicates that the process of terminating the JP1/AJS3 CSA Web Application Server service has been completed normally.

This message reports that the startup process of the JP1/AJS3 CSA Web Application Server service has started.

(S)

The system has output to the log that the startup process of the JP1/AJS3 CSA Web Application Server service has started.

This message reports that the JP1/AJS3 CSA Web Application Server service has been started.

(S)

The system has output to the log that the JP1/AJS3 CSA Web Application Server service has been started.

This message reports that an error has occurred during the startup process of the JP1/AJS3 CSA Web Application Server service.

(S)

The system has output to the log that an error has occurred during the startup process of the JP1/AJS3 CSA Web Application Server service.

(O)

Before this message is displayed, the message indicating the error is output to the application server log. Take action according to the message that was output immediately before this message.

An unexpected error occurred during the startup process of the JP1/AJS3 CSA Web Application Server service.

(S)

The system aborts the process.

(O)

The configuration of JP1/AJS3 for Cloud Service Applications may be corrupt. Perform a recovery installation.

This message reports that the stop process of the JP1/AJS3 CSA Web Application Server service has started.

(S)

The system has output to the log that the JP1/AJS3 CSA Web Application Server service has been stopped.

This message reports that the JP1/AJS3 CSA Web Application Server service has been stopped.

(S)

The system has output to the log that the JP1/AJS3 CSA Web Application Server service has been stopped.

This message reports that the API process has started.

(S)

The system has output to the log that the API process has been started.

This message reports that the API process has completed.

(S)

The system has output to the log that the API process has been completed normally.

This message reports that an error has occurred during the API process.

(S)

The system has output to the log that an error has occurred during the API process.

(O)

Take action according to the messages that were output before and after this message.

This message indicates where the exception occurred.

(S)

The system has output to the log an indication of the location where the exception occurred.

This message shows the stack trace information.

The stack trace information is output according to the language type set in the OS.

(S)

The system has output the stack trace information to the log.

This message shows the API input information.

(S)

The system has output the API input information to the log.

This message shows the API execution information.

(S)

The system has output the API execution information to the log.

Legend:

Δ: Tab symbol

This message shows the information of the request source to get the information of the service linkage job.

(S)

The system has output the execution information of the service linkage job to the log.

Legend:

Δ: Tab symbol

This message shows the information of the request source to get the information of the service linkage monitoring job.

(S)

The system has output the execution information of the service linkage monitoring job to the log.

The file is not found.

(S)

The system assumes default value and continues processing.

An error occurred during the file input process for file-name. The following may be the cause.

• Unacceptable characters are specified for the file name or folder name.

• The length of the file name, folder name, or file path is incorrect.

• Insufficient capacity on the disc.

• Editing is in progress in another program.

(S)

The system aborts the process.

(O)

Eliminate the cause of errors and stop the JP1/AJS3 CSA HTTP Server service. Then, restart the JP1/AJS3 CSA Web Application Server service and start the JP1/AJS3 CSA HTTP Server service.

An error occurred during the file input process for file-name. The following may be the cause.

• Unacceptable characters are specified for the file name or folder name.

• The length of the file name, folder name, or file path is incorrect.

• There are no access rights for files and folders that store files.

• Insufficient capacity on the disc.

• Editing is in progress in another program.

(S)

The system aborts the process.

(O)

Eliminate the cause of errors and stop the JP1/AJS3 CSA HTTP Server service. Then, restart the JP1/AJS3 CSA Web Application Server service and start the JP1/AJS3 CSA HTTP Server service.

The process was aborted because an incorrect specification was made in the file.

(S)

The system aborts the process.

(O)

Set the environment configuration file correctly. Change the settings and stop the JP1/AJS3 CSA HTTP Server service. Then, restart the JP1/AJS3 CSA Web Application Server service and start the JP1/AJS3 CSA HTTP Server service.

In line-number, the approximate location of the incorrect description will be output. If there is no error in line-number, review the descriptions before and after the line-number.

This message reports the configuration definition that has been loaded into memory.

(S)

The system has output the configuration definition that has been loaded into memory to the log.

This message reports the failure to wait for file access retry.

(S)

The system has output to the log that there was a failure to wait for file access retry.

This message reports that the file close process failed.

(S)

The system has output to the log that the file close process has failed.

This message reports that the file has been read successfully.

(S)

The system has output to the log that the file has been loaded successfully.

An error occurred during the file output process for file-name. The following may be the cause.

• Unacceptable characters are specified for the file name or folder name.

• The length of the file name, folder name, or file path is incorrect.

• There are no access rights for files and folders that store files.

• Insufficient capacity on the disc.

• Editing is in progress in another program.

(S)

The system aborts the process.

(O)

Eliminate the cause of the error and try the operation again.

This message reports that the that the file has been written successfully.

(S)

The system has output to the log that the file was written successfully.

The logged-in session is already invalid. Log in again.

(S)

The system aborts the process.

(O)

Log in again and try the operation again.

The logged-in session is already invalid.

(S)

The system has output to the log that the logged-in session is already invalid.

The logged-in session is already invalid.

(S)

The system has output to the log that a session has been created.

This message reports that a session timed out.

(S)

The system has output to the log that a session timed out.

This message reports that a session was deleted.

(S)

The system has output to the log that a session was deleted.

An error occurred during the initialization of the log output process. The following may be the cause.

• The user does not have access privileges to the files at the lower level of the log folder.

• Insufficient capacity on the disc.

(S)

The system aborts the process.

(O)

Eliminate the cause of the error. If the problem cannot be solved, the configuration of JP1/AJS3 for Cloud Service Applications may be corrupt. Perform a recovery installation.

An error occurred during the log output process. The following may be the cause.

• The user does not have access privileges to the files at the lower level of the log folder.

• Insufficient capacity on the disc.

(S)

Continues processing.

(O)

Eliminate the cause of the error. If the problem cannot be solved, the configuration of JP1/AJS3 for Cloud Service Applications may be corrupt. Perform a recovery installation.

An error occurred during the end processing of the log output process. The following may be the cause.

• The user does not have access privileges to the files at the lower level of the log folder.

• Insufficient capacity on the disc.

(S)

Continues processing.

(O)

Eliminate the cause of the error. If the problem cannot be solved, the configuration of JP1/AJS3 for Cloud Service Applications may be corrupt. Perform a recovery installation.

The definition does not exist.

(S)

Cancels processing.

(O)

The definition does not exist. Register it again.

Login failed because the JP1 username or password was invalid.

(S)

Cancels processing.

(O)

Enter the JP1 username and password registered on the Access Control Server to which it is connected and then log in.

The process was aborted because the request was incorrectly specified.

(S)

Cancels processing.

(O)

Use the data collection tool to collect data, and then contact the system administrator.

There is an error in the description of the message body of the request.

(S)

Cancels processing.

(O)

Describe the message body of the request correctly.

In line-number, the approximate location of the incorrect description will be output. If there is no error in line-number, review the descriptions before and after the line-number.

request-header is not specified.

(S)

Cancels processing.

(O)

Specify the request-header.

The value in request-header is incorrect.

(S)

Cancels processing.

(O)

Specify correct value for request-header.

Failed to save execution history.

(S)

Continues processing.

The specified definition name does not exist.

A definition-type displays one of the following:

• service linkage job definition

• service linkage monitoring job definition

• connection definition

• execution definition

• authentication definition

• monitoring definition

(S)

Cancels processing.

(O)

Refresh the web screen to confirm that the definition exists, and then select it again.

Login or connection could not be established because an error occurred on JP1/Base at the connection destination during the user authentication process. The following may be the cause.

• The host name of the Access Control Server is incorrectly specified in the settings of JP1/Base at the connection destination.

• The Access Control Server has not started.

(S)

Cancels processing.

(O)

Eliminate the cause of the error and try the operation again.

If the connection destination is UNIX and the Authorized Server is specified as local host, the settings for JP1/Base are required to start as the Access Control Server. For the setting method, see the description of specifying the Access Control Server in the JP1/Base User's Guide.

Processing cannot start because the connection destination cannot connect to the Access Control Server.

(S)

Cancels processing.

(O)

Check whether the specified Access Control Server on JP1/Base at the connection destination is running or not.

This message reports that the release process of login information failed.

(S)

The system has output to the log that the release process of login information failed.

Backup of the database file has been completed.

(S)

Continues processing.

An error occurred during the database file backup.

The following factors may be the cause.

• The database file is being used by a process other than the JP1/AJS3 CSA Web Application Server service.

• The database file has been destroyed.

(S)

Continues processing.

(O)

Check whether the database file is being used by a process other than the JP1/AJS3 CSA Web Application Server service. If it is used by another process and this error message is not output at the next definition operation, no action is required. If this error message is output at the next definition operation, even if the database file is not used by other processes, restart the JP1/AJS3 CSA Web Application Server service. After the restart, if still this error message is output, collect the data and contact your system administrator.

Database maintenance has been completed.

(S)

Continues processing.

An error occurred during database maintenance.

The following factors may be the cause.

• The database file is being used by a process other than the JP1/AJS3 CSA Web Application Server service.

• The database file has been destroyed.

(S)

Continues processing.

(O)

Check whether the database file is being used by a process other than the JP1/AJS3 CSA Web Application Server service. If it is used by another process and this error message is not output at the next definition operation, no action is required. If this error message is output at the next definition operation, even if the database file is not used by other processes, restart the JP1/AJS3 CSA Web Application Server service. After the restart, if still this error message is output, collect the data and contact your system administrator.

Maintenance of the execution history table has been completed.

(S)

Continues processing.

An error occurred during maintenance of the execution history table.

The following factors may be the cause.

• The database file is being used by a process other than the JP1/AJS3 CSA Web Application Server service.

• The database file has been destroyed.

(S)

Continues processing.

(O)

Check whether the database file is being used by a process other than the JP1/AJS3 CSA Web Application Server service. If it is used by another process and this error message is not output at the next definition operation, no action is required. If this error message is output at the next definition operation, even if the database file is not used by other processes, restart the JP1/AJS3 CSA Web Application Server service. After the restart, if still this error message is output, collect the data and contact your system administrator.

The operation-target definition does not have the required operation permissions.

(S)

The system aborts the process.

(O)

Review whether the JP1 user who is operating has the required operation permissions for the JP1 resource group name that is set in the operation-target definition. If the permissions are insufficient, grant the required privileges before starting the operation.

An error occurred during access to the database file.

The following factors may be the cause.

• The database file is being used by a process other than the JP1/AJS3 CSA Web Application Server service.

• The database file has been destroyed.

(S)

The system aborts the process.

(O)

Check whether the database file is being used by a process other than the JP1/AJS3 CSA Web Application Server service. If it is being used by another process, check that the operation that caused this error is performed correctly after ending the process. If the operation is not performed correctly, try it again. If the same operation is performed again and the same error still occurs, restart the JP1/AJS3 CSA Web Application Server service. If the same error occurs even after restarting the JP1/AJS3 CSA Web Application Server service, restore the backed-up database file. If the same error occurs even after restoring the database file, collect the data and contact your system administrator.

An unexpected error occurred during processing. The following may be the cause.

• The configuration of JP1/AJS3 for Cloud Service Applications is corrupted.

• The API being processed was forcibly discarded because JP1/AJS3 for Cloud Service Applications was stopped or restarted.

(S)

The system aborts the process.

(O)

If the configuration of JP1/AJS3 for Cloud Service Applications has been changed, perform a recovery installation.

If the JP1/AJS3 for Cloud Service Applications was stopped or restarted, check to what extent the API processing has been reflected.

Otherwise, eliminate the cause of the error. If the problem cannot be solved, collect the data and contact your system administrator.

A system error occurred during processing. There may be a problem with the execution environment of the JP1/AJS3 CSA Web Application Server service.

(S)

The system aborts the process.

(O)

Eliminate the cause of the error. If the problem cannot be solved, collect the data and contact your system administrator.

Insufficient memory was detected in the execution environment of the JP1/AJS3 CSA Web Application Server service.

(S)

The system aborts the process.

(O)

Check the physical memory usage of the host where the JP1/AJS3 CSA Web Application Server service is running.

If the capacity of the available physical memory is insufficient, terminate unnecessary applications to increase the size of available physical memory.

For details of required capacity of memory of JP1/AJS3 for Cloud Service Applications, see the release notes.

This message reports that an unexpected error has occurred during the process.

(S)

Continues processing.

(O)

The configuration of JP1/AJS3 for Cloud Service Applications may be corrupt. Perform a recovery installation.

If the problem cannot be solved, collect the data and contact your system administrator.

This message reports that there is an unacceptable input in corresponding-field-name because the job definition is invalid.

(S)

The system initializes the value in corresponding-field-name.

The value was entered incorrectly in field-name.

(S)

The system aborts the process.

(O)

Re-enter the correct value in field-name.

An unexpected error occurred during the definition program.

(S)

The system aborts the process.

(O)

This may be a temporary error. Close the Service Linkage Job Definition screen or the Service Linkage Monitoring Job Definition screen, and then reopen the screen to define the job.

If the same error occurs, the folder (system-drive\temp) required for the custom job definition linkage or custom event job definition linkage may be missing. See the description of the KAVV801-E message in the manual, JP1/Automatic Job Management System 3 Messages and take action. If the problem persists, collect the data by using the data collection tool and contact your system administrator.

The service-linkage-definition-information-file-name could not be loaded correctly.

(The file may not exist, may not be opened, or the contents may be incorrect.)

A service-linkage-definition-information-file-name displays one of the following:

• service linkage definition information file

• service linkage monitoring definition information file

(S)

The system aborts the process.

(O)

Recreate the service linkage definition information file or the service linkage monitoring definition information file, and register the service linkage job or service linkage monitoring job again.

No value was entered in field-name.

(S)

The system aborts the process.

(O)

Enter a value in field-name.

The total size of the input value has exceeded the limit.

(S)

The system aborts the process.

(O)

Review the input values if there are any unnecessary values or values that can be shortened and click the OK button again.

The field-name is outside the minimum-value - maximum-value range.

If the Total time is shown for field-name, review the values specified for repeat-interval and number-of-times-to-repeat.

(S)

The system aborts the process.

(O)

Enter a value within the specifiable range.

The field-name is not specified.

(S)

The system aborts the process.

(O)

Specify the required item.

• The magnification of the Define Details window and message dialog will be reduced to a scale that fits on all connected displays, as the specified size exceeds the dimensions of all connected displays.

• If the display information cannot be correctly obtained, the window will be shown without magnification.

(S)

The processing continues at a size smaller than the specified scale factor.

(O)

Make sure that a sufficiently large display is connected and then reopen the Define Details window.

The service linkage job or service linkage monitoring job is registered successfully.

A service-linkage-job-type displays one of the following:

• service linkage job

• service linkage monitoring job

Required options are not specified.

(S)

The system aborts the process.

(O)

Specify required options and rerun the command.

You specified unavailable options.

(S)

The system aborts the process.

(O)

Specify the available option and rerun the command.

No value was specified for the option.

(S)

The system aborts the process.

(O)

Specify the value of the option and rerun the command.

A value has been specified for an option that does not require a value.

(S)

The system aborts the process.

(O)

Correct the command format and rerun the command.

The format of the option value is incorrect.

(S)

The system aborts the process.

(O)

Specify the correct value of the option and rerun the command.

The same option is specified twice or more.

(S)

The system aborts the process.

(O)

Correct the option specified twice or more to only once and rerun the command.

You specified a custom job or a custom event job that already exists.

(S)

The system aborts the process.

(O)

Specify a job name that is not registered in JP1/AJS3 - View and rerun the command.

You cannot access the specified file.

(S)

The system aborts the process.

(O)

Correct the access rights and existence of the file and rerun the command.

The contents of the service linkage definition information file or service linkage monitoring definition information file are invalid.

The contents may have changed due to editing or saving the file using a text editor.

(S)

The system aborts the process.

(O)

Export the definition information file from JP1/AJS3 for Cloud Service Applications again and rerun the command.

The maximum number of custom jobs or custom event jobs that View can hold has been exceeded.

A job-type displays one of the following:

• custom jobs

• custom event jobs

A service-linkage-job-type displays one of the following:

• service linkage job

• service linkage monitoring job

(S)

The system aborts the process.

(O)

Delete the unused custom job or custom event job and rerun the command, or register the jobs on another View host.

The command has run while the Register Custom Job screen was open or while the Import, List display, or Delete command is running.

(S)

The system aborts the process.

(O)

If the Register Custom Job dialog box is opened, close it and rerun the command.

If another service linkage job or service linkage monitoring job operation command is running, rerun the command after the operation command has completed.

The service linkage job is not registered.

A service-linkage-job-type displays one of the following:

• service linkage job

• service linkage monitoring job

The service linkage job was deleted successfully.

A service-linkage-job-type displays one of the following:

• service linkage job

• service linkage monitoring job

An option that cannot be specified at the same time has been specified.

(S)

The system aborts the process.

(O)

Check the specified option and rerun the command with a combination of options that can be specified at the same time.

You specified a service linkage job name that does not exist, or a custom job name other than a service linkage job.

Alternatively, you specified a service linkage monitoring job name that does not exist.

A service-linkage-job-type displays one of the following:

• service linkage job

• service linkage monitoring job

(S)

The system aborts the process.

(O)

Check the service linkage job name or the service linkage monitoring job name you want to delete and rerun the command.

A job-type displays one of the following:

• custom job

• custom event job

If the job-type is a custom job, operations cannot be performed for the following reasons:

• Read and write permissions are not set for files located under the custom job registration information folder^#1.

• Files located under the custom job registration information folder^#1 are being edited in another program.

If the job-type is a custom event job, operations cannot be performed for the following reasons:

• Read and write permissions are not set for files located under the custom event job registration information folder^#2.

• Files located under the custom event job registration information folder^#2 are being edited in another program.

#1:

The following folder:

View_Data_Path^#3\custom.dir\

#2:

The following folder:

View_Data_Path^#3\customevent.dir\

#3:

View_Data_Path: JP1/AJS3 - View data folder

(S)

The system aborts the process.

(O)

Eliminate the cause of the error.

A service-linkage-job-type displays one of the following:

• service linkage job

• service linkage monitoring job

If the service-linkage-job-type is a service linkage job, operations cannot be performed for the following reasons:

• Read and write permissions are not set for the service linkage job-specific information storage destination folder^#1 and files located under the folder.

• Files located under the service linkage job-specific information storage destination folder^#1 are being edited in another program.

If the service-linkage-job-type is a service linkage monitoring job, operations cannot be performed for the following reasons:

• Read and write permissions are not set for the service linkage monitoring job-specific information storage destination folder^#2 and files located under the folder.

• Files located under the service linkage monitoring job-specific information storage destination folder^#2 are being edited in another program.

#1:

Either of the following folders:

• View_Path^#3\image\custom

• View_Data_Path^#4\csadef

#2:

Either of the following folders:

• View_Path^#3\image\custom

• View_Data_Path^#4\csadef\evcustom

#3:

View_Path: JP1/AJS3 - View installation folder

#4:

View_Data_Path: JP1/AJS3 - View data folder

(S)

The system aborts the process.

(O)

Eliminate the cause of the error.

An unexpected error occurred during the service linkage job or service linkage monitoring job operation command.

(S)

The system aborts the process.

(O)

Collect the data by using the data collection tool and contact your system administrator.

An error occurred during the initialization of the log output process.

(S)

The system aborts the process.

(O)

The user does not have access privileges to the files at the lower level of the log folder or there might be insufficient memory or disc capacity.

Eliminate the cause of the error. If the problem cannot be solved, the configuration of JP1/AJS3 - View may be corrupted. Perform a recovery installation.

An error occurred during the log output process. The following may be the cause.

• The user does not have access privileges to the files at the lower level of the log folder.

• Insufficient capacity on the disc.

The location of the log folder is as follows:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V\log

The default for %ALLUSERSPROFILE% is system-drive\ProgramData.

(S)

The system aborts the process.

(O)

Eliminate the cause of the error.

An unexpected error occurred during the start processing of service linkage job or service linkage monitoring job operation command.

(S)

The system aborts the process.

(O)

There might be insufficient memory or disc capacity. Terminate unnecessary applications and rerun the command.

If the problem cannot be solved, the configuration of JP1/AJS3 - View may be corrupted. Perform a recovery installation.

The system failed to start the service linkage job or service linkage monitoring job command.

(S)

The system aborts the process.

(O)

The following factors may be the cause.

• There might be insufficient memory or disc capacity. Terminate unnecessary applications and rerun the command.

• JP1/AJS3 - View is installed in the root of the drive. Install JP1/AJS3 - View in a location other than the root of the drive.

If the problem cannot be solved, the configuration of JP1/AJS3 - View may be corrupted. Perform a recovery installation.

The user who tried to run the service linkage job or service linkage monitoring job operation command does not have the required command operation permissions.

(S)

The system aborts the process.

(O)

Rerun the command on a command prompt running with administrator privileges.

The folder specified in the environment variable does not exist.

Use the default custom job or custom event job registration information folder^#1 and folder^#2 containing the service linkage job or service linkage monitoring job-specific information.

#1:

View_Data_Path^#3\custom.dir (for a service linkage job)

View_Data_Path^#3\customevent.dir (for a service linkage monitoring job)

#2:

View_Data_Path^#3\csadef (for a service linkage job)

View_Data_Path^#3\csadef\customevent (for a service linkage monitoring job)

#3:

View_Data_Path: JP1/AJS3 - View data folder

An environment-variable-name displays one of the following:

• AJS_CSA_VIEW_CUSTOMJOBDIR

• AJS_CSA_VIEW_CUSTOMEVJOBDIR

Forced overwrite option was specified for a custom job other than a service linkage job.

(S)

The system aborts the process.

(O)

Specify another custom job name and rerun the registration command.

The command line parameters specified for the command are too long. The command cannot be started.

(S)

Cancels processing.

(O)

Correctly specify the command line parameters, and then re-execute the command.

The service linkage job will be started.

(S)

Continues processing.

The service linkage job will be ended.

(S)

Continues processing.

The communication with the JP1/AJS3 for Cloud Service Applications server will be started.

(S)

Continues processing.

The communication with the JP1/AJS3 for Cloud Service Applications server ends.

(S)

Continues processing.

This message reports the name and command line of the process to be executed from now.

The command line for the processing name will be output in the next line with the same process ID and same thread ID.

(S)

Continues processing.

The service linkage objects monitoring job will be started.

The system starts monitoring the monitoring target file.

(S)

Continues processing.

The service linkage objects monitoring process will be started.

(S)

The system starts the service linkage objects monitoring process.

The service linkage objects monitoring process will be terminated.

(S)

The system terminates the service linkage objects monitoring process.

The object was created.

(S)

Continues processing.

The object existed when the job was started.

(S)

Continues processing.

The object was deleted.

(S)

Continues processing.

No objects existed when the job was started.

(S)

Continues processing.

The object was updated.

(S)

Continues processing.

The time-out period has elapsed. The job will be terminated.

(S)

The job is timed-out and terminated based on the time-out period specified.

An environment variable or CSA definition item has an error in one of the following:

• Required value has no value

• Character count

• Format (character string, numeric, etc.)

When the environment variables are AJS_CSA_EXECRI (repeat interval) and AJS_CSA_EXECRN (number of times to repeat), the possible causes may include the following:

• The total time required for retries of end confirmation processing, based on the repeat interval and the number of times to repeat, exceeds 2,880 minutes.

• The repeat interval is specified, but the number of times to repeat is not.

• The number of times to repeat is specified, but the repeat interval is not.

The environment variable name or maintenance information is output in Maintenance information.

(S)

The system aborts the process.

(O)

Specify the following values correctly and then rerun the command.

• Environment variable

  - AJS_CSA_AUTHINFNAME

  - AJS_CSA_DEFINFNAME

  - AJS_CSA_ENV_variable-value

  - AJS_CSA_EXECRI

  - AJS_CSA_EXECRN

• CSA definition

The specification of environment setting parameter is invalid.

(S)

The system aborts the process.

(O)

Redefine the environment definition as necessary.

The job definition contains an error in one of the following areas:

• Required values not entered

• Character length

• Format (character string, numerals, etc.)

(S)

The system aborts the process.

(O)

Define the correct job, and then rerun the process.

The definition of the service linkage monitoring job does not match the monitoring definition on the JP1/AJS3 for Cloud Service Applications server.

The following factors may be the cause.

On update is specified as the job definition monitoring condition, but no update monitoring target is specified for the monitoring definition on the JP1/AJS3 for Cloud Service Applications server.

(S)

The system aborts the process.

(O)

Specify an update monitoring target for the monitoring definition on the JP1/AJS3 for Cloud Service Applications server, and then rerun the service linkage monitoring job.

A macro variable exceeded 4,096 bytes after conversion.

(S)

The maximum size of a macro variable is 4,096 bytes. If a macro variable exceeds 4,096 bytes, any excessive information is truncated and the process continues.

(O)

Data exceeding 4,096 bytes in a macro variable is not passed onto succeeding jobnets or jobs. Check the execution status of any succeeding jobnet or job, and review the job definition if problems are found.

An error occurred when extracting information from the object list information based on the extraction position information.

(S)

The system aborts the process.

(O)

Confirm the following:

• Whether the object list information was properly acquired

• Whether the results obtained from object list information are in the expected format

• Whether the correct extraction position information was specified

• Whether the memory is enough

If there is not enough memory, check whether the output amount of the execution results (standard output) of the command executed from the service linkage monitoring job is large. If the output amount is large, adjust the options of the command to be executed from the service linkage monitoring job so that unnecessary information is not output.

The result of extraction from the object list information is incorrect.

(S)

The system aborts the process.

(O)

The following factors may be the cause, depending on the maintenance-information-1 value.

Review the command execution result and extraction position information.

• When 1

  The result of applying the extraction position information to the object list information result is in the incorrect JSON format.

• When 2

  The result of applying the extraction position information to the object list information result is not in JSON array format.

• When 3

  The object name extraction result is not a JSON array with string elements.

• When 4

  The extraction results for the specified update monitoring targets 1 to 3 contain elements other than string values, numerical values, Boolean values, and null values.

• When 5

  The number of elements in the object name extraction result does not match the number of elements in the extract result for the specified update monitoring targets 1 to 3.

• When 6

  The result of extraction from the object name is a null character.

Numerical information extracted from the extraction position information in the update monitoring target information contained numerical values that cannot be handled by the service linkage objects monitoring job.

(S)

The system aborts the process.

(O)

Numerical information that can be handled by update monitoring target information in the service linkage objects monitoring job includes the following:

Integers from -10,995,116,277,760 to 10,995,116,277,760

When handling numerical information, truncate the information to fit within this value range, and then rerun the service linkage objects monitoring job.

An error has been detected with the service linkage objects monitoring process, and it will be terminated.

(S)

A non-continuable error occurred during processing, terminating the service linkage objects monitoring process. The service linkage objects monitoring job cannot perform monitoring.

Out of memory has occurred. Messages cannot be output to detailed execution results.

(S)

Out of memory has occurred. The process will continue without outputting messages to detailed execution results.

(O)

Check that there is sufficient memory.

For details about the memory requirements for JP1/AJS3, see the description of the required memory size and disk utilization in the Release Notes.

Out of memory has occurred.

(S)

The system checks whether the object status has been updated again at the next monitoring interval. Alternatively, the corresponding job ends abnormally.

(O)

Check whether you have sufficient memory to execute the program. Check whether any service linkage objects monitoring jobs have ended abnormally using JP1/AJS3 - View. If service linkage objects monitoring jobs have ended abnormally, register them again.

The service linkage objects monitoring process failed to start.

(S)

A non-continuable error occurred during the service linkage objects monitoring job process startup process, terminating the process. The service linkage objects monitoring job cannot perform monitoring.

(O)

Check whether a resource shortage has occurred. After confirming, restart JP1/AJS3.

An error occurred in inter-process communication with the agent, and the service linkage objects monitoring process will be terminated.

(S)

An error occurred in inter-process communication with the agent, and the service linkage objects monitoring process will be terminated. The service linkage objects monitoring job cannot perform monitoring.

(O)

Confirm the following:

• Whether system resources are sufficient.

• Whether the directory created when installing JP1/AJS3 has been accidentally deleted.

After confirming, restart JP1/AJS3.

Inter-process communication with the agent failed.

(S)

An error occurred in inter-process communication with the agent. Depending on the location where the error occurred, the service linkage objects monitoring process will be terminated. In such cases, the service linkage objects monitoring job cannot perform monitoring. Service linkage objects monitoring job event detection may have failed.

(O)

Check whether system resources are sufficient, or whether the directory created when installing JP1/AJS3 has been accidentally deleted. If the service linkage objects monitoring process is running, check the service linkage objects monitoring job that returned an error in JP1/AJS3 - View, and rerun the job. If the service linkage objects monitoring process is stopped, restart JP1/AJS3.

Failed to open the information file handled by the service linkage objects monitoring process.

(S)

The monitoring start process for the corresponding job cannot be executed.

(O)

Check whether system resources are sufficient, or whether the directory created when installing JP1/AJS3 has been accidentally deleted.

After confirming, check the service linkage objects monitoring job that returned an error in JP1/AJS3 - View, and rerun the job.

Failed the required initialization process to communicate with the jpoagtjobshow command.

(S)

Continues processing. However, information is not provided to the jpoagtjobshow command.

(O)

Confirm the following:

• Whether system resources are sufficient.

• Whether the permissions environment for the startup user is correct.

• Whether the directory created when installing JP1/AJS3 has been accidentally deleted.

To display the correct information with the jpoagtjobshow command, restart JP1/AJS3.

Failed to read from the pipe of the jpoagtjobshow command.

(S)

Continues processing. However, information is not provided to the jpoagtjobshow command.

(O)

Confirm the following:

• Whether system resources are sufficient.

• Whether the permissions environment for the startup user is correct.

• Whether the directory created when installing JP1/AJS3 has been accidentally deleted.

To display the correct information with the jpoagtjobshow command, rerun the command.

Failed to create an information file for the jpoagtjobshow command.

(S)

Continues processing. However, information is not provided to the jpoagtjobshow command.

(O)

Confirm the following:

• Whether system resources are sufficient.

• Whether the permissions environment for the startup user is correct.

• Whether the directory created when installing JP1/AJS3 has been accidentally deleted.

To display the correct information with the jpoagtjobshow command, rerun the command.

Failed to write to the pipe of the jpoagtjobshow command.

(S)

Continues processing. However, information is not provided to the jpoagtjobshow command.

(O)

Confirm the following:

• Whether system resources are sufficient.

• Whether the permissions environment for the startup user is correct.

• Whether the directory created when installing JP1/AJS3 has been accidentally deleted.

To display the correct information with the jpoagtjobshow command, rerun the command.

There is job information that could not be written when creating the information file for the jpoagtjobshow command.

(S)

Continues processing. However, information is not provided to the jpoagtjobshow command.

(O)

Confirm the following:

• Whether system resources are sufficient.

• Whether the permissions environment for the startup user is correct.

• Whether the directory created when installing JP1/AJS3 has been accidentally deleted.

To display the correct information with the jpoagtjobshow command, rerun the command.

The status passing information storage file cannot be opened for the service linkage objects monitoring job. The object monitoring status is not passed on. When JP1/AJS3 is started, processing is performed without the status of objects monitored when the service stopped being passed on.

(S)

The object monitoring status is not passed on. When JP1/AJS3 is started, service linkage objects monitoring job processing is performed without the status of objects monitored when the service stopped being passed on.

(O)

Confirm the following:

• Whether system resources are sufficient.

• Whether the directory created when installing JP1/AJS3 has been accidentally deleted.

• For cluster operation, whether operating settings in FQDN format are the same for primary and secondary nodes when operating a DNS using a service linkage objects monitoring job.

Failed to configure settings for the next monitoring process.

(S)

An error occurred in the settings for the next monitoring process. The system checks whether the object status has been updated again at the next monitoring interval. Alternatively, the corresponding job ends abnormally.

(O)

Confirm the following:

• Whether system resources are sufficient.

• Whether the permissions environment for the startup user is correct.

• Whether the directory created when installing JP1/AJS3 has been accidentally deleted.

Failed to start the job.

(S)

An error occurred in the job startup process. The corresponding job will end abnormally.

(O)

Confirm the following:

• Whether system resources are sufficient.

• Whether the permissions environment for the startup user is correct.

• Whether the directory created when installing JP1/AJS3 has been accidentally deleted.

The loading of the connection configuration file of the service linkage job or service linkage monitoring job failed.

(S)

The system aborts the process.

(O)

Check the following possible causes.

1. There is no connection configuration file.

2. The path to the connection configuration file is incorrect.

3. You do not have permission to access the connection configuration file.

Take the following actions and try again.

1. Set the connect configuration file.

2. Enter the correct path to the connect configuration file.

3. Set access privileges to the connection configuration file.

There is an error in the syntax of connection configuration file for the service linkage job or service linkage monitoring job.

The following factors may be the cause.

• A value is not specified.

• The length of the value is invalid.

• The value is not one of the available values.

• Out of the range of available values.

• Required specifications are not satisfied.

• Unknown item name is specified.

(S)

The system aborts the process.

(O)

Correct the connection configuration file and try again.

An error occurred during the communication with the JP1/AJS3 for Cloud Service Applications server.

The following causes for the job execution host can be considered.

• The settings of connection configuration file are incorrect.

• The environment is not capable of communicating with the JP1/AJS3 for Cloud Service Applications server.

• JP1/AJS3 for Cloud Service Applications server host and JP1/AJS3 for CSA are stopped.

• A network failure has occurred.

• The SSL communication settings do not match the JP1/AJS3 for Cloud Service Applications server.

(S)

The system aborts the process.

(O)

Eliminate the cause of the error and try again.

• CSAServerName

• CSAConnectProtocol

• CSAConnectPortNumber

• ProxyAddr

• CAFile

If the problem cannot be solved, collect the data by using the data collection tool and contact your system administrator.

An error occurred on the JP1/AJS3 for Cloud Service Applications server.

The probable causes are as follows:

• The connection configuration file for the job execution host is configured incorrectly.

• The user does not have permission for the definitions on the JP1/AJS3 for Cloud Service Applications server.

• The authentication definition specified for the job does not exist on the JP1/AJS3 for Cloud Service Applications server.

• The service linkage job definition or service linkage monitoring job definition for the job in which the error occurred does not exist on the JP1/AJS3 for Cloud Service Applications server.

• The execution definition or connection definition specified for the service linkage job does not exist on the JP1/AJS3 for Cloud Service Applications server.

• The monitoring definition or connection definition specified for the service linkage monitoring job does not exist on the JP1/AJS3 for Cloud Service Applications server.

(S)

The system aborts the process.

(O)

Confirm the JP1/AJS3 for Cloud Service Applications message.

Additionally, confirm whether the following are correct, and specify the correct values.

• The ProxyAddr setting specified in the connection configuration file

• The authentication definition name specified in the service linkage job definition or the service linkage monitoring job definition

• The service linkage job definition or the service linkage monitoring job definition on the JP1/AJS3 for Cloud Service Applications server

• The JP1 user name used when executing the service linkage job or the service linkage monitoring job, and the permissions level in JP1/AJS3 for Cloud Service Applications set for the JP1 user name

• The resource group name for the definition in JP1/AJS3 for Cloud Service Applications

The IP address could not be resolved from the host name JP1/AJS3 for Cloud Service Applications-server-name of the JP1/AJS3 for Cloud Service Applications server.

(S)

The system aborts the process.

(O)

On agent-host-name, in order to resolve the IP address of the host name JP1/AJS3 for Cloud Service Applications-server-name of the JP1/AJS3 for Cloud Service Applications server, correct the settings of the hosts file, jp1hosts file, jp1hosts2 file, or DNS. Then, confirm that the IP address of the host name of JP1/AJS3 for Cloud Service Applications server is set correctly. After that, try again.

If the above measures do not solve the problem, collect the data by using the data collection tool and contact your system administrator.

An error occurred during the communication with the JP1/AJS3 for Cloud Service Applications server. Retry the request to the JP1/AJS3 for Cloud Service Applications server according to the settings for retry interval and retry count. After this message is output, wait for the retry interval and then retry. If an error occurs even after reaching the maximum retry count, the KABB6202-E message will be output.

(S)

Continues processing.

(O)

Check whether the JP1/AJS3 for Cloud Service Applications server host and JP1/AJS3 for Cloud Service Applications are running.

The format of the information obtained from JP1/AJS3 for Cloud Service Applications is invalid. The information may be corrupted due to a communication problem with JP1/AJS3 for Cloud Service Applications.

(S)

The system aborts the process.

(O)

Check whether the host name and port number of the JP1/AJS3 for Cloud Service Applications at the connection destination are correct.

If the problem cannot be solved, collect the following data and contact your system administrator.

• Log information of the JP1/AJS3 for Cloud Service Applications at the connection destination

• Log information of the host where the job is executed

The command executed by the service linkage job ended abnormally.

(S)

The system aborts the process when an error occurred during the connection processing. If an error occurred in a command executed by a subsequent service linkage job, then the system continues the job output and subsequent processes.

(O)

Check the following and try again.

• If KNBB6004-I was output immediately before, there is no error in the command executed by the service linkage job.

• The input information of the command executed by the service linkage job is appropriate.

• The abnormal end setting is as designed.

The job will be end abnormally if either of the following conditions did not match.

• The value of the variable specified for the process normal end condition and the value of the process normal end condition

• The value of the variable specified for the process continuation condition, and both of the value of the process normal end condition and the value of the retry condition for the process continuation condition

(S)

The system continues the job output and subsequent processes.

(O)

The service executed by the cloud service may be in an abnormal state. Check the status and eliminate the cause.

The process exceeded the number of repeat count specified in the continuation condition.

(S)

The system continues the job output and subsequent processes.

(O)

The service executed by the cloud service may be in an abnormal state. Check the status and eliminate the cause.

The command could not run from the service linkage job.

The OS environment might not be configured correctly (for example, the PATH environment variable is specified incorrectly).

(S)

The system aborts the process.

(O)

Check that the OS environment is configured correctly (for example, whether the PATH environment variable is specified incorrectly by the job execution host).

If you cannot solve the problem, use the data collection tool to collect data, and then contact the system administrator.

The command run by a service linkage job was terminated because of a signal.

(S)

The system aborts the process when an error occurred during the connection processing. If an error occurred in a command executed by a subsequent service linkage job, then the system continues the job output and subsequent processes.

(O)

Check whether the command run by the service linkage job was not terminated forcibly.

The standard output from the command executed by the service linkage objects monitoring job for object monitoring has exceeded the LimitObjMonStdOutSize environment setting parameter.

The following may have occurred.

• The command line specified in the monitoring definition on the JP1/AJS3 for Cloud Service Applications server contains errors.

• There are too many objects or information to acquire.

(S)

The connection termination processing is executed if it is configured. The job will end abnormally.

(O)

Check for errors in the command line defined for the monitoring definition on the JP1/AJS3 for Cloud Service Applications server.

Either edit the command line, or reduce the number of objects to limit the number of objects or information acquired as a result of running the command.

The standard error output from the command executed by the service linkage objects monitoring job for object monitoring exceeded 3,072KB.

When the standard error output from the command executed is specified in the monitoring definition on the JP1/AJS3 for CSA server to output to a log or detailed execution results, the information may get cut off, or become garbled.

The following factors may be the cause.

The command line specified in the monitoring definition for JP1/AJS3 for CSA at the connection destination contains errors.

(S)

Continues processing.

(O)

Check for errors in the command line defined for the monitoring definition on the JP1/AJS3 for Cloud Service Applications server, and then apply countermeasures.

The command executed by the service linkage monitoring job has been terminated abnormally. Monitoring will continue in accordance with the monitoring definition.

(S)

Continues processing.

(O)

Confirm the following:

• If KNBB6004-I is output immediately before, check whether the command executed from the service linkage monitoring job contains errors.

• Whether the input information of the command executed from the service linkage monitoring job is correct.

• Whether the abnormal end settings are as intended.

Failed to mask user when executing commands in the service linkage monitoring job.

(S)

The system aborts the process.

(O)

Check the following possible causes.

1. The manager host name specified as the server host name for the JP1 user is incorrect on the agent host.

2. The JP1 user is not registered in the user mapping definition on the agent host.

3. A non-existent OS user is registered in the user mapping definition on the agent host.

4. The wrong OS user password is registered in the user mapping definition on the agent host (Windows only).

5. There is no JP1 user with the same name as the OS user that executed the ajsentry command.

6. The owner JP1 user is different to the JP1 user responsible for execution registration.

7. Out of memory has occurred.

8. If Owner user is specified as the Executed by in the detailed definition of the job, and the Owner field is blank, an OS user with a name not registered as a JP1 user is set as the account under which the JP1/AJS3 service is activated on the manager host.

After addressing the potential factors, reissue the request.

1. Set the correct manager host name as the server host name for the JP1 user.

2. In the user mapping definition for the agent host executing the job, register the JP1 user displayed as the JP1-user-name in the message and map it to the OS user.

3. In the user mapping definition for the agent host executing the job, register an OS user that exists.

4. Run the jbsumappass command and set the password for the OS user again. Specify the OS user password as the password. (Windows only)

5. After performing either of the following actions, rerun the ajsentry command.

   - Add a JP1 user with the same name as the OS user, and map the JP1 user with the OS user.

   - In the job definition, specify the owner as the user executing the job.

6. Determine whether to register job execution as the owner or as the user performing an execution registration, and correctly configure the Executed by.

7. Confirm the memory status, and review the expected memory requirements.

8. In the user mapping definition, register the JP1 user displayed as the JP1-user-name in the message. When using Windows, set an OS user of the same name as the user name registered as the JP1 user on the startup account for the JP1/AJS3 service on the manager host.

For details about how to configure user mapping settings, see 3. Setup in the manual JP1/Automatic Job Management System 3 Configuration Guide (for Windows), or 13. Setup in the manual JP1/Automatic Job Management System 3 Configuration Guide (for UNIX).

For details about JP1/AJS3 commands, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference, or 4. Commands Used for Special Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

For details about JP1/Base commands, see the manual JP1/Base User's Guide.

The command executed from the service linkage monitoring job ended abnormally.

(S)

The system aborts the process when an error occurred during connection processing.

If an error occurred in a command executed during monitoring processing, the process will continue from connection termination processing.

(O)

Check the following and try again.

• There is no error in the command executed by the service linkage monitoring job.

• The input information of the command executed by the service linkage monitoring job is appropriate.

• The abnormal end setting is as designed.

The command could not run from the service linkage monitoring job.

The OS environment might not be configured correctly (for example, the PATH environment variable is specified incorrectly).

(S)

The system aborts the process.

(O)

Check that the OS environment is configured correctly (for example, whether the PATH environment variable is specified incorrectly by the job execution host).

If you cannot solve the problem, use the data collection tool to collect data, and then contact the system administrator.

The command run by a service linkage monitoring job was terminated because of a signal.

(S)

The system aborts the process when an error occurred during the connection processing.

If an error occurred in a command executed by a monitoring process, then the system continues processing from connection termination processing.

(O)

Check whether the command run by the service linkage monitoring job was not terminated forcibly.

The acquisition of the environment variable failed.

(S)

The system aborts the process.

(O)

Check whether the length of the value of environment variable specified for the variable is not too long.

If the problem cannot be solved, collect the data by using the data collection tool and contact your system administrator.

The system failed to acquire the environment setting parameter. For physical host, JP1_DEFAULT is output to logical-host-name.

(S)

The system aborts the process.

(O)

Set the value output to the environment-setting-parameter correctly in the environment where the job is executed. For the output item name, see the manual.

The system abnormally terminated the thread for monitoring objects in the service linkage objects monitoring job.

(S)

The system terminates the service linkage objects monitoring process.

(O)

An excessive load may have been applied to the CPU. Check the CPU load.

If you cannot solve the problem, use the data collection tool to collect data, and then contact the system administrator.

The format of the status passing information storage file in the service linkage objects monitoring job is incorrect. The object monitoring status is not passed on. When JP1/AJS3 is started, processing is performed without the status of objects monitored when the service stopped being passed on.

(S)

The object monitoring status is not passed on. When JP1/AJS3 is started, service linkage objects monitoring job processing is performed without the status of objects monitored when the service stopped being passed on.

(O)

Confirm the following:

• Whether JP1/AJS3 inappropriately manipulates directories and files created upon installation.

Failed to write to the file.

(S)

The system aborts the process.

(O)

The possible reasons are shown below. Please verify and address these.

• The file path is long.

• No access permission is assigned to the folder.

• No upper-level folder exists. Alternatively, no access permission is assigned.

• Free disk space is running short.

• Another program is accessing the folder.

• System resources are running short.

If the problem persists, collect information by using the information collection tool and contact the system administrator.

Out of memory has occurred.

(S)

The system aborts the process.

(O)

Check the output volume of the execution results (standard output, standard error output) of the command run by the service linkage job and service linkage monitoring job. If the volume of output is too great, adjust it with the options of the command executed by the service linkage job and service linkage monitoring job so that unnecessary information is not output.

In other cases, see 3. Estimates in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide and check whether the amount of memory required to run JP1/AJS3 is secured.

A system error occurred.

(S)

The system aborts the process.

(O)

If maintenance information includes information about a memory shortage, follow the instructions in KNBB6450-E.

Also, if the execution results (standard output) of the command executed from the service linkage monitoring job contain multi-byte characters, check whether the language type and character encoding used by JP1/AJS3 match. If they do not match, adjust the command execution results (standard output) or JP1/AJS3 settings.

If this is not the case, collect the data by using the data collection tool and contact your system administrator.

An unexpected error occurred.

(S)

The system aborts the process.

(O)

Collect the data by using the data collection tool and contact your system administrator.