Re: Serializing changes to parmlib/proclib


Martin, Mike wrote:
All,

We are beginning to customize our z./OS 1.7 (to replace 1.4). We have
several folks who will be updating parmib and proclib. There is a
possibility that we might step on each other's changes. Say, for
instance, two people are making changes to COMMNDxx. Some people stage
their changes, i.e. copy parms out to another temporary library and work
on them and... then later... copy them back to parmlib.

My question.... Is there a way to lock member so that only one person
can be working on a member (or members) while they have the lock (the
lock could be held for days at a time)?

LMF
SCLM
Changeman
PanValet
Librarian
and of course, everyone's all time favorite....
....
....
Endevor :)

Mickey

.

Relevant Pages

  • Re: When is "volatile" used instead of "lock" ?
    ... you're not asserting there can be no JIT optimizations of members ... lock { ... surrounding access to a member doesn't stop the compiler from having ... memory references can move to later than a volatile write or earlier ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: When is "volatile" used instead of "lock" ?
    ... The sample clearly shows that putting a member between Enter/Exit does not ... that only the locked object is the volatile ... Nah - I'll fix it just using an extra lock. ... uncomment the volatile on continueRunning and it runs as ...
    (microsoft.public.dotnet.languages.csharp)
  • Serializing changes to parmlib/proclib
    ... We are beginning to customize our z./OS 1.7. ... Is there a way to lock member so that only one person ... For IBM-MAIN subscribe / signoff / archive access instructions, ...
    (bit.listserv.ibm-main)
  • Re: class instances and threads
    ... > I'd like to know if i need mutexs to lock the use of ... > member methods of a class instance shared between ... if you need to lock your critical regions without ...
    (comp.lang.cpp)