3.6 Systemwalker Operation Manager Infrastructure Command Output Message

This section describes the messages output by Systemwalker Operation Manager infrastructure commands.

A file write error occurred.

[Description]

The system failed to write the startup parameter file.

[System Action]

Aborts the process.

[System Administrator Response]

Place jobschev.txt into the write enable state, and then execute the command.

jobschev.txt is located in the following:

[Windows version]

Systemwalker installation directory\MPWALKER.JM\mpjobsch\etc\jobschev.txt

Systemwalker installation directory\MPWALKER.JM\mpjobsch\etc\jobschevn.txt

"n" of "jobschevn" indicates a subsystem number (1 to 9).

[UNIX version]

Solaris version: /var/opt/FJSVJOBSC/etc/jobschev.txt

or /var/opt/FJSVJOBSC/JOBDBn/etc/jobschev.txt

HP-UX version: /opt/FHPJOBSCH/db/etc/jobschev.txt

or /opt/FHPJOBSCH/db/JOBDBn/etc/jobschev.txt

AIX version: /usr/FAIXJOBSC/db/etc/jobschev.txt

or /usr/FAIXJOBSC/db/JOBDBn/etc/jobschev.txt

Linux version: /var/opt/FJSVJOBSC/etc/jobschev.txt

or /var/opt/FJSVJOBSC/JOBDBn/etc/jobschev.txt

"n" of "JOBDBn" indicates a subsystem number (1 to 9). When the subsystem number is zero, this file will be stored in the same directory as when not using multiple subsystems.

A file write error occured.system_number=n

[Description]

The system failed to write the startup parameter file of subsystem n.

[Parameter]

n: Subsystem number:

[System Action]

Aborts the process.

[System Administrator Response]

Place jobschev.txt into the write enable state, and then execute the command.

For information about the jobschev.txt storage place, see message "A file write error occurred" in this chapter.

Administrator not qualified.

[Description]

A user who does not belong to the Administrators group has executed a command available only for users in the Administrators group.

[System Action]

Aborts the process.

[User Response]

When executing the command, the user must belong to the Administrators group.

DBPATH is incorrect.

[Description]

Invalid path information has been specified for the database directory.

The following reasons are assumed:

No database directory is specified in the startup parameter of the Jobscheduler service.
The Jobscheduler service is not started.

[System Action]

Aborts the process.

[System Administrator Response]

If the specified database directory is wrong, correct it. Start the Jobscheduler service if not done.

[Windows]ERROR: csv data output error

[Description]

The system failed to write the specified csv file.

[System Action]

Aborts the process.

[User Response]

Remove the cause of impossibility of writing in the specified CSV format file.

ERROR: CSV data output error

[Description]

The system failed to write the specified csv file.

[Parameters]

XXXX: csv file name

[System Action]

Aborts the process.

[User Response]

Remove the cause of impossibility of writing in the specified CSV format file.

[Windows]ERROR: Failure in getting tree data for monitor_hosts_ex.

[Description]

The system failed to acquire the basic tree information registered in the configuration information database.

[System Action]

Aborts the process.

[System Administrator Response]

Remove factors that caused a process start failure, for example, memory usage and number of active processes.

[Windows]ERROR: Failure in WSAStartup.

[Description]

An error occurred in the socket initialization function.

[System Action]

Aborts the process.

[System Administrator Response]

Check whether network is connectable.

Otherwise, check whether the network environment is defined properly.

[Windows]ERROR: get tree data for monitor_hosts_ex.

[Description]

One of the following phenomena occurred:

The system failed to read the monitoring host definition file (CSV).
An input-output error occurred while writing the monitoring host definition file (Systemwalker installation directory \MPWALKER.JM\mpjmsrv\etc\monitor_hosts_ex).
Memory reservation failed.
Inconsistency occurred in the monitoring host definition file (CSV).

[System Action]

Aborts the process.

[System Administrator Response]

Confirm whether the monitoring host is defined properly. If it is not defined properly, correct it. If it is defined properly, check the memory usage.

ERROR: Input data error occurred.

[Description]

An error occurred while reading a CSV file.

[System Action]

Aborts the process.

[System Administrator Response]

Remove the cause by which the system cannot refer to the CSV file.

ERROR: Input data error occurred. line=n

[Description]

The CSV file contains a host name including a space or tab character.

[Parameters]

n: Line number

[System Action]

Ignore a host name including a space or tab character.

[System Administrator Response]

Correct the CSV file

ERROR: monitor_hosts_ex file access error

[Description]

An error occurred when the monitoring host definition file (monitor_hosts_ex) was read.

[System Action]

Aborts the process.

[System Administrator Response]

Check whether the monitoring host definition file can be referenced. The monitoring host definition file is located in--

Solaris version: /var/opt/FJSVJMCMN/etc

HP-UX version: /opt/FHPJMCMN/db/etc

AIX version: /usr/FAIXJMCMN/db/etc

Linux version: /var/opt/FJSVJMCMN/etc

ERROR: monitor_hosts_ex file open error

[Description]

An error occurred when the monitoring host definition file (monitor_hosts_ex) was opened.

[System Action]

Aborts the process.

[System Administrator Response]

Check whether the monitoring host definition file can be referenced. The monitoring host definition file is located in--

Solaris version: /var/opt/FJSVJMCMN/etc

HP-UX version: /opt/FHPJMCMN/db/etc

AIX version: /usr/FAIXJMCMN/db/etc

Linux version: /var/opt/FJSVJMCMN/etc

[Windows]ERROR: Systemwalker Centric Manager not found

[Description]

The -get option is not available because Systemwalker Centric Manager is not installed.

[System Action]

Aborts the process.

[System Administrator Response]

Systemwalker Centric Manager must be installed to use the -get option.

Check that Systemwalker Centric Manager is installed properly.

ERROR: Systemwalker Operation Manager not found

[Description]

Systemwalker Operation Manager is not installed.

[System Action]

Aborts the process.

[System Administrator Response]

Check that Systemwalker Centric Manager is installed properly.

[Windows]ERROR: temporary file not made

[Description]

A temporary file cannot be created to use the omgrmonitor command.

[System Action]

Aborts the process.

[System Administrator Response]

Confirm the disk space and file system configuration.

[UNIX]Jobscheduler daemon is started. The jmmode command cannot be used.

[Description]

This command is not available while the Jobscheduler daemon is running.

[System Action]

Aborts the process.

[System Administrator Response]

Stop the daemon before executing the command.

[UNIX]Jobscheduler:n daemon is started. The jmmode command cannot be used.

[Description]

This command is not available while the Jobscheduler daemon is running.

[Parameters]

n: Subsystem number

[System Action]

Aborts the process.

[System Administrator Response]

Stop the daemon before executing the command.

[UNIX]MicroJES daemon is started. The jmmode command cannot be used.

[Description]

This command is not available while the Job Execution Control daemon is running.

[System Action]

Aborts the process.

[System Administrator Response]

Stop the daemon before executing the command.

[UNIX]MicroJES:n daemon is started. The jmmode command cannot be used.

[Description]

This command is not available while the Job Execution Control daemon is running.

[Parameters]

n: Subsystem number

[System Action]

Aborts the process.

[System Administrator Response]

Stop the daemon before executing the command.

monitor_hosts_ex data get error.

[Description]

The system failed to create monitoring host information due to memory shortage.

[System Action]

Aborts the process.

[System Administrator Response]

Check the memory space. When some applications consume a large amount of memory space, execute this command in a time span in which the applications do not run.

[Windows]Systemwalker MpJobsch service is started. The jmmode command cannot be used.

[Description]

This command is not available while the Systemwalker MpJobsch service is running.

[System Action]

Aborts the process.

[System Administrator Response]

Stop the daemon before executing the command.

[Windows]Systemwalker MpJobschn service is started. The jmmode command cannot be used.

[Description]

This command is not available while the Systemwalker MpJobsch service is running.

[Parameters]

n: Subsystem number

[System Action]

Aborts the process.

[System Administrator Response]

Stop the daemon before executing the command.

[Windows]Systemwalker MpMjes service is started. The jmmode command cannot be used.

[Description]

This command is not available while the Systemwalker MpMjes service is running.

[System Administrator Response]

Stop the daemon before executing the command.

[Windows]Systemwalker MpMjesn service is started. The jmmode command cannot be used.

[Description]

This command is not available while the Systemwalker MpMjes service is running.

[Parameters]

n: Subsystem number

[System Administrator Response]

Stop the daemon before executing the command.

[UNIX]The LANG value is incorrect.

[Description]

The code system of the user environment is different from the default of the system, and the command cannot be executed.

[System Action]

Aborts the process.

[User Response]

Specify the same code system for the user and system default environments to execute the command.

Usage: jmmode { continue | cancel | check } [-func { JOB | WRT }]

[Description]

Correct parameter format of the jmmode command

[User Response]

Specify the parameter in the correct format.

Usage: jmmode { continue | cancel | check } [-func { JOB | WRT }] [-sys {all | 0 - 9}]

[Description]

Correct parameter format of the jmmode command

[User Response]

Specify the parameter in the correct format.

[Windows]Usage: omgrmonitor { -export filename [ -name monitored_host_configuration_name ] | -import filename [ -name monitored_host_configuration_name ] | -get filename }

[Description]

Correct parameter format of the omgrmonitor command

[User Response]

Specify the parameter in the correct format.

[UNIX]Usage: omgrmonitor { -export filename [ -name monitored_host_configuration_name ] | -import filename [ -name monitored_host_configuration_name ] }

[Description]

Correct parameter format of the omgrmonitor command

[User Response]

Specify the parameter in the correct format.