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



Yes....our command line is:

DROP PROCEDURE LIB.PROCNAME;

CREATE PROCEDURE LIB.PROCNAME (commands)

We're running v6r1m0 so I would assume it would have these commands, correct?



-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, September 10, 2015 10:52 AM
To: Midrange Systems Technical Discussion
Subject: Re: Dropping SQL Procedures in iNav

Are you simply using "DROP PROCEDURE xxx"? Just wondering if it's an overloading feature or some such thing.

Does your version of the OS support "CREATE OR REPLACE"?

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Brian Piotrowski <bpiotrowski@xxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 09/10/2015 10:33 AM
Subject: Dropping SQL Procedures in iNav
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Good morning all,

We seem to have some quirky behavior with our DROP PROCEDURE function in
"Run SQL Scripts" within iNAV. What we're trying to do is delete a
procedure and then recreate it. The way we have tried to do it is to
right-click the procedure in iNav, select "Generate SQL", edit the
procedure and execute it to recreate it. When we use "DROP PROCEDURE xxx"
it does not drop the procedure and complains the procedure already exists.
When we use "DROP SPECIFIC PROCEDURE xxx" it will drop the procedure and
go through the motions of recreating it, but when you refresh the
procedure list it does not exist and you need to rerun the SQL script
(minus the DROP command) to get it recreated.

Are we entering the command wrong? Should we be entering something else
to drop the procedure before it is recreated?

We are putting this command just before the "CREATE PROCEDURE" command in
the SQL script, so logically we thought it should perform the DROP and
then execute the CREATE function.

Any thoughts would be appreciated.


Thankee-sai!

/b;

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Brian Piotrowski
Manager - I.T.
Simcoe Parts Service, Inc.
Ph: 705-435-7814 x5995
Fx: 705-435-5029
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
http://www.simcoeparts.com<http://www.simcoeparts.com/>

Please consider the environment. Don't print this e-mail unless you really
need to.

The information contained in this communication is confidential and
intended only for the use of those to whom it is addressed. If you have
received this communication in error, please notify me by telephone
(collect if necessary) and delete or destroy any copies of it. Thank
you!


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.