Re: Oddity with QUSRTVUI

Stu,

This sounds to me like the kind of thing that happens when there is a
*USRIDX-related data area on your system. I saw something like this once,
and it was because one of my team had gone online and searched the IBM
support docs and found out that if you create a data area called Q<whatever>
in QGPL, then the behavior of some IBM processing changes. and they'd done
that.

IBM is in the habit of providing 'backdoors' like this - undocumented (or
partially documented) ways to affect the behavior of certain bits of
processing, typically by creating an appropriately-named logical data area
in QGPL or QUSRSYS. You'd only know about it if you contacted IBM because
something didn't work they way you wanted it to.

So, check in QGPL and QUSRSYS and also check the IBM docs for *USRIDX
support issues and see if anything pops up.

Rory

On Mon, Aug 23, 2010 at 7:18 AM, Dennis Lovelady <iseries@xxxxxxxxxxxx>wrote:

It's quiet out there. Too quiet. :)

Well, I can say that I have not seen this effect on any release
before/including V5R3. We haven't moved beyond that. I will say that I
suspect this is caused by something other than standard, IBM-supplied
QUSRTVUI functionality.

But if you're accustomed to ENQ/DEQ, why would you use QUSRTVUI? Just
curious.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"A diplomat is a man who always remembers a woman's birthday but never
remembers her age."
-- Robert Frost

Just today noticed a weird thing that happens whenever I use QUSRTVUI
(Retrieve User Index Entries). I'm running v5r4.

Every time QUSRTVUI runs, a user space gets created in QTEMP. The
user
space, always named (for me anyway) QUS + 7 hex chars (like QUS000007B),
is
always the same size (8192 bytes) and always filled with nulls. In
different jobs it has different names but still in QTEMP always. It
happens
for all indexes, both fixed- and variable-length.


Using comparable MI instructions to access the index does not cause
this.


Ever seen such a thing? Maybe it's normal and I just never noticed it
before.