This section explains the messages having event IDs, which are output by Jobscheduler commands.
[Description]
The correct jobschprint command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
No job net information was found during jobschprint command execution.
[System Action]
Aborts processing.
[Description]
The correct jobschcontrol command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[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]
Use the registered job net name in the Jobscheduler command.
[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]
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 project.
[Description]
No project owner name was specified in the definition file.
[System Action]
Aborts processing.
[System Administrator Response]
Specify the project owner name in the definition file.
[Description]
The Jobscheduler command has incorrect schedule information.
[System Action]
Aborts processing.
[System Administrator Response]
If it is shown by the jobschsetnet command, collect the Jobscheduler information by using the Maintenance Information Collection Tool and contact Fujitsu technical support. Otherwise, output this file from the jobschbackup directory to the database directory, and restart Jobscheduler.
[Description]
The correct jobschsetcal command syntax is shown.
[System Administrator Response]
Specify command parameters in the correct format.
[Description]
The Jobscheduler command has an incorrect parameter.
[System Action]
Aborts processing.
[User Response]
Check the Jobscheduler command parameters for an error.
[Description]
Since the group is not scheduled to start today, it cannot be reactivated.
[System Action]
Aborts processing.
[System Administrator Response]
To start a group, perform start operation instead of restart operation.
[Description]
An error has occurred while writing the project information (project_name.jsp file).
[System Action]
Aborts processing.
[System Administrator Response]
the error cause by referring to the previous message.
[Description]
The specified operation is not executed because the job net is being executed or in the warning status.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the job net has changed to another status.
[Description]
The job net could not restart because it was not terminated abnormally, not terminated forcibly, or not confirmed.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the job net has changed to another status.
[Description]
The specified operation is not executed because the job net is not being executed or not in the warning status.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the job net has changed to another status.
[Description]
The definition file was not read because it could not be opened.
[System Action]
Aborts processing.
[User Response]
Make sure that the definition file exists and the user is authorized to read it.
[Description]
The definition file has an incorrect keyword.
[Parameter]
XXXX: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
Processing of the Jobscheduler command was interrupted.
[System Action]
Aborts processing.
[User Response]
Remove the error cause by referring to the previous message.
[Description]
The definition file has an error control statement or an incorrect sequence of control statements.
[Parameter]
XXXX: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
Could not write schedule pattern information (db_calendar_ex.default).
[System Action]
Aborts processing.
[System Administrator Response]
Remove the error cause by referring to the previous message.
[Description]
The schedule pattern data specified by the Jobscheduler command parameter does not exist in the schedule pattern file (db_calendar_ex.default).
[System Action]
Aborts processing.
[User Response]
Check the Jobscheduler command parameters for an error.
[Description]
The Jobscheduler command has an incorrect parameter.
[System Action]
Aborts processing.
[User Response]
Check the Jobscheduler command parameters for an error.
[Description]
There is no running job to be output by the jobschprint command.
[System Action]
Aborts processing.
[User Response]
Collect the Jobscheduler information by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
The parameter specified by the operand of the definition file does not exist.
[Parameter]
XXXX: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
There is an error in the parameter specified by the operand of the definition file.
[Parameter]
XXXX: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
The control statement did not end with a semicolon.
[Parameter]
XXXX: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
Operand xxxx was used incorrectly in the definition file.
[Parameter]
XXXX: Operand name
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
The user authorized to access the display that is output by the jobschprint command does not exist.
[System Action]
Aborts processing.
[Description]
There is no queued job that is output by the jobschprint command.
[System Action]
Aborts processing.
[Description]
There is no history information that is output by the jobschprint command.
[System Action]
Aborts processing.
[Description]
The correct jobschsethol command syntax is shown.
[System Administrator Response]
Specify command parameters in the correct format.
[Description]
The calendar information could not be updated.
[System Action]
Aborts processing.
[System Administrator Response]
Check the following points:
The "sysfile.sys" file locating under the database directory can be accessed. The file may be disabled to access due to a file I/O error or others.
The disk has a sufficient space.
[Description]
The log information (jobdb1.log, jobdb2.log and jobdb3.log files locating under the database directory) does not exist. The log information may have been just switched or the job net has not been started yet.
[System Action]
Aborts processing.
[User Response]
To refer to the log information before being switched, use an editor to refer to the previous log while no job or job net is operating.
[Description]
The number of parameters specified in the operand of the definition file is incorrect.
[Parameter]
XXXX: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
The correct jobschsetnet command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The job net to be processed already exists.
[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]
There is an error either in the list file or in the definition file being read by the jobschsetnet command.
[System Action]
Aborts processing.
[User Response]
Correct the list file or the definition file.
[Description]
There is an in consistency in the definition file.
[Parameter]
XXXX: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
The job net startup condition is not specified in the definition file that is being read by the jobschsetnet command.
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
No process is specified if the startup date overlaps a holiday in the definition file that is being read by the jobschsetnet command.
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
A cancellation of the date not included in the definition file has been specified.
[Parameter]
XXXX: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
An operand is duplicated in the definition file although it is not allowed.
[Parameter]
XXXX: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
A parameter is duplicated in the definition file.
[Parameter]
XXXX: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
The operands were specified in the incorrect sequence in the definition file.
[Parameter]
XXXX: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
The job net information held in the Jobscheduler command is incorrect.
[System Action]
Aborts processing
[System Administrator Response]
Collect the Jobscheduler information by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
The job net information of the project already registered in the shared memory does not exist.
[Parameter]
XXXX: Project name
[System Action]
Aborts processing.
[System Administrator Response]
Make sure that the job net has been registered.
[Description]
One of the phenomena below occurred.
The specified project does not exist.
The user has no access privileges to the specified project.
No job net or group has been registered in the specified project.
[Parameter]
XXXX : Project name
[System Action]
Aborts processing.
[User Response]
Make sure that the specified project exists and that the correct access privileges have been set to the project. Also, make sure that the specified job net or group has been registered in the project.
To check the access privilege to the project, select "Permissions" in the "Security" menu in the job selection window of the Systemwalker Operation Manager window.
[Description]
A record having one of the following errors was detected when the message event information was being read:
Incorrect record length
Invalid record contents
[System Action]
Aborts processing.
[System Administrator Response]
Copy the file from the jobschbackup directory to the database directory, and re-execute the jobschconvert command.
[Description]
A message deletion was attempted on the job net that has no message information.
[System Action]
Aborts processing.
[System Administrator Response]
Check the job net if it has message information or not.
[Description]
The file name specified with the jobschchkfile command is invalid.
[System Action]
Stops processing
[System Administrator Response]
Check the following points, and then execute the jobschchkfile command again.
Has the file name been specified using its full path?
Has a directory name been specified for the file name?
[Description]
Because the Network Queuing System (NQS) is not supported, an NQS job net cannot be set.
[System Action]
Aborts processing.
[System Administrator Response]
Specify something other than NQS for job net execution attributes.
[Description]
None of jobschsetnet, jobschsetgrp and jobschmove commands can be executed when the window is being displayed.
[System Action]
Aborts processing.
[User Response]
Terminate the client unit (JobScheduler/CL) first, then execute the jobschsetnet, jobschsetgrp, or jobschmove commands.
[Description]
A record having an invalid length was detected when the schedule pattern information (db_calendar_ex.default) was being read.
[System Action]
Aborts processing.
[System Administrator Response]
Copy the schedule pattern information (db_calendar_ex.default) from the jobschbackup directory to the database directory, and restart Jobscheduler.
[Description]
The correct jobschmsgclear command syntax is shown.
[User Response]
Specify command parameters in the correct format.
See "2.10 Messages Starting with MpJobsch".
Restore group information from the jobschbackup directory.
[Description]
The specified operation is not executed because the job net is being saved or controlled.
[System Action]
Aborts processing.
[User Response]
After a while, reexecute the process.
[Description]
The correct jobschctlgrp command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The group to be processed already exists.
[System Action]
Aborts processing.
[User Response]
Review the group name.
[Description]
The group to be processed does not exist.
[System Action]
Aborts processing.
[User Response]
Review the group name.
[Description]
The specified operation is not executed because the job net belongs to a group.
[System Action]
Aborts processing.
[User Response]
Remove the job net from the group.
[Description]
The specified operation is not executed because the job net does not belong to a group.
[System Action]
Aborts processing.
[User Response]
Review the operation.
[Description]
The specified operation is not executed because the job net is not in pause status.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the job net has changed to another status.
[Description]
The specified operation is not executed because the job net is already in pause status.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the job net has changed to another status.
[Description]
The specified operation is not executed because the job net is not disabled.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the job net has changed to another status.
[Description]
The specified operation is not executed because the job net is already disabled.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the job net has changed to another status.
[Description]
The specified operation is not executed because the group is already being executed or in the warning status.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group has changed to another status.
[Description]
The group could not be restarted because it was not terminated abnormally, not terminated forcibly, or not confirmed.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group has changed to another status.
[Description]
The specified operation is not executed because the group is not being executed or not in the warning status.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group has changed to another status.
[Description]
The specified operation could not be executed because the group was not terminated abnormally.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group has changed to another status.
[Description]
The specified operation is not executed because job net xxxx already belongs to a group.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
Remove the job net from the group.
[Description]
The specified operation could not be executed because the single startup of job net xxxx was not specified.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
Specify the single job net startup.
[Description]
Job net xxxx cannot be stored in the group because the Valid during job net execution option is checked as its startup condition at message event occurrence.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
In the Messages sheet of the Job Net Properties window, uncheck the Valid during job net execution option. Then, register the job net again.
[Description]
The correct jobschsetgrp command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The specified job was not defined in the definition file that was being read by the jobschsetnet command.
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
The correct jobschmove command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The group cannot be moved because the group specified by the jobschmove command is the same as the destination group.
[System Action]
Aborts processing.
[User Response]
Check the jobschmove command parameters for an error.
[Description]
The job net cannot be moved because the group specified by the jobschmove command contains the destination job net.
[System Action]
Aborts processing.
[User Response]
Check the jobschmove command parameters for an error.
[Description]
The job net cannot be moved because the job net specified by the jobschmove command is the same as the destination job net.
[System Action]
Aborts processing.
[User Response]
Check the jobschmove command parameters for an error.
[Description]
The correct jobschcod command syntax is shown.
[System Administrator Response]
Specify command parameters in the correct format.
[Description]
The job net was not found in the definition file that was being read by the jobschsetgrp command.
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
The specified operation is not executed because the group to which the job net belongs is being saved or controlled.
[System Action]
Aborts processing.
[User Response]
After a while, reexecute the process.
[Description]
The specified operation is not executed because the group to which the job net belongs is already being executed or in the warning status.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group to which the job net belongs has changed to another status.
[Description]
The schedule information is incorrect.
[System Action]
Aborts processing.
[System Administrator Response]
If this message is output during execution of the jobschsetgrp command, collect the Jobscheduler information by using the Maintenance Information Collection Tool and contact Fujitsu technical support. Otherwise, copy the schedule information (project_name.grz) from the jobschbackup directory to the database directory, and restart Jobscheduler.
[Description]
The group data is not included in the information held in the Jobscheduler command.
[System Action]
Aborts processing.
[System Administrator Response]
Collect the Jobscheduler information by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
The message information file was not read because the "open," "lockf" or "read" operation to the message information failed.
[Parameter]
XXXX: User name
[System Action]
Aborts processing.
[System Administrator Response]
Copy the file from the jobschbackup directory to the database directory, and reexecute the jobschconvert command.
[Description]
The group confirmation failed because the Validate group confirmation option was unchecked in the Advanced Settings for Verification window.
[System Action]
Aborts processing.
[System Administrator Response]
To use group confirmation, check the Validate group confirmation option in the Advanced Settings for Verification window, and restart Jobscheduler.
[Description]
No Jobscheduler functions can be used because there is no project having available access privileges or a job net available for an operation does not exist in the project.
[System Action]
Aborts processing.
[User Response]
Ask the project owner or system administrator to set access privileges for a project.
Alternatively, check if there is a job net in the project.
[System Administrator Response]
Register a project available to the user. Or, set access privileges to allow the user to work on a project.
Alternatively, add a job net available for an operation.
[Description]
The process failed because no project name was specified.
[System Action]
Aborts processing.
[User Response]
Specify a project name.
[Description]
The environment variable LANG is incorrect.
[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 Systemwalker Operation Manager, then reexecute the command.
[Description]
No database files can be converted when daemon xxxx is running.
[Parameter]
XXXX : Daemon name
[System Action]
Aborts processing.
[System Administrator Response]
Stop the daemon first and execute the command.
[Description]
When existing database files were converted into new database files, a database file disabled to convert was found.
[Parameter]
XXXX : File name (Types are given below)
user_name
user_name.grp
project_name.jsp
project_name.dbx
project_name.grp
project_name.dbz
project_name.grz
sysfile.sys
monitor_hosts_ex
holiday_info.db
db_calendar.default
db_calendar_ex.default
sroot.var
[System Action]
Aborts the conversion of XXXX database file and continues processing.
[System Administrator Response]
Make sure that database xxxx has the version before being converted. If the conversion of the day change and holiday database (sysfile.sys) has failed, the startup of Jobscheduler may fail. In such case, copy the old database file from the "jobschbackup" directory to the new database directory, and reexecute the conversion.
[Description]
The specified database file was not found.
[System Action]
Aborts processing.
[System Administrator Response]
Copy the schedule information file you need to convert to the database directory, and try again.
[Description]
The specified database file has already been converted.
[Parameter]
XXXX : File name (Types are given below)
user name
sysfile.sys
[System Action]
Aborts processing.
[System Administrator Response]
If you need to convert a database file again, delete the following files from the database directory. Then, try again.
If the parameter is a user name: user-name.dbz
If the parameter is sysfile.sys: sysfile.sys
[Description]
The correct jobschconvert command syntax is shown.
[System Administrator Response]
Specify command parameters in the correct format.
[Description]
The specified calendar name was not found.
[System Action]
Aborts processing.
[User Response]
Check the jobschsethol command parameters for an error.
[Description]
The specified command was not executed because the code system of the user environment (LANG environment variables) where Jobscheduler commands are executed does not match the language type of Systemwalker Operation Manager daemon that was specified during installation of Systemwalker Operation Manager.
[System Action]
Aborts the execution of the command.
[User Response]
Change the LANG environment variables so that the code system of user environment (LANG environment variables) matches the language type of Systemwalker Operation Manager.
[Description]
The specified operation could not be executed because the job net was not terminated abnormally.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the job net has changed to another status.
[Description]
The job net confirmation failed because the Validate job net confirmation option was unchecked in the Advanced Settings for Verification window.
[System Action]
Aborts processing.
[System Administrator Response]
To use job net confirmation, check the Validate job net confirmation option in the Advanced Settings for Verification window, and restart Jobscheduler.
[Description]
The specified operation is not executed because the group is already in pause status.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group has changed to another status.
[Description]
The specified operation is not executed because the group is already disabled.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group has changed to another status.
[Description]
The specified operation is not executed because the group is not paused.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group has changed to another status.
[Description]
The specified operation is not executed because the group is not disabled.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group has changed to another status.
[Description]
There is no calendar information that is displayed by the jobschprint command.
[System Action]
Aborts processing.
[User Response]
Check the Jobscheduler command parameters.
[Description]
Communication with the calendar daemon has failed.
[System Action]
Aborts processing.
[System Administrator Response]
Check the Operation Manager client if its calendar function is available or not.
[Description]
The correct jobschsetproject command syntax is shown.
[System Administrator Response]
Specify command parameters in the correct format.
[Description]
No access control is available because the ACL Manager daemon is inactive.
[System Action]
Aborts processing.
[System Administrator Response]
Restart Systemwalker Operation Manager.
[Description]
The specified project name was incorrect.
[System Action]
Aborts processing.
[User Response]
Specify the correct project name.
[Description]
The specified project is not deleted because the project contains the job net information.
[System Action]
Aborts processing.
[User Response]
Delete all job net information from the project.
[Description]
The specified user name is incorrect.
[System Action]
Aborts processing.
[User Response]
Specify the correct user name.
[Description]
One of the phenomena below occurred during conversion of calendar information.
The calendar name already exists.
The calendar name contains illegal character codes that the calendar daemon cannot use.
[Parameter]
XXXX: Calendar name
[System Action]
Does not convert the calendar information.
[System Administrator Response]
Convert the calendar information separately if its conversion has failed.
[Description]
An error has occurred in the calendar API during conversion of calendar information.
[Parameter]
XXXX: Calendar name
YYYY: Error code
[System Action]
Does not convert the calendar information.
[System Administrator Response]
Remove the error cause by checking the error number. For information about error numbers, see the "Calendar API" section of Systemwalker Operation Manager Reference Guide.
[Description]
The start date of temporary change has not been specified in the definition file.
[System Action]
Aborts processing.
[User Response]
Specify the start date of temporary change in the definition file.
[Description]
The system calendar is not allowed to delete.
[System Action]
Aborts processing.
[Description]
The correct jobschmsgevent command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
One of the following has occurred.
A job net having Interstage attributes was attempted to start in the system where the Interstage cannot be used.
Registration of a job net having Interstage attributes was attempted by the command in the system where the Interstage cannot be used.
[System Action]
Rejects job net execution if this message is output by the daemon. Cancels job net registration if this message is output by the command.
[System Administrator Response]
Make sure that the Interstage has been installed and it operates normally.
[Description]
The correct jobschprint command syntax is shown (for multiple subsystems).
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschcontrol command syntax is shown (for multiple subsystems).
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschsetcal command syntax is shown (for multiple subsystems).
[System Administrator Response]
Specify a parameter in the correct format.
[Description]
The correct jobschsetnet command syntax is shown (for multiple subsystems).
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschmsgclear command syntax is shown (for multiple subsystems).
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschctlgrp command syntax is shown (for multiple subsystems).
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschsetgrp command syntax is shown (for multiple subsystems).
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschmove command syntax is shown (for multiple subsystems).
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschconvert command syntax is shown (for multiple subsystems).
[System Administrator Response]
Specify command parameters in the correct format.
[Description]
The correct jobschsetproject command syntax is shown (for multiple subsystems).
[System Administrator Response]
Specify command parameters in the correct format
[Description]
The correct jobschmsgevent command syntax is shown (for multiple subsystems).
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschmsgevent command syntax is shown (for multiple subsystems).
[User Response]
Specify command parameters in the correct format.
[Description]
The number of job nets registered for a single project has exceeded the limit (255 job nets). Addition of any more job net is not recommended.
[User Response]
If you need to register job nets above the limit in a single project, use Systemwalker Operation Manager EE. However, if the project has unnecessary job nets, delete them so that the job net count does not exceed the limit. If you have no job nets that you can delete, try to add job nets to another project.
[Description]
The correct jobschpoconvert command syntax is shown.
[System Administrator Response]
Specify the command in the correct format.
[Description]
The correct jobschpoconvert command syntax is shown (for multiple subsystems).
[System Administrator Response]
Specify command parameters in the correct format.
[Description]
The number of job nets registered for a single project has exceeded the preset value.
[User Response]
The number of job nets for a single project has exceeded the limit that has been set by the Systemwalker Operation Manager environment setup client. If the project has unnecessary job nets, delete them so that the job net count does not exceed the limit.
If you have no job nets that you can delete, try to add job nets to another project or review the preset limit on the Systemwalker Operation Manager environment setup client.
[Description]
A user outside of swadmin group has executed a Jobscheduler command although Jobscheduler command execution and demand job startup are restricted for users who do not belong to the swadmin group.
[User Response]
Log in as the user belonging to the swadmin group and execute the Jobscheduler commands, or contact the system administrator to check if the command execution user belongs to the swadmin group or not. If not, the system administrator should add the user to the swadmin group.
[Description]
The specified confirmation or startup is not executed because the job net is a child job net.
[System Action]
Aborts processing.
[Description]
No group can be registered under the current startup conditions.
The following reasons are assumed:
The group cannot be registered or changed because the single startup was not specified for the job net in the group.
The job net cannot be changed because the execution condition of the child job net or linked job net is other than "None".
The specified change cannot be made for the job net with the execution condition "None" specified.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
Change the job net startup conditions, or recheck the contents to be registered/changed.
[Description]
Because job net xxxx does not exist, it is not registered as a child job net.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
Create job net xxxx
[Description]
Because job net xxxx does not exist, it is not registered as the parent job net.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
Create job net xxxx.
[Description]
Job net xxxx is not registered because it does not satisfy the child job net startup conditions.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
Change the job net startup conditions to "none."
[Description]
Job net xxxx cannot be registered as a child job net because it already belongs to another parent job net.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
Remove job net xxxx from the parent job net.
[Description]
No job nets can be registered because the job net hierarchy has exceeded level 5.
[System Action]
Aborts processing.
[User Response]
Reduce the job net hierarchy to level 5 or below.
[Description]
No job nets can be registered because the job net hierarchy is looped.
[System Action]
Aborts processing.
[User Response]
Set the job nets in hierarchies without loop.
[Description]
Job net xxxx cannot be registered as the parent job net because it does not have job execution control attributes.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
Set job net xxxx to have job execution control attributes.
[Description]
Job net xxxx cannot be registered as a child job net because it does not have job execution control attributes.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
Set job net xxxx to have job execution control attributes.
[Description]
The startup days or operation schedule information is not output because the job net having such information does not exist.
[System Action]
Aborts processing.
[Description]
The parameter information file of the job could not be written.
[System Action]
Aborts processing.
[User Response]
Copy the parameter information file of the job from the jobschbackup directory to the database directory, and restart the Jobscheduler.
[Description]
The parent job net cannot be copied.
[System Action]
Aborts processing.
[Description]
The specified operation was not executed because the job net was not terminated abnormally or not terminated forcibly.
[System Action]
Aborts processing.
[Description]
The specified operation was not executed because the group was not terminated abnormally or not terminated forcibly.
[System Action]
Aborts processing.
[Description]
The end point information has an error.
[System Action]
Aborts processing.
[User Response]
Restore the end point information file from the jobschbackup directory.
[System Administrator Response]
Copy the "jobschchecklog.ini" file from the jobschbackup directory of Jobscheduler database directories.
[Description]
The end point information could not be read.
[System Action]
Aborts processing.
[User Response]
Restore the end point information file from the jobschbackup directory.
[System Administrator Response]
Copy the "jobschchecklog.ini" file from the jobschbackup directory of Jobscheduler database directories.
[Description]
The end point information could not be written.
[System Action]
Aborts processing.
[User Response]
Copy the "jobschchecklog.ini" file from the jobschbackup directory of Jobscheduler database directories.
[Description]
File xxxx is not processed because it is not a text file.
[Parameter]
xxxx: File name
[System Action]
Aborts processing.
[User Response]
Specify a text file only.
[Description]
The specified regular expression in the "-e" option of the jobschchecklog command or the jobschnetmemo command has a syntax error.
[System Action]
Aborts processing.
[User Response]
Check the command option for a syntax error.
[Description]
The latest rendezvous (or waiting) time you specified is earlier than the rendezvous time.
[System Action]
Aborts processing.
[User Response]
Specify the latest rendezvous time that is later than the rendezvous time.
[Description]
File xxxx could not be read.
[Parameter]
xxxx: File name
[System Action]
Aborts processing.
[User Response]
Remove the error cause by referring to the previous message.
[Description]
File xxxx could not be written.
[Parameter]
xxxx: File name
[System Action]
Aborts processing.
[User Response]
Remove the error cause by referring to the previous message.
[Description]
The temporary file to be used by the jobschchecklog command could not be read.
[System Action]
Aborts processing.
[User Response]
Remove the error cause by referring to the previous message.
[Description]
The temporary file to be used by the jobschchecklog command could not be written.
[System Action]
Aborts processing.
[User Response]
Remove the error cause by referring to the previous message.
[Description]
The correct jobschchecklog command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschchecklog command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschchecktime command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschchecktime command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The user privilege information could not be obtained.
[Parameter]
xxxx: Code
[System Action]
Aborts processing.
[System Administrator Response]
Make sure that the command execution user has been registered on this server.
[Description]
File xxxx could not be found.
[Parameter]
xxxx: File name
[System Action]
Aborts processing.
[System Administrator Response]
Make sure that the file exists.
[Description]
The job net cannot be revoked because it is not carried over.
[System Action]
Aborts processing.
[Description]
The job net cannot be reinstated because it is not set to "start only when message event has occurred" or "start once in a day."
[System Action]
Aborts processing.
[Description]
The job net cannot be reinstated because it is not executed today.
[System Action]
Aborts processing.
[Description]
The job net cannot be reinstated because it is paused or disabled.
[System Action]
Aborts processing.
[Description]
The correct jobschnetmemo command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschnetmemo command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The character string of the memo is too long.
[System Action]
Aborts processing.
[Description]
The character string of the memo contains an incorrect character or characters.
[System Action]
Aborts processing.
[Description]
The correct jobschctljob command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschctljob command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The specified job is not executed because the job net to which this job belongs does not have the job execution control attributes.
[System Action]
Aborts processing.
[Description]
The specified job does not exist.
[System Action]
Aborts processing.
[Description]
Multiple jobs having the specified job name exist.
[System Action]
Aborts processing.
[Description]
The job cannot be operated because it is being controlled.
[System Action]
Aborts processing.
[Description]
The specified operation is not available because the job is not being executed nor delayed.
[System Action]
Aborts processing.
[Description]
The job is not restarted because the job net to which this job belongs is not being executed or not in the warning status.
[System Action]
Aborts processing.
[Description]
The specified job cannot be reactivated because the job net is in neither the abnormal termination status nor the forced termination status.
[System Action]
Aborts processing.
[Description]
The specified operation is not executed because the job is being executed or delayed.
[System Action]
Aborts processing.
[Description]
The specified operation is not executed because the job is not paused.
[System Action]
Aborts processing.
[Description]
The specified operation is not executed because the job is already paused.
[System Action]
Aborts processing.
[Description]
The specified operation is not executed because the job is not disabled.
[System Action]
Aborts processing.
[Description]
The specified operation is not executed because the job is already being disabled.
[System Action]
Aborts the process.
[Description]
The year exceeding the limit was specified.
[System Action]
Aborts processing.
[Description]
The specified operation is not executed because the recovery job is being executed or in the warning status.
[System Action]
Aborts processing.
[Description]
No access privileges could be obtained.
[System Action]
Aborts processing.
[User Response]
If it is output during command execution, re-execute the command.
[System Administrator Response]
If it is output during command execution, re-execute the command.
If the problem persists, restart the job scheduler.
If that does not work, collect "Jobscheduler" information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.
[Description]
An attempt was made to register a batch framework job using a command while the system cannot use the Interstage Job Workload Server.
[System Action]
The job net cannot be registered.
[User Response]
Modify the icon type in the definition file to the correct value. Note that the support is not available if the Interstage Job Workload Server is not installed.
[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 message event occurrences so that the next copy/startup process does not occur until after the previous job net that was copied and started has finished executing.
Perform a confirmation operation on the previous 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]
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 message event 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 message event
[System Action]
Continues the process. However, the variable parameters will be disabled.
[Corrective Measures]
Use a job net with Job Execution Control attributes as the job net receiving the variable parameters.
Use a job net that waits for a single message event or only one of several message events as the job net receiving the variable parameters.
[Description]
A message event where variable parameters have been specified has been ignored by the job net receiving it. 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 message event
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]
The specified operation cannot be performed on job nets that have been copied and started.
[System Action]
Stops processing.
[Corrective Measures]
For some operations such as coping a job net, an equivalent operation can be performed by specifying the source job net. In such cases, perform the operation by specifying the source job net.
[Description]
Reading 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 (by checking whether the root user has write permissions, for example).
[Description]
The specified job net failed to start because it is a job net that cannot be started using variable parameters.
Job nets with the following execution attributes cannot be started using variable parameters:
Job nets with the Interstage attribute
Job nets with the PowerAIM attribute
Job nets with the Normal attribute
[System Action]
Stops processing.
[Description]
The length of the regular expression is longer than 256 bytes.
[System Action]
Aborts the process.
[User Response]
Set the regular expression in no more than 256 characters long.
[Description]
Job nets having the memo containing regular expressions registered cannot be found.
[System Action]
Aborts the process.
[User Response]
Review the regular expression.
[Description]
It is not possible to perform the specified operation because the job net is a linked job net.
[System Action]
Aborts the process.
[Description]
It is not possible to perform the specified operation because the job net is a master linked job net.
[System Action]
Aborts the process.
[Description]
The specified job cannot be operated because it belongs to the job net that is a master linked job net or that is under the layer of this master linked job.
[System Action]
Aborts the process.
[Description]
The master linked job net XXXX does not exist.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Create the job net XXXX.
[Description]
The job net XXXX cannot be registered because the execution conditions of this job net do not meet the requirements of a master linked job net.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Change the execution condition of the job net to "None".
[Description]
The job net XXXX cannot be registered as a linked job net because it does not have the Job Execution Control attribute.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Change the attribute of the job net XXXX to the Job Execution Control attribute.
[Description]
It is not possible to register the child job net as a linked job net when it is also the child job net of other job nets.
The job net that has been copied using "copy and startup" cannot be registered as a linked job net.
It is not possible to register a linked job net by specifying it in the master linked job net if it is the job net that is already registered as the linked job net.
It is not possible to register the job net as a linked job net if it contains linked job nets as jobs.
A linked job net cannot be registered in the schedule by dates project.
[System Action]
Aborts the process.
[User Response]
Correct the definition file.
[Description]
It is not possible to register the job net XXXX as a linked job net because the job net with the same name as the job net XXXX already exists.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Change the job net name of the linked job net to another unique name, and then register it.
[Description]
It is not possible to register the job net XXXX as a linked job net because the job net with the same name as the job net XXXX already exists.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Change the job net name of the linked job net to another unique name, and then register it.
[Description]
The linked job net XXXX cannot be registered because the length of the job net name of the linked job net has exceeded the 50-byte limit.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Change the job net name of the linked job net to a name no longer than 50 bytes, and then register it.
[Description]
The linked job net cannot be copied.
[System Action]
Aborts the process.
[Description]
It is not possible to perform the specified operation because the linked job net or its parent job net is currently being executed or in a warning state.
[System Action]
Aborts the process.
[User Response]
Wait for the linked job net status to change, and try again.
[Description]
Linked job nets that refer to the same master linked job can be registered only up to 100.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[Description]
It is not possible to register the job net XXXX as a child job net because it is the master linked job net.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Register the job net XXXX as a linked job net.
[Description]
It is not possible to perform the specified operation because the linked job net or its parent or child job net is currently being saved or controlled.
[System Action]
Aborts the process.
[User Response]
Wait a short time and try again.
[Description]
It is not possible to perform the specified operation because the master linked job net is currently being executed or in a warning state.
[System Action]
Aborts the process.
[User Response]
Wait for the master linked job net status to change, and try again.
[Description]
It is not possible to perform the specified operation because the master linked job net or its child job net is currently being saved or controlled.
[System Action]
Aborts the process.
[User Response]
Wait a short time and try again.
[Description]
The linked job net cannot be registered because the job net name XXXX is duplicated between the newly registered linked job net and the job nets under that layer.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Change the job net name of the linked job net to another unique name, and then register it.
[Description]
It is not possible to register the job net XXXX as a child job net because linked job nets exist below the level of the job net XXXX.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Delete the linked job nets below the level of the job net XXXX, and then register it.
[Description]
The correct jobschchknetvar command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschsleep command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct parameter format for the jobschoperate command.
[User Response]
Specify the parameter in the correct format.
[Description]
The correct parameter format for the jobschoperate command.
[User Response]
Specify the parameter in the correct format.
[Description]
When executing a stop operation with jobschoperate, some job nets and groups could not be stopped due to the status of Executing/Warning/End delayed/Disabled.
[User Response]
Make sure that the status of the job nets and groups in the project is correct, and then try the operation again.
[Description]
When executing a disabled operation with jobschoperate, some job nets and groups could not be stopped due to the status of Executing/Warning/End delayed.
[User Response]
Make sure that the status of the job nets and groups in the project is correct, and then try the operation again.
[Description]
When executing a stop operation with jobschoperate, some job nets and groups could not be stopped because it is being saved or controlled.
[User Response]
Wait a while and try again.
[Description]
When executing a continued operation with jobschoperate, some job nets and groups could not be continued because it is being saved or controlled.
[User Response]
Wait a while and try again.
[Description]
When executing a disabled operation with jobschoperate, some job nets and groups could not be disabled because it is being saved or controlled.
[User Response]
Wait a while and try again.
[Description]
When executing an enabled operation with jobschoperate, some job nets and groups could not be enabled because it is being saved or controlled.
[User Response]
Wait a while and try again.
[Description]
The job net XXXX cannot be registered as a child job net, because the copy and startup setting is enabled.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
Disable the copy and startup setting in job net XXXX.
[Description]
The job net XXXX cannot be registered as a linked job net, because the copy and startup setting is enabled.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
Disable the copy and startup setting in job net XXXX.
[Description]
The job net XXXX cannot be registered to a group, because the copy and startup setting is enabled.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
Disable the copy and startup setting in job net XXXX.
[Description]
A job net with name of 35 bytes or longer or with comment of 85 bytes or longer cannot be registered as a child job net if copy and startup is set for the parent job net.
[System Action]
Aborts processing.
[User Response]
Ensure that the child job net you attempted to register and the job nets within it do not have job net name or job net comment that exceed the maximum length.
[Description]
A job net with name of 35 bytes or longer or with comment of 85 bytes or longer cannot be registered as a linked job net if copy and startup is set for the parent job net.
[System Action]
Aborts processing.
[User Response]
Ensure that the linked job net you attempted to register and the job nets within it do not have job net name or job net comment that exceed the maximum length.
[Description]
When copying a job net for which the copy and startup setting is enabled, you cannot specify a copy destination job net name of 35 bytes or more.
[System Action]
Aborts processing.
[User Response]
Ensure that the copy destination job net name that does not exceed the maximum length.
[Description]
The command was not executed as a local job of the Jobscheduler.
[System Action]
Aborts processing.
[User Response]
Register the command in a Jobscheduler job and execute it. If the command was executed as a network job or distributed execution job, change the settings so that the job is executed as a local job.
[Description]
The correct jobschchkmsgevt command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
Reading of the message event occurrence history file failed.
[User Response]
Refer to the message displayed before this message and remove the cause of the error.
[Description]
The job net XXXX cannot have a comment of 85 bytes or more, because the copy and startup setting is enabled.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
Ensure that the new job net comment does not exceed the maximum length.
[Description]
"Wait for preceding job using OR condition" was set for the succeeding job and the current job was canceled by the OR condition. Therefore, the current job cannot be restarted.
[User Response]
Execute the operation after the job net has changed to another status.
[Description]
The correct jobschinit command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschinit command syntax is shown (for multiple subsystems).
[User Response]
Specify command parameters in the correct format.
[Description]
Failed to delete the subsystem.
[Parameter]
XXXX: Subsystem number
YYYY: Return value from the stemSchDelete command
[User Response]
Identify the cause by referring to the return value from the stemSchDelete command, take an appropriate corrective action, and execute the command again.
Return value | Meaning | Action |
|---|---|---|
0 | Completed | - |
1 | Usage display | Confirm how to specify the option. |
2 | The user has no privileges for executing this command. | System administrator (superuser) privileges are required. |
3 | A system error occurred. | Check the system environment. |
4 | Execution unavailable because of the differences in the code systems. | The code system used for Systemwalker Operation Manager is not identical with that for the command execution environment. Use the same code system as that for Systemwalker Operation Manager. |
5 | DB access failed | Failed on opening, or reading from or writing to DB. Confirm the following:
|
6 | The Jobscheduler daemon is not running, or it is during startup processing. | Activate the daemon. If the daemon is already activated, it is during startup processing or it is not running properly. Wait a few moments, or reactivate it. |
7 | The specified project is not found. | Confirm whether the specified project name is correct. |
8 | The project cannot be deleted because a group or job net is currently executing. | After the currently executing group or job net terminates, execute the command again. |
11 | This command has failed in reading ACL manager library. | Confirm whether the following file exists. If the file is found, it may be damaged. Re-install the file. /opt/systemwalker/lib/libmpfwsecjm.so |
12 | The project cannot be deleted because a carried over job net exists. | After addressing the problem by, for example, disabling the carried over job net, execute the command again. |
13 | The project cannot be deleted because a group or job net is currently operating or being stored. | After the currently operating or stored group or job net terminates, execute the command again. |
14 | Timeout | Confirm the load of Systemwalker Operation Manager, then execute the command again. |
15 | Unable to delete because a shutdown job net (JSHEND or JSHFORCE) has executed. | Restart the Jobscheduler, then execute the command gain. |
[Description]
The correct parameter format for the jobschrestexec command.
[User Response]
Specify the parameter in the correct format.
[Description]
The path length of the specified connection information file is too long.
[System Action]
Aborts processing.
[User Response]
Reconsider the path of the connection information file.
[Description]
The connection information file is not in JSON format.
[System Action]
Aborts processing.
[User Response]
Make sure that the connection information file is in JSON format.
[Description]
A required parameter is not specified in the connection information file.
[Parameter]
XXXX: Key name of a required parameter that is not specified
[System Action]
Aborts processing.
[User Response]
Make sure that the required parameters are set in the connection information file.
[Description]
An unnecessary parameter is specified in the connection information file.
[Parameter]
XXXX: Key name of the specified unnecessary parameter
[System Action]
Aborts processing.
[User Response]
Check whether unnecessary parameters have been set in the connection information file.
[Description]
A parameter value in the connection information file is invalid.
[Parameter]
XXXX: Key name of the parameter whose value is invalid
[System Action]
Aborts processing.
[User Response]
Make sure that the parameter values in the connection information file are specified correctly.
[Description]
The connection information file could not be read because open or read failed.
[Parameter]
XXXX: File name that failed to read
[System Action]
Aborts processing.
[User Response]
Check if the XXXX file is accessible.
[Description]
The HTTP response header or body could not be written because it failed to open or write the destination file.
[Parameter]
XXXX: Output destination file name that failed to write
[System Action]
Aborts processing.
[User Response]
Make sure that there is not enough free space.
Make sure that the destination directory for the HTTP response header or body exists.
Check the permissions/permissions of the destination directory in the HTTP response header or body.
[Description]
The HTTP request ended with a status code other than 200.
[Parameter]
XXXX: Type of failed HTTP request (request/ monitoring/ termination/ authentication)
YYYY: HTTP status code
[System Action]
Aborts processing.
[System Administrator Response]
If the type of HTTP request that failed (XXXX) is request/ monitoring/ termination
Make sure that the HTTP request information defined in the connection information file is correct.
If you specified credentials, make sure that the registered credentials are correct.
If the type of HTTP request that failed (XXXX) is authentication
Make sure that the credentials configured for the AzureAD/SAP cloud service are correct.
[Description]
The HTTP request failed due to a network connection problem.
[Parameter]
XXXX: Type of failed HTTP request (request /monitoring/ termination/ authentication)
[System Action]
Aborts processing.
[System Administrator Response]
If you have configured a proxy authentication name in the credentials file, make sure that the registered proxy credentials are correct.
Check for other network problems such as DNS settings.
[Description]
The HTTP request failed because it timed out.
[Parameter]
XXXX: Type of failed HTTP request (request/ monitoring/ termination/ authentication)
[System Action]
Aborts processing.
[System Administrator Response]
Rereview the connection timeout period set in the connection information file.
If not, make sure that the HTTP request information in the connection information file or the AzureAD/SAP cloud service credentials in the credentials are correct.
[Description]
The HTTP request failed due to a problem.
[Parameter]
XXXX: Type of failed HTTP request (request/ monitoring/ termination/ authentication)
[System Action]
Aborts processing.
[System Administrator Response]
Make sure that the HTTP request information set in the connection information file is correct.
If a credential name is set in the connection information file, check whether the registered credentials are correct.
If the problem is not resolved, collect "Jobscheduler" information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.
[Description]
A job on the cloud service timed out waiting for completion.
[System Action]
Aborts processing.
[System Administrator Response]
Adjust the monitoring polling interval and number of polling intervals set in the connection information file according to the processing volume of jobs executed on the cloud service.
[Description]
The execution result of the job on the cloud service is not the specified normal end value.
[Parameter]
XXXX: Execution result of the job on the cloud service
[System Action]
Aborts processing.
[System Administrator Response]
Check whether the job you submitted on the cloud service terminated normally, and then take the following actions.
If the command terminated normally, check whether the normal termination judgment key and value in the connection information file are set correctly.
If the job did not end normally, check and, if necessary, revise the job on the cloud service.
[Description]
The key to be inherited for monitoring and forced termination specified in connection information, key to be set for the job net variable, monitoring end judgment key, and normal end judgment key could not be found in the response result.
[Parameter]
XXXX:
Key to be inherited for monitoring and forced termination /Key to be set for the job net variable:
Substitution variable name
Monitoring end judgment key /Normal end judgment key:
Key name (pollingEndKey/ checkResultKey)
[System Action]
Aborts processing.
[System Administrator Response]
Make sure that the key to be inherited for monitoring and forced termination specified in connection information, key to be set for the job net variable, monitoring end judgment key, and normal end judgment key is set correctly.
If you are outputting the HTTP response body to a file, make sure that the key to extract exists in the HTTP response body.
[Description]
Failed to obtain authentication information during processing.
[Parameter]
XXXX: Authentication information name
[System Action]
Aborts processing.
[System Administrator Response]
Make sure that the authentication information of the authentication information name set in the connection information file is registered.
If so, check that the authentication information is correct.
[Description]
An access token is not found in the response result.
[System Action]
Aborts processing.
[System Administrator Response]
Make sure that the credentials for the AzureAD/SAP cloud service authentication configured in the credentials are correct.
[Description]
An internal logical error occurred during processing.
[System Action]
Aborts processing.
[System Administrator Response]
Collect "Jobscheduler" information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.
[Description]
The correct parameter format for the jobschsetauthinfo command.
[System Administrator Response]
Specify the parameter in the correct format.
[Description]
The correct parameter format for the jobschsetauthinfo command.
[System Administrator Response]
Specify the parameter in the correct format.
[Description]
Could not read because one of the open, lockf, or read authentication information failed.
[System Action]
Aborts processing.
[System Administrator Response]
Restore the authentication information (restauth.inf) from the jobschbackup directory under the database directory. For the restoration method, refer to the "Restoring Schedule Files" in the "Systemwalker Operation Manager Operation Guide", and restore the schedule information in the same way.
[Description]
An invalid format record was detected while reading authentication information.
[System Action]
Aborts processing.
[System Administrator Response]
Restore the authentication information (restauth.inf) from the jobschbackup directory under the database directory. For the restoration method, refer to the "Restoring Schedule Files" in the "Systemwalker Operation Manager Operation Guide", and restore the schedule information in the same way.
[Description]
The authentication information could not be written.
[System Action]
Aborts processing.
[System Administrator Response]
Restore the authentication information (restauth.inf) from the jobschbackup directory under the database directory. For the restoration method, refer to the "Restoring Schedule Files" in the "Systemwalker Operation Manager Operation Guide", and restore the schedule information in the same way.
[Description]
The format of the authentication information control statement is invalid.
[System Action]
Aborts processing.
[System Administrator Response]
Correct the authentication information control statement.
[Description]
The YYYY parameter that cannot be specified in the authentication information control statement is specified.
[Parameter]
XXXX: Authentication information name (Empty character if YYYY is name)
YYYY: Parameter name
[System Action]
Aborts processing.
[System Administrator Response]
Correct the authentication information control statement.
[Description]
The YYYY parameter in the authentication information control statement is invalid.
[Parameter]
XXXX: Authentication information name
YYYY: Parameter name
[System Action]
Aborts processing.
[System Administrator Response]
Correct the authentication information control statement.
[Description]
A parameter YYYY that cannot be specified in the authentication information control statement is specified.
[Parameter]
XXXX: Authentication information name
YYYY: Parameter name
[System Action]
Aborts processing.
[System Administrator Response]
Correct the authentication information control statement.
[Description]
The specified credentials cannot be found.
[System Action]
Aborts processing.
[System Administrator Response]
Specify the correct authentication information, and then retry the operation.
[Description]
An internal error occurred.
[System Action]
Aborts processing.
[System Administrator Response]
Collect "Jobscheduler" information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.
[Description]
The correct jobschprint command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschcontrol command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct "createsubsystem.exe" command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct "deletesubsystem.exe" command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschsetcal command syntax is shown.
[System Administrator Response]
Specify command parameters in the correct format.
[Description]
The correct jobschsethol command syntax is shown.
[System Administrator Response]
Specify command parameters in the correct format.
[Description]
The correct jobschsetnet command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschmsgclear command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschctlgrp command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschsetgrp command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschmove command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschcod command syntax is shown.
[System Administrator Response]
Specify command parameters in the correct format.
[Description]
The correct jobschconvert command syntax is shown.
[System Administrator Response]
Specify command parameters in the correct format.
[Description]
The correct jobschmsgevent command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschmsgevent command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschcancelnet command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
No job net is queued for the job net startup API.
[Description]
The correct jshtrace command syntax is shown.
[System Administrator Response]
Specify command parameters in the correct format.
[Description]
The correct chkfile command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschsetproject command syntax is shown
[System Administrator Response]
Specify command parameters in the correct format
[Description]
The correct jobschpoconvert command syntax is shown.
[System Administrator Response]
Specify the command in the correct format.
[Description]
The correct jobschprint command syntax is shown.
[System Administrator Response]
Specify command parameters in the correct format.
[Description]
The correct jobschcontrol command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschsetcal command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschsetnet command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschmsgclear command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschctlgrp command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschsetgrp command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschmove command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschconvert command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschpoconvert command syntax is shown
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschmsgevent command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschcancelnet command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschchecklog command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschchecktime command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschchecktime command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschnetmemo command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschnetmemo command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschctljob command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschctljob command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschchknetvar command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschsleep command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschoperate command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschoperate command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschchkmsgevt command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschinit command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct jobschinit command syntax is shown (for multiple subsystems).
[User Response]
Specify command parameters in the correct format.
[Description]
The correct parameter format for the jobschrestexe command.
[User Response]
Specify the parameter in the correct format.
[Description]
The correct parameter format for the jobschsetauthinfo command.
[System Administrator Response]
Specify the parameter in the correct format.
[Description]
The correct parameter format for the jobschsetauthinfo command.
[System Administrator Response]
Specify the parameter in the correct format.
[Description]
Command xxxx of the Jobscheduler has terminated normally.
[Parameter]
XXXX: Command name
[Description]
The jobschmsgevent command specifying the host name has terminated normally
[Parameter]
XXXX: Host name
[Description]
No job net information was found during jobschprint command execution.
[System Action]
Aborts processing.
[Description]
The schedule pattern data, specified by the Jobscheduler command parameter, does not exist in the schedule pattern file (db_calendar_ex.default).
[System Action]
Aborts processing.
[User Response]
Check the Jobscheduler command parameters for an error.
[Description]
The currently executing job that is output by the jobschprint command does not exist.
[System Action]
Aborts processing.
[Description]
The user authorized to access to the display that is output by the jobschprint command does not exist.
[System Action]
Aborts processing.
[Description]
There is no queued job that is output by the jobschprint command.
[System Action]
Aborts processing.
[Description]
There is no history information that is output by the jobschprint command.
[System Action]
Aborts processing.
[Description]
The group to be processed does not exist.
[System Action]
Aborts processing.
[User Response]
Review the group name.
[Description]
No Jobscheduler functions can be used because a project having the available access privileges does not exist.
[System Action]
Aborts processing.
[User Response]
Ask the project owner or system administrator for setup of access privileges.
[System Administrator Response]
Register a project available to the user. Or, set the access privileges to the project to allow its access by the user.
[Description]
There is no calendar information that is displayed by the jobschprint command.
[System Action]
Aborts processing.
[User Response]
Check the Jobscheduler command parameters for an error.
[Description]
No more projects can be registered because the number of projects registered in the Jobscheduler has exceeded the limit (1000 projects).
[System Action]
Aborts processing.
[System Administrator Response]
Delete unnecessary projects.
[Description]
Job nets having the memo containing regular expressions registered cannot be found.
[System Action]
Aborts the process.
[User Response]
Review the regular expression.
[Description]
When executing a stop operation with jobschoperate, some job nets and groups could not be stopped due to the status of Executing/Warning/End delayed/Disabled.
[User Response]
Make sure that the status of the job nets and groups in the project is correct, and then try the operation again.
[Description]
When executing a disabled operation with jobschoperate, some job nets and groups could not be stopped due to the status of Executing/Warning/End delayed.
[User Response]
Make sure that the status of the job nets and groups in the project is correct, and then try the operation again.
[Description]
When executing a stop operation with jobschoperate, some job nets and groups could not be stopped because it is being saved or controlled.
[User Response]
Wait a while and try again.
[Description]
When executing a continued operation with jobschoperate, some job nets and groups could not be continued because it is being saved or controlled.
[User Response]
Wait a while and try again.
[Description]
When executing a disabled operation with jobschoperate, some job nets and groups could not be disabled because it is being saved or controlled.
[User Response]
Wait a while and try again.
[Description]
When executing an enabled operation with jobschoperate, some job nets and groups could not be enabled because it is being saved or controlled.
[User Response]
Wait a while and try again.
[Description]
When existing database files were converted into new database files, a database file disabled to convert was found.
[Parameter]
xxxx: File name. It can be one of the followings.
user_name
user_name.grp
project_name.jsp
project_name.dbx
project_name.grp
project_name.dbz
project_name.grz
sysfile.sys
monitor_hosts_ex
holiday_info.db
db_calendar.default
db_calendar_ex.default
sroot.var
[System Action]
Process continues, ignoring the conversion of xxxx database file.
[System Administrator Response]
Make sure that database xxxx has the version before being converted. If the conversion of the day change and holiday database (sysfile.sys) has failed, the startup of Jobscheduler may fail. In such case, copy the old database file from the "jobschbackup" directory to the new database directory, and re-execute the conversion.
[Description]
One of the phenomena below occurred during conversion of calendar information.
The calendar name already exists.
The calendar name contains illegal character codes that the calendar service (Systemwalker MpJmCal) cannot use.
[Parameter]
xxxx: Calendar name
[System Action]
Does not convert the calendar information.
[System Administrator Response]
Convert the calendar information separately if its conversion has failed.
[Description]
No project owner name was specified in the definition file.
[System Action]
Aborts processing.
[User Response]
Specify the project owner name in the definition file
[Description]
The job net information being held in the Jobscheduler command has an error.
[System Action]
Aborts processing.
[System Administrator Response]
If it is shown by the jobschsetnet command, collect the Jobscheduler information by using the Maintenance Information Collection Tool and contact Fujitsu technical support.
Otherwise, output this file from the jobschbackup directory to the database directory, and restart the Jobscheduler.
[Description]
The Jobscheduler command has an incorrect parameter.
[System Action]
Aborts processing.
[User Response]
Check the Jobscheduler command parameters for an error.
[Description]
Since the group is not scheduled to start today, it cannot be reactivated.
[System Action]
Aborts processing.
[System Administrator Response]
Start the group instead of group reactivation.
[Description]
An error occurred when the project information ("project_name.jsp" file) was written.
[System Action]
Aborts processing.
[System Administrator Response]
Remove the error cause by referring to the previous message.
[Description]
The specified operation is not executed because the job net is being executed or in the warning status.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the job net has changed to another status.
[Description]
The job net could not restart because it was not terminated abnormally, not terminated forcibly, or not confirmed.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the job net has changed to another status
[Description]
The specified operation is not executed because the job net is not being executed or not in the warning status.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the job net has changed to another status
[Description]
The definition file was not read because it could not be opened.
[System Action]
Aborts processing.
[User Response]
Make sure that the definition file exists and the user is authorized to read it.
[Description]
Processing of the Jobscheduler command was interrupted.
[System Action]
Aborts processing.
[User Response]
Remove the error cause by referring to the previous message.
[Description]
The schedule pattern information could not be written.
[System Action]
Aborts processing.
[System Administrator Response]
Remove the error cause by referring to the previous message.
[Description]
The schedule pattern data, specified by the Jobscheduler command parameter, does not exist in the schedule pattern file (db_calendar_ex.default).
[System Action]
Aborts processing.
[User Response]
Check the Jobscheduler command parameters for an error.
[Description]
The Jobscheduler command has an incorrect parameter.
[System Action]
Aborts processing.
[User Response]
Check the Jobscheduler command parameters for an error.
[Description]
A user who does not belong to the Administrators group has executed a command available only for users in the Administrators group.
[System Action]
Aborts processing.
[User Response]
Execute the command as the user belonging to the Administrators group.
[Description]
There is no log information (jobdb1.log, jobdb2.log, and jobdb3.log under the database directory). 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 while no job or job net is operating.
[Description]
The job net to be processed already exists.
[System Action]
Aborts processing.
[User Response]
Review the job net name.
[Description]
There is an error either in the list file being read by the jobschsetnet command or in the definition file.
[System Action]
Aborts processing.
[User Response]
Correct the list file or the definition file.
[Description]
The job net startup condition is not specified in the definition file that is read by the jobschsetnet command.
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
No process is specified if the startup date overlaps a holiday in the definition file that is read by the jobschsetnet command.
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
None of jobschsetnet, jobschsetgrp and jobschmove commands can be executed when the screen is being displayed.
[System Action]
Aborts processing.
[User Response]
Terminate the client (such as job scheduler/CL) first, then execute the jobschsetnet, jobschsetgrp or jobschmove command.
[Description]
A record having an invalid length was detected when the schedule pattern information (db_calendar_ex.default) was being read.
[System Action]
Aborts processing.
[System Administrator Response]
Copy the schedule pattern information (db_calendar_ex.default) from the jobschbackup directory to the database directory, and restart the Jobscheduler.
[Description]
The specified operation is not executed because the job net is being saved or controlled.
[System Action]
Aborts processing.
[User Response]
After a while, re-execute the process.
[Description]
The group to be processed already exists.
[System Action]
Aborts processing.
[User Response]
Review the group name.
[Description]
The group to be processed does not exist.
[System Action]
Aborts processing.
[User Response]
Review the group name.
[Description]
The specified operation is not executed because the job net belongs to the group.
[System Action]
Aborts processing.
[User Response]
Remove the job net from the group.
[Description]
The specified operation is not executed because the job net does not belong to the group.
[System Action]
Aborts processing.
[User Response]
Review the operation.
[Description]
The specified operation is not executed because the job net is not paused.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the job net has changed to another status
[Description]
The specified operation is not executed because the job net is already paused.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the job net has changed to another status.
[Description]
The specified operation is not executed because the job net is not disabled.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the job net has changed to another status.
[Description]
The specified operation is not executed because the job net is already disabled.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the job net has changed to another status.
[Description]
The specified operation is not executed because the group is already being executed or in the warning status.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group has changed to another status.
[Description]
The group could not restart because it was not terminated abnormally, not terminated forcibly, or not confirmed.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group has changed to another status.
[Description]
The specified operation is not executed because the group is not being executed or not in the warning status.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group has changed to another status.
[Description]
The specified operation could not be executed because the group was not terminated abnormally.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group has changed to another status.
[Description]
The specified job was not defined in the definition file that was read by the jobschsetnet command.
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
The group cannot be moved because the group specified by the Jobschmove command is the same as the destination group.
[System Action]
Aborts processing.
[User Response]
Check the jobschmove command parameters for an error.
[Description]
The job net cannot be moved because the group specified by the Jobschmove command contains the destination job net.
[System Action]
Aborts processing.
[User Response]
Check the jobschmove command parameters for an error.
[Description]
The job net cannot be moved because the job net specified by the Jobschmove command is the same as the destination job net.
[System Action]
Aborts processing.
[User Response]
Check the jobschmove command parameters for an error.
[Description]
The job net was not found in the definition file that was read by the jobschsetgrp command.
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
The specified operation is not executed because the group to which the job net belongs is being saved or controlled.
[System Action]
Aborts processing.
[User Response]
After a while, re-execute the process.
[Description]
The specified operation is not executed because the group to which the job net belongs is already being executed or in the warning status.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group to which the job net belongs has changed to another status.
[Description]
The group information has an error.
[System Action]
Aborts processing.
[System Administrator Response]
Collect the Jobscheduler information by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
The group confirmation failed because the Validate group confirmation option was unchecked in the Advanced Settings for Verification window.
[System Action]
Aborts processing.
[System Administrator Response]
To use group confirmation, check the Validate group confirmation option in the Advanced Settings for Verification window, and restart the Jobscheduler.
[Description]
The process failed because no project name was specified.
[System Action]
Aborts processing.
[User Response]
Specify the project name.
[Description]
No database files can be converted when the service is active.
[System Action]
Aborts processing.
[System Administrator Response]
Stop the service before executing the command.
[Description]
The specified calendar name was not found.
[System Action]
Aborts processing.
[User Response]
Check the jobschsethol command parameters for an error.
[Description]
The specified operation could not be executed because the job net was not terminated abnormally.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the job net has changed to another status.
[Description]
The job net confirmation failed because the Validate job net confirmation option was unchecked in the Advanced Settings for Verification window.
[System Action]
Aborts processing.
[System Administrator Response]
To use job net confirmation, check the Validate job net confirmation option in the Advanced Settings for Verification window, and restart the Jobscheduler.
[Description]
The specified operation is not executed because the group is already paused.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group has changed to another status.
[Description]
The specified operation is not executed because the group is already disabled.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group has changed to another status.
[Description]
The specified operation is not executed because the group is not paused.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group has changed to another status.
[Description]
The specified operation is not executed because the group is not disabled.
[System Action]
Aborts processing.
[User Response]
Execute the operation after the group has changed to another status.
[Description]
Communication process with the Systemwalker MpJmCal service has failed.
[System Action]
Aborts processing.
[System Administrator Response]
Check the Operation Manager client if its calendar function is available or not.
[Description]
The Jobscheduler command cannot be executed because the Jobscheduler service is inactive.
[System Action]
Aborts processing.
[System Administrator Response]
Start the Jobscheduler service, then re-execute the command.
[Description]
No message event could be generated because a message event name exceeding 114 bytes long was specified and its jobschmsgevent command was executed.
[System Action]
Aborts processing.
[User Response]
Execute the jobschmsgevent command by specifying up to 114 bytes of message event name, including project name and job net name.
[Description]
Interprocess communication between the Jobscheduler command and Jobscheduler service has failed.
[System Action]
Aborts processing.
[System Administrator Response]
Collect the Jobscheduler information by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
The request was rejected because the Jobscheduler service was being started.
[System Action]
Aborts processing.
[User Response]
After a while, re-enter the Jobscheduler command.
[Description]
The specified jot net is not queued for the job net startup API.
[System Action]
Aborts processing.
[Description]
The Jobscheduler command was rejected because the termination process job net (JSHEND or JSHFORCE) was started.
[System Action]
Aborts processing.
[Description]
The file name specified by the jobschmsgevent command parameter was not found.
[System Action]
Aborts processing.
[User Response]
Check the file name and re-execute the jobschmsgevent command.
[Description]
The directory specified does not exist.
[System Action]
Aborts processing.
[System Administrator Response]
Specify an existing directory.
[Description]
The job net startup API function has been disabled by the startup parameter of Jobscheduler service.
[System Action]
Aborts processing.
[System Administrator Response]
To use the job net startup API function, set the startup parameter of Jobscheduler service again by using the jobschsetparm command, and restart the Jobscheduler service.
[Description]
No access control is available because the Systemwalker ACL Manager service is inactive.
[System Action]
Aborts processing.
[System Administrator Response]
Start the Systemwalker ACL Manager service.
[Description]
The specified project name was incorrect.
[System Action]
Aborts processing.
[User Response]
Specify the correct project name.
[Description]
The specified project is not deleted because the project contains the job net information.
[System Action]
Aborts processing.
[User Response]
Delete all job net information from the project.
[Description]
The specified user name is incorrect.
[System Action]
Aborts processing.
[User Response]
Specify the correct user name.
[Description]
The start date of temporary change has not been specified in the definition file.
[System Action]
Aborts processing.
[User Response]
Specify the start date of temporary change in the definition file.
[Description]
The system calendar is not allowed to delete.
[System Action]
Aborts processing.
[Description]
One of the following has occurred.
A job net having Interstage attributes was attempted to start in the system where the Interstage cannot be used.
Registration of a job net having Interstage attributes was attempted by the command in the system where the Interstage cannot be used.
[System Action]
Rejects job net execution if this message is output by the service. Cancels job net registration if this message is output by the command.
[System Administrator Response]
Make sure that the Interstage has been installed and it operates normally.
[Description]
A user outside of swadmin group has executed a Jobscheduler command although 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. option was checked.
[User Response]
Log in as the user belonging to the swadmin group and execute the Jobscheduler commands, or ask the system administrator for addition of command execution users to the swadmin group.
[Description]
The specified confirmation or startup is not executed because the job net is a child job net.
[System Action]
Aborts processing.
[Description]
No job nets can be registered because the job net hierarchy has exceeded level 5.
[System Action]
Aborts processing.
[User Response]
Reduce the job net hierarchy to level 5 or below.
[Description]
No job nets can be registered because the job net hierarchy is looped.
[System Action]
Aborts processing.
[User Response]
Set the job nets in hierarchies without loop.
[Description]
The startup days or operation schedule information is not output because the job net having such information does not exist.
[System Action]
Aborts processing.
[Description]
The parameter information file of the job could not be written.
[System Action]
Aborts processing.
[User Response]
Copy the parameter information file of the job from the jobschbackup directory to the database directory, and restart the Jobscheduler.
[Description]
The parent job net cannot be copied.
[System Action]
Aborts processing.
[Description]
The specified operation was not executed because the job net was not terminated abnormally or not terminated forcibly.
[System Action]
Aborts processing.
[Description]
The specified operation was not executed because the group was not terminated abnormally or not terminated forcibly.
[System Action]
Aborts processing.
[Description]
The end point information has an error.
[System Action]
Aborts processing.
[User Response]
Restore the end point information file from the jobschbackup directory.
[System Administrator Response]
Copy the "jobschchecklog.ini" file from the jobschbackup directory of Jobscheduler database directories.
[Description]
The end point information could not be read.
[System Action]
Aborts processing.
[User Response]
Restore the end point information file from the jobschbackup directory.
[System Administrator Response]
Copy the "jobschchecklog.ini" file from the jobschbackup directory of Jobscheduler database directories.
[Description]
The end point information could not be written.
[System Action]
Aborts processing.
[User Response]
Restore the end point information file from the jobschbackup directory.
[System Administrator Response]
Copy the "jobschchecklog.ini" file from the jobschbackup directory of Jobscheduler database directories.
[Description]
The entry in the "-e" option of the jobschchecklog or jobschchecklog command has a syntax error.
[System Action]
Aborts processing.
[User Response]
Check the command option for a syntax error
[Description]
The latest rendezvous (or waiting) time you specified is earlier than the rendezvous time.
[System Action]
Aborts processing.
[User Response]
Specify the latest rendezvous time that is later than the rendezvous time.
[Description]
The temporary file to be used by the jobschchecklog command could not be read.
[System Action]
Aborts processing.
[User Response]
Remove the error cause by referring to the previous message.
[Description]
The temporary file to be used by the jobschchecklog command could not be written.
[System Action]
Aborts processing.
[User Response]
Remove the error cause by referring to the previous message.
[Description]
The job net cannot be reinstated because it is not carried over.
[System Action]
Aborts processing.
[Description]
The job net cannot be reinstated because it is not set to "start only when message event has occurred" or "start once in a day."
[System Action]
Aborts processing.
[Description]
The job net cannot be reinstated because it is not executed today.
[System Action]
Aborts processing.
[Description]
The job net cannot be reinstated because it is paused or disabled.
[System Action]
Aborts processing.
[Description]
The character string of the memo is too long.
[System Action]
Aborts processing.
[User Response]
Specify the character string of the memo within 128 bytes long.
[Description]
The character string of the memo contains an incorrect character or characters.
[System Action]
Aborts processing.
[User Response]
Correct the character string of the memo.
[Description]
The specified job is not executed because the job net to which this job belongs does not have the job execution control attributes.
[System Action]
Aborts processing.
[Description]
The specified job does not exist.
[System Action]
Aborts processing.
[User Response]
Review the job name.
[Description]
Multiple jobs having the specified job name exist.
[System Action]
Aborts processing.
[User Response]
Rename the job to have a unique name in the system.
[Description]
The job cannot be operated because it is being controlled.
[System Action]
Aborts processing.
[User Response]
After a while, re-execute the process.
[Description]
The specified operation is not executed because the job is not being executed or delayed.
[System Action]
Aborts processing.
[Description]
The job is not restarted because the job net to which this job belongs is not being executed or not in the warning status.
[System Action]
Aborts processing.
[Description]
The job was not restarted because it was not terminated abnormally or not terminated forcibly.
[System Action]
Aborts processing.
[Description]
The specified operation is not executed because the job is being executed or delayed.
[System Action]
Aborts processing.
[Description]
The specified operation is not executed because the job is not paused.
[System Action]
Aborts processing.
[Description]
The specified operation is not executed because the job is already paused.
[System Action]
Aborts processing.
[Description]
The specified operation is not executed because the job is not disabled.
[System Action]
Aborts processing.
[Description]
The specified operation is not executed because the job is already disabled.
[System Action]
Aborts processing.
[Description]
The year exceeding the limit was specified.
[System Action]
Aborts processing.
[User Response]
Check the year specification.
[Description]
The specified operation is not executed because the recovery job is being executed or in the warning status.
[System Action]
Aborts processing.
[Description]
No access privileges could be obtained.
[System Action]
Aborts processing.
[System Administrator Response]
Collect the Jobscheduler information by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
The specified operation cannot be performed on job nets that have been copied and started.
[System Action]
Aborts processing.
[Corrective Measures]
Perform the operation by specifying the source job net.
[Description]
The specified job net failed to start because it is a job net that cannot be started using variable parameters.
Job nets with the following execution attributes cannot be started using variable parameters:
Job nets with the Interstage attribute
[System Action]
Aborts processing.
[Description]
The length of the regular expression is longer than 256 bytes.
[System Action]
Aborts the process.
[User Response]
Set the regular expression in no more than 256 characters long.
[Description]
It is not possible to perform the specified operation because the job net is a linked job net.
[System Action]
Aborts the process.
[Description]
It is not possible to perform the specified operation because the job net is a master linked job net.
[System Action]
Aborts the process.
[Description]
The specified job cannot be operated because it belongs to the job net that is a master linked job net or that is under the layer of this master linked job.
[System Action]
Aborts the process.
[Description]
It is not possible to register the child job net as a linked job net when it is also the child job net of other job nets.
The job net that has been copied using "copy and startup" cannot be registered as a linked job net.
It is not possible to register a linked job net by specifying it in the master linked job net if it is the job net that is already registered as the linked job net.
It is not possible to register a job net as a linked job net if the job net contains linked job nets as jobs.
A linked job net cannot be registered in the schedule by dates project.
[System Action]
Aborts the process.
[User Response]
Correct the definition file.
[Description]
The linked job net cannot be copied.
[System Action]
Aborts the process.
[Description]
It is not possible to perform the specified operation because the linked job net or its parent job net is currently being executed or in a warning state.
[System Action]
Aborts the process.
[User Response]
Wait for the linked job net status to change, and try again.
[Description]
It is not possible to perform the specified operation because the linked job net or its parent or child job net is currently being saved or controlled.
[System Action]
Aborts the process.
[User Response]
Wait a short time and try again.
[Description]
It is not possible to perform the specified operation because the master linked job net is currently being executed or in a warning state.
[System Action]
Aborts the process.
[User Response]
Wait for the master linked job net status to change, and try again.
[Description]
It is not possible to perform the specified operation because the master linked job net or its child job net is currently being saved or controlled.
[System Action]
Aborts the process.
[User Response]
Wait a short time and try again.
[Description]
A job net with name of 35 bytes or longer or with comment of 85 bytes or longer cannot be registered as a child job net if copy and startup is set for the parent job net.
[System Action]
Aborts processing.
[User Response]
Ensure that the child job net you attempted to register and the job nets within it do not have job net name or job net comment that exceed the maximum length.
[Description]
A job net with name of 35 bytes or longer or with comment of 85 bytes or longer cannot be registered as a linked job net if copy and startup is set for the parent job net.
[System Action]
Aborts processing.
[User Response]
Ensure that the linked job net you attempted to register and the job nets within it do not have job net name or job net comment that exceed the maximum length.
[Description]
When copying a job net for which the copy and startup setting is enabled, you cannot specify a copy destination job net name of 35 bytes or more.
[System Action]
Aborts processing.
[User Response]
Ensure that the copy destination job net name that does not exceed the maximum length.
[Description]
The command was not executed as a local job of the Jobscheduler.
[System Action]
Aborts processing.
[User Response]
Register the command in a Jobscheduler job and execute it. If the command was executed as a network job or distributed execution job, change the settings so that the job is executed as a local job.
[Description]
Reading of the message event occurrence history file failed.
[User Response]
Refer to the message displayed before this message and remove the cause of the error.
[Description]
When copying a job net for which the copy and startup setting is enabled, you cannot specify JSHEND or JSHFORCE as the copy destination job net name.
[System Action]
Aborts processing.
[User Response]
Specify a job net name other than JSHEND and JSHFORCE as the copy destination job net name.
[Description]
"Wait for preceding job using OR condition" was set for the succeeding job and the current job was canceled by the OR condition. Therefore, the current job cannot be restarted.
[User Response]
Execute the operation after the job net has changed to another status.
[Description]
The specified connection information file name is too long.
[System Action]
Aborts processing.
[User Response]
Reconsider the path of the connection information file.
[Description]
The connection information file is not in JSON format.
[System Action]
Aborts processing.
[User Response]
Make sure that the connection information file is in JSON format.
[Description]
A job on the cloud service timed out waiting for completion.
[System Action]
Aborts processing.
[System Administrator Response]
Adjust the monitoring polling interval and number of polling intervals set in the connection information file according to the processing volume of jobs executed on the cloud service.
[Description]
No access tokens were found in the response results.
[System Action]
Aborts processing.
[System Administrator Response]
Make sure that the credentials for the AzureAD/SAP cloud service authentication configured in the credentials are correct.
[Description]
An internal logical error occurred during processing.
[System Action]
Aborts processing.
[System Administrator Response]
Collect "Jobscheduler" information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.
[Description]
Could not read because one of the open, lockf, or read authentication information failed.
[System Action]
Aborts processing.
[System Administrator Response]
Restore the authentication information (restauth.inf) from the jobschbackup directory under the database directory. For the restoration method, refer to the "Restoring Schedule Files" in the "Systemwalker Operation Manager Operation Guide", and restore the schedule information in the same way.
[Description]
An invalid format record was detected while reading authentication information.
[System Action]
Aborts processing.
[System Administrator Response]
Restore the authentication information (restauth.inf) from the jobschbackup directory under the database directory. For the restoration method, refer to the "Restoring Schedule Files" in the "Systemwalker Operation Manager Operation Guide", and restore the schedule information in the same way.
[Description]
The authentication information could not be written.
[System Action]
Aborts processing.
[System Administrator Response]
Restore the authentication information (restauth.inf) from the jobschbackup directory under the database directory. For the restoration method, refer to the "Restoring Schedule Files" in the "Systemwalker Operation Manager Operation Guide", and restore the schedule information in the same way.
[Description]
The format of the authentication information control statement is invalid.
[System Action]
Aborts processing.
[System Administrator Response]
Correct the authentication information control statement.
[Description]
The specified authentication information cannot be found.
[System Action]
Aborts processing.
[System Administrator Response]
Specify the correct authentication information, and then retry the operation.
[Description]
An internal error occurred.
[System Action]
Aborts processing.
[System Administrator Response]
Collect "Jobscheduler" information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.
[Description]
The definition file has an incorrect keyword.
[Parameter]
xxxx: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
The definition file has an error control statement or an incorrect sequence of control statements.
[Parameter]
xxxx: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
The parameter specified by the operand of the definition file does not exist.
[Parameter]
xxxx: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
There is an error in the parameter specified by the operand of the definition file.
[Parameter]
xxxx: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
The control statement did not end with a semicolon.
[Parameter]
xxxx: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
Operand xxxx was used incorrectly in the definition file.
[Parameter]
xxxx: Operand name
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
An incorrect number of parameters was specified in the operand of the definition file.
[Parameter]
xxxx: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
There is an in consistency in the definition file.
[Parameter]
xxxx: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
A cancellation of the date not set in the definition file has been specified.
[Parameter]
xxxx: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
An operand is duplicated in the definition file although it is not allowed.
[Parameter]
xxxx: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
A parameter is duplicated in the definition file although it is not allowed.
[Parameter]
xxxx: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
The operands were specified in the incorrect sequence in the definition file.
[Parameter]
xxxx: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
The job net information of the user already registered in the shared memory does not exist.
[Parameter]
xxxx: User name
[System Action]
Aborts processing.
[System Administrator Response]
Collect the Jobscheduler information by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
One of the phenomena below occurred.
The specified project does not exist.
The user has no access privileges to the specified project.
The job net or group has been registered in the specified project.
[Parameter]
xxxx: Project name
[System Action]
Aborts processing.
[User Response]
Make sure that the specified project exists and that the correct access privileges have been registered for the project. Also, make sure that the specified job net or group has been registered in the project.
To check the access privilege to the project, select "Permissions" in the "Security" menu in the job selection window of the Systemwalker Operation Manager window.
[Description]
A record having one of the following errors was detected when the message event information was being read:
Incorrect record length
Invalid record at the beginning of message event information
[Parameter]
xxxx: User name
[System Action]
Aborts processing.
[System Administrator Response]
Copy the file from the jobschbackup directory to the database directory, and re-execute the jobschconvert command.
[Description]
The file name specified with the jobschchkfile command is invalid.
[Parameter]
XXXX: Specified file names etc.
[System Action]
Stops processing
[System Administrator Response]
Confirm the option or settings in the file such as a list file specified for the option to check the following points, and then execute the jobschchkfile command again.
Has the file name been specified using its full path?
Has a directory name been specified for the file name?
Is the file name valid?
Is the format of the applicable file valid?
[Description]
The specified operation is not executed because job net xxxx already belongs to the group.
[Parameter]
xxxx: Job net name
[System Action]
Aborts processing.
[User Response]
Remove the job net from the group.
[Description]
The specified operation could not be executed because the single startup of job net xxxx was not specified.
[Parameter]
xxxx: Job net name
[System Action]
Aborts processing.
[User Response]
Specify the single job net startup.
[Description]
Job net xxxx cannot be stored in the group because the Enable during job net execution option is specified or selected as its startup condition during occurrence of a message event.
[Parameter]
xxxx: Job net name
[System Action]
Aborts processing.
[User Response]
On the Messages sheet of Job Net Properties window, deselect the Enable during job net execution option. Then, register the job net again.
[Description]
The message information file was not read because the "open," "lockf" or "read" operation of the message information failed.
[Parameter]
xxxx: Job net name
[System Action]
Aborts processing.
[System Administrator Response]
Copy the file from the jobschbackup directory to the database directory, and re-execute the jobschconvert command.
[Description]
The database cannot be converted because service xxxx is active.
[Parameter]
xxxx: Service name
[System Action]
Aborts processing.
[System Administrator Response]
Stop the service before executing the command.
[Description]
The specified database file has already been converted.
[System Action]
Aborts processing.
[System Administrator Response]
If you need to convert a database file again, delete the following files from the database directory. Then, reconvert the file.
If the parameter is a user name: user-name. dbz
If the parameter is "sysfile.sys": sysfile.sys
[Description]
An incorrect date was specified in the definition file.
[Parameter]
xxxx: Line number or a range of line numbers where an error has occurred
[System Action]
Aborts processing.
[User Response]
Correct the definition file.
[Description]
An incorrect host name is included in the file that has been specified by the jobschmsgevent command parameter.
[System Action]
Aborts processing.
[System Administrator Response]
Check the specified host name and re-execute the jobschmsgevent command.
[Description]
The event could not be written in the event log by the jobschmsgevent command.
[Parameter]
xxxx: Host name (a hyphen (-) is shown for the local host.)
[System Action]
Aborts processing.
[User Response]
Take the appropriate action by referring to the message that is output together with this message.
[Description]
The job net cannot be registered because the current execution condition is not appropriate.
The following reasons are assumed:
The group cannot be registered or changed because the single startup was not specified for the job net in the group.
The job net cannot be changed because the execution condition of the child job net or linked job net is other than "None".
The specified change cannot be made for the job net with the execution condition "None" specified.
[Parameter]
xxxx: Job net name
[System Action]
Aborts processing.
[User Response]
Change the job net startup conditions, or recheck the contents to be registered/changed.
[Description]
Because job net xxxx does not exist, it is not registered as a child job net.
[Parameter]
xxxx: Job net name
[System Action]
Aborts processing.
[User Response]
Create job net xxxx.
[Description]
Because job net xxxx does not exist, it is not registered as the parent job net.
[Parameter]
xxxx: Job net name
[System Action]
Aborts processing.
[User Response]
Create job net xxxx.
[Description]
Job net xxxx is not registered because it does not satisfy the child job net startup conditions.
[Parameter]
xxxx: Job net name
[System Action]
Aborts processing.
[User Response]
Change the job net startup conditions to "none."
[Description]
Job net xxxx cannot be registered as a child job net because it already belongs to another parent job net.
[Parameter]
xxxx: Job net name
[System Action]
Aborts processing.
[User Response]
Remove job net xxxx from the parent job net.
[Description]
Job net xxxx cannot be registered as the parent job net because it does not have job execution control attributes.
[Parameter]
xxxx: Job net name
[System Action]
Aborts processing.
[User Response]
Set job net xxxx to have job execution control attributes.
[Description]
Job net xxxx cannot be registered as a child job net because it does not have job execution control attributes.
[Parameter]
xxxx: Job net name
[System Action]
Aborts processing.
[User Response]
Set job net xxxx to have job execution control attributes.
[Description]
File xxxx is not processed because it is not a text file.
[Parameter]
xxxx: File name
[System Action]
Aborts processing.
[User Response]
Specify a text file only.
[Description]
File xxxx could not be read.
[Parameter]
xxxx: File name
[System Action]
Aborts processing.
[User Response]
Remove the error cause by referring to the previous message.
[Description]
File xxxx could not be written.
[Parameter]
xxxx: File name
[System Action]
Aborts processing.
[User Response]
Remove the error cause by referring to the previous message.
[Description]
The user privilege information could not be obtained.
[Parameter]
xxxx: Code
[System Action]
Aborts processing.
[System Administrator Response]
Collect the Jobscheduler information by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
File xxxx could not be found.
[Parameter]
xxxx: File name
[System Action]
Aborts processing.
[System Administrator Response]
Make sure that the file exists.
[Description]
No message event could be generated by the jobschmsgevent command. A non-Windows server may have been specified or the "server" service is inactive on the specified host.
[Parameter]
xxxx: Host name
[System Action]
Aborts processing.
[User Response]
Make sure that the "server" service operates normally on the specified host.
[Description]
No message event could be generated. The specified host may be filled with event logs.
[Parameter]
xxxx: Host name
[System Action]
Aborts processing.
[User Response]
Set the specified host to accept event logs.
[Description]
The master linked job net XXXX does not exist.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Create the job net XXXX.
[Description]
The job net XXXX cannot be registered because the execution conditions of this job net do not meet the requirements of a master linked job net.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Change the execution condition of the job net to "None".
[Description]
The job net XXXX cannot be registered as a linked job net because it does not have the Job Execution Control attribute.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Change the attribute of the job net XXXX to the Job Execution Control attribute.
[Description]
It is not possible to register the job net XXXX as a linked job net because the job net with the same name as the job net XXXX already exists.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Change the job net name of the linked job net to another unique name, and then register it.
[Description]
It is not possible to register the job net XXXX as a linked job net because the job net with the same name as the job net XXXX already exists.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Change the job net name of the linked job net to another unique name, and then register it.
[Description]
The linked job net XXXX cannot be registered because the length of the job net name of the linked job net has exceeded the 50-byte limit.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Change the job net name of the linked job net to a name no longer than 50 bytes, and then register it.
[Description]
Linked job nets that refer to the same master linked job can be registered only up to 100.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[Description]
It is not possible to register the job net XXXX as a child job net because it is the master linked job net.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Register the job net XXXX as a linked job net.
[Description]
The linked job net cannot be registered because the job net name XXXX is duplicated between the newly registered linked job net and the job nets under that layer.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Change the job net name of the linked job net to another unique name, and then register it.
[Description]
It is not possible to register the job net XXXX as a child job net because linked job nets exist below the level of the job net XXXX.
[Parameter]
XXXX: Job net name
[System Action]
Aborts the process.
[User Response]
Delete the linked job nets below the level of the job net XXXX, and then register it.
[Description]
Job net XXXX, which you are attempting to register as a child job net, cannot be registered because the copy and startup setting is enabled.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
Disable the copy and startup setting in job net XXXX.
[Description]
The job net XXXX cannot be registered as a linked job net, because the copy and startup setting is enabled.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
Disable the copy and startup setting in job net XXXX.
[Description]
The job net XXXX cannot be registered to a group, because the copy and startup setting is enabled.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
Disable the copy and startup setting in job net XXXX.
[Description]
The job net XXXX cannot have a comment of 85 bytes or more, because the copy and startup setting is enabled.
[Parameter]
XXXX: Job net name
[System Action]
Aborts processing.
[User Response]
Ensure that the new job net comment does not exceed the maximum length.
[Description]
The file name is too long.
[Parameter]
XXXX: File name
[User Response]
Check the export destination specification.
[Description]
A required parameter is not specified in the connection information file.
[Parameter]
XXXX: Key name of a required parameter that is not specified
[System Action]
Aborts processing.
[User Response]
Make sure that the required parameters are set in the connection information file.
[Description]
An unnecessary parameter is specified in the connection information file.
[Parameter]
XXXX: Key name of the specified unnecessary parameter
[System Action]
Aborts processing.
[User Response]
Check whether unnecessary parameters have been set in the connection information file.
[Description]
A parameter value in the connection information file is invalid.
[Parameter]
XXXX: Key name of the parameter whose value is invalid
[System Action]
Aborts processing.
[User Response]
Make sure that the parameter values in the connection information file are specified correctly.
[Description]
The connection information file could not be read because open or read failed.
[Parameter]
XXXX: File name that failed to read
[System Action]
Aborts processing.
[User Response]
Make sure the file that failed to read is accessible.
[Description]
The HTTP response header or body could not be written because it failed to open or write the destination file.
[Parameter]
XXXX: Output destination file name that failed to write
[System Action]
Aborts processing.
[User Response]
Make sure that there is not enough free space.
Make sure that the destination directory for the HTTP response header or body exists.
Check the permissions/permissions of the destination directory in the HTTP response header or body.
[Description]
The HTTP request failed due to a network connection problem.
[Parameter]
XXXX: Type of failed HTTP request (request /monitoring/ termination/ authentication)
[System Action]
Aborts processing.
[System Administrator Response]
If you have configured a proxy authentication name in the credentials file, make sure that the registered proxy credentials are correct.
Check for other network problems such as DNS settings.
[Description]
The HTTP request failed because it timed out.
[Parameter]
XXXX: Type of failed HTTP request (request/ monitoring/ termination/ authentication)
[System Action]
Aborts processing.
[System Administrator Response]
Rereview the connection timeout period set in the connection information file.
If not, make sure that the HTTP request information in the connection information file or the AzureAD/SAP cloud service credentials in the credentials are correct.
[Description]
The HTTP request failed due to a problem.
[Parameter]
XXXX: Type of failed HTTP request (request/ monitoring/ termination/ authentication)
[System Action]
Aborts processing.
[System Administrator Response]
Make sure that the HTTP request information set in the connection information file is correct.
If a credential name is set in the connection information file, check whether the registered credentials are correct.
If the problem is not resolved, collect "Jobscheduler" information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.
[Description]
The execution result of the job on the cloud service is not the specified normal end value.
[Parameter]
XXXX: Execution result of the job on the cloud service
[System Action]
Aborts processing.
[System Administrator Response]
Check whether the job you submitted on the cloud service terminated normally, and then take the following actions.
If the command terminated normally, check whether the normal termination judgment key and value in the connection information file are set correctly.
If the job did not end normally, check and, if necessary, revise the job on the cloud service.
[Description]
The key to be inherited for monitoring and forced termination specified in connection information, key to be set for the job net variable, monitoring end judgment key, and normal end judgment key could not be found in the response result.
[Parameter]
XXXX:
Key to be inherited for monitoring and forced termination /Key to be set for the job net variable:
Substitution variable name
Monitoring end judgment key /Normal end judgment key:
Key name (pollingEndKey/ checkResultKey)
[System Action]
Aborts processing.
[System Administrator Response]
Make sure that the key to be inherited for monitoring and forced termination specified in connection information, key to be set for the job net variable, monitoring end judgment key, and normal end judgment key is set correctly.
If you are outputting the HTTP response body to a file, make sure that the key to extract exists in the HTTP response body.
[Description]
Failed to obtain authentication information during processing.
[Parameter]
XXXX: Authentication information name
[System Action]
Aborts processing.
[System Administrator Response]
Make sure that the authentication information of the authentication information name set in the connection information file is registered.
If so, check that the authentication information is correct.
[Description]
An error has occurred in the calendar API during conversion of calendar information.
[Parameter]
xxxx: Calendar name
yyyy: Error number
[System Action]
Does not convert the calendar information.
[System Administrator Response]
Remove the error cause by checking the error number. For information about error numbers, see the "Calendar API" section of the Systemwalker Operation Manager Reference Guide.
[Description]
No message event could be generated by the jobschmsgevent command. The user having incorrect access privileges may have executed the command from the specified host.
[Parameter]
xxxx: Host name
yyyy: User name
[System Action]
Aborts processing.
[User Response]
Register the correct user name and password on the specified host.
[Description]
Failed to delete the subsystem.
[Parameter]
XXXX: Subsystem number
YYYY: Return value from the stemSchDelete command
[User Response]
Identify the cause by referring to the return value from the stemSchDelete command, take an appropriate corrective action, and execute the command again.
Return value | Meaning | Action |
|---|---|---|
0 | Completed | - |
1 | Usage display | Confirm how to specify the option. |
2 | The user has no privileges for executing this command. | System administrator (superuser) privileges are required. |
3 | A system error occurred. | Check the system environment. |
4 | Execution unavailable because of the differences in the code systems. | The code system used for Systemwalker Operation Manager is not identical with that for the command execution environment. Use the same code system as that for Systemwalker Operation Manager. |
5 | DB access failed | Failed on opening, or reading from or writing to DB. Confirm the following:
|
6 | The Jobscheduler daemon is not running, or it is during startup processing. | Activate the daemon. If the daemon is already activated, it is during startup processing or it is not running properly. Wait a few moments, or reactivate it. |
7 | The specified project is not found. | Confirm whether the specified project name is correct. |
8 | The project cannot be deleted because a group or job net is currently executing. | After the currently executing group or job net terminates, execute the command again. |
11 | This command has failed in reading ACL manager library. | Confirm whether the following file exists. If the file is found, it may be damaged. Re-install the file. /opt/systemwalker/lib/libmpfwsecjm.so |
12 | The project cannot be deleted because a carried over job net exists. | After addressing the problem by, for example, disabling the carried over job net, execute the command again. |
13 | The project cannot be deleted because a group or job net is currently operating or being stored. | After the currently operating or stored group or job net terminates, execute the command again. |
14 | Timeout | Confirm the load of Systemwalker Operation Manager, then execute the command again. |
15 | Unable to delete because a shutdown job net (JSHEND or JSHFORCE) has executed. | Restart the Jobscheduler, then execute the command gain. |
[Description]
The HTTP request ended with a status code other than 200.
[Parameter]
XXXX: Type of failed HTTP request (request/ monitoring/ termination/ authentication)
YYYY: HTTP status code
[System Action]
Aborts processing.
[System Administrator Response]
If the type of HTTP request that failed (XXXX) is request/ monitoring/ termination
Make sure that the HTTP request information defined in the connection information file is correct.
If you specified credentials, make sure that the registered credentials are correct.
If the type of HTTP request that failed (XXXX) is authentication
Make sure that the credentials configured for the AzureAD/SAP cloud service are correct.
[Description]
The required parameter YYYY is not specified in the authentication information control statement.
[Parameter]
XXXX: Authentication information name. Empty character if YYYY is name.
YYYY: Parameter name
[System Action]
Aborts processing.
[System Administrator Response]
Correct the authentication information control statement.
[Description]
The YYYY parameter in the authentication information control statement is invalid.
[Parameter]
XXXX: Authentication information name
YYYY: Parameter name
[System Action]
Aborts processing.
[System Administrator Response]
Correct the authentication information control statement.
[Description]
A parameter YYYY that cannot be specified in the authentication information control statement is specified.
[Parameter]
XXXX: Authentication information name
YYYY: Parameter name
[System Action]
Aborts processing.
[System Administrator Response]
Correct the authentication information control statement.
