Author |
Message
|
shilpa.sabade |
Posted: Wed Mar 12, 2014 9:29 am Post subject: REHOST from IBM mainframe to AIX - Signed COMP-3 issue |
|
|
Voyager
Joined: 23 Feb 2011 Posts: 76
|
Need your Suggestion Please .
We are doing a conversion from IBM mainframe to AIX. applications are converted to AIX COBOL ..We are trying to
do a minimal approach due to cost (of course).
Here is the flow :
Windows system -XML(MQ7.5) ---> WMB(V8)XML-MRM) ----> z/os ( NEW AIX MQ V7.5)
1. In current world ( to Z/OS) - we are setting CCSID 500 and Encoding 785 . This works perfectly fine.
2. For AIX system .. i changed WMB flow with CCSID 819 and Encoding 785. AIX COBOL fails while processing Pac decimals.
I tried different combination of Encoding .. not positive result yet. Tried MQGET with Convert -- Fails again.
Tried MQ Channel CONVERT =YES ..doesnt work.
With Encoding 785 / 273 - when i check hex code .. data looks good. Trying to under stand why application does not like this data. |
|
Back to top |
|
 |
bruce2359 |
Posted: Wed Mar 12, 2014 9:34 am Post subject: Re: REHOST from IBM mainframe to AIX - Signed COMP-3 issue |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
shilpa.sabade wrote: |
2. For AIX system .. i changed WMB flow with CCSID 819 and Encoding 785. AIX COBOL fails while processing Pac decimals.
...
Trying to under stand why application does not like this data. |
How does the AIX COBOL fail? Exactly what error are you getting?
Did you read about COBOL differences for packed-decimal data here http://publib.boulder.ibm.com/infocenter/comphelp/v7v91/index.jsp?topic=%2Fcom.ibm.aix.cbl.doc%2Frpdif02.htm ? _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
shilpa.sabade |
Posted: Wed Mar 12, 2014 9:43 am Post subject: |
|
|
Voyager
Joined: 23 Feb 2011 Posts: 76
|
AIX - COBOL fails to identify - These packed decimals as numeric fields .
WRT - Links .. i read through the difference .. AIX COBOL and Host COBOL differ while representing unsigned fileds . In my case we have fields as signed.
Am bit confused on is my Encoding type incorrect on WMB flow?
need your advise.
thank you |
|
Back to top |
|
 |
bruce2359 |
Posted: Wed Mar 12, 2014 9:52 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
shilpa.sabade wrote: |
AIX - COBOL fails to identify |
Do you mean that you receive no run-time error indication? No run-time error message? Or are you saying that the compiler does not flag an error?
Does the application end normally, or abnormally? If abnormally, what abend code?
It would help if you posted the packed-data field in the message before the message is sent, and after it ends up in the destination queue. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
shilpa.sabade |
Posted: Wed Mar 12, 2014 10:25 am Post subject: |
|
|
Voyager
Joined: 23 Feb 2011 Posts: 76
|
bruce2359 wrote: |
shilpa.sabade wrote: |
AIX - COBOL fails to identify |
Do you mean that you receive no run-time error indication? No run-time error message? Or are you saying that the compiler does not flag an error?
Does the application end normally, or abnormally? If abnormally, what abend code? |
I Took the trace of CICS program - ABCODE 2110 . Abend occurs right after MQGET.
CICS ABCODE. Fields ...... (2110, X'83E') Message format not valid.
-------------------------------------------------------------------------------
03/12/2014 13:15:59 unikixtran20: Terminal Transaction QBJN Program QBP707CO Line 00003616
03/12/2014 13:15:59 unikixtran20: Exiting LINK Rcode 000000000000
03/12/2014 13:15:59 unikixtran20: 202f7b10 PROGRAM UTL060CO
03/12/2014 13:15:59 unikixtran20: 222a8f98 COMMAREA 47202020 5142502e 424f482e 41444a55 G QBP.BOH.ADJU
03/12/2014 13:15:59 unikixtran20: 222b2a72 LENGTH 000615
03/12/2014 13:15:59 unikixtran20: -------------------------------------------------------------------------------
03/12/2014 13:15:59 unikixtran20: Terminal Transaction QBJN Program QBP707CO Line 00003037
03/12/2014 13:15:59 unikixtran20: Entering ABEND
03/12/2014 13:15:59 unikixtran20: 222a651d ABCODE 2110
03/12/2014 13:15:59 unikixtran20: -------------------------------------------------------------------------------
Quote: |
It would help if you posted the packed-data field in the message before the message is sent, and after it ends up in the destination queue. |
I Caught the OUTPUT message On WMB Windows server .
Here is the data :
00000064 .L0000 0....._ 0F4C3030 30302020 2030037F 0000185F
00000080 ........ ..... .. 0F000400 0F000400 0F000400 0F200000
Here is the message from AIX queue ( Destiantion )
00000064 .L0000 0....._ 0F4C3030 30302020 2030037F 0000185F
00000080 ........ ..... .. 0F000400 0F000400 0F000400 0F200000
they are identical .
Here is the message caught on MF Queue:
00000064 .L0000 0."...^ 0FD3F0F0 F0F04040 40F0037F 0000185F
00000080 ........ ..... .. 0F000400 0F000400 0F000400 0F400000 |
|
Back to top |
|
 |
Vitor |
Posted: Wed Mar 12, 2014 10:52 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Have you looked up the 2110 reason code (not just the MQRC_FORMAT_ERROR part)?
What is the MQMD.Format value?
Is Convert set on the MQGet call? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
shilpa.sabade |
Posted: Wed Mar 12, 2014 11:05 am Post subject: |
|
|
Voyager
Joined: 23 Feb 2011 Posts: 76
|
Vitor wrote: |
Have you looked up the 2110 reason code (not just the MQRC_FORMAT_ERROR part)?
What is the MQMD.Format value?
Is Convert set on the MQGet call? |
Format : 'MQSTR '
Yes - its MQGET with CONVERT . |
|
Back to top |
|
 |
Vitor |
Posted: Wed Mar 12, 2014 11:30 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
shilpa.sabade wrote: |
Format : 'MQSTR ' |
So the message is described as a text string, but has packed decimals in a mixed format? Does that offer a clue to your problem? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
shilpa.sabade |
Posted: Wed Mar 12, 2014 12:09 pm Post subject: |
|
|
Voyager
Joined: 23 Feb 2011 Posts: 76
|
Vitor wrote: |
shilpa.sabade wrote: |
Format : 'MQSTR ' |
So the message is described as a text string, but has packed decimals in a mixed format? Does that offer a clue to your problem? |
I did some more digging on this -- In WMB flow mapping node - format is set to CWF1 ( our MRM message set).
But when i browse the message in Destination Queue : its MQSTR.
AM i missing something here ?  |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Mar 12, 2014 12:10 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Have you tried it with MQFMT_NONE ?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
shilpa.sabade |
Posted: Wed Mar 12, 2014 1:07 pm Post subject: |
|
|
Voyager
Joined: 23 Feb 2011 Posts: 76
|
fjb_saper wrote: |
Have you tried it with MQFMT_NONE ?  |
Tries this option now .. Got same ABCODE -2110.  |
|
Back to top |
|
 |
bruce2359 |
Posted: Wed Mar 12, 2014 1:45 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Any errors recorded in the system or qmgr error files? An FFST dump created? _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
shilpa.sabade |
Posted: Wed Mar 12, 2014 2:12 pm Post subject: |
|
|
Voyager
Joined: 23 Feb 2011 Posts: 76
|
bruce2359 wrote: |
Any errors recorded in the system or qmgr error files? An FFST dump created? |
no FDC files .
error files do not report any errors. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Mar 12, 2014 6:22 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Ok so you're getting a format error...
How are you creating your message. We will need to see some code...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
shilpa.sabade |
Posted: Thu Mar 13, 2014 7:07 am Post subject: |
|
|
Voyager
Joined: 23 Feb 2011 Posts: 76
|
fjb_saper wrote: |
Ok so you're getting a format error...
How are you creating your message. We will need to see some code...  |
fjb_saper , thank you so much for your and time and guidance ..
Flow doesnot have any esql code . Its a mapping node ..which is doing conversion.
and Here are my observations ..
1. in Z/OS setup --
Front end WIndows application sets Format as MQSTR ,
In mapping node (WMB ) .. There is assign statement to MQMD format = CWF1.
MQMQ on Destination queue :
MQMD
SourceQueue:CHARACTER:WMS.PART.OUT
Transactional:BOOLEAN:true
Encoding:INTEGER:785
CodedCharSetId:INTEGER:500
Format:CHARACTER: MQSTR
Version:INTEGER:2
Report:INTEGER:0
MsgType:INTEGER:8
Application on Z/OS is able to consume these messages all fine.
2. For AIX setup ,
In Mapping node i changed CCSID to = 819 ..
Destination queue MQMD-
MQMD
SourceQueue:CHARACTER:WMS.PART.OUT
Transactional:BOOLEAN:true
Encoding:INTEGER:785
CodedCharSetId:INTEGER:819
Format:CHARACTER: MQSTR
Version:INTEGER:2
Report:INTEGER:0
MsgType:INTEGER:8
AIX-COBOL application fails here with ABCODE=2110.
3. As suggested by Vitor and you ..
I changed ASSIGN VALUE in mapping node for Format = MQFMT_NONE
When i see MQMD on destination ..
All properties , which are set in MQMD in mapping node , are not effective :
Encoding : 546 CCSID : 500
Format : ' '
Encoding - is changed to that of incoming message !
4. I tweaked front end application - and changed input Format to NONE :
but AIX application still fails with ABCODE=2110.
MQMD:
Encoding : 785 CCSID : 500
Format : ' ' |
|
Back to top |
|
 |
|