Re: Disconnect job / end job question on locks -- MIDRANGE-L

Where she claims she was in that program (and I truly do believe her at
this point) she would not have had a lock on any record.

But now that I think about it, the QSYSOPR message was at 16:37. I got the
phone call from the office manager at 16:40. It took until 16:52 for me to
get back to work and sign on. So I was looking at locks 15 minutes AFTER
the message occurred. The fact she had a lock at 16:52 may not be relevant
at all.

I actually don't really know what the lock was at 16:37.

On Thu, May 3, 2018 at 8:38 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

Another option is to rewrite the application following some guidelines
from a late 1960's book on interactive programming. Basically, you do not
do a read with lock on a maintenance screen. Instead you do a
read
Present screen. When enter is pressed
Read to other variables (old RPGers used to use two files for this. ie: a
logical based on the same pf)
Compare to see if someone else changed the row while you were waiting on
the user to press enter.
If not, proceed with your update

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: "Rob Berendt" <rob@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: 05/03/2018 08:27 AM
Subject: Re: Disconnect job / end job question on locks
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

Heck, I don't know. Go into the program on session 1. From session 2
verify that the record is locked. Go back to session 1 and take the big X

to kill it. From session 2 see if the record is still locked. If so,
time it until the lock is released. Then we can start looking at things.

See also
CHGTELNA Session keep alive timeout . . . TIMMRKTIMO

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: "Jeff Crosby" <jlcrosby@xxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: 05/03/2018 08:17 AM
Subject: Re: Disconnect job / end job question on locks
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

The RNQ1218 Unable to allocate a record in file <filename> (R C G D F)
was
at 16:37.

But that's while I wasn't at work.

When I got back to work, did the WRKOBJLCK, called her, etc., all that
activity happened within a minute. Her 4 joblogs end at 16:52:36,
16:52:37, 16:52:37, and 16:52:45. (One of the 16:52:37 jobs was the one
updating open POs).

My point is that 1) I saw she had the lock, 2) called her immediately, and
3) she said she had closed/signed off the sessions at least 5 minutes
earlier.

So is there a delay of that long (several minutes) for the job actually
ending and the locks getting released?

On Thu, May 3, 2018 at 7:50 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

Jeff,
You didn't post the time of the original message:
RNQ1218 Unable to allocate a record in file <filename> (R C G D F).
Whose to say that didn't happen before the user shutdown?
If the joblog is gone it may be in DSPMSG QSYSOPR or DSPLOG.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: "Jeff Crosby" <jlcrosby@xxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"

<midrange-l@xxxxxxxxxxxx>

Date: 05/03/2018 07:44 AM
Subject: Disconnect job / end job question on locks
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

V7R3, IBM i is in the cloud and we connect via site-to-site VPN.

So yesterday I leave work 30 minutes early for an appointment. About 5
minutes out I get a call from the office manager that the "Daily

Reports"

batch job (creates and emails a bunch of status reports) is at a
standstill, not moving. So I head back to work. Within a minute I get

a

text that QSYSOPR has a message that needs a response (got a love/hate
relationship with message queue monitors).

I arrive at work and the message in QSYSOPR is the wonderful RNQ1218
Unable
to allocate a record in file <filename> (R C G D F).

Before replying, I do a WRKOBJLCK <filename> to see who has it and what
they're doing. A buyer is updating an open PO. I reply R, then call

the

buyer. She claims she is not on at all, no 5250 sessions open and she

has

been signed off for 5-10 minutes. I do another WRKOBJLCK <filename> and
the updating a PO lock is gone. Remember, this is all in less that a
minute and she claims to have been off at least 5 minutes.

I look at her spool files for joblogs. She started 4 5250 sessions just
after 8am. Every one of them has this message, within seconds of each
other:

CPF5140 Diagnostic 70 05/02/18 16:52:36.989193
QWSERROR QSYS 0573 QWSGET QSYS 0683
Message . . . . : Session stopped by a request from device <device>.

Cause . . . . . : The request shutdown was caused by either the user
turning the power off, by a device error, or the ASCII controller
inactivity timer expired.
Recovery . . . : Close the files and vary the device off (VRYCFG
command). If the problem occurs again, enter the ANZPRB command to run
problem analysis.

Each job ended (per the joblog) within seconds of the above message. And
one of the joblogs shows that she was in the PO updating program at the
time.

Doesn't this indicate that within the ACS 5250 session (and without
signing
off), she did one of 1) clicked Communication/disconnect, 2) File/exit

(or

exit all), or 3) Clicked the X in the upper right corner of the window

to

close it? I'm pretty sure the answer to this is yes. Furthermore, I

note

she has done this several days in a row.

The secondary question is would the job locks (like that file) hang

around

for some minutes? Doesn't seem to me like they would, but . . .

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@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
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: http://amzn.to/2dEadiD

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
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: http://amzn.to/2dEadiD

--

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@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
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: http://amzn.to/2dEadiD

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
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: http://amzn.to/2dEadiD

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
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: http://amzn.to/2dEadiD