By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,558 Members | 1,060 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,558 IT Pros & Developers. It's quick & easy.

Problem with procedure ...

P: n/a
Hi!

We have two (nearly) identical systems, one is a production system, the
second is a quality system.

Becaus of any events, I get an error in the quality system:
SQL0444N Routine "*INTOUSER" (specific name "SQL030826105315132") is
implemented with code in library or path
"...sqlproc/ROLPROD/REAS/P0531516",
function "pgsjmp" which cannot be accessed. Reason code: "4".
SQLSTATE=42724

Fact is, that the procedure did run a while ago and nobody knows, what
was changed in the quality system.

DB2-8.1 Fixpack 4 on z/Linux.

Thanks for any hint.

Dirk
Nov 12 '05 #1
Share this Question
Share on Google+
7 Replies


P: n/a
Dirk Deimeke wrote:
Hi!

We have two (nearly) identical systems, one is a production system, the
second is a quality system.

Becaus of any events, I get an error in the quality system:
SQL0444N Routine "*INTOUSER" (specific name "SQL030826105315132") is
implemented with code in library or path
"...sqlproc/ROLPROD/REAS/P0531516",
function "pgsjmp" which cannot be accessed. Reason code: "4".
SQLSTATE=42724

Fact is, that the procedure did run a while ago and nobody knows, what
was changed in the quality system.


Have you verified that the library named "P0531516" actually exists in the
directory under sqllib/function?

--
Knut Stolze
Information Integration
IBM Germany / University of Jena
Nov 12 '05 #2

P: n/a
Knut Stolze:
Have you verified that the library named "P0531516" actually exists in the
directory under sqllib/function?


Yes, it does exist in a subdirectory.

Thanks.

Dirk
Nov 12 '05 #3

P: n/a
I recently set up a new instance to develop stored procs and I too was
getting SQL0444 error referenceing "pgsjmp" errors. I was getting a
different reason code though. My problem was resolved by chnaging the
compile string. Have you checked the compile string, and tried
building the procedure?


Dirk Deimeke <de*****@gmx.de> wrote in message news:<10*************@deimeke.newsoffice.de>...
Knut Stolze:
Have you verified that the library named "P0531516" actually exists in the
directory under sqllib/function?


Yes, it does exist in a subdirectory.

Thanks.

Dirk

Nov 12 '05 #4

P: n/a
Private Pyle:
I recently set up a new instance to develop stored procs and I too was
getting SQL0444 error referenceing "pgsjmp" errors. I was getting a
different reason code though. My problem was resolved by chnaging the
compile string. Have you checked the compile string, and tried
building the procedure?


I have a SQL-procedure with "create procedure ...".

How do i set the compile string?

Greetings

Dirk
Nov 12 '05 #5

P: n/a
Dirk Deimeke <de*****@gmx.de> wrote in message news:<21****************@dirk.deimeke.net>...
Private Pyle:
I recently set up a new instance to develop stored procs and I too was
getting SQL0444 error referenceing "pgsjmp" errors. I was getting a
different reason code though. My problem was resolved by chnaging the
compile string. Have you checked the compile string, and tried
building the procedure?
I have a SQL-procedure with "create procedure ...".

How do i set the compile string?

Greetings


Do you have these two variables set?

DB2_SQLROUTINE_COMPILE_COMMAND
DB2_SQLROUTINE_COMPILER_PATH

Check it out using db2set -all, if not you need to set the path to the
compiler and also set the compile string in the
DB2_SQLROUTINE_COMPILE_COMMAND variable.

Dirk

Nov 12 '05 #6

P: n/a
Private Pyle:
Do you have these two variables set? DB2_SQLROUTINE_COMPILE_COMMAND
DB2_SQLROUTINE_COMPILER_PATH
No.
Check it out using db2set -all, if not you need to set the path to the
compiler and also set the compile string in the
DB2_SQLROUTINE_COMPILE_COMMAND variable.


The same setting (without the variables) works for our production
machine.

I think it is a restore problem.

We restored our production system into a different database on our
quality system. Some references seem to be broken.

Do I have to drop all procedures and then create them again?

Regards

Dirk
Nov 12 '05 #7

P: n/a
How did you resolve this. I have exactly the same problem.

Nov 12 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.