|
Hello, I want to separate several serviceprograms that are often used by our applications. These srvpgms do very common things, like getting customer info, article coding info, stock info, selection subfile windows, etc. Until now I always compiled these serviceprograms with ACTGRP *CALLER, and the applications that use these servicepgms are always compiled with *NEW or sometimes in a named ACTGRP. There are about 150 applications that often use parts of these 60 serviceprograms. So far so good. I realize that the dowside of this approach is that every time an application starts that was compiled with ACTGRP *NEW, it will initialize the almost same bundle of serviceprograms that were used in the previous executed applications. So what I want to do is to put these serviceprograms in a separate named activation group, for example COMMONAG.. Then resources for these serviceprograms are initialized at once and remain available for all applications that are executed later. The serviceprograms are optimized *FULL and about 700 - 900 Kb each. Total serviceprogram size is 48 Mb. Static storage is 11 Mb. My questions: 1) Does it cause problems when I keep this COMMONAG during the job's life with this static storage of 11 Mb and of course the ODPs for about 40 files loaded ? 2) Do activation groups have a size limit ? 3) Are there any other problems that I do not foresee? Any help would be appreciated. Arco Simonse DISCLAIMER: This message contains information that may be privileged or confidential and is the property of C.Meijer B.V. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy,disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. This footnote also confirms that this email message has been swept by the presence of computer viruses
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.