John.
The companies I have worked (except for one) were all COBOL.
They learned early on that when one of the COBOL subroutines abended
(started with the ILC modules if memory serves me)) at 0030 in the AM
someone got rolled out of bed to fix it. COBOL programmers that I
have worked for are risk adverse and did not want things like this to
happen. They wanted an environment that once tested it worked
*FOREVER* which was likely not to happen with DYNAM. Forget load
module size they wanted write once run forever. They would much
rather have a S0C4 in the daytime hours to debug than at 0030 . I
have worked in banking (granted 40 years years ago) and the few COBOL
programs that I was exposed to were linked statically and thus was
standard.
I personally have been rolled out at 0100 many times because of a
S0CX in one of the cobol subroutines (I didn't write it the main
program) since it was an IBM module I got called and had to hand hold
the programmer to get it it running again. It was *usually* a
combination of relinking a cross release of ILC programs that were
were not friendly.
Statically linked programs were also at risk but usually not to badly
and were not fun to track down as a result, so there are no universal
rules). It was simple to just recompile and relink all the programs
in question.
Assembler programmers were less likely to have issues as they were
well aware of "foreign" changes and were not likes to point the
finger at IBM software.
I would have to disagree (to a point) about measurements for loadlibs
because at several places I had QCM and it would publish numbers at
step termination time about I/O times about JOBLIB/STEPLIB times and
you could actually tell how how much time fetch took for each
library. Granted QCM is no longer sold but we did use it to its full
use when it was available.
Ed
On Oct 26, 2013, at 2:04 PM, John Gilmore wrote:
Ed [Gould],
The COBOL shops---chiefly in insurance, banking, and
communications---that I know well instead do use DYNAM heavily, often
when there is no clear rationale for doing so.
Even within a single shop, however, batch jobs are likely to differ
significantly in 1) j how much they use execution-time load libraries
and 2) which, if any, of these libraries they use.
My plea was for measurements that would make better decisions among
the available alternatives possible.
John Gilmore, Ashland, MA 01721 - USA
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
