Re: Growing Programs -- MIDRANGE-L

Subject: Re: Growing Programs
From: rob@xxxxxxxxx
Date: Tue, 30 Aug 2011 17:12:35 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

What may change in size without involving recompiling or UPDPGM for module
based programs.

Well, a sql program may change because it stores some dynamic information
in there about how to best process some of the statements in it.

Perhaps you have something which does a CHGAUT '/QSYS.LIB/MYLIB.LIB/*.PGM'
... to reset all the authority in all programs in a library. That would
count as a "change". Not sure if it would affect size.

Perhaps you run a routine CHGPGM to do something. We had havoc created by
doing a CHGPGM to save size by removing observability. Not such a big
deal on programs compiled on V5R1 and above but a major bummer on earlier
programs and CISC-to-RISC or migration to 6.1 and above.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

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.