The System z® LPEX
Editor and PL/I Editor automatically validate the syntax of PL/I
files and embedded CICS® and
SQL statements.
The editor performs real-time syntax checking and provides annotations
describing the errors. If an errors is found, warning icon (
) is displayed. To see the annotation
describing the error, hover your mouse over the icon. The maximum
number of errors reported is 200.
To turn off real-time syntax checking, select Disable
syntax parser on the Real-Time Syntax Checking preference
page. To enable or disable SQL annotations, use the EXEC
SQL statements preference page.
The System z LPEX Editor
and the COBOL Editor check for the following kinds of errors in COBOL
source files:
- COBOL syntax errors
- Missing include files
- Undeclared variables
The following sections provide examples of the kinds of errors
the editor detects in PL/I files.
Example of syntax error
In the following
example from the HelloApp.pli sample program, an error was flagged
in the Do forever; statement.
You can place your cursor over
the flag to display an annotation that explains the error:
Example of missing include file
In the following
example from the Global Auto Mart sample application, the GAM0ICT
include file is missing:
Example of undeclared variables
If a program
uses a variable that is undeclared, the editor displays a warning.
In the following example from the HelloApp.pli sample file, the program
declares a variable named theAnswer2, but uses a variable named theAnswer.
Limitations
The following legal PL/I syntactic
constructions are marked as errors:
- Illegal PL/I syntax in macro preprocessor input, when the macro
preprocessor output is legal PL/I
- Labels on preprocessor directives
- Entry constants
- Type functions
- Generic attributes
- Factoring of attributes when declaring structures
- isub option with defined attribute
- tstack attribute of the attach statement
- Implicit variable declarations
The following illegal PL/I syntactic constructions are not marked
as errors:
- Condition prefixes for do statements
- Label prefixes for declare, default, when, otherwise, and on statements
- Scaling factors for float or fixed
- Duplicate attributes for declaration statements
- Syntax errors in macro preprocessor output
The NAMES, OR and NOT compiler options are supported in PROCESS
statements and property groups associated with PL/I programs. OR and
NOT default compiler options specified on the remote system are not
supported. Other compiler options are not supported.