I think you're right Skip. My impression from some old coding attempts,
is that Unix by default lacks the kind of integrity we're used to seeing
on MVS. Clists and Rexx's die if they get an error but a shell script
just chugs along as if nothing happened. I remember coding a multi-task
program in C and if I wrote to stdout (the screen) from 2 tasks at about
the same time, one message might end up in the middle of another. This
is strange stuff that I would have thought would be taken care with an
enqueue under the covers.
My guess is it's just a different mentality. If you want to lock your
open file in Unix, you have to lock it yourself, otherwise a simpler
(and quicker) method is used where anybody can access and even write to
the same file at the same time as someone else.
I could be wrong with a lot of this... it's just my impression as a
part-time Unix user/programmer.
Jesse 1 Robinson wrote:
My first reaction was to respond acerbically that file integrity never quite
made the UNIX afterthought list, but that would have been unkind, so I won't.
But if it works, it might be worth a try. It's not customer data anyway...
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
