×
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.
On 2/1/2016 1:58 PM, Charles Wilt wrote:
Sounds like there's a mismatch in the field definitions.
That is not allowed when using KLIST or %KDS().
You don't have to worry about size when using literals in the a free format
SETLL/READEQ.
You don't have to worry about size type with %KDS either. Although since
it's way easier to define a *KEY data structure than to define all the
subfields for a program-described data structure, I think %KDS almost
always _does_ have an exact match.
But even in free format, if you just specify a field name or literal
without putting it in parentheses, it has to be an exact match.
chain field record; // requires an exact match
chain (field) record; // just requires a matching type
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.
midrange.com
