Re: SETLL question -- RPG400-L

Subject: Re: SETLL question
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Tue, 2 Feb 2016 21:31:42 -0500
List-archive: <http://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

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

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

CLP program to CLLE program. , JRusling
RE: SETLL question , Rich Marion

This mailing list archive is Copyright 1997-2025 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.