HP3000-L Archives

February 1999, Week 2

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:
"Michael P. Smith" <[log in to unmask]>
Reply To:
Michael P. Smith
Date:
Fri, 12 Feb 1999 13:12:38 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
We all know that every process get's it's own NMSTACK and NMHEAP when it is
created.  And that by specifying a NMSTACK= or NMHEAP= on the :RUN statement
we can increase or decress the size of that STACK/HEAP.  However, what
happens when the program in question is not the one being run but is
actually being CREATEd by the program we are running?

I think that the processes being CREATEd will use it's own internal limits
(specified at :LINK time) or if none are specified it will use the system
limits (configured in :SYSGEN).  But if that is true, it would mean in order
to change the limits on a program meant to run as a child, you would have to
do an :LINKEDIT ALTPROG.  This would also mean that you couldn't have
different versions of the program running with different limits.  It just
doesn't sound right, but maybe that's what is happening.

Anyone know for sure?  If not, then I guess I'll have to code it up and try
it out.

 ---------------------------------------------------------------
| Michael P. Smith                                              |
| Sr. Systems Programmer                                        |
| The Hertz Corporation    [log in to unmask] (work)          |
| Oklahoma City, OK        [log in to unmask] (personal)      |
 ---------------------------------------------------------------
The thoughts, views and expressions contained in this message are those
of Michael P. Smith, and do not necessarily reflect those of the Hertz
Corporation.  To reply via email, remove the .xx from email address.

ATOM RSS1 RSS2