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



Sorry that is an old program the we got from someone years ago.
We have a program that was created decades ago call dbr that shows all logicals and the physical no matter which one is keyed.
Example
Data Base Relations

File Library Atr
SYSCOLUMNS QSYS2 PF
* COLUMNS QSYS2 LF
COLUMNS SYSIBM LF
SQLCOLUMNS SYSIBM LF
USER_STG SYSIBMADM LF
USER_STG QSYS2 LF

The * is the logical that was selected by.
I use it all of the time.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of VERNON HAMBERG Owner via MIDRANGE-L
Sent: Tuesday, January 2, 2024 2:51 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Cc: VERNON HAMBERG Owner <vhamberg@xxxxxxxxxxxxxxx>; midrange-l@xxxxxxxxxxxxxxxxxx
Subject: RE: Get PF for LF

Caution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, contact your IT Department



Hi Troy


I don't see DSPFLD on a machine I have full authority on. I had recommended DSPFD below - is that what you meant?


If not, I'm curious to know what DSPFLD is and where it comes from - TAA Tools, perhaps?

I'm also curious - does the tool you speak of tell you which tables an LF is based on? DSPFLD sounds like DSPFFD, I also googled for DSPFLD and found a 30-year-old QMQRY thing, as well as a toolset called Projex4i and some other stuff - had never heard of Projex4i, anyone know it? Also something suggested by Nick Litten based on the QADB* tables - I have to give the same caveat - IBM locks those down pretty well. I just did a little test, first on a machine where my USRCLS is *SECOFR - I can do anything, of course. Then on our company system - DSPPFM QADBXREF gave me a not authorized message. So did trying to take the SQL statement that SYSTABLES is - over QADBXREF and another QADB* table - and rightfully so.


Many in these lists have elevated authority - be careful about recommending things you can just do - same challenge if you're a software developer and test everything with your special profile, not what a customer will be using.


Regards
Vern


On Tue, 2 Jan, 2024 at 11:27 AM, Troy Foster <tfoster@xxxxxxxxxxxxxxxx> wrote:


To: midrange systems technical discussion

Dspfld on logical.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx>> On Behalf Of VERNON HAMBERG Owner via MIDRANGE-L
Sent: Friday, December 29, 2023 2:09 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: VERNON HAMBERG Owner <vhamberg@xxxxxxxxxxxxxxx<mailto:vhamberg@xxxxxxxxxxxxxxx>>; midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Get PF for LF

Caution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, contact your IT Department



Hi Justin


The QADB* PFs and LFs are severely restricted - IBM do not want them accidentally corrupted. If you are able to work with them, you would seem to have some elevated level of authority to them. I think it is strongly advised not to use them in programs that regular users will be running

The JSON in the recent SYSFILES can be used nicely by using the JSON_TABLE function, I would think. But if you are on pre-7.5 release, I recommend the DSPFD thing - it's been around forever, safe, reliable. And you can't trust that IBM won't put tighter reins on these "system" files.


The reason I know is related to a tool I once wrote that used the QADB* files and failed when lower authority levels tried to run things.


Cheers
Vern


On Fri, 29 Dec, 2023 at 1:13 PM, Justin Taylor <jtaylor.0ab@xxxxxxxxx<mailto:jtaylor.0ab@xxxxxxxxx>> wrote:


To: midrange-l

Both QSYS2.SYSFILES and QSYS.QADBLDEP give the answer, but SYSFILES returns it as JSON. I prefer not to parse JSON if I don't have to.

Thanks guys!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx><mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx><mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>>
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx><mailto:support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx>> for any subscription related questions.

.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.

.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.


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.