× 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.



Hi James -

On Wed, 06 Feb 2013 09:15:01 -0800, "James H. H. Lampert"
<jamesl@xxxxxxxxxxxxxxxxx> wrote:

Hmm. I seem to recall at least one personal experience with Bad Things
Happening when certain ILE-only constructs were back-doored into
*DFTACTGRP by using *CALLER.

I run into that occasionally in testing, but it doesn't happen in
production.

And what happens if you need a program that would behave badly in
*DFTACTGRP to terminate-but-stay-activated (either so it can pick up
where it left off, or so multiple calls in a batch job don't create
separate spool files)? Named activation groups can be most helpful in
such situations.

In our main billing system (which is where my responsibility lies), I
don't allow any such badly behaved programs. They can either play
nicely with others or they can go stand in the corner!

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.