× 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 26/03/2009, at 12:53 AM, David FOXWELL wrote:

Simon, I'd also like to be able to highlight the lines of the email I'm replying to with a >, how do you do that?

Depends on your e-mail client. The headers in your e-mail indicate WinDOS therefore probably Outlook. Even that smelly pile of poo can quote reply text. Take Tools->Options and open the Send tab. Click on Plain Text Settings and ensure "Indent the original text with" is selected and that '>' is the quote character. Since this appears to be the default behaviour perhaps you are sending HTML e-mail in which case stop doing that. Better though would be to use a better e-mail client.

First of all, let me say that all our applications run in the DFTACTGRP. ILE and OPM. If there's bad design, I guess it starts there.

Now you've set foot on the path to enlightenment. Running RPG IV is *DFTACTGRP is a "compatibility" mode intended to ease the migration to RPG IV. It allows you to use the benefits of RPG IV without having to learn ILE. During this phase everything (old RPG III, RPG/400, and new RPG IV) should be running in *DFTACTGRP. However, once you start using named activation groups you really cannot continue to use *DFTACTGRP in the same application. Doing so just makes a mess as you are discovering.

But what do you do, rewrite and/or convert everything to ILE so that it will run outside the DFTACTGRP?

One possible approach:
Step 1) Convert to RPG IV running in *DFTACTGRP. Any *SRVPGMs should be *CALLER.
Step 2) Once all code is RPG IV run *PGM objects in QILE (or other named activation group)--usual technique is to have main programs specify the desired activation group and sub-programs use *CALLER like *SRVPGMs generally do.
Step 3) Analyse application behaviour and use additional named or *NEW activation groups where appropriate--it may be that it is inappropriate or unnecessary for your application.

We are running a program that exists in several versions, each one in its own ACTGRP.

What do you mean by versions? Different source code? Or just uses different libraries for files?

This will permit the application to start in a general environment (DFTACTGRP), then depending on user choice, switch to an environment specific to that choice. This will let us switch from families of files that exist in different libraries, eg File1, File2, etc exists in Lib1, Lib2, etc We will have an ACTGRP per library containing each group of files.

What is specific to that environment? What is it about the application that needs separate activation groups per client?

So, we start in DFTACTGRP, go to named ACTGRP X, return to DFTACTGRP go to named ACTGRP Y, etc.

Big mess! especially if you still have RPG III code being called from your client-specific named activation groups.

If the reason for this mess is simply trying to get different libraries used by different "client selector" programs then use *NEW as suggested by Joep. However, you still need to get out of *DFTACTGRP. At a minimum you need to ensure that code called by your client-specific program(s) runs in the same activation group.


Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.