The LMAP option didn't work with the new version of the CM program, but I
just used it with the previous version, and - as you might guess - there are
253 segments including all SL calls.  So that is the problem.  I suppose
there is no way around the limit of 255...  So, now to eliminate anything
unnecessary, if I can.

Thanks, Keven!

James Dunlap

----- Original Message ----- 
From: "Keven Miller (rtt)" <[log in to unmask]>
To: "James D. Dunlap" <[log in to unmask]>
Cc: <[log in to unmask]>
Sent: Monday, February 25, 2008 12:54 PM
Subject: Re: [HP3000-L] Too Many Code Segments


> James D. Dunlap wrote:
> > The CMSEG "current" value is 255, per SYSGEN > MISC > SH RE.
> >
> > I went ahead and made a CSLT via SYSGEN > TAPE VERBOSE and then did ISL>
> > UPDATE CONFIG while booting from the CSLT (alternate path), but I am
still
> > getting the same error (TOO MANY CODE SEGMENTS - LOADERR 37).  The CM
> > program in question has 21 segments.  Why does the system still not
allow
> > for 234 more?
>
> The 255 limit is for all segments from the program and any SL segments
> that get loaded.
> So if you are running with LIB=G, the potential is loading
> the group SL, the pub SL, and always the system SL.
>
> If you run with the ;LMAP option, besides coming to your screen,
> the output of segment mapping of a load process is put into
> LOADLIST.PUB.SYS.
> Also the file LOADMAP.PUB.SYS shows where mpe has already loaded
> system segments.
>
> I dont remember if LOADLIST is produced when you get this error,
> but its worth a try with ;LMAP. It may give output and show how many
> segments, and from where it does get before the error.
>
> Also, intrinsic LOADPROC, I believe would also be affected by this
> 255 limit, if your doing a LOADPROC from some other SL besides those
> in your ;LIB= path. But that won't show up until runtime.
>
> Keven
>

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