Subject: | |
From: | |
Reply To: | |
Date: | Thu, 4 Jul 1996 08:16:50 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Jeff Vance writes:
>Hi Jim,
>
>I wish there was an easy way to have process local CI variables. It
>has been our our want-to-do-sometime list for a long time (> 6 years).
>The only "local variable" concept the CI has are command file and UDC
>parameters. Parameters are always treated as strings (even if not
>quoted) and are pass-by-value arguments: parameters cannot be modified
>by the script. But I can't think of a way to exploit this since HPCIERR
>(and CIERROR) are global to every process in the same job/session. In fact,
>this very problem has made it difficult to write OpenView OperationsCenter
>scripts for the 3000.
[last parts snipped]
I would really, really, really love having process local variables. If you
are doing any MPE sockets based c/s stuff you will find quite quickly that
job/session global objects like file equations/vars create an interesting
problem when porting existing code that relies on these values being unique
to user (client).
FWIW - We use Jeff Kell's PIN idea to get uniqueness by process. Works
great, but it would be nice to not have to bother.
duane (off-site enjoying the 4'th)
[log in to unmask]
|
|
|