SQL/MP Installation and Management Guide

Installing SQL/MP
HP NonStop SQL/MP Installation and Management Guide—523353-004
2-8
Initializing SQL/MP
You can use the FUP SECURE command to alter the security of these programs and
the FUP LICENSE command to license the programs, if necessary. To alter the
security of the SQL sensitive program SQLCI2, you can either use the SQL ALTER
PROGRAM statement or the FUP SECURE command.
1. If old versions of SORT, SORTPROG, and RECGEN programs still exist on
$SYSTEM.SYSTEM, remove them now by entering this command at the command
interpreter prompt:
26> PURGE $SYSTEM.SYSTEM.SORT, $SYSTEM.SYSTEM.SORTPROG,
$SYSTEM.SYSTEM.RECGEN
If SORT, SORTPROG, or RECGEN programs exist on $SYSTEM.SYSTEM from a
previous RVU, the results are unpredictable.
SQL/MP uses the FastSort programs SORT and SORTPROG for sorting
operations and the RECGEN program for parallel loading of indexes. The INSTALL
process moves these programs to the SYSnn subvolume (in which nn is two digits
assigned during system generation).
2. Verify that the SORT, SORTPROG, and RECGEN programs on the SYSnn
subvolume are secured for execute access on your node. If your node runs in a
network, check that these programs are secured for network execute access. If
SQL/MP initiates a SORT operation and the SORT, SORTPROG, or RECGEN
security does not allow access, a run-time sort error, Sort Start Error 4, is
generated.
You can use the FUP SECURE command to alter the security of these programs, if
necessary.
3. Check that the SQLMSG file you are using is the one released with the new
version of SQL/MP. The message file contains error messages, warning
messages, and help text for SQL/MP. You can check the version by running SQLCI
and entering the ENV command; the message file version is listed as
MESSAGEFILE VRSN in the ENV output.
Check that these message files are secured for read access on your node:
$SYSTEM.SYSTEM.SQLMSG
$SYSTEM.SYSTEM.NLCPMSG
If your node is part of a network, check that these message files are secured for
network read access. If necessary, secure them for network access by entering
these commands:
32> FUP SECURE ($SYSTEM.SYSTEM.SQLMSG, &
32> & $SYSTEM.SYSTEM.NLCPMSG), “NN-N”
Note. The SQLCI2 program is not licensed under normal circumstances. Only the super ID
can license the SQLCI2 program. For more information, see Appendix A, Licensed SQLCI2
Process.