From dc154650fcb21c6f0d6d4938cf6c9d050f6b5d3e Mon Sep 17 00:00:00 2001 From: Peter Haumer <4391934+phaumer@users.noreply.github.com> Date: Tue, 12 Mar 2024 17:47:21 -0700 Subject: [PATCH] Updates for the 4.0.0 release --- README.md | 67 ++- .../rse-api-for-zowe-cli/LICENSE.txt | 8 +- .../rse-api-for-zowe-cli/NOTICES.txt | 525 +----------------- product-licenses/zapp/LICENSE.txt | 20 +- product-licenses/zapp/NOTICES.txt | 135 ++++- zapp/zapp-schema-1.1.0.json | 433 +++++++++++++++ 6 files changed, 621 insertions(+), 567 deletions(-) create mode 100644 zapp/zapp-schema-1.1.0.json diff --git a/README.md b/README.md index ef7a019b8..5d743afb5 100644 --- a/README.md +++ b/README.md @@ -9,11 +9,11 @@ > Go here for the full [Documentation](https://ibm.github.io/zopeneditor-about/Docs/introduction.html?utm_source=vscode&utm_medium=referral&utm_campaign=vscode_marketplace) online. -**Note, Z Open Editor version 3 has some breaking changes that require manual migration steps. See this dedicated [user documentation page](https://ibm.github.io/zopeneditor-about/Docs/zopeneditor_v3.html) for details.** +**New**: IBM Z Open Editor v4.0.0 introduced advanced capabilities that go beyond program editing. These are at the moment local preprocessor support for COBOL, a new Web view built on top of Zowe Explorer that displays z/OS resources such as data sets and jobs in a sortable table, and a new DBB user build VS Code Problems view integration. All users get a 60-day evaluation trial for these advanced capabilities. After that they are licensed via the IBM Developer for z/OS Enterprise Edition offering. The language editing capabilities are still free and will be maintained and enhanced as always. See the [IBM Documentation](https://ibm.biz/code-whatsnew) with details. -This extension provides language support for the IBM Enterprise programming languages for z/OS®. It supports COBOL v6.4, PL/I v6.1, and High Level Assembler for z/OS 2.5 and TSO/E REXX. This also includes capabilities for embedded statements in COBOL and PL/I for CICS 6.1, IMS 15.1.0 and SQL DB2 for z/OS 12.1. Earlier versions of any of these components will also work. +**New**: IBM Z Open Editor v3.3.0 introduced AI assistance for Java developers with [IBM watsonx Code Assistant for Z](https://www.ibm.com/products/watsonx-code-assistant-z), which supports AI-assisted transformation of COBOL to Java for modernizing applications. -IBM Z Open Editor realizes its language support by implementing fully functional [language servers](https://langserver.org/) together with additional editor enhancements that enable IBM Z developers to utilize features such as: +The core extension provides language support for the IBM Enterprise programming languages for z/OS®. It supports COBOL v6.4, PL/I v6.1, and High Level Assembler for z/OS 3.1 and TSO/E REXX. This also includes capabilities for embedded statements in COBOL and PL/I for CICS 6.1 (6.2 Beta), IMS 15.1.0 and SQL DB2 for z/OS 12.1. Earlier versions of any of these components will also work. IBM Z Open Editor realizes its language support by implementing fully functional [language servers](https://langserver.org/) together with additional editor enhancements that enable IBM Z developers to utilize features such as: - Real-time syntax checking and highlighting while you type - Problems view with all syntax errors and (in COBOL) unreachable code @@ -31,18 +31,20 @@ IBM Z Open Editor realizes its language support by implementing fully functional - Custom code snippet support and more than 200 high value code snippets for COBOL, PL/I, and JCL out of the box - Search and replace refactoring across multiple program files -Note, that the current early releases for HLASM and REXX only support a subset of the capabilities available for COBOL and PL/I. For the Job Control Language (JCL), the extension only provides syntax highlighting. +Note, that for Job Control Language (JCL), the extension only provides syntax highlighting. To learn more about the IBM Z Open Editor extension's capabilities, we suggest that you walk through our [documentation](https://ibm.github.io/zopeneditor-about/Docs/introduction.html) and try it with the [example repository](https://github.com/IBM/zopeneditor-sample) provided on GitHub. -To interact with z/OS, this extension also automatically co-installs the [Zowe Explorer](https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe) VS Code Extension. This extension can be used to edit COBOL, PL/I, HLASM, REXX, and JCL files opened on z/OS MVS™ and USS using the Zowe extension's Data Sets and USS views. It can even run JCL jobs via right-click and let's you download and browse job spool files. Note, that since Z Open Editor version 2.0.2 version 2.0.0 or newer of Zowe Explorer is required. +To interact with z/OS, this extension also automatically co-installs the [Zowe Explorer](https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe) VS Code Extension. This extension can be used to edit COBOL, PL/I, HLASM, REXX, and JCL files opened on z/OS MVS™ and USS using the Zowe extension's Data Sets and USS views. It can even run JCL jobs via right-click and let's you download and browse job spool files. ## Table of contents - [Privacy notice](#privacy-notice-for-feedback) - [Prerequisites](#prerequisites) - [Configuring Java](#configuring-java) +- [IBM watsonx Code Assistant for Z](#generate-java-from-cobol-using-ibm-watsonx-code-assistant-for-z) - [COBOL and PL/I Language Server Protocol capability examples](#language-server-protocol-capability-examples) +- [Advanced Capabilities](#advanced-capabilities) ## Privacy notice for feedback @@ -53,12 +55,14 @@ This editor uses [Microsoft VS Code's Telemetry](https://code.visualstudio.com/d This current release of IBM Z Open Editor will collect anonymous data for the following events: - Activation of this VS Code extension -- Opening and closing files of a specific language such as COBOL, PL/I, HLASM, REXX, JCL +- Deactivation of this VS Code extension +- Opening, closing and saving files of a specific language such as COBOL, PL/I, HLASM, REXX, JCL - Resolving of include files and assembler macros: success or failure - Using common language server operations such as code completion, references, definition, rename - Starting a user build -- Deactivation of this VS Code extension - Responding to the feedback dialog +- Using IBM watsonx Code Assistant for Z operations +- Activating trial or full unlock licenses Such events are logged with the following information: @@ -79,16 +83,15 @@ Review the [IBM Z Open Editor License Agreement](https://github.com/IBM/zopenedi Here are the prerequisites for installing this extension in Visual Studio Code: -- Microsoft VS Code version 1.53.2 or later: We recommend using always the latest VS Code version available. However, the required minimal version since v2 of Z Open Editor is now 1.53.2; it was 1.44.0 in v1. If you do not have VS Code installed we recommend using the [Visual Studio Code for Java Installer](https://code.visualstudio.com/docs/languages/java#_install-visual-studio-code-for-java) provided by Microsoft as it automatically downloads and installs a Java SDK together with VS Code. (See, but skip the next bullet for the Java dependency, if you use this option.) +- Microsoft VS Code version 1.81.0 or later: We recommend using always the latest VS Code version available. If you do not have VS Code installed we recommend using the [Visual Studio Code for Java Installer](https://code.visualstudio.com/docs/languages/java#_install-visual-studio-code-for-java) provided by Microsoft as it automatically downloads and installs a Java SDK together with VS Code. (See, but skip the next bullet for the Java dependency, if you use this option.) - Java SDK or JRE version 11 or later - 64 bit: The language servers included in this extension are implemented in Java. Therefore, you need to install and configure a 64-bit Java SDK or Runtime in order to start it successfully. We recommend installing VS Code for Java as described above, but if you already have VS Code or want to install Java yourself then you can choose from the following options: - You can use versions 11, or 17 of [IBM's Semeru Runtime](https://developer.ibm.com/languages/java/semeru-runtimes/) that can be [downloaded here](https://developer.ibm.com/languages/java/semeru-runtimes/downloads). - You can use [Oracle Java 11](https://www.oracle.com/java/technologies/downloads/#java11) or the LTS versions 17 of Oracle Java. - You can also use version 11, or 17 of the [OpenJDK](https://adoptium.net/index.html). - - If you are using version 1.1 or newer of Z Open Editor you can also use just a Java Runtime Environments (JRE) as well. - Newer versions of Java should also work, but are not as rigorously tested for Z Open Editor as Java 11. - Various settings are provided to configure how the extension uses Java. See the [Configuring Java](#configuring-java) section below for more details. -- Zowe CLI 7.3.1 or newer (CLI 6.33.3 and newer also still works) and the Zowe Explorer VS Code extension v2.4.0 or newer: To make use of [Zowe](https://zowe.org) to open and edit files directly from z/OS MVS or USS, you need Zowe client software and either IBM RSE API or z/OSMF configured. We strongly recommend that you use Zowe CLI version 7 or newer. For more information, see [Installing Zowe CLI](https://docs.zowe.org/stable/user-guide/cli-installcli) and [VS Code Extension for Zowe](https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe#user-content-prerequisites). Once installed, you must [create a Zowe CLI user profile](https://ibm.github.io/zopeneditor-about/Docs/interact_zos_overview.html) so that data sets can be found and accessed. +- Zowe CLI 7.21.3 or newer and the Zowe Explorer VS Code extension v2.14.1 or newer: To make use of [Zowe](https://zowe.org) to open and edit files directly from z/OS MVS or USS, you need Zowe client software and either IBM RSE API or z/OSMF configured. For more information, see [Installing Zowe CLI](https://docs.zowe.org/stable/user-guide/cli-installcli) and [VS Code Extension for Zowe](https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe#user-content-prerequisites). Once installed, you must [create a Zowe CLI team configuration file](https://ibm.github.io/zopeneditor-about/Docs/interact_zos_overview.html) so that data sets can be found and accessed. - (Optional) Git: To use the features that involve Git, you must install Git and have it available in your system path so that VS Code can display it. On Macs, Git comes out of the box. On Linux, you can install Git with your distribution's package manager. On Windows, you can get Git from . @@ -102,7 +105,7 @@ Then once you finished installing the IBM Z® Open Editor extension open the dir ## Configuring Java -The COBOL, PL/I, HLASM, and REXX language servers utilized by IBM Z Open Editor were implemented using the Java programming language. Therefore, a Java Runtime is required to be available via settings or the program path to start in VS Code. The IBM Z Open Editor extension utilizes VS Code Settings properties, which can be added to VS Code user settings, to configure which and how Java should be used. These settings allow you to select the specific installation of Java to pick, in case you have several installations, as well as set parameters such as how much memory you want the extension to use. +The COBOL, PL/I, HLASM, and REXX language servers utilized by IBM Z Open Editor were implemented using the Java programming language. Therefore, a Java Runtime is required to be available via settings or the program path to start in VS Code. The IBM Z Open Editor extension utilizes VS Code user settings to configure which and how Java should be used. These settings allow you to select the specific installation of Java to pick, in case you have several installations, as well as set parameters such as how much memory you want the language servers to use. ### Selecting the Java installation to use @@ -114,7 +117,7 @@ Before starting a language server the language server clients in the IBM Z Open 1. The PATH defined for the environment in which Z Open Editor runs (i.e. you default Windows or MacOS path) 1. A typical platform-specific location. For example, on MacOS it will execute the `/usr/libexec/java_home -V` and on Windows the `where java.exe` commands to locate a valid Java installation. -As you can see user settings always take precedence over the other options listed, which enables you to specify a different Java version for IBM Z Open Editor than the default on your computer in case you have installed multiple version. If you used the recommended [Visual Studio Code for Java Installer](https://code.visualstudio.com/docs/languages/java#_install-visual-studio-code-for-java) the `java.home` user setting was set by this installer. +As you can see user settings always take precedence over the other options listed, which enables you to specify a different Java version for IBM Z Open Editor than the default on your computer in case you have installed multiple version. If you used the recommended [Visual Studio Code for Java Installer](https://code.visualstudio.com/docs/languages/java#_install-visual-studio-code-for-java) the `java.home` user setting was set by this installer. Also note, that the methods at the end of the list require a significant amount of time as they are executing programs on your system. To improve startup times you should consider user settings as they provide the best startup performance. If Java cannot be located check the VS Code Output view's Z Open Editor tab for any error and try to fix the problem by either setting the `JAVA_HOME` environment variable or create an entry in your VS Code user settings. @@ -140,6 +143,10 @@ By default, the language server clients that start the language servers for COBO "zopeneditor.server.memoryAllocation": 640 ``` +## Generate Java from COBOL using IBM watsonx Code Assistant for Z + +Enable IBM watsonx Code Assistant and upload a COBOL service that is prepared for transformation. Use AI-assistance to generate Java classes and object-oriented Java business logic that is semantically equivalent to existing COBOL to help you quickly get started modernizing your applications. To learn more, visit the [IBM watsonx Code Assistant Product guide](https://www.ibm.com/products/watsonx-code-assistant-z). + ## Language Server Protocol capability examples The following animations just give you glimpse of the capabilities available in IBM Z Open Editor. We are showing you different examples using different programming languages, but most of the features shown here are available for all four languages: COBOL, PL/I, HLASM, as well as REXX. @@ -200,20 +207,6 @@ Select a variable or a paragraph name, right-click for menu, and choose `Peek Re ![ ](readme/peek-references.gif) -## Summary of keyboard shortcuts - -| Description | Windows | Mac | -| ------------------------------------------------ | --------------- | ------------------ | -| Search for identifiers within the outline | `Ctrl+Shift+O` | `Cmd+Shift+O` | -| Show the list of available code completion | `Ctrl+space` | `Ctrl+Space` | -| Open copybook/include files in a separate editor | `Ctrl+click` | `Cmd+Click` | -| Change all occurrences | `Ctrl+F2` | `Cmd+F2` | -| Find all references | `Alt+shift+F12` | `Option+Shift+F12` | -| Peek references | `Shift+F12` | `Shift+F12` | -| Go to definition | `F12` | `F12` | -| Peek definition | `Alt+F12` | `Option+F12` | -| Rename symbols | `F2` | `F2` | - ## User Build The User Build feature helps COBOL, PL1, and HLASM developers to leverage IBM Dependency Based Build (DBB) toolkit right from their local VS Code or Eclipse Che development environment. A developer who is working on a COBOL, PL1, or HLASM applications can run a User Build to compile and link programs before the code is ready to be exposed to the repository for others to use. With User Build, you can compile your program without having to perform commits or pushes. @@ -227,4 +220,24 @@ User Build automatically does the following when you click to run a build: User Build allows developers to do their zOS development locally using modern tools without context switching. -See our Z Open Editor documentation for [details](https://ibm.github.io/zopeneditor-about/Docs/introduction.html). +To learn more see the [IBM Documentation](https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-building-cobol-pli-hlasm-programs-user-build). + +## Advanced Capabilities + +IBM Z Open Editor v4.0.0 is the first release to introduce a set of all-new enterprise-level advanced capabilities. While the core Z Open Editor continues to provide full language support for COBOL, PL/I, REXX, and HLASM for free, this release adds capabilities for enterprise-level development use cases that go beyond program editing. They cover capabilities that you would typically only find in our commercial editing solutions such as IBM Developer for z/OS Enterprise Edition (IDzEE). With this release, we started adding these capabilities to Z Open Editor under the same licensing terms as IDzEE and a 60-day evaluation license. IDzEE customers can unlock the features by using RSE API or separately distributed activation kits. For more information, see [IBM Documentation](https://ibm.biz/code-whatsnew). + +### Local preprocessor support for COBOL + +Run a preprocessor on your local workstation driven by a new ZAPP profile type and then continue editing with full syntax checking (except for the preprocessor statements) and automatically rerunning the preprocessor at save. Compare the preprocessor generated code with your code side-by-side. Support for running the preprocessor on z/OS will be added in a future release. + +![ ](readme/preprocessor.gif) + +### z/OS Resources table + +An all new feature rich Web view that extends Zowe Explorer with a sortable table. Gain insights into your jobs and data sets by listing, filtering, and sorting on many available properties. + +![ ](readme/zos-resource-table.gif) + +### Advanced Dependency-Based user build error reporting + +User build logs are automatically downloaded, parsed, and presented in the editor's Problems view showing descriptions and error codes. Navigate to errors in your code with a mouse click in the Problems view to review and fix your issue and then rerun your build. diff --git a/product-licenses/rse-api-for-zowe-cli/LICENSE.txt b/product-licenses/rse-api-for-zowe-cli/LICENSE.txt index 26fbc242e..26c3cab83 100644 --- a/product-licenses/rse-api-for-zowe-cli/LICENSE.txt +++ b/product-licenses/rse-api-for-zowe-cli/LICENSE.txt @@ -3,7 +3,7 @@ LICENSE INFORMATION The Programs listed below are licensed under the following License Information terms and conditions in addition to the Program license terms previously agreed to by Client and IBM. If Client does not have previously agreed to license terms in effect for the Program, the International License Agreement for Non-Warranted Programs (i125-5589-06) applies. Program Name (Program Number): -IBM RSE API Plug-in for Zowe CLI V3.3 (Component) +IBM RSE API Plug-in for Zowe CLI V4.0 (Plug-in) The following standard terms apply to Licensee's use of the Program. @@ -12,9 +12,9 @@ Modifiable Third Party Code To the extent, if any, in the NOTICES file IBM identifies third party code as "Modifiable Third Party Code," IBM authorizes Licensee to 1) modify the Modifiable Third Party Code and 2) reverse engineer the Program modules that directly interface with the Modifiable Third Party Code provided that it is only for the purpose of debugging Licensee's modifications to such third party code. IBM's service and support obligations, if any, apply only to the unmodified Program. -L/N: L-HLBW-AHV9GY -D/N: L-HLBW-AHV9GY -P/N: L-HLBW-AHV9GY +L/N: L-JBEK-LHSZWN +D/N: L-JBEK-LHSZWN +P/N: L-JBEK-LHSZWN International License Agreement for Non-Warranted Programs diff --git a/product-licenses/rse-api-for-zowe-cli/NOTICES.txt b/product-licenses/rse-api-for-zowe-cli/NOTICES.txt index 938fbdaf3..55532efb2 100644 --- a/product-licenses/rse-api-for-zowe-cli/NOTICES.txt +++ b/product-licenses/rse-api-for-zowe-cli/NOTICES.txt @@ -1,6 +1,6 @@ NOTICES AND INFORMATION -IBM RSE API Plug-in for Zowe CLI V3.3 +IBM RSE API Plug-in for Zowe CLI V4.0 The IBM license agreement and any applicable information on the web download page for IBM products refers Licensee to this file for details @@ -26,7 +26,7 @@ from the use of this NOTICES file or its contents, including without limitation URLs or references to any third party websites. ===================================================================== -Start of Notices for IBM RSE API Plug-in for Zowe CLI 3.3.x +Start of Notices for IBM RSE API Plug-in for Zowe CLI 4.0.x ===================================================================== ===================================================================== @@ -785,527 +785,14 @@ END OF UNLICENSE NOTICES AND INFORMATION ===================================================================== -End of Notices for IBM RSE API Plug-in for Zowe CLI 3.3.x +End of Notices for IBM RSE API Plug-in for Zowe CLI 4.0.x ===================================================================== -===================================================================== -START OF MIT LICENSE NOTICES AND INFORMATION -===================================================================== - -MIT LICENSE CODE. The Program includes all or portions of the following -software which is available under the MIT License. - -fast-deep-equal 3.x -Copyright 2017 Evgeny Poberezkin - -argparse 1.x -Copyright 2012 "Vitaly Puzrin" (https://github.com/puzrin) - -punycode 2.x -Copyright Mathias Bynens - -json-schema-traverse 1.x -Copyright 2017 Evgeny Poberezkin - -js-yaml 3.x -Copyright 2011-2015 by Vitaly Puzrin - -require-from-string 2.x -Copyright Vsevolod Strukchinsky (github.com/floatdrop) - -lodash 4.x -Copyright OpenJS Foundation and other contributors - -js-yaml 4.x -Copyright 2011-2015 by Vitaly Puzrin - -ajv 7.x -Copyright 2015-2021 Evgeny Poberezkin - -ajv-formats 1.x -Copyright 2020 Evgeny Poberezkin - -yawn-yaml 1.x -Copyright 2015 Mohsen Azimi - - - - -MIT License - -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all -copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. - - -===================================================================== -END OF MIT LICENSE NOTICES AND INFORMATION -===================================================================== - -===================================================================== -START OF PYTHON SOFTWARE FOUNDATION LICENSE NOTICES AND INFORMATION -===================================================================== -The Program includes some or all of the following that IBM obtained under the Python Software Foundation License. - - -argparse 2.x Copyright 2001-2002 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 - - - - - - -A. HISTORY OF THE SOFTWARE -========================== - -Python was created in the early 1990s by Guido van Rossum at Stichting -Mathematisch Centrum (CWI, see http://www.cwi.nl) in the Netherlands -as a successor of a language called ABC. Guido remains Python's -principal author, although it includes many contributions from others. - -In 1995, Guido continued his work on Python at the Corporation for -National Research Initiatives (CNRI, see http://www.cnri.reston.va.us) -in Reston, Virginia where he released several versions of the -software. - -In May 2000, Guido and the Python core development team moved to -BeOpen.com to form the BeOpen PythonLabs team. In October of the same -year, the PythonLabs team moved to Digital Creations (now Zope -Corporation, see http://www.zope.com). In 2001, the Python Software -Foundation (PSF, see http://www.python.org/psf/) was formed, a -non-profit organization created specifically to own Python-related -Intellectual Property. Zope Corporation is a sponsoring member of -the PSF. - -All Python releases are Open Source (see http://www.opensource.org for -the Open Source Definition). Historically, most, but not all, Python -releases have also been GPL-compatible; the table below summarizes -the various releases. - - Release Derived Year Owner GPL- - from compatible? (1) - - 0.9.0 thru 1.2 1991-1995 CWI yes - 1.3 thru 1.5.2 1.2 1995-1999 CNRI yes - 1.6 1.5.2 2000 CNRI no - 2.0 1.6 2000 BeOpen.com no - 1.6.1 1.6 2001 CNRI yes (2) - 2.1 2.0+1.6.1 2001 PSF no - 2.0.1 2.0+1.6.1 2001 PSF yes - 2.1.1 2.1+2.0.1 2001 PSF yes - 2.2 2.1.1 2001 PSF yes - 2.1.2 2.1.1 2002 PSF yes - 2.1.3 2.1.2 2002 PSF yes - 2.2.1 2.2 2002 PSF yes - 2.2.2 2.2.1 2002 PSF yes - 2.2.3 2.2.2 2003 PSF yes - 2.3 2.2.2 2002-2003 PSF yes - 2.3.1 2.3 2002-2003 PSF yes - 2.3.2 2.3.1 2002-2003 PSF yes - 2.3.3 2.3.2 2002-2003 PSF yes - 2.3.4 2.3.3 2004 PSF yes - 2.3.5 2.3.4 2005 PSF yes - 2.4 2.3 2004 PSF yes - 2.4.1 2.4 2005 PSF yes - 2.4.2 2.4.1 2005 PSF yes - 2.4.3 2.4.2 2006 PSF yes - 2.5 2.4 2006 PSF yes - 2.7 2.6 2010 PSF yes - -Footnotes: - -(1) GPL-compatible doesn't mean that we're distributing Python under - the GPL. All Python licenses, unlike the GPL, let you distribute - a modified version without making your changes open source. The - GPL-compatible licenses make it possible to combine Python with - other software that is released under the GPL; the others don't. - -(2) According to Richard Stallman, 1.6.1 is not GPL-compatible, - because its license has a choice of law clause. According to - CNRI, however, Stallman's lawyer has told CNRI's lawyer that 1.6.1 - is "not incompatible" with the GPL. - -Thanks to the many outside volunteers who have worked under Guido's -direction to make these releases possible. - - -B. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON -=============================================================== - -PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 --------------------------------------------- - -1. This LICENSE AGREEMENT is between the Python Software Foundation -("PSF"), and the Individual or Organization ("Licensee") accessing and -otherwise using this software ("Python") in source or binary form and -its associated documentation. - -2. Subject to the terms and conditions of this License Agreement, PSF -hereby grants Licensee a nonexclusive, royalty-free, world-wide -license to reproduce, analyze, test, perform and/or display publicly, -prepare derivative works, distribute, and otherwise use Python -alone or in any derivative version, provided, however, that PSF's -License Agreement and PSF's notice of copyright, i.e., "Copyright (c) -2001, 2002, 2003, 2004, 2005, 2006 Python Software Foundation; All Rights -Reserved" are retained in Python alone or in any derivative version -prepared by Licensee. - -3. In the event Licensee prepares a derivative work that is based on -or incorporates Python or any part thereof, and wants to make -the derivative work available to others as provided herein, then -Licensee hereby agrees to include in any such work a brief summary of -the changes made to Python. - -4. PSF is making Python available to Licensee on an "AS IS" -basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR -IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND -DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS -FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT -INFRINGE ANY THIRD PARTY RIGHTS. - -5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON -FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS -A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON, -OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. - -6. This License Agreement will automatically terminate upon a material -breach of its terms and conditions. - -7. Nothing in this License Agreement shall be deemed to create any -relationship of agency, partnership, or joint venture between PSF and -Licensee. This License Agreement does not grant permission to use PSF -trademarks or trade name in a trademark sense to endorse or promote -products or services of Licensee, or any third party. - -8. By copying, installing or otherwise using Python, Licensee -agrees to be bound by the terms and conditions of this License -Agreement. - - -BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 -------------------------------------------- - -BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1 - -1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an -office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the -Individual or Organization ("Licensee") accessing and otherwise using -this software in source or binary form and its associated -documentation ("the Software"). - -2. Subject to the terms and conditions of this BeOpen Python License -Agreement, BeOpen hereby grants Licensee a non-exclusive, -royalty-free, world-wide license to reproduce, analyze, test, perform -and/or display publicly, prepare derivative works, distribute, and -otherwise use the Software alone or in any derivative version, -provided, however, that the BeOpen Python License is retained in the -Software, alone or in any derivative version prepared by Licensee. - -3. BeOpen is making the Software available to Licensee on an "AS IS" -basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR -IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND -DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS -FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT -INFRINGE ANY THIRD PARTY RIGHTS. - -4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE -SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS -AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY -DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. - -5. This License Agreement will automatically terminate upon a material -breach of its terms and conditions. - -6. This License Agreement shall be governed by and interpreted in all -respects by the law of the State of California, excluding conflict of -law provisions. Nothing in this License Agreement shall be deemed to -create any relationship of agency, partnership, or joint venture -between BeOpen and Licensee. This License Agreement does not grant -permission to use BeOpen trademarks or trade names in a trademark -sense to endorse or promote products or services of Licensee, or any -third party. As an exception, the "BeOpen Python" logos available at -http://www.pythonlabs.com/logos.html may be used according to the -permissions granted on that web page. - -7. By copying, installing or otherwise using the software, Licensee -agrees to be bound by the terms and conditions of this License -Agreement. - - -CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 ---------------------------------------- - -1. This LICENSE AGREEMENT is between the Corporation for National -Research Initiatives, having an office at 1895 Preston White Drive, -Reston, VA 20191 ("CNRI"), and the Individual or Organization -("Licensee") accessing and otherwise using Python 1.6.1 software in -source or binary form and its associated documentation. - -2. Subject to the terms and conditions of this License Agreement, CNRI -hereby grants Licensee a nonexclusive, royalty-free, world-wide -license to reproduce, analyze, test, perform and/or display publicly, -prepare derivative works, distribute, and otherwise use Python 1.6.1 -alone or in any derivative version, provided, however, that CNRI's -License Agreement and CNRI's notice of copyright, i.e., "Copyright (c) -1995-2001 Corporation for National Research Initiatives; All Rights -Reserved" are retained in Python 1.6.1 alone or in any derivative -version prepared by Licensee. Alternately, in lieu of CNRI's License -Agreement, Licensee may substitute the following text (omitting the -quotes): "Python 1.6.1 is made available subject to the terms and -conditions in CNRI's License Agreement. This Agreement together with -Python 1.6.1 may be located on the Internet using the following -unique, persistent identifier (known as a handle): 1895.22/1013. This -Agreement may also be obtained from a proxy server on the Internet -using the following URL: http://hdl.handle.net/1895.22/1013". - -3. In the event Licensee prepares a derivative work that is based on -or incorporates Python 1.6.1 or any part thereof, and wants to make -the derivative work available to others as provided herein, then -Licensee hereby agrees to include in any such work a brief summary of -the changes made to Python 1.6.1. - -4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS" -basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR -IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND -DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS -FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT -INFRINGE ANY THIRD PARTY RIGHTS. - -5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON -1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS -A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, -OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. - -6. This License Agreement will automatically terminate upon a material -breach of its terms and conditions. - -7. This License Agreement shall be governed by the federal -intellectual property law of the United States, including without -limitation the federal copyright law, and, to the extent such -U.S. federal law does not apply, by the law of the Commonwealth of -Virginia, excluding Virginia's conflict of law provisions. -Notwithstanding the foregoing, with regard to derivative works based -on Python 1.6.1 that incorporate non-separable material that was -previously distributed under the GNU General Public License (GPL), the -law of the Commonwealth of Virginia shall govern this License -Agreement only as to issues arising under or with respect to -Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this -License Agreement shall be deemed to create any relationship of -agency, partnership, or joint venture between CNRI and Licensee. This -License Agreement does not grant permission to use CNRI trademarks or -trade name in a trademark sense to endorse or promote products or -services of Licensee, or any third party. - -8. By clicking on the "ACCEPT" button where indicated, or by copying, -installing or otherwise using Python 1.6.1, Licensee agrees to be -bound by the terms and conditions of this License Agreement. - - ACCEPT - - -CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 --------------------------------------------------- - -Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, -The Netherlands. All rights reserved. - -Permission to use, copy, modify, and distribute this software and its -documentation for any purpose and without fee is hereby granted, -provided that the above copyright notice appear in all copies and that -both that copyright notice and this permission notice appear in -supporting documentation, and that the name of Stichting Mathematisch -Centrum or CWI not be used in advertising or publicity pertaining to -distribution of the software without specific, written prior -permission. - -STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO -THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND -FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE -FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES -WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN -ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT -OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. - - -===================================================================== -End OF PYTHON SOFTWARE FOUNDATION LICENSE NOTICES AND INFORMATION -===================================================================== - - - -===================================================================== -START OF BSD-2-CLAUSE LICENSE NOTICES AND INFORMATION -===================================================================== - -BSD-2-Clause - -The Program includes some or all of the following that IBM obtained under the BSD-2-Clause License: - -esprima 4.x Copyright JS Foundation and other contributors, https://js.foundation/ -uri-js 4.x Copyright 2011 Gary Court - - - - - - -BSD-2-CLAUSE LICENSE - - -Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: -1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. -2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. -THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - - -===================================================================== -END OF BSD-2-CLAUSE LICENSE NOTICES AND INFORMATION -===================================================================== - -===================================================================== -START OF BSD-3-CLAUSE LICENSE NOTICES AND INFORMATION -===================================================================== - -BSD-3-Clause License - -The Program includes some or all of the following that IBM obtained -under the BSD-3-Clause License: - - -sprintf-js -Copyright (c) 2007-2014, Alexandru Marasteanu (hello [at) alexei (dot] ro) - - - -BSD-3-CLAUSE LICENSE - -All rights reserved. - -Redistribution and use in source and binary forms, with or without modification, is permitted -provided that the following conditions are met: - - Redistributions of source code must retain the above copyright notice, this list of - conditions and the following disclaimer. - - Redistributions in binary form must reproduce the above copyright notice, this list of - conditions and the following disclaimer in the documentation and/or other materials - provided with the distribution. - - Neither the name of the nor the names of its contributors may be used - to endorse or promote products derived from this software without specific prior written - permission. - -THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS -OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY -AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR -CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL -DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, -DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, -WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN -ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - - -===================================================================== -END OF BSD-3-CLAUSE LICENSE NOTICES AND INFORMATION -===================================================================== - - -===================================================================== -START OF WTFPL LICENSE NOTICES AND INFORMATION -===================================================================== - -WTFPL LICENSE - -The Program includes some or all of the following that IBM obtained -under the WTFPL License: - -yaml-js -Copyright (C) 2004 Sam Hocevar - - - - - - -WTFPL LICENSE - -DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE -Version 2, December 2004 - -Copyright (C) 2004 Sam Hocevar - -Everyone is permitted to copy and distribute verbatim or modified copies of this -license document, and changing it is allowed as long as the name is changed. - -DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE -TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION - - 0. You just DO WHAT THE FUCK YOU WANT TO. - -Standard License Header - -There is no standard license header for the license - -===================================================================== -END OF WTFPL LICENSE NOTICES AND INFORMATION -===================================================================== -===================================================================== -START OF UNLICENSE NOTICES AND INFORMATION -===================================================================== - -The Program includes some or all of the following that IBM obtained under the Public Domain Equivalent License, Unlicense: - - - - - -This is free and unencumbered software released into the public domain. - -Anyone is free to copy, modify, publish, use, compile, sell, or -distribute this software, either in source code form or as a compiled -binary, for any purpose, commercial or non-commercial, and by any -means. - -In jurisdictions that recognize copyright laws, the author or authors -of this software dedicate any and all copyright interest in the -software to the public domain. We make this dedication for the benefit -of the public at large and to the detriment of our heirs and -successors. We intend this dedication to be an overt act of -relinquishment in perpetuity of all present and future rights to this -software under copyright law. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, -EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF -MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. -IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR -OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, -ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR -OTHER DEALINGS IN THE SOFTWARE. - -For more information, please refer to - -===================================================================== -END OF UNLICENSE NOTICES AND INFORMATION -===================================================================== -L/N: L-HLBW-AHV9GY -D/N: L-HLBW-AHV9GY -P/N: L-HLBW-AHV9GY +L/N: L-JBEK-LHSZWN +D/N: L-JBEK-LHSZWN +P/N: L-JBEK-LHSZWN diff --git a/product-licenses/zapp/LICENSE.txt b/product-licenses/zapp/LICENSE.txt index a172ec0a8..54fe1df01 100644 --- a/product-licenses/zapp/LICENSE.txt +++ b/product-licenses/zapp/LICENSE.txt @@ -3,7 +3,7 @@ LICENSE INFORMATION The Programs listed below are licensed under the following License Information terms and conditions in addition to the Program license terms previously agreed to by Client and IBM. If Client does not have previously agreed to license terms in effect for the Program, the International License Agreement for Non-Warranted Programs (i125-5589-06) applies. Program Name (Program Number): -IBM Zapp Core Library V1.0 (Plug-in) +IBM Zapp Core Library V1.1 (Plug-in) The following standard terms apply to Licensee's use of the Program. @@ -12,9 +12,9 @@ Modifiable Third Party Code To the extent, if any, in the NOTICES file IBM identifies third party code as "Modifiable Third Party Code," IBM authorizes Licensee to 1) modify the Modifiable Third Party Code and 2) reverse engineer the Program modules that directly interface with the Modifiable Third Party Code provided that it is only for the purpose of debugging Licensee's modifications to such third party code. IBM's service and support obligations, if any, apply only to the unmodified Program. -L/N: L-YVXN-CTM9H3 -D/N: L-YVXN-CTM9H3 -P/N: L-YVXN-CTM9H3 +L/N: L-KTSR-8RJLXL +D/N: L-KTSR-8RJLXL +P/N: L-KTSR-8RJLXL International License Agreement for Non-Warranted Programs @@ -148,7 +148,7 @@ In Mexico: In the third sentence, delete the words "to an account specified by I In Mexico: Add the following new sentence after the third sentence: -Payments will be made through electronic transfer of funds to an account specified by IBM or in IBM's domicile which is located in Alfonso Napoles Gandara 3111, Santa Fe Pe�a Blanca, Alvaro Obregon, Mexico City, Zip Code 01210. +Payments will be made through electronic transfer of funds to an account specified by IBM or in IBM´s domicile which is located in Alfonso Napoles Gandara 3111, Santa Fe Peña Blanca, Alvaro Obregon, Mexico City, Zip Code 01210. Add at the end of paragraph c the following sentence: @@ -168,7 +168,7 @@ Section 6. Governing Laws and Geographic Scope In paragraph a, replace the first sentence only with: -In Argentina: Both parties agree to the application of the laws of the Republic of Argentina, without regard to the conflict of law principles. Any proceeding regarding the rights, duties, and obligations arising from this Agreement will be brought in the Ordinary Commercial Court of the City of "Ciudad Aut�noma de Buenos Aires". +In Argentina: Both parties agree to the application of the laws of the Republic of Argentina, without regard to the conflict of law principles. Any proceeding regarding the rights, duties, and obligations arising from this Agreement will be brought in the Ordinary Commercial Court of the City of "Ciudad Autónoma de Buenos Aires". In Chile: Both parties agree to the application of the laws of Chile, without regard to the conflict of law principles. Any conflict, interpretation or breach related to this Agreement that cannot be solved by the Parties should be remitted to the jurisdiction of the Ordinary Courts of the city and district of Santiago. @@ -208,7 +208,7 @@ In Venezuela: Venezuela Add the following sentences at the end of paragraph b: -In Brazil: All disputes arising out of or related to this Agreement, including summary proceedings, will be brought before and subject to the exclusive jurisdiction of the Forum of the City of S�o Paulo, State of S�o Paulo, Brazil and the parties irrevocably agree with this specific jurisdiction renouncing any other, however privileged it may be. +In Brazil: All disputes arising out of or related to this Agreement, including summary proceedings, will be brought before and subject to the exclusive jurisdiction of the Forum of the City of São Paulo, State of São Paulo, Brazil and the parties irrevocably agree with this specific jurisdiction renouncing any other, however privileged it may be. In Mexico: The Parties agree to submit themselves to the exclusive jurisdiction of the courts of Mexico City to resolve any dispute arising from this Agreement. The Parties waive to any other jurisdiction that may correspond to them due to their current or future domiciles, or for any other reason. @@ -228,7 +228,7 @@ In Brazil: delete the entire 2nd sentence of "Neither party will bring a legal a Add as a new paragraph l to this section: -In Canada: Both parties agree to write this document in English. Les parties ont convenu de r�diger le pr�sent document en langue anglaise. +In Canada: Both parties agree to write this document in English. Les parties ont convenu de rédiger le présent document en langue anglaise. 2. ASIA PACIFIC @@ -358,7 +358,7 @@ Section 4. Liability and Intellectual Property Protection In paragraph a, in the first sentence insert the following before the words "the amounts paid": -In Belgium, France, Germany, Italy, Luxembourg, Malta, Portugal, and Spain: the greater of �500,000 (five hundred thousand euro) or +In Belgium, France, Germany, Italy, Luxembourg, Malta, Portugal, and Spain: the greater of €500,000 (five hundred thousand euro) or In Ireland and United Kingdom: 125% of @@ -368,7 +368,7 @@ In Spain: and proven damages incurred by Licensee as a direct consequence of the In paragraph a, insert after the first sentence the following new sentence: -In Slovakia: Referring to � 379 of the Commercial Code, Act No. 513/1991 Coll. as amended, and concerning all conditions related to the conclusion of the agreement, both parties state that the total foreseeable damage, which may accrue, shall not exceed the amount above, and it is the maximum for which IBM is responsible. +In Slovakia: Referring to § 379 of the Commercial Code, Act No. 513/1991 Coll. as amended, and concerning all conditions related to the conclusion of the agreement, both parties state that the total foreseeable damage, which may accrue, shall not exceed the amount above, and it is the maximum for which IBM is responsible. In paragraph a, insert before the second sentence the following new sentence: diff --git a/product-licenses/zapp/NOTICES.txt b/product-licenses/zapp/NOTICES.txt index 67b66c0fa..02bc9ae38 100644 --- a/product-licenses/zapp/NOTICES.txt +++ b/product-licenses/zapp/NOTICES.txt @@ -1,6 +1,6 @@ NOTICES AND INFORMATION -IBM Zapp Core Library V1.0 +IBM Zapp Core Library V1.1 The IBM license agreement and any applicable information on the web download page for IBM products refers Licensee to this file for details @@ -25,7 +25,7 @@ and all liability for errors and omissions or for any damages accruing from the use of this NOTICES file or its contents, including without limitation URLs or references to any third party websites. -Start of Notices for IBM Zapp Core Library 1.0.0 +Start of Notices for IBM Zapp Core Library 1.1.0 ===================================================================== ===================================================================== @@ -95,14 +95,37 @@ SOFTWARE. ===================================================================== END OF MIT LICENSE NOTICES AND INFORMATION ===================================================================== +START OF APACHE 2.0SOFTWARE FOUNDATION LICENSE NOTICES AND INFORMATION +====================================================================== +APACHE SOFTWARE LICENSE 2.0. +The Program includes some or all of the following that IBM obtained +under the Apache License Version 2.0: + +sr305 +listenablefuture +opentest4j +snakeyaml +asm-analysys +asm-commons +asm-tree +Apiguardian-api +jackson-bom + +This software may also consist of voluntary contributions made by many +individuals to the Apache Software Foundation. Some or all of the following +software may be components of other included software packages noted later +in this file. For more information on the Apache Software Foundation, please +see http://www.apache.org. +===================================================================== +START OF APACHE 2.0 SOFTWARE FOUNDATION LICENSE NOTICES AND INFORMATION ===================================================================== START OF PYTHON SOFTWARE FOUNDATION LICENSE NOTICES AND INFORMATION ===================================================================== The Program includes some or all of the following that IBM obtained under the Python Software Foundation License. -argparse 2.x +agparse 1.x @@ -462,6 +485,104 @@ ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF S ===================================================================== END OF BSD-3-CLAUSE LICENSE NOTICES AND INFORMATION ===================================================================== +START OF ECLIPSE V2 LICENSE NOTICES AND INFORMATION +===================================================================== +The Program includes some or all of the following that IBM obtained under the Eclipse Public License - v 2.0 Clause: + +The Program contains open source software obtained from the Eclipse Foundation (herein collectively referred to as "Eclipse Code"). Notices and important information, including instructions for obtaining source code, for the Eclipse Code may be found in associated "about.html" files ("About Files") that accompany the Eclipse Code. These About Files are provided for informational purposes only, and notwithstanding anything to the contrary therein, your use of such Eclipse Code shall be governed by the terms of the IBM end user license agreement. + +junit-bom +junit-jupiter +junit-jupiter-api +junit-jupiter-engine +junit-jupiter-params +junit-jupiter-platform-commmons +Junit-platform-enngine +clipse Public License - v 2.0 + +THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT. + + 1. DEFINITIONS + + "Contribution" means: + a) in the case of the initial Contributor, the initial content Distributed under this Agreement, and + b) in the case of each subsequent Contributor: + i) changes to the Program, and + ii) additions to the Program; + + where such changes and/or additions to the Program originate from and are Distributed by that particular Contributor. A Contribution "originates" from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf. Contributions do not include changes or additions to the Program that are not Modified Works. + + "Contributor" means any person or entity that Distributes the Program. + + "Licensed Patents" mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program. + + "Program" means the Contributions Distributed in accordance with this Agreement. + + "Recipient" means anyone who receives the Program under this Agreement or any Secondary License (as applicable), including Contributors. + + "Derivative Works" shall mean any work, whether in Source Code or other form, that is based on (or derived from) the Program and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. + + "Modified Works" shall mean any work in Source Code or other form that results from an addition to, deletion from, or modification of the contents of the Program, including, for purposes of clarity any new file in Source Code form that contains any contents of the Program. Modified Works shall not include works that contain only declarations, interfaces, types, classes, structures, or files of the Program solely in each case in order to link to, bind by name, or subclass the Program or Modified Works thereof. + + "Distribute" means the acts of a) distributing or b) making available in any manner that enables the transfer of a copy. + + "Source Code" means the form of a Program preferred for making modifications, including but not limited to software source code, documentation source, and configuration files. + + "Secondary License" means either the GNU General Public License, Version 2.0, or any later versions of that license, including any exceptions or additional permissions as identified by the initial Contributor. + 2. GRANT OF RIGHTS + a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, Distribute and sublicense the Contribution of such Contributor, if any, and such Derivative Works. + b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import and otherwise transfer the Contribution of such Contributor, if any, in Source Code or other form. This patent license shall apply to the combination of the Contribution and the Program if, at the time the Contribution is added by the Contributor, such addition of the Contribution causes such combination to be covered by the Licensed Patents. The patent license shall not apply to any other combinations which include the Contribution. No hardware per se is licensed hereunder. + c) Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein, no assurances are provided by any Contributor that the Program does not infringe the patent or other intellectual property rights of any other entity. Each Contributor disclaims any liability to Recipient for claims brought by any other entity based on infringement of intellectual property rights or otherwise. As a condition to exercising the rights and licenses granted hereunder, each Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed, if any. For example, if a third party patent license is required to allow Recipient to Distribute the Program, it is Recipient's responsibility to acquire that license before distributing the Program. + d) Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement. + e) Notwithstanding the terms of any Secondary License, no Contributor makes additional grants to any Recipient (other than those set forth in this Agreement) as a result of such Recipient's receipt of the Program under the terms of a Secondary License (if permitted under the terms of Section 3). + 3. REQUIREMENTS + 3.1 If a Contributor Distributes the Program in any form, then: + a) the Program must also be made available as Source Code, in accordance with section 3.2, and the Contributor must accompany the Program with a statement that the Source Code for the Program is available under this Agreement, and informs Recipients how to obtain it in a reasonable manner on or through a medium customarily used for software exchange; and + b) the Contributor may Distribute the Program under a license different than this Agreement, provided that such license: + i) effectively disclaims on behalf of all other Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose; + ii) effectively excludes on behalf of all other Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits; + iii) does not attempt to limit or alter the recipients' rights in the Source Code under section 3.2; and + iv) requires any subsequent distribution of the Program by any party to be under a license that satisfies the requirements of this section 3. + 3.2 When the Program is Distributed as Source Code: + a) it must be made available under this Agreement, or if the Program (i) is combined with other material in a separate file or files made available under a Secondary License, and (ii) the initial Contributor attached to the Source Code the notice described in Exhibit A of this Agreement, then the Program may be made available under the terms of such Secondary Licenses, and + b) a copy of this Agreement must be included with each copy of the Program. + 3.3 Contributors may not remove or alter any copyright, patent, trademark, attribution notices, disclaimers of warranty, or limitations of liability ("notices") contained within the Program from any copy of the Program which they Distribute, provided that Contributors may add their own appropriate notices. + 4. COMMERCIAL DISTRIBUTION + + Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense. + + For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages. + 5. NO WARRANTY + + EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, AND TO THE EXTENT PERMITTED BY APPLICABLE LAW, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations. + 6. DISCLAIMER OF LIABILITY + + EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, AND TO THE EXTENT PERMITTED BY APPLICABLE LAW, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. + 7. GENERAL + + If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable. + + If Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b) shall terminate as of the date such litigation is filed. + + All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable. However, Recipient's obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive. + + Everyone is permitted to copy and distribute copies of this Agreement, but in order to avoid inconsistency the Agreement is copyrighted and may only be modified in the following manner. The Agreement Steward reserves the right to publish new versions (including revisions) of this Agreement from time to time. No one other than the Agreement Steward has the right to modify this Agreement. The Eclipse Foundation is the initial Agreement Steward. The Eclipse Foundation may assign the responsibility to serve as the Agreement Steward to a suitable separate entity. Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be Distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to Distribute the Program (including its Contributions) under the new version. + + Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, by implication, estoppel or otherwise. All rights in the Program not expressly granted under this Agreement are reserved. Nothing in this Agreement is intended to be enforceable by any entity that is not a Contributor or Recipient. No third-party beneficiary rights are created under this Agreement. + Exhibit A - Form of Secondary Licenses Notice + + "This Source Code may also be made available under the following Secondary Licenses when the conditions for such availability set forth in the Eclipse Public License, v. 2.0 are satisfied: {name license(s), version(s), and exceptions or additional permissions here}." + + Simply including a copy of this Agreement, including this Exhibit A is not sufficient to license the Source Code under Secondary Licenses. + + If it is not possible or desirable to put the notice in a particular file, then You may include the notice in a location (such as a LICENSE file in a relevant directory) where a recipient would be likely to look for such a notice. + + You may add additional accurate notices of copyright ownership. + +===================================================================== +END OF ECLIPSE PUBLIC LICENSE V2 LICENSE NOTICES AND INFORMATION +===================================================================== + ===================================================================== @@ -542,9 +663,9 @@ For more information, please refer to END OF UNLICENSE NOTICES AND INFORMATION ===================================================================== -End of Notices for IBM Zapp Core Library 1.0.0 +End of Notices for IBM Zapp Core Library 1.1.0 -L/N: L-YVXN-CTM9H3 -D/N: L-YVXN-CTM9H3 -P/N: L-YVXN-CTM9H3 +L/N: L-KTSR-8RJLXL +D/N: L-KTSR-8RJLXL +P/N: L-KTSR-8RJLXL diff --git a/zapp/zapp-schema-1.1.0.json b/zapp/zapp-schema-1.1.0.json new file mode 100644 index 000000000..e4d3c6a03 --- /dev/null +++ b/zapp/zapp-schema-1.1.0.json @@ -0,0 +1,433 @@ +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "title": "IBM Zapp Document", + "description": "JSON schema for zapp.json and zapp.yaml files. Version 1.1.0 -- Licensed Materials - Property of IBM - (c) Copyright IBM Corporation 2022, 2024. All Rights Reserved.", + "type": "object", + "definitions": { + "coreProperties": { + "type": "object", + "required": ["name"], + "additionalProperties": false, + "properties": { + "name": { + "description": "The name of the Z Project.", + "type": "string", + "maxLength": 214, + "minLength": 1 + }, + "description": { + "description": "This helps people understand your project as it would be used by tools.", + "type": "string" + }, + "version": { + "description": "Version is a string and it must be parsable for managing dependencies.", + "type": "string", + "default": "1.0.0" + }, + "groupId": { + "description": "Defines a group name that is shared for each application part in case of applications composed of multiple parts. Allows to uniquely identify the parts by concatenating with the artifact id. For example a groupId `com.ibm.wazi` with an artifactId `service` would create the unique application identifier `com.ibm.wazi.service`.", + "type": "string", + "examples": ["com.ibm.wazi", "payments"] + }, + "artifactId": { + "description": "Define id of the application artifact. Use it in combination with a groupId for multi-part applications.", + "type": "string", + "default": "", + "examples": ["sam"] + }, + "parentId": { + "description": "In case of a multi-part application defines the name of the parent application part. This zapp will inherit properties such as propertyGroups defined in the parent.", + "type": "string", + "default": "", + "examples": ["com.ibm.wazi.parent"] + }, + "keywords": { + "description": "This helps people discover your project.", + "type": "array", + "items": { + "type": "string" + } + }, + "homepage": { + "description": "The url to the project homepage.", + "type": "string", + "oneOf": [ + { + "format": "uri" + }, + { + "enum": ["."] + } + ] + }, + "license": { + "type": "string", + "description": "You should specify a license for your package so that people know how they are permitted to use it and any restrictions you're placing on it." + }, + "author": { + "$ref": "#/definitions/person" + }, + "contributors": { + "description": "A list of people who contributed to this package.", + "type": "array", + "items": { + "$ref": "#/definitions/person" + }, + "minItems": 1 + }, + "maintainers": { + "description": "A list of people who maintain this package.", + "type": "array", + "items": { + "$ref": "#/definitions/person" + }, + "minItems": 1 + }, + "propertyGroups": { + "description": "A list of properties defining path names for resolving dependencies.", + "type": "array", + "items": { + "$ref": "#/definitions/propertyGroupItem" + }, + "minItems": 1 + }, + "profiles": { + "description": "Profiles are additional groups of properties that should only should become valid under specific conditions such as running in a build job or as part of a debug session.", + "type": "array", + "items": { + "$ref": "#/definitions/profile" + }, + "minItems": 1 + } + } + }, + "propertyGroupItem": { + "type": "object", + "additionalProperties": false, + "required": ["name"], + "properties": { + "name": { + "type": "string", + "description": "The name of the property group, which is used in hovers and error messages.", + "examples": ["sample-local", "sample-remote"] + }, + "language": { + "type": "string", + "enum": ["cobol", "pl1", "hlasm", "rexx", "jcl"], + "description": "Limits the property group to one specific language." + }, + "compilerOptions": { + "type": "string", + "description": "Global compiler options separated by a comma that impact the parsing of the programs for the editor. Requires that you specify a language. If there are multiple Property Groups for a language with compiler option then they will be concatenated." + }, + "libraries": { + "type": "array", + "description": "An array of potential library locations defining the search order for include files. Libraries with the name 'syslib' will be handled as default include locations. The list can contain many entries of the type 'local' or 'mvs'. It can contain items of the same type twice in case, for example, you want to search in remote locations first, then some local location, and if still not found more remote locations.", + "items": { + "$ref": "#/definitions/libraryItem" + }, + "minItems": 1 + } + } + }, + "libraryItem": { + "type": "object", + "additionalProperties": false, + "required": ["name", "type", "locations"], + "properties": { + "name": { + "type": "string", + "description": "Name of the library. The default name should be `syslib` if using unnamed libraries.", + "default": "syslib", + "examples": ["syslib", "currencylib"] + }, + "type": { + "type": "string", + "enum": ["mvs", "local"], + "description": "The type of the property group defining where dependencies should be located. Allowed values are 'local' for using a local workspace and 'mvs' for dependencies located in MVS Datasets.", + "default": "local", + "examples": ["local", "mvs"] + }, + "locations": { + "type": "array", + "description": "An array of include file locations. For 'local' libraries values can be absolute and relative filename paths using GLOB patterns. For 'mvs' libraries value can be data set names. GLOB patterns for data sets are currently not supported.", + "items": { + "type": "string" + }, + "minItems": 1, + "examples": ["**/copybook", "USER1.SAMPLE.COBCOPY"] + } + } + }, + "person": { + "description": "A person who has been involved in creating or maintaining this package", + "type": ["object", "string"], + "required": ["name"], + "properties": { + "name": { + "type": "string" + }, + "url": { + "type": "string", + "format": "uri" + }, + "email": { + "type": "string", + "format": "email" + } + } + }, + "profile": { + "type": "object", + "description": "Profiles are additional groups of properties that should only should become valid under specific conditions such as running in a build job or as part of a debug session.", + "additionalProperties": false, + "required": ["name", "type"], + "properties": { + "name": { + "type": "string", + "description": "The name of the profile.", + "examples": ["dbb-build"] + }, + "type": { + "type": "string", + "enum": ["dbb", "rseapi", "debug", "preprocessor"], + "description": "The type of the profile.", + "default": "dbb", + "examples": ["dbb", "rseapi", "preprocessor"] + }, + "location": { + "type": "string", + "enum": ["mvs", "local"], + "description": "A string of include file locations. For 'local' libraries values can be absolute and relative filename paths using GLOB patterns. For 'mvs' libraries value can be data set names. GLOB patterns for dat sets are currently not supported.", + "examples": ["**/copybook", "USER1.SAMPLE.COBCOPY"] + }, + "settings": { + "description": "Settings objects specific to the type specified for the profile.", + "type": "object" + } + }, + "anyOf": [ + { + "required": ["name", "type", "settings"], + "additionalProperties": false, + "properties": { + "name": { "type": "string" }, + "type": { "const": "dbb", "type": "string" }, + "settings": { + "$ref": "#/definitions/dbbSettingsItem" + } + } + }, + { + "required": ["name", "type", "settings"], + "additionalProperties": false, + "properties": { + "name": { "type": "string" }, + "type": { "const": "rseapi", "type": "string" }, + "settings": { + "$ref": "#/definitions/rseapiSettingsItem" + } + } + }, + { + "required": ["name", "type", "settings", "location"], + "additionalProperties": false, + "properties": { + "name": { "type": "string" }, + "type": { "const": "preprocessor", "type": "string" }, + "location": { "const": "local", "type": "string" }, + "settings": { + "$ref": "#/definitions/localPreprocessorSettingsItem" + } + } + }, + { + "required": ["name", "type", "settings", "location"], + "additionalProperties": false, + "properties": { + "name": { "type": "string" }, + "type": { "const": "preprocessor", "type": "string" }, + "location": { "const": "mvs", "type": "string" }, + "settings": { + "$ref": "#/definitions/mvsPreprocessorSettingsItem" + } + } + } + ] + }, + "dbbSettingsItem": { + "type": "object", + "additionalProperties": false, + "required": ["application", "command"], + "description": "DBB build script properties for running User Build on remote host.", + "properties": { + "application": { + "type": "string", + "description": "Defines the name of the application to build. Will be used to create a folder on USS to upload all files to." + }, + "command": { + "type": "string", + "description": "Command that the build script is executed with such as the path to groovyz and it's parameters." + }, + "buildScriptPath": { + "type": "string", + "description": "The full path of build script on the remote host that should be used with the command." + }, + "buildScriptArgs": { + "type": "array", + "items": { + "type": "string" + }, + "description": "A list of strings that are the parameters for the build script. Check the documentation for built-in variables, such as the name of the program to build, that can be used here." + }, + "additionalDependencies": { + "type": "array", + "items": { + "type": "string" + }, + "description": "Lists of GLOB patterns that define the files that should be uploaded to USS for a build. Relative path names are interpreted relative to the location of the ZAPP file that is being used for the build, which is a ZAPP file in the same workspace as the program to be build." + }, + "logFilePatterns": { + "type": "array", + "items": { + "type": "string" + }, + "description": "Lists of GLOB patterns that define the files that should be downloaded from USS after the build. Relative path names are interpreted relative to the DBB log directory user setting. If not provided then all files of the user setting location will be downloaded." + } + } + }, + "rseapiSettingsItem": { + "type": "object", + "additionalProperties": false, + "description": "RSE API client settings for interactions with a z/OS remote host running an RSE API server.", + "required": ["mappings", "default.encoding"], + "properties": { + "mappings": { + "type": "array", + "description": "A list of mapping objects that map local file extensions to transfer modes and encodings to MVS datasets that can be specified using wildcards.", + "items": { "$ref": "#/definitions/rseapiSettingsItemMapping" } + }, + "default.encoding": { + "type": "string", + "description": "The encoding to be used when no mapping can be found. If not provided then either the user or server default will be used." + } + } + }, + "rseapiSettingsItemMapping": { + "type": "object", + "additionalProperties": false, + "description": "One mapping that contains at least transfer and resource values.", + "properties": { + "extension": { + "type": "string", + "description": "A local file extension such as cbl or pl1." + }, + "transfer": { + "type": "string", + "enum": ["text", "binary"], + "description": "The transfer mode to be used. Can be 'text' or 'binary'." + }, + "resource": { + "type": "string", + "description": "The data set name to be mapped to. Can use a wildcard such as '**CPY'." + }, + "encoding": { + "type": "string", + "description": "The encoding to be used for text transfer. See the RSE API documentation for the values allowed." + }, + "memberMappings": { + "type": "array", + "items": { + "type": "object", + "additionalProperties": false, + "description": "One member mapping that contains at least transfer and resource values.", + "properties": { + "extension": { + "type": "string", + "description": "A local file extension such as cbl or pl1." + }, + "transfer": { + "type": "string", + "enum": ["text", "binary"], + "description": "The transfer mode to be used. Can be 'text' or 'binary'." + }, + "encoding": { + "type": "string", + "description": "The encoding to be used for text transfer. See the RSE API documentation for the values allowed." + }, + "resource": { + "type": "string", + "description": "The data set member name to be mapped to. Can use a wildcard such as '**CPY'." + } + } + }, + "description": "A nested mappings array with resource mappings to members of the data sets that were mapped by the parent mapping." + } + } + }, + "localPreprocessorSettingsItem": { + "type": "object", + "additionalProperties": false, + "description": "Preprocessor properties for preprocessing COBOL/PL/I files.", + "required": ["command", "outputPath", "fileExtension"], + "properties": { + "command": { + "type": "string", + "description": "The command to run to execute the preprocessor executable." + }, + "outputPath": { + "type": "string", + "description": "Path where preprocessor produces its build output." + }, + "fileExtension": { + "type": "string", + "description": "The desired file extension for the post-processed file." + }, + "environmentVariables": { + "type": "object", + "additionalProperties": false, + "description": "Specifies any user defined environment variables to be passed to the preprocessor.", + "patternProperties": { + "[a-zA-Z_][a-zA-Z0-9_]*": { + "anyOf": [{ "type": "string" }] + } + } + } + } + }, + "mvsPreprocessorSettingsItem": { + "type": "object", + "additionalProperties": false, + "description": "Preprocessor properties for preprocessing COBOL/PL/I files.", + "required": [ + "commandDataSet", + "commandParameters", + "outputDataSet", + "tempDataHLQ" + ], + "properties": { + "commandDataSet": { + "type": "string", + "description": "Specifies an input listing sequential data set." + }, + "commandParameters": { + "type": "string", + "description": "The parameters for the command being run." + }, + "outputDataSet": { + "type": "string", + "description": "Specifies an output listing sequential data set." + }, + "tempDataHLQ": { + "type": "string", + "description": "Specifies the high-level qualifier used for data sets created by plug-in requests to export observation files." + } + } + } + }, + "anyOf": [ + { + "$ref": "#/definitions/coreProperties" + } + ] +}