Elvis wrote:
Right-Click on Schemas and click on "Select schemas to display" and add
MANLIB to it. Now drill down to MANLIB Stored Procedures and you
should see it.
This process, which you and another poster suggested, worked perfectly.
Thank you.
>
Stored procedure definitions can also be seen by doing:
SELECT * FROM SYSPROCS
Could it be I don't have enough permissions for this?
Connected to relational database S10dcd4b on 192.168.1.43 as Jbailo -
073480/Quser/Qzdasoinit
SELECT * FROM SYSPROCS
SQL State: 42704
Vendor Code: -204
Message: [SQL0204] SYSPROCS in JBAILO type *FILE not found. Cause . . .
.. . : SYSPROCS in JBAILO type *FILE was not found. If this is an ALTER
TABLE statement and the type is *N, a constraint or partition was not
found. If this is not an ALTER TABLE statement and the type is *N, a
function, procedure, or trigger was not found. If a function was not
found, SYSPROCS is the service program that contains the function. The
function will not be found unless the external name and usage name do
not match exactly. Examine the job log for a message that gives more
details on which function name is being searched for and the name that
did not match. Recovery . . . : Change the name and try the request
again. If the object is a node group, ensure that the DB2 Multisystem
product is installed on your system and create a nodegroup with the
CRTNODGRP CL command. If an external function was not found, be sure
that the case of the EXTERNAL NAME on the CREATE FUNCTION statement
exactly matches the case of the name exported by the service program.
Processing ended because the highlighted statement did not complete
successfully
--
Texeme Construct
http://www.myspace.com/texeme