×
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.
Another tidbit I left out:
The SQL in the program is actually referencing CDRPKGP. When the program is ran in "daily" mode it overrides to CDRPKGDAYP, so that's just another piece in the puzzle.
Mark W contacted me off list suggesting doing a PRTSQLINF against my service program with the embedded SQL.
It's referencing CDRPKG05 which is what I'd expect. I would also expect it to use an index called CDRPKG06 (which is used when I run the sql interactively).
However I can see the program running right now and it is not using CdrPkg05 (or CdrPkgDay5 which is what the daily version would use).
UPDATE CDRPKGP SET APPLIEDAMT = APPLIEDAMT + : H , APPLIEDQTY = APPLIEDQTY + :
H , APPLYSEQ# = ( CASE WHEN APPLYSEQ# = 0 THEN ( SELECT MAX ( APPLYSEQ# ) + 1
FROM CDRPKGP WHERE EDITID = : H AND CDRSEQ# = : H ) ELSE APPLYSEQ# END ) WHERE
EDITID = : H AND CDRSEQ# = : H AND ROWID = : H
SQL4021 Access plan last saved on 08/13/15 at 13:32:37.
SQL4020 Estimated query run time is 0 seconds.
SQL4017 Host variables implemented as reusable ODP.
SQL4007 Query implementation for join position 1 table 1.
SQL4008 Index CDRPKG05 used for table 1.
SQL4026 Index only access used on table number 1.
SQL4011 Index scan-key row positioning used on table 1.
SQL4007 Query implementation for join position 2 table 1.
SQL4008 Index CDRPKG01 used for table 1.
SQL4026 Index only access used on table number 1.
SQL4011 Index scan-key row positioning used on table 1.
SQL4006 All indexes considered for table 0.
Kurt Anderson
Sr. Programmer/Analyst - Application Development, Service Delivery Platform
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kurt Anderson
Sent: Thursday, August 13, 2015 4:14 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: New Advised Index not used
Visual explain of me pasting in the SQL that I was running in STRSQL shows the indexes (there are actually two, despite my message talking about one) are being used as I would expect.
Kurt Anderson
Sr. Programmer/Analyst - Application Development, Service Delivery Platform
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Luis Rodriguez
Sent: Thursday, August 13, 2015 4:08 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: New Advised Index not used
Kurt,
Have you tried to run your SQL under Visual Explain? I seem to have read that it (VE) should be used instead of STRDBG.
Regards,
Luis
Luis Rodriguez
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.