sbank-detail-jobs

sbank-detail-jobs [options] [ <jobid.resource> | <event_id> ... <jobid.resource> | <event_id>]

Detail job information. NOTE: 1. The arguments <jobid.resource> or <event_id> are NOT REQUIRED; 2. event_id is the JOB DATABASE ID; 3. <jobid> is the SCHEDULER CREATED ID, such as Cobalt; 4. <jobid> can also be entered using option -j <jobid> ; 5. <event_id> can also be entered using option -e <event_id> ; 6. <resource> can also be entered using option -r <resource> ; 7. regardless, you can use options or arguments to get detail job information

OPTIONS

--version

show program's version number and exit

-h, --help

show this help message and exit

-a ALLOCATION_ID, --allocation-id=ALLOCATION_ID

filter on allocation id

-e EVENT_ID, --event-id=EVENT_ID

filter on event id

-f FIELD_INFO, --field-to-display=FIELD_INFO

FIELD_INFO is <FIELD>[:<WIDTH>], for available fields enter -f? or -f "?", to add fields enter -f "+ <FIELD>[:<WIDTH>] ..."

-j JOBID, --jobid=JOBID

filter on jobid

-n NUM_FIELDS_TO_DISPLAY, --num-fields-to-display=NUM_FIELDS_TO_DISPLAY

set number of fields to display

-p PROJECT, --project=PROJECT

filter on name or id, DO NOT MIX, enter 'all' to get all, wild cards '*' is allowed but only on names

-r RESOURCE, --resource=RESOURCE

filter on name or id, DO NOT MIX, enter 'all' to get all, wild cards '*' is allowed but only on names

-t TRANSACTION_ID, --transaction-id=TRANSACTION_ID

filter on transaction id

-u USER, --user=USER

filter on name or id, DO NOT MIX, enter 'all' to get all, wild cards '*' is allowed but only on names

-w "FIELD_INFO", --field-width

"FIELD_INFO" FIELD_INFO is <FIELD>:<WIDTH>, for available fields enter -w? or -w "?"

-E END, --end=END

[OPER1]<UTC_DATE1>[...[OPER2]<UTC_DATE2>], where the operators OPER1 and OPER2 can be one of the following: ge, gt, le, lt, eq or >=, >, <=, <, ==. Operator Defaults: OPER1 is 'lt' for single date entry, OPER1 and OPER2 are 'ge' and 'lt', respectively, for range date entry. Date Parsing Precedence: YEAR then MONTH then DAY, i.e., 121101 is parsed as YYMMDD, hence Nov. 1, 2012

-H, --human-readable

abbreviate numbers and use unit suffixes: K (thousands), M (millions), G (billions), T (trillions) ...

-S START, --start=START

[OPER1]<UTC_DATE1>[...[OPER2]<UTC_DATE2>], where the operators OPER1 and OPER2 can be one of the following: ge, gt, le, lt, eq or >=, >,<=, <, == . Operator Defaults: OPER1 is 'ge' for single date entry, OPER1 and OPER2 are 'ge' and 'lt', respectively, for range date entry. Date Parsing Precedence: YEAR then MONTH then DAY, i.e., 121101 is parsed as YYMMDD, hence Nov. 1, 2012

-T TRANSACTION_TYPE, --transaction-type=TRANSACTION_TYPE

transaction types: CHARGE, REFUND, PULLBACK, DEPOSIT, VOID

--created=CREATED_TIMESTAMP

[OPER1]<UTC_DATE1>[...[OPER2]<UTC_DATE2>], where the operators OPER1 and OPER2 can be one of the following: ge, gt, le, lt, eq or >=, >, <=, <, ==. Operator Defaults: OPER1 is 'ge' for single date entry, OPER1 and OPER2 are 'ge' and 'lt', respectively, for range date entry. Date Parsing Precedence: YEAR then MONTH then DAY, i.e., 121101 is parsed as YYMMDD, hence Nov. 1, 2012

--debug=DEBUG_LEVEL

SILENT, MUCH_LESS, LESS, MORE, VERBOSE, DEBUG, DEBUG1, DEBUG2

--eligible=ELIGIBLE_TIMESTAMP

[OPER1]<UTC_DATE1>[...[OPER2]<UTC_DATE2>], where the operators OPER1 and OPER2 can be one of the following: ge, gt, le, lt, eq or >=, >, <=, <, ==. Operator Defaults: OPER1 is 'ge' for single date entry, OPER1 and OPER2 are 'ge' and 'lt', respectively, for range date entry. Date Parsing Precedence: YEAR then MONTH then DAY, i.e., 121101 is parsed as YYMMDD, hence Nov. 1, 2012

--get-not-charged

only un-charged jobs

--history-date-range=END

[OPER1]<UTC_DATE1>[...[OPER2]<UTC_DATE2>], where the operators OPER1 and OPER2 can be one of the following: ge, gt, le, lt, eq or >=, >, <=, <, ==. Operator Defaults: OPER1 is 'ge' for single date entry, OPER1 and OPER2 are 'ge' and 'lt', respectively, for range date entry. Date Parsing Precedence: YEAR then MONTH then DAY, i.e., 121101 is parsed as YYMMDD, hence Nov. 1, 2012

--last-updated=LAST_UPDATED_TIMESTAMP

[OPER1]<UTC_DATE1>[...[OPER2]<UTC_DATE2>], where the operators OPER1 and OPER2 can be one of the following: ge, gt, le, lt, eq or >=, >, <=, <, ==. Operator Defaults: OPER1 is 'gt' for single date entry, OPER1 and OPER2 are 'ge' and 'lt', respectively, for range date entry. Date Parsing Precedence: YEAR then MONTH then DAY, i.e., 121101 is parsed as YYMMDD, hence Nov. 1, 2012

--no-commas

remove commas from comma separated thousands

--no-header

do not display the header

--no-history

do not show history information

--no-rows

do not display the row data

--no-sys-msg

do not display system message

--no-totals

do not display the totals

--queued=QUEUED_TIMESTAMP

[OPER1]<UTC_DATE1>[...[OPER2]<UTC_DATE2>], where the operators OPER1 and OPER2 can be one of the following: ge, gt, le, lt, eq or >=, >, <=, <, ==. Operator Defaults: OPER1 is 'ge' for single date entry, OPER1 and OPER2 are 'ge' and 'lt', respectively, for range date entry. Date Parsing Precedence: YEAR then MONTH then DAY, i.e., 121101 is parsed as YYMMDD, hence Nov. 1, 2012