API depends on your version and you need to have the client installed from Server/DEsktop initiating the API
the PDF document should have been included on you CD2 called Command Line Program Guide
I will use 5.3.1 as an example:
open a command prompt
Browse to C:\Program Files (x86)\TIDAL\Scheduler\client
type in set alias=DEV > example=DEV otherwise it defaults to Admiral
type in SACMD
type HOST I always type in HOST so I can verify what master I am running against (nio need if only one connection)
type in jobmon with your options I included below from doc
[-d date] +display_options [filtering_options] [-b]
It may be of limited use in 5.3.1 because to isolate you need to know Job ID or Alias or some other filter critiera... Job ID is in database jobmst.dbo.jobmst_id which is the unique identified and can be different from alias... depending on your requirements (dashboard?) and how you have organized your jobs a SQL query would be the better option.
DISPLAY
| r | Job rule ID |
| i | Job run ID |
| p | Parent job group ID |
| j | Job type (job or job group) |
| c | Occurrence number |
| o | Job or job group owner |
| u | Runtime user |
| h | Agent The Agent the job runs on |
| z | Scheduled vs. unscheduled job |
| t | Job start time |
| s | Job status |
| v | Job duration |
| n | Job name |
| a | Job alias |
| q | Queue |
| x | Exit code |
| FILTER |
| -r | rule_id Job rule ID |
| -p | group_id Parent job group ID |
| -j | type Job type. You can choose: job group: group, or 1 job: Job, or 2 |
| -o | owner Job or job group owner |
| -u | run_user Runtime user |
| -h | agent The Agent name the job runs on |
| -s | job Status ( Completed Abnormally=103, Normal=101) |
| -a | alias Job alias |
| -x | exit_code Exit code |
| -b | Suppresses the header information |
