PDA

View Full Version : Need Help with Overflow Error causing a program dump.


David Abramowitz
11-20-2002, 03:19 AM
Check to see what you are printing in the *INZSR portion of your program. Examining the values in the program dump may help. Dave
Guest.Visitor
11-20-2002, 07:31 AM
Diana, It sounds to me as if there is an OvrPrtF command being run before your program runs. A wild guess would be that the overflow line 74 is greater than the Lines Per Page setting for this printer file. If you display the job when this error occurs, one of the options is to display overrides, this will let you know if indeed your printer file is being overrridden. Bill Diana A wrote: > I am getting the following error when I try to execute a program that > has an external print file: "Overflow line 74 for file R10311 in > library JDFOBJ not valid." > > The message id for this error is CPF42214. This error occurred during > the *Init phase of the RPG program. > > The printer file was created with the overflow line set to 62, but I > don't know if that has anything to do with the above error. > > Can anyone tell me what is causing this error or what it means? > > Thanks in advance.
Guest.Visitor
11-21-2002, 10:08 AM
I am getting the following error when I try to execute a program that has an external print file: "Overflow line 74 for file R10311 in library JDFOBJ not valid." The message id for this error is CPF42214. This error occurred during the *Init phase of the RPG program. The printer file was created with the overflow line set to 62, but I don't know if that has anything to do with the above error. Can anyone tell me what is causing this error or what it means? Thanks in advance.
GlenKerner
11-21-2002, 10:08 AM
I noticed that your program referenced an object in JDFOBJ. It has been a while but are you using JD Edwards? Is this a modified version of there programs? If so, JD Edwards has a routine that is executed at the beginning of the program, or at least used to, that does a lot of manipulations with the printer output. It could be a set up issue with JDE. As I said it has been a while but if you are using JDE it would be a place to start.