The following are the commands used for the Master Schedule Management function:
Configures and removes the Master Schedule Management function environment.
Executes and manages the daily schedule management.
Sets the registered projects as the master definition of the daily schedule management.
Deletes a project including the information in the project.
Creates a project to be used in performing operation changes. (Copying the project)
Changes a release day of project that was created for operation changes. (Moving the project)
Returns the master information to the state before the release day that the operation change was implemented.
Generates a message event based on process date.
Displays the saved schedule information.
Changes the IP address of the management server or schedule server under the cluster environment.
Outputs the job net history information if the Master Schedule Management function is enabled.
Outputs a job net's current status if the Master Schedule Management function is enabled.
Submits (extract/register) job nets individually from the master information to the already created Schedule by dates project.
Changes a database directory of the Master Schedule Management function.
Registers/deletes the service for cluster in the Master Schedule Management function. This command is used to use the Master Schedule Management function in a cluster environment.
Point
When the Extended User Management function is enabled, the access right authentication depends on the OS user that executes the jobschmsgeventex and stemprint commands:
If the OS user is a system administrator, the commands are executed with the Operation Manager administrator privileges (has update rights for all projects).
If the OS user is a project owner, the commands are executed with the assumption that the owner has update rights over their projects.
If the OS user is neither a system administrator nor a project owner, the OS user that executed the commands are included in the OS users corresponding to all Operation Manager users that have access to the project, and the commands are executed if the user has the privileges. If the OS user that executed the commands corresponds to more than one Operation Manager user, the OS user will be given the most powerful privileges (update rights > change and operation rights > reference rights) among the privileges that the corresponding Operation Manager users have. If the corresponding Operation Manager user has both change rights and operation rights, then the OS user will also have both privileges.
When the Systemwalker authentication repository is enabled, the access right authentication depends on the OS user that executes the jobschmsgeventex and stemprint commands:
If the OS user is a system administrator, the commands are executed with the Operation Manager administrator privileges (has update rights for all projects).
If the OS user is a project owner, the commands are executed with update rights over the project they are the owner of.
If the OS user is neither a system administrator nor a project owner, the commands are executed if the OS user has access rights over the project (update rights, change rights, operation rights, and reference rights).