Re: Program ends, no messages, logs, etc -- C400-L

× 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.

Subject: Re: [C400-L] Program ends, no messages, logs, etc
From: Walt Fles <wfles@xxxxxxxxxxx>
Date: Tue, 25 May 2004 16:17:50 -0500
List-archive: <http://archive.midrange.com/c400-l>
List-help: <mailto:c400-l-request@midrange.com?subject=help>
List-id: C programming iSeries / AS400 <c400-l.midrange.com>
List-post: <mailto:c400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/c400-l>, <mailto:c400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/c400-l>, <mailto:c400-l-request@midrange.com?subject=unsubscribe>

I take that back, the program that invokes the thread that does the system() call ends,with a message CPF1241. Would be nice if I could see where or how it was stopping, like an object dump or stack trace or something.

When a program dies abnormally on the iSeries (for ILE/C) you don't get a core dump as such, what you get is either a nice CPF/MCH error message in the job log or on the status line.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Program ends, no messages, logs, etc , Walt Fles

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.