RE: ILE COBOL Call -- COBOL400-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: ILE COBOL Call
From: "Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>
Date: Sat, 8 Feb 2003 21:22:07 -0500
Importance: Normal
List-archive: <http://archive.midrange.com/cobol400-l>
List-help: <mailto:cobol400-l-request@midrange.com?subject=help>
List-id: COBOL Programming on the iSeries/AS400 <cobol400-l.midrange.com>
List-post: <mailto:cobol400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/cobol400-l>,<mailto:cobol400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/cobol400-l>,<mailto:cobol400-l-request@midrange.com?subject=unsubscribe>

Gary,

  >> I have an ILE COBOL program that I am trying to call a "regular" COBOL
program, however it crashes....

Does the call fail on the first attempt or on second and subsequent ?  What
type of crash are you getting?  What field/statement does it point to?

There really aren't any situations I can think of where a failure would
occur when calling from ILE to OPM that wouldn't occur when calling from
OPM.  Have you tried a really skinny ILE program (i.e. nothing but the call)
to see if that works?

Jon Paris
Partner400

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.