Invalid input parameter has a value of '&1'.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Invalid function code '&1' passed to module.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
You have no more storage space.
Your command cannot be executed because you don't have any space left in your virtual storage or in the QMF internal buffer.
Use a RESET DATA command. This should give you additional storage space. If you are not using DATA now, perhaps more storage space is necessary for your session. If this error repeats, contact your QMF administrator. If you are running a QBE query, reduce your query operation rows until you no longer receive the message.
The database does not support 3-part names.
The name you specified has a location qualifier "&V1". The database you are using does not support location qualifiers.
Remove the location qualifier "&V1" and retry your command. See your QMF administrator to make sure you are using the correct database.
Invalid function code '&1' passed to module.
Follow the directions in the referenced message.
Errors detected while &1 EXEC was executed.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Free storage failed.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
QMF could not read the communication database. Bind package &V1..
The QMF programs may not be installed in the local database. Alternatively, the QMF programs are installed, but installation of the DB2 communication database may have followed that of QMF.
Ask your QMF administrator to bind the DBRM for &V1. to a package in the local database.
See DSQ10012
Follow the directions in the referenced message.
The module &1 could not be loaded.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
The module &1 could not be deleted.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
PROFILE information is needed to start your session.
Characteristics necessary to control your terminal session are not available to QMF. You cannot proceed until you have a PROFILE.
Ask your QMF administrator to enroll you into the QMF system. When this has been completed, restart your session.
Cannot reset: you have no saved profile.
There is no profile for your userid, and no default system profile, in the system control table Q.PROFILES. Hence you cannot reset your profile. You can continue operating with the current profile in temporary storage.
Give the command DISPLAY PROFILE, and change your current profile to have the values you would like. Then give the command SAVE PROFILE, so there will be a profile on record for your userid (otherwise you will not be able to sign on to QMF again). Find out who or what erased your profile, and prevent it happening again.
Your directory entry for QMF is not valid.
In order to sign on to QMF, you must have a directory entry that names the SQL/DS database virtual machine that QMF connects to.
See your QMF administrator about correcting your directory entry.
PROFILE information is needed to connect as &V1..
Characteristics necessary to control your terminal session as user &V1 are not available to QMF. You cannot proceed until there is a PROFILE for &V1..
Ask your QMF administrator to enroll the requested user into the QMF system. When this has been completed, a connect for that user can then be accomplished.
Invalid function code '&1' passed to module.
Follow the directions in the referenced message.
OK, the &1 command was cancelled at your request.
See DSQ10012
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
See DSQ10012
Follow the directions in the referenced message.
Error reading Q.RESOURCE_VIEW. SQLCA is: &V1
The was an error detected when trying to read QMF governor resource view. The SQLCA contains information about the specific error. QMF continues to function without access to resource table.
Report the error in accordance with your installation's procedures.
Invalid function code '&1' passed to module.
Follow the directions in the referenced message.
See DSQ10012
Follow the directions in the referenced message.
Invalid function code of '&1' encountered as input to DI function.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Invalid data type of '&1' returned from DBM.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Query uses too many columns.
&V1. is the number of columns being selected or inserted which exceeds &V2., the maximum number of columns allowed from any table or set of tables in a single query.
Rewrite the query to use fewer columns. If the query is in SQL, check statements like "SELECT * FROM A, B, C", which selects every column from each of tables A, B, and C.
See DSQ10012
Follow the directions in the referenced message.
Unexpected failure on 'DESCRIBE'.
This is a system error. Please see your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Free storage failed.
Follow the directions in the referenced message.
DESCRIBEd statement is not a 'SELECT'.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Free storage failed.
Follow the directions in the referenced message.
See DSQ10012
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
Column name '&V1.' is over 18 characters long.
Column name '&V1.' is over 18 characters long. Currently, QMF only supports up to 18 characters column name.
Specify a shorter column name and continue to use QMF.
Invalid data type of '&1' encountered.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
See DSQ10012
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
See DSQ10012
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
Invalid function code '&1' passed to module.
Follow the directions in the referenced message.
OK, the &1 command was cancelled at your request.
Type '&1' invalid in Q.OBJECT_DIRECTORY row '&2'.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
An object named on your &V1 command can't be processed.
Your &V1 command uses &V2..&V3 as the name of an object in the database. A &V4 object with this name exists in the database, but has a subtype &V5 which cannot be processed by QMF.
Change the name on your &V1 command to the name of an object QMF can process and give your command again. If you entered this command from the LIST panel, be sure that your command was formatted correctly. Refer to help behind the LIST panel for details on entering QMF commands from that panel.
An object named on your &V1 command can't be processed.
Your &V1 command uses &V2..&V3 as the name of an object in the database. A &V4 object with this name exists in the database, but has a version level &V5 which cannot be processed by QMF.
Change the name on your &V1 command to the name of an object QMF can process and give your command again. If you entered this command from the LIST panel, be sure that your command was formatted correctly. Refer to help behind the LIST panel for details on entering QMF commands from that panel.
Invalid function code '&1' passed to module.
Follow the directions in the referenced message.
See DSQ10013
Follow the directions in the referenced message.
Cannot use location in QMF query, procedure, or form names.
QMF objects must be stored in the local database. Location as part of a query, procedure, or form name is not allowed. A QMF query, procedure, or form name has the following format:
authid.objectname
Remove the location qualifier "&V1" from the name and retry the command.
See DSQ10012
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
Model '&1' invalid in Q.OBJECT_DIRECTORY row '&2'.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
See DSQ10012
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
Invalid function code '&1' passed to module.
Follow the directions in the referenced message.
View &V1. does not exist.
You requested information that causes QMF to select from the view specified by global variable &V2.. That view, &V1., was not found in the database. If your database supports 3-part names and a location qualifier was added to the name of the view, the location qualifier that was used follows: &V3.
Make sure that &V1. is the correct name. If it is not, change global variable &V2. to specify the correct name. If the name is correct, contact your QMF administrator for further information.
Note: If the view name is Q.DSQEC_QMFOBJS, then there is no global variable that can be set to specify a different view name. Q.DSQEC_QMFOBJS must be recreated. If this is the case, contact your QMF administrator for further information.
The definition of view &V2. is not valid.
You requested information that causes QMF to select from the view named in global variable &V1.. The definition of that view is not valid, probably because it contains a SELECT DISTINCT clause and there are more columns in the view than expected by QMF.
If your definition of a list view contains a SELECT DISTINCT clause, then your definition must contain only the columns specified for this view in Installing and Managing QMF for your operating system.
Make sure that &V2. is the correct name. If it is not, change global variable &V1. to specify the correct name. If the name is correct, contact your QMF administrator for further information.
The location qualifier cannot be used.
The name you specified has a location qualifier. A three-part object name cannot be used until the local location name is defined.
Remove the location qualifier and retry your command. See your QMF administrator to make sure you are using the correct database, or to define the local location name.
&V2 is not a valid location name.
One of the following has occurred:
Correct the location name and try again.
Error executing LIST command. SQLCA is: &1.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Column &V4. is not found in view &V2..
You requested information that causes QMF to select from the view named in global variable &V1.. The specified view, &V2., must be defined with the required column &V4..
If your database supports 3-part names and a location qualifier was added to the name of the view, the location qualifier that was used follows: &V3.
Recreate view &V2., defining the &V4. column as required.
One or more rows selected for object information are too long.
You requested information that causes QMF to select from one or more of the views named in the global variables that control where QMF gets object information (such as a list of names). QMF was unable to use that view to process your request. The view or views that were used to process your request are the following: &V1. &V2. &V3.. The global variable or variables that were used to get the view names are the following: &V4. &V5. &V6..
The most likely cause of this problem is that the view is defined as SELECT DISTINCT, and at least one row that QMF is trying to retrieve contains data that is too long for the database to sort in processing the SELECT DISTINCT.
Make sure that the view names in your global variables are correct. If they are, contact your QMF administrator for further information. Information about creating alternative views for retrieving object details can be found in the Installing and Managing QMF for your operating system.
A view column is defined incorrectly.
You requested information that causes QMF to select from one or more of the views named in the global variables that control where QMF gets object information (such as a list of names). Either the OWNER, TNAME, or CNAME column in one of those views is derived from a column function or expression; these columns must be derived from actual table columns.
The view or views that were used to process your request are the following: &V1. &V2. &V3.. The global variable or variables that were used to get the view names are the following: &V4. &V5. &V6..
If your database supports 3-part names and a location qualifier was added to the name of the view, the location qualifier that was used follows: &V7.
Make sure that the view names in your global variables are correct. If they are, contact your QMF administrator for further information. Information about creating alternative views for retrieving object details can be found in the Installing and Managing QMF for your operating system.
You are not authorized to use view &V1..
You requested information that causes QMF to select from the view specified by global variable &V2.. You must have the privilege to select from this view before it can be used to get the information you requested. If your database supports 3-part names and a location qualifier was added to the name of the view, the location qualifier that was used follows: &V3.
Make sure that &V1. is the correct name. If it is not, change global variable &V2. to specify the correct name. If the name is correct, contact your Information Center for further information.
See DSQ10166
Follow the directions in the referenced message.
Column &V3. in &V2. allows nulls.
You requested information that causes QMF to select from the view named in global variable &V1.. That view, &V2., contains a column named &V3., which is incorrectly defined. The column must be defined as NOT NULL before the view can be used to get the information you requested.
If your database supports 3-part names and a location qualifier was added to the name of the view, the location qualifier that was used follows: &V4.
Recreate view &V2., defining the &V3. column as NOT NULL.
Column &V3. of view &V2. is too long.
You requested information that causes QMF to select from the view named in global variable &V1.. That view, &V2., contains a column named &V3., which is too long. The column is defined with a length of &V4., but the maximum allowed length is &V5.. The column must be defined with a length of &V5. or less before the view can be used to get the information you requested.
If your database supports 3-part names and a location qualifier was added to the name of the view, the location qualifier that was used follows: &V6.
Recreate view &V2., defining the &V3. column as one with a length of &V5. or less.
&V3. in &V2. is not character data.
You requested information that causes QMF to select from the view named in global variable &V1.. That view, &V2., contains a column named &V3., which is incorrectly defined. The column must be defined as character data before the view can be used to get the information you requested.
If your database supports 3-part names and a location qualifier was added to the name of the view, the location qualifier that was used follows: &V4.
Recreate view &V2., defining the &V3. column as character data.
Free storage failed.
Follow the directions in the referenced message.
See DSQ10012
Follow the directions in the referenced message.
Invalid function code '&1' passed to module.
Follow the directions in the referenced message.
Part of the identifier in global variable &V1. is missing.
You requested information that causes QMF to select from the view named in global variable &V1.. The identifier &V2. specified in that global variable is missing a required part. For example,
SMITH.
is incomplete because a name is expected after the ".". If you intend this identifier to be a complete name, you must enclose it in double quotes (for example, "SMITH.").
Change the value of global variable &V1. so that it specifies a complete identifier.
The identifier in global variable &V1. can't start with ".".
You requested information that causes QMF to select from the view named in global variable &V1.. The identifier &V2. specified in that global variable starts with ".". The "." (period) character cannot be used as the first character of an unquoted name.
Remove the "." from the first character of the identifier in global variable &V1., or enclose the entire name in double quotes (for example, ".ABC").
The name in global variable &V1. has an unpaired double quote.
You requested information that causes QMF to select from the view named in global variable &V1.. The identifier &V2. specified in that global variable has a double quote at the start or end of a name, but does not have a matching end or start double quote. For example,
"MY*TABLE
is invalid because it has no end double quote.
Add a matching double quote to the name specified by global variable &V1..
The name in global variable &V1. has an embedded double quote.
You requested information that causes QMF to select from the view named in global variable &V1.. The identifier &V2. specified in that global variable contains an embedded double quote. Identifiers may not have an embedded double quote. For example, ABC"XYZ is invalid. Double quotes may be used to enclose a name. For example, the table name "MY*TABLE*" is valid.
Remove the embedded double quote from the name specified by global variable &V1..
Unexpected result &1 from package &2.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
The name in global variable &V1. must not have a location name.
You requested information that causes QMF to select from the view named in global variable &V1.. The identifier &V2. specified in that global variable has a location qualifier of &V3.. You must not specify a location qualifier as part of the view name, because QMF will automatically add a location qualifier, if needed, when using the view.
Change the value of global variable &V1. so that it does not include the location qualifier.
See DSQ10093
Follow the directions in the referenced message.
Invalid function code '&1' passed to module.
Follow the directions in the referenced message.
See DSQ10012
Follow the directions in the referenced message.
Invalid function code '&1' passed to module.
Follow the directions in the referenced message.
'&1'.'&2' not found in Q.OBJECT_DATA.
This is a system error. Please see your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Invalid function code '&1' passed to module.
Follow the directions in the referenced message.
Unexpected return code from RPT: &1.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Invalid function code '&1' passed to module.
Follow the directions in the referenced message.
Internal error due to insufficient parameters passed to DSQICONN.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Your startup location name length exceeded &V2 characters.
You supplied the location name, &V1, during QMF start up. However, location names at your installation cannot exceed &V2 characters.
QMF cannot start until you provide a valid startup location name.
Verify that the location name, &V1, is correct. If you do not want to process remote unit of work in QMF, omit the startup location name and restart QMF. Otherwise, contact your QMF administrator.
See DSQ10012
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
Location name is not supported in your current database.
You have supplied a location name when you started QMF. However, you cannot use the location name parameter because the connection to remote locations is not supported in your database.
QMF cannot start with the location name.
Remove the location name value in the location parameter and restart QMF. Otherwise, contact your QMF administrator.
Cannot use database; ATTACH subtask error.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Cannot use database; RC = &1.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Cannot use QMF: the database manager program is not active.
QMF operates only with a database manager program. The database manager program, "&V1", is not running now.
Call your QMF administrator to get the database manager program running.
Cannot use database; subsystem id=&1, reason=&2.
This is a system error. Please see your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Not authorized to use PLANID &V1 in the database.
The procedure you used to invoke QMF referred to the DB2 PLANID "&V1". You are not authorized to use that PLANID.
Check the invocation procedure. Perhaps you spelled the PLANID incorrectly.
You cannot use the local DB2: too many users are active.
The local DB2 subsystem cannot handle more users at the present time.
Wait until one or more active users log off before trying to use QMF.
Cannot use database; PLANID=&1, reason=&2.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Cannot discontinue use of database; RC=&1.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Invalid subsystem id SID &V1 in the current operating system.
The procedure you used to invoke QMF referred to the DB2 subsystem ID SID "&V1". The SID "&V1" is invalid in the current operating system.
Check the invocation procedure. Perhaps you spelled the SID incorrectly.
Invalid PLANID &V1 in the database.
The procedure you used to invoke QMF referred to the DB2 PLANID "&V1". PLANID "&V1" is invalid.
Check the invocation procedure. Perhaps you spelled the PLANID incorrectly.
Warning, release of call attachment facility does not match release of DB2.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Invalid input parameter has a value of '&1'.
Follow the directions in the referenced message.
Invalid function code '&1' passed to module.
Follow the directions in the referenced message.
DESCRIBEd statement is not a 'SELECT'.
Follow the directions in the referenced message.
Table has too many columns.
The table has &V1. columns which exceeds &V2., the maximum number of columns allowed.
Write and run a query that selects fewer columns than the maximum.
See DSQ10012
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
You are not authorized to select from Q.DSQ_RESERVED.
The QMF table Q.DSQ_RESERVED was not authorized to public during QMF installation. This table should be authorized to public.
Contact your QMF administrator for assistance.
The module &1 could not be loaded.
Follow the directions in the referenced message.
The module &1 could not be deleted.
Follow the directions in the referenced message.
You are not authorized to select from SYSTEM.SYSOPTIONS.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
SQLOPTION &1 is not defined in SYSTEM.SYSOPTIONS.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
SQLOPTION &1 in SYSTEM.SYSOPTIONS has wrong value &2.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
DB2 resource limit stopped QMF execution.
During QMF initialization, DB2 indicated that a resource limit was exceeded. QMF needed more time to execute a dynamic SQL statement.
Contact your QMF administrator to have the DB2 resource limit changed.
Invalid function code '&1' passed to module.
Follow the directions in the referenced message.
The database product (&V1) is not supported by QMF.
QMF has rejected an attempt to connect to a DRDA application server. The database product was identified as:
This release of QMF supports database product types of:
Verify the location name specified for the connection. Make corrections then retry the connection.
Contact your QMF Administrator for assistance in determining supported database product levels.
Errors detected while &1 EXEC was executed.
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
See DSQ10333
Follow the directions in the referenced message.
OK, the &1 command was cancelled at your request.
Only tables, views, and aliases have been listed.
You used the LOCATION option with your list request. Location names cannot be used to refer to QMF objects (queries, procedures, and forms), therefore they are not included in your list. Your list includes any tables, views, or alias names found in the database.
If you would like to see a list of QMF objects, do not use a location name when requesting the list.
See DSQ10012
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
See DSQ10012
Follow the directions in the referenced message.
Invalid function code of '&1' encountered as input to DI function.
Follow the directions in the referenced message.
See DSQ10013
Follow the directions in the referenced message.
QMF objects cannot be listed when a location is specified.
You used a location name when requesting a list of QMF objects (queries, procedures, or forms). Location names cannot be used to refer to QMF objects. You can use only those QMF objects that are stored on your current database.
If you would like to see a list of QMF objects that are stored on your current database, do not specify a location name when requesting the list.
Type '&1' invalid in Q.OBJECT_DIRECTORY row '&2'.
Follow the directions in the referenced message.
Invalid function code of '&1' encountered as input to DI function.
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
See DSQ10012
Follow the directions in the referenced message.
The module &1 could not be loaded.
Follow the directions in the referenced message.
The module &1 could not be deleted.
Follow the directions in the referenced message.
Buffer too small to contain SQL statement.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Invalid function code '&1' passed to module.
Follow the directions in the referenced message.
Unavailable resources at location &V5..
System resources were unavailable when your remote request was processed at location &V5. You are still connected to the current location.
Refer to the DB2 Messages and Codes manual for a detailed explanation of this error.
You may continue to use QMF. If the problem persists, contact your QMF administrator.
Your connection to &V5 was lost due to unavailable resources.
Your connection to location &V5 was lost because certain system resources were unavailable when your remote request was processed at location &V5.
Refer to the DB2 Messages and Codes manual for a detailed explanation of this error.
QMF attempted to reconnect you to the current location, If the attempt succeeds, you may continue to use QMF. If not, the Lost Connection Prompt panel prompts you to connect to another location, or to exit QMF.
If QMF successfully reconnects you to the current location, you can continue to use QMF.
If the Lost Connection Prompt panel is displayed, you can choose to connect to another location. If you cannot connect to a location, exit QMF and contact your QMF administrator.
If the problem persists, contact your QMF administrator.
SQLCODE: -30041 Database: DB2 QMF Function: All
You are not authorized to access the specified location.
Your attempt to access the specified location failed because your userid does not have sufficient authority. The SQLCODE is &V9..
Your connection to the current location was lost because of this error. QMF attempted to reconnect you to the current location. If the reconnect attempt fails, the Lost Connection Prompt panel prompts you to connect to another location or to exit QMF.
If QMF successfully reconnects you to the current location, you may continue to use QMF.
If the Lost Connection Prompt panel is displayed, you can choose to connect to another location. If you cannot connect to a location, exit QMF and contact your QMF administrator.
SQLCODE: -30060 Database: DB2 QMF Function: All
The specified location was not found.
Your attempt to access the specified location failed because the location could not be found. This may happen because the specified location is remote and it was defined incorrectly in the local DB2 subsystem. The SQLCODE is &V9..
Your connection to the current location was lost because of this error. QMF attempted to reconnect you to the current location. If the reconnect attempt fails, the Lost Connection Prompt panel prompts you to connect to another location, or to exit QMF.
If QMF successfully reconnects you to the current location, you can continue to use QMF.
If the Lost Connection Prompt panel is displayed, you can choose to connect to another location. If you cannot connect to a location, exit QMF and contact your QMF administrator.
If the specified location is incorrectly defined in your local DB2 subsystem, contact your QMF administrator.
SQLCODE: -30061 Database: DB2 QMF Function: All
A communication error has been detected.
Refer to the DB2 Messages and Codes manual for a detailed explanation of this error.
The SQLCA is: &V1..
This error may occur because your database system does not support a connection to the specified target location.
Or, this error may occur when the application server is SQL/DS and the "FORCE WITHOUT DISABLE" command was issued while a connection was routed via AVS or TSAF.
Because of this error, your connection was lost. QMF attempted to connect you to the location you were connected to before the error was detected. If the reconnect attempt fails, you will see the Lost Connection Prompt panel.
If QMF successfully reconnected you to the previous location, you can continue to use QMF.
If the Lost Connection Prompt panel is displayed, you can choose to connect to another location, or to exit QMF. If you cannot establish connection to a location, exit QMF and consult your QMF administrator.
If the problem persists, provide your QMF administrator with the SQLCA data.
SQLCODE: -30080 Database: DB2 QMF Function: All
Remote update is disallowed in a READ-ONLY environment.
You have attempted to update, insert or delete data at a remote location, but your current operating environment allows remote read only. For example, you cannot update remote data in a CICS operating environment if server database does not support 2-phase commit.
To access remote data in a READ-ONLY operating environment, you can use one of the following:
You can continue to use QMF. If you need to update remote data, switch to an operating environment that supports it; otherwise, contact your QMF administrator.
SQLCODE: -30090 Database: DB2 QMF Function: All
The server does not support DDM parameter &V1..
Your attempt to connect to a remote server failed because that server does not support the Distributed Data Management (DDM) command parameter value, &V1..
The SQLCODE is &V9..
A possible cause for this error:
Verify that your QMF command is correct. If it is correct, contact your QMF administrator for assistance. Refer to the Messages and Codes manual of the currently connected server for a detailed explanation on this error.
SQLCODE: -30073 Database: DB2 QMF Function: All
A communications error was detected.
A communications error was detected while communicating with a remote client or server. The following data was returned:
The return code values are documented in Assembler Callable Services for OpenEdition MVS.
Consult with a communications expert to determine the cause of the failure.
SQLCODE: -30081 Database: DB2 QMF Function: All
Unavailable resources at location &V1..
System resources were unavailable when your remote request was processed at location &V1. However, you are still connected to the current location.
Refer to the SQL/DS Messages and Codes manual for a detailed explanation.
You can continue to use QMF. If this problem persists, contact your QMF administrator.
Your connection to &V1 was lost due to unavailable resources.
Your connection to &V1 was lost because system resources were unavailable when your remote request was processed at location &V1.
Refer to the SQL/DS Messages and Codes manual for a detailed explanation of this error.
QMF attempted to reconnect you to the current location. If the attempt succeeds, you can continue to use QMF. If not, the Lost Connection Prompt panel prompts you to connect to another location, or to exit QMF.
If QMF successfully reconnects you to the current location, you can continue to use QMF at location &V1..
If the Lost Connection Prompt panel is displayed, you can choose to connect to another location. If you cannot connect to a location, exit QMF and contact your QMF administrator.
If the problem persists, contact your QMF administrator.
SQLCODE: -30041 Database: SQL/DS QMF Function: All
You are not authorized to access the location &V1..
Your attempt to access the location &V1 was unsuccessful because your userid does not have sufficient authority to access that location. The SQLCODE is &V9..
Your connection to the current location was lost because of this error. QMF attempted to reconnect you to the current location. If the reconnect attempt fails, the Lost Connection Prompt panel prompts you to connect to another location, or to exit QMF.
If you issued a CONNECT command specifying both a userid and a location name, you should have explicit connect authority at the target location.
If QMF successfully reconnects you to the current location and using your default userid at location &V1 is sufficient, you can issue a "CONNECT TO &V1" command. The implicit connect provided by the database allows you to access &V1 with the default userid.
If you are prompted to reconnect and using the default user ID at location &V1 is sufficient, enter &V1 for the location value and leave userID and password blank. If you cannot connect to location &V1, specify a different location.
If you must use a userid other than your default at &V1., exit QMF and obtain the explicit connect authority at location &V1 through your QMF administrator.
SQLCODE: -30060 Database: SQL/DS QMF Function: All
The specified location name was not found.
Your attempt to access the specified location was unsuccessful because that location could not be found. This may happen because the specified location is a remote location and it was defined incorrectly in the SQL/DS database. The SQLCODE is &V9..
Your connection to the current location was lost because of this error. QMF attempted to reconnect you to the current location. If the attempt is unsuccessful, the Lost Connection Prompt panel prompts you to connect to another location, or to exit QMF.
If the specified location name is defined in your user communications directory, verify if the entry for the specified location is defined correctly. If not, correct it and try again.
If QMF successfully reconnects you to the current location, you can continue to use QMF.
If the Lost Connection Prompt panel is displayed, you can choose to connect to another location. If you cannot connect to a location, exit QMF and contact your QMF administrator.
Contact your QMF administrator to define the location &V1 correctly in your default SQL/DS database.
SQLCODE: -30061 Database: SQL/DS QMF Function: All
A communication error has been detected.
Refer to the SQL/DS Messages and Codes manual for a detailed explanation of this error.
The SQLCA is: &V1..
This error may occur for the following reasons:
Because of this error, your connection was lost.
QMF attempted to connect you to the location you were connected to before the error was detected. If the reconnect attempt failed, you will see the Lost Connection Prompt panel.
If QMF successfully reconnected you to the previous location, you can continue to use QMF.
If the Lost Connection Prompt panel is displayed, you can choose to connect to another location, or to exit QMF. If you cannot connect to a location, exit QMF and consult your QMF administrator.
If you have issued a CONNECT command and have an old password in the user communications directories, update the password and reload the communications directories.
If the problem persists, provide your QMF administrator with the SQLCA data.
SQLCODE: -30080 Database: SQL/DS QMF Function: All
Remote update is disallowed in a READ-ONLY environment.
You have attempted to update, insert or delete data at a remote location, but your current operating environment allows remote read only. For example, you cannot update remote data in a CICS operating environment if server database does not support two-phase commit.
To access remote data in a READ-ONLY operating environment, you can use one of the following:
You can continue to use QMF. If you need to update remote data, switch to an operating environment that supports it; otherwise, contact your QMF administrator.
SQLCODE: -30090 Database: SQL/DS QMF Function: All
The server does not support DDM parameter &V1..
Your attempt to connect to a remote server failed because that server does not support the Distributed Data Management (DDM) command parameter value, &V1..
The SQLCODE is &V9..
A possible cause for this error:
Verify that your QMF command is correct. If it is correct, contact your QMF administrator for assistance. Refer to the Messages and Codes manual of the currently connected server for a detailed explanation on this error.
SQLCODE: -30073 Database: SQL/DS QMF Function: All
System problem in FP function. FPCODE = &1.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Sorry, a system error occurred. Your command may not have been executed.
&DSQSMSG1
The computer has detected an internal error. Error information is recorded in the table Q.ERROR_LOG and QMF trace data.
Report the error in accordance with your installation's procedures. See Installing and Managing QMF for your operating system for help in interpreting the error information in Q.ERROR_LOG and QMF trace data. Also, check to see if your command executed correctly. You may continue to use QMF.
SQLCODE: -00922 Database: N/A QMF Function: Special
Sorry, a system error occurred. Your command may not have been executed.
&DSQSMSG1
The computer has detected an internal error. Error information is recorded in the table Q.ERROR_LOG and QMF trace data.
Report the error in accordance with your installation's procedures. See Installing and Managing QMF for your operating system for help in interpreting the error information in Q.ERROR_LOG and QMF trace data. Also, check to see if your command executed correctly. You may continue to use QMF.
SQLCODE: -00923 Database: N/A QMF Function: Special
OK, command canceled.
SQLCODE: -00999 Database: N/A QMF Function: Special
Non end-user SQLCODE returned from DBM. SQLCA is as follows: &1
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Sorry, a system error occurred. Your command may not have been executed.
&DSQSMSG1
The computer has detected an internal error. Error information is recorded in the table Q.ERROR_LOG and QMF trace data.
Report the error in accordance with your installation's procedures. See Installing and Managing QMF for your operating system for help in interpreting the error information in Q.ERROR_LOG and QMF trace data. Also, check to see if your command executed correctly. You may continue to use QMF.
SQLCODE: -00902 Database: N/A QMF Function: Special
Your query is too long or too complex.
The QBE query results in a SQL statement that is too long or too complex to be interpreted. It can be simplified by reducing the number of :
Shorten your query or rewrite it as more than one query. Consider writing a query that produces a table of intermediate results. Save that table, and write a second query that uses it to produce your final result.
SQLCODE: -00101 Database: SQL/DS QMF Function: QBE
&V1 starts with a digit, but is not a valid number.
&V1 starts with a digit, but is not a valid integer, decimal, or floating-point number. If it is meant to be a:
Change &V1 and run the query again.
SQLCODE: -00103 Database: SQL/DS QMF Function: QBE
A NULL, expression, or comparison in your query is invalid.
If your query uses NULL, make sure that it is used to the right of an =. Also make sure that it is not part of an expression, or a condition that contains an expression.
If your query uses I., and the I. row contains no links to other rows, make sure that only constants are used in the I. row.
If your query uses U., make sure that columns containing a U. do not contain a comparison.
Correct any invalid use of NULL, remove an expression from a row that has an I., or remove a comparison from a column that has a U. operator.
SQLCODE: -00105 Database: SQL/DS QMF Function: QBE
A row with D., I., or U. can't link to a row of the same table.
Any row containing a D., I., or U. cannot be linked to another row if both refer to the same table.
Remove the link and run the query again.
SQLCODE: -00118 Database: SQL/DS QMF Function: QBE
You cannot modify a column twice in the same query.
"Modify" includes insert (I.) and update (U.). For example, in the following invalid query, the column 'YEARS' cannot be modified more than once.
Incorrect:
* *
Q.STAFF | ID | YEARS | JOB | YEARS |
--------+------+-------+-------+-------|
I. | 400 | 7 | CLERK | 8 |Change the query and run it again.
SQLCODE: -00121 Database: SQL/DS QMF Function: QBE
An AO. or DO. is used in more than 16 columns.
No more than 16 columns can contain an AO. or DO. operator.
Reduce the number of columns that contain AO. or DO. to 16 or fewer.
SQLCODE: -00124 Database: SQL/DS QMF Function: QBE
More than one UNQ. or COUNT. reference to a row.
A row may contain no more than one UNQ. or CNT. reference. The following invalid query has a CNT. and a UNQ. reference to the row in the Q.STAFF table.
Invalid
Query:
Q.STAFF | DEPT | SALARY | YEARS |
--------+------+--------+-------|
| P.G. | _S | _Y |
| | CONDITIONS |
|----------+--------------------|
| P.CNT._S | AVG.UNQ._Y > 5 |Correct your query and run it again.
SQLCODE: -00127 Database: SQL/DS QMF Function: QBE
You used too many tables or columns in your query.
In your query, one of the following items exceeds the limits listed:
Table Names 15
Selected columns 255Correct your query to conform to the limits, then rerun it.
SQLCODE: -00129 Database: SQL/DS QMF Function: QBE
A LONG VARCHAR column is used incorrectly.
The following limitations apply to using a column of data type LONG VARCHAR or LONG VARGRAPHIC:
Either comply with the previously listed conditions for columns of data type LONG VARCHAR or LONG VARGRAPHIC, or remove the column, and rerun the query.
SQLCODE: -00134 Database: SQL/DS QMF Function: QBE
A LONG VARCHAR column is used incorrectly.
The following limitations apply to using a column of data type LONG VARCHAR or LONG VARGRAPHIC:
Either comply with the previously listed conditions for columns of data type LONG VARCHAR or LONG VARGRAPHIC, or remove the column, and rerun the query.
SQLCODE: -00135 Database: SQL/DS QMF Function: QBE
Insert or update value does not satisfy view definition.
WITH CHECK OPTION was used in the definition of the view whose data you are trying to change. All attempts to insert or update rows in the view are checked to make sure that the results will conform to the definition of the view. Some value in your query does not satisfy a condition in that definition.
Examine the definition of the view to determine why the change was rejected, and change the value in the query.
SQLCODE: -00141 Database: SQL/DS QMF Function: QBE
Your query attempts to modify data in a view.
You cannot use I., U., or D. with a view that ...
Write separate queries to modify the tables used to create the view.
SQLCODE: -00150 Database: SQL/DS QMF Function: QBE
Your query attempts to modify data in a view.
You cannot use I., U., or D. with a view that ...
Write separate queries to modify the tables used to create the view.
SQLCODE: -00151 Database: SQL/DS QMF Function: QBE
Invalid query of a view.
The operation violates one of these rules:
- data from more than one table.
- data selected using a SQL DISTINCT
or GROUP BY.Make your query valid according to the above.
SQLCODE: -00152 Database: SQL/DS QMF Function: QBE
Invalid query of a view.
The operation violates one of these rules:
- data from more than one table.
- data selected using a SQL DISTINCT
or GROUP BY.Make your query valid according to the above.
SQLCODE: -00154 Database: SQL/DS QMF Function: QBE
Query uses a view defined by grouping.
A view is defined by grouping if its definition uses GROUP BY or HAVING. Such a view may not be used in a query along with any other view or table.
Consider doing something like this:
SQLCODE: -00155 Database: SQL/DS QMF Function: QBE
Invalid definition or use of view.
This view was created using DISTINCT or GROUP-BY. You must conform to the following rules in order to use the view.
For example, if the view definition is as follows:
CREATE VIEW V1 (COLA,COLB) AS SELECT DISTINCT (COL1,COL2) FROM TABLEA
You must select both COLA and COLB from V1. Also, you could not use AVG(COLA) or other column functions.
Change the query and run it again.
SQLCODE: -00156 Database: SQL/DS QMF Function: QBE
A name in your query starts or ends with a blank.
Names must not begin or end with a blank. In the following invalid query, the name, " YEARS", is invalid because it contains a leading blank.
Invalid
Query:
Q.STAFF | NAME | " YEARS" |
--------+------+----------|
P. | | |Remove the leading or trailing blank from the name.
SQLCODE: -00165 Database: SQL/DS QMF Function: QBE
Invalid DBCS constant.
Your query included a "DBCS constant", a graphic literal that begins with G', N', or X' .
If you intended to use a character constant, enclose the entire constant in single quotes.
If you intended to use a DBCS constant, it should be in the following form:
G'<aabbcc>' or N'<aabbcc>'
The < and > stand for shift-out (so) and shift-in (si). There must be an even number of characters between si and so.
Change your query and run it again.
SQLCODE: -00166 Database: SQL/DS QMF Function: QBE
The datetime value has invalid syntax.
The string representation of a valid DATE has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIME has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIMESTAMP has the following format:
'yyyy-mm-dd-hh.mm.ss.nnnnnn'
Correct the syntax for the datetime value and run the query again.
SQLCODE: -00180 Database: SQL/DS QMF Function: QBE
The datetime value is not a valid value.
The string representation of a datetime value contains a value which is out of range. The proper ranges for datetime values are as follows:
Years - 1 to 9999 Months - 1 to 12 Days - 1 to 31 Hours - 0 to 24 Minutes - 0 to 59 Seconds - 0 to 59
Correct the datetime value and run the query again.
SQLCODE: -00181 Database: SQL/DS QMF Function: QBE
An arithmetic expression with a datetime value is invalid.
The specified arithmetic expression contains an improperly used datetime value or simple duration. Some correct examples are:
Q.PROJECT | STARTD | |
----------+--------+------------------|
| _D | P._D + 10102433. |Check datetime value and run the query again.
SQLCODE: -00182 Database: SQL/DS QMF Function: QBE
An arithmetic operation on a date or timestamp has a result that is invalid.
The result of an arithmetic operation is a date or timestamp that is not within the valid range. Valid dates are between 0001-01-01 and 9999-12-31.
Correct the datetime value and run the query again.
SQLCODE: -00183 Database: SQL/DS QMF Function: QBE
The date or time value cannot be formatted.
One of the following has occurred:
Either change your string representation of the date or time value to be one of the recognized formats, or contact your QMF administrator for assistance in making the local date or time routine available to the database.
SQLCODE: -00185 Database: SQL/DS QMF Function: QBE
The mixed data consists of improper DBCS data value.
The mixed data may have a missing X'OE' (shift-out) or X'OF' (shift-in) or half of a DBCS character.
Refer to the SQL/DS Messages and codes manual for a detailed explanation of this error with reason code &V1..
Verify that the referenced data values are correct. If not, make the necessary change and rerun the query.
SQLCODE: -00191 Database: SQL/DS QMF Function: QBE
The first argument of the &V1 scalar function cannot be of MIXED subtype.
You cannot use an expression of MIXED subtype as the first argument of the &V1 scalar function.
Correct your SQL statement and try again.
SQLCODE: -00192 Database: SQL/DS QMF Function: QBE
Column &V1 is not in the table named.
&V1 appears as a column name in an example table, but it is not a column in that table in the database.
Change the column name. Give the command "DRAW tablename" (where "tablename" is the name of the table) to get an example table with all the column names filled in correctly.
SQLCODE: -00202 Database: SQL/DS QMF Function: QBE
&V1..&V2 not in system catalog.
The object named in your statement cannot be found in the system catalog. The name may be misspelled or you may have the wrong qualifier (&V1).
Correct the name and run your query again.
SQLCODE: -00204 Database: SQL/DS QMF Function: QBE
Column name &V1 is not in table &V2..
You used column name &V1.. It was not found in table &V2.. You may have misspelled the name, or the table name may need to be qualified.
Verify that the column name and owner are correct and spelled correctly.
SQLCODE: -00205 Database: SQL/DS QMF Function: QBE
Invalid use of colon (:).
Your query uses a name preceded by a colon, as in "WHERE NAME = :NAME (That usage has a meaning in a query submitted to the preprocessor program, but not in a query in QMF.)
Correct your query. Use names of tables, columns, or views, or else character constants enclosed in single quotes.
SQLCODE: -00312 Database: SQL/DS QMF Function: QBE
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00313 Database: SQL/DS QMF Function: QBE
One or more characters could not be converted into a usable code for the current server.
Your SQL statement referenced a character string, which must be converted to a code suitable for the application server. However, due to a mismatch in data representation, this was not possible. The character string is incompatible with the corresponding column data type. Consequently, you cannot use the character string as specified.
Verify that the character columns and values you referenced are correct. If not, make the necessary change and try the query again. Otherwise, contact your QMF administrator.
SQLCODE: -00330 Database: SQL/DS QMF Function: QBE
A character string could not be converted due to incompatible CCSIDs.
Your SQL statement referenced a character string that has a coded character set ID(CCSID) &V1 in a coded character set that differs from the current one. To use this character string at the current server, it must be converted from the source CCSID &V1 to the target CCSID &V2. However, this pair of CCSIDs conversion rule is not defined in the SYSSTRINGS system table. Therefore, the database system could not convert the character string to a code suitable for the application server.
Refer to the SQL/DS Messages and codes manual for a detailed explanation of this error with reason code &V3. Possible causes for this conversion error are:
Verify that the referenced character columns and values that you referenced are correct. If not, make the necessary change and rerun the query again. Otherwise, contact your QMF administrator.
SQLCODE: -00332 Database: SQL/DS QMF Function: QBE
Invalid data type in position &V1..
Some SQL data types are not supported by the application requester. &V1 is the position of the first element with an invalid data type in the SQLDA. A common cause for this error is that the application requester has attempted to describe large object data residing at the application server. Some of the SQLTYPEs that can cause this error are: LOB, BLOB, CLOB, and DBLOB.
Remove the invalid data types and run the query again.
SQLCODE: -00351 Database: SQL/DS QMF Function: QBE
Data of different types must not be used in an expression or condition.
You used data of different types in an expression or condition. For example, the following is not valid because character data (SMITH) is compared to numeric data (_SALARY):
Invalid _SALARY = SMITH Example:
Change any expression or condition so that data of the same type is used.
SQLCODE: -00401 Database: SQL/DS QMF Function: QBE
An arithmetic expression contains character data.
Arithmetic expressions, and expressions using the built-in functions AVG and SUM, may use only numeric data. Some expression in your query uses character data.
Rewrite the expression, using only numeric data, and run your query again.
SQLCODE: -00402 Database: SQL/DS QMF Function: QBE
Some character value is too long for the corresponding column.
One of the values you are trying to insert is longer than the width of the column you want to insert it into.
Change the value to fit the column and run the query again.
SQLCODE: -00404 Database: SQL/DS QMF Function: QBE
Numeric value is outside allowable range for column.
Your query specifies a column that has an incorrect numeric value. The value might be the result of an expression.
The proper ranges for SQL values are as follows:
FLOAT ...... -7.2E75 to -5.4E-79, 0,
5.4E-79 to 7.2E75
INTEGER .... -2147483648 to 2147483647
SMALLINT ... -32768 to 32767
DECIMAL .... The range depends on the
precision and scale of
the column. For example,
if the value is being
specified for a decimal
column defined with
precision = 5 and
scale = 2, the range is
-999.99 to 999.99.Change the numeric value for the column and rerun your query.
SQLCODE: -00405 Database: SQL/DS QMF Function: QBE
Numeric value is outside allowable range for column.
Your query specifies a column that has an incorrect numeric value. The value might be the result of an expression.
The proper ranges for SQL values are as follows:
FLOAT ...... -7.2E75 to -5.4E-79, 0,
5.4E-79 to 7.2E75
INTEGER .... -2147483648 to 2147483647
SMALLINT ... -32768 to 32767
DECIMAL .... The range depends on the
precision and scale of
the column. For example,
if the value is being
specified for a decimal
column defined with
precision = 5 and
scale = 2, the range is
-999.99 to 999.99.Change the numeric value for the column and rerun your query.
SQLCODE: -00406 Database: SQL/DS QMF Function: QBE
A column defined as NOT NULL may not contain a NULL.
Your query uses I. or U. in an attempt to enter a NULL into a column that is designated as NOT NULL. The following query attempts to insert a NULL into ID, but ID is defined as a NOT NULL column. Note that in an I. row, NULL is entered for
Q.STAFF | ID | NAME | DEPT |
-------+----+------------+-------|
I. | | 'J.Harris' | |
| YEARS |
|-------|
| NULL |Specify a value for the NOT NULL column.
SQLCODE: -00407 Database: SQL/DS QMF Function: QBE
An update or insert value is incompatible with the data type of its associated column.
Your query attempts to insert or update a column with a value from another column that is incompatible. The following invalid query attempts to insert into a numeric column (ID) a value from a character column (NAME).
Invalid
Query:
MYSTAFF | ID | NAME |
--------+----------+----------|
I. | _N | _N |
Q.STAFF | ID | NAME |
--------+----------+----------|
| _I | _N |Use a compatible value.
SQLCODE: -00408 Database: SQL/DS QMF Function: QBE
&V1 is not a valid numeric value.
Your query tried to assign &V1 to a numeric field. What it tried to assign is either a floating point constant of 31 characters or more, or a value containing non-numeric characters.
Change &V1 and run your query again.
SQLCODE: -00410 Database: SQL/DS QMF Function: QBE
Invalid use of "USER". USER was used in an expression, compared to numeric data, or not used in a condition.
USER may be used only in a condition. Additionally, it may not be compared to numeric data. The following is an example of a valid use of USER.
Q.STAFF | NAME | SALARY | COMM | YEARS | ---------+-------+--------+------+-------| P. | USER | | | |
Correct the use of USER in your query.
SQLCODE: -00411 Database: SQL/DS QMF Function: QBE
Arithmetic overflow during change of data type.
The result of an arithmetic or insert operation is not valid because arithmetic overflow occurred. For example, you may have tried to INSERT values with a data type of INTEGER into a column with data type of SMALLINT. Conversion is possible so long as the INTEGER values are small enough. But a value larger than 32767 will cause arithmetic overflow.
Change your operation and run the query again.
SQLCODE: -00413 Database: SQL/DS QMF Function: QBE
A LIKE operator in your query does not refer to character data or graphic data.
The LIKE operator may only be used with a column that has character data or graphic data. Your query uses a LIKE to refer to a column that does not have character or graphic data. For example,
Invalid Q.STAFF | NAME | SALARY |
Query: --------+------+-----------|
P. | | LIKE'20%' |Remove the LIKE reference to numeric data or datetime data and run the query again.
SQLCODE: -00414 Database: SQL/DS QMF Function: QBE
Data to be retrieved into the same column of two separate P. rows must have comparable definitions.
Your query contains 2 or more P. rows with data definitions that cannot be compared. This query unsuccessfully attempted to retrieve data into the same column. The data definitions for these P. rows must be comparable for the retrieval to succeed. Additionally, the columns to be retrieved into the same output column must have the same field procedure and column CCSID value, provided the columns to be retrieved have field procedures.
The following query attempts to retrieve NUMERIC data (DEPT) and LONG VARCHAR data (JOB) into the same column.
Invalid
Query:
Q.staff | DEPT | | JOB |
---------+---------+--------+---------|
| _D | P. _D | |
| | P. _J | _J |
Ensure that data retrieved into the same column have comparable definitions.
SQLCODE: -00415 Database: SQL/DS QMF Function: QBE
Data to be retrieved into the same column by two different P. rows must not refer to long variable character data.
Your query attempts to retrieve data into the same column from 2 sources, but at least one of those sources is data defined as long variable character data. The following is an example of such an invalid query.
Invalid MYTABLE | LONGVARCHAR1 |
Query: --------+--------------|
P. | |
P. | _L2 |
YOURTABLE | LONGVARCHAR2 |
----------+--------------|
| _L2 |
Remove the reference in the same column to long variable character data.
SQLCODE: -00416 Database: SQL/DS QMF Function: QBE
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00417 Database: SQL/DS QMF Function: QBE
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00418 Database: SQL/DS QMF Function: QBE
Decimal division is not possible with the values used.
Either the precision of the numerator or the scale of the denominator is too large for decimal division.
Change the precision or scale of your decimal division values and run the query again. Note that an integer or small integer value may have been converted to decimal for this calculation.
SQLCODE: -00419 Database: SQL/DS QMF Function: QBE
The foreign key value is not valid.
An update or insert query specified a value for a foreign key. However, the value is not equal to any of the primary key values of the parent table.
If the name of the referential constraint for the foreign key was provided by the database, that name is as follows: &V1..&V2..
Use a value for the foreign key that matches one of the primary key values.
SQLCODE: -00530 Database: SQL/DS QMF Function: QBE
The row cannot be updated or deleted because of a dependent row.
The attempt to update or delete a parent row failed, because the parent row has a dependent row or cascades to a dependent row that has been restricted using the RESTRICT rule.
If the name of the referential constraint for the foreign key was provided by the database, that name is as follows: &V1..&V2..
Make sure you selected the correct row. If you did, update or delete the dependent rows for which RESTRICT was specified. Then update or delete the parent row.
SQLCODE: -00532 Database: SQL/DS QMF Function: QBE
Cannot update a primary key or unique constraint in multiple rows.
You cannot use U. to update a primary key or unique constraint in more than one row at a time.
Make sure the update request selects no more than one row of data.
SQLCODE: -00534 Database: SQL/DS QMF Function: QBE
The deletion is invalid because table &V1..&V2 can be affected.
You cannot use D. to delete from a table based on values in table &V1..&V2, because table &V1..&V2 can be affected by the deletion.
Do not attempt to delete from a table based on values in a table that can be affected.
SQLCODE: -00536 Database: SQL/DS QMF Function: QBE
You lack the authorization necessary to run your query.
Your QBE query uses one of the operators listed below, and requires the corresponding authorization on the appropriate tables.
D. -- DELETE I. -- INSERT P. -- SELECT U. -- UPDATE
See your QMF administrator to obtain the proper authorization for your query.
SQLCODE: -00551 Database: SQL/DS QMF Function: QBE
You lack the authorization necessary to run your query.
Your QBE query uses one of the operators listed below, and requires the corresponding authorization on the appropriate tables.
D. -- DELETE I. -- INSERT P. -- SELECT U. -- UPDATE
See your QMF administrator to obtain the proper authorization for your query.
SQLCODE: -00552 Database: SQL/DS QMF Function: QBE
You cannot use the database without CONNECT authority.
In order to use the database, you need CONNECT authority. If you have already used the database during this session, another user may have revoked your CONNECT authority while you were running.
Report your problem to your QMF administrator.
SQLCODE: -00561 Database: SQL/DS QMF Function: QBE
Graphic and Mixed data types are not supported by the current server.
Your SQL statement referenced the clause or scalar function, &V1, and the current server does not support it.
This may happen because:
Issue the SQL statement on a server that supports Mixed, Graphic and Vargraphic data types. If you use these data types at the current server, contact your QMF administrator to reset the system default CCSIDs.
SQLCODE: -00640 Database: SQL/DS QMF Function: QBE
Table &V1..&V2 cannot be accessed. &V3 &V4 is inactive.
No operation can be performed on table &V1..&V2 because the &V3 &V4 is inactive.
Try again when the key has been activated.
SQLCODE: -00668 Database: SQL/DS QMF Function: QBE
Invalid comparison with a column defined with a field procedure.
The value that is compared to a column defined with a field procedure does not have the same field type. The comparison is performed on the encoded form of the value in the column. For example, if the encoded value of the column is INTEGER, the data type of the value being compared must be identical. If they are strings, their data types must be compatible.
Correct the SQL statement and run the query again.
SQLCODE: -00687 Database: SQL/DS QMF Function: QBE
Space allocated for data in your DBSPACE is full.
Your query will not run because there is not enough space for data in your DBSPACE.
If you are creating a table, specify a different DBSPACE. Otherwise, contact your QMF administrator for procedures to provide more data space and run the query again.
SQLCODE: -00701 Database: SQL/DS QMF Function: QBE
Space assigned for indexes in your DBSPACE is full.
Your query cannot be processed until more DBSPACE is added for indexes.
If you are creating a table, specify a different DBSPACE. Otherwise, contact your QMF administrator for procedures to provide more index space and run the query again.
SQLCODE: -00702 Database: SQL/DS QMF Function: QBE
Space for header information in your DBSPACE is full.
The space allocated in your DBSPACE by the parameter NHEADER for header information is full. Your query cannot be processed unless additional DBSPACE space is obtained.
If you are creating a table, specify a different DBSPACE. Otherwise, contact your QMF administrator for procedures to provide more header space and run the query again.
SQLCODE: -00703 Database: SQL/DS QMF Function: QBE
The PRIVATE DBSPACE needed by your query is in use.
A PRIVATE DBSPACE can be accessed by only one user at any time. The table you requested in your query is in a PRIVATE DBSPACE now in use.
Run your query again when the PRIVATE DBSPACE is available.
SQLCODE: -00710 Database: SQL/DS QMF Function: QBE
There is not enough room in INTERNAL DBSPACEs to run the query.
QMF was not able to acquire sufficiently many, or sufficiently large, INTERNAL DBSPACEs. You may be able to simplify your query or break it up into two queries or more.
Ask your QMF administrator to acquire more INTERNAL DBSPACE for QMF.
SQLCODE: -00712 Database: SQL/DS QMF Function: QBE
An arithmetic operation in the SQL statement has resulted in an error.
You are trying to use a view, but an arithmetic operation in the subselect clause of the view definition has resulted in an error. The exception type is &V1, the operation type is &V2, and the data type is &V3.
Contact the owner of the view to examine the arithmetic operation and the columns within the subselect clause of the view to determine what data may be causing the program exception.
SQLCODE: -00801 Database: SQL/DS QMF Function: QBE
An Arithmetic operation in the SQL command has resulted in an error.
The SQL command attempted an Arithmetic operation such as Multiplication or Division. However, the computer detected that one or more of the values in the columns selected was invalid. For example: the result of multiplication exceeds internal computer storage or division-by-zero.
Examine the Arithmetic operation and the columns within the command to determine what data may be causing the program exception.
SQLCODE: -00802 Database: SQL/DS QMF Function: QBE
Duplicate value in a unique index column.
One of the columns into which you are inserting or updating a new value contains that same value already. That column is a 'Unique Index' column. Unique Index columns cannot have duplicate values.
Change the value so that it does not duplicate a value already existing. Run your query again.
SQLCODE: -00803 Database: SQL/DS QMF Function: QBE
The package &V1 is not found in the catalog table.
When SQL/DS tried to run the QMF program, it could not find the package in the catalog table SYSTEM.SYSACCESS. This can happen because:
Refer to the SQL/DS Messages and Codes manual for a detailed explanation and report this problem to your QMF administrator.
SQLCODE: -00805 Database: SQL/DS QMF Function: QBE
You do not have authorization to modify system catalogs.
You cannot modify system catalogs unless you have been granted authority. You may read the system catalogs and retrieve data using queries or DISPLAY commands.
Follow your QMF administrator procedures if authority is required.
SQLCODE: -00808 Database: SQL/DS QMF Function: QBE
You cannot perform this operation with a system catalog.
Your request specified a system catalog. Users cannot delete from a system catalog, add a primary or foreign key to a system catalog, or refer to a system catalog as a parent of a foreign key.
To drop the object "name1" from the database, give the command ERASE name1.
SQLCODE: -00823 Database: SQL/DS QMF Function: QBE
The portion of the database you require is in use.
The object you need in the database cannot be accessed until another user has completed processing.
End your QMF session and sign on again at a later time.
SQLCODE: -00911 Database: SQL/DS QMF Function: QBE
The portion of the database you require is in use.
The object you need in the database cannot be accessed until another user has completed processing.
End your QMF session and sign on again at a later time.
SQLCODE: -00912 Database: SQL/DS QMF Function: QBE
A CANCEL request has been issued.
The CANCEL could have been issued by the user or by the system. The CANCEL issued by the system is a result of reaching the limit on lock request blocks.
Redo your changes as necessary. If you did not issue the CANCEL request, and you continue to get SQLCODE -914, contact your system programmer about increasing the NLRBU or the NLRBS parameters when starting the application server.
SQLCODE: -00914 Database: SQL/DS QMF Function: QBE
Your query was not processed because of the system work load.
Your query cannot be processed now because of the work load on the database system.
Continue with another operation and try to run your query at a later time. Contact your QMF administrator for more details about the current system work load.
SQLCODE: -00915 Database: SQL/DS QMF Function: QBE
Your query was not processed because of operator action.
The system operator interrupted the processing of your query. This was not due to an error in the query.
Run the query again.
SQLCODE: -00916 Database: SQL/DS QMF Function: QBE
The database manager program ran out of storage.
The database manager program does not have enough virtual storage to run your query.
Try later when there is less activity on QMF. If the condition persists, inform your QMF administrator.
SQLCODE: -00930 Database: SQL/DS QMF Function: QBE
The communications path to &V1. is not available.
You cannot access database &V1. for one of the following reasons:
Verify that the database name, &V1., is correct. If not, use a correct database name and retry your request.
The limit on the number of connections allowed to the SQL/DS virtual machine is set by the MAXCONN value in the SQL/DS virtual machine directory. If this limit has been exceeded, try your request later when the system activity is lighter. If this condition occurs frequently, contact your QMF administrator to get the MAXCONN value increased.
If the "CONNECT TO <location>" command is supported, QMF may have reconnected you to the current location. If so, you can continue to use QMF. If QMF cannot reconnect you, the Lost Connection Prompt panel prompts you to connect to another location.
SQLCODE: -00933 Database: SQL/DS QMF Function: QBE
The database manager program ran out of storage.
The database manager program does not have enough virtual storage to run your query.
Try later when there is less activity on QMF. If the condition persists, inform your QMF administrator.
SQLCODE: -00939 Database: SQL/DS QMF Function: QBE
The database &V1 is not ready or cannot be found.
You cannot access the database for one of the following reasons:
Verify that the database name, &V1., is correct. If not, use a correct database name and retry your request.
If the "CONNECT TO <location>" command is supported, QMF may have reconnected you to the current location. If so, you can continue to use QMF. If QMF cannot reconnect you, the Lost Connection Prompt panel prompts you to connect to another location.
SQLCODE: -00940 Database: SQL/DS QMF Function: QBE
The database manager program ran out of storage.
The database manager program does not have enough virtual storage to run your query.
Try later when there is less activity on QMF. If the condition persists, inform your QMF administrator.
SQLCODE: -00942 Database: SQL/DS QMF Function: QBE
The QMF virtual machine, &V2, cannot access database &V1..
The QMF virtual machine is not properly defined. The file ARISRMBT MODULE, on the QMF machine's A-disk, does not describe the database program that QMF is attempting to access.
Tell your QMF administrator about this message and wait for their response. There is nothing you can do until the QMF virtual machine is properly defined.
SQLCODE: -00943 Database: SQL/DS QMF Function: QBE
Your connection to SQL/DS was severed because of operator action.
The SQL/DS virtual-machine operator entered the FORCE command to cause ROLLBACK of the current logical unit of work and to sever your connection to the SQL/DS system. The userid, password, and database name are reset to their default values.
You can continue. Any explicit CONNECTs you have issued have been lost. You must issue another explicit CONNECT request, using the same USER ID, to reestablish your original connection.
SQLCODE: -00948 Database: SQL/DS QMF Function: QBE
You cannot use this view.
Your command names a view whose definition has one of these errors:
Correct: SELECT DEPT, AVG(SALARY)
FROM Q.STAFF GROUP BY DEPTCorrect: SELECT DEPT, JOB, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT, JOB (Not: GROUP BY DEPT)
Correct: HAVING MIN(YEARS) > 6
(Not: HAVING YEARS > 6) Correct: SUM (UNITS * RATE)
(Not: SUM(UNITS) * RATE)Change the definition of the view and enter the command again.
SQLCODE: -00119 Database: SQL/DS QMF Function: Command
The table specified has too many columns.
In the specified table, the following item exceeds the limit.
Selected columns 255
Correct your command so that it conforms to the limit.
SQLCODE: -00129 Database: SQL/DS QMF Function: Command
Insert or update value does not satisfy view definition.
Your &V1 command attempted to insert or update a view that uses the "WITH CHECK OPTION" clause. All attempts to insert or update rows into this view are checked to ensure that the results conform to the view definition. A value that you attempted to insert or update does not satisfy that definition.
Examine the view definition to determine why the change was rejected. Then, change the value that your &V1 command attempted to process.
SQLCODE: -00141 Database: SQL/DS QMF Function: Command
You cannot modify the specified object.
The specified object is a view based on more than one table. INSERT, DELETE, or UPDATE of a view is not permitted if the VIEW is based on more than one table.
Verify that the table/view name you specified is correct.
SQLCODE: -00149 Database: SQL/DS QMF Function: Command
You cannot use &V1 with this view.
You cannot name a view in a command if executing the command would require QMF to...
- data from more than one table - a column defined by a built-in function (like SUM(COMM)) - data selected by DISTINCT or GROUP BY
Pick a new name for the data, give the command "SAVE DATA AS newname", and so create a new table.
SQLCODE: -00150 Database: SQL/DS QMF Function: Command
Column &V2 cannot be changed.
Your &V1 command cannot be executed with the replace option, because that changes a column in:
Choose a new name for the data to be saved, and so save it as a new table.
SQLCODE: -00151 Database: SQL/DS QMF Function: Command
You cannot use &V1 with this view.
You cannot name a view in a command if executing the command would require QMF to...
- data from more than one table - a column defined by a built-in function (like SUM(COMM)) - data selected by DISTINCT or GROUP BY
Pick a new name for the data, give the command "SAVE DATA AS newname", and so create a new table.
SQLCODE: -00154 Database: SQL/DS QMF Function: Command
A double-quoted name cannot start or end with a blank.
Your command contains a double-quoted name that begins or ends with a blank. Nothing in the database can have such a name.
This may be a typographical error. Make the correction and issue the command again. If you entered this command from the LIST panel, be sure that your command was formatted correctly. Press the HELP function key on the LIST panel for details on entering QMF commands from that panel.
SQLCODE: -00165 Database: SQL/DS QMF Function: Command
Your &V1 command referenced an invalid DATETIME value.
Your &V1 command referenced an invalid DATETIME value. This may happen if your command references a view which contains an invalid DATETIME value in the view definition. The string representation of a valid DATE has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIME has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIMESTAMP has the following format:
'yyyy-mm-dd-hh.mm.ss.nnnnnn'
If your &V1 command references a view, correct the syntax for the DATETIME value in the view definition and run the &V1 command again. Contact your QMF administrator for further help.
SQLCODE: -00180 Database: SQL/DS QMF Function: Command
&V2..&V3 cannot be found.
&V3 is not the name of anything in the database owned by &V2.. Possibly your &V1 command specified a synonym based on table &V2..&V3.. Such a table no longer exists in the database. Commands using synonyms based on this table cannot be executed.
Continue with another operation.
SQLCODE: -00204 Database: SQL/DS QMF Function: Command
Column name &V1 is not in table &V2..
You used column name &V1.. It was not found in table &V2.. You may have misspelled the name, or the table name may need to be qualified.
Verify that the column name and owner are correct and spelled correctly.
SQLCODE: -00205 Database: SQL/DS QMF Function: Command
One or more converted characters are not usable.
Your &V1 command referenced a character string which needs to be converted to a code suitable for the application server. However, due to a mismatch in data representation, this was not possible. The character string is incompatible with the corresponding column data type. Consequently, the character string could not be used as specified.
Verify that your command is correct. If not, make the necessary change and rerun the command. Otherwise, consult your QMF administrator.
SQLCODE: -00330 Database: SQL/DS QMF Function: Command
A character string could not be converted due to incompatible CCSIDs.
Your &V1 command referenced a character string that has a coded character set ID(CCSID) &V2 in a coded character set that differs from the current one. To use this character string at the current server, this character string must be converted from the source CCSID &V2 to the target CCSID &V3..
However, this pair of CCSIDs conversion rule is not defined in the SYSSTRINGS system table. Therefore, the database system could not convert the character string to a code suitable for the application server.
Refer to the SQL/DS Messages and codes manual for a detailed explanation of the error with reason code &V4..
Verify that your command is correct. If not, make the necessary changes and re-issue the command. Otherwise, contact your QMF administrator.
SQLCODE: -00332 Database: SQL/DS QMF Function: Command
Unsupported data type in position &V2..
Some SQL data types are not supported by the application requester. &V2 is the position of the first element with an unsupported data type in the SQLDA. A common cause for this error is that the application requester connected to an application server and has attempted to describe the data type residing at the application server. Some of the SQLTYPEs that can cause this error are: CLOB, BLOB and DBCLOB.
Remove the unsupported data types and run the query again.
SQLCODE: -00351 Database: SQL/DS QMF Function: Command
You cannot use &V1 with this view.
You cannot name a view in a command if executing the command would require QMF to:
- data from more than one table - a column defined by a built-in function (like SUM(COMM)) - data selected by DISTINCT or GROUP BY
Pick a new name for the data, give the command "SAVE DATA AS newname", and so create a new table.
SQLCODE: -00407 Database: SQL/DS QMF Function: Command
The foreign key value is not valid.
The table being replaced by your &V1 command has a foreign key. Your new data contains a value for the foreign key &V2..&V3. that is not equal to any of the primary key values of the parent table.
If the name of the referential constraint for the foreign key was provided by the database, that name is as follows: &V2..&V3..
You cannot replace the table with the new data. Consider saving your data as a new table.
SQLCODE: -00530 Database: SQL/DS QMF Function: Command
The table cannot be replaced because RESTRICT is specified.
The table you attempted to replace has a primary key defined. To replace the table, the existing rows, and with them the primary key, must be deleted. However, a value of the primary key cannot be deleted because RESTRICT was specified for one or more descendant tables.
Either save the data as a new table, or re-examine the constraint rules for all dependent tables.
SQLCODE: -00532 Database: SQL/DS QMF Function: Command
You cannot create something for the owner "SYSTEM".
For example, you cannot run a query that contains a statement like this:
Incorrect:
CREATE TABLE SYSTEM.NEWTABLE .....Nor give a command like this:
Incorrect:
SAVE DATA AS SYSTEM.NEWTABLEDo not attempt this operation.
SQLCODE: -00550 Database: SQL/DS QMF Function: Command
You lack the authorization needed for this &V1 command.
For DRAW, DISPLAY, EXPORT, or PRINT, you need SELECT authorization on the table or view named.
You can use ERASE only with tables or views you own.
To replace an existing table with SAVE or IMPORT, you need SELECT, DELETE and INSERT authorization.
To create a new table with SAVE or IMPORT, you need the authorization to create the table you named.
Contact your QMF administrator to obtain the proper authorization.
SQLCODE: -00551 Database: SQL/DS QMF Function: Command
You lack the authorization needed for this &V1 command.
For DRAW, DISPLAY, EXPORT, or PRINT, you need SELECT authorization on the table or view named.
You can use ERASE only with tables or views you own.
To replace an existing table with SAVE or IMPORT, you need SELECT, DELETE and INSERT authorization.
To create a new table with SAVE or IMPORT, you need the authorization to create the table you named.
Contact your QMF administrator to obtain the proper authorization.
SQLCODE: -00552 Database: SQL/DS QMF Function: Command
You cannot use the database without CONNECT authority.
In order to use the database, you need CONNECT authority.
If you have already used the database during this session, another user may have revoked your CONNECT authority while you were running.
If you were attempting to use the CONNECT command, the userid and/or the password specified were not valid.
If you were already using the database and used CONNECT to connect to a different ID, then you want to connect back to your original ID, you may not have the authority to explicitly connect to that user ID. When you started QMF using that user id, you were implicitly connected.
Report the problem to your QMF administrator.
SQLCODE: -00560 Database: SQL/DS QMF Function: Command
You cannot use the database without CONNECT authority.
In order to use the database, you need CONNECT authority.
If you have already used the database during this session, another user may have revoked your CONNECT authority while you were running.
If you were attempting to use the CONNECT command, the userid and/or the password specified were not valid.
If you were already using the database and used CONNECT to connect to a different ID, then you want to connect back to your original ID, you may not have the authority to explicitly connect to that user ID. When you started QMF using that user id, you were implicitly connected.
Report the problem to your QMF administrator.
SQLCODE: -00561 Database: SQL/DS QMF Function: Command
You cannot use the database without CONNECT authority.
In order to use the database, you need CONNECT authority.
If you have already used the database during this session, another user may have revoked your CONNECT authority while you were running.
If you were attempting to use the CONNECT command, the userid and/or the password specified were not valid.
If you were already using the database and used CONNECT to connect to a different ID, then you want to connect back to your original ID, you may not have the authority to explicitly connect to that user ID. When you started QMF using that user id, you were implicitly connected.
Report the problem to your QMF administrator.
SQLCODE: -00564 Database: SQL/DS QMF Function: Command
An object of the same name already exists.
The object you are creating or the DBSPACE space you want to acquire has a name that already exists.
Change the name to one that doesn't exist in the data base and run your query again.
SQLCODE: -00601 Database: SQL/DS QMF Function: Command
Data length, scale, or precision for some column is invalid.
The DATA you are attempting to SAVE or the TABLE you are attempting to IMPORT contains a data length, or a decimal scale or precision that is either zero or greater than the maximum supported by the database.
If you are trying to SAVE DATA, and the data you want to save was retrieved by running a query, then the query most likely selected a column with data length zero. Change the query so it does not select this column and re-run the query.
If you are trying to IMPORT a TABLE, or SAVE DATA that was previously imported, then the data most likely contains a decimal column with a precision larger than the maximum supported by the database. Change the data format to a precision within the database limits.
SQLCODE: -00604 Database: SQL/DS QMF Function: Command
You have no room to SAVE DATA.
The DBSPACE named in your PROFILE already has 255 tables.
Either enter a different DBSPACE in your PROFILE or ERASE a table to free space for an entry.
SQLCODE: -00607 Database: SQL/DS QMF Function: Command
There is no DBSPACE you can use for &V1..
One of the following is true:
Contact your QMF administrator to obtain the proper DBSPACE.
SQLCODE: -00608 Database: SQL/DS QMF Function: Command
You cannot &V1 a table in the SPACE named in your profile.
The SPACE named in your profile is owned by another user or by the system. You do not have the proper authority to &V1 a table in it.
Change the name of your table space by using the command SET (SPACE=tablespacename from a QMF object panel, or by changing the value of SPACE in your profile. Follow your local procedures to get authorization to use a tablespace owned by another.
SQLCODE: -00610 Database: SQL/DS QMF Function: Command
There is no private DBSPACE available for your table.
The SPACE value in your profile has been set to blank and you do not have a private DBSPACE. When you issued the &V1 command, it resulted in a CREATE TABLE statement and a search was done to find a private DBSPACE owned by &V2..
Either there were no DBSPACEs found, they were full, or they were located in non-recoverable storage pools.
Contact your QMF administrator to obtain a valid DBSPACE to use for the SPACE value in your profile or create your private DBSPACE.
SQLCODE: -00620 Database: SQL/DS QMF Function: Command
&V4 &V5 is inactive.
You cannot &V1 table &V2..&V3 because the &V4 &V5 is inactive.
Try again when the key has been activated.
SQLCODE: -00668 Database: SQL/DS QMF Function: Command
There is not enough DBSPACE space to perform &V1..
&V1 cannot be performed because there is not enough space available in the DBSPACE.
If you are saving a new table, specify a different DBSPACE in the SPACE option of your profile. The specified table should be ERASEd first since the table was created by the &V1 command, even though there was not enough space to insert the data.
If you are saving an existing table, erasing the table might cause existing authorizations, views, or indexes to be lost. If you wish to delete the existing table and use a larger DBSPACE, ERASE the table and modify the profile SPACE option as described above. Otherwise, see your QMF administrator for further information.
SQLCODE: -00701 Database: SQL/DS QMF Function: Command
Space assigned for indexes in your DBSPACE is full.
Your &V1 command cannot be executed until more space is added to your DBSPACE for indexes.
If you are saving a new table, specify a different DBSPACE in the SPACE option of your profile. Otherwise, contact your QMF administrator for procedures to add more index space to your DBSPACE and run the query again.
SQLCODE: -00702 Database: SQL/DS QMF Function: Command
Space assigned for header information in your DBSPACE is full.
The space assigned in your DBSPACE by the parameter NHEADER for header information is full. &V1 cannot be processed unless additional DBSPACE is obtained.
If you are saving a new table, specify a different DBSPACE in the SPACE option of your profile. Otherwise, contact your QMF administrator for procedures to provide more header space and run the query again.
SQLCODE: -00703 Database: SQL/DS QMF Function: Command
Requested private DBSPACE is in use.
The private DBSPACE needed by your command can be used by only one user at a time.
Give the &V1 command later, when the private DBSPACE is available.
SQLCODE: -00710 Database: SQL/DS QMF Function: Command
There is not enough room in INTERNAL DBSPACEs to perform &V1..
QMF was not able to acquire sufficiently many, or sufficiently large, INTERNAL DBSPACEs. If your command uses a view, you may be able to simplify it by revising the view.
Ask your QMF administrator to acquire more INTERNAL DBSPACE for QMF.
SQLCODE: -00712 Database: SQL/DS QMF Function: Command
An Arithmetic operation in the view definition has resulted in an error.
Your &V1 command refers to a view. An arithmetic operation in the subselect clause of the view definition has resulted in an error. The exception type is &V2, the operation type is &V3, and the data type is &V4.
Contact the owner of the view to examine the arithmetic operation and the columns within the subselect clause of the view to determine what data may be causing the program exception.
SQLCODE: -00801 Database: SQL/DS QMF Function: Command
An Arithmetic operation in the SQL command has resulted in an error.
The SQL command attempted an Arithmetic operation such as Multiplication or Division. However, the computer detected that one or more of the values in the columns selected was invalid. For example: the result of multiplication exceeds internal computer storage or division-by-zero.
Examine the Arithmetic operation and the columns within the command to determine what data may be causing the program exception.
SQLCODE: -00802 Database: SQL/DS QMF Function: Command
Duplicate value in a unique index column.
One of the columns being modified by your command contains a value equal to the one being inserted. That column is a 'Unique Index' column. Unique Index columns cannot have duplicate values. Your &V1 command was not executed.
You cannot change or replace the existing table or view with your data. Consider saving the data as a new table.
SQLCODE: -00803 Database: SQL/DS QMF Function: Command
The package &V2 is not found in the catalog table.
When SQL/DS tried to run the QMF program, it could not find the package in the catalog table SYSTEM.SYSACCESS. This can happen because:
Refer to the SQL/DS Messages and Codes manual for a detailed explanation and report this problem to your Information Center.
SQLCODE: -00805 Database: SQL/DS QMF Function: Command
You do not have authorization to modify system catalogs.
You cannot modify system catalogs unless you have been granted authority. You may read the catalogs and retrieve data using SQL query statements. Your "&V1" command was not executed.
Follow your QMF administrator procedures if authority is required.
SQLCODE: -00808 Database: SQL/DS QMF Function: Command
CONNECT denied by accounting user exit routine.
Your attempt to connect to SQL/DS was rejected by your installation's accounting user exit routine.
See your QMF administrator.
SQLCODE: -00815 Database: SQL/DS QMF Function: Command
You cannot &V1 a system catalog.
The operation is not permitted. No user can be authorized to do it.
Do not attempt that operation.
SQLCODE: -00823 Database: SQL/DS QMF Function: Command
You cannot use a userid when connecting in the current location.
You cannot use a userid and/or password in the CONNECT command because your current location or the target location does not support SQL/DS private protocol. If the location is DB2 or VSE SQL/DS, userid and password cannot be specified in the CONNECT command.
If you are running in VM, the location is DB2 or VSE SQL/DS, and the protocol option in SQLINIT is AUTO, you can issue one of the following CONNECT commands:
If the protocol option is DRDA and the location is either SQL/DS or DB2, you can issue the following command:
If you attempt to connect to another userid, verify that you entered the CONNECT command at the correct location. Otherwise, contact your QMF administrator.
If you attempt to connect to another location with a userid, verify that the location is correct. If so, omit the userid/password in the command; otherwise, contact your QMF administrator.
SQLCODE: -00836 Database: SQL/DS QMF Function: Command
Command failed due to errors in communications directories.
Your local installation must define either a system or a user communications directory, containing a nickname entry for the location name specified in your &V1. command. The SQL/DS database encountered an error when it tried to resolve this nickname entry. However, you are still connected to the same location. The SQLCODE is &V9 and the reason code is &V2.. Refer to the SQL/DS Messages and Codes manual for a detailed explanation of this error.
One reason for this error is that you may have specified a location name that is not defined in the communications directories.
If the specified location name is incorrect, correct it and try again.
In the communications directories, verify that the nickname entry for the specified location name has the correct TPN, LUNAME and DBNAME.
If you do not have a user communications directory or your user communications directory does not have a nickname entry for the specified location, contact your QMF administrator.
SQLCODE: -00841 Database: SQL/DS QMF Function: Command
You must connect to a location to continue using QMF.
Your database server is lost due to the previous error. If you wish to continue using QMF, you may try to reconnect or you can choose to exit QMF.
If you choose to connect to another location, enter the proper values to connect to a valid location. Otherwise, you must exit QMF.
SQLCODE: -00900 Database: SQL/DS QMF Function: Command
The portion of the database you require is in use.
The object you need in the database cannot be accessed until another user has completed processing.
End your QMF session and sign on again at a later time.
SQLCODE: -00911 Database: SQL/DS QMF Function: Command
The portion of the database you require is in use.
The object you need in the database cannot be accessed until another user has completed processing.
End your QMF session and sign on again at a later time.
SQLCODE: -00912 Database: SQL/DS QMF Function: Command
A CANCEL request has been issued.
The CANCEL could have been issued by the user or by the system. The CANCEL issued by the system is a result of reaching the limit on lock request blocks.
Redo your changes as necessary. If you did not issue the CANCEL request, and you continue to get SQLCODE -914, contact your system programmer about increasing the NLRBU or the NLRBS parameters when starting the application server.
SQLCODE: -00914 Database: SQL/DS QMF Function: Command
&V1 was not processed because of the system work load.
&V1 cannot be performed now because of the work load on the QMF system.
Continue with another operation and try &V1 at a later time. Contact your QMF administrator for more details about the current system work load.
SQLCODE: -00915 Database: SQL/DS QMF Function: Command
&V1 was not performed because of operator action.
The system operator interrupted the processing of &V1.. Your command was given correctly, but not processed.
Give the command again.
SQLCODE: -00916 Database: SQL/DS QMF Function: Command
The database manager program ran out of virtual storage.
The database manager program does not have enough virtual storage to run your &V1 command.
Try later when there is less activity on QMF. If the condition persists, inform your QMF administrator.
SQLCODE: -00930 Database: SQL/DS QMF Function: Command
The communications path to &V2. is not available.
You cannot access database &V2. for one of the following reasons:
If you issued the "CONNECT TO &V2." command, verify that the location name &V2 is correct and has been defined in the communications directories. If not, correct it and try again. Otherwise, contact your QMF administrator for the correct communications protocol.
The limit on the number of connections allowed to the SQL/DS virtual machine is set by the MAXCONN value in the SQL/DS virtual machine directory. If this limit has been exceeded, try your command later when the system activity is lighter. If this condition occurs frequently, contact your QMF administrator to get the MAXCONN value increased.
If the "CONNECT TO <location>" command is supported and you have issued a command other than CONNECT, QMF may have reconnected you to the current location. If so, continue to use QMF. If not, the Lost Connection Prompt panel prompts you to connect to another location.
SQLCODE: -00933 Database: SQL/DS QMF Function: Command
The database manager program ran out of virtual storage.
The database manager program does not have enough virtual storage to run your &V1 command.
Try later when there is less activity on QMF. If the condition persists, inform your QMF administrator.
SQLCODE: -00939 Database: SQL/DS QMF Function: Command
The database &V2 is not ready or cannot be found.
You cannot access the database for one of the following reasons:
If you issued the "CONNECT TO &V2." command, verify that the location name &V2 is correct and has been defined in the communications directories. If not, correct it and try again. Otherwise, contact your QMF administrator.
If the "CONNECT TO <location>" command is supported and you have issued a command other than CONNECT, QMF may have reconnected you to the current location. If so, continue to use QMF. If not, the Lost Connection Prompt panel prompts you to connect to another location.
SQLCODE: -00940 Database: SQL/DS QMF Function: Command
The database manager program ran out of virtual storage.
The database manager program does not have enough virtual storage to run your &V1 command.
Try later when there is less activity on QMF. If the condition persists, inform your QMF administrator.
SQLCODE: -00942 Database: SQL/DS QMF Function: Command
The QMF virtual machine, &V3, cannot access database &V2..
The QMF virtual machine is not properly defined. The file ARISRMBT MODULE, on the QMF machine's A-disk, does not describe the database program that QMF is attempting to access.
Tell your QMF administrator about this message and wait for their response. There is nothing you can do until the QMF virtual machine is properly defined.
SQLCODE: -00943 Database: SQL/DS QMF Function: Command
Your connection to SQL/DS was severed because of operator action.
The SQL/DS virtual-machine operator entered the FORCE command to cause ROLLBACK of the current logical unit of work and to sever your connection to the SQL/DS system. The USER ID, password, and database name are all reset to their default values.
You can continue. Any explicit CONNECTs you have issued have been lost. You must issue another explicit CONNECT request, using the same USER ID, to reestablish your original connection.
SQLCODE: -00948 Database: SQL/DS QMF Function: Command
Your query is too long or too complex.
The SQL statement is too long or too complex to be interpreted. It can be simplified by reducing the number of ...
You may also have defined a view with more than 140 columns or a row wider than 4070 characters.
Shorten your query or rewrite it as more than one query. If this problem continues, contact your QMF administrator.
SQLCODE: -00101 Database: SQL/DS QMF Function: SQL Query
Data is too long. Check your quotes.
A character constant must be enclosed in quotes. If you omit a closing quote, your data could exceed the maximum length: 254 characters normally, or 127 graphic characters if you are using the Double Byte Character Set under SQL/DS.
Change your data and run the query again.
SQLCODE: -00102 Database: SQL/DS QMF Function: SQL Query
&V1 starts with a digit, but is not a valid number.
&V1 starts with a digit, but is not a valid integer, decimal, or floating-point number. If it is meant to be a...
Change &V1 and run the query again.
SQLCODE: -00103 Database: SQL/DS QMF Function: SQL Query
Either &V1 or something near it is invalid.
Some of the possible causes are:
Examine your query, make the necessary changes, and run it again.
SQLCODE: -00104 Database: SQL/DS QMF Function: SQL Query
&V2 cannot follow &V1..
Some of the possible causes are ...
Change the query and run it again.
SQLCODE: -00105 Database: SQL/DS QMF Function: SQL Query
Something is missing from the end of the query.
The missing item could be anything from a single quote to several lines. Queries that end like these examples could cause this message:
incomplete)
missing)
everything after
is missing)Complete your query and run it again.
SQLCODE: -00106 Database: SQL/DS QMF Function: SQL Query
&V1 is too long. Maximum allowable size is &V2.
The query contains a name whose length exceeds the maximum length. When determining the length of this name, an EBCDIC character counts as one byte and a DBCS character counts as two bytes.
A qualifier for a table or view name cannot be more than 8 bytes long.
Shorten &V1 and run the query again.
SQLCODE: -00107 Database: SQL/DS QMF Function: SQL Query
&V1 is too long. Maximum allowable size is &V2.
The query contains a name whose length exceeds the maximum length. When determining the length of this name, an EBCDIC character counts as one byte and a DBCS character counts as two bytes.
A qualifier for a table or view name cannot be more than 8 bytes long.
Shorten &V1 and run the query again.
SQLCODE: -00108 Database: SQL/DS QMF Function: SQL Query
&V1 is not a function.
Some of the functions are AVG, MAX, MIN, SUM, COUNT, DATE, TIME, TIMESTAMP, YEAR, MONTH, DAY, HOUR, MINUTE, SECOND, MICROSECOND, CHAR, and DAYS. If &V1 is one of these, be sure that the punctuation of the statement is correct. For example:
SELECT MIN(PRICE), MAX(PRICE)
is correct.
SELECT DATE('1996-10-01') - 10102433.
is correct.Change the name of the function or the punctuation of the statement and run the query again.
SQLCODE: -00110 Database: SQL/DS QMF Function: SQL Query
A column function does not use any column name.
The column functions AVG, MAX, MIN, and SUM must act on expressions that contain a column name from one of the tables accessed.
Correct: SELECT SUM (SALARY * 1.15) FROM Q.STAFF Incorrect: SELECT SUM (18000 * 1.15) FROM Q.STAFF
Make sure that all of your column functions have columns to act on and run the query again.
SQLCODE: -00111 Database: SQL/DS QMF Function: SQL Query
A column function uses an invalid expression.
The column functions are AVG, COUNT, MAX, MIN, and SUM. Column function expressions cannot contain column functions.
Correct: AVG(UNITS * PRICE) Incorrect: AVG(UNITS * MAX(PRICE))
Change your query so that the column function has a correct expression and run it again.
SQLCODE: -00112 Database: SQL/DS QMF Function: SQL Query
The 3-part name you specified is invalid.
The location qualifier of &V1. does not match the name of the connected location &V2. SQL/DS only supports 3-part names whose location qualifiers match the name of the current location.
Issue the QMF CONNECT command to connect to the specified location, then continue with your query activities.
SQLCODE: -00114 Database: SQL/DS QMF Function: SQL Query
&V1 is used incorrectly.
A simple comparison like '>' or '=' must not be followed by a list of items. ANY and ALL comparisons must be followed by a subselect, rather than an expression or a list of items. For Example:
Correct: WHERE SALARY > ALL (SELECT COMM FROM Q.STAFF) Incorrect: WHERE SALARY > ALL (10000)
Change the usage of &V1 and run your query again.
SQLCODE: -00115 Database: SQL/DS QMF Function: SQL Query
The database label is too long.
The length of the label for a column or table exceeds the maximum of 30 bytes. An EBCDIC character counts as one byte and a DBCS character counts as two bytes.
Shorten the label and run the query again.
SQLCODE: -00116 Database: SQL/DS QMF Function: SQL Query
The number of values doesn't match the number of columns.
In a statement like INSERT INTO Q.STAFF, you must provide a value for every column that was defined as NOT NULL.
If you do not give a list of columns after the table name, then give a value for every column in the table, after VALUES.
If you do give a list of columns after the table name, then give a value for every column in that list, after VALUES.
Example:
INSERT INTO Q.STAFF (ID, NAME, DEPT)
VALUES (400, 'HARRISON', 20)Provide a value for each column you want to INSERT INTO and run the query again.
SQLCODE: -00117 Database: SQL/DS QMF Function: SQL Query
You can't modify a table used in a subquery.
"Modify" includes INSERT, UPDATE, and DELETE.
Incorrect: INSERT INTO Q.STAFF SELECT * FROM Q.STAFF WHERE YEARS > 7
The example tries to modify the table from which it is receiving data.
Change your query so that the same table used in the subquery is not modified or write a separate query to modify the table.
SQLCODE: -00118 Database: SQL/DS QMF Function: SQL Query
The grouping is inconsistent.
One of the following has occurred:
Correct: SELECT DEPT, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT
Correct: SELECT DEPT, JOB, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT, JOB (Not: GROUP BY DEPT)(If you use * after SELECT, list all column names after GROUP BY.
Correct: HAVING MIN(YEARS) > 6
(Not: HAVING YEARS > 6)Correct: SELECT DEPT, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT
Change the SQL statement and run your query again.
SQLCODE: -00119 Database: SQL/DS QMF Function: SQL Query
A built-in function or grouped column is used incorrectly.
You cannot use a built-in function (AVG, COUNT, MAX, MIN or SUM) after WHERE or SET except as part of a subquery.
Correct:
WHERE YEARS > (SELECT AVG(YEARS)
FROM Q.STAFF)
Incorrect:
WHERE YEARS > AVG(YEARS)If your query refers to a view, a column named after GROUP BY in the view definition cannot be used in a condition in your query. For example, if DEPT is used after GROUP BY in defining VIEW, then the following is
Incorrect: SELECT DEPT, SUMSALARY FROM VIEW WHERE DEPT = 20
Change your query and run it again. If your query uses a view, write a query to select from the table the view is based on.
SQLCODE: -00120 Database: SQL/DS QMF Function: SQL Query
You cannot modify a column twice in the same query.
"Modify" includes INSERT and UPDATE. For example, in the following invalid statement, the column 'YEARS' cannot be modified more than once.
Incorrect:
INSERT INTO Q.STAFF (ID, YEARS, JOB,
YEARS)
VALUES (400, 7, 'clerk', 8)Change the SQL statement so that there is only one modification and run it again.
SQLCODE: -00121 Database: SQL/DS QMF Function: SQL Query
The grouping is inconsistent.
One of the following has occurred:
Correct: SELECT DEPT, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT
Correct: SELECT DEPT, JOB, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT, JOB (Not: GROUP BY DEPT)(If you use * after SELECT, list all column names after GROUP BY.
Correct: HAVING MIN(YEARS) > 6
(Not: HAVING YEARS > 6)Correct: SELECT DEPT, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT
Change the SQL statement and run your query again.
SQLCODE: -00122 Database: SQL/DS QMF Function: SQL Query
No more than 16 columns allowed after ORDER BY.
Your ORDER BY list contains more than 16 columns referred to by name or integer. The maximum allowed is 16.
Reduce the number of columns referred to in the ORDER BY clause to 16 or less and run the query again.
SQLCODE: -00124 Database: SQL/DS QMF Function: SQL Query
You cannot ORDER BY column &V1..
There is no column &V1 in the list after SELECT. (The column number refers to the place of a column in the list after SELECT. You cannot use column 8, for example, if fewer than 8 columns are listed.)
Correct the query and run it again.
SQLCODE: -00125 Database: SQL/DS QMF Function: SQL Query
You cannot use DISTINCT more than once in a query.
Examples of DISTINCT usage:
Correct: SELECT AVG(DISTINCT SALARY), DEPT FROM STAFF GROUP BY DEPT HAVING AVG(SALARY) > 16000 Incorrect: SELECT AVG(DISTINCT SALARY), DEPT FROM STAFF GROUP BY DEPT HAVING AVG(DISTINCT SALARY) > 16000
Remove all but one DISTINCT from your query and run it again.
SQLCODE: -00127 Database: SQL/DS QMF Function: SQL Query
Use NULL with IS or IS NOT.
NULL cannot be used as an item in a list following IN in a WHERE clause. For example
WHERE AMT IN (20,50,NULL) is wrong, but WHERE AMT IN (20,50) OR AMT IS NULL is OK.
Change the phrase with NULL and run your query again.
SQLCODE: -00128 Database: SQL/DS QMF Function: SQL Query
You used too many tables or columns in your query.
In your query, one of the following items exceeds the limits listed:
Table Names 15
Selected columns 255Correct your query to conform to the limits, then rerun it.
SQLCODE: -00129 Database: SQL/DS QMF Function: SQL Query
You use SELECT twice; parentheses needed.
Your query refers to a value or set of values computed by another query, called a subquery. The subquery portion of the complete query must be enclosed in parentheses.
Place parentheses around the subquery (SELECT..........) and run the query again.
SQLCODE: -00130 Database: SQL/DS QMF Function: SQL Query
An escape character used with the LIKE keyword is not valid.
To be an escape character, you must enclose a single character in quotes in the ESCAPE clause. The escape character can be in the string following LIKE only if it is followed by itself, %, or _. You cannot specify the ESCAPE clause if the column name at the left of the LIKE or NOT LIKE has the MIXED attribute. For example, in the following WHERE clause
WHERE COL1 LIKE 'AA+%BB%' ESCAPE '+'
'+' is the escape character, and COL1 is of type CHARACTER;, the WHERE clause will produce values of COL1 that begin with 'AA%BB'. In this example, in the character string following LIKE, any use of '+' other than '++', '+%', or '+_' is an error. (Note that if COL1 has the MIXED attribute, the escape character cannot be specified.)
Fix the character string, or choose a different escape character and change the character string accordingly. Verify that the column name at the left of the LIKE or NOT LIKE does not have the MIXED attribute.
SQLCODE: -00131 Database: SQL/DS QMF Function: SQL Query
LIKE or NOT LIKE is used incorrectly.
A condition written with LIKE or NOT LIKE is invalid. Follow LIKE or NOT LIKE by character string; you may use the symbols '%' and '_'.
Write NAME LIKE 'JO%' , where NAME is
a column name.
If the LIKE condition appears in the WHERE clause of an UPDATE or DELETE statement, the column used must not be derived from an expression, a constant, or a scalar function in the view definition.
Change the condition using LIKE or NOT LIKE and run your query again.
SQLCODE: -00132 Database: SQL/DS QMF Function: SQL Query
An expression is improperly used after a HAVING or WHERE clause.
You must use a column name, rather than an expression, as the argument of a built-in function, when that column is a correlated reference column in a WHERE or HAVING clause. For example:
SELECT DEPT,SUM(YEARS) FROM Q.STAFF VARX GROUP BY DEPT HAVING SUM(YEARS) > ANY (SELECT AVG(YEARS) FROM Q.STAFF GROUP BY DEPT HAVING MAX(YEARS) > MIN(1*VARX.YEARS))
is incorrect -- (1*VARX.YEARS) cannot be the argument of a built-in function MIN because it is an expression containing the correlated reference variable VARX.YEARS.
Correct your query and rerun it.
SQLCODE: -00133 Database: SQL/DS QMF Function: SQL Query
A LONG VARCHAR column is used incorrectly.
The following limitations apply to using a column of data type LONG VARCHAR or LONG VARGRAPHIC:
Either comply with the previously listed conditions for columns of data type LONG VARCHAR or LONG VARGRAPHIC, or remove the column, and rerun the query.
SQLCODE: -00134 Database: SQL/DS QMF Function: SQL Query
A LONG VARCHAR column is used incorrectly.
The following limitations apply to using a column of data type LONG VARCHAR or LONG VARGRAPHIC:
Either comply with the previously listed conditions for columns of data type LONG VARCHAR or LONG VARGRAPHIC, or remove the column, and rerun the query.
SQLCODE: -00135 Database: SQL/DS QMF Function: SQL Query
The length of the result from &V1 is greater than &V2..
The result of the &V1 operation is too long. It cannot be greater than &V2..
Change your query to create a shorter result, and run the query again.
SQLCODE: -00137 Database: SQL/DS QMF Function: SQL Query
WITH CHECK cannot be used with this view.
The WITH CHECK option cannot be used if...
Continue with another operation.
SQLCODE: -00140 Database: SQL/DS QMF Function: SQL Query
Insert or update value does not satisfy view definition.
WITH CHECK OPTION was used in the definition of the view whose data you are trying to change. All attempts to insert or update rows in the view are checked to make sure that the results will conform to the definition of the view. Some value in your query does not satisfy a condition in that definition.
Examine the definition of the view to determine why the change was rejected, and change the value in the query.
SQLCODE: -00141 Database: SQL/DS QMF Function: SQL Query
You cannot modify the specified object.
The specified object is a view based on more than one table. INSERT, DELETE, or UPDATE of a view is not permitted if the VIEW is based on more than one table.
Verify that the table/view name you specified is correct.
SQLCODE: -00149 Database: SQL/DS QMF Function: SQL Query
You cannot modify the data in this view.
You cannot use INSERT, UPDATE, or DELETE a view that ...
Write separate queries to modify the tables used to create the view.
SQLCODE: -00150 Database: SQL/DS QMF Function: SQL Query
You cannot modify the data in this view.
You cannot use INSERT, UPDATE, or DELETE a view that ...
Write separate queries to modify the tables used to create the view.
SQLCODE: -00151 Database: SQL/DS QMF Function: SQL Query
Condition uses a column defined by a built-in function.
One of the tables used in your query is a view. After WHERE, a condition uses a column from that view that is defined in terms of one of the built-in functions (AVG, COUNT, MAX, MIN, SUM). Columns defined in that way cannot be used in conditions.
Check the definition of the view to see what columns you cannot use after WHERE. Correct your query and run it again.
SQLCODE: -00152 Database: SQL/DS QMF Function: SQL Query
View columns defined by expressions or functions need names.
Your CREATE VIEW statement includes a column defined from an expression, such as UNITS * PRICE; a built-in function, such as AVG(YEARS); or a constant, such as 'JUNE 1'. You must supply names for those columns, and so you must have a name list with a name for each column.
Provide new names for all columns defined from functions or expressions in your CREATE VIEW query.
SQLCODE: -00153 Database: SQL/DS QMF Function: SQL Query
Invalid definition or use of view.
The operation violates one of these rules:
- data from more than one table - data selected by DISTINCT or GROUP BY
Make your command valid according to the rules on views and give it again.
SQLCODE: -00154 Database: SQL/DS QMF Function: SQL Query
A view defined by GROUP BY or HAVING is named after FROM.
One of the tables named after FROM in your query is a view defined by a query that uses a GROUP BY or HAVING clause. That view cannot be named after FROM along with any other table.
Rewrite your query so as not to name the view along with another table, after FROM. Run the query again.
SQLCODE: -00155 Database: SQL/DS QMF Function: SQL Query
Invalid definition or use of view.
This view was created using DISTINCT or GROUP-BY. You must conform to the following rules in order to use the view.
For example, if the view definition is as follows:
CREATE VIEW V1 (COLA,COLB) AS SELECT DISTINCT (COL1,COL2) FROM TABLEA
You must select both COLA and COLB from V1. Also, you could not use AVG(COLA) or other column functions.
Change the query and run it again.
SQLCODE: -00156 Database: SQL/DS QMF Function: SQL Query
A view cannot be used in a FOREIGN KEY clause.
&V1..&V2 is a view that was identified in a FOREIGN KEY clause of a CREATE or ALTER TABLE statement. A FOREIGN KEY clause must identify a table, not a view.
Be sure that the correct name was used. Do not refer to a view in a FOREIGN KEY clause.
SQLCODE: -00157 Database: SQL/DS QMF Function: SQL Query
The CREATE VIEW and SELECT lists need the same number of columns.
There must be a column name in your SELECT list for every column name in the CREATE VIEW list. If you replace the list of names in the SELECT list with an asterisk (*), the view will contain the same column names as the original table.
Change the SELECT list column names to conform to the CREATE VIEW list and run the query again.
SQLCODE: -00158 Database: SQL/DS QMF Function: SQL Query
Invalid use of colon (:).
Your query uses a name preceded by a colon, as in "WHERE NAME = :NAME (That usage has a meaning in a query submitted to the preprocessor program, but not in a query in QMF.)
Correct your query. Use names of tables, columns, or views, or else character constants enclosed in single quotes.
SQLCODE: -00163 Database: SQL/DS QMF Function: SQL Query
Invalid DBCS constant.
Your query included a "DBCS constant", a graphic literal that begins with G', N', or X' .
If you intended to use a character constant, enclose the entire constant in single quotes.
If you intended to use a DBCS constant, it should be in the following form:
G'<aabbcc>' or N'<aabbcc>'
The < and > stand for shift-out (so) and shift-in (si). There must be an even number of characters between so and si.
Change your query and run it again.
SQLCODE: -00164 Database: SQL/DS QMF Function: SQL Query
A name within double quotes cannot start or end with a blank.
You tried to run a query containing a name within double quotes that begins or ends with a blank. This is not allowed. For example, the query shown below is incorrect because " 1978 PARTS" begins with a blank.
Incorrect: CREATE VIEW " 1978 PARTS" AS SELECT * FROM INVNTRY WHERE DATE = '1978'
Change your query and run it again.
SQLCODE: -00165 Database: SQL/DS QMF Function: SQL Query
Invalid DBCS constant.
Your query included a "DBCS constant", a graphic literal that begins with G', N', or X' .
If you intended to use a character constant, enclose the entire constant in single quotes.
If you intended to use a DBCS constant, it should be in the following form:
G'<aabbcc>' or N'<aabbcc>'
The < and > stand for shift-out (so) and shift-in (si). There must be an even number of characters between so and si.
Change your query and run it again.
SQLCODE: -00166 Database: SQL/DS QMF Function: SQL Query
Invalid hexadecimal literal.
Your query included a "hexadecimal literal", a constant that begins with X' ....
If you intended to use a character constant, enclose the entire constant in single quotes.
If you intended to use a hexadecimal literal, use a valid hexadecimal code expressed with an even number of characters.
Correct your query and run it again.
SQLCODE: -00167 Database: SQL/DS QMF Function: SQL Query
Invalid DBCS constant.
Your query included a "DBCS constant", a graphic literal that begins with G', N', or X' .
If you intended to use a character constant, enclose the entire constant in single quotes.
If you intended to use a DBCS constant, it should be in the following form:
G'<aabbcc>' or N'<aabbcc>'
The < and > stand for shift-out (so) and shift-in (si). There must be an even number of characters between so and si.
Change your query and run it again.
SQLCODE: -00169 Database: SQL/DS QMF Function: SQL Query
Invalid DBCS constant.
Your query included a "DBCS constant", a graphic literal that begins with G', N', or X' .
If you intended to use a character constant, enclose the entire constant in single quotes.
If you intended to use a DBCS constant, it should be in the following form:
G'<aabbcc>' or N'<aabbcc>'
The < and > stand for shift-out (so) and shift-in (si). There must be an even number of characters between so and si.
Change your query and run it again.
SQLCODE: -00170 Database: SQL/DS QMF Function: SQL Query
Argument '&V1' of scalar function '&V2' is invalid.
The data type, length, or value specified for scalar function '&V2' is incorrect. Refer to SQL query publications for more information.
Change the data type, length, or value of '&V2' function and run the query again.
SQLCODE: -00171 Database: SQL/DS QMF Function: SQL Query
The number of arguments specified for scalar function '&V1' is invalid.
The SQL statement has specified the scalar function &V1 with either too many or too few arguments. The supported functions are:
DATE, TIME, TIMESTAMP, YEAR, MONTH, DAY, HOUR, MINUTE, SECOND, MICROSECOND, CHAR, DAYS, AVG, MAX, MIN, COUNT.
Examine the use of the scalar function &V1. Change the scalar function and run the query again.
SQLCODE: -00172 Database: SQL/DS QMF Function: SQL Query
The datetime value has invalid syntax.
The string representation of a valid DATE has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIME has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIMESTAMP has the following format:
'yyyy-mm-dd-hh.mm.ss.nnnnnn'
Correct the syntax for the datetime value and run the query again.
SQLCODE: -00180 Database: SQL/DS QMF Function: SQL Query
The datetime value is not a valid value.
The string representation of a datetime value contains a value which is out of range. The proper ranges for datetime values are as follows:
Years - 1 to 9999 Months - 1 to 12 Days - 1 to 31 Hours - 0 to 24 Minutes - 0 to 59 Seconds - 0 to 59
Correct the datetime value and run the query again.
SQLCODE: -00181 Database: SQL/DS QMF Function: SQL Query
An arithmetic expression with a datetime value is invalid.
The specified arithmetic expression contains an improperly used datetime value or simple duration. Some correct examples are:
SELECT STARTD + 10102433. FROM Q.PROJECT SELECT STARTD + 1 YEAR FROM Q.PROJECT
Correct the expression and run the query again.
SQLCODE: -00182 Database: SQL/DS QMF Function: SQL Query
An arithmetic operation on a date or timestamp has a result that is invalid.
The result of an arithmetic operation is a date or timestamp that is not within the valid range. Valid dates are between 0001-01-01 and 9999-12-31.
Correct the datetime value and run the query again.
SQLCODE: -00183 Database: SQL/DS QMF Function: SQL Query
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00184 Database: SQL/DS QMF Function: SQL Query
The date or time value cannot be formatted.
One of the following has occurred:
Either change your string representation of the date or time value to be one of the recognized formats, or contact your QMF administrator for assistance in making the local date or time routine available to the database.
SQLCODE: -00185 Database: SQL/DS QMF Function: SQL Query
A simple duration is not in a date/time arithmetic expression.
Simple durations such as 1 MONTH must be used in a correct date/time arithmetic context. For example, a WHERE clause for the statement:
SELECT PROJNO FROM Q.PROJECT could be:
WHERE STARTD - 1 MONTH > '1987-05-05'
WHERE STARTD > DATE('1987-05-05') +
1 MONTHDO NOT use them alone in an expression such as:
WHERE STARTD > 1 MONTH.
Or in an expression that is not identified as a date:
SELECT PROJNO FROM Q.PROJECT could be:
WHERE STARTD - 1 MONTH > '1987-05-05'
WHERE STARTD > DATE('1987-05-05') +
1 MONTHPut the simple duration in a correct date/time arithmetic expression and run the query again.
SQLCODE: -00187 Database: SQL/DS QMF Function: SQL Query
Your statement referenced an invalid CCSID &V1.
Your CREATE TABLE or ALTER TABLE statement referenced an invalid coded character set ID (CCSID) &V1. For one of the following reasons, this CCSID is not recognized by the SQL/DS database:
Correct the CCSID tag or the subtype for the character column in your CREATE TABLE or ALTER TABLE statement.
SQLCODE: -00189 Database: SQL/DS QMF Function: SQL Query
The mixed data consists of improper DBCS data value.
The mixed data may have a missing X'OE' (shift-out) or X'OF' (shift-in) or half of a DBCS character.
Refer to the SQL/DS Messages and codes manual for a detailed explanation of this error with reason code &V1..
Verify that the referenced data values are correct. If not, make the necessary change and rerun the query.
SQLCODE: -00191 Database: SQL/DS QMF Function: SQL Query
The first argument of the &V1 scalar function cannot be of MIXED subtype.
You cannot use an expression of MIXED subtype as the first argument of the &V1 scalar function.
Correct your SQL statement and try again.
SQLCODE: -00192 Database: SQL/DS QMF Function: SQL Query
Qualifier &V1 is not named after FROM.
A qualifier, &V1, that is used in the query in the SELECT, WHERE, GROUP BY or ORDER BY clause, is not found in the FROM clause of the query. If FROM is used more than once, as in a subquery, the qualifier may be used in one place and be needed in another.
A table name used as a qualifier must be specified exactly as it appears in the FROM clause.
A correlation variable used as a qualifier must be defined in the FROM clause.
Name &V1 after FROM.
SQLCODE: -00201 Database: SQL/DS QMF Function: SQL Query
Column &V1 is not in any table named in the query.
&V1 is not a column in any table or view named in the query. If it is intended to be a character constant, enclose it in single quotes.
Change the column name or add the table containing column &V1 to the query, and run the query again.
SQLCODE: -00202 Database: SQL/DS QMF Function: SQL Query
Column &V1 is in more than one table.
An unqualified column name is ambiguous if more than one table or view in the FROM clause has a column with that name, or if more than one column of a nested table expression has that name. A qualified column name is ambiguous only if the correlation name for the column name and for a nested table expression is not unique.
If the problem is caused by a non-unique column name in a nested table expression, change the nested table expression so that the column is unique. If the problem is caused by the use of an unqualified name, qualify it with a table, view or correlation name.
SQLCODE: -00203 Database: SQL/DS QMF Function: SQL Query
&V1..&V2 not in system catalog.
The object named in your statement cannot be found in the system catalog. The name may be misspelled or you may have the wrong qualifier (&V1).
Correct the name and run your query again.
SQLCODE: -00204 Database: SQL/DS QMF Function: SQL Query
Column name &V1 is not in table &V2..
You used column name &V1.. It was not found in table &V2.. You may have misspelled the name, or the table name may need to be qualified.
Verify that the column name and owner are correct and spelled correctly.
SQLCODE: -00205 Database: SQL/DS QMF Function: SQL Query
The &V1 &V2 on &V3..&V4 could not be found.
The query refers to &V1 &V2.. This &V1 does not exist for table &V3..&V4..
Check for a spelling error.
SQLCODE: -00206 Database: SQL/DS QMF Function: SQL Query
Use column numbers with ORDER BY, not column names.
When using ORDER BY with UNION, do not use a column name after ORDER BY. Instead, use a number that tells the position of the column in the list after SELECT.
Example: SELECT NAME, ID FROM Q.STAFF UNION SELECT NAME, TEMPID FROM Q.APPLICANT ORDER BY 1
Change the column names to column numbers and run the query again.
SQLCODE: -00207 Database: SQL/DS QMF Function: SQL Query
&V1 must be in the SELECT list.
&V1 follows ORDER BY. Either &V1 was not included in the SELECT list or it is misspelled after ORDER BY.
Add &V1 to the SELECT list; be sure it agrees with the column name after ORDER BY.
SQLCODE: -00208 Database: SQL/DS QMF Function: SQL Query
Column &V1 appears after ORDER BY and twice after SELECT.
Your SELECT list contains the column name &V1 from more than one table. Which of the columns of the same name do you wish to ORDER BY?
After ORDER BY, refer to the proper column by a number. Or add a qualifier to the column name.
SQLCODE: -00209 Database: SQL/DS QMF Function: SQL Query
Table name &V1 after FROM needs a table label.
The SQL command contains a table name as a qualifier which occurs two or more times after FROM. Since the table name is not unique, each table name after FROM needs a unique table label to qualify the column names.
Add unique table labels to the table names after FROM and run your query again.
SQLCODE: -00211 Database: SQL/DS QMF Function: SQL Query
Invalid use of colon (:).
Your query uses a name preceded by a colon, as in "WHERE NAME = :NAME (That usage has a meaning in a query submitted to the preprocessor program, but not in a query in QMF.)
Correct your query. Use names of tables, columns, or views, or else character constants enclosed in single quotes.
SQLCODE: -00312 Database: SQL/DS QMF Function: SQL Query
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00313 Database: SQL/DS QMF Function: SQL Query
One or more characters could not be converted into a usable code for the current server.
Your SQL statement referenced a character string, which must be converted to a code suitable for the application server. However, due to a mismatch in data representation, this was not possible. The character string is incompatible with the corresponding column data type. Consequently, you cannot use the character string as specified.
Verify that the character columns and values you referenced are correct. If not, make the necessary change and try the query again. Otherwise, contact your QMF administrator.
SQLCODE: -00330 Database: SQL/DS QMF Function: SQL Query
A character string could not be converted due to incompatible CCSIDs.
Your SQL statement referenced a character string that has a coded character set ID(CCSID) &V1 in a coded character set that differs from the current one. To use this character string at the current server, it must be converted from the source CCSID &V1 to the target CCSID &V2. However, this pair of CCSIDs conversion rule is not defined in the SYSSTRINGS system table. Therefore, the database system could not convert the character string to a code suitable for the application server.
Refer to the SQL/DS Messages and codes manual for a detailed explanation of this error with reason code &V3. Possible causes for this conversion error are:
Verify that the referenced character columns and values that you referenced are correct. If not, make the necessary change and rerun the query again. Otherwise, contact your QMF administrator.
SQLCODE: -00332 Database: SQL/DS QMF Function: SQL Query
Invalid data type in position &V1..
Some SQL data types are not supported by the application requester. &V1 is the position of the first element with an invalid data type in the SQLDA. A common cause for this error is that the application requester has attempted to describe large object data residing at the application server. Some of the SQLTYPEs that can cause this error are: LOB, BLOB, CLOB, and DBLOB.
Remove the invalid data types and run the query again.
SQLCODE: -00351 Database: SQL/DS QMF Function: SQL Query
Data of different types must not be used in an expression or condition.
You used data of different types in an expression or condition. For example, the following is not valid because character data ('COMM') is used in a numeric expression:
Invalid WHERE SALARY = 12*'COMM'
Change any expression or condition so that data of the same type is used.
SQLCODE: -00401 Database: SQL/DS QMF Function: SQL Query
Numeric data is required.
Arithmetic expressions and the AVG and SUM built-in functions require numeric data. Non-numeric data cannot be used. Your query was not processed.
Change your query to include all numeric data with the arithmetic expression or built-in function and run the query again.
SQLCODE: -00402 Database: SQL/DS QMF Function: SQL Query
Some character value is too long for the corresponding column.
One of the values you are trying to insert is longer than the width of the column you want to insert it into.
Change the value to fit the column and run the query again.
SQLCODE: -00404 Database: SQL/DS QMF Function: SQL Query
Numeric value is outside allowable range for column.
Your query specifies a column that has an incorrect numeric value. The value might be the result of an expression.
The proper ranges for SQL values are as follows:
FLOAT ...... -7.2E75 to -5.4E-79, 0,
5.4E-79 to 7.2E75
INTEGER .... -2147483648 to 2147483647
SMALLINT ... -32768 to 32767
DECIMAL .... The range depends on the
precision and scale of
the column. For example,
if the value is being
specified for a decimal
column defined with
precision = 5 and
scale = 2, the range is
-999.99 to 999.99.Change the numeric value for the column and rerun your query.
SQLCODE: -00405 Database: SQL/DS QMF Function: SQL Query
Numeric value is outside allowable range for column.
Your query specifies a column that has an incorrect numeric value. The value might be the result of an expression.
The proper ranges for SQL values are as follows:
FLOAT ...... -7.2E75 to -5.4E-79, 0,
5.4E-79 to 7.2E75
INTEGER .... -2147483648 to 2147483647
SMALLINT ... -32768 to 32767
DECIMAL .... The range depends on the
precision and scale of
the column. For example,
if the value is being
specified for a decimal
column defined with
precision = 5 and
scale = 2, the range is
-999.99 to 999.99.Change the numeric value for the column and rerun your query.
SQLCODE: -00406 Database: SQL/DS QMF Function: SQL Query
You cannot update a NOT NULL column with a null value.
Some column you are updating does not allow NULL, and you want to update it with a null value. The null value could be from a subquery.
Remove the invalid NULL from your query and run it again.
SQLCODE: -00407 Database: SQL/DS QMF Function: SQL Query
A subquery returned an incompatible data type.
A value from a subquery used to update or insert was incompatible with the corresponding column. The subquery value and the corresponding column must have the same data type. For example, to update a numeric column, you must select only a numeric value in the subquery.
Change the subquery and run the query again.
SQLCODE: -00408 Database: SQL/DS QMF Function: SQL Query
COUNT was used incorrectly.
The built-in function, COUNT, can be used only with a "*" or with DISTINCT and a column name. Examples of usage:
Change your use of COUNT and run the query again.
SQLCODE: -00409 Database: SQL/DS QMF Function: SQL Query
&V1 is not a valid numeric value.
Your query tried to assign &V1 to a numeric field. What it tried to assign is either a floating point constant of 31 characters or more, or a value containing non-numeric characters.
Change &V1 and run your query again.
SQLCODE: -00410 Database: SQL/DS QMF Function: SQL Query
USER was used incorrectly.
USER stands for "user identification"; its value is an 8-character word. One of these errors has occurred:
Incorrect: USER - 50
Change your SQL statement and run your query again.
SQLCODE: -00411 Database: SQL/DS QMF Function: SQL Query
Use only one column after SELECT in the subquery.
When SELECT is used in a subquery, (except after INSERT), it can select only one column name.
Incorrect: (SELECT PARTNO, PRICE.......)
Change the SELECT list in your subquery and run the query again.
SQLCODE: -00412 Database: SQL/DS QMF Function: SQL Query
Arithmetic overflow during change of data type.
The result of an arithmetic or insert operation is not valid because arithmetic overflow occurred. For example, you may have tried to INSERT values with a data type of INTEGER into a column with data type of SMALLINT. Conversion is possible so long as the INTEGER values are small enough. But a value larger than 32767 will cause arithmetic overflow.
Change your operation and run the query again.
SQLCODE: -00413 Database: SQL/DS QMF Function: SQL Query
LIKE requires character or graphic data, the column has numeric or datetime data.
You wrote something like this: LIKE '1%' or LIKE '%12.40.25', where LIKE compares a partial value to the values in some column. The column has a numeric or datetime data type and LIKE requires character or graphic data.
Correct your query and run it again. With numeric data, use a numeric comparison, like "n >= 1000 and n < 2000".
SQLCODE: -00414 Database: SQL/DS QMF Function: SQL Query
Column attributes in your SELECT lists do not agree.
You connected two or more queries by UNION or UNION ALL. The SELECT lists in each query must have the same number of columns. Corresponding columns in each SELECT list must have comparable data definitions for the SELECT to succeed. If corresponding columns have field procedures, the columns must have the same field procedure and column CCSID value.
Rewrite your query with the SELECT lists of comparable columns, and rerun your query.
SQLCODE: -00415 Database: SQL/DS QMF Function: SQL Query
Wide character columns cannot be used with UNION.
A column with data type LONG VARCHAR, or with a width greater than 254, cannot be listed after SELECT in a query that uses UNION. Columns with these data types can be used: INTEGER, SMALLINT, DECIMAL, FLOAT, CHAR. A VARCHAR column can be used if its width is less than 255.
Remove any column wider than 254 characters from the SELECT list of any query used with UNION.
SQLCODE: -00416 Database: SQL/DS QMF Function: SQL Query
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00417 Database: SQL/DS QMF Function: SQL Query
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00418 Database: SQL/DS QMF Function: SQL Query
Decimal division is not possible with the values used.
Either the precision of the numerator or the scale of the denominator is too large for decimal division.
Change the precision or scale of your decimal division values and run the query again. Note that an integer or small integer value may have been converted to decimal for this calculation.
SQLCODE: -00419 Database: SQL/DS QMF Function: SQL Query
Even number of hexadecimal characters needed.
Your query included a "hexadecimal literal", a constant that begins with X'. The constant is associated with a column that has a GRAPHIC data type, and so must represent an even number of hexadecimal characters. Check that the length of the constant (between the single quotes) is divisible by four.
Correct your query and run it again.
SQLCODE: -00421 Database: SQL/DS QMF Function: SQL Query
SELECT lists do not have the same number of columns.
You connected two or more queries by UNION. The SELECT lists in each query must have the same number of columns.
Correct the query and run it again.
SQLCODE: -00422 Database: SQL/DS QMF Function: SQL Query
Invalid hexadecimal literal after IN.
Your query included a "hexadecimal literal", a constant that begins with X'. If there is a hexadecimal literal before IN, the first item in the list after IN may NOT be a hexadecimal literal.
Incorrect: X'C9C4' IN (X'F1F0', X'F2F0') Correct: X'C9C4' IN (10, X'F2F0')
Correct your query and run it again.
SQLCODE: -00423 Database: SQL/DS QMF Function: SQL Query
A subquery using a GROUP BY or HAVING clause needs ALL, ANY, EXISTS, or IN.
A subquery that uses a GROUP BY or HAVING clause can be expected to produce more than one value. It should be preceded by one of the keywords ALL, ANY, EXISTS, or IN.
Change the query and run the query again.
SQLCODE: -00516 Database: SQL/DS QMF Function: SQL Query
The foreign key value is not valid.
An update or insert query specified a value for a foreign key. However, the value is not equal to any of the primary key values of the parent table.
If the name of the referential constraint for the foreign key was provided by the database, that name is as follows: &V1..&V2..
Use a value for the foreign key that matches one of the primary key values.
SQLCODE: -00530 Database: SQL/DS QMF Function: SQL Query
The row cannot be updated or deleted because of a dependent row.
The attempt to update or delete a parent row failed, because the parent row has a dependent row or cascades to a dependent row that has been restricted using the RESTRICT rule.
If the name of the referential constraint for the foreign key was provided by the database, that name is as follows: &V1..&V2..
Make sure you selected the correct row. If you did, update or delete the dependent rows for which RESTRICT was specified. Then update or delete the parent row.
SQLCODE: -00532 Database: SQL/DS QMF Function: SQL Query
Cannot update a primary key or unique constraint in multiple rows.
An UPDATE operation attempted to update a primary key or unique constraint in multiple rows of the table. An UPDATE statement that affects the primary key or unique constraint cannot be used to update more than one row of the table.
Make sure the search condition of the UPDATE statement selects no more than one row of the table to be updated.
SQLCODE: -00534 Database: SQL/DS QMF Function: SQL Query
The DELETE statement is invalid because table &V1..&V2 can be affected.
A DELETE operation was attempted with table &V1..&V2, which was referred to in a subquery. However, this table is a dependent of the object table of the operation and is not protected from change by a rule of RESTRICT, so the deletion cannot be done.
Do not refer to a table in a subquery of a DELETE statement if the table can be affected by that statement.
SQLCODE: -00536 Database: SQL/DS QMF Function: SQL Query
You used a column name more than once.
A primary key, foreign key or unique constraint cannot contain duplicate column names. In a primary key, foreign key, or unique constraint clause, you used the same column name more than once. The column in error is &V1 &V2.
Specify unique column names.
SQLCODE: -00537 Database: SQL/DS QMF Function: SQL Query
Foreign key &V1 does not conform to the description of the primary key of table &V2..&V3..
You can receive this error for one of the following reasons:
If field procedure is defined for the corresponding columns, their column CCSID values should be identical.
Correct the FOREIGN KEY clause so that its description matches that of the indicated table's primary key.
SQLCODE: -00538 Database: SQL/DS QMF Function: SQL Query
Table &V1..&V2 does not have a primary key.
You specified table &V1..&V2 as a parent table in a FOREIGN KEY clause, but it cannot be defined as a parent table because it does not have a primary key.
Define a primary key for the table using ALTER TABLE.
SQLCODE: -00539 Database: SQL/DS QMF Function: SQL Query
Foreign key &V1 is invalid because it is a duplicate referential constraint.
The indicated FOREIGN KEY clause defines the same foreign key and parent table as another referential constraint.
Remove the duplicate referential constraint from the statement.
SQLCODE: -00541 Database: SQL/DS QMF Function: SQL Query
&V1 cannot be a column of a primary key or unique constraint because it can contain null values.
Column &V1 can contain null values; therefore, it cannot be included in a primary key or unique constraint clause.
When defining the primary key or unique constraint use only columns that cannot contain null values. Correct the primary key or unique constraint clause and run the statement again.
SQLCODE: -00542 Database: SQL/DS QMF Function: SQL Query
You cannot create &V1 for the owner "SYSTEM".
For example, you cannot run a query that contains a statement like this:
CREATE TABLE SYSTEM.&V1 .....
Do not attempt this operation.
SQLCODE: -00550 Database: SQL/DS QMF Function: SQL Query
The specified object does not exist, or you lack needed authority.
The specified object does not exist, or it's a read-only view, or you lack some needed authority, as follows:
If you misnamed an existing object, use the correct name. If you lack needed authority, contact your QMF administrator.
SQLCODE: -00551 Database: SQL/DS QMF Function: SQL Query
The specified object does not exist, or you lack needed authority.
The specified object does not exist, or it's a read-only view, or you lack some needed authority, as follows:
If you misnamed an existing object, use the correct name. If you lack needed authority, contact your QMF administrator.
SQLCODE: -00552 Database: SQL/DS QMF Function: SQL Query
You cannot grant a privilege to yourself.
The database manager does not allow you to grant your own privileges or set your password even though you have been granted CONNECT authority implicitly through the command "GRANT CONNECT TO ALL USERS". You can only change your password after the DBA has granted CONNECT authority to you explicitly and set you initial password.
Correct the statement and run it again.
SQLCODE: -00554 Database: SQL/DS QMF Function: SQL Query
You cannot revoke a privilege from yourself.
Privileges can only be revoked by one user with the proper authority from another user. However, if SQLRULES(STD) is in effect or CURRENT RULES contains STD, GRANT to self is allowed.
Contact your QMF administrator if you want any database privileges reduced.
SQLCODE: -00555 Database: SQL/DS QMF Function: SQL Query
You cannot revoke this privilege from &V1..
Either &V1 does not have the privilege you are trying to revoke, or it was granted by a user with a different authorization identifier from yours. You can revoke only privileges granted under your authorization identifier.
Proceed to another operation.
SQLCODE: -00556 Database: SQL/DS QMF Function: SQL Query
You cannot grant or revoke this combination of privileges.
One privilege you want to grant or revoke conflicts with the granting or revoking of another privilege in the same statement.
Break up your GRANT or REVOKE statement into separate statements and run the query again.
SQLCODE: -00557 Database: SQL/DS QMF Function: SQL Query
You cannot revoke a "special" privilege from a DBA.
Users cannot revoke "special" privileges , such as RESOURCE, from those with DBA authority.
Don't attempt this operation.
SQLCODE: -00558 Database: SQL/DS QMF Function: SQL Query
You cannot use the database without CONNECT authority.
In order to use the database, you need CONNECT authority. If you have already used the database during this session, another user may have revoked your CONNECT authority while you were running.
Report your problem to your QMF administrator.
SQLCODE: -00561 Database: SQL/DS QMF Function: SQL Query
Statement references an invalid userid.
A SQL userid must begin with an alphabetic character and contain eight or fewer alphabetic or numeric characters. It must contain no embedded blanks or special characters.
The userids PUBLIC and SYSTEM can be used only in certain restricted contexts.
In particular, the special privileges (CONNECT, DBA, and RESOURCE) cannot be GRANTed to or REVOKEd from PUBLIC or SYSTEM.
Do not attempt this operation unless you can change the userid it names.
SQLCODE: -00564 Database: SQL/DS QMF Function: SQL Query
The name of the object you are creating already exists.
The object you are creating or acquiring has a name that already exists.
Change the name to one that doesn't exist in the data base and run your query again.
SQLCODE: -00601 Database: SQL/DS QMF Function: SQL Query
Your table or view contains too many columns.
Your query would create a table or view with more than the maximum number of columns allowed.
Change your query so that the table or view you are creating will have less than 256 columns.
SQLCODE: -00602 Database: SQL/DS QMF Function: SQL Query
The &V1 column contains duplicate values.
You cannot create a &V1 column that contains duplicate values. One of the columns you named does so. If a column has a type of VARCHAR or VARGRAPHIC, two columns that differ only in the number of trailing blanks might cause duplication.
Change your CREATE statement so that it does not refer to a column with duplicate values, or else delete rows with duplicate values from the table.
SQLCODE: -00603 Database: SQL/DS QMF Function: SQL Query
Column definition problem.
Your query specifies a column that has a length, precision, or scale outside the data type limit. Some possible causes of your query error are:
Change the column definition to conform to the data type limit and run your SQL query again. See the SQL Reference manual for your database for a detailed explanation on the data type limits.
SQLCODE: -00604 Database: SQL/DS QMF Function: SQL Query
Your statement exceeds the maximum-allowable number of indexes for a table.
The maximum-allowable number of indexes for a SQL/DS table is 255 and the target table currently has that number of indexes.
This condition can occur if the target table already has 255 indexes and you issued either a CREATE INDEX or ALTER TABLE statement with the ADD PRIMARY KEY or ADD UNIQUE constraint clause.
Drop all unnecessary indexes and reissue your statement.
To do this, you can use a DROP INDEX statement or an ALTER TABLE statement with the DROP PRIMARY KEY or DROP UNIQUE constraint clause. For a list of all the SQL/DS indexes, display the SYSINDEXES system table.
SQLCODE: -00605 Database: SQL/DS QMF Function: SQL Query
The table or column named does not exist or is owned by another user.
The table or column named in your COMMENT ON statement or LABEL ON statement does not exist or it is owned by another user. You can only use the statement(s) for tables you have created. You may COMMENT ON or LABEL ON another user's tables only if you have DBA authority.
Continue with another operation.
SQLCODE: -00606 Database: SQL/DS QMF Function: SQL Query
You cannot add more tables to this DBSPACE.
The maximum number of tables for a DBSPACE is 255.
Either create your table in a different DBSPACE, or drop a table in the named DBSPACE to free space for an entry.
SQLCODE: -00607 Database: SQL/DS QMF Function: SQL Query
DBSPACE not found.
If you used IN with a DBSPACE name, either
If you didn't use IN, either
Enter the name of a DBSPACE that you can use and run your SQL query again.
SQLCODE: -00608 Database: SQL/DS QMF Function: SQL Query
You cannot ALTER a SYSTEM DBSPACE.
No user can ALTER a SYSTEM DBSPACE. The information in this storage area is vital to the operation of the system and cannot be changed by the user.
Do not attempt this operation.
SQLCODE: -00609 Database: SQL/DS QMF Function: SQL Query
You cannot create a table in the specified DBSPACE.
You must have the proper authority to create a table in a DBSPACE owned by another user or by the system.
Use another DBSPACE to create your table. Follow your local procedures if you need authorization to use a DBSPACE owned by another user or by the system.
SQLCODE: -00610 Database: SQL/DS QMF Function: SQL Query
You cannot use NOT NULL with ALTER TABLE.
The ALTER TABLE statement adds one new column to a table. All existing rows are expanded with a null value for the new column. The NOT NULL option cannot be used.
Remove the NOT NULL option from your ALTER TABLE statement and run the query again.
SQLCODE: -00611 Database: SQL/DS QMF Function: SQL Query
You used column name &V1 twice.
A table cannot contain two columns with the same name. In CREATE TABLE, CREATE VIEW, or CREATE INDEX you used column name &V1 more than once. In ALTER TABLE, &V1 is already the name of a column in the table.
Choose another column name and run your query again.
SQLCODE: -00612 Database: SQL/DS QMF Function: SQL Query
Columns chosen cannot be indexed.
Under CMS, you cannot index a LONG VARCHAR or LONG VARGRAPHIC column.
Under TSO, you cannot index a VARCHAR column whose maximum allowable length is over 254 characters.
Under either CMS or TSO, you cannot index a group of columns if the sum of their internal lengths exceeds 255 characters.
Revise your index or primary key definition, either by omitting one or more of the columns or by replacing long columns with shorter ones.
SQLCODE: -00614 Database: SQL/DS QMF Function: SQL Query
The CREATE INDEX or PRIMARY KEY statement specifies to many columns.
The number or columns specified in the CREATE INDEX or PRIMARY KEY statement exceeds the maximum number of columns allowed.
Change your CREATE INDEX or PRIMARY KEY statement to conform to the column limit.
SQLCODE: -00617 Database: SQL/DS QMF Function: SQL Query
An Explain table has an improper definition.
An error occurred during the execution of the EXPLAIN statement because a required explanation table is improperly defined.
The definition could be incorrect due to:
Correct the definition of the required explanation table before using EXPLAIN. See the SQL Reference manual for more information on the EXPLAIN statement and defining the explanation tables.
SQLCODE: -00619 Database: SQL/DS QMF Function: SQL Query
There is no private, recoverable DBSPACE available.
The DBSPACE name was not specified in the CREATE TABLE command, so a search was done to find a private DBSPACE owned by &V1..
Either there were no DBSPACEs found, they were full, or they were located in non-recoverable storage pools.
Either acquire a private DBSPACE, make room in an existing space, or explicitly specify the DBSPACE you want.
SQLCODE: -00620 Database: SQL/DS QMF Function: SQL Query
You cannot specify SET NULL for foreign key &V1..
The SET NULL delete rule cannot be specified for the FOREIGN KEY clause &V1 because no column of the key allows null values.
Either change a column of the key to allow null values or change the delete rule.
SQLCODE: -00629 Database: SQL/DS QMF Function: SQL Query
Keyword &V1 is given twice.
This query can use keyword &V1 only once. It was found two or more times.
Correct the query and run it again.
SQLCODE: -00630 Database: SQL/DS QMF Function: SQL Query
The table cannot be defined as a dependent of &V3..&V4 because of rule restrictions.
You cannot define the table as a dependent of table &V3..&V4.. The relationship would conflict with existing relationships. For example, you cannot define a dependent table to have more than one SET NULL relationship with a given parent table. The reason the relationship cannot be defined is identified by reason code '&V5'.
Either correct the FOREIGN KEY clause, or remove the clause from the statement. See SQL/Data System Messages and Codes for an explanation of reason code '&V5'.
SQLCODE: -00632 Database: SQL/DS QMF Function: SQL Query
Graphic and Mixed data types are not supported by the current server.
Your SQL statement referenced the clause or scalar function, &V1, and the current server does not support it.
This may happen because:
Issue the SQL statement on a server that supports Mixed, Graphic and Vargraphic data types. If you use these data types at the current server, contact your QMF administrator to reset the system default CCSIDs.
SQLCODE: -00640 Database: SQL/DS QMF Function: SQL Query
&V1 is a duplicate name.
You cannot use &V1 as a new foreign key or unique constraint name because the name has already been used with this table. The duplication can occur if the specified name already exists for the same foreign key or unique constraint on the current table.
Either use a different name or do not specify a name. If you do not specify a name, a default name will be assigned.
SQLCODE: -00644 Database: SQL/DS QMF Function: SQL Query
The foreign key cannot be defined due to the delete-connected rule using multiple paths.
The relationship will cause table &V1..&V2 to be delete-connected to table &V3..&V4 through multiple paths. The foreign key cannot be defined because of the reason code &V5..
Refer to the SQL/DS Messages and Codes manual for a detailed explanation of this error.
Verify that the connections for the related tables are defined correctly. If not, correct it and retry the SQL statement; otherwise, contact your QMF administrator for assistance.
SQLCODE: -00648 Database: SQL/DS QMF Function: SQL Query
Table &V1..&V2 already has a primary key.
A primary key cannot be defined for table &V1..&V2 because it already has a primary key. A table cannot have more than one primary key.
If you want a different primary key for this table, then the existing primary key must be dropped first.
SQLCODE: -00656 Database: SQL/DS QMF Function: SQL Query
UPDATE STATISTICS does not work with a view.
The UPDATE STATISTICS statement cannot be used with a view. It can only be used with one table.
Write queries to operate on the tables that make up the view and run the query again. Example:
UPDATE STATISTICS FOR TABLE PRICES
SQLCODE: -00657 Database: SQL/DS QMF Function: SQL Query
The &V1 &V2 defined for table &V3..&V4 cannot be activated.
The &V1 &V2 cannot be activated because the key would not be valid. For example, if an inactive primary key contains duplicate values, then it cannot be activated. The reason the key cannot be activated is identified by reason code '&V5'.
See SQL/Data System Messages and Codes for an explanation of reason code '&V5'.
SQLCODE: -00667 Database: SQL/DS QMF Function: SQL Query
Table &V1..&V2 cannot be accessed. &V3 &V4 is inactive.
No operation can be performed on table &V1..&V2 because the &V3 &V4 is inactive.
Try again when the key has been activated.
SQLCODE: -00668 Database: SQL/DS QMF Function: SQL Query
The primary key index cannot be dropped explicitly.
You cannot drop a primary key index using DROP INDEX.
If you want to reorganize the primary key index, you can use the ACTIVATE PRIMARY KEY clause of the ALTER TABLE statement. It will drop and re-create the primary key index. If you want to drop the primary key, you can use the DROP PRIMARY KEY clause of the ALTER TABLE statement.
SQLCODE: -00669 Database: SQL/DS QMF Function: SQL Query
The foreign key &V1 for table &V2..&V3 cannot be created.
The foreign key &V1 cannot be created because the key would not be valid. For example, if the parent table referred to by the foreign key has an inactive primary key, then the foreign key cannot be created. The reason the key cannot be activated is identified by reason code '&V4'.
See SQL/Data System Messages and Codes for an explanation of reason code '&V4'.
SQLCODE: -00670 Database: SQL/DS QMF Function: SQL Query
SQL/DS cannot load the DBCS data conversion routine.
The database fails to load your DBCS data conversion routine &V1 due to reason code &V2 and sub-code &V3.. The possible causes for this error condition are:
Furthermore, if the sub-code is X'01', the error was found at the application requester; if the sub-code is X'02', the error was found at the application server.
If the conversion routine &V1 is correct, contact your QMF administrator for assistance.
SQLCODE: -00674 Database: SQL/DS QMF Function: SQL Query
Data type &V1 for column &V2 is not permitted.
Data type &V1 is valid only for character columns (CHAR, VARCHAR, and LONGVARCHAR).
Remove the &V1 option from column &V2..
SQLCODE: -00683 Database: SQL/DS QMF Function: SQL Query
Invalid comparison with a column defined with a field procedure.
The value that is compared to a column defined with a field procedure does not have the same field type. The comparison is performed on the encoded form of the value in the column. For example, if the encoded value of the column is INTEGER, the data type of the value being compared must be identical. If they are strings, their data types must be compatible.
Correct the SQL statement and run the query again.
SQLCODE: -00687 Database: SQL/DS QMF Function: SQL Query
Your statement could cause the invalid entities table to overflow.
Your statement could cause an index to be marked invalid; therefore, it must reserve an entry in the invalid entities table. However, the number of invalid indexes and potentially invalid indexes are greater than the database internal limit. Your statement cannot be processed.
If there are many users running CREATE INDEX and REORGANIZE INDEX concurrently, try your statement again later. If the error persists, contact your QMF administrator to find the invalid indexes and clean up the entities table.
SQLCODE: -00698 Database: SQL/DS QMF Function: SQL Query
All storage pools for available DBSPACES are full.
DBSPACES are available, but the storage pools in which they reside do not have enough space for you to acquire DBSPACES. If you used STORPOOL clause, the specified storage pool is full and you may want to use another storage pool. If you did not use STORPOOL clause, it implies that all the available storage pools are full. There is not enough storage pool space for you to acquire DBSPACES.
Contact your QMF administrator to find the full storage pools and to increase their sizes by adding DBEXTENTS to the storage pools.
SQLCODE: -00699 Database: SQL/DS QMF Function: SQL Query
No available space in storage pool &V1.
Your SQL statement requires a new page or a shadow page but the storage pool &V1 does not have enough space.
Contact your QMF administrator to increase the size of storage pool &V1.. If your SQL statement is a REORGANIZE INDEX, ask the Information Center to determine if the index is marked invalid. If the index is invalid, you will have to either drop and recreate the index, or reorganize it again after the storage problem has been corrected.
SQLCODE: -00700 Database: SQL/DS QMF Function: SQL Query
Space allocated for data in your DBSPACE is full.
Your query will not run because there is not enough space for data in your DBSPACE.
If you are creating a table, specify a different DBSPACE. Otherwise, contact your QMF administrator for procedures to provide more data space and run the query again.
SQLCODE: -00701 Database: SQL/DS QMF Function: SQL Query
Space assigned for indexes in your DBSPACE is full.
Your query cannot be processed until more DBSPACE is added for indexes.
If you are creating a table, specify a different DBSPACE. Otherwise, contact your QMF administrator for procedures to provide more index space and run the query again.
SQLCODE: -00702 Database: SQL/DS QMF Function: SQL Query
Space for header information in your DBSPACE is full.
The space allocated in your DBSPACE by the parameter NHEADER for header information is full. Your query cannot be processed unless additional DBSPACE space is obtained.
If you are creating a table, specify a different DBSPACE. Otherwise, contact your QMF administrator for procedures to provide more header space and run the query again.
SQLCODE: -00703 Database: SQL/DS QMF Function: SQL Query
No DBSPACE available of the requested size and type.
Your ACQUIRE DBSPACE statement was not processed. One of the following has occurred:
If a storage pool was specified, verify that the storage pool exists by contacting your QMF administrator. If the storage pool exists, reduce the number of pages in your PAGES option or ask for another type of DBSPACE. If this does not work, contact your QMF administrator to request more DBSPACE and enter your ACQUIRE DBSPACE statement again when a DBSPACE has been added.
SQLCODE: -00704 Database: SQL/DS QMF Function: SQL Query
The value given for &V1 is invalid.
For an ACQUIRE or ALTER DBSPACE statement, the following values are used if the associated parameter is not specified:
NHEADER - 8 PAGES - 128
PCTFREE - 15 LOCK - PAGE
PCTINDEX - 33For CREATE INDEX or when adding a primary key to a table, a default of 10 is used for PCTFREE if it is not specified.
The maximum and minimum values for &V1 depend upon the application. Contact your QMF administrator for specific information.
Change the value of &V1 and rerun the query.
SQLCODE: -00705 Database: SQL/DS QMF Function: SQL Query
You cannot drop, lock, or alter a PUBLIC DBSPACE.
A PUBLIC DBSPACE can only be dropped, locked, or altered by a user with the proper authority.
Contact a user in your installation with the required authority and request the drop or alter action.
SQLCODE: -00708 Database: SQL/DS QMF Function: SQL Query
This DBSPACE contains system catalog tables.
No user can drop a DBSPACE containing system catalog tables.
Don't attempt to drop this DBSPACE.
SQLCODE: -00709 Database: SQL/DS QMF Function: SQL Query
The PRIVATE DBSPACE needed by your query is in use.
A PRIVATE DBSPACE can be accessed by only one user at any time. The table you requested in your query is in a PRIVATE DBSPACE now in use.
Run your query again when the PRIVATE DBSPACE is available.
SQLCODE: -00710 Database: SQL/DS QMF Function: SQL Query
There is not enough room in INTERNAL DBSPACEs to run the query.
QMF was not able to acquire sufficiently many, or sufficiently large, INTERNAL DBSPACEs. You may be able to simplify your query or break it up into two queries or more.
Ask your QMF administrator to acquire more INTERNAL DBSPACE for QMF.
SQLCODE: -00712 Database: SQL/DS QMF Function: SQL Query
An arithmetic operation in the SQL statement has resulted in an error.
You are trying to use a view, but an arithmetic operation in the subselect clause of the view definition has resulted in an error. The exception type is &V1, the operation type is &V2, and the data type is &V3.
Contact the owner of the view to examine the arithmetic operation and the columns within the subselect clause of the view to determine what data may be causing the program exception.
SQLCODE: -00801 Database: SQL/DS QMF Function: SQL Query
An Arithmetic operation in the SQL command has resulted in an error.
The SQL command attempted an Arithmetic operation such as Multiplication or Division. However, the computer detected that one or more of the values in the columns selected was invalid. For example: the result of multiplication exceeds internal computer storage or division-by-zero.
Examine the Arithmetic operation and the columns within the command to determine what data may be causing the program exception.
SQLCODE: -00802 Database: SQL/DS QMF Function: SQL Query
Duplicate value in a unique index column.
One of the columns into which you are inserting or updating a new value contains that same value already. That column is a 'Unique Index' column. Unique Index columns cannot have duplicate values.
Change the value so that it does not duplicate a value already existing. Run your query again.
SQLCODE: -00803 Database: SQL/DS QMF Function: SQL Query
The package &V1 is not found in the catalog table.
When SQL/DS tried to run the QMF program, it could not find the package in the catalog table SYSTEM.SYSACCESS. This can happen because:
Refer to the SQL/DS Messages and Codes manual for a detailed explanation and report this problem to your QMF administrator.
SQLCODE: -00805 Database: SQL/DS QMF Function: SQL Query
You do not have authorization to modify system catalogs.
You cannot modify system catalogs unless you have been granted authority. You may read the system catalogs and retrieve data using queries or DISPLAY commands.
Follow your QMF administrator procedures if authority is required.
SQLCODE: -00808 Database: SQL/DS QMF Function: SQL Query
Row is too long.
The result of your insert or update operation would be to create a row longer than is allowed. The maximum length is 4070 positions, unless there are LONG VARCHAR or LONG VARGRAPHIC columns.
Change your query to create a shorter row, and run the query again.
SQLCODE: -00809 Database: SQL/DS QMF Function: SQL Query
A subquery produces more than one value.
A subquery should not produce values from more than one column of a table; in many cases it should not produce values from more than one row. Use ALL, ANY, EXISTS, or IN with a subquery that produces more than one value.
Examples: WHERE DEPT = ANY (SELECT DEPTNUMB FROM Q.ORG) HAVING AVG(X) > ALL (SELECT X FROM Y) WHERE EXISTS (SELECT * FROM X WHERE N1 = N2)
Change your query and run it again.
SQLCODE: -00810 Database: SQL/DS QMF Function: SQL Query
You cannot LOCK a view.
LOCK is used only to lock a table or dbspace. Views are not stored as tables are, and cannot be locked.
You may LOCK one or more of the tables that make up the view.
SQLCODE: -00813 Database: SQL/DS QMF Function: SQL Query
Cannot LOCK a system catalog table or a system DBSPACE.
Your LOCK statement attempted to LOCK a system catalog or a DBSPACE containing the system catalog tables. No user, regardless of authority, can LOCK these items.
If exclusive access to the systems catalogs is required, contact your QMF administrator and request exclusive use of the database. LOCK is not necessary if no other users are active.
SQLCODE: -00814 Database: SQL/DS QMF Function: SQL Query
CONNECT denied by accounting user exit routine.
Your attempt to connect to SQL/DS was rejected by your installation's accounting user exit routine.
See your QMF administrator.
SQLCODE: -00815 Database: SQL/DS QMF Function: SQL Query
You cannot perform this operation with a system catalog.
Your request specified a system catalog. Users cannot delete from a system catalog, add a primary or foreign key to a system catalog, or refer to a system catalog as a parent of a foreign key.
To drop the object "name1" from the database, give the command ERASE name1.
SQLCODE: -00823 Database: SQL/DS QMF Function: SQL Query
The portion of the database you require is in use.
The object you need in the database cannot be accessed until another user has completed processing.
End your QMF session and sign on again at a later time.
SQLCODE: -00911 Database: SQL/DS QMF Function: SQL Query
The portion of the database you require is in use.
The object you need in the database cannot be accessed until another user has completed processing.
End your QMF session and sign on again at a later time.
SQLCODE: -00912 Database: SQL/DS QMF Function: SQL Query
A CANCEL request has been issued.
The CANCEL could have been issued by the user or by the system. The CANCEL issued by the system is a result of reaching the limit on lock request blocks.
Redo your changes as necessary. If you did not issue the CANCEL request, and you continue to get SQLCODE -914, contact your system programmer about increasing the NLRBU or the NLRBS parameters when starting the application server.
SQLCODE: -00914 Database: SQL/DS QMF Function: SQL Query
Your query was not processed because of the system work load.
Your query cannot be processed now because of the work load on the database system.
Continue with another operation and try to run your query at a later time. Contact your QMF administrator for more details about the current system work load.
SQLCODE: -00915 Database: SQL/DS QMF Function: SQL Query
Your query was not processed because of operator action.
The system operator interrupted the processing of your query. This was not due to an error in the query.
Run the query again.
SQLCODE: -00916 Database: SQL/DS QMF Function: SQL Query
The database manager program ran out of storage.
The database manager program does not have enough virtual storage to run your query.
Try later when there is less activity on QMF. If the condition persists, inform your QMF administrator.
SQLCODE: -00930 Database: SQL/DS QMF Function: SQL Query
The communications path to &V1. is not available.
You cannot access database &V1. for one of the following reasons:
Verify that the database name, &V1., is correct. If not, use a correct database name and retry your request.
The limit on the number of connections allowed to the SQL/DS virtual machine is set by the MAXCONN value in the SQL/DS virtual machine directory. If this limit has been exceeded, try your request later when the system activity is lighter. If this condition occurs frequently, contact your QMF administrator to get the MAXCONN value increased.
If the "CONNECT TO <location>" command is supported, QMF may have reconnected you to the current location. If so, you can continue to use QMF. If QMF cannot reconnect you, the Lost Connection Prompt panel prompts you to connect to another location.
SQLCODE: -00933 Database: SQL/DS QMF Function: SQL Query
The database manager program ran out of storage.
The database manager program does not have enough virtual storage to run your query.
Try later when there is less activity on QMF. If the condition persists, inform your QMF administrator.
SQLCODE: -00939 Database: SQL/DS QMF Function: SQL Query
The database &V1 is not ready or cannot be found.
You cannot access the database for one of the following reasons:
Verify that the database name, &V1., is correct. If not, use a correct database name and retry your request.
If the "CONNECT TO <location>" command is supported, QMF may have reconnected you to the current location. If so, you can continue to use QMF. If QMF cannot reconnect you, the Lost Connection Prompt panel prompts you to connect to another location.
SQLCODE: -00940 Database: SQL/DS QMF Function: SQL Query
The database manager program ran out of storage.
The database manager program does not have enough virtual storage to run your query.
Try later when there is less activity on QMF. If the condition persists, inform your QMF administrator.
SQLCODE: -00942 Database: SQL/DS QMF Function: SQL Query
The QMF virtual machine, &V2, cannot access database &V1..
The QMF virtual machine is not properly defined. The file ARISRMBT MODULE, on the QMF machine's A-disk, does not describe the database program that QMF is attempting to access.
Tell your QMF administrator about this message and wait for their response. There is nothing you can do until the QMF virtual machine is properly defined.
SQLCODE: -00943 Database: SQL/DS QMF Function: SQL Query
Your view cannot be created because all the DBSPACES for access modules are full.
Because all DBSPACEs for access modules are full, another DBSPACE for access modules must be acquired before you can create the view successfully. A DBSPACE might be full if all the available access modules in the DBSPACE are used, or no more free space is available in the DBSPACE.
Contact your QMF administrator to obtain an additional DBSPACE for access modules, and run your query again.
SQLCODE: -00945 Database: SQL/DS QMF Function: SQL Query
Your view cannot be created because there is not enough room in DBSPACE number &V1..
Your view could not be created because the database found that DBSPACE number &V1 is full. A DBSPACE might be full if all the available access modules in the DBSPACE are used or no more space is available in the DBSPACE.
Contact your QMF administrator to obtain an additional DBSPACE for access modules, and run your query again.
SQLCODE: -00946 Database: SQL/DS QMF Function: SQL Query
Your connection to SQL/DS was severed because of operator action.
The SQL/DS virtual-machine operator entered the FORCE command to cause ROLLBACK of the current logical unit of work and to sever your connection to the SQL/DS system. The userid, password, and database name are reset to their default values.
You can continue. Any explicit CONNECTs you have issued have been lost. You must issue another explicit CONNECT request, using the same USER ID, to reestablish your original connection.
SQLCODE: -00948 Database: SQL/DS QMF Function: SQL Query
Buffer too small to contain SQL statement.
Follow the directions in the referenced message.
Internal error detected in module &1.
This is a system error. Please see your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Invalid function code of '&1' encountered as input to DI function.
Follow the directions in the referenced message.
Invalid data type of '&1' returned from DBM.
Follow the directions in the referenced message.
See DSQ10078
Follow the directions in the referenced message.
See DSQ10012
Follow the directions in the referenced message.
Unexpected failure on 'DESCRIBE'.
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
DESCRIBEd statement is not a 'SELECT'.
Follow the directions in the referenced message.
Row from database is longer than 32767 characters.
The rows selected by your query are too long to process.
Eliminate something from the list of columns selected so that a data row is shorter than 32,767 characters. The minimum width for each column is two characters plus the data length. Columns wider than 254 characters are cut off by QMF as needed to fit the limit of 32,767.
Free storage failed.
Follow the directions in the referenced message.
See DSQ10317
Follow the directions in the referenced message.
Row from database is longer than 32,767 characters.
The rows selected by your &V1 command are too long to process.
Write and run a query that will use fewer than all the columns of the table -- less than 32,767 characters. The minimum width for each column is two characters plus the data length. Columns wider than 254 characters are cut off by QMF as needed to fit the limit of 32,767.
Free storage failed.
Follow the directions in the referenced message.
See DSQ10012
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
See DSQ10012
Follow the directions in the referenced message.
Data type &V1 is not supported.
One of the columns in the table that you referenced has a data type of &V1 which is not supported.
Data type &V1 is supported in QMF DRAW command and Table Editor only. You are not able to reference data type &V1 in any other situations.
See DSQ10093
Follow the directions in the referenced message.
Invalid function code of '&1' encountered as input to DI function.
Follow the directions in the referenced message.
Invalid data type of '&1' returned from DBM.
Follow the directions in the referenced message.
See DSQ10078
Follow the directions in the referenced message.
See DSQ10012
Follow the directions in the referenced message.
Unexpected failure on 'DESCRIBE'.
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
DESCRIBEd statement is not a 'SELECT'.
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
See DSQ10012
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
See DSQ10093
Follow the directions in the referenced message.
Required storage could not be allocated.
This is a system error. Please see your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Free storage failed.
Follow the directions in the referenced message.
Creation of template tree failed.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
A selection expression could not be added.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Error calling RM - Function(&1) CRC(&2) CSI(&3).
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Internal error preparing to call Repository Manager.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Error calling RM - Function(&1) CRC(&2) CSI(&3).
Follow the directions in the referenced message.
Creation of template tree failed.
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
Internal error preparing to call Repository Manager.
Follow the directions in the referenced message.
Invalid data was received from Repository Manager.
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Free storage failed.
Follow the directions in the referenced message.
Error calling RM - Function(&1) CRC(&2) CSI(&3) Return code(&4).
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Invalid data was received from Repository Manager.
Follow the directions in the referenced message.
Internal error preparing to call Repository Manager.
Follow the directions in the referenced message.
Error calling RM - Function(&1) CRC(&2) CSI(&3) Return code(&4).
Follow the directions in the referenced message.
Internal error preparing to call Repository Manager.
Follow the directions in the referenced message.
Invalid data was received from Repository Manager.
Follow the directions in the referenced message.
Required storage could not be allocated.
Follow the directions in the referenced message.
Error calling RM - Function(&1) CRC(&2) CSI(&3).
Follow the directions in the referenced message.
Error calling RM - Function(&1) CRC(&2) CSI(&3) Return code(&4).
Follow the directions in the referenced message.
Error occurred while resetting the query, error(&1).
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Error occurred while resetting the data, error(&1).
This is a system error. See your system administrator for assistance, or consult the Installing and Managing QMF manual for your operating system.
Free storage failed.
Follow the directions in the referenced message.
Internal error preparing to call Repository Manager.
Follow the directions in the referenced message.
Invalid data was received from Repository Manager.
Follow the directions in the referenced message.
Internal error preparing to call Repository Manager.
Follow the directions in the referenced message.
Free storage failed.
Follow the directions in the referenced message.
Internal error preparing to call Repository Manager.
Follow the directions in the referenced message.
See DSQ10012
Follow the directions in the referenced message.
Internal error detected in module &1.
Follow the directions in the referenced message.
Invalid function code of '&1' encountered as input to DI function.
Follow the directions in the referenced message.
Internal error detected in module &1.
Follow the directions in the referenced message.
Your query is too long or too complex.
The QBE query results in a SQL statement that is too long or too complex to be interpreted. It can be simplified by reducing the number of ...
Shorten your query or rewrite it as more than one query. Consider writing a query that produces a table of intermediate results. Save that table, and write a second query that uses it to produce your final result.
SQLCODE: -00101 Database: DB2 QMF Function: QBE
&V1 starts with a digit, but is not a valid number.
&V1 starts with a digit, but is not a valid integer, decimal, or floating-point number. If it is meant to be a:
Change &V1 and run the query again.
SQLCODE: -00103 Database: DB2 QMF Function: QBE
A NULL, expression, or comparison in your query is invalid.
If your query uses NULL, make sure that it is used to the right of an =. Also make sure that it is not part of an expression, or a condition that contains an expression.
If your query uses I., and the I. row contains no links to other rows, make sure that only constants are used in the I. row.
If your query uses U., make sure that columns containing a U. do not contain a comparison.
Correct any invalid use of NULL, remove an expression from a row that has an I., or remove a comparison from a column that has a U. operator.
SQLCODE: -00104 Database: DB2 QMF Function: QBE
Name &V1 contains an invalid character.
The names for databases, storage groups, tablespaces, and bufferpools can contain only upper-case alphabetic, national (*, &&, or @), or numeric characters. The first character must be alphabetic or a national character.
Correct the invalid character in name &V1 and run the query again.
SQLCODE: -00113 Database: DB2 QMF Function: QBE
A row with D., I., or U. can't link to a row of the same table.
Any row containing a D., I., or U. cannot be linked to another row if both refer to the same table.
Remove the link and run the query again.
SQLCODE: -00118 Database: DB2 QMF Function: QBE
Query has an invalid reference to a view.
A column used with GROUP BY in the definition of a view cannot be updated or used in a condition. A column defined by a built-in function cannot be updated.
Incorrect example:
CREATE VIEW VJ(A, B) AS
SELECT JOB, AVG(COMM)
FROM Q.STAFF GROUP BY JOB
VJ | A | B |
-----+-----+---|
| MGR | |
The query is incorrect because
column A is used in an implied
condition.
In addition, neither column A
nor B may be used with U..Write your query to access the table that the view is based on.
SQLCODE: -00120 Database: DB2 QMF Function: QBE
You cannot modify a column twice in the same query.
"Modify" includes insert (I.) and update (U.). For example, in the following invalid query, the column 'YEARS' cannot be modified more than once.
Incorrect:
* *
Q.STAFF | ID | YEARS | JOB | YEARS |
--------+------+-------+-------+-------|
I. | 400 | 7 | CLERK | 8 |Change the query and run it again.
SQLCODE: -00121 Database: DB2 QMF Function: QBE
The parameter in position &V1 must be a constant or keyword.
The parameter in position &V1 of the function &V2 is not a constant when it is required to be a constant or a keyword when it is required to be a keyword.
Correct the function call and run the query again.
SQLCODE: -00123 Database: DB2 QMF Function: QBE
More than one UNQ. or COUNT. reference to a row.
A row may contain no more than one UNQ. or CNT. reference. The following invalid query has a CNT. and a UNQ. reference to the row in the Q.STAFF table.
Invalid
Query:
Q.STAFF | DEPT | SALARY | YEARS |
--------+------+--------+-------|
| P.G. | _S | _Y |
| | CONDITIONS |
|----------+--------------------|
| P.CNT._S | AVG.UNQ._Y > 5 |Correct your query and run it again.
SQLCODE: -00127 Database: DB2 QMF Function: QBE
Query uses more than 15 table references.
One query may not make more than 15 references to tables.
Divide your query into two or more queries, each with 15 or fewer table references.
SQLCODE: -00129 Database: DB2 QMF Function: QBE
LIKE has incompatible data types.
If the column name is of type character, the expression at the right of LIKE or NOT LIKE must be of type character. If the column name is of type graphic, the expression at the right of LIKE or NOT LIKE must be of type graphic.
Check the data type of every operand and run the query again.
SQLCODE: -00131 Database: DB2 QMF Function: QBE
A wide character column is used incorrectly.
Several restrictions exist when using a column that has a character data type and a width greater than 254 characters. The column cannot be used in search conditions, in sorting, or with arithmetic operations. Values used to insert or update must be constants; they cannot come from subqueries.
In QBE queries, the only entries that may be used in the column are the operators P., I., or U..
Change your use of any wide character column or remove it, and run the query again.
SQLCODE: -00134 Database: DB2 QMF Function: QBE
A table cannot be sorted because the combined sort key is too long.
A single combined sort key is derived from one of the following:
If the length of the combined sort field exceeds 4000, the table cannot be sorted.
Reduce the length of the combined sort key.
SQLCODE: -00136 Database: DB2 QMF Function: QBE
You cannot modify the data in this view.
You cannot use INSERT, UPDATE, or DELETE a view that:
Write separate queries to modify the tables used to create the view.
SQLCODE: -00150 Database: DB2 QMF Function: QBE
Column &V1 cannot be changed.
You cannot use INSERT, UPDATE, or DELETE (in SQL) or I., U., or D. (in QBE) to change a column in:
Write separate queries to modify the tables used to create the view.
SQLCODE: -00151 Database: DB2 QMF Function: QBE
Query uses a view defined by grouping.
A view is defined by grouping if its definition uses GROUP BY or HAVING. Such a view may not be used in a query along with any other view or table.
Consider doing something like this:
SQLCODE: -00155 Database: DB2 QMF Function: QBE
Insert or update value does not satisfy view definition.
WITH CHECK OPTION was used in the definition of the view whose data you are trying to change. All attempts to insert or update rows in the view are checked to make sure that the results will conform to the definition of the view. Some value in your query does not satisfy a condition in that definition.
Examine the definition of the view to determine why the change was rejected, and change the value in the query.
SQLCODE: -00161 Database: DB2 QMF Function: QBE
The datetime value &V1 is invalid.
The string representation of a valid DATE has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIME has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIMESTAMP has the following format:
'yyyy-mm-dd-hh.mm.ss.nnnnnn'
Correct the syntax for the datetime value and run the query again.
SQLCODE: -00180 Database: DB2 QMF Function: QBE
The datetime value is not a valid value.
The string representation of a datetime value contains a value which is out of range. The proper ranges for datetime values are as follows:
Years - 1 to 9999 Months - 1 to 12 Days - 1 to 31 Hours - 0 to 24 Minutes - 0 to 59 Seconds - 0 to 59
Correct the datetime value and run the query again.
SQLCODE: -00181 Database: DB2 QMF Function: QBE
An arithmetic expression with a datetime value is invalid.
The specified arithmetic expression contains an improperly used datetime value or simple duration. Some correct examples are:
Q.PROJECT | STARTD | |
----------+--------+------------------|
| _D | P._D + 10102433. |Check datetime value and run the query again.
SQLCODE: -00182 Database: DB2 QMF Function: QBE
An arithmetic operation on a date or timestamp has a result that is invalid.
The result of an arithmetic operation is a date or timestamp that is not within the valid range. Valid dates are between 0001-01-01 and 9999-12-31.
Correct the datetime value and run the query again.
SQLCODE: -00183 Database: DB2 QMF Function: QBE
The date or time value cannot be formatted.
One of the following has occurred:
Either change your string representation of the date or time value to be one of the recognized formats, or contact your QMF administrator for assistance in making the local date or time routine available to the database.
SQLCODE: -00185 Database: DB2 QMF Function: QBE
&V1 could not be found.
The query refers to &V1.. Nothing with this name exists in the database.
Check for a spelling error.
SQLCODE: -00204 Database: DB2 QMF Function: QBE
Column name &V1 is not in table &V2..
You used column name &V1.. It was not found in table &V2.. You may have misspelled the name, or the table name may need to be qualified.
Verify that the column name and owner are correct and spelled correctly.
SQLCODE: -00205 Database: DB2 QMF Function: QBE
Column &V1 is not in the table named.
&V1 appears as a column name in an example table, but it is not a column in that table in the database.
Change the column name. Give the command "DRAW tablename" (where "tablename" is the name of the table) to get an example table with all the column names filled in correctly.
SQLCODE: -00206 Database: DB2 QMF Function: QBE
The location qualifier cannot be used.
The name you specified has a location qualifier. A three-part object name cannot be used until the local location name is defined.
Remove the location qualifier and retry your query. See your QMF administrator to make sure you are using the correct database, or to define the local location name.
SQLCODE: -00250 Database: DB2 QMF Function: QBE
&V1 is not a valid location name.
&V1 contains an alphabetic extender (#, @, $). Alphabetic extenders are not allowed in location names.
Correct the location name and try again.
SQLCODE: -00251 Database: DB2 QMF Function: QBE
Function is not supported (reason code = &V1).
The statement cannot be processed because it violates a restriction as indicated by the following reason codes:
The action corresponding to the reason code is:
SQLCODE: -00270 Database: DB2 QMF Function: QBE
Invalid context for identifier &V1..
Something in your query that might be valid in a query submitted to the preprocessor is not valid in QMF. The error may be in the identifier or in some reserved word preceding it.
Incorrect:
WHERE NAME IN (JONES, SMITH)
(Write 'JONES' and 'SMITH' in single
quotes.)
Incorrect:
WHERE NAME = :JONES
(":" is invalid.)
Incorrect:
SELECT NAME INTO TYPE
(INTO should be FROM.)Correct the query and run it again.
SQLCODE: -00312 Database: DB2 QMF Function: QBE
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00313 Database: DB2 QMF Function: QBE
A character string could not be converted due to undefined CCSIDs.
Your SQL statement referenced a character string with a coded character set ID(CCSID) &V1 in a coded character set that differs from the current one. To use this character string at the current server, this character string must be translated from the source CCSID &V1 to the target CCSID &V2. However, this pair of CCSIDs conversion rule is not defined in the SYSSTRINGS system table. Therefore, the database system could not convert the character string to a code suitable for the application server.
Verify that the character columns and values you referenced are correct. If not, make the necessary change and try the query again. Otherwise, contact your QMF administrator.
SQLCODE: -00332 Database: DB2 QMF Function: QBE
Invalid use of the ON clause.
The ON clause is being used incorrectly for one of the following reasons:
Correct the syntax of the ON clause and run the query again.
SQLCODE: -00338 Database: DB2 QMF Function: QBE
Invalid data type in position &V1..
Some SQL data types are not supported by the application requester. &V1 is the position of the first element with an invalid data type in the SQLDA. A common cause for this error is that the application requester has attempted to describe large object data residing at the application server. Some of the SQLTYPEs that can cause this error are: LOB, BLOB, CLOB, and DBLOB.
Remove the invalid data types and run the query again.
SQLCODE: -00351 Database: DB2 QMF Function: QBE
A ROWID column has an invalid value.
An attempt to insert an invalid value into a ROWID column was made.
Only ROWID values previously generated by DB2 can be used as values for insertion into a ROWID column. Alternatively, insert the row specifying the keyword DEFAULT for the ROWID column value or remove the ROWID column from the insert column-list.
SQLCODE: -00399 Database: DB2 QMF Function: QBE
Data of different types must not be used in an expression or condition.
You used data of different types in an expression or condition. For example, the following is not valid because character data (SMITH) is compared to numeric data (_SALARY):
Invalid _SALARY = SMITH Example:
Change any expression or condition so that data of the same type is used.
SQLCODE: -00401 Database: DB2 QMF Function: QBE
An arithmetic expression contains character data.
Arithmetic expressions, and expressions using the built-in functions AVG and SUM, may use only numeric data. Some expression in your query uses character data.
Rewrite the expression, using only numeric data, and run your query again.
SQLCODE: -00402 Database: DB2 QMF Function: QBE
Value given is too long for column &V1..
The maximum width of column &V1 is less than the number of characters you are trying to put into it.
Change the value to fit the column and run the query again.
SQLCODE: -00404 Database: DB2 QMF Function: QBE
Numeric value &V1 is outside the allowable range for your column.
&V1 is outside the range of values allowed for the associated column.
The proper ranges for SQL values are as follows:
FLOAT ...... -7.2E75 to -5.4E-79, 0,
5.4E-79 to 7.2E75
INTEGER .... -2147483648 to 2147483647
SMALLINT ... -32768 to 32767
DECIMAL .... The range depends on the
precision and scale of the
column. For example, if
the value is being
specified for a decimal
column defined with
precision = 5 and
scale = 2, the range is
-999.99 to 999.99.Change &V1 and continue.
SQLCODE: -00405 Database: DB2 QMF Function: QBE
Numeric value is outside allowable range for column.
Your query specifies a column that has an incorrect numeric value. The value might be the result of an expression.
The proper ranges for SQL values are as follows:
FLOAT ...... -7.2E75 to -5.4E-79, 0,
5.4E-79 to 7.2E75
INTEGER .... -2147483648 to 2147483647
SMALLINT ... -32768 to 32767
DECIMAL .... The range depends on the
precision and scale of the
column. For example, if
the value is being
specified for a decimal
column defined with
precision = 5 and
scale = 2, the range is
-999.99 to 999.99.Change the numeric value for the column and rerun the query.
SQLCODE: -00406 Database: DB2 QMF Function: QBE
A column defined as NOT NULL may not contain a NULL.
Your query uses I. or U. in an attempt to enter a NULL into a column that is designated as NOT NULL. The following query attempts to insert a NULL into ID, but ID is defined as a NOT NULL column. Note that in an I. row, NULL is entered for
Q.STAFF | ID | NAME | DEPT |
-------+----+------------+-------|
I. | | 'J.Harris' | |
| YEARS |
|-------|
| NULL |Specify a value for the NOT NULL column.
SQLCODE: -00407 Database: DB2 QMF Function: QBE
An update or insert value is incompatible with the data type of its associated column.
Your query attempts to insert or update a column with a value from another column that is incompatible. The following invalid query attempts to insert into a numeric column (ID) a value from a character column (NAME).
Invalid
Query:
MYSTAFF | ID | NAME |
--------+----------+----------|
I. | _N | _N |
Q.STAFF | ID | NAME |
--------+----------+----------|
| _I | _N |Use a compatible value.
SQLCODE: -00408 Database: DB2 QMF Function: QBE
A name in your query starts or ends with a blank.
Names must not begin or end with a blank. In the following invalid query, the name, " YEARS", is invalid because it contains a leading blank.
Invalid
Query:
Q.STAFF | NAME | " YEARS" |
--------+------+----------|
P. | | |Remove the leading or trailing blank from the name.
SQLCODE: -00409 Database: DB2 QMF Function: QBE
Value starting '&V1' is longer than 30 characters.
A floating-point constant cannot be more than 30 characters long.
Round &V1 so that it can be written with 30 characters or fewer.
SQLCODE: -00410 Database: DB2 QMF Function: QBE
Invalid use of "USER". USER was used in an expression, compared to numeric data or graphic data, or not used in a condition.
USER may be used only in a condition. Additionally, it may not be compared to numeric data or graphic data. The following is an example of a valid use of USER.
Q.STAFF | NAME | SALARY | COMM | YEARS | --------+------+--------+------+-------| P. | USER | | | |
Correct the use of USER in your query and run the query again.
SQLCODE: -00411 Database: DB2 QMF Function: QBE
Arithmetic overflow during change of data type.
The result of an arithmetic or insert operation is not valid because arithmetic overflow occurred. For example, you may have tried to INSERT values with a data type of INTEGER into a column with data type of SMALLINT. Conversion is possible so long as the INTEGER values are small enough. But a value larger than 32767 will cause arithmetic overflow.
Change your operation and run the query again.
SQLCODE: -00413 Database: DB2 QMF Function: QBE
A LIKE operator in your query does not refer to character data or graphic data.
The LIKE operator may only be used with a column that has character data or graphic data. Your query uses a LIKE to refer to a column that does not have character or graphic data. For example,
Invalid Q.STAFF | NAME | SALARY |
Query: --------+------+-----------|
P. | | LIKE'20%' |Remove the LIKE reference to numeric data or datetime data and run the query again.
SQLCODE: -00414 Database: DB2 QMF Function: QBE
Data to be retrieved into the same column of two separate P. rows must have comparable definitions.
Your query contains 2 or more P. rows with data definitions that cannot be compared. This query unsuccessfully attempted to retrieve data into the same column. The data definitions for these P. rows must be comparable for the retrieval to succeed. Additionally, the columns to be retrieved into the same output column must have the same field procedure and column CCSID value, provided the columns to be retrieved have field procedures.
The following query attempts to retrieve NUMERIC data (DEPT) and LONG VARCHAR data (JOB) into the same column.
Invalid
Query:
Q.staff | DEPT | | JOB |
---------+---------+--------+---------|
| _D | P. _D | |
| | P. _J | _J |
Ensure that data retrieved into the same column have comparable definitions.
SQLCODE: -00415 Database: DB2 QMF Function: QBE
Data to be retrieved into the same column by two different P. rows must not refer to long variable character data.
Your query attempts to retrieve data into the same column from 2 sources, but at least one of those sources is data defined as long variable character data. The following is an example of such an invalid query.
Invalid MYTABLE | LONGVARCHAR1 |
Query: --------+--------------|
P. | |
P. | _L2 |
YOURTABLE | LONGVARCHAR2 |
----------+--------------|
| _L2 |
Remove the reference in the same column to long variable character data.
SQLCODE: -00416 Database: DB2 QMF Function: QBE
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00417 Database: DB2 QMF Function: QBE
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00418 Database: DB2 QMF Function: QBE
Decimal division is not possible with the values used.
Either the precision of the numerator or the scale of the denominator is too large for decimal division.
Change the precision or scale of your decimal division values and run the query again. Note that an integer or small integer value may have been converted to decimal for this calculation.
SQLCODE: -00419 Database: DB2 QMF Function: QBE
An invalid character string argument was used with the &V1 function.
A character string argument did not conform to the requirements of the function. For example, a character string passed to the DECIMAL function did not conform to the rules for forming an SQL integer or decimal constant.
Change the value of the argument so that it conforms to the requirements of the function.
SQLCODE: -00420 Database: DB2 QMF Function: QBE
Invalid use of DISTINCT or ALL with &V1..
The keyword DISTINCT or ALL was detected within the parentheses in a reference to the function &V1.. This function was recognized as a scalar function.
If a scalar function is being used then remove the keyword DISTINCT or ALL. It is invalid for a scalar function.
If a column function is being used, then there is a problem with function resolution. Check the value of special register CURRENT FUNCTION PATH. Also check the spelling of the function name and the number and types of parameters in both the query and the system catalog.
SQLCODE: -00441 Database: DB2 QMF Function: QBE
The function &V1 has too many arguments.
Too many arguments were specified in the reference to function &V1. The maximum allowable is 90.
Correct the statement by ensuring the correct number of arguments was used and run the query again.
SQLCODE: -00442 Database: DB2 QMF Function: QBE
This query exceeds a DB2 cost estimate limit.
DB2 has determined that the cost estimate for this query exceeds a limit specified in the Resource Limit Facility (DB2 governor) preventing the query from being run.
The details of the cost estimate for the query statement are:
If the cost category value is 'B', seek the assistant of your DB2 administrator, the DB2 catalog statistics or resource limit specification tables (RLST) might need updating.
If the SQL statement is consuming too much processor time, rewrite the statement to perform more efficiently and run the query again.
Things to check might be:
Some queries can be made simpler by removing the GROUP BY clause from the query and using the GROUP usage code in the QMF FORM instead.
Some queries will perform better by using advanced SQL syntax, such as Outer Join or the CASE expression,
For advanced analysis the EXPLAIN SQL statement can be used to gather information about the structure and execution performance of a query.
Refer to the SQL Reference for more information on Queries and the EXPLAIN statement.
Refer to the DB2 Administration manual for more information on tuning queries and writing efficient predicates and subqueries.
SQLCODE: -00495 Database: DB2 QMF Function: QBE
The query reference to a remote object is invalid.
One of the following invalid conditions exists:
Refer to the DB2 SQL Reference manual for more information on using remote objects.
SQLCODE: -00512 Database: DB2 QMF Function: QBE
The alias name &V1 cannot be defined on another local or remote alias.
The object indicated by &V1 exist at the location indicated. However, It is defined as an alias at at that location.
Modify the query to ensure that all object references are to tables or views at the indicated location.
SQLCODE: -00513 Database: DB2 QMF Function: QBE
The foreign key value is not valid.
An update or insert query specified a value for a foreign key. However, the value is not equal to any of the primary key values of the parent table.
If the name of the referential constraint for the foreign key was provided by the database, that name is as follows: &V1..&V2..
Use a value for the foreign key that matches one of the primary key values.
SQLCODE: -00530 Database: DB2 QMF Function: QBE
The primary key &V1 in a parent row cannot be updated.
Your update request specifies a value for the primary key of the table being updated, but the row identified by that primary key value has dependent rows associated with it. The value of a primary key in a parent row cannot be updated if the parent row has any dependent rows.
Make sure you selected the correct row to be updated. Before a primary key value in a parent row can be updated, the parent row must not have any dependent rows.
SQLCODE: -00531 Database: DB2 QMF Function: QBE
The row cannot be deleted because of a RESTRICT delete rule.
The delete operation attempted to delete a parent row. However, the row cannot be deleted because a delete rule of RESTRICT is associated with tables that can be affected by this deletion. Either the row has a dependent in a relationship with a delete rule of RESTRICT, or the deletion cascades to a row that is a dependent in a relationship with a delete rule of RESTRICT.
Make sure you selected the correct row to be deleted. If you did, delete any dependent rows with a delete rule of RESTRICT. Then delete the parent row.
SQLCODE: -00532 Database: DB2 QMF Function: QBE
Cannot insert multiple rows into a self-referencing table.
You cannot use I. to insert more than one row at a time into a self-referencing table.
Make sure the insert request inserts only one row of data.
SQLCODE: -00533 Database: DB2 QMF Function: QBE
Cannot update a primary key or unique constraint in multiple rows.
You cannot use U. to update a primary key or unique constraint in more than one row at a time.
Make sure the update request selects no more than one row of data.
SQLCODE: -00534 Database: DB2 QMF Function: QBE
The deletion is invalid because table &V1 can be affected.
You cannot use D. to delete from a table based on values in table &V1, because table &V1 can be affected by the deletion.
Do not attempt to delete from a table based on values in a table that can be affected.
SQLCODE: -00536 Database: DB2 QMF Function: QBE
Table &V1 has no primary index for the primary key.
You cannot use table &V1.. It has a primary key, but no primary index.
Define a primary index for the table before you refer to it.
SQLCODE: -00540 Database: DB2 QMF Function: QBE
You lack the authorization necessary to run your query.
Your QBE query uses one of the operators listed below, and requires the corresponding authorization on the appropriate tables.
D. -- DELETE I. -- INSERT P. -- SELECT U. -- UPDATE
See your QMF administrator to obtain the proper authorization for your query.
SQLCODE: -00551 Database: DB2 QMF Function: QBE
You lack the authorization necessary to run your query.
Your QBE query uses one of the operators listed below, and requires the corresponding authorization on the appropriate tables.
D. -- DELETE I. -- INSERT P. -- SELECT U. -- UPDATE
See your QMF administrator to obtain the proper authorization for your query.
SQLCODE: -00552 Database: DB2 QMF Function: QBE
&V1 cannot be used with this catalog object.
You cannot use INSERT, UPDATE, or DELETE with the catalog object specified in the SQL statement. You cannot use the DEFER YES option for indexes on catalog tables SYSINDEXES, SYSKEYS, and SYSINDEXPART.
Do not attempt this operation.
SQLCODE: -00607 Database: DB2 QMF Function: QBE
&V1 cannot be performed on system databases.
System databases cannot be the object of certain types of operations, including &V1..
Do not attempt this operation.
SQLCODE: -00618 Database: DB2 QMF Function: QBE
Too many columns specified in the unique key.
Your CREATE TABLE statement uses too many columns in the UNIQUE clause. The total number of columns specified must be exceed the database limits.
Reduce the totals number of key columns in the UNIQUE clause. Refer to the SQL Reference manual for database limits.
SQLCODE: -00642 Database: DB2 QMF Function: QBE
Procedure &V1 rejects the result.
&V1 is a procedure defined by your installation to edit or validate the results of queries. The result of your query did not meet some requirement of this procedure.
See your QMF administrator for descriptions of your installation's edit and validation procedures.
SQLCODE: -00652 Database: DB2 QMF Function: QBE
The maximum size of a table object has been exceeded.
One or more of the objects that make up a table has reached its maximum size. The storage objects that make up a table are:
Once a storage object has grown to its maximum size, it cannot be extended further.
To make existing space within the object available to store new data, you can:
SQLCODE: -00659 Database: DB2 QMF Function: QBE
A utility, the Resource Limit Facility, or the Distributed Data Facility is running.
If a system utility is running, it must complete execution before your query can be run. If the Resource Limit Facility is running, it must be stopped or switched to a different resource limit control table before your query can be run. If the Distributed Data Facility is running, it must be stopped before an object in the communications database can be dropped.
Wait for the utility to finish, or wait until the Resource Limit Facility stops or switches to a different resource limit control table, then run your query again. Or wait until the Distributed Data Facility stops, then drop the object.
SQLCODE: -00666 Database: DB2 QMF Function: QBE
Column &V1 violates installation defined field procedure. RT: &V2, RS: &V3, MSG: &V4..
A field procedure error has occurred on column &V1. Use return code (RT) to determine the problem:
4 Invalid value on encode or decode or
invalid column definition.
8 Invalid parameter value.
12 Field procedure error on any
function.Use reason code (RS) and message (MSG) token for additional information.
If it is not a field procedure error, determine the requirements imposed by the field procedure. If it is a field procedure error, examine the field procedure.
SQLCODE: -00681 Database: DB2 QMF Function: QBE
A column defined with a field procedure cannot be compared to another column with a different field procedure.
If a column with a field procedure is compared to another column, the two columns must have the same field procedure.
Correct the SQL statement and run the query again.
SQLCODE: -00686 Database: DB2 QMF Function: QBE
Column field types incomparable.
If a column with a field procedure is compared to another column, they must have the same field procedure and same field type. The comparison is performed on the encoded form of the values in the columns. For example, if the encoded values are numeric, their data types must be identical; if they are strings, their data types must be compatible.
Correct the SQL statement and run the query again.
SQLCODE: -00687 Database: DB2 QMF Function: QBE
Database &V1 is not a shared database on the owning subsystem.
You are trying to access an object in the database identified by &V1. That database is defined as ROSHARE READ on the subsystem that you are accessing. However, the database is not defined as ROSHARE OWNER on the owning subsystem. Therefore, the object cannot be accessed.
Verify that the correct object was specified.
SQLCODE: -00735 Database: DB2 QMF Function: QBE
DB2 auxiliary table cannot be referenced directly.
Data in an auxiliary table cannot be accessed by specifying the auxiliary table name. Data in an auxiliary table can only be accessed through operations on the base table.
Use the corresponding base table and re-run the query.
SQLCODE: -00766 Database: DB2 QMF Function: QBE
Attempted to insert a value into ROWID GENERATED ALWAYS column.
When inserting into a table, a value was specified for a ROWID GENERATED ALWAYS column &V1.. GENERATED ALWAYS columns should not be specified in the column-list for an insertion unless the corresponding entry in the VALUES list is DEFAULT.
Remove the ROWID column from the column-list or specify DEFAULT for the ROWID identifier column in the VALUES clause.
SQLCODE: -00798 Database: DB2 QMF Function: QBE
Division by zero was attempted.
The processing of a column or arithmetic expression resulted in division by zero.
Correct the statement and run the query again.
SQLCODE: -00801 Database: DB2 QMF Function: QBE
An Arithmetic operation in the SQL command has resulted in an error.
The SQL command attempted an Arithmetic operation such as Multiplication or Division. However, the computer detected that one or more of the values in the columns selected was invalid. For example: the result of multiplication exceeds internal computer storage or division-by-zero.
Examine the Arithmetic operation and the columns within the command to determine what data may be causing the program exception.
SQLCODE: -00802 Database: DB2 QMF Function: QBE
Duplicate value in a unique index column.
One of the columns into which you are inserting or updating a new value contains that same value already. That column is a 'Unique Index' column. Unique Index columns cannot have duplicate values.
Change the value so that it does not duplicate a value already existing. Run your query again.
SQLCODE: -00803 Database: DB2 QMF Function: QBE
A program is not found in the current plan.
QMF executed the application plan &V2, which needs the program &V1..
If you are accessing remote data, the name of your plan may have been changed to DISTSERV.
This program was not found in the plan &V2.. The following are some causes of this error:
Refer to the DB2 Messages and Codes manual for a detailed explanation and report this problem to your QMF administrator.
SQLCODE: -00805 Database: DB2 QMF Function: QBE
Your query uses too many columns.
You cannot select or insert more than the maximum number of columns allowed by the database from any table or set of tables in a single query.
Rewrite the query to use fewer columns. If the query is in SQL, check statements like "SELECT * FROM A, B, C", which selects every column from each of tables A, B, and C.
SQLCODE: -00840 Database: DB2 QMF Function: QBE
You must connect to a location to continue using QMF.
Your database server is lost due to the previous error. If you wish to continue using QMF, you may use the QMF Lost Connection Prompt panel to connect to another location, or you can choose to exit QMF.
If you choose to connect to another location, enter the proper values to connect to a valid location. Otherwise, you must exit QMF.
SQLCODE: -00900 Database: DB2 QMF Function: QBE
Unsuccessful execution caused by an unavailable resource. Reason code &V1, type of resource &V2, and resource name &V3..
The request could not be executed because the resource '&V3' of type '&V2' was not available at this time for the reason indicated by '&V1'. See DB2 Messages and Codes manual for a detailed explanation of the reason code &V1..
This may be a temporary condition.
Some common causes for this condition are:
If you have access to the MVS JES log information, browse the log records for this unavailable resource error.
If you need to refer to a local object, but you are currently connected to a remote location, you can connect to the local location and then reference the local object.
If the resource is temporarily unavailable, issue your query again.
If DDF is stopped and the Lost Connection prompt is displayed, you may only be able to reconnect to the local DB2.
If the error condition persists, contact your QMF administrator for assistance.
SQLCODE: -00904 Database: DB2 QMF Function: QBE
Unsuccessful execution because DB2 resource limit was exceeded. Resource name = &V1., limit = &V2..
The execution of the SQL statement was terminated because a DB2 resource limit was exceeded.
To avoid exceeding the DB2 resource limit, consider simplifying the SQL statement, restructuring the tables and indexes, or changing the resource limits. For further assistance, contact your QMF administrator.
SQLCODE: -00905 Database: DB2 QMF Function: QBE
Unable to determine if the updates made at a remote location were successful or not.
A system error occurred at the remote location where the updates were made, or a communication failure with the remote location occurred. The error occurred after the request to commit the updates was sent to the remote location. The error prevents DB2 from determining whether or not the commit operation succeeded. If the commit succeeded, updates will appear in the database. If the commit failed, the updates will have been backed out.
After communication has been reestablished with the remote location, query the data to determine whether or not the commit operation was successful.
SQLCODE: -00907 Database: DB2 QMF Function: QBE
The portion of the database you require is in use.
The object you need in the database cannot be accessed until another user has completed processing.
End your QMF session and sign on again at a later time.
SQLCODE: -00911 Database: DB2 QMF Function: QBE
The portion of the database you require is in use.
The object you need in the database cannot be accessed until another user has completed processing.
End your QMF session and sign on again at a later time.
SQLCODE: -00913 Database: DB2 QMF Function: QBE
You must connect to a location to continue using QMF.
Your database server is lost due to the previous error. If you wish to continue using QMF, you may use the QMF Lost Connection Prompt panel to connect to another location, or you can choose to exit QMF.
If you choose to connect to another location, enter the proper values to connect to a valid location. Otherwise, you must exit QMF.
SQLCODE: -00918 Database: DB2 QMF Function: QBE
There is not enough storage available to process the statement.
A request was made to the database manager that required another memory page but no more pages are available to the database manager. Some possible causes are:
Correct the problem and run the query again.
SQLCODE: -00930 Database: DB2 QMF Function: QBE
You cannot access remote data while DDF is inactive.
Your query attempted to access data at the remote database, but Distributed Data Facility is not started. Your query is rolled back.
You may continue using QMF. If problem persists, contact your QMF administrator.
SQLCODE: -00948 Database: DB2 QMF Function: QBE
The &V2. value of &V3. is invalid.
Your &V1 command generated a SQL statement that specifies a data type that has an incorrect &V2 specification of &V3.. The &V2 specification for that data type must not exceed the limit.
Some possible causes of your query error are:
Verify that the input data for your &V1 command does not exceed the database limit. If so, change the &V2 specification so that it is within the data type limit, and rerun the command. See the SQL Reference manual for your database for a detailed explanation on the data type limits.
SQLCODE: -00060 Database: DB2 QMF Function: Command
Name &V2 contains an invalid character.
The names for databases, storage groups, tablespaces, and bufferpools can contain only upper-case alphabetic, national (*, &&, or @), or numeric characters. The first character must be alphabetic or a national character.
Correct the invalid character in name &V2 (check for lower-case characters) and execute your command again. If you are using SAVE DATA or IMPORT TABLE to create a new table, the name in error may be the table space name from the profile. If so, use DISPLAY PROFILE to see this SPACE value.
SQLCODE: -00113 Database: DB2 QMF Function: Command
You cannot use this view.
Your command names a view whose definition has one of these errors:
Correct: SELECT DEPT, AVG(SALARY)
FROM Q.STAFF GROUP BY DEPTCorrect: SELECT DEPT, JOB, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT, JOB (Not: GROUP BY DEPT)
Correct: HAVING MIN(YEARS) > 6
(Not: HAVING YEARS > 6) Correct: SUM (UNITS * RATE)
(Not: SUM(UNITS) * RATE)Change the definition of the view and enter the command again.
SQLCODE: -00119 Database: DB2 QMF Function: Command
You cannot use &V1 with this view.
You cannot name a view in a command if executing the command would require QMF to...
- data from more than one table - a column defined by a built-in function (like SUM(COMM)) - data selected by DISTINCT or GROUP BY
Pick a new name for the data, give the command "SAVE DATA AS newname", and so create a new table.
SQLCODE: -00150 Database: DB2 QMF Function: Command
Column &V2 cannot be changed.
Your &V1 command cannot be executed with the replace option, because that changes a column in:
Choose a new name for the data to be saved, and so save it as a new table.
SQLCODE: -00151 Database: DB2 QMF Function: Command
Your &V1 command referenced an invalid DATETIME value.
Your &V1 command referenced an invalid DATETIME value. This may happen if your command references a view which contains an invalid DATETIME value in the view definition. The string representation of a valid DATE has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIME has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIMESTAMP has the following format:
'yyyy-mm-dd-hh.mm.ss.nnnnnn'
If your &V1 command references a view, correct the syntax for the DATETIME value in the view definition and run the &V1 command again. Contact your QMF administrator for further help.
SQLCODE: -00180 Database: DB2 QMF Function: Command
&V2 cannot be found.
The name "&V2" was found in your &V1 command or as a result of processing your &V1 command, but nothing with that name can be found in the database.
Check for a spelling error. To see a list of forms, procedures, queries, or tables you can use, give one of these commands:
LIST FORMS LIST PROCS LIST QUERIES LIST TABLES
followed by the option (OWNER=ALL).
If you attempted to save a new table into the database, ensure that you have the correct SPACE value in your user profile.
SQLCODE: -00204 Database: DB2 QMF Function: Command
Column name &V1 is not in table &V2..
You used column name &V1.. It was not found in table &V2.. You may have misspelled the name, or the table name may need to be qualified.
Verify that the column name and owner are correct and spelled correctly.
SQLCODE: -00205 Database: DB2 QMF Function: Command
The location qualifier cannot be used.
The name you specified has a location qualifier. A three-part object name cannot be used until the local location name is defined.
Remove the location qualifier and retry your command. See your QMF administrator to make sure you are using the correct database, or to define the local location name.
SQLCODE: -00250 Database: DB2 QMF Function: Command
&V2 is not a valid location name.
One of the following has occurred:
Correct the location name and try again.
SQLCODE: -00251 Database: DB2 QMF Function: Command
The &V1. command cannot process the current data object.
Column number &V2. in the current data object is incompatible with the corresponding column of the target table. This incompatibility is due to running QMF from a DB2 environment where the ROWID datatype is not supported.
If column position &V2. is the last column in the data object, recreate the data object without that column and run the &V1. command again.
Otherwise, QMF must be run from a DB2 environment that supports the ROWID datatype before the desired QMF action can be completed. The ROWID datatype is supported by DB2 for OS/390 Version 6 and higher.
SQLCODE: -00301 Database: DB2 QMF Function: Command
A character string could not be converted due to undefined CCSIDs.
Your &V1 command referenced a character string that has a coded character set ID(CCSID) &V2 in a coded character set that differs from the current one. To use this character string at the current server, the character string must be translated from the source CCSID &V2 to the target CCSID &V3.
However, this pair of CCSIDs conversion rule is not defined in the SYSSTRINGS system table. Therefore, the database system could not convert the character string to a code suitable for the application server.
Verify that your &V1 command is correct. If not, make the necessary changes and re-issue the command. Otherwise, contact your QMF administrator.
SQLCODE: -00332 Database: DB2 QMF Function: Command
Unsupported data type in position &V2..
Some SQL data types are not supported by the application requester. &V2 is the position of the first element with an unsupported data type in the SQLDA. A common cause for this error is that the application requester connected to an application server and has attempted to describe the data type residing at the application server. Some of the SQLTYPEs that can cause this error are: CLOB, BLOB and DBCLOB.
Remove the unsupported data types and run the query again.
SQLCODE: -00351 Database: DB2 QMF Function: Command
Only one column defined as ROWID is allowed in a table.
Your &V1 command attempted to create a table with more than one ROWID column or to add a ROWID column to a table that already has one.
Do not attempt to save more than one column of ROWID data type in the data of the &V1 command.
SQLCODE: -00372 Database: DB2 QMF Function: Command
You cannot use &V1 with this view.
You cannot name a view in a command if executing the command would require QMF to...
- data from more than one table - a column defined by a built-in function (like SUM(COMM)) - data selected by DISTINCT or GROUP BY
Pick a new name for the data, give the command "SAVE DATA AS newname", and so create a new table.
SQLCODE: -00407 Database: DB2 QMF Function: Command
This query exceeds a DB2 cost estimate limit.
DB2 has determined that the cost estimate for this query exceeds a limit specified in the Resource Limit Facility (DB2 governor) preventing the query from being run.
The details of the cost estimate for the query statement are:
If the cost category value is 'B', seek the assistant of your DB2 administrator, the DB2 catalog statistics or resource limit specification tables (RLST) might need updating.
If the SQL statement is consuming too much processor time, rewrite the statement to perform more efficiently and run the query again.
Things to check might be:
Some queries can be made simpler by removing the GROUP BY clause from the query and using the GROUP usage code in the QMF FORM instead.
Some queries will perform better by using advanced SQL syntax, such as Outer Join or the CASE expression,
For advanced analysis the EXPLAIN SQL statement can be used to gather information about the structure and execution performance of a query.
Refer to the SQL Reference for more information on Queries and the EXPLAIN statement.
Refer to the DB2 Administration manual for more information on tuning queries and writing efficient predicates and subqueries.
SQLCODE: -00495 Database: DB2 QMF Function: Command
Your command reference to a remote object is invalid.
Your &V1 command refers to a remote object. The remote reference may be the result of using an alias. One of the following conditions exists:
SQLCODE: -00512 Database: DB2 QMF Function: Command
The foreign key value is not valid.
The table being replaced by your &V1 command has a foreign key. Your new data contains a value for the foreign key &V2..&V3. that is not equal to any of the primary key values of the parent table.
If the name of the referential constraint for the foreign key was provided by the database, that name is as follows: &V2..&V3..
You cannot replace the table with the new data. Consider saving your data as a new table.
SQLCODE: -00530 Database: DB2 QMF Function: Command
The table cannot be replaced because RESTRICT is specified.
The table you attempted to replace has a primary key defined. To replace the table, the existing rows, and with them the primary key, must be deleted. However, a value of the primary key cannot be deleted because RESTRICT was specified for one or more descendant tables.
Either save the data as a new table, or re-examine the constraint rules for all dependent tables.
SQLCODE: -00532 Database: DB2 QMF Function: Command
&V2 has no primary index for the primary key.
You cannot use the &V1 command with table &V2.. The table has a primary key, but no primary index.
Define a primary index for the table before you use the &V1 command with it.
SQLCODE: -00540 Database: DB2 QMF Function: Command
You lack the authorization necessary for this &V1 command.
You (the &V2 id) cannot issue this &V1 command because you do not have the authority to perform &V3 on object &V4..
For DRAW, DISPLAY, EXPORT, or PRINT, your id &V2 needs SELECT authority on the table or view.
You can use ERASE only with tables or views you own or have administrative authority.
To replace an existing table with SAVE or IMPORT, you need SELECT, DELETE and INSERT authorization on that table.
To create a new table with SAVE or IMPORT, you need the authority to perform &V3 on object &V4..
Contact your QMF administrator to obtain the proper authorization.
SQLCODE: -00551 Database: DB2 QMF Function: Command
You lack the authorization needed for this &V1 command.
For DRAW, DISPLAY, EXPORT, or PRINT, you need SELECT authorization on the table or view named.
You can use ERASE only with tables or views you own.
To replace an existing table with SAVE or IMPORT, you need SELECT, DELETE and INSERT authorization.
To create a new table with SAVE or IMPORT, you need the authorization to create the table you named.
Contact your QMF administrator to obtain the proper authorization.
SQLCODE: -00552 Database: DB2 QMF Function: Command
Remote update is disallowed in a READ-ONLY environment.
You have attempted to update, insert or delete data at a remote location, but your current operating environment allows remote read only. For example, you cannot update remote data in a CICS operating environment if server database does not support two-phase commit.
To access remote data in a READ-ONLY operating environment, you can use one of the following:
You can continue to use QMF. If you need to update remote data, switch to an operating environment that supports it; otherwise, contact your QMF administrator.
SQLCODE: -00571 Database: DB2 QMF Function: Command
&V2 is the name of a &V3 already in the database.
You assigned the name &V2 to a &V3.. But it names something existing in the database. A name cannot be used more than once.
Change the name &V2 and continue.
SQLCODE: -00601 Database: DB2 QMF Function: Command
Data length, scale, or precision for some column is invalid.
The DATA you are attempting to SAVE or the TABLE you are attempting to IMPORT contains a data length, or a decimal scale or precision that is either zero or greater than the maximum supported by the database.
If you are trying to SAVE DATA, and the data you want to save was retrieved by running a query, then the query most likely selected a column with data length zero. Change the query so it does not select this column and re-run the query.
If you are trying to IMPORT a TABLE, or SAVE DATA that was previously imported, then the data most likely contains a decimal column with a precision larger than the maximum supported by the database. Change the data format to a precision within the database limits.
SQLCODE: -00604 Database: DB2 QMF Function: Command
&V1 cannot be used with this catalog object.
You cannot use ERASE or SAVE with any catalog object.
Do not attempt this operation.
SQLCODE: -00607 Database: DB2 QMF Function: Command
&V2 is not allowed on system databases.
Your &V1 command requires the &V2 operation to be performed on the database. But that operation is not allowed on system databases.
Do not attempt this operation.
SQLCODE: -00618 Database: DB2 QMF Function: Command
Table space &V3 already contains a table.
Your command generated a CREATE TABLE statement, and the database attempted to put the table in the tablespace &V3.. However, &V3 is a partitioned or default table space that already contains an existing table. Only one table can be contained in a partitioned or default table space.
Be sure you have the correct SPACE value in your QMF user profile. Do not attempt to create more than one table in a partitioned or default table space.
SQLCODE: -00646 Database: DB2 QMF Function: Command
Procedure &V2 rejects the result.
Your &V1 command requires an operation that was rejected by &V2, a procedure defined by your installation that edits or validates the results of queries.
See your QMF administrator for descriptions of your installation's edit and validation procedures.
SQLCODE: -00652 Database: DB2 QMF Function: Command
Table &V2 has no partitioned index.
Your &V1 command attempted to create or use a partitioned table, but no partitioned index has been created for that table. A partitioned table (a table in a partitioned tablespace) cannot be referenced until the index for that table has been created. Table &V2 in partitioned tablespace &V3 has no index.
If you are trying to use an existing table, be sure that the correct table was specified in your &V1 command. If it was, create an index, using the CLUSTER clause, for that table and execute your command again.
If you are trying to create a new table, make sure that the SPACE value in your profile does not specify the name of a partitioned table space. If you want to save or import data into a partitioned table, the table and its index must be created before the SAVE or IMPORT command is issued.
SQLCODE: -00653 Database: DB2 QMF Function: Command
The maximum size of a table object has been exceeded.
One or more of the objects that make up a table has reached its maximum size. The storage objects that make up a table are:
Once a storage object has grown to its maximum size, it cannot be extended further.
To make existing space within the object available to store new data, you can:
SQLCODE: -00659 Database: DB2 QMF Function: Command
&V1 cannot be performed because a system function is active.
Either a system utility, the Resource Limit Facility, or the Distributed Data Facility is running. If a system utility is running, it must complete operation before &V1 can be performed. If the Resource Limit Facility is running, it must be stopped or switched to a different resource limit control table before &V1 can be performed. If the Distributed Data Facility is running, it must be stopped before &V1 can be performed.
Wait for the utility to finish, or wait until the Resource Limit Facility stops or switches to a different resource limit control table, or wait until the Distributed Data Facility stops, then resubmit &V1.
SQLCODE: -00666 Database: DB2 QMF Function: Command
You cannot &V1 this table.
The table you want to erase is in a partitioned tablespace. In order to erase such a table, you must drop the entire tablespace.
Do not attempt this operation.
SQLCODE: -00669 Database: DB2 QMF Function: Command
Rows are longer than the table space page size.
The rows of the table you are trying to create are longer than the page size of the assigned table space.
Either:
SQLCODE: -00670 Database: DB2 QMF Function: Command
Your command was rejected by DB2 Data Definition Control Support.
Your &V1 command was rejected by DB2 Data Definition Control Support (DDCS) due to reason code &V2.. Refer to DB2 messages and codes manual for explanation.
Verify that you have specified the correct object name. Consult your QMF administrator to verify that the DDL registration install option is set properly and check if the desired Data Definition Control Support mode is running. Then check the application registration and object registration tables to determine if the entries are correct. If they are not, update the registration table accordingly.
SQLCODE: -00690 Database: DB2 QMF Function: Command
Cannot find the required registration table &V2.
The Data Definition Control Support cannot find the Application Registration Table and/or Object Registration table &V2; your &V1 command cannot be run until the registration tables are properly defined.
Verify that you have specified the correct object name. Consult your QMF administrator to verify the registration tables are created properly and the table names are correct.
SQLCODE: -00691 Database: DB2 QMF Function: Command
Table space, index or table is inconsistent with the owning subsystem.
The definition of a table space, index or table in a ROSHARE READ database defined as ROSHARE READ must be consistent with its description in the owning subsystem.
Verify that the definition of the table space, index or table is consistent with that of the owning subsystem.
SQLCODE: -00733 Database: DB2 QMF Function: Command
Database &V2 is not a shared database on the owning subsystem.
You are trying to access an object in the database identified by &V2. That database is defined as ROSHARE READ on the subsystem that you are accessing. However, the database is no longer defined as ROSHARE OWNER on the owning subsystem. Therefore, the object cannot be accessed.
Verify that the correct object was specified in your &V1 command.
SQLCODE: -00735 Database: DB2 QMF Function: Command
You cannot use an implicit table space in a read-only shared database.
Your &V1 command caused QMF to try to create a table. However, the SPACE value in your profile specifies only a database name, which causes a table space to be implicitly created for the table. The database is a read-only shared database, and table spaces cannot be implicitly created in read-only shared databases.
Create a tablespace for the table, using the name from the owning subsystem. Set the SPACE value in your profile equal to dbname.tsname, where dbname is the name of the database, and tsname is the name of table space. (Make sure you remove the word "DATABASE" from your profile SPACE value.) Then issue your &V1 command again.
SQLCODE: -00737 Database: DB2 QMF Function: Command
The definition for the table &V2. is incomplete.
Table &V2. is not available until the auxiliary tables and indexes for its externally stored columns have been created.
Create the missing auxiliary tables and indexes and re-run the command.
SQLCODE: -00747 Database: DB2 QMF Function: Command
The &V1. command is not permitted on an auxiliary table.
Data in an auxiliary table cannot be accessed by specifying the auxiliary table name. Data in an auxiliary table can only be accessed through operations on the base table.
Use the corresponding base table in the command.
SQLCODE: -00766 Database: DB2 QMF Function: Command
The &V1. command cannot process the current data object.
The current data object has an incompatibility with column "&V2." of the target table. This incompatibility is due to running QMF from a DB2 environment where the ROWID datatype is not supported.
If column "&V2." is the last column of the target table, recreate the data object without that corresponding column of data and run the &V1. command again.
Otherwise, QMF must be run from a DB2 environment that supports the ROWID datatype before the desired QMF action can be completed. The ROWID datatype is supported by DB2 for OS/390 Version 6 and higher.
SQLCODE: -00798 Database: DB2 QMF Function: Command
Division by zero was attempted.
The processing of a column or arithmetic expression resulted in division by zero.
Correct the statement and run the query again.
SQLCODE: -00801 Database: DB2 QMF Function: Command
An Arithmetic operation in the SQL command has resulted in an error.
The SQL command attempted an Arithmetic operation such as Multiplication or Division. However, the computer detected that one or more of the values in the columns selected was invalid. For example: the result of multiplication exceeds internal computer storage or division-by-zero.
Examine the Arithmetic operation and the columns within the command to determine what data may be causing the program exception.
SQLCODE: -00802 Database: DB2 QMF Function: Command
Duplicate value in a unique index column.
One of the columns being modified by your command contains a value equal to the one being inserted. That column is a 'Unique Index' column. Unique Index columns cannot have duplicate values. Your &V1 command was not executed.
You cannot change or replace the existing table or view with your data. Consider saving the data as a new table.
SQLCODE: -00803 Database: DB2 QMF Function: Command
Your command invoked a program not found in the current plan.
Your &V1 command executed the application plan &V3, which needs the program &V2..
If you were accessing remote data, the name of your plan may have been changed to DISTSERV.
However, this program was not found in the plan &V3.. The following are some causes of this error:
Refer to the DB2 Messages and Codes manual for a detailed explanation and report this problem to your Information Center.
SQLCODE: -00805 Database: DB2 QMF Function: Command
Remote update is disallowed in a READ-ONLY environment.
You have attempted to update, insert or delete data at a remote location, but your current operating environment allows remote read only. For example, you cannot update remote data in a CICS operating environment if server database does not support 2-phase commit.
To access remote data in a READ-ONLY operating environment, you can use one of the following:
You can continue to use QMF. If you need to update remote data, switch to an operating environment that supports it; otherwise, contact your QMF administrator.
SQLCODE: -00817 Database: DB2 QMF Function: Command
You must connect to a location to continue using QMF.
Your database server is lost due to the previous error. If you wish to continue using QMF, you may use the QMF Lost Connection Prompt panel to connect to another location, or you can choose to exit QMF.
If you choose to connect to another location, enter the proper values to connect to a valid location. Otherwise, you must exit QMF.
SQLCODE: -00900 Database: DB2 QMF Function: Command
Unavailable resource.
The request was not executed because the resource '&V4' of type '&V3' was unavailable at this time for the reason indicated by '&V2'. You may have entered an incorrect resource name. Or, the resource may be temporarily unavailable. See the DB2 Messages and Codes manual for a detailed explanation of the reason code &V2..
Some common causes for this condition are:
Ensure that the specified resource is valid.
If you have access to the MVS JES log information, browse the log records for this unavailable resource error.
If you need to refer to a local object, but you are currently connected to a remote location, you can connect to the local location and then reference the local object.
If the resource is temporarily unavailable, issue your query again.
If DDF is stopped and the Lost Connection prompt is displayed, you may only be able to reconnect to the local DB2.
If the error condition persists, contact your QMF administrator for assistance.
SQLCODE: -00904 Database: DB2 QMF Function: Command
DB2 resource limit was exceeded - &V1 terminated.
The &V1 command was terminated because a DB2 resource limit was exceeded.
To avoid exceeding the DB2 resource limit, consider restructuring the tables and indexes or changing the resource limits. For further assistance, contact your QMF administrator.
SQLCODE: -00905 Database: DB2 QMF Function: Command
Cannot determine if the remote update was successful.
A system error occurred at the remote location where the updates were made, or a communication failure with the remote location occurred. The error occurred after the request to commit the updates was sent to the remote location. The error prevents DB2 from determining whether or not the commit operation succeeded. If the commit succeeded, updates will appear in the database. If the commit failed, the updates will have been backed out.
After communication has been reestablished with the remote location, query the data to determine whether or not the commit operation was successful.
SQLCODE: -00907 Database: DB2 QMF Function: Command
The portion of the database you require is in use.
The object you need in the database cannot be accessed until another user has completed processing.
End your QMF session and sign on again at a later time.
SQLCODE: -00911 Database: DB2 QMF Function: Command
The portion of the database you require is in use.
The object you need in the database cannot be accessed until another user has completed processing.
End your QMF session and sign on again at a later time.
SQLCODE: -00913 Database: DB2 QMF Function: Command
You must connect to a location to continue using QMF.
Your database server is lost due to the previous error. If you wish to continue using QMF, you may use the QMF Lost Connection Prompt panel to connect to another location, or you can choose to exit QMF.
If you choose to connect to another location, enter the proper values to connect to a valid location. Otherwise, you must exit QMF.
SQLCODE: -00918 Database: DB2 QMF Function: Command
There is not enough storage available to process the statement.
A request was made to the database manager that required another memory page but no more pages are available to the database manager. Some possible causes are:
Correct the problem and run the command again.
SQLCODE: -00930 Database: DB2 QMF Function: Command
Your command tried to access remote data while DDF is inactive.
Your &V1 command attempted to access data at the remote database, but Distributed Data Facility is not started. Your command is rolled back.
You may continue using QMF. If problem persists, contact your QMF administrator.
SQLCODE: -00948 Database: DB2 QMF Function: Command
The location name is not known to the local DB2 subsystem.
You issued a "CONNECT TO <location>" command, and the location name neither specifies the local DB2 subsystem nor is listed in the DB2 communications database.
If the location name is not the local DB2 subsystem name, it must be defined in the DB2 SYSIBM.SYSLOCATIONS table.
Verify that the specified location name is correct. If not, correct it and try again.
You can use the following steps to list all the location names defined in the SYSIBM.SYSLOCATIONS table:
If you are still unable to connect to the desired location, contact your QMF administrator.
SQLCODE: -00950 Database: DB2 QMF Function: Command
Character "&V1" in your query is invalid.
Your query cannot be processed because something is wrong with the character "&V1". It could be misplaced or invalid in the context in which it is being used.
Remove "&V1" or change it to a valid character.
SQLCODE: -00007 Database: DB2 QMF Function: SQL Query
Value beginning '&V2' &V1 needs an end quote.
Character constants must be enclosed in single quotes (like 'SANDERS'), and names of objects in the database, such as tables and columns, may be enclosed in double quotes (like "MYTABLE"). Without the final quote, there is no way to know where the constant or name is supposed to end.
When a quote is used inside another quoted string, it must be shown as two consecutive quotes. For example:
Correct: ... WHERE NAME = 'O''CONNOR' Incorrect: ... WHERE NAME = 'O'CONNOR'
If the value is meant to be a character constant or double- quoted name, add an end quote or duplicate some quote inside it. Otherwise, remove the opening quote.
SQLCODE: -00010 Database: DB2 QMF Function: SQL Query
The &V1. value of &V2. is invalid.
Your query specifies a data type that has an incorrect &V1 specification of &V2.. The &V1 specification for that data type must not exceed the limit.
Some possible causes of your query error are:
Change the &V1 specification so that it is within the data type limit, and run the query again. See the SQL Reference manual for your database for a detailed explanation on the data type limits.
SQLCODE: -00060 Database: DB2 QMF Function: SQL Query
The statement is not valid in this database manager.
The statement you just attempted to execute is not valid in DB2, though it may be valid with other database manager programs. A full list of SQL statements and options that are not allowed in DB2 is contained in the DB2 Reference Manual.
Use only DB2 statements while using this database manager.
SQLCODE: -00084 Database: DB2 QMF Function: SQL Query
Your query is too long.
The statement is too long or too complex to be interpreted. Your nesting of subqueries and correlated queries could be too complex for SQL processing.
Shorten your query or rewrite it as more than one query. If this problem continues, contact your QMF administrator.
SQLCODE: -00101 Database: DB2 QMF Function: SQL Query
Constant beginning '&V3.' &V1. is too long.
Reference line: ==>&V2.
The constant is longer than the maximum allowed. A character constant must be enclosed in quotes. If you omit a closing quote, your data could exceed the maximum length. Normally, character string length is 254 characters or 124 graphic characters if you use double byte character set; CURRENT SQLID value is 8 characters and CURRENT DEGREE value is 3 characters.
Correct the constant and run the query again.
SQLCODE: -00102 Database: DB2 QMF Function: SQL Query
&V3.&V1. is not a valid number.
Reference line: ==>&V2.
&V3. starts with a digit, but is not a valid integer, decimal, or floating-point number. If it is meant to be a...
Change &V3. and run the query again.
SQLCODE: -00103 Database: DB2 QMF Function: SQL Query
SQL error at or before &V3. &V1..
Reference line: ==>&V2.
Some common errors that produce this message are:
The line of symbols below lists one or more symbols that might be correct based on the context so far, though they might not all work with the whole query.
The list of alternate symbols are only suggestions. Some of the symbols might not be legal statements for the database manager being used. Those symbols might be correct for statements sent to other database management systems. &V4.
Correct the query and rerun it.
SQLCODE: -00104 Database: DB2 QMF Function: SQL Query
The statement contains an invalid string.
The statement contains an invalid string. Only a character string or a graphic string is valid.
Specify the correct format of string. For graphic data check for paired delimiters, the character G, and an even number of bytes within the string.
SQLCODE: -00105 Database: DB2 QMF Function: SQL Query
Name starting '&V3.' &V1. is over &V4. characters long.
Reference line: ==>&V2.
If this name specifies a column, table, view, index, alias, synonym, collection ID, or check constraint it should not exceed 18 characters. For DB2/400, the collection ID should not exceed 10 characters.
If this name specifies a location, it should not exceed 16 characters.
If this name specifies a table, view qualifier, database, table space, storage group, bufferpool, referential constraint specified in the CREATE or ALTER TABLE statements, or package ID, it should not exceed 8 characters.
Specify a shorter name and continue to use QMF.
SQLCODE: -00107 Database: DB2 QMF Function: SQL Query
The name &V1 has the wrong number of qualifiers.
The object with the name &V1 can have only one qualifier. A column name is qualified with a table name, which is either qualified or unqualified, or a correlation name. In some contexts, a column name requires a table name qualifier.
Qualify the object correctly and run the query again.
SQLCODE: -00108 Database: DB2 QMF Function: SQL Query
&V1 is not valid in its context.
Some SQL keywords may not appear in some contexts. For example, ORDER BY, INTO, and FOR UPDATE may not be used with CREATE VIEW. INTO may not appear in any SELECT statement.
Correct the query and run it again.
SQLCODE: -00109 Database: DB2 QMF Function: SQL Query
Incorrect hexadecimal data found in value starting &V3.&V1..
Reference line: ==>&V2.
A single hexadecimal character is expressed by two letters or digits, so a hexadecimal value must be expressed by an even number of the digits 0 through 9 or the letters A, B, C, D, E, or F. The incorrect hexadecimal value either has an odd number of digits or letters, or contains an invalid letter or other character.
Correct the invalid value and run the query again.
SQLCODE: -00110 Database: DB2 QMF Function: SQL Query
A column function does not use any column name.
The column functions AVG, MAX, MIN, and SUM must act on expressions that contain a column name from one of the tables accessed.
Correct: SELECT SUM (SALARY * 1.15) FROM Q.STAFF Incorrect: SELECT SUM (18000 * 1.15) FROM Q.STAFF
Make sure that all of your column functions have columns to act on and run the query again.
SQLCODE: -00111 Database: DB2 QMF Function: SQL Query
A column function uses an invalid expression.
The column functions are AVG, COUNT, MAX, MIN, and SUM. Column function expressions cannot contain column functions.
Correct: AVG(UNITS * PRICE) Incorrect: AVG(UNITS * MAX(PRICE))
Change your query so that the column function has a correct expression and run it again.
SQLCODE: -00112 Database: DB2 QMF Function: SQL Query
Name &V3.&V1. contains an invalid character.
Reference line: ==>&V2.
The names for databases, storage groups, tablespaces, and bufferpools can contain only upper-case alphabetic, national (*, &, or @), or numeric characters. The first character must be alphabetic or a national character.
Correct the invalid character in name &V3. and run the query again.
SQLCODE: -00113 Database: DB2 QMF Function: SQL Query
Incorrect use of &V3.&V1..
Reference line: ==>&V2.
A simple comparison like '>' or '=' must not be followed by a list of items. ANY and ALL comparisons must be followed by a subselect, rather than an expression or a list of items. For Example:
Correct: WHERE SALARY > ALL (SELECT COMM
FROM Q.STAFF)
Incorrect: WHERE SALARY > ALL (10000)Change the usage of &V3. and run your query again.
SQLCODE: -00115 Database: DB2 QMF Function: SQL Query
The number of values does not match the number of columns.
In a statement like INSERT INTO Q.STAFF, you must provide a value for every column that was defined as NOT NULL.
If you do not give a list of columns after the table name, then give a value for every column in the table, after VALUES.
If you do give a list of columns after the table name, then give a value for every column in that list, after VALUES.
Example:
INSERT INTO Q.STAFF (ID, NAME, DEPT)
VALUES (400, 'HARRISON', 20)Provide a value for each column you want to INSERT INTO and run the query again.
SQLCODE: -00117 Database: DB2 QMF Function: SQL Query
You can't modify a table used in a subquery.
"Modify" includes INSERT, UPDATE, and DELETE.
Incorrect: INSERT INTO Q.STAFF SELECT * FROM Q.STAFF WHERE YEARS > 7
The example tries to modify the table from which it is receiving data.
Change your query so that the same table used in the subquery is not modified or write a separate query to modify the table.
SQLCODE: -00118 Database: DB2 QMF Function: SQL Query
The grouping is inconsistent.
One of the following has occurred:
Correct: SELECT DEPT, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT
Correct: SELECT DEPT, JOB, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT, JOB (Not: GROUP BY DEPT)(If you use * after SELECT, list all column names after GROUP BY.
Correct: HAVING MIN(YEARS) > 6
(Not: HAVING YEARS > 6)Correct: SELECT DEPT, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT
Change the SQL statement and run your query again.
SQLCODE: -00119 Database: DB2 QMF Function: SQL Query
A built-in function or a grouped column is used incorrectly, '&V3.'&V1..
Reference line: ==>&V2.
You cannot use a built-in function (AVG, COUNT, MAX, MIN or SUM) after WHERE or SET except as part of a subquery.
Correct: WHERE YEARS > (SELECT AVG(YEARS) FROM Q.STAFF) Incorrect: WHERE YEARS > AVG(YEARS)
If your query refers to a view, a column named after GROUP BY in the view definition cannot be used in a condition in your query. For example, if DEPT is used after GROUP BY in defining the view DV, then the following is
Incorrect: SELECT DEPT, SUMSALARY FROM DV WHERE DEPT = 20
Change your query and run it again. If the problem is a grouped column in a view, try using the table the view is based on.
SQLCODE: -00120 Database: DB2 QMF Function: SQL Query
You cannot modify a column twice in the same query.
"Modify" includes INSERT and UPDATE. For example, in the following invalid statement, the column 'YEARS' cannot be modified more than once.
Incorrect:
INSERT INTO Q.STAFF (ID, YEARS, JOB,
YEARS)
VALUES (400, 7, 'clerk', 8)Change the SQL statement so that there is only one modification and run it again.
SQLCODE: -00121 Database: DB2 QMF Function: SQL Query
The grouping is inconsistent.
One of the following has occurred:
Correct: SELECT DEPT, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT
Correct: SELECT DEPT, JOB, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT, JOB (Not: GROUP BY DEPT)(If you use * after SELECT, list all column names after GROUP BY.
Correct: HAVING MIN(YEARS) > 6
(Not: HAVING YEARS > 6)Correct: SELECT DEPT, AVG(SALARY) FROM Q.STAFF GROUP BY DEPT
Change the SQL statement and run your query again.
SQLCODE: -00122 Database: DB2 QMF Function: SQL Query
The parameter in position &V1 must be a constant or keyword.
The parameter in position &V1 of the function &V2 is not a constant when it is required to be a constant or a keyword when it is required to be a keyword.
Correct the function call and run the query again.
SQLCODE: -00123 Database: DB2 QMF Function: SQL Query
The number in the SELECT list does not identify a column.
The column number in error may be 0, or it may be larger than the number of columns listed after SELECT.
Incorrect Examples:
ORDER BY 5 means ordering by the
fifth item in the
SELECT list; it won't
work if the SELECT
list has only four items.
ORDER BY 0 will never work.Change the column number following ORDER BY to agree with the SELECT list and run the query again.
SQLCODE: -00125 Database: DB2 QMF Function: SQL Query
You cannot use DISTINCT more than once in a query.
Examples of DISTINCT usage:
Correct: SELECT AVG(DISTINCT SALARY), DEPT FROM STAFF GROUP BY DEPT HAVING AVG(SALARY) > 16000 Incorrect: SELECT AVG(DISTINCT SALARY), DEPT FROM STAFF GROUP BY DEPT HAVING AVG(DISTINCT SALARY) > 16000
Remove all but one DISTINCT from your query and run it again.
SQLCODE: -00127 Database: DB2 QMF Function: SQL Query
Use NULL with IS or IS NOT.
NULL cannot be used as an item in a list following IN in a WHERE clause. For example
WHERE AMT IN (20,50,NULL) is wrong, but WHERE AMT IN (20,50) OR AMT IS NULL is OK.
Change the phrase with NULL and run your query again.
SQLCODE: -00128 Database: DB2 QMF Function: SQL Query
Query uses more than 15 table references.
One query may not make more than 15 references to tables.
Divide your query into two or more queries, each with 15 or fewer table references.
SQLCODE: -00129 Database: DB2 QMF Function: SQL Query
An escape character used with the LIKE keyword is not valid.
To be an escape character, you must enclose a single character in quotes in the ESCAPE clause. The escape character can be in the string following LIKE only if it is followed by itself, %, or _. You cannot specify the ESCAPE clause if the column name at the left of the LIKE or NOT LIKE has the MIXED attribute. For example, in the following WHERE clause
WHERE COL1 LIKE 'AA+%BB%' ESCAPE '+'
'+' is the escape character, and COL1 is of type CHARACTER;, the WHERE clause will produce values of COL1 that begin with 'AA%BB'. In this example, in the character string following LIKE, any use of '+' other than '++', '+%', or '+_' is an error. (Note that if COL1 has the MIXED attribute, the escape character cannot be specified.)
Fix the character string, or choose a different escape character and change the character string accordingly. Verify that the column name at the left of the LIKE or NOT LIKE does not have the MIXED attribute.
SQLCODE: -00130 Database: DB2 QMF Function: SQL Query
Statement with LIKE has incompatible data types.
If the column name to the left of LIKE or NOT LIKE is of type CHARACTER, the expression at the right must be of type CHARACTER. If the column name is of type GRAPHIC, the expression at the right must be of type GRAPHIC.
If the expression to the right of LIKE or NOT LIKE contains ESCAPE character, the data type of the ESCAPE character must be compatible with the type of the column name to the left.
Check the data type of every operand and run the query again.
SQLCODE: -00131 Database: DB2 QMF Function: SQL Query
An incorrect value is used in a LIKE comparison &V1..
Reference line: ==>&V2.
The actual error may be just before or just after the LIKE.
LIKE should be preceded by a column name and followed by a character constant. Use the symbol '%' within the constant to stand for a string of zero or more characters; use '_' to stand for any single character.
For example, if you were searching a directory for a certain Johnson of whose spelling you were uncertain, you might say
WHERE NAME LIKE 'J%NS_N'
Change the condition using LIKE and run your query again.
SQLCODE: -00132 Database: DB2 QMF Function: SQL Query
An expression is improperly used after a HAVING or WHERE clause.
You must use a column name, rather than an expression, as the argument of a built-in function, when that column is a correlated reference column in a WHERE or HAVING clause. For example:
SELECT DEPT,SUM(YEARS) FROM Q.STAFF VARX GROUP BY DEPT HAVING SUM(YEARS) > ANY (SELECT AVG(YEARS) FROM Q.STAFF GROUP BY DEPT HAVING MAX(YEARS) > MIN(1*VARX.YEARS))
is incorrect -- (1*VARX.YEARS) cannot be the argument of a built-in function MIN because it is an expression containing the correlated reference variable VARX.YEARS.
Correct your query and rerun it.
SQLCODE: -00133 Database: DB2 QMF Function: SQL Query
A wide character column is used incorrectly.
Several restrictions exist when using a column that has a character data type and a width greater than 254 characters. The column cannot be used in search conditions, in sorting, or with arithmetic operations. Values used to insert or update must be constants; they cannot come from subqueries.
In SQL queries the column cannot be used with built-in column functions, HEX or VARGRAPHIC functions, ORDER BY, GROUP BY, UNION, or indexes.
Change your use of any wide character column or remove it, and run the query again.
SQLCODE: -00134 Database: DB2 QMF Function: SQL Query
Sort key length cannot exceed 4,000 bytes.
The sort key is made up of the list of columns specified following DISTINCT, or in an ORDER BY or GROUP BY clause. If both DISINCT and ORDER BY or GROUP BY are present, the sort key is made from the combination of both column lists.
Change your statement so that the internal length of the sort key will not exceed 4,000 bytes. One or more column names must be deleted from the ORDER BY or GROUP BY clause, or the list following the DISTINCT qualifier.
SQLCODE: -00136 Database: DB2 QMF Function: SQL Query
The result of concatenation is too long.
The length of the result of a concatenation (two vertical bars "||") exceeds 32,764 characters or 16,382 graphic characters.
Change your query to create a shorter string, and run the query again.
SQLCODE: -00137 Database: DB2 QMF Function: SQL Query
The second or third argument of the SUBSTR function is out of range.
SUBSTR(ARG1, ARG2, ARG3)
ARG1: must be a character or graphic
string
ARG2: must be an integer and
1 <= ARG2 <= L
ARG3: must be an integer and
0 <= ARG3 <= L-N+1
Where L : the length of ARG1
N : the value of ARG2Change the second or third argument of SUBSTR and run the query again.
SQLCODE: -00138 Database: DB2 QMF Function: SQL Query
You cannot modify the data in this view.
You cannot use INSERT, UPDATE, or DELETE a view that ...
Write separate queries to modify the tables used to create the view.
SQLCODE: -00150 Database: DB2 QMF Function: SQL Query
Column &V1 cannot be changed.
You cannot use INSERT, UPDATE, or DELETE (in SQL) or I., U., or D. (in QBE) to change a column in:
Write separate queries to modify the tables used to create the view.
SQLCODE: -00151 Database: DB2 QMF Function: SQL Query
The DROP &V1 clause in the ALTER statement is invalid.
The DROP &V1 clause in the ALTER statement is invalid because &V2 is a &V3.. Either the DROP FOREIGN KEY clause of an ALTER TABLE statement tried to drop a check constraint, or the DROP CHECK clause of an ALTER TABLE statement tried to drop a referential constraint.
Change the statement to use the correct DROP clause of the ALTER TABLE statement.
SQLCODE: -00152 Database: DB2 QMF Function: SQL Query
View columns defined by expressions or functions need names.
Your CREATE VIEW statement includes a column defined from an expression, such as UNITS * PRICE; a built-in function, such as AVG(YEARS); or a constant, such as 'JUNE 1'. You must supply names for those columns, and so you must have a name list with a name for each column.
Provide new names for all columns defined from functions or expressions in your CREATE VIEW query.
SQLCODE: -00153 Database: DB2 QMF Function: SQL Query
You cannot create a view that uses UNION or contains a remote object.
The definition of the view to be created uses the keyword UNION or contains a remote object. This is not permitted in the definition of a view.
Define the view in some other way.
SQLCODE: -00154 Database: DB2 QMF Function: SQL Query
A view defined by GROUP BY or HAVING is named after FROM.
One of the tables named after FROM in your query is a view defined by a query that uses a GROUP BY or HAVING clause. That view cannot be named after FROM along with any other table.
Rewrite your query so as not to name the view along with another table, after FROM. Run the query again.
SQLCODE: -00155 Database: DB2 QMF Function: SQL Query
Query does not identify a table.
ALTER TABLE, DROP TABLE, LOCK TABLE, or CREATE INDEX may be used only with tables. Names of a view or remote object cannot be used after these statements.
Be sure that the proper table name was used in the query. Do not use the name of a view or remote object after the statements listed above.
SQLCODE: -00156 Database: DB2 QMF Function: SQL Query
Only a table name can be specified in a FOREIGN KEY clause. &V1 is not a table name.
&V1 was identified in a FOREIGN KEY clause of a CREATE or ALTER TABLE statement. However, &V1 is not a table name. A FOREIGN KEY clause must identify a table.
Be sure that a table name is used in the FOREIGN KEY clause.
SQLCODE: -00157 Database: DB2 QMF Function: SQL Query
The CREATE VIEW and SELECT lists need the same number of columns.
There must be a column name in your SELECT list for every column name in the CREATE VIEW list. If you replace the list of names in the SELECT list with an asterisk (*), the view will contain the same column names as the original table.
Change the SELECT list column names to conform to the CREATE VIEW list and run the query again.
SQLCODE: -00158 Database: DB2 QMF Function: SQL Query
Name used is a table, not a view or an alias.
DROP VIEW is used only to drop a view. DROP ALIAS is used only to drop an alias. COMMENT ON ALIAS is used only to comment on an alias.
You cannot drop or comment on a table using DROP VIEW, DROP ALIAS or COMMENT ON ALIAS.
If you want to drop or comment on a table, use the DROP TABLE or COMMENT ON TABLE statement.
SQLCODE: -00159 Database: DB2 QMF Function: SQL Query
WITH CHECK cannot be used with this view.
The WITH CHECK option cannot be used if...
Continue with another operation.
SQLCODE: -00160 Database: DB2 QMF Function: SQL Query
Insert or update value does not satisfy view definition.
WITH CHECK OPTION was used in the definition of the view whose data you are trying to change. All attempts to insert or update rows in the view are checked to make sure that the results will conform to the definition of the view. Some value in your query does not satisfy a condition in that definition.
Examine the definition of the view to determine why the change was rejected, and change the value in the query.
SQLCODE: -00161 Database: DB2 QMF Function: SQL Query
You cannot create a view in another user's name.
Your query attempted to create a view with a qualified name (a name of the form USERID.TABLENAME), and the qualifier of the name was not your own DB2 authorization ID. You can only create a view using an authorization ID other than your own if you have "SYSADM" authority.
Correct the query and run it again or obtain the authorization needed to create a view for someone else.
SQLCODE: -00164 Database: DB2 QMF Function: SQL Query
The number of arguments specified for scalar function '&V1' is invalid.
The SQL statement has specified the scalar function &V1 with either too many or too few arguments. The supported scalar functions are:
DECIMAL, DIGITS, FLOAT, HEX, INTEGER, VARGRAPHIC, DATE, TIME, TIMESTAMP, DAYS, YEAR, MONTH, DAY, HOUR, MINUTE, SECOND, MICROSECOND, LENGTH, SUBSTR, and VALUE.
Examine the use of the scalar function &V1. Change the scalar function and run the query again.
SQLCODE: -00170 Database: DB2 QMF Function: SQL Query
Argument '&V1' of scalar function '&V2' is invalid.
The data type, length, or value specified for scalar function '&V2' is incorrect. Refer to SQL query publications for more information.
Change the data type, length, or value of '&V2' function and run the query again.
SQLCODE: -00171 Database: DB2 QMF Function: SQL Query
The datetime value &V1 is invalid.
The string representation of a valid DATE has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIME has one of the following formats:
'mm/dd/yyyy' 'dd.mm.yyyy' 'yyyy-mm-dd' or LOCAL format
The string representation of a valid TIMESTAMP has the following format:
'yyyy-mm-dd-hh.mm.ss.nnnnnn'
Correct the syntax for the datetime value and run the query again.
SQLCODE: -00180 Database: DB2 QMF Function: SQL Query
The datetime value is not a valid value.
The string representation of a datetime value contains a value which is out of range. The proper ranges for datetime values are as follows:
Years - 1 to 9999 Months - 1 to 12 Days - 1 to 31 Hours - 0 to 24 Minutes - 0 to 59 Seconds - 0 to 59
Correct the datetime value and run the query again.
SQLCODE: -00181 Database: DB2 QMF Function: SQL Query
An arithmetic expression with a datetime value is invalid.
The specified arithmetic expression contains an improperly used datetime value or simple duration. Some correct examples are:
SELECT STARTD + 10102433. FROM Q.PROJECT SELECT STARTD + 1 YEAR FROM Q.PROJECT
Correct the expression and run the query again.
SQLCODE: -00182 Database: DB2 QMF Function: SQL Query
An arithmetic operation on a date or timestamp has a result that is invalid.
The result of an arithmetic operation is a date or timestamp that is not within the valid range. Valid dates are between 0001-01-01 and 9999-12-31.
Correct the datetime value and run the query again.
SQLCODE: -00183 Database: DB2 QMF Function: SQL Query
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00184 Database: DB2 QMF Function: SQL Query
The date or time value cannot be formatted.
One of the following has occurred:
Either change your string representation of the date or time value to be one of the recognized formats, or contact your QMF administrator for assistance in making the local date or time routine available to the database.
SQLCODE: -00185 Database: DB2 QMF Function: SQL Query
Column &V1 has been specified incorrectly as NOT NULL.
In an ALTER TABLE statement, the column &V1 has been specified as NOT NULL and either the DEFAULT clause was not specified or was specified as DEFAULT NULL. When new columns are added to an existing table, a value must be assigned to the new column for all existing rows. By default, the null value is assigned. However, since the column has been defined as NOT NULL, a default value other than null must be defined.
Correct the statement by either removing the NOT NULL restriction on the column or provide a default value other than NULL for the column. Then run the statement again.
SQLCODE: -00193 Database: DB2 QMF Function: SQL Query
Do not use qualified column names with ORDER BY.
When using ORDER BY with UNION or UNION ALL, do not use a qualified column name after the ORDER BY. Instead, use an unqualified name or a number that tells the position of the column in the list after SELECT.
Example 1: SELECT NAME, ID FROM Q.STAFF UNION SELECT NAME, TEMPID FROM Q.APPLICANT ORDER BY 1 Example 2: SELECT NAME, ID FROM Q.STAFF UNION SELECT NAME, TEMPID FROM Q.APPLICANT ORDER BY NAME
Change the statement so that qualified column names are not being used and run the query again.
SQLCODE: -00197 Database: DB2 QMF Function: SQL Query
The query is empty or contains only comments.
An empty query, or one containing only comments, contains no instructions to do anything. It cannot be run.
Write another query.
SQLCODE: -00198 Database: DB2 QMF Function: SQL Query
SQL error at or before &V3. &V1..
Reference line: ==>&V2.
Some common errors that produce this message are:
The line below lists one or more symbols that might have been correct, based on the context so far, though they might not all work with the whole query.
The list of alternate symbols are only suggestions. Some of the symbols might not be legal statements for the database manager being used. Those symbols might be correct for statements sent to other database management systems. &V4.
Correct the query and run it again.
SQLCODE: -00199 Database: DB2 QMF Function: SQL Query
Column &V1 is in more than one table.
An unqualified column name is ambiguous if more than one table or view in the FROM clause has a column with that name, or if more than one column of a nested table expression has that name. A qualified column name is ambiguous only if the correlation name for the column name and for a nested table expression is not unique.
If the problem is caused by a non-unique column name in a nested table expression, change the nested table expression so that the column is unique. If the problem is caused by the use of an unqualified name, qualify it with a table, view or correlation name.
SQLCODE: -00203 Database: DB2 QMF Function: SQL Query
&V1 could not be found.
The query refers to &V1.. Nothing with this name exists in the database.
Check for a spelling error.
SQLCODE: -00204 Database: DB2 QMF Function: SQL Query
Column name &V1 is not in table &V2..
You used column name &V1.. It was not found in table &V2.. You may have misspelled the name, or the table name may need to be qualified.
Verify that the column name and owner are correct and spelled correctly.
SQLCODE: -00205 Database: DB2 QMF Function: SQL Query
Column &V1 is not in any table named in the query.
&V1 is not a column in any table or view named in the query. If it is intended to be a character constant, enclose it in single quotes.
Change the column name or add the table containing column &V1 to the query, and run the query again.
SQLCODE: -00206 Database: DB2 QMF Function: SQL Query
Use column numbers with ORDER BY, not column names.
When using ORDER BY with UNION, do not use a column name after ORDER BY. Instead, use a number that tells the position of the column in the list after SELECT.
Example: SELECT NAME, ID FROM Q.STAFF UNION SELECT NAME, TEMPID FROM Q.APPLICANT ORDER BY 1
Change the column names to column numbers and run the query again.
SQLCODE: -00207 Database: DB2 QMF Function: SQL Query
&V1 must be in the SELECT list.
&V1 follows ORDER BY. Either &V1 was not included in the SELECT list or it is misspelled after ORDER BY.
Add &V1 to the SELECT list; be sure it agrees with the column name after ORDER BY.
SQLCODE: -00208 Database: DB2 QMF Function: SQL Query
The use of &V1 is not unique in the SQL statement.
The name &V1 appears multiple times in the SQL statement creating a conflict.
For a CREATE TRIGGER statement, a name used in the REFERENCING clause is not unique.
For a SELECT statement, a name used in the FROM clause is not unique.
Change the statement to specify unique names.
In a trigger definition, change the names in the REFERENCING clause so that there are no duplicates.
In a SELECT statement, rewrite the FROM clause. Associate correlation names with table names or modify existing correlation names so that all tables are uniquely identified.
SQLCODE: -00212 Database: DB2 QMF Function: SQL Query
An expression in the &V2 clause is not valid.
In the &V2 clause, the expression beginning with "&V1" is not valid.
Refer to reason number &V3 in this list:
Modify the SELECT statement and run the query again. Refer to action number &V3 in this list:
SQLCODE: -00214 Database: DB2 QMF Function: SQL Query
The number of elements on each side of "&V1" are not the same.
The number of elements on the left and right sides of the predicate operator "&V1" are not the same. The number of elements must be the same on both sides.
These elements can appear in a list of expressions enclosed in parentheses or as the columns from a select statement enclosed in parentheses.
Correct the predicate so that the same number of elements are on each side of the predicate operator.
If the predicate operator indicated is "=", the problem could be with an IN predicate written with a SELECT statement.
SQLCODE: -00216 Database: DB2 QMF Function: SQL Query
The Explain table &V1. does not exist.
The EXPLAIN statement requires one or more user-supplied explanation tables in which it places information. The table &V1 is not defined at the current database location.
Create the required explanation table before using EXPLAIN. See the SQL Reference manual for more information on the EXPLAIN statement and creating the explanation tables.
SQLCODE: -00219 Database: DB2 QMF Function: SQL Query
An Explain table has an improper definition.
An error occurred during the execution of the EXPLAIN statement because a required explanation table is improperly defined.
The definition could be incorrect due to:
Correct the definition of the required explanation table before using EXPLAIN. See the SQL Reference manual for more information on the EXPLAIN statement and defining the explanation tables.
SQLCODE: -00220 Database: DB2 QMF Function: SQL Query
The location qualifier cannot be used.
The name you specified has a location qualifier. A three-part object name cannot be used until the local location name is defined.
Remove the location qualifier and retry your query. See your QMF administrator to make sure you are using the correct database, or to define the local location name.
SQLCODE: -00250 Database: DB2 QMF Function: SQL Query
&V1 is not a valid location name.
&V1 contains an alphabetic extender (#, @, $). Alphabetic extenders are not allowed in location names.
Correct the location name and try again.
SQLCODE: -00251 Database: DB2 QMF Function: SQL Query
Function is not supported (reason code = &V1).
The statement cannot be processed because it violates a restriction as indicated by the following reason codes:
The action corresponding to the reason code is:
SQLCODE: -00270 Database: DB2 QMF Function: SQL Query
&V3 is used incorrectly &V1..
Some of the errors that produce this message are:
Correct: WHERE NAME LIKE 'J%' Incorrect: WHERE NAME LIKE J%
Correct: WHERE NAME IN ('JOB','JIM')
Incorrect: WHERE NAME IN (JOB, JIM)Correct: WHERE NAME = 'JOB' or
WHERE NAME = JOB
Incorrect: WHERE NAME = :JOBCorrect the query and run it again.
SQLCODE: -00312 Database: DB2 QMF Function: SQL Query
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00313 Database: DB2 QMF Function: SQL Query
A character string could not be converted due to undefined CCSIDs.
Your SQL statement referenced a character string with a coded character set ID(CCSID) &V1 in a coded character set that differs from the current one. To use this character string at the current server, this character string must be translated from the source CCSID &V1 to the target CCSID &V2. However, this pair of CCSIDs conversion rule is not defined in the SYSSTRINGS system table. Therefore, the database system could not convert the character string to a code suitable for the application server.
Verify that the character columns and values you referenced are correct. If not, make the necessary change and try the query again. Otherwise, contact your QMF administrator.
SQLCODE: -00332 Database: DB2 QMF Function: SQL Query
Invalid use of the ON clause.
The ON clause is being used incorrectly for one of the following reasons:
Correct the syntax of the ON clause and run the query again.
SQLCODE: -00338 Database: DB2 QMF Function: SQL Query
Invalid data type in position &V1..
Some SQL data types are not supported by the application requester. &V1 is the position of the first element with an invalid data type in the SQLDA. A common cause for this error is that the application requester has attempted to describe large object data residing at the application server. Some of the SQLTYPEs that can cause this error are: LOB, BLOB, CLOB, and DBLOB.
Remove the invalid data types and run the query again.
SQLCODE: -00351 Database: DB2 QMF Function: SQL Query
Only one column defined as ROWID is allowed in a table.
An attempt was made to create a table with more than one ROWID column or to add a ROWID column to a table that already has one.
Do not include more than one column of ROWID data type in a CREATE TABLE or ALTER TABLE SQL statement.
SQLCODE: -00372 Database: DB2 QMF Function: SQL Query
The option GENERATED is incorrectly specified.
GENERATED was specified in a CREATE or ALTER TABLE statement for a column with a data type that is not ROWID, or is not a distinct type that is based on ROWID. GENERATED can only be specified for a column with a data type of ROWID, or a distinct type that is based on ROWID.
Eliminate the GENERATED clause or ensure that the data type of the object is ROWID.
SQLCODE: -00397 Database: DB2 QMF Function: SQL Query
A ROWID column has an invalid value.
An attempt to insert an invalid value into a ROWID column was made.
Only ROWID values previously generated by DB2 can be used as values for insertion into a ROWID column. Alternatively, insert the row specifying the keyword DEFAULT for the ROWID column value or remove the ROWID column from the insert column-list.
SQLCODE: -00399 Database: DB2 QMF Function: SQL Query
Data of different types must not be used in an expression or condition.
You used data of different types in an expression or condition. For example, the following is not valid because character data ('COMM') is used in a numeric expression:
Invalid WHERE SALARY = 12*'COMM'
Change any expression or condition so that data of the same type is used.
SQLCODE: -00401 Database: DB2 QMF Function: SQL Query
Numeric data is required.
AVG and SUM column functions, DECIMAL, DIGITS, FLOAT, and INTEGER scalar functions require numeric data. Non-numeric data cannot be used. Arithmetic expressions requires numeric or datetime data.
Change your query to include all numeric data with the arithmetic expression or function. Run the query again.
SQLCODE: -00402 Database: DB2 QMF Function: SQL Query
Value given is too long for column &V1..
The maximum width of column &V1 is less than the number of characters you are trying to put into it.
Change the value to fit the column and run the query again.
SQLCODE: -00404 Database: DB2 QMF Function: SQL Query
Numeric value &V3.&V1. is outside the allowable range for your column.
Reference line: ==>&V2.
&V3. is outside the range of values allowed for the associated column. The value might be the result of an expression.
The proper ranges for SQL values are as follows:
FLOAT .... -7.2E75 to -5.4E-79, 0,
5.4E-79 to 7.2E75
INTEGER .. -2147483648 to 2147483647
SMALLINT . -32768 to 32767
DECIMAL .. The range depends on the
precision and scale of the
column. For example, if
the value is being specified
for a decimal column defined
with precision = 5 and
scale = 2, the range is
-999.99 to 999.99.Change the numeric value and rerun the query.
SQLCODE: -00405 Database: DB2 QMF Function: SQL Query
Numeric value is outside allowable range for column.
Your query specifies a column that has an incorrect numeric value. The value might be the result of an expression.
The proper ranges for SQL values are as follows:
FLOAT ...... -7.2E75 to -5.4E-79, 0,
5.4E-79 to 7.2E75
INTEGER .... -2147483648 to 2147483647
SMALLINT ... -32768 to 32767
DECIMAL .... The range depends on the
precision and scale of the
column. For example, if
the value is being
specified for a decimal
column defined with
precision = 5 and
scale = 2, the range is
-999.99 to 999.99.Change the numeric value for the column and rerun the query.
SQLCODE: -00406 Database: DB2 QMF Function: SQL Query
Column &V1 cannot contain a NULL value.
The update or insert value for column &V1 was NULL. But column &V1 was made NOT NULL in the table definition. If you are inserting a row, the failure to specify a value for a column implies that you want to insert NULL in it.
Enter a value for column &V1..
SQLCODE: -00407 Database: DB2 QMF Function: SQL Query
New value has wrong data type for column &V1..
The data type of the new value in column &V1 does not agree with the data type of the column. Both must be numbers, character strings, graphic strings, dates, times, or time stamps.
Enter some other value for column &V1 and run the query again.
SQLCODE: -00408 Database: DB2 QMF Function: SQL Query
COUNT was used incorrectly.
The built-in function, COUNT, can be used only with a "*" or with DISTINCT and a column name. Examples of usage:
Change your use of COUNT and run the query again.
SQLCODE: -00409 Database: DB2 QMF Function: SQL Query
Value starting '&V1' is longer than 30 characters.
A floating-point constant cannot be more than 30 characters long.
Round &V1 so that it can be written with 30 characters or fewer.
SQLCODE: -00410 Database: DB2 QMF Function: SQL Query
The CURRENT DATE/TIME, CURRENT SQLID, or USER keyword cannot be used as specified.
The CURRENT DATE/TIME, CURRENT SQLID, or USER keyword appearing within an SQL statement is applied in a way that is invalid for its data type:
Change your SQL statement and run the query again.
SQLCODE: -00411 Database: DB2 QMF Function: SQL Query
Use only one column after SELECT in the subquery.
When SELECT is used in a subquery, (except after INSERT), it can select only one column name.
Incorrect: (SELECT PARTNO, PRICE.......)
Change the SELECT list in your subquery and run the query again.
SQLCODE: -00412 Database: DB2 QMF Function: SQL Query
Arithmetic overflow during change of data type.
The result of an arithmetic or insert operation is not valid because arithmetic overflow occurred. For example, you may have tried to INSERT values with a data type of INTEGER into a column with data type of SMALLINT. Conversion is possible so long as the INTEGER values are small enough. But a value larger than 32767 will cause arithmetic overflow.
Change your operation and run the query again.
SQLCODE: -00413 Database: DB2 QMF Function: SQL Query
LIKE requires character or graphic data, the column has numeric or datetime data.
You wrote something like this: LIKE '1%' or LIKE '%12.40.25', where LIKE compares a partial value to the values in some column. The column has a numeric or datetime data type and LIKE requires character or graphic data.
Correct your query and run it again. With numeric data, use a numeric comparison, like "n >= 1000 and n < 2000".
SQLCODE: -00414 Database: DB2 QMF Function: SQL Query
Column attributes in your SELECT lists do not agree.
You connected two or more queries by UNION or UNION ALL. The SELECT lists in each query must have the same number of columns. Corresponding columns in each SELECT list must have comparable data definitions for the SELECT to succeed. If corresponding columns have field procedures, the columns must have the same field procedure and column CCSID value.
Rewrite your query with the SELECT lists of comparable columns, and rerun your query.
SQLCODE: -00415 Database: DB2 QMF Function: SQL Query
Wide character columns cannot be used with UNION.
A column with data type LONG VARCHAR, or with a width greater than 254, cannot be listed after SELECT in a query that uses UNION. Columns with these data types can be used: INTEGER, SMALLINT, DECIMAL, FLOAT, CHAR. A VARCHAR column can be used if its width is less than 255.
Remove any column wider than 254 characters from the SELECT list of any query used with UNION.
SQLCODE: -00416 Database: DB2 QMF Function: SQL Query
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00417 Database: DB2 QMF Function: SQL Query
Invalid use of "?".
If the character "?" is part of the name of something in the database, the name must be enclosed in double quotes. Any other use of "?" for a name in a query is invalid. The character "?" can also be used as a character constant, but it must be enclosed in single quote.
Correct your query and run the query again.
SQLCODE: -00418 Database: DB2 QMF Function: SQL Query
Decimal division is not possible with the values used.
Either the precision of the numerator or the scale of the denominator is too large for decimal division.
Change the precision or scale of your decimal division values and run the query again. Note that an integer or small integer value may have been converted to decimal for this calculation.
SQLCODE: -00419 Database: DB2 QMF Function: SQL Query
An invalid character string argument was used with the &V1 function.
A character string argument did not conform to the requirements of the function. For example, a character string passed to the DECIMAL function did not conform to the rules for forming an SQL integer or decimal constant.
Change the value of the argument so that it conforms to the requirements of the function.
SQLCODE: -00420 Database: DB2 QMF Function: SQL Query
SELECT lists do not have the same number of columns.
You connected two or more queries by UNION. The SELECT lists in each query must have the same number of columns.
Correct the query and run it again.
SQLCODE: -00421 Database: DB2 QMF Function: SQL Query
The value beginning with "&V1" is too long.
A system cast or adjustment function was called to transform the value in some way but the value is too long. Truncation is not allowed where this value is used.
The value appears in one of the following situations:
If the value is a literal string in the SQL statement, it is too long for its intended use.
If the value is not a literal string, examine the SQL statement to determine where the transformation is taking place. Either the input to the transformation is too long, or the target is too short.
Check the SQL Reference manual for specific length limits. They may differ between various database servers.
Correct the usage and run the query again.
SQLCODE: -00433 Database: DB2 QMF Function: SQL Query
&V1. &V2. was not found.
No routine was was found with compatible arguments for &V1. &V2..
This occurs when the database manager cannot find a routine it can use to implement the reference to &V1. &V2.. There are several reasons why this could occur:
Correct the statement and run the query again.
SQLCODE: -00440 Database: DB2 QMF Function: SQL Query
Invalid use of DISTINCT or ALL with &V1..
The keyword DISTINCT or ALL was detected within the parentheses in a reference to the function &V1.. This function was recognized as a scalar function.
If a scalar function is being used then remove the keyword DISTINCT or ALL. It is invalid for a scalar function.
If a column function is being used, then there is a problem with function resolution. Check the value of special register CURRENT FUNCTION PATH. Also check the spelling of the function name and the number and types of parameters in both the query and the system catalog.
SQLCODE: -00441 Database: DB2 QMF Function: SQL Query
The function &V1 has too many arguments.
Too many arguments were specified in the reference to function &V1. The maximum allowable is 90.
Correct the statement by ensuring the correct number of arguments was used and run the query again.
SQLCODE: -00442 Database: DB2 QMF Function: SQL Query
The name &V1 is reserved for system use.
The user defined function or distinct type cannot be created because the name selected is reserved for use by the system.
Names that cannot be used for functions or distinct types, even if they are delimited identifiers, include:
"=" "<" ">" ">=" "<=" "&&=" "&&>" "&&<" "!=" "!>" "!<" "<>" "¬=" "¬<" "¬>" ALL AND ANY BETWEEN DISTINCT EXCEPT EXISTS FALSE FOR FROM IN IS LIKE MATCH NOT NULL ONLY OR OVERLAPS SIMILAR SOME TRUE TYPE UNIQUE UNKNOWN
Select a name for the function or distinct type that is not reserved for system use.
SQLCODE: -00457 Database: DB2 QMF Function: SQL Query
An object dependency prevents statement execution.
A DROP or REVOKE statement cannot remove an object while another object has a dependency on it.
If the object is a distinct type, the dependencies could be:
If the object is a distinct type, the dependencies for REVOKE could be:
Either decide to not remove the object at all or remove the dependent object first.
SQLCODE: -00478 Database: DB2 QMF Function: SQL Query
The GROUP BY clause contains &V1 nested within &V2..
The following types of nesting are not allowed within a GROUP BY clause:
CUBE within CUBE, ROLLUP or GEL ROLLUP within CUBE, ROLLUP or GEL () within CUBE, ROLLUP or GEL GROUPING SET within CUBE, ROLLUP, GROUPING SET or GEL
where GEL represents a grouping-expression -list, an element shown in the syntax diagram of the GROUP BY clause. Refer to the SQL Reference manual for more information.
Modify the GROUP BY clause to remove the nesting and run the query again.
SQLCODE: -00481 Database: DB2 QMF Function: SQL Query
This query exceeds a DB2 cost estimate limit.
DB2 has determined that the cost estimate for this query exceeds a limit specified in the Resource Limit Facility (DB2 governor) preventing the query from being run.
The details of the cost estimate for the query statement are:
If the cost category value is 'B', seek the assistant of your DB2 administrator, the DB2 catalog statistics or resource limit specification tables (RLST) might need updating.
If the SQL statement is consuming too much processor time, rewrite the statement to perform more efficiently and run the query again.
Things to check might be:
Some queries can be made simpler by removing the GROUP BY clause from the query and using the GROUP usage code in the QMF FORM instead.
Some queries will perform better by using advanced SQL syntax, such as Outer Join or the CASE expression,
For advanced analysis the EXPLAIN SQL statement can be used to gather information about the structure and execution performance of a query.
Refer to the SQL Reference for more information on Queries and the EXPLAIN statement.
Refer to the DB2 Administration manual for more information on tuning queries and writing efficient predicates and subqueries.
SQLCODE: -00495 Database: DB2 QMF Function: SQL Query
The query reference to a remote object is invalid.
One of the following invalid conditions exists:
Refer to the DB2 SQL Reference manual for more information on using remote objects.
SQLCODE: -00512 Database: DB2 QMF Function: SQL Query
The alias name &V1 cannot be defined on another local or remote alias.
The object indicated by &V1 exist at the location indicated. However, It is defined as an alias at at that location.
Modify the query to ensure that all object references are to tables or views at the indicated location.
SQLCODE: -00513 Database: DB2 QMF Function: SQL Query
The table &V1 already has that unique constraint.
Duplicate unique constraints are not allowed.
For a CREATE TABLE statement, a UNIQUE clause uses the same column list as the PRIMARY KEY clause or another UNIQUE clause.
For an ALTER TABLE statement, a UNIQUE clause uses the same column list as the PRIMARY KEY or a UNIQUE constraint that already exists for the table.
"&V2" is either the CONSTRAINT name in the SQL statement or the first name specified in the column list of the UNIQUE clause followed by three periods.
Remove the duplicate UNIQUE clause or change the column list to a set of columns that is not already part of a unique constraint.
SQLCODE: -00528 Database: DB2 QMF Function: SQL Query
The foreign key value is not valid.
An update or insert query specified a value for a foreign key. However, the value is not equal to any of the primary key values of the parent table.
If the name of the referential constraint for the foreign key was provided by the database, that name is as follows: &V1..&V2..
Use a value for the foreign key that matches one of the primary key values.
SQLCODE: -00530 Database: DB2 QMF Function: SQL Query
The primary key &V1 in a parent row cannot be updated.
Your update request specifies a value for the primary key of the table being updated, but the row identified by that primary key value has dependent rows associated with it. The value of a primary key in a parent row cannot be updated if the parent row has any dependent rows.
Make sure you selected the correct row to be updated. Before a primary key value in a parent row can be updated, the parent row must not have any dependent rows.
SQLCODE: -00531 Database: DB2 QMF Function: SQL Query
The row cannot be deleted because of a RESTRICT delete rule.
The delete operation attempted to delete a parent row. However, the row cannot be deleted because a delete rule of RESTRICT is associated with tables that can be affected by this deletion. Either the row has a dependent in a relationship with a delete rule of RESTRICT, or the deletion cascades to a row that is a dependent in a relationship with a delete rule of RESTRICT.
Make sure you selected the correct row to be deleted. If you did, delete any dependent rows with a delete rule of RESTRICT. Then delete the parent row.
SQLCODE: -00532 Database: DB2 QMF Function: SQL Query
Cannot insert multiple rows into a self-referencing table.
An INSERT operation with a subselect attempted to insert multiple rows into a self-referencing table. The subselect of the INSERT operation should return no more than one row of data.
Make sure the search condition of the subselect returns no more than one row of data.
SQLCODE: -00533 Database: DB2 QMF Function: SQL Query
Cannot update a primary key or unique constraint in multiple rows.
An UPDATE operation attempted to update a primary key or unique constraint in multiple rows of the table. An UPDATE statement that affects the primary key or unique constraint cannot be used to update more than one row of the table.
Make sure the search condition of the UPDATE statement selects no more than one row of the table to be updated.
SQLCODE: -00534 Database: DB2 QMF Function: SQL Query
The DELETE statement is invalid because table &V1 can be affected.
A DELETE operation was attempted with table &V1, which was referred to in a subquery. However, this table is a descendant of the object table of the operation and is not protected from change by a delete rule of RESTRICT, so the deletion cannot be done.
Do not refer to a table in a subquery of a DELETE statement if the table can be affected by that statement.
SQLCODE: -00536 Database: DB2 QMF Function: SQL Query
You used column name &V1 more than once.
A primary key or foreign key cannot contain duplicate column names. In a PRIMARY KEY or FOREIGN KEY clause, you used column name &V1 more than once.
Specify unique column names.
SQLCODE: -00537 Database: DB2 QMF Function: SQL Query
Foreign key &V1 does not conform to the description of the primary key of table &V2..
Either the foreign key identified by &V1 does not have the same number of columns as the primary key of table &V2, or the descriptions of these keys are not identical. The requirement for identical descriptions includes data type, length attribute, and field procedure.
Correct the FOREIGN KEY clause so that the description of the foreign key conforms to that of the primary key of the indicated table.
SQLCODE: -00538 Database: DB2 QMF Function: SQL Query
Table &V1 does not have a primary key.
You specified table &V1 as a parent table in a FOREIGN KEY clause, but it cannot be defined as a parent table because it does not have a primary key.
Define a primary key for the table using ALTER TABLE.
SQLCODE: -00539 Database: DB2 QMF Function: SQL Query
Table &V1 has no primary index for the primary key.
You cannot use table &V1.. It has a primary key, but no primary index.
Define a primary index for the table before you refer to it.
SQLCODE: -00540 Database: DB2 QMF Function: SQL Query
Foreign key &V1 is invalid because it is a duplicate referential constraint.
The indicated FOREIGN KEY clause defines the same foreign key and parent table as another referential constraint.
Remove the duplicate referential constraint from the statement.
SQLCODE: -00541 Database: DB2 QMF Function: SQL Query
&V1 cannot be a column of a primary key or unique constraint because it can contain null values.
Column &V1 can contain null values; therefore, it cannot be included in a primary key or unique constraint clause.
When defining the primary key or unique constraint use only columns that cannot contain null values. Correct the primary key or unique constraint clause and run the statement again.
SQLCODE: -00542 Database: DB2 QMF Function: SQL Query
The check constraint cannot be added.
The check constraint cannot be added because the table contains a row that violates the constraint. At least one existing row in the table violates the check constraint that is to be added in the ALTER TABLE statement.
Examine the check constraint definition that is specified in the ALTER TABLE statement and the data in the table to determine why the ALTER TABLE statement was rejected.
SQLCODE: -00544 Database: DB2 QMF Function: SQL Query
The operation is not allowed because a row violates the CHECK CONSTRAINT &V1.
Table check constraint violations occurred on an INSERT or UPDATE statement. The resulting row violated the check constraint definition on the table.
Examine the data and the check constraint definition to determine why the INSERT or UPDATE statement was rejected. The data must be changed to satisfy the check constraint. The check constraint definition is contained in the SYSIBM.SYSCHECKS catalog table.
SQLCODE: -00545 Database: DB2 QMF Function: SQL Query
The CHECK CONSTRAINT named &V1 is invalid.
A table check constraint named &V1 in the CREATE TABLE or ALTER TABLE statement is invalid. The constraint definition could be in error for one or more of the following reasons:
Additional restrictions can exist for check constraint definitions.
Correct the constraint definition and run the query again. See the SQL Reference manual for more information on the CREATE TABLE statement and defining a check constraint.
SQLCODE: -00546 Database: DB2 QMF Function: SQL Query
The CHECK CONSTRAINT that is defined with &V1 is invalid.
A check constraint in the CREATE TABLE or ALTER TABLE statement is invalid for one or more of the following reasons:
Correct the constraint definition and run the query again.
SQLCODE: -00548 Database: DB2 QMF Function: SQL Query
&V3 does not exist, or you lack the necessary authority.
&V3 does not exist, or it is a read-only view, or you (the &V1 id) lack the &V2 authority. The possible causes of the authorization failure are:
If you misnamed an existing object, use the correct name. If the &V1 id lacks needed authority, contact your QMF administrator.
SQLCODE: -00551 Database: DB2 QMF Function: SQL Query
The specified object does not exist, or you lack needed authority.
The specified object does not exist, or it's a read-only view, or you lack some needed authority, as follows:
If you misnamed an existing object, use the correct name. If you lack needed authority, contact your QMF administrator.
SQLCODE: -00552 Database: DB2 QMF Function: SQL Query
&V1 is not a valid authorization ID.
The authorization ID specified in SET CURRENT SQLID is neither your primary authorization ID nor one of your secondary authorization IDs.
Correct the authorization ID in the statement or contact your QMF administrator to have the specified authorization ID defined for your use.
SQLCODE: -00553 Database: DB2 QMF Function: SQL Query
You cannot grant a privilege to yourself.
Privileges can only be granted from one user with the proper authority to another user. However, if SQLRULES(STD) is in effect or CURRENT RULES contains STD, GRANT to self is allowed.
Contact your QMF administrator if you need additional privileges.
SQLCODE: -00554 Database: DB2 QMF Function: SQL Query
You cannot revoke a privilege from yourself.
Privileges can only be revoked by one user with the proper authority from another user. However, if SQLRULES(STD) is in effect or CURRENT RULES contains STD, GRANT to self is allowed.
Contact your QMF administrator if you want any database privileges reduced.
SQLCODE: -00555 Database: DB2 QMF Function: SQL Query
You cannot revoke this privilege from &V1..
Either &V1 does not have the privilege you are trying to revoke, or it was granted by a user with a different authorization identifier from yours. You can revoke only privileges granted under your authorization identifier.
Proceed to another operation.
SQLCODE: -00556 Database: DB2 QMF Function: SQL Query
Keyword &V3.&V1. is invalid as used.
Reference line: ==>&V2.
The error may have been caused by any of the following:
The line below lists some of the keywords that might possibly be valid instead of &V3. in the context so far. &V4.
Correct the query and continue.
SQLCODE: -00557 Database: DB2 QMF Function: SQL Query
Invalid use of "AT ALL LOCATIONS" on GRANT or REVOKE.
The location qualifier specified for a GRANT or REVOKE is invalid. Only table privileges (SELECT, INSERT, UPDATE, and so on), excluding ALTER and INDEX privileges, should be granted to IDs at different locations.
See DB2 SQL Reference for valid keywords for GRANT or REVOKE statement.
SQLCODE: -00558 Database: DB2 QMF Function: SQL Query
GRANT and REVOKE cannot be run now.
The authorization portion of the system is temporarily disabled. GRANT and REVOKE queries cannot be run.
Run your query again when the authorization portion of the system is running. Contact your QMF administrator for more details.
SQLCODE: -00559 Database: DB2 QMF Function: SQL Query
Remote update is disallowed in a READ-ONLY environment.
You have attempted to update, insert or delete data at a remote location, but your current operating environment allows remote read only. For example, you cannot update remote data in a CICS operating environment if server database does not support 2-phase commit.
To access remote data in a READ-ONLY operating environment, you can use one of the following:
You can continue to use QMF. If you need to update remote data, switch to an operating environment that supports it; otherwise, contact your QMF administrator.
SQLCODE: -00571 Database: DB2 QMF Function: SQL Query
The DEFAULT value conflicts with the column definition.
USER, CURRENT SQLID, or a constant value was specified as a default value for a column, but either the target column length is too short or it's data type is incompatible.
Change the statement so that the default value conforms to the column definition.
SQLCODE: -00574 Database: DB2 QMF Function: SQL Query
The result-expressions of a CASE expression cannot all be NULL.
There is a CASE expression in the statement that has all the result-expressions coded with the keyword NULL.
Change the CASE expression to include at least one result-expression with a keyword other than NULL and run the query again.
SQLCODE: -00580 Database: DB2 QMF Function: SQL Query
The data types of the result-expressions of a CASE expression are not compatible.
There is a CASE expression in the statement that has result-expressions that are not compatible. The data types of the result-expressions might be incompatible because the CASE condition result data types are not all:
The data types must match. For example: If you are using character data in one instance all data types must be character.
Correct the result-expressions so that the are compatible and run the query again.
SQLCODE: -00581 Database: DB2 QMF Function: SQL Query
The search-condition in a SEARCH-WHEN-CLAUSE is not valid.
The search-condition in a SEARCH-WHEN-CLAUSE specifies a quantified predicate, an IN predicate, or an EXISTS predicate, which are not allowed.
Correct the search-condition and run the query again.
SQLCODE: -00582 Database: DB2 QMF Function: SQL Query
&V1 is the name of an existing &V2..
You tried to CREATE an object named &V1 when a &V2 of that name already exists.
Either DROP &V2 &V1 before running the query, or choose another name for &V1..
SQLCODE: -00601 Database: DB2 QMF Function: SQL Query
The CREATE INDEX or PRIMARY KEY statement specifies to many columns.
The number or columns specified in the CREATE INDEX or PRIMARY KEY statement exceeds the maximum number of columns allowed.
Change your CREATE INDEX or PRIMARY KEY statement to conform to the column limit.
SQLCODE: -00602 Database: DB2 QMF Function: SQL Query
The specified unique index column has duplicate values.
You cannot create an unique index on the specified columns because the table already contains rows that have duplicate values on the column. If a column has a type of VARCHAR or VARGRAPHIC, two columns that differ only in the number of trailing blanks might cause duplication.
Change your CREATE statement so that it does not refer to a column with duplicate values, or else delete rows with duplicate values from the table.
SQLCODE: -00603 Database: DB2 QMF Function: SQL Query
Column definition problem.
Your query specifies a column that has a length, precision, or scale outside the data type limit. Some possible causes of your query error are:
Change the column definition to conform to the data type limit and run your SQL query again. See the SQL Reference manual for your database for a detailed explanation on the data type limits.
SQLCODE: -00604 Database: DB2 QMF Function: SQL Query
&V1 cannot be used with this catalog object.
You cannot use INSERT, UPDATE, or DELETE with the catalog object specified in the SQL statement. You cannot use the DEFER YES option for indexes on catalog tables SYSINDEXES, SYSKEYS, and SYSINDEXPART.
Do not attempt this operation.
SQLCODE: -00607 Database: DB2 QMF Function: SQL Query
You used column name &V1 twice.
A table cannot contain two columns with the same name. In CREATE TABLE, CREATE VIEW, or CREATE INDEX you used column name &V1 more than once. In ALTER TABLE, &V1 is already the name of a column in the table.
Choose another column name and run your query again.
SQLCODE: -00612 Database: DB2 QMF Function: SQL Query
The primary key is too long or has too many columns.
The sum of the length attributes of the columns identified in a PRIMARY KEY clause is greater than 254 bytes, or the number of columns identified is greater than 16.
Modify the table definition to make the total length of the columns identified in the primary key less than or equal to 254 bytes, or change the PRIMARY KEY clause to specify no more than 16 columns.
SQLCODE: -00613 Database: DB2 QMF Function: SQL Query
Columns chosen cannot be indexed.
Under CMS, you cannot index a LONG VARCHAR or LONG VARGRAPHIC column.
Under TSO, you cannot index a VARCHAR column whose maximum allowable length is over 254 characters.
Under either CMS or TSO, you cannot index a group of columns if the sum of their internal lengths exceeds 255 characters.
Revise your index or primary key definition, either by omitting one or more of the columns or by replacing long columns with shorter ones.
SQLCODE: -00614 Database: DB2 QMF Function: SQL Query
You cannot drop &V2; other objects depend on it.
&V2 cannot be dropped because the &V3 named &V4 refers to it.
If you want to drop &V2, first drop all objects that depend on it.
SQLCODE: -00616 Database: DB2 QMF Function: SQL Query
Table &V1. cannot have a TYPE 1 index.
A type 1 index cannot be created on the following tables:
In addition, a type 1 index cannot be created on a ROWID column of a table.
Either create the index as TYPE 2 or, if LOCKSIZE ROW was used, alter the LOCKSIZE of the table space containing the table to a value other than ROW.
SQLCODE: -00617 Database: DB2 QMF Function: SQL Query
&V1 cannot be performed on system databases.
System databases cannot be the object of certain types of operations, including &V1..
Do not attempt this operation.
SQLCODE: -00618 Database: DB2 QMF Function: SQL Query
DBID &V1 was previously assigned to &V2..
The database being created was assigned a DBID of &V1, which is identical to the DBID assigned to database &V2.. There is an inconsistency between the DB2 catalog and directory.
Notify the system programmer. The inconsistency must be corrected before CREATE DATABASE will be successful.
SQLCODE: -00621 Database: DB2 QMF Function: SQL Query
You cannot specify FOR MIXED DATA in CREATE or ALTER TABLE statement.
You specified FOR MIXED DATA is specified in a column description of a CREATE or ALTER TABLE statement, but the MIXED DATA install option for this subsystem is set to NO.
Change the FOR clause to the allowable options BIT or SBCS. If FOR MIXED DATA option is required, consult your DB2 Information Center to reset the MIXED DATA install option to YES.
SQLCODE: -00622 Database: DB2 QMF Function: SQL Query
Table &V1 can have only one CLUSTER index.
The CREATE INDEX statement would create a second CLUSTER index on table &V1.. But a table may have only one CLUSTER index.
Determine the identity and validity of the existing CLUSTER index. Consider creating the new index without the CLUSTER definition.
SQLCODE: -00623 Database: DB2 QMF Function: SQL Query
Table &V1 already has a primary key.
A primary key cannot be defined for table &V1 because it already has a primary key. A table cannot have more than one primary key.
If you want a different primary key for this table, then the existing primary key must be dropped first.
SQLCODE: -00624 Database: DB2 QMF Function: SQL Query
Table &V1 does not have an index to enforce the uniqueness of the primary key.
When adding a primary key to a table using ALTER TABLE, a unique index must already be defined with a key that is identical to that specified in the PRIMARY KEY clause. Table &V1 does not have a unique index for the specified primary key.
Make sure the key list specified on the ALTER TABLE statement identifies an existing unique index of the table.
SQLCODE: -00625 Database: DB2 QMF Function: SQL Query
The ALTER statement cannot be executed because the page set is not stopped.
An ALTER statement specifies BUFFERPOOL, USING, PRIQTY, or GBPCACHE clause, but the page set is not stopped.
Stop the page set, then try again.
SQLCODE: -00626 Database: DB2 QMF Function: SQL Query
The ALTER statement is invalid because the index or table space has user-managed data sets.
The index or table space that you are trying to alter has user-managed data sets, but the ALTER statement contains a PRIQTY, SECQTY, or ERASE clause. These clauses are valid only for DB2-managed data sets. The primary and secondary space allocation of a user-managed data set cannot be changed by means of an ALTER statement.
Verify that the correct index or table space is specified.
SQLCODE: -00627 Database: DB2 QMF Function: SQL Query
The clauses are mutually exclusive.
Mutually exclusive clauses were specified in one or more of the following ways:
Specify one clause or the other, but not both.
SQLCODE: -00628 Database: DB2 QMF Function: SQL Query
You cannot specify SET NULL for foreign key &V1..
The SET NULL delete rule cannot be specified for the FOREIGN KEY clause &V1 because no column of the key allows null values.
Either change a column of the key to allow null values or change the delete rule.
SQLCODE: -00629 Database: DB2 QMF Function: SQL Query
WHERE NOT NULL invalid for type 1 indexes.
A type 1 index cannot be created with the WHERE NOT NULL specification.
Either remove the WHERE NOT NULL specification or create the index as a type 2 index.
SQLCODE: -00630 Database: DB2 QMF Function: SQL Query
Foreign key &V1 is too long or has too many columns.
The sum of the length attributes of the columns identified in the FOREIGN KEY clause for &V1 is greater than 254 bytes, or the number of columns identified is greater than the database limit.
Modify the table definition to conform to the limit of the sum of the length attributes of the columns identified in the FOREIGN KEY clause.
SQLCODE: -00631 Database: DB2 QMF Function: SQL Query
The table cannot be defined as a dependent of &V1 because of delete rule restrictions.
You cannot define the table as a dependent of table &V1.. The relationship would conflict with existing relationships. For example, the relationship might cause the table to be delete-connected to itself.
Remove the FOREIGN KEY clause from the statement.
SQLCODE: -00632 Database: DB2 QMF Function: SQL Query
The delete rule must be &V1..
The FOREIGN KEY clause of the ALTER TABLE statement must specify a delete rule of &V1 because of one of the following:
Change the delete rule in the FOREIGN KEY clause.
SQLCODE: -00633 Database: DB2 QMF Function: SQL Query
The delete rule must not be CASCADE.
The CASCADE delete rule specified in the FOREIGN KEY clause is not valid because of one of the following:
Change the delete rule in the FOREIGN KEY clause.
SQLCODE: -00634 Database: DB2 QMF Function: SQL Query
The delete rules cannot be different or cannot be SET NULL.
The delete rules specified in two FOREIGN KEY clauses of the CREATE TABLE statement are not valid. The foreign keys would cause the table to be delete-connected to one table through multiple paths using different delete rules or a delete rule of SET NULL.
Change the delete rule in one or both of the FOREIGN KEY clauses. If the table is to be delete-connected to one table through multiple paths, the relationships must use the same delete rule (CASCADE or RESTRICT).
SQLCODE: -00635 Database: DB2 QMF Function: SQL Query
The partitioning keys for partition &V1 are not specified in ascending or descending order.
Your query creates a CLUSTER index for a partitioned table (a table in a partitioned tablespace). The key values in the limit-key-value specifications must be given in ascending or descending order.
Correct the limit-key-value specifications so that the values for successive partitions are in strictly ascending or descending order.
SQLCODE: -00636 Database: DB2 QMF Function: SQL Query
&V3.&V1. is given twice.
Reference line: ==>&V2.
This query can use keyword &V3. only once. It was found two or more times.
Correct the query and run it again.
SQLCODE: -00637 Database: DB2 QMF Function: SQL Query
Table &V1 cannot be created because the column definitions are missing.
The CREATE TABLE statement does not contain any column definitions.
Add at least one column definition to the statement.
SQLCODE: -00638 Database: DB2 QMF Function: SQL Query
A nullable column of a foreign key with a delete rule of set null cannot be a column of a partitioned key.
A partition key of the clustering index cannot be updated. Therefore, a foreign key column with a delete rule of SET NULL cannot be a column of a partition key if that column is nullable. If this error occurs for an ALTER TABLE operation, the foreign key cannot be created. If this error occurs for a CREATE INDEX operation, the index cannot be created.
If the error was CREATE INDEX, either change the index partition key definition or drop and redefine the referential constraint with a different delete rule. If the error was ALTER TABLE, either change the referential delete rule or drop and redefine the partition index key so that all nullable index keys are not part of the foreign Keys.
SQLCODE: -00639 Database: DB2 QMF Function: SQL Query
LOCKSIZE ROW cannot be specified.
LOCKSIZE ROW cannot be specified because a table in this tablespace has a type 1 index. If LOCKSIZE ROW is specified for a table space, all indexes on tables in the table space must be type 2 indexes.
Either use the ALTER INDEX statement to convert all type 1 indexes to type 2 indexes or use another LOCKSIZE option.
SQLCODE: -00640 Database: DB2 QMF Function: SQL Query
Too many columns specified in the unique key.
Your CREATE TABLE statement uses too many columns in the UNIQUE clause. The total number of columns specified must be exceed the database limits.
Reduce the totals number of key columns in the UNIQUE clause. Refer to the SQL Reference manual for database limits.
SQLCODE: -00642 Database: DB2 QMF Function: SQL Query
Invalid value for &V1 in &V2 query.
The value given for &V1 in the &V2 query is not a permitted value.
Refer to the SQL Help for information about allowable values for &V1 in &V2 queries.
SQLCODE: -00644 Database: DB2 QMF Function: SQL Query
Table space &V2 already contains a table.
Table space &V2, named in the CREATE TABLE query, is a partitioned or default table space that already contains an existing table. Only one table can be contained in a partitioned or default table space.
Be sure you used the correct table space in the query. Do not attempt to create more than one table in a partitioned or default table space.
SQLCODE: -00646 Database: DB2 QMF Function: SQL Query
Bufferpool &V1 must be activated.
Bufferpool &V1, named in your CREATE or ALTER query for a table space or index space, is not activated. The bufferpool has NUMPAGES = 0.
Table spaces and index spaces can only be assigned (or re-assigned) to bufferpools currently activated.
Be sure that the proper bufferpool was named in the create or alter statement. If it was, activate the bufferpool and execute the statement again.
SQLCODE: -00647 Database: DB2 QMF Function: SQL Query
Something is preventing ALTER INDEX from executing.
The ALTER INDEX statement cannot be executed because of reason number &V1.. in this list:
Correct the situation indicated in reason number &V1.. above before running the statement again.
SQLCODE: -00650 Database: DB2 QMF Function: SQL Query
Procedure &V1 rejects the result.
&V1 is a procedure defined by your installation to edit or validate the results of queries. The result of your query did not meet some requirement of this procedure.
See your QMF administrator for descriptions of your installation's edit and validation procedures.
SQLCODE: -00652 Database: DB2 QMF Function: SQL Query
Table &V1 has no partitioned index.
A partitioned table (a table in a partitioned tablespace) cannot be referenced until the CLUSTER index for that table has been created. Table &V1 has no CLUSTER index.
Be sure that the correct table was specified in the statement. If it was, create a CLUSTER index for that table and execute your statement again.
SQLCODE: -00653 Database: DB2 QMF Function: SQL Query
The maximum size of a table object has been exceeded.
One or more of the objects that make up a table has reached its maximum size. The storage objects that make up a table are:
Once a storage object has grown to its maximum size, it cannot be extended further.
To make existing space within the object available to store new data, you can:
SQLCODE: -00659 Database: DB2 QMF Function: SQL Query
&V1 is not partitioned.
Your CREATE INDEX query contains PART specifications, but tablespace &V1 is not a partitioned tablespace.
Be sure that the proper table is specified in the statement. If it was, the table must be partitioned before a partitioned index can be created.
SQLCODE: -00662 Database: DB2 QMF Function: SQL Query
Wrong number of key limit values for &V1..
The number of limit-key-values in at least one PART specification is either zero or greater than the number of columns in the index key.
Change the number of limit-key-values and continue.
SQLCODE: -00663 Database: DB2 QMF Function: SQL Query
Limit-key fields of index &V1 are too long.
The total length of the keys for a partitioned index may not exceed 40 bytes internally.
Reduce the total number of columns used in key fields of your index.
SQLCODE: -00664 Database: DB2 QMF Function: SQL Query
The PART clause of an ALTER statement is omitted or invalid.
The ALTER statement is invalid for one of the following reasons:
Determine whether the table space or index you want to alter is partitioned. If it is partitioned, specify a PART clause that identifies the partition you want to alter. If it is not partitioned, do not use a PART clause.
SQLCODE: -00665 Database: DB2 QMF Function: SQL Query
A utility, the Resource Limit Facility, or the Distributed Data Facility is running.
If a system utility is running, it must complete execution before your query can be run. If the Resource Limit Facility is running, it must be stopped or switched to a different resource limit control table before your query can be run. If the Distributed Data Facility is running, it must be stopped before an object in the communications database can be dropped.
Wait for the utility to finish, or wait until the Resource Limit Facility stops or switches to a different resource limit control table, then run your query again. Or wait until the Distributed Data Facility stops, then drop the object.
SQLCODE: -00666 Database: DB2 QMF Function: SQL Query
The index cannot be removed by the DROP INDEX statement.
The DROP INDEX statement attempted to drop one of the following indexes:
Neither of these indexes can be explicitly dropped. They can only be removed implicitly by dropping another object.
To remove a cluster index for a table in a partitioned table space, drop the associated partitioned table space.
To remove a unique index defined on a ROWID column with the GENERATED BY DEFAULT attribute, drop the associated table.
SQLCODE: -00667 Database: DB2 QMF Function: SQL Query
This table has an edit procedure: you cannot ALTER.
If a table has an edit procedure, no columns can be added to it. The ALTER statement was not executed.
Be sure that the correct table was specified in the ALTER statement. Do not attempt to ALTER the definition of a table that has an installation-written edit procedure.
SQLCODE: -00668 Database: DB2 QMF Function: SQL Query
You cannot use DROP with this table.
The table you want to drop is in a partitioned tablespace. In order to drop such a table, you must drop the entire tablespace.
Do not attempt this operation.
SQLCODE: -00669 Database: DB2 QMF Function: SQL Query
Rows are longer than tablespace page size.
The length of the rows in a table cannot exceed the page size of the tablespace containing the table.
For CREATE TABLE, either ...
For ALTER TABLE, reduce the width of the new column. If the table already has the maximum row length, no new column can be added.
SQLCODE: -00670 Database: DB2 QMF Function: SQL Query
ALTER TABLESPACE cannot change the page size.
The attempted change to the bufferpool value would change the page size of the tablespace, from 4K to 32K or from 32K to 4K.
If the tablespace uses one of the 4K bufferpools (BP0, BP1, or BP2), it may be re-assigned to one of the other 4K bufferpools. (If it is assigned to BP32K, it cannot be altered.)
SQLCODE: -00671 Database: DB2 QMF Function: SQL Query
DROP is not allowed on TABLE &V1.
The DROP operation failed for one of the following reasons:
Before dropping the table, alter the table specifying DROP RESTRICT ON DROP.
SQLCODE: -00672 Database: DB2 QMF Function: SQL Query
A primary index cannot be created.
A primary key cannot be created because the table contains rows that are duplicates with respect to the values of the identified primary key columns. The primary key definition failed because the table being altered already contains rows that duplicate the values of the PRIMARY KEY clause columns.
Remove the erroneous rows from the table and define the primary key again.
SQLCODE: -00672 Database: DB2 QMF Function: SQL Query
32K bufferpools cannot be used for indexes.
Your CREATE INDEX query named a bufferpool with a page size of 32K. Only the 4K bufferpools BP0, BP1, and BP2 can be used for indexes.
Name a different bufferpool.
SQLCODE: -00676 Database: DB2 QMF Function: SQL Query
Not enough storage to expand bufferpools.
Several situations could cause this message:
Contact your QMF administrator.
SQLCODE: -00677 Database: DB2 QMF Function: SQL Query
Value for limit-key doesn't match column &V3..
The limit-key value given for column &V3 does not have the same data type as the column.
If the value should have a character data type, enclose it in single quotes.
SQLCODE: -00678 Database: DB2 QMF Function: SQL Query
Your table or view contains too many columns.
Your query would create a table or view with more than the maximum number of columns allowed.
Change your query so that the number of columns in the table or view you are creating will not exceed the database limit.
SQLCODE: -00680 Database: DB2 QMF Function: SQL Query
Column &V1 violates installation defined field procedure. RT: &V2, RS: &V3, MSG: &V4..
A field procedure error has occurred on column &V1. Use return code (RT) to determine the problem:
4 Invalid value on encode or decode or
invalid column definition.
8 Invalid parameter value.
12 Field procedure error on any
function.Use reason code (RS) and message (MSG) token for additional information.
If it is not a field procedure error, determine the requirements imposed by the field procedure. If it is a field procedure error, examine the field procedure.
SQLCODE: -00681 Database: DB2 QMF Function: SQL Query
FIELDPROC, SBCS, BIT or MIXED data cannot be used on column &V1..
Either FIELDPROC, SBCS, BIT or MIXED data was specified on column &V1. This is invalid because these data types cannot be specified for a numeric, date, time, long string, or non-null default value column.
Correct the SQL statement and rerun the query.
SQLCODE: -00683 Database: DB2 QMF Function: SQL Query
The length of the parameter list beginning &V1 is too long.
FIELDPROC program-name (parameter list)
The parameter list is optional for FIELDPROC. The number of parameters and data type of each are determined by the field procedure. The maximum length of the parameter list is 254 bytes, including commas but excluding insignificant blanks and the delimiting parentheses.
Correct the SQL statement and run the query again.
SQLCODE: -00684 Database: DB2 QMF Function: SQL Query
A column defined with a field procedure cannot be compared to another column with a different field procedure.
If a column with a field procedure is compared to another column, the two columns must have the same field procedure.
Correct the SQL statement and run the query again.
SQLCODE: -00686 Database: DB2 QMF Function: SQL Query
Column field types incomparable.
If a column with a field procedure is compared to another column, they must have the same field procedure and same field type. The comparison is performed on the encoded form of the values in the columns. For example, if the encoded values are numeric, their data types must be identical; if they are strings, their data types must be compatible.
Correct the SQL statement and run the query again.
SQLCODE: -00687 Database: DB2 QMF Function: SQL Query
Number of columns defined in the dependent table exceeds the maximum.
The maximum number of columns allowed for a dependent table is 749.
Possible causes of this error are:
Correct your SQL statement so that the number of columns defined in the dependent table is no more than 749 columns.
SQLCODE: -00689 Database: DB2 QMF Function: SQL Query
Your SQL statement was rejected by DB2 Data Definition Control Support.
DB2 Data Definition Control Support (DDCS) rejected your SQL statement due to reason code &V1.. Refer to the DB2 Messages and Codes manual for an explanation.
Verify that you have specified the correct object name. Consult your Information Center to verify the DDL registration install option is set properly and check if the desired Data Definition Control Support mode is running. Then check the application registration and object registration tables to determine if the entries are correct. If they are not, update the registration table accordingly.
SQLCODE: -00690 Database: DB2 QMF Function: SQL Query
Cannot find the required registration table &V1.
The DB2 Data Definition Control Support cannot find the Application Registration Table and/or Object Registration table. Your query will not run until these tables are properly defined.
Consult your Information Center to verify the registration tables are created properly and the table names are correct.
SQLCODE: -00691 Database: DB2 QMF Function: SQL Query
Invalid use of &V2 in a trigger definition.
The CREATE TRIGGER statement for &V1 includes an invalid use of &V2. as either a correlation-name or a temporary table identifier in the REFERENCING clause.
Refer to reason number &V3.. in this list:
Correct the REFERENCING clause of the CREATE TRIGGER statement before running the statement again.
SQLCODE: -00696 Database: DB2 QMF Function: SQL Query
Invalid REFERENCING clause in a trigger definition.
The CREATE TRIGGER statement includes a REFERENCING clause with one of the following invalid combinations:
Remove the invalid correlation names or temporary table identifiers from the REFERENCING clause or change the trigger granularity before running the statement again.
SQLCODE: -00697 Database: DB2 QMF Function: SQL Query
Your query specified an invalid value for &V1 register.
Your statement specified an invalid value for the &V1 special register. For the SET CURRENT DEGREE statement, the value of CURRENT DEGREE must be 'ANY', '1', or '1 '.
Use a valid value to set the &V1 special register.
SQLCODE: -00713 Database: DB2 QMF Function: SQL Query
The parent table must be in a read-only shared database.
The table that you are creating or altering is in a read-only shared database. A foreign key in your CREATE or ALTER statement references a parent table that is not in a read-only shared database. The parent of a table in a read-only shared database must also be in a read-only shared database. The parent of a table in a shared database must also be in a shared database.
Make sure that the FOREIGN KEY clause refers to the correct parent table.
SQLCODE: -00730 Database: DB2 QMF Function: SQL Query
You must define &V1 with SHAREOPTIONS(1,3).
The VSAM SHAREOPTIONS for the user-defined dataset &V1 must be (1,3) for all the indexes and table spaces in the shared database.
Use the VSAM command LISTC to display the SHAREOPTIONS for the dataset &V1. If SHAREOPTIONS is not (1,3), correct it.
SQLCODE: -00731 Database: DB2 QMF Function: SQL Query
The table space or index space is not defined on the owning subsystem.
The database specified in your CREATE statement is defined on the subsystem with ROSHARE READ attribute. The table space or index must be defined on the owning subsystem before you can create it in the database.
Verify that the table space or index is defined on the owning subsystem that owns the shared database.
SQLCODE: -00732 Database: DB2 QMF Function: SQL Query
Table space, index or table is inconsistent with the owning subsystem.
The definition of a table space, index or table in a ROSHARE READ database defined as ROSHARE READ must be consistent with its description in the owning subsystem.
Verify that the definition of the table space, index or table is consistent with that of the owning subsystem.
SQLCODE: -00733 Database: DB2 QMF Function: SQL Query
You cannot ALTER the ROSHARE attribute of a database.
You cannot alter a database from ROSHARE READ to either ROSHARE OWNER or ROSHARE NONE.
Verify that the correct database was specified on the ALTER DATABASE statement. To change the ROSHARE attribute of a read-only shared database, DROP and recreate the database.
SQLCODE: -00734 Database: DB2 QMF Function: SQL Query
Database &V1 is not a shared database on the owning subsystem.
You are trying to access an object in the database identified by &V1. That database is defined as ROSHARE READ on the subsystem that you are accessing. However, the database is not defined as ROSHARE OWNER on the owning subsystem. Therefore, the object cannot be accessed.
Verify that the correct object was specified.
SQLCODE: -00735 Database: DB2 QMF Function: SQL Query
Your CREATE statement contains an invalid OBID &V1.
Your OBID &V1 is either out of the acceptable range of 1 to 65535, or &V1 is already in use for the given database.
Verify that the given OBID is valid. If the existing object is in error, then DROP and CREATE that object using the correct OBID value.
SQLCODE: -00736 Database: DB2 QMF Function: SQL Query
You cannot use an implicit table space in a read-only shared database.
Your CREATE TABLE statement uses the IN DATABASE clause to indicate the database in which the table is to be created. This implicitly creates a table space in the database. Table spaces cannot be created implicitly in read-only shared databases.
Create a table space for the table, using the same name on the owning subsystem. Then rerun the CREATE TABLE statement, specifying the database and table space names.
SQLCODE: -00737 Database: DB2 QMF Function: SQL Query
The definition for the table is incomplete.
An attempt was made to access or reference a table with one or more LOB columns, however, one of the following conditions exist.
Perform as many of the steps listed below as needed.
Run the query again.
SQLCODE: -00747 Database: DB2 QMF Function: SQL Query
An auxiliary table &V1. can have only one index.
An index already exists for the specified auxiliary table. An auxiliary table can have only one index, but the CREATE INDEX statement would create a second index.
Do not attempt to create a second index for the specified auxiliary table.
SQLCODE: -00748 Database: DB2 QMF Function: SQL Query
Invalid triggered SQL statement in a trigger definition.
The trigger definition for &V1 includes an unsupported triggered SQL statement. The SQL statements supported as a triggered SQL statement depend on the type of trigger.
Certain DB2 servers support these SQL statements in both types
of triggers:
- a SIGNAL SQLSTATE statement.
- a CALL SQL statement.
Check the trigger definition for any triggered SQL statement that does not match the lists above and remove it.
See the SQL Reference manual for more information on the CREATE TRIGGER statement and supported triggered SQL statements.
SQLCODE: -00751 Database: DB2 QMF Function: SQL Query
Table space is invalid.
The table space is invalid for one of the following reasons:
Either
SQLCODE: -00763 Database: DB2 QMF Function: SQL Query
LOB table space and base table space must be in the same database.
An attempt was made to create an auxiliary table in a LOB table space that is not in the same database as the associated base table space.
Specify a LOB table space in the same database as the associated base table space and run the query again.
SQLCODE: -00764 Database: DB2 QMF Function: SQL Query
DB2 auxiliary table cannot be referenced directly.
Data in an auxiliary table cannot be accessed by specifying the auxiliary table name. Data in an auxiliary table can only be accessed through operations on the base table.
Use the corresponding base table and re-run the query.
SQLCODE: -00766 Database: DB2 QMF Function: SQL Query
Missing or invalid column specification for index &V1..
The CREATE INDEX statement failed for one of the following reasons:
Correct the syntax of the CREATE INDEX statement:
SQLCODE: -00767 Database: DB2 QMF Function: SQL Query
Auxiliary table already exists for the specified column or partition.
An attempt was made to create an auxiliary table, but an auxiliary table for the specified column or partition already exists. When the base table belongs to a non-partitioned table space, there can be only one auxiliary table per LOB column of the table. When the base table belongs to a partitioned table space, for any given LOB column, all values of the LOB column for a given partition are stored in their own auxiliary table. There must be one auxiliary table per partition of the base table space.
Check that the correct table name, column name, and if applicable, partition number have been specified. If a different name is desired for the existing auxiliary table, the RENAME TABLE statement can be used to rename the auxiliary table.
SQLCODE: -00768 Database: DB2 QMF Function: SQL Query
ROWID column is required when defining LOB columns.
An attempt was made to create a table &V1 with a LOB column or to add a LOB column to a table, but the table does not have a ROWID column. A table with a LOB column must also have a ROWID column.
If creating a table with a LOB column, define a column with type ROWID in the same table. If using ALTER to add a LOB column to a table, first use ALTER to add a column with type ROWID to the table.
SQLCODE: -00770 Database: DB2 QMF Function: SQL Query
Invalid triggered SQL statement in a trigger definition.
The trigger definition for &V1 includes an unsupported triggered SQL statement. The SQL statements supported as a triggered SQL statement depend on the type of trigger.
Certain DB2 servers support these SQL statements in both types
of triggers:
- a SIGNAL SQLSTATE statement.
- a CALL SQL statement.
Check the trigger definition for any triggered SQL statement that does not match the lists above and remove it.
See the SQL Reference manual for more information on the CREATE TRIGGER statement and supported triggered SQL statements.
SQLCODE: -00797 Database: DB2 QMF Function: SQL Query
Attempted to insert a value into ROWID GENERATED ALWAYS column.
When inserting into a table, a value was specified for a ROWID GENERATED ALWAYS column &V1.. GENERATED ALWAYS columns should not be specified in the column-list for an insertion unless the corresponding entry in the VALUES list is DEFAULT.
Remove the ROWID column from the column-list or specify DEFAULT for the ROWID identifier column in the VALUES clause.
SQLCODE: -00798 Database: DB2 QMF Function: SQL Query
Division by zero was attempted.
The processing of a column or arithmetic expression resulted in division by zero.
Correct the statement and run the query again.
SQLCODE: -00800 Database: DB2 QMF Function: SQL Query
An Arithmetic operation in the SQL command has resulted in an error.
The SQL command attempted an Arithmetic operation such as Multiplication or Division. However, the computer detected that one or more of the values in the columns selected was invalid. For example: the result of multiplication exceeds internal computer storage or division-by-zero.
Examine the Arithmetic operation and the columns within the command to determine what data may be causing the program exception.
SQLCODE: -00802 Database: DB2 QMF Function: SQL Query
Duplicate value in a unique index column.
One of the columns into which you are inserting or updating a new value contains that same value already. That column is a 'Unique Index' column. Unique Index columns cannot have duplicate values.
Change the value so that it does not duplicate a value already existing. Run your query again.
SQLCODE: -00803 Database: DB2 QMF Function: SQL Query
A program is not found in the current plan.
QMF executed the application plan &V2, which needs the program &V1..
If you are accessing remote data, the name of your plan may have been changed to DISTSERV.
This program was not found in the plan &V2.. The following are some causes of this error:
Refer to the DB2 Messages and Codes manual for a detailed explanation and report this problem to your QMF administrator.
SQLCODE: -00805 Database: DB2 QMF Function: SQL Query
A subquery produces more than one value.
A subquery should not produce values from more than one column of a table; in many cases it should not produce values from more than one row. Use ALL, ANY, EXISTS, or IN with a subquery that produces more than one value.
Examples: WHERE DEPT = ANY (SELECT DEPTNUMB FROM Q.ORG) HAVING AVG(X) > ALL (SELECT X FROM Y) WHERE EXISTS (SELECT * FROM X WHERE N1 = N2)
Change your query and run it again.
SQLCODE: -00811 Database: DB2 QMF Function: SQL Query
A subquery using a GROUP BY or HAVING clause needs ALL, ANY, EXISTS, or IN.
A subquery that uses a GROUP BY or HAVING clause can be expected to produce more than one value. It should be preceded by one of the keywords ALL, ANY, EXISTS, or IN.
Change the query and run the query again.
SQLCODE: -00815 Database: DB2 QMF Function: SQL Query
Remote update is disallowed in a READ-ONLY environment.
You have attempted to update, insert or delete data at a remote location, but your current operating environment allows remote read only. For example, you cannot update remote data in a CICS operating environment if server database does not support 2-phase commit.
To access remote data in a READ-ONLY operating environment, you can use one of the following:
You can continue to use QMF. If you need to update remote data, switch to an operating environment that supports it; otherwise, contact your QMF administrator.
SQLCODE: -00817 Database: DB2 QMF Function: SQL Query
Your query uses too many columns.
You cannot select or insert more than the maximum number of columns allowed by the database from any table or set of tables in a single query.
Rewrite the query to use fewer columns. If the query is in SQL, check statements like "SELECT * FROM A, B, C", which selects every column from each of tables A, B, and C.
SQLCODE: -00840 Database: DB2 QMF Function: SQL Query
A valid CCSID has not been specified for this system.
A valid CCSID was not specified on either the ASCII CODED CHARACTER SET or the EBCDIC CODED CHARACTER SET subsystem parameter on installation panel DSNTIPF.
Contact your system administrator to have the necessary CCSID defined on your system.
SQLCODE: -00872 Database: DB2 QMF Function: SQL Query
Data encoded with different CCSIDs cannot be referenced in the same SQL statement.
You cannot refer to a column defined in an ASCII table in the same SQL statement as a column defined in an EBCDIC table.
Correct the SQL statement and run the query again.
SQLCODE: -00873 Database: DB2 QMF Function: SQL Query
The TABLE encoding scheme conflicts with the TABLE SPACE encoding scheme.
If CCSID ASCII was specified, then the containing table space is EBCDIC. If CCSID EBCDIC was specified, then the containing table space is ASCII. The encoding scheme of the table must be the same as the table space which contains the table.
Correct the SQL statement and run the query again.
SQLCODE: -00874 Database: DB2 QMF Function: SQL Query
&V1 cannot be used with the ASCII data referenced encoding scheme.
ASCII data was referenced in one of the following situations:
Correct the SQL statement and run the query again.
SQLCODE: -00875 Database: DB2 QMF Function: SQL Query
TYPE 1 INDEX cannot be created for a table defined as ASCII.
A CREATE TYPE 1 INDEX statement was specified for an ASCII table. Only type 2 indexes are supported for ASCII tables.
Correct the SQL statement to specify TYPE 2 index for the index being created and run the query again.
SQLCODE: -00876 Database: DB2 QMF Function: SQL Query
CCSID ASCII is not allowed for this database or table space.
The database or table space specified is required to be EBCDIC.
Remove the CCSID ASCII clause from the statement and run the query again.
SQLCODE: -00877 Database: DB2 QMF Function: SQL Query
The PLAN_TABLE used for EXPLAIN cannot be ASCII.
PLAN_TABLEs must be encoded EBCDIC for use with EXPLAIN.
Drop the existing PLAN_TABLE and recreate it with the EBCDIC encoding scheme.
SQLCODE: -00878 Database: DB2 QMF Function: SQL Query
Invalid column definition specified on the CREATE TABLE statement for and ASCII table.
A CREATE TABLE statement for an ASCII table cannot define a column as GRAPHIC, VARGRAPHIC, or LONG VARGRAPHIC when the MIXED DATA install option is set to NO.
Contact your system administrator to properly set up the install options for ASCII tables, or change the data types of the columns in your CREATE TABLE statement.
SQLCODE: -00879 Database: DB2 QMF Function: SQL Query
You must connect to a location to continue using QMF.
Your database server is lost due to the previous error. If you wish to continue using QMF, you may use the QMF Lost Connection Prompt panel to connect to another location, or you can choose to exit QMF.
If you choose to connect to another location, enter the proper values to connect to a valid location. Otherwise, you must exit QMF.
SQLCODE: -00900 Database: DB2 QMF Function: SQL Query
Unsuccessful execution caused by an unavailable resource. Reason code &V1, type of resource &V2, and resource name &V3..
The request could not be executed because the resource '&V3' of type '&V2' was not available at this time for the reason indicated by '&V1'. See the DB2 Messages and Codes manual for a detailed explanation of the reason code &V1..
This may be a temporary condition.
Some common causes for this condition are:
If you have access to the MVS JES log information, browse the log records for this unavailable resource error.
If you need to refer to a local object, but you are currently connected to a remote location, you can connect to the local location and then reference the local object.
If the resource is temporarily unavailable, issue your query again.
If DDF is stopped and the Lost Connection prompt is displayed, you may only be able to reconnect to the local DB2.
If the error condition persists, contact your QMF administrator for assistance.
SQLCODE: -00904 Database: DB2 QMF Function: SQL Query
Unsuccessful execution because DB2 resource limit was exceeded. Resource name = &V1., limit = &V2..
The execution of the SQL statement was terminated because a DB2 resource limit was exceeded.
To avoid exceeding the DB2 resource limit, consider simplifying the SQL statement, restructuring the tables and indexes, or changing the resource limits. For further assistance, contact your QMF administrator.
SQLCODE: -00905 Database: DB2 QMF Function: SQL Query
Unable to determine if the updates made at a remote location were successful or not.
A system error occurred at the remote location where the updates were made, or a communication failure with the remote location occurred. The error occurred after the request to commit the updates was sent to the remote location. The error prevents DB2 from determining whether or not the commit operation succeeded. If the commit succeeded, updates will appear in the database. If the commit failed, the updates will have been backed out.
After communication has been reestablished with the remote location, query the data to determine whether or not the commit operation was successful.
SQLCODE: -00907 Database: DB2 QMF Function: SQL Query
The portion of the database you require is in use.
The object you need in the database cannot be accessed until another user has completed processing.
End your QMF session and sign on again at a later time.
SQLCODE: -00911 Database: DB2 QMF Function: SQL Query
The portion of the database you require is in use.
The object you need in the database cannot be accessed until another user has completed processing.
End your QMF session and sign on again at a later time.
SQLCODE: -00913 Database: DB2 QMF Function: SQL Query
You must connect to a location to continue using QMF.
Your database server is lost due to the previous error. If you wish to continue using QMF, you may use the QMF Lost Connection Prompt panel to connect to another location, or you can choose to exit QMF.
If you choose to connect to another location, enter the proper values to connect to a valid location. Otherwise, you must exit QMF.
SQLCODE: -00918 Database: DB2 QMF Function: SQL Query
There is not enough storage available to process the statement.
A request was made to the database manager that required another memory page but no more pages are available to the database manager. Some possible causes are:
Correct the problem and run the query again.
SQLCODE: -00930 Database: DB2 QMF Function: SQL Query
You cannot access remote data while DDF is inactive.
Your query attempted to access data at the remote database, but Distributed Data Facility is not started. Your query is rolled back.
You may continue using QMF. If problem persists, contact your QMF administrator.
SQLCODE: -00948 Database: DB2 QMF Function: SQL Query
An SQL error occurred at or before &V3..
A syntax error was detected at the specified token. The text " &V4 " indicates up to 20 characters of the statement that preceded the error. Some common errors that produce this message are:
The line of symbols below lists one or more symbols that might be correct based on the context so far, though they might not all work with the whole query.
The list of alternate symbols are only suggestions. Some of the symbols might not be legal statements for the database manager being used. Those symbols might be correct for statements sent to other database management systems. &V5
Correct the query and rerun it.
&V1. &V2. was not found.
No routine was was found with compatible arguments for &V1. &V2..
This occurs when the database manager cannot find a routine it can use to implement the reference to &V1. &V2.. There are several reasons why this could occur:
Correct the statement and run the query again.
The specified combination of privileges cannot be granted or revoked.
One of the following occurred:
Correct the statement and run it again.
FOREIGN KEY &V1 is not valid.
FOREIGN KEY &V1 is not valid. The table cannot be defined as a dependent of table &V2 because of delete rule restrictions (reason code = &V3). A referential constraint cannot be defined because the object table of the CREATE TABLE or ALTER TABLE statement cannot be defined as a dependent of table &V2 for one of the following reason codes:
The delete rules of the existing relationships cause an error, not the delete rule specified in the FOREIGN KEY clause of the CREATE TABLE or ALTER TABLE statement. &V1 is the constraint name specified in the FOREIGN KEY clause from the CREATE TABLE or ALTER TABLE statement.
Eliminate the particular FOREIGN KEY clause from the CREATE TABLE or ALTER TABLE statement and run the statement again.
The delete rule of FOREIGN KEY &V1 must be &V2..
The delete rule specified in a FOREIGN KEY clause of the CREATE TABLE or ALTER TABLE statement is not valid. Reason code &V3 was given. The indicated delete rule is required for one of the following reason codes:
&V1 is the constraint name specified in the FOREIGN KEY clause from the CREATE TABLE or ALTER TABLE statement.
Change the delete rule and run the statement again.
See DSQ18104
Follow the directions in the referenced message.
See DSQ18440
Follow the directions in the referenced message.
Invalid use of DISTINCT or ALL with &V1..
The keyword DISTINCT or ALL was detected within the parentheses in a reference to the function &V1.. This function was recognized as a scalar function.
If a scalar function is being used then remove the keyword DISTINCT or ALL. It is invalid for a scalar function.
If a column function is being used, then there is a problem with function resolution. Check the value of special register CURRENT FUNCTION PATH. Also check the spelling of the function name and the number and types of parameters in both the query and the system catalog.
See DSQ18557
Follow the directions in the referenced message.
See DSQ18632
Follow the directions in the referenced message.
See DSQ18633
Follow the directions in the referenced message.