Article View: comp.lang.perl.misc
Article #70CPSM and CANCEL REQID
From: DENIS R
Date: Wed, 12 Feb 2003 10:17
Date: Wed, 12 Feb 2003 10:17
29 lines
1955 bytes
1955 bytes
Hi,
Environment
We use CPSM (1.4 with CICS TS 1.30) with one TOR and two AORs and we
observe some problem about the CANCEL of ICE with some transactions
whitch use a REQID.
In the application an ICE is created with a START TRANSID INTERVAL
REQID and before RETURN TRANSID. The ICE is cancelled with the command
CANCEL REQID (PF3 key)before the next START TRANSID INTERVAL REQID.
All the temporary storage created in the AORs are routed in the TOR
but we can see in MAINVIEW a TS named TERMID/TRANSID still stay in a
AOR as the ICE. (This is the name of the REQID.)
Problem
The transaction is OK when the execution is in the same AOR and if
after the RETURN TRANSID the transaction is in the other one AOR, the
TS is unknown for the application.
CANCEL REQID with option SYSID can resolve the problem but not
acceptable for us.
Question ?
Does anybody knows how this CANCEL REQID can be made without the SYSID
option ?
Is it possible to use the WLM of CPSM (TRANGRP) to resolve the problem
?
Best regards,
Rapha�l DENIS
Technical Details
Message-ID:
<1066b291.0302120217.59bf238d@posting.google.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!postnews1.google.com!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII X-Google-Thread: fa0ae,90439408ff00a40,start X-Google-Attributes: gidfa0ae,public X-Google-Thread: 10f713,90439408ff00a40,start X-Google-Attributes: gid10f713,public X-Google-ArrivalTime: 2003-02-12 02:17:17 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!postnews1.google.com!not-for-mail From: raphael.denis.prestataire@cegetel.fr (DENIS R) Newsgroups: comp.lang.perl.misc,bit.listserv.cics-l Subject: CPSM and CANCEL REQID Date: 12 Feb 2003 02:17:16 -0800 Organization: http://groups.google.com/ Lines: 29 Message-ID: <1066b291.0302120217.59bf238d@posting.google.com> NNTP-Posting-Host: 195.115.41.103 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1045045036 24798 127.0.0.1 (12 Feb 2003 10:17:16 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 12 Feb 2003 10:17:16 GMT