Version 4.2.6 for Mainframes (Update)	SEARCH   INDEX   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT

This system command is used to set various compilation options. The options are evaluated when a Natural programming object is compiled.

If you enter the COMPOPT command without any options, a screen is displayed where you can enable or disable the options described below.

The default settings of the individual options are set with the corresponding keyword subparameters of the parameter macro NTCMPO in the Natural parameter module or in the profile parameter CMPO. When you change the library, the COMPOPT options are reset to their default values.

This document covers the following topics:

• Syntax Explanation

• Specifying Compiler Keyword Parameters

• General Compilation Options

• Compilation Options for Ensuring Version Compatibility

Syntax Explanation

Specifying Compiler Keyword Parameters

You can specify compiler keyword parameters on different levels:

1. The default settings of the individual keyword parameters are specified in the macro NTCMPO in the Natural parameter module NATPARM.

2. At session start, you can override the compiler keyword parameters with the profile parameter CMPO.

3. During an active Natural session, there are two ways to change the compiler keyword parameters with the COMPOPT system command: either directly using command assignment (COMPOPT option=value) or by issuing the COMPOPT command without keyword parameters which displays the Compilation Options screen. The settings assigned to a compiler option are in effect until you issue the next LOGON command to another library. At LOGON, the default settings set with the macro NTCMPO and/or the profile parameter CMPO (see above) will be resumed. Example:

   OPTIONS KCHECK=ON
   DEFINE DATA LOCAL
   1 #A (A25) INIT <'Hello World'>
   END-DEFINE
   WRITE #A
   END
   

4. In a Natural programming object (for example: program, subprogram), you can set compiler parameters (options) with the OPTIONS statement. Example:

   OPTIONS KCHECK=ON
   WRITE 'Hello World'
   END
   

   The compiler options defined in an OPTIONS statement will only affect the compilation of this programming object, but do not update settings set with the command COMPOPT.

General Compilation Options

The following options are available:

• KCHECK - Keyword Checking

• PCHECK - Parameter Checking for Object Calling Statements

• DBSHORT - Interpretation of Database Short Field Names

• PSIGNF - Internal Representation of Positive Sign of Packed Numbers

• TSENABL - Applicability of TS Profile Parameter

• GFID - Generation of Global Format IDs

• LOWSRCE - Allow Lower-Case Source

• TQMARK - Translate Quotation Mark

• THSEP - Dynamic Thousands Separator

• CPAGE - Code Page Support for Alphanumeric Constants

• DB2ARRY - Support DB2 Arrays in SQL SELECT and INSERT Statements

• CHKRULE - Validate INCDIR Statements in Maps

These options correspond to the keyword subparameters of the CMPO profile parameter and/or the NTCMPO parameter macro.

KCHECK - Keyword Checking

The section Performing a Keyword Check (in the Programming Guide) contains a list of the keywords that are checked by the KCHECK option.

The section Alphabetical List of Natural Reserved Keywords (in the Programming Guide) contains an overview of all Natural keywords and reserved words.

PCHECK - Parameter Checking for Object Calling Statements

DBSHORT - Interpretation of Database Short Field Names

A database field defined in a DDM is described by two names:

• the short name with a length of 2 characters, used by Natural to communicate with the database (especially with Adabas);

• the long name with a length of 3-32 characters (1-32 characters, if the underlying database type accessed is DB2/SQL), which is supposed to be used to reference the field in the Natural programming code.

Under special conditions, you may reference a database field in a Natural program with its short name instead of the long name. This applies if running in Reporting Mode without Natural Security and if the database access statement contains a reference to a DDM instead of a view.

The decision if a field name is regarded as a short-name reference depends on the name length. When the field identifier consists of two characters, a short-name reference is assumed; a field name with another length is considered as a long-name reference. This standard interpretation rule for database fields can additionally be influenced and controlled by setting the compiler option DBSHORT to ON or OFF:

Examples:

Assume the following data base field definition in the DDM EMPLOYEES:

Example 1:

OPTIONS DBSHORT=ON
READ EMPLOYEES 
  DISPLAY AA      /* data base short name AA is allowed
END

Example 2:

OPTIONS DBSHORT=OFF
READ EMPLOYEES 
  DISPLAY AA      /* syntax error NAT0981, because DBSHORT=OFF
END

Example 3:

OPTIONS DBSHORT=ON
DEFINE DATA LOCAL
1 V1 VIEW OF EMPLOYEES
  2  PERSONNEL-ID
END-DEFINE
READ V1 BY PERSONNEL-ID 
  DISPLAY AA     /* syntax error NAT0981, because PERSONNEL-ID is defined in view;
                 /* (even if DBSHORT=ON)
END-READ
END

PSIGNF - Internal Representation of Positive Sign of Packed Numbers

TSENABL - Applicability of TS Profile Parameter

This option determines whether the profile parameter TS (translate output for locations with non-standard lower-case usage) is to apply only to Natural system libraries (that is, libraries whose names begin with "SYS", except SYSTEM) or to all user libraries as well.

Natural objects cataloged with TSENABL=ON determine the TS parameter even if they are located in a non-system library.

GFID - Generation of Global Format IDs

This option allows you to control Natural's internal generation of global format IDs so as to influence Adabas's performance concerning the re-usability of format buffer translations.

For details on global format IDs, see the Adabas documentation.

Rules for Generating GLOBAL FORMAT-IDs in Natural

• For Natural nucleus internal system-file calls:

  GFID=abccddee

  where	equals
  a	x'F9'
  b	x'22' or x'21' depending on DB statement
  cc	physical database number (2 bytes)
  dd	physical file number (2 bytes)
  ee	number created by runtime (2 bytes)

• For user programs or Natural utilities:

  • GFID=abbbbbbc for file number less than or equal to 255 and Adabas Version lower than 6.2 (see NTDB macro).

    where	equals
    a	x'F8' or x'F7' or x'F6'
    bbbbbb	bytes 1-6 of STOD value
    c	physical file number

  • GFID=axbbbbbc for file number greater than 255 and Adabas Version lower than 6.2.

    where	equals
    a	x'F8' or x'F7' or x'F6'
    x	physical file number - high order byte
    bbbbb	Bytes 2-6 of STOD value
    c	physical file number - low order byte

  • GFID=abbbbbb for Adabas Version 6.2 or higher.

    where	equals
    a	x'F8' or x'F7' or x'F6' where: F6=UPDATE SAME F7=HISTOGRAM F8=all others
    bbbbbbb	bytes 1-7 of STOD value

  Note:
  STOD is the return value of the store clock machine instruction (STCK).

LOWSRCE - Allow Lower-Case Source

This option supports the use of lower or mixed-case program sources on mainframe platforms. It facilitates the transfer of programs written in mixed/lower-case characters from other platforms to a mainframe environment.

When you use lower-case characters with LOWSRCE=ON, consider the following:

• The syntax rules for variable names allow lower-case characters in subsequent positions. Therefore, you can define two variables, one written with lower-case characters and the other with upper-case characters.

  Example:

  DEFINE DATA LOCAL
  1 #Vari  (A20)
  1 #VARI  (A20)
  

  With LOWSRCE=OFF, these variables are treated as different variables.

  With LOWSRCE=ON, the compiler is not case sensitive and does not make a distinction between lower/upper-case characters. This will lead to a syntax error because a duplicate definition of a variable is not allowed.

• Using  the session parameter EM (Edit Mask) in an I/O statement or in a MOVE EDITED statement, there are characters which influence the layout of the data setting assigned to a variable (EM control characters), and characters which insert text fragments into the data setting.

  Example:

  #VARI :='1234567890'
    WRITE #VARI (EM=XXXXXxxXXXXX)
  

  With LOWSRCE=OFF, the output is "12345xx67890", because for alpha-format variables only upper-case X, H and circumflex accent (ˆ) sign can be used.

  With LOWSRCE=ON, the output is "1234567890", because an x character is treated like an upper-case X and, therefore, interpreted as an EM control character for that field format. To avoid this problem, enclose constant text fragments in apostrophes (').

  Example:

  WRITE #VARI(EM=XXXXX'xx'XXXXX)

  The text fragment is not considered an EM control character, regardless of the LOWSRCE settings.

• Since all variable names are converted to upper-case characters with LOWSRCE=ON, the display of variable names in I/O statements (INPUT, WRITE or DISPLAY) differs.

  Example:

  MOVE 'ABC' to #Vari
    DISPLAY #Vari
  

  With LOWSRCE=OFF, the output is:

         #Vari
    --------------------
    
    ABC
  

  With LOWSRCE=ON, the output is:

         #VARI
    --------------------
    
    ABC
  

TQMARK - Translate Quotation Mark

Example:

RESET A(A5)                    
A:= 'AB"CD'                    
WRITE '12"34' / A / A (EM=H(5))
END                            

With TQMARK ON, the output is:

12'34     
AB'CD     
C1C27DC3C4

With TQMARK OFF, the output is:

12"34     
AB"CD     
C1C27FC3C4

THSEP - Dynamic Thousands Separator

This option can be used to enable or disable the use of thousands separators at compilation time. See also the profile and session parameter THSEPCH and the section Customizing Separator Character Displays (in the Programming Guide).

CPAGE - Code Page Support for Alphanumeric Constants

The CPAGE option can be used to activate a conversion routine which translates all alphanumeric constants (from the code page that was active at compilation time into the code page that is active at runtime) when the object is started at runtime.

See also CPAGE Compiler Option in the Unicode and Code Page Support documentation.

DB2ARRY - Support DB2 Arrays in SQL SELECT and INSERT Statements

The DB2ARRY option can be used to activate retrieval and/or insertion of multiple rows from/into DB2 by a single SQL SELECT or INSERT statement execution. This allows the specification of arrays as receiving fields in the SQL SELECT and as source fields in the SQL INSERT statement. If DB2ARRY is ON, it is no longer possible to use Natural alphanumeric arrays for DB2 VARCHAR/GRAPHIC columns. Instead of these, long alphanumeric Natural variables have to be used.

CHKRULE - Validate INCDIR Statements in Maps

The CHKRULE option can be used to enable or disable a validation check during the catalog process for maps.

Compilation Options for Ensuring Version Compatibility

The following options are available:

• FINDMUN - Detect Inconsistent Comparison Logic in FIND Statements

• MASKCME - MASK Compatible with MOVE EDITED

• NMOVE22 - Assignment of Numeric Variables of Same Length and Precision

• V41COMP - Disable New Version 4.2 Syntax

These options correspond to the keyword subparameters of the CMPO profile parameter and/or the NTCMPO parameter macro.

FINDMUN - Detect Inconsistent Comparison Logic in FIND Statements

With Natural Version 2.3, the comparison logic for multiple-setting fields in the WITH clause of the FIND statement has been changed. This means that when Version 2.2 programs containing certain forms of FIND statements are compiled under Version 3.1, they will return different results. This option can be used to search for FIND statements whose WITH clauses use multiple-setting fields in a way that is no longer consistent with the enhanced Version 3.1 comparison logic.

The comparison logic for multiple-value fields in the WITH clause of the FIND statement has been changed with Natural Version 2.3 so as to be in line with the comparison logic in other statements (e.g. IF).

Four different forms of the FIND statement can be distinguished (the field MU in the following examples is assumed to be a multiple-value field):

1. FIND XYZ-VIEW WITH MU = 'A'

   With Version 2.2 and above, this statement returns records in which at least one occurrence of MU has the value "A".

2. FIND XYZ-VIEW WITH MU NOT EQUAL 'A'

   With Version 2.2, this statement returns records in which no occurrence of MU has the value "A" (same as 4.). With Version 2.3 and above, this statement returns records in which at least one occurrence of MU does not have the value "A".

3. FIND XYZ-VIEW WITH NOT MU NOT EQUAL 'A'

   With Version 2.2, this statement returns records in which at least one occurrence of MU has the value "A" (same as 1.). With Version 2.3 and above, this statement returns records in which every occurrence of MU has the value "A".

4. FIND XYZ-VIEW WITH NOT MU = 'A'

   With Version 2.2 and above, this statement returns records in which no occurrence of MU has the value "A". This means that if you newly compile under Version 2.3 existing Version 2.2 programs containing FIND statements of the forms 2. and 3., they will return different results.

If you specify FINDMUN=ON, error NAT0998 will be returned for every FIND statement of form 2. or 3. detected at compilation.

Should you in these cases wish to continue to get the same results as with Version 2.2, you have to change the statements as follows:

In Form 2:

FIND XYZ-VIEW WITH MU NOT EQUAL 'A'

into

FIND XYZ-VIEW WITH NOT MU = 'A'

In Form 3:

FIND XYZ-VIEW WITH NOT MU NOT EQUAL 'A'

into

FIND XYZ-VIEW WITH MU = 'A'

MASKCME - MASK Compatible with MOVE EDITED

NMOVE22 - Assignment of Numeric Variables of Same Length and Precision

V41COMP - Disable New Version 4.2 Syntax

Important:
This compiler option will be available only with Natural Version 4.2 to allow a smooth transition. It will be removed again with a subsequent release of Natural after Version 4.2.

A number of functions and programming features introduced with Natural Version 4.2 would give rise to problems when a program developed and compiled with Version 4.2 is to be recompiled for putting into operation in a Version 4.1 environment. The relevant functions or features are listed below.

The V41COMP option has been provided to detect such incompatibilities and trigger an error message that supplies a reason code for why the recompilation failed. The following values are possible:

Compilation Relevant Differences between Version 4.2 and 4.1

The following table gives an overview of the compilation relevant differences between Version 4.2 and 4.1 and indicates the reason code that will be supplied when incompatible syntax is detected:

DEFINE DATA LOCAL
1 #ARR (A10/1:*)

INCLUDE COPY01 'WRITE *LINE'
               'WRITE *PROGRAM'

www.softwareag.com

Copyright © 1979-2010 Software AG, Darmstadt, Germany.

SEARCH   INDEX   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT