fyi,

I just encountered a strange problem where a channel failure did not result
in a channel event being generated.  I didn't realize we had a problem
until an application generated an email informing me of a connection
problem.  IBM says this is a known problem.

----- Forwarded by Richard Tsujimoto/Consultant-NewYork/CanonUSA on
04/26/2004 03:07 PM -----
                                                                       
                      mqseries                                         
                      <[EMAIL PROTECTED]         To:      [EMAIL PROTECTED]
                      .com>                    cc:                   
                      Sent by: Erica D         Subject: pmr# 72499,7td attn; Erica
                      Hatchell                                         
                      <[EMAIL PROTECTED]                               
                      .com>                                          
                                                                       
                                                                       
                      04/26/2004 02:53                                 
                      PM                                               
                      Please respond                                   
                      to mqseries                                      
                                                                       
                                                                       




Hi Richard,

This looks to be a known issue.
.
1474.PRB
When are Channel Stopped Events (MQRC_CHANNEL_STOPPED (2283, X'8EB')
generated?
.
The behaviour has changed since the introduction of IC29815
so that "Channel Stopped" events are only generated when the
channel program itself generates a stopped event. Customers
will therefore find that if a channel goes straight into a
 retry mode after it is started, they will not get a
 MQRC_CHANNEL_STOPPED event with MQRQ_CHANNEL_STOPPED_RETRY.
The confusing issue is that an MQRC_CHANNEL_STARTED event
is written to the SYSTEM.ADMIN.CHANNEL.EVENT queue when the
channel is started via runmqsc or the MQSeries Explorer, even
if the channel isn't actually able to initialize a conversation
with the remote end.

The difference between the event generated by runmqsc/explorer
 and the channel process is that you can see the name of the
process in the PutApplName:

PutApplName : 'ebSphere MQ\bin\runmqchl.EXE'

OR

PutApplName : 'ebSphere MQ\bin\AMQPCSEA.EXE'

Additionally the MQCFH will contain a blank conname if the channel
process hasn't generated the event e.g:


00000000:  0700 0000 2400 0000 0100 0000 2E00 0000 '....$...........'
00000010:  0100 0000 0100 0000 0000 0000 EA08 0000 '............Û...'
00000020:  0200 0000 0400 0000 1800 0000 DF07 0000 '............?...'
00000030:  0000 0000 0400 0000 464F 4E5A 0400 0000 '........FONZ....'
00000040:  2400 0000 AD0D 0000 0000 0000 0D00 0000 '$...¡...........'
00000050:  464F 4E5A 2E54 4F2E 5249 4348 3300 0000 'FONZ.TO.RICH3...'

As opposed the the following MQCFH when the channel process has been
started:

00000000:  0700 0000 2400 0000 0100 0000 2E00 0000 '....$...........'
00000010:  0100 0000 0100 0000 0000 0000 EB08 0000 '............Ù...'
00000020:  0B00 0000 0400 0000 1800 0000 DF07 0000 '............?...'
00000030:  0000 0000 0400 0000 464F 4E5A 0400 0000 '........FONZ....'
00000040:  2400 0000 AD0D 0000 0000 0000 0D00 0000 '$...¡...........'
00000050:  464F 4E5A 2E54 4F2E 5249 4348 3300 0000 'FONZ.TO.RICH3...'
00000060:  0400 0000 2000 0000 B10D 0000 0000 0000 '.... ...?.......'
00000070:  0B00 0000 5249 4348 2E58 4D49 5451 3300 '....RICH.XMITQ3.'
00000080:  0400 0000 2400 0000 B20D 0000 0000 0000 '....$...?.......'
00000090:  1000 0000 392E 3230 2E39 332E 3636 2831 '....9.20.93.66(1'
000000A0:  3431 3529 0300 0000 1000 0000 FC03 0000 '415)........³...'
000000B0:  0700 0000 0300 0000 1000 0000 F503 0000 '............§...'
000000C0:  4595 0000 0300 0000 1000 0000 2E04 0000 'Eò..............'
000000D0:  0000 0000 0300 0000 1000 0000 2F04 0000 '............/...'
000000E0:  0000 0000 0400 0000 2400 0000 D20B 0000 '........$...Ê...'
000000F0:  0000 0000 0D00 0000 464F 4E5A 2E54 4F2E '........FONZ.TO.'
00000100:  5249 4348 3300 0000 0400 0000 1400 0000 'RICH3...........'
00000110:  D30B 0000 0000 0000 0000 0000 0400 0000 'Ë...............'
00000120:  1400 0000 D40B 0000 0000 0000 0000 0000 '....È...........'

Future releases of MQSeries will provide a Channel stanza
tuning parameter StopEvent = Always, which will revert to the
old behaviour of always generating a STOP event.

Regards Erica,
MQSeries Level 2 Support - Distributed Platforms
Email:   [EMAIL PROTECTED]
Need online help?  Go to http://www.ibm.com/support/
Need publications? Go to http://www.ibm.com/shop/publications/order

When sending mail to MQSERIES, please add the Level 2 rep's name and the
Problem Number in the Subject line.
** In addition please call  the support center and update your problem
record. (or electronically update your problem record)  **
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Reply via email to