SQL/MX Remote Conversational Interface (RMXCI) Guide for SQL/MX Release 3.2 (H06.25+, J06.14+)

Total files present ......................99
Total files processed ....................99
Total sqls processed ....................198
Total errors ..............................0
Total warnings ............................0
Total warnings ............................0
Total connections .........................5
Total connection failures..................0
============================================================================
PRUN completed at Jul 11, 2011 9:33:21 AM
============================================================================
• On Windows, the following prun command initiates a parallel run operation with the -d
option:
SQL>prun -d
SQL> prun -scriptsdir C:\mydir\Testing\samples\ -ld C:\mydir\Testing\logs\ -e sql -o n -c 10
PRUN options are -scriptsdir C:\mydir\Testing\samples\
-logsdir C:\mydir\Testing\logs\
-extension sql
-overwrite n
-connections 10
Status: Complete
_____________________________________________
PARALLELRUN(PRUN)SUMMARY
_____________________________________________
Total files present ......................10
Total files processed ....................10
Total sqls processed ....................62
Total errors ..............................0
Total warnings ............................0
Total successes ............................62
Total connections .........................10
Total connection failures..................0
• The prun command can be started in noninteractive mode using the –q parameter:
rmxci.sh -h nsksys.ind.hp.com -dsn
TDM_Default_DataSource -u super.super -p host1
-q "prun –sd /usr/home/rmxci/prun -o y -c 3"
• The following prun command is started in non interactive mode from an obey file:
SQL>obey startPrun.txt
SQL>prun -sd /usr/home/rmxci/prun -ld /usr/home/rmxci/prun/logs -e sql -o y -c 5
PRUN options are -scriptsdir /usr/home/rmxci/prun
-logsdir /usr/home/rmxci/prun/logs
-extension sql
-overwrite yes
-connections 5
Status: Complete
For a summary of all errors and warnings that occurred during the prun operation, go to the
error subdirectory in the same directory as the log files (for example,
/usr/home/rmxci/log/error) and open the prun.err.log summary file.
For details about the errors that occurred during the execution of a script file, open each individual
log file (<script-file.sql>.log)
QUIT command
The quit command disconnects from the database and exits the RMXCI session. This command
is an alternative to the exit command.
Syntax
EXIT [[WITH]{status}] [IF{condition}]
status
is any 1-byte integer. The status is a shell return value, and the range of allowable values
is platform dependent.
QUIT command 101