The bstatus Command

To get status on batch jobs, use the bstatus command:

bstatus [ -jobs ] [ -engines ] [ -stagedir id ] [ -canceljob id ] [ -batches]

bstatus accepts the following arguments:

bstatus Arguments

Argument	Description
jobs	Lists all jobs on the Manager. This does not include pending batch jobs. The output displays name, jobid, tasks, priority, and status for each job. If there are no jobs, only the four rows of heading lines are returned.
engines	Lists all Engines connected to the Manager. The output displays name, ID, OS, and status of each Engine. If there are no jobs, only the four rows of heading lines are returned.
stagedir	Lists all files living on the staging directory for the given job ID or batchjob ID.
canceljob	Cancels a job. This only works for job IDs, not batch IDs, and the Driver must have appropriate permissions for this operation.
batches	Lists all Batch jobs on the Manager and their status. The output displays name, batchid, and status of each Batch. If there are no batches, no output is returned.

The bstatus command prints its output interspersed with Manager log output on stderr. To view only the bstatus output on a UNIX system, you can redirect stderr to null, for example, with bstatus -jobs 2>/dev/null. Windows users can use the syntax bstatus -jobs 2>&0.

To check the status of a Batch Job, you must be running PDriver with a Driver user that has the appropriate Security Role on the Manager. To do this, create a Driver user mapped to a role with access to the Batch Admin View feature (such as the default Manage role), and set DSUsername and DSPassword in the driver.properties file to this username.