🚀 go-pugleaf

In article <19671.2b5ebe5f@ecs.umass.edu>, jhwelch@ecs.umass.edu writes:
> Since a LICENSE LOAD command realizes it's already loaded somewhere
> else there must be an undocumented system call that performs this
> task.  EXE$CHECK_LICENSE looks like a promising area to investigate
> but of course it's not on the listing CD.

  Yup. None of this is documented and it makes it hard to do things such as
the one you suggest. Of course, it also makes it hard for the bad guys to
do nasty things (or at least that seems to be DEC's reasoning).

  LICENSE LOAD loads licenses from the LDB into kernel-mode logicals, doing
some checks along the way. I would guess that it uses some form of cluster
communication to verify and possibly adjust the logicals on other nodes dur-
ing the load.

  If you have something to monitor (and even better, decode) SCS or lock
manager traffic on the net, you might look to see what's being passed. The
logicals live in LMF$LICENSE_TABLE, so a SHOW LOG/TABLE=LMF$LICENSE_TABLE
will show you the licenses currently loaded. Once you see the format of the
logical names, you can easily check to see if a license is loaded for any
combination of producer and product.

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381