Re: Growing Programs

Robert,

If you are using third party software and the software was shipped to you by the software provider with the program objects compressed, that could also contribute to size differences.  If a program does not get used, it should remain compressed.  Then, the first time it gets used by the i/OS, it will automatically get decompressed and then remain in that state.

Just another possibility.

We ship all of our software with the program objects compressed to save time when getting the software from us via download.

Rich Loeber
Kisco Information Systems
http://www.kisco.com
SDG
-------------------------

Quoting Robert Munday <rwmunday@xxxxxxxxxxxxx>:

Rob,


Sounds reasonable.  Thanks for the reply.



Robert Munday


-----Original Message-----
From: rob@xxxxxxxxx
Sent: Aug 30, 2011 4:12 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Growing Programs

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
--
Group Dekko
Dept 1600
Mail to:  2505 Dekko Drive
           Garrett, IN 46738
Ship to:  Dock 108
           6928N 400E
           Kendallville, IN 46755
http://www.dekko.com


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.