| Author |
Message
|
| hfvmg |
 Posted: Wed Mar 25, 2015 12:42 am Post subject: IBUS 9.0.0.3 and 9.0.0.2 compatibility |
 |
|
Newbie
Joined: 25 Mar 2015
Posts: 2
|
Is there any way of making IBUS 9.0.0.3 work like 9.0.0.2?
The problem is that the solution which works fine with 9.0.0.2 , doesn't work with 9.0.0.3. |
|
| Back to top |
|
 |
| zpat |
| Posted: Wed Mar 25, 2015 12:48 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Give MUCH more detail.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Mar 25, 2015 12:50 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
What sort of problem? Please explain?
It might be that your flow worked on 9.0.0.2 because of a 'loophole' which got fixed in 9.0.0.3.
Have you looked at the list of Fixed in 9.0.0.3 and checked to see if this is the case?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| hfvmg |
| Posted: Wed Mar 25, 2015 1:33 am Post subject: |
|
|
Newbie
Joined: 25 Mar 2015
Posts: 2
|
| Quote: |
| It might be that your flow worked on 9.0.0.2 because of a 'loophole' which got fixed in 9.0.0.3. |
you mean problem with shared variables?
Adding MQSI_ALLOW_PROPAGATE_WITH_SHARED_LOCK_HELD=1 helped with that problem.
I heard of a special compatibility mode from my colleagues, that can make 9.0.0.3 work like 9.0.0.2. Maybe it is a mistake and it doesn' exist at all...
The scheme of my process in general:
1. Buld solution with 9.0.0.2
2. Test it on machine with 9.0.0.3 , as if it was 9.0.0.2. So if there was a magic "compatibility mode" , i could use it. Otherwise i need to fix every problem (like the one with shared variables) and hope that new problems wont appear.
3. Deploy solution on machine with 9.0.0.2
Any thoughts? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Mar 25, 2015 1:58 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
mqsichangebroker -f
look it up and see if this is the magic potion you need?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Mar 25, 2015 2:49 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Start at the beginning. Instead of looking for a "magic" answer - tell us what problems you have found.
Apart from anything else - other people here will want to know what they are for their own upgrades. Please share your knowledge as we share ours.
mqsichangebroker -f is only of use to disable new fixpack function, it does not stop all changes to the product logic if these are bug fixes.
Not putting on the fixpack is one sure way to keep it working as before.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
|
|
