Table 1 lists TuxJES commands and functions.
Generates the security profile for TuxJES system TuxJES command interface. TuxJES administration server. TuxJES conversion server. TuxJES job control API. TuxJES Queue system.genappprofile – Generates the security profile for TuxJES systemThis 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. The output is a security profile file which contains the user name and encrypted passwords. The generated security profile file can be used by the artjesadmin tool to login to an Oracle Tuxedo domain.genapprofile supports the following parameters and options:The location of the generated security profile file. If this option is not specified, the default value is ~/.tuxAppProfile.artjesadmin – TuxJES command interface.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 "*".artjesadmin supports the following sub commands:Submits a job to TuxJES system. The scriptfile parameter is the job script to be submitted.
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': the option string passed to EJR-i =scriptfile: The script file. It can be an absolute path format or a relative path in the current working directory. It is limited to a 1023 length in an absolute path.Once successfully invoked, the return format Job xxx is submitted successfully. If an error occurs, an error message is printed.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
Table 2 Error Codes -n jobname: Display jobs with given job name-j jobid: Display a particular job information-c job_class: Display a particular class jobs information-a: Display all jobs-v: Verbose modeListing 1 printjob Output
• JOBNAME: The job name.
• JobID: The job ID generated by TuxJES system
• Owner: Job Owner.
• Prty: Job priority
• C: The job class.
• Status: Job status
• EXECUTING: a job is running
• CONVING: a job waiting for conversion
• WAITING: a job waiting for execution.
• DONE: a job finished successfully.
• FAIL: a job finished but failed
• HOLD_WAITING: a JOB is in hold state after conversion
• HOLD_CONVING: a job is in hold state without conversion
• INDOUBT: a job is in doubt state due to its initiator restarted
• If no option is specified, the "-a" option is assumed.-n jobname: Hold jobs with given job name-j jobid: Hold a particular job-c job_class: Hold a particular class jobs-a: Hold all jobsIf no option is specified, the "-a" option is assumed.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-c job_class: Release a particular class jobs-a: Release all jobsIf no option is specified, the "-a" option is assumed.Cancels a job and moves it to the output queue. For running jobs, this command informs the related ARTJESINITIATOR to invoke EJR with "-k" option. Other jobs are moved directly to the output queue. The TuxJES system assumes the job is terminated when EJR returns. The options are as follows:-n jobname: Cancel jobs with given job name-j jobid: Cancel a particular job-c job_class: Cancel a particular class jobs-a: Cancel all jobsIf no option is specified, the "-a" option is assumed.Completed jobs in the output queue are moved to the purge queue. For other jobs, purgejob has same effect as canceljob. The purgejob command does not purge the job directly. The ARTJESPURGE server deletes the job from the TuxJES system. If ARTJESPURGE is not started, the job remains in the output queue.-n jobname: Purge jobs with given job name-j jobid: Purge a particular job-a: Purge all jobsIf no option is specified, the "-a" option is assumed.S: job submission event; the event name is ARTJES_JOBSUBMITC: job conversion complete event; the event name is ARTJES_JOBCVTE: job execution finish event; the event name is ARTJES_JOBEXECP: job purge event; the event name is ARTJES_ARTJESPURGEA: 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 – TuxJES Administration server.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:The default job class if the job class is not set for a job. It is an optional attribute. The default job class is A if this attribute is not set.If it is not set, only one job can be in execution status for a job name. NODELAY will remove the dependency check. The default value is delay execution.S: Job submission event. Event name: ARTJES_JOBSUBMITC: Job conversion complete event. Event name: ARTJES_JOBCVTE: Job execution finish event. Event name: ARTJES_JOBFINISHP: Job purge event. Event name:ARTJES_JOBPURGEA: All supported events.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.ARTJESCONV – TuxJES conversion server.ARTJESINITIATOR – Job InitiatorARTJESINITIATOR 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.ARTJESINITIATOR supports the following parameters and options:Specifies the job classes this ARTJESINITIATOR server is associated. If this option is not specified, ARTJESINITIATOR fails to start.In this example, ten ARTJESINITIATOR instances are configured and are associated with the "A","H" and "Z" job classes.ARTJESPURGE – Purges job queueARTJESPURGE monitors the purge queue. If it finds a job in the purge queue, it removes the job in the queue and deletes the directory JESROOT/<JOBID>.In order to emulate the z/OS JES2 system, TuxJES system uses a queue mechanism for batch job life cycle management. All queues are created in one queue space called "JES2QSPACE". A batch job is represented by a message that resides and is transferred to queues listed in Table 3.
Table 3 TuxJES Queues 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. The TuxJES system provides a sample shell script (jesqinit) to create the queue space (JES2QSPACE) and the queues listed in Table 3. You can modify the script to adapt to your environment, but must adhere to the following: