Table 1 lists TuxJES commands and functions.
This utility generates the security profile for TuxJES system. When genappprofile is launched, you are prompted to enter the Oracle Tuxedo application password, user name, user password and the database connection (
MT_DB_LOGIN). The output is a security profile file which contains the Oracle Tuxedo application password, user name, user password and the database connection.
artjesadmin is the TuxJES command interface. It requires the TuxJES system must be started first.
artjesadmin supports the following parameters and options:
The security profile file generated by genappprofile. The default value is
~/.tuxAppProfile. The user name in this profile is the owner of the submitted jobs. A job without a specified owner is assigned the owner name "*".
Note:
|
artjesadmin is not responsible for scriptfile propagation. It must be located on a shared file system if the conversion and execution are not on same machines. The options are as follows:
|
-o='xxx': Specifies the options passed to the EJR script file using the
-i option.
artjesadmin also supports direct job submission using the following format:
artjesadmin has a return code different from zero if there is an error occurs as listed in
Table 2
-n jobname: Display jobs with given job name
-j jobid: Display a particular job information
•
|
JobID: The job ID generated by TuxJES system
|
•
|
CONVING: a job waiting for conversion
|
•
|
WAITING: a job waiting for execution.
|
•
|
DONE: a job finished successfully.
|
•
|
FAIL: a job finished but failed
|
•
|
INDOUBT: a job is in doubt state due to its initiator restarted
|
-n jobname: Hold jobs with given job name
-j jobid: Hold a particular job
Releases the jobs in HOLD_WAITING or
HOLD_CONVING status so that they can be picked up by
ARTJESCONV for conversion or
ARTJESINITIATOR for running. The options are as follows:
-n jobname: Release jobs with given job name
-j jobid: Release a particular job
-n jobname: Cancel jobs with given job name
-j jobid: Cancel a particular job
-n jobname: Purge jobs with given job name
-j jobid: Purge a particular job
-g groupname: the Tuxedo group name of the
ARTJESINITIATOR server
-i serverid: the Tuxedo server id of the
ARTJESINITIATOR server
-g groupname: the Tuxedo group name of the
ARTJESINITIATOR server
-i serverid: the Tuxedo server id of the
ARTJESINITIATOR server
S: job submission event; the event name is
ARTJES_JOBSUBMIT
C: job conversion complete event; the event name is
ARTJES_JOBCVT
E: job execution finish event; the event name is
ARTJES_JOBEXEC
P: job purge event; the event name is
ARTJES_ARTJESPURGE
A: all supported events. If the event is set to "on", A is the default.
on |off: The submission is on or off. the "on" setting can be used with the
-t option. "off" will unsubscribe all event subscriptions.
ARTJESADM is an Oracle Tuxedo application server provided by TuxJES. The
artjesadmin command communicates with
ARTJESADM for most tasks.
ARTJESADM must be configured in the UBBCONFIG file in front of other TuxJES servers since others they access services provided by
ARTJESADM. If
JESCONFIG is changed, all TuxJES related servers must be restarted for new configurations to take effect.
ARTJESADM supports the following parameters and options:
JESCONFIG represents the full path name of the TuxJES system configuration file. It allows the following parameters:
S: Job submission event. Event name: ARTJES_JOBSUBMIT
C: Job conversion complete event. Event name: ARTJES_JOBCVT
E: Job execution finish event. Event name: ARTJES_JOBFINISH
P: Job purge event. Event name:ARTJES_JOBPURGE
If EVENTPOST is not specified, no events are posted. The data buffer with event pos is FML32 type and the fields are defined in JESDIR/include/jesflds.h.
ARTJESINITIATOR is an Oracle Tuxedo application server provided the TuxJES. It is responsible for invoking the EJR to execute the jobs.
Once a ARTJESINITIATOR is killed or shutdown while it has job running, it will put the job in the
INDOUBT state when it is restarted.
Specifies the job classes this ARTJESINITIATOR server is associated. If this option is not specified,
ARTJESINITIATOR associates with all job classes.
In this example, ten ARTJESINITIATOR instances are configured and are associated with the
"A",
"H" and
"Z" job classes.
|
|
|
When a batch job is submitted to the TuxJES system, it is put in the conversion queue first. There is only one conversion queue in the system. A converted job is moved from the "conversion queue" to the "execution queue". The jobs in the queue are processed in FIFO order.
|
|
|
|
|
|
|
|
|
|
|
|
|