Kris,
thank you for your explanation, you are right. I didn't get in real
trouble with it. I have found it out at a customer's system accidently
while I showed him the SFS-locking. He then tried directly the FTP. If
you use ftp with its own userid then it works as expected with the
message "file sharing conflict".
kind regards
Franz Josef Pohlen
Kris Buelens schrieb:
I guess the userid in the FTP session is the same as the one Xediting
the file in which case SFS is right permitting the overwrite. The
same problem happens when Xediting user submits a batch job: the batch
worker machine can update the file. Or, when using remote SFS your
userid can update that file from another VM system.
This is why it is **very** bad practice to use FF (FFILE) or SS
(SSAVE) as standard XEDIT command in lieu of FILE and SAVE. When the
Xedited file was updated by something else, XEDIT's FILE command will
tell "file already exists..."
2008/3/8, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
Hi listers,
I like to use the shared file system in cms instead of the standard
minidisks. Now I have a problem with the file locking and I want to ask
you if this might be only a configuration or a real software bug. I have
first created a file on SFS and afterwards re-edited it to lock the
file. When I try to xedit the file from another user the I get the
correct message "DMSXFI1215E File Y Y T1 is locked UPDATE by another
user". But while editing the file I can overwrite it with ftp without
problems. I assume, this is a bug, but I want to make sure before
opening a pmr.
--
kind regards
Franz Josef Pohlen
