RE: Odd error ... program object in use by another thread, but the job only has one thread.

David,

This may be way off the mark, but do you use IBM's defaults when
allocating an object?  Reading IBM's help for lock scope makes me wonder
if your client doesn't have the lock scope parm for ALCOBJ set to
*THREAD.  I wouldn't think this would cause the problem you are
encountering, but stranger things have happened.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Friday, July 15, 2005 1:03 PM
To: Midrange Systems Technical Discussion
Subject: Odd error ... program object in use by another thread, but the
job only has one thread.


Folks:

I'm encountering a very weird problem ... one of our customers is
encountering a problem when our product (Implementer) is trying to
rename a program object.  We are receiving a "CPFA030-Object already in
use" error.

The details of the message are 'Cannot allocate object for reason code
1. 1 -- Object PGMA of type *PGM in library LIBA is in use by another
thread.'

The odd part is ... the job we're running in only has a single thread...
and the object is exclusively allocated to the job that is trying to
execute the rename.

One thing of note is the fact that they are using IASPs.

A search on CPFA030 on both Google and the knowledgebase turned up with
nothing.

This is happening on a V5R3 system.

Any suggestions?

Thanks!

david