Re: SQL Lock

----- Original Message -----
From: <JReksodiputro@hammer.net>
To: <rpg400-l@midrange.com>
Sent: Thursday, January 10, 2002 11:59 PM
Subject: SQL Lock



> Is there something that I miss?
> Do I need to do something on the SQLRPGLE to "release" the lock for
"EXECUTE
> IMMEDIATE"?

There isn't enough information from the RPG program, but some places to
look:

-- what is the commit level used in the program? *None? or something else.
-- is commit being used properly? (if at all)
-- what is the value of the close sql cursor prompt on the create program?
the default is *endpgm. if it was changed to *endjob, the odp could still be
there.
-- what activation group does the rpg program run in? Caller?
-- what activation group does the cl program run in? Caller? If caller, then
the command line is gonna put you in the default group.

lastly, if this is to be a batch job of some sort, one should not care as
the termination of the job would cause the lock to be released.


===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified Specialist - iSeries Administrator
 -- IBM Certified Specialist - RPG IV Developer

"I want to be different, just like everybody else!"
  - Ceili Rain