SQL/MX Remote Conversational Interface (RMXCI) Guide for SQL/MX Release 3.1 (H06.23+, J06.12+)

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.
Syntax
QUIT [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.
condition
is the same as the condition parameter defined for the “IF...THEN command” (page 69). See
“Condition Parameter” (page 69).
Considerations
You must enter the command in one line.
Examples
The following command disconnects from the database platform and exits RMXCI:
SQL>quit
If the previously run command returns the error code 4082, the conditional exit command
stops running the script file and then disconnects and exits from RMXCI.
log /usr/home/rmxci/log/errorCode.log
select * from employee;
quit if errorcode=4082
log off
The following results are logged on getting error 4082:
SQL>select * from employee;
*** ERROR[4082] Table, view or stored procedure
NONSTOP_SYSTEM_NSK.PUBLIC_ACCESS_SCHEMA.USR.EMPLOYEE
does not exist or is inaccessible.
SQL>quit if errorcode=4082
RECONNECT command
The reconnect command creates a new connection to the database platform using the login
credentials of the last successful connection.
QUIT command 79