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



Charles,

<aside attitued="picked_upon"> Sigh! I started out to write what I
thought I remembered which might be helpful. Then I created a DDS file
to prove that I was, as it turned out, wrong. Then I went to the
infocenter to check a manual. Then I created and tested (STRSDA 3) a
format with 800 "both" fields. Infocenter is *still* loading. </aside>

DDS-defined dspf, right?

What is the device type where the error occurred?

Cheers,
Terry.

P.S.: Infocenter is *still* loading.


On Wed, 2008-10-08 at 16:59 -0400, Charles Wilt wrote:
All, I'm getting an error during I/O to a display file:


RNQ1251

Message . . . . : Permanent I/O error occurred in file FV011RP (C G D F).
Cause . . . . . : RPG procedure FV011R in program HLTHCURRLS/FV011R at
statement 11288 detected a permanent (not recoverable) file, session, or
device error. The session, device and/or program has been stopped. Examine
the major/minor return code value to determine the specific error that
occurred. If the major return code is 80 then a system or file error
occurred and programmer action is required to fix the problem. If the major
return code is 81 then a session or device error occurred, but use of
Technical description . . . . . . . . : The major return code is 80. The
minor return code is C0.

CPF5192
Message . . . . : Data sent to device QPADEV001X not valid. Negative
response code is 10050129.
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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.