DB2/400 – Why does each Physical File member has its own access path?

30 pts.
Tags:
DB/400
Physical File
why each physical file member has its own access path?

Answer Wiki

Thanks. We'll let you know when a new response is added.

Hi Ashish86

Good site:

http://publib.boulder.ibm.com/infocenter/iadthelp/v7r0/index.jsp?topic=/com.ibm.etools.iseries.pgmgd.doc/c0925076288.htm

Access path — is roughly equlivant to as SQL index.
If a physical file is keyed it will have two access paths –
the keyed path and the sequential path.

— Your question was about each member — IBM assumed that since seperate members were
created they would be accessed seperately. For native access – RPG/COBOL you can specify
the member(s) to use with the OVRDBF. The members selected will appear to have a single
access path. How this actually works or did they have a single path all along, I don’t know.

With SQL the member is selected with the CREATE ALIAS command but that is limited to one member.
A view could union the alias(s).

AS/400 developers have used members where SQL developers would have included another key field.

Phil

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following