Trap SQLCODE from RUNSQLSTM

25 pts.
Tags:
RUNSQLSTM
SQL
I have a RUNSQLSTM that updates a table. When it hits a duplicate, it quits and returns SQL9010. What I want it to do is just skip the step that got a duplicate and move on. Is there a way to do this?

Software/Hardware used:
Iseries

Answer Wiki

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

Use an EXCEPTION JOIN to only insert/update those records that do not already exist in the table.

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
  • TomLiotta
    Is this a set of updates? Or is it a single update each time you run RUNSQLSTM? -- Tom
    125,585 pointsBadges:
    report
  • khalon
    sorry to be so long in replying.. the problem still exists.
    It is a single update to add a row to a table.  As it could already be in the table,  I just want to ignore duplicates and not return SQL9010 which causes the proc to fail.
    25 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:

Share this item with your network:

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