|
Hi Rob -
Also using FRCDTA will affect performance just as DFRWRT(*NO) does.
True, but only on the format(s) on which you specify it, rather than every format in the file like DFRWRT(*NO).
You might also try going through the display file and removing keywords that may not actually be needed.
I had a situation several months ago where I was modifying a program to call another program which has its own display file. I started getting display file errors on the display file of the original program when I started a new transaction, but only after my program had been called in the processing of the first transaction. This error had not occurred when I was testing my program inside of a simple shell.
The display file of the first program (which was purchased software that I now provide in-house support for) looked like something converted from S/36 SFGR specs or possibly written by a first-grader. (And the RPG/400 program was just as bad.) The display file had lots of unneeded OVERLAY keywords and other unneeded keywords. When I removed the keywords that weren't actually needed, the display file still worked the way it was supposed to, and the halts went away.
Ken http://www.kensims.net/ Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind.
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.
midrange.com
