miser_jinfo(1)
miser_jinfo - query miser about the schedule of a submitted job
As shipped in IRIX 6.5. First release of IRIX 6.5.
NAME miser_jinfo - query miser about the schedule of a submitted job SYNOPSIS miser_jinfo -j bid DESCRIPTION The miser_jinfo command is used to query the schedule of a job that has already been scheduled by miser(1) If the specified job exists and miser(1) is running, miser_jinfo will return the schedule in the same format as miser_submit(1). DISPLAY The format of the schedule returned by miser_jinfo is a table that lists the batch ID, segment ID, multiple, priority, exception condition, total wall clock time, completion date, CPUs allocated, and memory allocated for each segment of the resource table. The batch ID is used by miser, various miser commands, and the kernel to communicate about a specific job. It is equivalent to the process group id, although this may change in future. The segment ID identifies the current segment in the resource schedule list. The priority is a field provided for use by scheduling policies. The total wall clock time is the product of the CPU time and the number of CPUs. The completion date is when Miser has scheduled the segment to terminate. The CPUs allocated and the memory allocated list the resources reserved for that segment. OPTIONS -j bid The bid is the ID of the miser job and is the process group id of the job. For a more detailed discussion of the bid see miser_submit(1) and miser(1). BUGS If miser is killed before the miser_jinfo command returns from communicating with miser, then the miser_jinfo command will hang until miser is restarted. SEE ALSO miser(5), miser(1), miser(4), miser_submit(1), miser_submit(4), miser_qinfo(1), miser_move(1), miser_reset(1).