ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Bug in importing signed elements with virtual decimal point

Post new topic  Reply to topic
 Bug in importing signed elements with virtual decimal point « View previous topic :: View next topic » 
Author Message
kirani
PostPosted: Thu Jun 06, 2002 3:57 pm    Post subject: Bug in importing signed elements with virtual decimal point Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

I came across a bug while importing COBOL Copybook that have signed decimal elements. To find out exact problem, I created following copybook and imported into MRM.
Code:

        01 TEST-FLOAT.
            03 ELE1 PIC S9(2).
            03 ELE2 PIC S9(2)V99.
            03 ELE3 PIC S9(3).
            03 ELE4 PIC S9(2)V9.
            03 ELE5 PIC S9(4).
            03 ELE6 PIC S9(5)V99.
            03 ELE7 PIC S9(6)V99.
            03 ELE8 PIC S9(7)V99.
            03 ELE9 PIC S9(8)V99.
            03 ELE10 PIC S9(9)V99.
   


WMQI created following elements into MRM and their properties were set to following,
Code:


Element Name - Logical Type, Physical Type, Length Count, Virtual Decimal Point, Signed


ELE1  - INTEGER, Extended Decimal, 2, n/a, Yes
ELE2  - DECIMAL, Extended Decimal, 4, 2, No
ELE3  - INTEGER, Extended Decimal, 3, n/a, Yes
ELE4  - DECIMAL, Extended Decimal, 2, 1, No
ELE5  - INTEGER, Extended Decimal, 4, n/a, Yes
ELE6  - DECIMAL, Extended Decimal, 7, 2, No
ELE7  - DECIMAL, Extended Decimal, 8, 2, No
ELE8  - DECIMAL, Extended Decimal, 9, 2, No
ELE9  - DECIMAL, Extended Decimal, 10, 2, No
ELE10 - DECIMAL, Extended Decimal, 11, 2, No


After looking at this data, I think, WMQI is not able to set Signed property in CWF tab for numbers with virtual decimal point.

Did anyone came across similar problem? I am not sure whether this is working in MQSI 2.0.x or not.
I am using WMQI 2.1 CSD2.
_________________
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
View user's profile Send private message Visit poster's website
dkesel
PostPosted: Fri Nov 08, 2002 2:56 pm    Post subject: Reply with quote

Newbie

Joined: 08 Nov 2002
Posts: 4

Hi Kiran,

I am seeing similar problems on WMQI 2.1. My question is whether or not this is fixed with CSD3? If not, what is the work around? Are there issues with COBOL signed packed decimals, as well?

Thank you!
Donna
Back to top
View user's profile Send private message
kirani
PostPosted: Fri Nov 08, 2002 10:38 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Hi Donna,

I have not yet installed CSD3 on our servers, so I am not sure whether this bug is fixed or not. But I remember reading something similar to this bug in CSD3 readme.txt file. Currently, I am manually checking the field lengths for decimal fields after the import.
_________________
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
View user's profile Send private message Visit poster's website
kwelch
PostPosted: Wed Nov 13, 2002 6:32 am    Post subject: Reply with quote

Master

Joined: 16 May 2001
Posts: 255

Kiran,

Yes we had a similar problem with signed fields. We also had a problem with the padding character for pic x fields being set to NUL instead of space and I think someone told me that there was a fix for that but it was after CSD 2.

Karen
Back to top
View user's profile Send private message Send e-mail
kirani
PostPosted: Fri Nov 22, 2002 2:22 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Finally we installed CSD3 on our server! I tried importing the same copybook into WMQI, this time all properties were set correctly! Looks like they fixed this in CSD3! I'm hoping that they have also fixed the problem of byte allocation (Total Length) for COMP3 fields.

With CSD2 I never had problems with Padding char for PIC X fields. I think If you create an element by hand (without importing the copybook) WMQI will set padding to NUL.
_________________
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
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Bug in importing signed elements with virtual decimal point
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.