HLASM Language Support

HLASM Language Support is an extension that supports the High Level Assembler language. It provides code completion, highlighting and navigation features, shows mistakes in the source, and lets you trace how the conditional assembly is evaluated with a modern debugging experience.

HLASM Language Support is also part of Code4z, an all-round package that offers a modern experience for mainframe application developers, including COBOL Language Support, Explorer for Endevor, Zowe Explorer and Debugger for Mainframe extensions.

Getting Started

Enabling the Extension

Follow these steps to open a HLASM project:

1. In File -> Open Folder..., select the folder with the HLASM sources.
2. Open any HLASM source file (note that HLASM does not have a standard filename extension) or create a new file.
3. If the auto-detection of HLASM language does not recognize the file, set it manually in the bottom-right corner of the VS Code window.
4. The extension is now enabled on the open file. If you have macro definitions in separate files or use the COPY instruction, you need to set up a workspace.

Setting Up a Multi-File Project Environment

The HLASM COPY instruction copies the source code from various external files, as driven by HLASM evaluation. The source code interpreter in the HLASM Extension needs to be set up correctly to be able to find the same files as the HLASM assembler program.

To do this, set up two configuration files — proc_grps.json and pgm_conf.json. Follow these steps:

1. After you open a HLASM file for the first time, two pop-ups display. Select Create pgm_conf.json with current program and Create empty proc_grps.json. The two configuration files are then created with default values. They are stored in the .hlasmplugin subfolder.
2. Navigate to the proc_grps.json file. This is the entry point where you can specify paths to macro definitions and COPY files.
3. Fill the libs array with the corresponding paths. For example, if you have your macro files in the ASMMAC/ folder, add the string "ASMMAC" into the libs array.

Follow the section External Macro Libraries and COPY Members below for more detailed instructions on configuring the environment.

Language Features

The HLASM Language Support extension parses and analyzes all parts of a HLASM program. It resolves all ordinary symbols, variable symbols and checks the validity of most instructions. The extension supports conditional and unconditional branching and can define global and local variable symbols. It can also expand macros and COPY instructions.

LSP Features

Highlighting

The HLASM Language Support extension highlights statements with different colors for labels, instructions, operands, remarks and variables. Statements containing instructions that can have operands are highlighted differently to statements that do not expect operands. Code that is skipped by branching AIF, AGO or conditional assembly is not colored.

Autocomplete

Autocomplete is enabled for the instruction field. While typing, a list of instructions starting with the typed characters displays. Selecting an instruction from the list completes it and inserts the default operands. Variables and sequence symbols are also filled with a value from their scope.

Go To Definition and Find All References

The extension adds the 'go to definition' and 'find all references' functionalities. Use the 'go to definition' functionality to show definitions of variable symbols, ordinary symbols and macros, or open COPY files directly. Use the 'find all references' functionality to show all places where a symbol is used.

Macro Tracer

The macro tracer functionality allows you to track the process of assembling HLASM code. It lets you see step-by-step how macros are expanded and displays values of variable symbols at different points during the assembly process. You can also set breakpoints in problematic sections of your conditional assembly code.

The macro tracer is not a debugger. It cannot debug running executables, only track the compilation process.

Configuring the Macro Tracer

1. Open your workspace.
2. In the left sidebar, click the bug icon to open the debugging panel (Ctrl + Shift + D).
3. Select create a launch.json file.
   A "select environment" prompt displays.
4. Enter HLASM Macro tracer.
   Your workspace is now configured for macro tracing.

Using the Macro Tracer

To run the macro tracer, open the file that you want to trace. Then press F5 to open the debugging panel and start the debugging session.

When the tracer stops at a macro or COPY instruction, you can select step into to open the macro or COPY file, or step over to skip to the next line.

Breakpoints can be set before or during the debugging session.

Configuration

External Macro Libraries and COPY Members

The HLASM Language Support extension looks for locally stored members when a macro or COPY instruction is evaluated. The paths of these members are specified in two configuration files in the .hlasmplugin folder of the currently open workspace:

• proc_grps.json defines processor groups by assigning a group name to a list of directories. Hence, the group name serves as a unique identifier of a set of HLASM libraries defined by a list of directories (some of which can be optional). Additionaly, the SYSPARM and SYSTEM_ID options can be specified in the asm_options section.

• pgm_conf.json provides a mapping between programs (open-code files) and processor groups. It specifies which list of directories is used with which source file. If a relative source file path is specified, it is relative to the current workspace.

To use a predefined set of macro and copy members, follow these steps:

1. Specify any number of library directories to search for macros and COPY files in proc_grps.json. These directories are searched in order they are listed.
2. Name the group of directories with an identifier. You have created a new processor group.
3. Use the identifier of the new processor group with the name of your source code file in pgm_conf.json to assign the library members to the program.

The structure of the configuration is based on CA Endevor® SCM. Ensure that you configure these files before using macros from separate files or the COPY instruction. When you open a HLASM file or manually set the HLASM language for a file, you can choose to automatically create these files for the current program.

Example proc_grps.json:

The following example defines two processor groups, GROUP1 and GROUP2, and a list of directories to search for macros and COPY files, it also defines the SYSPARM assembler parameter for GROUP1. Additionally, if the library MACLIB/ does not exist in the workspace, the plugin does not report it as an error.

The path C:/common/**/maclib contains the wildcard **, which matches any number of characters and directory separators. Path masks can also be specified using the wildcard * which matches characters but not directory separators. The order of libraries selected by a path mask is arbitrary. We therefore recommend you ensure that macro names within these libraries are unique.

{
  "pgroups": [
    {
      "name": "GROUP1",
      "libs": [
        "ASMMAC/",
        {
          "path": "MACLIB/",
          "optional": true
        },
        "C:/SYS.ASMMAC",
        "C:/common/**/maclib"
      ],
      "asm_options": {
        "SYSPARM": "ZOS210"
      }
    },
    {
      "name": "GROUP2",
      "libs": [
        "G2MAC/",
        "C:/SYS.ASMMAC",
        "C:/common/**/maclib"
      ]
    }
  ]
}

Example pgm_conf.json:

The following example specifies that GROUP1 is used when working with source_code and GROUP2 is used when working with second_file.

{
  "pgms": [
    {
      "program": "source_code",
      "pgroup": "GROUP1"
    },
    {
      "program": "second_file",
      "pgroup": "GROUP2"
    },
  ]
}

If you have the two configuration files configured as above and invoke the MAC1 macro from source_code, the folder ASMMAC/ in the current workspace is searched for a file with the exact name "MAC1". If that search is unsuccessful the folder C:/SYS.ASMMAC is searched. If that search is unsuccessful an error displays that the macro does not exist.

The program name in pgm_conf.json can be wildcarded, as in the following example:

{
  "pgms": [
    {
      "program": "*",
      "pgroup": "GROUP1"
    }
  ]
}

In this example, GROUP1 is used for all open code programs.

File Extensions

The alwaysRecognize option in pgm_conf.json has been deprecated in favour of the standard VSCode user and workspace level setting file.associations.

proc_grps.json can include an optional parameter macro_extensions which contains a list of extensions that are to be used to identify files with macro definitions. The options can be specified both at the top level of the file, providing the default list for all libraries in all process groups, and at the level of individual library definitions, overriding the default from the top level.

For example, with the extension .hlasm, a user can add the macro MAC to his source code even if it is in a file called MAC.hlasm.

The following example of proc_grps.json specifies that files with the extension .hlasm are recognized as macros, with the exception of macros in the C:/external/project/macs directory, where they need to have the extension .mac.

{
  "pgroups": [
    {
      "name": "GROUP1",
      "libs": [
        "ASMMAC/",
        "C:/SYS.ASMMAC",
        {
          "path": "C:/external/project/macs",
          "macro_extensions": [
            ".mac"
          ]
        }
      ]
    }
  ],
  "macro_extensions": [
    ".hlasm"
  ]
}

Suppression of Diagnostics

For files that use macros extensively but do not have the definitions available, diagnostics reported by HLASM Language support might not be helpful. For those cases, there is the setting diagnosticsSuppressLimit, which can be set either in the editor settings, or in pgm_conf.json. For files that do not have processor group configuration in pgm_conf.json, all diagnostics are suppressed if they exceed the configured limit.

{
  "pgms": [
    {
      "program": "source_code",
      "pgroup": "GROUP1"
    }
  ],
  "diagnosticsSuppressLimit" : 15
}

In the pgm_conf.json above, the source_code file has a configuration, so all discovered diagnostics are always shown. However, if you open another file and do not assign a processor group to it, its diagnostics are not shown if there are more than 15 of them.

Preprocessors

Processor groups can be configured so that the HLASM source will be processed with a preprocessor. Currently, there is the option to use DB2 preprocessor.

It can by configured using the preprocessor key in processor group:

{
  "pgroups": [
    {
      "name": "GROUP1",
      "libs": [ "ASMMAC/" ],
      "preprocessor": "DB2"
    }
  ]
}

Questions, issues, feature requests, and contributions

• If you have a question about how to accomplish something with the extension, or come across a problem, file an issue on GitHub
• Contributions are always welcome! Please see our GitHub repository for more information.
• Any and all feedback is appreciated and welcome!

Technical Assistance and Support for HLASM Language Support

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 CA Support Online
• 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 CA 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 CA software and Broadcom shall not be responsible for these effects or any resulting degradation in performance of the Broadcom CA software. Severity 1 cases must be opened via telephone and elevations of lower severity incidents to Severity 1 status must be requested via telephone.

Privacy Notice

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. See the telemetry.telemetryLevel and telemetry.enableTelemetry (deprecated) settings of VS Code.

The current release of HLASM Language Support collects anonymous data for the following events:

• Activation of this VS Code extension
• Open and close of files
• Invocation of the following features: Autocomplete, Go to definition, Find all references and Hover
• Launch of Macro tracer and subsequent user interactions with the debugging interface (step into, step over, continue, set breakpoints)
• Malfunctions of the extension

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 HLASM Language Support
• Extension response time

Additionally, when a file is opened, the following information are logged:

• Number of diagnostics (errors and warnings)
• Number of files that were parsed including macros and COPY files
• Number of parsed lines
• Whether the diagnostics were suppressed
• Whether matching processor group was found in the configuration