This folder contains an example for a VS Code multi-root workspace demonstrating how it can be utilized for IBM Z Open Editor for ZAPP and IBM User Build. For the extended User Build example switch to the branch wazi-main. The branch main will only cover ZAPP.
See the VS Code documentation for more details about how multi-root workspaces are used. To open this example, use the VS Code menu File > Open Workspace from File... and select the file multiroot/workspace/sam.code-workspace. VS Code will reload itself and now show the folders that make up the multi-root workspace comrpising of the copybooks, sam, and workspace folders. Each of these has been configured to be its own individual workspace. They could have been distributed to all kinds of other folders on your system, each having their own Git repository, but we kept here in one hierarchy to provide them as an easy to install example in our https://github.com/IBM/zopeneditor-sample GitHub repository.
Expand the workspace folder sam and open the file SAM1.cbl. You see that Z Open Editor resolves the copybooks included in (around) lines 65, 71 and 75 although the sam workspace does not include any copybooks.
Open and examine the zapp.yaml file in sam (See here to learn more about ZAPP). You see that it specifies a property-group with the name sam-local with the two syslib entries cust and trans. These folders are located in a different workspace as you find them in the copybooks workspace folder. Z Open Editor will look in all workspaces of the multi-root workspace for these folders relative to the workspace root folder as specified in the sam.code-workspace file.
It is possible to have multiple ZAPP files in your multi-root workspaces. They must be in the root folder of each workspace. Z Open Editor will combine all the property-groups it finds in all of these ZAPP files and try to resolve them. The order will somewhat arbitrary, but can be described as the workspace folder first and then the other workspaces in alphabetical order of their path names. We recommend to keep ZAPP files in the workspace of the application programs for which they are used for.