AW: Replacing objects if they exist: Another SQL-newbie UDF question

If you are already on release 7.1 it is possible to use CREATE OR REPLACE
(service) program objects such as triggers, stored procedures or UDFs and
Views.
CREATE OR REPLACE FUNCTION FunctionName (Parameter ....)
...



Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"


-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von James Lampert
Gesendet: Friday, 29. April 2011 23:27
An: Midrange Systems Technical Discussion
Betreff: 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