I'll just pretend I'm Domino support from HCL and say turn on yet another debug parameter and see if it happens again.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Paul Roy
Sent: Thursday, January 31, 2019 1:20 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Stream file check out
Checkouts are usually audited ... if audit is active and receivers still available DSPJRN QAUDJRN should give you more info.
When a stream file is checked out, you need to use CHKIN command to release the lock.
I have seen some programmers using CHKIN/CHKOUT command to verify the existence of a stream file... They say this is CHKOBJ for stream files...
this (bad) habits could result in stream files checked out... and locked.
..
From: Rob Berendt <rob@xxxxxxxxx>
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Date: 31/01/2019 17:07
Subject: Stream file check out
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
I have a few stream files locked.
Before blindly adding them to an omit list on the nightly backup I'm trying to determine why they are locked. Only appears to be happening on this lpar.
This lpar is a HA target lpar. I've tried a few tools like WRKLNK, DSPIFSLCK and iACS and they all say it is not currently being used but it is checked out by a coworker. Coworker has no idea why it is checked out by him. Checked out January 15, 2019 11:22:25. QHST shows several 441615/QUSER/QZSOSIGN requests associated with him at that time. This lock date/time is over a month past our last IPL. So not a startup issue.
So how does one find a log of the checkout?
Last changed date is about 5 years ago.
Object is currently journaled . . . . : No
These are java jar files.
I'm leaning towards using the unlock option and see what happens.
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
--
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
midrange.com
