132 Display File oddness -- RPG400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: 132 Display File oddness
From: "Buddy McClean" <Buddy.McClean@xxxxxxxxxxxx>
Date: Wed, 13 Feb 2019 14:10:23 -0600
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@lists.midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.lists.midrange.com>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

Good Day

An interesting gotcha that kept me occupied for an embarrassing amount of time.

I have a SFL display file that uses 132 pos wide display. I have 2 sub files and 1 kept getting an error saying the PAGVAL() was too large. Even though they were almost identical.

After some time, I found that if there is a field that spans col 80, even if there are fields after that, it will give the PAGVAL halt.

So I changed the field to not be in that position and no halt. I suppose it is the boundary between an 80 col and 132 and may have control char.

Strange.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

132 Display File oddness , Buddy McClean
RE: 132 Display File oddness , Hiebert, Chris

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