|
Hans, Thanks for you reply, at least it makes thinks understandable. Cheers.... Loek. ----- Original Message ----- From: "Hans Boldt" <boldt@ca.ibm.com> Newsgroups: gmane.comp.lang.as400.rpg To: <rpg400-l@midrange.com> Sent: Thursday, May 16, 2002 5:13 PM Subject: Re: Different results *like define opcode RPG/400 versus RPG/IV > L. Maartens wrote: > > However, if you say ' coding LIKE on a D-Spec defines the field with the > > same format as the original', does this refer to the field when that is > > defined in the DDS as zoned, or to the field as defined internally in the > > program (packed), in case such a field is not defined as a data structure > > subfield? > > OK, this falls into the category of how numeric fields on I-Specs > are defined. Consider the possibility that a numeric field may > occur in several records, each with a different external format. As > far as RPG is concerned, that's fine. And if there is no explicit > definition of that field within the program, RPG will automatically > define the field internally, and define the format as packed decimal. > > If you explicitly define the field internally (as a standalone > field, a subfield, or whatever), then that definition takes > precedence. LIKE definition always refers to the internal > definition of the field. > > > > > > > > > > _______________________________________________ > This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list > To post a message email: RPG400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l > or email: RPG400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/rpg400-l. >
As an Amazon Associate we earn from qualifying purchases.
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.