| Author |
Message
|
| catwood2 |
 Posted: Wed Dec 06, 2006 11:19 am Post subject: WMQI2.1 -> WBIMB 6.0: mqsimigratemsgsets COBOL C Lang |
 |
|
Centurion
Joined: 17 May 2002
Posts: 108
|
TIA for any pointers.
Have a couple message sets using COBOL and C Lang. Only have the mrp's - no supporting files (as I understand it - copy books or headers). I understand from the manuals (and the posts here) I'll need to manually create them in toolkit or use wizard. I think my questions boil down to:
Can I extract the needed COBOL and C Lang info from the related mrp files?
If not, and I don't have the source cobol / c files, what is the best course of action? |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Dec 06, 2006 2:58 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
What is your requirement? ( why do you need the original C/COBOL files? ).
You can create a v6 message set from an MRP file. |
|
| Back to top |
|
|
| catwood2 |
| Posted: Thu Dec 07, 2006 4:11 am Post subject: |
|
|
Centurion
Joined: 17 May 2002
Posts: 108
|
When I review the migrate report I have errors specific to the cobol and C lang:
"COBOL Language Binding not supported"
and BIP0174W, BIP0173W, BIP0169
From the manual it indicates that the migration doesn't support Cobol and C Lang. The requirement is to successfully represent these message sets in 6.0. It appears that can not be done with migration command due to the errors. So, that's what I'm trying to sort.
thx |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Dec 07, 2006 6:53 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
BIP0173 and BIP0174 are warning messages, not errors. The import should have completed successfully. Have you checked to see whether it has created a new message set in your tooling?
This is what the docs say:
| Quote: |
# Any COBOL language binding layer is discarded with a BIP0174 warning message.
# Any C language binding layer is discarded with a BIP0173 warning message. |
|
|
| Back to top |
|
|
| catwood2 |
| Posted: Thu Dec 07, 2006 7:00 am Post subject: |
|
|
Centurion
Joined: 17 May 2002
Posts: 108
|
| I do see the message sets. I was assuming a loss of needed functionality with those items being discarded. I have "inherited" support of these long running flows and am not completely sure what it means to have those discarded. I assume they are necessary to provide the same level of functionality as the 2.1 message sets? |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Dec 07, 2006 7:22 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| I was assuming a loss of needed functionality with those items being discarded |
You assume incorrectly. v6 does not need these bindings. The C and COBOL language bindings were only used if you wanted to generate a C or COBOL file from your WMQI 2.1 message set. You can't generate C and COBOL files from v6 message sets, so the bindings are not required. |
|
| Back to top |
|
|
| catwood2 |
| Posted: Thu Dec 07, 2006 8:02 am Post subject: |
|
|
Centurion
Joined: 17 May 2002
Posts: 108
|
| OK - that clears that up. Thanks again for the assist! |
|
| Back to top |
|
|
|
|
