LJS (List Job Profile Statistics) command issued from CA Workload Automation ESP Edition returns "JOBnnnnn ON RDR AT hh.mm.ss MON 11NOV1918"

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

Description: This Knowledge Base article explains why "11NOV1918" is returned instead of the job's actual start date.

Solution:

"11NOV1918" is an arbitrary date set as a default initial date for the job START time.  When the job END processing is done, this date gets replaced with either job SUBMIT (if available), or job END date and time.  If WA ESP could not locate the job's actual start date and time, the arbitrary date "11NOV1918" remains.

When this condition occurs, the following informational messages can be seen in the ESP auditlog:

ESP387I JOB name(JOBnnnnn) AUTOPOSTED FROM INPUT
ESP2573I JOB name(JOBnnnnn) AUTOPOSTED FROM EXEC

Note: here are the explanations of above messages:

- 387I  JOB name(JOBnnnnn) AUTOPOSTED FROM INPUT 

Reason:                                                                      
At initialization or as the result of a QUPDATE command, the product detected
that the job queue status of the identified job had not been updated, and    
that a mismatch existed between the JES status and the product status.       
In this case, the job is on the product input queue but not on the JES input 
queue.  This could happen at any time where the product had not received an  
explicit notification of job start, job end or purge. This situation can     
arise when jobs are active when the system is brought down or crashes,       
or if the product is down for an extended period.   

                         
- 2573I JOB name(JOBnnnnn) AUTOPOSTED FROM EXEC

Reason:
At initialization or as the result of a QUPDATE command, the product detected
that the job queue status of the identified job had not been updated, and that
a mismatch existed between the JES status and the product status. In this case,
the job is in on the product exec queue but not on the JES exec queue.
This could happen at any time where the product had not received an explicit
notification of job start, job end or purge. This situation can arise when jobs are
active when the system is brought down or crashes, or if the product is down
for an extended period.    

                                                                        
System Action:                                                               
The job is moved to the appropriate queue. The job is posted with a post id  
of 'SYSTEM!' to indicate that the post was not a normal post and that some   
data might be missing or inaccurate (such as time on queue etc.).