Question

IBM DB2 load restart

UDB for mainframe, z/OS, OS/390, DB2

I am faced with a situation where my SYSREC file for a LOAD could potentially have duplicates. If there are dupes then I have a step that follows that analyses the SYSDISC file,so my DISCARDS is set to 0.

If for whatever reason the utility blows up (ran out of space, whatever) and I choose to RESTART it I want it to skip processing those records in the SYSREC that were already inserted successfully.

But in my testing I am finding that the utility clutters up my SYSDISC with the records that were inserted before the abend (which I don't want to process) in addition to the ones caused by there being duplicates to begin with (which i do want to process).

Is there a way to force the utility to RESTART in such a way that it will start reading teh SYSREC only from the last commit? I tried UTILID='RESTART(CURRENT)'- no good.

I have RESUME YES, SHRLEVEL CHANGE.

Thanks a lot for your time

I always believed that IBM utilities worked as a set of phases chained logically and that they, either completed the tasks(or phases) or not at all.

With this in mind LOAD's SHRLEVEL CHANGE support somehow changed this concept in that it resembles me more a program issuing SQL INSERTs than a batch utility that inserts rows massively.

Stupid as this might sound. Have you tried with a differente DISP option for the SYSDISC DD defining a new dataset on the restarted job?

Just my humble hint.

Regards.
Enrique