MX Release 3.1 (H06.23+, J06.12+)

SQL>CREATE SCHEMA INVENT;

--- SQL operation complete.

SQL>-- CREATE TABLES/VIEWS in SCHEMA INVENT

SQL>SET SCHEMA INVENT;

--- SQL operation complete.

SQL>CREATE TABLE INVENT.supplier

+> suppnum NUMERIC (4) UNSIGNED NO DEFAULT NOT NULL

+> ,suppname CHARACTER (18)NO DEFAULT NOT NULL

+> ,street CHARACTER (22) NO DEFAULT NOT NULL

+> ,city CHARACTER (14) NO DEFAULT NOT NULL

+> ,state CHARACTER (12) NO DEFAULT NOT NULL

+> ,postcode CHARACTER (10) NO DEFAULT NOT NULL

+> ,PRIMARY KEY (suppnum)

);

--- SQL operation complete.

For more information about the @ and obey commands, see the “@ command” (page 57) and the

“OBEY command” (page 74).

Logging output

To log output of a RMXCI session while running one script file at a time, use the spool or log

command. When you run an obey or @ command, RMXCI displays each command in the script

file, the output for each command, and diagnostic messages in the SQL/MX Remote Conversational

Interface. The spool or log command captures this output as it appears in the SQL/MX Remote

Conversational Interface and logs it in a log file.

For more information, see “Logging output” (page 45).

Running scripts in parallel

In RMXCI, the @ and obey commands enable you to run only one script file at a time. However,

the prun command enables you to run multiple script files simultaneously.

NOTE: The prun command can be run in noninteractive mode. The command allows options

to be specified on the command-line, which enables prun to be run in script and/or obey files.

The prun command is most useful for running sets of Data Definition Language (DDL)

statements simultaneously, which speeds up the process of creating large databases. Put all

dependent or related DDL statements in the same script file.

For more information on running scripts in parallel using the prun command, see the “PRUN

command” (page 77).

50 Running scripts in RMXCI