Re: Weird compiler message and failure -- 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: Weird compiler message and failure
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Tue, 02 Dec 2014 13:58:30 -0800
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/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 12/2/14 1:06 PM, Thomas Garvey wrote:

However, the PGMINFO parameter _is_ *NO and the INFOSTMF parameter is
blank. The source is being compiled from a *SRC source file member, NOT
a stream file.

Hmm.

Is there (and I haven't bothered to check whether there is such a thing) an H-spec overriding the PGMINFO parameter?

PGMINFO is something I've only used in connection with web services and the like.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Weird compiler message and failure , Thomas Garvey

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.