| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Fail to trigger CICS tran on OS/390 platform |
« View previous topic :: View next topic » |
| Author |
Message
|
| wilsonho3 |
 Posted: Thu Nov 21, 2002 6:26 am Post subject: Fail to trigger CICS tran on OS/390 platform |
 |
|
Voyager
Joined: 20 Nov 2001
Posts: 98
Location: Hong Kong
|
Hi all
I has a trigger problem need help
I has the following set up On os/390 platform
Message queue
-----------------
default persistence : y
deault priority : 0
Message delivery seq: P P=priority
permit share access : Y
default share option :E E-exclusive
indextype : N N=none
Max queue depth : 99999999
max message length :4194304
default bind : O O=open
Trigger type :F
trigger set :Y
trigger depth :1
process :procss.name
initiation queue : CICS01.INITQ
CICS01.INITQ
===========
default persistence :Y
default priority :0
message delivery seq  P=priority
permit share option :Y
default share option :exclusive
indextypr : N N=none
max queue depth :99999999
max message length :4194304
default bind  o=open
trigger type : N
trigger set :N
trigger message priority :0
trigger depth :1
process
=======
CICS type and the corret tran name (I sure it is correct)
Result
======
When I put message on message queue (I stop the CKTI first to sure
the message arrive the message queue and not to be triggered).
HAving I sure the message arrive the queue, I start the CKTI, the
message gone, but there is no triggering occur. I does not find
tran task on CKTI task penal. There is no message on dead letter
queue, no message no message queue, no triggering occurs. Does
any body explain to me why. How to debug the triggering on os/390
thank you
wilson |
|
| Back to top |
|
 |
| mgrabinski |
| Posted: Thu Nov 21, 2002 10:46 pm Post subject: |
|
|
Master
Joined: 16 Oct 2001
Posts: 246
Location: Katowice, Poland
|
Hi,
Are you sure you have the process 'procss.name'? (MQ is case sensitive!)
_________________
Marcin Grabinski <>< |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Nov 25, 2002 6:42 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
The message is expired on the queue waiting for you to start the trigger monitor? The queue will show the depth of 1 even if the message is expired until something does an MQGET on the queue to discard the expired message.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
