| Author |
Message
|
| Founet |
 Posted: Tue Sep 21, 2004 12:46 pm Post subject: Persistent message & coupling on Z/os |
 |
|
Newbie
Joined: 21 Sep 2004
Posts: 6
Location: france
|
I begin new sysplex project z/os system.
I have a problem when messages are send by remote Queue to my local queue in the coupling facility . Msg go to the DLQ with code 2048 .
Qalias is not persitent
QLocal in not persistent and type shared
Application don't use the MQMD Pesistent option to put message on remote Queue
Define CFSTRUCT wih level=2 and persistent=no
In DLQ the putappl is CHIN (channel initiator name ) is't good
Is the message became persitent because the XmitQ is persitent ?
Sorry for my english .
Thank's for help |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Tue Sep 21, 2004 2:48 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7716
|
Look at the Persistence Attribute of the Remote Queue Definition the application is putting to. That is what is setting the message's persistence atribute if the app itself is not specifying it.
Once the message passes thru the remote queue def, it is already assigned the persistence attribute, and no queue farther downstream, not even the XMITQ, will change it.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Founet |
| Posted: Wed Sep 22, 2004 10:19 am Post subject: |
|
|
Newbie
Joined: 21 Sep 2004
Posts: 6
Location: france
|
Thank Peter ...
It's not possible for us to change QA and QRemote from PERSITENT to NOPERSISTENT on all QMGR who send message in the QL witch is in the coupling ... the only solution have found is to pass an alter CFSTRUCT(xxx) CFLEVEL(3) RECOVER(ON) .. before the CFSTRUCT was in CFLEVL(2) RECOVER(NO)....
I hope this solution don't generate too much overhead ! have you ideas on this subject ?
For instance i have only 5000 msg/day in Coupling and only on triggerer Queues ..and it's ok
Thank's |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Sep 22, 2004 3:38 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7716
|
I have never used Shared Queues, sorry. I was just suggesting a way not to have the messages be Persistent. Looks like someone with more z/OS expirience will have to jump in.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| frankdk |
| Posted: Thu Sep 23, 2004 12:22 pm Post subject: |
|
|
Novice
Joined: 10 Jun 2004
Posts: 20
Location: Copenhagen, Denmark
|
Hi
5000 msg/day is nothing to wory about. Just remember to do regular BACKUP CFSTRUCT(..) commands. When you do restart of your MQ systems it will scan logs of ALL qmgrs back to the last backup!! if the coupling facility is not 100% intact.
Backup every hour is a good start.
Another thing. You have only one trigger queue? If it triggers only one system to handle messages you will not need a shared queue.
_________________
Regards,
Frank |
|
| Back to top |
|
|
| Founet |
| Posted: Mon Sep 27, 2004 12:42 am Post subject: |
|
|
Newbie
Joined: 21 Sep 2004
Posts: 6
Location: france
|
Al the files in the coupling are locals queues and trigger first..
For instance it's only for test & pre production ..
We decide to put only locals queues with trigger .. not for Xmit and client queues. For instance we have 400Meg in coupling it's too short to keep an activity with remote Qmanager .
(400Meg accept 55.000 messages length 125).
Did you put Xmit queue in coupling ? |
|
| Back to top |
|
|
| frankdk |
| Posted: Wed Oct 06, 2004 10:12 am Post subject: |
|
|
Novice
Joined: 10 Jun 2004
Posts: 20
Location: Copenhagen, Denmark
|
| Founet wrote: |
| Did you put Xmit queue in coupling ? |
Yes we have tried that. Works fine, but channel may start from any qmgr in the group.
_________________
Regards,
Frank |
|
| Back to top |
|
|
|
|
