RE: Error trapping in RUNSQLSTM

Rob,

Not what you wanted to hear, but the way I work around this is to create the
function the first time from source that doesn't have the DROP in it; then I
go back and add the DROP statement.

Charles


> -----Original Message-----
> From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx]
> Sent: Tuesday, January 13, 2004 12:02 PM
> To: MIDRANGE-L@xxxxxxxxxxxx
> Subject: Error trapping in RUNSQLSTM
> 
> 
> I have a source member that I want to use in RUNSQLSTM that 
> looks like:
> DROP FUNCTION ROUTINES/STRIPEMAIL;
> 
> CREATE FUNCTION ROUTINES/STRIPEMAIL (CHAR (512))
> RETURNS CHAR (100)
> DETERMINISTIC
> NO SQL
> RETURNS NULL ON NULL INPUT
> NO EXTERNAL ACTION ALLOW PARALLEL
> SIMPLE CALL
> EXTERNAL NAME 'ROUTINES/SRVEMAIL(STRIPEMAIL)';
> 
> However the function may or may not already exist.  If it 
> does not exist 
> the RUNSQLSTM aborts.  How does one do error trapping in 
> RUNSQLSTM?  Keep 
> in mind the following:
> DSPMSGD RANGE(SQL0084) MSGF(QSQLMSG)
> 
> Rob Berendt
> -- 
> "All creatures will make merry... under pain of death."
> -Ming the Merciless (Flash Gordon)
> _______________________________________________
> 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.
>