ESP LJS command returns 11NOV1918, but not the actual date

Products

• ESP Workload Automation

Issue/Introduction

Receiving  "11NOV1918" instead of the job's actual start date?

ESP audit log shows:
   ESP387I  JOB name(JOBnnnnn) AUTOPOSTED FROM INPUT
   ESP2573I JOB name(JOBnnnnn) AUTOPOSTED FROM EXEC

                                                                             

Cause

- 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 when the product has 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 on the product exec queue but not the JES exec queue.
This could happen at any time when 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.    

Resolution

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 normal and that some   
data might be missing or inaccurate (such as time on queue etc.).