Configuration of libraries

The parser library approaches the dependency resolution in a way similar to the mainframe. On a mainframe, you define the locations of your dependencies in a JCL file (more on JCL here). As the user might want to include a large number of dependencies for multiple open codes, the source code management tool CA Endevor groups these dependencies into so-called processor groups. Then, the user assigns a processor group to the open code and Endevor resolves the dependencies.

To provide a similar experience with local files, the parser library simulates this behavior. If the user wants to include dependencies in his project, he has to define 2 configuration files inside his workspace: pgm_conf.json and proc_grps.json. The workspace component of the parser library then processes the configurations, retrieving their values upon initialization. Moreover, each time a save command is issued on any configuration file, the configuration values are reloaded via load_config method.

Processor groups

The proc_grps configuration file contains a JSON array of possible processor groups, which consist of a name and an array of folder paths, which can be relative to the root of the workspace. Additionally, path masks can be specified using wildcard sequences * (matching arbitrary 0 or more characters) and ** (matching directory separators as well as other characters). An example can be found in [lst:proc_grps].

When load_config is called, the workspace retrieves these processor groups from the configuration file and creates libraries. The libraries provide information about paths to their dependency files. During the parsing, the workspace retrieves the library corresponding to the provided processor group name and uses it to search for a macro or copy file.

Program configuration

The pgm_conf configuration file contains a JSON array of program names (or wildcards [section:wildcard]), matched to their processor groups. It serves as a list of HLASM open code files and states the libraries (in the form of processor groups) that contain the dependencies of each open code. An example can be found in [lst:pgm_conf].

From this configuration, the workspace remembers the processor group - open code mapping.

    {
      "pgroups": [
        {
          "name":"GROUP1",
          "libs": [
            "ASMMAC/",
            "C:/SYS.ASMMAC",
            "C:/common/**/maclib"
          ]
        },
        {
          "name":"GROUP2",
          "libs": [
            "G2MAC/",
            "C:/SYS.ASMMAC"
          ]
        }
      ]
    }


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