I have a copybook containing all (current) languages as defined by the standard ISO639-2 as conditional names.
All fine at well but to my surprise a program using this copybook does not compile using fujitsu COBOL85 version V30L10.
The compile step produces the following error message:
(fujitsu COBOL85 V30L10)
The copybook responsible for this error message is as follows:
(extract!)
When I change the line being marked to be in error, 'line 217' (see error message above), from:
into
than the compile step ends without errors!
To emphasize...there was, and is, no SET Japanese TO TRUE statement within the program being compiled.
The error truly is from the copybook and not the program that includes this copybook!
Question: Is the word "Japanese" a COBOL reserved word?
Note:
I know that there is a Japanese language extention.
And that there are compiler directives to handle/support japanese words within a COBOL source.
But I am not aware that the (English!) word "Japanese" itself is a COBOL reserved word.
I already looked in manuals and other documentation but I am unable to find that the word "Japanese" is a reserved COBOL word! Still...I might overlook a trivial detail! A trivial detail that will embarrass me and makes me feel foolish! Even than I like to know!
On a side note:
If anybody else is interested in the copybook (the ISO639 definition of about 480+ languages) then I am happy to sent him/her a copy!...it may save you some boring copy&paste repetitive coding work.
ATTENTION: I had to tweak some identifier names a little because some of the characters are not allowed within a COBOL identifier name (e.g.: space ü é ç ó ... etc).
Interested!?!...my email address can be found on the following web site:
(For my email address see the end of the paragraph: 'About the author')
Regards, Wim Ahlers.
All fine at well but to my surprise a program using this copybook does not compile using fujitsu COBOL85 version V30L10.
The compile step produces the following error message:
(fujitsu COBOL85 V30L10)
Code:
** DIAGNOSTIC MESSAGE ** (EXAMPLE2)
ISO639$2 217: JMN1123I-S INVALID WORD '88' IS FOUND. IGNORED UNTIL NEXT VALID PARAGRAPH,SECTION OR DIVISION.
STATISTICS: HIGHEST SEVERITY CODE=S, PROGRAM UNIT=1
The copybook responsible for this error message is as follows:
(extract!)
Code:
.. ... VALUE ...
88 Italian VALUE 'ita'.
88 Javanese VALUE 'jav'.
88 Lojban VALUE 'jbo'.
88 Japanese VALUE 'jpn'.
88 Judeo-Persian VALUE 'jpr'.
88 Judeo-Arabic VALUE 'jrb'.
88 Kara-Kalpak VALUE 'kaa'.
88 Kabyle VALUE 'kab'.
88 Kachin VALUE 'kac'.
88 Kalaallisut VALUE 'kal'.
88 Kamba VALUE 'kam'.
.. ... VALUE ...
When I change the line being marked to be in error, 'line 217' (see error message above), from:
Code:
88 Japanese VALUE 'jpn'.
Code:
88 Japanese[COLOR=red]X[/color] VALUE 'jpn'.
To emphasize...there was, and is, no SET Japanese TO TRUE statement within the program being compiled.
The error truly is from the copybook and not the program that includes this copybook!
Question: Is the word "Japanese" a COBOL reserved word?
Note:
I know that there is a Japanese language extention.
And that there are compiler directives to handle/support japanese words within a COBOL source.
But I am not aware that the (English!) word "Japanese" itself is a COBOL reserved word.
I already looked in manuals and other documentation but I am unable to find that the word "Japanese" is a reserved COBOL word! Still...I might overlook a trivial detail! A trivial detail that will embarrass me and makes me feel foolish! Even than I like to know!
On a side note:
If anybody else is interested in the copybook (the ISO639 definition of about 480+ languages) then I am happy to sent him/her a copy!...it may save you some boring copy&paste repetitive coding work.
ATTENTION: I had to tweak some identifier names a little because some of the characters are not allowed within a COBOL identifier name (e.g.: space ü é ç ó ... etc).
Interested!?!...my email address can be found on the following web site:
(For my email address see the end of the paragraph: 'About the author')
Regards, Wim Ahlers.