HP3000-L Archives

July 1996, Week 1

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:
Jeff Kell <[log in to unmask]>
Reply To:
Jeff Kell <[log in to unmask]>
Date:
Thu, 4 Jul 1996 00:31:32 EDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (23 lines)
On Wed, 3 Jul 1996 15:47:23 -0700 Jeff Vance said:
>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.
 
One possible extension - create new HPCIERR-like variables qualified by PIN
number, e.g., HPLOCALCIERRORnnn where "nnn" is the PIN of the process.  This
would let new applications exploit the availability of this function without
breaking any of the existing applications.  I would suggest "hiding" this
somehow internally, but this would probably break other things (many existing
applications query the CIERROR to determine an offspring and/or sibling's
status).
 
Jeff Kell <[log in to unmask]>
 
PS - Eight "MAC..." posts suppressed (administrivia)

ATOM RSS1 RSS2