This option is available both in the Create New Service Interface (bottom-up) wizard (see Setting preferences for COBOL XML converters) and in the command-line batch processor (see the property GEN_COMMENT_IN_XSD in CodegenProperty).
| Type of file: | Purpose: | |
|---|---|---|
| Input file: | A COBOL source code file or copybook file | This file contains the request language structure and the response language structure that you specify for the Web service. |
| Output WSDL and XSD files: | A WSDL file | This file describes the Web service. |
| Two XSD files | These two files describe a message format that is derived from the the request language data structure and the response language data structure. | |
When the option described in this topic is enabled, the runtime code generator extracts the comments from the COBOL source code file and adds the comments to the WSDL file and to the two XSD files described in the previous table.
| Item: | Description: |
|---|---|
| Which comment lines are extracted: |
|
| Where the comment lines are placed in the XSD and WSDL files: | The extracted comment lines within each level 01 COBOL data item in the COBOL source code file are added to the documentation element of the annotation element belonging to the top-level data type derived from that level 01 COBOL data item. |
| Entity references: | Characters that are used in XML as pre-defined entity references are replaced by their expanded forms. For example, an ampersand symbol (&) is replaced by a string that represents the ampersand entity expansion. |
| Multibyte characters: | Multibyte characters in the text of a COBOL comment must follow the rules given in the Enterprise COBOL documentation for multibyte characters. |
| Globalization concerns: | The content of the COBOL comment lines is expected to follow the rules of the Enterprise COBOL version 3.4 and later. No attempts to manipulate, transform or translate the content (beyond what is described in this section) is done by the EST generation process. |
| Invalid XML code points: | If invalid XML 1.0 codepoints appear in the COBOL comments and the copybook is given to the Rational® Developer for System z® tools for processing, then the behavior of the tool is unpredictable (The null character (0x00) is an example of invalid XML content). |