| Author |
Message
|
| venkat kurra |
 Posted: Sat Nov 06, 2004 4:29 am Post subject: Migration of a flow/set to WBIMB CSD4 |
 |
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
We migrated a flow and set from 2.1 to WBIMB 5.0/csd4. In the 2.1 level it show the out put with spaces (2004112 Hartford) but in 5.0 the space filled with "."(2004112.....Hartford). I am not a developper and i do not have much inforatmion at this time. We need a space between date and name(same as 2.1),how can we remove dots(".").
Do we need any code changes after migration?Let me know if any one experienced the same problem.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Sat Nov 06, 2004 6:13 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What tool is showing you these periods?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Nov 06, 2004 7:16 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Jeff, I work with Venkat.
QPASA, MO71, amqsbcg, they all show the blanks spaces (in hex, 20) in output messages at 2.1. But at 5.0.4, they show dots (in hex, 1A).
Poking around I found a queue that had messages from 5.0.3 and 5.0.4. Same deal. At 5.0.3 the padding is spaces / hex 20, but at 5.0.4, the padding is dots / hex 1A. (Venkat, that is AACORERR_OUT on HIGMQIDA).
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Nov 07, 2004 7:36 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay, so the hex values are different... That's important to know.
What CCSIDs are you using? Are you translating between them inside the flow?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sun Nov 07, 2004 12:33 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
The MQMDs of the messages are identical. 437 is the CCSID. 546 is the Encoding.
The coding in the flows did not change. The only thing that changed was CSD04 was put on. And then the dots came...
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| kirani |
| Posted: Sun Nov 07, 2004 9:55 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
What is the padding set to for this field?
Is the broker also at csd 4?
_________________
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 |
|
|
| shanson |
| Posted: Mon Nov 08, 2004 2:06 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
| Assuming the MRM is being used here, please post the details of the message set. What physical format? What is the logical type of the field? If CWF what is the physical type of the field? What is the padding character of the field? If CWF what is the message set level property 'byte alignment pad' set to? |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Mon Nov 08, 2004 11:01 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
Actual migration was completed with CSD3.After few weeks later we upgraded to CSD4 and experienced this problem. The output queue has all messages of CSD3 & CSD4 level and the problem happened after CSD4 upgrade.
Finally it works after we delete and remigration of these flows/sets from 2.1 to 5.0/CSD4 directly.
Thank you all
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| kirani |
| Posted: Tue Nov 09, 2004 12:09 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Venkat,
It's good to know that your problem is resolved. But it would help others if you could answer to shanson's questions.
_________________
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 |
|
|
| shanson |
| Posted: Tue Nov 09, 2004 2:45 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
I need to know precisely what you did here. This is what I think you did, please correct anything that is wrong - in particular any additional deployments of the message set:
- Developed message set on v2.1
- Deployed message set to v2.1 broker
- Messages contain x'20'
- Installed toolkit at v5.0.3
- Installed broker at v5.0.3
- Migrated message set from v2.1 to v5.0.3 toolkit
- Deployed message set to v5.0.3 broker
- Messages still contain x'20'
- Upgraded toolkit to v5.0.4
- Upgraded broker to v5.0.4
- Messages now contain x'1A'
- Re-migrated message set from v2.1 to v5.0.4 toolkit
- Deployed message set to v5.0.4 broker
- Messages contain x'20' again |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Tue Nov 09, 2004 6:54 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
Sure i am very happy to assist you to find out the issue or resolution.
- Developed message set on v2.1 - YES
- Deployed message set to v2.1 broker -YES
- Messages contain x'20' - YES(We need blank space)
- Installed toolkit at v5.0.3 -YES
- Installed broker at v5.0.3 -YES
- Migrated message set from v2.1 to v5.0.3 toolkit -YES
- Deployed message set to v5.0.3 broker -YES
- Messages still contain x'20' -YES(We saw the old messages)
- Upgraded toolkit to v5.0.4 -Broker first then the tollkit
- Upgraded broker to v5.0.4 -Before the toolkit
- Messages now contain x'1A' -YES(we found dots instead of blank space)
- Re-migrated message set from v2.1 to v5.0.4 toolkit -YES
- Deployed message set to v5.0.4 broker -YES
- Messages contain x'20' again -YES(this exactly we are looking for)
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| shanson |
| Posted: Tue Nov 09, 2004 7:05 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
Thanks Venkat - please can you now answer the questions I posted earlier, so we understand your message and the field(s) involved.
| Quote: |
| What physical format? What is the logical type of the field? If CWF what is the physical type of the field? What is the padding character of the field? If CWF what is the message set level property 'byte alignment pad' set to? |
|
|
| Back to top |
|
|
| venkat kurra |
| Posted: Tue Nov 09, 2004 8:27 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
Shanson,
I need to work with developper to get all this inforamtion. I let you know as soon as i get those details.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Tue Nov 09, 2004 9:03 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
Here it is...
physical format = CWF
physical type = fixed character string / padding char = spaces
byte alignment = 1byte
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| shanson |
| Posted: Tue Nov 09, 2004 9:36 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
| Venkat, can I ask you to raise a PMR so that IBM service can look into this? |
|
| Back to top |
|
|
|
|
