| Author |
Message
|
| WBI_user |
 Posted: Fri May 03, 2002 7:11 pm Post subject: |
 |
|
Partisan
Joined: 07 Aug 2001
Posts: 386
|
Is there any documentation on what's changed between 202 and 21. We have already encountered two problem with our flow after the migration.
1. we have a compare in the filter node comparing a char value 04 to interger 4. V202 compare this equal. V2.1 will not compare equal unless we explicitly cast the char to integer. I know we were not careful in 202 and 202 was just forgiveful. But this caused us unexpected outage.
2. We have a integer MRM field which set to 4 zeros.
set outputroot.mrm.integer.data = '0000'
v202 give us 0000 in the field.
V21 give us 0 and 3 blanks and this upset the receiving application.
We found out that the default is left justify and pad with blanks. We have to change it to right justify and pad with zero to get the output we need.
We just don't know what else is changed and what other problem we will encounter.
Can anyone point us to the right place where we can find a list of changes between 202 and 21 so that we can fix it to avoid unplanned impact.
[ This Message was edited by: Kelvin Yung on 2002-05-03 20:24 ] |
|
| Back to top |
|
 |
| CodeCraft |
| Posted: Fri May 17, 2002 11:26 am Post subject: |
|
|
Disciple
Joined: 05 Sep 2001
Posts: 195
|
In an ideal world, even with massive testing, the complexity of this product is such that some things may slip through the net. 2.1 *should* be backwardly compatible with 2.0x w.r.t. runtime behaviour. Because of these, you're unlikely to find documented behavioural differences other than those outlining new features and enhancements.
Any change in behaviour you find, you should bring to the attention of IBM Support and have either a fix, or explanation produced. In some cases people have exploited 2.0x bugs which no longer exist!!!
Casting (implicit/explicit) should work as before. If you find this is not the case, open a PMR and have it investigated.
On lists of known issues, you could raise a PMR with a TQ on what APARs have been raised/fixed since 2.1 CSD 02 has been released.
If you are not on CSD 02, you should be, as it's manditory and recommended. |
|
| Back to top |
|
|
| zpat |
| Posted: Sun May 19, 2002 11:27 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| People have reported that CSD02 "breaks" the Control Center. So should we apply it to the CM and Broker but not the CC? |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Thu May 23, 2002 7:38 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
Yes CSD2 breaks CC.When i was applied CSD2 on my workstation(CC only) it show empty WORKSPACE,no message sets,no message flows.If you click on messageflows then it show BIP0009E ERROR.I am OK after uninstalled CSD2.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| CodeCraft |
| Posted: Thu May 23, 2002 7:56 am Post subject: CSD 02 IS **MANDITORY** |
|
|
Disciple
Joined: 05 Sep 2001
Posts: 195
|
| Therefore, instead of backing it off you should resolve the issue by contacting IBM support. As a workaround try copying LogonInfo.* from the Config. Mgr. "bin" to the Control Centre client's "bin". |
|
| Back to top |
|
|
| kirani |
| Posted: Thu May 23, 2002 7:25 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
CodeCraft is correct. I faced the same problem and it was resolved after copying these files. This topic was discussed in following thread,
http://www.webmq.com/phpBB2/viewtopic.php?t=2745&highlight=logoninfo
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
|
|
