The job manager batch mode is provided by the gsserver.exe service program.
It enables the job manager to be started in a command line or as a Windows NT service.
The command line options are as follows:
Setup of an automatic start-up service
gsserver -a "<external service name>" "<internal service name>" [-depends:[none|all]] <parameters>
Setup of a manual start-up service
gsserver -i "<external service name>" "<internal service name>" [-depends:[none|all]] <parameters>
Start from command line
gsserver -c <parameters>
Start from command line without console
gsserver -q <parameters>
All command line parameters can be specified for a service:
Parameters |
Meaning |
-depends:[all|none] |
Managing dependencies |
-l | -d |
Logical server name (-lGSSOUM) <driver>/<base> in local mode ("-dSQL Server/JM") |
-u |
User for the connection (-usa) |
-p |
Password for the connection (-psa_password) |
-e |
Environment name (display) (-eGTS) |
-n |
Internal (running) manager name. Default machine name. Corresponds to the name of the machine running a job. |
-r |
Restricting start-up of queues (-r<id1>,<id2>...). The job manager (JM) will only start specified queues. Warning: queue IDs must be separated by commas, with no spaces. Example: -r1,5 restricts the JM to queues from IDs 1 and 5. |
-i<language_code> |
Selecting display language. For example, -i2057 selects the English interface. By default, the job manager is displayed in the language selected in the Visual Adelia Runtime configuration. |
-remove-schema |
Deletes the GSSOUM schema for requests (use HGXXX tables instead of GSSOUM.GSXXX). |
<name>=<value> |
Defining environment variable. |
<file_name_1> |
Parameter file. This file will be searched for in the current directory, then in the PATH. If this parameter has not been specified, the gestsoum.ini file will be searched for. |
<file_name_2> |
User parameters (use with an extension DLL). This file will be searched for in the current directory, then in the PATH. If this parameter has not been specified, the user.ini file will be searched for. |
For example, to install a service with connection parameters specified in GTS.ini (manual definition of dependencies):
C:\> gsserver -a "Job Manager - GTS" "gsserverGTS" GTS.ini
Adelia Job Manager v2.0.0.1
The following middleware services have been found:
1: Adelia - Middleware
Enter index for service dependency (return=no dependency):
The following database services have been found:
1: DB2 - DB2
2: MSSQLSERVER
3: OracleServiceBDCADEL
4: OracleServicePS00JCV
Enter index for service dependency (return=no dependency): 2
==> adding MSSQLSERVER (MSSQLSERVER) to the dependencies list...
Job Manager - GTS installed.
C:\> _
The same installation with automatic management of dependencies (a bad choice in this case as too many dependencies are established):
C:\> gsserver -a "Job Manager - GTS" "gsserverGTS" -depends:all GTS.ini
Adelia Job Manager v2.0.0.1
==> adding AdeliaDaemon (Adelia - Middleware) to the dependencies list...
==> adding DB2 (DB2 - DB2) to the dependencies list...
==> adding MSSQLSERVER (MSSQLSERVER) to the dependencies list...
==> adding OracleServiceBDCADEL (OracleServiceBDCADEL) to the dependencies list...
==> adding OracleServicePS00JCV (OracleServicePS00JCV) to the dependencies list...
Job Manager - GTS installed.
C:\> _
To start a local manager on the SQL Server JM database from a command line:
C:\> gsserver -c "-dSQL Server/GTS" -usa -psa_password
Job manager listening (3916)...
Note: it is not possible to start two job managers with the same name (host machine name by default) for a manager database.
