mutexing a single session

Article View: bit.listserv.appc-l

Article #376

Back to bit.listserv.appc-l Previous Next

#376

From: Richard L. Gray ((919) 254-7408)
Date: Thu, 27 Jan 1994 18:10

14 lines
1580 bytes

Tom,
   If you're using CM/2 1.0 or greater, I'm not sure I understand the
problem (i.e. why you need the mutex).  The cmaccp doesn't use the
session until an an allocate arrives.  If you use cmsrc to make the
allocate wait for an available session, and you are managing your tp
instances with the extension calls, you should have no problem, right?
Alternatively, you could queue work on one side or the other, and do
all the updates at once.  For instance, when the pc sends a request to
IMS, it could ask if there are any responses for earlier work waiting
to be picked up.  Of course, the frequency of requests could cause a
problem if this only happens once a month and you have to wait till
next month for the answer.
Richard L. Gray
APPC Market Enablement

Technical Details

Message-ID: <APPC-L%94012716270391@AMERICAN.EDU>

Path: arc1-ca.pugleaf.net!gmd.de!Germany.EU.net!EU.net!howland.reston.ans.net!news.cac.psu.edu!psuvm!auvm!VNET.IBM.COM!rlgray

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10aed9,9ee4f0168942a29e,start
X-Google-Attributes: gid10aed9,public
X-Google-ArrivalTime: 1994-01-27 01:04:20 PST
Path: arc1-ca.pugleaf.net!gmd.de!Germany.EU.net!EU.net!howland.reston.ans.net!news.cac.psu.edu!psuvm!auvm!VNET.IBM.COM!rlgray
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.appc-l
Return-Path: <@AUVM.AMERICAN.EDU:owner-appc-l@AUVM.AMERICAN.EDU>
Return-Path: <@AUVM.AMERICAN.EDU,@CUNYVM.CUNY.EDU:rlgray@VNET.IBM.COM>
X-Addr: Internet:  rlgray@vnet.ibm.com NO SNIVELING!
Message-ID: <APPC-L%94012716270391@AMERICAN.EDU>
Date: Thu, 27 Jan 1994 13:10:02 EST
Sender: APPC Discussion List <APPC-L@AUVM.BITNET>
From: "Richard L. Gray ((919) 254-7408)" <rlgray@VNET.IBM.COM>
Subject: mutexing a single session
Lines: 13