Shared state variables in IDS2000?

Hi there, I am looking for a way to implement a set of shared state variables in IDS 2000, similar to what an app server would provide. A typical example: if the end-of-day batch process is running, then all new user connections must be read-only. Global variables in SPL stored procedures are not shared among users. How about stored procedures in C? Any other way (without using a table)? -- Bashar Chalabi CTL, London

If you write UDF's in C for IDS.2000 you can certainly allocate and reference a new shared memory segment for this purpose. Of course you could only control user apps that call the check function. Art S. Kagel Bashar Chalabi wrote: > > Hi there, > > I am looking for a way to implement a set of shared state variables in IDS > 2000, similar to what an app server would provide. > > A typical example: if the end-of-day batch process is running, then all new > user connections must be read-only. > > Global variables in SPL stored procedures are not shared among users. How > about stored procedures in C? > > Any other way (without using a table)? > > -- > Bashar Chalabi > CTL, London

> If you write UDF's in C for IDS.2000 you can certainly allocate and reference > a new shared memory segment for this purpose. Of course you could only > control user apps that call the check function. Yeah, but that would make it OS dependant. Anything else? Thanks -- Bashar Chalabi CTL, London

You can use the Named Memory API. On Mon, 24 Jan 2000 18:07:12 -0000, "Bashar Chalabi" <bashar@ctl.com> wrote: >> If you write UDF's in C for IDS.2000 you can certainly allocate and >reference >> a new shared memory segment for this purpose. Of course you could only >> control user apps that call the check function. > >Yeah, but that would make it OS dependant. Anything else? > >Thanks