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



What naming conventions SQL or System Naming are you using?
When using SQL Naming conventions the library list is ignored.
Or did you set a default schema by executing the SET CURRENT SCHEMA command.
If so the library list is ignored (even though System Naming conventions are
used).

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)


-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxx> On Behalf Of
MichaelQuigley@xxxxxxxxxx
Sent: Freitag, 24. August 2018 14:17
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: STRSQL strange behavior when running under STRDBG

----- Message from Robert Wenzel <robert.wenzel@xxxxxxxxx> on Tue,
21 Aug 2018 13:22:51 -0400 -----

To:

rpg400-l@xxxxxxxxxxxx

Subject:

STRSQL strange behavior when running under STRDBG

Has anyone encountered this?

I started a debug session for an RPGILE program. The program calls a
CLLE
program which creates a work file in QTEMP and then does an OVRDBF
command. I set a breakpoint in the RPGILE program after the call to
the CLLE program. At the breakpoint I accessed the command line (ESC
key).
Then issued STRSQL. When I issued the statement "select * from
qtemp/workfile" it returned the rows created by the application. I
wanted
to make a copy of the data in my library. To make sure I didn't have
the
file already in my library I issued "select * from mylibrary/workfile"
expecting to get an error message but it returned the exact same rows
as the data in QTEMP. I then exited the SQL session and issued WRKOBJ
mylibrary/workfile and no results returned.

So, what's up with running STRSQL under STRDBG? Does the OVRDBF
statement
in the CLLE program ignore the explicit reference to mylibrary and
returning the data from the QTEMP file instead?


Hi Robert,

I tried a quick experiment on our soon to be retired V7.1 system and on our
new POWER9 system running 7.3. I see the same results you're seeing whether
I'm in STRDBG or not. It would appear that SQL does ignore the library
qualification when an OVRDBF exists. I only tried at the library level. If I
had more time, I would open a PMR to verify the behavior--to which the
probable answer would be "work as designed." But it would be nice to verify
that.

Oh, I also tried it with changing my current library to *CRTDFT. That had no
impact on the results either. I did not try different options on the
OVRSCOPE--I only used OVRSCOPE(*JOB).

Michael Quigley
Computer Services
The Way International
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD


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.