Re: DSPDBR via SQL view

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Nice!

On 6/10/2020 5:33 PM, Mark Waterbury wrote:
>   Try using QADBLDEP instead.
>
> That's a LF over QADBFDEP ... they are shipped with *PUBLIC *USE authority.
>
>      On Wednesday, June 10, 2020, 5:29:01 PM EDT, smith5646midrange@xxxxxxxxx <smith5646midrange@xxxxxxxxx> wrote:
>   
>   Not authorized to object QADBFDEP in QSYS type *FILE.
>
> This is for a program I am going to load on client's machines so it can't
> adopt authority or any of those types of work arounds that would give me
> authority.
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steve
> M via MIDRANGE-L
> Sent: Wednesday, June 10, 2020 5:24 PM
> To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
> Cc: Steve M <txpenguin1@xxxxxxxxxxx>
> Subject: RE: DSPDBR via SQL view
>
> What you have below looks like is should work, doesn't it?
>
> Select *
>  From qsys.qadbfdep
> Where dbffil = table name
>
> (you can add 'where dbflib = schema/library' if you are just looking at one
> schema/library at a time)
>
> That should then list each index/view/logical in column dbffdp.
>
> What's missing in that which you still need?
>
> Looks like that's it....
>
> Steve Meisinger
>
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
> smith5646midrange@xxxxxxxxx
> Sent: Wednesday, June 10, 2020 15:54
> To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: RE: DSPDBR via SQL view
>
> Thanks everyone for all of the ideas but the question was about using an
> existing IBM view and not how to create my own.
>
> It sounds like such a view does not exist so I will continue to do things
> the hard way.
>
>
> -----Original Message-----
> From: smith5646midrange@xxxxxxxxx <smith5646midrange@xxxxxxxxx>
> Sent: Monday, June 8, 2020 10:26 PM
> To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: RE: DSPDBR via SQL view
>
> I was referring to using it in an sql statement as in
>
> select * from qadbfdep
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Kevin
> Wright
> Sent: Monday, June 8, 2020 10:23 PM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: RE: DSPDBR via SQL view
>
> DSPDBR QADBFDEP?
>
> Otherwise there may be an infinite recursion problem.
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
> smith5646midrange@xxxxxxxxx
> Sent: Tuesday, 9 June 2020 12:19 PM
> To: 'Midrange Systems Technical Discussion'
> <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: DSPDBR via SQL view
>
> Does anyone know if there is an SQL view that will provide all of the
> logicals and indexes built over a physical file?  Basically I'm looking for
> an IBM view that gives me what DSPDBR to an outfile gives me.  I know there
> is a file out there named QADBFDEP but it is locked down by default and I
> need something accessible by a PGMR or USER profile.
>
>
>
> On a somewhat related subject, is there any "command to view" cross
> reference documentation anywhere?  For example: DSPFD *MBRLSIT =
> SYSPARTITIONSTAT.  It is hard to find which view you need to use when you
> don't know the name of it.  If you know the command, this would point you to
> the correct view or views.
>
> --
> 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.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com
> --
> 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.
>
> Help support midrange.com by shopping at amazon.com with our affiliate link:
> https://amazon.midrange.com
>
>
> --
> 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.
>
> Help support midrange.com by shopping at amazon.com with our affiliate link:
> https://amazon.midrange.com
>
> --
> 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.
>
> Help support midrange.com by shopping at amazon.com with our affiliate link:
> https://amazon.midrange.com