|
I have to admit no. I've been stuck at my desk and haven't had a chance. I am the last person to compile that display file before the problem. I made a change to it a few years ago before I fubared it I had looked and seen that it still had my name on it. I'm absolutely sure I compiled it as I have already described. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Hatzenbeler, Tim Sent: Tuesday, April 25, 2006 3:08 PM To: Midrange Systems Technical Discussion Subject: RE: Negative response code... RNX1251 Did you restore your old display file, and see what the rstdsp value was set to in the previous working version of this file? Just wondering? -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Wallroff Sent: Tuesday, April 25, 2006 1:01 PM To: Midrange Systems Technical Discussion Subject: RE: Negative response code... RNX1251 It's not a data integrity problem. The screen is simply for the most part an entry screen and all the fields are blank when you go into it. It's used to collect data to run a report. I know it's not a data problem because I could go into it in Production without a problem until I simply recompiled the old, unchanged source again then the error started happening there too. It's something to do with the system, either a parm was added or changed on the CRTDSPF or I don't know what. Like I said, I normally simply compile our display files on the way out of SDA without changing any parms. I was given the tip to create the DSPF with the CRTDSPF command and to change the RSTDSP parm to *YES from it's default of *no. That cause the error to go away but I'm thinking that's just a work around and I would like to know what is up with the system. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Luke Dalton Sent: Monday, April 24, 2006 3:16 PM To: 'Midrange Systems Technical Discussion' Subject: RE: Negative response code... RNX1251 Sounds more like a data integrity problem to me. Are you sure you're not sending invalid data (i.e., something below hex 40) to a display field? -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Wallroff Sent: Monday, April 24, 2006 3:01 PM To: Midrange Systems Technical Discussion Subject: Negative response code... RNX1251 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 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.