Table 1 lists TuxJES commands and functions.
This utility generates the security profile for TuxJES system. When genjesprofile 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 with the file permission “-rw-------”.
artjesadmin is the TuxJES command interface. It requires the TuxJES system must be started first.
artjesadmin supports the following parameters and options:
Option -h prints
artjesadmin usage information as listed above.
Option -v indicates the current version of Oracle Tuxedo Application Runtime for Batch.
The security profile file generated by genjesprofile. The default value is
~/.tuxAppProfile. It requires the owner of the security profile must be the user who runs
artjesadmin. The user name in this profile is the owner of the submitted jobs. A job without a specified owner is assigned the owner name "*".
•
|
If -f profile is specified, the specified profile file will be used;
|
•
|
If -f is specified while profile is not, ~/.tuxAppProfile will be used as the profile file;
|
•
|
If -f is not specified, nothing will be used as the profile file.
|
Option -y and
-t are added to submit a job in the synchronous way.
Table 2 shows some details.
|
|
|
|
|
|
|
|
|
|
|
Optional. If -t is omitted, artjesadmin will wait infinitely.
While timeout occurs, artjesadmin command line will exit but the job will run by JES continuously without impact.
|
Table 3 lists the exit codes for
artjesadmin if
-y is specified.
Option -p and
-j are added to get job status without interaction in
artjesadmin console.
Table 5 lists the exit codes for artjesadmin if
-p is specified.
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 7
-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
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
L: job cancel completed event; the event name is
ARTJES_JOBCANCEL
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
L: Job cancel completed event. Event Name:
ARTJES_JOBCANCEL
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.
NONE: Default value. Indicates jobs are executed by the OS user who starts JES system. This is compatible with all previous implementations on JES system.
USER_IDENTICAL: Indicates jobs are executed by the
Oracle Tuxedo user with which JES client joins JES system. Make sure that each Oracle Tuxedo user corresponds to an existing OS user before you choose this value.
USER_MAPPING: When this value is specified, the JES system looks up the TuxJES user mapping file and finds out the OS user corresponding to the Oracle Tuxedo user with which JES client joins JES system, and then appoints this OS user as the job executor.
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
Table 9 lists the terms you need to know for a good understanding of the user substitution feature described in this section.
|
|
When artjesadmin is executed with...
|
When PRIVILEGE_MODE is set to...
|
|
|
|
|
USER_IDENTICAL or USER_MAPPING
|
Note:
|
Oracle Tuxedo SECURITY parameter must be set to USER_AUTH, ACL or MANDATORY_ACL, otherwise JES system fails to start up and the following error message is printed into ULOG: "ERROR: The current Tuxedo security level disallow the given privilege mode".
|
|
|
|
|
|
USER_IDENTICAL or USER_MAPPING
|
artjesadmin fails to login and the following error message is displayed: "ERROR: failed to join application."
|
Table 11 and
Table 12 show the permissions of users with different identities when operating jobs in TuxJES system enabling the user substitution.
The value of PRIVILEGE_MODE in
JESCONFIG should be specified to
MAPPING_CREDENTIAL or
IDENTITY_CREDENTIAL.
If the value of PRIVILEGE_MODE in
JESCONFIG is
MAPPING_CREDENTIAL, the value of
USER_MAPPING_FILE should be specified and the user mapping file should contain the mapping between
Oracle Tuxedo users and OS users.
•
|
Execute tmboot by root when JES system is running on the master machine of a MP domain.
|
•
|
Execute tlisten by root when JES system is running on a slave machine of a MP environment.
|
The SECURITY parameter in
RESOURCE section of
TUXCONFIG should be
USER_AUTH,
ACL or
MANDATORY_ACL.
Note:
|
If SECURITY parameter is set to APP_PW and AUTHSVC parameter is configured, the SECURITY level is regarded as USER_AUTH by Oracle Tuxedo.
|