Platform LSF Reference Version 6.2

bpost
Platform LSF Reference
108
bpost
sends external status messages and attaches data files to a job
SYNOPSIS
bpost [-i message_index] [-d "description"] [-a data_file]
job_ID |
"job_ID[index]" | -J job_name
bpost [-h | -V]
DESCRIPTION
Provides external status information or sends data to a job in the system. Done or exited
jobs cannot accept messages.
By default, operates on the message index 0. By default, posts the message
"no description".
If a you specify a job ID:
◆ You can only send messages and data to your own jobs.
◆ You cannot send messages and data to jobs submitted by other users.
◆ Only root and LSF administrators can send messages to jobs submitted by other
users.
◆ Root and LSF administrators cannot attach data files to jobs submitted by other
users.
Job names are not unique; if you specify
-J job_name:
◆ You can ony send messages and data to your own jobs.
◆ You cannot send messages and data to jobs submitted by other users.
◆ Root and the LSF administrators can only send messages and data to their own jobs.
A job can accept messages until it is cleaned from the system. If your application
requires transfer of data from one job to another, use the
-a option of bpost(1) to
attach a data file to the job, then use the
bread(1) command to copy the attachment to
another file.
You can associate several messages and attached data files with the same job. As the job
is processed, use
bread(1) or bstatus(1) to retrieve the messages posted to the job.
Use
bread(1) to copy message attachments to external files.
For example, your application may require additional job status descriptions besides the
ones that LSF provides internally (
PEND, RUN, SUSP, etc.) Use the -d option to place
your own status or job description text as a message to the job.
You can also use
bstatus -d to update the external job status. The command:
$ bstatus -d "description" myjob
is equivalent to:
$ bpost -i 0 -d "description" myjob
With MultiCluster, both clusters must run LSF Version 6.2 or later. You cannot post a
message to a MultiCluster job if the clusters are disconnected. You cannot attach files to
MultiCluster jobs.