The following limitations apply to the expanded copybook view:
- Bookmarks are not supported in the expanded copybook view. You can add bookmarks in copybooks that are opened as standalone files.
- It is not possible to edit copybooks referenced through a COPY... REPLACING statement in expanded copybook view when the view shows the replaced values. In this case, the expanded copybook view is read-only.
- The read-only status of expanded copybooks is not preserved when you close the project. Next time you open the project, the copybook is shown in the Expanded Copybook view but not as read-only.
- If you used the OF or IN phrases with a COPY statement, it is not possible to show the corresponding copybook in the Expanded Copybook view or open it using the
Open "CopybookName" in New Window command if the copybook is stored in a library file (where you have used the COPYLBR Compiler directive).
- Navigating to items in the expanded copybook view is not supported from the
Class View or using the
Navigate To command.
- References to file locations in the output windows such as pointing to the build output, or in the results received by
Find in Files, do not point to items in the expanded copybook view.
- Selecting the currently selected statement in the call stack in an expanded copybook may show the actual copybook. You can use the
Show Next Statement command of the debugger to return the actual expanded copybook position.
- The Breakpoints window always shows the line number of a breakpoint within the file containing it, not the line number within expanded copybook view.
- The
Call Stack,
Threads and
IntelliTrace windows all display line numbers corresponding to the file containing the statement, not the line number within expanded copybook view.
- If you move the caret to an invalid position in the expanded copybook view, the
Set Next Statement command will display an ‘Unable to set the next statement to this location’ error message and the copybook will be opened as a separate document.
- When stepping through managed code, if the next statement to step onto is within the same class or program, and on the same line number, but in a different source file, the debugger steps over that statement. For example, if you try to step from line 10 of
Program1.cbl to line 10 of
Copybook1.cpy, the debugger steps over the statement in the copybook.
- When you add a COPY statement in a COBOL program and then show it in Expanded Copybook View, the line for the copybook statement is read-only. If you then perform an Undo in the COBOL program, the COPY statement is removed while the contents of the copybook is still shown in the program.
- Replace All does not work inside the Expanded Copybook View
- For copybooks in your project with file extensions that are not traditionally associated with COBOL you must first add the file extension to the list of known copybooks extensions in
Tools > Options > Text Editor > File Extensions before you can show them in Expanded Copybook View.
