This section explains the APIs provided by Jobscheduler.
Operating environments and precautionary notes that are common to Jobscheduler APIs are shown below.
Operating Environment
These APIs can only operate on machines where a Systemwalker Operation Manager server is installed. They will not operate on machines where only the Systemwalker Operation Manager client is installed.
The job net manipulation API, job net manipulation (startup parameter specification) API, group manipulation API and job net start time change API are available for Windows, Solaris and Linux versions.
The job net manipulation API/EE, job net manipulation (startup parameter specification) API/EE, group manipulation API/EE and job net start time change API/EE are available for Windows, Solaris and Linux versions.
Cautions
Use VisualC++ (version 2015) for compiler and multithread (DLL) for runtime library as the compile environment. [Windows]
Use the same version/levels of the LIB file and INCLUDE file.
Do not call Jobscheduler APIs from multiple threads in a single process simultaneously.
Do not execute the APIs from an environment where standard output and standard error output are closed.
Jobscheduler APIs are not synchronized with the Operation Management Server. Due to this, the completion of the APIs does not guarantee the completion of API processing executed on the server.
Also, there may be a slight time lag during which the API is executed and the processing is accepted on the server.
When the Extended User Management function is enabled, the access right authentication depends on the OS user that executes the API [UNIX]:
If the OS user is a system administrator:
The API is executed with the Operation Manager administrator privileges (has update rights for all projects).
If the OS user is a project owner:
The API is executed with the assumption that the owner has update rights over their projects.
If the OS user is neither a system administrator nor project owner:
The API is executed if the OS user that executed the API is included in the OS users corresponding to all Operation Manager users that have access to the project, and the API is executed if the user has the privileges. If the OS user that executed the API 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.
