RE: [ EXTERNAL ]Re: When is a View not a View

Martijn and All,

These views are all in the same library and All looked normal in the sys catalogs.

UPDATE:
The vendor for my new product sent me an updated Jar file last night and we got it loaded this morning. It has addressed the issue within this toolset.
I do have some open questions as to what they did to make this work, and if I get an answer I'll report back here.

Like I had noted this is also happening in the ODBC driver, not associated with this vendor's product and so, my feeling is that there is something, somewhere that is defining these objects a bit differently. But, I'm not finding it in any of the QSYS2 files I've looked at thus far.

But it's working where I need it working, and so I can continue our migration process.

Thanks to all with your ideas!

Ken



-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Martijn van Breden
Sent: Thursday, December 19, 2024 2:01 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [ EXTERNAL ]Re: When is a View not a View

[You don't often get email from m.vanbreden@xxxxxxxxxxxxxxxxxxxxxxxxxx. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]

Hello Ken,

That's pretty peculiar... a couple of things pop up in my head:


1.
Are these views all defined in the same library/schema?
2.
If not, are all libraries defined as schemas, so with their own views on the catalog?
3.
Do you see any particular differences in their definitions when you query the views in the system catalog (qsys2.sysviews and qsys2.sysviewdep)


Kind regards, Met vriendelijke groet,



Martijn van Breden

lead software architect