SQL30073N error querying certain mainframe tables

[jpotucek]

Not sure if I can explain this adequately but here goes...

We are having a peculiar problem when certain users attempt to Select against certain IBM DB2 V9 Mainframe tables via a query tool that we use called AQT we get this error:

40003(-30073)[IBM][CLI Driver][DB2] SQL30073N "0x0000" Parameter value
"0x0000" is not supported. SQLSTATE=58017
(0.05 secs)


This certainly looks like an IBM DB2 Driver error.

The problem that I am facing is that although all users involved have the same DB2 Client version (V9, the same version DB2 Client Drivers, the databases on their clients are all cataloged the same way and the same permissions on the target tables - not all users are having the problem.

All users can launch the command editor and select against the tables but some users cannot query using the query tool and get the above error.

So far I have done the following on the laptops that are experiencing the problem:

Reinstalled IBM DB2 Client
Reinstalled IBM DB2 Drivers
Re-Cataloged all databases in the DB2 Client
reinstalled our Query tool


Our query tools seems to be the common denominator but I'm still thinking it's the IBM Driver.. Anyone want to weigh in with some help or advice?

 

[fredericofonseca]

small test for you to do.

I'll assume your clients will have Excel installed on their machines (or a similar product), and that they will be able to query those DB2 tables using the supplied DB2 driver.

Get them to execute the exact same SQL through MS Query (or equivalent) using the db2 driver. if it works fine there, then most likely the problem is on how your AQT software prepares and invokes the DB2 driver.

Hard to say on my part as I never worked with that AQT thing.

Regards

Frederico Fonseca
SysSoft Integrated Ltd

http://www.syssoft-int.com

FAQ219-2884
FAQ181-2886

 

[papadba]

What has been specified for the DDM parameter?

From an SQLSTATE list:
"58017 The DDM parameter value is not supported."

 

[jpotucek]

The DB2 driver appears to work fine. Users that cannot Query via AQT (Advanced Query Tool) can launch the DB2 Client and Query the table via the DB2 Command Editor - which I'm assuming is using the same DB2 Driver. I have uninstalled - reinstalled AQT on the affected machines and this has not made a difference. ???? not sure what to make of this.

and excuse my ignorance.. but what do you mean by "What has been specified for the DDM parameter?"

 

[papadba]

The error is because the value specified in the DDM parameter is invalid (if the quote from the error list is correct).

If the AQT has a problem and other methods work, suggest you contact the AQT vendor. Maybe they already know how to correct this - or at least provide info on what values are presented for the various parameters.

Does the AQT documentation or the documentation for the db2 driver being used mention the DDM parameter?

 

[MarcLodge]

Hi jpotucek,
Ask one of the users that is receiving this error to send you the query that he/she is running. Get one of the users that has never received the error to run the self same query and see if it errors.

What I am trying to determine here is whether it is user/laptop based or whether it is the actual query that is the problem.

Marc
P.S I think that DDM stands for Distributed Data Management

 

[jpotucek]

Marc,

The query is a simple select * from a small table. The some people are getting the error and some people are not. The people that are getting the error are also getting the error when running the same select * from their DB2 Command Editor. After reinstalling the db2 client, updating the db2 driver and reinstalling AQT I'm not sure what else to try ..

 

[MarcLodge]

Hi jpotucek,
OK, so from what you say, we can rule out the actual query as the source of the problem as exactly the same query works for one user but not for another.

In order to diagnose this one stage further you need to determine whether it is machine or user dependant. If possible, get a user who is experiencing the problem to log on to a machine where the problem doesn't exist, under his/her own userid and rn the query. Also, get the person who is not experiencig the problem to log on to the problematical machine and run the query.

At the end of this process, you should be able to determine whether it's the machine or the userid. At the moment, from what you've said, it sounds as if it's the machine, but you need to be sure before you can go further.

Let us know how you get on.

Marc

 

[fredericofonseca]

Looking at books online

http://www.ibm.com/Search/?q=SQL30073N+&v=16&lang=en&cc=&en=utf&Search=Search

look at these apars.

http://www-01.ibm.com/support/docview.wss?uid=swg1JR21645

http://www-01.ibm.com/support/docview.wss?uid=isg1II14043

Just some examples of what can be the issue


If the users get the error from the db2 client line then the problem is with the DB2 client side of things on that pc. so if the software version is the same, then it will be a configuration problem of the DB2 client, and this can be a leftover from previous installations.

I would compare all registry entries and configuration files (including ODBC driver configuration on control panel) and see what is different from the failing computer(s) and a working one.



Regards

Frederico Fonseca
SysSoft Integrated Ltd

http://www.syssoft-int.com

FAQ219-2884
FAQ181-2886

 

[jpotucek]

I have ruled out permissions issue on mainframe side with the userids - My client IS working and when I log and run the query from a users machine that IS experiencing the problem it fails.. and vice versa. A user who is experiencing the problem can log onto my machine and the query will work. I then compared DB2 drivers and ODBC configurations between the two machines and they were identical. I then uninstalled rebooted and reinstalled DB2 Client on the affected machine with no change.

 

[MarcLodge]

Hi Jpotucek,
It's really looking as if it's the machine, but before we can conclude that 100% I have a last question:

On the machine that is producing the error, can any tables be read successfully, or do they all fail?

Marc

 

[jpotucek]

Yes, most mainframe tables can be queried against with no problem. It is only a handfull of tables that cannot be queries from certain clients. We have ruled out user permissions on the mainframe.

Our mainframe DBA is once again looking at what might be different about this handfull of tables that cannot be queried from certain machines.

I think I've ruled out DB2 connect as well for two reasons.. I can query the tables from the DB2 Connect Server AND if it was a DB2 Connect problem.. I would think all users would be effected. Shoot me now!!

 

[MarcLodge]

Hi jpotucek,
Very weird. You can only assume that the ODBC driver on each machine has got a slightly different setting that, for example, will not allow access to views or maybe synonyms or maybe the table name is slightly longer. It's going to be something odd like that.

When the DBA comes back to you with an answer (and I'm hoping that he will be able to find a commonality amongst the tables you are unable to access) it's then going to be a case of looking at all the settings in the driver to see if any odd occurs.

Let us know what the DBA says.

Marc

 

[papadba]

Does everyone connect to the same db2 subsystem? Is there any chance that for some the data is "local" and for others "remote"?