Re: CRTSQLRPGI Activation Group default -- RPG400-L

× 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 Fri, Aug 5, 2022 at 8:21 AM Craig Richards <craig@xxxxxxxxxxxxxxxx>
wrote:

I would be happy to ask developers to insert BUILD instructions whenever a
program is being maintained, but it seems unreasonable to force someone to
do that if they are (for example) having to recompile 100 programs due to a
file change (especially without a change management system)

IMO, if your developers are adding a field to a table and having to
recompile 100 programs, you're doing it wrong in the first place.

Especially if you don't have a CMS.

RPG programs should not directly reference a PF, instead they should only
reference LF with an explicit field list.

Add a new column to the PF (or better yet an SQL table) and nothing needs
to be recompiled.
Create a new LF, with the new column and then modify the RPG programs that
need to access it to use the new LF.

It's an easy architecture to move to, the only real caveat is if you have
SQL Indexes that are used by RPG record level access; you can still
implement it just a bit of one time pain.

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.