In article <[log in to unmask]>,
   [log in to unmask] (Mike Paivinen) wrote:
[snip]
>If you're willing to go to the trouble of modifying your applications, this
>method can be used without putting HZCICOMMAND in the system NL.  You only
>have to put HZCICOMMAND in XL.PUB.SYS.  This can be done on-line as long as
>no program is executing that is bound to a procedure in XL.PUB.SYS.  [I know
>we've had problems in the past where HP programs launched at boot time used
>XL.PUB.SYS.  This effectively meant XL.PUB.SYS couldn't be modified on-line.
>I have no idea where the system stands at this point.  Can someone else
>comment?]
 
Well,
 
  On both my 4.0 and 5.0 systems, pin 1 opens the ficticious file
PROGEN.PUB.SYS.  But file number 8, which is the program file name, is
XL.PUB.SYS and shows (via :LISTF,3) 1 accessor, shared, 1 reader.
 
  Unfortunately, even if XL.PUB.SYS wasn't being opened by pin 1.  It would be
opened by any user that was running a program pointing to the new HZCICOMMAND
pseudo-intrinsic.  Now, this doesn't mean that it is pointless.  It would
alleviate the problem of shutting the system down every time I wanted to make a
change to HZCICOMMAND.  I would just have to log ever user off instead
(pseudo-online changes:))
 
  On a side note, I have encountered a show stopper that I failed to consider.
Vendors need to issue CI commands of their own.  I therefore need a way to
determine if the command being issued is for the program or for the user and as
far as I can tell, there is no way of doing this unless the vendor provides
some
kind of mechanism of their own.  Ironically, I know of atleast one vendor who
did this, although I think it was by accident.  Robelle's QEDIT program makes
calls to the COMMAND intrinsic for commands that the program needs while
passing
user commands via the HPCICOMMAND intrinsic.  By doing it this way, Robelle is
allowing me to disable the HPCICOMMAND intrinsic without affecting their
program
which issues his own commands via the COMMAND intrinsic.
 
  BTW, you were right in one other thing.  I am looking to control access to CI
commands BY USER and BY PROGRAM.  By wanting this, HP Security Monitor is not a
viable solution.
 
  Also, thanks for replying to this message Mike.  It's nice to see HP
participating so actively in the newsgroups:)
 
 
 
-------------------------------------------------------------------
Michael P. Smith                        [log in to unmask]
HP Systems Programmer                   [log in to unmask]
Hertz Corporation, Oklahoma City, OK
-------------------------------------------------------------------
 
 'Be a team player, it diffuses the blame'  - Dilbert
 
-------------------------------------------------------------------
The views and opinions expressed in this document are expressly
my own.  So get off the couch, I obviously need more help than you.