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



Hi Rick -

why is it a rule that when building a logical file, the physical you are
building it over must be the first instance of that file in your library
list?
That's not the rule.  The rule is that the physical file on DTAMBRS keyword
must be also be one of the physical file(s) specified in the DDS.  That's
what CPF7356 is trying to tell you.

Apparently you did not specify a library name in the DDS, so the logical is
built over the physical found via the library list.  On the command you are
telling the system to put a member in the logical file based on a member in
a different physical file.

It doesn't matter if you specify library names in the DDS and/or the
command, or whether you use the library list.  What matters is that you
must end up with the same physical file in the same library from both the
source and the command.

So you must first decide what physical file (or files if it is a join
logical or multi-format logical) the logical is to be built over.

Then do a CRTLF making sure that the correct physical will be located,
either by specifying the library name in the DDS, or by not specifying it
in the DDS and making sure it is highest in the library list.

On the DTAMBRS keyword, do the same as what you did for the DDS ... either
specify the library name or use the library list.

Ken
Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone in their right mind.



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.