SQL/MP Reference Manual
HP NonStop SQL/MP Reference Manual—523352-013
P-11
Sample Configuration File
Sample Configuration File
== Sample configuration file for loading index
== partitions in parallel. Creates index AGEINDEX
== on table CUST, which is partitioned as follows:
== $DATA1.SALES.CUST
== $DATA2.SALES.CUST
== $DATA3.SALES.CUST
== \NEWYORK.$DATA1.SALES.CUST
== AGEINDEX is partitioned as follows:
== $DATA4.SALES.AGEINDEX
== $DATA5.SALES.AGEINDEX
== \NEWYORK.$DATA2.SALES.AGEINDEX
== \NEWYORK.$DATA3.SALES.AGEINDEX
== Set up a default priority for the RECGEN processes:
CREATEINDEX BASETABLE DEFAULT PRI ( 140 )
CREATEINDEX BASETABLE DEFAULT \NEWYORK PRI ( 140 )
== Set up default pools of scratch files for
== the sort processes.
CREATEINDEX INDEX DEFAULT SCRATCH ($TEMP1,$TEMP2,$TEMP3)
CREATEINDEX INDEX DEFAULT \NEWYORK SCRATCH ($TEMP4,$TEMP5)
== Request that overflow scratch files avoid certain
== disks: those specified plus $SYSTEM and TM/MP audit
== trail disks.
CREATEINDEX INDEX DEFAULT NOSCRATCHON ($SYS*,$WORK*)
== Request that overflow scratch files use specific
== disks on the remote node.
CREATEINDEX INDEX DEFAULT \NEWYORK SCRATCHON ($TEMP*)
== Request that the $data3 sort process use $temp7 for
== scratch space.
CREATEINDEX INDEX \NEWYORK.$data3 SCRATCH ($TEMP7)
== End of Configuration File
Parameters
Parameters let you provide literals for prepared DML statements or command files
when you execute the statements or commands (using EXECUTE or OBEY) rather
than when you PREPARE or create them. You can use parameters for literals in DML
statements compiled with PREPARE or for literals in SQLCI command files.
Typically, you use parameters instead of literals so that you can PREPARE a statement
at one time and execute it later—possibly multiple times—substituting different values
for each execution with the USING clause of EXECUTE.
If you use named parameters, you can also use the TACL PARAM command or the
SQLCI SET PARAM command to assign values to the parameters before you issue an
EXECUTE (for a statement) or OBEY (for a command file). In this case, you can also
reuse the parameters in subsequent executions of the statement or command file
without resetting them.