Re: ILE and locked file -- RPG400-L

Subject: Re: ILE and locked file
From: Daniel Gross <daniel@xxxxxxxx>
Date: Wed, 20 Jul 2022 17:16:24 +0200
List-archive: <https://archive.midrange.com/rpg400-l/>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

Am 20.07.2022 um 17:02 schrieb Charles Wilt <charles.wilt@xxxxxxxxx>:
Also as mentioned, best practice would be to have the SRVPGM as *CALLER.
Your CLLE should be either a named activation group or *NEW.

Placing the service programs in *CALLER is good, as long as all (!!) of your programs are in a named AG or use *NEW ... but it's a really bad idea if one of your programs uses *CALLER too.

*NEW is not a bad idea - I had an application design where the "root" programs (those which get called from the command line or from the menus) always use *NEW and everything else (RPGLE programs and service programs) used *CALLER.

So a new AG was built with the call from the command line, and it was deconstructed when this program ended.

Today I always try to use named AG for programs and service programs - normally thematically bundled like "everything in finance uses ACTGRP(FINANCE)" and so on.

Bye
Daniel

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.