Geez,
I just realized I never said that. That's what
IBM said would fix it. We use a CLP to find
them and then use CHKIN to unlock them.
Sorry.
From: Roger Harman <roger.harman@xxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/14/2016 12:54 PM
Subject: Re: Weird CPFA09E/CPD384E on a SAV
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Why not use the CHKIN command on the offending objects and see if your
problem goes away?
Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power
________________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> on behalf of
broehmer@xxxxxxxxxxxxxxx <broehmer@xxxxxxxxxxxxxxx>
Sent: Monday, March 14, 2016 10:41 AM
To: Midrange Systems Technical Discussion
Subject: Re: Weird CPFA09E/CPD384E on a SAV
I really should have said "Checked out" not open.
We were on V6R1 also. E4C.
Bill
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
--
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:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
"CONFIDENTIALITY NOTICE: This e-mail transmission (and/or the attachments
accompanying it) contain confidential information belonging to the sender.
The information is intended only for the use of the intended recipient.
If you are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution or the taking of any action in reliance
on the contents of the information is strictly prohibited. Any
unauthorized interception of this transmission is illegal under the law.
If you have received this transmission in error, please promptly notify
the sender by reply e-mail, and then destroy all copies of the
transmission."
--
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:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
midrange.com
