Program works in debug but not run time
I have an RPGLE program that works when run in debug mode but will not update the file when run outside of debug.
I have looked at the obvious, such as library list to ensure using same versions of programs.
At a loss......
Software/Hardware used:
Software/Hardware used:
ASKED:
January 9, 2007 10:57 AM
UPDATED:
December 29, 2009 4:48 PM
Answer Wiki:
It seems like I ran into this once. However, my issue was that a copy of the file being updated was sitting in another libarary other than the one I was looking at.
=========================================================
If it is only "debug" that makes the difference, then the program is coded to work differently under debug. I'd say that's pretty unlikely. But we don't know what you think works differently.
Are there different values in variables? Is a different path taken in code? Does an I/O statement work differently?
The only time I've ever seen debug make a difference <i>when everything else was equal</i> was a case where an I/O statement only properly populated variables in debug and not in normal mode. It turned out that the input was coded to run without any wait. It would always have time to complete when the program ran in single-cycle mode under debug.
That could be something like your case, but I'd expect that to be very unlikely.
Far more likely is the suggestion that it fails in batch but runs correctly interactive, or some similar difference in how the program is called. The suggestion that the parm list is the culprit is a good possibility there.
Describe the circumstances under which it succeeds and those under which it fails. Something other than debug is where the problem is likely to be found.
Tom
To see all answers submitted to the Answer Wiki: View Answer History.
Check your joblog for any errors that might have presented themselves. What release level is your i5 at?
I have had this problem before and it was related to the fact that I was running the debug interactively, but the regular run of the program was run in batch. The problem was traced back to the way that parameters are passed on a sbmjob. This may be your problem, especially if you are passing in numeric parameters.
Is this an SQL RPG program? Reason I am asking is we have run into problems where a program was not created with COMMIT(*NONE) so it is assuming the program is being called under commitment control. Nothing was being written or updated in the program until we recreated it.
I agree with previous answer. Happened to me once. I was running debug interactive. While alone it was run in batch.
I’d look at my library list in each situtation.
Jack
Is the file journaled? If so, check the journal entries to see what was updated after you run the program outside of debug.
To further clarfiy some of the other answers posted – is this a batch job. If so, check the library list of the batch job. This should be in the job description. Also, look into the begining of the job log to see what library list it really used to run the job.
If the job is using a different library list and you are making updates thru a logical file, the LF might be pointing to an entirely different PF, but you are querying the file what you believe is right.
Another thing that I have come across is expecting new records at end of file, but the record was inserted elsewhere due to key sequence.
In debug you specify to update live files. Running live you have to be authorized to update the file in production. If not a library issue it could be an authorization issue, Run th job in batch and specify a log to print. This will tell you what is happening in batch.