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



Nathan,
By native I don't mean embedded SQL. I mean RLA via RPG. This is the way the project started and it performed well for the dozen SQL statements that were converted to RPG but we want to avoid having to convert.
Actually, I run each SQL statement from RPGLE via embedded SQL using an EXECUTE IMMEDIATE statement.
We already run this RPGLE via several server jobs waiting on a *DTAQ but that still takes too long.
I don't know how the SQL Server interface operates but if it performs then I may attempt sending the work file request there from i5.
The best I've managed so far on i5 is it reduce it from 60 secs to under 30 by submitting it to a batch job that runs a C program I created to employ the multi-threading API provided by IBM (beats using multiple server threads)

Peter.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Thursday, 30 May 2013 9:39 a.m.
To: Midrange Systems Technical Discussion
Subject: Re: Performance question and SQL SERVER

Hello Peter,

It is problematic to convert these 300 to native RPGLE which I know
would perform well.

What do you mean by native RPGLE? Using RLA? Using embedded SQL?

 However, if the same transaction is repeated then the same result can
be returned in  about 5 seconds.

What if the Job running the SQL were left running? Say waiting for a request to be placed on a queue?

he can easily create a script that runs all 300 statements on

SQL server in just a few second with no performance problems.
Why is that?


Not sure. Could he be using an asynchronous interface, which returns quickly, even though SQL Server continues to crunch in the background? I used that trick in the past.

-Nathan

--
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 correspondence is for the named person's use only. It may contain confidential
or legally privileged information, or both. No confidentiality or privilege is waived
or lost by any mistransmission. If you receive this correspondence in error, please
immediately delete it from your system and notify the sender. You must not disclose,
copy or rely on any part of this correspondence if you are not the intended recipient.
Any views expressed in this message are those of the individual sender, except where
the sender expressly, and with authority, states them to be the views of Veda.
If you need assistance, please contact Veda on either :-
Australia 1300-762-207 or New Zealand +64 9 367 6200

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.