Re: Checking if a command processing program was called from ILE or OPM -- MIDRANGE-L

Subject: Re: Checking if a command processing program was called from ILE or OPM
From: Mark S Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>
Date: Fri, 24 Mar 2017 11:04:56 -0400
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>

Hi, Charles:

> On 3/24/2017 10:29 AM, Charles Wilt wrote:

...(snip)...
AFAIK, there's no reason a DFTACTGRP(*YES) program would need to be differentiated from a true OPM program.

Using various APIs, etc., would still ldentify the *PGM as "ILE"... you have to examine the "activation group" attribute to determine that it was actually created with "DFTACTGRP(*YES)".

So, my point was that knowing just "OPM" vs. "ILE" as far as the calling program is concerned, does not really "help" much, hence my suggestion to make the CPP "agnostic"-- e.g. force the CPP to run in its own ACTGRP, so it can tolerate being invoked from OPM or ILE contexts.

HTH,

Mark

This mailing list archive is Copyright 1997-2026 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.