× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




Cut the copy too soon.

On 21/04/2008, at 5:05 AM, Jim Franz wrote:
Everything in joblog normal till then.
This error occurred when several users calling same group of programs, before and after error.

Is "something" deleted by one user that the code expects will still be available for another user? I mean a timing issue where one user creates something, another user connects and uses it and deletes it (because they process faster), then the failure occurs when the first user references the destroyed object?

You'll need to examine your code to determine if this is a possibility.


Using native file logging wwwaccess and wwwerror. No indication of "why".
What can I do in logging to get more detail? Job log already at max level.

You can change the MCH3402 message description to dump the job information which will give you the call stack and other stuff. CHGMSGD MCH3402 DMPLST(*JOB). Might be helpful.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.