× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. May 2019

Re: [EXTERNAL] Log everything for a user

I have remoted in (5250) from home on Sunday evening. His single 5250 job
will have a lock on the file in question.

WRKACTJOB shows he's at MNU-blahblah

and the call stack contains only

Program
QCMD QSYS
QUICMENU QSYS
QUIMNDRV QSYS
QWSGET QSYS
QT3REQIO QSYS

meaning he's back at a menu with nothing in the call stack that shouldn't
be there. Yet he has the lock, so I'm thinking there is somewhere in my
code where I have done an ALCOBJ without a corresponding DLCOBJ. I can't
find it.

I have looked at the joblog when the above condition exists and the job is
still active and seen nothing to indicate some anomaly. Yet he has the
lock.

So I want a full on no holds barred joblog at that point in time. I have
an advanced job scheduler job that will generate a spool file of locks on
that file Sunday evenings every 5 minutes. So armed with both I should see
_when_ the lock got established and what he was doing when said lock was
established and not released.




On Thu, May 23, 2019 at 1:17 PM Craig Richards <craig@xxxxxxxxxxxxxxxx>
wrote:

In my experience, the most common causes of long-term locks are:

1. Maintenance Screen holding a lock waiting for user response. (User
down the pub quaffing ale)
2. Some process has accessed a record for UPDATE but is only doing the
UPDATE based on certain conditions and has not issued an UNLOCK in the
situation where it's not updating.
If this is the LAST record processed (i.e it doesn't go on to read
another record (releasing the previous lock) then the lock remains until
the program ends.

Is it possible that some kind of housekeeping over the weekend triggers
something like 2. above to kick in?

On Thu, 23 May 2019 at 18:08, Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
wrote:

I already know who's got the lock and in what job. What I don't know is
_why_ he still has a lock, when he shouldn't have one any longer.

On Thu, May 23, 2019 at 12:58 PM Rob Berendt <rob@xxxxxxxxx> wrote:

One option is to change the submitted job. Have it check for a lock on
the object. If it finds a lock then list the locks, and snag their
joblogs.
See also:



https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/QSYS2.OBJECT_LOCK_INFO
But that will only tell you the job, program, statement id and a few
dozen
other worthless things... ;-)


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Jeff Crosby
Sent: Thursday, May 23, 2019 12:45 PM
To: Midrange Systems Technical Discussion <
midrange-l@xxxxxxxxxxxxxxxxxx

Subject: Re: [EXTERNAL] Log everything for a user

You know what. I'm just going to change the SIGNOFF default to *LIST
before leaving work tomorrow.. Hardly any sign ons over the weekend,
so
we
should not get too many unwanted joblogs.

On Thu, May 23, 2019 at 11:53 AM Alan Shore via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Hi Jeff
The answer may not be what you want to hear We had the same problem -
and the only way to capture what/who was creating this lock was to
sign on myself on Sunday night We found the cause and made the
necessary change Alan Shore E-mail : ASHORE@xxxxxxxx Phone [O] :
(631)
200-5019 Phone [C] : (631) 880-8640 'If you're going through hell,
keep going.'
Winston Churchill


-----Original Message-----
From: MIDRANGE-L [mailto: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: [EXTERNAL] 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.
--
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.
--
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




As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.