The jobschsetnet command is used when setting up (register/change/delete/copy) a job net, and setting (register/delete) startup days, message events and temporary changes information with the job net information.
<Setting Up Job Nets>
This section explains the jobschsetnet command in setting job nets along with the following items: Synopsis, Description, and Options.
Synopsis
[To register] jobschsetnet -nent [project name] definition file [-sys subsystem-number](*1)
[To change] jobschsetnet -nche [project name] definition file [-sys subsystem-number](*1)
jobschsetnet -ncheall [project name] definition file [-sys subsystem-number](*1) [To delete] jobschsetnet -ndel [project name/]job net name [-mod mode] [-sys subsystem-number](*1) [To copy] jobschsetnet -ncpy [copy source project name/]copy source job net name [copy destination project name/]copy destination job net name [-sys subsystem-number](*1)
[-sys subsystem-number] is the option of Systemwalker Operation Manager EE.
Description
Registers, changes, deletes and copies job nets.
When registering or changing a job net, you can set startup days information (including information on exception days) expanded by using the jobschprint -r command.
Can specify project names that you want to operate.
Note
About the number of job nets that can be registered with a project
The maximum number of job nets that can be registered with a project differs, depending on the edition (SE or EE):
In Systemwalker Operation Manager SE, up to 255 job nets can be registered.
In Systemwalker Operation Manager EE, there is no limit on the number of job nets that can be registered.
Options
-nent
Based on the information in the definition file, registers job nets. Note that registration is not possible if the job net with the same name already exists.
Note
If multiple job net control statements are described in the definition file and a nested job net is included, it is necessary to describe the child job net and linked job net before the parent job net.
If multiple job net control statements are described in the definition file and a base job net is included, it is necessary to describe the startup days of the base job net in a separate definition file from that of the job net you are using.
project name
Specifies the name of the project that stores the job net information. When registering, if there is only one project for the user of executing the jobschsetnet command to access for updating, this option can be omitted. When changing/deleting/copying, if there is only one project having job nets registered among the projects accessible for update by the user of executing the jobschsetnet command, this option can be omitted.
definition file
Specifies the name of the file where the job net control statements and job control statements are stored.
To register multiple job nets, you need to write multiple job net control statements in the file.
For more details on the job net control statement, see "4.10.1 Job Net Control Statement".
For more details on the job control statement, see "4.10.2 Job Control Statement".
-nche
-ncheall
Changes existing job nets based on the information in the definition file.
For the -nche option, it is convenient to note the changes in the definition file used when registering the job net. For operands that have not been mentioned in the definition file, changes will not be made to them if it is a job net to be changed, but if a job is to be changed, care must be taken because the definitions will be deleted. List all operands in the definition file when changing a job.
For the -ncheall option, regardless of the job net/job, it sets default values for parameters for operands that are not described in the definition file. If only the operands are specified in the definition file, the default values are also set for the parameters. Items with no default values, such as startup date/message event/temporary change information, are deleted.
Note
In job net control statements, operands and parameters must be specified in pairs. For the -ncheall option, that means when only operands are described in the definition file, parameters are not deleted. To delete startup days, message events, or temporary changes information registered, specify -ncheall option or execute the -sdel option of the jobschesetnet command.
Note
Clearing message events that have occurred when changing job nets
All message events are cleared when a job net is changed. Therefore, if a job net is changed after message events have occurred, it will be necessary to reproduce the message events again.
Note
If multiple job net control statements are described in the definition file and a nested job net is included, it is necessary to describe the child job net and linked job net before the parent job net.
If the parent job net is described first, the following error message is output, and the command may terminate abnormally.
[UNIX]
MpJobsch: ERROR: 0225: The job net is being saved or controlled.
[Windows]
MpJobsch: ERROR: 6225: The job net is being saved or controlled.
If multiple job net control statements are described in the definition file and a base job net is included, it is necessary to describe the job net that is using the startup days of that standard job net in a separate definition file.
If the same definition file is used, the following error message is output, and the command may terminate abnormally.
[UNIX]
MpJobsch: ERROR: 0225: The job net is being saved or controlled.
[Windows]
MpJobsch: ERROR: 6225: The job net is being saved or controlled.
-ndel
Deletes job nets. Once the job net has been deleted, the entire registration information of the job net and the jobs composing the job net is also deleted.
If a job net in a layered job net is deleted without specifying the -mod option, the second layer job net will become the first layer job net.
job net name
Specifies the name of the job net to be deleted. You cannot specify a job net of the second level or lower.
-mod mode
Specify the delete mode with 0 or 1. This mode determines the job net to delete.
If the deletion target is a copied job net, the subordinate child job nets will also be deleted regardless of this setting. The default is 0.
Deletes the specified job net only.
If the deletion target is a layered job net, the second layer job net will become the first layer job net.
Deletes the subordinate child job nets.
-ncpy
Copies job nets. The status of the copy destination job net becomes "Disabled". However, copying cannot be performed if a job net with the same name already exists in the copy destination project.
If the job net with "base job net" specified is copied to a different project, the name of base job net is removed. However, the startup day information except the base job net name is the same as the copy source.
copy source project name
Specifies the name of the project where the source job net information is stored. If there is only one project having job nets registered among the projects that can be referenced by the user of executing the jobschsetnet command, this option can be omitted.
copy source job net name
Specifies the name of job net to be copied.
copy destination project name
Specifies the name of the project where the destination job net information is stored. If omitted, it is assumed that the same project name as the source project name is specified. Specify the project name that can be accessed for update by the user of executing the jobschsetnet command.
copy destination job net name
Specifies the name of job net to which the job net is copied.
Information
Job net copy option -ncop in V13.3.1 or earlier
In V13.3.1 or earlier, the -ncop option was provided for copying job nets. In this version, you still can specify the -ncop option in the same way as the -ncpy option, but the status of a copy destination job net copied using the -ncop option will be "Waiting".
-sys subsystem-number
In the system with multiple subsystems, this option is used to specify the subsystem that you want to operate. Specify the target subsystem number using a range of 0 to 9. If omitted, the default is subsystem 0.
<Setting Startup Days/Message Events/Temporary Changes Information>
This section explains the jobschsetnet command in setting startup days/message events/temporary changes information along with the following items: Synopsis, Description, Options, and Cautions.
Synopsis
[To register] jobschsetnet -sent [project name] definition file [-sys subsystem-number](*1) [To delete] jobschsetnet -sdel [project name/] job net name [SCH|MSG|TMP] [-sys subsystem-number](*1)
[-sys subsystem-number] is the option of Systemwalker Operation Manager EE.
Description
Registers/deletes the startup days, message events, and temporary changes information in the job net information.
Options
-sent
Based on the information in the definition file, registers the startup days, message events, and temporary changes information.
project name
Specifies the name of the project where the job net information is stored. If there is only one project having job nets registered among the projects accessible for update by the user of executing the jobschsetnet command, this option can be omitted.
definition file
Specifies the name of the file where the control statements for the startup days, message events and temporary changes information are stored.
For more details on the startup days control statement, see the "4.10.3 Startup Days Control Statement".
For more details on the message event control statement, see "4.10.4 Message Event Control Statement".
For more details on the temporary changes control statement, see the "4.10.5 Temporary Changes Control Statement".
-sdel
Deletes the startup days/message event/temporary changes information.
job net name [SCH|MSG|TMP]
Specifies the name of the job net on which the startup days/message event/temporary changes information is deleted.
Only deletes the startup days.
Only deletes the message events.
Only deletes the temporary changes information.
-sys subsystem-number
In the system with multiple subsystems, this option is used to specify the subsystem that you want to operate. Specify the target subsystem number using a range of 0 to 9. If omitted, the default is subsystem 0.
The command storage directory and cautions for this command are shown below:
Command Location
Windows | Systemwalker Operation Manager installation directory\MpWalker.JM\bin |
Solaris | /usr/bin |
Cautions
If deletion of a job net fails, all job nets, including the underlying job nets, are not deleted.
For the job net with startup days/message event/temporary changes information that has been registered, when registering a new startup days/message event/temporary changes information, the new information in the definition file will override the previous one.
When you want to delete all of the startup days/message event/temporary changes information, do not specify any SCH, MSG or TMP parameters.
This command only requests the server to change the job net for its information, which means that completing the command does not guarantee that these changes have been applied to the job net (after executing this command, the changes may be reflected in the job net after an extended period.)
When you change or delete the schedule pattern and the holiday calendar used in the job net to be registered using this command, it must be performed after this command is completed.
If job nets are to be registered using this command with the files output by the jobschprint -r or jobschprint -R commands, job icon position information is initialized, so make the proper adjustments afterwards.
If the following messages are output even after you confirmed the job net completion using the jobschprint command, wait for a while and execute the command again because the messages were output due to the marginal timing issue while the job net status was transitioning to the completed status.
"The job net is already in the executing or warning state."
"The job net is already in the executing or warning state."
