FORCE_STARTJOB event timestamp is logging the wrong time.

Document ID : KB000013572
Last Modified Date : 14/02/2018
Show Technical Document Details
Question:

We issue a sendevent -E FORCE_STARTJOB for a job and it is execute immediate as we expect but the autorep detail report shows an incorrect time for the FORCE_STARTJOB event.

 

Example:

job1 03/08/2017 11:54:43 03/08/2017 11:54:43 SU 8544998/1 0 

Status/[Event] Time Ntry ES ProcessTime Machine 

-------------- --------------------- -- -- --------------------- ---------------------------------------- 

[FORCE_STARTJOB] 03/08/2017 05:06:27 0 PD 03/08/2017 12:06:26 

STARTING 03/08/2017 11:54:42 1 PD 03/08/2017 11:54:42 host1

RUNNING 03/08/2017 11:54:43 1 PD 03/08/2017 11:54:43 host1

<Executing at host1> 

SUCCESS 03/08/2017 11:54:43 1 PD 03/08/2017 11:54:43 host1

Environment:
Workload Automation AE 11.3.xPlatform - ANYDatabase -ANY
Answer:

The "Time" field represent the time the event is scheduled to be processed.

The sendevent command does allow for a -T option where one may provide a scheduled time for the event to be executed.

If the -T option is omitted then the event should be scheduled immediately.

The sendevent command communicates with the as_server and asks it to write the event to the database on its behalf.

If the -T option is omitted then the current time the as_server believes it to be is used.

 

So in the example above the as_server believes it to be an older / past time than what the scheduler believes it to be.

 

If the issue's scope is only with the as_server then restart the as_server to confirm if it recognizing the correct current time.

If the issue persists check for timezone settings in the as_server's start up script (waae_server.$AUTOSERV) and check the database and operating system's times as well.

Synchronize them as needed.