Re: Permanent I/O Error occured to DSPF

Device class . . . . . . . . . . . : *VRT
Device type . . . . . . . . . . . : 3477
Device model . . . . . . . . . . . : FC

Now interestingly enough, I get the error when using IBM's Client
Access; however if I use Powerterm, I don't get the error. The device
description is the same in either case.

Ah, I have duplicated that. My working emulation was xt5250. The
challenge here was to find a Client Access CD <grin />.

Speaking of STRSDA OPTION(3) ... Does your dspf fail in the context
of SDA? If the display works here, it suggests that the problem is in
the data which the program is sending.


Along the way, I provoked message SDA2801 which says in part

The local work station can have up to 126 input capable fields.

This contradicts both my memory and the current experiment, which
demonstrate a limit of 256 input fields.


The message says furthermore

This limit is reduced by one for each occurrence of the
DSPATR(OID) or the DSPATR(SP) keywords.

I remember, however, that each input field not in order left-to-right
and top-to-bottom counts twice against the limit. Of course, I could
be remembering in technicolor. Do these extra counts bring you any
closer to an explanation of the problem?


Is the question still of interest? If so, can you share the dspf? I
can try to ressurect some old HACL code which may (or may not, of
course) shed some light on the problem.

Cheers,
Terry.

Device class . . . . . . . . . . . : *VRT
Device type . . . . . . . . . . . : 3477
Device model . . . . . . . . . . . : FC

Charles

On Thu, Oct 9, 2008 at 11:00 AM, Terrence Enger

<tenger@xxxxxxxxxxxxxxxx> wrote:

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

,