You want to trigger the CICS bridge, right? Shouldn't you use APPLICID(CKBR)? Also, 
from your original symptoms, you may have CKTI opening "RequestQueue"; it should be 
opening "InitQueue".

> -----Original Message-----
> From: Moreira, Paulo [SMTP:[EMAIL PROTECTED]
> Sent: Thursday, July 03, 2003 1:17 AM
> To:   [EMAIL PROTECTED]
> Subject:           Re: Still having problems with the CICS bridge
> 
> Hi,
> 
> The configuration I'm using is the following:
> 
> DEF QL('RequestQueue') +
> TRIGGER +
> TRIGTYPE(FIRST) +
> INITQ('InitQueue') +
> PROCESS('TestProcess')
> 
> DEF QL('InitQueue')
> 
> DEF PROCESS('TestProcess') +
> APPLTYPE(CICS) +
> APPLICID(ATG1)
> 
> 
> My JMS application is putting the messages on the RequestQueue. Is there
> anything wrong with this configuration?
> 
> Many thanks
> 
> Paulo
> 
> -----Original Message-----
> From: Miller, Dennis [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 02, 2003 9:05 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Still having problems with the CICS bridge
> 
> 
> You are getting your queues mixed up. Either you are sending your request
> message to the initq or the trigger monitor is reading the bridge queue.  On
> CICS there should be two distinct queues:
> 
>         Bridge Queue
>                 Send your CICS requests here
>                 Input to bridge monitor
>                 Triggering parameters specify the Initq
>                 Used exclusively by the CICS bridge
>         Init Queue
>                 Referenced in trigger parameters of the Bridge queue
>                 Input to trigger monitor (CKTI)
>                 Shared by many applications
> 
> 
> 
> 
> > -----Original Message-----
> > From: Moreira, Paulo [SMTP:[EMAIL PROTECTED]
> > Sent: Wednesday, July 02, 2003 5:47 AM
> > To:   [EMAIL PROTECTED]
> > Subject:           Still having problems with the CICS bridge
> >
> > Hi,
> >
> > We have a MQ-CICS bridge running. I'm sending a message to the request
> queue
> > with the following format:
> >
> > MessageID - MQMI_NONE
> > CorrelationID - MQCI_NEW_SESSION
> > I'm not using the RFH2 header
> > ReplytoQueue - Another queue that is used for replies
> > Message content- CICS Program name (8 characters) + commarea (I tried to
> > play around with format using ascii and ebcdic but I had always the same
> > problem)
> >
> > The request message is being read, and I'm always having a response in a
> > dead-letter queue, with the reason code 266 (MQFB_TM_ERROR - MQTM
> structure
> > not valid or missing).
> > Anyone has any idea about what is going wrong?
> >
> > Many thanks
> >
> > Paulo
> >
> >
> >
> > --
> > The contents of this e-mail are intended for the named addressee only. It
> > contains information that may be confidential. Unless you are the named
> > addressee or an authorized designee, you may not copy or use it, or
> disclose
> > it to anyone else. If you received it in error please notify us
> immediately
> > and then destroy it.
> >
> > 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
> 
> 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
> 
> 
> --
> The contents of this e-mail are intended for the named addressee only. It
> contains information that may be confidential. Unless you are the named
> addressee or an authorized designee, you may not copy or use it, or disclose
> it to anyone else. If you received it in error please notify us immediately
> and then destroy it.
> 
> 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

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