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



On 5/1/2013 4:12 PM, Smith, Mike wrote:

I have an issue where my program is behaving badly when I promote it from Test to QA.
I have moved the programs/files up and down between these two environments multiple times with the same results.
Below is what is happening in the QA Environment.

I have program A(subfile) that calls program B(maintenance). Program B has 2 main screens depending on record from program A. Both screens allow you to press a command key to call program C.
When returning from program C to program B one of the screens has the data on the left hand side of the screen disappear. The other screen works fine.
Both screens have the same keys words set.
Also I have a command key that prompts for a value that gets a Permanent I/O error.

I have deleted the programs/files from the QA environment and recompiled from scratch. Same results. When all are in my Test library the programs work as expected.

I'd start with the permanent I/O error. Generally, there are 3 big ones:
1) No data but SFLDSP was specified
2) Funky data in the database (like characters below x'C1')
3) Trying to display a 27x132 screen on a 24x80 display

The exact error message and the diagnostic messages which precede it in
the joblog will help.

How are you 'moving' the objects? MOVOBJ? SAVOBJ / RSTOBJ? Are your
test and QA environments in the same LPAR / machine?
--buck


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.