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



Nope, not that either.  I'm the last person to touch the source.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Raul A. Jager W.
Sent: Monday, April 24, 2006 3:46 PM
To: Midrange Systems Technical Discussion
Subject: Re: Negative response code... RNX1251

It sounds like somebody modified the source, and because of the problem 
he left the old object.

John Wallroff wrote:

>I have a very frustrating problem.  I am working on a display file that
>we have had for several years.  This display file is now coming up with
>these errors when it is displayed, another display file is display and
>this display file is displayed for a 2nd time...
>
> 
>
>Data sent to device FLJOHN1 not valid.  Negative response code is      
>
>  10050126.                                                            
>
>Permanent I/O error occurred in file IABS423.                          
>
>Function check. RNX1251 unmonitored by IABR423 at statement 0000000797,
>
>  instruction X'0000'.                                                 
>
>Permanent I/O error occurred in file IABS423 (C G D F).                
>
>Permanent I/O error occurred in file IABS423 (C G D F).                
>
> 
>
>We have 2 partitions on our iSeries, a Dev side and a Production side.
>I was making some changes to this display file on the Dev Box and I
>started getting this error while testing the changes.  Well, long story
>short, I moved the old source files from Production onto the Dev box to
>try to figure out where the problem really was.  I compiled the
original
>display file and it's came up with the same error when I ran it.  The
>production box was working so to test if it was some type of
>configuration difference between the Production box and the Development
>box I simply recompiled the existing source on the Production box, now
>it's coming up with the error.  Keep in mind, nothing has changed on
the
>production box other then an old existing Display file was recompiled.
>
> 
>
>Do any of you out there have any idea what the heck is going on?  Is
>there some kind of PTF that I'm missing that addresses this?  This
>Display file has been around and has been used for a long time.  I
>personally made a change to it 4 years ago and it's always worked.  On
>the Production box nothing has changed other then recompiling the
source
>so I don't think there is a problem with the source or RPGLE program
>that runs it.  My gut feeling is that there is a system issue.  Doing a
>Google search on the error RNX1251 even brought up an issue with V5R2
>and this error and showed a PTF.  We are on V5R3 and are pretty up to
>date other then I've yet to load the latest CUM set.  I plan on doing
>that this week on our Dev box and if everything looks good on the
>Production box this weekend.
>
> 
>
>Thank you very much for your help in advanced. 
>
>  
>



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.