×
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.
On Wed, Feb 6, 2013 at 1:33 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:
The day that someone at MYCOMPANY decides they need STATIC storage
scoped not just to the job level, but to the activation group level is
the day they re-create that service program as ACTGRP(*CALLER). They'll
be doing work on it anyway in order to implement the new functionality
they're contemplating.
That statement doesn't make sense. changing the service program to
ACTGRP(*CALLER) would have no effect if every program using it still had
ACTGRP(MYCOMPANY)
A more likely scenario is that you'd create a new program with
ACTGRP(MYPGM) or ACTGRP(*NEW) that tried to make use of procedures from an
existing service program that had ACTGRP(MYCOMPANY)...now you have trouble.
Now you have to change all *SRVPGM program (used by this new program) to
*CALLER
Is it really so hard to remember 2 rules...
*PGM ACTGRP(MYCOMPANY)
*SRVPGM ACTGRP(*CALLER)
Instead of the one?
Charles
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.
midrange.com
