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

Cause: An obey file with an infinite loop was run. This loop was caused by a nested obey either
directly by obeying itself or indirectly (for example, by obeying another file, which in turn obeys
the original).
Effect: The obey command is halted. No other obey files are run and control returns to the session
prompt.
Recovery: Reduce the depth of nested obey and then run the script. Ensure that there are no loops
in your nested obey calls. For example: Consider files A.sql, B.sql, and C.sql. You obey A.sql
which obeys B.sql which in turn obeys C.sql. Ensure that C.sql does not obey A.sql.
29468
Session Disconnected. Please connect to the database by using
connect/reconnect command.
Cause: Connection to the NonStop system has been lost. One reason for this issue might be network
problems.
Effect: Most RMXCI commands fail.
Recovery: Connect to the NonStop platform with the connect or reconnect command and retry
the commands.
29469
Unable to align display for multi-byte characters.
Cause: The results displayed were not aligned when the data had multi-byte characters.
Effect: The results displayed are not in tabular format.
Recovery: Not applicable.
29471
Unable to find RMXCI variable.
Cause: A conditional statement with a non quoted string was specified. RMXCI interprets this as
a variable. This variable was not found in the environment as a SQL parameter or as a RMXCI
variable in lasterror, errorcode, reccount or activitycount. commands.
Effect: The conditional statement fails to run.
Recovery: For SQL param, ensure that the variable is prefixed by a question mark. Check the
spelling for the environment or RMXCI variable.
29472
Unable to compare an integer with a string.
Cause: The left side of a conditional statement was an integer and the right side was a string.
Effect: The conditional statement fails to run.
Recovery: Not applicable.
29473
Unable to compare a string with an integer.
Cause: The left side of a conditional statement was a string and the right side was an integer.
Effect: The conditional statement fails to run.
Recovery: Not applicable.
29474
Unable to compare strings using the operator.
Cause: An operator other than =, ==, <>, !=, ~=, ^= was used to compare strings.
Effect: The conditional statement fails to run.
Recovery: Specify allowed operators for comparing strings and retry the statement.
128 Error messages