There are several limitations with using the editors.
The following features are not available in the COBOL Editor,
PL/I Editor, and Compare Editor when you compare COBOL or PL/I files:
Autosave
Automatic maintenance of sequence numbers
Preventing text modifications that are left of the information
margin from shifting sequence numbers out of position.
Split tokens are not supported in include statements
or exec statements in PL/I programs.
Split tokens that include DBCS characters are not supported.
The following uses of COBOL line continuations are not supported
by the COBOL parser, or have limited support:
Line continuations in copybooks
Line continuations in EXEC blocks
Line continuations in COPY or REPLACE statements
Line continuations of line comments
Line continuations in picture clauses
When editing PL/I and COBOL programs, the editors do not support
starting a token on one line and then continuing the same token on
the next line. If you type I in the last column
of one line, and F in the first column of the
next line, the compiler does not interpret that to be an IF token.
When editing PL/I and COBOL programs, do not split integer literals
or any other tokens across lines.
Note: Splitting string literals across
lines is supported.
Remote bidirectional characters are not supported. Remote files
that contain bidirectional characters can be opened in read-only mode
only. Use the System z® LPEX
Editor to edit these files.
When you create a partitioned data set member in ISPF,
and set the data set profile option PACK ON to use
direct access storage devices (DASD) more efficiently, the editors
in Rational® Developer for z Systems™ cannot
read the members because of the packed format. You cannot unpack and
expand the data using the editors in Rational Developer for z Systems.
You must unpack the data set before you attempt to edit members. For
more information about using PACK ON, see the related
topics.