Mload application phase - effect of dropped restart log table

Hi Experts,
1. "If the job paused during the application phase, and the work and error tables have not been dropped and restart log table is dropped, then restart the job" (I changed it as per my understanding  -- Mload reference 14.10 pg no. 42)
 
2. "If the Teradata MultiLoad job script has been lost, use the following abbreviated script
to restart the job:
.LOGON tdpid/userid/password;
.LOGTABLE logtablename;
.BEGIN MLOAD . . . ;
.END MLOAD;
.LOGOFFs
The BEGIN MLOAD command must identify all of the target tables, work tables, and
error tables of the original job, and they must all be intact and not corrupted. When
submitting the abbreviated script, Teradata MultiLoad uses the checkpoint markers in the
work tables to restart the task at the point it stopped in the application phase."
 
So, can we restart a Multiload job that paused/failed in application phase even without Restart log table?  So, if we restart the job, it tries to read the restart log table which is not present and hence will try to read the work tables?  Can the Mload job be restarted without restart log table even in Acquisition phase?  Are these check point markers produce equilvalent information that should be in restart log table?  Thank you for your time on this.