How can I delete a temporary AS/400 collection

  • Thread starter Thread starter Steve Cahoon
  • Start date Start date
S

Steve Cahoon

I am running an ADO application from Access that creates a
temporary collection on the AS/400, then runs multiple
AS/400 queries to build a result set. I then download the
result set to Access. Finally, I drop all of the tables
that I have created on the AS/400. As a last step, I would
like to drop the AS/400 collection but the command errors
out with "[IBM][Client Access Express ODBC Driver (32-bit)]
[DB2/400 SQL]SQL0913 - Row or object XXX in *N type *LIB
in use." However, since my application is the only one
using the library I know that it is not in use. Do you
have any idea how I can remove the collection? I am
executing a commit and a release but to no avail.
 
Steve Cahoon said:
I am running an ADO application from Access that creates a
temporary collection on the AS/400, then runs multiple
AS/400 queries to build a result set. I then download the
result set to Access. Finally, I drop all of the tables
that I have created on the AS/400. As a last step, I would
like to drop the AS/400 collection but the command errors
out with "[IBM][Client Access Express ODBC Driver (32-bit)]
[DB2/400 SQL]SQL0913 - Row or object XXX in *N type *LIB
in use." However, since my application is the only one
using the library I know that it is not in use. Do you
have any idea how I can remove the collection? I am
executing a commit and a release but to no avail.
Click to expand...

If you create the objects in the QTemp library they will automatically be
destroyed when you disconnect.
 
Hi Rick,

Thank you for your help. The application actually connects
to multiple AS/400s during processing so the application
connection is reused (i.e. closed and opened for another
database connection) So, the qtemp library won't work for
the application.

Thank you,
Steve

-----Original Message-----
Steve Cahoon said:
I am running an ADO application from Access that creates a
temporary collection on the AS/400, then runs multiple
AS/400 queries to build a result set. I then download the
result set to Access. Finally, I drop all of the tables
that I have created on the AS/400. As a last step, I would
like to drop the AS/400 collection but the command errors
out with "[IBM][Client Access Express ODBC Driver (32- bit)]
[DB2/400 SQL]SQL0913 - Row or object XXX in *N type *LIB
in use." However, since my application is the only one
using the library I know that it is not in use. Do you
have any idea how I can remove the collection? I am
executing a commit and a release but to no avail.
Click to expand...

If you create the objects in the QTemp library they will automatically be
destroyed when you disconnect.


--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com


.
Click to expand...
 
-----Original Message-----
Steve Cahoon said:
I am running an ADO application from Access that creates a
temporary collection on the AS/400, then runs multiple
AS/400 queries to build a result set. I then download the
result set to Access. Finally, I drop all of the tables
that I have created on the AS/400. As a last step, I would
like to drop the AS/400 collection but the command errors
out with "[IBM][Client Access Express ODBC Driver (32- bit)]
[DB2/400 SQL]SQL0913 - Row or object XXX in *N type *LIB
in use." However, since my application is the only one
using the library I know that it is not in use. Do you
have any idea how I can remove the collection? I am
executing a commit and a release but to no avail.
Click to expand...

If you create the objects in the QTemp library they will automatically be
destroyed when you disconnect.


--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com


.
Click to expand...
.
I did some research at the IBM site and found the
Click to expand...
following:
"If you execute a DROP COLLECTION statement from the
client, an inquiry message is sent to the QSYSOPR message
queue on the AS/400, and your application will not respond
until the message is handled on the AS/400 server."
 
Back
Top