Re: Easiest way, in a CL pgm, to find out what source member a program was compiled from? -- MIDRANGE-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: Easiest way, in a CL pgm, to find out what source member a program was compiled from?
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Thu, 31 Mar 2011 15:35:01 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

James Lampert wrote:

Anybody know, off-hand, an easy way for a CL program to find out what
source member a program (or the main entry-point module of a
multi-module program) was compiled from?

Perhaps some of the program & CL api's would be helpful ...

http://urlq.us/i or http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/apis/pgm1.htm

QCLRPGMI, QBNRSPGM, & QBNRMODI look likely.

david

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.