Subject: | |
From: | |
Reply To: | |
Date: | Mon, 19 Oct 2009 15:40:10 +0100 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
A bit late to reply I know but I don't check the list that often these
days but do you not simply append "/LOCKWORD" to the file name?
I has been I while since I did it so forgive me if I am wrong.
Have been writing tools for SQL Server to pass the days
e.g.
<plug>
http://www.sqlserverjobmonitor.com
</plug>
Ken Vickers
Walter J. Murray wrote:
> Greetings,
>
> A few days ago, there was discussion about accessing a KSAM file with a
> lockword from a COBOL program. As I recall, someone made the statement
> that it couldn't be done with the standard COBOL verbs, but required
> using the file system intrinsics. I don't remember anyone challenging
> that statement.
>
> What's the problem using COBOL verbs to access a KSAM file with a
> lockword? It works fine for me. Did I miss something in the
> discussion?
>
> I agree with the person who wrote that he would rather use the COBOL I/O
> statements than intrinsic calls. KSAM was designed specifically with
> COBOL in mind, and it works great.
>
> Walter
>
> Walter J. Murray
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
_____________________________________________________
Computing Solutions Limited
10 St. Andrews Road
Droitwich Spa
WR9 8DN
Company Registered in England and Wales - No. 2540518
_____________________________________________________
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|