This section explains messages starting with MpStem.
Those messages are output by the Master Schedule Management function.
Content output in the Master Schedule Management function detailed error information file and its storage location
The Master Schedule Management function detailed error information file is output when a system error such as a failure in system call for the Master Schedule Management function occurs, and contains the detailed error information. The content of the error information and the file storage location are as follows.
Output content
****************** Occurring time of Error : YYYY/MM/DD HH:MM:SS ***************** Error code = [aaaaa] [Error information] MESSAGETEXT PID:nnnnn xxxxx yyyyy(zzzzz)
The output items have the following meanings.
Date and time of occurrence of the phenomenon
Error code of the Master Schedule Management function
This item is not always output.
Message describing the occurred phenomenon
Process ID of the process with which the error occurred
Storage location
Systemwalker installation directory
\mpwalker.jm\mpstemsv\stemDBn\log\errdump.log (n signifies a subsystem number)
/var/opt/FJSVstem/stemDBn/log/errdump.log (n signifies a subsystem number)
[Description]
The schedule management command has been executed to extract and apply schedules for daily management. The message shows the date yyyymmdd to schedule the operation.
[Parameter]
yyyymmdd: Date
[System Action]
Continues processing.
[Description]
The schedules for daily management have been extracted and applied successfully. The message shows the date yyyymmdd of the scheduled operation.
[Parameter]
yyyymmdd: Date
[System Action]
Terminates processing successfully.
[Description]
The operation schedule for the date yyyymmdd has already been created and it is not necessary to recreate the schedule. This message appears at the day change time, when the Jobscheduler service or daemon is started, or the user executed the schedule for the current date (today).
[Parameter]
yyyymmdd: Date
[System Action]
Terminates processing successfully.
[Description]
The predefined operational changes have reached the specified release date. The changes have been applied to the master information.
[System Action]
Continues processing.
[Description]
Among the job nets scheduled up to the previous day of the day change time, a job net which has not been handled yet exists.
[System Action]
Continues processing.
[System Administrator Response]
Handle the unfinished job net in the Master Schedule Management [Monitor Carried over Job Nets] window.
[Description]
The number of projects reached the maximum while registering schedules. The obsolete schedules have been moved to the following directory.
Systemwalker installation directory
\mpwalker.jm\mpstemsv\stemDBn\move directory (n signifies a subsystem number)
/var/opt/FJSVstem/stemDBn/move directory (n signifies a subsystem number)
[System Action]
Continues processing.
[System Administrator Response]
When referring to the moved schedules, execute the stemprintnet (saved information confirmation ) command.
[Description]
The operation schedule for the date yyyymmdd has already been created, and the user cannot create another schedule for that date. This message appears when the user executed the schedule management command with an operation date specified.
[Parameter]
yyyymmdd: Date
[System Action]
Aborts processing.
[System Administrator Response]
The master database has been updated for the new schedule. To recreate a schedule for the specified date, use the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window, or re-execute the schedule management command with the reschedule option. The command format of the reschedule mode is:
stemManager -d yyyymmdd -force
[Description]
The schedule could not be created by day change time, because the specified date has some incomplete schedule data. The user may have previously failed to create a schedule by executing the schedule management command for this date.
[Parameter]
yyyymmdd: Date
[System Action]
Aborts processing.
[System Administrator Response]
Schedule the operation in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window or execute the schedule management command with an operation date specified to make a recovery from the previous error and create a schedule.
[Description]
The schedule management command is already started up.
[Parameter]
yyyymmdd: Date
[System Action]
Aborts processing.
[System Administrator Response]
Check the schedule status in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window.
Wait for the current schedule creation completes and retry operation for the date for which schedule was not created (yyyymmdd).
[Description]
An error occurred in the environment for creating schedule information. Refer to Content output in the Master Schedule Management function detailed error information file and its storage location for the error details, and resolve the problem.
[Parameter]
yyyymmdd: Date
[System Action]
Aborts processing.
[System Administrator Response]
Refer to Content output in the Master Schedule Management function detailed error information file and its storage location and resolve the problem. Schedule the operation in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window, or execute the schedule management command with an operation date specified.
[Description]
An error occurred while extracting the schedule information from the master database. Refer to Content output in the Master Schedule Management function detailed error information file and its storage location for the error details, and resolve the problem.
[System Action]
Aborts processing.
[System Administrator Response]
Refer to "Content output in the Master Schedule Management function detailed error information file and its storage location" and resolve the problem. Schedule the operation in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window, or execute the schedule management command with an operation date specified.
[Description]
The schedule management command failed to save the scheduling status. Refer to Content output in the Master Schedule Management function detailed error information file and its storage location for the error details, and resolve the problem.
[System Action]
Aborts processing.
[System Administrator Response]
Refer to Content output in the Master Schedule Management function detailed error information file and its storage location and resolve the problem. Schedule the operation in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window, or execute the schedule management command with an operation date specified.
[Description]
An error occurred while sending the schedule information from the management server to the schedule server. Refer to Content output in the Master Schedule Management function detailed error information file and its storage location for the error details, and resolve the problem.
[Parameter]
XXXX: Server name
[System Action]
Aborts processing.
[System Administrator Response]
Refer to Content output in the Master Schedule Management function detailed error information file and its storage location and resolve the problem. Schedule the operation in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window, or execute the schedule management command with an operation date specified.
[Description]
An error occurred while registering the schedule information to Jobscheduler. Check the operating status of Jobscheduler. Refer to Content output in the Master Schedule Management function detailed error information file and its storage location for the error details, and resolve the problem.
[Parameter]
XXXX: Server name
This is not output when the operation is performed with a single server without registering the schedule server.
[System Action]
Aborts processing.
[System Administrator Response]
Refer to Content output in the Master Schedule Management function detailed error information file and its storage location and resolve the problem. Schedule the operation in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window, or execute the schedule management command with an operation date specified.
[Description]
The system was unable to find the schedule server specified by the schedule management command or in the extracted schedule information.
[Parameter]
XXXX: Server name
[System Action]
Aborts processing.
[System Administrator Response]
Check the schedule server settings, specify the valid schedule server name and execute the schedule management command. Otherwise, match the default host name in the job net definition information with the host name specified on the schedule server. Then, retry operation.
[Description]
An error occurred while saving the project in Systemwalker Operation Manager on the schedule server, because the project data is corrupted, or the user specified for the project owner and access privileges does not exist.
Refer to Content output in the Master Schedule Management function detailed error information file and its storage location for the error details, and resolve the problem.
[Parameter]
XXXX: Project name
[System Action]
Aborts processing.
[System Administrator Response]
Check the project information registered to Systemwalker Operation Manager. If no problem is found, execute the register project master command and schedule the operation in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window, or execute the schedule management command with an operation date specified.
If no project name appears in the Project name field, it means that an error occurred also on the project name management information. Identify the project with corrupted data by referring to the detailed error information and make the recovery as instructed above.
[Description]
An error occurred while saving the schedule in Systemwalker Operation Manager on the schedule server, because the extracted schedule data are corrupted.
Refer to Content output in the Master Schedule Management function detailed error information file and its storage location for the error details, and resolve the problem.
[Parameter]
XXXX: Server name
[System Action]
Aborts processing.
[System Administrator Response]
Refer to Content output in the Master Schedule Management function detailed error information file and its storage location and resolve the problem. Schedule the operation in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window, or execute the schedule management command with an operation date specified.
[Description]
An error occurred while communicating with the schedule server.
[Parameter]
XXXX: Server name
[System Action]
Aborts processing.
[System Administrator Response]
Check the following status first to resolve the problem. Then, retry operation.
The schedule server is running.
Systemwalker Operation Manager is running on the schedule server.
There is no problem on the network.
[Description]
The same host name is defined more than once in the schedule server settings.
[Parameter]
XXXX: Server name
[System Action]
Aborts processing.
[System Administrator Response]
Check the target servers with the Schedule server fields in the Master Schedule Management Environment Setup dialog box and make necessary corrections.
[Description]
The same IP address is defined more than once in the schedule server settings.
[Parameter]
XXXX: IP address
[System Action]
Aborts processing.
[System Administrator Response]
Check the IP addresses of the target servers in the Schedule server fields in the Master Schedule Management Environment Setup dialog box and make necessary corrections.
[Description]
The master schedule management environment is not configured correctly.
Refer to Content output in the Master Schedule Management function detailed error information file and its storage location for the error details, and resolve the problem.
[Parameter]
XXXX: Server name
[System Action]
Aborts processing.
[System Administrator Response]
Check the configuration in the Master Schedule Management Environment Setup dialog box. If the mode indicates invalid settings, reset the mode and apply changes to reconstruct the environment. If Content output in the Master Schedule Management function detailed error information file and its storage location shows an invalid settings of the schedule server, check the list of schedule servers and remove or modify the relevant schedule server then apply the changes.
[Description]
The user cannot schedule the operation for the past date.
During creation of a schedule for daily management
The schedule for daily management cannot be executed for the dates before the schedule status management date.
With a job net submission command
A job net cannot be submitted for a past date.
[Parameter]
yyyymmdd: Date
[System Action]
Aborts processing.
[System Administrator Response]
Do not create past schedule information.
[Description]
The system was unable to schedule the operation for the specified date, because the system previously failed to cancel the schedule on the day.
Refer to Content output in the Master Schedule Management function detailed error information file and its storage location for the error details, and resolve the problem.
[Parameter]
yyyymmdd: Date
[System Action]
Aborts processing.
[System Administrator Response]
Refer to Content output in the Master Schedule Management function detailed error information file and its storage location, resolve the cancellation error, and cancel the schedule again. Once the schedule is cancelled, the user may create a schedule.
[Description]
An error occurred while applying the schedule information to Jobscheduler. Check the operation status of Jobscheduler or the Master Schedule Management in the Master Schedule Management [Status Summary] window. If the cause remains unknown despite the above checks, refer to Content output in the Master Schedule Management function detailed error information file and its storage location for the error details, and resolve the problem.
[Parameter]
mmdd: Date
[System Action]
Aborts processing.
[System Administrator Response]
When the problem is solved, schedule the operation in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window.
[Description]
No subsystem has been created for Systemwalker Operation Manager.
[System Action]
Aborts processing.
[System Administrator Response]
Create a subsystem of Systemwalker Operation Manager and reconfigure the environment in the Master Schedule Management Environment Setup dialog box.
[Description]
The schedule distribution environment setup file is corrupted.
[System Action]
Aborts processing.
[System Administrator Response]
If backup data are available, restore the file from the following backup directory:
<backupdirectory>\omgr\mpstemsv\stemDBn\etc\stemmanager.ini (n signifies a subsystem number)
<backupdirectory>/FJSVstem/stemDBn/etc/stemmanager.ini (n signifies a subsystem number)
Note that restoring the environment setup file also restores the database that stores the schedule status and depending on the date when the backup was created, some information may be lost.
If there is no backup, delete the following file and set up the schedule environment again.
Systemwalker installation directory
\mpwalker.jm\mpstemsv\stemDBn\etc\stemmanager.ini (n signifies a subsystem number)
/var/opt/FJSVstem/stemDBn/etc/stemmanager.ini (n signifies a subsystem number)
[Description]
Future operations within 30 days from the current day can be scheduled.
[Parameter]
yyyymmdd: Date
[System Action]
Aborts processing.
[System Administrator Response]
Do not schedule future operations over 30 days from the current day.
[Description]
The user cannot schedule the operation for a date in the previous year, because the system loses the past startup date information on the day when the year changes.
[Parameter]
yyyymmdd: Date
[System Action]
Aborts processing.
[System Administrator Response]
Do not schedule for a date in the previous year.
[Description]
An error occurred while modifying the operation schedule for the specified date. Refer to Content output in the Master Schedule Management function detailed error information file and its storage location for the error details, and resolve the problem.
[System Action]
Aborts processing.
[System Administrator Response]
Refer to Content output in the Master Schedule Management function detailed error information file and its storage location and resolve the problem. Schedule the operation in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window, or execute the schedule management command with an operation date specified.
[Description]
An error occurred while checking the changes in the operation schedule for the specified date. Refer to Content output in the Master Schedule Management function detailed error information file and its storage location for the error details, and resolve the problem.
[System Action]
Aborts processing.
[System Administrator Response]
Refer to Content output in the Master Schedule Management function detailed error information file and its storage location and resolve the problem. Schedule the operation in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window, or execute the schedule management command with an operation date specified.
[Description]
The user cannot create a new schedule because the operation change performed previously had been failed.
[System Action]
Aborts processing.
[System Administrator Response]
Terminate the schedule of the date that has an abnormal status. Schedule the operation in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window, or execute the schedule management command with an operation date specified.
[Description]
The user cannot specify the schedule server when newly creating a schedule for an operation date.
[System Action]
Aborts processing.
[System Administrator Response]
Specify a subsystem to create a new schedule.
[Description]
The system was unable to distribute the schedule, because the virtual time is not in synchronization between the management server and the schedule server. The message shows the name of the schedule server that is out of synchronization.
[Parameter]
XXXX: Server name
[System Action]
Aborts processing.
[System Administrator Response]
Select the Subsystem in the Master Schedule Management Environment Setup dialog box, check the Set the virtual time and select Synchronize date/time only.
[Description]
The master setting of the project is not registered properly.
[Parameter]
XXXX: Project name
[System Action]
Aborts processing.
[System Administrator Response]
Reconfigure the project master (stemSetPrjMaster).
[Description]
The management server failed to check the schedule registration status on the schedule server during scheduling.
Refer to Content output in the Master Schedule Management function detailed error information file and its storage location for the error details, and resolve the problem.
[Parameter]
XXXX: Server name
[System Action]
Aborts processing.
[System Administrator Response]
Refer to Content output in the Master Schedule Management function detailed error information file and its storage location and resolve the problem. Schedule the operation in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window, or execute the schedule management command with an operation date specified.
[Description]
An error occurred on the schedule server while reporting the schedule application status to the management server.
[System Action]
Aborts processing.
[System Administrator Response]
Schedule the operation in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window.
[Description]
An error occurred while applying the schedule information. Refer to Content output in the Master Schedule Management function detailed error information file and its storage location for the error details, and resolve the problem.
[System Action]
Aborts processing.
[System Administrator Response]
Refer to Content output in the Master Schedule Management function detailed error information file and its storage location and resolve the problem. Schedule the operation in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window.
[Description]
The operation style of Master Schedule Management has been changed from single-server to multi-server structure. The user may no longer perform the recovery tasks for the errors occurred in the operation schedules during the single-server operation.
[System Action]
Aborts processing.
[System Administrator Response]
Cancel the schedule of the date that has an abnormal status, and reschedule the operations. Or, change the operation structure back to the single-server operation, and perform the recovery tasks. Cancel the schedule or schedule the operation in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window, or execute the schedule management command with an operation date specified.
[Description]
There was a string that exceeded the maximum size of the data field at code conversion of schedule information strings. Correct the relevant string of the master information by referring to the information on exceeded fields output to "Content output in the Master Schedule Management function detailed error information file and its storage location".
[Parameter]
XXXX: Schedule server name
[System Action]
Aborts processing.
[System Administrator Response]
After correcting the relevant string output to Content output in the Master Schedule Management function detailed error information file and its storage location of the master information, schedule the operation in the Master Schedule Management [Status Summary] window or Master Schedule Management [Status Details] window, or execute the schedule management command with an operation date specified.
[Description]
It is not possible to distribute schedule information because the version of Systemwalker Operation Manager running on the schedule server is earlier than that of Systemwalker Operation Manager running on the management server.
[Parameter]
XXXX: Name of schedule server
[System Action]
Abort the process.
[System Administrator Response]
Upgrade the version of Systemwalker Operation Manager running on the schedule server, and retry the operation.
[Description]
An unsupported function was included when schedule information was distributed from the management server to the schedule server.
[Parameter]
XXXX: Server name
[System Action]
Aborts processing.
[System Administrator Response]
Definition information that contains an unsupported function is output to Content output in the Master Schedule Management function detailed error information file and its storage location. Correct the master information definition after examining the contents of the detailed error information file of the Master Schedule Management function. After correcting the master information definition, run the schedule in the Master Schedule Management [Status Summary] window or the Master Schedule Management [Status Details] window, or execute the schedule management command with an operation date specified.
[Description]
Past startup day information will be lost if the schedule straddles two years, preventing the schedule from being executed.
[Parameter]
XXXX: Server name
[System Action]
Aborts processing.
[System Administrator Response]
Make sure that past schedules do not straddle two years.
[Description]
There is no schedule to process on the specified date.
[System Action]
Continues processing.
[Description]
An invalid value is specified in the schedule configuration file. The default value will be used.
Storage location of the schedule configuration file:
Systemwalker installation directory
\mpwalker.jm\mpstemsv\stemDBn\etc\stemmanager.ini (n signifies a subsystem number)
/var/opt/FJSVstem/stemDBn/etc/stemmanager.ini (n signifies a subsystem number)
[System Action]
Continues processing with the default value.
[System Administrator Response]
Check the settings in the Master Schedule Management Environment Setup dialog box, and save the settings. This resets all invalid settings in the dialog box, and applies the default settings.
[Description]
The schedule information has been registered more than once.
[Parameter]
XXXX: Server name
[System Action]
Aborts the second processing.
[System Administrator Response]
re-execute the schedule.
[Description]
The system processed the operation changes normally during the scheduling process, but it failed to delete the project used for changing operation.
[System Action]
Continues processing.
[System Administrator Response]
Delete the project for changing operation from the Systemwalker Operation Manager Client after checking its status.
[Description]
The schedule information is disabled for the project, but the schedule information was not extracted because the master setting information does not exist.
[Parameter]
XXXX: Project name
[System Action]
Process continues without extracting the target project.
[System Administrator Response]
Retry executing the project master setting command by specifying the target project.
[Description]
The audit log could not be output because a problem occurred when an attempt was made to load the library used to output the audit log.
[System Action]
Continues processing, but does not output the audit log.
[Corrective Measures]
Check whether the following files exist. If they do, one or more of the files may have become corrupted. In such cases, either reinstall Systemwalker Operation Manager or contact a Fujitsu SE.
Systemwalker installation directory\MPWALKER.JM\bin\mpaudito.dll
/opt/systemwalker/lib/libmpaudito.so
/opt/systemwalker/lib/libmpaudito_nt.so
/opt/systemwalker/lib/libmpaudito.sl
/opt/systemwalker/lib/libmpaudito_nt.sl
[Description]
The audit log could not be output because a problem occurred when an attempt was made to open the audit log output file.
[System Action]
Continues processing, but does not output the audit log.
[Corrective Measures]
Check that there is sufficient free space.
Check that the directory where the audit log is to be output exists.
Check the permissions/rights associated with the directory where the audit log is to be output. If user restriction definitions are not used, the directory must be able to be written to by General Users/Everyone.
The audit log output file may be corrupt. Back up the damaged file and then delete it.
If a problem has occurred on the disk where the audit log is to be output, it may be necessary to replace or restore the hard disk.
The audit log output file and directory can be specified using the mpsetlogsend_omgr command. Refer to the Systemwalker Operation Manager Reference Guide for details on the mpsetlogsend_omgr command.
[Description]
Policy information could not be set.
[Parameter]
XXXX: Policy information file
[System Action]
Continues processing with the policy information left unset.
[Corrective Measures]
Check the policy information that failed to be set. Restart the Jobscheduler daemon or service to set the policy information again.
[Description]
Policy information could not be set because the environment for the Master Schedule Management function was not in place.
[System Action]
Continues processing with the policy information left unset.
[Corrective Measures]
Create the environment for the Master Schedule Management function and then distribute the policy information again.
[Description]
Past schedule information could not be created because the past schedule information function is not supported by V12.1 or earlier.
[Parameter]
XXXX: Server name
[System Action]
Continues processing with the status of the schedule server unchanged as "Not started".
[Description]
The command for Master Schedule Management function was rejected because the termination process job net (JSHEND or JSHFORCE) has been started.
[System Action]
Aborts processing.
[System Administrator Response]
Restart Jobscheduler and retry the command execution.
