|
Mike said: >That's the mystery - it will fail when >called with the same parameters that >will generate a spool file during debug. Your task is to isolate the differences between the two runs. Does the production job run in batch? Did the debug job run interactively? If the parameters are the same, then I would very carefully look at the library lists of the two runs. Especially if there are multiple versions of CORO6a on the system. In my hoary old age, I've learnt the hard and humbling way that the library list is a common thing to overlook. If there's no joy there, check the RPG program itself. Is there a *PSSR that's trapping a message and aborting before you expect? Let go of all your assumptions and scrutinise everything. I have never seen a report program run differently in debug, but I have seen communications programs change behaviour because of the changed timing (it takes much more time when stepping through a program than having it run full-speed.) --buck
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.