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



<snip>
We have the need to run inquiries across years. I must be brain-dead
today,
because I can't come up with a *good* solution to access all the members
of
the physical file. One minor detail - because of the way historical
data is
stored, we currently have 34 members in the physical file. Running
CRTLF
FILE(QTEMP/MVGLDET99) DTAMBRS(*ALL) OPTION(*NOSRC *NOLIST) results in
the
following job log:
File MVGLDET99 created in library QTEMP.
Number of members not valid for file MVGLDET99.
Member MVGLDET99 not added to file MVGLDET99 in QTEMP.
Secondary help for the second message has:
Message . . . . : Number of members not valid for file
MVGLDET99.
Cause . . . . . : The requested operation was not performed for
file
MVGLDET99 in library QTEMP because the number of members is not valid.
When
adding a logical file member, with either the CRTLF command or the
ADDLFM
command, the number of member names specified on the DTAMBRS parameter
must
be 1 to 32. When a join logical file is created, the number of member
names
specified must be 1 to 256. When a physical file is created, the
number
of
members must be
1.
Recovery . . . : No recovery. Report the problem (ANZPRB
command).
I can see why this failed - 34 is not in a range of 1-32.
</snip>

How about an SQL Statement with a Union?

Depends on how many records you are getting out. You would have to do
OVRDBF to unique names or create Alias for the members you want.



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.