16.3 Job Execution Control API

This section explains information on the APIs provided by Job Execution Control:

The operating environments, precautionary items, and required files which are common to Job Execution Control APIs are explained below.

Operating Environment

This API can only operate on the machine where a Systemwalker Operation Manager server has been installed. It cannot operate on the machine where only the Systemwalker Operation Manager client has been installed.

Cautions

In a compiling environment, use Visual C++ (version 2005) as the compiler and "multithread" for the runtime library. [Windows]
As for applications that have link with LIB, establish their links again by using the file and INCLUDE file provided in this version/level.
Do not call the Job Execution Control APIs from multiple threads within a single process simultaneously.

Required Files

The following files are required for use with the Job Execution Control APIs shown above:

[Windows x86]

LIB:: f3cuapi.lib

INCLUDE:: f3cuapi.h

[Windows x64]

LIB:: f3cuapi_x64.lib

INCLUDE:: f3cuapi_x64.h

[Common to Solaris 32-bit, Solaris 64-bit, Linux x86 and Linux x64]

LIB:: libmjes.so

INCLUDE:: mjesapi.h

The Job Execution Control APIs are contained in the LIB file, and declarations for the constants and structures used by these APIs are entered in the INCLUDE file.

These files are stored in the following directories:

[Windows]

LIB:: Systemwalker Operation Manager installation directory: MpWalker.JM\lib

INCLUDE:: Systemwalker Operation Manager installation directory: MpWalker.JM\include

[Common to Solaris and Linux]

LIB:: /opt/FJSVMJS/usr/lib

INCLUDE:: /opt/FJSVMJS/usr/include