× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



That's not a bad solution, but I was really hoping to figure out how to do 
the error trapping within.  I hate having to write wrapper CL programs and 
the other solution will fly better with our change management package.

Rob Berendt
-- 
"All creatures will make merry... under pain of death."
-Ming the Merciless (Flash Gordon)




"Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/13/2004 12:33 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
RE: Error trapping in RUNSQLSTM






Rob

After encountering similar scenario, I investigated several solutions and 
in
the end settled on this:

1) put all of your DROP statements in a separate member (only DROP
statements)
2) run that statements like this RUNSQLSTM ERRLVL(30)
3) run your CREATE and other statements in other member(s) using default
error level (10)

This scheme ignores any failures of any of the DROP statements but doesn't
ignore similar failures in the other, more relevant statements.

Any other solution (CL or otherwise) just introduced more complexity than 
I
wanted for this particular situation.

Elvis

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, January 13, 2004 11:02 AM
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.





_______________________________________________
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.