Re: Alternating arrays as D-spec -- 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.

Subject: Re: Alternating arrays as D-spec
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Mon, 2 Nov 2015 08:33:29 -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 10/30/2015 9:50 PM, Scott Klement wrote:

Looks like Barbara didn't notice that there's an unused byte (positions
15, 22, 29, etc) between the array elements in your I-specs.

Oops, you're right, I didn't notice. I did check whether there was anything between q1 and c2, but I didn't think of checking between c1 and c2.

Rather than hardcode the overlay position, I think I'd add another char(1) subfield between c1 and q1. But actually I prefer your rec.elem(1).q1 way.

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.