×
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.
Yes, we knew what was doing it too. So we wrote a CLP that checked for
that file and it always came back with the same user.
We just could never find out why it was being locked/left open
after she used it.
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/14/2016 12:29 PM
Subject: Re: Weird CPFA09E/CPD384E on a SAV
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
On 3/14/16, 10:14 AM, broehmer@xxxxxxxxxxxxxxx wrote:
http://www.rpgpgm.com/2015/07/checking-for-locked-objects-in-qdls-and.html
Well, we know EXACTLY what's locking the objects.
I was asked what OS release this is happening under. It's V6R1, running
(FWIW) on an E4A.
Looking again at
<
http://www-01.ibm.com/support/docview.wss?uid=nas8N1016325>
I see that the UPDHST thing apparently only applies to "checked-out"
files, not files that are actually open.
We can save QSYS.LIB objects while active; why is it that this is
happening on an IFS object even with SAVACT(*YES) SAVACTOPT(*ALL)?
I suppose I could simply catch the exception with a MONMSG. Or add an
OMIT to the SAV.
--
JHHL
midrange.com
