Re: [Bulk] RE: Check out and Check in IFS files - Means what?

I use CHKOUT/CHKIN when I want to protect an IFS stream file from updates
with a "short term" lock, say for the lifetime of a particular job or
process. It's the IFS equivalent of ALCOBJ with lock type exclusive allow
read (*EXCLRD).

So typically CHKOUT a file (or directory) at the start of a background job,
do some processing and then CHKIN towards the end of the job. Error
handling should cater for the job to fail with files checked out at point
of failure, so preventing the need for a number of manual CHKINs.

The problem with CHKOUT is that AFIK, there is no straightforward way to
get a list which IFS files are currently checked out?





On 16 March 2016 at 21:46, Mark S Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>
wrote:

Jim:

Wrong on both counts. The user who issues CHKOUT can still modify that
file, even prior to the CHKIN. The CHKIN just releases the lock.

And, it will "back up" just fine, even if the SAV is issued by a different
user. (The SAV is "read-only" as far as the data content of the
"checked-out" file is concerned.)

HTH,

Mark S. Waterbury

On 3/16/2016 4:06 PM, Jim Oberholtzer wrote:

If you check an IFS file out, no updates are allowed to that file until
you
check it back in. I don't think it will back up either.

I don't think I've ever seen it used, except by mistake.

--
Jim Oberholtzer
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
paultherrien@xxxxxxxxxxxxxxxxxx
Sent: Wednesday, March 16, 2016 3:00 PM
To: 'Midrange Systems Technical Discussion'
Subject: Check out and Check in IFS files - Means what?

What does it mean to 'check out' and to 'check in' and IFS object.

I can see in the documentation that these are actions to be taken, but I
do
not see a description of what these actions actually do.

Does this is anyway have anything to do with why I cannot seem to edit a
file in the IFS that everyone has full authority to?



Paul Therrien

Andeco Software, LLC

225-229-2491

paultherrien@xxxxxxxxxxxxxxxxxx

www.andecosoftware.com


--
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.

--
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.