Dear all
Situation:
We try to run Stored Procedures on DB2 Databases located on MVS - which should not matter, but who knows / see below ...
Running SQL-statements - e.g. SELECT ... - runs fine, therefore we know that in general the situation is ok: SQL-Agent, CONN-Objects, DB2 user access, etc.
But when running
any StoredProcedure we always get the following message:
2023-01-26 10:11:20 - U02000005 Job 'JOBS.TESTSP.SQL.NATIV' with RunID '1136009' is to be started.
2023-01-26 10:11:21 - U02012001 Successfully established connection to 'Z033:9936/DBP9:currentSchema=UC4TEST;' with user 'g008653'.
2023-01-26 10:11:21 DB2
2023-01-26 10:11:21 DSN12015
2023-01-26 10:11:21 - U02012014 JDBC Driver version: 4.32.28
2023-01-26 10:11:21 call sysproc.dsnwzp(?)
2023-01-26 10:11:21 DB2 SQL Error: SQLCODE=-440, SQLSTATE=42884, SQLERRMC=PROCEDURE;SYSPROC.DSNWZP, DRIVER=4.32.28
2023-01-26 10:11:21 NO AUTHORIZED PROCEDURE NAMED SYSPROC.DSNWZP HAVING COMPATIBLE ARGUMENTS WAS FOUND. SQLCODE=-440, SQLSTATE=42884, DRIVER=4.32.28
2023-01-26 10:11:21 - U02004025 Job-script execution was aborted.
2023-01-26 10:11:21 - U02012006 SQL Rollback executed
(Of course) The same StoredProcedures do run correctly using the same users when run by the db2-cli.
When StoredProcedures are run on non-MVS-DB2 they also run fine. So we have no systematic problem.
Did somebody come accross a similar problem?Btw: We did some experiments with the CONN-(JDBC-parameters)Database-AdvancedSettings during the problem analysis and had the impression, that they are just not taken into account.
------------------------------
Stefan Lerch
Senior Consultant
at
www.systempartners.chFor AUTOMIC trainings please check
https://www.systempartners.ch/en/homee/services/training/trainingautomic/------------------------------