Hi Deepak Mincheri

Control-M A API do not provide ALL general Active Job Form values as response from ^run job:status::get^

as of latest API Control-M Automation API 9.0.19. those are the provided fields returned.

{
  "jobId": "LocalControlM:00008",
  "folderId": "LocalControlM:00007",
  "numberOfRuns": 0,
  "name": "job1",
  "folder": "SanityCommandOk",
  "type": "Command",
  "status": "Wait Condition",
  "held": true,
  "deleted": false,
  "startTime": "",
  "endTime": "",
  "estimatedStartTime": [],
  "estimatedEndTime": [],
  "orderDate": "180903",
  "ctm": "LocalControlM",
  "description": "",
  "host": "",
  "application": "OsApp",
  "subApplication": "",
  "outputURI": "Job did not run, it has no output",
  "logURI": "http://localhost:48080/run/job/LocalControlM:00008/log?token=a3be0b6b63bed01f1e11da24319ba133_81C95551"
  }

The only way I would see this happening is by requesting BMC a RFE.

As workarounds:

1) you may want to ^deploy jobs::get^ and export the original job definition

2) or install DB vendor NODEJS like PostgreSQL support over CTM API NODEJS and perform querys straight to the CTMEM DB like we do.

https://node-postgres.com/

Hope that it helps you

My Best

A>Gomes