You shall never use PIPE CMS xxx if you want to be sure what happens. Use
"PIPE COMMAND CMDCALL CREATE LOCK" b2bfile "UPDATE SESSION",
"| VAR MESSAGE"
"PIPE COMMAND QUERY LOCK" b2bfile ,
"| STEM LOCK_MSG."
"PIPE COMMAND DELETE LOCK" b2bfile "| HOLE"
Kris,
IBM Belgium, VM customer support
> We have had problems where the WRITE to an SFS file does not close
> quickly enough for a subsequent READ. IBM may have addressed all those
> problems.
> I believe someone suggested doing a LOCK on the file. We do just that
> with a LOG file that we have for an application that has data put into
> it by several SVMs somewhat concurrently.
> We use a LOCK when the SVM want do do a write and test for it before
> attemting to do a WRITE. You could put the LOCK on the WRITE and test
> before the READ if the LOCK exists.
> Our code looks somewhat like:
> b2bfile = "B2BLOG" date("S") "L"
> "PIPE CMS CREATE LOCK" b2bfile "UPDATE SESSION",
> "| VAR MESSAGE"
>
> "PIPE CMS QUERY LOCK" b2bfile ,
> "| STEM LOCK_MSG."
>
> "PIPE CMS DELETE LOCK" b2bfile "| HOLE"
> Jim
> --------------------------------------------------------
> If you are not an intended recipient of this e-mail, please notify the
> sender, delete it and do not read, act upon, print, disclose, copy,
retain
> or redistribute it. Click here for important additional terms relating
to
> this e-mail. http://www.ml.com/email_terms/
> --------------------------------------------------------
