RE: Log everything for a user

[Rob Berendt <rob@xxxxxxxxx>]

I wonder why embedded SQL was the culprit?
Operation done without turning off commitment control and failure to commit?
Failure to close cursor?
Some faulty optimizer logic?

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jeff Crosby
Sent: Tuesday, May 28, 2019 7:41 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Log everything for a user

RESOLVED

Darren - embedded SQL was the culprit here too.  I changed the ALCOBJ by
adding CONFLICT(*RQSRLS).   Then, by logging his job and checking the locks
on this file every 5 minutes I confirmed this worked.

Thanks, Darren.  Very much.

On Fri, May 24, 2019 at 8:54 AM Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
wrote:

> I read the help on CONFLICT(*RQSRLS).  Doesn't sound like I could hurt 
> anything by trying this.  I still want to find out exactly what is 
> holding the lock though.
>
> On Fri, May 24, 2019 at 8:39 AM Darren Strong <darren@xxxxxxxxx> wrote:
>
> > For us, access paths as a result of an embedded SQL program accessing 
> > the file is the cause for many locks on a file.  There is an extra 
> > hidden parm in ALCOBJ which requests that these temporary locks be 
> > dropped by all jobs.  I run it sometimes to see if there are any real 
> > locks on a file when I need exclusive access to it.
> >
> > Maybe something like this:
> > ALCOBJ OBJ((FILNAM *FILE *EXCL)) CONFLICT(*RQSRLS)
> >
> >
> >
> > -----Original Message-----
> > From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of 
> > Jeff Crosby
> > Sent: Thursday, May 23, 2019 11:49 AM
> > To: Midrange Systems Technical Discussion 
> > <midrange-l@xxxxxxxxxxxxxxxxxx>
> > Subject: Log everything for a user
> >
> > I've got a user who, on Sundays nights only, gets a lock on a 
> > particular file in his interactive job that does not get released.  
> > Later in his shift it causes an issue for a job he submits that needs 
> > exclusive access to that file.  I can't figure out where that lock is 
> > coming from and not being released.  He doesn't do anything different 
> > on Sunday than the rest of the week, yet this only happens on Sunday.
> >
> > I want to capture the joblog from his interactive job.  I changed his 
> > initial program to include a  LOG(4 00 *SECLVL) LOGCLPGM(*YES) on him 
> > to capture what he's doing.
> >
> > However, if he does a SIGNOFF *NOLIST I won't get the job log anyway.  
> > He signs off via menu option, but it could be one of several menus.  
> > So I either change the option on any menu he could sign off from, or 
> > I change the default on the SIGNOFF command for this weekend.
> >
> > Some other easy way I haven't thought of?
> >
> > Thanks.
> >
> > --
> >
> >
> > Jeff Crosby
> > VP Information Systems
> > UniPro FoodService/Dilgard
> > P.O. Box 13369
> > Ft. Wayne, IN 46868-3369
> > 260-422-7531
> > direct.dilgardfoods.com
> >
> > The opinions expressed are my own and not necessarily the opinion of 
> > my company.  Unless I say so.
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) 
> > mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx 
> > To subscribe, unsubscribe, or change list options,
> > visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> > Before posting, please take a moment to review the archives at 
> > https://archive.midrange.com/midrange-l.
> >
> > Please contact support@xxxxxxxxxxxx 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 Midrange Systems Technical Discussion (MIDRANGE-L) 
> > mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx 
> > To subscribe, unsubscribe, or change list options,
> > visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> > Before posting, please take a moment to review the archives at 
> > https://archive.midrange.com/midrange-l.
> >
> > Please contact support@xxxxxxxxxxxx for any subscription related 
> > questions.
> >
> > Help support midrange.com by shopping at amazon.com with our 
> > affiliate
> > link: https://amazon.midrange.com
>
>
> --
>
>
> Jeff Crosby
> VP Information Systems
> UniPro FoodService/Dilgard
> P.O. Box 13369
> Ft. Wayne, IN 46868-3369
> 260-422-7531
> direct.dilgardfoods.com
>
> The opinions expressed are my own and not necessarily the opinion of 
> my company.  Unless I say so.