activation groups, compiling CLLE programs -- MIDRANGE-L

Subject: activation groups, compiling CLLE programs
From: Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx>
Date: Fri, 9 Jun 2017 15:34:10 -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/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I have noticed that I am doing all kinds of "bad" things in respect to
activation groups...

I don't know where to start, other than maybe changing the command defaults
on CRTBNDCL
to DFTACTGRP(*NO) ACTGRP('<our_named_actgrp>')

we are kinda getting into the habit of compiling our RPGLE programs as
ACTGRP(*CALLER).
But since most of our CL and CLLE is set to *DFTACTGRP, most of our RPGLE
is running there as well....

we don't have /copy on our H specs, or any other real helps in place for
this....

what have others done to help with getting programs created with the
correct activation group settings?

Follow-Ups:

Re: activation groups, compiling CLLE programs , CRPence

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.