Re: Unicode, %status and *STATUS -- RPG400-L

Good News Everybody!

The new search engine is LIVE!

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

Subject: Re: Unicode, %status and *STATUS
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Mon, 26 Mar 2018 15:33:31 -0400
List-archive: <https://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: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

On 2018-03-25 11:04 AM, Joep Beckeringh wrote:

We're incorporating more Unicode fields in our database. But in some cases we still have to maintain a 5250 user interface to these data. So we want to signal to 5250 users when we encounter untranslatable characters in a field. For that we use program status; status is 50 when conversion results in substitution.

If you add keyword CCSIDCVT(*EXCP) to your H spec, the status code when a conversion results in substitution will be exception-status 452 rather than non-exception status 50.

It might be easier to use MONITOR to deal with an exception rather than checking for status 50.

Follow-Ups:

Re: Unicode, %status and *STATUS , j . beckeringh

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.