Dave, Actually, the manual says teraspace allocations are valid only in the job that does the allocation, if you want to share the allocations then you need to deal with the share memory apis. Now, if you are referencing teraspace with a space pointer I'm not sure how that would play out, on one hand teraspace is only valid in the job that allocates it, on the other hand a space pointer is a space pointer from any job. -Walden ------------ Walden H Leverich III President Tech Software (516)627-3800 x11 WaldenL@TechSoftInc.com http://www.TechSoftInc.com -----Original Message----- From: David & Eileen Keck [mailto:email@example.com] Sent: Monday, December 24, 2001 11:11 To: firstname.lastname@example.org Subject: Re: Teraspace memory allocation I beg to differ. As I suggested in a previous post on this topic, a Teraspace Server process could be set up as a daemon. From a design point of view, mutiple jobs can certainly share the same teraspace by referencing the same handle / cookie. Dave K. ----- Original Message ----- From: "Simon Coulter" <email@example.com> To: <firstname.lastname@example.org> Sent: Saturday, December 22, 2001 10:08 PM Subject: Re: Teraspace memory allocation ----snip ---------- > TS exists only > for the duration of a job/process thus a handle cannot be stored externally > to the process and reused in a different process. ----snip----------- _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-Lemail@example.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.