Understanding resynchronization messages

As described in Tracking jobs, the information about the workload assigned to the agent is in term of events that record the work yet to be submitted and the outcome of the already processed work. During normal processing, the agent uses three event data sets to handle these events. The same data sets are also used for recovery purposes after a restart. They are (as known by their DD name within the agent for z/OS started task):

EELEVDS

Stores the events that track the complete life of a submitted job (submission, execution, outcome).

After a stop/restart, the agent searches this data set for the latest emitted events to send them to dynamic workload broker again.

EELHTREF

Stores the job submission requests received from dynamic workload broker. Contains information in terms of type of submission (by reference or by definition), the JCL or its location, the variable table when applicable. As soon as a request stored in EELHTREF has been thoroughly processed (the job has been queued to the submit task), it is flagged as completed.

After a stop/restart, the agent searches this data set for incomplete requests and processes them again.

EELHTDS

Stores the JCLs queued to the submit task.

After a stop/restart, the agent searches this data set for queued but not yet submitted JCLs in order to queue them again and complete their processing.

EELHT28I
EELHTDS REPROCESSING CAUSED RESUBMISSION OF FOLLOWING EVENT:
SSEQ: SEQ RECORD: REC CYCLE: CYC JOBALIAS:
JOBALIA1
JOBALIA2
Explanation: While reprocessing the EELHTDS data set
(recovery data set for pending submissions)after a restart, the agent 
found in pending status the job identified by the alias indicated by
JOBALIA1 and JOBALIA2.
The EELHTDS record where the job was found is identified by 
the REC record number and the CYC write cycle.
System action: The agent sends the job to the submit task again.

EELHT36I
INFORMATION ABOUT RESTART PROCESSING OF EELHTDS DATA SET FOLLOWS:  
HTDS NEXT TO WRITE        : REC INREC CYC INCYC
HTDS RESEND START POSITION: REC STREC CYC STCYC
HTDS RESEND STOP POSITION : REC CUREC CYC CUCYC
HTDS LAST SUBMIT DONE     : REC LSREC CYC LSCYC SSEQ: LSSS
Explanation: At start up the agent reprocesses the EELHTDS
data set (recovery data set for pending submissions) to find the
jobs that need to be submitted again
because their submission was left pending.
Before the jobs are processed again, the following information is provided:
• The EELHTDS position where the next record will be written, identified 
  by record number INREC and write cycle INCYC.

• The EELHTDS range that will be analyzed, identified by:
  • start position:	record number STREC, write cycle STCYC
  • end position:	record number CUREC, write cycle CUCYC.

• The last submission made by the agent before the restart,
  identified by sequence number LSSS and the related record in 
  EELHTDS having record number LSREC and write cycle LSCYC.
System action: Processing continues.

EELHT37I
INFORMATION ABOUT RESTART PROCESSING OF EELHTREF DATA SET FOLLOWS:  
HTREF NEXT TO WRITE    : REC INREC CYC INCYC
HTREF START POSITION   : REC STREC CYC STCYC
HTREF LAST POSITION    : REC LAREC CYC LACYC
HTDS LAST SUBMIT STORED: REC HTREC CYC HTCYC SSEQ: HTSS
Explanation: At start up the agent reprocesses the EELHTREF
data set (recovery data set for pending requests) to find the
jobs that need to be processed again as they were left pending.
Before the jobs are processed again, the following information is provided:
• The EELHTREF position where the next record will be written, identified 
  by record number INREC and write cycle INCYC.

• The EELHTREF range that will be analyzed, identified by:
  • start position:	record number STREC, write cycle STCYC
  • end position:	record number LAREC, write cycle LACYC.

• The last submission recorded in EELHTDS by the agent before the restart,
  identified by sequence number HTSS and the related record in 
  EELHTDS having record number HTREC and write cycle HTCYC.
System action: Processing continues.

EELHT38I
EELHTREF REPROCESSING RECOVERED FOLLOWING EVENT:
JOBALIA1
JOBALIA2
Explanation: At start up the agent reprocesses the EELHTREF
data set (recovery data set for pending requests) to find the
jobs that need to be submitted again as they were left pending.
This message is issued for each reprocessed job identified by 
the alias indicated by JOBALIA1 and JOBALIA2.
System action: Processing continues.

EELHT42I
THE HTTP SERVER FINISHED THE SYNCHRONIZATION WITH THE SUBMIT TASK.
NUM SUBMISSION EVENTS HAVE BEEN REPROCESSED.
Explanation: At start up the agent reprocesses the EELHTDS
data set (recovery data set for pending submissions) to find the
jobs that need to be submitted again because their submission 
was left pending. During the process, message EELHT28I is issued
for each resubmitted job. At the end of the process, message
EELHT42I is issued to communicate the total number of reprocessed
events NUM.
Note that it can happen that the number of issued EELHT28I messages
is lower than NUM. This occurs when incomplete events are found
(as reported by message EELHT35W) and therefore cannot be submitted.
System action: None.

EELHT44I
THE HTTP SERVER STARTED THE EELHTREF DATA SET PROCESSING.
Explanation: At start up the agent checks the EELHTREF
data set (recovery data set for pending requests) to find any
pending job submissions that need to be processed.
System action: The agent processes the EELHTREF data set.

EELHT45I
THE HTTP SERVER ENDED THE EELHTREF DATA SET PROCESSING.
NUM SUBMISSION EVENTS HAVE BEEN REPROCESSED.
Explanation: At start up the agent checks the EELHTREF
data set (recovery data set for pending requests) to find any
pending job submissions that need to be processed.
System action: None.