Just wanted to reply for the archives that this did fix my problem. Jasper reports is now working from my PC to the iSeries.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Carlin
Sent: Monday, March 16, 2009 9:38 AM
To: Midrange Systems Technical Discussion
Subject: Re: Deleting QZDAPKG
I have followed the steps from the IBM document recently without issue.
http://www-01.ibm.com/support/docview.wss?rs=0&dc=DB520&dc=D900&dc=D800&dc=DA900&dc=DA800&q1=377117296+AND+AS400KBXXYYZZRCH&uid=nas186256a81004eff5c86256ff500732959&loc=en_US&cs=UTF-8&lang=all
I can't speak to the specifics of adding it to your save procedure because I don't know what you end or don't end during a save, but this procedure (inserted into the end of your save or not) works very well.
----- Original Message -----
From: "Mike Cunningham" <mike.cunningham@xxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Monday, March 16, 2009 8:53:17 AM GMT -05:00 US/Canada Eastern
Subject: Deleting QZDAPKG
I am trying to get Jasperserver to work with DB2/400 and Jasper is causing a "CPD4392 Attributes of value number 2 in field HVR0002 not valid" error to occur in one of the QZDASOINIT jobs followed by an SQL0901 error. The joblog also shows...
Attributes of value number 2 in field HVR0002 not valid.
PROBLEM WITH QDT FOR STMT# 16, QDT# 1, OCLE 1
QDT@:80000000 00000000 1dd01517 ec4a8df0
WSQCQDT@:80000000 00000000 1dd01517 ec4a8df0
WSQPAS@: 80000000 00000000 1dd01517 ec000a00
CURSOR NAME IS FILE
STMT NAME IS FIFAABTALC
PACKAGE NAME IS in library
Dump output directed to spooled file 2, job 208239/QUSER/QZDASOINIT
created on system AS400ADM on 03/16/09 08:16:17.
The spool dumps are not much help. I did find this article from a few years back about deleting QZDAPKG to fix this problem.
http://www.itjungle.com/fhg/fhg091306-story03.html
I have other jobs using JDBC and OLEDB connections without problem and since there is only one QZDAPKG file on the system I would suspect it is used with all external database requests not just the ones coming from Jasper yet Jasper is the only one generating the error. I can tell from the dumps that Jasper is trying to get a list of tables from a library at the time the error occurs and our other JDBC jobs do not query SQL for a list of available tables or columns.
Has anyone had to do this recently and is deleting the QZDAPKG file as save as the article makes it sound? Is it something I could safely add (one time) to my nightly save routing to do the delete in the middle of the night and be sure things will start ok after the backup ends?
midrange.com
