Did the second run also cause the fault?
Is there anything in that job or job stream that could be trying to
build a huge dynamic array? Such as trying to READ and entire report
into a variable?
--
Regards,
Clif
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
W. Clifton Oliver, CCP
CLIFTON OLIVER & ASSOCIATES
Tel: +1 619 460 5678 Web: www.oliver.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On Oct 18, 2005, at 3:03 PM, [EMAIL PROTECTED] wrote:
Any ideas? Suggestions? Oh, the program DID NOT ACTUALLY ABORT. It
completed and printed the reports correctly. HUH? Yes, I ran it
again and
confirmed that the reports I generated were identical to the ones
printed
at 2pm via cron job.
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
