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

date: Thu, 17 Mar 2016 11:32:03 +0000
from: Keith McCully <keithmccully@xxxxxxxxx>
subject: 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?

You can find the CHKIN/CHKOUT status with a call to qp0lGetAttr (an API I
didn't even know existed). An example here:

http://code.midrange.com/35c8f45786.html

Some of the APIs are pretty straightforward; qp0lGetAttr really isn't one
of them. A more complicated example retrieving both the CHKIN/CHKOUT status
and the object's authorizations:

http://code.midrange.com/3f643b4d88.html

If you had a utility that printed out the contents of the IFS, you could
replace the call to 'stat' with a call to qp0lGetAttr, and modify it to
have a listing of which files are currently checked out.

Chris
www.brilligware.com - home of MineSweeper5250

----------------------------------------------------------
Show me your flowcharts and conceal your tables, and I
shall continue to be mystified. Show me your tables, and
I won't usually need your flowcharts; they'll be
obvious. Frederick Brooks