Re: Locked and yet not locked . . . .

Seems, to me, that RUNSQLSTM might have initiated a background process that
holds the lock. Why it is an issue now depends on system load. Is this
error repeatable? Is it run at different times of day? If it repeats,
what happens if a DLYJOB is inserted before the GRTOBJAUT? Maybe a delay
of 1 second might be sufficient. Or, a MONMSG after GRTOBJAUT to perform
the DLYJOB and try the GRTOBJAUT one additional time.

Just wild guess, based on a bug I fixed in a program. That bug wasn't in
some potential back-end processing. But, this sure seems like the same
condition.


John McKee

On Fri, Oct 7, 2016 at 8:39 PM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

This is weird.

I've got a CL program that runs RUNSQLSTM on a member containing code to
generate a view with the same name as the member. And at the end, to ensure
that the view has the same authorities as its based-on PF, I've got the
statement:

GRTOBJAUT OBJ(&LIB/&MBRNAME) OBJTYPE(*FILE) +

REFOBJ(&LIB/&PFNAME)

where &LIB is the library, &MBRNAME is the name of both the member and the
SQL View that member generates, and &PFNAME is the name of the based-on PF.

The program has been in service for years, and this particular statement
for a year and a half, without any problems.

And yet recently, it's been going into a lock wait, and then throwing a
chain of exceptions:

File FOO in library BAR in use.
Function not done for user profile BAZ.
One or more errors occurred during processing of command.
CPF2227 received by PLUGH at 7500. (C D I R)

(FOO being the SQL View we just created) And yet, WRKOBJLCK doesn't find
any locks on FOO.

Anybody have any idea what could cause that?

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.