Restart Logic

suraaj · New User Joined: 16 Apr 2009 Posts: 69 Location: Canada

A job processed 4 VSAM records and 4 DB2 row without performing a COMMIT. The job ABENDed on the 5th processing record. Explain how we could handle a restart for this situation.

Rohit Umarjikar · Posted: Fri Feb 27, 2015 9:38 pm

It depents on your Commit frequency. If you are doing it let us say after 10 records then after you commit store the last record into Restart table. Now if 11th record is a bad one and Job abends then when you Restart it have a dummy read till last key that is stored and then process further. Now with your numbers above it won't commit so you need to process from top.

suraaj · New User Joined: 16 Apr 2009 Posts: 69 Location: Canada

There is no commit. The job has already run. Now we have to handle this.

Rohit Umarjikar · Posted: Sat Feb 28, 2015 3:04 am

Either correct the bad record or remove it and then restart and then investigate further with that record as to what and why happened as you do not want to compromise your SLA.

Marso · Posted: Mon Mar 02, 2015 7:58 pm

Is the VSAM file updated also, or only the DB2 table ?

As the job has abended and you had no commits, all DB2 updates have been rollbacked. You only need to correct the error (the data or the program) and rerun the job.

If you had had commits before the abend, it would be more difficult to resume the process (because you'd need to skip an unknown number of updates).

suraaj · New User Joined: 16 Apr 2009 Posts: 69 Location: Canada

Yes both VSAM and DB2 table have been updated.