Re: RUNSQLSTM drop/create alias error

I almost always run with COMMIT(*NONE) - have to is the files are not journaled. And ERRLVL has to be set high enough to allow errors when trying to delete something that is not there - so long as you KNOW you can tolerate that error.

-------------- Original message --------------
From: "Frances Denoncourt" <Frances.Denoncourt@xxxxxxxxxxxxxx>

Now, I'm trying to figure out what could have caused everything to go haywire.
I did attempt to run the RUNSQLSTM and forgot to use the "*NONE" parameter which
apparently defaults to *CHG. I didn't set ERRLVL. Could that have done
something?

"A commitment-control level is specified on the RUNSQLSTM command. If a
commitment-control level other than *NONE is specified, the SQL statements are
run under commitment control. If all of the statements successfully execute, a
COMMIT is done at the completion of the SQL statement processor. Otherwise, a
ROLLBACK is done. A statement is considered successful if its return code
severity is less than or equal to the value specified on the ERRLVL parameter of
the RUNSQLSTM command."

Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404

Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email

"Frances Denoncourt" 05/12/2008 10:40 AM

Buck,
I just tried your QMQRY suggestion. Wow. Works.
I think I found the utility you mentioned in the FAQ - article by you?

Thanks SO much for your help - everyone.



Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404

Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email

Buck 05/12/2008 9:51 AM >>>

Frances Denoncourt wrote:

In fact, I cannot use any of the SQL statements I used to run from a menu I

created a year or two ago. I thought that I had botched the update one that I
reuse, but that's apparently not the case since an insert one I have set up will
not work, now, either. I haven't used that one in quite some time.

As a further diagnostic aid, maybe you can try to run the same SQL
statements through iSeries Navigator? Or maybe make a QMQRY out of one
and try that?

CRTSRCPF QQMQRYSRC RCDLEN(92)
STRSEU and put your SQL statement in a member
CRTQMQRY
STRQMQRY

Is QMQRY works, look in the FAQ for an example of a utility that lets
one run any SQL statement from the command line. It uses QMQRY's
substitution variable capability...
--buck
--
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.

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