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



Here is the code I am refering to. The user may want to search for %beauty%
in the name field of the client file. The client file has about 1/2 million
records. So this may take a while. This also needs to be done interactive
since they want what they want when they want it :)

Dynstm is built by user requirements. So it can be more complicated.

Dynstm = select * from clientfile where upper(name) like '%ZONE%'
and city = 'NY' fetch first 25 rows only

exec sql set option datfmt=*usa;
exec sql prepare s2 from :dynstm;
exec sql declare c2 cursor for s2;
exec sql open c2;
exec sql fetch c2 into :thefileds;
dow sqlcod = 0;
blah blah blah
enddo

The user will hit enter and can wait as long as a minute. So, in turn, they
close out the client access window which really makes a mess.




-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of rob@xxxxxxxxx
Sent: Friday, January 18, 2008 8:57 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: Interupting an rpg sql search

I take it you're talking about the RPG we all know and love and not some
client/server version like VARPG?
I don't think you'll find a whole lot on "event programming" with RPG or
RPGLE. That's what might interrupt a long running process.
You're pretty much restricted to ENDJOB or SysReq. (Typically mapped to
Shift-Esc on a PC keyboard). Normally you'd use option 2. However, on
some long runners like that, I've had to use option 90 to force a sign off
because option 2 would tell me something like it couldn't be halted during
the middle of some critical operation or some such thing.

I'd really evaluate that SQL statement. Traditional wisdom is to do a
STRDBG UPDPROD(*YES) and do not specify a program name. After the program
is done you can do a DSPJOBLOG and you'll see tons of SQL stuff in there
to look at.

Another consideration is CHGQRYA QRYTIMLMT(15)

After doing a little poking around, you might post the SQL statement and
we can see if you really flubbed it up. Hey, even I've made mistakes. :-)

I don't suppose there's some way to throw a halt indicator? (Ducking and
running.)

Rob Berendt

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.