IBM DB2 load restart

pts.
Tags:
IBM DB2
OS/390
UDB for mainframe
z/OS
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

Answer Wiki

Thanks. We'll let you know when a new response is added.

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

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Sumithar
    Enrique Thanks for the reply. What you are saying is right, SHRLEVEL CHANGE does make it a sort of INSERT with COMMITs and such like so it is no longer an all or nothing deal like it was with phases. I am not sure I understand your suggestion vis-a-vis changing the discard dataset's disposition. How would that let the utility know where it left off in the SYSREC dataset? Regards
    0 pointsBadges:
    report
  • Evaldez
    Hi Sumithar: I think that, at this stage, DB2 keeps an internal counter of records. If you are cautious enough to keep the originally DISCARDed records, I think you're good to go. Give it a try ! Regards. Enrique
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following