Re: LF definition issue -- MIDRANGE-L

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

The UNIQUE characteristic of another LF or of the based-on PF does not preclude the creation of the LF with its own specific [duplicate key ordering] characteristics. The LF should either share or not share a compatible non-unique access path rather than fail to create. That is, I do not expect any unique key specifications outside of that LF DDS would or should have any impact. A combination of both LIFO and UNIQUE file level keywords within the one LF DDS source would fail the CRTLF with CPD7640 "Indicated keyword not allowed with FIFO keyword."

Regards, Chuck

On 01-Sep-2011 10:40 , Alan Shore wrote:

From what I can remember FIFO is to be used when there are duplicate
keys - non-unique keys
In your physical file (or any other logical files) have you
specified UNIQUE
If yes, then its telling you that there is some conflict
If no - sorry

Mark Murphy on Thursday, September 01, 2011 1:21 PM wrote:

Anyone know why the FIFO keyword in this LF definition would give
me problems? I searched the manual, and can't find anything that
applies.

<<SNIP LF DDS with FIFO file level kwd>>

The error message is:
* CPD3245 40 1 Message . . . . : The duplicate
key ordering attribute is not valid.

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.