HP3000-L Archives

November 1999, Week 1

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:
Reply To:
Date:
Tue, 2 Nov 1999 20:21:55 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (22 lines)
James Clark wrote:
>
> On the new machine architecture size is usually not a problem, because of
> the addressable memory. The problem is in the CM (old code). CM code had a
> limit of 16K words of code and 32K words of data (that is 2 byte words) when
> HP emulated the Classic, they maintained that for compatibility. I have only
> run into a few situations where a program could only run on the new machines
> and not on the old ones. As to further segmenting the code, that all depends
> on the logic of the code. Try to fit all the code which needs to run
> together into the same segment, and I also believe that HP COBOL (using
> sections to handle segmenting) had some caveat about sections above 50 and
> those which were below 50. Can't remember what the situation was but do
> remember it had something to do with performance. Such as do not have code
> in the lower 50 call code in the upper 50 repeatedly.

Segments below 50 will be refreshed from the original disk image if the
segment is left and then reentered. Segments above 50 are essentially
static. Major impact if the program uses the ALTER verb. If you say
ALTER PARA-X TO PROCEED TO PARA-Y, then leave the segment, then re-enter
the segment, segments below 50 will have the original PARA-X whereas
segments above 50 will still have the PARA-Y reference.

ATOM RSS1 RSS2