RE: CHKIN/CHKOUT

Those commands are hold overs from the System/38 days. Not of much use
anymore......

That is until you consider recovery operations, recovery of those marked
objects become interesting.

Best advice, stay clear.....


--
Jim Oberholtzer
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Justin Taylor
Sent: Friday, December 01, 2017 5:08 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: CHKIN/CHKOUT

Which is why I said, "The biggest difference being that it locks to the user
rather than the job".


________________________________
From: Mark S Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>
Sent: Friday, December 1, 2017 12:33 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: CHKIN/CHKOUT


CHKOUT and CHKIN are not like ALCOBJ and DLCOBJ because ALCOBJ and DLCOBJ
are "temporary" locks that do not persist across job boundaries, while
CHKOUT and CHKIN permanently "stamp" the object with that information, and
it persists even across IPLs.

On 12/1/2017 1:18 PM, Justin Taylor wrote:
Looks to be for IFS files what ALCOBJ/DLCOBJ are for system objects. The

biggest difference being that it locks to the user rather than the job.


--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx 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:
http://amzn.to/2dEadiD