bread

reads messages and attached data files from a job

Synopsis

bread [-i message_index] [-a file_name] job_ID | "job_ID[index]" | -J job_name
bread [-h | -V]

Description

Reads messages and data posted to an unfinished job with bpost.

By default, displays the message description text of the job. By default, operates on the message with index 0.

You can read messages and data from a job until it is cleaned from the system. You cannot read messages and data from done or exited jobs.

If a you specify a job ID:

  • You can get read messages of jobs submitted by other users, but you cannot read data files attached to jobs submitted by other users.

  • You can only read data files attached to your own jobs.

  • Root and LSF administrators can read messages of jobs submitted by other users.

  • Root and LSF administrators cannot read data files attached to jobs submitted by other users.

Job names are not unique; if you specify -J job_name:

  • You only can read messages and data from your own jobs.

  • You cannot read messages and data from jobs submitted by other users.

  • Root and the LSF administrators can only read messages and data from their own jobs.

The command:
bstatus
is equivalent to:
bread -i 0

Options

-a file_name

Gets the text message and copies the data file attached to the specified message index of the job to the file specified by file_name. Data files cannot be attached to MultiCluster jobs.

If you do not specify a message index, copies the attachment of message index 0 to the file. The job must have an attachment, and you must specify a name for the file you are copying the attachment to. If the file already exists, -a overwrites it with the new file.

By default, -a gets the attachment file from the directory specified by the JOB_ATTA_DIR parameter. If JOB_ATTA_DIR is not specified, job message attachments are saved in LSB_SHAREDIR/info/.

-i message_index

Specifies the message index to be retrieved.

Default: 0

job_ID | "job_ID[index]" | -J job_name

Required. Specify the job to operate on.

The job name can be up to 4094 characters long for UNIX and Linux or up to 255 characters for Windows. Job names are not unique.

The wildcard character (*) can be used anywhere within a job name, but cannot appear within array indices. For example job* returns jobA and jobarray[1], *AAA*[1] returns the first element in all job arrays with names containing AAA, however job1[*] will not return anything since the wildcard is within the array index.

-h

Prints command usage to stderr and exits.

-V

Prints LSF release version to stderr and exits.

Example

bpost -i 1 -d "step 1" -a step1.out 2500
bread -i 1 -a step2.in 2500
JOBID      MSG_ID FROM      POST_TIME      DESCRIPTION
2500       1      user1     May 19 13:59   step 1

Displays the message description text step 1 for message index 1 of job 2500 and copies the data in the file step1.out attached to message 1 to the file step2.in.

See also

bpost(1), bstatus(1), bsub(1), JOB_ATTA_DIR