EXTNAME behavior using *KEY in SQLRPGLE -- RPG400-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.

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
--
[ Picked text/plain from multipart/alternative ]
I am trying some of the new features of V5R2 and have come across something
I can not explain.

If I understand the documentation correctly I should be able to code an
externally described data structure and define only the key fields.  This
data structure could then be used as the key list for file operations.
Using the definition below the SQL pre-compiler choked on the external
definition.  When I removed the *KEY parameter it was happy.  Using the
LIKEREC key word with *KEY seems to work fine.  Is there something I am
missing?  Has anyone else seen similar behavior?

Definition:
d klCOPDEF01    e ds                  ExtName(COPDEF01: *Key)

Pre-compiler error:
MSG ID  SEV  RECORD  TEXT
SQL1001  30      85       External file definition for COPDEF01 not found.

Rick Chevalier
Sr. Programmer Analyst

(817) 525-7178
rick.chevalier@americredit.com

--

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.