Hi all,

With his permission I am forwarding a suggestion from Dennis Heider.  I
want to make this discussion as public as possible hoping that one
persons suggestion will trigger another.

Jeff Vance, CSY

--- Forwarded mail from "Heidner, Dennis L" <[log in to unmask]>

From: "Heidner, Dennis L" <[log in to unmask]>
To: "'Jeff Vance'" <[log in to unmask]>
Subject: Design for System CI vars (long)
Date: Mon, 16 Sep 1996 11:58:01 -0700

Jeff,

I like the idea of  improved CI variables... would it be worth looking
at VAR in a some what different manner.    Instead of trying to add
ACD's for variables, locks, etc.... why not create a new command called
"SETSTRUCT"    It might look something like:


SETSTRUCT  MY_IPC_APP USING  HPPROMPT, MYCIVAR,
XYZ[;ACD=(......)][;PASS=xxxxx][;DOMAIN={local|global|session|system}]

The above command would include HPPROMPT, MYCIVAR, XYZ.   Access to ANY
of the variables would be controlled by the ACD.

In order to access the structure or any of the variables defined by
another process or script you would be required to execute  a
"GETSTRUCT" command.

Three other commands which would be needed are DELSTRUCT, SHOWSTRUCT,
and SAVESTRUCT.    The latter command would save the structure and its
values to a file for access after a machine was rebooted.

For example:

SETSTRUCT MY_FOO USING FOO,FOO2,FOO3;DOMAIN=LOCAL
SETVAR FOO 1
SETVAR FOO2 2
SETVAR FOO3 3

Now because the structure was defined to be local, FOO, FOO2, and FOO3
are local.   Had an ACD been specified, they would have inherited that
also.

Dennis Heidner

<phone numbers snipped>

---End of forwarded mail from "Heidner, Dennis L"
<[log in to unmask]>

--