SQL/MP Installation and Management Guide

Licensed SQLCI2 Process
HP NonStop SQL/MP Installation and Management Guide—523353-004
A-2
Running SQLCI2 as another user
To use the licensed SQLCI2 process, create a DEFINE that enables SQLCI to use the
licensed SQLCI2 version rather than the normal SQLCI2 version. This protects you
from making unintended changes to your system when you are logged on as
super.super.
You must log on as the super ID and create the =_SQL_CI2_sys DEFINE, pointing to
the licensed version. Use this command:
38> ADD DEFINE =_SQL_CI2_sys, CLASS MAP, FILE
$SYSTEM.SYSTEM.SQLCI2L
In the command, sys is the node (system) name without the backslash.
While this DEFINE is in effect, SQLCI automatically uses the SQLCI2 version in the
SQLCI2L file. To stop using the licensed process, you must either end the SQLCI
session and delete the DEFINE or log off as the super ID.
This command deletes the DEFINE:
48> DELETE DEFINE =_SQL_CI2_sys
In the command, sys is the node name without the backslash.
Running SQLCI2 as another user
For another example, suppose that you want to set up licensing so that a specific
group or specific users can execute it. Select a name for a subvolume on $SYSTEM
exclusively for licensed processes, for example $SYSTEM.LICENSED. and copy
SQLCI, SQLCI2, and SQLUTIL from $SYSTEM.SYSTEM to this subvolume.
Enter these commands at the command interpreter prompt:
33> LOGON SUPER.SUPER, password
34> FUP DUP $SYSTEM.SYSTEM.SQLCI, $SYSTEM.LICENSED.SQLCI
34> FUP DUP $SYSTEM.SYSTEM.SQLCI2, $SYSTEM.LICENSED.SQLCI2
34> FUP DUP $SYSTEM.SYSTEM.SQLUTIL, $SYSTEM.LICENSED.SQLUTIL
36> SQLCOMP /IN SQLCI2L/ CATALOG $SYSTEM.SQL
37> FUP LICENSE $SYSTEM.LICENSED.SQLCI2
37> FUP LICENSE $SYSTEM.LICENSED.SQLUTIL
Finally, use FUP or Safeguard to limit who can execute the programs in this
subvolume.
Those users can then start SQLCI with this command:
RUN $SYSTEM.LICENSED.SQLCI