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



Lim,

Why not use the record format name? You can find it in this location in the
file feedback structure:

RcdFmt 261 270a

Patrick

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Lim Hock-Chai
Sent: Tuesday, February 26, 2008 3:03 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: How to get the Physical file member name when reading a
logicalmember that is based on multiple physical members

Hello,
I need to know the actual physical file member name of record that being
read from a logical file member that is based on multiple physical members.
I did some research and found that position 395-396 in INFDS seems to be
what I needed. It seems to contain the actual physical-file-member-number
of the currently read logical file record.
The question is how can I translate this member number into the actual
member name? The only way I know of is to do DSPFD to a temporary out file
and do a chain to this temp file using member number as the RRN.
This sound ugly.




--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.