Data Build Manual

Customizing SQL-LOAD Output
Customizing Data Build
099331 Tandem Computers Incorporated 6–27
3. Edit NEWLOAD and add CPU x (same x) to each of the SQLCI commands; there
will be one SQLCI command for each table to be loaded by the conversion
program, for example:
SQLCI/CPU x , OUT $S.#ZZLOAD1/LOAD $ZBLD,=TABLE1,SORTED, &
RECIN 0051, BLOCKIN 31977, SOURCEREC OUT-filename ; EXIT;
4. Insert the following command before the first SQLCI LOAD command.
RUN ZZPROGMX /NAME $ZBLD, CPU y, NOWAIT/
5. Add a CPU parameter to the SQLMSGS command and specify any CPU other than
the CPU on which SQLCI runs. Do not change the table name:
RUN $ vol .ZDATABLD.SQLMSGS/name $ZBLDE, &
CPU z ,NOWAIT/ tablename
6. OBEY DEFINES.
7. OBEY NEWLOAD.
To perform steps 6 and 7 at a later time, set the default subvolume to the project
subvolume where the DEFINES file is located. This subvolume also contains the
dictionary for SOURCEREC in the SQLCI command.
Since the SQLUTIL process can consume 100% of a CPU, SQLCI should be run in a
different CPU than the CPU the input and output devices are attached to.
Running Multiple SQL-
LOADS at the Same Time
To run multiple SQL-LOADs concurrently, simply setup multiple OBEY files as
described in the previous subsection.
Change $ZBLD to a different process name; note that there are at least two $ZBLDs in
each OBEY file; there is a $ZBLD in the RUN ZZPROGMX command and, for each
input file to be converted, there is a $ZBLD in each associated SQLCI command. Each
occurrence of $ZBLD must be changed to the same name.
Change $ZBLDE to a different process name; note that there are two $ZBLDEs for
every table in each OBEY (command) file. There is a $ZBDLE in the RUN SQLMSGS
command and for the following SQLCI OUT parameter. All $ZBLDEs in each OBEY
(command) file can be changed to the same name. SQLMSGS and SQLCI should
always run as a pair. OBEY (command) files which are active concurrently must have
different $ZBLD and $ZBLDE process names between them, but they may be the same
within the same OBEY (command) file.
All SQLCI processes associated with the same conversion program process name run
sequentially and should not be run NOWAITed; there is no advantage to run these
SQLCI processes in different CPUs. If SQLCI processes for different conversion
program process names run concurrently, they should execute in a different CPU
because the SQLUTIL process is CPU intensive.