| Author |
Message
|
| pankajg |
 Posted: Fri Aug 23, 2002 3:33 pm Post subject: Rules used for importing cobol copybooks |
 |
|
Acolyte
Joined: 11 Oct 2001
Posts: 53
|
Hi All
Can you please help in listing ALL the rules to be followed ,while importing copybooks into MQSI - Msg set.
Like...
1. copybook file should be .txt / .cbl etc...
2. The first char in the line N should be at column X...
3. Each line should follow with a dot / period.
This will of great help...
Thanks
_________________
Regards
Pankaj |
|
| Back to top |
|
 |
| kirani |
| Posted: Fri Aug 23, 2002 3:49 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Pankaj,
There is no additional rule imposed by MQSI while importing a COBOL copybook. Make sure your copybook is a valid copybook and it adheres to COBOL coding standards.
_________________
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 |
|
|
| Tibor |
| Posted: Mon Aug 26, 2002 12:00 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| kirani wrote: |
| There is no additional rule imposed by MQSI while importing a COBOL copybook. Make sure your copybook is a valid copybook and it adheres to COBOL coding standards. |
Well... I was coding in COBOL on Tandem, and the compiler was ANSI85 compliant. However, MQSI sent error messages when we tried importing COBOL definitions. But when I made an export of existing msgset then I re-formatted own COBOL copybook, then worked  .
But manuals don't tell about exact definition of 'valid copybook'.
Tibor |
|
| Back to top |
|
|
| pankajg |
| Posted: Tue Aug 27, 2002 10:10 am Post subject: |
|
|
Acolyte
Joined: 11 Oct 2001
Posts: 53
|
Thanks Kirani , Tibor.
Are you aware of any online docs on the "desired Standard format of a copybook before being imported into MQSI.
Also , reference to any tool that can generate a MRM msg( byte stream ) as per a copybook is appreciated.
Thanks
_________________
Regards
Pankaj |
|
| Back to top |
|
|
| sgopal |
| Posted: Tue Aug 27, 2002 10:48 am Post subject: |
|
|
Acolyte
Joined: 30 Jul 2002
Posts: 63
|
While importing the COBOL Copybook into message set, a report is generated. You can check the report for successful import of all the COBOL Elements.
Regarding valid COBOL copybook, itz common rule like 01 level should start from column 8, and the COPYBOOK should contain valid pic. clause and all that..
I could not find any documentation which talks about 'valid copybook'. |
|
| Back to top |
|
|
| pankajg |
| Posted: Thu Aug 29, 2002 4:06 pm Post subject: |
|
|
Acolyte
Joined: 11 Oct 2001
Posts: 53
|
Thanks Gopal.
_________________
Regards
Pankaj |
|
| Back to top |
|
|
| kwelch |
| Posted: Fri Aug 30, 2002 6:34 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 255
|
Pankag,
I haven't done a copybook import for awhile, but some of the things I have had problems with in the past were 88 levels and redefines. We removed all of them from our copybooks before the import. Also, in COBOL it's common to use the word FILLER and there may be numerous FILLER's in a copybook. It seemed as though WMQI could handle a few but after awhile started erring on duplicate names. So we also just renamed all the FILLER to FILLER1, FILLER2, etc.
Karen |
|
| Back to top |
|
|
|
|
