When RC/Migrator analysis output is executed by Batch Processor .SYNC points are taken at each stage. These set a restart point for Batch Processor to begin again. All work before them has been committed. How can I find out which SYNC point was the last one to be processed?
Apart from looking at the last job output that failed the RC/Migrator Execution Display will show you this information.
It can be entered in one of two ways.
From option 3 on the RC/Migrator main menu or with the "X" command placed next to a given Analysis output line.
If the job has been executed before, then the restart record can be viewed from this display.
Using the BPID of the job, or the Strategy name, the records can be seen.
The result are the restart records for this strategy. Both ANALYSIS jobs and EXECUTION jobs are recorded.
PTEDL1 ------------ Execution Display Panel ----------- yyyy/mm/dd hh:mm
COMMAND ===> SCROLL ===> CSR
BPID ==> *
DB2 SSID ==> ssid Strat Creator ==> USERID1 Timestamp ==> *
Status ==> * Strat Name ==> TSROLE Type ==> *
--- Strategy ----
BPID Creator Name St T Syncpoint-# Timestamp Message
__ USERID1-TSROLE-USERID1-2008022 USERID1 TSROLE NI S 40 2008022720540978 LOAD TABLE HLQ.TBROLE
__ USERID1-TSROLE-USERID1-2008022 USERID1 TSROLE NC A 0 2008022720404956 ANALYSIS FOR HLQ.TSROLE
The second line shows that the "T" Type column is "A" for the Analysis job. The Message Column tells you that also.
The first line shows that the "T" column is "S" for the Execution job and the execution reached Syncpoint-# number 40.
The "ST" status column tells us that "NI" means "Error during execution, job terminated.".
If the execution was successful then the "ST column would show "NC", which means "Completed successfully".
The Message column tells us that it was doing a load of a table at the time and it tells you the table name.
This message comes from the SYNC row in the Analysis output being executed.
".SYNC 40 'LOAD TABLE HLQ.TBROLE'.
From here the execution can also be restarted with the "S" line command.
If you have identified and fixed the problem that caused the execution to stop;
Specify RESTART "Y" on the Batch Processor Interface screen and it will start from sync point 40 automatically.
Check to make sure that there is no Utility still stopped and that no work datasets are left over from the last run if a utility was involved.
Utilities must be restarted in the .CALL statement with the RESTART parm. See TEC467133 for more details. See also TEC446808 regarding Terminating a Batch Processor ID that is flagged Incomplete.