
| Parameter | Options | Description | Default Value |
| Platform |
|
The platform on which the COBOL program runs. Selecting a platform sets the other Platform Information attributes to default values that are appropriate for that platform. The platform default values still can be changed individually. For IMS™ select z/OS®. |
|
| Code Page Selection |
|
The Codepage of the COBOL program on the target platform. |
|
| Floating Point Format |
|
The floating point format (IBM or IEEE). When the byte representation of floating point numbers is as defined in IBM z/Architecture® Principles of Operation this is referred to as an IBM 390 Hexadecimal floating point format. When the byte representation of floating point numbers is as defined by IEEE standard 754, this is referred to as an IEEE Non-Extended floating point format. |
|
| Endian | Little | The little endian representation of integer data. When the byte representation of integers is ordered from the least significant byte to most significant byte, this is referred to as a little endian representation. |
|
| Big | The big endian representation of integer data. When the byte representation of integers is ordered from the most significant byte to the least significant byte, this is referred to as a big endian representation. | ||
| Remote integer endian | Little | This property complements working with user exits, such as DFHCNV macros. The supplied DFHCNV macros manipulate 2 byte and 4 byte integers, but not 8 byte integers. You can use the endian property to control the format of 8 byte integers, and use the remote integer endian property to control the format of 2 byte and 4 byte integers. If no user exit exists, or if the user exit does not manipulate the endian character integers, then you must specify the same value that is used for the endian property. |
|
| Big | This property complements working with user exits, such as DFHCNV macros. The supplied DFHCNV macros manipulate 2 byte and 4 byte integers, but not 8 byte integers. You can use the endian property to control the format of 8 byte integers, and use the remote integer endian property to control the format of 2 byte and 4 byte integers. If no user exit exists, or if the user exit does not manipulate the endian character integers, then you must specify the same value that is used for the endian property. | ||
| External decimal sign | ASCII | Controls data conversion for external decimal COBOL data types. If the COBOL program is running on a machine whose codepage is American Standard Coded Information Interchange format (ascii), select ASCII. |
|
| EBCDIC | Controls data conversion for external decimal COBOL data types. If the COBOL program is running on a machine whose codepage is Extended Binary Coded Decimal Interchange Format (EBCDIC), select EBCDIC. | ||
| EBCDIC Custom | Controls data conversion for external decimal
COBOL data types. This property allows DFHCNV macros to be used to
convert external decimal data types, and then corrects the codepoint
which contains the sign bit.
|
||
| Quote |
|
|
|
| TRUNC |
|
|
|
| NSYMBOL |
|
|
|

| Parameter | Options | Description | Default Value |
| Compile Time Locale Name | For a list of the valid Locale and the corresponding code pages supported, see Locales and code pages supported | COBOL for Windows uses the POSIX-defined locale conventions.
Locale value syntax: ll _CC.codepageID where
You must code a valid value for the locale name (ll CC) and a valid code page (codepageID) that corresponds to the locale name, as listed in Locales and code pages supported. You can use the characters that are represented in a supported code page in COBOL names, data definitions, literals, and comments. The locale in effect determines the code page for compiling source programs (including alphanumeric literal values). That is, the code page that is used for compilation is based on the locale setting at compile time. Thus, the evaluation of literal values in the source program is handled with the locale in effect at compile time. |
en_US |
| ASCII code pages | IBM-1252 For a given locale name, the last one in the set of ascii code pages is chosen as the default, since they more common (because they are newer). |
||
| Error messages languages |
|
This gives you the option to select the language that error messages appear in. | Default is the current locale in which eclipse is running. |
| Currency Sign | You can use the CURRENCY option to provide an alternate default currency symbol to be used for the COBOL source. The CURRENCY SIGN value must be a valid COBOL alphanumeric literal (including a hexadecimal literal) representing a single character. For example, '$' or "$" or X'9F" or x'9F'. | Default value is "$". | |
| SOSI |
|
Use the SOSI compiler option to specify if DBCS character strings in a literal are delimited by the shift-out and shift-in characters. | The default is dependent on the platform
that is selected in the General tab:
|
| COLLSEQ |
|
|
The default is dependent on the platform
that is selected in the General tab:
|
| NCOLLSEQ |
|
|
The default is dependent on the platform
that is selected in the General tab:
|
| File Extension Support | Using the File Extension Support table,
you can change the default extension behavior. You can assign an extension
to contain a full program or data structures only.
|
Support for Copybooks In Arbitrary Directories
To add the ability to import a COBOL source that has dependency on copybooks that are in arbitrary locations, you can add various directory locations using the COBOL preference page SYSLIB tab.

You can add, remove, or edit these entries. Clicking Edit opens the following window:
Move Up and Move Down allow you to change the order of these directories. The COBOL importer looks for copybooks in the directories in the specified order.