Dave:

Is this what you are trying to find out - which logical files are sharing
access
paths instead of building new ones?

You can find out which files are sharing access paths by checking the file
description.

DSPFD 
FILE(mylib/lfile*)
TYPE(*MBR)
FILEATR(*LF)

If the access path is being shared by another logical file, you'll see on
the
display "Implicit Access Path Sharing: Yes". If you have sent the DSPFD to
an
outfile, the field name is MBISMT, and sharing is indicated with an "I".

In addition, if the access path is implicitly shared, you can see which
access
path is being used. On the display, it is presented as "File Owning Access
Path:
mylib/lfile2". In the outfile, the fields are MBISL for the library and
MBISF
for the file name of the File Owning Access Path.

Regards, 
Debbie Gallagher

--------------------------------
Original Message
--------------------------------
Subject: DSPFD and share paramter

I have a library that contain 1000+ files (PF & LF). I would like to find
out what the share access path is set to for each file with out printing
each file and searching the output.

I have tried doing a DSPF with only *BASATR and output to a data base
file. The share parameter is in the database file layout but is empty. 

Is this happening to anyone else?

Would someone suggest a way that I might get the information I need?

Thanks
Dave Willenborg

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.