The messages output by Jobscheduler are listed below. The source name is "MpJobsch".
[Description]
Failure in either fork or execv of job net abnormal exit routine (jobsch.exit) or jobnet normal exit routine (jobsch.exit.normal)
[System Action]
Does not execute job net abnormal exit routine (jobsch.exit) or jobnet normal exit routine (jobsch.exit.normal)
[System Administrator Response]
If the job net terminates normally, check the presence of the job net normal exit routine (jobsch.exit.normal) and execution privileges. If it terminates abnormally or is forcibly terminated, check the presence of the job net abnormal exit routine (jobsch.exit) and execution privileges.
[Description]
There is a mistake in argument of job net management daemon (tsktnsrv).
[System Action]
Does not execute job net.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Either of the following occurred:
Failed to access directory of job net information of Jobscheduler.
Exceeded upper limit (1000) of number of projects that can be registered in Jobscheduler.
[System Action]
Aborts processing.
[System Administrator Response]
Read the message displayed before this message, then find the cause of abnormality.
[Description]
Could not read job net information due to failure in open, lockf, or read processing of job net information.
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Could not write schedule information or job net history information (net.spool).
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
An error occurred in the time system call.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
An error occurred while creating a shared memory with the shmget system call.
[System Action]
Aborts processing.
[System Administrator Response]
Check if the Jobscheduler daemon is started more than once, and the system has enough resources.
[Description]
Received signal in main process of the Jobscheduler daemon.
[Parameter]
XXXX: Signal name (SIGABRT/SIGILL/SIGINT/SIGINT/SIGSEGV/SIGTERM)
[System Action]
Aborts processing.
[Description]
Either of the following conditions occurred:
The database directory does not exist or no symbolic link is set up to the database directory.
The Jobscheduler daemon is not started.
[System Action]
Aborts processing.
[System Administrator Response]
If no symbolic link is set up to the database directory, set up one. If the database directory does not exist, restore it from backup or reinstall Systemwalker Operation Manager.
If the Jobscheduler daemon is not started, start the daemon.
[Description]
The information of the job net does not exist in the schedule information due to either of the following reasons:
The job net specified in the argument of the Jobscheduler command has been deleted.
The job net indicated by the Jobscheduler command has been deleted.
[System Action]
Aborts processing.
[System Administrator Response]
Check if the job net has been registered.
Restore schedule information from the jobschbackup directory located in the database directory, when the job net is displayed by either the Jobscheduler daemon or the jobschcontrol command. See "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
In other cases, collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
The database directory does not exist or no symbolic link is set up to the database directory.
[System Action]
Aborts processing.
[System Administrator Response]
If no symbolic link is set up to the database directory, set up one. If the database directory does not exist, restore it from backup or reinstall Systemwalker Operation Manager.
[Description]
Either of the following conditions occurred:
Failed to acquire the ID of shared memory
An error occurred while obtaining a shared memory with the shmat system call
[System Action]
Aborts processing.
[System Administrator Response]
Check if the system has sufficient memory (and resources).
[Description]
A record in either of the following conditions was detected while reading schedule information:
Invalid record length
Invalid as the first record in job net information
[Parameter]
XXXX: Project name
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
The argument in the message execution control process (tskmmsrv) is invalid.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Jobscheduler has successfully communicated with POP3 server
[Description]
A failure occurred in any of open, lockf or read of message information.
[System Action]
Aborts processing.
[System Administrator Response]
Read the message displayed before this message, then find the cause of the error.
[Description]
Failed to load library.
[System Action]
Aborts processing.
[System Administrator Response]
Read the message displayed before this message, then find the cause of abnormality.
[Description]
Failed to retrieve day change time from the calendar function.
[System Action]
Aborts processing.
[System Administrator Response]
Check if the Calendar daemon is running properly. Also check if the Calendar function is available on the Operation Manager Client and the day change time is defined correctly.
[Description]
The number of projects that can be registered in Jobscheduler has exceeded the upper limit (1000).
[System Action]
Aborts processing.
[System Administrator Response]
Delete any unnecessary projects.
[Description]
Project information does not exist in the shared memory which is controlled by Jobscheduler.
[System Action]
Aborts processing.
[System Administrator Response]
Check whether the number of registered projects exceeds 1000. If more than 1000 projects are registered, configure subsystems and reduce the number of registered projects on the system. Also check whether the relevant project is deleted.
[Description]
Job information controlled by Jobscheduler is invalid.
[System Action]
Aborts processing.
[User Response]
Check whether or not the job is deleted.
[Description]
Failed to set distributed policy information.
[Parameter]
XXXX: Policy information file
[System Action]
Cancels the daemon startup processing.
[System Administrator Response]
Check the policy information not set. When resetting policy information, restart the Jobscheduler daemon.
In case of acldata.bat file, the cause of the failure is that the user account information on the extraction source server and that on the distribution destination server does not match.
Take one of the following actions to remove the failure.
Register the same user account as the one registered on the extraction source server on the distribution destination server.
Within the acldata.bat file, change the operand of security commands (mpsetac, mpchown) to an existing user account.
Delete the acldata.bat file and reset the security information in the Set Permissions window and the Change Owner window.
[Description]
The system failed to read the project information.
For the cause of the communication error (TCP/IP socket error), refer to the error message logged before this message such as "MpJobsch: ERROR: open() too many open files".
These messages indicate that the file descriptor of the program is missing and the Operation Manager Client was terminated abnormally. This error may occur when Operation Manager Client is not terminated successfully.
[System Action]
Continues the process without the file.
[System Administrator Response]
If the error message "open() too many open files" is logged, sending HUP signal to the tskwnsrv process may release the bad socket and resolve the problem.
If this problem persists, check the configuration and the network environment. The operational settings may be preventing the Operation Manager Client from exiting normally (such as frequent reset of the client PC), or the network path may have encountered a problem so review the environment.
[Description]
The communication management process (jobschmsmd) has failed to retrieve job net output information.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Could not obtain job standard output/standard error output because an error occurred in job standard output/standard error output management.
Failed to generate a temporary file required for managing standard output/ standard error output by the tmpfile function
Failed to execute file allocation processing of standard output/ standard error output with the dup2 function
Failed to read password information with the getpwnam function
Failed to modify a group ID with the setgid function
Failure to modify a user ID with the setuid function
Failed to execute any of write, open or lockf to the file required for saving standard output/ standard error output.
[System Action]
Aborts processing.
[System Administrator Response]
Read the message displayed before this message, then find the cause of the error.
[Description]
Could not write job net/job start/end message due to failure in open, lockf, write, or time processing for obtaining time of log information (jobdb1.log, jobdb2.log and jobdb3.log located in the database directory).
[System Action]
Aborts processing.
[System Administrator Response]
Read the message displayed before this message, then find the cause of the error.
[Description]
Failure in fork which is required for copying the main daemon called for detachment process of Jobscheduler main daemon from control terminal. System may be overloaded.
[System Action]
Aborts processing.
[System Administrator Response]
Start Jobscheduler daemon when the system is less loaded.
[Description]
Failed to read execution parameter information of Jobscheduler daemon. Execution parameter definition file (jobschev.txt) may be damaged.
[System Action]
Aborts the execution of the daemon.
[System Administrator Response]
After deleting startup parameter definition file, re-create startup parameters in the Define Jobscheduler Startup Parameters window and restart the Jobscheduler daemon.
The startup parameter definition file is stored in the following location.
Systemwalker installation directory\MPWALKER.JM\mpjobsch\etc\jobschev.txt
or
Systemwalker installation directory\MPWALKER.JM\mpjobsch\etc\jobschevn.txt
"n" of "jobschevn" indicates a subsystem number (1 to 9).
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).
[Description]
Could not read job net information due to failure in open, lockf, or read processing of job net information.
[Parameter]
XXXX: Project name
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Could not write Jobscheduler job net information or job net history information (net.spool).
[Parameter]
XXXX: Project name
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Could not write job net/job start/end message due to failure in open, lockf, write, or time processing for obtaining time of log information (jobdb1.log, jobdb2.log and jobdb3.log located in the database directory).
[System Action]
Aborts processing.
[System Administrator Response]
Read the message displayed before this message, then find the cause of abnormality.
[Description]
Could not read schedule pattern information due to failure in open, lockf, or read processing of schedule pattern information (db_calendar_ex.default).
[System Action]
Aborts processing.
[System Administrator Response]
Read the message displayed before this message, then find the cause of abnormality.
[Description]
Jobscheduler daemon has ended.
[Description]
An error occurred in accessing the jobschlock directory when starting the Jobscheduler daemon.
[System Action]
Aborts processing.
[System Administrator Response]
Check if the files stored in jobschlock directory is accessible (and write privileges have been granted to the root user).
The jobschlock directory is stored in the following location.
Systemwalker installation directory\MPWALKER.JM\mpjobsch\jobdb\jobschlock
or
Systemwalker installation directory\MPWALKER.JM\mpjobsch\jobdbn\jobschlock
"n" of "jobdbn" indicates a subsystem number (1 to 9).
Solaris version:
/var/opt/FJSVJOBSC/jobschlock
or
/var/opt/FJSVJOBSC/JOBDBn/jobschlock
HP-UX version:
/opt/FHPJOBSCH/db/jobschlock
or
/opt/FHPJOBSCH/db/JOBDBn/jobschlock
AIX version:
/usr/FAIXJOBSC/db/jobschlock
or
/usr/FAIXJOBSC/db/JOBDBn/jobschlock
Linux version:
/var/opt/FJSVJOBSC/jobschlock
or
/var/opt/FJSVJOBSC/JOBDBn/jobschlock
"n" of "JOBDBn" indicates a subsystem number (1 to 9).
[Description]
Failure in open or read processing of schedule pattern information (db_calendar_ex.default).
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule pattern information (db_calendar_ex.default) from the jobschbackup directory located in the database directory. See "When the Disk Space of file system is Insufficient" in the Systemwalker Operation Manager User's Guide for how to restore the information.
[Description]
While reading job net information, a job net which does not hold any job at all was detected.
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Jobscheduler daemon is already started
[System Action]
Aborts processing.
[System Administrator Response]
Check start processing to prevent the double startup of the Jobscheduler service.
[Description]
There is no calendar information.
[System Action]
Aborts processing.
[System Administrator Response]
The file sysfile.sys (the database for the day change time and holidays) has been deleted or the holiday calendar referred to by job nets does not exist.
If sysfile.sys has been deleted, restart the Jobscheduler daemon. You can restart it on a Systemwalker
Operation Manager Environment Setup Client.
If that calendar does not exist, create a calendar with the name same as the one to be referred or set the calendar correctly.
The sysfile.sys file is stored in the following location.
Systemwalker installation directory\MPWALKER.JM\mpjobsch\jobdb\sysfile.sys
or
Systemwalker installation directory\MPWALKER.JM\mpjobsch\jobdbn\sysfile.sys
"n" of "jobdbn" indicates a subsystem number (1 to 9).
Solaris version:
/var/opt/FJSVJOBSC/sysfile.sys
or
/var/opt/FJSVJOBSC/JOBDBn/sysfile.sys
HP-UX version:
/opt/FHPJOBSCH/db/sysfile.sys
or
/opt/FHPJOBSCH/db/JOBDBn/sysfile.sys
AIX version:
/usr/FAIXJOBSC/db/sysfile.sys
or
/usr/FAIXJOBSC/db/JOBDBn/sysfile.sys
Linux version:
/var/opt/FJSVJOBSC/sysfile.sys
or
/var/opt/FJSVJOBSC/JOBDBn/sysfile.sys
"n" of "JOBDBn" indicates a subsystem number (1 to 9).
[Description]
Failure in updating calendar information
[System Action]
Aborts processing.
[System Administrator Response]
Check the following:
The sysfile.sys file located in the database directory is accessible. If the file is not accessible due to file I/O error, etc.
There is enough disk space.
[Description]
Unauthorized user used a command which requires superuser privileges. Only the superuser can use the command.
[System Action]
Aborts processing.
[User Response]
Execute the command with superuser privileges.
[Description]
Unrecoverable error suspended Jobscheduler command processing. The Jobscheduler daemon may have been inactive.
[System Action]
Aborts processing.
[System Administrator Response]
Start the Jobscheduler daemon.
[Description]
Could not read/modify calendar information.
[System Action]
Aborts processing.
[User Response]
Please check whether the problem relates to any of the following:
Calendar daemon is not started.
Error in calendar name.
Calendar name referred to by JobScheduler has been deleted.
You can find job nets which are using the calendar in the Calendar Status dialog box.
[Description]
Target job net does not exist.
[System Action]
Aborts processing.
[User Response]
Check the job net name.
[Description]
The name of the target job net is invalid.
[System Action]
Aborts processing.
[User Response]
Check the job net name.
[Description]
Communication management process (jobschmsmd) does not exist in the directory which is specified in environment variable JOBEXE_PATH or the default directory.
[System Action]
Terminates the jobschmsm command.
[System Administrator Response]
Check execution privileges and the presence of the communication management process (jobschmsmd).
[Description]
Host name exceeding 64 bytes is specified in the monitoring host definition file.
[System Action]
Ignores host name exceeding 64 bytes.
[System Administrator Response]
Correct the monitoring host definition in the Define Monitoring Host window. This definition can also be corrected by using the omgrmonitor command.
[Description]
The Jobscheduler has failed to send job net control information.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Jobscheduler has failed to receive job net monitor information.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Communication process (jobschmsmd) argument is incorrect
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Invalid host name is specified in the monitoring host definition file.
[System Action]
Aborts processing.
[System Administrator Response]
Correct the monitoring host definition in the Define Monitoring Host window. This definition can also be corrected by using the omgrmonitor command.
[Description]
Invalid host name for local host.
[System Action]
Aborts processing.
[System Administrator Response]
Set the host name of local host as the OS.
[Description]
An error occurred in the getaddrinfo function.
[System Action]
Aborts processing.
[System Administrator Response]
Check the network configuration on the server.
[Description]
Failure in service name jobsch_tcp acquisition for communication with the monitored host
[System Action]
Aborts processing.
[System Administrator Response]
Specify service name jobsch_tcp (default value 9240/ tcp) in the /etc/services file. If the host is using the name service, define the setting accordingly.
[Description]
Abnormality occurred in communication with the Jobscheduler daemon on the monitored host.
[System Action]
Aborts processing.
[System Administrator Response]
Check if there is no problem on the network between the monitoring host and the monitored host.
[Description]
An error occurred in the select system call.
[System Action]
Aborts processing.
[System Administrator Response]
Check if the following communications are available:
Communications between the Operation Manager Client and the server
Communications between the monitoring host and the monitored host
[Description]
An error occurred while communicating with the jobschmsm command
[System Action]
Aborts processing
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Host name exceeding 64 bytes is specified in the monitoring permission host definition file.
[System Action]
Ignores host name exceeding 64 bytes.
[System Administrator Response]
Correct the monitoring permission host definition file in the Define Monitoring Permission Host window and restart the daemon.
[Description]
No host name is specified in the monitoring host definition file.
[System Action]
Aborts processing.
[System Administrator Response]
Correct the monitoring host definition in the Define Monitoring Host window. This definition can also be corrected by using the omgrmonitor command.
[Description]
Failure in service name jobsch_udp acquisition for communication with the monitored host.
[System Action]
Aborts processing.
[System Administrator Response]
Specify service name jobsch_udp (default value 9240/ udp) in the /etc/services file. If the host is using the name service, define the setting accordingly.
[Description]
Invalid host information is held internally.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failed to open the file which stores job net output information received by the communication management process (jobschmsmd).
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failure in either fork or exec of job net abnormal exit routine (msm.db/ jobnet.exit)
[System Action]
Does not start job net abnormal exit routine (msm.db/ jobnet.exit). Aborts processing.
[System Administrator Response]
Check execution privileges and the existence of the job net abnormal exit routine (msm.db/ jobnet.exit)
[Description]
Failure in either fork or exec of the non-communication exit routine (msm.db/ jobschmsm.exit)
[System Action]
Does not start the non-communication exit routine (msm.db/ jobschmsm.exit)
[System Administrator Response]
Check execution privileges and the existence of the non-communication exit routine (msm.db/ jobschmsm.exit)
[Description]
The Jobscheduler multi-system monitor daemon argument is incorrect.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
An abnormality occurred in communication with the Jobscheduler daemon.
[System Action]
Aborts processing.
[System Administrator Response]
Check if there is no problem on the network between the monitoring host and the monitored host.
[Description]
Failed to obtain service name jobsch_tcp to be used for communication with the monitoring host.
[System Action]
Aborts processing.
[System Administrator Response]
Specify service name jobsch_tcp (default value 9240/tcp) in the /etc/services file in the system root. If the host is using the name service, define the setting accordingly.
[Description]
There is schedule information with 0 bytes.
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Abnormality occurred during job net information communication inside Jobscheduler daemon.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failure to read job net output information.
[System Action]
Aborts processing.
[System Administrator Response]
Confirm the following:
You can access the projectname_jobnetname_nn.log (nn: any numeric character) file located under the database directory.
Whether an I/O error has occurred on the file and access is disabled.
There is enough available disk space.
[Description]
Failure in holiday shifting for job net information
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failure in either open or read of schedule pattern information (db_calendar_ex.default)
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule pattern information (db_calendar_ex.default) from jobschbackup directory located under the database directory. See "When the Disk Space is Insufficient" in the Systemwalker Operation Manager User's Guide for how to restore the information.
[Description]
Jobscheduler cannot start it because an error has occurred at the bind system call of the jobschmsm command.
[System Action]
Aborts processing.
[System Administrator Response]
Check that the command is not in use by another user and start it later.
[Description]
Jobscheduler could not write job net information due to failure in open, lockf, read and write of the information.
[Parameter]
XXXX : File name
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Length of value of environment variable "JOBEXE_PATH" has exceeded the upper limit of 128 bytes.
[System Action]
Aborts processing.
[System Administrator Response]
Change the value of environment variable "JOBEXE_PATH" to within 128 bytes.
[Description]
An error occurred in the getaddrinfo function.
[System Action]
Aborts processing.
[System Administrator Response]
Check whether the IP addresses of the hosts specified in the monitoring host definition file and the monitoring permission host definition file are registered in "/etc/hosts". The IP addresses of these hosts can be confirmed on the following windows:
Monitoring Host definition file: Define Monitoring Host window
Monitoring Permission Host definition file: Define Monitoring Permission Host window.
[Description]
Could not read due to failure in opening monitor authorization host file (msm.db/access_hosts).
[System Action]
Aborts processing.
[System Administrator Response]
Check for the presence of the monitor authorization host file (database directory/msm.db/access_hosts).
If the monitor authorization host file does not exist, set the Monitoring Permission Host from the Environment Setup Client.
[Description]
Failure in acquisition of machine ID used in Job Execution Control.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failure to send job net information to multiple system monitor processes (tskmssrv).
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Job Execution Control job net daemon (tskbasrv) argument is incorrect
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Host name with space or tab character is specified in the monitoring host definition file.
[System Action]
Ignores host name with space or tab character.
[System Administrator Response]
Correct the monitoring host definition file on the Define Monitoring Host window. This definition can also be corrected by using the omgrmonitor command.
[Description]
Host name with space or tab character is specified in the monitoring permission host definition file.
[System Action]
Ignores host name with space or tab character.
[System Administrator Response]
Correct the monitoring permission host definition file on the Define Monitoring Permission Host window.
[Description]
Failure to execute job in Job Execution Control job net.
[System Action]
Does not execute job and returns end code 243.
[User Response]
Make sure that the Job Execution Control daemon is running.
[Description]
Failure in backing up file.
[Parameter]
XXXX: File name
[System Action]
Aborts processing.
[System Administrator Response]
Check if there is enough disk space.
[Description]
Jobscheduler cannot handle project name exceeding 50 characters.
[Parameter]
XXXX: project name
[System Action]
Aborts processing.
[User Response]
Specify a project name within 50 characters.
[Description]
Failed to create file used to prevent repeated execution of Jobscheduler command.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Monitoring host definition file does not exist.
[System Action]
Aborts processing.
[System Administrator Response]
Correct the monitoring host definition file on the Define Monitoring Host window. This definition can also be corrected by using the omgrmonitor command.
[Description]
An error occurred in the fork system call required for starting job net management daemon (tsktnsrv).
[Parameter]
XXXX : Project name
YYYY : Job net name
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
An error occurred in the execv system call which is required for starting job net management daemon (tsktnsrv).
[Parameter]
XXXX : Project name
YYYY : Job net name
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failed to execute file.
[Parameter]
XXXX: File name
[System Action]
Aborts processing.
[User Response]
Check for the presence and execution privileges of the file.
[Description]
Failure in either fork or exec of log information switch over exit routine (jobdb.exit)
[System Action]
Does not start log information switch over exit routine (jobdb.exit)
[System Administrator Response]
Check execution privileges and the existence of log information switch over exit routine (jobdb.exit)
[Description]
Mistake in mail link daemon (tskmlsrv) argument.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failure in communicating with POP3 server. Cannot set up E-Mail link.
[System Action]
Continues processing though the E-Mail link function cannot be used.
[System Administrator Response]
Check whether the POP3 server defined on environment definition startup parameter information is working or not.
[Description]
Failed to initialize FLEXlm.
[System Action]
Aborts processing.
[System Administrator Response]
Confirm the settings for FLEXlm.
[Description]
Failed to retrieve FLEXlm license.
[System Action]
Aborts processing.
[System Administrator Response]
Check license and password settings for FLEXlm.
[Description]
Invalid argument in communication daemon (tskwnsrv).
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
A communication error occurred between Jobscheduler daemon and the Operation Manager Client.
For the cause of the communication error (TCP/IP socket error), refer to the error message logged before this message such as "MpJobsch: ERROR: write() broken pipe" and "MpJobsch: ERROR: read() Connection reset by peer".
These messages indicate that the socket was disconnected illegally and the Operation Manager Client was terminated abnormally.
[System Action]
Handles the socket error and continues processing.
[System Administrator Response]
If this problem persists, check the configuration and the network environment. The operational settings may be preventing the Operation Manager Client from exiting normally (such as frequent reset of the client PC), or the network path may have encountered a problem.
[Description]
Failure in communication between a communication control daemon (tskwnsrv) or a host list daemon (tskmdsrv) and PC.
[System Action]
Aborts processing.
[System Administrator Response]
If this message is output frequently, check if an operation is disconnecting the Operation Management Client abnormally (e.g., a client PC is resetting frequently), if there is a problem in the network path, or if an incorrect communication or an illegal access from outside the system is being performed.
[Description]
The local host name exceeds 64 bytes.
[System Action]
Aborts processing.
[User Response]
Specify a local host name within 64 bytes.
[Description]
Failure to acquire service name, jobsch_win to be used for communication with Jobscheduler/CL.
[System Action]
Cannot use Jobscheduler/CL.
[System Administrator Response]
Specify service name jobsch_win (default value 9297/tcp) in the /etc/service file in the system root. If the host is using the name service, define the setting accordingly.
[Description]
Cannot start the Jobscheduler daemon because a PC or the host list daemon (tskmdsrv) was connected when the Jobscheduler daemon was last exited.
[System Action]
Aborts processing.
[System Administrator Response]
Start the Jobscheduler daemon one minute after shutting down the PC or exiting the host list daemon (tskmdsrv) using the kill command.
[Description]
Failed to open last log information
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Detected an erroneous record in calendar information.
[System Action]
Aborts processing.
[System Administrator Response]
There is some conflicting information in sysfile.sys (the database for the day change time and holidays). Stop the Jobscheduler daemon, delete sysfile.sys, and start the Jobscheduler daemon again. By restarting the Jobscheduler daemon, the sysfile.sys file will be recreated.
[Description]
Cannot re-schedule group or job net because an error occurred in the msgsnd system call.
[System Action]
Aborts processing.
[System Administrator Response]
Check if resources are insufficient on the system (too many messages in queue, etc).
[Description]
Cannot read due to failure to open log information.
[System Action]
Aborts processing.
[System Administrator Response]
Identify the cause of failure in accessing log information (jobdb1.log, jobdb2.log and jobdb3.log located in the database directory).
[Description]
Could not read schedule information due to failure in either open, lockf, or read processing of it.
[Parameter]
XXXX: Project name
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Failed to schedule information.
[System Action]
Aborts processing.
[System Administrator Response]
Read the message displayed before this message, then find the cause of abnormality.
[Description]
Invalid record in schedule information.
[Parameter]
XXXX: Project name
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Deleted due to abnormality in information of group YYYY of project XXXX.
[Parameter]
XXXX: Project name
YYYY: Group name
[System Action]
Deletes group YYYY of project XXXX, then continues processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Could not write schedule information due to failure in either open, lockf, or read processing of it.
[Parameter]
XXXX: Project name
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Failure to write group information.
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
The log information file was switched because the log information file size exceeded the value specified in the Jobscheduler startup parameter.
[System Action]
Executes log information switch exit routine (jobdb.exit).
[User Response]
No action is required. To view log information existed before switching, use an editor to see the previous log file.
[Description]
Failure in "fork" or "exec" of log information switch exit routine (jobdb.exit).
[System Action]
Does not execute log information switch exit routine (jobdb.exit).
[System Administrator Response]
Check for the presence and execution privileges of the log information switch exit routine (jobdb.exit).
[Description]
Failure to send schedule information to multiple system monitor processes (tskmssrv).
[System Action]
Aborts processing.
[System Administrator Response]
Check if there is no problem on the network.
[Description]
Schedule will be executed after group YYYYY of project XXXX has been completed.
A group is started once a day and schedule on the day is determined depending on the startup day of job nets within the group.
If the group is not completed successfully at the day change time, the group does not perform the subsequent scheduling. The execution of the subsequent schedule is notified of when the group has completed successfully.
Note that, when the group is in either status below, groups scheduled on the day will be carried over even if day change time elapses.
When the group is not started.
When the group confirmation is validated and the execution status is Abended, Canceled or Closed.
[Parameter]
XXXX: Project name
YYYY: Group name
[User Response]
If the group is executing, wait until it completes. If the group is waiting for execution, the message event for which the first job net is waiting may not be generated yet. Confirm the reason why the message was not generated.
[Description]
Cannot execute specified operation because group is being saved or controlled.
[System Action]
Aborts processing.
[User Response]
Perform operation after group status changes.
[Description]
Invalid argument in the host list process (tskmdsrv).
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Invalid argument in the event management process (tskevsrv).
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failure in fork or exec of day change time notice exit routine. (jobsch.time.exit).
[System Action]
Does not execute day change time notification exit routine (jobsch.time.exit).
[System Administrator Response]
Check for the presence and execution privileges of the day change time notification exit routine (jobsch.time.exit).
[Description]
Jobscheduler cannot handle user names that exceed 20 characters.
[Parameter]
XXXX : user name
[System Action]
Aborts processing.
[User Response]
Operate Jobscheduler with a user name specified within 20 characters.
[Description]
There is inconsistency between group information and job net information
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Failed to obtain service name of "jobsch_win" to be used for communication with the communication control process (tskwnsrv).
[System Action]
Cannot use Jobscheduler/CL.
[System Administrator Response]
Specify service name jobsch_win (default value 9297/tcp) in the /etc/service file. If the host is using the name service, define the setting accordingly.
[Description]
The Jobscheduler daemon has been started.
[System Action]
Starts the Jobscheduler daemon.
[Description]
Cannot execute specified operation because the Jobscheduler daemon is being started.
[System Action]
Aborts processing.
[User Response]
Perform operation after the Jobscheduler daemon has been started.
[Description]
Invalid environment variable LANG.
[System Action]
If this message is output by the daemon, it operates under English environment. If output by a command, the daemon is not started.
[User Response]
If this message was output by the daemon, correct the environment variable "LANG" of the OS, then restart the daemon. If this message was output by a command, correct the environment variable "LANG" of user environment, then reexecute the command.
[Description]
Either of the following conditions has occurred:
Failed to link with PowerAIM since the shared library of PowerAIM was unavailable.
Job nets of PowerAIM attributes cannot be registered since the system cannot use PowerAIM.
[System Action]
If this message is output by the daemon, the daemon will be terminated.
If this message is output by a command, the job nets will not be registered.
[System Administrator Response]
Check that PowerAIM has been properly installed.
[Description]
Failed to obtain information of host XXXX specified in the monitoring permission host definition file.
[Parameter]
XXXX: host name
[System Action]
Jobscheduler does not communicate with the relevant host.
[System Administrator Response]
Confirm the monitoring permission host definition file on the Define Monitoring Permission Host window.
[Description]
The argument of the PowerAIM job net control daemon (tskpasrv) is wrong.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Stopped the trace function due to abnormality in the trace function of XXXX.
[Parameter]
XXXX: Name of program to be executed (e.g., tskussrv)
[System Action]
Stops further output of XXXX trace information.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
XXXX YYYY has not started
[Parameter]
XXXX : Project name
YYYY : Job net name
[Description]
Failure in either fork or execv of the job completion exit routine (jobsch.job.exit).
[System Action]
The job completion exit routine (jobsch.job.exit) is not started.
[System Administrator Response]
Check for the presence and execution privileges of the job completion exit routine (jobsch.job.exit).
[Description]
Database under JOBDB PATH is for previous version.
[System Action]
Aborts processing.
[System Administrator Response]
Convert the database by using the jobschconvert command.
[Description]
The job net did not start at the scheduled start time because either the message event for starting was not generated, or the previous job net did not end normally.
[Parameter]
XXXX: Project name
YYYY: Job net name
[System Action]
Job net is not started at the scheduled start time.
[System Administrator Response]
Generate the message event that caused the error by not satisfying the startup condition , or start the previous job net and terminate it normally.
[Description]
Job net could not finish before the estimated end time.
[Parameter]
XXXX: Project Name
YYYY: Job net Name
[User Response]
This message may be output even when a job net does not start.
If the day change time is changed, time inversion between the startup scheduled time and the end scheduled time may occur, causing this message to be output. Verify that the following condition is met:
Day change time <= Startup scheduled time < End scheduled time
[Description]
It is a message used for linking with System Monitor. The job net has started.
[Parameter]
XXXX: Job Net Comment
YYYY: Job Net Name
ZZZZ: Project Name
[Description]
It is a message used for linking with System Monitoring. The job net has normal ended.
[Parameter]
XXXX: Job Net Comment
YYYY: Job Net Name
CCCC: Job Net Completion Code
ZZZZ: Project Name
[Description]
It is a message used for linking with System Monitor. The job net has abnormally ended.
[Parameter]
XXXX: Job Net Comment
YYYY: Job Net Name
CCCC: Job Net Completion Code
ZZZZ: Project Name
[User Response]
The job net exited abnormally. Check the job details, and investigate the cause using the completion code of the job.
[Description]
This message is used for linking with the System Monitor function. Job net execution has been refused.
[Parameter]
XXXX: Job Net Comment
YYYY: Job Net Name
ZZZZ: Project Name
[Description]
This message is used for linking with the System Monitor function. Job net execution has been skipped.
[Parameter]
XXXX: Job Net Comment
YYYY: Job Net Name
ZZZZ: Project Name
[Description]
This message is used for linking with the System Monitor function. Job net execution has pseudo-normally ended.
[Parameter]
XXXX: Job Net Comment
YYYY: Job Net Name
CCCC: Job Net Completion Code
ZZZZ: Project Name
[Description]
The activation delay exit routine of the job net (startlate.exit) failed at either fork or execv.
[System Action]
The activation delay exit routine of the job net (startlate.exit) does not start.
[System Administrator Response]
Review the existence and execution privileges of the activation delay exit routine (startlate.exit) of the job net.
[Description]
The termination delay exit routine of the job net (endlate.exit) failed at either fork or execv.
[System Action]
The termination delay exit routine of the job net (endlate.exit) does not start.
[System Administrator Response]
Review the existence and execution privileges of the termination delay exit routine (endlate.exit) of the job net.
[Description]
The Jobscheduler daemon failed to activate with the virtual time specified.
[System Action]
The system assumes that the virtual time is not set, and the Jobscheduler daemon operates in real time.
[User Response]
If this message is preceded by error massage 341, the virtual time on the Systemwalker Operation Manager Environment Setup Client is set to a time in the past. Virtual time must be set to the future. Reset the virtual time and restart the Jobscheduler daemon.
If the message 341 is not output, then access to the startup parameter file of the Jobscheduler daemon has failed. Verify the access privileges of files under the Jobscheduler's database directory, then restart the Jobscheduler daemon.
The startup parameter file (jobschev.txt) is stored in the following location.
Systemwalker installation directory\MPWALKER.JM\mpjobsch\etc\jobschev.txt
or
Systemwalker installation directory\MPWALKER.JM\mpjobsch\etc\jobschevn.txt
"n" of "jobschevn" indicates a subsystem number (1 to 9).
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).
[Description]
The Jobscheduler daemon failed to activate with the virtual time specified.
[System Action]
The system assumes that the virtual time is not set, and the Jobscheduler daemon operates in real time.
[User Response]
The virtual time on the Systemwalker Operation Manager Environment Setup Client was set to a time in the past. Virtual time must be set to the future. Reset the virtual time and restart the Jobscheduler daemon.
[Description]
No swadmin group exists in the /etc/group file.
[System Action]
Although it is set to allow only users in the swadmin group to activate commands and demand jobs of Jobscheduler, no swadmin group exists. As a result, the Jobscheduler daemon cannot be activated.
[User Response]
Create a swadmin group in /etc/group and add users that are allowed to activate commands and demand jobs of Jobscheduler.
[Description]
Although it is set to allow only users in the swadmin group to activate commands and demand jobs of Jobscheduler, no swadmin group exists or failure in changing attributes of each file occurred, thus the security cannot be enhanced.
[User Response]
If this message is displayed with message 342, create a swadmin group in /etc/group and add users that are allowed to activate commands and demand jobs of the Jobscheduler.
If not, check that the Jobscheduler database directory exists and attributes of the database directory, the files in the database directory and subdirectories are modifiable, then restart the Jobscheduler daemon.
[Description]
IPC resource which has XXXX as a key is already used by another application.
[Parameter]
XXXX : Key
[System Action]
Uses another key.
[User Response]
No action is required since another key is used.
If IPC resources that were being used by the Jobscheduler are left behind because the Jobscheduler daemon was forcibly terminated, restart the system.
[Description]
An inter-process communication (IPC) resource was created with a key XXXX.
[Parameter]
XXXX : Key
[Description]
Failure in opening the file used when requesting the key for creating IPC resource occurred.
[System Action]
Aborts the startup process of the daemon.
[System Administrator Response]
Verify any messages preceded by this message, and remove the cause of this abnormality.
[Description]
Although the restriction that only the users in the swadmin group are allowed to activate commands and demand jobs of Jobscheduler is lifted, the security enhancement could not be released because of failure in changing attributions of files.
[System Administrator Response]
Confirm that the access privileges for the files under Jobscheduler database directory are correct and restart the Jobscheduler daemon.
[User Response]
Check that the Jobscheduler database directory exists and attributes of the database directory, the files in the database directory and subdirectories are modifiable, then restart the Jobscheduler daemon.
[Description]
Failed to read the parameter information file for the job.
[System Action]
Aborts processing.
[User Response]
Restore the parameter information file for the job from the jobschbackup directory.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failed to access the file.
[Parameter]
XXXX: File name
[System Action]
Aborts processing.
[User Response]
Refer to the message logged prior to this message and resolve the problem.
[Description]
The system function returned an error.
XXXX and later is "iconv() Illegal byte sequence" or "iconv() Invalid Argument"
Code conversion failed since the status of job output information was any of the following:
Information was output in binary code
Information with 966 bytes or more was output in a single line
[Parameter]
XXXX: System function name
YYYY: Message
[System Action]
Aborts processing.
[System Administrator Response]
XXXX and later is "iconv() Illegal byte sequence" or "iconv() Invalid Argument"
Review the job output information to prevent it from falling under any of the statuses shown below.
Information was output in binary code
Information with 966 bytes or more was output in a single line
If you have to refer to output results, see the following file. Job's output results are output after the one byte space (maximum: 4 bytes) from the first string in the file.
Jobscheduler database directory/projectname_jobnetname_nn.log
Enter any two numeric characters in "nn" in "Jobscheduler database directory/projectname_jobnetname_nn.log".
The database directory of Jobscheduler is as follows.
Systemwalker installation directory\MPWALKER.JM\mpjobsch\jobdb
or
Systemwalker installation directory\MPWALKER.JM\mpjobsch\jobdbn
"n" of "jobdbn" indicates a subsystem number (1 to 9).
Solaris version:
/var/opt/FJSVJOBSC
or
/var/opt/FJSVJOBSC/JOBDBn
HP-UX version:
/opt/FHPJOBSCH/db
or
/opt/FHPJOBSCH/db/JOBDBn
AIX version:
/usr/FAIXJOBSC/db
or
/usr/FAIXJOBSC/db/JOBDBn
Linux version:
/var/opt/FJSVJOBSC
or
/var/opt/FJSVJOBSC/JOBDBn
"n" of "JOBDBn" indicates a subsystem number (1 to 9).
When this message is output, restart the system.
In cases other than the above, collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
XXXX and later is "msgrcv() Invalid argument" or "msgrcv() Identifier removed"
Message queue was deleted by the ipcrm command or some application.
XXXX and later is "msgget() No space left on device"
Some application uses numerous kernel parameters of the system (msgsys:msginfo_msgmni).
XXXX and later is getpwnam() No such file or directory
The user executing a network job is not registered in the job requesting server.
If "read() Resource temporarily unavailable" is displayed after XXXX
There are not enough server resources or processing is concentrating.
If "msgsnd() Invalid argument" is displayed after XXXX
The job net terminated after the Jobscheduler daemon terminated.
If "read() No such file or directory" is displayed after XXXX
Communication between the client and the server has been disconnected.
In other cases, an error occurred on the system function.
[Parameter]
XXXX: System function name
YYYY: Message
[System Action]
Aborts processing.
[System Administrator Response]
XXXX and later is "msgrcv() Invalid argument" or "msgrcv() Identifier removed"
Prevent the ipcrm command or the relevant application from deleting message queue.
When this message is output, restart the system.
XXXX and later is "msgget() No space left on device"
Add the following value to the current value of the kernel parameter of the system (msgsys:msginfo_ msgmni) to extend message queue.
4 x the number of subsystems to be used (it must be 1 for SE version)
XXXX and later is "getpwnam() No such file or directory"
Register the user executing the network job in the job requesting server.
If "read() Resource temporarily unavailable" is displayed after XXXX
Eliminate the cause of the insufficient resources.
If "msgsnd() Invalid argument" is displayed after XXXX
Cancel any executing job nets before stopping the Jobscheduler daemon.
For the execution privileges of the network and distributed execution jobs, see "Job Execution Privileges" in the Systemwalker Operation Manager Installation Guide.
If "read() No such file or directory" is displayed after XXXX
Try connecting the client to the server again.
In cases other than the above, collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
The project specified to process is missing.
[System Action]
Aborts processing.
[User Response]
Check the project name.
[Description]
The message event name is not specified for jobschmsgevent command.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Code conversion of the standard output or the standard error output for the job failed. Illegal characters are contained in the job result file.
[System Action]
Aborts processing.
[User Response]
Do not contain illegal characters such as binary codes in the standard output and standard error output for the job.
[Description]
There are not enough message queues. Performance in job processing may be degraded.
[System Action]
Aborts processing.
[User Response]
Extend the message queue by referring to "Extending the Message Queue" in the Systemwalker Operation Manager Installation Guide.
[Description]
XXXX = 3, YYYY = 0
A connection error occurred.
XXXX = 8, YYYY = 11
Failed to obtain a semaphore.
XXXX = 16, YYYY =0
Failed to convert the code.
In other cases, an error occurred while the ACL Manager was running.
[Parameter]
XXXX: Error code
YYYY: Detailed code
[System Action]
Aborts processing.
[Corrective Measures]
XXXX = 3, YYYY = 0
Check that the following process is running on the Operation Manager Server. If the problem persists even if the process is in active, collect the maintenance information with the swcolinf, maintenance information collection command (for server) and contact a Fujitsu's system engineer.
/usr/lib/MpFwsec
XXXX = 8, YYYY = 11
Check that the setting value related to the semaphore of system parameters is appropriate for the operating environment.
XXXX = 16, YYYY = 0
Make sure that the mandatory SUNWjfpu software is installed. For the mandatory software for Systemwalker Operation Manager, see the Release Note.
For other cases, collect the maintenance information with the swcolinf, maintenance information collection command (for server) and contact a Fujitsu's system engineer. For how to use the swcolinf command, refer to the Systemwalker Operation Manager Reference Guide.
[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.
/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]
Job definition variable information could not be read because an "open", "lockf" or "read" operation failed.
[System Action]
Aborts processing.
[Corrective Measures]
Restore the job definition variable information from the jobschbackup directory under the database directory. Refer to "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for information about how to restore job definition variable information.
[Description]
Job definition variable information could not be written because an "open", "lockf", "read" or "write" operation failed.
[System Action]
Aborts processing.
[Corrective Measures]
Restore the job definition variable information from the jobschbackup directory under the database directory. Refer to "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for information about how to restore job definition variable information.
[Description]
Reading parameter information for a job has failed.
[Parameter]
XXXX: File name
[System Action]
Aborts processing.
[Corrective Measures]
Restore the job parameter information from the jobschbackup directory under the database directory. Refer to "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for information about how to restore job parameter information.
[Description]
Writing variable parameter information has failed.
[Parameter]
XXXX: File name
[System Action]
Aborts processing.
[Corrective Measures]
Check whether it is possible to access the parameter information file (by checking whether the root user has write permissions, for example).
[Description]
Writing to the message event occurrence history file failed.
[System Action]
Continues processing without writing to the message event occurrence history file.
[System Administrator Response]
Read the message displayed before this message, then find the cause of this abnormality.
[Description]
Reading of the job net variable information file failed.
[Parameter]
XXXX: FILE NAME
[System Action]
Aborts processing.
[System Administrator Response]
Read the message displayed before this message, then find the cause of this abnormality.
[Description]
Writing to the jobnet variable information file failed.
[Parameter]
XXXX: FILE NAME
[System Action]
Aborts processing.
[System Administrator Response]
Read the message displayed before this message, then find the cause of this abnormality.
[Description]
Deletion of the jobnet variable information file during job net startup failed.
[Parameter]
XXXX: FILE NAME
[System Action]
Aborts processing.
[System Administrator Response]
Check if the file is accessible (and privileges such as write privileges have been granted to the root user).
[Description]
The license key is not registered, or the trial period has expired.
[System Action]
Outputs the message and cancels the processing.
[System Administrator Response]
A license is required. Refer to "Release Note" for information on corrective measures.
[Description]
This product is a trial version, and the remaining trial period is XXXX days.
[Parameter]
XXXX: Remaining trial period
[System Action]
Maintains the operation.
[System Administrator Response]
Purchase the product to continue using it after the trial period has expired.
[Description]
Successful communication with POP3 server.
[Description]
The Jobscheduler service is stopped.
[Description]
The communication between the communication management process (tskwnsrv) and PC failed due to an error such as force-termination of the client.
[System Action]
Aborts processing.
[System Administrator Response]
No action is necessary, if the type of the message logged prior to this message is INFO. If the type of the message logged prior to this message is ERROR, refer to the message and resolve the problem.
[Description]
Switched log information file because log information file size exceeded value specified in the startup parameter of the Jobscheduler service.
[System Action]
Executes log information switch exit routine (jobdbexit.exe).
[User Response]
No action is required. To view log information before switching, use an editor to see the previous log file.
[Description]
The Jobscheduler service has started startup processing.
[Description]
The Jobscheduler service has ended.
[Description]
The Jobscheduler service has started end processing because the end processing job net (JSHEND or JSHFORCE) has been started.
[Description]
The Jobscheduler service has completed start processing.
[Description]
Event log information will be reloaded.
[Description]
A host name that contains a space or tab character is specified in the monitoring permission host definition file.
[Parameter]
XXXX : Incorrect host name
[System Administrator Response]
Correct the monitoring permission host definition file in the Define Monitoring Permission Host window.
[Description]
XXXX YYYY job net did not start.
[Parameter]
XXXX: Project name
YYYY: Job net name
[Description]
XXXX message event occurred due to the jobschmsgevent command.
[Parameter]
XXXX: Message event name
[Description]
The system function returned a return value other than 'normal'.
[Parameter]
XXXX: Name of the function that called the system function
YYYY: Function name
CCCC: Return value
ZZZZ: System message
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
The socket function returned a return value other than 'normal'.
[Parameter]
XXXX: Name of the function that called the socked function
YYYY: Socket function name
ZZZZ: Code
[System Action]
Aborts processing.
[System Administrator Response]
Refer to the message logged immediately after this message and check if this error does not affect the operation.
[Description]
This product is a trial version, and the remaining trial period is XXXX days.
[Parameter]
XXXX: Remaining trial period
[System Action]
Maintains the operation.
[System Administrator Response]
Purchase the product to continue using it after the trial period has expired.
[Description]
Host name exceeding 64 bytes is specified in the monitoring permission host definition file.
[System Action]
Ignores host name exceeding 64 bytes.
[System Administrator Response]
Correct the monitoring permission host definition file in the Define Monitoring Permission Host window and restart the daemon.
[Description]
A host name that contains a space or tab character is specified in the monitoring permission host definition file.
[System Action]
Ignores the host name that contains a space or tab character.
[System Administrator Response]
Correct the monitoring permission host definition by using the Define Monitoring Permission Host window.
[Description]
Failure in communicating with the POP3 server. Cannot set up e-mail link.
[System Action]
Continues processing though the e-mail link function cannot be used.
[System Administrator Response]
Check that the POP3 server defined on environment definition startup parameter information is working.
[Description]
Event log type is not specified for monitoring event logs.
[System Action]
Monitors all event log types.
[System Administrator Response]
Check the event log setting by using the jobschsetparm command.
[Description]
The maximum limit (255) for the number of job nets that can be registered per project has been exceeded. Fujitsu recommends not adding any more job nets to this project.
[User Response]
To register more job nets in a project than this maximum limit (255), use the Enterprise Edition of Systemwalker Operation Manager. Delete any job nets in the project that are no longer necessary, so that the total number of job nets in the project does not exceed the maximum limit. If there are no job nets in the project that can be deleted, add the excess job nets to a different project.
[Description]
The number of job nets that have been registered in a single project has exceeded the value set as the warning level.
[User Response]
The number of job nets in the project has reached the upper limit that has been set on the Systemwalker Operation Manager Environment Setup Client. Delete any unnecessary job nets so that the upper limit is not exceeded. If there are no job nets that can be deleted, either add the excess job nets to a different project or change the value that has been specified for the upper limit with the Systemwalker Operation Manager Environment Setup Client.
[Description]
The Jobscheduler service has not been started at the specified virtual time.
[System Action]
The virtual time is considered not specified, and the Jobscheduler service will be operated in actual time.
[User Response]
If this message is generated following the error message 3307, the virtual time has been set earlier than actual time on the Systemwalker Operation Manager Environment Setup Client. Only future time can be specified for the virtual time. Re-set the virtual time, and then restart the Jobscheduler service.
If the error message 3307 is not generated, access to the startup parameter file for the Jobscheduler service has failed. Review access privileges for files under the Jobscheduler service database directory, and then restart the Jobscheduler service.
[Description]
The Jobscheduler service has not been started at the specified virtual time.
[System Action]
The virtual time is considered not specified, and the Jobscheduler service will be operated in actual time.
[User Response]
The virtual time has been set earlier than actual time on the Systemwalker Operation Manager Environment Setup Client. Only future time can be specified for the virtual time. Re-set the virtual time, and then restart the Jobscheduler service.
[Description]
When the "Restrict so that only users included in the swadmin group can start demand jobs, start jobnet Job execution control attributes or use Jobscheduler command functions." check box is not checked, change of access privileges for files under the Jobscheduler service database directory has failed.
[User Response]
Check that the Jobscheduler database directory exists and attributes of the database directory, the files in the database directory and subdirectories are modifiable.
[System Administrator Response]
Review the access privileges for files under the Jobscheduler service database directory.
[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
[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]
Failed to set distributed policy information.
[Parameter]
XXXX : Policy information file
[System Action]
Continues processing by ignoring the information for which settings could not be done.
[System Administrator Response]
Check the information for which settings could not be done. Restart the JobScheduler service when you correct policy information settings.
In case of acldata.bat file, the cause behind the failure is that, the user account information in the extraction source server and the distribution destination server does not match. Hence, take one of the following actions.
Register the same user account on the distribution destination server and the extraction source server.
Change the operand of security command (mpsetacl, mpchown) within acldata.bat file to an existing user account.
Delete the acldata.bat file and then reset the security information in the Set Permissions window and the Change Owner window.
[Description]
Failed to obtain the host xxxx information written in the monitoring permission host definition file.
[Parameter]
xxxx: Host name
[System Action]
Does not communicate with the failed host.
[System Administrator Response]
Check the Define Monitoring Permission Host window, and then make settings so that registered hosts can acquire IP addresses using name resolution.
[Description]
Stopped the XXXX trace function due to abnormality in the trace function.
[Parameter]
XXXX: Name of program to be executed (e.g. tskussrv)
[System Action]
Stops further output of XXXX trace information.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
The job net did not start on the estimated start time since the message event for starting was not generated or the previous job net did not end normally.
[Parameter]
XXXX: Project name
YYYY: Job net name
[System Action]
Job net is not started on the estimated start time.
[System Administrator Response]
Generate the message event that caused lack of startup condition or start the previous job net and terminate it normally.
[Description]
The job net could not finish before the estimated end time.
[Parameter]
XXXX: Project Name
YYYY: Job Net Name
[User Response]
This message may be output even when a job net does not start.
If the day change time is changed, time inversion between the startup scheduled time and the end scheduled time may occur, causing this message to be output. Verify that the following condition is met:
Day change time <= Startup scheduled time < End scheduled time
[Description]
The group YYYY of the project XXXX has not yet finished, so scheduling is done after it ends.
A group is started once a day and schedule on the day is determined depending on the startup day of job nets within the group.
If the group is not completed successfully at the day change time, the group does not perform the subsequent scheduling. The execution of the subsequent schedule is notified of when the group has completed successfully.
Note that, when the group is in either status below, groups scheduled on the day will be carried over even if day change time elapses.
When the group is not started.
When the group confirmation is validated and the execution status is Abended, Canceled or Closed.
[Parameter]
XXXX: Project name
YYYY: Group name
[User Response]
If the group is executing, wait until it completes. If the group is waiting for execution, the message event of the head job net may not be generated yet. Confirm the reason why the message was not generated.
[Description]
A variable parameter specified for the jobschmsgevent command has been ignored by the job net receiving it. The message event itself has been received successfully.
The cause can be attributed to the following factors:
The job net receiving the message event may not have Job Execution Control attributes. Only job nets with Job Execution Control attributes can receive variable parameters.
The job net receiving the variable parameters is neither of the following:
A job net waiting for a single message event
A job net waiting for any of a number of message events
Only job nets waiting for a single message event and job nets waiting for any of a number of specific message events can receive variable parameters.
[Parameter]
XXXX: Project name
YYYY: The name of the job net receiving the variable parameters
[System Action]
Continues the process. However, the variable parameters will be disabled.
[System Administrator Response]
Use a job net with Job Execution Control attributes as the job net receiving the variable parameters.
To allow a job net to receive variable parameters , use a job net that is waiting for a single message event or waiting for any of a number of message events.
[Description]
Failure in CreateProcess of the job net abort exit routine (jobschexit.bat/jobschexit.exe).
[System Action]
Does not execute the job net abort exit routine (jobschexit.bat/jobschexit.exe).
[System Administrator Response]
Check for the presence and execution privileges of the job net abort exit routine (jobschexit.bat/jobschexit.exe) if the job net aborts or is forcibly terminated.
[Description]
Either of the following occurred:
Failed to access the job net information directory of Jobscheduler.
Exceeded upper limit (256) of number of users that can be registered to Jobscheduler.
[System Administrator Response]
Read the message displayed before this message, then find the cause of this abnormality.
[Description]
Could not read job net information due to failure in open, lockf, or read processing of schedule information.
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring schedule files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Could not write job net information or job net history information (net.spool).
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring schedule files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
An error occurred in the time system call.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
An error occurred in creating a shared memory.
[System Action]
Aborts processing.
[System Administrator Response]
Check if the system has enough resources.
[Description]
The following symptoms have occurred:
The database directory is not specified in the startup parameter of Jobscheduler.
The Jobscheduler service is not started.
[System Action]
Aborts processing.
[System Administrator Response]
If the database directory is not correctly specified, specify a valid value. If the Jobscheduler service is not started, start the service.
[Description]
One of the following symptoms occurred:
No database directory is specified in the startup parameter of Jobscheduler.
Failed to read the directory specified in the startup parameter of Jobscheduler.
Failure in "chdir" to the directory specified in the startup parameter of Jobscheduler.
[System Action]
Aborts processing.
[System Administrator Response]
If the database directory is not specified in the startup parameter of Jobscheduler, specify it. Otherwise, check for the directory specified in the startup parameter of Jobscheduler.
[Description]
An error occurred in obtaining a shared memory.
[System Action]
Aborts processing.
[System Administrator Response]
If the error cause is not clear, collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
The job net specified by the Jobscheduler command parameter is not registered yet in the job net information.
[System Action]
Aborts processing.
[User Response]
Check the Jobscheduler command parameters for an error.
[Description]
Invalid argument in message execution control process (tskmmsrv).
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failure either in open, lockf, or read processing of message information.
[System Action]
Aborts processing.
[System Administrator Response]
Read the message displayed before this message, then find the cause of the abnormality.
[Description]
Failure in "LoadLibrary".
[System Action]
Aborts processing.
[System Administrator Response]
Read the message displayed before this message, then find the cause of the abnormality.
[Description]
Failed to acquire day change time from the calendar function.
[System Action]
Aborts processing.
[System Administrator Response]
Check if Systemwalker MpJmCal service is running properly. Also check if the Calendar function is enabled for the Operation Manager Client and the day change time is defined correctly.
[Description]
Exceeded the upper limit (1000) of the number of projects that can be registered to Jobscheduler.
[System Action]
Aborts processing.
[System Administrator Response]
Delete unwanted projects.
[Description]
There is no information of the project in the shared memory controlled by Jobscheduler.
[System Action]
Aborts processing.
[System Administrator Response]
Check if the number of registered projects does not exceed 1000. If more than 1000 projects are registered, configure subsystems and reduce the number of registered projects on the system. Also check if the project is not deleted.
[Description]
Job information controlled by Jobscheduler is invalid.
[System Action]
Aborts processing.
[User Response]
Check if the project is not deleted.
[Description]
Failed to set distributed policy information.
[System Action]
Aborts the service start process.
[System Administrator Response]
Distribute policy information again.
[Description]
An error has occurred while reading the project information (Project name : .jsp file).
[System Action]
Aborts processing
[System Administrator Response]
Remove the cause of the abnormality by referring to the message displayed before this message.
[Description]
Could not obtain job standard output/standard error output because an error occurred in controlling job standard output/standard error output.
[System Action]
Aborts processing.
[System Administrator Response]
Remove the cause of the abnormality by referring to the message displayed before this message.
[Description]
Failure in CreateProcess when starting the Jobscheduler service.
System may be overloaded.
[System Action]
Aborts processing.
[System Administrator Response]
Start the Jobscheduler service (Systemwalker MpJobsch service) when the system is less loaded.
[Description]
Reading of the startup parameter information for the Jobscheduler service failed.
The startup parameter definition file (jobschev.txt) may be damaged.
[System Action]
Aborts the service startup process.
[System Administrator Response]
Recover the startup parameter definition file manually according to the following steps:
Delete the startup parameter definition file (Systemwalker installation directory\mpjobsch\etc\jobschev.txt).
Reset the startup parameter in the Define Jobscheduler Startup Parameters window.
At this time, a popup message that indicates there is no startup parameter definition file and the file will be created appears. Then, click the OK button and set the startup parameter.
After the recovery, start the Jobscheduler service (Systemwalker MpJobsch service).
[Description]
Could not write job net/job start/end message due to failure in open, lockf, write, or time processing (for obtaining time) of job information.
[System Action]
Aborts processing.
[System Administrator Response]
Read the message displayed before this message and remove the cause of this abnormality.
[Description]
Could not read the schedule pattern information due to failure in "open", "lockf", or "read" processing of schedule pattern information (db_calendar_ex.default).
[System Action]
Aborts processing.
[System Administrator Response]
Read the message displayed before this message, and remove the cause of this abnormality.
[Description]
An error occurred while accessing the jobschlock directory when starting the Jobscheduler service.
[System Action]
Aborts processing.
[System Administrator Response]
Check if the files stored in jobschlock directory is accessible (and not read-only).
Systemwalker installation directory\MPWALKER.JM\mpjobsch\jobdb\jobschlock
or
Systemwalker installation directory\MPWALKER.JM\mpjobsch\jobdbn\jobschlock
"n" of "jobdbn" indicates a subsystem number (1 to 9).
Solaris version:
/var/opt/FJSVJOBSC/jobschlock
or
/var/opt/FJSVJOBSC/JOBDBn/jobschlock
HP-UX version:
/opt/FHPJOBSCH/db/jobschlock
or
/opt/FHPJOBSCH/db/JOBDBn/jobschlock
AIX version:
/usr/FAIXJOBSC/db/jobschlock
or
/usr/FAIXJOBSC/db/JOBDBn/jobschlock
Linux version:
/var/opt/FJSVJOBSC/jobschlock
or
/var/opt/FJSVJOBSC/JOBDBn/jobschlock
"n" of "JOBDBn" indicates a subsystem number (1 to 9).
[Description]
Failure in "open" or "read" processing of schedule pattern information (db_calendar_ex.default).
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule pattern information (db_calendar_ex.default) from the jobschbackup directory under the database directory. See "When the Disk Space is Insufficient" in the Systemwalker Operation Manager User's Guide for how to restore the information.
[Description]
The Jobscheduler service has already been started.
[System Action]
Aborts processing.
[System Administrator Response]
Review the startup process so as not to start the Jobscheduler service repeatedly.
[Description]
There is no calendar information.
[System Action]
Aborts processing.
[System Administrator Response]
sysfile.sys which is the database of day change time/holiday information in the database directory has been deleted or there is no holiday calendar referred to by job nets.
If sysfile.sys has been deleted, restart the Jobscheduler service (Systemwalker MpJobsch service) since it is recreated at the startup of the Jobscheduler service.
If no holiday calendar to be referred to exists, create a holiday calendar with the same name as the one to be referred to or set the relevant calendar correctly.
[Description]
Failure in updating calendar information.
[System Action]
Aborts processing.
[System Administrator Response]
Check that sysfile.sys which is the database of day change time/holiday information is accessible (whether it is read-only etc.).
[Description]
Unrecoverable error suspended Jobscheduler command processing. The Jobscheduler service may not be started.
[System Action]
Aborts processing.
[System Administrator Response]
Start the Jobscheduler service.
[Description]
There is no log information. Log information may just have been switched or job net may not be executed.
[System Action]
Aborts processing.
[User Response]
To view log information before switching, use an editor to see the previous log file.
[Description]
Could not read/change calendar information.
[System Action]
Aborts processing.
[User Response]
Please check whether the problem relates to any of the following:
The Systemwalker MpJmCal service is not started.
The calendar name specified is incorrect.
The calendar referred to by JobScheduler or Service/Application startup definitions has been deleted.
[Description]
Target job net does not exist.
[System Action]
Aborts processing.
[User Response]
Check the job net name.
[Description]
The name of the target job net is invalid.
[System Action]
Aborts processing.
[User Response]
Check the job net name.
[Description]
The host name that is greater than 64 bytes is specified in the monitoring host definition file.
[System Action]
If the host name length is greater than 64 bytes, the host name is ignored. .
[User Response]
Correct the monitoring host definition file in the Define Monitoring Host window. This definition can also be corrected by using the omgrmonitor command.
[Description]
Invalid host name is specified in the monitoring host definition file .
[System Action]
Aborts processing.
[System Administrator Response]
Correct the monitoring host definition file on the Define Monitoring Host window. This definition can also be corrected by using the omgrmonitor command.
[Description]
Invalid host name for the local host.
[System Action]
Aborts processing.
[System Administrator Response]
Set the host name of local host as the OS.
[Description]
An error occurred in the getaddrinfo function.
[System Action]
Aborts processing.
[System Administrator Response]
Check the network configuration on the server.
[Description]
An abnormality occurred in communication with the Jobscheduler service on the monitored host.
[System Action]
Aborts processing.
[System Administrator Response]
Check if there is no problem on the network between the monitoring host and the monitored host.
[Description]
An error occurred in the select system call.
[System Action]
Aborts processing.
[System Administrator Response]
Confirm whether the network has any problem.
[Description]
No host name is specified in the monitoring host definition file.
[System Action]
Aborts processing.
[System Administrator Response]
Correct the monitoring host definition file in the Define Monitoring Host window. This definition can also be corrected by using the omgrmonitor command.
[Description]
Invalid host information is held internally.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
An abnormality occurred in communication with the Jobscheduler service.
[System Action]
Aborts processing.
[System Administrator Response]
Check if the monitoring host is defined correctly (the host name and the IP address), and there is no problem on the network between the monitoring host and the monitored host.
[Description]
Failed to obtain the service name of "jobsch_tcp" to be used for communication with the monitoring host.
[System Action]
Aborts processing.
[System Administrator Response]
Specify the service name "jobsch_tcp" (default value 9240/tcp) in the system root\etc\services file. If the host is using the name service, define the settings accordingly.
[Description]
There are 0 bytes of job net information.
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring schedule files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
An abnormality occurred during job net information communication inside the Jobscheduler service.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failed to read the job net output information.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
An error occurred in the getaddrinfo function.
[System Action]
Aborts processing.
[System Administrator Response]
Check whether the IP addresses of the hosts specified in the monitoring host definition file and the monitoring permission host definition file are registered in "SystemRoot\etc\hosts". The IP addresses of these hosts can be confirmed in the following windows:
Monitoring Host definition file: Define Monitoring Host window
Monitoring Permission Host definition file: Define Monitoring Permission Host window.
[Description]
Could not read due to failure in opening the access host definition file (database directory\msm.db\access_hosts).
[System Action]
Aborts processing.
[System Administrator Response]
Check for the presence of the access host definition file (database directory\msm.db\access_hosts).
If the monitor authorization host file does not exist, set the Monitoring Permission Host from the Environment Setup Client.
[Description]
Failed to obtain the machine ID used in Job Execution Control.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failure to send job net information to the multiple system monitor processes (tskmssrv).
[System Action]
Aborts processing.
[System Administrator Response]
Confirm whether the network environment has any problem.
[Description]
Invalid argument in the Job Execution Control job net management process (tskbasrv).
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
A host name containing spaces or tab characters is specified in the monitoring host definition file.
[System Action]
Ignores the host name with spaces or tab characters.
[System Administrator Response]
Correct the monitoring host definition file on the Define Monitoring Host window.
[Description]
A host name containing spaces or tab characters is specified in the monitoring permission host definition file.
[System Action]
Ignores host name with spaces or tab characters.
[System Administrator Response]
Correct the monitoring host permission definition file on the Define Monitoring Permission Host window.
[Description]
Failed to execute a job in a job net of Job Execution Control.
[System Action]
Does not execute the job and returns completion code 243.
[User Response]
Take corrective measures logged to job output information against the error message of Job Execution Control .
[Description]
Failure to create the file used to prevent repeated execution of Jobscheduler commands.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
The monitoring host definition file does not exist.
[System Action]
Aborts processing.
[System Administrator Response]
Correct the monitoring host definition file in the Define Monitoring Host window. This definition can also be corrected by using the omgrmonitor command.
[Description]
Mistake in the mail link process (tskmlsrv) argument.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Invalid argument in the communication control process (tskwnsrv).
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
A communication error occurred between the Jobscheduler service and the Operation Manager Client.
For the cause of the communication error (TCP/IP socket error), refer to the error message logged before this message such as "MpJobsch: ERROR: write() broken pipe", and "MpJobsch: ERROR: read() Connection reset by peer".
These messages indicate that the socket was disconnected illegally and the Operation Manager Client was terminated abnormally.
[System Action]
Handles the socket error and continues processing.
[System Administrator Response]
If this problem persists, check the configuration and the network environment. The operational settings may be preventing the Operation Manager Client from exiting normally (such as frequent reset of the client PC), or the network may have encountered a problem.
[Description]
Failure in communication between the communication control process (tskwnsrv) or the host list process (tskmdsrv) and PC.
[System Action]
Aborts processing.
[System Administrator Response]
If this problem persists, check the configuration and the network environment. The operational settings may be preventing the Operation Manager Client from exiting normally (such as frequent reset of the client PC), or the network may have encountered a problem.
No action is required, if this error rarely occurs.
[Description]
The local host name exceeds 64 bytes.
[System Action]
Aborts processing.
[User Response]
Specify a local host name within 64 bytes.
[Description]
Failure to obtain service name jobsch_win to be used for communication with Jobscheduler/CL.
[System Action]
Cannot use Jobscheduler/CL.
[System Administrator Response]
Specify service name jobsch_win (default value 9297/tcp) in the system root\etc\services file. If the host is using the name service, define the settings accordingly.
[Description]
Cannot start the Jobscheduler service because the PC or the host list process (tskmdsrv) was connected when the Jobscheduler service was last exited.
[System Action]
Aborts processing.
[System Administrator Response]
Start the Jobscheduler service one minute after shutting down the PC.
[Description]
Detected an invalid record in calendar information.
[System Action]
Aborts processing.
[System Administrator Response]
Restart the Jobscheduler service.
[Description]
Cannot re-schedule groups or job nets because an interprocess communication error occurred.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Cannot read log information due to failure to open it.
[System Action]
Aborts processing.
[System Administrator Response]
Identify the cause of failure in accessing log information (jobdb1.log, jobdb2.log and jobdb3.log located in the database directory).
[Description]
Failed to read the group information
[System Action]
Aborts processing.
[System Administrator Response]
Read the message displayed before this message and remove the cause of this abnormality.
[Description]
Failed to write the group information.
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring schedule files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Failure in CreateProcess of the log information switch exit routine (jobdbexit.bat/jobdbexit.exe).
[System Action]
Does not execute the log information switch exit routine (jobdbexit.bat/jobdbexit.exe).
[System Administrator Response]
Check for the presence and execution privileges of the log information switch exit routine (jobdbexit.bat/jobdbexit.exe).
[Description]
Failure to send the group information to the multi-system monitoring processes (tskmssrv).
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Cannot execute specified operation because the group is being saved or controlled.
[System Action]
Aborts processing.
[User Response]
Perform operation after a while.
[Description]
Invalid argument in the host list process (tskmdsrv).
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Invalid argument in the event management process (tskevsrv).
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failure in CreateProcess of the day change time notice exit routine. (timeexit.bat/timeexit.exe).
[System Action]
Does not execute the day change time notification exit routine (timeexit.bat/timeexit.exe).
[System Administrator Response]
Check for the presence and execution privileges of the day change time notification exit routine (timeexit.bat/timeexit.exe).
[Description]
Failed to obtain service name jobsch_win to be used for communication with the communication control process (tskwnsrv).
[System Action]
Cannot use Jobscheduler/CL.
[System Administrator Response]
Specify service name jobsch_win (default value 9297/tcp) in the system root\etc\services file. If the host is using the name service, define the settings accordingly.
[Description]
Cannot execute specified operation because the Jobscheduler service is being started.
[System Action]
Aborts processing.
[User Response]
Perform operation after the Jobscheduler service has been started.
[Description]
Invalid environment variable LANG.
[System Action]
If this message is output by the service, it operates in English environment. If output by the command, the service is not started.
[User Response]
Correct environment variable LANG, then restart the service or command.
[Description]
Failed in CreateProcess for the job completion exit routine (jobexit.bat/jobexit.exe).
[System Action]
The Job completion exit routine (jobexit.bat/jobexit.exe) is not started.
[System Administrator Response]
Check for the presence and execution privileges of the job completion exit routine (jobexit.bat/jobexit.exe).
[Description]
The database under JOBDB PATH is for previous versions.
[System Action]
Aborts processing.
[System Administrator Response]
Convert the database by using the jobschconvert command.
[Description]
Failed to obtain the resources for interprocess communication.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failed to receive a message during interprocess communication.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failed to send the message during interprocess communication.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failed to obtain the resources for interprocess communication.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failure to send the message during interprocess communication.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Could not obtain memory required for creating process.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Could not obtain a buffer memory required for interprocess communication.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Invalid argument in the event log monitor process (tskelsrv).
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
There is no message event name for the jobschmegevent command.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failure in CreateProcess of the message event handling process. System may be overloaded.
[System Action]
Aborts processing.
[System Administrator Response]
Start the Jobscheduler service when the system is less loaded.
[Description]
Failed to open the message table (database directory\JOBSCHMSGEVENT.TBL).
[System Action]
Aborts processing.
[System Administrator Response]
Change the attribute on the logon account of the Jobscheduler service (Systemwalker MpJobsch service) to be able to access jobschmsgevent.tbl located in the database directory.
[Description]
Failed to read the startup parameter of the Jobscheduler service. Registry information may be corrupted.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Invalid startup parameter of the Jobscheduler service. Registry information may be corrupted.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
No work directory (WORK) exists as a subdirectory for the database directory.
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Failure in CreateProcess of the job net completion exit routine (normalexit.bat/normalexit.exe).
[System Action]
Does not execute the job net completion exit routine (normalexit.bat/normalexit.exe).
[System Administrator Response]
Check for the presence and execution privileges of the job net completion exit routine (normalexit.bat/normalexit.exe).
[Description]
Cannot execute specified operation because the Jobscheduler service is being started.
[System Action]
Aborts processing.
[User Response]
Perform operation after the Jobscheduler service has been started.
[Description]
No drive name available for user authentication.
[System Action]
Aborts user authentication.
[User Response]
Among drive names of the computer on which the Jobscheduler service is running (A to Z), change the status of unwanted drive names to unused and retry execution.
[Description]
Failed to create the process activation delay exit routine (startlateexit.bat/startlateexit.exe)of job net.
[System Action]
Does not activate the activation delay exit routine (startlateexit.bat/startlateexit.exe)of job net.
[System Administrator Response]
Review the existence and execution privileges for the activation delay exit routine (startlateexit.bat/startlateexit.exe) of the job net.
[Description]
Failed to create the process termination delay exit routine (endlateexit.bat/endlateexit.exe) of job net.
[System Action]
Does not start the termination delay exit routine (endlateexit.bat/endlateexit.exe)of the job net.
[System Administrator Response]
Review the existence and execution privileges for the termination delay exit routine (endlateexit.bat/endlateexit.exe) of the job net.
[Description]
The Jobscheduler service could not be started due to failure in changing access privileges of the files in the Jobscheduler service database directory when the "Restrict so that only users included in the swadmin group can start demand jobs, start jobnets, Job execution control attributes or use Jobscheduler command functions" check box is checked.
[System Administrator Response]
If this message is generated at the same time as the error message 6346, see the actions for that message. If the error message 6346 is not generated at the same time, check for the presence of the swadmin group and the access privileges for the files under the Jobscheduler service database directory. Then restart the Jobscheduler service.
[Description]
The Jobscheduler database directory is not on the NTFS file system. Security cannot be reinforced.
[System Administrator Response]
Move the Jobscheduler database directory to the NTFS file system.
[Description]
Failed to read the parameter information file for the job.
[System Action]
Aborts processing.
[User Response]
Copy the parameter information of the job from the jobschbdirectory to the database directory and restart Jobscheduler.
[Description]
The project specified to process is missing.
[System Action]
Aborts processing.
[User Response]
Check the project name.
[Description]
Failed to access the schedule information.
[System Action]
Aborts processing.
[System Administrator Response]
Check whether an application that accesses the files under the Jobscheduler database directory exists. If exists, prevent it from accessing the files while Jobscheudler is operating.
[Description]
Writing to the message event occurrence history file failed.
[System Action]
Continues processing without writing to the message event occurrence history file.
[System Administrator Response]
Read the message displayed before this message, then find the cause of this abnormality.
[Description]
The license key is not registered, or the trial period has expired.
[System Action]
Outputs the message and cancels the processing.
[System Administrator Response]
A license is required. Refer to "Relese Note" for information on corrective measures.
[Description]
An error occurred in the system function.
[Parameter]
XXXX: Calling function name
YYYY: Name of function where error occurred
ZZZZ: Error message of system
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Received a signal in the main process of the Jobscheduler service.
[Parameter]
XXXX: Signal name (SIGABRT/SIGILL/SIGINT/SIGSEGV/SIGTERM)
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Detected a record in one of the following conditions when reading job net information:
Invalid record length
Invalid as first record in job net information
[Parameter]
XXXX: Project name
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring schedule files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Could not read schedule information due to failure in open, lockf, or read of the information.
[Parameter]
XXXX: Project name
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring schedule files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Could not write the schedule information or job net history information (net.spool) of Jobscheduler .
[Parameter]
XXXX: Project name
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring schedule files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Failure in the backing up file.
[Parameter]
XXXX: File name
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Jobscheduler cannot handle project name exceeding 50 characters.
[Parameter]
XXXX: project name
[System Action]
Aborts processing.
[User Response]
Specify a project name within 50 characters for Jobscheduler.
[Description]
Failure to execute the file.
[Parameter]
XXXX: File name
[System Action]
Aborts processing.
[User Response]
Check for the presence and execution privileges of the file.
[Description]
Failed to read the schedule information because of failure in "open", "lockf", or "read".
[Parameter]
XXXX: Project name
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring schedule files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Invalid record was found in the schedule information.
[Parameter]
XXXX: Project name
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring schedule files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Could not write the schedule information because of failure in "open", "lockf", or "read".
[Parameter]
XXXX: Project name
[System Action]
Aborts processing.
[System Administrator Response]
Restore schedule information from the jobschbackup directory located in the database directory. See "Restoring schedule files" in the Systemwalker Operation Manager User's Guide for how to restore the file.
[Description]
Jobscheduler can handle only user names specified within 20 characters.
[Parameter]
XXXX : user name
[System Action]
Aborts processing.
[User Response]
Specify a user name within 20 characters.
[Description]
An error occurred in the system function.
[Parameter]
XXXX: Calling function name
YYYY: Name of function where error occurred
CCCC: Error number
ZZZZ: Error message of system
[System Action]
Aborts processing
[System Administrator Response]
YYYY and later is "RegisterEventSource() 5: Access denied."
If the jobschmsgevent command is executed specifying the target host of message events, check the following:
The user who is executing the command is a registered user on the target host, and the password matches, and
The user is valid.
If one of the above requirements is not satisfied, use a network job and generate the message event on the target host.
YYYY and later is "Regist RegisterEventSource() 1722: RPC server is not available"
If the jobschmsgevent command is executed specifying the target host of message events, specify an existing host name and a Windows computer. Also, start the Server service on the target host.
YYYY and later is "ReportEvent() 997: Redundant I/O process."
In the Properties of the Windows Event log, select the option "Overwrite events as needed".
YYYY and later is "ReadFile() 6: Invalid handle"
Check whether any irrelevant file has been created in the Jobscheduler database directory. If created, delete the file.
YYYY and later is "ReadFile() 170:The requested resource is in use."
The resource for the Jobscheduler is being used by another application. Identify the cause by referring to the messages output before and after this message and take an appropriate corrective action.
YYYY and later is "SetEndOfFile() 1224:The requested operation cannot be performed on a file with a user mapped section open."
The resource for the Jobscheduler is being used by another application. Identify the cause by referring to the messages output before and after this message and take an appropriate corrective action.
YYYY and later is "GetTempFileName() 80:The file exists."
Check that the disk resource is not exhausted. It may be exhausted when the temporary files used with exit programs have not been deleted. When using exit programs, set them so that they delete the temporary files. For the exit information, see "Exit Information" in the Systemwalker Operation Manager Reference Guide.
CCCC and later is "1500:The event log file is corrupt."
Restore the event log file based on the associated documents of Microsoft or Windows.
For other error messages, collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
An error occurred in the system function.
[Parameter]
XXXX: Calling function name
YYYY: Name of function where error occurred
ZZZZ: Error message of system
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
XXXX keyword definition is missing in the message table (JOBSCHMSGEVENT.TBL).
[Parameter]
XXXX: Keyword
[System Action]
Aborts processing.
[System Administrator Response]
Correct the keyword in message table in the Define Message Table window.
[Description]
An invalid keyword is specified in the message table (JOBSCHMSGEVENT.TBL).
[Parameter]
XXXX: Keyword
[System Action]
Aborts processing.
[System Administrator Response]
Correct the keyword in message table in the Define Message Table window.
[Description]
The Jobscheduler service process aborted.
[Parameter]
XXXX: Process name (e.g. tskbasrv)
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Invalid subdirectory in the database directory.
[Parameter]
XXXX: Subdirectory name
[System Action]
Aborts processing.
[System Administrator Response]
Check the file and access privileges of the database directory.
[Description]
Failed to access the file.
[Parameter]
XXXX: File name
[System Action]
Aborts processing.
[User Response]
Refer to the message logged prior to this message and resolve the problem.
[Description]
XXXX = 3, YYYYY = 0
A connection error occurred.
Other than the above
An error occurred while the ACL Manager was running.
[Parameter]
XXXX: Error code
YYYY: Detailed code
[System Action]
Aborts processing.
[Corrective Measures]
XXXX = 3, YYYYY = 0
Check that the Systemwalker ACL Manager service is running on the Operation Manager server.
If the service is running or for cases other than the above, collect the maintenance information on Framework - Security with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
Job definition variable information could not be read because an "open", "lockf" or "read" operation failed.
[System Action]
Aborts processing.
[Corrective Measures]
Restore the job definition variable information from the jobschbackup directory under the database directory. Refer to "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for information about how to restore job definition variable information.
[Description]
Job definition variable information could not be written because an "open", "lockf", "read" or "write" operation failed.
[System Action]
Aborts processing.
[Corrective Measures]
Restore the job definition variable information from the jobschbackup directory under the database directory. Refer to "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for information about how to restore job definition variable information.
[Description]
A message event with specified variable parameters has been ignored by the destination job net. The cause can be attributed to the following factors:
The destination job net may have been stopped when it received the message event with variable parameters.
Valid during job net execution may have been specified for the destination job net and the message event with variable parameters may have been received while the job net was executing.
[Parameter]
XXXX: Project Name
YYYY: The name of the job net receiving the variable parameters
ZZZZ: Message event name
[System Action]
Aborts processing.
[Corrective Measures]
Perform a Continue operation for the destination job net.
To have the job net receive message events with variable parameters even while it is executing, make copy specifications using the jobschmsgevent command.
[Description]
Reading parameter information for a job has failed.
[Parameter]
XXXX: File name
[System Action]
Aborts processing.
[Corrective Measures]
Restore the job parameter information from the jobschbackup directory under the database directory. Refer to "Restoring Schedule Files" in the Systemwalker Operation Manager User's Guide for information about how to restore job parameter information.
[Description]
Writing parameter information for a job has failed.
[Parameter]
XXXX: File name
[System Action]
Aborts processing.
[Corrective Measures]
Check whether it is possible to access the parameter information file for the job (such as whether users belonging to the Administrators group have write privileges, for example).
[Description]
Writing variable parameter information has failed.
[Parameter]
XXXX: File name
[System Action]
Aborts processing.
[Corrective Measures]
Check whether it is possible to access the parameter information file (by checking whether the root user has write permissions, for example).
[Description]
Reading of the jobnet variable information file failed.
[Parameter]
XXXX: FILE NAME
[System Action]
Aborts processing.
[System Administrator Response]
Read the message displayed before this message, then find the cause of this abnormality.
[Description]
Writing to the jobnet variable information file failed.
[Parameter]
XXXX: FILE NAME
[System Action]
Aborts processing.
[System Administrator Response]
Read the message displayed before this message, then find the cause of this abnormality.
[Description]
Deletion of the jobnet variable information file during job net startup failed.
[Parameter]
XXXX: FILE NAME
[System Action]
Aborts processing.
[System Administrator Response]
Check if the file is accessible (and privileges such as write privileges have been granted to the root user).
[Description]
Deleted due to an abnormality in the information of group YYYY of user XXXX.
[Parameter]
XXXX: User name
YYYY: Group name
[System Action]
Deletes group YYYY of user XXXX, then continues processing.
[System Administrator Response]
Restore the group information from the jobschbackup directory under the database directory.
[Description]
There is an invalid definition in the message event table (JOBSCHMSGEVENT.TBL).
[Parameter]
XXXX: Start line number of invalid definition
YYYY: End line number of invalid definition
[System Action]
Ignores lines with the invalid definition and continues processing
[System Administrator Response]
Correct the message table in the Define Message Table window.
[Description]
An error occurred in the system function (Windows Sockets).
[Parameter]
XXXX: Calling function name
YYYY: Name of function where error occurred
ZZZZ: Error code of system
[System Action]
Aborts processing.
[System Administrator Response]
Collect Jobscheduler information with the Maintenance Information Collection Tool and contact a Fujitsu's system engineer.
[Description]
You cannot activate shutdown job net as a startup condition at system startup.
[Parameter]
XXXX: Start line number of definition error
YYYY: End line number of definition error
[System Action]
Continues processing without activating the job net.
[System Administrator Response]
Redefine startup conditions for shutdown job net.
[Description]
An attempt was made to copy and start a job net according to the copy and startup specification in the jobschmsgevent command, but the attempt failed.
The cause can be attributed to the following factors:
If the previous job net that was copied and started has not finished executing, the next copy and startup operation will not be performed. The status of the previous job net that was copied and started is "Executing", "End delayed" or "Warning".
If a confirmation operation has not been performed on the previous job net that was copied and started, the next copy and startup operation will not be performed. In environments where the Validate job net confirmation check box has been selected in the Advanced Settings for Verification window, the status of the previous job net is "Abended". In environments where the Check canceled check box has also been selected, the status of the previous job net is "Canceled".
The copy job net may have been created using a method other than copy and startup. Job nets that have been created using methods other than copy and startup (such as job nets that have been created manually using the Jobscheduler window) cannot be copied using copy and startup
Under-scores (_) and suffixes are attached to the names and comments of job nets that are created by copying. This may have caused the length of the job net name or job net comment to exceed the maximum length.
[Parameter]
XXXX: Project Name
YYYY: The name of the copy job net
[System Action]
Aborts processing. The job net will not be copied or started.
[Corrective Measures]
Adjust the timing of when message events occur so that the next copy/startup does not occur until after the copy job net (the job net that was started earlier by copying the source job net using the copy and startup function) has finished executing.
Perform a confirmation operation on the preceding job net that was copied and started.
Either delete the job net that was created using a method other than copy and startup, or change the suffix that was specified in the -c option of the jobschmsgevent command when the job net was copied.
Change either the suffix or the original job net name or job net comment so that the length of the name and comment for the job net that is created by copying does not exceed the maximum length.
[Description]
Message for linking with System Monitor. Execution of the job net started.
[Parameter]
XXXX: Job net comment
YYYY: Job net name
ZZZZ: Project name
[Description]
Message for linking with System Monitor. The job net has been completed.
[Parameter]
XXXX: Job net comment
YYYY: Job net name
CCCC: Job net completion code
ZZZZ: Project name
[Description]
Message for linking with System Monitor. The job net has been terminated abnormally.
[Parameter]
XXXX: Job net comment
YYYY: Job net name
CCCC: Job net completion code
ZZZZ: Project name
[Description]
Message for linking with System Monitor. Job net execution was rejected.
[Parameter]
XXXX: Job net comment
YYYY: Job net name
ZZZZ: Project name
[Description]
Message for linking with System Monitor. Job net execution was skipped.
[Parameter]
XXXX: Job net comment
YYYY: Job net name
ZZZZ: Project name
[Description]
It is a message used for linking with System Monitor. Job net has been pseudo-normally terminated.
[Parameter]
XXXX: Job net comment
YYYY: Job net name
CCCC: Job net completion Code
ZZZZ: Project name
[Description]
Displays the message text specified as the argument of the job net execution API.
[Parameter]
XXXX: Message text specified as argument
[Description]
Displays the message text specified as the argument of the job net execution API.
[Parameter]
XXXX: Message text specified as argument
[Description]
Displays the message text specified as the argument of the job net execution API.
[Parameter]
XXXX: Message text specified as argument
