Change command syntax

DB2® Change Management Expert verifies the syntax of your change commands before they are applied to the database. DB2 Change Management Expert indicates suspected problems by placing an indicator (red 'x') next to the problem.

DB2 Change Management Expert verifies the validity of your change commands automatically, whether you create change commands with the Data Project Explorer or you import them from a file.DB2 Change Management Expert supports the same change command syntax as DB2 for Linux®, UNIX, and Windows®.

Remember: Problems are also reported in the Problems view.

If you notice syntax errors in your document, it might be caused by an incorrect statement terminator. Right-click in the Change Command Editor and select Set Statement Terminator to change the statement terminator.

If you use input that is generated by other products, ensure that the input is valid. The most common problem is with statement terminators, which are used to separate multiple statements. Any UCS-2 character in the range 0x0000 to 0x0080 inclusive can be used as the statement terminator provided that the statement terminator does not appear any where else in the statement. For example, you cannot use a semicolon as a statement terminator for an SQL statement to create a trigger because semicolons are required within the definition of the trigger body. You can change the statement terminator throughout the input by placing a script options statement terminator directive before the statements.


Feedback

Copyright IBM Corporation 2006, 2007. All Rights Reserved.