Try changing your severity level and commitment control.
RUNSQLSTM SRCFILE(MYLIB/FOO)
SRCMBR(BAR)
COMMIT(*NONE)
ERRLVL(20)
I believe ERRLVL(20) will ignore the drop statement when it doesn't exist.
-Tom Stieger
California Fine Wire
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Friday, April 29, 2011 2:27 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Replacing objects if they exist: Another SQL-newbie UDF question
Suppose I want to create an object that might already exist, replacing it if it does, from a source member executed with RUNSQLSTM.
I already noticed, when creating, then labeling, views, that if the LABEL ON statement fails, the system apparently rolls beck the CREATE TABLE as well.
So I seem to be in a double-bind: if I put a DROP statement at the beginning of the member, before the CREATE VIEW, CREATE FUNCTION, or CREATE <whatever> statement, and the original object is not there to be deleted, I would expect the whole thing to fail, without anything getting created.
And I already know empirically that if I don't DROP an already-existing object that I'm creating, the CREATE fails.
Is there a way to make this work without having to use two separate RUNSQLSTMs on two separate source members?
--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
