[07/13] incubator-trafodion git commit: Created the initial version of the Trafodion Messages Manual. Fixed broken links between different manuals.

[db...@apache.org]

http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/e77d8018/docs/messages_guide/src/asciidoc/_chapters/executor_msgs.adoc
----------------------------------------------------------------------
diff --git a/docs/messages_guide/src/asciidoc/_chapters/executor_msgs.adoc b/docs/messages_guide/src/asciidoc/_chapters/executor_msgs.adoc
new file mode 100644
index 0000000..26fa1c4
--- /dev/null
+++ b/docs/messages_guide/src/asciidoc/_chapters/executor_msgs.adoc
@@ -0,0 +1,935 @@
+////
+/**
+* @@@ START COPYRIGHT @@@
+*
+* Licensed to the Apache Software Foundation (ASF) under one
+* or more contributor license agreements.  See the NOTICE file
+* distributed with this work for additional information
+* regarding copyright ownership.  The ASF licenses this file
+* to you under the Apache License, Version 2.0 (the
+* "License"); you may not use this file except in compliance
+* with the License.  You may obtain a copy of the License at
+*
+*   http://www.apache.org/licenses/LICENSE-2.0
+*
+* Unless required by applicable law or agreed to in writing,
+* software distributed under the License is distributed on an
+* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+* KIND, either express or implied.  See the License for the
+* specific language governing permissions and limitations
+* under the License.
+*
+* @@@ END COPYRIGHT @@@
+  */
+////
+
+[[executor-messages]]
+= Executor Messages (8000 through 8999)
+
+[[SQL-8006]]
+== SQL 8006
+
+```
+The stream timed out, but the cursor is still open.
+```
+
+*Cause:* A cursor is still open although its stream timed out.
+
+*Effect:* The operation fails.
+
+*Recovery:* Close the cursor before trying to open it.
+
+[[SQL-8007]]
+== SQL 8007
+
+```
+The operation has been canceled.
+```
+
+*Cause:* You pressed the break key.
+
+*Effect:* The operation stops.
+
+*Recovery:* None.
+
+<<<
+[[SQL-8012]]
+== SQL 8012
+
+```
+8012 Encoding of CONTROL QUERY DEFAULTs: <encoding>.
+```
+
+*Cause:* Trafodion displays an internal CONTROL
+QUERY DEFAULT encoding.
+
+*Effect:* None.
+
+*Recovery:* This is an informational message only; no corrective action
+is needed.
+
+[[SQL-8016]]
+== SQL 8016
+
+```
+An attempt was made to access <name> which has a system version that is incompatible with the version of the accessing software.
+```
+
+*Cause:* You attempted to access a system version that is incompatible
+with the version of the accessing software.
+
+*Effect:* The operation fails.
+
+*Recovery:* The system you are trying to access must be on a system
+version that is compatible with your accessing software. Upgrade that
+system.
+
+<<<
+[[SQL-8017]]
+== SQL 8017
+
+```
+Explain information is not available for this query.
+```
+
+*Cause:* The explain default has been turned off for this query.
+
+*Effect:* Trafodion is not able to display explain
+information.
+
+*Recovery:* Turn the explain default on for this query.
+
+[[SQL-8101]]
+== SQL 8101
+
+```
+The operation is prevented by check constraint <name-1> on table <name-2>.
+```
+
+Where constraint <name-1> is the name of the constraint.
+
+Where table <name-2> is the name of the table.
+
+*Cause:* You attempted to perform an operation on table <name-1> that is
+prevented by check constraint <name-2>.
+
+*Effect:* The operation fails.
+
+*Recovery:* Change the data you are attempting to enter to be consistent
+with the constraint.
+
+<<<
+[[SQL-8102]]
+== SQL 8102
+
+```
+The operation is prevented by a unique constraint.
+```
+
+*Cause:* You attempted to perform an operation that is prevented by a
+unique constraint.
+
+*Effect:* Trafodion could not perform the
+operation.
+
+*Recovery:* Make the data you enter unique to be consistent with the
+constraint.
+
+[[SQL-8103]]
+== SQL 8103
+
+```
+The operation is prevented by referential integrity constraint <name-1> on table <name-2>.
+```
+
+Where <name-1> is the name of the constraint.
+
+Where <name-2> is the name of the table.
+
+*Cause:* You attempted to perform an operation on table <name-1> that is
+prevented by referential integrity constraint <name-2>.
+
+*Effect:* The operation fails.
+
+*Recovery:* Change the data you are attempting to enter to be consistent
+with the constraint. The data must exist in another table. For example,
+if you are trying to enter a department number for an employee, the
+department number must exist in a department number table.
+
+<<<
+[[SQL-8104]]
+== SQL 8104
+
+```
+The operation is prevented by the check on view <name-1> cascaded from the check option on <name-2>.
+```
+
+Where view <name-1> is the name of the view.
+
+Where <name-2> is the name of the table.
+
+*Cause:* You attempted to perform an operation on table <name-1>. The
+operation has been prevented by the check on view <name-2>, cascaded
+from the check option on the table.
+
+*Effect:* The operation fails.
+
+*Recovery:* Change the view properties, if appropriate.
+
+[[SQL-8105]]
+== SQL 8105
+
+```
+The operation is prevented by the check option on view <name>.
+```
+
+Where <name> is the name of the view.
+
+*Cause:* You attempted to perform an operation on table name that is
+prevented by the check option on view <name>.
+
+*Effect:* The operation fails.
+
+*Recovery:* Insert into the base table rather than this view.
+
+<<<
+[[SQL-8302]]
+== SQL 8302
+
+```
+All partitions of <type> <object> are unavailable.
+```
+
+Where <type> is the type of the affected object, such as table.
+
+Where <object> is the fully qualified ANSI name of the affected object.
+
+*Cause:* Late name resolution could not resolve the ANSI name to an
+available partition.
+
+*Effect:* The operation fails.
+
+*Recovery:* Determine why none of the partitions were available, then
+correct the error and resubmit.
+
+[[SQL-8553]]
+== SQL 8553
+
+```
+Stream overflow; subscription rate has fallen too far behind publishing rate.
+```
+
+*Cause:* The table used by the streaming cursor has overflowed.
+
+*Effect:* The cursor or statement is closed.
+
+*Recovery:* Reopen the statement or cursor and resume subscribing.
+
+<<<
+[[SQL-8573]]
+== SQL 8573
+
+8573 The user does not have <level> privilege on table or view <name>.
+
+Where <level> is the user privilege level.
+
+Where <name> is the name of the object.
+
+*Cause:* You attempted to perform an operation on object <name>, for
+which you do not have a sufficient privilege <level>.
+
+*Effect:* The operation fails.
+
+*Recovery:* None. Have the system administrator change your privilege
+level, if appropriate.
+
+[[SQL-8576]]
+== SQL 8576
+
+```
+Statement was recompiled.
+```
+
+*Cause:* Trafodion recompiled the statement.
+
+*Effect:* The operation fails.
+
+*Recovery:* Recompile the program.
+
+<<<
+[[SQL-8577]]
+== SQL 8577
+
+```
+Table, index or view <name> was not found.
+```
+
+Where <name> is the name of the object.
+
+*Cause:* Trafodion could not find the object
+<name>.
+
+*Effect:* The operation fails.
+
+*Recovery:* Verify the location of the object and resubmit.
+
+[[SQL-8578]]
+== SQL 8578
+
+```
+Similarity check passed.
+```
+
+*Cause:* The similarity check passed.
+
+*Effect:* None.
+
+*Recovery:* Informational message only; no corrective action is needed.
+
+<<<
+[[SQL-8579]]
+== SQL 8579
+
+```
+Similarity check failed: <name>
+```
+
+*Cause:* The similarity check failed.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the syntax and resubmit.
+
+[[SQL-8604]]
+== SQL 8604
+
+```
+Transaction subsystem <name> returned error <number> while starting a transaction.
+```
+
+Where <name> is the subsystem name.
+
+Where <number> is the error number.
+
+*Cause:* Transaction subsystem <name> has returned error <number> while
+starting a transaction.
+
+*Effect:* The operation fails.
+
+*Recovery:* Contact the mailto:user@trafodion.incubator.apache.org[Trafodion User Distribution mailing list].
+
+<<<
+[[SQL-8605]]
+== SQL 8605
+
+```
+Committing a transaction which has not started.
+```
+
+*Cause:* You attempted to commit a transaction that has not been
+started.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the syntax so that the transaction is started before
+it is committed, and resubmit.
+
+[[SQL-8606]]
+== SQL 8606
+
+```
+Transaction subsystem <name> returned error <number> on a commit transaction.
+```
+
+Where <name> is the name of the subsystem.
+
+Where <number> is the error number.
+
+*Cause:* Transaction subsystem <name> has returned error <number> while
+committing a transaction.
+
+*Effect:* The operation fails.
+
+*Recovery:* Contact the mailto:user@trafodion.incubator.apache.org[Trafodion User Distribution mailing list].
+
+<<<
+[[SQL-8607]]
+== SQL 8607
+
+```
+Rolling back a transaction that has not started.
+```
+
+*Cause:* You attempted to roll back a transaction that has not started.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the syntax so that the sequence of events is
+correct, and resubmit.
+
+[[SQL-8608]]
+== SQL 8608
+
+```
+Transaction subsystem <name> returned error <number> on rollback transaction.
+```
+
+Where <name> is the name of the subsystem.
+
+Where <number> is the error number.
+
+*Cause:* Transaction subsystem <name> has returned error <number> while
+rolling back a transaction.
+
+*Effect:* The operation fails.
+
+*Recovery:* Contact the mailto:user@trafodion.incubator.apache.org[Trafodion User Distribution mailing list].
+
+<<<
+[[SQL-8609]]
+== SQL 8609
+
+```
+Waited rollback performed without starting a transaction.
+```
+
+*Cause:* You attempted to perform a waited rollback on a transaction
+that has not started.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the syntax so that the sequence of events is
+correct, and resubmit.
+
+[[SQL-8610]]
+== SQL 8610
+
+```
+Transaction subsystem <name> reported error <number> on a waited rollback transaction.
+```
+
+Where <name> is the name of the subsystem.
+
+Where <number> is the error number.
+
+*Cause:* Transaction subsystem <name> has returned error <number> while
+performing a waited rollback transaction. *Effect:* The operation fails.
+
+*Recovery:* Contact the mailto:user@trafodion.incubator.apache.org[Trafodion User Distribution mailing list].
+
+<<<
+[[SQL-8612]]
+== SQL 8612
+
+```
+Transaction mode cannot be set if the transaction is already running.
+```
+
+*Cause:* You attempted to set the transaction mode, but the transaction
+is already running.
+
+*Effect:* The operation fails.
+
+*Recovery:* Abort and restart the transaction if you must change its
+mode.
+
+[[SQL-8613]]
+== SQL 8613
+
+```
+SQL cannot commit or rollback a transaction that was started by application.
+```
+
+*Cause:* An application started a transaction outside of Trafodion that Trafodion could not commit
+or rollback.
+
+*Effect:* The operation fails.
+
+*Recovery:* The application that started the transaction must perform a
+commit or rollback. Trafodion must start any transactions it will later commit or rollback.
+
+<<<
+[[SQL-8808]]
+== SQL 8808
+
+```
+Module file <name> contains corrupted or invalid data.
+```
+
+Where <name> is the name of the file.
+
+*Cause:* Trafodion has detected corrupted or
+invalid data in the module file <name>.
+
+*Effect:* Trafodion could not execute the file.
+
+*Recovery:* Recompile the .mdf file, using the Trafodion compiler, to
+create a valid module file.
+
+[[SQL-8809]]
+== SQL 8809
+
+```
+Open of the module file <name> failed with error <number>.
+```
+
+Where <name> is the name of the file.
+
+Where <number> is the error number returned.
+
+*Cause:* Trafodion was unable to open module file
+<name>.
+
+*Effect:* The operation fails.
+
+*Recovery:* Check the location of the module file and retry the
+operation.
+
+<<<
+[[SQL-8819]]
+== SQL 8819
+
+```
+Begin transaction failed while preparing the statement.
+```
+
+*Cause:* This is an internal error.
+
+*Effect:* The operation fails.
+
+*Recovery:* None. Contact the mailto:user@trafodion.incubator.apache.org[Trafodion User Distribution mailing list].
+
+[[SQL-8820]]
+== SQL 8820
+
+```
+Transaction commit failed while closing the statement.
+```
+
+*Cause:* This is an internal error.
+
+*Effect:* The operation fails.
+
+*Recovery:* None. Contact the mailto:user@trafodion.incubator.apache.org[Trafodion User Distribution mailing list].
+
+<<<
+[[SQL-8821]]
+== SQL 8821
+
+```
+Rollback transaction failed during the process of fetching the statement.
+```
+
+*Cause:* This is an internal error.
+
+*Effect:* The operation fails.
+
+*Recovery:* None. Contact the mailto:user@trafodion.incubator.apache.org[Trafodion User Distribution mailing list].
+
+[[SQL-8824]]
+== SQL 8824
+
+```
+The input <module-id> does not have a module name.
+```
+
+*Cause:* A module name was not passed into the module ID structure that
+was passed in.
+
+*Effect:* The operation fails.
+
+*Recovery:* Make sure a module name is passed into the module ID
+structure.
+
+<<<
+[[SQL-8826]]
+== SQL 8826
+
+```
+The module could not be added.
+```
+
+*Cause:* This is an internal error.
+
+*Effect:* The operation fails.
+
+*Recovery:* None. Contact the mailto:user@trafodion.incubator.apache.org[Trafodion User Distribution mailing list].
+
+[[SQL-8827]]
+== SQL 8827
+
+```
+The request <name> could not be sent.
+```
+
+Where <name> is the name of the request.
+
+*Cause:* Trafodion was unable to send request <name>. 
+
+*Effect:* The operation fails.
+
+*Recovery:* Use the errors that accompany this one to diagnose and
+correct the problem.
+
+<<<
+[[SQL-8832]]
+== SQL 8832
+
+```
+Transaction has not been started.
+```
+
+*Cause:* A transaction has not been started.
+
+*Effect:* The operation fails.
+
+*Recovery:* Verify that the transaction has been started or start it if
+it has not been.
+
+[[SQL-8833]]
+== SQL 8833
+
+```
+The input parameter is an invalid SQL transaction command.
+```
+
+*Cause:* This is an internal error.
+
+*Effect:* The operation fails.
+
+*Recovery:* None. Contact the mailto:user@trafodion.incubator.apache.org[Trafodion User Distribution mailing list].
+
+<<<
+[[SQL-8834]]
+== SQL 8834
+
+```
+The SQL installation directory could not be found. Operating system error <number>.
+```
+
+Where <number> is the error number.
+
+*Cause:* Trafodion was unable to find the Trafodion installation directory and 
+received an operating system error <number>.
+
+*Effect:* The operation fails.
+
+*Recovery:* Locate the Trafodion installation directory,
+correct your syntax, and resubmit.
+
+[[SQL-8836]]
+== SQL 8836
+
+```
+Application specified an invalid update column for cursor.
+```
+
+*Cause:* There is an error in the program that this code is embedded in.
+The build might not have completed correctly.
+
+*Effect:* The operation fails.
+
+*Recovery:* Verify that the build was successful and resubmit.
+
+<<<
+[[SQL-8837]]
+== SQL 8837
+
+```
+The user id passed in is invalid.
+```
+
+*Cause:* The value of the user ID passed in is not valid.
+
+*Effect:* The operation fails.
+
+*Recovery:* Make sure that the user ID of the form `group id | name, user id | user name`, 
+and that the password is valid and exists on the current system.
+
+[[SQL-8840]]
+== SQL 8840
+
+```
+Object name provided to CLI is not valid.
+```
+
+*Cause:* The object named provided to CLI is invalid 
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the object name and resubmit.
+
+<<<
+[[SQL-8841]]
+== SQL 8841
+
+```
+User application committed or aborted a transaction started by SQL. This transaction needs to be committed or aborted by calling SQL COMMIT or ROLLBACK WORK.
+```
+
+*Cause:* Trafodion started a transaction that was committed or aborted by an embedded program, 
+rather than by Trafodion.
+
+*Effect:* The operation fails.
+
+*Recovery:* Commit or abort the transaction by calling SQL COMMIT or
+
+ROLLBACKWORK.
+
+[[SQL-8842]]
+== SQL 8842
+
+```
+The cursor, <name>, referenced by this statement is not found or is not updatable.
+```
+
+Where <name> is the name of the cursor.
+
+*Cause:* There is an error in the program that this code is embedded in.
+The build might not have completed successfully.
+
+*Effect:* The operation fails.
+
+*Recovery:* Verify that the build was successful and resubmit.
+
+<<<
+[[SQL-8846]]
+== SQL 8846
+
+```
+An empty SQL statement was passed in.
+```
+
+*Cause:* The SQL source statement passed to the compiler to do the
+prepare was empty.
+
+*Effect:* The operation fails.
+
+*Recovery:* You must pass in a valid SQL source statement.
+
+[[SQL-8850]]
+== SQL 8850
+
+```
+The table specified in this cursor update or delete statement is different than the table specified in the declare cursor statement.
+```
+
+*Cause:* The table specified in the update or DELETE statement is not
+the same as the one specified in the declare cursor statement, as is
+required.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the syntax and resubmit.
+
+<<<
+[[SQL-8860]]
+== SQL 8860
+
+```
+Module file <name> has an obsolete module header.
+```
+
+Where <name> is the file name.
+
+*Cause:* The module file <name> has an obsolete module header.
+
+*Effect:* The operation fails.
+
+*Recovery:* Rebuild the module file and resubmit.
+
+[[SQL-8861]]
+== SQL 8861
+
+```
+Module file <name> has an obsolete descriptor location table header.
+```
+
+Where <name> is the file name.
+
+*Cause:* The module file <name> has an obsolete table header.
+
+*Effect:* The operation fails.
+
+*Recovery:* Rebuild the module file and resubmit.
+
+<<<
+[[SQL-8862]]
+== SQL 8862
+
+```
+Module file <name> has an obsolete descriptor location table entry.
+```
+
+Where <name> is the file name.
+
+*Cause:* The module file <name> has an obsolete descriptor location
+table entry.
+
+*Effect:* The operation fails.
+
+*Recovery:* Rebuild the module file and resubmit.
+
+[[SQL-8863]]
+== SQL 8863
+
+```
+Module file <name> has an obsolete descriptor header.
+```
+
+Where <name> is the file name.
+
+*Cause:* The module file <name> has an obsolete descriptor header.
+
+*Effect:* The operation fails.
+
+*Recovery:* Rebuild the module file and resubmit.
+
+<<<
+[[SQL-8864]]
+== SQL 8864
+
+```
+Module file <name> has an obsolete descriptor entry.
+```
+
+Where <name> is the file name.
+
+*Cause:* The module file <name> has an obsolete descriptor entry.
+
+*Effect:* The operation fails.
+
+*Recovery:* Rebuild the module file and resubmit.
+
+[[SQL-8865]]
+== SQL 8865
+
+```
+Module file <name> has an obsolete procedure location table header.
+```
+
+Where <name> is the file name.
+
+*Cause:* The module file <name> has an obsolete procedure location table
+header.
+
+*Effect:* The operation fails.
+
+*Recovery:* Rebuild the module file and resubmit.
+
+<<<
+[[SQL-8866]]
+== SQL 8866
+
+```
+Module file <name> has an obsolete procedure location table entry.
+```
+
+Where <name> is the file name.
+
+*Cause:* The module file <name> has an obsolete procedure location table
+entry.
+
+*Effect:* The operation fails.
+
+*Recovery:* Rebuild the module file and resubmit.
+
+[[SQL-8867]]
+== SQL 8867
+
+```
+An error while reading from file <name>.
+```
+
+Where <name> is the file name.
+
+*Cause:* Trafodion encountered an error while
+reading the module file <name>.
+
+*Effect:* The operation fails.
+
+*Recovery:* Rebuild the module file and resubmit.
+
+<<<
+[[SQL-8882]]
+== SQL 8882
+
+```
+Containing SQL is not permitted.
+```
+
+*Cause:* A stored procedure registered with the NO SQL attribute
+attempted to access Trafodion.
+
+*Effect:* The corresponding SQL request is rejected.
+
+*Recovery:* Either change the definition of the stored procedure to
+allow SQL access, or determine why the stored procedure contains
+Trafodion  statements that might be called while the stored
+procedure is executing.
+
+[[SQL-8888]]
+== SQL 8888
+
+```
+The underlying insert, update, or delete operation of cursor <cursor-name> is still in progress. Since the cursor is being closed before the operation is complete, all affected rows will be rolled back.
+```
+
+<cursor-name> is the cursor being closed.
+
+*Cause:* A cursor with an underlying insert, delete, or update operation
+was closed before the operation was complete.
+
+*Effect:* The cursor was closed but all rows affected by opening this
+cursor have been rolled back.
+
+*Recovery:* OPEN the cursor again and FETCH all rows until SQLCODE = 100
+is returned.
+
+<<<
+[[SQL-8890]]
+== SQL 8890
+
+```
+The SQL compiler failed to initialize properly. Query results may differ from what is expected, due to different compiler defaults.
+```
+
+*Cause:* The Trafodion compiler failed to correctly initialize.
+
+*Effect:* Query results might be affected.
+
+*Recovery:* Stop the Trafodion  and restart it.
+
+[[SQL-8901]]
+== SQL 8901
+
+```
+The MXUDR server for this statement is no longer running. The statement will be assigned a new MXUDR server if it is executed again.
+```
+
+*Cause:* During execution of a Trafodion statement, an
+attempt was made to contact a nonexistent Trafodion UDR server.
+
+*Effect:* The operation fails.
+
+*Recovery:* Retry the Trafodion statement.
+
+<<<
+[[SQL-8904]]
+== SQL 8904
+
+```
+SQL/MX did not receive a reply from MXUDR, possibly caused by internal errors while executing user-defined routines.
+```
+
+*Cause:* During execution of a Trafodion statement,
+the Trafodion  did not receive an expected reply from
+the Trafodion UDR server.
+
+*Effect:* The operation fails.
+
+*Recovery:* Verify that the Trafodion UDR server is running. If
+not, the Trafodion statement will acquire a new
+Trafodion UDR server when it is next executed.
+
+

http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/e77d8018/docs/messages_guide/src/asciidoc/_chapters/file_system_errors.adoc
----------------------------------------------------------------------
diff --git a/docs/messages_guide/src/asciidoc/_chapters/file_system_errors.adoc b/docs/messages_guide/src/asciidoc/_chapters/file_system_errors.adoc
new file mode 100644
index 0000000..ba08d03
--- /dev/null
+++ b/docs/messages_guide/src/asciidoc/_chapters/file_system_errors.adoc
@@ -0,0 +1,529 @@
+////
+/**
+* @@@ START COPYRIGHT @@@
+*
+* Licensed to the Apache Software Foundation (ASF) under one
+* or more contributor license agreements.  See the NOTICE file
+* distributed with this work for additional information
+* regarding copyright ownership.  The ASF licenses this file
+* to you under the Apache License, Version 2.0 (the
+* "License"); you may not use this file except in compliance
+* with the License.  You may obtain a copy of the License at
+*
+*   http://www.apache.org/licenses/LICENSE-2.0
+*
+* Unless required by applicable law or agreed to in writing,
+* software distributed under the License is distributed on an
+* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+* KIND, either express or implied.  See the License for the
+* specific language governing permissions and limitations
+* under the License.
+*
+* @@@ END COPYRIGHT @@@
+  */
+////
+
+[[file-system-errors]]
+= File-System Errors
+
+Some error messages generated by the Neoview platform include file-system error
+codes. For example:
+
+====
+*SQL 1024*
+
+```
+File system error <error-number> occurred on <text-string-1>. <text-string-2>.
+```
+====
+
+This section lists all file-system error codes and provides the corresponding error text
+for each code number. The error text can sometimes help you troubleshoot a problem.
+If the initial error message and file-system error text are insufficient to help you solve a
+problem, or if you need more information, 
+contact the mailto:user@trafodion.incubator.apache.org[Trafodion User mailing list].
+
+
+[cols="15%l,85%",options="header",]
+|===
+| Error | Text
+| 0000  | The operation completed successfully.
+| 0001  | A read procedure reached end-of-file or a write procedure reached end of tape.
+| 0002  | The operation specified is not allowed on this type of file.
+| 0003  | An open or purge of a partition failed.
+| 0004  | An open operation for an alternate key file failed.
+| 0005  | Sequential buffering not used because no space was available in the process-control buffer for the sequential block buffer.
+| 0006  | A system message was received from another process. 
+| 0007  | This process cannot accept a command because the receiving file is not opened correctly.
+| 0008  | The operation was successful (examine message control word for additional status).
+| 0009  | A read through a locked record was successful. 
+| 0010  | The new record or file could not be created because a file by that name or a record with that key already exists.
+| 0011  | The file is not in the directory or the record is not in the file, or the specified tape file is not on a labeled tape.
+| 0012  | The file is in use.
+| 0013  | The filename was not specified in proper form.
+| 0014  | That device does not exist on this segment.
+| 0015  | The disk or segment specified for a file RENAME operation does not match the name of the disk or segment of the file.
+| 0016  | No file with that file number has been opened.
+| 0017  | A paired-open was specified and the file is not open by the primary process, the parameters supplied do not match the parameters supplied when the file was opened by the primary, or the primary process is not alive.
+| 0018  | The segment specified does not exist in the network.
+| 0019  | There is no more space for devices in the logical device table.
+| 0020  | File name is too long to be opened across a network, or swap file or segment name is not acceptable.
+| 0021  | An illegal <count> was specified in a file-system call, or the operation attempted to transfer too much or too little data.
+| 0022  | The application parameter or buffer address is out of bounds.
+| 0023  | The disk address is out of bounds, or the maximum number of blocks in an alternate-key file is exceeded.
+| 0024  | Privileged mode is required for this operation.
+| 0025  | AWAITIO[X] or CANCEL attempted on file opened for waited I/O. 
+| 0026  | AWAITIO[X] or CANCEL or CONTROL 22 attempted on a file with no outstanding I/O requests.
+| 0027  | An operation was attempted with outstanding no-waited I/O requests pending.
+| 0028  | The number of outstanding non-blocking operations would exceed that specified; an attempt was made to open a disk file or receiving file with the maximum number of concurrent operations more than 1; an attempt to ADD more than the configured maximum number of sub devices for an I/O process; or sync depth exceeds number the opener can handle; or trying to run more than 254 processes from the same program file.
+| 0029  | A required parameter is missing in a procedure call, or two mutually exclusive parameters were supplied.
+| 0030  | Message system is unable to obtain memory because either no entry is available in the message block pool or the maximum number of RECEIVE or SEND message blocks are already in use.
+| 0031  | Unable to obtain file-system buffer space. 
+| 0032  | Unable to obtain storage pool space.
+| 0033  | I/O process is unable to obtain sufficient buffer space. 
+| 0034  | Unable to obtain a file-system control block.
+| 0035  | Unable to obtain an I/O process control block, or the transaction or open lock unit limit has been reached.
+| 0036  | Unable to lock physical memory; not enough memory available.
+| 0038  | Attempt to perform operation on wrong type of system.
+| 0039  | The server process received a request with a sync ID older than the set of saved replies.
+| 0040  | The operation timed out. A command did not complete within the time specified by its <time-limit> parameter.
+| 0041  | A checksum error occurred on a file synchronization block. 
+| 0042  | Attempt to read from unallocated extent.
+| 0043  | Unable to obtain disk space for file extent.
+| 0044  | The disk directory or device control table is full.
+| 0045  | The file is full; or two entries for <process-name> were already in the process pair directory.
+| 0046  | An invalid key was specified; key length passed to CREATE exceeds 255 bytes; or application failed to open an alternate-key file.
+| 0047  | The alternate key data is not consistent with primary file data.
+| 0048  | Security violation; illegal operation attempted. 
+| 0049  | Access violation; attempt to use an unexpired labeled tape for output; or a mismatch between a DEFINE Use attribute (input or output/extend) and the current operation (read or write).
+| 0050  | Directory error on a disk.
+| 0051  | Directory on a disk is marked bad.
+| 0052  | Error in the disk free space table.
+| 0053  | File system internal error. 
+| 0054  | I/O error in disk free space table or in Data Access Manager undo area.
+| 0055  | I/O error in disk directory; the file is no longer accessible. 
+| 0056  | I/O error on disk label; the disk is no longer accessible. 
+| 0057  | The disk free space table is full.
+| 0058  | The disk free space table is marked bad.
+| 0059  | The disk file is bad; there is a mismatch in the internal file control block, or the file structure in a structured file is inconsistent.
+| 0060  | The file resides on a removed disk, the device is stopped or not open, or a server has failed and a process has been replaced by a different process with the same name since the server was opened.
+| 0061  | No more file opens are permitted on this disk or device; the system administrator issued a STOPOPENS command or the number of open files reached the maximum allowed. 
+| 0062  | The disk was mounted but no mount order was given, so the file open is not permitted.
+| 0063  | The disk was mounted and the mount is in progress, so a file open is not permitted.
+| 0064  | The disk was mounted and the mount is in progress, so a file open is not permitted.
+| 0065  | Only special requests permitted - or special request to RAID-1 disk pair attempted with only one device in special state.
+| 0066  | The device is stopped, a hard failure occurred on the controller, the disk and controller are not compatible, or both halves of a RAID-1 disk are down.
+| 0070  | Continue the file operation.
+| 0071  | A duplicate record was encountered.
+| 0072  | An attempt was made to access an unmounted or nonexistent partition, or to access a secondary partition.
+| 0073  | The disk file or record is locked.
+| 0074  | The number of read updates without replies exceeds the receive depth.
+| 0075  | Requesting process has no current process transaction identifier.
+| 0076  | Transaction is in the process of ending.
+| 0078  | Transaction identifier is invalid or obsolete.
+| 0079  | A transaction attempted to update or delete a record which it has not previously locked.
+| 0080  | Invalid operation on protected file or non-protected disk.
+| 0081  | Operation is not valid for a transaction which still has non-blocking I/Os outstanding on a disk or process file.
+| 0082  | Transaction Services not running on this segment or on the remote segment.
+| 0083  | Attempt to begin more concurrent transactions than can be handled.
+| 0084  | Transaction Services has not been configured on this segment or on the remote segment.
+| 0085  | A device has not been started for Transaction Services. 
+| 0086  | BEGINTRANSACTION is disabled either by the operator or because one or more Transaction Services limits have been reached.
+| 0087  | Waiting on a READ request and did not get it.
+| 0088  | A CONTROL READ is pending so a second READ is not valid. 
+| 0089  | A remote device cannot accept text because it has no buffer available.
+| 0090  | The transaction was aborted by the system because its parent process died, a server using the transaction failed, or a message to a server using the transaction was cancelled.
+| 0091  | A Transaction Services crash occurred during commitment of the transaction; the transaction may or may not have been committed.
+| 0092  | Distributed transaction aborted by system because the path to a remote segment that was part of the transaction was down.
+| 0093  | A transaction was aborted because it spanned too many transaction log files.
+| 0094  | A transaction was aborted by operator command.
+| 0095  | A transaction was aborted because of Data Access Manager process takeover by backup.
+| 0096  | The transaction was aborted because it exceeded the AUTOABORT timeout duration.
+| 0097  | Transaction aborted by call to ABORTTRANSACTION.
+| 0098  | Allocation of a Transaction Control Block failed because the local table is full, or the table on a remote segment is full.
+| 0099  | Process attempted to use features of a microcode option that is not installed on this segment.
+| 0100  | Device is not ready or the controller is not operational. 
+| 0101  | The tape is write protected.
+| 0102  | Printer paper out, bail open or end of ribbon.
+| 0103  | Disk not ready due to power failure.
+| 0104  | No response from printer.
+| 0105  | Invalid printer vertical format unit buffer.
+| 0106  | A buffered WRITE has failed; data in printer buffer was lost. |0110| Only BREAK access is permitted.
+| 0111  | Operation aborted because of BREAK.
+| 0112  | READ or WRITEREAD preempted by operator message or too many user console messages.
+| 0113  | DEFINE class or attributes are not valid for the attempted function.
+| 0119  | Error code value was too large to fit into an 8-bit buffer; file-system error number is greater than 255.
+| 0120  | Data parity error, or attempt to access a tape whose density is higher than the switch setting on the tape drive.
+| 0121  | Data overrun error, hardware problem.
+| 0122  | Request aborted due to possible data loss caused by reset of circuit, bus sequence error; or Data Access Manager process takeover.
+| 0123  | Subdevice is busy. 
+| 0124  | A line reset is in progress, loss of data is possible. 
+| 0130  | Illegal disk address requested, or formatting error occurred.
+| 0131  | Write-check error from disk; internal circuitry fault. 
+| 0132  | Seek incomplete from disk; cylinder address not reached after retry.
+| 0133  | Access not ready on disk; cylinder address not reached. 
+| 0134  | Address compare error on disk.
+| 0135  | Write-protect violation with disk write. 
+| 0136  | Disk unit ownership error (dual-port disk).
+| 0137  | Controller buffer parity error.
+| 0138  | Interrupt overrun; a device interrupted the processor before the software could respond.
+| 0139  | Controller error; internal diagnostic failure.
+| 0140  | Modem error (communication link not yet established, modem failure, momentary loss of carrier, or disconnect).
+| 0148  | Attempt to read unwritten data.
+| 0150  | End-of-tape marker detected.
+| 0151  | Runaway tape detected, or attempt to access a tape whose density is lower than the switch setting on the tape drive.
+| 0152  | Unusual end-tape unit went offline.
+| 0153  | Tape drive power restored.
+| 0154  | BOT detected during backspace files or backspace records. 
+| 0155  | Only nine-track magnetic tape allowed on this system. 
+| 0156  | Tape command rejected.
+| 0157  | I/O process internal system error. 
+| 0160  | Request is invalid for device state; protocol error.
+| 0161  | Impossible event occurred for line state.
+| 0162  | Operation timed out.
+| 0163  | EOT received or power at autocall unit is off.
+| 0164  | Disconnect received or data line is occupied (busy).
+| 0165  | RVI received or data line not occupied after setting call request.
+| 0166  | ENQ received or auto call unit failed to set present-next-digit.
+| 0167  | EOT received on line bid, or data-set-status not set
+| 0168  | NAK received on line bid, or auto-call unit failed to clear present-nextdigit after digit-present was set.
+| 0169  | WACK received on line bid, auto-call unit set abandon-call-and-retry, or station disabled or undefined.
+| 0170  | No ID sequence received during circuit assurance mode or invalid message control word entry number on write.
+| 0171  | No response received on bid/poll/select, or reply invalid.
+| 0172  | Reply not proper for protocol; invalid control sequence or invalid data.
+| 0173  | Maximum allowable NAKs received (transmission error), invalid message control word on WRITE, or invalid request ID.
+| 0174  | WACK received or bus frame aborted.
+| 0175  | Incorrect alternating ACK received, or command rejected.
+| 0176  | Poll sequence ended with no responder.
+| 0177  | Text overrun (insufficient buffer space for data transfer).
+| 0178  | No address list specified.
+| 0179  | Application buffer is incorrect, control request pending, or autopoll active.
+| 0180  | Unknown device status received.
+| 0181  | Sub device expected status information but received data instead.
+| 0187  | Operation returning with no useful data.
+| 0188  | Damage to logical flow of events.
+| 0189  | Response not yet available. 
+| 0190  | Device error; hardware problem.
+| 0191  | Device power on, or terminal reset.
+| 0192  | Device in diagnose mode; system operator running diagnostics. 
+| 0193  | Invalid or missing microcode file.
+| 0194  | Device use or mount request rejected by operator.
+| 0195  | Operation requires use of Tape Services but it is not running; tape operation is not allowed.
+| 0196  | A tape label record is missing or incorrect. 
+| 0197  | An SQL error has occurred.
+| 0198  | A DEFINE of the given name could not be found.
+| 0199  | The disk file is protected by security software. 
+| 0200  | The device is owned by an alternate port.
+| 0201  | The current path to the device is down, an attempt was made to write to a non-existent process, the message-system request was incorrectly formatted, or an error was found in the message system interface.
+| 0210  | Device ownership changed during operation.
+| 0211  | The node performing the operation failed during the operation.
+| 0213  | Channel data parity error (path error).
+| 0214  | Channel timeout (path error).
+| 0215  | I/O attempted to absent memory page (hardware path error).
+| 0216  | Memory breakpoint encountered during this I/O operation. 
+| 0217  | Memory parity error during this I/O (hardware path error).
+| 0218  | Interrupt timeout occurred on a channel, or a controller, modem, or the line between, or lost the modem clock (path error).
+| 0219  | Illegal device reconnect (path error).
+| 0220  | Protect violation; an I/O controller attempted an illegal write. 
+| 0221  | Controller handshake violation (path error).
+| 0222  | Bad channel status from EIO instruction (path error).
+| 0223  | Bad channel status from IIO instruction (path error). 
+| 0224  | Controller error (fatal error).
+| 0225  | No unit assigned or multiple units assigned to the same unit number (path error).
+| 0230  | Node power failed, then restored.
+| 0231  | Controller power failed, then restored.
+| 0232  | Access is denied due to error in communication with the security monitor.
+| 0233  | Error in call to SERVERCLASS_SEND_.
+| 0240  | Network line handler error; operation not started. Ownership switch was performed.
+| 0241  | Network error; operation not started.
+| 0246  | External cluster bypass error; operation aborted.
+| 0248  | Network line handler error; operation aborted.
+| 0249  | Network error; operation aborted.
+| 0250  | All paths to the system are down. 
+| 0251  | Network protocol error (path error).
+| 0252  | Required class is not available. 
+| 0255  | Net line handler flooded; too many interrupts.
+| 0512  | An invalid parameter was specified.
+| 0513  | A file name was missing. 
+| 0514  | The sequential I/O procedures do not support the specified device type.
+| 0515  | The specified access is invalid. 
+| 0516  | The specified buffer address is invalid.
+| 0517  | The specified file code in the SET^FILE call does not match the file code of the file.
+| 0518  | The block buffer provided to OPEN^FILE is too small.
+| 0519  | The block length specified in the SET^FILE call does not match the block buffer length in OPEN^FILE.
+| 0520  | The specified record length was either too small or too large.
+| 0521  | The specified file is not a valid EDIT file.
+| 0522  | Either the SET^FILE or CHECK^FILE operation is not valid on an open file or OPEN^FILE was called for a file already open.
+| 0523  | An EDITREAD or EDITREADINIT error occurred.
+| 0524  | The specified file was not open.
+| 0525  | The requested operation was inconsistent with the access mode.
+| 0526  | The required operation failed because of insufficient stack space.
+| 0527  | The temporary buffer required for a non-blocking WRITE^FILE operation was not provided.
+| 0530  | The program called WRITE^FILE for the receiving file before calling READ^FILE.
+| 0531  | A call to CHECK^BREAK could not open the receiving file the receiving file was opened without calling OPEN^FILE.
+| 0532  | A non-blocking I/O operation has been restarted.
+| 0533  | An internal sequential I/O error occured.
+| 0534  | A discrepancy was detected between the common file-control-block checksum and the previous checksum.
+| 0535  | A discrepancy was detected between the file file-control-block checksum and the previous checksum.
+| 0541  | A data structure version is incompatible with the requested operation.
+| 0550  | File operation attempted at illegal position.
+| 0551  | Duplicate exists for insertion-ordered alternate key.
+| 0561  | The item code in a list is not recognized.
+| 0563  | The size of an output buffer was too small.
+| 0564  | The operation is not supported for this file type.
+| 0565  | A malformed request was denied.
+| 0566  | This reply is malformed or not appropriate.
+| 0567  | The define used is incompatible for use with target system's TOS version.
+| 0570  | An out-of-sequence message was received.
+| 0571  | A duplicate message was received.
+| 0572  | Message cannot be accepted because sequence number has been reset.
+| 0573  | The requested process handle cannot be returned.
+| 0578  | The block size specified is too large. 
+| 0579  | The record size specified is too large for the given block size, file type and format.
+| 0580  | An open failed because the file was oversize and the opener did not specify use of 64-bit primary keys.
+| 0581  | An operation involving 32-bit primary keys was attempted on an open which specified use of 64-bit keys.
+| 0582  | Alternate key information could not be returned because it cannot be expressed in the superseded format of the parameter.
+| 0583  | An extent size specified is too large. 
+| 0584  | The operation could not be performed because a software component does not support format-2 disk files.
+| 0586  | Transaction_Keep_ was attempted without a valid transaction dialog message.
+| 0587  | Transaction_Keep_ was called when there was already a kept transaction.
+| 0588  | There was no kept transaction but the operation required one.
+| 0589  | The operation could not be performed because there was a kept transaction.
+| 0590  | The parameter value is invalid or inconsistent with another.
+| 0593  | The request was cancelled.
+| 0594  | A tape-catalog error was returned to Tape Services. Refer to the event log for detailed information.
+| 0595  | An error was returned to Tape Services. Refer to the event log for detailed information.
+| 0597  | A required item is missing from an item list. 
+| 0632  | Not enough stack space to complete request. 
+| 0633  | Operation is invalid because a performance measurement utility is running.
+| 0634  | A logical device number exceeded 16 bits. 
+| 0635  | A disk cannot be accessed because the other side is locked. 
+| 0638  | Process cannot be stopped until process returns to stopmode 1.
+| 0639  | Process cannot be stopped until process goes to stopmode 0. 
+| 0700  | The sequence number of the message received by the Data Access Manager process from a recovery process does not match.
+| 0701  | The Data Access Manager process received a message from a recovery process that requires that the Data Access Manager process be in the STARTED state; it is currently in the STOPPED state.
+| 0702  | The Data Access Manager process received an erroneous message from a recovery process. The message requested a physical REDO and also requested that a transaction log be generated.
+| 0703  | The Data Access Manager process encountered a Creation Volume Sequence Number in a transaction-log record sent by a recovery process that is more recent than the CRVSN of the File Label.
+| 0704  | The Data Access Manager process encountered a Previous Volume Sequence Number in a transaction-log record sent by a recovery process that does not match the Volume Sequence Number of the data block on disk.
+| 0705  | Generated by the Data Access Manager process when it receives a Transaction Services Transaction Log Disk request type message and the Data Access Manager process is not an transaction-log disk.
+| 0706  | Generated by the Data Access Manager process when it receives a request message that is inappropriate for a Transaction Log Data Access Manager Process.
+| 0707  | Generated by the Data Access Manager process when the Disk Process Name Stamp (DPNameTimeStamp) in the message sent by a recovery process does not match the current DPNameTimeStamp of the disk.
+| 0708  | The Data Access Manager process encountered a File Label that had its UndoNeeded flag set when a recovery request specified that the UndoNeeded flag must not be set.
+| 0709  | The Data Access Manager process encountered a File Label that had its RedoNeeded flag set when a recovery request specified that the RedoNeeded flag must not be set.
+| 0711  | The Data Access Manager process received a corrupt transaction-log record in a message from a recovery process.
+| 0751  | A tape manager returned an error to Tape Services. Refer to the event log for detailed information.
+| 0899  | An attempt to switch nodes failed. 
+| 1024  | The specified SQL subset is not defined to the file system.
+| 1025  | The supplied row or update value violates one of the constraints for the table.
+| 1026  | The selection expression on an SQL view has been violated.
+| 1027  | The Data Access Manager process encountered a bad SQL label or tree of labels.
+| 1028  | The Data Access Manager process accessed a label of an unexpected type during an OPEN or during an SQL label operation.
+| 1029  | A request to share an existing SQL open failed because no matching open was found.
+| 1030  | An invalid lock key length was specified for an SQL table.
+| 1031  | Some of the supplied values for DECIMAL or VARCHAR columns are invalid, or the supplied row is too long. Also, the disk process might have encountered a bad column in a stored row or a value in an update on a row that would change the length of a VARCHAR column in an entry-sequenced table.
+| 1032  | The SQL row description is inconsistent.
+| 1033  | The SQL key column description is inconsistent, or the specified key is too long.
+| 1034  | SQL internal error: The requested operation has failed because of an inconsistency in specifying the SQL catalog.
+| 1035  | SQL internal error.
+| 1036  | SQL internal error.
+| 1037  | SQL internal error.
+| 1038  | SQL internal error.
+| 1039  | An SQL UPDATE statement was attempted, but update intent was not specified when the cursor was declared.
+| 1040  | There is no current row. The cursor position is either before the first row of the set, after the last row, or between two rows.
+| 1041  | SQL internal error.
+| 1042  | The operation required a default value for a column that was defined as NO DEFAULT.
+| 1043  | SQL internal error.
+| 1044  | The operation is not allowed while an SQL cursor is open.
+| 1045  | SQL internal error.
+| 1046  | SQL internal error.
+| 1047  | The SQL index being used is marked invalid because the catalog manager has not successfully loaded it.
+| 1048  | SQL internal error.
+| 1049  | SQL internal error.
+| 1050  | SQL internal error.
+| 1051  | SQL internal error.
+| 1052  | A row was encountered that resides in a block having a data parity error. The row does not satisfy the WHERE clause.
+| 1053  | An ECC error or a checksum error occurred indicating that it is impossible to process the accessed block. No data is returned.
+| 1054  | Unable to access a non-protected table or protection view that has been altered by an uncommitted DDL statement.
+| 1055  | Unable to perform a utility operation while an uncommitted DDL operation from another transaction exists.
+| 1056  | Unable to access a table that is being recovered by Transaction Services.
+| 1057  | Unable to access a table that is being altered by another user.
+| 1058  | Unable to access a table that is being dropped by another user.
+| 1059  | Unable to access a protection view whose underlying table does not exist or is inconsistent.
+| 1060  | SQL internal error.
+| 1061  | The cursor is no longer defined in the Data Access Manager process.
+| 1062  | SQL internal error.
+| 1063  | SQL internal error.
+| 1064  | The table cannot be dropped because protection views are still defined for the table.
+| 1065  | This error message has two possible causes: 1) Either an SQL internal error has occurred. 2) An attempt was made to execute either an UPDATE WHERE CURRENT OF or DELETE WHERE CURRENT OF statement by using a cursor declared with the BROWSE ACCESS option.
+| 1066  | Internal error: Occurred in OPEN.
+| 1067  | Internal error: Occurred in the file system or Data Access Manager process OPEN protocol.
+| 1068  | SQL internal error.
+| 1069  | SQL internal error.
+| 1070  | The process's program file is not licensed.
+| 1071  | SQL internal error.
+| 1072  | SQL internal error.
+| 1073  | SQL internal error.
+| 1074  | Internal error: SQL file system procedure.
+| 1075  | A FETCH was attempted following a FETCH that failed. This left the cursor in an undefined position.
+| 1076  | SQL internal error.
+| 1077  | The redefinition timestamp for a partition does not match the other partitions. This is a serious consistency failure.
+| 1078  | The disk process encountered an invalid row.
+| 1079  | The requested key compression option is inconsistent with the data type, offset in row, or descending flag of some of the key columns.
+| 1080  | The transaction ID does not match the current transaction ID for a protected table with a lock protocol or for a non-protected temporary table.
+| 1081  | SQL internal error.
+| 1082  | SQL internal error.
+| 1083  | An internal input SQL structure has an invalid format, as indicated by an incorrect EYE^CATCHER data item value. The program might have corrupted the SQL region or SQL executor segment, or an SQL internal error might have occurred.
+| 1084  | Unable to insert into an SQL view that does not allow insertions.
+| 1085  | SQL internal error or access incompatible SQL objects that were created on an SQL system with a later release date than the SQL system doing the accessing.
+| 1086  | Unable to unlock an SQL table that has locks through either STABLE ACCESS or REPEATABLE ACCESS.
+| 1087  | The SQL file system detected an internal disk process error.
+| 1088  | SQL internal error.
+| 1089  | SQL internal error.
+| 1090  | The requested SQL operation cannot be completed because of current limitations on message sizes.
+| 1091  | The file or table cannot be purged until the NOPURGEUNTIL date.
+| 1092  | The operation cannot be performed because the resulting disk directory entry would be too long. Too many columns, partitions, indexes, protection views, or constraints have been defined.
+| 1093  | The operation cannot be performed because the resulting row would exceed the RECLENGTH value defined for the relative table.
+| 1094  | The limit on the number of columns that can make up a key has been exceeded for indexes or key-sequenced tables.
+| 1095  | An invalid value has been supplied for the BLOCKSIZE attribute.
+| 1096  | The BLOCKSIZE value for this table is too small for the row length of the table.
+| 1097  | Unable to access an object that is off-line or has an inconsistent definition.
+| 1098  | The supplied MAXEXTENTS value is too large, or the total size of the partitions would exceed the largest allowable table size.
+| 1099  | The definitions of the table and/or index partitions are inconsistent, or the index label and corresponding underlying table values are inconsistent.
+| 1100  | An operand was truncated during assignment of character data.
+| 1101  | Truncation was needed, but prohibited during assignment of character data.
+| 1102  | An overflow occurred during expression evaluation.
+| 1103  | An underflow occurred during expression evaluation.
+| 1104  | An SQL column of type DECIMAL contained values that are not digits.
+| 1105  | Unable to assign a negative value to a column defined as unsigned.
+| 1106  | An unsigned numeric has a negative value.
+| 1107  | Division by zero occurred during expression evaluation.
+| 1108  | Data type of column not supported by this release.
+| 1109  | An invalid SQL data type was encountered.
+| 1110  | An operation between incompatible SQL types was requested.
+| 1111  | SQL internal error.
+| 1112  | Arithmetic operation was requested in an unexpected unsigned data type.
+| 1113  | Invalid operator value during expression evaluation.
+| 1114  | Invalid LIKE pattern during expression evaluation.
+| 1115  | A specified SYSKEY value exceeds the current defined size of the relative SQL table.
+| 1116  | The SQL file system aborted the transaction because an SQL statement could not be completed.
+| 1117  | Unable to use an undefined index.
+| 1118  | The specified view is not defined.
+| 1119  | The specified partition is not defined.
+| 1120  | SQL internal error.
+| 1121  | This error message has two possible causes: 1) A remote user specified local-only authority in the SECURE attribute for the object being created or altered. 2) The SECURE attribute did not grant read authority to all users being granted write authority.
+| 1122  | The supplied KEYTAG value is already defined for this table.
+| 1123  | SQL internal error.
+| 1124  | SQL internal error.
+| 1125  | SQL internal error.
+| 1126  | SQL internal error.
+| 1127  | Unable to update an SQL catalog table from a process that is not licensed.
+| 1128  | An operand was scale truncated during expression evaluation.
+| 1129  | Scale truncation was needed but prohibited during expression evaluation.
+| 1130  | Unable to use SQL on a system where the product is not installed.
+| 3501  | More control information was received than this dialect allows.
+| 3502  | Server does not have sufficient available storage for this request.
+| 3503  | Server does not support this dialect.
+| 3504  | Server does not support this request type.
+| 3505  | Server version is not current.
+| 4001  | Operation not permitted. Process does not have the appropriate privileges or permissions to perform the requested operation.
+| 4002  | No such file or directory.
+| 4003  | No such process or table entry.
+| 4004  | Interrupted system call.
+| 4005  | I/O error.
+| 4006  | No such device or address.
+| 4007  | Argument list too long.
+| 4008  | Exec format error.
+| 4009  | Bad file descriptor.
+| 4010  | No children.
+| 4011  | No more processes.
+| 4012  | Insufficient user memory.
+| 4013  | Permission denied.
+| 4014  | Bad address.
+| 4016  | Mount device busy.
+| 4017  | File already exists.
+| 4018  | Cross-device link.
+| 4019  | No such device.
+| 4020  | Not a directory.
+| 4021  | Is a directory.
+| 4022  | Invalid function argument.
+| 4023  | File table overflow.
+| 4024  | Maximum number of files already open.
+| 4025  | Invalid operation on terminal device.
+| 4026  | Object (text) file busy.
+| 4027  | File too large.
+| 4028  | No space left on device.
+| 4029  | Illegal seek.
+| 4030  | Read only file system.
+| 4031  | Too many links.
+| 4032  | Broken pipe or no reader on socket.
+| 4033  | Argument out of range.
+| 4034  | Value out of range.
+| 4035  | No message of desired type.
+| 4036  | Identifier removed.
+| 4045  | Deadlock condition.
+| 4046  | No record locks available.
+| 4061  | No data sent or received.
+| 4099  | Function not implemented.
+| 4101  | Operation would block.
+| 4102  | Operation now in progress.
+| 4103  | Operation already in progress.
+| 4104  | Socket operation on nonsocket.
+| 4105  | Destination address required.
+| 4106  | Message too long.
+| 4107  | Protocol wrong type for socket.
+| 4108  | Protocol not available.
+| 4109  | Protocol not supported.
+| 4110  | Socket type not supported.
+| 4111  | Operation not supported on socket.
+| 4112  | Protocol family not supported. 
+| 4113  | Address family not supported.
+| 4114  | Address already in use.
+| 4115  | Can't assign requested address.
+| 4116  | Network is down.
+| 4117  | Network is unreachable.
+| 4118  | Network dropped connection on reset.
+| 4119  | Software caused connection abort.
+| 4120  | Connection reset by remote host.
+| 4121  | No buffer space available.
+| 4122  | Socket is already connected.
+| 4123  | Socket is not connected.
+| 4124  | Can't send after socket shutdown.
+| 4126  | Connection timed out.
+| 4127  | Connection refused.
+| 4128  | Host is down.
+| 4129  | No route to host.
+| 4131  | File name too long.
+| 4132  | Directory not empty.
+| 4180  | Invalid data in buffer.
+| 4181  | No reply in buffer.
+| 4182  | Partial buffer received.
+| 4183  | Interface error from SPI.
+| 4184  | Version mismatch.
+| 4185  | XDR encoding error.
+| 4186  | XDR decoding error.
+| 4195  | Out-of-band data available.
+| 4196  | Invalid socket call.
+| 4197  | File type not supported.
+| 4198  | C file (code 180) not odd unstructured.
+| 4199  | Insufficient internal memory.
+| 4200  | Too many symbolic links during path name resolution.
+| 4201  | File-set catalog internal consistency error.
+| 4202  | Root file set is not mounted.
+| 4203  | POSIX not running or not installed.
+| 4204  | Illegal byte sequence.
+| 4205  | Process is not common runtime-environment (CRE) compliant but requests a service that depends on CRE.
+| 4206  | Illegal service requested.
+| 4207  | An unexpected OSS subsystem error occurred.
+| 4208  | Illegal operation attempted on file descriptor.
+| 4209  | Logic error.
+| 4211  | Current working directory or filename longer than PATH_MAX.
+| 4212  | An error occurred during invocation of a DEFINE procedure.
+| 4213  | A cross node exec has been attempted while holding a semaphore.
+| 4214  | An invalid message tag had been encountered when setlocale_from_msg() function was called. There was no corresponding message for the message tag.
+| 4215  | Positioning of a file directory failed because there were more than 65535 names in the directory beginning with the same first two characters.
+| 4216  | The function is supported but not for the referenced object type.
+| 4217  | Socket transport server not running.
+| 4218  | Message queue server not running.
+| 4219  | Terminal Helper process not running.
+| 4220  | An operation was attempted on a large file using a small file I/O API.
+| ===

http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/e77d8018/docs/messages_guide/src/asciidoc/_chapters/generator_msgs.adoc
----------------------------------------------------------------------
diff --git a/docs/messages_guide/src/asciidoc/_chapters/generator_msgs.adoc b/docs/messages_guide/src/asciidoc/_chapters/generator_msgs.adoc
new file mode 100644
index 0000000..aabf27a
--- /dev/null
+++ b/docs/messages_guide/src/asciidoc/_chapters/generator_msgs.adoc
@@ -0,0 +1,59 @@
+////
+/**
+* @@@ START COPYRIGHT @@@
+*
+* Licensed to the Apache Software Foundation (ASF) under one
+* or more contributor license agreements.  See the NOTICE file
+* distributed with this work for additional information
+* regarding copyright ownership.  The ASF licenses this file
+* to you under the Apache License, Version 2.0 (the
+* "License"); you may not use this file except in compliance
+* with the License.  You may obtain a copy of the License at
+*
+*   http://www.apache.org/licenses/LICENSE-2.0
+*
+* Unless required by applicable law or agreed to in writing,
+* software distributed under the License is distributed on an
+* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+* KIND, either express or implied.  See the License for the
+* specific language governing permissions and limitations
+* under the License.
+*
+* @@@ END COPYRIGHT @@@
+  */
+////
+
+[[generator-messages]]
+= Generator Messages (7000 through 7999)
+
+[[SQL-7001]]
+== SQL 7001
+
+```
+Default value <value> is not valid for column <name>.
+```
+
+*Cause:* You attempted to create a table with an invalid default <value>
+for column <name>.
+
+*Effect:* The operation fails.
+
+*Recovery:* Correct the syntax and resubmit.
+
+[[SQL-7003]]
+== SQL 7003
+
+```
+A plan using cluster sampling could not be produced for this query.
+```
+
+*Cause:* You can use cluster sampling in a query only on a base table
+result set and only if there is no WHERE clause in the SELECT statement.
+This query does not satisfy these conditions.
+
+*Effect:* Trafodion is unable to compile the query.
+
+*Recovery:* Rewrite the query (for example, using nested queries) so
+that cluster sampling is performed on a base table with no WHERE-clause
+predicate.
+

http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/e77d8018/docs/messages_guide/src/asciidoc/_chapters/introduction.adoc
----------------------------------------------------------------------
diff --git a/docs/messages_guide/src/asciidoc/_chapters/introduction.adoc b/docs/messages_guide/src/asciidoc/_chapters/introduction.adoc
new file mode 100644
index 0000000..6d3405e
--- /dev/null
+++ b/docs/messages_guide/src/asciidoc/_chapters/introduction.adoc
@@ -0,0 +1,116 @@
+////
+/**
+* @@@ START COPYRIGHT @@@
+*
+* Licensed to the Apache Software Foundation (ASF) under one
+* or more contributor license agreements.  See the NOTICE file
+* distributed with this work for additional information
+* regarding copyright ownership.  The ASF licenses this file
+* to you under the Apache License, Version 2.0 (the
+* "License"); you may not use this file except in compliance
+* with the License.  You may obtain a copy of the License at
+*
+*   http://www.apache.org/licenses/LICENSE-2.0
+*
+* Unless required by applicable law or agreed to in writing,
+* software distributed under the License is distributed on an
+* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+* KIND, either express or implied.  See the License for the
+* specific language governing permissions and limitations
+* under the License.
+*
+* @@@ END COPYRIGHT @@@
+  */
+////
+
+= Introduction
+
+== Message Handling
+
+Trafodion reports exception condition messages at a Trafodion Database
+Connectivity Service conversational interface (DCS) window and in the
+Trafodion Command Interface (TrafCI).
+
+Most Trafodion  exception condition messages describe error conditions
+for which recovery action is required. Some messages are warnings that
+provide information for which no action is required.
+
+Error messages that appear in response to SQL commands are logged to the
+DCS application's log file if you have used the LOG command to request
+them.
+
+The format of a Trafodion  error is "*** ERROR" followed by the error number
+in brackets, and the descriptive text. Use the error number shown to find
+information about a particular error in this manual. For example, information
+for Trafodion error 1125 can be found under "SQL 1125."
+
+Messages are listed in this manual in numeric order, broken down by the component
+that produced them.
+
+[[viewing-trafodion-database-messages]]
+== Viewing Trafodion Database Messages
+
+The message key is a sequential SQL message number that is returned
+automatically by Trafodion  when an exception condition
+occurs. For example, the following message might be displayed within
+your application development tool while you prepare an embedded SQL
+program:
+
+```
+*** ERROR[1000] A syntax error occurred.
+```
+
+<<<
+This message number is the SQLCODE value (without the sign). In this
+manual, you will find the following message information for ERROR[1000]:
+
+====
+*SQL 1000*
+
+1000 A syntax error occurred.
+
+*Cause:* You specified a statement with incorrect syntax.
+
+*Effect:* The Trafodion  statement fails.
+
+*Recovery:* Correct the syntax and resubmit.
+====
+
+[[sqlstate-and-sqlcode]]
+== SQLSTATE and SQLCODE
+
+SQLSTATE and SQLCODE status codes are returned to indicate either that
+an SQL statement completed successfully or that an exception condition
+was raised during execution of an SQL statement.
+
+The ANSI SQL SQLSTATE variable is a five-character string with a
+two-character class code followed by a three-character subclass code. An
+SQLSTATE value of 00000 indicates successful completion.
+
+Trafodion extends the ANSI SQL SQLSTATE values to include other situations
+not described by the ANSI values. If an ANSI SQL SQLSTATE value exists for
+an error condition, the Trafodion database software returns that value.
+Otherwise, Trafodion returns an SQLSTATE value that is defined by the Trafodion
+database software.
+
+Trafodion also returns a numeric SQLCODE value after SQL statement execution.
+SQLCODE values with negative numbers signify errors.
+
+SQLCODE values with positive numbers other than 0 (successful completion) or 100
+(no data was found) signify warning messages. Trafodion  identifies all messages
+by their unsigned SQLCODE value and their calculated SQLSTATE value. The SQLCODE
+is used to calculate the SQLSTATE value for all Trafodion messages other than
+those for which an ANSI SQL SQLSTATE value exists.
+
+The SQLCODE parameter is a deprecated feature that is supported to
+maintain compatibility with earlier versions of the American standard.
+
+<<sqlstate-values,_SQLSTATE Values_>> identifies the equivalent SQLSTATE and
+SQLCODE values for Trafodion  warning and error messages.
+
+[[getting-help]]
+== Getting Help
+
+Some messages have no recovery and you will be instructed to contact the
+mailt:user@trafodion.incubator.apache.org[Trafodion user mailing list].
+

http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/e77d8018/docs/messages_guide/src/asciidoc/_chapters/optimizer_msgs.adoc
----------------------------------------------------------------------
diff --git a/docs/messages_guide/src/asciidoc/_chapters/optimizer_msgs.adoc b/docs/messages_guide/src/asciidoc/_chapters/optimizer_msgs.adoc
new file mode 100644
index 0000000..899eec4
--- /dev/null
+++ b/docs/messages_guide/src/asciidoc/_chapters/optimizer_msgs.adoc
@@ -0,0 +1,118 @@
+////
+/**
+* @@@ START COPYRIGHT @@@
+*
+* Licensed to the Apache Software Foundation (ASF) under one
+* or more contributor license agreements.  See the NOTICE file
+* distributed with this work for additional information
+* regarding copyright ownership.  The ASF licenses this file
+* to you under the Apache License, Version 2.0 (the
+* "License"); you may not use this file except in compliance
+* with the License.  You may obtain a copy of the License at
+*
+*   http://www.apache.org/licenses/LICENSE-2.0
+*
+* Unless required by applicable law or agreed to in writing,
+* software distributed under the License is distributed on an
+* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+* KIND, either express or implied.  See the License for the
+* specific language governing permissions and limitations
+* under the License.
+*
+* @@@ END COPYRIGHT @@@
+  */
+////
+
+[[optimizer-messages]]
+= Optimizer Messages (6000 through 6999)
+
+[[SQL-6001]]
+== SQL 6001
+
+```
+DISTINCT aggregates can be computed for only one column per table expression.
+```
+
+*Cause:* You attempted to compute DISTINCT aggregates for more than one
+column.
+
+*Effect:* DISTINCT aggregates can be computed only for one column per
+table expression.
+
+*Recovery:* Correct syntax and resubmit.
+
+[[SQL-6002]]
+== SQL 6002
+
+```
+The metadata table HISTOGRAMS or HISTOGRAM_INTERVALS contains invalid values. If you have manually modified the metadata table, then you should undo your changes using the CLEAR option in UPDATE STATISTICS.
+```
+
+*Cause:* You have manually modified the metadata table, and now it
+contains invalid values.
+
+*Effect:* Trafodion is unable to complete
+compilation.
+
+*Recovery:* Undo your changes using the CLEAR option in UPDATE
+STATISTICS.
+
+<<<
+[[SQL-6003]]
+== SQL 6003
+
+```
+The metadata table HISTOGRAMS or HISTOGRAM_INTERVALS contains invalid boundary value <value> for column <name>. If you have manually modified the metadata table, then you should undo your changes using the CLEAR option in UPDATE STATISTICS.
+```
+
+*Cause:* You have manually modified the metadata table, and now it
+contains an invalid boundary value.
+
+*Effect:* The Trafodion database uses default histograms to compile the
+query. This is a warning message.
+
+*Recovery:* Undo your changes using the CLEAR option in UPDATE
+STATISTICS.
+
+[[SQL-6007]]
+== SQL 6007
+
+```
+Multi-column statistics for columns <names> from table <name> were not available; as a result, the access path chosen might not be the best possible.
+```
+
+*Cause:* Statistics are not available for the multicolumn join you are
+performing.
+
+This message appears when the user has not updated statistics for column
+<names> and when the rowcount in table <name> is more than the value of
+the defaults table constant HIST_ROWCOUNT_REQUIRING_STATS. If you want
+to suppress this message, set that value to a very large number, and you
+will see this message only for tables with more rows than that, and for
+which there are no updated statistics.
+
+*Effect:* None. This is a warning message.
+
+*Recovery:* None.
+
+<<<
+[[SQL-6008]]
+== SQL 6008
+
+```
+Statistics for column <name> were not available. As a result, the access path chosen might not be the best possible.
+```
+
+*Cause:* Statistics are not available for the statement you specified.
+
+This message appears when the user has not updated statistics for column
+<name> and when the rowcount in the table is more than the value of the
+defaults table constant HIST_ROWCOUNT_REQUIRING_STATS. If you want to
+suppress this message, set that value to a very large number, and you
+will see this message only for tables with more rows than that, and for
+which there are no updated statistics.
+
+*Effect:* None. This is a warning message.
+
+*Recovery:* None.
+