Re: Multi- Occurrence Data Structure -- 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: Multi- Occurrence Data Structure
From: Adam Glauser <adamglauser@xxxxxxxxxxxx>
Date: Wed, 12 Dec 2007 12:37:04 -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 AS400 / 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/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

James Lampert wrote:

MOVE is useful, as it is frequently useful to assign a string in such a way that any padding or truncation happens on the left, and I know of no other construct, in RPG or any other HLL, that does this. (CPYBRA and CPYBRAP do it in MI).

Unless I've missed your meaning, EVALR allows just that.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Multi- Occurrence Data Structure , James Lampert
RE: Multi- Occurrence Data Structure , Joe Pluta

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.