HP3000-L Archives

February 2000, 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:
Frank McConnell <[log in to unmask]>
Reply To:
Frank McConnell <[log in to unmask]>
Date:
Sun, 27 Feb 2000 23:03:07 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
Steve Robertson <[log in to unmask]> wrote:
> When I try to run certain applications, I get a CODE SEGMENT IS TOO
> LARGE error. Like in the previous problem, these applications used to
> run OK. Any insight into what the problem is here?

The maximum code segment size is tunable via SYSDUMP or INITIAL (the
boot program), and it would appear that you have some code segments in
program or SL files that are larger than your system's current
maximum.

If you do a coolstart or SYSDUMP (to cut a new cold load tape), answer
"Y" to "ANY CHANGES?" and then when it gets to "SEGMENT LIMIT
CHANGES?" answer "Y" again.  One of the questions you'll get after
that is "MAX CODE SEGMENT SIZE=nnnn (MIN=1024, MAX=16384)?" and you
can probably max it out at 16384.

Did the Y2K tapes come with an installation workbook?  Somewhere in
the traditional MPE V/E update notes was a set of questions that you
were supposed to work through that would yield the numbers for several
important tunables (based on your expected workload and some of the
products you might have on your subsys tape), then you were supposed
to cut a new cold load tape with SYSDUMP using these numbers and
reboot from that before starting the update.

-Frank McConnell

ATOM RSS1 RSS2