Re: ILE and locked file

Am 20.07.2022 um 17:15 schrieb Jay Vaughn <jeffersonvaughn@xxxxxxxxx>:

so to entertain this theory of death and destruction...

I created a new test CLP that runs in DAG.
It calls my current test CLLE that I just changed to *CALLER.
*CALLER calls my *SRVPGM running in its named actgrp.
But runs fine - no locks on my files.

so this is the same model as the layout that does not work right.. but this
runs fine.

What else?

Jay

On Wed, Jul 20, 2022 at 11:02 AM Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

Besides calling the *SRVPGM procedures...

What else are the CLLE *PGM's doing?

I too suspect there's a problem running the *CALLER CLLE in the (poorly
named) default activation group (DAG).

For instance, if you are calling the CLLE from the command line, then it
would get activated into the DAG. Running ILE code it the DAG is one of
Jon Paris' 7 deadly sins of ILE.

Also as mentioned, best practice would be to have the SRVPGM as *CALLER.
Your CLLE should be either a named activation group or *NEW.

Charles

On Wed, Jul 20, 2022 at 8:18 AM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

I have a *SRVPGM that runs in a named activation group.
It contains a procedure that does the following...
- dltf qtemp.file
- create table qtemp.file
- inserts/updates the qtemp.file

From a CLLE pgm that runs in *NEW, I am testing this procedure call in

the

*SRVPGM.
The procedure is called 4 different times with no issues. Expected

results

for each call.

Now I place those same 4 calls to the procedure into a different CLLE

that

runs in *CALLER (this may have nothing to do with it but just throwing it
out there).
On the 2nd call to the procedure when it tries to do the DLTF, it cannot
allocate the file and fails.
I have tried to DLCOBJ the file from lock state *SHRRD prior but that

does

not work.
(when i do a wrkobjlck on the qtemp.file I see it is locked with *SHRRD)

What are my other options to overcome this? Why does it not do this in

my

test CLLE?

tia

Jay
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com