The only likely forgiveable scheme is that when the old CK program was
written, exclusive access was assumed.

The next version was done by someone following the book, which indicates
that Exclusive (lock) be used around writes.

Why it takes longer is yet to be seen - iirc the native cobol should run
faster.  there could be any number of reasons, such as no locks takes no
time, but what else is different?

Tracy Pierce

> -----Original Message-----
> From: Peter Smithson [mailto:[log in to unmask]]
> Sent: Tuesday, September 28, 2004 4:32 AM
> To: [log in to unmask]
> Subject: Comparing COBOL verbs with CK intrinsics
>
>
>  Hi,
>
> I've got a test program which can now run either with COBOL
> verbs or CK
> intrinsics.  It tests reading and writing to three KSAM XL files.
>
> It supposedly does the same thing in either mode.
>
> The CK route takes 18 hours and the COBOL verb route takes 22 hours.
>
> I'm wondering why there's a difference and notice that the code has
> "EXCLUSIVE" and "UN-EXCLUSIVE" around the "WRITE" and "REWRITE" verbs.
> This wasn't done for CKWRITE and CKREWRITE.  Reading the
> manuals for the
> CK intrinsics I see it says that CKLOCK should be used on a
> CKWRITE (the
> files have been opened in a shared mode).
>
> But I have feeling I read somewhere that KSAMXL removes the need to do
> this locking.  Is this a throw back to the older version of KSAM?
>
> Any idea why the programer would have thought locking was required for
> COBOL verbs but not for the CK intrinsics?
>
> Thanks.
>
> Peter
> --
> http://www.beluga.freeserve.co.uk
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *