× 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.



Rory,

It's actually a Plex generated app, the compile listing is 600+ pages
and the dump is 200+.

There's lot's of program to systems fields to control the DSPATA or
the screen fields, but I don't know at a glance if the data in there
is valid or not.

I'm getting the error on a READ of a title record on the screen.
Which only has a few fields. I thought perhaps the problem was in
another region, and was just not manifesting itself till the READ due
to DFRWRT(*YES). So I tried changing that, but I still only get an
error on the READ.

Charles

On Wed, Oct 8, 2008 at 5:12 PM, Rory Hewitt <roryhewitt@xxxxxxxxx> wrote:
Charles,

A format table overflow will occur if you have more than 256 input fields on
the screen. This is *not* the problem unless you're using the DSM API's to
build screens.

Almost certainly, you're trying to display data which is < x'40'. Check your
data fields to see if some 'bad' data has crept into your database - that's
the most likely reason. Alternatively, run the program in debug and check
the data in all fields just prior to the EXFMT. Perhaps it's invalid data in
a program-to-system field (if you're using them).

BTW, technically, it's not *all* characters < x'40' which cause problems -
it's just *certain* characters < x'40' - those which are defined as 5250
data stream control characters, such as x'1D', for instance. So x'1F'
displays as a reverse-image cursor, for example.

Rory

On Wed, Oct 8, 2008 at 1:59 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

All, I'm getting an error during I/O to a display file:


<snip>
Cause . . . . . : The condition was caused by the program output data
containing below hex 40 or too many input fields. More information on the
negative response code can be found in either the IBM 5494 Remote Control
Unit Functions Reference (under negative responses) or the SNA Formats
Manual (under SENSE or LUSTAT codes). Invalid data (below hex 40) may
have
occurred in one of the following ways:
Invalid parameter data passed in variable to command language program.
Variable is used in SNDPGMMSG command. Command fails when data is
displayed.
Hexadecimal characters below hex 40 entered into TEXT parameter of
create
command. Display command for object fails when object parameters are
displayed.
Data base record containing invalid data displayed by the application
program.
Failure to specify RSTDSP(*YES) when alternating displays from more than
one file to the device, where both files have input fields.

I've looked at the dump, I don't see any invalid characters (< x'40').

I looked up the sense code and it says:
10050129 = Format table overflow

Does anybody have an idea of what's wrong?

Thanks!

Charles Wilt
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
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 thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.