AW: Still having problems with the CICS bridge
Paulo, (quote on) Put application name - RequestQueue name appended with CKTI (quote off) your cics trigger monitor ckti is started using the applicaition requestqueue instead of the initqueue. your setup looks to be wrong. go into your cics system start ckqc transaction place cursor on connection and press enter use 4 - display whats the name of the initqueue? it should be 'initqueue', but i bet it is 'requestqueue', which is wrong... (mhh... how much shall bet... mhhh :-)) thats what it should be: qlocal(requestqueue) specifies -> initq(initqueue) <- used by ckti thats what it looks like qlocal(requestqueue) <- used by ckti regards stefan -Ursprüngliche Nachricht- Von: Moreira, Paulo [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 3. Juli 2003 13:24 An: [EMAIL PROTECTED] Betreff: Re: Still having problems with the CICS bridge Stefan, First of all thanks for your great help. My message is going to the RequestQueue. Basically, the message has the following contents: -Does not use the RFH2 header -Format - None (since it doesn't use the RFH2 header I cannot define the Format) -Correlation ID -MQCI_NEW_SESSION -Message Content - program name (8 bytes) + commarea (31 bytes)- I tried with the program name in ASCII and in EBCDIC, and I had the same error (can you please which one should I use). I'm using a JMS ByteMessage. The message in the DLQ has the following contents: Reason Code -266 Queue - RequestQueue Put application name - RequestQueue name appended with CKTI We tried to change the queue configuration, and we started to have a different reason code - 2210 (MQRC_FORMAT_ERROR). After having this error, for any message I send to the request queue, I'll have the following error: CSQC746E CKBR 047 Invalid CCSID, 500 expected, 1208 received CSQC760I CKBR 047 MsgId =C3E2D840D4F5F3F04040404040404040B9A9A175074AB640 Then we have to restart the CICS bridge in order to solve this problem. I think that this is related with a bug fixed in APAR PQ68284. I'm not sure why am I getting the reason code 2210. The only reason I can imagine is that the message doesn't have a defined format, but the bridge is trying to convert the message data(MQGMO_CONVERT). But the MQ Application Programming guide states that I can use the MQFMT_NOME if I don't include an MQCIH, so I think I'm not doing anything wrong. Many thanks Paulo -Original Message- From: Raabe, Stefan [mailto:[EMAIL PROTECTED] Sent: Thursday, July 03, 2003 12:13 PM To: [EMAIL PROTECTED] Subject: AW: Still having problems with the CICS bridge sorry, I typed paolo instead of paulo and - in addition - the mail had some other old typing within it related to this problem before i typed what i wanted to send. i try again, please ignore the old mail: Paulo, check the information in the dead letter queue. You told us about the reason 266, but you should check further information from the dlq header. You may use the MA10 Supportpac (there is a little dead letter queue handler within it), otherwise browse the queue and check the bytes with the MQDLH structure (should be found in the application programmers reference) 1. what the queue name the message was destigned for? 2. whats the message contents? 3. what is the putapplication name? with these information it should be possible to find out what happened. if the queue is the initiation queue and the message contents is the request message, then you are putting to the wrong queue. if the queue is not the initiation queue but the putting application is the ckti (cics trigger monitor) then ckti is listening to the wrong queue. if it is something else (maybe a ckti in a different cics system) then you have to figure it out by yourself. maybe use display qstatus to see who is listening to the queue you put your requests too. i put a message to a cics initqueue to show you a sample output from the dlq handler that comes with the ma10 supportpac: COMMAND ===>, DLQName ,===>,MYQM.DEAD.QUEUE , MsgLen ,===>,0197, CurDepth ,===>,0006, (,0006,) StrucId ,===>,DLH , Version,===>,+0001, Reason ,===>,+0266, , , DestQ ,===>,MYCICS00.INITQ , DestQmgr,===>,MYQM, Encoding,===>,+0785, CodedCharSetId ,===>,+0273, Format ,===>,MQSTR , PutApplType,===>,+0001, ,CICS PutApplName ,===>,MYCICS00CKTI, PutDate ,===>,20030703, PutTime,===>,09394960, Dead Message: - REQUEST MESSAGE FOR PAOLO hope this helps. let us know what you found out. regards stefan Instructions for managing your mailing list subscr
AW: Still having problems with the CICS bridge
sorry, I typed paolo instead of paulo and - in addition - the mail had some other old typing within it related to this problem before i typed what i wanted to send. i try again, please ignore the old mail: Paulo, check the information in the dead letter queue. You told us about the reason 266, but you should check further information from the dlq header. You may use the MA10 Supportpac (there is a little dead letter queue handler within it), otherwise browse the queue and check the bytes with the MQDLH structure (should be found in the application programmers reference) 1. what the queue name the message was destigned for? 2. whats the message contents? 3. what is the putapplication name? with these information it should be possible to find out what happened. if the queue is the initiation queue and the message contents is the request message, then you are putting to the wrong queue. if the queue is not the initiation queue but the putting application is the ckti (cics trigger monitor) then ckti is listening to the wrong queue. if it is something else (maybe a ckti in a different cics system) then you have to figure it out by yourself. maybe use display qstatus to see who is listening to the queue you put your requests too. i put a message to a cics initqueue to show you a sample output from the dlq handler that comes with the ma10 supportpac: COMMAND ===>, DLQName ,===>,MYQM.DEAD.QUEUE , MsgLen ,===>,0197, CurDepth ,===>,0006, (,0006,) StrucId ,===>,DLH , Version,===>,+0001, Reason ,===>,+0266, , , DestQ ,===>,MYCICS00.INITQ , DestQmgr,===>,MYQM, Encoding,===>,+0785, CodedCharSetId ,===>,+0273, Format ,===>,MQSTR , PutApplType,===>,+0001, ,CICS PutApplName ,===>,MYCICS00CKTI, PutDate ,===>,20030703, PutTime,===>,09394960, Dead Message: - REQUEST MESSAGE FOR PAOLO hope this helps. let us know what you found out. regards stefan 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
AW: Still having problems with the CICS bridge
Paolo,
check the information in the dead letter queue.
You told us about the reason 266, but you
should check further information from the dlq header.
You may use the MA10 Supportpac (there is a little
dead letter queue handler within it), otherwise
browse the queue and check the bytes with the
MQDLH structure (should be found in the application
programmers reference)
1. what the queue name the message was destigned for?
2. whats the message contents?
3. what is the putapplication name?
with these information it should be possible to find
out what happened.
if the queue is the initiation queue and the message
contents is the request message, then you are putting
to the wrong queue.
if the queue is not the initiation queue but the
putting application is the ckti (cics trigger monitor)
then ckti is listening to the wrong queue.
if it is something else (maybe a ckti in a different cics
system) then you have to figure it out by yourself.
maybe use display qstatus to see who is listening to
the queue you put your requests too.
i put a message to a cics initqueue to show you a sample
output from the dlq handler that comes with the ma10
supportpac:
COMMAND ===>,
DLQName ,===>,MYQM.DEAD.QUEUE ,
MsgLen ,===>,0197, CurDepth ,===>,0006, (,0006,)
StrucId ,===>,DLH , Version,===>,+0001,
Reason ,===>,+0266, , ,
DestQ ,===>,MYCICS00.INITQ ,
DestQmgr,===>,MYQM,
Encoding,===>,+0785, CodedCharSetId ,===>,+0273,
Format ,===>,MQSTR , PutApplType,===>,+0001, ,CICS
PutApplName ,===>,MYCICS00CKTI,
PutDate ,===>,20030703, PutTime,===>,09394960,
Dead Message: -
REQUEST MESSAGE FOR PAOLO
hope this helps.
let us know what you found out.
regards
stefan
2.
log on into the cics system
start transaktion ckqc
use connection, then 4- display
what is the name of the initq? it should be 'InitQueue', but
maybe it is 'RequestQueue')
3.
if it is 'InitQueue', then try the following:
put disable the 'InitQueue'
run your application
if you get a proper returncode (2051 put inhibited)
then the application is putting to the initq.
3
depending on the os/390 version
-Ursprüngliche Nachricht-
Von: Moreira, Paulo [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 3. Juli 2003 10:17
An: [EMAIL PROTECTED]
Betreff: 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
AW: Still having problems with the CICS bridge
Paolo, is the queue you are putting the request message to an init queue, read by a trigger monitor (most likely CKTI within cics)? regards stefan -Ursprüngliche Nachricht- Von: Moreira, Paulo [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 2. Juli 2003 14:47 An: [EMAIL PROTECTED] Betreff: 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
