SQL0901 Error in V7R1, but not V6R1

Hey All,

We are performing some tests on our V7R1 box in preparation for our move from V6R1 and found an SQL in one of the programs that is failing with a SQL0901 error.

Here is what I have. When I run the SQL outside of the code in STRSQL, I get the SQL0901 error. The joblog looks like:

Pointer not set for location referenced.
*** DBOP QRO creation FAILED! ***.
Internal failure occurred in query processor.
Internal failure occurred in query processor.
Ownership of object GPTFLST in QTEMP type *USRSPC changed.
SQL system error.

The table is a Join Logical File with some select/omit logic and 5 tables.

The SQL looks like:

SELECT Field1, Field2 from LIB/JOINLOG where Field3 = '12345'

Both of the CPF4204 errors look like:

Message ID . . . . . . : CPF4204 Severity . . . . . . . : 50
Message type . . . . . : Escape
Date sent . . . . . . : 06/21/11 Time sent . . . . . . : 11:59:50

Message . . . . : Internal failure occurred in query processor.
Cause . . . . . : A system failure has occurred in the query processor
program. The query definition template number is 1.
Recovery . . . : See the low-level messages. Correct any errors and try
your request again. If the problem continues, report the problem (ANZPRB
command).

The expanded SQL0901 error shows:

Message ID . . . . . . : SQL0901 Severity . . . . . . . : 50
Message type . . . . . : Diagnostic
Date sent . . . . . . : 06/21/11 Time sent . . . . . . : 11:59:50

Message . . . . : SQL system error.
Cause . . . . . : An SQL system error has occurred. The current SQL
statement cannot be completed successfully. The error will not prevent
other SQL statements from being processed. Previous messages may indicate
that there is a problem with the SQL statement and SQL did not correctly
diagnose the error. The previous message identifier was CPF4204. Internal
error type 3107 has occurred. If precompiling, processing will not continue
beyond this statement.
Recovery . . . : See the previous messages to determine if there is a
problem with the SQL statement. To view the messages, use the DSPJOBLOG
command if running interactively, or the WRKJOB command to view the output
of a precompile. An application program receiving this return code may
attempt further SQL statements. Correct any errors and try the request
again.

What is the 'error type 3107'? I don't recall seeing it before.

Any help will be appreciated!

Thanks!


Steve Needles

Northland Insurance

(651) 310-4203



==============================================================================
This communication, including attachments, is confidential, may be subject to legal privileges, and is intended for the sole use of the addressee. Any use, duplication, disclosure or dissemination of this communication, other than by the addressee, is prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy this communication and all copies.