Hi All;
I have what I hope is a simple environmental problem. I have some SQL
that creates a VERY simple procedure. When the create is executed from
Quest (from a Windows client) - no problem. As soon as I go to the
command line (on the actual DB server), I get a strange (and somewhat
frightening) sqlcode -1007 (corrupt tablespace!?). I'm pretty sure it
has something to do with CLP/statement terminator behavior, but cannot
find the recipe for success. Any help really appreciated!

Here's the SQL that runs fine from Windows/Quest:

CREATE PROCEDURE DVLXTRCT_TEST_ECHO_SP
(IN P_ECHO_TEXT CHARACTER(50)
)
 DYNAMIC RESULT SETS 1
 LANGUAGE SQL
 NOT DETERMINISTIC
 CALLED ON NULL INPUT
 READS SQL DATA
 INHERIT SPECIAL REGISTERS
 pgm: begin
               DECLARE c1 CURSOR WITH RETURN TO CALLER FOR
               values(P_Echo_Text)
;
 -- to return result set, do not CLOSE cursor
       OPEN c1;
 end;
=========================================================
=========================================================

Here is my command line session with the sqlcode:
--> db2 connect to xxxxx

  Database Connection Information

Database server        = DB2/AIX64 8.2.3
SQL authorization ID   = xxxxxxxx
Local database alias   = xxxxxxxxxxx

--> db2 -atf pete_test_proc.ddl

SQLCA Information

sqlcaid : SQLCA     sqlcabc: 136   sqlcode: 1007   sqlerrml: 0
sqlerrmc:
sqlerrp : SQL08023
sqlerrd : (1) 0                (2) 0                (3) 0
          (4) 0                (5) 0                (6) 0
sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)
          (7)      (8)      (9)      (10)       (11)
sqlstate:

explanation of sqlcode -1007
----------------------------------------------------------
User Response:

Discontinue use of the object or table space. Contact IBM service
to inspect the object and the table space.

sqlcode :   -1007

====================================================================
====================================================================

I have tried replacing the semi-colons with @, but get the same error.
Help?!

Pete H