HP3000-L Archives

February 2010, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Roy Brown <[log in to unmask]>
Reply To:
Roy Brown <[log in to unmask]>
Date:
Tue, 23 Feb 2010 15:22:40 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (69 lines)
In message <[log in to unmask]>, Brian Donaldson 
<[log in to unmask]> writing at 04:18:10 in his/her local time opines:-
>
>I have been researching a bit into why a particular program is  taking over
>7 (yes, SEVEN) minutes to compile.
>
>Of course, my box is just a little 917LX but even so, I think 7 minutes is
>ridiculous.
>
>I discovered a few things that *may be* causing the problem:
>
>1) Cobol macros but no idea why. I remember when I once worked at a
>certain company
>they had the same problem, incessant use of macros and *l-o-n-g* compile
>times.
>
>2) My use of the $control options:
>
>a) OPTIMIZE=1 (compiler creates a smaller nmprg file)
>b) VALIDATE (compiler creates code to check for illegal ascii digits and/or
> illegal decimal digits)
>c)BOUNDS (compiler creates code to check for subscripts out of range  etc.)
>d) OPTFEATURES= CALLALIGNED (I think ensures call statement parms are on a
>word boundary in a mainline)
>and OPTFEATURES=LINKALIGNED (I think ensures call statement parms are on a
>word boundary in a sub)
>
>
>I have spent time de- macro -izing the program and I also removed these
>$control options.
>
>The compile time so far is about 2 1/2 minutes as seen below:
>
>COB85XL LOCKERV1.SOURCE.!HPACCOUNT,LOCKERV1.NMOBJ.!HPACCOUNT,$NULL
>
>PAGE 0001  COBOL II/iX HP31500A.04.21  [85] Copyright  Hewlett-Packard CO.
>1987
>
>
>
>0 ERROR(s), 0 QUESTIONABLE, 0 WARNING(s)
>
>    DATA AREA IS    2C1FC  BYTES.
>CPU TIME = 0:02:20.  WALL TIME =  0:02:26.
>
>Although the compile time is seriously reduced, I felt much safer with all
>these safeguards
>in the program(s) and now they're all gone I am feeling rather  nervous.
>
>Any thoughts, comments, suggestions etc will be welcomed.
>
>TIA,
>Brian Donaldson.

How big is your program source?
How big is the resulting executable?
Are you pulling stuff in from libraries, and if so what, generally?

But if you got more than 4 minutes off the compile time by removing 
those features/options, I think that tells its own story....


-- 
Roy Brown        'Have nothing in your houses that you do not know to be
Kelmscott Ltd     useful, or believe to be beautiful'  William Morris

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2