3.1.4.7 Printing

printjob(ptj) -n jobname | -j jobid | -c job_class |-a [-v][-t JCL|KSH][-m] | -l
Displays the existing jobs. If no option is specified, it displays all jobs. The options are as follows:
  • -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 mode
  • -t JCL|KSH: Display JCL|KSH jobs
  • -m: Print the CPU time usage of each step in one JOB
  • -l: Display the number of jobs for each job class in each job status type

Note:

-l option is not supported when you use /Q to store and manage metadata of Batch jobs.
Listing Sample: Printing Output
> ptj -a
JOBNAME       JobID     Owner       Prty C       Type         Status
--------     --------   --------    ---------    ------       --------
 cjob       00000015     *             5 A         KSH          DONE
 cjob       00000016     *             5 A         KSH          DONE
 cjob       00000018     *             5 A         KSH          CONVING

total:3
success:3
  • JOBNAME: The job name.
  • JobID: The job ID generated by TuxJES system
  • Type: the job type (JCL or KSH)
  • 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
    • CANCELED: a job is canceled

In verbose mode, the job detail information is displayed:

  • Submit time: The submit time of the job
  • Step: The current running job step. It is only applicable to running jobs.
  • Type Run: The TYPRUN definition of the job.
  • Machine: Only for running/done/failed jobs. It is the machine name that the job is/was running on.
  • CPU usage: The user CPU usage and system CPU usage for the job execution.
  • Result: Job operation result, “OK” or error message.
If no option is specified, the "-a" option is assumed.
holdjob(hj) -n job name | -j jobid | -c job_class | -a
Hold the specified jobs which are in CONVING or WAITING status. The options are as follows:
  • -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 jobs
If no option is specified, the "-a" option is assumed.
releasejob(rlj) -n job name |-j jobid | -c job_class | -a
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 jobs
If no option is specified, the "-a" option is assumed.
canceljob(cj) -n job name |-j jobid | -c job_class l -a
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 jobs
If no option is specified, the "-a" option is assumed.
purgejob(pgj) -n job name |-j jobid | -c job class | -s job status | -a
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.
The options are as follows:
  • -n jobname: Purge jobs with given job name
  • -j jobid: Purge a particular job
  • -c job class: Purge jobs with given job class
  • -s job status: Purge jobs with given job status
  • -a: Purge all jobs
If no option is specified, the "-a" option is assumed.
changeconcurrent(chco) -g groupname -i serverid -n concurrent_num
Changes the number of maximum concurrent executing jobs for the ARTJESINITIATOR server which is designated by the -g and -i options. The change takes effect with no need to restart the ARTJESINITIATOR server.
The options are as follows:
  • -g groupname: the Tuxedo group name of the ARTJESINITIATOR server
  • -i serverid: the Tuxedo server id of the ARTJESINITIATOR server
  • -n concurrent_num: the number of maximum concurrent executing jobs
The change is not persistent, which means the number is reset when the ARTJESINITIATOR server restarts.
printconcurrent(pco) -g groupname -i serverid
Displays the number of maximum concurrent executing jobs for the ARTJESINITIATOR server which is designated by -g and -i options.
The options are as follows:
  • -g groupname: the Tuxedo group name of the ARTJESINITIATOR server
  • -i serverid: the Tuxedo server id of the ARTJESINITIATOR server
event (et) [-t C,E,P,L,A] on|off
This command tells artjesadmin to subscribe particular job event. The options are:
  • 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.
If the subscribed event type is not configured in JESCONFIG, an error is reported.
verbose(v) on|of
Turn on /off verbose mode.