Posted: Mon Dec 05, 2005 3:48 am Post subject: COBOL language name problem
Newbie
Joined: 01 Dec 2005 Posts: 3 Location: India
I am a new user of WMQI 2.1 .
I got following problem.
Previous messages with COBOL language name greater than 32 bytes are existing in the system however when the same message is checked out & tried to check in it gives error that COBOL language name is invalid( needs 32 byte name).
Can anyone please tell me the significance of COBOL COPY BOOK & COBOL LANGUAGE NAME ? _________________ Hemant Shinde
Can anyone please tell me the significance of COBOL COPY BOOK & COBOL LANGUAGE NAME ?
The only significance of the COBOL COPY BOOK & COBOL LANGUAGE NAME is if you intend to generate (export) COBOL copybooks from your message set defintion. They have no effect on how the MRM parses and serializes messages.
So changing them will not effect the behaviour of the broker.
Typically they may be generated as a result of a COBOL import.
Q. Which service level of WMQI 2.1 are you on ?
Q. Do you have the COPYBOOK from which this message was imported and can you still import it withput error on the level of broker you are running.
Posted: Mon Dec 05, 2005 9:44 pm Post subject: Q. Which service level of WMQI 2.1 are you on ?
Newbie
Joined: 01 Dec 2005 Posts: 3 Location: India
Thank you Wooda.
Will you please tell me how to find service level ?
About COPYBOOKS :
they are not available.I am copying messages from one message set to new one & there it gives the above problem. I would like to know whether I can get any document specifying the COBOL LANGUAGE NAME limit & why the previous ( created by another person ) names has been accepted ? _________________ Hemant Shinde
On 2.1 if you are on windows you'll need to look in the registry to find the service level (like 2.1.0.7) the CSD level is this value -1 (eg. 2.1.0.7 is CSD 6)
If you are on unix then check the appropriate package install utility (eg pkginfo/lslpp/swlist etc.)
As indicated by the APAR text JT posted it is possible that COBOL binding names were imported or generated in an invalid form but will fail when checked out and in.
Of course that APAR fixes the generation of COBOL names but wont fix yours which are already generated.
If your names are invalid according to COBOL syntax you will have to change or regenerate them (with the fixed CSD level).
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