Author |
Message
|
jlamond |
Posted: Fri Nov 10, 2006 5:25 am Post subject: Queue Alias Support for Initq |
|
|
Voyager
Joined: 28 May 2002 Posts: 94 Location: Paris
|
I know this forum might not be the right place for this type of requirement but knowing that a certain number of IBMer are looking at it, I felt like 'my not'...
One issue that I have been facing many time is the propagation of queues definition between various stage of development up to production ( Dev, QA, pre prod, prod, etc), with the concern of integrity. In an ideal world, queues should be defined on the test environment and than definitions been deployed on others environment.
My problem as always be to deal with INITQ... For instance, I have been dealing with test (developper) environment where their is only 2 or 3 CICS regions and a target of 10 to 15 CICS regions. Been able to declare Alias INITQ would have make me life so easier. Having this I could define 15 or 20 different INITQ Alias on one system and have those same alias pointing to only 2 or 3 system somewhere else. Life would be so better and I could migration queues creation within standard migration process.
Thank you IBM if you can do something for it.
Best regards, and sorry it this was not the right place for posting this message.
Jean-Marc _________________ Jean-Marc |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Nov 10, 2006 3:19 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Jean -Marc, as tu jete un coup d'oeil au support packs MS03 (+ MO71 and MQ72)?
I believe the latest version will allow you to backup zOS ... if not look for the equivalent on zOS (it exists)...
If you add at the end of the script an alter changing the target q depending on the environment and then run the combined script in the new environment... you should be fine.
After that you can rerun the script from a backup in the new environment.
And please thank Wayne for creating that excellent support pack (MS03)  _________________ MQ & Broker admin |
|
Back to top |
|
 |
jlamond |
Posted: Sat Nov 11, 2006 3:24 am Post subject: |
|
|
Voyager
Joined: 28 May 2002 Posts: 94 Location: Paris
|
Oui je connais bien ces txppacs! and yes they are excellent.
But this does not solve the manipulation requirement ! It will be so great to be able to specify a queue alias within the init queue property of a local queue. This would allow to segragate infrastructure objects from application objetcs.
Regards,
Jean-Marc _________________ Jean-Marc |
|
Back to top |
|
 |
wschutz |
Posted: Sat Nov 11, 2006 3:53 am Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
There is an official channel for submitting requests for product enhancement. You should contact your IBM rep.
Although many IBM'ers participate here, mqseries.net is not the official channel for requesting changes. ..... _________________ -wayne |
|
Back to top |
|
 |
Nigelg |
Posted: Mon Nov 13, 2006 1:58 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004 Posts: 1046
|
There is nothing to stop you putting an alias queue name in the INTIQ attribute of a queue. The problem comes when using that queue in a trigger monitor; the queue is opened INPUT_EXCLUSIVE, so only a single trigger monitor can read from the queue at any one time. _________________ MQSeries.net helps those who help themselves.. |
|
Back to top |
|
 |
Mr Butcher |
Posted: Mon Nov 13, 2006 2:36 am Post subject: |
|
|
 Padawan
Joined: 23 May 2005 Posts: 1716
|
afaik the INITQ has to be a QLOCAL, otherwise MQ will not create a trigger message. _________________ Regards, Butcher |
|
Back to top |
|
 |
|