Listing of SQL messages

Static analysis of the expression relies on a component of the static context, &1, that has not been assigned a value.

The XPath expression cannot be processed.

Evaluation of the expression starting with &1 requires that the focus component of the dynamic context be assigned. The token is being considered as the beginning of a path expression which does not have an associated context item or context sequence. This might be the result of not specifying an XPath context item expression in the passing clause. Other common causes for this error include:

• The value in token &1 was intended to be a literal string but delimiting quotation characters are missing.
• The value in token &1 was intended to be a function but the opening and closing parentheses are missing.

The XPath expression cannot be processed.

• For a constructor function of an XML schema atomic type, atomization of its argument must not result in more than one atomic value.
• The cast of a value of &1 to target &2 must be a supported cast.
• An XPath expression was used in an output column of the XMLTABLE built in table function that could not be cast to the expected type. This typically happens when the expression result contains more than one atomic value and a singleton is expected; or a cast from the result type to the expected data type is not supported.

The XPath expression cannot be processed.

The XPath expression cannot be processed.

- Verify that you are passing the correct number of parameters to the function call.

- If the function call uses a function name with no prefix, verify that the local name of the function matches a function that is defined in the default function namespace, or use the correct prefix.

- If the function call uses a prefix, verify that the local name of the function matches a function that is defined in the namespace indicated by the prefix.

• The types of the operands are not a valid combination for the given operator. For example, the operands of an arithmetic operator are not numeric types.
• One or both operands of an arithmetic operator are a sequence of more than one item, but the given operator requires single item operands. The notation (item(), item()+) represents the type of a sequence of more than one item.
• An XML document is being constructed from an attribute node. A sequence item that is used to construct an XML document must not be an attribute node. This error can occur when a sequence that contains an attribute is returned to SQL as an XML value.

The XPath expression cannot be processed.

• If the prefix name is "xml" or "xmlns", then change the prefix name to a different namespace prefix or remove the namespace declaration.
• If the namespace URI is 'http://www.w3.org/XML/1998/namespace' or 'http://www.w3.org/2000/xmlns/', then change the namespace URI specified in the declaration of the namespace prefix.

The effective boolean value can be computed only if the sequence operand is one of the following sequences:

• An empty sequence
• A sequence where the value of the first item is a node
• A singleton sequence with a value of type xs:string, xs:untypedAtomic or a type derived from one of these types.
• A singleton sequence with a value of any numeric type or derived from any numeric type.

The expression cannot be processed.

• The logical expressions AND and OR
• An fn:not function invocation
• Certain types of predicates, such as a[b]
• The WHERE clause of an FLWOR expression
• Conditional expressions, such as IF

Ensure that the sequence operand of each effective boolean value calculation has a valid sequence operand, as described in the explanation.

• If the error results from a function invocation, verify that the string parameters used for QNames or local names have the correct lexical form.
• If the error results from a cast expression, verify that the source value is not one of the special float or double values NaN, INF, or -INF.

• &1 was explicitly passed to a constructor function or specified in a cast expression with a target data type of &2.
• An expression that includes &1 implicitly cast the value to the target data type of &2. Many XPath expressions use implicit casting to process the expressions. For example, an implicit cast is used in general comparisons of numeric values that require the values to be of data type xs:double.
• &1 is not within the range of valid values for the target type &2.

The XPath expression cannot be processed.

• If the error occurs in an expression that casts from one primitive type to another, verify that casting from the source type to the target type is supported. If the cast is not supported, either remove the expression or cast the value to a different data type.
• Check for expressions that would result in implicit casting to values that may not conform to the data type of the implicit cast.

• If the function is fn:avg, verify that the following conditions are met: If the input sequence contains duration values, the values must be either all xs:yearMonthDuration values or all xs:dayTimeDuration values. If the input sequence contains numeric values, the values must all be promotable to a single common type that is one of the four numeric types, xs:yearMonthDuration or xs:dayTimeDuration or one of its subtypes.
• If the function is fn:max or fn:min, verify that the following conditions are met: All items in the input sequence must be numeric or derived from a single base type for which the gt operator (for fn:max) or lt operator (for fn:min) is defined. If the input sequence contains numeric values, the values must all be promotable to a single common type and the values in the sequence must have a total order. If the input sequence contains duration values, the values must be either all xs:yearMonthDuration values or all xs:dayTimeDuration values.
• If the function is fn:sum, verify that the following conditions are met: All items in the input sequence must be numeric or derived from a single base type. The type must support addition. If the input sequence contains numeric values, the values must all be promotable to a single common type. If the input sequence contains duration values, the values must be either all xs:yearMonthDuration values or all xs:dayTimeDuration values.

• 1 -- Unsupported Byte Order Mark, declaration string order is incorrect, declaration must be in lower case, the 'version=' string is missing, or unsupported attributes were specified.
• 6 -- Specified version is not supported.
• 7 -- Specified encoding is not supported, or the internal encoding does not match the external encoding.
• 8 -- The XML declaration is not terminated.

• 1 - A rowset name is not specified or is not fully qualified.
• 2 - Any mapping must specify either a target column or a condition. Neither a target column nor a condition is specified.
• 3 - The annotation has an unexpected format.
• 4 - The annotation is empty.

The XML schema document can be determined by matching &2 to the SCHEMALOCATION column of the XSROBJECTCOMPONENTS catalog table. The XML schema is not enabled for decomposition.

• 1 - Specify a rowset name or fully qualify the rowset name.
• 2 - Specify either a target column or a condition.
• 3 - Correct the format of the annotation.
• 4 - Specify an annotation value.

There can only be one value for the db2-xdb:defaultSQLSchema annotation across all XML schema documents that comprise an annotated XML schema. The specified SQL schema name &1 at or near &2 in the XML schema document &3 conflicts with another value for db2-xdb:defaultSQLSchema annotation in this or another XML schema document of the XML schema.

• 1 - An element or attribute has a namespace prefix that is not mapped to a URI. All namespace prefixes used in the location path must be associated with a namespace in the XML schema document containing the annotation specifying this location path.
• 2 - Syntax is not valid for a location path.
• 3 - The specified path does not match any possible path from a root node to a location where the element or attribute may appear in an instance document.

• 1 - Ensure that namespace prefixes in the db2-xdb:locationPath are correct or add a declaration for the missing namespace.
• 2 - Ensure that the syntax of the value for db2-xdb:locationPath is valid syntax for a location path.
• 3 - Ensure that the value for db2-xdb:locationPath corresponds to a possible path from the root node to the element or attribute at the end of the location path.

• Not enabled for decomposition (possibly never enabled)
• Disabled for decomposition

Decomposition can only be performed using XML schemas that are enabled for decomposition. XML decomposition was not started.

• The WITH DATA option cannot be specified with ON REPLACE PRESERVE ROWS.
• A field procedure cannot be defined for a column that has a generated expression.

• 21 The status of the DataLinks cannot be verified. A file cannot be used for INSERT and UPDATE statements while in link pending mode.

• 1 -- Refers to another materialized query table or a protected system file, or to a view that refers to a materialized query table or a protected system file.
• 2 -- Refers to a declared global temporary table, a created global temporary table, a table in QTEMP, a program-described file, or a non-SQL logical file in the FROM clause.
• 3 -- Refers to a VIEW that contains an item for a materialized query table that is not valid.
• 4 -- Contains an expression with a DataLink or a distinct type based on a DataLink where the DataLink is FILE LINK CONTROL.
• 6 -- Refers to a function that has an external action or that is not deterministic.
• 8 -- Refers to a special register or global variable.
• 9 -- Refers to result column that is a not an SQL data type, such as binary with precision, DBCS-ONLY, or DBCS-EITHER.
• 10 -- Refers to a column that has a field procedure defined and that column is used in an expression in the select-list.

• 2 -- The ALTER specified DROP MATERIALIZED QUERY or ALTER MATERIALIZED QUERY, but the specified table is not a materialized query table.
• 4 -- The table has one or more triggers defined.
• 8 -- The table is referenced in the definition of another materialized query table.
• 9 -- The table is referenced directly or indirectly (such as through a view) in the SELECT statement.
• 10 -- The ALTER specified ADD MATERIALIZED QUERY, but the specified table is already a materialized query table.
• 11 -- The number of columns in the existing table does not match the number of columns for the result of the SELECT statement.
• 12 -- Column data types in the existing table do not match the column data types for the result of the SELECT statement.
• 16 -- The ALTER specified ADD MATERIALIZED QUERY, but the specified table has more than one member.
• 19 -- The table is a system-period temporal table or a history table and cannot be defined as a materialized query table.
• 20 -- The ALTER specified ALTER MATERIALIZED QUERY or ADD MATERIALIZED QUERY and either the specified table &1 in &2 or the referenced table &4 in &5 is using row or column access control.

If the failure is due to reason code 20, you must remove all masks and permissions defined on &1 in &2 or &4 in &5. Additionally, row and column access control must be deactivated for both tables.

• 1 - RANGE or ROWS is specified but the OVER clause does not contain an ORDER BY clause.
• 2 - RANGE is specified but the OVER clause has an ORDER BY clause that contains more than one sort key expression.
• 3 - RANGE is specified but the data type of the range value cannot be subtracted from the sort key expression in the ORDER BY clause in the OVER clause.
• 4 - UNBOUNDED FOLLOWING is specified as the first value of BETWEEN or UNBOUNDED PRECEDING is specified as the second value of BETWEEEN.

• 1 - Add an ORDER BY clause in the OVER clause that uses RANGE or ROWS.
• 2 - Make sure the OVER clause that specifies RANGE has only one sort key expression in its ORDER BY clause.
• 3 - For the OVER clause that uses RANGE, make sure the range value can be subtracted from the sort key expression in its ORDER BY clause. The sort key expression must be a numeric or datetime data type. If the sort key expression is a datetime data type, the range value must be a decimal literal the represents a duration for that data type.
• 4 - Specify correct boundary values in the BETWEEN clause.

• The entire table can be returned with a fullselect on a RETURN statement. In this case, there must be exactly one RETURN statement and no PIPE statements in the function.
• The table can be returned one row at a time with the PIPE statement. An empty RETURN statement is used to indicate the end of the function. In this case, there must be at least one RETURN statement and may be any number of PIPE statements in the function.

• A value to a parameter of a remote stored procedure and the value being truncated is greater than 127 bytes. In this case, the indicator variable will contain a value of 127.
• A LOB or XML value to a host variable and the value being truncated is greater than 32767 bytes. In this case, the indicator variable will contain a value of 32767.

In these cases the actual length of the truncated value cannot be returned to the application using the indicator variable. The actual length of the value is returned as message token length.

• The outer fullselect of a SELECT or SELECT INTO statement.
• The only fullselect of a SET or VALUES INTO statement.
• The query expression of a RETURN statement.

If &1 is a view, the WHERE clause in the view definition cannot contain a function that is not deterministic, has external action, or modifies SQL data.

If &1 is a logical file, it cannot have select/omit specifications or be a join logical file.

• Column &1 is a partitioning key column.
• Column &1 is a column in a history table.
• Column &1 is a ROW BEGIN, ROW END, or TRANSACTION START ID and must have a data type that is timestamp with a precision of 12.
• Column &1 is a ROW BEGIN or ROW END and must not allow null values.

• 1 -- ADD PARTITION BY was specified on an ALTER TABLE statement, but the table is already a partitioned table or is a physical file
• 2 -- ADD PARTITION, ALTER PARTITION, ATTACH PARTITION, DETACH PARTITION, or DROP PARTITION was specified on an ALTER TABLE statement, but the table is not a partitioned table.
• 3 -- DROP PARTITION of a RANGE partition was specified on the ALTER TABLE statement, but the PRESERVE ROWS clause was used. The PRESERVE ROWS clause is only valid for partitioned tables that have HASH partitioning.
• 4 -- ALTER PARTITION, ATTACH PARTITION, or DETACH PARTITION of a HASH partition was specified on an ALTER TABLE statement.
• 5 -- A RANGE partition specified on a CREATE OR REPLACE TABLE statement did not match a partition in the existing table.
• 6 -- The partition being attached does not have a range defined.

• Table &1 is a partitioned table and DDS-created logical file &3 is based on the table.
• Table &1 cannot contain a generated column because multi-format logical file &3 is based on the table.
• Table &1 cannot contain a generated column because single-format logical file &3 based on multiple physical files is based on the table.

• 8 -- A function defined as MODIFIES SQL DATA cannot be specified in the select list of a query that contains an OFFSET clause.

• 1 -- The result of applying the sort sequence table to field &1 is greater than 32,742 bytes.
• 2 -- The sort sequence table cannot be applied to the following functions: LOCATE, POSITION, POSSTR, and LOCATE_IN_STRING.
• 3 -- The sort sequence table cannot be applied to a LIKE predicate or %WLDCRD function.
• 4 -- A shared weight sort sequence table cannot be applied to the key fields of a create encoded vector index with INCLUDE statement.
• 5 -- The ICU (International Components for Unicode) table cannot be used for this index.

• 1 -- "xmlns" is used as an XML attribute name or as a prefix for an XML element or attribute name.
• 2 -- The XML namespace prefix in a qualified XML name is not declared within its scope.
• 3 -- The name for an XML element or XML attribute is not an XML QName.
• 4 -- The name for an XML processing instruction is not an XML NCName.
• 5 -- The name for an XML processing instruction cannot contain "xml".
• 6 -- The name for an argument of XMLTABLE is not an XML NCName.

• 1 -- The XML namespace prefix is not an XML NCName.
• 2 -- The name "xml" or "xmlns" cannot be used as an XML namespace prefix.
• 3 -- The XML namespace prefix is not unique.

• 1 -- The number of columns in the source and target tables do not match.
• 5 -- The source table has more than one partition.
• 6 -- The source table is a view, a materialized query table, a declared global temporary table, a system-period temporal table, a history table, or a system table.
• 7 -- The source table and the target table are the same table.
• 8 -- NOT LOGGED INITIALLY was specified for either the source table or the target table, but not both.
• 20 -- The source table has row access control activated but the target table does not have row access control activated.
• 21 -- The source table has column access control activated but the target table does not have column access control activated.
• 28 -- Cannot detach a partition from a table that is the parent of an enabled referential integrity constraint.
• 29 -- The source table and the target table are on different iASPs.
• 31 -- Both the source table and the target table must be mirrored or neither table can be mirrored.

• 1 -- The BY VALUE clause can only be specified when the corresponding data type is XML for an argument of the XMLTABLE function.
• 2 -- The BY VALUE clause can only be specified for an XMLTABLE result column with data type XML.

• The TRUNCATE statement would result in the activation of delete triggers but the statement specified RESTRICT WHEN DELETE TRIGGERS, either implicitly or explicitly. This can occur when enabled delete triggers exist for the table to be truncated, and the result of the TRUNCATE statement would activate the triggers.
• The TRUNCATE statement is for a table that is the parent table in a referential constraint.
• The CREATE OR REPLACE TABLE statement with ON REPLACE DELETE ROWS is for a table that is the parent table in a referential constraint.

• 1 -- The data types do not match.
• 2 -- The null attributes do not match.
• 4 -- The CCSIDs do not match.
• 7 -- The row change timestamp attributes do not match.
• 8 -- The allocate lengths do not match.
• 9 -- A column mask is defined and enabled for column &6 but not for column &7.
• 10 -- The row begin attributes do not match.
• 11 -- The row end attributes do not match.
• 12 -- The transaction start ID attributes do not match.
• 24 -- The field procedures do not match.
• 25 -- The generated expression attributes do not match.
• 27 -- The default values do not match.

Text describing the problem is: &4.

• 1 - One of the text search administrative tables was not found.
• 3 - Text search support is not installed.
• 4 - Text search support is not started.
• 7 - No text search servers have been defined.

Run the PREPARE, OPEN, EXECUTE IMMEDIATE, or FETCH statement when the current connection is to the local database.

Array types can only be used:

• As an argument of as SQL scalar function or an SQL or JAVA procedure.
• For an SQL variable declared in an SQL procedure or SQL scalar function.
• In a CAST specification in an SQL procedure or SQL scalar function.

The data type of the array type that is used when a routine is invoked must match the data type of the array that was used when the routine was created.

The REGEXP_LIKE function returns a boolean type and can only be used as a predicate.

The format string may not be valid for one of the following reasons:

• The format does not contain a format element.
• The format contains multiple elements that represent the same component of a timestamp.
• The format contains a format element that does not apply to the data type of the expression.
• The format contains AM, IYYY.

• The string expression is too short or too long.
• The string expression does not conform to the template specified in the format string.
• Too many digits were specified in the string expression for the corresponding format element in the format string.
• A value in the string expression is not valid for the corresponding format element in the format string.

• If a cycle is expected, add the NOCYCLE keyword to the CONNECT BY clause.
• If no cycles are expected, use the CONNECT_BY_ISCYCLE pseudo column along with the NOCYCLE keyword to find a row that is directly or indirectly an ancestor of itself.

• The construct was specified in the START WITH clause.
• In the subselect where it was specified, there is no CONNECT BY clause.
• PRIOR was specified outside the context of a CONNECT BY clause.
• An argument of CONNECT_BY_ROOT or SYS_CONNECT_BY_PATH cannot be an aggregate function or OLAP specification.
• ORDER SIBLINGS BY was specified, but there is a DISTINCT, GROUP BY, or HAVING clause in the query which has changed the partial order provided by the hierarchical query.

• If the construct is LEVEL and this is not a hierarchical query, make sure a column or variable with that name exists and can be resolved to for the statement.
• Verify that there is a CONNECT BY clause in the subselect containing &1.
• Remove &1 from the statement.

• 20 -- The USING clause is specified and the select list contains only T.* where T is a table in the join. All the columns in table T are contained in the USING clause so the result table is empty.

The expression can only contain constants, special registers, variables, and parameter markers. The expression cannot contain a column, a scalar fullselect, or a function that is not deterministic or has an external action.

• 37 -- A trigger, &4 in &5, is defined for the table and the trigger is not defined as secured or is a read trigger.
• 38 -- A view is defined on the table. Trigger &4 in &5 is defined for that view and the trigger is not defined as secured.
• 39 -- A materialized query table definition directly or indirectly references user defined function &4 in &5 which must be defined as secured due to one of the following conditions: 1) The materialized query table is defined on the table and the table has row or column access control. 2) The materialized query table has row or column access control. 3) The function either directly or indirectly references a table with row or column access control.

37, 38 -- Alter trigger &4 in &5 using the SECURE keyword to make it secure.

• 39 -- Alter user defined function &4 in &5 using the SECURE keyword to make it secure. If the user defined function name is *N, examine the job log to determine which function needs to be altered.

• A user defined function must be secure if it is referenced in a PERMISSION or MASK or is referenced in a view that is referenced by a PERMISSION or MASK.
• A trigger must be secure if it is defined on a table with an active PERMISSION or MASK.
• A trigger must be secure if it is defined on a view that is based on a table with an active PERMISSION or MASK.
• A read trigger cannot be defined over a table with active row or column level access control.

• 3 -- &1 begins with the letters QIBM which are not allowed as the first 4 characters of a row permission or column mask name.

• 1 -- The table for which the row permission or the column mask is being defined. The definition references &1 in &2, type *&3, or references view or alias &5 in &6 that is defined over &1 in &2.
• 3 -- User-defined function &5 in &6, which is not secure.
• 4 -- Function &5 in &6, which is defined as not deterministic or is defined to have an external action. The function cannot be RRN, RID, HASHED_VALUE, DATAPARTITIONNAME, DATAPARTITIONNUM, DBPARTITIONNAME, or DBPARTITIONNUM if the function references the table for which the permission or mask is being defined.
• 5 -- An OLAP specification.
• 7 -- A ROW CHANGE expression.
• 8 -- A sequence reference.
• 9 -- A declared global temporary table, a table in QTEMP, a file with a read trigger, or a distributed file.
• 11 -- A * or name.* in a SELECT clause.
• 35 -- Mask cannot return NULL for a column that is defined as NOT NULL.
• 53 -- Table &5 in &6, which is a member alias.

This failure may occur when attempting to do one of the following operations:

• CREATE MASK or CREATE PERMISSION of &7 in &8.
• CREATE FUNCTION or ALTER FUNCTION of a function that is used by &7 in &8 type &9.
• ALTER TABLE of &1 in &2.
• ALTER MASK or ALTER PERMISSION of &7 in &8.
• ALTER MASK, ALTER PERMISSION, DROP MASK, or DROP PERMISSION of any mask or permission defined on &1 in &2.
• CREATE MASK or CREATE PERMISSION of additional masks or permissions defined on &1 in &2.
• Any operation that uses table &1 in &2.

• Have an actual length that is not greater than 254 bytes.
• Contain only supported format elements.
• Not result in a string with an actual length greater than the length attribute of the result.

• The string expression is too long for the format string.
• The string expression does not conform to the template specified in the format string. For example, there are more digits in the string expression than for the corresponding format element in the format string or a value in the string expression is not valid for the corresponding format element in the format string.

• 20 -- The result table is derived from a recursive common table expression and column &3 is specified in the fullselect of the recursive common table expression. A column mask cannot be applied to column &3.
• 30 -- An insert or update operation is using a masked value returned from column mask &1 in &2 for column &3. The expression specified in the THEN or ELSE clause of the column mask definition that is used to return the masked value is not a direct reference of column &3.
• 51 -- A distributed table cannot be referenced in a query that also references a table with active permissions or masks.
• 52 -- A table with read triggers cannot be referenced in a query that also references a table with active permissions or masks.

For INSERT and UPDATE, the value returned from the mask must be a direct reference to the column itself.

Remove the incorrect reference and try the request again.

• 1 -- Dependent object &5 in &6 type &7 references column &8.
• 2 -- The authorization ID associated with the statement in not authorized to the QIBM_DB_SECADM function.
• 3 -- &1 in &2 type *&4 is defined with row or column access control. An attempt to regenerate &5 in &6 has failed.

• 1 -- DROP the dependent object &5 in &6 type &7 and try the request again.
• 2 -- Perform the operation with a user profile that is authorized to the Database Security Administrator function. This is obtained through Application Administration in System i® Navigator, or with the Change Function Usage Information (CHGFCNUSG) command with a function ID of QIBM_DB_SECADM.
• 3 -- See previously listed messages in the job log for the cause of the failure, correct the problem and retry the request.

• 1 -- The new view definition of &1 in &2 contains a reference to itself. This circular self-reference can either be explicit in the definition, or implicit by a reference to another view that explicitly or implicitly references &1.
• 2 -- Function &1 in &2 contains a reference to itself in its default expression. This can happen through the invocation of another function that references &1.
• 3 -- CREATE OR REPLACE TABLE of &1 in &2 contains a reference to itself or to a dependent view, materialized query table, or alias.

• 1 -- The CALL statement or function invocation includes named argument &1 which does not exist for routine &2 in schema &3.
• 2 -- The CALL statement or function invocation includes named argument &1 which is followed by one or more unnamed arguments. All arguments following a named argument must also be named.
• 3 -- The CALL statement or function invocation specifies named argument &1 more than once, either explicitly or implicitly.
• 4 -- The CALL statement specifies named argument &1 and routine &2 in &3 is not found. Named arguments are only supported for procedures defined with the CREATE PROCEDURE statement.
• 5 -- The function invocation of &2 in &3 specifies named argument &1 and the ordinal position of the corresponding parameter is different for at least two candidate functions.

• 1 -- The table is already a system-period temporal table or a history table.
• 2 -- The table does not have a SYSTEM_TIME period defined or does not have a transaction start ID column.
• 3 -- The table is a materialized query table or a distributed table.
• 6 -- The table or the associated history table has the NOT LOGGED INITIALLY attribute activated.
• 10 -- The table has a ROWID or a DataLink with FILE LINK CONTROL column.

• 1 -- The start column and the end column cannot be the same column.
• 6 -- The start column must be defined as a row begin column and the end column must be defined as a row end column.

• 1 -- The table is a system-period temporal table, a history table, a view, a declared global temporary table, a materialized query table, a distributed table, or was created using DDS.
• 4 -- The table has a column defined as a generated column.
• 5 -- The table has a period defined.
• 6 -- The table is part of a referential constraint or has a primary or unique constraint.
• 7 -- The number of columns in the system-period temporal table and the history table are not the same.
• 10 -- The corresponding columns of the system-period temporal table and the history table must have identical names, data type, length, precision, scale, CCSID, FOR xxx DATA, null attribute, hidden attribute, and field procedure.
• 12 -- The table has a before insert or before update trigger defined.
• 13 -- Both the temporal table and the history table must be mirrored or neither table can be mirrored.

• 1 -- A FOR SYSTEM_TIME period was specified both in the definition of a view and explicitly or implicitly in a query that references the view.
• 2 -- A FOR SYSTEM_TIME period was specified in the FROM clause but the table is not a view or system-period temporal table.
• 3 -- Expression is not valid. The result of the expression must be compatible with a TIMESTAMP(12). It cannot contain a column reference, a scalar fullselect, or a function that is not deterministic, has an external action, or modifies SQL data.
• 4 -- The period specification or period clause was specified for a view where the view definition includes an external function other than NO SQL or an SQL function that is not inline capable.
• 6 -- A FOR SYSTEM_TIME clause was specified but the value of the CURRENT TEMPORAL SYSTEM_TIME special register is not null and the SYSTIME option is set to YES.

• 1 -- Cannot add a period to a history table.
• 2 -- Cannot drop a period from a system-period temporal table.
• 4 -- Cannot drop versioning for a table that is not a system-period temporal table.
• 9 -- Cannot truncate a system-period temporal table.
• 11 -- Cannot define a referential constraint where either the parent or child table is a history table. A primary or unique constraint cannot be defined for a history table.
• 12 -- Cannot detach a partition from a system-period temporal table.
• 13 -- Cannot add a column to a history table.
• 16 -- Cannot add a generated column, ROWID column, or DataLink with FILE LINK CONTROL column to a system-period temporal table.
• 17 -- Cannot specify ACTIVATE NOT LOGGED INITIALLY.
• 21 -- CREATE TABLE with the OR REPLACE option cannot reference a system-period temporal table or a history table.
• 22 -- An ALTER TABLE statement for a system-period temporal table attempted to define a referential constraint with a delete rule of CASCADE, SET DEFAULT, or SET NULL.

To allow system adjustment of the row begin and row end values, set the SYSTIME_PERIOD_ADJ INI option to have a value of *ADJUST.

• CREATE FUNCTION (SQL)
• CREATE PROCEDURE (SQL)
• CREATE TRIGGER

If the argument is one of these statements, it is not valid if it has already been wrapped and the token directly following the WRAPPED keyword is not a supported application server value.

• 1 -- The statement was wrapped on a platform or version that is not supported.
• 2 -- The obfuscated portion of the statement is corrupted.

• 1 -- The CURRENT TEMPORAL SYSTEM_TIME special register contains a non-null value and the target of the data change operation is a system-period temporal table (directly or indirectly). The data in a system-period temporal table cannot be changed when a period specification is in effect.

• 1 -- Syntax error in regular expression pattern.
• 2 -- Unrecognized backslash escape sequence in pattern.
• 3 -- Incorrect Unicode property name.
• 4 -- Use of regular expression feature that is not supported.
• 5 -- Incorrectly nested parentheses in regular expression pattern.
• 6 -- Decimal number is too large.
• 7 -- Error in {min,max} interval.
• 8 -- Maximum is less than minimum in {min,max} interval.
• 9 -- Back-reference is made to a non-existent capture group.
• 10 -- Look-behind pattern matches must have a bounded maximum length.
• 11 -- Regular expressions cannot have UnicodeSets containing strings.
• 12 -- Octal character constants must be less than or equal to 0377.
• 13 -- Missing a closing bracket on a bracket expression.
• 14 -- In a character range [x-y], x is greater than y.
• 15 -- Unspecified error.

The location codes are:

• '01'X -- The error was detected at the application requester.
• '02'X -- The error was detected at the application server.

A possible list of protocol errors is:

• '121C'X -- Not authorized to command.
• '1245'X -- Conversation protocol error. The error code is &3.
• '124C'X -- Data stream syntax error. The error code is &3.
• '1254'X -- Unexpected error condition. The error code is &3.
• '125F'X -- Application server does not support function requested.
• '2202'X -- Cursor not open.
• '2204'X -- Relational database not connected.
• '2207'X -- Relational database already connected.
• '220A'X -- Data descriptor not valid. The error code is &3.
• '220E'X -- Data descriptor did not match data.
• '220F'X -- Cursor already open.
• '221D'X -- Command not valid for conversation type.

If the protocol error does not appear in the list, refer to the DDM Architecture Reference for DDM code point &1.

The location codes are:

• '01'X -- The error was detected at the application requester.
• '02'X -- The error was detected at the application server.

A possible list of protocol errors is:

• '1218'X -- Unsupported function requested. The error code is &3.
• '1232'X -- Unexpected permanent error.
• '1245'X -- Conversation protocol error. The error code is &3.
• '1254'X -- Unexpected error condition. The error code is &3.

If the protocol error does not appear in the list, refer to the DDM Architecture Reference for DDM code point &1.

On the remote system, the DDM manager class was &1 with manager level &2.

DRDA resource &2 is unavailable at relational database &1 with location code &3.

The resource codes are:

• '1409'X -- Communication buffer.
• '1410'X -- Local build space.
• '1411'X -- Diagnostic area.
• '1412'X -- Local build space.
• '1413'X -- LOB build space.
• '1414'X -- Pool space.

The location codes are:

• '01'X -- Application requester.
• '02'X -- Application server.

DRDA resource &2 is unavailable at relational database &1 with location code &3.

The resource codes are:

• '1409'X -- Communication buffer.
• '1410'X -- Local build space.
• '1411'X -- Diagnostic area.
• '1412'X -- Local build space.
• '1413'X -- LOB build space.
• '1414'X -- Pool space.

The location codes are:

• '01'X -- Application requester.
• '02'X -- Application server.

• Use the Add Relational Database Directory Entry (ADDRDBDIRE) command to add the relational database name to the relational database directory.
• Change the relational database name to match the relational database directory entry.
• Verify the relational database name is defined on the remote location.

If the DDM command is '2012'X, the remote system does not support the SQL DESCRIBE TABLE statement. If the DDM command is not '2012'X, to determine which command is not supported, see the DDM Architecture Reference. For a list of DDM commands, refer to the Architecture Books section of the Bibliography in the Distributed database programming topic collection in the Database category in the IBM i Information Center, http://www.ibm.com/systems/i/infocenter/.

The location codes are:

• '01'X -- The error was detected at the application requester.
• '02'X -- The error was detected at the application server.

The location code are:

• '01'X -- The error was detected at the application requester.
• '02'X -- The error was detected at the application server.

A possible list of DDM parameter values is:

• '0035'X -- The SBCS CCSID is not supported.
• '119C'X -- The SBCS CCSID is not supported.
• '2112'X -- The schema name or package name is longer than the maximum supported by the application server.
• '2120'X -- The string delimiter is not supported.
• '2121'X -- The decimal delimiter is not supported.
• '2128'X -- The schema name is longer than the maximum supported by the application server.
• '2131'X -- The userid is longer than the maximum supported by the application server.

If &1 is not in the list above, refer to the DDM Architecture Reference for a description of the parameter value that was not supported.

• The remote system is not available.
• The communications network is not available.
• The userid used to start the connection may not exist on the remote system.
• The remote system may require the password to be encrypted.
• The password may not be valid for the userid. The characters and case of the password specified must match exactly the password on the remote system.
• A server authorization entry for the remote system, if used, may be incorrect. Server names must be in upper case. The QRETSVRSEC system value must be set to '1' to retain passwords.

If message CPE3425 (connection refused) precedes this message, the cause may be:

• The DDM/DRDA TCP/IP server is not started on the remote system.
• An incorrect port was specified for the remote system.
• The remote system is restricting DRDA ports.
• The SOCKS server, if used, is not configured properly.

The APPC major return code is &1 and the minor return code is &2. For TCP/IP, both return codes will be 00. If the return codes are not both 00, their meaning can be found in the APPC Programming topic in the Information Center, http://www.ibm.com/systems/i/infocenter/.

• The local system timed out waiting for the connection to be started.

• 0 -- Unknown cause.
• 1 -- Password expired.
• 2 -- Password not valid.
• 3 -- Password missing.
• 4 -- Protocol violation.
• 5 -- User ID not found.
• 6 -- User ID not valid. For a DB2 for IBM i server, this could mean a damaged user profile or PASSWORD(*NONE).
• 7 -- User ID revoked or disabled.
• 15 -- Security processing at the server failed.
• 16 -- The new password is not valid.
• 17 -- The security mechanism requested by the client is not supported or allowed at the server. See recovery information below.
• 22 -- Security processing at the client failed.
• 23 -- CCSID conversion of the password failed.

• 1 -- By using the USER ... USING ... clause on the SQL CONNECT statement, or
• 2 -- By using the ADDSVRAUTE CL command to add a server authorization entry for the remote server under the user's profile. The server name (DRDA RDB NAME) must be entered in upper case. &N The DRDA server can be configured with the CHGDDMTCPA CL command to not require a password, or to not require an encrypted password.

• The remote system is not available.
• The communications network is not available.
• The userid used to start the connection may not exist on the remote system.

This message can occur when initially attempting to connect to a system other than DB2 for IBM i using interactive SQL with the COMMIT option set to *NONE.

PATH -- schema-names

AS400NAMING -- SQL (Default) or SYSTEM

OS400NAMING -- SQL (Default) or SYSTEM

SORTSEQ -- HEX (Default) or JOBRUN

MAXSCALE -- between 0 and 31

MINDIVSCALE -- between 0 and 9, MINDIVSCALE must not exceed MAXSCALE

ROUNDING -- HALFEVEN (Default), CEILING, DOWN, FLOOR, HALFDOWN, HALFUP, or UP

EXTENDEDINDICATOR -- NO (Default) or YES

DATEOVERIDE -- ISO (Default), USA, EUR, JIS

CONCURRENTACCESSRESOLUTION -- NO (Default) or YES

SYSTEMTIMESENSITIVE -- NO (Default) or YES

• For embedded SQL remove the WITH RELEASE clause from the CLOSE.
• For CLI remove the option to define cursors with release.

• The member could not be found by the precompiler. The member does not exist in the file specified in the INCFILE parameter on the CRTSQLxxx command. If source file is *N, the source file used for the SQL INCLUDE statement is the file specified on the SRCFILE parameter.
• You must be authorized to the source file that contains member &1.

• Ensure that the name of the member is correct. If the member name is already correct and member name &1 is not found, verify the file containing the member on the INCFILE parameter of the CRTSQLxxx command is correct.
• Obtain the required authority from either the security officer or the source file owner.

• Cursor &1 has already been specified in a previous DECLARE CURSOR statement. A cursor name must be unique within the program.
• Procedure &1 specified on a CALL statement is ambiguous.

• 1 -- Top level count is incorrect
• 2 -- SQDS_ITEMS is incorrect
• 3 -- Level of array-related descriptor items is incorrect

• The value given for the maximum number of items on an ALLOCATE DESCRIPTOR statement is not between 1 and 8000.
• The item number given on a GET DESCRIPTOR or SET DESCRIPTOR statement is not between 1 and the maximum number of items assigned when the descriptor was allocated.

• The GET DESCRIPTOR statement requested the DATA or INDICATOR item, but the DATA or INDICATOR item has no value.
• The GET DESCRIPTOR or SET DESCRIPTOR statements specified a host variable for the DATA item that is not valid. The host variable must match the DATA item in type, length, precision, scale, and CCSID.

• The descriptor name is longer than 128 characters.
• The descriptor name has not been allocated with an ALLOCATE DESCRIPTOR statement.
• A descriptor with this name already exists for the connection and scope.

• DECLARE CURSOR, DECLARE STATEMENT, FETCH, OPEN, CLOSE, WHENEVER, PREPARE, EXECUTE, EXECUTE IMMEDIATE, INCLUDE, SELECT INTO, VALUES INTO, DECLARE VARIABLE, DECLARE PROCEDURE, DESCRIBE, GET DIAGNOSTICS, SIGNAL, RESIGNAL, ALLOCATE CURSOR, ASSOCIATE LOCATOR, ALLOCATE DESCRIPTOR, DEALLOCATE DESCRIPTOR, GET DESCRIPTOR, and SET DESCRIPTOR are not allowed in interactive SQL, dynamic SQL, or when using the RUNSQLSTM or RUNSQL commands.
• BEGIN DECLARE SECTION and END DECLARE SECTION are not allowed in interactive SQL, in dynamic SQL, in RPG, or in REXX.
• A blocked INSERT statement is not allowed in interactive SQL or dynamic SQL.
• The CONNECT, SET CONNECTION, RELEASE, and DISCONNECT statements are not allowed in dynamic SQL or REXX. CONNECT with constants specified for user ID and password is not allowed in a precompiled program.
• SET ENCRYPTION PASSWORD with constants specified for user ID or hint is not allowed in a precompiled program.
• SELECT and VALUES cannot be issued from an EXECUTE IMMEDIATE statement or the RUNSQLSTM or RUNSQL commands.
• The SET OPTION statement is only allowed in REXX, in a precompiled program, or in SQL routines. In a precompiled program, it must be the first SQL statement in the program.
• ALLOCATE CURSOR, ASSOCIATE LOCATORS, DECLARE STATEMENT, DECLARE VARIABLE, DECLARE PROCEDURE, GET DIAGNOSTICS, INCLUDE, SELECT INTO, SET CURRENT DEGREE, SET RESULT SETS, SIGNAL, WHENEVER, blocked INSERT, blocked FETCH, locator statements, and SQL descriptor statements are not allowed in REXX.
• The SET TRANSACTION statement is not allowed when the current connection is to a remote database.
• The SET SESSION AUTHORIZATION statement can only be run in the default activation group. It is not allowed in REXX, or when using the RUNSQLSTM or RUNSQL commands.
• The WRAPPED keyword for functions, procedures, and triggers is not allowed in a precompiled program.
• The SQL statement specified is not a valid statement on the current release of DB2 for IBM i. The statement may be valid on a future release of DB2 for IBM i or on some other system's implementation of SQL.

• Verify that all the rows in the specified table need to be deleted or updated and try the statement again.
• If the rows in the specified table do not need to be deleted or updated, add a WHERE clause and precompile the program again.

• In a CREATE VIEW, CREATE TABLE, CREATE INDEX, CREATE MASK, CREATE PERMISSION, or ALTER TABLE statement.
• In a default value clause for a parameter in a CREATE PROCEDURE or CREATE FUNCTION statement.
• In any interactive SQL statement when the statement processing value is *RUN or *VLD.
• In an SQL statement processed by the RUNSQLSTM or RUNSQL commands.
• In an INSERT, UPDATE, DELETE, CALL, or DECLARE CURSOR statement in REXX.

• Specify either a constant or a column name to replace the host variable. The colon indicates that the name that follows is a host variable. Remove the colon to specify a column name.
• If in interactive SQL, set the statement processing value to *SYN to syntax check a statement that contains a host variable.
• If in REXX, change the host variables to parameter markers and prepare the INSERT, UPDATE, DELETE, CALL, or DECLARE CURSOR statement.

• LONG VARCHAR, LONG VARGRAPHIC, and LONG VARBINARY can only be specified for column definitions in the CREATE TABLE statement.
• In the XMLTABLE function BINARY, VARBINARY, BLOB, ROWID, DATALINK, and strongly typed distinct types are not allowed as input arguments or as result column types.
• In the JSON_TABLE function the input argument must be a string data type. BINARY, VARBINARY, BLOB, ROWID, DATALINK, XML, and strongly typed distinct types are not allowed as result column types. For a formatted result column, the result data type must be character or Unicode graphic.

• If this is a FETCH statement, no more rows satisfy the selection values (end of file). The name of the cursor is &1 and the result set identifier is &2. If the result set identifier is non-zero, the result table for this cursor was being accessed as a stored procedure result set.
• If this is a FETCH statement for a scrollable cursor, a record was not found. If NEXT was specified, end of file was reached. If PRIOR was specified, the beginning of the file was reached. If RELATIVE was specified, either the beginning of file or the end of file was reached, depending on the value specified. If FIRST or LAST was specified, then no records satisfy the selection criteria. The name of the cursor is &1.
• If this is an embedded SELECT statement, no rows satisfy the selection values.
• If this is an UPDATE, INSERT, DELETE, or MERGE statement, no rows satisfy the subselect, WHERE clause, or MERGE criteria. No rows were updated, inserted, or deleted.
• If SKIP LOCKED DATA is specified, no available rows qualified for return.

• 1 - The total number of subselects combined using UNION, EXCEPT, and INTERSECT is greater than 1000.
• 2 - The total number of columns, constants, and operators is greater than the SQL limits.
• 3 - The sum of the lengths of the non-LOB and XML columns in a select list, table, view definition, or user defined table function is greater than 32766 or the definition contains LOB or XML columns and the sum of the lengths specified on the ALLOCATE clause for varying-length fields and the non-varying field lengths is greater than 32740. The maximum length is reduced if any of the columns are varying-length or allow null values.
• 4 - The total number of subselects referenced in an outer subselect is greater than 256.
• 5 - The total length of the statement text is greater than 2097152, or the total length of the prepare attribute string text is greater than 65535.
• 6 - The relative position value specified on the FETCH statement is outside the range of valid values.
• 7 - A system name could not be generated.

• Verify that token &1 is valid. Use apostrophes or quotation marks if a character constant is required.
• Remove the character or characters that are not valid if a number is required.

• Verify the SQL statement in the area of the token &1. Correct the statement. The error could be a missing comma or quotation mark, it could be a misspelled word, or it could be related to the order of clauses.
• If the error token is <END-OF-STATEMENT>, correct the SQL statement because it does not end with a valid clause.

• An odd number of bytes were found between the shift-out and shift-in characters.
• Multiple shift-out characters were found before a shift-in character was found.
• A shift-out and shift-in were not found in the first and last byte, respectively, or were found in a position other than the first and last byte of a graphic string constant.
• The PL/I form of the graphic string was used but the program is not PL/I.
• A shift-out was found indicating a PL/I graphic string. The shift-out was not followed by a DBCS apostrophe, an even number of DBCS characters, another DBCS apostrophe, a DBCS G, and a shift-in.

If this is a LABEL ON statement for a column, and the string is longer than 20 bytes, then one of the 20-byte segments has a DBCS constant that is not valid.

• DECFLOAT precision must be either 16 or 34.
• FLOAT precision must be in the range 1-53. If 1-23 is specified, the data type is single-precision floating point. If 24-53 is specified, the data type is double-precision floating point.

• System names cannot exceed 10 characters.
• SQL names cannot exceed 128 characters.
• Relational database names cannot exceed 18 characters.
• Procedure or function names cannot exceed 128 characters. If the external program name is not specified, the name cannot exceed 10 characters because it is used for the program name.
• Host variable names in C and C++ cannot exceed 128 characters. Host variable names in all other languages cannot exceed 64 characters.
• A JSON name cannot exceed 128 characters.
• A JSON path name cannot exceed 128 characters.

The maximum length of the string for a password is 128.

The maximum length of the string for a COMMENT ON statement is 2000. The string for COMMENT ON SEQUENCE cannot exceed 500 characters.

The maximum length of the string for a LABEL ON statement is 50. If the label is specified as a column heading, the maximum is 60.

The maximum length of the string for a package version is 64.

• SELECT INTO and VALUES INTO statements cannot include the FOR UPDATE clause, the FOR READ ONLY clause, the OPTIMIZE clause, or the UNION, EXCEPT or INTERSECT operator.
• A SELECT or VALUES statement used in cursor declarations or subselects cannot have an INTO clause.
• CREATE VIEW statements may not have an INTO, ORDER BY, FOR UPDATE, FOR READ ONLY, or OPTIMIZE clause.
• INSERT statements may not have an INTO clause in a subselect, a FOR UPDATE, FOR READ ONLY, or an OPTIMIZE clause.
• INSERT with VALUES cannot have an ORDER BY, OFFSET, or FETCH FIRST clause.
• WHERE CURRENT OF cursor clause is not allowed in statements processed in interactive SQL or statements processed by the RUNSQLSTM command.
• The NOT NULL clause is not allowed in the definition of a column being added to a table unless a default value is specified.
• OVERRIDING USER VALUE and OVERRIDING SYSTEM VALUE are only valid if the statement is changing a column that is defined with GENERATED.
• The INSERTING, UPDATING, and DELETING trigger event predicates are only allowed in a trigger.
• ON REPLACE cannot be specified unless OR REPLACE is specified.
• The RAISE_ERROR function cannot be specified alone in the select list or in a CASE expression.

An ordinary identifier must begin with (A-Z, $, #, or @) and be followed by zero or more (A-Z, 0-9, $, #, @, or _).

A delimited identifier is a string of characters within SQL escape characters. The characters allowed in delimited names depends on the type of name.

• The characters between the escape characters for system table names, schema names, package names and other system object names can be any characters except Hex 00-3F, Hex 40 (space), Hex 5C (*), Hex 6F (?), Hex 7D ('), Hex 7F ("), and Hex FF.
• The characters between the escape characters for SQL names can be any characters except Hex 00-3F and Hex FF.
• Delimited system column names must begin with (A-Z, $, #, or @) and be followed by zero or more (A-Z, 0-9, $, #, @, or an _).

A relational database name can contain A-Z, 0-9, $, #, @, and _.

Ordinary identifiers that are contained within host variables must not include lowercase letters because they are not converted to uppercase.

• For an INSERT or UPDATE statement, the number of values is not the same as the number of columns.
• For an UPDATE statement, the number of entries in the select list of a row fullselect does not match the number of columns listed in the SET clause.
• For an INSERT with subselect, the number of entries in the select list is not the same as the number of columns for the INSERT.
• For an INSERT statement, one or more of the columns omitted from the column list was created as NOT NULL.
• For an INSERT statement, one or more of the columns specified for the INSERT was created as NOT NULL, and the statement specified DEFAULT as the value to be inserted.
• For SET or VALUES INTO, the number of values is not the same as the number of target host variables.

• Column &1 specified in a HAVING clause is not within an aggregate function and is not in the GROUP BY clause.
• An expression specified in a HAVING clause is not within an aggregate function and is not in the GROUP BY clause.

• An aggregate function or user-defined function sourced on an aggregate function cannot be specified in a SET clause, in a GROUP BY clause, in a START WITH clause, in a CONNECT BY clause, in a JOIN condition, as the return expression for a RETURN statement, as an argument of a table function, or as an expression in a SET statement, a VALUES INTO statement, or a MERGE statement. An aggregate function or user-defined function sourced on an aggregate function is allowed in a WHERE clause only if the WHERE clause appears within a subquery of a HAVING clause.
• The ARRAY_AGG function can only be specified in the select list of a SELECT INTO statement or in a scalar subquery on the right side of a SET statement. DISTINCT cannot be specified with ARRAY_AGG.
• An OLAP specification cannot be used in a WHERE clause, in a VALUES clause, in a GROUP BY clause, in a HAVING clause, in a START WITH clause, in a CONNECT BY clause, or in a JOIN condition. An OLAP specification cannot be used as an expression in a SET statement, VALUES INTO statement, CALL statement, or MERGE statement, in the SET clause of an UPDATE statement, in a key definition of a CREATE INDEX statement, in an XMLTABLE function, or as the return expression for a RETURN statement.

• If the object is a view, two columns in the view may identify the same column in the base table.
• The names may correspond to the same system column name.

• Remove the duplicate column.
• Specify a column list on the statement to remove the duplicate column.

• The statement contains column name &1 and an aggregate function in the SELECT clause and no GROUP BY clause is specified.
• Column name &1 is specified in the SELECT clause but not in the GROUP BY clause.
• An expression is specified in the SELECT clause but not in the GROUP BY clause.
• A column or expression that is specified in the ORDER BY clause, but not in the SELECT clause, does not conform to the grouping rules listed above.

• If a GROUP BY clause is required, make certain that all columns or expressions in the SELECT list and ORDER BY clause are also in the GROUP BY clause.
• If a GROUP BY clause is not needed, the SELECT list and ORDER BY clause should not contain aggregate functions with column names.

The ESCAPE character is not valid if:

• The length is not 1 SBCS character or 1 graphic character.
• The shift-in (X'0E') and the shift-out (X'0F') characters are specified.

The LIKE pattern is not valid if:

• The character string expression forming the pattern contains an ESCAPE character that is not followed by a percent sign, an underscore, or another ESCAPE character.
• The graphic string expression forming the pattern contains an ESCAPE character that is not followed by a DBCS percent sign, a DBCS underscore, or another ESCAPE character.

• The operand to the right of the LIKE operator is not character, binary, graphic, or numeric.
• The operands of the LIKE predicate are not compatible.
• The ESCAPE character is not character, binary, or graphic.

AVG( outertable.column1 + innertable.column2 )

is not valid, while the expression

AVG( outertable.column1 ) + innertable.column2

is valid.

• The argument of a COUNT function is too long. The argument of a COUNT function cannot be longer than 2000 bytes if DISTINCT is specified. If the argument is graphic, then the argument cannot be longer than 1000 DBCS characters.
• More than 268 libraries were specified on the SET PATH statement or on the SET OPTION SQLPATH statement.

• ORDER BY
• GROUP BY
• OUTER JOIN and EXCEPTION JOIN
• OLAP ordering
• ARRAY_AGG function
• XMLAGG function

If the allow copy data option is ALWCPYDTA(*NO), the total length of all expressions cannot exceed 32766 bytes.

CUBE grouping can have a maximum of 10 expressions.

• 32766 bytes if the result is fixed-length character or fixed-length binary.
• 32740 bytes if the result is varying-length character or varying-length binary.
• 16383 DBCS characters if the result is fixed-length graphic.
• 16370 DBCS characters if the result is varying-length graphic.
• 2147483647 bytes if the result is a binary or character LOB.
• 1073741823 DBCS characters if the result is a double-byte character LOB.

• For the SUBSTRING function, argument 2 specifies the position of the first character of the result and argument 3 specifies the length of the result. Argument 2 must be a valid position of the first argument. Argument 3 must not exceed the length of argument 1 between argument 2 and the end of the string.
• For the LEFT function, argument 2 specifies the length of the result. Argument 2 must not exceed the length of argument 1.
• For the OVERLAY function, argument 3 must not exceed the length of argument 1.
• If argument 1 is a character string or a binary string, a character is a byte, and if argument 1 is graphic string, a character is a DBCS character.
• If the argument is *N, then one of the arguments is not valid but the argument number is not known.

Reason code 1, section number &1 has already been assigned.

Reason code 2, section number &1 is smaller than next possible number.

Reason code 3, section number on ENDBND is smaller than highest one assigned.

Reason code 4, section number is not in the SQL package.

Reason code 5, section number of zero is not valid.

ppp identifies the product as follows:

DSN for DB2 for z/OS®

ARI for VM and VSE

QSQ for DB2 for IBM i

SQL for all other DB2 products

vv is a two-digit version identifier such as '07'

rr is a two-digit release identifier such as '01'

m is a one-digit modification level such as '0' .

For example, if the application server is Version 7 Release 1 of DB2 for z/OS, the value of the product identification is 'DSN07010'.

A view or logical file can be used only for read operations if one or more of the following conditions are true:

-- The view contains a DISTINCT keyword, GROUP BY clause, HAVING clause, CONNECT BY clause, FOR SYSTEM_TIME clause, or an aggregate function in the outer fullselect.

-- The view or logical file references more than one table in the outer fullselect.

-- The view contains a subquery that refers to the same table as the table of the outer fullselect. A view of this type may be used for inserting rows.

-- The view contains UNION, EXCEPT, or INTERSECT in the outer fullselect.

-- All the columns of the view are expressions, constants, or special registers.

-- All the columns of the logical file are input only.

-- The select list of the view omits a column of the based on table that does not allow null values or default values. Inserting into the view is not allowed.

-- A history table cannot be modified directly.

• Derived from an expression, a constant, or a special register.
• Defined on a column of an underlying view that cannot be updated.
• A column of a logical file that is defined as input only.

Either extended indicator support is not enabled or extended indicator support is enabled but the indicator value is not UNASSIGNED.

• An element of the SELECT list is not a column and the AS clause is not specified.
• Corresponding columns of the subselects in a UNION, EXCEPT, or INTERSECT do not have the same name.
• Two result columns have the same column name. Every column name and system-column name must be unique in a table or view definition. If two column names are the same, the column name is &1.

• Provide a list of names for the columns in the table, view, or derived table.
• Specify an AS clause to assign a unique name to the unnamed elements or to rename the duplicate columns in the SELECT list.

• The number of column names specified for a view in a CREATE VIEW statement is not the same as the number of elements specified in the following fullselect.
• The number of column names specified for a table in a CREATE TABLE statement is not the same as the number of elements specified in the following fullselect.
• The number of column names specified in a correlation clause is not the same as the number of elements in the table, derived table, table function, data change table reference, or UNNEST.
• The number of column names specified in a column list of a common table expression is not the same as the number of elements specified in the fullselect.
• The number of columns specified in the RETURNS TABLE clause of a user defined table function is not the same as the number of elements specified in the fullselect in the RETURN statement.
• The number of columns specified in the RETURNS TABLE clause of a user defined table function is not the same as the number of elements specified on the PIPE statement.

CREATE TRIGGER must specify a table if it is a BEFORE or AFTER trigger. CREATE TRIGGER must specify a view if it is an INSTEAD OF trigger.

A GRANT or REVOKE with the USER keyword must specify a user profile. A GRANT or REVOKE with the GROUP keyword must specify a group profile.

If this is a DROP statement:

• If &1 is an index, use a DROP INDEX statement.
• If &1 is a view, use a DROP VIEW statement.
• If &1 is a table, use a DROP TABLE statement.
• If &1 is an alias, use a DROP ALIAS statement.

If this is a COMMENT ON INDEX or COMMENT ON ALIAS statement and &1 is a table or view, use a COMMENT ON TABLE statement.

If this is a RENAME INDEX statement and &1 is a table or view, use a RENAME TABLE statement.

If this is a REFRESH TABLE statement, specify a materialized query table.

If this is a CREATE TRIGGER, specify a table for a BEFORE or AFTER trigger, or a view for an INSTEAD OF trigger.

If this is a GRANT or REVOKE statement, specify the correct type of profile or remove the USER or GROUP keyword.

• The first FROM clause identifies more than one table or view.
• The first SELECT clause contains the DISTINCT keyword.
• A UNION, EXCEPT, or INTERSECT was specified.
• The outer subselect contains a GROUP BY clause.
• The outer subselect contains a HAVING clause.
• The outer subselect contains an aggregate function.
• The outer subselect contains a UNION, EXCEPT, or INTERSECT.
• All the select items in the outer subselect are expressions.
• The WHERE clause contains a global variable.
• The SELECT statement contains a scalar subselect.
• The WITH CASCADED CHECK OPTION clause was specified and a view in the FROM clause contains a scalar subselect.
• A special register or a function that is not deterministic, MODIFIES SQL DATA, or EXTERNAL ACTION is somewhere other than the outer select list.
• A view in the FROM clause has an INSTEAD OF trigger defined on it.
• The WHERE clause contains the VERIFY_GROUP_FOR_USER scalar function.