COBOL Language Support enhances the COBOL programming experience on your IDE. The extension leverages the language server protocol to provide autocomplete, syntax highlighting and coloring, and diagnostic features for COBOL code and copybooks. The COBOL Language Support extension can also connect to a mainframe using the Zowe Explorer extension to automatically retrieve copybooks used in your programs and store them in your workspace.
COBOL Language Support recognizes files with the extensions .cob, .cbl and .cobol as COBOL files, and .cpy and .copy as COBOL copybooks.
How can we improve COBOL Language Support? Let us know on our Git repository
This extension is a part of the Che4z open-source project. Feel free to contribute right here.
COBOL Language Support is also part of Code4z, an all-round package that offers a modern experience for mainframe application developers, including HLASM Language Support, Explorer for Endevor, Zowe Explorer, COBOL Control Flow and Debugger for Mainframe extensions.
- Java version 8 or higher with the PATH variable correctly configured. For more information, see the Java documentation.
- To enable automatic copybook retrieval from the mainframe, the following are required:
- Zowe Explorer version 1.15.0 or higher.
- A Zowe Explorer
zosmforzftpprofile with credentials and a connection URL defined.
The COBOL Language Support extension is supported on Visual Studio Code and Eclipse Che.
This extension is not compatible with other extensions that provide COBOL support except COBOL Control Flow. We recommend that you disable all other COBOL-related extensions to ensure that COBOL Language Support functions correctly.
The COBOL Language Support extension only supports IBM Enterprise COBOL. Other versions of COBOL are not supported.
COBOL Language Support provides the following COBOL syntax awareness features:
Autocomplete speeds up the coding process by intuitively suggesting the most likely variables or paragraphs to follow existing code. The extension provides live suggestions while you type for:
- COBOL keywords, variables, paragraphs and sections
- IDMS DML keywords
- CICS and DB2 SQL keywords
- Code Snippets
- Copybook variable and paragraph names
- Names of copybooks that are used in the program
- Names of locally-stored subroutines that are used in the program
The autocomplete feature is only available in the main COBOL file, not in copybooks.
This feature checks for mistakes and errors in COBOL code. The syntax check feature reviews the whole content of the code and suggests fixes, through syntax and semantic analysis which returns diagnostics on the entire context of the code, not just keywords.
This feature is also enabled for CICS and DB2 SQL keywords and variables.
The extension enables syntax highlighting for COBOL code.
Contrasting colors are used in displayed code for ease of identifying and distinguishing keywords, variables, paragraphs and sections.
The extension enables outline view and breadcrumb view, which show the structure of elements within the program and allow easy navigation between them.
Before you write your COBOL code from scratch, search the snippet library for useful templates.
Follow these steps:
- Press
F1to open the command palette. - Type Insert Snippet and press enter.
- Select the snippet that you want to insert.
You can also insert a code snippet by typing the name of the snippet in your code and clicking on the autocomplete text.
The COBOL Language Support extension also supports user snippets. Add your custom snippets to the COBOL.json file in your user snippets folder.
The dialects setting lets you include the specific language analysis in your COBOL files. For now you can include IDMS as a language of choice. The dialects setting is not enabled by default. To enbale the setting, go to VS Code Settings > User > Extensions > COBOL Language Support > Cobol-lsp: Dialects.
Note: If you disable the setting, your IDMS bits of code are highlighted as errors.
The COBOL Language Support extension supports subroutines specified in CALL statements if the called program is stored in a local folder in your workspace. The Go To Definition and Find All References functionalities, as well as autocomplete, are extended to work for names of subroutines.
To enable subroutine support, specify the paths of folders containing subroutine files in your workspace extension settings.
Follow these steps:
- Open the Extensions tab, click the cog icon next to COBOL Language Support and select Extension Settings to open the COBOL Language Support extension settings.
- Switch from User to Workspace.
- Under Subroutine-manager: Paths-local, specify the paths of the folders containing subroutines.
- Tip: We recommend that you specify relative paths from the workspace root. To obtain the relative path of a folder in your workspace, right-click it in the folder tree and select Copy Relative Path.
- The folders are searched in the order they are listed. If two folders contain a subroutine with the same file name, the one from the folder higher on the list is used.
- Open a program or project.
Subroutine support features are now enabled.
If you specify your subroutine folders using absolute paths or paths containing ../ or ./, the subroutine folders are not watched for changes. You might need to resolve names of recently added files in your code manually.
The COBOL Language Support extension supports copybooks used in your source code that are stored in a local folder in your workspace. If your copybooks are stored in mainframe data sets, you can use a Zowe Explorer profile to automatically download them from the mainframe to your workspace.
You can use copybooks stored in local folders, mainframe data sets or both. To enable copybook support, you specify the folders and data sets that contain copybooks used in your project in the workspace settings. When a copybook is used in the program, the folders and data sets are searched in the order they are listed for files and members that match the name of the copybook. If a copybook with the same file name is located in both a local folder and a mainframe data set, the one in the local folder is used.
COBOL Language Support also supports copybooks for the IDMS and MAID dialects, called with the COPY IDMS and COPY MAID statements. For more information, see the IDMS documentation.
Copybook support features are disabled for files stored in the folder .c4z/.extsrcs in your workspace. If you also use the Debugger for Mainframe extension to debug your COBOL programs, you might have some files stored in this folder.
Configuring copybook support on COBOL Language Support also enables copybook support features of the COBOL Control Flow extension.
You can store your copybooks locally in folders in your workspace and specify those folder paths in your workspace extension settings.
Follow these steps:
- Open the Extensions tab, click the cog icon next to COBOL Language Support and select Extension Settings to open the COBOL Language Support extension settings.
- Switch from User to Workspace.
- Specify the paths of the folders containing copybooks:
- Under Cpy-manager: Paths-local for standard IBM Enterprise COBOL.
- Under Cpy-manager: Paths-local: Maid for the MAID dialect.
- Under Cpy-manager: Paths-local: Idms for the IDMS dialect.
- Tip: We recommend that you specify relative paths from the workspace root. To obtain the relative path of a folder in your workspace, right-click it in the folder tree and select Copy Relative Path.
- The folders are searched in the order they are listed. If two folders contain a copybook with the same file name, the one from the folder higher on the list is used.
- Open a program or project.
Copybook support features are now enabled.
If you specify your copybook folders using absolute paths or paths containing ../ or ./, the copybook folders are not watched for changes. You might need to resolve names of recently added copybooks in your code manually.
To resolve copybook names manually, hover over the copybook name with the error underline, select Quick Fix... and Resolve copybook.
You can also set up automatic copybook retrieval from the mainframe to download copybooks from mainframe data sets to your workspace.
Follow these steps:
- Ensure that you have a Zowe Explorer profile configured, with credentials and a connection URL defined.
- Open the Extensions tab, click the cog icon next to COBOL Language Support and select Extension Settings to open the COBOL Language Support extension settings.
- Switch from User to Workspace.
- Under Cpy-manager: Paths-dsn, list the names of any number of partitioned data sets on the mainframe to search for copybooks. The data sets are searched in the order they are listed, so if two data sets contain a copybook with the same member name, the one from the data set higher on the list is downloaded.
- Under Profile, enter the name of your Zowe Explorer profile.
- Open a program or project.
All copybooks used in the program or project which are not stored locally are downloaded from the mainframe data sets that you specified in step 3.
Copybook support features are now enabled.
Copybooks that you retrieve from mainframe data sets are stored in the .c4z/.copybooks directory within the workspace, which is created automatically.
Because copybooks that are downloaded to the .copybooks folder might change on the mainframe, we recommend that you refresh your copybooks from time to time. To refresh your copybooks, manually delete the .copybooks folder in your workspace. The copybooks are then re-downloaded from the mainframe the next time you open a file that references each copybook.
Copybooks downloaded from the mainframe using an older version of COBOL Language Support might also be found in a .copybooks directory in the workspace root. We recommend that you delete this folder so that all files are downloaded again to the .c4z/.copybooks folder.
The extension includes the following copybook support features:
Syntax and semantic analysis are enabled for keywords, variables, and paragraphs across all copybooks used in the COBOL file, to ensure and maintain compatibility of copybooks called in code.
The semantic analysis feature takes into account COPY REPLACING statements which alter the content of copybooks when checking for errors.
Syntax coloring is automatically enabled for copybook files with the extension .cpy and .copy, as long as they are used in the main COBOL file. You can also select the COBOL Copybook language mode to enable syntax coloring for copybook files.
The Find All References and Go To Definition functionalities are extended to work for occurrences of copybook names, variables and paragraphs in the main COBOL file.
- Find All References identifies all occurrences of variables and paragraphs from copybooks in the code.
- Go To Definition enables you to right-click on any variable or paragraph to reveal a definition of the element. If the definition is in a copybook, or the name of a copybook, the copybook opens.
- Inbuilt protection against recursive and missing copybooks. If the copybook is missing or contains looping code, an error displays, preventing issues only being discovered when the code is executed.
- Variables and paragraphs are defined across copybooks. This ensures consistency of code, and prevents issues in error diagnostics caused by incorrect variables or paragraphs in code.
- Functionality to skip variable levels when called, reducing call time.
To generate a troubleshooting log for the LSP server, specify a value for the parameter cobol-lsp.logging.level.root in the extension settings. Specify one of the following values:
- ERROR
- WARN
- INFO
- DEBUG
- TRACE
- ALL
These values are ordered from returning the least information ("ERROR"; errors only) to the most information ("ALL"; all details).
Troubleshooting logs are stored in the subfolder \LSPCobol\logs within your user home directory.
The COBOL Language Support extension is made available to customers on the Visual Studio Code Marketplace in accordance with the terms and conditions contained in the provided End-User License Agreement (EULA).
If you are on active support for Brightside, you get technical assistance and support in accordance with the terms, guidelines, details, and parameters that are located within the Broadcom Working with Support guide.
This support generally includes:
- Telephone and online access to technical support
- Ability to submit new incidents 24x7x365
- 24x7x365 continuous support for Severity 1 incidents
- 24x7x365 access to Broadcom Support
- Interactive remote diagnostic support
- Technical support cases must be submitted to Broadcom in accordance with guidance provided in “Working with Support”.
Note: To receive technical assistance and support, you must remain compliant with “Working with Support”, be current on all applicable licensing and maintenance requirements, and maintain an environment in which all computer hardware, operating systems, and third party software associated with the affected Broadcom software are on the releases and version levels from the manufacturer that Broadcom designates as compatible with the software. Changes you elect to make to your operating environment could detrimentally affect the performance of Broadcom software and Broadcom shall not be responsible for these effects or any resulting degradation in performance of the Broadcom software. Severity 1 cases must be opened via telephone and elevations of lower severity incidents to Severity 1 status must be requested via telephone.
The extensions for Visual Studio Code developed by Broadcom Inc., including its corporate affiliates and subsidiaries, ("Broadcom") are provided free of charge, but in order to better understand and meet its users’ needs, Broadcom may collect, use, analyze and retain anonymous users’ metadata and interaction data, (collectively, “Usage Data”) and aggregate such Usage Data with similar Usage Data of other Broadcom customers. Please find more detailed information in License and Service Terms & Repository.
This data collection uses built-in Microsoft VS Code Telemetry, which can be disabled, at your sole discretion, if you do not want to send Usage Data.
The current release of COBOL Language Support collects anonymous data for the following events:
- Activation of this VS Code extension
- Problem interaction
- Quick Fix
- Invalid ZOWE credentials
- ZOWE connection issues
- Java version issues
Each such event is logged with the following information:
- Event time
- Operating system and version
- Country or region
- Anonymous user and session ID
- Version numbers of Microsoft VS Code and COBOL Language Support