Job Management Partner 1/Automatic Job Management System 3 - Web Operation Assistant Description, Operator's Guide and Reference

[Contents][Glossary][Index][Back][Next]


9.2 Messages

KAVI3000-I


JP1/AJS2 - Web Operation Assistant started.

The JP1/AJS3 WOA Web Application Server service has started normally.

(S)
Outputs information to the log, to indicate that the JP1/AJS3 WOA Web Application Server service has started.

KAVI3001-E


JP1/AJS2 - Web Operation Assistant failed to start.

An attempt to start the JP1/AJS3 WOA Web Application Server service has failed, because an error occurred during startup processing.

(S)
Cancels startup of the JP1/AJS3 WOA Web Application Server service.

(O)
A message indicating the cause of the error was output to the log information before this message. Check the cause of the error according to the log information (see 8.2 Log information).

KAVI3002-E


JP1/AJS2 - Web Operation Assistant is not running.

You could not log on because the JP1/AJS3 WOA Web Application Server service was not running.

(S)
Cancels the logon processing.

(O)
Make sure that the JP1/AJS3 WOA Web Application Server service has started. If it has not started, start the JP1/AJS3 WOA Web Application Server service.

KAVI3003-I


The button-name button was pressed on window-name window-type.

This message informs that the button was clicked during operation of JP1/AJS3 - Web Operation Assistant.

(S)
Has output information to the log to indicate that the button was clicked during operation of JP1/AJS3 - Web Operation Assistant.

KAVI3004-W


Invalid specification in configuration definition. (item-name)

The JP1/AJS3 WOA Web Application Server service has started using the default environment settings parameters, because the configuration file contained an invalid specification.

(S)
Uses the default environment settings parameters to continue startup processing of the JP1/AJS3 WOA Web Application Server service.

(O)
Revise the specified environment settings parameters in the configuration file (see 3.3.1 How to define the configuration file (environment settings parameters)). After revising the settings, stop the JP1/AJS3 WOA HTTP Server service, restart the JP1/AJS3 WOA Web Application Server service, and then start the JP1/AJS3 WOA HTTP Server service.

KAVI3005-E


Login is invalid. Please log in again.

The session to which you currently log on has been disabled. Log on again. If you log off after creating a new window, your logon will be disabled for the remaining open windows.

(S)
Cancels processing.

(O)
Log on again, and then re-execute the operation. If more than one window created after logon is open, close all but one window, and then log on again (see 1.5(3) Notes on operations).

KAVI3006-E


The log output processing could not be initialized. Detailed information (detailed-information-1, detailed-information-2)

An attempt to start the JP1/AJS3 WOA Web Application Server service has failed, due to an error that occurred during output of the integrated trace log.

(S)
Cancels startup of the JP1/AJS3 WOA Web Application Server service.

(O)
Contact the system administrator and collect information (see 8.4 Method for collecting information).

KAVI3007-E


The log could not be output. Detailed information (detailed-information-1, detailed-information-2)

An attempt to output the integrated trace log has failed. There might be a problem with the integrated trace function.

(S)
Cancels the output of the integrated trace log.

(O)
Contact the system administrator and collect information (see 8.4 Method for collecting information).

KAVI3008-W


An attempt to terminate the log output processing failed. Detailed information (detailed-information-1, detailed-information-2)

An attempt to stop the output of the integrated trace log has failed.

(S)
Continues processing to stop the JP1/AJS3 WOA Web Application Server service.

(O)
Contact the system administrator and collect information (see 8.4 Method for collecting information).

KAVI3009-E


Operations can be done only from the page which displays the latest information.

Operations are only possible on the JP1/AJS3 - Web Operation Assistant page from which the status was last acquired.

(S)
Cancels the attempted processing.

(O)
Execute the operation on the JP1/AJS3 - Web Operation Assistant page from which the status was last acquired. Alternatively, re-acquire the status, and then re-execute the operation.
If more than one window created after logon is open, close all but one of the windows, and then log on again (see 1.5(3) Notes on operations).

KAVI3010-I


RECV: receive-data

This message indicates that the JP1/AJS3 WOA Web Application Server service has received data.

(S)
Outputs information to the log, to indicate that the JP1/AJS3 WOA Web Application Server service has received data.

KAVI3011-E


The initialization process for remote command failed.

An attempt to start the JP1/AJS3 WOA Web Application Server service has failed because initialization for remote command execution failed.

(S)
Cancels startup of the JP1/AJS3 WOA Web Application Server service.

(O)
A message indicating the cause of the error was output to the log information before this message. Check the cause of the error according to the log information (see 8.2 Log information).

KAVI3012-E


An attempt to initialize the processing of the folder (folder-name) has failed.

An attempt to start the JP1/AJS3 WOA Web Application Server service has failed, because initialization of the folder has failed.

(S)
Cancels startup of the JP1/AJS3 WOA Web Application Server service.

(O)
Make sure that you have access permissions for both the SYSTEM and Administrators groups for the folder shown in the message, or the folders and files in that folder.

KAVI3013-I


Make cookie available.

Cookies are disabled in the Web browser settings. Since JP1/AJS3 - Web Operation Assistant uses cookies, you must enable them.

(S)
Cancels logon processing.

(O)
In Internet Explorer, choose Internet Options, click the Privacy tab, and then enable cookies. For details, see Help for Internet Explorer.

KAVI3014-E


Specify (field-name).

(S)
Cancels processing.

(O)
Enter a value in field-name, and then re-execute the operation.

KAVI3090-I


JP1/AJS2 - Web Operation Assistant is terminated.

The JP1/AJS3 WOA Web Application Server service has terminated normally.

(S)
Outputs information to the log, to indicate that the JP1/AJS3 WOA Web Application Server service has terminated.

KAVI3100-E


The specified user (user-name) is not registered to this system.

You cannot log on because the information set for the specified JP1 user is not contained in the user environment settings file.

(S)
Cancels logon processing.

(O)
In the user environment settings file, enter the information set for the specified JP1 user (for details about how to code the user environment settings file, see 4.2 Environment defined in the user environment settings file).

KAVI3200-E


Select observation targets.

The status could not be acquired because the items to be monitored were not specified in the frame for setting status acquisition conditions.

(S)
Cancels the status acquisition.

(O)
Specify the items to be monitored in the frame for setting status acquisition conditions, and then re-acquire the status.

KAVI3201-E


No unit satisfies the specified conditions.

As a result of status acquisition, the unit that meets the specified conditions is not found.

(S)
Cancels the status acquisition.

(O)
Review the settings for monitoring target and search conditions in frame for setting status acquisition conditions.
In addition, if the database type for the monitoring target scheduler service is embedded database or HiRDB, check if a status acquisition mode has been set for the RDB connection definition.
If a status acquisition mode has been set, check if the server type for the RDB connection definition has been set correctly.

KAVI3202-E


Input host name.

The status could not be acquired because the host name for the items selected to be monitored was not specified in the frame for setting status acquisition conditions.

(S)
Cancels the status acquisition.

(O)
Specify the host name for the items selected to be monitored in the frame for setting status acquisition conditions, and then re-acquire the status.

KAVI3203-E


Input scheduler service name.

The status could not be acquired because the scheduler service name for the items selected to be monitored was not specified in the frame for setting status acquisition conditions.

(S)
Cancels the status acquisition.

(O)
Specify the scheduler service name for the items selected to be monitored in the frame for setting status acquisition conditions, and then re-acquire the status.

KAVI3204-E


Input unit name.

The status could not be acquired because the unit name for the items selected to be monitored was not specified in the frame for setting status acquisition conditions.

(S)
Cancels the status acquisition.

(O)
Specify the unit name for the items selected to be monitored in the frame for setting status acquisition conditions, and then re-acquire the status.

KAVI3207-E


Input the number of rows per page.

The status could not be acquired when Display (*** records/page) was specified for the display method in the frame for setting status acquisition conditions, because the number of records per page was not specified.

(S)
Cancels the status acquisition.

(O)
Specify the number of records to be displayed per page in the frame for setting status acquisition conditions, and then re-acquire the status.

KAVI3209-E


Input comment string.

The status could not be acquired, because a comment string was used as a search condition, but no comment string was specified in the frame for setting status acquisition conditions.

(S)
Cancels the status acquisition.

(O)
Specify the string for the comments you want to search for, and then re-acquire the status.

KAVI3210-E


Input execution host name.

The status could not be acquired when a target host name was used as a search condition, because the target host name to be searched for was not specified in the frame for setting status acquisition conditions.

(S)
Cancels the status acquisition.

(O)
Specify the target host name to be searched for, and then re-acquire the status.

KAVI3211-E


Input complete unit name.

The status could not be acquired because a complete unit name, beginning with a forward slash (/), was not specified for the unit name selected to be monitored in the frame for setting status acquisition conditions.

(S)
Cancels the status acquisition.

(O)
Specify a complete unit name, beginning with a forward slash, for the unit name selected to be monitored in the frame for setting status acquisition conditions, and then re-acquire the status.

KAVI3212-E


Cannot treat as unit.

The status could not be acquired because the unit name selected to be monitored in the frame for setting status acquisition conditions contained any of the following invalid characters:

\ " [ ] ` ( ) = ; (semicolon) : (colon) , (comma)

(S)
Cancels the status acquisition.

(O)
Correctly specify the unit name selected to be monitored in the frame for setting status acquisition conditions, and then re-acquire the status (for details about the valid characters for unit names, see 6.3.3 Frame for setting status acquisition conditions).

KAVI3220-I


Status acquisition started.: maintenance-information

This message indicates that the status acquisition has started.

(S)
Outputs information to the log, to indicate that the status acquisition has started.

KAVI3221-I


Status acquisition ended.: maintenance-information

This message indicates that the status acquisition has ended.

(S)
Outputs information to the log, to indicate that the status acquisition has ended.

KAVI3222-I


RDB connection definition has been set up. : maintenance-information

The parameters specified in the RDB connection definition file have been set.

(S)
Outputs information to the log to indicate that the specified parameters have been set in the RDB connection definition file.

KAVI3250-E


An error occurred in database: maintenance-information-1 maintenance-information-2

An attempt to acquire the status has failed, because an error occurred during access to the database for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager.

(S)
Cancels the status acquisition.

(O)
Check the log information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager to find the cause of the error, and then resolve the problem. (When the monitoring target is JP1/AJS3 - Manager, see the manual Job Management Partner 1/Automatic job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17. Troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)
If a firewall exists between the host on which the JP1/AJS3 WOA Web Application Server service has started and the embedded database or HiRDB for the scheduler database to be monitored, check the firewall settings. Also check the settings of the RDB connection definition file. For details about the RDB connection definition file and its settings, see 3.8.3 Settings on JP1/AJS3- Web Operation Assistant.
If the error occurs repeatedly, check the database configuration definition, and correct any errors. (For details about the database settings, when the monitoring target is JP1/AJS3 - Manager, see C. Advanced Setup of an Embedded Database in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1, when the monitoring target is JP1/AJS2 - Manager, see 3.5 Determine the database to use in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)
If the error still persists, contact the system administrator and collect information (see 8.4 Method for collecting information).

KAVI3280-I


INFORMATION : (maintenance-information)

This message provides maintenance information for JP1/AJS3 - Web Operation Assistant.

(S)
Outputs maintenance information for JP1/AJS3 - Web Operation Assistant to the log.

KAVI3281-E


An unexpected error occurred during status acquisition.: (maintenance-information)

An attempt to acquire the status has failed, because an unexpected error occurred during status acquisition.

(S)
Cancels the status acquisition.

(O)
Contact the system administrator and collect information (see 8.4 Method for collecting information).

KAVI3282-E


Invalid data was detected during status acquisition. : (maintenance-information)

An attempt to acquire the status has failed, because an unexpected data format was detected during status acquisition.

(S)
Cancels the status acquisition.

(O)
Make sure that no TCP/IP communication error occurred between the monitoring target JP1/AJS3 - Manager host or JP1/AJS2 - Manager host and the host running the JP1/AJS3 WOA Web Application Server service. If communication is not possible, check and, if necessary, revise the network settings, including hardware.
Alternately, make sure that mix-ups of character set types did not occur in the monitoring target JP1/AJS3 - Manager host or JP1/AJS2 - Manager host. If any mix-ups occurred, revise the character set type setting. (see 1.5(1) Notes on the environment.)
If the error occurs repeatedly, check the log information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager to find the cause of the error, and then resolve the problem. (When the monitoring target is JP1/AJS3 - Manager, see the manual Job Management Partner 1/Automatic job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17. Troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)
If the error still persists, contact the system administrator and collect information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager. (When the monitoring target is JP1/AJS3 - Manager, see 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17.4 Collecting information for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)

KAVI3283-E


An error occurred in the temporary input file during status acquisition. : (maintenance-information)

An attempt to acquire the status has failed, because an attempt to read the file failed during status acquisition.

(S)
Cancels the status acquisition.

(O)
Re-acquire the status.
If the error occurs repeatedly, contact the system administrator and collect information (see 8.4 Method for collecting information).

KAVI3284-E


An error occurred in the monitoring target during status acquisition. : (maintenance-information)

An attempt to acquire the status has failed, because an error occurred in the monitoring target JP1/AJS3 - Manager during status acquisition.

(S)
Cancels the status acquisition.

(O)
Check the log information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager to find the cause of the error, and then resolve the problem. (When the monitoring target is JP1/AJS3 - Manager, see the manual Job Management Partner 1/Automatic job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17. Troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)
If the error persists, contact the system administrator and collect information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager. (When the monitoring target is JP1/AJS3 - Manager, see 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17.4 Collecting information for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)

KAVI3285-E


The monitoring target JP1/AJS2 could not accept the request. : (maintenance-information)

An attempt to acquire the status has failed, because the version of the monitoring target JP1/AJS2 - Manager was not applicable to JP1/AJS3 - Web Operation Assistant.

(S)
Cancels the status acquisition.

(O)
Make sure that the version of the monitoring target JP1/AJS2 - Manager is 08-00 or later. If it is not, you must change the version of the monitoring target JP1/AJS2 - Manager to 08-00 or later.
When the scheduler database to be monitored is ISAM, make sure that the version of the monitoring target JP1/AJS2 - Manager is applicable to each item displayed in the status list. For details about the version of the monitoring target JP1/AJS2 - Manager required for each item displayed, see 4.3.4 Items displayed in the status list.
If the version is correct but the error occurs repeatedly, contact the system administrator and collect information (see 8.4 Method for collecting information).

KAVI3400-I


Select operation targets.

The operation could not be executed, because the operation target unit was not selected in the statuses frame or status confirmation frame.

(S)
Cancels the attempted operation.

(O)
Select the operation target unit, and then re-execute the operation.

KAVI3401-I


Specify the operation options.

An operation option is not specified.

(S)
Cancels the attempted operation.

(O)
An operation option is not specified, or Do not change is specified for all items. Select operation options, and then re-execute the operation.

KAVI3410-E


Since the unit under operation, it cannot perform specified operation.

The operation could not be executed, because the specified unit was undergoing another operation in JP1/AJS3 - Web Operation Assistant.

(S)
Cancels the attempted operation.

(O)
Check the operation results for the specified unit, and then re-execute the operation when the status of the unit is other than Now running.

KAVI3411-I


The object of deletion does not exist.

The Operation Results list in the operation results frame did not contain the result to be deleted.

(S)
Cancels deletion of the results displayed in the operation results frame.

KAVI3412-I


Performed the next operation to observe. (maintenance-information)

The operation was performed on the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager.

(S)
Outputs information to the log, to indicate that the specified operation was performed.

KAVI3413-I


The operation (operation-name) was performed execution result. (maintenance-information)

This message indicates that the execution results of the operation were obtained.

(S)
Outputs the execution results of the operation to the log.

KAVI3414-E


The inaccurate command sentence was performed. : maintenance-information

The operation could not be executed, because an invalid command was executed in the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager. The probable causes are as follows:

  • The network was disconnected.
  • There is a network routing problem.
  • Data on the network was corrupted.

(S)
Cancels the operation.

(O)
Make sure that no TCP/IP communication error occurred between the monitoring target JP1/AJS3 - Manager host or JP1/AJS2 - Manager host and the host running the JP1/AJS3 WOA Web Application Server service. If communication is not possible, check and, if necessary, revise the network settings, including hardware.
If the error occurs repeatedly, contact the system administrator and collect information. (When the monitoring target is JP1/AJS3 - Manager, see 8.4 Method for collecting information in this manual, and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 troubleshooting . When the monitoring target is JP1/AJS2 - Manager, see 17.4 Collecting information for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)

KAVI3415-E


The JP1/AJS2 being monitored could not receive the request for the operation (operation-name).

The operation could not be executed because the JP1/AJS being monitored rejected the operation option that contains an error.

(S)
Cancels the specified operation.

(O)
Check the options specified for operation, correct the error, and then re-execute the operation.
If this error message appears when the job status is being changed, check the OS type of the monitoring target. If the OS type is UNIX, check the value of the specified return code (see 2.2.3 Performing operation from the list view).

KAVI3416-Q


Are you sure you want to delete Operation Results (target : deletion-range)?

This message asks you whether you want to delete the operation results.

(S)
Waits for a response.

(O)
Click OK to delete the operation results. Click Cancel to cancel the deletion.

KAVI3600-E


The user name or password is invalid.

You cannot log on because the JP1 user name or password is invalid.

(S)
Cancels logon processing.

(O)
Enter the JP1 user name or password registered in the monitoring destination authentication server, and then log on.

KAVI3601-Q


Are you sure you want to log out?

This message asks you whether you want to log off JP1/AJS3 - Web Operation Assistant.

(S)
Waits for a response.

(O)
Click OK to log off. Click Cancel to cancel the logoff.

KAVI3602-E


Input user name.

The JP1 user name is not entered in the Login window.

(S)
Cancels logon processing.

(O)
Enter the JP1 user name in the Login window, and then re-execute the logon operation.

KAVI3603-E


Input password.

The password is not entered in the Login window.

(S)
Cancels logon processing.

(O)
Enter the password in the Login window, and then re-execute the logon operation.

KAVI3604-I


User (user-name) logged in.

This message informs that the user has logged on.

(S)
Has output information to the log to indicate that the user has logged on.

KAVI3605-I


User (user-name) logged out.

This message informs that the user has logged off.

(S)
Has output information to the log to indicate that the user has logged off.

KAVI3620-E


Cannot connect to Access Control Server.

Communication was not possible because a connection to the authentication server could not be established. The probable causes are as follows:

  • The authentication server is not running.
  • The host running the JP1/AJS3 WOA Web Application Server service is not connected to the authentication server via the network.

(S)
Cancels authentication processing.

(O)
Make sure that the authentication server is running. Also make sure that no TCP/IP communication error occurred between the monitoring target JP1/AJS3 - Manager host and the host running the JP1/AJS3 WOA Web Application Server service. If communication is not possible, check and, if necessary, revise the network settings, including hardware.
If the error occurs repeatedly, contact the system administrator and collect information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager. (When the monitoring target is JP1/AJS3 - Manager, see 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17.4 Collecting information for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)

KAVI3800-E


The settings file (file-name) was not found.

An attempt to start the JP1/AJS3 WOA Web Application Server service has failed, due to a problem with the settings file. The probable causes are as follows:

  • The file shown in the message was not found.
  • You do not have access permissions for both the SYSTEM and Administrators groups for the file shown in the message and the folder containing the file.
  • Another program is using the file shown in the message.

(S)
Cancels startup of the JP1/AJS3 WOA Web Application Server service.

(O)
Correct the cause of the error. If the file shown in the message is not found, create a file by copying the model file#, and then re-specify the setting.

#
The model file name is the file name shown in the message, with the extension .model.

KAVI3801-E


An error occurred while the settings file (file-name) was being input.

An attempt to start the JP1/AJS3 WOA Web Application Server service has failed, because an attempt to read the settings file has failed. A temporary problem might have occurred in the execution environment for the JP1/AJS3 WOA Web Application Server service.

(S)
Cancels startup of the JP1/AJS3 WOA Web Application Server service.

(O)
Stop the JP1/AJS3 WOA HTTP Server service, restart the JP1/AJS3 WOA Web Application Server service, and then start the JP1/AJS3 WOA HTTP Server service.
If the error occurs repeatedly, contact the system administrator and collect information (see 8.4 Method for collecting information).

KAVI3802-E


An error occurred while the settings file (file-name) was being output.

An attempt to write to the settings file has failed. The probable causes are as follows:

  • You do not have access permissions for both the SYSTEM and Administrators groups for the file shown in the message, and the folder containing the file.
  • Free disk space is insufficient in the machine on which JP1/AJS3 - Web Operation Assistant is installed.
  • Another program is using the file shown in the message.

(S)
Cancels the output of the settings file.

(O)
Correct the cause of the error.

KAVI3803-W


The settings file (file-name) was not found. The default setup is assumed and the processing continues.

The JP1/AJS3 WOA Web Application Server service has started using the default settings, due to a problem with the settings file. The probable causes are as follows:

  • The file shown in the message was not found.
  • You do not have access permissions for both the SYSTEM and Administrators groups for the file shown in the message, and the folder containing the file.
  • Another program is using the file shown in the message.

(S)
Assumes the default settings to continue processing.

(O)
Correct the cause of the error.
If the file shown in the message is not found, check the settings in the User Environment Settings window. If the settings are incorrect, revise them.

KAVI3804-W


An error occurred while the settings file (file-name) was being input. The default setup is assumed and processing continues.

The JP1/AJS3 WOA Web Application Server service has started using the default settings, because the contents of the settings file were invalid. The settings in the User Environment Settings window might not have been applied.

(S)
Assumes the default settings to continue processing.

(O)
Check the settings in the User Environment Settings window. If the settings are incorrect, revise them.

KAVI3805-E


Creation of the folder (folder-name) went wrong.

The file required for monitoring could not be created because an attempt to create a folder has failed.

The probable causes are as follows:

  • The folder could not be created because a file having the same name as this folder already exists on the same level.
  • You do not have access permissions for both the SYSTEM and Administrators groups for the JP1/AJS3 - Web-Operation-Assistant-installation-folder\sys\dbclient folder.
  • Free disk space is insufficient in the machine on which JP1/AJS3 - Web Operation Assistant is installed.

(S)
Cancels the processing in which the error occurred.

(O)
Correct the cause of the error.
If the error occurs repeatedly, contact the system administrator and collect information (see 8.4 Method for collecting information).

KAVI3900-E


A system error has occurred. : maintenance-information

A system error occurred during processing. There might be a problem with the execution environment for the JP1/AJS3 WOA Web Application Server service.

(S)
Cancels the processing in which the error occurred.

(O)
Contact the system administrator and collect information (see 8.4 Method for collecting information).

KAVI3902-E


The error which is not expected during operation execution occurred. : maintenance-information

An unexpected error occurred when the operation was being executed. There might be a problem with the execution environment for the JP1/AJS3 WOA Web Application Server service.

(S)
Cancels the processing in which the error occurred.

(O)
Contact the system administrator and collect information (see 8.4 Method for collecting information).

KAVI3903-E


Insufficient memory occurred. : maintenance-information

Memory became insufficient in the execution environment for the monitoring target JP1/AJS3 - Manager, JP1/AJS2 - Manager or the JP1/AJS3 WOA Web Application Server service.

(S)
Cancels the processing in which the error occurred.

(O)
Check the amount of memory on the host that is running the JP1/AJS3 WOA Web Application Server service.
If the amount of available physical memory is insufficient, terminate unnecessary applications, and then increase the amount of memory available (for details about the physical memory requirements for JP1/AJS3 - Web Operation Assistant, see E.2(1) Estimating memory requirements).

KAVI3905-E


Unexpected error occurred in JP1/AJS2 - Web Operation Assistant. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

An unexpected error occurred during processing. There might be a problem with the execution environment for the JP1/AJS3 WOA Web Application Server service.

(S)
Cancels the processing in which the error occurred.

(O)
Contact the system administrator and collect information (see 8.4 Method for collecting information).

KAVI3906-E


Error occurred in JP1/Base. : maintenance-information

An error occurred in the authentication server and the monitoring target JP1/Base.

(S)
Cancels the processing in which the error occurred.

(O)
Check the log information for the authentication server and monitoring target JP1/Base to find the cause of the error, and then correct the error (see Troubleshooting in the manual Job Management Partner 1/Base User's Guide).

KAVI3920-E


Cannot find required class file. : maintenance-information-1 maintenance-information-2 maintenance-information-3

The operation could not be executed, because the class file required for executing the operation was not found. The file structure for JP1/AJS3 - Web Operation Assistant might be invalid.

(S)
Cancels the processing in which the error occurred.

(O)
Reinstall JP1/AJS3 - Web Operation Assistant.
If the error occurs repeatedly, contact the system administrator and collect information (see 8.4 Method for collecting information).

KAVI3921-E


Cannot find required method. : maintenance-information-1 maintenance-information-2 maintenance-information-3

The operation could not be executed, because the method required for executing the operation was not found. The file structure for JP1/AJS3 - Web Operation Assistant might be invalid.

(S)
Cancels the processing in which the error occurred.

(O)
Reinstall JP1/AJS3 - Web Operation Assistant.
If the error occurs repeatedly, contact the system administrator and collect information (see 8.4 Method for collecting information).

KAVI3922-E


Cannot find required file. : maintenance-information-1 maintenance-information-2

The file required for executing the operation was not found. There may be a problem with the JP1/AJS3 - Web Operation Assistant file structure.

(S)
Cancels the processing in which the error occurred.

(O)
Re-install JP1/AJS3 - Web Operation Assistant.
If the error occurs repeatedly, contact the system administrator and collect information (see 8.4 Method for collecting information).

KAVI4000-E


The parameter (parameter) is not specified by setup of the user (user-name) of a setting file (file-name).

An attempt to start the JP1/AJS3 WOA Web Application Server service has failed, because the required parameter parameter was not specified in the settings file.

(S)
Cancels startup of the JP1/AJS3 WOA Web Application Server service.

(O)
In the settings file, specify the parameter shown in the message (see 4.2.3 Details about the parameters for the user environment settings).

KAVI4001-E


In the settings of the user (user-name) in the settings file (file-name), an invalid value is specified for a parameter (parameter).

An attempt to start the JP1/AJS3 WOA Web Application Server service has failed, because the value of the parameter parameter was incorrectly specified in the settings file.

(S)
Cancels startup of the JP1/AJS3 WOA Web Application Server service.

(O)
Correct the value of the parameter shown in the message (see 4.2.3 Details about the parameters for the user environment settings).

KAVI4002-E


Enter the values lower-limit - upper-limit in the field (field-name).

A value outside the valid range is entered for field-name.

(S)
Cancels the status acquisition, execution of an operation, or application of the environment settings.

(O)
For field-name, enter a value in the range indicated by lower-limit - upper-limit.

KAVI4003-E


Enter a character string within maximum-length for (field-name).

A string exceeding the maximum length was entered for field-name.

(S)
Cancels the application of the environment settings.

(O)
For field-name, enter a string consisting of no more than maximum-length characters.

KAVI4004-E


All display items cannot be made hidden.

An item to be displayed in the status list was not specified.

(S)
Cancels the application of the environment settings.

(O)
Specify at least one item to be displayed in the status list.

KAVI4005-E


All the items of the scheduler service for monitoring cannot be hidden.

An attempt to start the JP1/AJS3 WOA Web Application Server service has failed, because all the scheduler services to be monitored were set to be hidden.

(S)
Cancels startup of the JP1/AJS3 WOA Web Application Server service.

(O)
Specify the user environment settings file so that one or more scheduler services to be monitored will be displayed (see 4.2.3 Details about the parameters for the user environment settings).

KAVI4006-E


item do not exist in the settings file (file-name)

An attempt to start the JP1/AJS3 WOA Web Application Server service has failed, because the required item item did not exist in the settings file.

(S)
Cancels startup of the JP1/AJS3 WOA Web Application Server service.

(O)
Add the item shown in the message to the settings file (see 4.2.3 Details about the parameters for the user environment settings).

KAVI4007-E


Since operation-button-name buttons are set as hidden, setting of set-item cannot be performed.

You cannot set the operation option because the operation-button-name button is set to be hidden.

(S)
Cancels the display of the Default Settings windows for the operation option.

(O)
To set set-item, specify the user environment settings file so that the operation-button-name button will be displayed (see 4.2.3 Details about the parameters for the user environment settings).

KAVI4008-W


An invalid specification exists in the RDB connection definition. (line-number : specification)

The RDB connection definition file contains an invalid specification.

(S)
Ignores the incorrect specification and continues the startup processing of the JP1/AJS3 WOA Web Application Server service.

(O)
Correctly specify the monitoring target name or parameters in the RDB connection definition file (see 3.8.3(2) (c) List of environment settings parameters in the RDB connection definition file). After revising the settings, stop the JP1/AJS3 WOA HTTP Server service, restart the JP1/AJS3 WOA Web Application Server service, and then start the JP1/AJS3 WOA HTTP Server service.

KAVI4009-E


The parameter (parameter) is not specified by the setup for monitoring target (monitoring-target-name) in the RDB connection definition file

An attempt to start the JP1/AJS3 WOA Web Application Server service has failed, because the value of the parameter was incorrectly specified in the RDB connection definition file.

(S)
Cancels startup of the JP1/AJS3 WOA Web Application Server service.

(O)
In the RDB connection definition file, specify the parameter shown in the message.

KAVI4010-E


In the settings of the monitoring target (monitoring-target-name) in the RDB connection definition file, an invalid value is specified for a parameter (parameter).

An attempt to start the JP1/AJS3 WOA Web Application Server service has failed, because the value of the parameter was incorrectly specified in the RDB connection definition file.

(S)
Cancels startup of the JP1/AJS3 WOA Web Application Server service.

(O)
Correct the value of the parameter shown in the message.

KAVI4100-E


Execute the command from the administrator console.

The command failed because it was executed from a Command Prompt window that was not opened with administrator permissions.

(S)
Terminates command processing.

(O)
Re-execute the command from a Command Prompt window that has been opened with administrator permissions.

KAVI4200-E


Since a problem was in JP1/AJS2 of observe , operation was interrupted. : maintenance-information-1 maintenance-information-2

The operation could not be executed due to a problem in the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager. The probable causes are as follows:

  • There is a problem with the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager.
  • The monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager is taking time to perform processing.

(S)
Cancels the status acquisition or operation execution.

(O)
Check the log information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager to find the cause of the error, and then resolve the problem. (When monitoring target is JP1/AJS3 - Manager, see the manual Job Management Partner 1/Automac Job Management System 3 Troubleshooting. When monitoring target is JP1/AJS2 - Manager, see 17. Troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)
If the error occurs repeatedly, contact the system administrator and collect information for the monitoring target JP1/AJS2 - Manager. (When monitoring target is JP1/AJS3 - Manager, see 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. When monitoring target is JP1/AJS2, see 17.4 Collecting information for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)

KAVI4201-E


The user-mapping in JP1/Base of observe has failed. : maintenance-information-1 maintenance-information-2

The operation could not be executed because user mapping failed.

(S)
Cancels the status acquisition or operation execution.

(O)
If the user mapping settings for the authentication server are invalid, correct the cause of the error (see Setting the User Management Functionality in the manual Job Management Partner 1/Base User's Guide).
If the error occurs repeatedly, contact the system administrator and collect information (see 8.4 Method for collecting information).

KAVI4202-E


IO error of a file has occurred. : maintenance-information

The operation failed because a file I/O error occurred. The probable causes are as follows:

When this message appears during operation from a list or during status acquisition for a monitoring target that uses ISAM as a scheduler database:
  • You do not have access permissions, for both the SYSTEM and Administrators groups, for the files and folders in the JP1/AJS3 - Web-Operation-Assistant-installation-folder\uCPSB\CC\web\containers\WOA\webapps\jp1ajs2woa\tmp folder.
  • The free disk space is insufficient in the machine on which JP1/AJS3 - Web Operation Assistant is installed.
  • Another program is using a file in the JP1/AJS3 - Web-Operation-Assistant-installation-folder\uCPSB\CC\web\containers\WOA\webapps\jp1ajs2woa\tmp\rcmd folder.

When this message appears during status acquisition for a monitoring target that uses an embedded database or HiRDB as a scheduler database:
  • You do not have access permissions for both the SYSTEM and Administrators groups for the JP1/AJS3 - Web-Operation-Assistant-installation-folder\conf\dbclient folder, and the folders and files in that folder.
  • You do not have access permissions for both the SYSTEM and Administrators groups for the JP1/AJS3 - Web-Operation-Assistant-installation-folder\sys folder.
  • Another program is using a file in the JP1/AJS3 - Web-Operation-Assistant-installation-folder\conf\dbclient folder.
  • Free disk space is insufficient in the machine on which JP1/AJS3 - Web Operation Assistant is installed.

When this message appears during startup of the JP1/AJS3 WOA Web Application Server service or during login to JP1/AJS3 - Web Operation Assistant:
  • You do not have access permissions for both the SYSTEM and Administrators groups for the JP1/AJS3 - Web-Operation-Assistant-installation-folder\conf\dbclient folder, and the folders and files contained in that file.
  • Another program is using a file in the JP1/AJS3 - Web-Operation-Assistant-installation-folder\conf\dbclient folder.

(S)
Cancels the status acquisition or operation execution.

(O)
Correct the cause of the error. After correcting the error, stop the JP1/AJS3 WOA HTTP Server service, restart the JP1/AJS3 WOA Web Application Server service, and then start the JP1/AJS3 WOA HTTP Server service.

KAVI4203-E


Host name of observe cannot be resolved to IP address. : maintenance-information

The operation could not be executed, because the host name could not be resolved by using the monitoring target host.

(S)
Cancels the status acquisition or operation execution.

(O)
Specify the settings so that the host name can be resolved by using the monitoring target host.

KAVI4204-E


It was not connectable with the observe. : maintenance-information

The operation could not be executed, because a connection with the monitoring target could not be established. The probable causes are as follows:

  • When the monitoring target is JP1/AJS3 - Manager, the JP1/AJS3 service is not running.
  • When the monitoring target is JP1/AJS2 - Manager, the JP1/AJS2 Monitor service is not running.
  • There is a network problem.
  • There is a problem with JP1/AJS3 - Manager or JP1/AJS2 - Manager on the monitoring target host.

(S)
Cancels the status acquisition or operation execution.

(O)
If the monitoring target is JP1/AJS3 - Manager, make sure that the JP1/AJS3 service is running. If the monitoring target is JP1/AJS2 - Manager, make sure that the JP1/AJS2 Monitor service is running. Also make sure that no TCP/IP communication error occurred between the monitoring target JP1/AJS3 - Manager host or JP1/AJS2 - Manager host and the host running the JP1/AJS3 WOA Web Application Server service. If communication is not possible, check and, if necessary, revise the network settings, including hardware.
If the error occurs repeatedly, check log information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager to find the cause of the error, and then resolve the problem. (When the monitoring target is JP1/AJS3 - Manager, see the manual Job Management Partner 1/Automac Job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17. Troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)
If the error still persists, contact the system administrator and collect information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager. (When the monitoring target is JP1/AJS3 - Manager, see 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17.4 Collecting information for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)

KAVI4205-E


It disconnected observe. : maintenance-information

The operation could not be executed, because the connection with the monitoring target was disconnected.

(S)
Cancels the status acquisition or operation execution.

(O)
Make sure that no TCP/IP communication error occurred between the monitoring target JP1/AJS3 - Manager host or JP1/AJS2 - Manager host and the host running the JP1/AJS3 WOA Web Application Server service. If communication is not possible, check and, if necessary, revise the network settings, including hardware.
If the error occurs repeatedly, check the log information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager to find the cause of the error, and then resolve the problem. (When the monitoring target is JP1/AJS3 - Manager, see the manual Job Management Partner 1/Automac Job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17. Troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)
If the error still persists, contact the system administrator and collect information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager. (When the monitoring target is JP1/AJS3 - Manager, see 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17.4 Collecting information for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)

KAVI4206-E


Invalid data received. : maintenance-information

The operation could not be executed, because an unexpected data format was detected.

(S)
Cancels the status acquisition or operation execution.

(O)
Make sure that no TCP/IP communication error occurred between the monitoring target JP1/AJS3 - Manager host or JP1/AJS2 - Manager host and the host running the JP1/AJS3 WOA Web Application Server service. If communication is not possible, check and, if necessary, revise the network settings, including hardware.
If the error persists, check the log information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager to find the cause of the error, and then resolve the problem. (When the monitoring target is JP1/AJS3 - Manager, see the manual Job Management Partner 1/Automac Job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17. Troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)
If the error still persists, contact the system administrator and collect information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager. (When the monitoring target is JP1/AJS3 - Manager, see 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17.4 Collecting information for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)

KAVI4207-E


A timeout occurred during interprocess communication. : maintenance-information

A timeout occurred during the wait for a response from JP1/AJS3 - Manager or JP1/AJS2 - Manager. The probable causes are as follows:

  • There is a network problem.
  • There is a problem with the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager.
  • The monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager is taking time to perform processing.

(S)
Cancels the status acquisition or operation execution.

(O)
Make sure that no TCP/IP communication error occurred between the monitoring target JP1/AJS3 - Manager host or JP1/AJS2 - Manager host and the host running the JP1/AJS3 WOA Web Application Server service. If communication is not possible, check and, if necessary, revise the network settings, including hardware.
If the error occurs repeatedly, check the log information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager to find the cause of the error, and then resolve the problem. (When the monitoring target is JP1/AJS3 - Manager, see the manual Job Management Partner 1/Automac Job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17. Troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)
If the error still persists, contact the system administrator and collect information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager. (When the monitoring target is JP1/AJS3 - Manager, see 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17.4 Collecting information for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)

KAVI4208-E


The error information from observe was unacquirable. : maintenance-information

An error occurred in the monitoring target, but information about the error could not be acquired. The probable causes are as follows:

  • You do not have access permissions, for both the SYSTEM and Administrators groups, for the files and folders in the JP1/AJS3 - Web-Operation-Assistant-installation-folder\uCPSB\CC\web\containers\WOA\webapps\jp1ajs2woa\tmp folder.
  • The free disk space is insufficient in the machine on which JP1/AJS3 - Web Operation Assistant is installed.
  • Another program is using a file in the JP1/AJS3 - Web-Operation-Assistant-installation-folder\uCPSB\CC\web\containers\WOA\webapps\jp1ajs2woa\tmp\rcmd folder.

(S)
Cancels the status acquisition or operation execution.

(O)
Correct the cause of the error.
If the error occurs repeatedly, contact the system administrator and collect information. (when the monitoring target is JP1/AJS3 - Manager, see 8.4 Method for collecting information in this manual, and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting, when monitoring target is JP1/AJS2 - Manager, when the monitoring target is JP1/AJS2 - Manager, 17.4 Collecting information for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)

KAVI4209-E


Communication access was denied at the connection destination. : maintenance-information

The operation could not be executed, because JP1/Base on the authentication server was set up to reject communications for the host name or IP address specified for the monitoring target host.

(S)
Cancels the status acquisition or operation execution.

(O)
Check the settings of JP1/Base on the authentication server, and make sure that the IP bind method is set for the physical host for receiving data. (see 1.9 Communication protocol of JP1/Base in the manual Job Management Partner 1/Base User's Guide). If the IP bind method is set, specify the IP address set for the monitoring target host, or the host name which can be resolved to that IP address.

KAVI4210-E


JP1/AJS2 of observe does not correspond to this system. : maintenance-information

The operation could not be executed, because the version of the monitoring target JP1/AJS2 - Manager was not 08-00 or later.

(S)
Cancels the status acquisition or operation execution.

(O)
Make sure that the version of the monitoring target JP1/AJS2 - Manager is 08-00 or later. If it is not, you must change the version of the monitoring target JP1/AJS2 - Manager to 08-00 or later.
If the version is correct but the error still occurs, contact the system administrator and collect information (see 8.4 Method for collecting information).

KAVI4211-E


The specified scheduler service does not exist. : maintenance-information

The operation could not be executed, because the specified scheduler service was not defined in the host to be monitored.

(S)
Cancels the status acquisition or operation execution.

(O)
Make sure that both the target host name and the scheduler service exist.

KAVI4212-E


Error occurred in JP1/Base of connection place. : maintenance-information

The status could not be acquired, or the operation could not be executed, because an error occurred in JP1/Base used in the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager.

(S)
Cancels the status acquisition or operation execution.

(O)
Check the log information for JP1/Base used in the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager to find the cause of the error, and then resolve the problem. (See 15. Troubleshooting in the manual Job Management Partner 1/Base User's Guide.)

KAVI4213-E


Error occurred in JP1/AJS2 to observe. (Remote error code: error-code)

The operation could not be executed due to a problem in the monitoring target JP1/AJS3 - Manager. The probable causes are as follows:

  • The monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager has a problem.
  • The monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager is taking time to execute processing.

(S)
Cancels the status acquisition or operation execution.

(O)
Check the log information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager to find the cause of the error, and then resolve the problem. (When the monitoring target is JP1/AJS3 - Manager, see the manual Job Management Partner 1/Automac Job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17. Troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)
If the error persists, contact the system administrator and collect information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager. (When the monitoring target is JP1/AJS3 - Manager, see 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17.4 Collecting information for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)

KAVI4214-E


Setup is not performed to be observed by this host.

The operation could not be executed, because the specified scheduler service was not set up so that it could be monitored from the monitoring host.

(S)
Cancels the status acquisition or operation execution.

(O)
To monitor the scheduler service, execute the ajswoarelsetup command on the JP1/AJS3 - Manager host or JP1/AJS2 - Manager host containing the scheduler service (see 3.1.1 Setting up JP1/AJS3 - Manager or JP1/AJS2 - Manager).

KAVI4215-E


An error occurred in the standard output file. : maintenance-information

The status could not be acquired, or the operation could not be executed, because an attempt to write to the standard output file has failed. The probable causes are as follows:

  • You do not have access permissions for both the SYSTEM and Administrators groups, for the files and folders in the JP1/AJS3 - Web-Operation-Assistant-installation-folder\uCPSB\CC\web\containers\WOA\webapps\jp1ajs2woa\tmp folder.
  • The free disk space is insufficient in the machine on which JP1/AJS3 - Web Operation Assistant is installed.

(S)
Cancels the status acquisition or operation execution.

(O)
Correct the cause of the error.

KAVI4217-E


The following error occurred in the monitor target JP1/AJS2. : (error-details)

The status could not be acquired, or the operation could not be executed, because an error occurred in the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager.

(S)
Cancels the status acquisition or operation execution.

(O)
Check the details about the error shown in the message and the log information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager to find the cause of the error, and then resolve the problem. (When the monitoring target is JP1/AJS3 - Manager, see the manual Job Management Partner 1/Automac Job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17. Troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)
If the error occurs repeatedly, contact the system administrator and collect information for the monitoring target JP1/AJS3 - Manager or JP1/AJS2 - Manager. (When the monitoring target is JP1/AJS3 - Manager, see 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. When the monitoring target is JP1/AJS2 - Manager, see 17.4 Collecting information for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 2 Planning and Administration Guide.)

KAVI4218-E


Cannot connect to the RDB destination host (host-name) that is set in the scheduler service of the monitored object.

A connection could not be established with the RDB connection-destination host that is defined in the scheduler service to be monitored. The probable causes are as follows:

  • An invalid value is specified for the environment settings parameter RDB-connection-destination-host-name for the monitoring target scheduler service for the scheduler service to be monitored.
  • There is a network problem.

(S)
Cancels the status acquisition.

(O)
Check and, if necessary, revise the value of RDB-connection-destination-host-name set for an environment setting parameter for the scheduler service to be monitored. (When the monitoring target is JP1/AJS3 - Manager, see 2.2 Setting up the scheduler service environment in Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2, when the monitoring target is JP1/AJS2 - Manager, see 4.1.3 Defining the scheduler file configuration or 14.1.3 Defining the scheduler service environment setting parameters in the manual Job Management Partner 1/Automatic Job Management System 2 Setup Guide).
Make sure that no TCP/IP communication error occurred between the host specified in RDB-connection-destination-host-name for the environment setting parameter for the scheduler service to be monitored, and the host running the JP1/AJS3 WOA Web Application Server service. If communication is not possible, check and, if necessary, revise the network settings, including hardware. If the error occurs repeatedly, contact the system administrator and collect information (see 8.4 Method for collecting information).

[Contents][Back][Next]


[Trademarks]

Copyright (C) 2010, Hitachi, Ltd.
Copyright (C) 2010, Hitachi Software Engineering Co., Ltd.