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