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



There used to be a limitation of 128 input capable fields on a display (not
sure if this is still the case).  I don't recall what error was sent.  You
might also try it on a different device in case you are having a hardware
error on the device.

-----Original Message-----
From: RReddy@medicalartspress.com [mailto:RReddy@medicalartspress.com]
Sent: Wednesday, 10 January, 2001 6:56 AM
To: RPG400-L@midrange.com
Subject: Re: MCH0601



I took the original display file & re-compiled my program.. I have no
errors at all.

My question is why would adding a simple field to the subfile would give me
error???.

Anyways i really appreciate all your help.

You guys are great.

Thanks.
Reddy






Jim Langston <jimlangston@conexfreight.com>@midrange.com on 01/09/2001
05:01:38 PM

Please respond to RPG400-L@midrange.com

Sent by:  owner-rpg400-l@midrange.com


To:   RPG400-L@midrange.com
cc:

Subject:  Re: MCH0601


CPF5257 means there was a failure on a read or write operation, and to
see the previous messages in the job log.

When you see this screen again, with the help, hit the F10 key (jog log)
then hit F10 again to see details.  You usually have to scroll up one
page.  There are probably going to be 4 or 5 lines of errors for this,
one of which is the actual error, all the other messages get filtered
down though this.

Can you get to this screen and paste what the job log says, please?

FYI, detail for CPF5257:

 Message ID . . . . . . . . . :   CPF5257
 Message file . . . . . . . . :   QCPFMSG
   Library  . . . . . . . . . :     QSYS

 Message . . . . :   Failure for device or member &4 file &2 in library &3.
 Cause . . . . . :   An error occurred during a read or write operation. If
   this is a display file, the display may not be usable.
 Recovery  . . . :   See the previously listed messages, correct the
errors,
   and try the request again.  If the problem continues, report the problem
   (ANZPRB command).


Regards,

Jim Langston

RReddy@medicalartspress.com wrote:
>
> Here is what i get...
>
> Message ID . . . . . . :   RNQ1299       Severity . . . . . . . :   99
> Message type . . . . . :   Inquiry
> Date sent  . . . . . . :   01/09/01      Time sent  . . . . . . :
15:02:19
>
> Message . . . . :   I/O error CPF5257 was detected in file ECINQDSP (C G
D F).
> Cause . . . . . :   The RPG procedure ECINQPGM in program EDITST/ECINQPGM
>   received the message CPF5257 at statement 020000 while performing I/O
>   operation EXFMT on file ECINQDSP. The actual file is EDITST/ECINQDSP.
> Recovery  . . . :   Check the job log for more information on the cause
of the
>   error and contact the person responsible for program maintenance.
> Possible choices for replying to message . . . . . . . . . . . . . . . :
>   D -- Obtain RPG formatted printout of system storage.
>   S -- Obtain printout of system storage.
>   G -- Continue processing at *GETIN.
>   C -- Cancel.
>   F -- Obtain full formatted printout of system storage.
>
> Buck Calabro <buck.calabro@aptissoftware.com>@midrange.com on 01/09/2001
> 02:26:34 PM
>
> Please respond to RPG400-L@midrange.com
>
> Sent by:  owner-rpg400-l@midrange.com
>
> To:   RPG400-L@midrange.com
> cc:
>
> Subject:  RE: MCH0601
>
> Reddy wrote:
>
> >The program errors out at random .. its not always at the same
> >sceneraio..even i put the program in debug mode.. i have no way of
knowing
> >where would i see the error message next time.
> >
> >But i do get the same error message everytime
> >
> >I am going nuts.. please advice.
>
> Are there any messages in the job log before this one?  Often, there are
> informational messages that occur before the escape message is issued.
>
> Buck Calabro
> Aptis; Albany, NY
> "Nothing is so firmly believed as
>  that which we least know" -- Michel Montaigne
> Visit the Midrange archives at http://www.midrange.com
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---



+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.