diff --git a/404.html b/404.html index 6aeb32858..d45ec8bb7 100644 --- a/404.html +++ b/404.html @@ -41,11 +41,11 @@ } )(); IBM Z® Open Editor - + -

404

That's a Four-Oh-Four.
Take me home
- +

404

Looks like we've got some broken links.
Take me home
+ diff --git a/Blog/announcing-jcl.html b/Blog/announcing-jcl.html index 4c1a3de3a..8966ac729 100644 --- a/Blog/announcing-jcl.html +++ b/Blog/announcing-jcl.html @@ -41,11 +41,11 @@ } )(); A Modern JCL (Job Control Language) Editor | IBM Z® Open Editor - + -
IBM Z® Open Editor

A Modern JCL (Job Control Language) Editor

by Prasang Prajapati
18 June 2024

In the ongoing effort to bring z/OS® application development into the rich ecosystem of modern code editors, the JCL (Job Control Language) programming language is the next major addition. Enabled in IBM Z® Open Editor 4.3.0 and IBM® Wazi Developer 4.3.0open in new window, you will be able to benefit from our Language Server Protocol (LSP)open in new window implementation for JCL. This brings a plethora of language features to the editor, which make JCL development easier and more accessible.

There are several language features now available to augment the JCL editing experience.

Syntax highlighting

Arguably the most important of the bunch, the colorization of code is hard to go without these days. It's quite surprising how far a little color variance can go to make distinguishing symbols easier. Bringing visual clarity to the syntactically wild JCL programming language, this feature undeniably improves the speed and precision of development.

JCL syntax highlighting

Syntax errors

Out of the many mainframe programming languages, JCL is truly the free spirit. Job control language (JCL) is used to tell the system what program to execute, followed by a description of program inputs and outputs. Basic JCL contains three types of statements: JOB, EXEC, and DD. A job can contain several EXEC statements (steps) and each step might have several DD statements. JCL provides a wide range of parameters and controls, but you will find that you use only a subset most of the time. Making a small typing mistake in adding mentioned JCL statements can lead to a major failure in submitting a JOB about which z/OS resources will be needed to process a batch job pr to start a system task. Syntax errors in an editor can help users identify mistakes that have been made in the program easily.

JCL syntax errors

Code completion

Writing code can be a tedious process, and one that requires incredible memory and focus. Some of the simplest mistakes are misspelled statements, and given that JCL does not require JOB statement before steps (EXEC statement), these spelling errors can go completely unnoticed until some strange runtime errors occur. To alleviate this problem, you can utilize code completion to see INCLUDE statement, JCL Library statement, JOB statement, PROC statements and much more as you type. This incredibly powerful feature gives you the confidence to know that the symbol you type is the right one.

JCL code completion

Outline view

A highly underrated feature, the outline view provides an overview of a program. We did the research, studying real JCL developers, to find out how to make this feature actually useful. What we found, it can be a powerful navigation tool for quickly going a step (an EXEC statement). Instead of crowding the outline view with every EXEC statement to find a DD statement that is inside a step, it was significantly more useful when users could glance over and see what EXEC and DD statements were defined in a JOB, and if they wanted, navigate there with one click.

JCL Outline

Commenting and uncommenting JCL code

You can comment out one or multiple selected lines of code or a selected section of code by using the toggle comment function.

How to use it

To toggle comment for one or multiple selected lines of code, press Cmd+/ (Mac) or Ctrl+/ (Windows), or go to Edit > Toggle Line Comment.

To toggle comments for a selected section of code, press Option+Shift+A (Mac) or Alt+Shift+A (Windows), or go to Edit > Toggle Block Comment.

See the following example where we first toggle line comment on a single line, then toggle line comment on multiple selected lines, and finally toggle block comment on a selection:

jcl toggle comment

More information

For information about how to utilize the different language features, see Making JCL code changes.

Last Updated:
Contributors: Prasang Prajapati
- +
IBM Z® Open Editor

A Modern JCL (Job Control Language) Editor

by Prasang Prajapati
18 June 2024

In the ongoing effort to bring z/OS® application development into the rich ecosystem of modern code editors, the JCL (Job Control Language) programming language is the next major addition. Enabled in IBM Z® Open Editor 4.3.0 and IBM® Wazi Developer 4.3.0open in new window, you will be able to benefit from our Language Server Protocol (LSP)open in new window implementation for JCL. This brings a plethora of language features to the editor, which make JCL development easier and more accessible.

There are several language features now available to augment the JCL editing experience.

Syntax highlighting

Arguably the most important of the bunch, the colorization of code is hard to go without these days. It's quite surprising how far a little color variance can go to make distinguishing symbols easier. Bringing visual clarity to the syntactically wild JCL programming language, this feature undeniably improves the speed and precision of development.

JCL syntax highlighting

Syntax errors

Out of the many mainframe programming languages, JCL is truly the free spirit. Job control language (JCL) is used to tell the system what program to execute, followed by a description of program inputs and outputs. Basic JCL contains three types of statements: JOB, EXEC, and DD. A job can contain several EXEC statements (steps) and each step might have several DD statements. JCL provides a wide range of parameters and controls, but you will find that you use only a subset most of the time. Making a small typing mistake in adding mentioned JCL statements can lead to a major failure in submitting a JOB about which z/OS resources will be needed to process a batch job pr to start a system task. Syntax errors in an editor can help users identify mistakes that have been made in the program easily.

JCL syntax errors

Code completion

Writing code can be a tedious process, and one that requires incredible memory and focus. Some of the simplest mistakes are misspelled statements, and given that JCL does not require JOB statement before steps (EXEC statement), these spelling errors can go completely unnoticed until some strange runtime errors occur. To alleviate this problem, you can utilize code completion to see INCLUDE statement, JCL Library statement, JOB statement, PROC statements and much more as you type. This incredibly powerful feature gives you the confidence to know that the symbol you type is the right one.

JCL code completion

Outline view

A highly underrated feature, the outline view provides an overview of a program. We did the research, studying real JCL developers, to find out how to make this feature actually useful. What we found, it can be a powerful navigation tool for quickly going a step (an EXEC statement). Instead of crowding the outline view with every EXEC statement to find a DD statement that is inside a step, it was significantly more useful when users could glance over and see what EXEC and DD statements were defined in a JOB, and if they wanted, navigate there with one click.

JCL Outline

Commenting and uncommenting JCL code

You can comment out one or multiple selected lines of code or a selected section of code by using the toggle comment function.

How to use it

To toggle comment for one or multiple selected lines of code, press Cmd+/ (Mac) or Ctrl+/ (Windows), or go to Edit > Toggle Line Comment.

To toggle comments for a selected section of code, press Option+Shift+A (Mac) or Alt+Shift+A (Windows), or go to Edit > Toggle Block Comment.

See the following example where we first toggle line comment on a single line, then toggle line comment on multiple selected lines, and finally toggle block comment on a selection:

jcl toggle comment

More information

For information about how to utilize the different language features, see Making JCL code changes.

Last Updated:
Contributors: Prasang Prajapati
+ diff --git a/Blog/announcing-rexx.html b/Blog/announcing-rexx.html index 1cf48a6f6..36510bce8 100644 --- a/Blog/announcing-rexx.html +++ b/Blog/announcing-rexx.html @@ -41,11 +41,11 @@ } )(); A Modern REXX Editor | IBM Z® Open Editor - + -
IBM Z® Open Editor

A Modern REXX Editor

by Bradley Knaysi
18 March 2021

In the ongoing effort to bring z/OS® application development into the rich ecosystem of modern code editors, the REXX programming language is the next major addition. Enabled in IBM Z® Open Editor 1.2.0, IBM® Wazi Developer 1.2.0open in new window, and IBM Developer for z/OS 15.0.1open in new window, you will be able to benefit from our Language Server Protocol (LSP)open in new window implementation for REXX. This brings a plethora of language features to the editor, which make REXX development easier and more accessible.

There are several language features now available to augment the REXX editing experience.

Syntax highlighting

Arguably the most important of the bunch, the colorization of code is hard to go without these days. It's quite surprising how far a little color variance can go to make distinguishing symbols easier. Bringing visual clarity to the syntactically wild REXX programming language, this feature undeniably improves the speed and precision of development.

Syntax errors

Out of the many mainframe programming languages, REXX is truly the free spirit. While many languages enforce spacing, tabbing, and case-sensitivity to parse elements of the code, REXX has little to no such constraints. The result is a wide variety of programming styles, which leave the developer wondering what valid syntax is and is not. This is where syntax errors shine, bringing visual clarity to common and sometimes frustratingly trivial mistakes.

Code completion

Writing code can be a tedious process, and one that requires incredible memory and focus. Some of the simplest mistakes are misspelled symbols, and given that REXX does not require variable declaration before definition, these spelling errors can go completely unnoticed until some strange runtime error occurs. To alleviate this problem, you can utilize code completion to see variables, keyword instructions, internal routines, and built-in functions as suggestions as you type. This incredibly powerful feature gives you the confidence to know that the symbol you type is the right one.

Hover

REXX can be a daunting language to learn. Oftentimes, all you need is a little information about what an element is, what it does, and how to use it, in order to understand it. With the addition of the hover feature, moving your mouse over any keyword instruction or built-in function will reveal these critical bits of information. This brings documentation directly into the editor, letting you work in one place without having to navigate elsewhere to find knowledge.

Find references

It's fairly common to want to find matching symbols in a REXX program. Without relying on CTRL+F to navigate comments and partial matches, you can quickly find references on a symbol to get a quick view of all occurrences. This handy feature makes searching for other symbols easier than ever, without having to lose your place in the file.

Outline view

A highly underrated feature, the outline view provides an overview of a program. We did the research, studying real REXX developers, to find out how to make this feature actually useful. What we found, it can be a powerful navigation tool for quickly going to internal routine definitions. Instead of crowding the outline view with every loop and switch statement, it was significantly more useful when user's could glance over and see what internal routines were defined, and if they so desired, navigate there with one click.

More information

For information about how to edit REXX programs, see the REXX editing tutorial.

For information about how to utilize the different language features, see the Making REXX code changes page.

Last Updated:
Contributors: Bradley Knaysi, Min Huang, Peter Haumer, Peter Haumer
- +
IBM Z® Open Editor

A Modern REXX Editor

by Bradley Knaysi
18 March 2021

In the ongoing effort to bring z/OS® application development into the rich ecosystem of modern code editors, the REXX programming language is the next major addition. Enabled in IBM Z® Open Editor 1.2.0, IBM® Wazi Developer 1.2.0open in new window, and IBM Developer for z/OS 15.0.1open in new window, you will be able to benefit from our Language Server Protocol (LSP)open in new window implementation for REXX. This brings a plethora of language features to the editor, which make REXX development easier and more accessible.

There are several language features now available to augment the REXX editing experience.

Syntax highlighting

Arguably the most important of the bunch, the colorization of code is hard to go without these days. It's quite surprising how far a little color variance can go to make distinguishing symbols easier. Bringing visual clarity to the syntactically wild REXX programming language, this feature undeniably improves the speed and precision of development.

Syntax errors

Out of the many mainframe programming languages, REXX is truly the free spirit. While many languages enforce spacing, tabbing, and case-sensitivity to parse elements of the code, REXX has little to no such constraints. The result is a wide variety of programming styles, which leave the developer wondering what valid syntax is and is not. This is where syntax errors shine, bringing visual clarity to common and sometimes frustratingly trivial mistakes.

Code completion

Writing code can be a tedious process, and one that requires incredible memory and focus. Some of the simplest mistakes are misspelled symbols, and given that REXX does not require variable declaration before definition, these spelling errors can go completely unnoticed until some strange runtime error occurs. To alleviate this problem, you can utilize code completion to see variables, keyword instructions, internal routines, and built-in functions as suggestions as you type. This incredibly powerful feature gives you the confidence to know that the symbol you type is the right one.

Hover

REXX can be a daunting language to learn. Oftentimes, all you need is a little information about what an element is, what it does, and how to use it, in order to understand it. With the addition of the hover feature, moving your mouse over any keyword instruction or built-in function will reveal these critical bits of information. This brings documentation directly into the editor, letting you work in one place without having to navigate elsewhere to find knowledge.

Find references

It's fairly common to want to find matching symbols in a REXX program. Without relying on CTRL+F to navigate comments and partial matches, you can quickly find references on a symbol to get a quick view of all occurrences. This handy feature makes searching for other symbols easier than ever, without having to lose your place in the file.

Outline view

A highly underrated feature, the outline view provides an overview of a program. We did the research, studying real REXX developers, to find out how to make this feature actually useful. What we found, it can be a powerful navigation tool for quickly going to internal routine definitions. Instead of crowding the outline view with every loop and switch statement, it was significantly more useful when user's could glance over and see what internal routines were defined, and if they so desired, navigate there with one click.

More information

For information about how to edit REXX programs, see the REXX editing tutorial.

For information about how to utilize the different language features, see the Making REXX code changes page.

Last Updated:
Contributors: Bradley Knaysi, Min Huang, Peter Haumer, Peter Haumer
+ diff --git a/Blog/announcing-zos-resources-table.html b/Blog/announcing-zos-resources-table.html new file mode 100644 index 000000000..d7612e6dd --- /dev/null +++ b/Blog/announcing-zos-resources-table.html @@ -0,0 +1,51 @@ + + + + + + + + + Managing data sets, jobs, and UNIX files in Z Open Editor with the z/OS Resources Table | IBM Z® Open Editor + + + + +
IBM Z® Open Editor

Managing data sets, jobs, and UNIX files in Z Open Editor with the z/OS Resources Table

by Benjamin Santos
18 September 2024

Speaking from experience, mainframe development has a steep learning curve. Starting out, I had no experience with z/OS or with many of the programming languages that run on z/OS. On top of that, the tools used in mainframe development seemed daunting. I had grown accustomed to the modern IDEs I used while studying computer science in college and I felt hesitant to give them up to use traditional tools like ISPF instead.

IBM Z Open Editor is a great option for developers who prefer programming in a modern development environment (like me). It is a Visual Studio Code extension that combines the out-of-the-box capabilities of VS Code with language support for popular z/OS programming languages. From the beginning, Z Open Editor has used Zowe Explorer APIs for interacting with z/OS. Zowe Explorer relies on VS Code tree views for displaying and managing z/OS resources, which are very limited when it comes to sorting and filtering large amounts of resources. To address these shortcomings, we set out to provide a richer user experience that addresses many of our customer's requirements for dealing with large amounts of resources while still delivering a modern development experience. This was the design philosophy of the z/OS Resources Table.

The z/OS Resources Table is a tabular view that you can use to manage z/OS data sets, UNIX files, and jobs. It is intended to make the mainframe onboarding experience easier while still providing capabilities that are useful for more experienced developers.

Getting Started

To get started with the z/OS Resources Table, you need to create a Zowe Explorer profileopen in new window. These profiles contain information necessary for Z Open Editor to connect to your z/OS host. If you have already created a Zowe Explorer profile, you can begin using the table without any additional setup.

MVS, UNIX System Services, and JES views

When you open the table, you will be prompted to select a profile and a resource to interact with. You can select one of the three following resources:

  • MVS for managing data sets and data set members
  • USS for managing UNIX files
  • JES for managing jobs

Each view in the table will provide you with a set of actions you can use. Some actions are available across all resources, such as the navigation actions in the table's top-left which work like a web browser's navigation toolbar. Other actions are only available for the specific resource you are accessing, some of which we demonstrate below.

MVS

The MVS view is used to manage data sets. The table supports many basic data set operations (create, delete, edit, etc.) and more complex operations for filtering and viewing data sets. Click on a partitioned data set to view its members and clicking a sequential data set or data set member will open it in the editor.

Using the MVS view to submit data set members as jobs.Using the MVS view to submit data set members as jobs.

As demonstrated in the GIF above, you can quickly edit and submit the table’s active filter to control what resources are visible. You can also easily apply actions to multiple resources at once using batch actions. To sort the table, you can click on any column header to sort the table alphanumerically by that attribute, as you would in an Excel spreadsheet.

In Z Open Editor v4.5.0, we released new MVS search capabilities for RSE API users. You can specify string content to search for across sequential data sets or data set members. You can also specify a data set or member name pattern to narrow down their search results further.

Using the MVS Search and Filter menus to find COBOL programs that include the copybook CUSTCOPY.Using the MVS Search and Filter menus to find COBOL programs that include the copybook CUSTCOPY.

JES

The JES view is used for managing jobs and viewing job output. The table supports many basic job operations (canceling jobs, issuing stop or modify commands, viewing spool files, etc.) and provides capabilities for filtering jobs by name or status.

Viewing spool files of an active job.Submitting a JCL job in the MVS view. Using the JES to view filter jobs and view spool files to see why the submitted job failed.

Overflow menu actions, unlike batch actions, can be used to perform an action on a specific resource. The overflow menu can be opened by clicking on the three dots ⋮ on the right side of a table row as demonstrated in the GIF above.

UNIX System Services

The USS view is used for accessing and editing your host's UNIX files. You can navigate through the table by clicking on rows. Clicking a directory will display its contents and clicking a file will open it in a new editor, similar to how you would navigate directories using Windows File Explorer. The table supports basic UNIX operations (creating new files and directories, changing permissions, etc.) and more complex operations, including searching for files. With the new UNIX System Services search capabilities released in Z Open Editor v4.5.0, you can search for files by name and/or content.

Locating a user build log file by searching for a DBB error code.Locating a user build log file by searching for a DBB error code.

Learn More

This blog was meant to give you a high-level overview of what is available in the z/OS Resources Table. Many available actions are not covered here and the table is receiving new features and capabilities with each release. Try it out, and if there is a missing feature that you would like to be added, you can create an enhancement request on the Z Open Editor public repositoryopen in new window. For more information on the z/OS Resources Table, see its documentationopen in new window.

Last Updated:
Contributors: Benjamin Santos
+ + + diff --git a/Blog/code-snippets.html b/Blog/code-snippets.html index ea956bd20..5bc9459ed 100644 --- a/Blog/code-snippets.html +++ b/Blog/code-snippets.html @@ -41,11 +41,11 @@ } )(); Improve your z/OS enterprise developer productivity with IBM Z Open Editor‘s code snippets library | IBM Z® Open Editor - + -
IBM Z® Open Editor

Improve your z/OS enterprise developer productivity with IBM Z Open Editor‘s code snippets library

by Peter Haumer and Jonathan Sayles

Learning a new technology such as a new programming language with its SDKs and APIs can be a daunting task. Even developers with years of experience often start a new programming assignment by first researching code in previous projects they worked on or other related work. The massive popularity of sites such as https://stackoverflow.comopen in new window with its 11 M registered users shows that there is a big need for looking up best practices and standard solution patterns.

For z/OS enterprise developers, this problem is worse as there is not a lot of information out there. We currently count only 440 question about z/OS on Stack Overflow out of a total of 19 M. So many new enterprise developers start new assignments by first going on an "archaeological dig” in their organization following the popular "Monkey See, Monkey Do" development pattern, hunting down an existing program, copying the entire file, then cannibalizing the source, deleting most of the PROCEDURE and DATA DIVISION, editing the ENVIRONMENT and IDENTIFICATION DIVISIONs, etc. We might even have thought of this as a kind of haphazard "code reuse”. Occasionally we might have wondered if there are some better and more structured ways to reuse production code in order to jump start program development.

Production code reuseopen in new window has long been an objective for software developers. There are at least three important reasons given for this:

  • Productivity: Reusing syntactically correct and working code takes less time to develop and test.
  • Consistency and standards conformance: Maintenance and support costs are lowered as reusable code consists of recognizable patterns.
  • Education: By leveraging a catalog of reusable functions, developers who are new to z/OS can be given working examples of advanced language, statements, and code patterns accelerating time to mastery.

With IBM Z Open Editoropen in new window, we want to provide a development environment that feels natural and modern for the next generation of enterprise developers and gives them the tools they need. So, in addition to providing the latest language and editing features, we also want to help new developers to get started quicker as well as experienced developers to have access to best practices.

To achieve that goal, we enlisted IBM's most experienced educators and services consultants to give use their treasure trove of code patterns that they felt provided the largest value to COBOL, PL/I, and JCL practitioners. Greg Lambert, form the IBM Z Open Editor team, curated these collections and provided them as code snippets available in the latest release of IBM Z Open Editoropen in new window. The result is a library with a total of 186 snippets categorized as follows:

  • COBOL: 27 general COBOL language support snippets, 12 embedded SQL snippets, 29 CICS, 12 IMS, and 8 VSAM
  • PL/I: 12 general PL/I language support snippets, 29 CICS, 11 IMS, and 7 VSAM
  • JCL: 27 code snippets

These snippets provide everything you need from elemental basic statement groups, to full sets of routines and paragraphs of business logic with full computations and complex conditional logic, and frequently used statements such as job cards, database routines, or complex COBOL code such as UNSTRING and many more.

You can use these snippets for learning and as starting points for your own projects as well as use VS Code’s ability to manage your own library of user-created snippets based on these. If you have already used code snippets with IBM Developer for Z (IDz), we even provide an Import command to load these snippets into IBM Z Open Editor as well. For information about how to insert code snippets, create your own code snippets, and import code snippets from IBM Developer for z/OS, see the documentationopen in new window.

The following animated GIF shows you a few examples for how to use IBM Z Open Editor's snippets.

IBM Z Open Editor Code Snippets

Fig. 1: IBM Z Open Editor Code Snippets in action.

Although we provide these snippets as-is, we would love to hear from you about the value of the current stack, what issues you found, as well as what other snippets we should add. You can submit issues to our github siteopen in new window to start the discussion.

Last Updated:
Contributors: Peter Haumer, Min Huang, Peter Haumer, enzi
- +
IBM Z® Open Editor

Improve your z/OS enterprise developer productivity with IBM Z Open Editor‘s code snippets library

by Peter Haumer and Jonathan Sayles

Learning a new technology such as a new programming language with its SDKs and APIs can be a daunting task. Even developers with years of experience often start a new programming assignment by first researching code in previous projects they worked on or other related work. The massive popularity of sites such as https://stackoverflow.comopen in new window with its 11 M registered users shows that there is a big need for looking up best practices and standard solution patterns.

For z/OS enterprise developers, this problem is worse as there is not a lot of information out there. We currently count only 440 question about z/OS on Stack Overflow out of a total of 19 M. So many new enterprise developers start new assignments by first going on an "archaeological dig” in their organization following the popular "Monkey See, Monkey Do" development pattern, hunting down an existing program, copying the entire file, then cannibalizing the source, deleting most of the PROCEDURE and DATA DIVISION, editing the ENVIRONMENT and IDENTIFICATION DIVISIONs, etc. We might even have thought of this as a kind of haphazard "code reuse”. Occasionally we might have wondered if there are some better and more structured ways to reuse production code in order to jump start program development.

Production code reuseopen in new window has long been an objective for software developers. There are at least three important reasons given for this:

  • Productivity: Reusing syntactically correct and working code takes less time to develop and test.
  • Consistency and standards conformance: Maintenance and support costs are lowered as reusable code consists of recognizable patterns.
  • Education: By leveraging a catalog of reusable functions, developers who are new to z/OS can be given working examples of advanced language, statements, and code patterns accelerating time to mastery.

With IBM Z Open Editoropen in new window, we want to provide a development environment that feels natural and modern for the next generation of enterprise developers and gives them the tools they need. So, in addition to providing the latest language and editing features, we also want to help new developers to get started quicker as well as experienced developers to have access to best practices.

To achieve that goal, we enlisted IBM's most experienced educators and services consultants to give use their treasure trove of code patterns that they felt provided the largest value to COBOL, PL/I, and JCL practitioners. Greg Lambert, form the IBM Z Open Editor team, curated these collections and provided them as code snippets available in the latest release of IBM Z Open Editoropen in new window. The result is a library with a total of 186 snippets categorized as follows:

  • COBOL: 27 general COBOL language support snippets, 12 embedded SQL snippets, 29 CICS, 12 IMS, and 8 VSAM
  • PL/I: 12 general PL/I language support snippets, 29 CICS, 11 IMS, and 7 VSAM
  • JCL: 27 code snippets

These snippets provide everything you need from elemental basic statement groups, to full sets of routines and paragraphs of business logic with full computations and complex conditional logic, and frequently used statements such as job cards, database routines, or complex COBOL code such as UNSTRING and many more.

You can use these snippets for learning and as starting points for your own projects as well as use VS Code’s ability to manage your own library of user-created snippets based on these. If you have already used code snippets with IBM Developer for Z (IDz), we even provide an Import command to load these snippets into IBM Z Open Editor as well. For information about how to insert code snippets, create your own code snippets, and import code snippets from IBM Developer for z/OS, see the documentationopen in new window.

The following animated GIF shows you a few examples for how to use IBM Z Open Editor's snippets.

IBM Z Open Editor Code Snippets

Fig. 1: IBM Z Open Editor Code Snippets in action.

Although we provide these snippets as-is, we would love to hear from you about the value of the current stack, what issues you found, as well as what other snippets we should add. You can submit issues to our github siteopen in new window to start the discussion.

Last Updated:
Contributors: Peter Haumer, Min Huang, Peter Haumer, enzi
+ diff --git a/Blog/external-posts.html b/Blog/external-posts.html index 5550cbef8..0c0f22284 100644 --- a/Blog/external-posts.html +++ b/Blog/external-posts.html @@ -41,11 +41,11 @@ } )(); External Blog Posts and Articles | IBM Z® Open Editor - + -
IBM Z® Open Editor

External Blog Posts and Articles

Announcements and Official Communications

Articles

IBM Z DevOps Blogs

Other Useful Resources

Last Updated:
Contributors: Peter Haumer
- +
IBM Z® Open Editor

External Blog Posts and Articles

Announcements and Official Communications

Articles

IBM Z DevOps Blogs

Other Useful Resources

Last Updated:
Contributors: Peter Haumer
+ diff --git a/Blog/hlasm-blog.html b/Blog/hlasm-blog.html index 52d39e558..b8b015063 100644 --- a/Blog/hlasm-blog.html +++ b/Blog/hlasm-blog.html @@ -41,11 +41,11 @@ } )(); IBM Z Open Editor: A modern IDE for IBM High Level Assembler | IBM Z® Open Editor - + -
IBM Z® Open Editor

IBM Z Open Editor: A modern IDE for IBM High Level Assembler

By Daniel Beall

It may seem that an assembler editor simply needs syntax highlighting. After all, don't assembler programmers need only the most spartan of tools? However, after collaborating with IBMer assembler experts Brenton Belmar, a Senior Technical Staff Member of the IBM zMilicode team, Mike Fulton, an IBM Distinguished Engineer and IBM Z Open Automation Utilitiesopen in new window creator, and Walter Church of the IBM z/VM team, this sentiment could not be proven more wrong. We found that assembler deserves, just like COBOL and PL/I (two languages our IBM Z Open Editor also supports), much more attention. The IBM Z Open Editor adds, with version 1.0 available on June 12th, 2020, a new language server for IBM High Level Assembler (HLASM), bringing support for developers who want to use Visual Studio Code or Red Hat CodeReady Workspacesopen in new window to develop and maintain their applications.

Before we dive into the specifics of our assembler support, you might be wondering what exactly language servers and the Z Open Editor are. The Z Open Editoropen in new window is an extension for Visual Studio Code that provides language support for IBM Enterprise COBOL and PL/I. The language server is what "powers" our tooling for languages like COBOL, PL/I, and now HLASM. Language servers are implementations of language server protocol which is an initiative to standardize communication between editors and programming language tooling.

The process of building a language server for HLASM and adding it to our extension was not trivial, and we could not have done it without listening to users. From Brenton, Mike, and Walter, we discovered several important points about assembler:

  • HLASM has very advanced features compared to traditional assembly languages such as macros, copybooks, and conditional assembler.

  • HLASM programs can be very large. We found assembler programs with upwards of thirty thousand lines of code and of symbols. Navigating and exploring such large programs requires the ability to have indexes in the form of outline views and cross-refencing support in the editor that is language aware and goes beyond simple search.

  • z/Architecture is a CISC, or complex instruction set computer-architecture, with a myriad of instructions. In addition to bread-and-butter instructions, the latest mainframes support state-of-the-art hardware transactional memoryopen in new window, cryptographic, and SIMD instructions. The programmer must be able tohave code completion for instructions as well as inspect them.

It's clear the collaborative process helped us keep the uniqueness of assembler in mind. While designing the outline view, we experimented with including every symbol within a program. However, after better learning our user's needs, we found that it is better to simply have only CSECTs, DSECTs, and macros in the outline view. Often, if every symbol were to be included, the outline view would become extremely cluttered. The outline view is not the only feature where we've kept assembler's distinctiveness firmly in mind. In our code completion, we include reference information about assembler instructions. And, last but not least, we have included configurable vertical bars and tab stops to help users easily 'eyeball' sequence numbers and continuation line indicators. We feel these features will help assembler programmers, both veterans and novices alike, have a better experience working with language in our editor.

Editor Features

Let me walk you through some of the capabilities we added and how we think they can be useful for assembler developers.

Code Completion: When typing an instruction or operand, the editor will suggest instructions or symbol names. Since HLASM has over a thousand instructions, we found this to be very useful for quickly searching for relevant instructions.

COMPLETION GIF

Hover: Never worry about having to scroll to find the contents of a symbol again. To preview the contents of an operand symbol, simply move your mouse cursor over the symbol.

HOVER GIF

Go to Definition: To go to where a symbol is defined, simply right click an operand symbol, and click 'Go to Definition.' This is very convenient for large assembler programs. Having to scroll through a program or press Ctrl +F (Windows) or Cmd+F (Mac) to search through every use of a symbol is very tedious in comparison.

GO TO DEFINITION GIF

Copybook Resolution: To preview the contents of a copybook, move your mouse cursor over the copybook name in a COPY statement. You can also open the copybook in a separate editor by pressing Ctrl+Click (Windows) or Cmd+Click (Mac). To use this feature property groupsopen in new window will have to be set.

COPYBOOK GIF

Peek References: A results references view is displayed underneath symbols. Click any result to go to that location within a file.

HLASM PEEK REFERENCES GIF

Outline View: Explore and navigate assembler code. Relevant macros, CSECTs, and DSECTs are shown in the outline view.

HLASM OUTLINE GIF

Configurable Vertical Rulers and Tabstops: Easily navigate within a line. Press Tab to move forward and Shift+Tab to move backwards. Vertical rulers are included by default. Please see our documentationopen in new window to adjust vertical rulers and tabstops from defaults.

HLASM RULERS AND TABSTOPS GIF

Excited to try the Z Open Editor with HLASM support? Here's how

First, find out more about our editor at our About Pageopen in new window, and then see a full list of features on our Documentation Pageopen in new window. Next, please ensure prerequisitesopen in new window for our editor are installed. Then, download the extension through the Visual Studio Code Marketplaceopen in new window. Once the extension is installed, open an assembler file of your choice, or one of our samplesopen in new window. The editor should offer syntax highlighting and the features described above.

We would love to hear from you

We're incredibly thankful for having the opportunity to work with assembler experts such as Brenton, Walter, and Mike. But, at the same time, we want to better meet the needs of users external to IBM. We greatly welcome any feedback about our editor and how you and your organization are using assembler.

Having said that, we've created two ways for you to easily provide your comments:

1. Take our surveyopen in new window about HLASM editors and tooling.

2. For any questions, issues, or enhancement ideas, please do not hesitate to open an issue at our GitHub pageopen in new window.

We're looking forward to hearing from you and appreciate any feedback to improve this solution and help you be more productive.

Further Resources

In addition to trying our editor, we invite you to sample further resources related to mainframe hardware, the Z Open Editor, and HLASM.

Last Updated:
Contributors: Keng-Hui Beall, Peter Haumer, Peter Haumer, Chun Hong Zheng
- +
IBM Z® Open Editor

IBM Z Open Editor: A modern IDE for IBM High Level Assembler

By Daniel Beall

It may seem that an assembler editor simply needs syntax highlighting. After all, don't assembler programmers need only the most spartan of tools? However, after collaborating with IBMer assembler experts Brenton Belmar, a Senior Technical Staff Member of the IBM zMilicode team, Mike Fulton, an IBM Distinguished Engineer and IBM Z Open Automation Utilitiesopen in new window creator, and Walter Church of the IBM z/VM team, this sentiment could not be proven more wrong. We found that assembler deserves, just like COBOL and PL/I (two languages our IBM Z Open Editor also supports), much more attention. The IBM Z Open Editor adds, with version 1.0 available on June 12th, 2020, a new language server for IBM High Level Assembler (HLASM), bringing support for developers who want to use Visual Studio Code or Red Hat CodeReady Workspacesopen in new window to develop and maintain their applications.

Before we dive into the specifics of our assembler support, you might be wondering what exactly language servers and the Z Open Editor are. The Z Open Editoropen in new window is an extension for Visual Studio Code that provides language support for IBM Enterprise COBOL and PL/I. The language server is what "powers" our tooling for languages like COBOL, PL/I, and now HLASM. Language servers are implementations of language server protocol which is an initiative to standardize communication between editors and programming language tooling.

The process of building a language server for HLASM and adding it to our extension was not trivial, and we could not have done it without listening to users. From Brenton, Mike, and Walter, we discovered several important points about assembler:

  • HLASM has very advanced features compared to traditional assembly languages such as macros, copybooks, and conditional assembler.

  • HLASM programs can be very large. We found assembler programs with upwards of thirty thousand lines of code and of symbols. Navigating and exploring such large programs requires the ability to have indexes in the form of outline views and cross-refencing support in the editor that is language aware and goes beyond simple search.

  • z/Architecture is a CISC, or complex instruction set computer-architecture, with a myriad of instructions. In addition to bread-and-butter instructions, the latest mainframes support state-of-the-art hardware transactional memoryopen in new window, cryptographic, and SIMD instructions. The programmer must be able tohave code completion for instructions as well as inspect them.

It's clear the collaborative process helped us keep the uniqueness of assembler in mind. While designing the outline view, we experimented with including every symbol within a program. However, after better learning our user's needs, we found that it is better to simply have only CSECTs, DSECTs, and macros in the outline view. Often, if every symbol were to be included, the outline view would become extremely cluttered. The outline view is not the only feature where we've kept assembler's distinctiveness firmly in mind. In our code completion, we include reference information about assembler instructions. And, last but not least, we have included configurable vertical bars and tab stops to help users easily 'eyeball' sequence numbers and continuation line indicators. We feel these features will help assembler programmers, both veterans and novices alike, have a better experience working with language in our editor.

Editor Features

Let me walk you through some of the capabilities we added and how we think they can be useful for assembler developers.

Code Completion: When typing an instruction or operand, the editor will suggest instructions or symbol names. Since HLASM has over a thousand instructions, we found this to be very useful for quickly searching for relevant instructions.

COMPLETION GIF

Hover: Never worry about having to scroll to find the contents of a symbol again. To preview the contents of an operand symbol, simply move your mouse cursor over the symbol.

HOVER GIF

Go to Definition: To go to where a symbol is defined, simply right click an operand symbol, and click 'Go to Definition.' This is very convenient for large assembler programs. Having to scroll through a program or press Ctrl +F (Windows) or Cmd+F (Mac) to search through every use of a symbol is very tedious in comparison.

GO TO DEFINITION GIF

Copybook Resolution: To preview the contents of a copybook, move your mouse cursor over the copybook name in a COPY statement. You can also open the copybook in a separate editor by pressing Ctrl+Click (Windows) or Cmd+Click (Mac). To use this feature property groupsopen in new window will have to be set.

COPYBOOK GIF

Peek References: A results references view is displayed underneath symbols. Click any result to go to that location within a file.

HLASM PEEK REFERENCES GIF

Outline View: Explore and navigate assembler code. Relevant macros, CSECTs, and DSECTs are shown in the outline view.

HLASM OUTLINE GIF

Configurable Vertical Rulers and Tabstops: Easily navigate within a line. Press Tab to move forward and Shift+Tab to move backwards. Vertical rulers are included by default. Please see our documentationopen in new window to adjust vertical rulers and tabstops from defaults.

HLASM RULERS AND TABSTOPS GIF

Excited to try the Z Open Editor with HLASM support? Here's how

First, find out more about our editor at our About Pageopen in new window, and then see a full list of features on our Documentation Pageopen in new window. Next, please ensure prerequisitesopen in new window for our editor are installed. Then, download the extension through the Visual Studio Code Marketplaceopen in new window. Once the extension is installed, open an assembler file of your choice, or one of our samplesopen in new window. The editor should offer syntax highlighting and the features described above.

We would love to hear from you

We're incredibly thankful for having the opportunity to work with assembler experts such as Brenton, Walter, and Mike. But, at the same time, we want to better meet the needs of users external to IBM. We greatly welcome any feedback about our editor and how you and your organization are using assembler.

Having said that, we've created two ways for you to easily provide your comments:

1. Take our surveyopen in new window about HLASM editors and tooling.

2. For any questions, issues, or enhancement ideas, please do not hesitate to open an issue at our GitHub pageopen in new window.

We're looking forward to hearing from you and appreciate any feedback to improve this solution and help you be more productive.

Further Resources

In addition to trying our editor, we invite you to sample further resources related to mainframe hardware, the Z Open Editor, and HLASM.

Last Updated:
Contributors: Keng-Hui Beall, Peter Haumer, Peter Haumer, Chun Hong Zheng
+ diff --git a/Blog/ibm-wazi-development-client-introduction-blog.html b/Blog/ibm-wazi-development-client-introduction-blog.html index a040b30aa..2e0df68f7 100644 --- a/Blog/ibm-wazi-development-client-introduction-blog.html +++ b/Blog/ibm-wazi-development-client-introduction-blog.html @@ -41,11 +41,11 @@ } )(); Kubernetes-Native Integrated Z Developer Environment with IBM Wazi for Red Hat CodeReady Workspaces Development Client | IBM Z® Open Editor - + -
IBM Z® Open Editor

Kubernetes-Native Integrated Z Developer Environment with IBM Wazi for Red Hat CodeReady Workspaces Development Client

By Prasang A Prajapati

Have you ever experienced problems in setting up a development environment? Also, have you ever heard this excuse when reporting a bug to a colleague? "It works on my machine!"

You are joining a new development team or project and you have spent the first couple of days or longer just with installing the right tools, getting access to the right system and configuring your development profiles. Similarly, when starting a new project, a large portion of time and energy is spent on setting up the development environment. Think about how inefficient it could be if this type of set up routine is repeated for every new team member or new project every time.

To address this problem, there is an amazing tool called IBM® Wazi for Red Hat® CodeReady Workspaces Development Clientopen in new window (IBM Wazi Development Client). IBM Wazi Development Client is built on the Red Hat CodeReady Workspaces project. IBM Wazi Development Client uses Kubernetes and containers to provide any member of the development or IT team with a consistent, secure, and zero-configuration development environment for the IBM Z® Platform. The user experience is as fast and familiar as an integrated development environment (IDE) on their laptop.

IBM Wazi Development Client provides a modern experience for mainframe software developers working with z/OS® applications in the cloud by leveraging the available Visual Studio Code (VS Code) extensions IBM Z Open Editoropen in new window, IBM User Buildopen in new window and Zowe™ Exploreropen in new window, as well as the command-line tools Zowe CLIopen in new window and IBM RSE API Plug-in for Zowe CLI. Developers can use these Visual Studio Code extensions and command line tools on their local machine with the Visual Studio Codeopen in new window desktop IDE. Now, IBM Wazi Development Client makes this experience also available in the cloud. Powered by the open-source projects Zowe and Red Hat CodeReady Workspaces, IBM Wazi Development Client offers an easy, streamlined on-boarding process to get new mainframe developers using the tools they need. Using container technology and stacks, IBM Wazi Development Client brings the necessary technology to the task at hand.

Mainframe developers can now have rich language support for COBOL, PL/I, Assembler and JCL using IBM Z Open Editoropen in new window as well as connectivity to Z host using Zowe Exploreropen in new window, run user builds using IBM User Buildopen in new window, and interact with the IBM Remote System Explorer API, all in one Mainframe Development package using the IBM Wazi Development Client stackopen in new window with custom plugin and devfile registry support.

wazi-development-client

Fig 1: IBM Wazi for Red Hat CodeReady Workspaces Development Client controller architecture

The above figure explains workspaces controller architecture for the IBM Wazi Development Client. OpenShift® leverages the Kubernetes concept of a pod, which is one or more containers deployed together on one host, and the smallest compute unit that can be defined, deployed, and managed. In the IBM Wazi Development Client, when the user creates a workspace using Wazi Development Client Stack, it creates a workspace with deployed user runtime as well as a plugin sidecar container.

IBM Wazi Development Client Dashboard

wazi-development-client-dashboard

Fig 2: Screen capture of IBM Wazi Development Client Dashboard

Features

Here are the main features that IBM Wazi Development Client offers.

  1. IBM Z Open Editoropen in new window

    IBM Z Open Editor is a free Visual Studio Code extension that provides a modern editing experience for IBM Z Enterprise languages. IBM Z Open Editor gives developers the freedom to code in COBOL, PL/I and Assembler using the same editor they use for other languages such as Java™ and JavaScript. Learn moreopen in new window

    ibm-z-open-editor-cobolFig 3: Editing experience of COBOL files using IBM Z Open Editor in IBM Wazi Development Client

    ibm-z-open-editor-pl1Fig 4: Editing experience of PL/I files using IBM Z Open Editor in IBM Wazi Development Client

    ibm-z-open-editor-assemblerFig 5: Editing experience of Assembler files using IBM Z Open Editor in IBM Wazi Development Client

  2. IBM User Buildopen in new window

    The IBM User Build VS Code extension helps COBOL developers leverage the IBM Dependency Based Build (DBB) toolkit right from their local VS Code or IBM Wazi Development Client enviroment. Learn moreopen in new window

    ibm-user-buildFig 6: User Build using IBM User Build in IBM Wazi Development Client

  3. Zowe Exploreropen in new window

    Zowe Explorer is a free Visual Studio Code extension that lets you interact with data sets, USS files and jobs that are stored on IBM z/OS mainframes. You can explore data sets, USS files and jobs to view their contents, make changes, and upload the changes to the mainframe. Interacting with data sets, USS files and jobs from VS Code can be more convenient than using command-line interfaces or 3270 emulators. Learn moreopen in new window

    zowe-explorerFig 7: Interacting with data sets, USS files and jobs that are stored on IBM z/OS mainframes using Zowe Explorer in IBM Wazi Development Client

  4. Zowe CLIopen in new window

    Zowe CLI is a command-line interface that lets you interact with the mainframe in a familiar, off-platform format. Zowe CLI helps to increase overall productivity, reduce the learning curve for developing mainframe applications, and exploit the ease-of-use of off-platform tools. Zowe CLI lets you use common tools such as Integrated Development Environments (IDEs), shell commands, bash scripts, and build tools for mainframe development. Through its ecosystem of plug-ins, you can automate actions on systems such as IBM Db2®, IBM CICS®, and more. It provides a set of utilities and services for users who want to become efficient in supporting and building z/OS applications quickly. Learn moreopen in new window

    zowe-cliFig 8: Running Zowe commands to create, delete, or update profiles using Zowe CLI in IBM Wazi Development Client

  5. IBM RSE API Plug-in for Zowe CLI

    IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in) extends Zowe CLI to let you interact with z/OS resources. The RSE CLI plug-in interacts with z/OS by using IBM Remote System Explorer API (RSE API) instead of using z/OSMF. The RSE API is a collection of REST APIs that allow a client to work with various components on the z/OS host system, including MVS™ data sets, z/OS UNIX files and commands, JES jobs, and more. The overall solution results in a complete set of operations that allows you to do everything with RSE API that you could do with z/OSMF. It is therefore a great alternative if you have already used the Remote System Explorer with other IBM offerings such as IBM Developer for z/OS or IBM Explorer for z/OS. Learn more

    ibm-rse-apiFig 9: Create, delete or update RSE profiles using the RSE CLI plug-in in IBM Wazi Development Client

Documentation

For more information or to learn more about IBM Wazi for Red Hat CodeReady Workspaces Development Client, see IBM Wazi for Red Hat CodeReady Workspaces Development Client Documentationopen in new window.

Note: IBM Wazi Development Client is built on top of Red Hat CodeReady Workspacesopen in new window. For more information on what else can be done with workspaces, see the End-User Guideopen in new window.

Questions or feedback

We would love to hear what you think of this solution. For any questions, issues, or enhancement ideas, you can open an issue in the Wazi Codeready WorkSpaces Github repositoryopen in new window.

We are always looking for ways to improve.

Last Updated:
Contributors: Lauren Li, PrasangAPrajapati, Peter Haumer, Arvin Bhatnagar, Hestia Zhang, Shi Kun Li, kmaselli
- +
IBM Z® Open Editor

Kubernetes-Native Integrated Z Developer Environment with IBM Wazi for Red Hat CodeReady Workspaces Development Client

By Prasang A Prajapati

Have you ever experienced problems in setting up a development environment? Also, have you ever heard this excuse when reporting a bug to a colleague? "It works on my machine!"

You are joining a new development team or project and you have spent the first couple of days or longer just with installing the right tools, getting access to the right system and configuring your development profiles. Similarly, when starting a new project, a large portion of time and energy is spent on setting up the development environment. Think about how inefficient it could be if this type of set up routine is repeated for every new team member or new project every time.

To address this problem, there is an amazing tool called IBM® Wazi for Red Hat® CodeReady Workspaces Development Clientopen in new window (IBM Wazi Development Client). IBM Wazi Development Client is built on the Red Hat CodeReady Workspaces project. IBM Wazi Development Client uses Kubernetes and containers to provide any member of the development or IT team with a consistent, secure, and zero-configuration development environment for the IBM Z® Platform. The user experience is as fast and familiar as an integrated development environment (IDE) on their laptop.

IBM Wazi Development Client provides a modern experience for mainframe software developers working with z/OS® applications in the cloud by leveraging the available Visual Studio Code (VS Code) extensions IBM Z Open Editoropen in new window, IBM User Buildopen in new window and Zowe™ Exploreropen in new window, as well as the command-line tools Zowe CLIopen in new window and IBM RSE API Plug-in for Zowe CLI. Developers can use these Visual Studio Code extensions and command line tools on their local machine with the Visual Studio Codeopen in new window desktop IDE. Now, IBM Wazi Development Client makes this experience also available in the cloud. Powered by the open-source projects Zowe and Red Hat CodeReady Workspaces, IBM Wazi Development Client offers an easy, streamlined on-boarding process to get new mainframe developers using the tools they need. Using container technology and stacks, IBM Wazi Development Client brings the necessary technology to the task at hand.

Mainframe developers can now have rich language support for COBOL, PL/I, Assembler and JCL using IBM Z Open Editoropen in new window as well as connectivity to Z host using Zowe Exploreropen in new window, run user builds using IBM User Buildopen in new window, and interact with the IBM Remote System Explorer API, all in one Mainframe Development package using the IBM Wazi Development Client stackopen in new window with custom plugin and devfile registry support.

wazi-development-client

Fig 1: IBM Wazi for Red Hat CodeReady Workspaces Development Client controller architecture

The above figure explains workspaces controller architecture for the IBM Wazi Development Client. OpenShift® leverages the Kubernetes concept of a pod, which is one or more containers deployed together on one host, and the smallest compute unit that can be defined, deployed, and managed. In the IBM Wazi Development Client, when the user creates a workspace using Wazi Development Client Stack, it creates a workspace with deployed user runtime as well as a plugin sidecar container.

IBM Wazi Development Client Dashboard

wazi-development-client-dashboard

Fig 2: Screen capture of IBM Wazi Development Client Dashboard

Features

Here are the main features that IBM Wazi Development Client offers.

  1. IBM Z Open Editoropen in new window

    IBM Z Open Editor is a free Visual Studio Code extension that provides a modern editing experience for IBM Z Enterprise languages. IBM Z Open Editor gives developers the freedom to code in COBOL, PL/I and Assembler using the same editor they use for other languages such as Java™ and JavaScript. Learn moreopen in new window

    ibm-z-open-editor-cobolFig 3: Editing experience of COBOL files using IBM Z Open Editor in IBM Wazi Development Client

    ibm-z-open-editor-pl1Fig 4: Editing experience of PL/I files using IBM Z Open Editor in IBM Wazi Development Client

    ibm-z-open-editor-assemblerFig 5: Editing experience of Assembler files using IBM Z Open Editor in IBM Wazi Development Client

  2. IBM User Buildopen in new window

    The IBM User Build VS Code extension helps COBOL developers leverage the IBM Dependency Based Build (DBB) toolkit right from their local VS Code or IBM Wazi Development Client enviroment. Learn moreopen in new window

    ibm-user-buildFig 6: User Build using IBM User Build in IBM Wazi Development Client

  3. Zowe Exploreropen in new window

    Zowe Explorer is a free Visual Studio Code extension that lets you interact with data sets, USS files and jobs that are stored on IBM z/OS mainframes. You can explore data sets, USS files and jobs to view their contents, make changes, and upload the changes to the mainframe. Interacting with data sets, USS files and jobs from VS Code can be more convenient than using command-line interfaces or 3270 emulators. Learn moreopen in new window

    zowe-explorerFig 7: Interacting with data sets, USS files and jobs that are stored on IBM z/OS mainframes using Zowe Explorer in IBM Wazi Development Client

  4. Zowe CLIopen in new window

    Zowe CLI is a command-line interface that lets you interact with the mainframe in a familiar, off-platform format. Zowe CLI helps to increase overall productivity, reduce the learning curve for developing mainframe applications, and exploit the ease-of-use of off-platform tools. Zowe CLI lets you use common tools such as Integrated Development Environments (IDEs), shell commands, bash scripts, and build tools for mainframe development. Through its ecosystem of plug-ins, you can automate actions on systems such as IBM Db2®, IBM CICS®, and more. It provides a set of utilities and services for users who want to become efficient in supporting and building z/OS applications quickly. Learn moreopen in new window

    zowe-cliFig 8: Running Zowe commands to create, delete, or update profiles using Zowe CLI in IBM Wazi Development Client

  5. IBM RSE API Plug-in for Zowe CLI

    IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in) extends Zowe CLI to let you interact with z/OS resources. The RSE CLI plug-in interacts with z/OS by using IBM Remote System Explorer API (RSE API) instead of using z/OSMF. The RSE API is a collection of REST APIs that allow a client to work with various components on the z/OS host system, including MVS™ data sets, z/OS UNIX files and commands, JES jobs, and more. The overall solution results in a complete set of operations that allows you to do everything with RSE API that you could do with z/OSMF. It is therefore a great alternative if you have already used the Remote System Explorer with other IBM offerings such as IBM Developer for z/OS or IBM Explorer for z/OS. Learn more

    ibm-rse-apiFig 9: Create, delete or update RSE profiles using the RSE CLI plug-in in IBM Wazi Development Client

Documentation

For more information or to learn more about IBM Wazi for Red Hat CodeReady Workspaces Development Client, see IBM Wazi for Red Hat CodeReady Workspaces Development Client Documentationopen in new window.

Note: IBM Wazi Development Client is built on top of Red Hat CodeReady Workspacesopen in new window. For more information on what else can be done with workspaces, see the End-User Guideopen in new window.

Questions or feedback

We would love to hear what you think of this solution. For any questions, issues, or enhancement ideas, you can open an issue in the Wazi Codeready WorkSpaces Github repositoryopen in new window.

We are always looking for ways to improve.

Last Updated:
Contributors: Lauren Li, PrasangAPrajapati, Peter Haumer, Arvin Bhatnagar, Hestia Zhang, Shi Kun Li, kmaselli
+ diff --git a/Blog/in-the-cloud-with-che.html b/Blog/in-the-cloud-with-che.html index 92a15d8c0..4333e036e 100644 --- a/Blog/in-the-cloud-with-che.html +++ b/Blog/in-the-cloud-with-che.html @@ -41,11 +41,11 @@ } )(); IBM Z® Open Editor in the cloud with Eclipse Che | IBM Z® Open Editor - + -
IBM Z® Open Editor

IBM Z® Open Editor in the cloud with Eclipse Che

by Prasang A. Prajapati, Eric Subah, and Peter Haumer.
Last updated: 3 December 2019

IBM Z Open Editoropen in new window is a free Visual Studio Code extension that provides a modern editing experience for IBM Z Enterprise languages. It gives developers the freedom to code in COBOL and PL/I using the same editor they use for other languages such as Java and JavaScript. Learn moreopen in new window.

However, Visual Studio Code is a rich client editor that needs to be installed and configured by every development team member on their development machines. In addition to installing the editor, enterprise developers also have to get access to source code and other resources residing in SCMs and on z/OS.

What if you could avoid all this and developers could just join a project by getting access and logging on to a website? After logging on, the source code, access to z/OS, and the development environment required for maintaining the project would just be there and developers can just dive in?

To realize on this vision, there is an excellent open source tool platform called Eclipse Cheopen in new window. It was built to make Kubernetes development accessible for development teams, providing one-click developer workspaces and eliminating the need for local environment configurations for the entire team. This use case applies not only to Kubernetes development, but by utilizing z/OS connectivity features such as the ones provided by the Zoweopen in new window open source project also fits with the requirements for z/OS Mainframe development projects.

You can run Eclipse Che in the public cloud, private cloud, or install it on a large list of distributed OS (Ubuntu/Linux/MacOS/Windows). To learn more about Eclipse Che, see Introduction to Eclipse Cheopen in new window. It is also built for extensibility allowing organizations to create and plug-in additional enhancements or features.

In the following, we want to show you how easy it is to set up such an Eclipse Che environment in IBM Cloud using OpenShift that is fully integrated with IBM Z Open Editoropen in new window as well as Zowe Exploreropen in new window in three simple steps. We will provide a sample application that you can use for exploration, but once you have it up and running, you can explore other possibilities for this new kind of development style using your own source code. We would love to hear your feedback and engage into a discussion on how we can make this work for your teams.

Screen capture for IBM Z Open Editor in Eclipse Che Fig. 1: The user experience of IBM Z Open Editor in Eclipse Che

Step 1: Getting started with IBM Cloud and OpenShift

We recommend exploring Eclipse Che on IBM Cloud utilizing IBM's OpenShift V3.11 offering available there. However, the instruction provided here should also work on any other OpenShift or Kubernetes hosting platforms that can run Eclipse Che. If in fact you have Eclipse Che running somewhere in your organization or a Cloud account of your own, you can directly jump to Step 3 now. Note that although the cluster and Che environment you are using needs to have at least 3 GB of memory available, the standard Che trial servers at https://che.openshift.ioopen in new window do not provide enough resources at the moment unfortunately.

Introducing OpenShift

  • An open source containerized platform developed by Red Hatopen in new window.
  • It is platform as a service (PaaS)open in new window. PaaS is a category of cloud computing services which provides an environment for customers to develop, run and manage their applications without the complex infrastructure of building and managing applications.
  • OpenShift container platform is a service which can be deployed on public, private or hybrid cloud which will help customers to deploy applications using docker containers.
  • It is built on top of Kubernetesopen in new window and provides you tools like OpenShift web console or OpenShift CLI to manage projects and deployments.
  • It simplifies development and operations for cloud native applications.
  • It provides a web console to access and manage all the projects using built-in catalogs as well as OpenShift Container Platform templates. To learn more about OpenShift Web Console, you can view the OpenShift web console Walkthrough documentationopen in new window.

Creating an OpenShift cluster on IBM Cloud

Prerequisite: To run Eclipse Che on IBM Cloud using OpenShift, you need have a full IBM Cloud account because the IBM Cloud trial accounts do not have the option to create OpenShift clusters at the moment.

After you have a full IBM Cloud account, follow the steps below to create an OpenShift cluster:

  1. Log in to your IBM Cloud accountopen in new window.

  2. From the Services Catalog, select Red Hat OpenShift Clusteropen in new window. Then, click Create in the summary page.

  3. In the Create a new OpenShift cluster page, choose your cluster setup details and name:

    1. For the Location, select the Single zone, which should be enough for evaluation. Set the Geography and then select any of the Worker zones.
    2. Enter a unique name for your cluster and select the resource group that you want to assign to your cluster.
    3. For Default worker pool, choose an available flavor for your worker nodes. Red Hat OpenShift on IBM Cloud supports OpenShift version 3.11 only, which includes Kubernetes version 1.11. The operating system is Red Hat Enterprise Linux 7.
    4. Set a number of worker nodes to create per zone, such as 3.

  4. To finish, click Create cluster.

Notes:

  • Your cluster creation might take some time to complete. After the cluster state shows Normal, the cluster network and load-balancing component take about 10 more minutes to deploy and update the cluster domain that you use for the OpenShift web console and other routes.

  • Verify that your cluster setup is finished before you continue to the next step by checking that the Ingress subdomain on the cluster details page follows a pattern of <cluster_name>.<region>.containers.appdomain.cloud.

Tip: If you want to learn more about customizing your cluster setup with the CLI, check out Creating an OpenShift clusteropen in new window.

Step 2: Deploying Eclipse Che

Once you have an OpenShift cluster, you can deploy Eclipse Che on it. This will be done with just a few command-line operations. To be able to execute these commands, there are two prerequisites that you need to install:

  • Git: To use the features that involve Git, you must install Git and have it available in your system path so that Visual Studio 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 https://git-scm.comopen in new window
  • OpenShift CLI: OpenShift CLI is used to manage projects and their deployments. The easiest way to download the CLI is by accessing the About page on the web console if your cluster administrator has enabled the download links. To install OpenShift CLI, you can follow the OpenShift CLI reference documentationopen in new window. The steps basically consist of downloading a .zip file with two binary files that you need to place in the right location of your command path.

Once you have these two in place, your can perform these installation steps:

  1. Using a command line shell, find a location for your home directory and clone the che-operatoropen in new window repository by running this command:

    git clone https://github.com/eclipse/che-operator.git
+    
    IBM Z® Open Editor
     IBM Z® Open Editor in the cloud with Eclipse Che
    by Prasang A. Prajapati, Eric Subah, and Peter Haumer.
     Last updated: 3 December 2019
    IBM Z Open Editoropen in new window is a free Visual Studio Code extension that provides a modern editing experience for IBM Z Enterprise languages. It gives developers the freedom to code in COBOL and PL/I using the same editor they use for other languages such as Java and JavaScript. Learn moreopen in new window.
    However, Visual Studio Code is a rich client editor that needs to be installed and configured by every development team member on their development machines. In addition to installing the editor, enterprise developers also have to get access to source code and other resources residing in SCMs and on z/OS.
    What if you could avoid all this and developers could just join a project by getting access and logging on to a website? After logging on, the source code, access to z/OS, and the development environment required for maintaining the project would just be there and developers can just dive in?
    To realize on this vision, there is an excellent open source tool platform called Eclipse Cheopen in new window. It was built to make Kubernetes development accessible for development teams, providing one-click developer workspaces and eliminating the need for local environment configurations for the entire team. This use case applies not only to Kubernetes development, but by utilizing z/OS connectivity features such as the ones provided by the Zoweopen in new window open source project also fits with the requirements for z/OS Mainframe development projects.
    You can run Eclipse Che in the public cloud, private cloud, or install it on a large list of distributed OS (Ubuntu/Linux/MacOS/Windows). To learn more about Eclipse Che, see Introduction to Eclipse Cheopen in new window. It is also built for extensibility allowing organizations to create and plug-in additional enhancements or features.
    In the following, we want to show you how easy it is to set up such an Eclipse Che environment in IBM Cloud using OpenShift that is fully integrated with IBM Z Open Editoropen in new window as well as Zowe Exploreropen in new window in three simple steps. We will provide a sample application that you can use for exploration, but once you have it up and running, you can explore other possibilities for this new kind of development style using your own source code. We would love to hear your feedback and engage into a discussion on how we can make this work for your teams.
    Screen capture for IBM Z Open Editor in Eclipse Che Fig. 1: The user experience of IBM Z Open Editor in Eclipse Che
     Step 1: Getting started with IBM Cloud and OpenShift
    We recommend exploring Eclipse Che on IBM Cloud utilizing IBM's OpenShift V3.11 offering available there. However, the instruction provided here should also work on any other OpenShift or Kubernetes hosting platforms that can run Eclipse Che. If in fact you have Eclipse Che running somewhere in your organization or a Cloud account of your own, you can directly jump to Step 3 now. Note that although the cluster and Che environment you are using needs to have at least 3 GB of memory available, the standard Che trial servers at https://che.openshift.ioopen in new window do not provide enough resources at the moment unfortunately.
     Introducing OpenShift
    • An open source containerized platform developed by Red Hatopen in new window.
    • It is platform as a service (PaaS)open in new window. PaaS is a category of cloud computing services which provides an environment for customers to develop, run and manage their applications without the complex infrastructure of building and managing applications.
    • OpenShift container platform is a service which can be deployed on public, private or hybrid cloud which will help customers to deploy applications using docker containers.
    • It is built on top of Kubernetesopen in new window and provides you tools like OpenShift web console or OpenShift CLI to manage projects and deployments.
    • It simplifies development and operations for cloud native applications.
    • It provides a web console to access and manage all the projects using built-in catalogs as well as OpenShift Container Platform templates. To learn more about OpenShift Web Console, you can view the OpenShift web console Walkthrough documentationopen in new window.
     Creating an OpenShift cluster on IBM Cloud
    Prerequisite: To run Eclipse Che on IBM Cloud using OpenShift, you need have a full IBM Cloud account because the IBM Cloud trial accounts do not have the option to create OpenShift clusters at the moment.
    After you have a full IBM Cloud account, follow the steps below to create an OpenShift cluster:
    1. Log in to your IBM Cloud accountopen in new window.
    2. From the Services Catalog, select Red Hat OpenShift Clusteropen in new window. Then, click Create in the summary page.
    3. In the Create a new OpenShift cluster page, choose your cluster setup details and name:
      1. For the Location, select the Single zone, which should be enough for evaluation. Set the Geography and then select any of the Worker zones.
      2. Enter a unique name for your cluster and select the resource group that you want to assign to your cluster.
      3. For Default worker pool, choose an available flavor for your worker nodes. Red Hat OpenShift on IBM Cloud supports OpenShift version 3.11 only, which includes Kubernetes version 1.11. The operating system is Red Hat Enterprise Linux 7.
      4. Set a number of worker nodes to create per zone, such as 3.
    4. To finish, click Create cluster.
    Notes:
    • Your cluster creation might take some time to complete. After the cluster state shows Normal, the cluster network and load-balancing component take about 10 more minutes to deploy and update the cluster domain that you use for the OpenShift web console and other routes.
    • Verify that your cluster setup is finished before you continue to the next step by checking that the Ingress subdomain on the cluster details page follows a pattern of <cluster_name>.<region>.containers.appdomain.cloud.
    Tip: If you want to learn more about customizing your cluster setup with the CLI, check out Creating an OpenShift clusteropen in new window.
     Step 2: Deploying Eclipse Che
    Once you have an OpenShift cluster, you can deploy Eclipse Che on it. This will be done with just a few command-line operations. To be able to execute these commands, there are two prerequisites that you need to install:
    • Git: To use the features that involve Git, you must install Git and have it available in your system path so that Visual Studio 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 https://git-scm.comopen in new window
    • OpenShift CLI: OpenShift CLI is used to manage projects and their deployments. The easiest way to download the CLI is by accessing the About page on the web console if your cluster administrator has enabled the download links. To install OpenShift CLI, you can follow the OpenShift CLI reference documentationopen in new window. The steps basically consist of downloading a .zip file with two binary files that you need to place in the right location of your command path.
    Once you have these two in place, your can perform these installation steps:
    1. Using a command line shell, find a location for your home directory and clone the che-operatoropen in new window repository by running this command:
      git clone https://github.com/eclipse/che-operator.git
 
      This repository contains all the scripts and configuration files needed to deploy Eclipse Che and all of its components to your cluster. Refer to Che/Codeready Workspaces Operator Documentationopen in new window to learn more about che-operator. Then, navigate to the new directory with
      cd che-operator
 
      as you will execute commands form there further below.
    2. Using the OpenShift command line tool you need to now first log in to your cluster. The OpenShift web console provides a user-friendly way to do so using access token generating the entire login command for you to copy-paste. To find that, go back to your OpenShift web console browser screen and open user menu in the upper right corner. There you find the option Copy Login Command, which will copy the command to your clipboard. Go back to your command line shell and paste the login command and run it. For more information, see Creating a Projectopen in new window.
    3. Now you are ready to create a namespace in your cluster and deploy Che in that namespace. A namespace is a virtual cluster in which multiple resources exist. Each resource can be referenced by its unique name. Therefore, namespaces avoid basic naming collisions. A Project in OpenShift is equivalent to a Kubernetes namespace. However, in addition to the namespace name, OpenShift projects can also manage a user-friendly display name and description. For details, see Users, Namespaces, and Projectsopen in new window.
      oc create namespace <your_namespace_name>
 
      Then, navigate with your cluster login to the newly created namespace:
      oc project <your_namespace_name>
@@ -54,6 +54,6 @@
    "folderPath": "/projects"
 }
 
      The editor is saved automatically. Make sure the JSON does not have any syntax errors and then just close it. Now you can create files in USS and save them.
    Zowe Explorer opening MVS data set member with COBOL program. Fig. 3: Using Zowe Explorer to access z/OS resources such as COBOL programs in MVS data sets from Eclipse Che.
     Limitations and Outlook
    The steps described above allowed you to very quickly get up and running with Eclipse Che creating a workspace that contained the IBM Z Open Editor as well as the Zowe Explorer. However, the workspace definition we used was not integrated into your Eclipse Che Stacks list now, nor can it be easily configured and changed. To set this up in your organization so that development teams can create their own custom workspace definitions and instantiate many more workspaces easily you need to setup and manage two registries: a plugin and a devfiles registry. We will go into the details for doing that in our next Blog post.
    If you already want to read up on the workspace architecture of Che you can review these documentation pages for the Che Workspace Architectureopen in new window and the Workspace Controlleropen in new window.
     Troubleshooting
    Working with a cluster sometimes requires a bit more patience waiting for deployment jobs to complete. Sometime timeouts or other errors could happen. Here are some of the more common issue you might run into and suggestions for how to solve them:
    1. Failed to start workspace
      Sometimes it does happen when the workspace pod is not assigned to the project. Press F5 and click refresh link appears on the screen.
    2. Error: Failed to run the workspace: "Workspace is going to be STOPPED. Reason: Workspace is not started in time. Trying interrupt runtime start"
      While creating a workspace, it requires storage to be configured on the cluster. Che claims a persistent volume to the cluster. OpenShift cluster on IBM Cloud has capability to provision storages dynamically when a project claims for the persistent volume. Depending on the IBM Cloud traffic, it spends good amount of time to approve your claim and assign a storage to your workspace pod. You may refresh or press F5 to start over again.
    3. Unable to create persistent volume on workspace pod
      While creating a workspace, it requires storage to be configured on the cluster. Che claims a persistent volume to the cluster. Your cluster may not have configured for dynamic storage allocation. You need to create workspace in an Ephemeral Mode. Ephemeral mode is a function that allows users to browse the Web on a shared device or a personal laptop by using a profile that won't save any data or history after the browser is closed. Stop our workspace first, then you can go to Workspaces tab and open Workspace Configuration by click a middle configuration icon on the right side under ACTIONS tab, open Overview tab and turn on Ephemeral Mode. SAVE and RUN your workspace again.
     Questions or Feedback
    We would love to hear what you think of this solution. For any questions, issues, or enhancement ideas, please do not hesitate to open an issue at our GitHubopen in new window.
    We are always looking for ways to improve.
    Last Updated: 
    Contributors: Peter Haumer, Peter Haumer
    
-    
+    
   
 
diff --git a/Blog/learning.html b/Blog/learning.html
index 4a8625048..fca77c31a 100644
--- a/Blog/learning.html
+++ b/Blog/learning.html
@@ -41,11 +41,11 @@
                 }
             )();
             Learning Resources | IBM Z® Open Editor
-    
+    
     
   
   
-    
    IBM Z® Open Editor
     Learning Resources
     References
     Training
    Last Updated: 
    Contributors: Peter Haumer, Bradley Knaysi, kmaselli
    
-    
+    
    IBM Z® Open Editor
     Learning Resources
     References
     Training
    Last Updated: 
    Contributors: Peter Haumer, Bradley Knaysi, kmaselli
    
+    
   
 
diff --git a/Blog/new-content.html b/Blog/new-content.html
index 030b66e6e..d87df8b11 100644
--- a/Blog/new-content.html
+++ b/Blog/new-content.html
@@ -41,11 +41,11 @@
                 }
             )();
             New Content and Blog Posts | IBM Z® Open Editor
-    
+    
     
   
   
-    
    IBM Z® Open Editor
     New Content and Blog Posts
    Welcome to the IBM Z® Open Editor Team Blog. Bookmark this page as we update it regularly with new content such as blog posts, articles, and videos.
     IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.4.0 released
    August 12th, 2024
    Our August 2024 release of Z Open Editor and RSE API Plugin focuses on incremental refinements and fixes. We added many improvements to our Advanced Capabilities such as the following:
    • z/OS Resources Tables, which now features content search and new filter options.
    • Our Preprocessor support, which now adds support for z/OSMF, a Cancel button, as well as many fixes and small refinements.
    • As another highlight, our HLASM editor has been extended to now support code completion for local macros showing you all the macros parameters allowing you to use the tab key to navigate from parameter to parameter to fill in values. For operations the code completion mechanism is now also utilized for syntax errors.
    For our free content we fix language support issues for PL/I, HLASM, as well as our all new JCL language server. For COBOL we added a first implementation of a long requested feature: code folding. We also made improvements to our RSE API Plugin for Zowe CLI by adding a new command for UNIX System Services and finally providing an installation option for air gap, i.e. installing the plugin without access to the public internet.
    As always see the full changelog here.
     IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.3.0 released
    June 18th, 2024
    IBM Z Open Editor 4.3.0 is now available adding support for another language: Job Control Language (JCL). The new language server is a first increment that provides most frequently requested features such as an Outline view, real-time syntax checking, and code completion. We are planning to add more capabilities in the future and look forward to your feedback. See this Blog post for an overview.
    In addition to this free new language feature, we are also adding to the advanced capabilities for our IDzEE/ADFz audience by completing our preprocessor story with remote preprocessor execution. Run a custom preprocessor on z/OS, perhaps implemented in REXX, using a TSO command that reads a program file in a data set to produce a processed output file to be used by our COBOL language server for editing the program with the preprocessor statements. See our examples GitHub repositoryopen in new window for demo preprocessor implementations in Java and REXX to get started.
    As always, we also improved our language support addressing changes for the latest PL/I v6.1 January 2024 compiler refresh, fixed bugs reported by the community, and added minor enhancements requested by customers, such as an improved support for editing strings with double-byte characters to avoid truncation issues. See the full list of changes here.
     IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.2.0 released
    May 16th, 2024
    We released Z Open Editor and RSE API CLI plugin 4.2.0 with two more additions to our Advanced Features set:
    1. We added a brand new capability for HLASM developers to work with macro files showing hovers, document links, go to definition, and code completion for macros provided in local files.
    2. We also updated the z/OS Resource table with UNIX System Services support to provide you with the same capabilities to browse, filter, sort, open, download, upload, create, and copy your unix folders and files with the same user experience that we added in the 4.0.0 release for MVS and JES.
    In addition to the usual bug fixes and refinements, we also added COBOL User Defined Functions support to Z Open Editor as well as enhancements and fixes for our watsonx Code Assistant for Z integration. Find the complete list of changes here.
     IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.1.0 released
    March 28th, 2024
    Just two weeks after our major 4.0.0 update that focused on adding advanced features to Z Open Editor, we are releasing v4.1.0 with key updates for our watsonx Code Assistant for Z integration and the RSE API Plugin for Zowe CLI.
    We added a graphical end-to-end walkthrough for how to get started and set up for using the Code Assistant's Transform features in Z Open Editor. We also added new ways of navigating from the generated Java code back to the COBOL sources using a VS Code CodeLens. Plus, we fixed various bugs and issues reported by our watsonx users.
    For our Zowe CLI plugin we added powerful new commands for performing content searches on the UNIX System Services files. The CLI also introduces new command to a special RSE API for storing key-value pairs. RSE provides this mini key-value database feature that any system programmer or developer can use for their own purposes. You can store configuration information for private use in personal automation scripts or provide data to shared scripts across your team.
    Also check this new Blog postopen in new window about how to create your own credentials managers for Zowe CLI. This approach was used in the Kubernetes-based manager that we created in the Zowe projectopen in new window that you can run in IBM Wazi for Dev Spaces utilizing OpenShift secrets.
     IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.0.0 released
    March 15th, 2024
    We released a major update to Z Open Editor. In addition to featuring support for all the latest COBOL, PL/I, CICS, and HLASM languages refresh releases for z/OS 3.1, many RSE API enhancements, IBM Z Open Editor v4.0.0 is now 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 to add 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 the IBM Developer for z/OS Documentationopen in new window.
    To emphasize, none of the other features that you were using in previous releases are impacted by the update. Previous features are still available for free and will still be maintained and enhanced as always. We are also still fully committed to supporting z/OSMF and RSE API for the free as well as advanced capabilities.
    Only the following three new features require a license. Our goal is to provide more and more advanced features such as these to Z Open Editor in the future:
    1. 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.
    2. z/OS Resources table: an all-new feature rich 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.
    3. Advanced Dependency-Based user build error reporting: User build logs are now automatically downloaded, parsed, and presented in the editor's Problems view with 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.
    See the Advanced Capabilities section in our docs for a complete overview of these new capabilities.
    As this is a major version release, we also upgraded some of our dependencies requiring newer versions of VS Code (1.81.0), Zowe CLI (7.21.3), and Zowe Explorer (2.14.1).
    Go here for the full list of changes.
    Also check out the completely redesigned IBM Z Open Debug v4.0.0open in new window VS Code extension. It is now using Zowe CLI profiles as well and provides an all-new Zowe Explorer inspired Debugger Profiles view for a seamless integration of the IBM z/OS Debugger into the Z Open Editor/Zowe Explorer-based user experience.
     IBM Z Open Editor with IBM watsonx Code Assistant for Z v3.4.0 released
    February 29th, 2024
    We released IBM Z Open Editor v3.4.0. It introduces an all new user experience for generating Java classes in watsonx Code Assistant for Z. The COBOL-centric class generation preview of previous releases has been replaced with an all new Java-centric presentation. Users can now preview the Java classes to be generated in an expandable table view that outlines the variable and method member names next to their mapped COBOL names. They can click hyperlinks within the mapping view to navigate directly back to the COBOL source code files for comparison. We also redesigned the watsonx Code Assistant for Z tree view to show a breakdown of method members per Java class that can be generated by the assistant's AI component. These methods are based on COBOL section and paragraph names and become available after the initial Java class generation step has been completed. This will make it easy for developer to find the methods in the generated Java classes that they still need to generate using the AI-based transformation.
    We also fixed eight bugs for the core Z Open Editor language support, which were reported by our community. Keep the feedback coming on GitHubopen in new window. See the detailed list of fixes here.
     IBM Z Open Editor with IBM watsonx Code Assistant for Z v3.3.3 and IBM RSE API Plug-in for Zowe CLI v3.3.3 released
    December 15th, 2023
    We released IBM Z Open Editor v3.3.3 with various fixes for the editor as well as the watsonx Code Assistant integration. Find the detailed list of changes here.
     IBM Z Open Editor with IBM watsonx Code Assistant for Z and IBM RSE API Plug-in for Zowe CLI v3.3.0 released
    October 25th, 2023
    Our next major release of Z Open Editor and the RSE API Plug-in for Zowe CLI is now available. We added many new features such as support for CICS 6.2 Beta and automatic generation of a default ZAPP file if none exists, improved syntax errors for HLASM, added support for SSH keys for user builds, and addressed many enhancement requests and bugs reported by our community. See the complete list of changes here.
    This is also the first release that integrates client capabilities for the new IBM watsonx Code Assistant for Z product offering. IBM watsonx Code Assistant uses generative AI to accelerate code generation and increase developer productivity for application modernization. IBM watsonx Code Assistant for Z is now enabled in IBM Z Open Editor to drive the selective and incremental transformation of COBOL business services into Java code. It uses the inventory and analysis tools of IBM Application Discovery and Delivery Intelligence (ADDI) to support development teams in refactoring business services in COBOL, transforming COBOL code to Java code, and validating the resulting outcome. It is a separate product offering that you can purchase and then use with Z Open Editor. Learn more at https://www.ibm.com/products/watsonx-code-assistant-zosopen in new window.
     IBM Z Open Editor v3.2.2 and IBM RSE API Plug-in for Zowe CLI v3.2.2 released
    September 15th, 2023
    We released a fix pack for our Z Open Editor and the RSE API CLI addressing feedback, fixing bugs, and incrementally improving our language support, by fixing two more issues related to conditional compilation. Find the detailed list of fixes with links to Github issues here.
     IBM Z Open Editor v3.2.1 and IBM RSE API Plug-in for Zowe CLI v3.2.1 released
    July 19th, 2023
    We released a fix pack for our Z Open Editor and the RSE API CLI addressing feedback and one regression report we received for v3.2.0. We also incorporated various language fixes for CICS, PL/I, and HLASM. Find the detailed list of fixes with links to Github issues here.
     IBM Z Open Editor v3.2.0, IBM RSE API Plug-in for Zowe CLI v3.2.0, and Wazi for Dev Spaces v3.0.0 released
    June 16th, 2023
    We released version 3.2.0 of Z Open Editor and RSE API Plug-in for Zowe CLI and we shipped the Q2 release of IBM Z and Cloud Modernization Stackopen in new window that features Wazi for Code 3.0.0 that comprises of Wazi for VS Code and Wazi for Dev Spaces. Wazi for Dev Spaces ships as a major release update with version 3.0.0, which is now based on the new Red Hat OpenShift Dev Spaces version 3.6. It is a zero-install experience of a full z/OS Enterprise Application development environment that just completely runs in the browser featuring our Z Open Editor, Z Open Debug, Wazi Analyze, Ansible for z/OS, Zowe Explorer and CLI as well as many more capabilities.
    With this version we replaced the Eclipse Theia editor that ran our Z Open Editor with VS Code in the browser, which provides the same great user experience of VS Code on the desktop, such as multi-root workspaces and the code snippet gallery. It also now provides full compatibility to most of the extensions from the VS Code marketplace. You are now finally able to utilize great extensions such as GitLensopen in new window or the latest Red Hat Ansible language extensionopen in new window, which did not work with Theia. As always you can give our browser-based experience a try using a Red Hat Sandbox as well as other browser-based solutions such as GitHub Codespaces or GitPod. See our Getting Started page for details.
    As we were preparing for Wazi for Dev Spaces 3.0.0, we did not have a May fix pack release, but we did not stop working on fixes for the issues reported by our community. As you can see from the large size of our detailed Changelog, we addressed 13 issues reported by our GitHub communityopen in new window as well as many more reported through other channels. We also added many new enhancements such as language updates for COBOL and PL/I:
    We also added various new configuration options based on user feedback. For example, for each language to enable or disable the Problems view and syntax errors shown within the editor using zopeneditor.<language>.disableProblems while maintaining other language features. It will allow users to continue working in the program with some language features despite parsing issues. We also added user-defined variables to ZAPP files as well as various options to control how include files will be downloaded via Zowe from MVS for user to tweak performance and reliability.
     IBM Z Open Editor v3.1.1 released
    March 30th, 2023
    We released version 3.1.1 of Z Open Editor with fixes for some regressions found in v3.1.0. See the list of fixes here.
     IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v3.1.0 released
    March 10th, 2023
    We released version 3.1.0 of Z Open Editor and RSE API Plug-in for Zowe CLI. The main focus of this release were language improvements and fixes as well as scalability and performance.
    For PL/I, we caught up with the October language refresh for v6.1open in new window. For COBOL, we worked through a long list of issues that you can see in the detailed Changelog here. We also added one more set of options to our experimental COBOL source code formatter that allows you to specify how TO and INTO clauses should be formatted and aligned.
    We also tackled various performance issues that users reported when editing very large programs. In particular, issues around using wildcard/glob pattern expressions in the ZAPP file, which could lead to a lot of local directories and files being searched. Through caching we were able to improve load times significantly. On a test system with slow I/O, by editing a program that includes 1000 copybooks located in a large repository with many sub-directories searched using wildcards (e.g. **/COPYBOOK/**), we measured a performance gain from 8 minutes to 30 seconds for opening the program and loading the files. On a Mac with a fast SSD, it was just 4 seconds. We also added the same improvements that we made in v3.0.1 for loading remote include files from MVS in parallel for COBOL to the PL/I language server as well, which leads to a significant performance improvement when opening files with many include files as well as opening several programs at the same time.
    We also added file watchers to ZAPP property groups that monitor local files for changes. Now if you change, add, or delete a local included file in any of our languages that are used by programs opened in the editor, the programs will be updated with the changes immediately on Mac while you type or after you save on Windows.
    In addition to these changes, you can find in our Changelog many more fixes and refinements for user build, ZAPP, COBOL code formatter, Zowe Explorer's JES view with RSE API, and more.
    Finally, you are now able to use Z Open Editor in Microsoft's GitHub Codespaces and GitPod with all our capabilities. You can even use it with limited capabilities as a web extension when using Visual Studio Code in a browser, such as vscode.dev or github.dev. We documented how you can try all these browser-based and cloud-based options for free on our Getting started page.
     IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v3.0.1 released
    January 18th, 2023
    Version 3.0.1 is now available fixing several user-reported bugs. See the detailed list here.
     IBM Z Open Editor v3.0.0, IBM RSE API Plug-in for Zowe CLI v3.0.0, and Wazi for Dev Spaces v2.3.0 released
    November 22nd, 2022
    IBM Z Open Editor v3.0.0 is a major new release that provides many improvements for end users as well as many optimizations to make it run even better in the cloud on all supported platforms (s390x, x86).
    Together with Zowe Explorer 2.4 we improved and simplified the setup of team configuration files in Wazi for Dev Spaces and made a lot of robustness improvements. We also updated user build with IBM Dependency-Based Build adding more features for multi-root workspaces, scoping your builds and filtering the files to upload and download. We removed redundancies between user settings and ZAPP in favor of ZAPP files and simplified the data model for property groups that require a simple migration.
    We completely refactored our language parsers and reduced the overall size of the extension by another 25% to now just 37.4MB (remember the times when we were way over a 100MB?), improving load times in Red Hat CodeReady Workspaces and Wazi for Dev Spaces even further. The language servers are up-to-date using on the parsers from IBM Developer for z/OS version 16 that are compiled with Java 11 requiring users to upgrade in this release to a Java 11 or newer runtime. With this update comes also a large number of language fixes and improvements for IBM's latest enterprise language versions and particular CICS 6.1. See our release notes for the complete list of fixes.
     IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi for Dev Spaces v2.2.0 released
    September 20th, 2022
    IBM Z and Cloud Modernization Stack v2022.3.1open in new window is released today and with it updated versions 2.2.0 of IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi for Dev Spaces v2.2.0. Check out the Changelog for Z Open Editor and RSE API CLI with the details.
     IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI v2.1.1 released
    August 4th, 2022
    Version 2.1.1 is now available. This release fixed several IBM User Build issues which include adding support for COBOL nested copybooks, enabled user to enter Zowe CLI profile credentials in a popup dialog inside VS Code, fixed handling of file paths with spaces, and fixed various issues running User Build in multi-root workspaces. Check out the full Changelog here.
     IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi for Dev Spaces v2.1.0 released
    June 14th, 2022
    Version 2.1.0 is now available, which adds support for COBOL v6.4, PL/I v6.1, CICS v6.1, and HLASM for IBM z16 and z/OS 2.5. We also fixed many bugs, improved our support for Zowe 2, and implemented various community enhancement requests. See the detailed list here.
    This release also adds an experimental COBOL code formatter that is consistent to formatting in IBM Developer for z/OS. We are very interested in feedback and ideas for improvementsopen in new window.
     Zowe 2 support added with version 2.0.2
    April 25th, 2022
    IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI version 2.0.2 are now available. This release adds now full support for Zowe 2.0 in particular Zowe Explorer 2, Zowe CLI 7, Zowe API Mediation Layer 2. You can continue using your Zowe CLI 6.x profiles for backwards compatibility, but you must update Zowe Explorer to version 2 to do so. Review our Getting Started with Zowe 2.0 section in the Documentation for details and instructions for how to migrate your 6.x profiles to the new 7.x format.
     IBM Z Open Editor 2.0.0 released
    March 15th, 2022
    IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI version 2.0.0 are now available. They have been released as a major version update to celebrate their availability in IBM Wazi Developer for Workspaces 2.0.0, which is now part of the new IBM Z and Cloud Modernization Stackopen in new window offering. Together with the recently announced IBM Wazi as a Serviceopen in new window initiative, you can see how IBM Wazi is enabling the developer experience for Z to be more increasingly run from the Cloud - accelerating how organizations can provide flexible and modern development environments to their developers.
    A key enhancement of the Z and Cloud Modernization Stack offering is that Z Open Editor now fully supports OpenShift on Linux on Z when running as part of IBM Wazi. This allows you to now access your entire development environment with a browser-based VS Code-like experience all on Z.
    In addition to supporting the s390x platform, this release focused on quality updates addressing defects, performance improvements, feedback, and enhancement requests submitted by the Z Open Editor community on GitHubopen in new window. See our Changelog here for a full breakdown of all the issues addressed.
    Note, that because Zowe 2.0 was delayed to late April 2022, Z Open Editor 2.0.0 and the RSE API CLI Plug-in still have to be updated to support it. This version still requires Zowe version 1.x. We plan to release a fully Zowe 2.0 supported update of the editor and CLI plugin with the Zowe 2.0 release.
     IBM Z Open Editor 1.4.1 released
    November 19th, 2021
    IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI 1.4.1 are now available. This release fixes several language support and User Build issues. Additionally, password prompts for invalid or empty credentials during remote copybook and include file resolving have been added to prevent accidental MVS user account lock-outs and allow the use of Zowe profiles without stored credentials. You can find a detailed view of the updates contained in this release in our Changelog.
     IBM Z Open Editor 1.4.0 released
    October 29th, 2021
    IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI 1.4.0 are now available. A key focus area of this release was performance. We reduced the size of the VS Code extension to half, which users will see in reduced start-up times and memory footprint. Find the details of the many other fixes and enhancements here.
     IBM Z Open Editor 1.2.6 released
    August 19th, 2021
    IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI 1.2.6 are now available. We fixed several defects and addressed minor enhancement requests from our community. Plus, we made sure everything still works with Zowe Explorer 1.18.0, which was going through API changes to prepare for its Conformance Criteriaopen in new window support. See the detailed Changelog here.
    There is also a new Blog post from Scott Davis called "Wazi Developer – what is behind this name?open in new window" that offers a larger scope of the positioning of Z Open Editor in Wazi Developer.
     IBM Z Open Editor 1.2.5 released
    June 18th, 2021
    IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi Developer 1.2.5 are now available. In addition to various fixes and performance improvements detailed in our Changelog here, Wazi Developer for Workspaces is now based on Red Hat CodeReady Workspaces 2.8 and packages Zowe Explorer 1.15.1 as well as Zowe CLI 6.31.
     IBM Z Open Editor 1.2.1 released
    April 21st, 2021
    We released fixes for IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in) with version 1.2.1. For the editor, you will find various fixes and improvements for REXX language support in 1.2.1. For the RSE CLI plug-in, we revised and cleaned up output, error and log messages, and implemented various enhancements for single sign-on with the Zowe API Mediation Layer (APIML). For an introduction to using our tools with the Zowe APIML, read this new blog postopen in new window by Joe Winchester, IBM's Zowe technical lead.
     IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi Developer v1.2.0 released
    March 19th, 2021
    We released v1.2.0 of our tools today. See this blog post for an overview to the main things we added, as well as our Z Open Editor Changelogopen in new window for the list of fixes.
    There are also two new blog posts giving you an in-depth look at the all new REXX language support we added in this release as well as all the new enhancements for IBM RSE API Plug-in for Zowe CLI.
     IBM Db2 for z/OS Developer Extension v1.1.0 released
    February 23rd, 2021
    The latest release of IBM Db2 for z/OS Developer Extension is now available on the Visual Studio Code marketplaceopen in new window. In this release, the extension delivers the following key features:
    1. Full support on native SQL stored procedure (NSP). Developers can deploy the NSP with different options, debug the NSP (including nested NSP) and run the NSP.
    2. Run SQL from anywhere. Developers can highlight and run SQL DIRECTLY from other types of language source code files, like Cobol file, C file, Java file, JavaScript/Python files, and so on (you name it), so that they don’t need to copy/paste the statement to another .sql file or twist the SQLs to validate the result.
    3. More commit/rollback setting for SQL execution.
    You can read more about these new features hereopen in new window.
     IBM Z Open Editor and RSE CLI Plug-in release 1.1.2, and new blog of IBM User Build
    December 9th, 2020
    We released v1.1.2 of Z Open Editor and the RSE CLI plug-in adding some exciting new featuresopen in new window for High Level Assembler developers working with macros and international customers working with special characters in EBCDIC.
    We also added a new post to our team blog giving you an introduction and overview to Z Open Editor's User Build capability: IBM Z® Open Editor makes building COBOL, PL/I, and HLASM applications easier with User Build.
     IBM Z Open Editor and RSE API Plug-in for Zowe CLI 1.1.1 released
    November 6th, 2020
    We released v1.1.1 of Z Open Editor and the RSE API Plug-in to catch up with the latest v1.10.1 release of Zowe Explorer fully supporting now Zowe CLI Base Profilesopen in new window with RSE API JWT tokensopen in new window as well. Plus, we fixed a couple of bugsopen in new window reported by our communityopen in new window.
    To get the full package go to our download site here: https://ibm.github.io/mainframe-downloads/downloads.html#waziopen in new window
    In the coming weeks we will also be publishing more media content around Wazi Developer. We start today with a new blog post about configuring Wazi Developer for Workspaces in OpenShift with certificates.
     IBM Wazi Developer for Red Hat CodeReady Workspaces 1.1 released
    October 30th, 2020
    IBM Z Open Editor is part of the overall IBM Wazi Developer for Red Hat CodeReady Workspaces 1.1open in new window offering now, which was released today. Wazi Developer is a packaging of various developer components for VS Code as well as Eclipse. If you are a Z Open Editor user you might particularly interested in the Z Debug extension for VS Code and the updated RSE API Zowe CLI Plug-in v1.1.0. We have a detailed Blog post here with all the new features we added to the RSE API CLI Plug-in.
    Wazi Developer also contains solution components for developing from the Hybrid Cloud utilizing Red Hat CodeReady Workspaces 2.3 on OpenShift 4.3 with our Z Open Editor and Debug. Plus, the Wazi Sandbox component that provides a fully virtualized z/OS environment, which enables development and testing of z/OS applications on Red Hat OpenShift running on x86 hardware.
    Go here for an overview with videos and blog post: https://www.ibm.com/products/wazi-developeropen in new window
    The downloads of the client tools as well as links to the Cloud solution installation instructions are available on our new Mainframe Downloads siteopen in new window.
    Also check the original announcement with more details for what is exactly included in this offering.
     IBM Db2 for z/OS Developer Extension 0.5.0 released
    October 27th, 2020
    The latest release of IBM Db2 for z/OS Developer Extension is now available on the Visual Studio Code Marketplaceopen in new window.
    Db2 Developer Extension 0.5.0 continues to simplify and modernize the experience of developing SQL applications for Db2 for z/OS by providing the ability to create Db2 connections, SQL execution support, syntax checking, code completion, and signature help.
    You can read more about these new features hereopen in new window.
     Z Open Editor 1.1.0 released
    October 23rd, 2020
    IBM Z Open Editor 1.1.0 was released to the VS Code Marketplaceopen in new window. This release fully integrates the IBM User Build extension and expands its capabilities to support building PL/I and HLASM applications as well. We are also adding new features to property groups such as language-specific scoping with compiler options that configure the editor, as well as a complete new representation of property groups called ZAPP files. We also finally added full support for the Zowe Secure Credentials Store Plug-inopen in new window for all Z Open Editor functions such as remote include file resolution or user build.
    See the complete list of changes hereopen in new window.
     Z Open Editor 1.0.3 released and new Eclipse Che trial
    August 7th, 2020
    IBM Z Open Editor 1.0.3 was released to the VS Code Marketplaceopen in new window fixing various defects, adding branch labels to the HLASM Outline view, as well as introducing custom include file extensions.
    We also updated our Eclipse Che trial described in this blog post. Now you can use the free Red Hat trial accounts at https://che.openshift.ioopen in new window to run Eclipse Che. With just a few mouse-clicks you can now deploy Z Open Editor there. It is really simple (paste a URL, Go) as it loads everything from the Cloud. See the instructions and our Che Devfile here: https://github.com/IBM/zopeneditor-about/tree/main/cheopen in new window
     New IBM VS Code extension for Db2 SQL available now
    July 30th, 2020
    The first release of IBM Db2 for z/OS Developer Extension is now available on the Visual Studio Code Marketplaceopen in new window. Db2 Developer Extension brings SQL language support to VS Code and to Eclipse Theia.
    You can read more about this new extension hereopen in new window.
     VS Code Marketplace update
    June 30th, 2020
    IBM Z Open Editor 1.0.2 was released to the VS Code Marketplaceopen in new window adding High Level Assembler support now to that version as well.
     IBM Wazi in the News
    June 24th, 2020
    We released a small bug fix update for IBM Z Open Editor v0.5.2/1.0.1 today that addresses an issue with running our language servers with a Java newer than version 8. Now it works again with Java SDKs released since then, such as LTS 11, 14 etc.
    Since the release of IBM Wazi for Red Hat® CodeReady Workspaces the overall solution and its components have been mentioned and featured throughout the Web in various publications:
    (List updated on 6/28.)
    Finally, our IBM RSE API Plug-in for Zowe CLI v.1.0.0 has been approved as fully Zowe CLI conformant and is now featured in the Open Mainframe Project's Conformance Galleryopen in new window.
     IBM Wazi for Red Hat® CodeReady Workspaces available now
    June 19th, 2020
    You can now try out IBM Wazi for Red Hat CodeReady Workspaces Development Client (IBM Wazi Development Client) for a productive in-cloud development experience. The technical preview for IBM Wazi Development Client can be found at the Mainframe DEV Center's Downloads pageopen in new window.
    Read our new blog post Kubernetes-Native Integrated Z Developer Environment with IBM Wazi for Red Hat® CodeReady Workspaces Development Client for an overview to learn more about the features and components of IBM Wazi Development Client.
     IBM Z Open Editor 0.5.0 and 1.0.0 released
    June 12th, 2020
    IBM Z Open Editor v0.5.0 is released to the VS Code Marketplace. See here for all the enhancements and fixes.
    IBM Z Open Editor v1.0.0 adds a new IBM High Level Assembler language server. Unfortunately, by adding this capability our VS Code extension exceeds the maximum code size allowed for VS Code extensions on the Microsoft VS Code Marketplace. Until we reduce the file size you can get the v1.0.0 release only as a free download from IBMopen in new window.
    IBM Z Open Editor v1.0.0 is also part of IBM Developer for z/OS Enterprise Editionopen in new window. Customers who purchase this edition will then be able to receive technical support for Z Open Editor.
    To learn more about the new High Level Assembler language server see our Blog post:
     IBM Wazi for Red Hat CodeReady Workspaces announcement
    May 5th, 2020
    We announced today IBM Wazi for Red Hat CodeReady Workspaces in which the Z Open Editor will play a critical part. See the following resources:
     New Z Open Editor release and public beta of IBM RSE API
    March 26th, 2020
    We released IBM Z Open Editor v0.4.7open in new window with Beta support for IBM Remote System Explorer API and the new IBM RSE API Plug-in for Zowe CLIopen in new window.
    See our new Blog post Interacting with z/OS using IBM RSE API Plug-in for Zowe CLI for an overview as well as links to demo videos.
     New article about Zowe and Z Open Editor
    March 16th, 2020
     Updated Code Snippet library in IBM Z® Open Editor v0.4.3
    December 23rd, 2019
    We released v0.4.3 to the marketplaceopen in new window with an all new set of code snippets. To read more about it see our latest blog post:
     Updated Che devfile to use IBM Z® Open Editor v0.4.3 and Zowe Explorer 1.0.1
    December 23rd, 2019
    If you follow the instructions in our Using IBM Z® Open Editor in Eclipse Che blog post for creating a new Che Workpspace using our devfileopen in new window, you now get the latest releases of the editor (v0.4.3) the Zowe Explorer (v1.0.1).
     DevOps.com article featuring IBM Z® Open Editor's LSP capabilities
    December 18th, 2019
    Bob Reselman published a great article about the Language Server Protocolopen in new window and uses Z Open Editor as an example.
     Using IBM Z® Open Editor on the Web
    December 4th, 2019
    We added two new articles describing how you can use the IBM Z Open Editor VS Code extension outside of VS Code on Web running in a browser. We show you how to do it with two very popular frameworks:
     Z DevOps Talks podcast
    December 3rd, 2019
    Rosalind Radcliffe talksopen in new window about our editor, bring-your-own-IDE, DevOps, and future trends.
     IBM Systems Magazine Article
    September 26th, 2019
    Sanjay Chandru published an article about IBM Z Open Editoropen in new window and how it fits in perfectly with DevOps for IBM Z.
     IBM Z® Open Editor Release Announcement
    September 19th, 2019
    Read the official announcementopen in new window for the IBM Z Open Editor's first release.
    Last Updated: 
    Contributors: Peter Haumer, Peter Haumer, kmaselli, Lauren Li, Chun Hong Zheng, PETER HAUMER, Lauren Li, Shi Kun Li, Billie, Billie Simmons, KRISTINA MAYO, Lauren K Li, Min Huang, Prasang-A-Prajapati, shikunli
    
-    
+    
    IBM Z® Open Editor
     New Content and Blog Posts
    Welcome to the IBM Z® Open Editor Team Blog. Bookmark this page as we update it regularly with new content such as blog posts, articles, and videos.
     IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.5.0 released
    September 19th, 2023
    For the September 2024 release we reached a major milestone for completing our z/OS Resource Table and summarized all the new capabilities in a new Blog post. Please, share it with all your users. In particular, we are completed our Search capabilities for the table by adding content search for PDS members as well as UNIX System Services files.
    The second advanced feature that got significant enhancements is our preprocessor support, which we extended to also work with PL/I programs. Our samples repositoryopen in new window now provides preprocessor examples in Java and REXX for both target languages as well.
    On the free features side we added a new experimental content menu action to expand a COBOL program embedding all the nested copybooks and substituting REPLACING values. The feature is not complete as does not yet cover conditional compilation, but we are looking forward to your feedback.
    Finally, we added new commands and options to our RSE API Plugin for Zowe CLI, such as copying content between LPARs, new encoding conversion options, as well as performance tweaks.
    See the full changelog here.
     IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.4.0 released
    August 12th, 2024
    Our August 2024 release of Z Open Editor and RSE API Plugin focuses on incremental refinements and fixes. We added many improvements to our Advanced Capabilities such as the following:
    • z/OS Resources Tables, which now features content search and new filter options.
    • Our Preprocessor support, which now adds support for z/OSMF, a Cancel button, as well as many fixes and small refinements.
    • As another highlight, our HLASM editor has been extended to now support code completion for local macros showing you all the macros parameters allowing you to use the tab key to navigate from parameter to parameter to fill in values. For operations the code completion mechanism is now also utilized for syntax errors.
    For our free content we fix language support issues for PL/I, HLASM, as well as our all new JCL language server. For COBOL we added a first implementation of a long requested feature: code folding. We also made improvements to our RSE API Plugin for Zowe CLI by adding a new command for UNIX System Services and finally providing an installation option for air gap, i.e. installing the plugin without access to the public internet.
    As always see the full changelog here.
     IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.3.0 released
    June 18th, 2024
    IBM Z Open Editor 4.3.0 is now available adding support for another language: Job Control Language (JCL). The new language server is a first increment that provides most frequently requested features such as an Outline view, real-time syntax checking, and code completion. We are planning to add more capabilities in the future and look forward to your feedback. See this Blog post for an overview.
    In addition to this free new language feature, we are also adding to the advanced capabilities for our IDzEE/ADFz audience by completing our preprocessor story with remote preprocessor execution. Run a custom preprocessor on z/OS, perhaps implemented in REXX, using a TSO command that reads a program file in a data set to produce a processed output file to be used by our COBOL language server for editing the program with the preprocessor statements. See our examples GitHub repositoryopen in new window for demo preprocessor implementations in Java and REXX to get started.
    As always, we also improved our language support addressing changes for the latest PL/I v6.1 January 2024 compiler refresh, fixed bugs reported by the community, and added minor enhancements requested by customers, such as an improved support for editing strings with double-byte characters to avoid truncation issues. See the full list of changes here.
     IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.2.0 released
    May 16th, 2024
    We released Z Open Editor and RSE API CLI plugin 4.2.0 with two more additions to our Advanced Features set:
    1. We added a brand new capability for HLASM developers to work with macro files showing hovers, document links, go to definition, and code completion for macros provided in local files.
    2. We also updated the z/OS Resource table with UNIX System Services support to provide you with the same capabilities to browse, filter, sort, open, download, upload, create, and copy your unix folders and files with the same user experience that we added in the 4.0.0 release for MVS and JES.
    In addition to the usual bug fixes and refinements, we also added COBOL User Defined Functions support to Z Open Editor as well as enhancements and fixes for our watsonx Code Assistant for Z integration. Find the complete list of changes here.
     IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.1.0 released
    March 28th, 2024
    Just two weeks after our major 4.0.0 update that focused on adding advanced features to Z Open Editor, we are releasing v4.1.0 with key updates for our watsonx Code Assistant for Z integration and the RSE API Plugin for Zowe CLI.
    We added a graphical end-to-end walkthrough for how to get started and set up for using the Code Assistant's Transform features in Z Open Editor. We also added new ways of navigating from the generated Java code back to the COBOL sources using a VS Code CodeLens. Plus, we fixed various bugs and issues reported by our watsonx users.
    For our Zowe CLI plugin we added powerful new commands for performing content searches on the UNIX System Services files. The CLI also introduces new command to a special RSE API for storing key-value pairs. RSE provides this mini key-value database feature that any system programmer or developer can use for their own purposes. You can store configuration information for private use in personal automation scripts or provide data to shared scripts across your team.
    Also check this new Blog postopen in new window about how to create your own credentials managers for Zowe CLI. This approach was used in the Kubernetes-based manager that we created in the Zowe projectopen in new window that you can run in IBM Wazi for Dev Spaces utilizing OpenShift secrets.
     IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.0.0 released
    March 15th, 2024
    We released a major update to Z Open Editor. In addition to featuring support for all the latest COBOL, PL/I, CICS, and HLASM languages refresh releases for z/OS 3.1, many RSE API enhancements, IBM Z Open Editor v4.0.0 is now 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 to add 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 the IBM Developer for z/OS Documentationopen in new window.
    To emphasize, none of the other features that you were using in previous releases are impacted by the update. Previous features are still available for free and will still be maintained and enhanced as always. We are also still fully committed to supporting z/OSMF and RSE API for the free as well as advanced capabilities.
    Only the following three new features require a license. Our goal is to provide more and more advanced features such as these to Z Open Editor in the future:
    1. 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.
    2. z/OS Resources table: an all-new feature rich 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.
    3. Advanced Dependency-Based user build error reporting: User build logs are now automatically downloaded, parsed, and presented in the editor's Problems view with 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.
    See the Advanced Capabilities section in our docs for a complete overview of these new capabilities.
    As this is a major version release, we also upgraded some of our dependencies requiring newer versions of VS Code (1.81.0), Zowe CLI (7.21.3), and Zowe Explorer (2.14.1).
    Go here for the full list of changes.
    Also check out the completely redesigned IBM Z Open Debug v4.0.0open in new window VS Code extension. It is now using Zowe CLI profiles as well and provides an all-new Zowe Explorer inspired Debugger Profiles view for a seamless integration of the IBM z/OS Debugger into the Z Open Editor/Zowe Explorer-based user experience.
     IBM Z Open Editor with IBM watsonx Code Assistant for Z v3.4.0 released
    February 29th, 2024
    We released IBM Z Open Editor v3.4.0. It introduces an all new user experience for generating Java classes in watsonx Code Assistant for Z. The COBOL-centric class generation preview of previous releases has been replaced with an all new Java-centric presentation. Users can now preview the Java classes to be generated in an expandable table view that outlines the variable and method member names next to their mapped COBOL names. They can click hyperlinks within the mapping view to navigate directly back to the COBOL source code files for comparison. We also redesigned the watsonx Code Assistant for Z tree view to show a breakdown of method members per Java class that can be generated by the assistant's AI component. These methods are based on COBOL section and paragraph names and become available after the initial Java class generation step has been completed. This will make it easy for developer to find the methods in the generated Java classes that they still need to generate using the AI-based transformation.
    We also fixed eight bugs for the core Z Open Editor language support, which were reported by our community. Keep the feedback coming on GitHubopen in new window. See the detailed list of fixes here.
     IBM Z Open Editor with IBM watsonx Code Assistant for Z v3.3.3 and IBM RSE API Plug-in for Zowe CLI v3.3.3 released
    December 15th, 2023
    We released IBM Z Open Editor v3.3.3 with various fixes for the editor as well as the watsonx Code Assistant integration. Find the detailed list of changes here.
     IBM Z Open Editor with IBM watsonx Code Assistant for Z and IBM RSE API Plug-in for Zowe CLI v3.3.0 released
    October 25th, 2023
    Our next major release of Z Open Editor and the RSE API Plug-in for Zowe CLI is now available. We added many new features such as support for CICS 6.2 Beta and automatic generation of a default ZAPP file if none exists, improved syntax errors for HLASM, added support for SSH keys for user builds, and addressed many enhancement requests and bugs reported by our community. See the complete list of changes here.
    This is also the first release that integrates client capabilities for the new IBM watsonx Code Assistant for Z product offering. IBM watsonx Code Assistant uses generative AI to accelerate code generation and increase developer productivity for application modernization. IBM watsonx Code Assistant for Z is now enabled in IBM Z Open Editor to drive the selective and incremental transformation of COBOL business services into Java code. It uses the inventory and analysis tools of IBM Application Discovery and Delivery Intelligence (ADDI) to support development teams in refactoring business services in COBOL, transforming COBOL code to Java code, and validating the resulting outcome. It is a separate product offering that you can purchase and then use with Z Open Editor. Learn more at https://www.ibm.com/products/watsonx-code-assistant-zosopen in new window.
     IBM Z Open Editor v3.2.2 and IBM RSE API Plug-in for Zowe CLI v3.2.2 released
    September 15th, 2023
    We released a fix pack for our Z Open Editor and the RSE API CLI addressing feedback, fixing bugs, and incrementally improving our language support, by fixing two more issues related to conditional compilation. Find the detailed list of fixes with links to Github issues here.
     IBM Z Open Editor v3.2.1 and IBM RSE API Plug-in for Zowe CLI v3.2.1 released
    July 19th, 2023
    We released a fix pack for our Z Open Editor and the RSE API CLI addressing feedback and one regression report we received for v3.2.0. We also incorporated various language fixes for CICS, PL/I, and HLASM. Find the detailed list of fixes with links to Github issues here.
     IBM Z Open Editor v3.2.0, IBM RSE API Plug-in for Zowe CLI v3.2.0, and Wazi for Dev Spaces v3.0.0 released
    June 16th, 2023
    We released version 3.2.0 of Z Open Editor and RSE API Plug-in for Zowe CLI and we shipped the Q2 release of IBM Z and Cloud Modernization Stackopen in new window that features Wazi for Code 3.0.0 that comprises of Wazi for VS Code and Wazi for Dev Spaces. Wazi for Dev Spaces ships as a major release update with version 3.0.0, which is now based on the new Red Hat OpenShift Dev Spaces version 3.6. It is a zero-install experience of a full z/OS Enterprise Application development environment that just completely runs in the browser featuring our Z Open Editor, Z Open Debug, Wazi Analyze, Ansible for z/OS, Zowe Explorer and CLI as well as many more capabilities.
    With this version we replaced the Eclipse Theia editor that ran our Z Open Editor with VS Code in the browser, which provides the same great user experience of VS Code on the desktop, such as multi-root workspaces and the code snippet gallery. It also now provides full compatibility to most of the extensions from the VS Code marketplace. You are now finally able to utilize great extensions such as GitLensopen in new window or the latest Red Hat Ansible language extensionopen in new window, which did not work with Theia. As always you can give our browser-based experience a try using a Red Hat Sandbox as well as other browser-based solutions such as GitHub Codespaces or GitPod. See our Getting Started page for details.
    As we were preparing for Wazi for Dev Spaces 3.0.0, we did not have a May fix pack release, but we did not stop working on fixes for the issues reported by our community. As you can see from the large size of our detailed Changelog, we addressed 13 issues reported by our GitHub communityopen in new window as well as many more reported through other channels. We also added many new enhancements such as language updates for COBOL and PL/I:
    We also added various new configuration options based on user feedback. For example, for each language to enable or disable the Problems view and syntax errors shown within the editor using zopeneditor.<language>.disableProblems while maintaining other language features. It will allow users to continue working in the program with some language features despite parsing issues. We also added user-defined variables to ZAPP files as well as various options to control how include files will be downloaded via Zowe from MVS for user to tweak performance and reliability.
     IBM Z Open Editor v3.1.1 released
    March 30th, 2023
    We released version 3.1.1 of Z Open Editor with fixes for some regressions found in v3.1.0. See the list of fixes here.
     IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v3.1.0 released
    March 10th, 2023
    We released version 3.1.0 of Z Open Editor and RSE API Plug-in for Zowe CLI. The main focus of this release were language improvements and fixes as well as scalability and performance.
    For PL/I, we caught up with the October language refresh for v6.1open in new window. For COBOL, we worked through a long list of issues that you can see in the detailed Changelog here. We also added one more set of options to our experimental COBOL source code formatter that allows you to specify how TO and INTO clauses should be formatted and aligned.
    We also tackled various performance issues that users reported when editing very large programs. In particular, issues around using wildcard/glob pattern expressions in the ZAPP file, which could lead to a lot of local directories and files being searched. Through caching we were able to improve load times significantly. On a test system with slow I/O, by editing a program that includes 1000 copybooks located in a large repository with many sub-directories searched using wildcards (e.g. **/COPYBOOK/**), we measured a performance gain from 8 minutes to 30 seconds for opening the program and loading the files. On a Mac with a fast SSD, it was just 4 seconds. We also added the same improvements that we made in v3.0.1 for loading remote include files from MVS in parallel for COBOL to the PL/I language server as well, which leads to a significant performance improvement when opening files with many include files as well as opening several programs at the same time.
    We also added file watchers to ZAPP property groups that monitor local files for changes. Now if you change, add, or delete a local included file in any of our languages that are used by programs opened in the editor, the programs will be updated with the changes immediately on Mac while you type or after you save on Windows.
    In addition to these changes, you can find in our Changelog many more fixes and refinements for user build, ZAPP, COBOL code formatter, Zowe Explorer's JES view with RSE API, and more.
    Finally, you are now able to use Z Open Editor in Microsoft's GitHub Codespaces and GitPod with all our capabilities. You can even use it with limited capabilities as a web extension when using Visual Studio Code in a browser, such as vscode.dev or github.dev. We documented how you can try all these browser-based and cloud-based options for free on our Getting started page.
     IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v3.0.1 released
    January 18th, 2023
    Version 3.0.1 is now available fixing several user-reported bugs. See the detailed list here.
     IBM Z Open Editor v3.0.0, IBM RSE API Plug-in for Zowe CLI v3.0.0, and Wazi for Dev Spaces v2.3.0 released
    November 22nd, 2022
    IBM Z Open Editor v3.0.0 is a major new release that provides many improvements for end users as well as many optimizations to make it run even better in the cloud on all supported platforms (s390x, x86).
    Together with Zowe Explorer 2.4 we improved and simplified the setup of team configuration files in Wazi for Dev Spaces and made a lot of robustness improvements. We also updated user build with IBM Dependency-Based Build adding more features for multi-root workspaces, scoping your builds and filtering the files to upload and download. We removed redundancies between user settings and ZAPP in favor of ZAPP files and simplified the data model for property groups that require a simple migration.
    We completely refactored our language parsers and reduced the overall size of the extension by another 25% to now just 37.4MB (remember the times when we were way over a 100MB?), improving load times in Red Hat CodeReady Workspaces and Wazi for Dev Spaces even further. The language servers are up-to-date using on the parsers from IBM Developer for z/OS version 16 that are compiled with Java 11 requiring users to upgrade in this release to a Java 11 or newer runtime. With this update comes also a large number of language fixes and improvements for IBM's latest enterprise language versions and particular CICS 6.1. See our release notes for the complete list of fixes.
     IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi for Dev Spaces v2.2.0 released
    September 20th, 2022
    IBM Z and Cloud Modernization Stack v2022.3.1open in new window is released today and with it updated versions 2.2.0 of IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi for Dev Spaces v2.2.0. Check out the Changelog for Z Open Editor and RSE API CLI with the details.
     IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI v2.1.1 released
    August 4th, 2022
    Version 2.1.1 is now available. This release fixed several IBM User Build issues which include adding support for COBOL nested copybooks, enabled user to enter Zowe CLI profile credentials in a popup dialog inside VS Code, fixed handling of file paths with spaces, and fixed various issues running User Build in multi-root workspaces. Check out the full Changelog here.
     IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi for Dev Spaces v2.1.0 released
    June 14th, 2022
    Version 2.1.0 is now available, which adds support for COBOL v6.4, PL/I v6.1, CICS v6.1, and HLASM for IBM z16 and z/OS 2.5. We also fixed many bugs, improved our support for Zowe 2, and implemented various community enhancement requests. See the detailed list here.
    This release also adds an experimental COBOL code formatter that is consistent to formatting in IBM Developer for z/OS. We are very interested in feedback and ideas for improvementsopen in new window.
     Zowe 2 support added with version 2.0.2
    April 25th, 2022
    IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI version 2.0.2 are now available. This release adds now full support for Zowe 2.0 in particular Zowe Explorer 2, Zowe CLI 7, Zowe API Mediation Layer 2. You can continue using your Zowe CLI 6.x profiles for backwards compatibility, but you must update Zowe Explorer to version 2 to do so. Review our Getting Started with Zowe 2.0 section in the Documentation for details and instructions for how to migrate your 6.x profiles to the new 7.x format.
     IBM Z Open Editor 2.0.0 released
    March 15th, 2022
    IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI version 2.0.0 are now available. They have been released as a major version update to celebrate their availability in IBM Wazi Developer for Workspaces 2.0.0, which is now part of the new IBM Z and Cloud Modernization Stackopen in new window offering. Together with the recently announced IBM Wazi as a Serviceopen in new window initiative, you can see how IBM Wazi is enabling the developer experience for Z to be more increasingly run from the Cloud - accelerating how organizations can provide flexible and modern development environments to their developers.
    A key enhancement of the Z and Cloud Modernization Stack offering is that Z Open Editor now fully supports OpenShift on Linux on Z when running as part of IBM Wazi. This allows you to now access your entire development environment with a browser-based VS Code-like experience all on Z.
    In addition to supporting the s390x platform, this release focused on quality updates addressing defects, performance improvements, feedback, and enhancement requests submitted by the Z Open Editor community on GitHubopen in new window. See our Changelog here for a full breakdown of all the issues addressed.
    Note, that because Zowe 2.0 was delayed to late April 2022, Z Open Editor 2.0.0 and the RSE API CLI Plug-in still have to be updated to support it. This version still requires Zowe version 1.x. We plan to release a fully Zowe 2.0 supported update of the editor and CLI plugin with the Zowe 2.0 release.
     IBM Z Open Editor 1.4.1 released
    November 19th, 2021
    IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI 1.4.1 are now available. This release fixes several language support and User Build issues. Additionally, password prompts for invalid or empty credentials during remote copybook and include file resolving have been added to prevent accidental MVS user account lock-outs and allow the use of Zowe profiles without stored credentials. You can find a detailed view of the updates contained in this release in our Changelog.
     IBM Z Open Editor 1.4.0 released
    October 29th, 2021
    IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI 1.4.0 are now available. A key focus area of this release was performance. We reduced the size of the VS Code extension to half, which users will see in reduced start-up times and memory footprint. Find the details of the many other fixes and enhancements here.
     IBM Z Open Editor 1.2.6 released
    August 19th, 2021
    IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI 1.2.6 are now available. We fixed several defects and addressed minor enhancement requests from our community. Plus, we made sure everything still works with Zowe Explorer 1.18.0, which was going through API changes to prepare for its Conformance Criteriaopen in new window support. See the detailed Changelog here.
    There is also a new Blog post from Scott Davis called "Wazi Developer – what is behind this name?open in new window" that offers a larger scope of the positioning of Z Open Editor in Wazi Developer.
     IBM Z Open Editor 1.2.5 released
    June 18th, 2021
    IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi Developer 1.2.5 are now available. In addition to various fixes and performance improvements detailed in our Changelog here, Wazi Developer for Workspaces is now based on Red Hat CodeReady Workspaces 2.8 and packages Zowe Explorer 1.15.1 as well as Zowe CLI 6.31.
     IBM Z Open Editor 1.2.1 released
    April 21st, 2021
    We released fixes for IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in) with version 1.2.1. For the editor, you will find various fixes and improvements for REXX language support in 1.2.1. For the RSE CLI plug-in, we revised and cleaned up output, error and log messages, and implemented various enhancements for single sign-on with the Zowe API Mediation Layer (APIML). For an introduction to using our tools with the Zowe APIML, read this new blog postopen in new window by Joe Winchester, IBM's Zowe technical lead.
     IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi Developer v1.2.0 released
    March 19th, 2021
    We released v1.2.0 of our tools today. See this blog post for an overview to the main things we added, as well as our Z Open Editor Changelogopen in new window for the list of fixes.
    There are also two new blog posts giving you an in-depth look at the all new REXX language support we added in this release as well as all the new enhancements for IBM RSE API Plug-in for Zowe CLI.
     IBM Db2 for z/OS Developer Extension v1.1.0 released
    February 23rd, 2021
    The latest release of IBM Db2 for z/OS Developer Extension is now available on the Visual Studio Code marketplaceopen in new window. In this release, the extension delivers the following key features:
    1. Full support on native SQL stored procedure (NSP). Developers can deploy the NSP with different options, debug the NSP (including nested NSP) and run the NSP.
    2. Run SQL from anywhere. Developers can highlight and run SQL DIRECTLY from other types of language source code files, like Cobol file, C file, Java file, JavaScript/Python files, and so on (you name it), so that they don’t need to copy/paste the statement to another .sql file or twist the SQLs to validate the result.
    3. More commit/rollback setting for SQL execution.
    You can read more about these new features hereopen in new window.
     IBM Z Open Editor and RSE CLI Plug-in release 1.1.2, and new blog of IBM User Build
    December 9th, 2020
    We released v1.1.2 of Z Open Editor and the RSE CLI plug-in adding some exciting new featuresopen in new window for High Level Assembler developers working with macros and international customers working with special characters in EBCDIC.
    We also added a new post to our team blog giving you an introduction and overview to Z Open Editor's User Build capability: IBM Z® Open Editor makes building COBOL, PL/I, and HLASM applications easier with User Build.
     IBM Z Open Editor and RSE API Plug-in for Zowe CLI 1.1.1 released
    November 6th, 2020
    We released v1.1.1 of Z Open Editor and the RSE API Plug-in to catch up with the latest v1.10.1 release of Zowe Explorer fully supporting now Zowe CLI Base Profilesopen in new window with RSE API JWT tokensopen in new window as well. Plus, we fixed a couple of bugsopen in new window reported by our communityopen in new window.
    To get the full package go to our download site here: https://ibm.github.io/mainframe-downloads/downloads.html#waziopen in new window
    In the coming weeks we will also be publishing more media content around Wazi Developer. We start today with a new blog post about configuring Wazi Developer for Workspaces in OpenShift with certificates.
     IBM Wazi Developer for Red Hat CodeReady Workspaces 1.1 released
    October 30th, 2020
    IBM Z Open Editor is part of the overall IBM Wazi Developer for Red Hat CodeReady Workspaces 1.1open in new window offering now, which was released today. Wazi Developer is a packaging of various developer components for VS Code as well as Eclipse. If you are a Z Open Editor user you might particularly interested in the Z Debug extension for VS Code and the updated RSE API Zowe CLI Plug-in v1.1.0. We have a detailed Blog post here with all the new features we added to the RSE API CLI Plug-in.
    Wazi Developer also contains solution components for developing from the Hybrid Cloud utilizing Red Hat CodeReady Workspaces 2.3 on OpenShift 4.3 with our Z Open Editor and Debug. Plus, the Wazi Sandbox component that provides a fully virtualized z/OS environment, which enables development and testing of z/OS applications on Red Hat OpenShift running on x86 hardware.
    Go here for an overview with videos and blog post: https://www.ibm.com/products/wazi-developeropen in new window
    The downloads of the client tools as well as links to the Cloud solution installation instructions are available on our new Mainframe Downloads siteopen in new window.
    Also check the original announcement with more details for what is exactly included in this offering.
     IBM Db2 for z/OS Developer Extension 0.5.0 released
    October 27th, 2020
    The latest release of IBM Db2 for z/OS Developer Extension is now available on the Visual Studio Code Marketplaceopen in new window.
    Db2 Developer Extension 0.5.0 continues to simplify and modernize the experience of developing SQL applications for Db2 for z/OS by providing the ability to create Db2 connections, SQL execution support, syntax checking, code completion, and signature help.
    You can read more about these new features hereopen in new window.
     Z Open Editor 1.1.0 released
    October 23rd, 2020
    IBM Z Open Editor 1.1.0 was released to the VS Code Marketplaceopen in new window. This release fully integrates the IBM User Build extension and expands its capabilities to support building PL/I and HLASM applications as well. We are also adding new features to property groups such as language-specific scoping with compiler options that configure the editor, as well as a complete new representation of property groups called ZAPP files. We also finally added full support for the Zowe Secure Credentials Store Plug-inopen in new window for all Z Open Editor functions such as remote include file resolution or user build.
    See the complete list of changes hereopen in new window.
     Z Open Editor 1.0.3 released and new Eclipse Che trial
    August 7th, 2020
    IBM Z Open Editor 1.0.3 was released to the VS Code Marketplaceopen in new window fixing various defects, adding branch labels to the HLASM Outline view, as well as introducing custom include file extensions.
    We also updated our Eclipse Che trial described in this blog post. Now you can use the free Red Hat trial accounts at https://che.openshift.ioopen in new window to run Eclipse Che. With just a few mouse-clicks you can now deploy Z Open Editor there. It is really simple (paste a URL, Go) as it loads everything from the Cloud. See the instructions and our Che Devfile here: https://github.com/IBM/zopeneditor-about/tree/main/cheopen in new window
     New IBM VS Code extension for Db2 SQL available now
    July 30th, 2020
    The first release of IBM Db2 for z/OS Developer Extension is now available on the Visual Studio Code Marketplaceopen in new window. Db2 Developer Extension brings SQL language support to VS Code and to Eclipse Theia.
    You can read more about this new extension hereopen in new window.
     VS Code Marketplace update
    June 30th, 2020
    IBM Z Open Editor 1.0.2 was released to the VS Code Marketplaceopen in new window adding High Level Assembler support now to that version as well.
     IBM Wazi in the News
    June 24th, 2020
    We released a small bug fix update for IBM Z Open Editor v0.5.2/1.0.1 today that addresses an issue with running our language servers with a Java newer than version 8. Now it works again with Java SDKs released since then, such as LTS 11, 14 etc.
    Since the release of IBM Wazi for Red Hat® CodeReady Workspaces the overall solution and its components have been mentioned and featured throughout the Web in various publications:
    (List updated on 6/28.)
    Finally, our IBM RSE API Plug-in for Zowe CLI v.1.0.0 has been approved as fully Zowe CLI conformant and is now featured in the Open Mainframe Project's Conformance Galleryopen in new window.
     IBM Wazi for Red Hat® CodeReady Workspaces available now
    June 19th, 2020
    You can now try out IBM Wazi for Red Hat CodeReady Workspaces Development Client (IBM Wazi Development Client) for a productive in-cloud development experience. The technical preview for IBM Wazi Development Client can be found at the Mainframe DEV Center's Downloads pageopen in new window.
    Read our new blog post Kubernetes-Native Integrated Z Developer Environment with IBM Wazi for Red Hat® CodeReady Workspaces Development Client for an overview to learn more about the features and components of IBM Wazi Development Client.
     IBM Z Open Editor 0.5.0 and 1.0.0 released
    June 12th, 2020
    IBM Z Open Editor v0.5.0 is released to the VS Code Marketplace. See here for all the enhancements and fixes.
    IBM Z Open Editor v1.0.0 adds a new IBM High Level Assembler language server. Unfortunately, by adding this capability our VS Code extension exceeds the maximum code size allowed for VS Code extensions on the Microsoft VS Code Marketplace. Until we reduce the file size you can get the v1.0.0 release only as a free download from IBMopen in new window.
    IBM Z Open Editor v1.0.0 is also part of IBM Developer for z/OS Enterprise Editionopen in new window. Customers who purchase this edition will then be able to receive technical support for Z Open Editor.
    To learn more about the new High Level Assembler language server see our Blog post:
     IBM Wazi for Red Hat CodeReady Workspaces announcement
    May 5th, 2020
    We announced today IBM Wazi for Red Hat CodeReady Workspaces in which the Z Open Editor will play a critical part. See the following resources:
     New Z Open Editor release and public beta of IBM RSE API
    March 26th, 2020
    We released IBM Z Open Editor v0.4.7open in new window with Beta support for IBM Remote System Explorer API and the new IBM RSE API Plug-in for Zowe CLIopen in new window.
    See our new Blog post Interacting with z/OS using IBM RSE API Plug-in for Zowe CLI for an overview as well as links to demo videos.
     New article about Zowe and Z Open Editor
    March 16th, 2020
     Updated Code Snippet library in IBM Z® Open Editor v0.4.3
    December 23rd, 2019
    We released v0.4.3 to the marketplaceopen in new window with an all new set of code snippets. To read more about it see our latest blog post:
     Updated Che devfile to use IBM Z® Open Editor v0.4.3 and Zowe Explorer 1.0.1
    December 23rd, 2019
    If you follow the instructions in our Using IBM Z® Open Editor in Eclipse Che blog post for creating a new Che Workpspace using our devfileopen in new window, you now get the latest releases of the editor (v0.4.3) the Zowe Explorer (v1.0.1).
     DevOps.com article featuring IBM Z® Open Editor's LSP capabilities
    December 18th, 2019
    Bob Reselman published a great article about the Language Server Protocolopen in new window and uses Z Open Editor as an example.
     Using IBM Z® Open Editor on the Web
    December 4th, 2019
    We added two new articles describing how you can use the IBM Z Open Editor VS Code extension outside of VS Code on Web running in a browser. We show you how to do it with two very popular frameworks:
     Z DevOps Talks podcast
    December 3rd, 2019
    Rosalind Radcliffe talksopen in new window about our editor, bring-your-own-IDE, DevOps, and future trends.
     IBM Systems Magazine Article
    September 26th, 2019
    Sanjay Chandru published an article about IBM Z Open Editoropen in new window and how it fits in perfectly with DevOps for IBM Z.
     IBM Z® Open Editor Release Announcement
    September 19th, 2019
    Read the official announcementopen in new window for the IBM Z Open Editor's first release.
    Last Updated: 
    Contributors: Peter Haumer, Peter Haumer, kmaselli, Lauren Li, PETER HAUMER, Chun Hong Zheng, Lauren Li, Shi Kun Li, Billie, Billie Simmons, KRISTINA MAYO, Lauren K Li, Min Huang, Prasang-A-Prajapati, shikunli
    
+    
   
 
diff --git a/Blog/new-releases.html b/Blog/new-releases.html
index e95a1f0d3..a632d8efa 100644
--- a/Blog/new-releases.html
+++ b/Blog/new-releases.html
@@ -41,11 +41,11 @@
                 }
             )();
             IBM Z Open Editor Releases | IBM Z® Open Editor
-    
+    
     
   
   
-    
    IBM Z® Open Editor
     IBM Z Open Editor Releases
     4.4.0 - 2024/08/12
    • Fixed the issue where Java was not being found on Windows or Linux when Z Open Editor searched the user's system. (Issue 420open in new window)
    • Added code folding to our COBOL language server, which features folding for Divisions, Sections, Paragraphs, Data-items, and EXEC SQL/CICS statements. Also added code folding range support to JCL.
    • Improved the COBOL and JCL Outline views to include comments in the selection ranges when clicking an outline node.
    • Fixed the issue with the resolution order for the NAMES() compiler option in PL/I when it was listed before include file locations.
    • Added the file extension .dbd, .mfs, and .pcb to the defaults for our HLASM editor.
    • We now provide snippet style code completion for HLASM operations and macros. Use tab to fill out or remove various parameters when the operation or macro is selected from the code completion list. The editor will then also show syntax errors when manually typing operation parameters incorrectly.
    • Added Go to References support for HLASM Operations and Macros to see references within the same file for a selected operation.
    • Fixed the issue in JCL where an incorrect error was shown for DD statement: "JCL incorrectly highlights empty DD line as error".
    • Fixed the issue in JCL where an incorrect error was shown for EXEC DLI and XOPTS(DLI) statements.
    • Performance improvements for language server document requests when finding the copybooks/include files. The language server now prioritizes requesting the most recently opened documents.
    • Experimental: all Z Open Editor VS Code extension strings have been localized to French and German using IBM's AI machine translation. Let us know if you like these translations.
    Advanced features:
    • New feature: added filter and search operations to the z/OS Resources table. You can now search within the content of sequential data sets that are currently listed in your table; search requires using IBM's RSE API. We also added new filter options to the table for RSE API and z/OSMF to help you refine the list displayed for the Zowe query directly in the table. More search and filter capabilities will be added for RSE API users soon.
    • Combined "last modified" date and "last modified" time columns into "last modified" in z/OSMF PDS member views of the z/OS Resources Table.
    • Fixed the issue where the z/OS Resources Table was not compatible with MVS date formats in RSE API v1.1.5.
    • Various fixes, refinements and improvements for remote preprocessor support such as improved logging of the remote preprocessor execution output, better error handling, support for z/OSMF with TSO Zowe profiles, added the 'Compare preprocessor input and output files' command to remote preprocessor files as well as improvements for managing the output file.
    • Added a progress bar and a Cancel button to user build operations. After clicking the Cancel button, user build will wait until any remote operation is completed and then stop.
    IBM RSE API Plug-in for Zowe CLI:
    • We are now providing a variant of the RSE API CLI Plug-in that can be used for installation in air gapped development environments. Find ibm-rse-api-for-zowe-cli-airgap-4.4.0.tgz in our IBM Wazi for VS Code Zip file at https://ibm.github.io/mainframe-downloads/downloads.htmlopen in new window.
    • Fixed the issue with multiple items included in data set filter search with RSE profiles.
    • Fixed the issue reported using RSE CLI for downloading files when using Nodejs v20. (Issue 427open in new window)
    • Added a new change sub-command: clear-tag which clears the tags of the specified UNIX System Services file.
     4.3.0 - 2024/06/18
    Note: Import update for the release of version 4.3.0 of IBM Z Open Editor: IBM watsonx Code Assistant for Zopen in new window, which supports AI-assisted transformation of COBOL to Java for modernizing applications, has now been moved into it's own VS Code extension IBM watsonx Code Assistant for Z version 2.0.0. All functionality has been migrated into this new dedicated extension. Receive your copy of the Z Code Assistant via your Passport Advantage Online account. See the Documentationopen in new window for more details.
    • New advanced feature: run your custom COBOL preprocessor on z/OS directly from our editor and edit your files without any syntax errors caused by preprocessor statements. We now offer local preprocessor execution and editor integrations as well as remote execution via TSO commands on z/OS.
    • All new JCL language server: with this release we add language support for z/OS MVS JCLopen in new window. This first version includes the following features: 
      • Improved syntax highlighting
      • Real-time syntax errors
      • Code completion using Ctrl/Cmd + Space
      • Outline view
      • On-enter rules in Textmate grammar for JCL 
        • Auto prefix newline with // if previous line prefixed with // (except for in-stream declarations i.e. DD *). Indentation is inherited (up to column 16 for non-empty lines). JOB declarations are automatically indented to column 16
        • Auto comment continuation for lines prefixed with //*
      • Vertical rulers at significant JCL column numbers (2, 10, 11, 15, 16, 72, 80)
      • JCL Custom tabstops (Default tabstops are: [0, 2, 10, 15, 19, 29, 39, 49, 59, 71, 72])
      • Support for commenting and uncommenting highlighted selections using Ctrl/Cmd + /
    • Completed support for PL/I v6.1 January 2024 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this blog postopen in new window for details. Additionally, support for the new JSONIGNORE, JSONNULL keywords was added.
    • Fixed the issue in the PL/I editor evaluating the names for include files differently than the compiler if the name includes special characters.
    • Fixed the issue of false unreachable code warnings around EXEC CICS PERFORM + HANDLE statements. (Issue 52open in new window)
    • Fixed the issue of false unreachable code warnings around EXEC SQL WHENEVER statements. Issue 63open in new window)
    • Fixed the issue in the REXX editor showing incorrect syntax errors for ELSE statements in certain scenarios.
    • Fixed the issue in HLASM where optional operands were not correctly accounted for when evaluating the number of operands provided. (Issue 418open in new window)
    • Added support for double-byte character editing. The editor will decorate double-byte character strings using guillemets icons and display a byte counter in the status bar giving users information about how many bytes they have left for the current line to avoid truncation.
    • Extended the status bar information for the active Zowe profiles, making it an active button with options to change the profile selection. For RSE API profiles, it provides the option to update the z/OS password.
    • Fixed the issue where renaming sequential data sets using the z/OS resources tables would temporarily show empty attributes for the renamed data set.
    IBM RSE API Plug-in for Zowe:
    • Added a check for Zowe CLI version compatibility that is executed by the RSE API plugin for Zowe CLI during installation.
    • Uploading files to z/OS UNIX System Service using RSE API profiles can now automatically detect if the file is binary.
    • Fixed the issue of showing an incorrect error message when no data sets were found that match a search pattern.
     4.2.0 - 2024/05/16
    • New advanced feature: custom macro resolution in HLASM programs with references to macros in local files. The HLASM editor shows hovers, document links, go to definition, and code completion for macros. This feature works with one to many macro declarations per include file, which is achieved by pre-scanning macro files if they can be found in local ZAPP property groups. For more information, see Custom Macros for HLASM.
    • Improved advanced feature: the z/OS resources table is updated to also support UNIX System Services. You can browse, filter, sort, open, download, upload, create, and copy your unix folders and files with the same user experience as in our previous release for MVS and JES. In addition, you find many UX refinements and polish for all views of this table. We also fixed 
      • presenting and sorting numbers and dates based on the user's locale.
      • presenting DSNTYPE for MVS data sets, even if the value is not provided by z/OSMF.
    • Added support for COBOL User Defined Function Prototypes. See COBOL documentationopen in new window for details.
    • Fix the issue where formatting EXEC SQL statements resulted in incorrect syntax (Issue 400open in new window).
    • Reorganized our startup and restart code to avoid problems such as Issue 403open in new window.
    IBM RSE API Plug-in for Zowe:
    • Fixed the issue of spool files not being correctly exported when their record length exceeded that of the destination dataset, resulting in truncation.
    • Fixed typographical errors in the new common-properties commands.
    • Fixed the issue that is seen downloading all members of a data set.
    IBM watsonx Code Assistant for Z:
    • Added editing of local variable names during class generation that will then be used during Java method generation.
    • Added editing of method input parameters during class generation that will then be used during Java class and method generation.
    • Improved Java method generation by sanitizing the COBOL code, such as removing comments and contents from columns 1-6 and 73-80.
    • Fixed the issue where for some edge cases the Java method generation was returning an empty code block.
    • Fix the issue where Java classes and methods were not appearing in the watsonx Code Assistant for Z tree view when the COBOL program was located in the top-level workspace folder.
    • Fixed the issue of the editor opening the same Java file in multiple editor tabs when using the watsonx Code Assistant for Z tree view.
    • Added support for proxy servers for watsonx interactions utilizing the VS Code settings http.proxy, http.proxyStrictSSL, http.proxyAuthorization when http.proxySupport is switched to on.
    • Various fixes and refinements for the watsonx tree view interactions related to item and source code selection.
     4.1.0 - 2024/03/28
    • Fixed the issue where SETC values were causing the HLASM parser to fail in certain scenarios. (Issue 396open in new window)
    • Added new options for listing additional job attributes in RSE API Plug-in for Zowe CLI.
    • Added ability to search files in UNIX System Services by file name or content in RSE API Plug-in for Zowe CLI.
    • Added new commands for storing and retrieving name/value pairs with RSE's Common Properties service in RSE API Plug-in for Zowe CLI.
    • Fixed the issue of failed downloads from z/OS for some file types using RSE API profiles.
    • Fixed the issue where downloading spool files with RSE API profiles would be stored with invalid file extensions.
    IBM watsonx Code Assistant for Z updates:
    • Added a walkthrough for new users to get a step-by-step guide on how to use watsonx Code Assistant for Z. You can access the walkthrough from the Z Open Editor Welcome page or from the VS Code Welcome page.
    • Added a new CodeLens when editing generated Java code to view and navigate to the COBOL source that watsonx Code Assistant for Z was using to generate a Java method.
    • COBOL files selected for Transformation in watsonx Code Assistant for Z will no longer open in read-only mode.
     4.0.0 - 2024/03/15
    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 Documentationopen in new window.
    To emphasize, none of the other features that you were using in previous releases are impacted by the update. Previous features are still available for free and will still be maintained and enhanced as always. We are also still fully committed to supporting z/OSMF and RSE API for the free as well as advanced capabilities.
    Only the following three new features require a license. Our goal is to provide more and more advanced features such as these to Z Open Editor in the future:
    1. 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.
    2. z/OS Resources table: an all-new feature rich 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.
    3. Advanced Dependency-Based user build error reporting: User build logs are now automatically downloaded, parsed, and presented in the editor's Problems view with 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.
    We reorganized the Z Open Editor Welcome page for you to see the status of your trial license. You can unlock the features by importing an activation kit or connecting to an RSE API server with configured IDzEE licenses.
    Free languages updates:
    • Added support for the COBOL v6.4 February 2024 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this blog postopen in new window for details.
    • Added support for the COBOL v6.4 October 2023 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this blog postopen in new window for details.
    • Added support for the PL/I v6.1 January 2024 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this blog postopen in new window for details.
    • Added support for the CICS v6.2 Beta Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features.
    • Added support for the z/OS 3.1 default HLASM macros. z/OS 3.1 is now the default option. To change your z/OS level, search zopeneditor.hlasm.zosMacrosVersion in settings.
    • Fixed the issue where the HLASM Language Server did not parse non-english characters correctly. (#389open in new window)
    • Added the debug scheme to our language clients, enabling full language server support providing you with features such as Outline view, Go to Definition, Find All References even when running IBM Z Open Debug sessions. (#360open in new window)
    Free RSE API Plug-in for Zowe CLI updates:
    • Z Open Editor extends the Zowe Explorer's Jobs view experience: open a spool file in Zowe Explorer and Z Open Editor will automatically provide JCL and messages syntax highlighting.
    • Added support for changing file tags on USS for RSE API profiles in Zowe Explorer.
    • Added support to show partitioned data set member attributes for RSE API profiles in Zowe Explorer.
    • Added support for creating a data sets for RSE API profiles using the new templates from Zowe Explorer.
    • Added support for Zowe profile encoding with DBB User Build download of log files.
    • Added new command issue unix-shell for RSE API profiles that utilizes a streaming command output and allows users to set environment variables for the executing shell.
    • Added new command export spool-file for RSE API profiles allowing export of job spool files to a sequential data set or data set members.
    • Added support for refreshToken and auto-refresh-token for RSE API profiles in Zowe Explorer.
    • Switched to using RSE API streaming for raw content when uploading to and downloading from MVS, UNIX System Services, and JES files.
    • Fixed the issue with creating a partitioned data set of the type LIBRARY for RSE API profiles did not work correctly.
    • Fixed the issue of command issue unix returning an incorrect exit code.
    • Fixed the error when submitting jobs using the --wfo (wait for output) option using RSE API profiles. (#385open in new window)
     3.4.0 - 2024/02/29
    • Fixed the issue with Embedded EXEC CICS statements where EXEC CICS GET CHANNEL was marked with the error "RESP expected instead of this input". (Issue 361open in new window)
    • Fixed the issue with Embedded CICS EXCI statements where CICS EXCI was marked with the error "RESP expected instead of this input".
    • Fixed the issue with Embedded SQL statements where SQLCA symbols were not resolved when an "EXEC SQL INCLUDE SQLCA" statement was inside of a conditional compilation block. (Issue 379open in new window)
    • Fixed the issue of incorrectly showing an error about the absence of an end directive when the conditional compilation directive ">>define" was on the last line of a Copybook file. (Issue 374open in new window)
    • Fixed the issue where COBOL COPY statements with a "." but without a whitespace were marked with an error.
    • Fixed the issue where document links were not resolving correctly when multiple documents were opened in parallel that pointed to the same include files in COBOL, PL/I, and HLASM files. (Issue 363open in new window)
    • Fixed an issue where document links would not remove the red underline for an include file after loading correctly in COBOL, PL/I, and HLASM files. (Issue 363open in new window)
    • Fixed the issue where REXX syntax highlighting would break when an empty comment statement was present /**/. (Issue 384open in new window).
    IBM watsonx Code Assistant for Z updates:
    • Replaced the COBOL-centric class generation preview with a new Java-centric presentation for watsonx Code Assistant for Z. Users can now preview the Java classes to be generated in an expandable table view that outlines the variable and method member names next to their mapped COBOL names. They can click hyperlinks within the mapping view to navigate directly back to the COBOL source code files for comparison.
    • Updated the watsonx Code Assistant for Z tree view to show a breakdown of method members per Java class that can be generated by the assistant's AI component. These methods are based on COBOL section and paragraph names and become available after the initial Java class generation step has been completed.
    • Updated the watsonx Code Assistant for Z tree view to support a new workflow for reopening saved COBOL-to-Java mappings and regenerating Java code.
    • Updated the watsonx Code Assistant for Z tree view with new icons and icon decorators that visualize which Java members mapped from COBOL paragraphs have already been generated and which not.
    • Updated error handling, error message dialogs, and log file messages.
    • Fixed the issue of the Welcome page checkbox for enabling/disabling watsonx Code Assistant for Z not being synchronized with the respective user setting.
     3.3.3 - 2023/12/15
    • Fixed the issue for COBOL where SKIP1, SKIP2, SKIP3, and EJECT tokens were not being handled correctly when placed within other statements to control white space. (Issue 307open in new window)
    • Fixed the issue where conditional compilation statements were not being handled correctly when placed in a >>WHEN OTHER phrase. (Issue 366open in new window)
    • Fixed the issue where the COBOL parser could hang or crash when a file's final line ended with a character in column 7.
    • Fixed the issue where a language server would start before all ZAPP files were processed missing settings such as compiler options. (Issue 364open in new window)
    • Fixed the issue where the RSE API plugin for Zowe CLI command to upload a file to a UNIX System Services directory would show an error.
    • Various bug and serviceability fixes as well as UI refinements for IBM watsonx Code Assistant for Z. Generate Java classes now by using the icon next to the COBOL program name or by using the context menu. When entering an API key you will now receive a confirmation message after a server-side validation check.
     3.3.2 - 2023/11/28
     3.3.1 - 2023/11/07
    • Corrected the default URL for the IBM watsonx Code Assistant for Z server setting.
     3.3.0 - 2023/10/25
    New: IBM watsonx Code Assistant uses generative AI to accelerate code generation and increase developer productivity for application modernization. IBM watsonx Code Assistant for Z is now enabled in IBM Z Open Editor to drive the selective and incremental transformation of COBOL business services into well-architected high-quality Java code. It uses the inventory and analysis tools of IBM Application Discovery and Delivery Intelligence (ADDI) to support development teams in refactoring business services in COBOL, transforming COBOL code to Java code, and validating the resulting outcome. Learn more and sign up for a trial at https://www.ibm.com/products/watsonx-code-assistant-zosopen in new window.
    Other fixes and enhancements in this release:
    • Added support for CICS v6.2 Beta to COBOL and PL/I language servers.
    • Added support for line and block comment shortcuts in PL/I and REXX.
    • Machine instruction statements in HLASM are now identified when the number of operands is incorrect. Assembler instructions are not supported at the moment.
    • Improved the parsing behavior of HLASM language servers, particularly around continuation lines. Symbols that are continued should now have that reflected when you hover over references. Symbols that are used in continuation lines now support language functionalities, such as hover, Go to Definition, and Find References.
    • Fixed the bug where lowercase and mixed-case macros were not correctly displaying document links in HLASM.
    • Added support for internal macros that are declared in an HLASM file. Macros that are declared in an HLASM file now support code completion, hover, and Go to Definition in the file. Note that macros declared with the same name as a default SYS1.MACLIB macro will take precedence over the default macro.
    • Added .mac as another default file extension for HLASM program files.
    • Improved syntax highlighting around %INCLUDE statements in REXX.
    • A ZAPP file will now be automatically generated if none can be found in any of your workspaces when a COBOL, PL/I, HLASM, or REXX file is opened for the first time. This ZAPP file will search in all your local folders for include files, such as copybooks, so you should modify it for a more specific path or remote MVS locations afterwards. This behavior can be disabled with the new user setting "zopeneditor.zapp.generateZappOnDemand". Include file statements in all of these languages now also have the Quick Fix menu entry to open ZAPP files for troubleshooting and to open the ZAPP documentation for quick reference.
    • Changed the behavior of the "Run user build with full upload" command to now upload also all files that are specified with additionalDependencies in the ZAPP file. (Issue 297open in new window)
    • Fixed the issue where user build did not properly filter search results for logs. (Issue 353open in new window)
    • Fixed the issue where user build related editor menu items and command palette items were displayed for COBOL and PL/I include files.
    • Fixed the issue where user build menu items and command palette items were not displayed for VS Code 1.76 and earlier versions. (Issue 349open in new window)
    • Fixed the issue where user build did not handle SSH keys for authentication in Zowe SSH profile. (Issue 355open in new window)
    • Fixed the issue with RSE API in Zowe Explorer where the user was prompted for username and password when using a token for authentication.
    • Added the ability to change owner, group, and permissions of Unix files on RSE CLI.
    • Added the ability to check a user's password expiration date with RSE CLI.
    • Fixed the issue where default RSE profiles were not displayed by default in Zowe Explorer's tree views when the team configuration profile did not contain z/OSMF profiles.
    • Added functionalities for RSE profiles, including copying files and directories in z/OS UNIX System Services, copying data sets, and cancelling jobs.
    • Added support for editing attributes in z/OS UNIX System Services for RSE profiles in Zowe Explorer.
    • Fixed the issue where RSE API Plug-in for Zowe CLI returned duplicate values when executing the list all members command using wildcard pattern parameters.
    • Fixed the issue where RSE API Plug-in for Zowe CLI did not return the correct error messages when executing the list or download all members command using incorrect parameters.
    • Fixed the issue where the Zowe profile status bar was not updated after edits were made to the team configuration profiles for RSE API profiles.
    • Added job timestamp to the output of the list jobs command for RSE API Plug-in for Zowe CLI when running commands against RSE API server v1.1.3.
     3.2.3 - 2023/10/11
    • Fixed the issue where Z Open Editor showed an incorrect warning about initializing secure credentials. (Issue 359open in new window)
    • Fixed the issue where RSE API profiles that were using token-based authentication stored token details incorrectly in certain situations.
    • Fixed the issue where building projects that were not managed with Git produced Git errors. The fix changes the behavior that when no Git repository can be found then all .gitattributes files are ignored.
     3.2.2 - 2023/09/15
    • Fixed the issue in COBOL where DEFINE(compilation-variable-name) was not applying the default value B'1'. (part of Issue 154open in new window)
    • Fixed the issue in COBOL where COBOL keywords are not able to be used as compilation-variable-name before a >>DEFINE statement. (part of Issue 154open in new window)
    • Fixed the issue where IBM User Build was not properly filtering search results for logs. (Issue 353open in new window)
    • Fixed the issue where RSE API plugin for Zowe CLI returned duplicate values for list all members.
    • Fixed the issue where the Zowe profile status bar field would not get updated after making edits to RSE API profiles in team configuration files.
    • Security fix limiting telemetry data volumes.
     3.2.1 - 2023/07/19
    • Added syntax and content assist support for the LOCATION options (LOC24 and LOC31) in the GETMAIN64 EXEC CICS embedded CICS command.
    • Fixed the issue where the PL/I PROCESS MAR/MARGIN options did not accept a third parameter. (Issue 344open in new window)
    • Fixed issues in the HLASM outline view to correctly handle duplicate elements such as CSECTS and DSECTS that are continued. Symbols that are reassigned will still point to the final declaration to prevent the outline from becoming overcrowded.
    • Fixed the issue in User Build where menu items and commands were not available when VS Code 1.76 or earlier versions were used. (Issue 349open in new window)
    • Fixed the issue in User Build for COBOL and PL/I where a copybook or include file with a name that was a substring of another copybook or include file name was not identified as a dependency correctly.
    • Fixed the issue that prevented the default RSE API Zowe CLI profiles to be displayed in Zowe Explorer's tree views at startup when Zowe team configuration profile files did not contain a z/OSMF profile.
     3.2.0 - 2023/06/16
    • Added support for the COBOL v6.4 April 2023 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this blog postopen in new window for details.
    • Fixed the coloring of the keyword NOT in COBOL. (Issue 328open in new window)
    • Fixed the missing syntax errors when statements (such as COPY) start to the left of Area A and overflowing data names (for example in USING statements) start to left of Area B. (Issue 340open in new window)
    • Fix the issue where comments were misinterpreted within a COPY statement when using an empty quoted pseudo text and the == identifier. (Issue 248open in new window)
    • Removed the ability to perform Number and Unnumber actions when COBOL Language Server is not running. (Issue 189open in new window)
    • Fixed certain COBOL words not highlighting correctly when placed at the end of a line. (Issue 346open in new window)
    • Added support for the PL/I v6.1 March 2023 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this blog postopen in new window for details.
    • Fixed the issue that caused PL/I comments to show a report when starting in column 1. (Issue 135open in new window)
    • Fixed the issue with PL/I code completion when a variable is in the same column with a DCL statement.
    • Added preview hovers and clickable hyperlinks to open include files in REXX.
    • Added support for jump targets as well as RSECT, LOCTR, and COM control sections in the HLASM outline view.
    • Fixed the issue where preview hovers failed to load for HLASM COPY statements when the copied document was closed after previously being opened by using the hover's hyperlink.
    • Added the user settings "zopeneditor.<language>.disableProblems" for each language to enable/disable the Problems view and syntax errors shown within the editor while maintaining other language features. It will allow users to continue working in the program with some language features despite parsing issues. This will not work in all circumstances as some syntax errors will also break other language features. (Issue 199open in new window and Issue 203open in new window)
    • Added the ability to define custom ZAPP variables in your personal user or workspace settings. Define variables in a new mappings table under zopeneditor.zapp.variables in the VS Code settings editor and then reference them in your ZAPP files with ${variable-name}. For example, define a variable here called HLQ with a value that represents your personal high-level qualifier on z/OS MVS. In your ZAPP file, reference it in a property group's location entry, such as ${HLQ}.COBOL.COPYBOOKs.
    • Fixed a copybook and include file watcher limitation about file precedence in remote and local non-syslib libraries.
    • Added the user setting "zopeneditor.zowe.maximumParallelFileDownloads" to specify how many parallel downloads Z Open Editor should perform when requesting include files from MVS. This will help minimize address spaces being allocated by z/OSMF. The default value of the setting is 5, and the maximum value is 10. Set it to 1 to disable parallel downloads. (Issue 134open in new window)
    • Added the user setting "zopeneditor.zowe.listBeforeDownload" to enable Z Open Editor to first search for the existence of a data set member before trying to download it when resolving include files. This will slow down performance, but will cause less logging on z/OS when using z/OSMF. The default is off to preserve performance. (Issue 134open in new window)
    • Fixed the issue where COBOL copybook requests were not sent in parallel in certain cases where Unix-style line endings were used on Windows.
    • Fixed the issue where COBOL and PL/I include file requests were sometimes sent twice if a document could not be found.
    • Fixed the issue that language server errors and exceptions caused by a timing issue are displayed. (Issue 332open in new window)
    • Fixed the issue where COPY or INCLUDE statements using custom libraries were in some cases resolved with syslib libraries.
    • Improved the folder watching performance. When folders within the scope of the current ZAPP property groups are deleted or created, open program files will be re-parsed instead of a complete extension restart.
    • Added the ability for User Build to automatically run the git check-attr command in the background to evaluate .gitattributes in any folder of the workspace to upload files to UNIX System Services with the correct file encoding. If Git is not installed or cannot be found by the editor, Z Open Editor will continue trying to evaluate encoding itself. (Issue 331open in new window)
    • Fixed the issue in User Build where files specified in a ZAPP file as additionalDependencies were not converted and tagged correctly when being uploaded to UNIX System Services.
    • Fixed the issue where User Build failed to run when dbbLogDir does not exist on UNIX System Services.
    • Added a warning message to the User Build output view to inform the user when the language server is stopped, because the language server will then not be able to compute dependencies such as copybooks and cannot upload them to z/OS.
    • Fixed the issue where User Build would not download any log files when the logFilePatterns property was not specified in the ZAPP file. Added a default that will download all files that match the pattern *.log.
    • Fixed an issue where user build menu was not always hidden when user build was disabled via settings. (Issue 347open in new window)
    • Fixed an issue where ZAPP and ZCodeFormat code snippets would not show when editing in multi-root workspaces.
    • Updated dependencies for security audits.
    • Added support for JCL symbols as a parameter for jobs on RSE CLI.
    • Fixed an issue when saving files to z/OS with Zowe Explorer using RSE API and resolving conflicts with changes done by other users to the same file. VS Code will now properly show the conflicts in its differences editor allowing you to merge and save.
     3.1.1 - 2023/03/30
    • Fixed an issue with COBOL language code completion where code completion was not working on the first line of a COBOL file.
    • Added support for $ and </> to be used as pseudo-text boundaries for the REPLACING strings in COBOL copybooks. (Issue 305open in new window)
    • Fixed an issue where COBOL literals were not being highlighted correctly when single quotes and double quotes were mixed. (Issue 308open in new window)
    • Fixed an issue where the connection to the language server got disposed showing errors in the output view. (Issue 332open in new window)
    • Fixed an issue where COBOL copybook requests did not download remote copybooks in parallel for non-syslib libraries.
    • Fixed an issue with .gitattributes where * could not be used as a pattern for encoding the selection of files. (Issue 331open in new window)
    • Fixed an issue where the Zowe team configuration's encoding property was not used when no .gitattributes file was present or no match was found. (Issue 331open in new window)
    • Fixed an issue where User Build on Windows uploaded remote copybooks to USS. (Issue 333open in new window)
    • Updated Zowe and third-party dependencies addressing security scan results.
     3.1.0 - 2023/03/10
    • Added support for the PL/I v6.1 October 2022 Refresh with updated syntax highlighting, outline view, real-time syntax checking, and other language related features. See this blog postopen in new window for details.
    • Added support for using comma in the DEFINE compiler option syntax for COBOL. (Issue 278open in new window)
    • Added code completion support for statements containing Unicode Strings in COBOL.
    • Added code completion support for Compiler Directing statements (Compiler Options) in COBOL.
    • Added code completion support for ENABLE PROGAM in EXEC CICS Statements in COBOL.
    • Fixed an issue with COBOL where CBL or PROCESS service directive was not being recognized. (Issue 253open in new window)
    • Fixed an issue with COBOL language showing false syntax errors for not correctly handling condition expressions on compilation variables in boolean format compared with the constant b'0' or b'1'. (Issue 321open in new window)
    • Reverted syntax highlighting changes from last release for unsupported Boolean literals (b and bx). The IBM COBOL compiler currently does not support them. (Issue 308open in new window)
    • Added new option alignToClauses to zcodeformat.yaml files to support aligning TO clauses, aligning INTO clauses, and aligning TO clauses into column.
    • Added file watching support for all languages so that programs with INCLUDE and COPY statements are now automatically re-parsed when local included files or copybooks are edited, created, or deleted. (Issue 108open in new window). See Known Issuesopen in new window for a limitation involving file precedence in remote and local non-syslib libraries.
    • Improved performance for loading PL/I include files. Include files that are being downloaded from a remote z/OS system will now resolve much faster as download requests are performed in parallel to a maximum of five files at once. (Issue 269open in new window)
    • Significantly improved performance for searching for local copybooks and include files via property groups that use glob patterns that expand to many results. (Issue 315open in new window, Issue 293open in new window)
    • Fixed an issue with no hover content of the copybook when COBOL source contains any errors in the COBOL program. (Issue 300open in new window)
    • Fixed a bug where large copybooks and include files were not completely resolved, resulting in errors such as Unable to resolve reference to variables included from copybooks. (Issue 313open in new window)
    • Fixed a bug when editing REXX programs with remote REXX include files, which were resolved and saved with an incorrect file extension.
    • Full support for all the new Zowe Explorer JES filtering options when using RSE API profiles.
    • Fixed issue where user build logs in nested directories were not being found (Issue 296open in new window).
    • Updated the user build output view and log file formatter to include timestamps when Z Open Editor's log level (zopeneditor.logger) is set to DEBUG to help with trouble-shooting and measuring build times. (Issue 292open in new window)
    • Added support for path name specification for .gitattributes in IBM User Build.
    • Added new option for tagging files using working-tree-encoding os=zos in .gitattributes in IBM User Build as an alternative to zos-working-tree-encoding.
    • Addressed a concern that code snippets for ZAPP and ZCodeFormat files appeared in the code completion for all YAML files being edited. We therefore removed them from the Snippet Gallery and provided them as pure context-sensitive code completion items for <ctrl-space>.
    • Z Open Editor is now available to install as a web extension with limited capabilities when using Visual Studio Code in a browser, such as vscode.dev or github.dev. Try it by going to https://vscode.dev/github/IBM/zopeneditor-sampleopen in new window and confirming to install the recommended extensions.
     3.0.1 - 2023/01/18
    • Performance improvements for loading COBOL copybooks. Copybooks that are being downloaded from a remote z/OS system will now resolve much faster as download requests are performed in parallel to a maximum of five files at once. PL/I will be updated with this capability in a later release. (Issue 269open in new window)
    • Fixed invalid "REDEFINES clause must begin in Area B" error shown in COBOL editor when using the REPLACING clause with a REDEFINES. (Issue 287open in new window)
    • Fixed issues with COBOL syntax highlighting when using literal delimiters. Respective language server fixes will be provided at a later date. (Issue 308open in new window)
    • Fixed spelling in COBOL code snippets. (Issue 286open in new window)
    • Fixed issue with %Replace in PL/I when using a minus sign in expression. (Issue 299open in new window)
    • Fixed an issue in User Build evaluating file names with special characters, such as $, in command shell expression. The DBB Daemon might also be effected by this problem. Remove the -DBB_PERSONAL_DAEMON command line parameter from the ZAPP file if you still run into this problem. (Issue 288open in new window)
    • Fixed an issue with User Build not downloading log files for programs with lower or mixed case filenames, because dbb-zappbuildopen in new window will automatically capitalize log file names. User Build will now also automatically capitalize the build file name when using the ${buildFile.basename} variable under logFilePatterns in the ZAPP file.
    • Fixed syntax error in ZAPP code snippet for the dbb user build profile.
    • Fixed issues in our RSE API support when using special characters in z/OS file or directory names.
    • Fixed bugs and improved the usability of the change password command in the IBM RSE API Plug-in for Zowe CLI.
    • Fixed error being thrown in Zowe Explorer when RSE API list of all members returns no members.
     3.0.0 - 2022/11/22
     Breaking Changes
    For more details on breaking changes and the required manual migration steps see our user documentationopen in new window.
    • Z Open Editor now requires as a minimum a Java 11 runtime for running language servers. Users must upgrade their installed Java 8 runtime or Z Open Editor's language capabilities will not be available. See the documentationopen in new window for the recommend Java Runtime Environments that you can use.
    • ZAPP files are now replacing various user settings and cannot be disabled enabled anymore. The user setting "zopeneditor.zapp.enabled" has been removed.
    • Property Groups have been removed from VS Code user and workspace settings. The setting "zopeneditor.propertygroups" is no longer available. Users must now use ZAPP files for specifying locations for include files. When only using Zowe Explorer to edit program files you need create a workspace folder with a ZAPP file as well.
    • Property Groups have been updated to contain references to local files as well as remote MVS files in the same property group item applying the same compiler options to each. The schema for a property group item has changed and users must update their ZAPP files. Please, check the documentationopen in new window for the details and our migration pageopen in new window for how to upgrade.
    • User Build settings have been updated to allow more configuration options such as allowing glob patterns to define files for uploading and downloading. See the IBM Wazi for VS Code User Build documentationopen in new window for more details.
     Other changes and fixes
    • Fixed syntax of EXEC CICS INQUIRE SYSTEM MAXOPENTCBS. (Issue 257open in new window)
    • Added missing CICS v6.1 INQUIRE SYSTEM options: SRRTASKS, MEMLIMIT and MQCONN that used to cause syntax errors.
    • Fixed CICS v6.1 EXEC CICS CREATE DB2ENTRY ATTRIBUTES option incorrectly flagged as an error.
    • Fixed CICS v6.1 EXEC CICS SET TAGS REFRESH with NOHANDLE and RESP options incorrectly flagged as an error.
    • Fixed an issue in COBOL syntax checking for a working storage variable starting with REMARKS. It would be incorrectly identified as a REMARKS paragraph. (Issue 276open in new window)
    • Fixed an issue with COBOL Syntax Highlighting in the sequence number fields (1-6 and 73-80). (Issue 193open in new window)
    • Fixed a NullPointerException caused by the PL/I Code Folding feature when opening copybook/include file from PL/I Editor. (Issue 277open in new window)
    • Fixed a NullPointerException caused by the PL/I Code Folding feature when the currently selected word matches a code completion suggestion that would alter the outline view. (Issue 283open in new window)
    • Fixed an issue with syntax checking for PL/I related to function parameters of type File as well as a DEFINE ORDINAL containing signed integers in the VALUE attribute.
    • Added REXX syntax highlighting for matching pairs of parenthesis. Auto-close parenthesis when typing.
    • Fixed an issue with improper error logging regarding the list command in RSE CLI.
     2.2.0 - 2022/09/20
    • Fixed User Build and the RSE API CLI's upload command to correctly encode file names with special characters. Files such as "T@A#R$C" will now be correctly uploaded to USS. (Issue 266open in new window)
    • Performance improvements for the REXX language server via parser optimizations. (Issue 256open in new window)
    • Updated the REXX hover hyperlinks to point to the z/OS 2.5.0 reference.
    • Improved performance and reliability for the HLASM language server by implementing cancellation support for requests that are no longer valid, as well as optimizing handling of document-link requests for macros.
    • Fixed a bug where mixed case variables were not handled correctly in HLASM.
    • Fixed a bug where hovers sometimes did not show the correct code snippet for SYS1.MACLIB macros in HLASM.
    • Fixed a bug where document link underlines were not showing for HLASM macros when a file is first opened. Similar to a problem fixed for COBOL in (Issue 81open in new window) and (Issue 114open in new window).
    • Fixed a bug where "Failed to fetch COPYBOOK" errors were causing slowdowns across the HLASM language server.
    • Added initial support for code folding for control statements to the PL/I language server.
     2.1.1 - 2022/08/14
    • Added support for running User Builds with nested copybooks for COBOL. Issue 251open in new window
    • Fixed User Build issues with credential dialogs and storing credentials for remote include file resolution using z/OSMF or RSE API. (Issue 245open in new window, Issue 255open in new window)
    • Fixed User Build issues with credential dialogs and storing credentials for SSH commands when using z/OSMF.
    • Fixed User Build issues when attempting to build from workspaces with spaces in the file path. (Issue 252open in new window)
    • Fixed various issues when using ZAPP and User Build in a multi-root workspace. You can now use multi-root workspaces as long as you use a single ZAPP file and provide it together with the application-conf folder in the same workspace as your program. Include files such as copybooks can be in many other multi-root workspace folders. The ZAPP file needs to specify property groups with a workspace folder relative path even for include files located in other workspaces. User Build with user settings in multi-root workspaces is not supported. Please, switch to ZAPP files. See our Sample GitHub repositoryopen in new window for more details and a examples for single-root workspaces, in the wazi-main branch as well as multi-root in the multiroot folder of the wazi-main branch. Also note, that for single as well as multi-root the value for the DBB buildScriptArgs parameter has changed for the --application parameter to be now just a relative path to the application-conf directory. So in most cases you can just use --application ., which makes it much easier as you do not have to provide the folder name of your workspace root in the ZAPP file anymore. Finally, the zopeneditor.userbuild.userSettings.localWorkspacePath user setting has been deprecated is not used anymore.
    • Fixed an issue in the Z Open Editor output log not always reporting the correct Zowe profile management version in use.
    • Fixed issue in the COBOL Code Formatter producing incorrect Area B alignments for USING statements.
     2.1.0 - 2022/06/14
    • Added language support for COBOL v6.4, PL/I v6.1, and CICS v6.1 with updated syntax highlighting, outline view, real-time syntax checking, and other language related features. See our documentationopen in new window for details. (Issue 240open in new window)
    • Added COBOL UTF-8-specific syntax elements in textmate grammar (Issue 241open in new window)
    • Added an experimental COBOL code formatter that can be configured similar to Prettier with a yaml or json file. Find more details in our documentation (Issue 31open in new window)
    • Updated HLASM Instructions to match the set that was shipped with IBM z16.
    • Updated HLASM Macros to match the z/OS 2.5 SYS1.MACLIB. Switch the z/OS version back to 2.4 SYS1.MACLIB by using the user setting zopeneditor.hlasm.zosMacrosVersion.
    • Added .macasm and .copyasm as default file extensions for HLASM. (Issue 220open in new window)
    • Added .bms as default file extensions for HLASM. (Issue 223open in new window)
    • Fixed an error in the Problems View when a custom-defined problemMatcher was used when compiling HLASM code. (Issue 230open in new window)
    • Various fixes and refinements for HLASM syntax highlighting.
    • Added REXX include file support consistent with the other languages using Property Groups in ZAPP files. (Issue 172open in new window)
    • Added a status bar item that displays the currently active Zowe profile used by Z Open Editor for remote include file resolution and IBM User Build. (Issue 165open in new window)
    • Added support to filter the information displayed in the RSE CLI plugin command zowe rse check jobs that displays all active job address space information. This functionality is available in RSE API v1.0.9.
    • Added support for use of passphrase in change password command with RSE API v1.0.9.
     2.0.3 - 2022/05/20
    • Fixed a synchronization issue that when saving syntactically correct ZAPP files the editor sometimes would still report errors.
    • Fixed an issue in User Build related to file upload operations in which Z Open Editor would not evaluate the .gitattributes file correctly, not following the Git standard for precedences. (Issue 236open in new window)
    • Updated how User Build parses .gitattributes files dealing with more file formats such as Windows CRLF files and added more logging for the encoding matches found or not found. (Issue 235open in new window)
    • Added support for using the ZOWE_CLI_HOME environment variable to specify an alternative location for global team configuration files to Zowe Explorer 2.0.2 and Z Open Editor. (Issue 238open in new window)
    • Fixed various errors that prevented Zowe Explorer and Z Open Editor to run in Eclipse Che especially plugin containers with Nodejs 12. You can use these extensions now with secure credentials disabled as documented hereopen in new window.
     2.0.2 - 2022/04/25
    • Added full support for Zowe 2.0 in particular Zowe Explorer 2, Zowe CLI 7, Zowe API Mediation Layer 2. You can continue using your Zowe CLI 6.x profiles for backwards compatibility, but you must update Zowe Explorer to version 2 to do so. Review our Getting Started with Zowe 2.0 section in the Z Open Editor user documentation or the Zowe CLI documentation for how to migrate your 6.x profiles to the 7.x format.
    • Added support for auto-init of Team config files to the IBM RSE API Plugin for Zowe CLI. Use it when you have you RSE API host component registered with the API Mediation Layer.
    • Switched the minimal required version of Node JS for IBM RSE API Plugin for Zowe CLI to version 14 as version 12 is out of support now.
    • Added user setting zopeneditor.server.startupOptions for providing custom Java startup options for language servers. Can be used with tech support for troubleshooting.
     2.0.0 - 2022/03/15
    Z Open Editor is released as major version update to 2.0 to celebrate its availability in IBM Wazi Developer for Workspaces 2.0 that is now part of the IBM Z and Cloud Modernization Stack and fully supports running on OpenShift on Linux on Z. Note that because Zowe 2.0 was delayed to late April 2022, Z Open Editor has to be updated to support it once Zowe has been released. Other fixes and enhancements in this release:
    • Added missing DEBUG-ITEM variables in the COBOL language server. (Issue 156open in new window)
    • Added missing JNIENVPTR and JSON-STATUS variables in the COBOL TextMate grammar and the COBOL language server. (Issue 156open in new window)
    • Fixed an issue in the COBOL language server not supporting a mixed case spelling of SQLCA and SQLDA. (Issue 208open in new window)
    • Fixed an issue in the COBOL language server where the Rename Symbol feature was not renaming symbols that were spelled using a different character casing.
    • Fixed an issue in the COBOL TextMate Grammar making the SCREEN keyword case insensitive.
    • Fixed an issue in the COBOL language server where parsing failed because of period in column 72 and standard sequence numbering present in the program. (Issue 202open in new window)
    • Fixed an issue in the COBOL Language Sever where parsing failed with invalid error message in COPY REPLACING statements. (Issue 181open in new window)
    • Performance and reliability improvements for the COBOL and PL/I language servers by implementing cancellation support for requests that are no longer valid as well as optimizing handling of document-link requests for include files.
    • Added new options to the truncation warning dialog for COBOL, PL/I, HLASM, REXX, and JCL files in Z Open Editor. Also, if only whitespaces are truncated the editor will not prompt anymore, it will just remove them automatically.
    • Fixed an issue in the PL/I language server where hover content for include files were not rendering in the correct format. (Issue 211open in new window)
    • Fixed an issue in the HLASM language server where NullPointerException were logged while rendering hovers after a document change.
    • Fixed an issue where HLASM syntax highlighting was not correctly recognizing sequence numbers at the end of lines (Issue 192open in new window).
    • Fixed an issue in the REXX language server where a trailing comma in a function parameter resulted in a syntax error.
    • Improved the REXX language server performance and stability when editing large files.
    • Z Open Editor and Zowe Explorer now share the profiles loaded into memory via the Zowe Explorer Extensibility API. Now if you make changes to a profile in Zowe Explorer or use the Reload button to load changes from disk done via CLI, the changes will be immediately visible to Z Open Editor without the need to run "Reload Zowe profiles" from the command palette. This command now performs the same operation as clicking the Zowe Explorer Refresh button.
    • Made the Zowe connection test in Z Open Editor more robust and fixed the issue of tests timing out for slow connections. (Issue 197open in new window)
    • Fixed an issue preventing submission of JCL in Zowe Explorer via command palette option "Zowe Explorer: Submit JCL" using RSE API CLI Zowe profiles.
    • Fixed an issue with token and base Zowe CLI profiles support for MVS connection tests for remote file resolving.
    • Added RSE API Zowe profile login and logout support for JSON Web Token authentication with the RSE API through Zowe Explorer.
    • Improved working with interactive TSO commands for RSE API Zowe profiles by adding the TSO command tag shell-id, that can be used with RSE API server v1.0.8.
    • User Build now works with Zowe CLI profiles that do not store credentials. User will be prompted to provide them when the build starts.
    • Adopted the latest version of dbb-zappbuildopen in new window for User Build that now considers file tags for processing. The JSON dependency file will now be uploaded as a UTF-8 file. If you are using an older version of dbb-zappbuild, please update with the latest changes from its main branch on GitHub.
    • Fixed an issue that would show the command IBM User Build: Run IBM User Build for files with unsupported languages in the command palette.
    • Fixed an issue that prevented recognizing ZAPP files running in Eclipse Che when workspaces folders were added or removed.
    • Reviewed and revised multiple user interface strings and dialogs.
    • Updated code samples in https://github.com/IBM/zopeneditor-sample/tree/wazi-mainopen in new window with Ansible playbooks and host variables for IBM Wazi Sandbox and the IBM Wazi as a Service tutorials.
     1.4.1 - 2021/11/19
    • Fixed an issue with COBOL syntax highlighting of reference modifications (Issue 177open in new window)
    • Fixed the VS Code Toggle Line Comment (Cmd-/ or Ctrl-/) command for COBOL. You can now use it with the cursor being placed anywhere in the line as well as select a whole block of code and set or remove the comment symbol as a toggle. (Issue 157open in new window)
    • Fixed several issues with HLASM syntax highlighting related to continuation lines, macro definitions, and substitution characters. (Issue 118open in new window, Issue 185open in new window). See our Known Issuesopen in new window page for problems not solved, yet.
    • Fixed various inconsistencies with the HLASM outline view. It will now show the first occurrences of CSECTs, DSECTs, MACROs, Branch Targets, and Labels. (Issue 148open in new window). See our Known Issuesopen in new window page for problems not solved, yet.
    • Enhanced HLASM outline view to now display all labels. See Customizing the outline viewopen in new window to change what is included in the outline view.
    • Added support to use all REXX keywords as variables, excluding the 'END' keyword as well as improved the readability of keyword-related syntax error messages.
    • Fixed an issue in which trying to load remote include files from MVS using an invalid Zowe CLI Profile password could lock user accounts due to too many failed attempts. Z Open Editor will now prompt for a new password to update the profile or allow canceling all requests. This fix also adds support for using Zowe CLI profiles that do not store credentials and you will be prompted when required. (Issue 142open in new window)
    • Fixed an issue that prevented switching from Z Open Editor language servers to other languages. (Issue 164open in new window)
    • Fixed a regression in which a ZAPP file was not found when using it in an IBM RSE API for Zowe CLI command parameter or in Z Open Editor when specifying a file with zopeneditor.zowe.defaultRseConversionMappingsFile that was not in the current workspace.
    • Fixed an issue with User Build where dependencies would not upload again after making a change inside VS Code settings or ZAPP file settings.
    • Fixed an issue with User Build where remote dependencies were being uploaded on Windows.
    • Enhanced User Build messages to be more informative and actionable.
    • Fixed security related logging issue.
     1.4.0 - 2021/10/29
    • You can now use User Build without SSH when using IBM RSE API for Zowe CLI profiles. SSH Zowe CLI profiles are now required by z/OSMF only.
    • User Build speed is increased by sending additional dependency and metadata information to IBM Dependency Based Build on z/OS. Check the documentation for new dbb-zappbuild build script arguments.
    • When you save user or workspace settings, Z Open Editor will recognize and reload all Zowe CLI profiles, which is particularly useful when you add new profile names to the zopeneditor.zowe setting.
    • Support for ZAPP files with Z Open Editor is now also available when running in Eclipse Che, Red Hat CodeReady Workspaces, and IBM Wazi Developer for Workspaces.
    • Startup performance is faster with a smaller memory footprint due to significantly reduced language server sizes.
    • You can use the IBM Debug for z/OS High Level Assembler debug listing files with the language ID hlasmlst and the default file extension langx.
    • Fixed an issue in which a newly created ZAPP file was not recognized until the editor restarted.
    • Enhanced some UI strings for effectiveness including menus and Preferences names and descriptions.
    • New commands are added to IBM RSE API for Zowe CLI: 
      • zowe rse create data-set --like: Allocates a new data set with the same attributes as an existing data set specified by the --like option in IBM RSE API for Zowe CLI. The allocate-like functionality can now also be used with RSE profiles in Zowe Explorer. To use this feature, RSE API server 1.0.7 or later versions are required.
      • zowe rse check system-address-space: Displays all active system address space information in RSE CLI plug-in. To use this feature, RSE API 1.0.5 or later versions, and IBM Explorer for z/OS 3.2.0.16 or later versions are required.
      • zowe rse check job-address-space: Displays all active job address space information in RSE CLI plug-in. To use this feature, RSE API 1.0.5 or later versions and IBM Explorer for z/OS 3.2.0.16 or later versions are required.
     1.2.6 - 2021/08/19
    • Fixed an issue with PL/I compiler options for margins not being interpreted correctly in the editor. (Issue 135open in new window)
    • Fixed an issue that encoded special characters incorrectly in include file hovers for all languages. (Issue 128open in new window)
    • Fixed issues with HLASM code completion not appearing correctly in continuation and empty lines. (Issue 118open in new window)
    • Various fixes and improvements for REXX: 
      • Fixed issues with handling multi-line strings correctly for REXX.
      • Made code completion in REXX case-sensitive so that it preserves the casing style the user was using before initiating completion requests with Ctrl+Space.
      • Added an editor ruler at column 80 in REXX files. All editor rulers are customizable through the settings.
      • Added truncation warnings for characters after column 80 in REXX files. The column number is customizable through the settings.
      • Various REXX refinements that improve stability and performance of parsing and error messages.
    • Fixed an issue in IBM RSE API for Zowe CLI that prevented the use of the correct encoding for file uploads to USS, which also impacted uploads via Zowe Explorer using an RSE API profile. This fix requires Zowe Explorer 1.18.0 or newer.
    • Fixed an issue in User Build that prevented the use of the correct encoding as defined in .gitattributes to files uploaded via z/OSMF or RSE API profiles.
    • Addressed the user request to allow the zopeneditor.zowe settings to be scoped for workspace settings. This will be useful for development teams who standardize the names of their Zowe CLI profiles for their projects and use them for build automation. (Issue 143open in new window)
    • Adopted the new Zowe Explorer zowe.files.temporaryDownloadsFolder.cleanup setting to support the use of multiple VS Code windows showing the same files opened via Zowe Explorer, in order to see different parts of the same program on two different screens. Note that disabling the cleanup will result in files downloaded from z/OS not being removed when the editor is closed or restarted, so when you open a file via Zowe Explorer you may be viewing an outdated local version. Use the right-click "Pull from Mainframe" command to ensure you are working with the latest files.
    • Adopted new Zowe Explorer APIs that require Zowe Explorer 1.15.0 or newer to be installed. This release has been tested with Zowe Explorer 1.18.0.
     1.2.5 - 2021/06/18
    • Refined COBOL Renumber and Unnumber support making it configurable to work with columns 1-6 or 73-80 or both. If content other than numberic values is already present in these locations in a specific row then it will not update that location to preserve the content. (Issue 8open in new window)
    • Fixed syntax highlighting for HLASM beyond column 16. There is still an issue with code completion that well be addressed in a later release. (Issue 118open in new window)
    • Improved performance and reliability of downloading larger numbers of include files such as SYS1.MACLIB macros for the HLAMS editor hovers.
    • Removed the performance warning dialog for property groups and replaced it with log messages (Issue 15open in new window)
    • User Build now writes its output into a separate log file for users to share and analyze.
    • Adoption of new Zowe Explorer API ICommand to allow issuing of TSO commands using RSE profiles via Zowe Explorer 1.14.0 and higher.
    • RSE CLI plug-in updates: 
      • RSE CLI plug-in now prompts user for credentials for RSE profiles without user and password, during zowe rse auth login command to obtain JWT token, and if RSE API token is expired to obtain new token.
      • Fixed a regression that broke uploading a file as a sequential data set.
     1.2.1 - 2021/04/21
    • Made various improvements to our REXX language server and fixed defects: 
      • Added support for nested comments in REXX
      • Added support for keyword instructions as variables in REXX (excludes DO, IF, PARSE, SELECT, TRACE).
      • Fixed a find references bug in REXX where variables and functions with the same name matched
      • Fixed a find references bug in REXX where keywords could be used to find references
      • Refined the hover content and code completion detail in REXX to make the information more concise
      • Updated the hover content in IBM Documentation to point to the new IBM Documentation pages for the z/OS 2.4.0 TSO/E REXX Reference.
      • Standardized the syntax highlighting in REXX to color all keywords the same
      • Fixed a syntax highlighting bug in REXX where "value" following "address" was not displaying in color as a keyword
      • Fixed a syntax highlighting bug in REXX where the routine name following "call" was not displaying in color as a function
    • Reviewed and updated all output and log messages for the IBM RSE API Plug-in for Zowe CLI to ensure consistency. Locate the log file in ~/.zowe/zowe/logs/zowe.log.
    • Updated RSE API support for Zowe CLI base profilesopen in new window for the Zowe API Mediation Layer (APIML)open in new window Single Sign On (SSO) for User Build and using the RSE API behind the Zowe APIML. Refer to this new blog postopen in new window for an overview about how to use RSE API with the Zowe API Mediation Layer.
     1.2.0 - 2021/03/19
    • REXX language server: in this release we added language support for TSO/E REXX for z/OS. This first version includes syntax highlighting, syntax errors, code completion, find references, outline view, and rich documentation hover features. See our docs for all the details. (Issue 14open in new window)
    • Added full support for encoding conversions to/from UTF-8 to/from international EBCDIC code pages for all our z/OS MVS interactions that use RSE API 
      • Introduced a new mapping file concept to ZAPP as well as standalone JSON files that allow specifying mappings to groups or individual data sets or even members.
      • Added support for all RSE API CLI commands with new parameters as well as the ability to read mapping files that read and write to MVS.
      • All Z Open Editor remote MVS read operations using RSE API to find include files now can use mappings defined in ZAPP or user-local mappings files.
      • The Zowe Explorer integration with RSE API can also be configured to use mappings files for read and write operations of data set members.
    • Added EBCDIC conversion mappings for z/OS USS to User Build. Users can provide a standard .gitattributes file that specifies the encoding the program files should be converted to when uploaded to z/OS USS for a build.
    • Added context menus for COBOL with the ability to remove as well as renumber sequence numbers. (Issue 8open in new window)
    • Made include file resolution case-insensitive by default to support users with lowercase filenames and property group path names on local case-sensitive file systems such as Linux. As this can lead potentially to ambiguity problems we also added a new user setting called zopeneditor.enforceCaseSensitiveIncludeFileNames to enable case sensitive matching, even on case-insensitive operation systems such as Windows.
    • The command Reload Zowe Profiles that you can use when you changed your Zowe profiles, which was mainly introduced for User Build, now also restarts the language servers and retries loading any remote MVS include files with the updated profile information.
    • Added a new Welcome page for new users that interactively checks for prerequisites and gives tips for getting started.
    • Added support for APIML SSO for remote include file resolution such as COBOL Copybooks located on MVS. (Issue 107open in new window)
    • Fixed an issue in which invalid Zowe CLI profile configurations could cause Z Open Editor to not activate. We now show error messages and the editor is still usable. (Issue 110open in new window)
     1.1.3 - 2020/12/12
    • Fixed regression when resolving copybooks/include files with property groups that have multiple syslib/library entries. (Issue 105open in new window)
     1.1.2 - 2020/12/09
    • Added support for SYS1.MACLIB macros to HLASM for code completion. If you have a valid Zowe Explorer connection, it will even retrieve the macro definition automatically and show you in rich hovers when you typed or completed the macro name. Ensure that you enable this feature in user settings before using it.
    • Improved the way that Z Open Editor is looking for your Java Runtime or SDK. Review our updated documentation for the search order in which it tries to locate Java, as well as how you can override it with user settings. Added official support for Java Runtimes, and an SDK is not required anymore.
    • RSE CLI plug-in has added an encoding field that you can specify when creating or editing a Zowe RSE API CLI profile. You can use this field with newly added encoding tags for the commands of uploading and downloading MVS and USS files. Resolving copybooks will now use this encoding tag as well for RSE API and z/OSMF connections. (Issue 82open in new window)
    • RSE CLI plug-in now supports MVS binary downloads. (Issue 58open in new window)
    To update to RSE CLI plug-in 1.1.2, follow the instructions hereopen in new window for the optional migration.
     1.1.1 - 2020/11/6
     1.1.0 - 2020/10/23
    • ZAPP (Z APPlication) file support. Instead of mixing the configuration of your application with VS Code Preferences you can now specify property groups and IBM User Build configurations in a new simple yaml (or json) file located in your workspace that you can share with your team in Git. See our docs for a tutorial.
    • Added support for the Zowe CLI Secure Credentials Plugins for all Z Open Editor operations such as resolving include files or running user build (Issue 66open in new window)
    • Property Groups can now be scoped to one specific language making include file resolution more efficient as well as to support compiler options. (Issue 72open in new window).
    • Added the ability to provide language-specific compiler options such as OR('!') to property groups to configure the editor (Issue 17open in new window, Issue 61open in new window).
    • Include file resolution for COBOL and PL/I ignores SQLCA and SQLDA (Issue 71open in new window).
    • Fixed issues with COBOL 6.3 support such as >>if >>else >>end-if (Issue 65open in new window).
    • The logger now provides more configuration information that will help in your interactions with tech support.
    • Fixed issues managing Zowe Explorer favorites when using RSE API.
    • Revised profile validation in Zowe Explorer when using RSE API.
    We now include the IBM User Build VS Code Extension in IBM Z Open Editor. Changes since the 1.0.0 release:
    • In addition to COBOL we added support for building PL/I and HLASM programs with IBM Dependency-Based Build.
    • Fixed an issue with corrupted DBB log files when downloaded from USS.
    • User Build menus no longer appear for remote MVS or USS files opened via Zowe Explorer to avoid confusion about what can be built and what cannot.
    • Added more detailed log messages in the IBM User Build Output window, such as the full ssh commands executed, as a summary of all the user and workspace settings being used for a build and more. The output will list all required and optional settings and their values before the user build script is executed. If any required settings are missing, user build will stop execution explaining which setting caused the problem.
    • User Build can now run with files that contain spaces in their paths.
     1.0.3 - 2020/08/07
    • Added support for specifying custom include file extensions. You can now use the IBM Z Open Editor Preferences page to add and remove the file extensions to be used when searching for local include files such as COBOL copybooks. Also consistently added the Data Sets settings for remote include files to the visual editor allowing users to remove the mappings they do not want mapped in the files.association setting (Issue 16open in new window).
    • Added branch targets to the HLASM Outline view.
    • Fixed COBOL syntax highlighting that uses a "/" character for comments (Issue 60open in new window).
    • Fixed HLASM syntax highlighting for macros starting with a "$" character (Issue 69open in new window).
    • Added a support for using the java.home user setting for developers that install VS Code with the Microsoft Installer of VS Code for Java developeropen in new window or the Java Extension Pack.
    • Added a Zowe Profile validation routine that is called when adding and using RSE API profiles with Zowe Explorer 1.7 or newer.
     1.0.2 - 2020/06/30
    • Merged v0.5.2 with v1.0.1 to publish v1.0.2 to the VS Code Marketplace that now includes the language server for IBM High-Level Assembler (HLASM) for z/OS 2.4.
    • Reorganized the language server packaging to reduce the size of the extension to less than half than it was before.
     1.0.1/0.5.2 - 2020/06/23
    • Fixed false positives in Java compatibility check that prevented newer Java SDK versions than 8 to be used. (Issue 57open in new window)
     1.0.0 - 2020/06/12
     0.5.0 - 2020/06/12
    • Added syntax error checking for COBOL Copybooks.
    • Added support for CICS 5.6 syntax.
    • Rewrote the algorithm for searching for remote include files using Zowe CLI profiles.
    • Added user settings for specifying which Zowe CLI profile to use for finding remote include files on MVS in case you use multiple z/OSMF or RSE API CLI profiles.
    • Added Logger to analyze issues. Switch it on in the IBM Z Open Editor VS Code Preferences under User Settings.
    • Fixed bug with Unreachable Code Detection in COBOL EXECL SQL statements and switched default of the "zopeneditor.cobol.enableUnreachableCodeWarnings" Preferences setting back to true. (Issue 18open in new window)
    • Updated LSP4J language servers to baseline v0.9.0 and VS Code language clients to v6.1.3.
    • Improved LSP startup times.
    • Added more Java runtime checks to ensure you are using a valid Java SDK with the Z Open Editor extension.
    • Various enhancements and fixes for RSE API support such as Get JCL from the Zowe Explorer JES view as well as Migrate/Recall from the Zowe Explorer MVS view.
    • Fixed rare race condition when starting language servers. (Issue 45open in new window)
    • Various stability fixes and refinements.
     0.4.9 - 2020/04/23
    • Fixed an issue when using RSE for the Zowe Explorer JES view.
    • Fixed errors messages users saw when creating z/OSMF profiles in Zowe Explorer when Zowe CLI and/or the IBM RSE API Plugin for Zowe CLI was not installed.
     0.4.7 - 2020/03/27
    • Added Beta-level support for the new Remote System Explorer API (RSEAPI) REST servers that can be used as an alternative to z/OSMF for remote file operations as well as Zowe Explorer visual explorer views. If you run RSE already for IBM Developer for Z or IBM z/OS Explorer you can simply update. Go to https://ibm.github.io/zopeneditor-aboutopen in new window for more details.
    • Reduced the memory consumption of the extension by starting language servers only if a program in a specifc language is opened for the first time. This will avoid that you are wasting valuable PC memory for languages that you do not use. In addition we added two optional commands that you can run to pause the COBOL or PL/I language server once you finished with one language and want to free up its memory. When you open a program of that language again the language server will restart.
    • Added code actions that provide suggestions for resolving COBOL copybooks and PL/I include files by linking to Online Help pages.
    • Removed MQ code templates for now as we ran into some language compatibility issues.
     0.4.5 - 2020/01/07
    • Added an additional 27 code snippets for MQ development with COBOL and 27 for MQ with PL/I.
     0.4.3 - 2019/12/18
    • Added more code snippets for COBOL, PL/I and JCL, which brings it to a total of 186. For COBOL we now provide 27 General COBOL language support snippets, 12 Embedded SQL snippets, 29 for CICS, 12 for IMS, and 8 for VSAM. Similarly, we provide for PL/I 12 General PL/I language support snippets, 29 CICS, 11 IMS, and 7 VSAM. Finally, we have 27 code snippets for JCL.
     0.4.1 - 2019/11/21
    • Language server updates to support IBM Enterprise COBOL v6.3 and PL/I v5.3.
    • Added all new sets of IBM field contributed code snippets for COBOL embedded SQL and CICS, PL/I embedded SQL, and various new JCL snippets. This is just the beginning of us curating a larger portfolio of high-value code snippets and incrementally releasing these in the coming months. Keep and eye out and let us know what you think of these snippetsopen in new window.
    • Added an import command for loading Code Snippets exported by the IBM Developer from z/OS. Do you have your own set of code snippets that you managed in the Snippets view in IDz? You can now export and import these into Z Open Editor.
    • Switched off COBOL Unreachable Code warnings by default as there are cases in which it can provide false positives (see hereopen in new window for details). If you can accept the risk of a few false reports then you can enable it again by using the "zopeneditor.cobol.enableUnreachableCodeWarnings": true VS Code user or workspace setting.
    • Fixed a code completion bug for COBOL and PL/I that would erase text to the right of the cursor.
    • Fixed cases in which COBOL statements before the IDENTIFICATION DIVISION would break syntax checking. (Issue #9open in new window)
    • Fixed exceptions thrown by the PL/I LSP when computing document links (Issue #13open in new window)
    • Fixed issues with COBOL Unreachable Code warnings not being shown at all in some cases. (Issue #7open in new window)
    • Fixed an issue in which invalid PIC clauses would not be reported as syntax errors.
     0.3.11 - 2019/09/27
    • "Unreachable Code" is not reported as an error anymore, but is now a warning message in the Problems View.
    • Switch off "Unreachable Code" detection completely with this new setting: "zopeneditor.cobol.enableUnreachableCodeWarnings": false.
    • We implemented GLOB pattern matching in Property Group settings for finding Copybooks on the local file system as requested in this issueopen in new window. Use with care as a very large search space will slow down the editor.
    • We added support for VS Code Multi-root Workspacesopen in new window allowing you to now specify Property Groups for finding Copybooks for a workspace comprising of many development project folders and Git repositories. To use it move your Property Groups to the Workspace File.
    • We updated and revised our documentation for using Property Groups with patterns and workspaces in the Online Helpopen in new window. We also added examples for using it on Windows versus Mac/Linux.
    • Fixed an issue with using the Tab key in Code Snippets and when using it for indentation in the editor.
     0.3.9 - 2019/09/23
    • Just removed Preview flag in preparation for the announcement.
    • Stay tuned for more cool things to come.
     0.3.7 - 2019/09/17
    • Fixes to the documentation and hyperlinks.
    • Renamed extension preferences configuration name.
     0.3.5 - 2019/09/13
    • First public release evolving out of the Wazi technology preview. See README.md for details.
    Last Updated: 
    Contributors: Peter Haumer, Peter Haumer, kmaselli, Billie Jean Simmons, PETER HAUMER, Chun Hong Zheng, Lauren Li, Hestia Zhang, KRISTINA MAYO, Lauren Li, Min Huang, Prasang-A-Prajapati, Saile Daimwood, Shi Kun Li, shikunli
    
-    
+    
    IBM Z® Open Editor
     IBM Z Open Editor Releases
     4.5.0 - 2024/09/19
    • Added experimental context-menu command to expand the current COBOL program. It currently expands copybooks and opens an new editor tab with a temporary file showing the result. The expansion utilizes our language server and is currently limited, not providing evaluation of conditional compilation, yet.
    • Fix the bug that caused incorrect symbol names in the COBOL outline view for code lines with trailing comments and sequence numbers.
    • Fixed the issue where JCL code folding ranges were computed incorrectly for lines with trailing comments and the folding range for JCL JOB cards were missing sub-element, i.e. EXEC steps.
    • Fixed the issue where JCL code completion were giving incorrect suggestions when a statement starts with // DD by using DD as a label name for DD, EXEC or JOB statements.
    Advanced features:
    • Completed the MVS search capabilities in the z/OS Resources table by adding PDS member search. You can look for strings inside all your members of the data sets currently listed in the table or qualified by a naming pattern for the members. Results will be shown in the table and allow you to navigate to file locations with a simple click. Requires RSE API Zowe profiles.
    • Added UNIX System Services search capabilities in the z/OS Resources table allowing you to search files with name patterns as well as the contents of these files. Results will be shown in the table in the same ways as MVS search results allowing you to navigate to file locations with a simple click. Requires RSE API Zowe profiles.
    • Added preprocessor support for PL/I in addition to COBOL. Execute a processor that transform your custom code into valid PL/I locally on your workstation or on z/OS and continue editing your original program in Z Open Editor.
    • Various bug fixes for resolving HLASM custom macro definition and providing code completion in the editor.
    IBM RSE API Plug-in for Zowe CLI:
    • Performance improvement for retrieving all the member names of a data set with a large number of members.
    • Added --lc local encoding option for MVS and UNIX upload and download commands.
    • Added new command data-set-cross-lpar for copying datasets from one LPAR to other.
    • Added new change sub-command unix-file-encoding that updates the UNIX file target encoding.
     4.4.0 - 2024/08/12
    • Fixed the issue where Java was not being found on Windows or Linux when Z Open Editor searched the user's system. (Issue 420open in new window)
    • Added code folding to our COBOL language server, which features folding for Divisions, Sections, Paragraphs, Data-items, and EXEC SQL/CICS statements. Also added code folding range support to JCL.
    • Improved the COBOL and JCL Outline views to include comments in the selection ranges when clicking an outline node.
    • Fixed the issue with the resolution order for the NAMES() compiler option in PL/I when it was listed before include file locations.
    • Added the file extension .dbd, .mfs, and .pcb to the defaults for our HLASM editor.
    • We now provide snippet style code completion for HLASM operations and macros. Use tab to fill out or remove various parameters when the operation or macro is selected from the code completion list. The editor will then also show syntax errors when manually typing operation parameters incorrectly.
    • Added Go to References support for HLASM Operations and Macros to see references within the same file for a selected operation.
    • Fixed the issue in JCL where an incorrect error was shown for DD statement: "JCL incorrectly highlights empty DD line as error".
    • Fixed the issue in JCL where an incorrect error was shown for EXEC DLI and XOPTS(DLI) statements.
    • Performance improvements for language server document requests when finding the copybooks/include files. The language server now prioritizes requesting the most recently opened documents.
    • Experimental: all Z Open Editor VS Code extension strings have been localized to French and German using IBM's AI machine translation. Let us know if you like these translations.
    Advanced features:
    • New feature: added filter and search operations to the z/OS Resources table. You can now search within the content of sequential data sets that are currently listed in your table; search requires using IBM's RSE API. We also added new filter options to the table for RSE API and z/OSMF to help you refine the list displayed for the Zowe query directly in the table. More search and filter capabilities will be added for RSE API users soon.
    • Combined "last modified" date and "last modified" time columns into "last modified" in z/OSMF PDS member views of the z/OS Resources Table.
    • Fixed the issue where the z/OS Resources Table was not compatible with MVS date formats in RSE API v1.1.5.
    • Various fixes, refinements and improvements for remote preprocessor support such as improved logging of the remote preprocessor execution output, better error handling, support for z/OSMF with TSO Zowe profiles, added the 'Compare preprocessor input and output files' command to remote preprocessor files as well as improvements for managing the output file.
    • Added a progress bar and a Cancel button to user build operations. After clicking the Cancel button, user build will wait until any remote operation is completed and then stop.
    IBM RSE API Plug-in for Zowe CLI:
    • We are now providing a variant of the RSE API CLI Plug-in that can be used for installation in air gapped development environments. Find ibm-rse-api-for-zowe-cli-airgap-4.4.0.tgz in our IBM Wazi for VS Code Zip file at https://ibm.github.io/mainframe-downloads/downloads.htmlopen in new window.
    • Fixed the issue with multiple items included in data set filter search with RSE profiles.
    • Fixed the issue reported using RSE CLI for downloading files when using Nodejs v20. (Issue 427open in new window)
    • Added a new change sub-command: clear-tag which clears the tags of the specified UNIX System Services file.
     4.3.0 - 2024/06/18
    Note: Import update for the release of version 4.3.0 of IBM Z Open Editor: IBM watsonx Code Assistant for Zopen in new window, which supports AI-assisted transformation of COBOL to Java for modernizing applications, has now been moved into it's own VS Code extension IBM watsonx Code Assistant for Z version 2.0.0. All functionality has been migrated into this new dedicated extension. Receive your copy of the Z Code Assistant via your Passport Advantage Online account. See the Documentationopen in new window for more details.
    • New advanced feature: run your custom COBOL preprocessor on z/OS directly from our editor and edit your files without any syntax errors caused by preprocessor statements. We now offer local preprocessor execution and editor integrations as well as remote execution via TSO commands on z/OS.
    • All new JCL language server: with this release we add language support for z/OS MVS JCLopen in new window. This first version includes the following features: 
      • Improved syntax highlighting
      • Real-time syntax errors
      • Code completion using Ctrl/Cmd + Space
      • Outline view
      • On-enter rules in Textmate grammar for JCL 
        • Auto prefix newline with // if previous line prefixed with // (except for in-stream declarations i.e. DD *). Indentation is inherited (up to column 16 for non-empty lines). JOB declarations are automatically indented to column 16
        • Auto comment continuation for lines prefixed with //*
      • Vertical rulers at significant JCL column numbers (2, 10, 11, 15, 16, 72, 80)
      • JCL Custom tabstops (Default tabstops are: [0, 2, 10, 15, 19, 29, 39, 49, 59, 71, 72])
      • Support for commenting and uncommenting highlighted selections using Ctrl/Cmd + /
    • Completed support for PL/I v6.1 January 2024 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this blog postopen in new window for details. Additionally, support for the new JSONIGNORE, JSONNULL keywords was added.
    • Fixed the issue in the PL/I editor evaluating the names for include files differently than the compiler if the name includes special characters.
    • Fixed the issue of false unreachable code warnings around EXEC CICS PERFORM + HANDLE statements. (Issue 52open in new window)
    • Fixed the issue of false unreachable code warnings around EXEC SQL WHENEVER statements. Issue 63open in new window)
    • Fixed the issue in the REXX editor showing incorrect syntax errors for ELSE statements in certain scenarios.
    • Fixed the issue in HLASM where optional operands were not correctly accounted for when evaluating the number of operands provided. (Issue 418open in new window)
    • Added support for double-byte character editing. The editor will decorate double-byte character strings using guillemets icons and display a byte counter in the status bar giving users information about how many bytes they have left for the current line to avoid truncation.
    • Extended the status bar information for the active Zowe profiles, making it an active button with options to change the profile selection. For RSE API profiles, it provides the option to update the z/OS password.
    • Fixed the issue where renaming sequential data sets using the z/OS resources tables would temporarily show empty attributes for the renamed data set.
    IBM RSE API Plug-in for Zowe:
    • Added a check for Zowe CLI version compatibility that is executed by the RSE API plugin for Zowe CLI during installation.
    • Uploading files to z/OS UNIX System Service using RSE API profiles can now automatically detect if the file is binary.
    • Fixed the issue of showing an incorrect error message when no data sets were found that match a search pattern.
     4.2.0 - 2024/05/16
    • New advanced feature: custom macro resolution in HLASM programs with references to macros in local files. The HLASM editor shows hovers, document links, go to definition, and code completion for macros. This feature works with one to many macro declarations per include file, which is achieved by pre-scanning macro files if they can be found in local ZAPP property groups. For more information, see Custom Macros for HLASM.
    • Improved advanced feature: the z/OS resources table is updated to also support UNIX System Services. You can browse, filter, sort, open, download, upload, create, and copy your unix folders and files with the same user experience as in our previous release for MVS and JES. In addition, you find many UX refinements and polish for all views of this table. We also fixed 
      • presenting and sorting numbers and dates based on the user's locale.
      • presenting DSNTYPE for MVS data sets, even if the value is not provided by z/OSMF.
    • Added support for COBOL User Defined Function Prototypes. See COBOL documentationopen in new window for details.
    • Fix the issue where formatting EXEC SQL statements resulted in incorrect syntax (Issue 400open in new window).
    • Reorganized our startup and restart code to avoid problems such as Issue 403open in new window.
    IBM RSE API Plug-in for Zowe:
    • Fixed the issue of spool files not being correctly exported when their record length exceeded that of the destination dataset, resulting in truncation.
    • Fixed typographical errors in the new common-properties commands.
    • Fixed the issue that is seen downloading all members of a data set.
    IBM watsonx Code Assistant for Z:
    • Added editing of local variable names during class generation that will then be used during Java method generation.
    • Added editing of method input parameters during class generation that will then be used during Java class and method generation.
    • Improved Java method generation by sanitizing the COBOL code, such as removing comments and contents from columns 1-6 and 73-80.
    • Fixed the issue where for some edge cases the Java method generation was returning an empty code block.
    • Fix the issue where Java classes and methods were not appearing in the watsonx Code Assistant for Z tree view when the COBOL program was located in the top-level workspace folder.
    • Fixed the issue of the editor opening the same Java file in multiple editor tabs when using the watsonx Code Assistant for Z tree view.
    • Added support for proxy servers for watsonx interactions utilizing the VS Code settings http.proxy, http.proxyStrictSSL, http.proxyAuthorization when http.proxySupport is switched to on.
    • Various fixes and refinements for the watsonx tree view interactions related to item and source code selection.
     4.1.0 - 2024/03/28
    • Fixed the issue where SETC values were causing the HLASM parser to fail in certain scenarios. (Issue 396open in new window)
    • Added new options for listing additional job attributes in RSE API Plug-in for Zowe CLI.
    • Added ability to search files in UNIX System Services by file name or content in RSE API Plug-in for Zowe CLI.
    • Added new commands for storing and retrieving name/value pairs with RSE's Common Properties service in RSE API Plug-in for Zowe CLI.
    • Fixed the issue of failed downloads from z/OS for some file types using RSE API profiles.
    • Fixed the issue where downloading spool files with RSE API profiles would be stored with invalid file extensions.
    IBM watsonx Code Assistant for Z updates:
    • Added a walkthrough for new users to get a step-by-step guide on how to use watsonx Code Assistant for Z. You can access the walkthrough from the Z Open Editor Welcome page or from the VS Code Welcome page.
    • Added a new CodeLens when editing generated Java code to view and navigate to the COBOL source that watsonx Code Assistant for Z was using to generate a Java method.
    • COBOL files selected for Transformation in watsonx Code Assistant for Z will no longer open in read-only mode.
     4.0.0 - 2024/03/15
    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 Documentationopen in new window.
    To emphasize, none of the other features that you were using in previous releases are impacted by the update. Previous features are still available for free and will still be maintained and enhanced as always. We are also still fully committed to supporting z/OSMF and RSE API for the free as well as advanced capabilities.
    Only the following three new features require a license. Our goal is to provide more and more advanced features such as these to Z Open Editor in the future:
    1. 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.
    2. z/OS Resources table: an all-new feature rich 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.
    3. Advanced Dependency-Based user build error reporting: User build logs are now automatically downloaded, parsed, and presented in the editor's Problems view with 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.
    We reorganized the Z Open Editor Welcome page for you to see the status of your trial license. You can unlock the features by importing an activation kit or connecting to an RSE API server with configured IDzEE licenses.
    Free languages updates:
    • Added support for the COBOL v6.4 February 2024 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this blog postopen in new window for details.
    • Added support for the COBOL v6.4 October 2023 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this blog postopen in new window for details.
    • Added support for the PL/I v6.1 January 2024 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this blog postopen in new window for details.
    • Added support for the CICS v6.2 Beta Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features.
    • Added support for the z/OS 3.1 default HLASM macros. z/OS 3.1 is now the default option. To change your z/OS level, search zopeneditor.hlasm.zosMacrosVersion in settings.
    • Fixed the issue where the HLASM Language Server did not parse non-english characters correctly. (#389open in new window)
    • Added the debug scheme to our language clients, enabling full language server support providing you with features such as Outline view, Go to Definition, Find All References even when running IBM Z Open Debug sessions. (#360open in new window)
    Free RSE API Plug-in for Zowe CLI updates:
    • Z Open Editor extends the Zowe Explorer's Jobs view experience: open a spool file in Zowe Explorer and Z Open Editor will automatically provide JCL and messages syntax highlighting.
    • Added support for changing file tags on USS for RSE API profiles in Zowe Explorer.
    • Added support to show partitioned data set member attributes for RSE API profiles in Zowe Explorer.
    • Added support for creating a data sets for RSE API profiles using the new templates from Zowe Explorer.
    • Added support for Zowe profile encoding with DBB User Build download of log files.
    • Added new command issue unix-shell for RSE API profiles that utilizes a streaming command output and allows users to set environment variables for the executing shell.
    • Added new command export spool-file for RSE API profiles allowing export of job spool files to a sequential data set or data set members.
    • Added support for refreshToken and auto-refresh-token for RSE API profiles in Zowe Explorer.
    • Switched to using RSE API streaming for raw content when uploading to and downloading from MVS, UNIX System Services, and JES files.
    • Fixed the issue with creating a partitioned data set of the type LIBRARY for RSE API profiles did not work correctly.
    • Fixed the issue of command issue unix returning an incorrect exit code.
    • Fixed the error when submitting jobs using the --wfo (wait for output) option using RSE API profiles. (#385open in new window)
     3.4.0 - 2024/02/29
    • Fixed the issue with Embedded EXEC CICS statements where EXEC CICS GET CHANNEL was marked with the error "RESP expected instead of this input". (Issue 361open in new window)
    • Fixed the issue with Embedded CICS EXCI statements where CICS EXCI was marked with the error "RESP expected instead of this input".
    • Fixed the issue with Embedded SQL statements where SQLCA symbols were not resolved when an "EXEC SQL INCLUDE SQLCA" statement was inside of a conditional compilation block. (Issue 379open in new window)
    • Fixed the issue of incorrectly showing an error about the absence of an end directive when the conditional compilation directive ">>define" was on the last line of a Copybook file. (Issue 374open in new window)
    • Fixed the issue where COBOL COPY statements with a "." but without a whitespace were marked with an error.
    • Fixed the issue where document links were not resolving correctly when multiple documents were opened in parallel that pointed to the same include files in COBOL, PL/I, and HLASM files. (Issue 363open in new window)
    • Fixed an issue where document links would not remove the red underline for an include file after loading correctly in COBOL, PL/I, and HLASM files. (Issue 363open in new window)
    • Fixed the issue where REXX syntax highlighting would break when an empty comment statement was present /**/. (Issue 384open in new window).
    IBM watsonx Code Assistant for Z updates:
    • Replaced the COBOL-centric class generation preview with a new Java-centric presentation for watsonx Code Assistant for Z. Users can now preview the Java classes to be generated in an expandable table view that outlines the variable and method member names next to their mapped COBOL names. They can click hyperlinks within the mapping view to navigate directly back to the COBOL source code files for comparison.
    • Updated the watsonx Code Assistant for Z tree view to show a breakdown of method members per Java class that can be generated by the assistant's AI component. These methods are based on COBOL section and paragraph names and become available after the initial Java class generation step has been completed.
    • Updated the watsonx Code Assistant for Z tree view to support a new workflow for reopening saved COBOL-to-Java mappings and regenerating Java code.
    • Updated the watsonx Code Assistant for Z tree view with new icons and icon decorators that visualize which Java members mapped from COBOL paragraphs have already been generated and which not.
    • Updated error handling, error message dialogs, and log file messages.
    • Fixed the issue of the Welcome page checkbox for enabling/disabling watsonx Code Assistant for Z not being synchronized with the respective user setting.
     3.3.3 - 2023/12/15
    • Fixed the issue for COBOL where SKIP1, SKIP2, SKIP3, and EJECT tokens were not being handled correctly when placed within other statements to control white space. (Issue 307open in new window)
    • Fixed the issue where conditional compilation statements were not being handled correctly when placed in a >>WHEN OTHER phrase. (Issue 366open in new window)
    • Fixed the issue where the COBOL parser could hang or crash when a file's final line ended with a character in column 7.
    • Fixed the issue where a language server would start before all ZAPP files were processed missing settings such as compiler options. (Issue 364open in new window)
    • Fixed the issue where the RSE API plugin for Zowe CLI command to upload a file to a UNIX System Services directory would show an error.
    • Various bug and serviceability fixes as well as UI refinements for IBM watsonx Code Assistant for Z. Generate Java classes now by using the icon next to the COBOL program name or by using the context menu. When entering an API key you will now receive a confirmation message after a server-side validation check.
     3.3.2 - 2023/11/28
     3.3.1 - 2023/11/07
    • Corrected the default URL for the IBM watsonx Code Assistant for Z server setting.
     3.3.0 - 2023/10/25
    New: IBM watsonx Code Assistant uses generative AI to accelerate code generation and increase developer productivity for application modernization. IBM watsonx Code Assistant for Z is now enabled in IBM Z Open Editor to drive the selective and incremental transformation of COBOL business services into well-architected high-quality Java code. It uses the inventory and analysis tools of IBM Application Discovery and Delivery Intelligence (ADDI) to support development teams in refactoring business services in COBOL, transforming COBOL code to Java code, and validating the resulting outcome. Learn more and sign up for a trial at https://www.ibm.com/products/watsonx-code-assistant-zosopen in new window.
    Other fixes and enhancements in this release:
    • Added support for CICS v6.2 Beta to COBOL and PL/I language servers.
    • Added support for line and block comment shortcuts in PL/I and REXX.
    • Machine instruction statements in HLASM are now identified when the number of operands is incorrect. Assembler instructions are not supported at the moment.
    • Improved the parsing behavior of HLASM language servers, particularly around continuation lines. Symbols that are continued should now have that reflected when you hover over references. Symbols that are used in continuation lines now support language functionalities, such as hover, Go to Definition, and Find References.
    • Fixed the bug where lowercase and mixed-case macros were not correctly displaying document links in HLASM.
    • Added support for internal macros that are declared in an HLASM file. Macros that are declared in an HLASM file now support code completion, hover, and Go to Definition in the file. Note that macros declared with the same name as a default SYS1.MACLIB macro will take precedence over the default macro.
    • Added .mac as another default file extension for HLASM program files.
    • Improved syntax highlighting around %INCLUDE statements in REXX.
    • A ZAPP file will now be automatically generated if none can be found in any of your workspaces when a COBOL, PL/I, HLASM, or REXX file is opened for the first time. This ZAPP file will search in all your local folders for include files, such as copybooks, so you should modify it for a more specific path or remote MVS locations afterwards. This behavior can be disabled with the new user setting "zopeneditor.zapp.generateZappOnDemand". Include file statements in all of these languages now also have the Quick Fix menu entry to open ZAPP files for troubleshooting and to open the ZAPP documentation for quick reference.
    • Changed the behavior of the "Run user build with full upload" command to now upload also all files that are specified with additionalDependencies in the ZAPP file. (Issue 297open in new window)
    • Fixed the issue where user build did not properly filter search results for logs. (Issue 353open in new window)
    • Fixed the issue where user build related editor menu items and command palette items were displayed for COBOL and PL/I include files.
    • Fixed the issue where user build menu items and command palette items were not displayed for VS Code 1.76 and earlier versions. (Issue 349open in new window)
    • Fixed the issue where user build did not handle SSH keys for authentication in Zowe SSH profile. (Issue 355open in new window)
    • Fixed the issue with RSE API in Zowe Explorer where the user was prompted for username and password when using a token for authentication.
    • Added the ability to change owner, group, and permissions of Unix files on RSE CLI.
    • Added the ability to check a user's password expiration date with RSE CLI.
    • Fixed the issue where default RSE profiles were not displayed by default in Zowe Explorer's tree views when the team configuration profile did not contain z/OSMF profiles.
    • Added functionalities for RSE profiles, including copying files and directories in z/OS UNIX System Services, copying data sets, and cancelling jobs.
    • Added support for editing attributes in z/OS UNIX System Services for RSE profiles in Zowe Explorer.
    • Fixed the issue where RSE API Plug-in for Zowe CLI returned duplicate values when executing the list all members command using wildcard pattern parameters.
    • Fixed the issue where RSE API Plug-in for Zowe CLI did not return the correct error messages when executing the list or download all members command using incorrect parameters.
    • Fixed the issue where the Zowe profile status bar was not updated after edits were made to the team configuration profiles for RSE API profiles.
    • Added job timestamp to the output of the list jobs command for RSE API Plug-in for Zowe CLI when running commands against RSE API server v1.1.3.
     3.2.3 - 2023/10/11
    • Fixed the issue where Z Open Editor showed an incorrect warning about initializing secure credentials. (Issue 359open in new window)
    • Fixed the issue where RSE API profiles that were using token-based authentication stored token details incorrectly in certain situations.
    • Fixed the issue where building projects that were not managed with Git produced Git errors. The fix changes the behavior that when no Git repository can be found then all .gitattributes files are ignored.
     3.2.2 - 2023/09/15
    • Fixed the issue in COBOL where DEFINE(compilation-variable-name) was not applying the default value B'1'. (part of Issue 154open in new window)
    • Fixed the issue in COBOL where COBOL keywords are not able to be used as compilation-variable-name before a >>DEFINE statement. (part of Issue 154open in new window)
    • Fixed the issue where IBM User Build was not properly filtering search results for logs. (Issue 353open in new window)
    • Fixed the issue where RSE API plugin for Zowe CLI returned duplicate values for list all members.
    • Fixed the issue where the Zowe profile status bar field would not get updated after making edits to RSE API profiles in team configuration files.
    • Security fix limiting telemetry data volumes.
     3.2.1 - 2023/07/19
    • Added syntax and content assist support for the LOCATION options (LOC24 and LOC31) in the GETMAIN64 EXEC CICS embedded CICS command.
    • Fixed the issue where the PL/I PROCESS MAR/MARGIN options did not accept a third parameter. (Issue 344open in new window)
    • Fixed issues in the HLASM outline view to correctly handle duplicate elements such as CSECTS and DSECTS that are continued. Symbols that are reassigned will still point to the final declaration to prevent the outline from becoming overcrowded.
    • Fixed the issue in User Build where menu items and commands were not available when VS Code 1.76 or earlier versions were used. (Issue 349open in new window)
    • Fixed the issue in User Build for COBOL and PL/I where a copybook or include file with a name that was a substring of another copybook or include file name was not identified as a dependency correctly.
    • Fixed the issue that prevented the default RSE API Zowe CLI profiles to be displayed in Zowe Explorer's tree views at startup when Zowe team configuration profile files did not contain a z/OSMF profile.
     3.2.0 - 2023/06/16
    • Added support for the COBOL v6.4 April 2023 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this blog postopen in new window for details.
    • Fixed the coloring of the keyword NOT in COBOL. (Issue 328open in new window)
    • Fixed the missing syntax errors when statements (such as COPY) start to the left of Area A and overflowing data names (for example in USING statements) start to left of Area B. (Issue 340open in new window)
    • Fix the issue where comments were misinterpreted within a COPY statement when using an empty quoted pseudo text and the == identifier. (Issue 248open in new window)
    • Removed the ability to perform Number and Unnumber actions when COBOL Language Server is not running. (Issue 189open in new window)
    • Fixed certain COBOL words not highlighting correctly when placed at the end of a line. (Issue 346open in new window)
    • Added support for the PL/I v6.1 March 2023 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this blog postopen in new window for details.
    • Fixed the issue that caused PL/I comments to show a report when starting in column 1. (Issue 135open in new window)
    • Fixed the issue with PL/I code completion when a variable is in the same column with a DCL statement.
    • Added preview hovers and clickable hyperlinks to open include files in REXX.
    • Added support for jump targets as well as RSECT, LOCTR, and COM control sections in the HLASM outline view.
    • Fixed the issue where preview hovers failed to load for HLASM COPY statements when the copied document was closed after previously being opened by using the hover's hyperlink.
    • Added the user settings "zopeneditor.<language>.disableProblems" for each language to enable/disable the Problems view and syntax errors shown within the editor while maintaining other language features. It will allow users to continue working in the program with some language features despite parsing issues. This will not work in all circumstances as some syntax errors will also break other language features. (Issue 199open in new window and Issue 203open in new window)
    • Added the ability to define custom ZAPP variables in your personal user or workspace settings. Define variables in a new mappings table under zopeneditor.zapp.variables in the VS Code settings editor and then reference them in your ZAPP files with ${variable-name}. For example, define a variable here called HLQ with a value that represents your personal high-level qualifier on z/OS MVS. In your ZAPP file, reference it in a property group's location entry, such as ${HLQ}.COBOL.COPYBOOKs.
    • Fixed a copybook and include file watcher limitation about file precedence in remote and local non-syslib libraries.
    • Added the user setting "zopeneditor.zowe.maximumParallelFileDownloads" to specify how many parallel downloads Z Open Editor should perform when requesting include files from MVS. This will help minimize address spaces being allocated by z/OSMF. The default value of the setting is 5, and the maximum value is 10. Set it to 1 to disable parallel downloads. (Issue 134open in new window)
    • Added the user setting "zopeneditor.zowe.listBeforeDownload" to enable Z Open Editor to first search for the existence of a data set member before trying to download it when resolving include files. This will slow down performance, but will cause less logging on z/OS when using z/OSMF. The default is off to preserve performance. (Issue 134open in new window)
    • Fixed the issue where COBOL copybook requests were not sent in parallel in certain cases where Unix-style line endings were used on Windows.
    • Fixed the issue where COBOL and PL/I include file requests were sometimes sent twice if a document could not be found.
    • Fixed the issue that language server errors and exceptions caused by a timing issue are displayed. (Issue 332open in new window)
    • Fixed the issue where COPY or INCLUDE statements using custom libraries were in some cases resolved with syslib libraries.
    • Improved the folder watching performance. When folders within the scope of the current ZAPP property groups are deleted or created, open program files will be re-parsed instead of a complete extension restart.
    • Added the ability for User Build to automatically run the git check-attr command in the background to evaluate .gitattributes in any folder of the workspace to upload files to UNIX System Services with the correct file encoding. If Git is not installed or cannot be found by the editor, Z Open Editor will continue trying to evaluate encoding itself. (Issue 331open in new window)
    • Fixed the issue in User Build where files specified in a ZAPP file as additionalDependencies were not converted and tagged correctly when being uploaded to UNIX System Services.
    • Fixed the issue where User Build failed to run when dbbLogDir does not exist on UNIX System Services.
    • Added a warning message to the User Build output view to inform the user when the language server is stopped, because the language server will then not be able to compute dependencies such as copybooks and cannot upload them to z/OS.
    • Fixed the issue where User Build would not download any log files when the logFilePatterns property was not specified in the ZAPP file. Added a default that will download all files that match the pattern *.log.
    • Fixed an issue where user build menu was not always hidden when user build was disabled via settings. (Issue 347open in new window)
    • Fixed an issue where ZAPP and ZCodeFormat code snippets would not show when editing in multi-root workspaces.
    • Updated dependencies for security audits.
    • Added support for JCL symbols as a parameter for jobs on RSE CLI.
    • Fixed an issue when saving files to z/OS with Zowe Explorer using RSE API and resolving conflicts with changes done by other users to the same file. VS Code will now properly show the conflicts in its differences editor allowing you to merge and save.
     3.1.1 - 2023/03/30
    • Fixed an issue with COBOL language code completion where code completion was not working on the first line of a COBOL file.
    • Added support for $ and </> to be used as pseudo-text boundaries for the REPLACING strings in COBOL copybooks. (Issue 305open in new window)
    • Fixed an issue where COBOL literals were not being highlighted correctly when single quotes and double quotes were mixed. (Issue 308open in new window)
    • Fixed an issue where the connection to the language server got disposed showing errors in the output view. (Issue 332open in new window)
    • Fixed an issue where COBOL copybook requests did not download remote copybooks in parallel for non-syslib libraries.
    • Fixed an issue with .gitattributes where * could not be used as a pattern for encoding the selection of files. (Issue 331open in new window)
    • Fixed an issue where the Zowe team configuration's encoding property was not used when no .gitattributes file was present or no match was found. (Issue 331open in new window)
    • Fixed an issue where User Build on Windows uploaded remote copybooks to USS. (Issue 333open in new window)
    • Updated Zowe and third-party dependencies addressing security scan results.
     3.1.0 - 2023/03/10
    • Added support for the PL/I v6.1 October 2022 Refresh with updated syntax highlighting, outline view, real-time syntax checking, and other language related features. See this blog postopen in new window for details.
    • Added support for using comma in the DEFINE compiler option syntax for COBOL. (Issue 278open in new window)
    • Added code completion support for statements containing Unicode Strings in COBOL.
    • Added code completion support for Compiler Directing statements (Compiler Options) in COBOL.
    • Added code completion support for ENABLE PROGAM in EXEC CICS Statements in COBOL.
    • Fixed an issue with COBOL where CBL or PROCESS service directive was not being recognized. (Issue 253open in new window)
    • Fixed an issue with COBOL language showing false syntax errors for not correctly handling condition expressions on compilation variables in boolean format compared with the constant b'0' or b'1'. (Issue 321open in new window)
    • Reverted syntax highlighting changes from last release for unsupported Boolean literals (b and bx). The IBM COBOL compiler currently does not support them. (Issue 308open in new window)
    • Added new option alignToClauses to zcodeformat.yaml files to support aligning TO clauses, aligning INTO clauses, and aligning TO clauses into column.
    • Added file watching support for all languages so that programs with INCLUDE and COPY statements are now automatically re-parsed when local included files or copybooks are edited, created, or deleted. (Issue 108open in new window). See Known Issuesopen in new window for a limitation involving file precedence in remote and local non-syslib libraries.
    • Improved performance for loading PL/I include files. Include files that are being downloaded from a remote z/OS system will now resolve much faster as download requests are performed in parallel to a maximum of five files at once. (Issue 269open in new window)
    • Significantly improved performance for searching for local copybooks and include files via property groups that use glob patterns that expand to many results. (Issue 315open in new window, Issue 293open in new window)
    • Fixed an issue with no hover content of the copybook when COBOL source contains any errors in the COBOL program. (Issue 300open in new window)
    • Fixed a bug where large copybooks and include files were not completely resolved, resulting in errors such as Unable to resolve reference to variables included from copybooks. (Issue 313open in new window)
    • Fixed a bug when editing REXX programs with remote REXX include files, which were resolved and saved with an incorrect file extension.
    • Full support for all the new Zowe Explorer JES filtering options when using RSE API profiles.
    • Fixed issue where user build logs in nested directories were not being found (Issue 296open in new window).
    • Updated the user build output view and log file formatter to include timestamps when Z Open Editor's log level (zopeneditor.logger) is set to DEBUG to help with trouble-shooting and measuring build times. (Issue 292open in new window)
    • Added support for path name specification for .gitattributes in IBM User Build.
    • Added new option for tagging files using working-tree-encoding os=zos in .gitattributes in IBM User Build as an alternative to zos-working-tree-encoding.
    • Addressed a concern that code snippets for ZAPP and ZCodeFormat files appeared in the code completion for all YAML files being edited. We therefore removed them from the Snippet Gallery and provided them as pure context-sensitive code completion items for <ctrl-space>.
    • Z Open Editor is now available to install as a web extension with limited capabilities when using Visual Studio Code in a browser, such as vscode.dev or github.dev. Try it by going to https://vscode.dev/github/IBM/zopeneditor-sampleopen in new window and confirming to install the recommended extensions.
     3.0.1 - 2023/01/18
    • Performance improvements for loading COBOL copybooks. Copybooks that are being downloaded from a remote z/OS system will now resolve much faster as download requests are performed in parallel to a maximum of five files at once. PL/I will be updated with this capability in a later release. (Issue 269open in new window)
    • Fixed invalid "REDEFINES clause must begin in Area B" error shown in COBOL editor when using the REPLACING clause with a REDEFINES. (Issue 287open in new window)
    • Fixed issues with COBOL syntax highlighting when using literal delimiters. Respective language server fixes will be provided at a later date. (Issue 308open in new window)
    • Fixed spelling in COBOL code snippets. (Issue 286open in new window)
    • Fixed issue with %Replace in PL/I when using a minus sign in expression. (Issue 299open in new window)
    • Fixed an issue in User Build evaluating file names with special characters, such as $, in command shell expression. The DBB Daemon might also be effected by this problem. Remove the -DBB_PERSONAL_DAEMON command line parameter from the ZAPP file if you still run into this problem. (Issue 288open in new window)
    • Fixed an issue with User Build not downloading log files for programs with lower or mixed case filenames, because dbb-zappbuildopen in new window will automatically capitalize log file names. User Build will now also automatically capitalize the build file name when using the ${buildFile.basename} variable under logFilePatterns in the ZAPP file.
    • Fixed syntax error in ZAPP code snippet for the dbb user build profile.
    • Fixed issues in our RSE API support when using special characters in z/OS file or directory names.
    • Fixed bugs and improved the usability of the change password command in the IBM RSE API Plug-in for Zowe CLI.
    • Fixed error being thrown in Zowe Explorer when RSE API list of all members returns no members.
     3.0.0 - 2022/11/22
     Breaking Changes
    For more details on breaking changes and the required manual migration steps see our user documentationopen in new window.
    • Z Open Editor now requires as a minimum a Java 11 runtime for running language servers. Users must upgrade their installed Java 8 runtime or Z Open Editor's language capabilities will not be available. See the documentationopen in new window for the recommend Java Runtime Environments that you can use.
    • ZAPP files are now replacing various user settings and cannot be disabled enabled anymore. The user setting "zopeneditor.zapp.enabled" has been removed.
    • Property Groups have been removed from VS Code user and workspace settings. The setting "zopeneditor.propertygroups" is no longer available. Users must now use ZAPP files for specifying locations for include files. When only using Zowe Explorer to edit program files you need create a workspace folder with a ZAPP file as well.
    • Property Groups have been updated to contain references to local files as well as remote MVS files in the same property group item applying the same compiler options to each. The schema for a property group item has changed and users must update their ZAPP files. Please, check the documentationopen in new window for the details and our migration pageopen in new window for how to upgrade.
    • User Build settings have been updated to allow more configuration options such as allowing glob patterns to define files for uploading and downloading. See the IBM Wazi for VS Code User Build documentationopen in new window for more details.
     Other changes and fixes
    • Fixed syntax of EXEC CICS INQUIRE SYSTEM MAXOPENTCBS. (Issue 257open in new window)
    • Added missing CICS v6.1 INQUIRE SYSTEM options: SRRTASKS, MEMLIMIT and MQCONN that used to cause syntax errors.
    • Fixed CICS v6.1 EXEC CICS CREATE DB2ENTRY ATTRIBUTES option incorrectly flagged as an error.
    • Fixed CICS v6.1 EXEC CICS SET TAGS REFRESH with NOHANDLE and RESP options incorrectly flagged as an error.
    • Fixed an issue in COBOL syntax checking for a working storage variable starting with REMARKS. It would be incorrectly identified as a REMARKS paragraph. (Issue 276open in new window)
    • Fixed an issue with COBOL Syntax Highlighting in the sequence number fields (1-6 and 73-80). (Issue 193open in new window)
    • Fixed a NullPointerException caused by the PL/I Code Folding feature when opening copybook/include file from PL/I Editor. (Issue 277open in new window)
    • Fixed a NullPointerException caused by the PL/I Code Folding feature when the currently selected word matches a code completion suggestion that would alter the outline view. (Issue 283open in new window)
    • Fixed an issue with syntax checking for PL/I related to function parameters of type File as well as a DEFINE ORDINAL containing signed integers in the VALUE attribute.
    • Added REXX syntax highlighting for matching pairs of parenthesis. Auto-close parenthesis when typing.
    • Fixed an issue with improper error logging regarding the list command in RSE CLI.
     2.2.0 - 2022/09/20
    • Fixed User Build and the RSE API CLI's upload command to correctly encode file names with special characters. Files such as "T@A#R$C" will now be correctly uploaded to USS. (Issue 266open in new window)
    • Performance improvements for the REXX language server via parser optimizations. (Issue 256open in new window)
    • Updated the REXX hover hyperlinks to point to the z/OS 2.5.0 reference.
    • Improved performance and reliability for the HLASM language server by implementing cancellation support for requests that are no longer valid, as well as optimizing handling of document-link requests for macros.
    • Fixed a bug where mixed case variables were not handled correctly in HLASM.
    • Fixed a bug where hovers sometimes did not show the correct code snippet for SYS1.MACLIB macros in HLASM.
    • Fixed a bug where document link underlines were not showing for HLASM macros when a file is first opened. Similar to a problem fixed for COBOL in (Issue 81open in new window) and (Issue 114open in new window).
    • Fixed a bug where "Failed to fetch COPYBOOK" errors were causing slowdowns across the HLASM language server.
    • Added initial support for code folding for control statements to the PL/I language server.
     2.1.1 - 2022/08/14
    • Added support for running User Builds with nested copybooks for COBOL. Issue 251open in new window
    • Fixed User Build issues with credential dialogs and storing credentials for remote include file resolution using z/OSMF or RSE API. (Issue 245open in new window, Issue 255open in new window)
    • Fixed User Build issues with credential dialogs and storing credentials for SSH commands when using z/OSMF.
    • Fixed User Build issues when attempting to build from workspaces with spaces in the file path. (Issue 252open in new window)
    • Fixed various issues when using ZAPP and User Build in a multi-root workspace. You can now use multi-root workspaces as long as you use a single ZAPP file and provide it together with the application-conf folder in the same workspace as your program. Include files such as copybooks can be in many other multi-root workspace folders. The ZAPP file needs to specify property groups with a workspace folder relative path even for include files located in other workspaces. User Build with user settings in multi-root workspaces is not supported. Please, switch to ZAPP files. See our Sample GitHub repositoryopen in new window for more details and a examples for single-root workspaces, in the wazi-main branch as well as multi-root in the multiroot folder of the wazi-main branch. Also note, that for single as well as multi-root the value for the DBB buildScriptArgs parameter has changed for the --application parameter to be now just a relative path to the application-conf directory. So in most cases you can just use --application ., which makes it much easier as you do not have to provide the folder name of your workspace root in the ZAPP file anymore. Finally, the zopeneditor.userbuild.userSettings.localWorkspacePath user setting has been deprecated is not used anymore.
    • Fixed an issue in the Z Open Editor output log not always reporting the correct Zowe profile management version in use.
    • Fixed issue in the COBOL Code Formatter producing incorrect Area B alignments for USING statements.
     2.1.0 - 2022/06/14
    • Added language support for COBOL v6.4, PL/I v6.1, and CICS v6.1 with updated syntax highlighting, outline view, real-time syntax checking, and other language related features. See our documentationopen in new window for details. (Issue 240open in new window)
    • Added COBOL UTF-8-specific syntax elements in textmate grammar (Issue 241open in new window)
    • Added an experimental COBOL code formatter that can be configured similar to Prettier with a yaml or json file. Find more details in our documentation (Issue 31open in new window)
    • Updated HLASM Instructions to match the set that was shipped with IBM z16.
    • Updated HLASM Macros to match the z/OS 2.5 SYS1.MACLIB. Switch the z/OS version back to 2.4 SYS1.MACLIB by using the user setting zopeneditor.hlasm.zosMacrosVersion.
    • Added .macasm and .copyasm as default file extensions for HLASM. (Issue 220open in new window)
    • Added .bms as default file extensions for HLASM. (Issue 223open in new window)
    • Fixed an error in the Problems View when a custom-defined problemMatcher was used when compiling HLASM code. (Issue 230open in new window)
    • Various fixes and refinements for HLASM syntax highlighting.
    • Added REXX include file support consistent with the other languages using Property Groups in ZAPP files. (Issue 172open in new window)
    • Added a status bar item that displays the currently active Zowe profile used by Z Open Editor for remote include file resolution and IBM User Build. (Issue 165open in new window)
    • Added support to filter the information displayed in the RSE CLI plugin command zowe rse check jobs that displays all active job address space information. This functionality is available in RSE API v1.0.9.
    • Added support for use of passphrase in change password command with RSE API v1.0.9.
     2.0.3 - 2022/05/20
    • Fixed a synchronization issue that when saving syntactically correct ZAPP files the editor sometimes would still report errors.
    • Fixed an issue in User Build related to file upload operations in which Z Open Editor would not evaluate the .gitattributes file correctly, not following the Git standard for precedences. (Issue 236open in new window)
    • Updated how User Build parses .gitattributes files dealing with more file formats such as Windows CRLF files and added more logging for the encoding matches found or not found. (Issue 235open in new window)
    • Added support for using the ZOWE_CLI_HOME environment variable to specify an alternative location for global team configuration files to Zowe Explorer 2.0.2 and Z Open Editor. (Issue 238open in new window)
    • Fixed various errors that prevented Zowe Explorer and Z Open Editor to run in Eclipse Che especially plugin containers with Nodejs 12. You can use these extensions now with secure credentials disabled as documented hereopen in new window.
     2.0.2 - 2022/04/25
    • Added full support for Zowe 2.0 in particular Zowe Explorer 2, Zowe CLI 7, Zowe API Mediation Layer 2. You can continue using your Zowe CLI 6.x profiles for backwards compatibility, but you must update Zowe Explorer to version 2 to do so. Review our Getting Started with Zowe 2.0 section in the Z Open Editor user documentation or the Zowe CLI documentation for how to migrate your 6.x profiles to the 7.x format.
    • Added support for auto-init of Team config files to the IBM RSE API Plugin for Zowe CLI. Use it when you have you RSE API host component registered with the API Mediation Layer.
    • Switched the minimal required version of Node JS for IBM RSE API Plugin for Zowe CLI to version 14 as version 12 is out of support now.
    • Added user setting zopeneditor.server.startupOptions for providing custom Java startup options for language servers. Can be used with tech support for troubleshooting.
     2.0.0 - 2022/03/15
    Z Open Editor is released as major version update to 2.0 to celebrate its availability in IBM Wazi Developer for Workspaces 2.0 that is now part of the IBM Z and Cloud Modernization Stack and fully supports running on OpenShift on Linux on Z. Note that because Zowe 2.0 was delayed to late April 2022, Z Open Editor has to be updated to support it once Zowe has been released. Other fixes and enhancements in this release:
    • Added missing DEBUG-ITEM variables in the COBOL language server. (Issue 156open in new window)
    • Added missing JNIENVPTR and JSON-STATUS variables in the COBOL TextMate grammar and the COBOL language server. (Issue 156open in new window)
    • Fixed an issue in the COBOL language server not supporting a mixed case spelling of SQLCA and SQLDA. (Issue 208open in new window)
    • Fixed an issue in the COBOL language server where the Rename Symbol feature was not renaming symbols that were spelled using a different character casing.
    • Fixed an issue in the COBOL TextMate Grammar making the SCREEN keyword case insensitive.
    • Fixed an issue in the COBOL language server where parsing failed because of period in column 72 and standard sequence numbering present in the program. (Issue 202open in new window)
    • Fixed an issue in the COBOL Language Sever where parsing failed with invalid error message in COPY REPLACING statements. (Issue 181open in new window)
    • Performance and reliability improvements for the COBOL and PL/I language servers by implementing cancellation support for requests that are no longer valid as well as optimizing handling of document-link requests for include files.
    • Added new options to the truncation warning dialog for COBOL, PL/I, HLASM, REXX, and JCL files in Z Open Editor. Also, if only whitespaces are truncated the editor will not prompt anymore, it will just remove them automatically.
    • Fixed an issue in the PL/I language server where hover content for include files were not rendering in the correct format. (Issue 211open in new window)
    • Fixed an issue in the HLASM language server where NullPointerException were logged while rendering hovers after a document change.
    • Fixed an issue where HLASM syntax highlighting was not correctly recognizing sequence numbers at the end of lines (Issue 192open in new window).
    • Fixed an issue in the REXX language server where a trailing comma in a function parameter resulted in a syntax error.
    • Improved the REXX language server performance and stability when editing large files.
    • Z Open Editor and Zowe Explorer now share the profiles loaded into memory via the Zowe Explorer Extensibility API. Now if you make changes to a profile in Zowe Explorer or use the Reload button to load changes from disk done via CLI, the changes will be immediately visible to Z Open Editor without the need to run "Reload Zowe profiles" from the command palette. This command now performs the same operation as clicking the Zowe Explorer Refresh button.
    • Made the Zowe connection test in Z Open Editor more robust and fixed the issue of tests timing out for slow connections. (Issue 197open in new window)
    • Fixed an issue preventing submission of JCL in Zowe Explorer via command palette option "Zowe Explorer: Submit JCL" using RSE API CLI Zowe profiles.
    • Fixed an issue with token and base Zowe CLI profiles support for MVS connection tests for remote file resolving.
    • Added RSE API Zowe profile login and logout support for JSON Web Token authentication with the RSE API through Zowe Explorer.
    • Improved working with interactive TSO commands for RSE API Zowe profiles by adding the TSO command tag shell-id, that can be used with RSE API server v1.0.8.
    • User Build now works with Zowe CLI profiles that do not store credentials. User will be prompted to provide them when the build starts.
    • Adopted the latest version of dbb-zappbuildopen in new window for User Build that now considers file tags for processing. The JSON dependency file will now be uploaded as a UTF-8 file. If you are using an older version of dbb-zappbuild, please update with the latest changes from its main branch on GitHub.
    • Fixed an issue that would show the command IBM User Build: Run IBM User Build for files with unsupported languages in the command palette.
    • Fixed an issue that prevented recognizing ZAPP files running in Eclipse Che when workspaces folders were added or removed.
    • Reviewed and revised multiple user interface strings and dialogs.
    • Updated code samples in https://github.com/IBM/zopeneditor-sample/tree/wazi-mainopen in new window with Ansible playbooks and host variables for IBM Wazi Sandbox and the IBM Wazi as a Service tutorials.
     1.4.1 - 2021/11/19
    • Fixed an issue with COBOL syntax highlighting of reference modifications (Issue 177open in new window)
    • Fixed the VS Code Toggle Line Comment (Cmd-/ or Ctrl-/) command for COBOL. You can now use it with the cursor being placed anywhere in the line as well as select a whole block of code and set or remove the comment symbol as a toggle. (Issue 157open in new window)
    • Fixed several issues with HLASM syntax highlighting related to continuation lines, macro definitions, and substitution characters. (Issue 118open in new window, Issue 185open in new window). See our Known Issuesopen in new window page for problems not solved, yet.
    • Fixed various inconsistencies with the HLASM outline view. It will now show the first occurrences of CSECTs, DSECTs, MACROs, Branch Targets, and Labels. (Issue 148open in new window). See our Known Issuesopen in new window page for problems not solved, yet.
    • Enhanced HLASM outline view to now display all labels. See Customizing the outline viewopen in new window to change what is included in the outline view.
    • Added support to use all REXX keywords as variables, excluding the 'END' keyword as well as improved the readability of keyword-related syntax error messages.
    • Fixed an issue in which trying to load remote include files from MVS using an invalid Zowe CLI Profile password could lock user accounts due to too many failed attempts. Z Open Editor will now prompt for a new password to update the profile or allow canceling all requests. This fix also adds support for using Zowe CLI profiles that do not store credentials and you will be prompted when required. (Issue 142open in new window)
    • Fixed an issue that prevented switching from Z Open Editor language servers to other languages. (Issue 164open in new window)
    • Fixed a regression in which a ZAPP file was not found when using it in an IBM RSE API for Zowe CLI command parameter or in Z Open Editor when specifying a file with zopeneditor.zowe.defaultRseConversionMappingsFile that was not in the current workspace.
    • Fixed an issue with User Build where dependencies would not upload again after making a change inside VS Code settings or ZAPP file settings.
    • Fixed an issue with User Build where remote dependencies were being uploaded on Windows.
    • Enhanced User Build messages to be more informative and actionable.
    • Fixed security related logging issue.
     1.4.0 - 2021/10/29
    • You can now use User Build without SSH when using IBM RSE API for Zowe CLI profiles. SSH Zowe CLI profiles are now required by z/OSMF only.
    • User Build speed is increased by sending additional dependency and metadata information to IBM Dependency Based Build on z/OS. Check the documentation for new dbb-zappbuild build script arguments.
    • When you save user or workspace settings, Z Open Editor will recognize and reload all Zowe CLI profiles, which is particularly useful when you add new profile names to the zopeneditor.zowe setting.
    • Support for ZAPP files with Z Open Editor is now also available when running in Eclipse Che, Red Hat CodeReady Workspaces, and IBM Wazi Developer for Workspaces.
    • Startup performance is faster with a smaller memory footprint due to significantly reduced language server sizes.
    • You can use the IBM Debug for z/OS High Level Assembler debug listing files with the language ID hlasmlst and the default file extension langx.
    • Fixed an issue in which a newly created ZAPP file was not recognized until the editor restarted.
    • Enhanced some UI strings for effectiveness including menus and Preferences names and descriptions.
    • New commands are added to IBM RSE API for Zowe CLI: 
      • zowe rse create data-set --like: Allocates a new data set with the same attributes as an existing data set specified by the --like option in IBM RSE API for Zowe CLI. The allocate-like functionality can now also be used with RSE profiles in Zowe Explorer. To use this feature, RSE API server 1.0.7 or later versions are required.
      • zowe rse check system-address-space: Displays all active system address space information in RSE CLI plug-in. To use this feature, RSE API 1.0.5 or later versions, and IBM Explorer for z/OS 3.2.0.16 or later versions are required.
      • zowe rse check job-address-space: Displays all active job address space information in RSE CLI plug-in. To use this feature, RSE API 1.0.5 or later versions and IBM Explorer for z/OS 3.2.0.16 or later versions are required.
     1.2.6 - 2021/08/19
    • Fixed an issue with PL/I compiler options for margins not being interpreted correctly in the editor. (Issue 135open in new window)
    • Fixed an issue that encoded special characters incorrectly in include file hovers for all languages. (Issue 128open in new window)
    • Fixed issues with HLASM code completion not appearing correctly in continuation and empty lines. (Issue 118open in new window)
    • Various fixes and improvements for REXX: 
      • Fixed issues with handling multi-line strings correctly for REXX.
      • Made code completion in REXX case-sensitive so that it preserves the casing style the user was using before initiating completion requests with Ctrl+Space.
      • Added an editor ruler at column 80 in REXX files. All editor rulers are customizable through the settings.
      • Added truncation warnings for characters after column 80 in REXX files. The column number is customizable through the settings.
      • Various REXX refinements that improve stability and performance of parsing and error messages.
    • Fixed an issue in IBM RSE API for Zowe CLI that prevented the use of the correct encoding for file uploads to USS, which also impacted uploads via Zowe Explorer using an RSE API profile. This fix requires Zowe Explorer 1.18.0 or newer.
    • Fixed an issue in User Build that prevented the use of the correct encoding as defined in .gitattributes to files uploaded via z/OSMF or RSE API profiles.
    • Addressed the user request to allow the zopeneditor.zowe settings to be scoped for workspace settings. This will be useful for development teams who standardize the names of their Zowe CLI profiles for their projects and use them for build automation. (Issue 143open in new window)
    • Adopted the new Zowe Explorer zowe.files.temporaryDownloadsFolder.cleanup setting to support the use of multiple VS Code windows showing the same files opened via Zowe Explorer, in order to see different parts of the same program on two different screens. Note that disabling the cleanup will result in files downloaded from z/OS not being removed when the editor is closed or restarted, so when you open a file via Zowe Explorer you may be viewing an outdated local version. Use the right-click "Pull from Mainframe" command to ensure you are working with the latest files.
    • Adopted new Zowe Explorer APIs that require Zowe Explorer 1.15.0 or newer to be installed. This release has been tested with Zowe Explorer 1.18.0.
     1.2.5 - 2021/06/18
    • Refined COBOL Renumber and Unnumber support making it configurable to work with columns 1-6 or 73-80 or both. If content other than numberic values is already present in these locations in a specific row then it will not update that location to preserve the content. (Issue 8open in new window)
    • Fixed syntax highlighting for HLASM beyond column 16. There is still an issue with code completion that well be addressed in a later release. (Issue 118open in new window)
    • Improved performance and reliability of downloading larger numbers of include files such as SYS1.MACLIB macros for the HLAMS editor hovers.
    • Removed the performance warning dialog for property groups and replaced it with log messages (Issue 15open in new window)
    • User Build now writes its output into a separate log file for users to share and analyze.
    • Adoption of new Zowe Explorer API ICommand to allow issuing of TSO commands using RSE profiles via Zowe Explorer 1.14.0 and higher.
    • RSE CLI plug-in updates: 
      • RSE CLI plug-in now prompts user for credentials for RSE profiles without user and password, during zowe rse auth login command to obtain JWT token, and if RSE API token is expired to obtain new token.
      • Fixed a regression that broke uploading a file as a sequential data set.
     1.2.1 - 2021/04/21
    • Made various improvements to our REXX language server and fixed defects: 
      • Added support for nested comments in REXX
      • Added support for keyword instructions as variables in REXX (excludes DO, IF, PARSE, SELECT, TRACE).
      • Fixed a find references bug in REXX where variables and functions with the same name matched
      • Fixed a find references bug in REXX where keywords could be used to find references
      • Refined the hover content and code completion detail in REXX to make the information more concise
      • Updated the hover content in IBM Documentation to point to the new IBM Documentation pages for the z/OS 2.4.0 TSO/E REXX Reference.
      • Standardized the syntax highlighting in REXX to color all keywords the same
      • Fixed a syntax highlighting bug in REXX where "value" following "address" was not displaying in color as a keyword
      • Fixed a syntax highlighting bug in REXX where the routine name following "call" was not displaying in color as a function
    • Reviewed and updated all output and log messages for the IBM RSE API Plug-in for Zowe CLI to ensure consistency. Locate the log file in ~/.zowe/zowe/logs/zowe.log.
    • Updated RSE API support for Zowe CLI base profilesopen in new window for the Zowe API Mediation Layer (APIML)open in new window Single Sign On (SSO) for User Build and using the RSE API behind the Zowe APIML. Refer to this new blog postopen in new window for an overview about how to use RSE API with the Zowe API Mediation Layer.
     1.2.0 - 2021/03/19
    • REXX language server: in this release we added language support for TSO/E REXX for z/OS. This first version includes syntax highlighting, syntax errors, code completion, find references, outline view, and rich documentation hover features. See our docs for all the details. (Issue 14open in new window)
    • Added full support for encoding conversions to/from UTF-8 to/from international EBCDIC code pages for all our z/OS MVS interactions that use RSE API 
      • Introduced a new mapping file concept to ZAPP as well as standalone JSON files that allow specifying mappings to groups or individual data sets or even members.
      • Added support for all RSE API CLI commands with new parameters as well as the ability to read mapping files that read and write to MVS.
      • All Z Open Editor remote MVS read operations using RSE API to find include files now can use mappings defined in ZAPP or user-local mappings files.
      • The Zowe Explorer integration with RSE API can also be configured to use mappings files for read and write operations of data set members.
    • Added EBCDIC conversion mappings for z/OS USS to User Build. Users can provide a standard .gitattributes file that specifies the encoding the program files should be converted to when uploaded to z/OS USS for a build.
    • Added context menus for COBOL with the ability to remove as well as renumber sequence numbers. (Issue 8open in new window)
    • Made include file resolution case-insensitive by default to support users with lowercase filenames and property group path names on local case-sensitive file systems such as Linux. As this can lead potentially to ambiguity problems we also added a new user setting called zopeneditor.enforceCaseSensitiveIncludeFileNames to enable case sensitive matching, even on case-insensitive operation systems such as Windows.
    • The command Reload Zowe Profiles that you can use when you changed your Zowe profiles, which was mainly introduced for User Build, now also restarts the language servers and retries loading any remote MVS include files with the updated profile information.
    • Added a new Welcome page for new users that interactively checks for prerequisites and gives tips for getting started.
    • Added support for APIML SSO for remote include file resolution such as COBOL Copybooks located on MVS. (Issue 107open in new window)
    • Fixed an issue in which invalid Zowe CLI profile configurations could cause Z Open Editor to not activate. We now show error messages and the editor is still usable. (Issue 110open in new window)
     1.1.3 - 2020/12/12
    • Fixed regression when resolving copybooks/include files with property groups that have multiple syslib/library entries. (Issue 105open in new window)
     1.1.2 - 2020/12/09
    • Added support for SYS1.MACLIB macros to HLASM for code completion. If you have a valid Zowe Explorer connection, it will even retrieve the macro definition automatically and show you in rich hovers when you typed or completed the macro name. Ensure that you enable this feature in user settings before using it.
    • Improved the way that Z Open Editor is looking for your Java Runtime or SDK. Review our updated documentation for the search order in which it tries to locate Java, as well as how you can override it with user settings. Added official support for Java Runtimes, and an SDK is not required anymore.
    • RSE CLI plug-in has added an encoding field that you can specify when creating or editing a Zowe RSE API CLI profile. You can use this field with newly added encoding tags for the commands of uploading and downloading MVS and USS files. Resolving copybooks will now use this encoding tag as well for RSE API and z/OSMF connections. (Issue 82open in new window)
    • RSE CLI plug-in now supports MVS binary downloads. (Issue 58open in new window)
    To update to RSE CLI plug-in 1.1.2, follow the instructions hereopen in new window for the optional migration.
     1.1.1 - 2020/11/6
     1.1.0 - 2020/10/23
    • ZAPP (Z APPlication) file support. Instead of mixing the configuration of your application with VS Code Preferences you can now specify property groups and IBM User Build configurations in a new simple yaml (or json) file located in your workspace that you can share with your team in Git. See our docs for a tutorial.
    • Added support for the Zowe CLI Secure Credentials Plugins for all Z Open Editor operations such as resolving include files or running user build (Issue 66open in new window)
    • Property Groups can now be scoped to one specific language making include file resolution more efficient as well as to support compiler options. (Issue 72open in new window).
    • Added the ability to provide language-specific compiler options such as OR('!') to property groups to configure the editor (Issue 17open in new window, Issue 61open in new window).
    • Include file resolution for COBOL and PL/I ignores SQLCA and SQLDA (Issue 71open in new window).
    • Fixed issues with COBOL 6.3 support such as >>if >>else >>end-if (Issue 65open in new window).
    • The logger now provides more configuration information that will help in your interactions with tech support.
    • Fixed issues managing Zowe Explorer favorites when using RSE API.
    • Revised profile validation in Zowe Explorer when using RSE API.
    We now include the IBM User Build VS Code Extension in IBM Z Open Editor. Changes since the 1.0.0 release:
    • In addition to COBOL we added support for building PL/I and HLASM programs with IBM Dependency-Based Build.
    • Fixed an issue with corrupted DBB log files when downloaded from USS.
    • User Build menus no longer appear for remote MVS or USS files opened via Zowe Explorer to avoid confusion about what can be built and what cannot.
    • Added more detailed log messages in the IBM User Build Output window, such as the full ssh commands executed, as a summary of all the user and workspace settings being used for a build and more. The output will list all required and optional settings and their values before the user build script is executed. If any required settings are missing, user build will stop execution explaining which setting caused the problem.
    • User Build can now run with files that contain spaces in their paths.
     1.0.3 - 2020/08/07
    • Added support for specifying custom include file extensions. You can now use the IBM Z Open Editor Preferences page to add and remove the file extensions to be used when searching for local include files such as COBOL copybooks. Also consistently added the Data Sets settings for remote include files to the visual editor allowing users to remove the mappings they do not want mapped in the files.association setting (Issue 16open in new window).
    • Added branch targets to the HLASM Outline view.
    • Fixed COBOL syntax highlighting that uses a "/" character for comments (Issue 60open in new window).
    • Fixed HLASM syntax highlighting for macros starting with a "$" character (Issue 69open in new window).
    • Added a support for using the java.home user setting for developers that install VS Code with the Microsoft Installer of VS Code for Java developeropen in new window or the Java Extension Pack.
    • Added a Zowe Profile validation routine that is called when adding and using RSE API profiles with Zowe Explorer 1.7 or newer.
     1.0.2 - 2020/06/30
    • Merged v0.5.2 with v1.0.1 to publish v1.0.2 to the VS Code Marketplace that now includes the language server for IBM High-Level Assembler (HLASM) for z/OS 2.4.
    • Reorganized the language server packaging to reduce the size of the extension to less than half than it was before.
     1.0.1/0.5.2 - 2020/06/23
    • Fixed false positives in Java compatibility check that prevented newer Java SDK versions than 8 to be used. (Issue 57open in new window)
     1.0.0 - 2020/06/12
     0.5.0 - 2020/06/12
    • Added syntax error checking for COBOL Copybooks.
    • Added support for CICS 5.6 syntax.
    • Rewrote the algorithm for searching for remote include files using Zowe CLI profiles.
    • Added user settings for specifying which Zowe CLI profile to use for finding remote include files on MVS in case you use multiple z/OSMF or RSE API CLI profiles.
    • Added Logger to analyze issues. Switch it on in the IBM Z Open Editor VS Code Preferences under User Settings.
    • Fixed bug with Unreachable Code Detection in COBOL EXECL SQL statements and switched default of the "zopeneditor.cobol.enableUnreachableCodeWarnings" Preferences setting back to true. (Issue 18open in new window)
    • Updated LSP4J language servers to baseline v0.9.0 and VS Code language clients to v6.1.3.
    • Improved LSP startup times.
    • Added more Java runtime checks to ensure you are using a valid Java SDK with the Z Open Editor extension.
    • Various enhancements and fixes for RSE API support such as Get JCL from the Zowe Explorer JES view as well as Migrate/Recall from the Zowe Explorer MVS view.
    • Fixed rare race condition when starting language servers. (Issue 45open in new window)
    • Various stability fixes and refinements.
     0.4.9 - 2020/04/23
    • Fixed an issue when using RSE for the Zowe Explorer JES view.
    • Fixed errors messages users saw when creating z/OSMF profiles in Zowe Explorer when Zowe CLI and/or the IBM RSE API Plugin for Zowe CLI was not installed.
     0.4.7 - 2020/03/27
    • Added Beta-level support for the new Remote System Explorer API (RSEAPI) REST servers that can be used as an alternative to z/OSMF for remote file operations as well as Zowe Explorer visual explorer views. If you run RSE already for IBM Developer for Z or IBM z/OS Explorer you can simply update. Go to https://ibm.github.io/zopeneditor-aboutopen in new window for more details.
    • Reduced the memory consumption of the extension by starting language servers only if a program in a specifc language is opened for the first time. This will avoid that you are wasting valuable PC memory for languages that you do not use. In addition we added two optional commands that you can run to pause the COBOL or PL/I language server once you finished with one language and want to free up its memory. When you open a program of that language again the language server will restart.
    • Added code actions that provide suggestions for resolving COBOL copybooks and PL/I include files by linking to Online Help pages.
    • Removed MQ code templates for now as we ran into some language compatibility issues.
     0.4.5 - 2020/01/07
    • Added an additional 27 code snippets for MQ development with COBOL and 27 for MQ with PL/I.
     0.4.3 - 2019/12/18
    • Added more code snippets for COBOL, PL/I and JCL, which brings it to a total of 186. For COBOL we now provide 27 General COBOL language support snippets, 12 Embedded SQL snippets, 29 for CICS, 12 for IMS, and 8 for VSAM. Similarly, we provide for PL/I 12 General PL/I language support snippets, 29 CICS, 11 IMS, and 7 VSAM. Finally, we have 27 code snippets for JCL.
     0.4.1 - 2019/11/21
    • Language server updates to support IBM Enterprise COBOL v6.3 and PL/I v5.3.
    • Added all new sets of IBM field contributed code snippets for COBOL embedded SQL and CICS, PL/I embedded SQL, and various new JCL snippets. This is just the beginning of us curating a larger portfolio of high-value code snippets and incrementally releasing these in the coming months. Keep and eye out and let us know what you think of these snippetsopen in new window.
    • Added an import command for loading Code Snippets exported by the IBM Developer from z/OS. Do you have your own set of code snippets that you managed in the Snippets view in IDz? You can now export and import these into Z Open Editor.
    • Switched off COBOL Unreachable Code warnings by default as there are cases in which it can provide false positives (see hereopen in new window for details). If you can accept the risk of a few false reports then you can enable it again by using the "zopeneditor.cobol.enableUnreachableCodeWarnings": true VS Code user or workspace setting.
    • Fixed a code completion bug for COBOL and PL/I that would erase text to the right of the cursor.
    • Fixed cases in which COBOL statements before the IDENTIFICATION DIVISION would break syntax checking. (Issue #9open in new window)
    • Fixed exceptions thrown by the PL/I LSP when computing document links (Issue #13open in new window)
    • Fixed issues with COBOL Unreachable Code warnings not being shown at all in some cases. (Issue #7open in new window)
    • Fixed an issue in which invalid PIC clauses would not be reported as syntax errors.
     0.3.11 - 2019/09/27
    • "Unreachable Code" is not reported as an error anymore, but is now a warning message in the Problems View.
    • Switch off "Unreachable Code" detection completely with this new setting: "zopeneditor.cobol.enableUnreachableCodeWarnings": false.
    • We implemented GLOB pattern matching in Property Group settings for finding Copybooks on the local file system as requested in this issueopen in new window. Use with care as a very large search space will slow down the editor.
    • We added support for VS Code Multi-root Workspacesopen in new window allowing you to now specify Property Groups for finding Copybooks for a workspace comprising of many development project folders and Git repositories. To use it move your Property Groups to the Workspace File.
    • We updated and revised our documentation for using Property Groups with patterns and workspaces in the Online Helpopen in new window. We also added examples for using it on Windows versus Mac/Linux.
    • Fixed an issue with using the Tab key in Code Snippets and when using it for indentation in the editor.
     0.3.9 - 2019/09/23
    • Just removed Preview flag in preparation for the announcement.
    • Stay tuned for more cool things to come.
     0.3.7 - 2019/09/17
    • Fixes to the documentation and hyperlinks.
    • Renamed extension preferences configuration name.
     0.3.5 - 2019/09/13
    • First public release evolving out of the Wazi technology preview. See README.md for details.
    Last Updated: 
    Contributors: Peter Haumer, Peter Haumer, PETER HAUMER, kmaselli, Billie Jean Simmons, Chun Hong Zheng, Lauren Li, Hestia Zhang, KRISTINA MAYO, Lauren Li, Min Huang, Prasang-A-Prajapati, Saile Daimwood, Shi Kun Li, shikunli
    
+    
   
 
diff --git a/Blog/ocp-ssl-cert.html b/Blog/ocp-ssl-cert.html
index afe4d33e1..04ee83b74 100644
--- a/Blog/ocp-ssl-cert.html
+++ b/Blog/ocp-ssl-cert.html
@@ -41,11 +41,11 @@
                 }
             )();
             IBM Wazi Developer for Red Hat CodeReady Workspaces: Set up an SSL Certificate in an OpenShift Container Platform | IBM Z® Open Editor
-    
+    
     
   
   
-    
    IBM Z® Open Editor
     IBM Wazi Developer for Red Hat CodeReady Workspaces: Set up an SSL Certificate in an OpenShift Container Platform
    by Arvin Bhatnagar
    A number of cloud based applications that run on OpenShift® Container Platform (OCP) uses a signed SSL certificateopen in new window to provide encryption over the wire. For instance, IBM® Wazi Developer for Red Hat® CodeReady Workspacesopen in new window, a single integrated solution that delivers a cloud native development experience for z/OS®, uses a signed SSL certificate for encryption by default. More information about IBM Wazi Developer for Red Hat CodeReady Workspaces can be found in the IBM Documentationopen in new window.
     Why a signed SSL certificate is needed
    Setting up an OpenShift Container Platform with a signed SSL certificate can present a number of challenges. The challenges are due to complex cloud architectures and the various formats and types of certificates to contend with. These complexities and the volume of information can make the overall process overwhelming to simply replace a default self-signed certificate with a signed certificate from a trusted CA server.
    An OCP Ingress Controlleropen in new window accepts external web based requests and proxys them based on the configured routes. The default certificate for an Ingress Controller is a self-signed certificate used for all applications under the .apps subdomain. Replacing the default certificate with one issued by a public Certificate of Authority (CA) allows incoming requests to connect securely to cloud based applications without the hassle of security warnings.
     How to set up a signed SSL certificate
    1. Request a certificate.
      The certificate for the Ingress Controller .apps subdomain must be a wildcard certificate. For example, if the domain of the OCP is openshift.ibm.com then the wildcard would be *.apps.openshift.ibm.com. A sample certificate server request using the OpenSSL toolopen in new window would be something similar to the following:
      openssl req -new -sha256 -nodes -out certserverrequest.csr -newkey rsa:2048 -keyout certserverkey.key -config <(
+    
      IBM Z® Open Editor
       IBM Wazi Developer for Red Hat CodeReady Workspaces: Set up an SSL Certificate in an OpenShift Container Platform
      by Arvin Bhatnagar
      A number of cloud based applications that run on OpenShift® Container Platform (OCP) uses a signed SSL certificateopen in new window to provide encryption over the wire. For instance, IBM® Wazi Developer for Red Hat® CodeReady Workspacesopen in new window, a single integrated solution that delivers a cloud native development experience for z/OS®, uses a signed SSL certificate for encryption by default. More information about IBM Wazi Developer for Red Hat CodeReady Workspaces can be found in the IBM Documentationopen in new window.
       Why a signed SSL certificate is needed
      Setting up an OpenShift Container Platform with a signed SSL certificate can present a number of challenges. The challenges are due to complex cloud architectures and the various formats and types of certificates to contend with. These complexities and the volume of information can make the overall process overwhelming to simply replace a default self-signed certificate with a signed certificate from a trusted CA server.
      An OCP Ingress Controlleropen in new window accepts external web based requests and proxys them based on the configured routes. The default certificate for an Ingress Controller is a self-signed certificate used for all applications under the .apps subdomain. Replacing the default certificate with one issued by a public Certificate of Authority (CA) allows incoming requests to connect securely to cloud based applications without the hassle of security warnings.
       How to set up a signed SSL certificate
      1. Request a certificate.
        The certificate for the Ingress Controller .apps subdomain must be a wildcard certificate. For example, if the domain of the OCP is openshift.ibm.com then the wildcard would be *.apps.openshift.ibm.com. A sample certificate server request using the OpenSSL toolopen in new window would be something similar to the following:
        openssl req -new -sha256 -nodes -out certserverrequest.csr -newkey rsa:2048 -keyout certserverkey.key -config <(
 cat <<-EOF
 [ req ]
 default_bits = 2048
@@ -76,6 +76,6 @@
 
      2. Create a secret for the certificate and private key using ocpcert.pem and certserverkey.key.
        oc create secret tls <Secret Name> --cert=<ocpcert.pem> --key=<certserverkey.key> -n openshift-ingress
 
      3. Update the Ingress Controller configuration with the secret we just created.
        oc patch ingresscontroller.operator default --type=merge -p '{"spec":{"defaultCertificate": {"name": "<Secret Name>"}}}' -n openshift-ingress-operator
 
        Reference Replacing the default ingress certificateopen in new window
      When a signed SSL certificate iss issued by a trusted CA server, then there is no further configurations required by the client browser accessing applications running on the OpenShift Container Platform from the .apps subdomain. It is recommended to use certificates from a trusted CA server versus a self-signed SSL certificate which would require further configurations on all client browsers to import both the intermediate and root certificates.
      The approach and instructions introduced in this article applies to an OpenShift Container Platform 4.3, but it might be applicable to later versions. Always confirm with the OpenShift documentation before proceeding.
      Last Updated: 
      Contributors: Arvin Bhatnagar, Hestia Zhang, Min Huang, Peter Haumer, Peter Haumer, kmaselli
      
-    
+    
   
 
diff --git a/Blog/rse-march-120.html b/Blog/rse-march-120.html
index 312e7bb1e..73404d9a9 100644
--- a/Blog/rse-march-120.html
+++ b/Blog/rse-march-120.html
@@ -41,11 +41,11 @@
                 }
             )();
             Everything you need to know about IBM RSE API Plug-in for Zowe CLI 1.2.0 | IBM Z® Open Editor
-    
+    
     
   
   
-    
      IBM Z® Open Editor
       Everything you need to know about IBM RSE API Plug-in for Zowe CLI 1.2.0
      by Billie Simmons
       Last updated: 17 March 2021
      We are excited to announce the release of IBM® RSE API Plug-in for Zowe™ CLI (RSE CLI plug-in) 1.2.0 with the following key updates:
       Support for encoding conversion for z/OS MVS
      Starting from RSE CLI plug-in 1.2.0, there are multiple ways to support encoding conversions for MVS. These ways follow the precedence rules below:
      1. Add the --encoding tag to the end of upload and download CLI commands.
      2. --mappings-file tag with location of a mappings file that follows the schemaopen in new window set in place.
        The --mappings-file tag can be used via CLI command at the end of MVS upload and download commands to point to a mappings file that is saved locally and not in the default location within the ~/.zowe/profiles/rse directory, or a ZAPP file that includes the MVS mappings schema.
      3. An encoding found in the current workspace within the ZAPP (Z APPlication) fileopen in new window.
        The ZAPP file is created in your development workspace's top-level directory. It can contain project-level property groups as well as other information. This file can be in JSON or YAML format.
      4. An encoding found in the default mappings file.
        The default mappings file is a new file that can be downloaded from the RSE API host component using the CLI command zowe rse check conversion-mappings. This default mappings file will then be downloaded to the ~/.zowe/profiles/rse directory. To learn more about RSE CLI plug-in's mappings files, check out the documentation on MVS EBCIDIC code pages and mappings filesopen in new window.
      5. An encoding set during RSE profile creation.
        When creating your RSE profile via CLI command, the --encoding tag can added to the command to set a default encoding that can be put in place while using that profile. When you create your RSE profile using Zowe Explorer, you will see an encoding option pop up to enter a default encoding value. In both cases, this value is optional and no default will be set in case you would prefer to use the host encoding settings set by a system administrator.
      6. Server default mappings.
       Support for SSO
      Starting from 1.2.0, the RSE CLI plug-in has full support for SSO using JSON Web Tokens (JWT) that are provided by the RSE API host component and the use of a base profileopen in new window. This support can also be used by IBM Z® Open Editor remote file resolutionopen in new window.
       Uploading and downloading MVS files as binary
      You can now add the --binary tag to the commands of uploading and downloading of MVS files. This tag was added to the following commands:
      • upload dir-to-pds
      • upload file-to-data-set
      • download data-set
      • download all-members
      MVS member filter search is supported starting from RSE CLI plug-in 1.2.0, and is realized as a tag to the CLI command zowe rse list all-members by adding --pattern <memberPattern> to the end of the list command.
      You can also use this feature in Zowe Explorer 1.12.0 or later versions by clicking the magnifying glass next to a profile's session name and entering a search pattern similar to HLQ.DATA.SET(*MEM).
       Copying and pasting PDS members
      You can copy and paste PDS members via CLI command and within the Zowe Explorer VS Code extension:
      • CLI command: Use the zowe rse copy data-set command to copy PDS members to a new member in another PDS as well as copy a Sequential data set to a new Sequential data set.
      • Zowe Explorer VS Code extension: Right-click on a PDS member to copy it, and right-click on a different PDS to paste and name the new member.
       Support for UNIX shell commands
      You can now issue UNIX shell commands by using a CLI command. The zowe rse issue unix <command> --cwd <workingDir> command can be issued via terminal, and a JSON that includes stdout and stderr will be returned.
       Changing your password on z/OS
      Starting from RSE CLI plug-in 1.2.0, you can change your password on z/OS via a CLI command, rather than green screen. You can now enter the CLI command zowe rse change password in a terminal to change your password on z/OS and update the profile's YAML file if the password is stored locally with or without the Secure Credential Store Plug-in for Zowe CLIopen in new window installed.
      You can check out all of the commands and their syntax at IBM RSE API Plug-in for Zowe CLI commandsopen in new window.
      Last Updated: 
      Contributors: Billie Simmons, Min Huang, Lauren Li, PETER HAUMER
      
-    
+    
      IBM Z® Open Editor
       Everything you need to know about IBM RSE API Plug-in for Zowe CLI 1.2.0
      by Billie Simmons
       Last updated: 17 March 2021
      We are excited to announce the release of IBM® RSE API Plug-in for Zowe™ CLI (RSE CLI plug-in) 1.2.0 with the following key updates:
       Support for encoding conversion for z/OS MVS
      Starting from RSE CLI plug-in 1.2.0, there are multiple ways to support encoding conversions for MVS. These ways follow the precedence rules below:
      1. Add the --encoding tag to the end of upload and download CLI commands.
      2. --mappings-file tag with location of a mappings file that follows the schemaopen in new window set in place.
        The --mappings-file tag can be used via CLI command at the end of MVS upload and download commands to point to a mappings file that is saved locally and not in the default location within the ~/.zowe/profiles/rse directory, or a ZAPP file that includes the MVS mappings schema.
      3. An encoding found in the current workspace within the ZAPP (Z APPlication) fileopen in new window.
        The ZAPP file is created in your development workspace's top-level directory. It can contain project-level property groups as well as other information. This file can be in JSON or YAML format.
      4. An encoding found in the default mappings file.
        The default mappings file is a new file that can be downloaded from the RSE API host component using the CLI command zowe rse check conversion-mappings. This default mappings file will then be downloaded to the ~/.zowe/profiles/rse directory. To learn more about RSE CLI plug-in's mappings files, check out the documentation on MVS EBCIDIC code pages and mappings filesopen in new window.
      5. An encoding set during RSE profile creation.
        When creating your RSE profile via CLI command, the --encoding tag can added to the command to set a default encoding that can be put in place while using that profile. When you create your RSE profile using Zowe Explorer, you will see an encoding option pop up to enter a default encoding value. In both cases, this value is optional and no default will be set in case you would prefer to use the host encoding settings set by a system administrator.
      6. Server default mappings.
       Support for SSO
      Starting from 1.2.0, the RSE CLI plug-in has full support for SSO using JSON Web Tokens (JWT) that are provided by the RSE API host component and the use of a base profileopen in new window. This support can also be used by IBM Z® Open Editor remote file resolutionopen in new window.
       Uploading and downloading MVS files as binary
      You can now add the --binary tag to the commands of uploading and downloading of MVS files. This tag was added to the following commands:
      • upload dir-to-pds
      • upload file-to-data-set
      • download data-set
      • download all-members
      MVS member filter search is supported starting from RSE CLI plug-in 1.2.0, and is realized as a tag to the CLI command zowe rse list all-members by adding --pattern <memberPattern> to the end of the list command.
      You can also use this feature in Zowe Explorer 1.12.0 or later versions by clicking the magnifying glass next to a profile's session name and entering a search pattern similar to HLQ.DATA.SET(*MEM).
       Copying and pasting PDS members
      You can copy and paste PDS members via CLI command and within the Zowe Explorer VS Code extension:
      • CLI command: Use the zowe rse copy data-set command to copy PDS members to a new member in another PDS as well as copy a Sequential data set to a new Sequential data set.
      • Zowe Explorer VS Code extension: Right-click on a PDS member to copy it, and right-click on a different PDS to paste and name the new member.
       Support for UNIX shell commands
      You can now issue UNIX shell commands by using a CLI command. The zowe rse issue unix <command> --cwd <workingDir> command can be issued via terminal, and a JSON that includes stdout and stderr will be returned.
       Changing your password on z/OS
      Starting from RSE CLI plug-in 1.2.0, you can change your password on z/OS via a CLI command, rather than green screen. You can now enter the CLI command zowe rse change password in a terminal to change your password on z/OS and update the profile's YAML file if the password is stored locally with or without the Secure Credential Store Plug-in for Zowe CLIopen in new window installed.
      You can check out all of the commands and their syntax at IBM RSE API Plug-in for Zowe CLI commandsopen in new window.
      Last Updated: 
      Contributors: Billie Simmons, Min Huang, Lauren Li, PETER HAUMER
      
+    
   
 
diff --git a/Blog/rse-march-beta.html b/Blog/rse-march-beta.html
index 4accb19c4..46bb85fca 100644
--- a/Blog/rse-march-beta.html
+++ b/Blog/rse-march-beta.html
@@ -41,11 +41,11 @@
                 }
             )();
             Interacting with z/OS using IBM RSE API Plug-in for Zowe CLI | IBM Z® Open Editor
-    
+    
     
   
   
-    
      IBM Z® Open Editor
       Interacting with z/OS using IBM RSE API Plug-in for Zowe CLI
      by Billie Simmons.
       Last updated: 10 June, 2020
      Update: As of 12 June, 2020 IBM RSE API Plug-in for Zowe CLI is generally available.
      We are excited to announce the Beta release of IBM RSE API Plug-in for Zowe CLIopen in new window, which now comes packaged with the VS Code download for IBM Developer for z/OS Enterprise Edition. This plug-in allows you to interact with z/OS by using IBM Remote System Explorer API (RSE API)open in new window, which now comes packaged with IBM Explorer for z/OS. If you have already used the Remote System Explorer (RSE) with other IBM offerings such as IBM Developer for z/OS or IBM Explorer for z/OS, this plug-in was built just for you.
      When using the IBM RSE API Plug-in for Zowe CLI with RSE API support, not only can you execute CLI operations, but you can also use the RSE protocol in combination with the Zowe Exploreropen in new window (v1.3.1 and above) and IBM Z Open Editoropen in new window VS Code extensions to graphically navigate and access file and job resources on your host system. The IBM Z Open Editor VS Code extension allows you to activate the use of the RSE plug-in profiles within Zowe Explorer in VS Codeopen in new window. You can use the RSE plug-in to perform the following tasks:
      • List, create, rename, delete USS files and directories and MVS data sets and members
      • Run JCL
      • Browse job spool files
      • Edit COBOL and PL/I files on z/OS by using the IBM Z Open Editor and Zowe Explorer VS Code extensions
      All commands and actions using Zowe Explorer that the Zowe CLI Profile offers are available using the RSE Profile with a few exceptions that are documented in our Known Issues page. For details about getting started with IBM RSE API Plug-in for Zowe CLI, check out our documentation on Interacting with z/OS® using RSE API.
       Using the RSE Plug-in via command line
      The RSE plug-in can be used in a command-line window on your development machine. Using it this way allows you to issue commands to perform the following tasks:
      • List, create, download, upload, and delete MVS data sets and members as well as USS files and directories.
      • Submit jobs, list jobs and spool files, download or view spool content, view job status, cancel a job, and delete a job.
      You can learn more about any command and all of its options simply by adding --help after the command. For instance, by typing zowe rse list --help, you can see all of the different items that can be listed using the RSE plug-in and a help response that gives details about the options as a response within the command-line window. You can also view help for all of the options through your web browser by adding --help-web after the command.
      Viewing Web Help
      For more information and a chart of all the available CLI commands IBM RSE API Plug-in for Zowe CLI has to offer at this time, take a look at our documentation on Using the RSE API CLI.
       Using an RSE profile with the Zowe Explorer VS Code extension
      Zowe Explorer now has an extensibility API that supports adding other protocols and IBM Z Open Editor includes such an extension utilizing the RSE CLI Plugin codebase. With this extensibility, having the IBM Z Open Editor VS Code extension allows you to use an RSE profile to connect to the host using Zowe Explorer to view a tree list of data sets and members in the DATA SETS view, UNIX files and directories in the UNIX SYSTEM SERVICES (USS) view, and jobs with spool files in the JOBS view.
      Within the Zowe Explorer views, you can perform the following tasks using the RSE plug-in:
      • Create, edit, save, rename, delete data sets, members, UNIX files, and directories on the host.
      • Upload local files as a partitioned data set member or as a sequential data set.
      • Submit JCL data sets or members as a job, delete jobs, download job spool files from the host to a local directory, and view job spool files in the text editor.
      Creating a New Data Set
      If you would like to know more about managing data sets using the Zowe Explorer VS Code extension, see our documentation on Manipulating data sets.
      To learn how to use IBM RSE API Plug-in for Zowe CLI with Zowe Explorer and IBM Z Open Editor, check out our documentation on Using RSE API in the Zowe Explorer VS Code extension.
       Getting hands-on
      Many developers learn best with hands-on experience, so we have developed a few exercises through which you can explore the different ways of using IBM RSE API Plug-in for Zowe CLI. Our tutorial covers three great approaches to managing z/OS resources with the plug-in:
      Ready to try out these hands-on approaches? Head over to the Tutorial page, which will point you to a sample repository and get you started with creating your RSE profile.
      Take a look at my video tutorials that cover these three approaches:
       We would love to hear from you
      Once you have tried out IBM RSE API Plug-in for Zowe CLI, we would love to hear what you think of it. For any questions, issues, or enhancement ideas, please do not hesitate to open an issue at our GitHubopen in new window. We are always looking for ways to improve our product.
      Last Updated: 
      Contributors: BillieJean-Simmons, Peter Haumer, Lauren Li, Peter Haumer, shikunli
      
-    
+    
      IBM Z® Open Editor
       Interacting with z/OS using IBM RSE API Plug-in for Zowe CLI
      by Billie Simmons.
       Last updated: 10 June, 2020
      Update: As of 12 June, 2020 IBM RSE API Plug-in for Zowe CLI is generally available.
      We are excited to announce the Beta release of IBM RSE API Plug-in for Zowe CLIopen in new window, which now comes packaged with the VS Code download for IBM Developer for z/OS Enterprise Edition. This plug-in allows you to interact with z/OS by using IBM Remote System Explorer API (RSE API)open in new window, which now comes packaged with IBM Explorer for z/OS. If you have already used the Remote System Explorer (RSE) with other IBM offerings such as IBM Developer for z/OS or IBM Explorer for z/OS, this plug-in was built just for you.
      When using the IBM RSE API Plug-in for Zowe CLI with RSE API support, not only can you execute CLI operations, but you can also use the RSE protocol in combination with the Zowe Exploreropen in new window (v1.3.1 and above) and IBM Z Open Editoropen in new window VS Code extensions to graphically navigate and access file and job resources on your host system. The IBM Z Open Editor VS Code extension allows you to activate the use of the RSE plug-in profiles within Zowe Explorer in VS Codeopen in new window. You can use the RSE plug-in to perform the following tasks:
      • List, create, rename, delete USS files and directories and MVS data sets and members
      • Run JCL
      • Browse job spool files
      • Edit COBOL and PL/I files on z/OS by using the IBM Z Open Editor and Zowe Explorer VS Code extensions
      All commands and actions using Zowe Explorer that the Zowe CLI Profile offers are available using the RSE Profile with a few exceptions that are documented in our Known Issues page. For details about getting started with IBM RSE API Plug-in for Zowe CLI, check out our documentation on Interacting with z/OS® using RSE API.
       Using the RSE Plug-in via command line
      The RSE plug-in can be used in a command-line window on your development machine. Using it this way allows you to issue commands to perform the following tasks:
      • List, create, download, upload, and delete MVS data sets and members as well as USS files and directories.
      • Submit jobs, list jobs and spool files, download or view spool content, view job status, cancel a job, and delete a job.
      You can learn more about any command and all of its options simply by adding --help after the command. For instance, by typing zowe rse list --help, you can see all of the different items that can be listed using the RSE plug-in and a help response that gives details about the options as a response within the command-line window. You can also view help for all of the options through your web browser by adding --help-web after the command.
      Viewing Web Help
      For more information and a chart of all the available CLI commands IBM RSE API Plug-in for Zowe CLI has to offer at this time, take a look at our documentation on Using the RSE API CLI.
       Using an RSE profile with the Zowe Explorer VS Code extension
      Zowe Explorer now has an extensibility API that supports adding other protocols and IBM Z Open Editor includes such an extension utilizing the RSE CLI Plugin codebase. With this extensibility, having the IBM Z Open Editor VS Code extension allows you to use an RSE profile to connect to the host using Zowe Explorer to view a tree list of data sets and members in the DATA SETS view, UNIX files and directories in the UNIX SYSTEM SERVICES (USS) view, and jobs with spool files in the JOBS view.
      Within the Zowe Explorer views, you can perform the following tasks using the RSE plug-in:
      • Create, edit, save, rename, delete data sets, members, UNIX files, and directories on the host.
      • Upload local files as a partitioned data set member or as a sequential data set.
      • Submit JCL data sets or members as a job, delete jobs, download job spool files from the host to a local directory, and view job spool files in the text editor.
      Creating a New Data Set
      If you would like to know more about managing data sets using the Zowe Explorer VS Code extension, see our documentation on Manipulating data sets.
      To learn how to use IBM RSE API Plug-in for Zowe CLI with Zowe Explorer and IBM Z Open Editor, check out our documentation on Using RSE API in the Zowe Explorer VS Code extension.
       Getting hands-on
      Many developers learn best with hands-on experience, so we have developed a few exercises through which you can explore the different ways of using IBM RSE API Plug-in for Zowe CLI. Our tutorial covers three great approaches to managing z/OS resources with the plug-in:
      Ready to try out these hands-on approaches? Head over to the Tutorial page, which will point you to a sample repository and get you started with creating your RSE profile.
      Take a look at my video tutorials that cover these three approaches:
       We would love to hear from you
      Once you have tried out IBM RSE API Plug-in for Zowe CLI, we would love to hear what you think of it. For any questions, issues, or enhancement ideas, please do not hesitate to open an issue at our GitHubopen in new window. We are always looking for ways to improve our product.
      Last Updated: 
      Contributors: BillieJean-Simmons, Peter Haumer, Lauren Li, Peter Haumer, shikunli
      
+    
   
 
diff --git a/Blog/rse-october-110.html b/Blog/rse-october-110.html
index 30014de94..49e6c23d2 100644
--- a/Blog/rse-october-110.html
+++ b/Blog/rse-october-110.html
@@ -41,14 +41,14 @@
                 }
             )();
             What's new with IBM RSE API Plug-in for Zowe CLI 1.1.0 | IBM Z® Open Editor
-    
+    
     
   
   
-    
      IBM Z® Open Editor
       What's new with IBM RSE API Plug-in for Zowe CLI 1.1.0
      by Billie Simmons.
       Last updated: 19 October, 2020
      There are some great new features in IBM RSE API Plug-in for Zowe CLI 1.1.0 that we are excited to share. With this release in conjunction with the release of IBM Remote System Explorer API (RSE API) 1.0.1, we will be introducing the following capabilities:
      These new features in the IBM RSE API Plug-in for Zowe CLI with RSE API support are introduced for execution as CLI operations.
       Download UNIX files as binary
      In this release, the binary tag for downloading UNIX files has been added as an option for downloading a USS file without translation via CLI command. You can find an example in the command help doc by issuing the following command:
      zowe rse download uss-file --help
+    
      IBM Z® Open Editor
       What's new with IBM RSE API Plug-in for Zowe CLI 1.1.0
      by Billie Simmons.
       Last updated: 19 October, 2020
      There are some great new features in IBM RSE API Plug-in for Zowe CLI 1.1.0 that we are excited to share. With this release in conjunction with the release of IBM Remote System Explorer API (RSE API) 1.0.1, we will be introducing the following capabilities:
      These new features in the IBM RSE API Plug-in for Zowe CLI with RSE API support are introduced for execution as CLI operations.
       Download UNIX files as binary
      In this release, the binary tag for downloading UNIX files has been added as an option for downloading a USS file without translation via CLI command. You can find an example in the command help doc by issuing the following command:
      zowe rse download uss-file --help
 
      Download Binary OptionBinary Download Command Example
       Get system and application information from the host
      Another new feature is the Check Status command that can be used to confirm that the RSE API server is running, as well as to gather information about the RSE API server for diagnostic puposes. The command outputs properties of the RSE API server such as the RSE version, RSE API version, and the port the server is running on, as well as z/OS system information such as the z/OS version and the host name.
      zowe rse check status
 
      The output contains the following information:
      Check Status Output
       Issue TSO commands
      IBM RSE API plug-in for Zowe CLI now has TSO capabilities, allowing users to input TSO commands and get a response back from a TSO session. To use it, replace COMMAND with your TSO command in the CLI command example below.
      zowe rse issue command "COMMMAND"
 
      This command creates a TSO address space, issues the TSO command through the newly created address space, waits for the READY prompt to print the response, and then terminates the TSO address space after returning the response.
      Issue TSO Command
       Use JSON Web Tokens (JWT) for authentication with the host
      Last, but definitely not least, is the addition of the use of JSON Web Tokens (JWT) for authentication with the host. This feature allows you to connect to the RSE API Server authentication service and obtain a token. The token provides authentication to services that are supported by the RSE API. When you log in, the token is stored in your profile's local YAML file until you issue the logout command. Profiles store connection information, and are used if you do not supply connection information in a command. This addition brings in three new commands that include:
      • zowe rse auth login
        Log in to an authentication service to obtain a JWT Token.
      • zowe rse auth query
        Get back JWT Token information if it is not yet expired.
      • zowe rse auth logout
        Log out of the authentication service and retire the JWT Token.
      At this time, username and password are still required during creation of the profile using command line operations, but the order of precedence kicks in if a JWT token is present in the profile. The RSE CLI plug-in will first check for a token. If the token is not present, then it will then check for username and password to authenticate with the host.
       Trying out the latest release
      To get your hands on the latest release and try out the new features, head over to Setting up integrations to interact with z/OS and see the documentation on how to get started. There, you can get the link to the download sites for IBM RSE API Plug-in for Zowe CLI and its host components.
      There are some known issues for these new commands and they are documented in our Known issues page.
      Last Updated: 
      Contributors: Billie Simmons, Lauren Li, Peter Haumer
      
-    
+    
   
 
diff --git a/Blog/userbuild-blog.html b/Blog/userbuild-blog.html
index a8b3da354..cad46bbd4 100644
--- a/Blog/userbuild-blog.html
+++ b/Blog/userbuild-blog.html
@@ -41,11 +41,11 @@
                 }
             )();
             IBM Z® Open Editor makes building COBOL, PL/I, and HLASM applications easier with User Build | IBM Z® Open Editor
-    
+    
     
   
   
-    
      IBM Z® Open Editor
       IBM Z® Open Editor makes building COBOL, PL/I, and HLASM applications easier with User Build
      by Kristina Mayo
      There is a new exciting feature in the IBM Z Open Editor VS Code extension, it's called User Build. User Build allows you as a z/OS® developer who writes COBOL, PL/I, or HLASM to build your applications directly out of VS Code or CodeReady Workspaces.
      This feature is created for you if you are an IBM® Dependency Based Buildopen in new window user and would like to try developing in VS Code. User Build enables you to:
      • Build applications without interrupting your workflow and going outside the IDE.
      • Quickly compile code changes without opening a pull request or sharing the code with others.
       Architectural overview
      As an overview, User Build builds a program by performing the following tasks automatically:
      • Uploads the application file to z/OS.
      • Uploads the application's copybooks and include files to z/OS.
      • Invokes the remote build script that you defined in User Build settings.
      • Downloads build log files locally for easier viewing.
      User Build diagram
      Notes:
      • User Build does not require Git to work.
      • User can specify a custom script to execute for User Build, though DBB with zAppBuild solution is recommended.
       Prerequisites
      Before using the user build feature, ensure that the following host and client requirements are met.
      Host requirements:
      Client requirements:
       User build settings
      Before running User Build, you need to configure it via settings to tell User Build where on z/OS to upload files and which build script to execute. The settings should be defined and store as JSON inside VS Code settings filesopen in new window.
      User Build has 2 types of settings: workspace settings and user settings, though both can be placed inside workspace settings file for convenience. See user build docsopen in new window for detailed descriptions of each setting.
      The following example shows workspace and user settings are all stored inside zopeneditor-sample/.vscode/settings.json for convenience. User Build settings example
       Running User Build
      Once settings are filled out, right-click inside a file in the editor, select Run IBM User Build to execute remote script and see results directly in VS Code.
      User Build menus inside VS Code
      The user build log will be streamed in the Output panel inside VS Code. The build is successful when you see the message Build State: CLEAN in the output. The picture below shows successful zAppBuild output for a COBOL application and a log file.
      User Build successful COBOL build
       Trying out User Build
      To get started with User Build, follow this hands-on tutorialopen in new window to use IBM's sample code and the defined workspace settings in the repository.
      For full documentation, refer to Setting up the user buildopen in new window.
      Last Updated: 
      Contributors: KRISTINA MAYO, Min Huang, Hestia Zhang, Peter Haumer, kmaselli
      
-    
+    
      IBM Z® Open Editor
       IBM Z® Open Editor makes building COBOL, PL/I, and HLASM applications easier with User Build
      by Kristina Mayo
      There is a new exciting feature in the IBM Z Open Editor VS Code extension, it's called User Build. User Build allows you as a z/OS® developer who writes COBOL, PL/I, or HLASM to build your applications directly out of VS Code or CodeReady Workspaces.
      This feature is created for you if you are an IBM® Dependency Based Buildopen in new window user and would like to try developing in VS Code. User Build enables you to:
      • Build applications without interrupting your workflow and going outside the IDE.
      • Quickly compile code changes without opening a pull request or sharing the code with others.
       Architectural overview
      As an overview, User Build builds a program by performing the following tasks automatically:
      • Uploads the application file to z/OS.
      • Uploads the application's copybooks and include files to z/OS.
      • Invokes the remote build script that you defined in User Build settings.
      • Downloads build log files locally for easier viewing.
      User Build diagram
      Notes:
      • User Build does not require Git to work.
      • User can specify a custom script to execute for User Build, though DBB with zAppBuild solution is recommended.
       Prerequisites
      Before using the user build feature, ensure that the following host and client requirements are met.
      Host requirements:
      Client requirements:
       User build settings
      Before running User Build, you need to configure it via settings to tell User Build where on z/OS to upload files and which build script to execute. The settings should be defined and store as JSON inside VS Code settings filesopen in new window.
      User Build has 2 types of settings: workspace settings and user settings, though both can be placed inside workspace settings file for convenience. See user build docsopen in new window for detailed descriptions of each setting.
      The following example shows workspace and user settings are all stored inside zopeneditor-sample/.vscode/settings.json for convenience. User Build settings example
       Running User Build
      Once settings are filled out, right-click inside a file in the editor, select Run IBM User Build to execute remote script and see results directly in VS Code.
      User Build menus inside VS Code
      The user build log will be streamed in the Output panel inside VS Code. The build is successful when you see the message Build State: CLEAN in the output. The picture below shows successful zAppBuild output for a COBOL application and a log file.
      User Build successful COBOL build
       Trying out User Build
      To get started with User Build, follow this hands-on tutorialopen in new window to use IBM's sample code and the defined workspace settings in the repository.
      For full documentation, refer to Setting up the user buildopen in new window.
      Last Updated: 
      Contributors: KRISTINA MAYO, Min Huang, Hestia Zhang, Peter Haumer, kmaselli
      
+    
   
 
diff --git a/Blog/web-based-with-theia.html b/Blog/web-based-with-theia.html
index e1c6dedf2..4bf4cd083 100644
--- a/Blog/web-based-with-theia.html
+++ b/Blog/web-based-with-theia.html
@@ -41,11 +41,11 @@
                 }
             )();
             Running IBM Z® Open Editor in the browser with Eclipse Theia | IBM Z® Open Editor
-    
+    
     
   
   
-    
      IBM Z® Open Editor
       Running IBM Z® Open Editor in the browser with Eclipse Theia
      by Peter Haumer.
       Last updated: 4 December 2019
      VS Code has become so popular that there are other editors out there now that provide a compatibility API to also consume VS Code extensions. One of the most popular ones is the web-based Eclipse Theiaopen in new window. Theia is also the default editor for the container-based Eclipse Cheopen in new window platform as well. Hence, we develop IBM Z Open Editor not only for VS Code, but also Theia, which opens our editor up for an even larger community than VS Code already provides. In fact, Z Open Editor has actually evolved out of a Theia extension that we introduced in 2018. For more details, see the Overviewopen in new window or a demo showing both user experiencesopen in new window.
       API compatibility
      Theia strives for full compatibility of the VS Code APIs. As Theia and VS Code evolve, the Theia team is keeping track of the status of the VS Code API implementation in Theia hereopen in new window. If new issues are found, the team accepts issue reports hereopen in new window using the tag vscode.
       Building Theia and running IBM Z Open Editor in it
      In this article, we will show you three different ways of building Theia and running it with IBM Z Open Editor and optionally Zowe Explorer that gives you access to z/OS® resources:
      1. Load it from npmjs.org
      2. Load a Docker container
      3. Build Theia from source
      To run IBM Z Open Editor and optionally Zowe Explorer with Theia, you must first download the vsix file(s) of IBM Z Open Editor VS Code extensionopen in new window and optionally Zowe Explorer VS Code extensionopen in new window from the VS Code Marketplace using the "Download Extension" link on the right.
       Alternative 1: Load it from npmjs.org
      If you want to try out the user experience for editing COBOL or PL/I code in a browser, you can build a Theia editor instance with our extension on your development machine easily and then run the Theia web server from the command line window. The main prerequisite is to have Node.js V10open in new window (not newer) and yarnopen in new window installed on your development machine. It can run on Linux, Windows, or macOS.
      1. Follow the instructions hereopen in new window to build a Theia instance using Node and Yarn with the two modifications described below.
      2. After pasting the contents for the package.json file, add the following additional entries into the dependencies object:
         "@theia/plugin-dev": "next",
+    
        IBM Z® Open Editor
         Running IBM Z® Open Editor in the browser with Eclipse Theia
        by Peter Haumer.
         Last updated: 4 December 2019
        VS Code has become so popular that there are other editors out there now that provide a compatibility API to also consume VS Code extensions. One of the most popular ones is the web-based Eclipse Theiaopen in new window. Theia is also the default editor for the container-based Eclipse Cheopen in new window platform as well. Hence, we develop IBM Z Open Editor not only for VS Code, but also Theia, which opens our editor up for an even larger community than VS Code already provides. In fact, Z Open Editor has actually evolved out of a Theia extension that we introduced in 2018. For more details, see the Overviewopen in new window or a demo showing both user experiencesopen in new window.
         API compatibility
        Theia strives for full compatibility of the VS Code APIs. As Theia and VS Code evolve, the Theia team is keeping track of the status of the VS Code API implementation in Theia hereopen in new window. If new issues are found, the team accepts issue reports hereopen in new window using the tag vscode.
         Building Theia and running IBM Z Open Editor in it
        In this article, we will show you three different ways of building Theia and running it with IBM Z Open Editor and optionally Zowe Explorer that gives you access to z/OS® resources:
        1. Load it from npmjs.org
        2. Load a Docker container
        3. Build Theia from source
        To run IBM Z Open Editor and optionally Zowe Explorer with Theia, you must first download the vsix file(s) of IBM Z Open Editor VS Code extensionopen in new window and optionally Zowe Explorer VS Code extensionopen in new window from the VS Code Marketplace using the "Download Extension" link on the right.
         Alternative 1: Load it from npmjs.org
        If you want to try out the user experience for editing COBOL or PL/I code in a browser, you can build a Theia editor instance with our extension on your development machine easily and then run the Theia web server from the command line window. The main prerequisite is to have Node.js V10open in new window (not newer) and yarnopen in new window installed on your development machine. It can run on Linux, Windows, or macOS.
        1. Follow the instructions hereopen in new window to build a Theia instance using Node and Yarn with the two modifications described below.
        2. After pasting the contents for the package.json file, add the following additional entries into the dependencies object:
           "@theia/plugin-dev": "next",
  "@theia/plugin-ext-vscode": "next"
 
          As the name indicates, these commands will add VS Code Extension compatibility.
        3. Then, use the plain yarn command to build everything.
        4. Create a folder called plugins in the directory where you built Theia, and drop the downloaded vsix file(s) into that folder.
        5. Start Theia with this augmented command:
          yarn theia start --plugins=local-dir:./plugins
 
        6. Now open a web browser and navigate to http://localhost:3000open in new window.
        Theia will now load and you can create a workspace directory on your local drive with COBOL or PL/I files with Z Open Editor language support. If you also downloaded the Zowe Explorer VS Code extension, you can see the stylized Z icon on the left that you can click to see the Data Set, USS, and JES viewers.
        Done. It is that easy.
        If you are looking for code samples to try, clone our sample repository with the following command and open that folder by clicking File > Open....
        git clone https://github.com/IBM/zopeneditor-sample.git
@@ -57,6 +57,6 @@
 # mkdir plugins
 # mv *.vsix plugins
 
      3. Restart the container and reload your browser.
      You are now able to create COBOL and PL/I files and see the Zowe Explorer views. To install more extensions into the container, go back to the container root shell. For example, you can install Zowe CLI into the container now as well.
       Alternative 3: Build Theia from source
      If you are interested in the Eclipse Theia project and want to try building it from source to explore it further, you can certainly do that and load Z Open Editor with it.
      The Theia development team provides a very detailed document on how to set up your workspace. In particular, it lists all the dependencies required on your development machine, which differs quite a bit depending on the OS you are working on.
      For more details, see the main Theia Developer Guide: https://github.com/eclipse-theia/theia/blob/master/doc/Developing.mdopen in new window.
      The main prerequisites are still Node V10 and Yarn. However, on a Windows PC, you need more dependencies such as the Windows Build Tools. The developer guideopen in new window proposes to install the Windows package manager Choco and then use it for the installation of most dependencies including Node and Yarn.
      After the prerequisites are set up, the steps for building Theia are basically to clone the repository and run yarn to build everything. If the build process aborts with errors, check for fixes in the Troubleshoot sections of the Theia development guideopen in new window.
      Once everything is built, running Theia with Z Open Editor and Zowe Explorer requires these additional steps:
      1. Create a folder called plugins in the top-level Theia folder you cloned.
      2. Copy the Z Open Editor and Zowe Explorer vsix files into that plugins folder.
      3. Run the command cd examples/browser.
      4. Run the command yarn start.
      5. Open a web browser and navigate to http://localhost:3000open in new window.
      Last Updated: 
      Contributors: Peter Haumer, Min Huang, Peter Haumer, Shi Kun Li
      
-    
+    
   
 
diff --git a/Blog/whats-new-120.html b/Blog/whats-new-120.html
index 3d9d8224f..eac9010d3 100644
--- a/Blog/whats-new-120.html
+++ b/Blog/whats-new-120.html
@@ -41,11 +41,11 @@
                 }
             )();
             Scaling up the audience with IBM Z Open Editor and Wazi Developer 1.2.0 | IBM Z® Open Editor
-    
+    
     
   
   
-    
      IBM Z® Open Editor
       Scaling up the audience with IBM Z Open Editor and Wazi Developer 1.2.0
      by Peter Haumer
       18 March 2021
      IBM Z® Open Editor 1.2, together with its companion application Zowe™ Explorer 1.13, and its packaging in IBM® Wazi Developer 1.2 are available now. This is already our eighth major release since we started publishing the editor in the VS Code Marketplaceopen in new window in September 2019. Since then, Z Open Editor has been installed almost 28.000 times by Enterprise Application developers and students from 85 different countries. We continue to add new features and refine the user experience based on the feedback we are getting. Therefore, several of the major capabilities added in this new release are some of the most frequently asked about enhancements, as well as address areas where we saw new users struggling. We hope that these capabilities will be attractive to users who have not considered our editor, yet. Here is a quick overview of the highlights.
       Added REXX as a new language
      We set out devising Z Open Editor with the vision of creating a great editing experience for z/OS® Enterprise languages that is really attractive to the next generation of developers. As we see big adoption numbers though educational offerings such as IBM's Master the Mainframe and the Open Mainframe Project's COBOL training classes, we also hear from experienced enterprise developers who use the editor and Zowe Explorer in their day-to-day activities. One request we heard from the experienced audience over and over is: can you support REXXopen in new window?
      With Z Open Editor 1.2, we are proud to announce that we are now shipping an all-new language server for REXX that gives you all the capabilities you expect: syntax errors and highlighting, code completion, outline view, navigate variable references etc. Plus, for all the enhancements that we added in the previous and current release around executing TSO and Unix commands for the IBM RSE API Plug-in for Zowe CLI, you can use them for your REXX development directly because they seamlessly integrate into the editor environment as a CLI.
      Our REXX support was realized by following the open language serveropen in new window protocol, just like our language support for COBOL, PL/I and High-Level Assembler. Therefore, we are also able to ship it with our flagship offering IBM Developer for z/OS 15.0.1open in new window at the same time giving developers the choice of using either a VS Code or Eclipse-based editing experience for REXX.
      To learn all about our REXX support, read our dedicated Blog postopen in new window and Tutorial.
       Full support of international EBCDIC code pages for all operations
      Another frequent request from developers is better support for code page conversions. Because Z Open Editor and Zowe Explorer pull program files from z/OS to edit them locally, the program files will be converted to UTF-8 and converted back to EBCDIC when written back. Particularly for MVS™, international users were asking for more options configuring the EBCDIC code pages to convert from and to.
      In previous releases of Zowe CLI, Zowe Explorer, and RSE API CLI plug-in, we added a parameter to specify the encoding to be used with your CLI profileopen in new window as well as specific uploadopen in new window and downloadopen in new window commands. These parameters are available to z/OSMF as well as RSE API users. However, they only covered a subset of use cases that people were telling us about. What if you uploaded whole directories with a mix of program and binary files or what if you had data sets using different code pages?
      Converted special characters
      Fig. 1: Z Open Editor converting special characters for EBCDIC code pages for remote MVS copybooks
      With Z Open Editor 1.2, we added special support for conversions with RSE API that allows you to configure conversion mappings based on various criteria such as based on local file name extensions or the names of the data set, using wildcards, you are interacting with. You can define such mapping rules on the organizational level as server defaults, on a project-level by managing the mappings files with your source code, for example in an SCM, as well as individual level by having a mapping file in your home directory. This will allow you to define different code pages for data sets used only by you versus data sets used by a team or project down to the member name level including mapping files as binary versus text.
      Conversion mappings can be used for all z/OS MVS interactions in Z Open Editor, Zowe Explorer, and RSE API CLI plug-in. For example, when you open a file in Zowe Explorer via an RSE API profile, when you resolve copybooks in COBOL programs using a remote property group, or executing a script using RSE API CLI plug-in commands. We also provide a similar mapping concept for USS when running Dependency-Based Builds using our User Build operations.
      To learn more about conversion mappings, see this new RSE API CLI blog post for this release as well as our detailed documentation page.
       A new onboarding experience for new developers
      For this release, we also had another look at typical stumbling blocks for new users. Particularly, the areas of ensuring the correct prerequisites are installed and configured on the developer's machine as well as Zowe CLI profiles are created and configured. We also see that users might either not be aware or have problems with correctly configuring property groups for resolving include files and copybooks.
      We decided to add a wizard in this release that welcomes new users, checks the installation and prerequisites, and makes recommendations for fixing. Plus, it provides pointers for getting started with various capabilities as well as how to provide feedback or ask questions. The Welcome page will open automatically the first time you install or upgrade to 1.2 and you can choose to disable or continue to see it at startup.
      Z Open Editor Welcome page
      Fig. 2: The new Welcome page for Z Open Editor 1.2
       Better support for teams working on different platforms
      Another area we saw users run into trouble with using include file resolution was specifying path and file names for include files, especially when different team members were working on different platforms. For example, a Windows user creating a COBOL copybook using a lowercase file name on the file system and in Git but referring to it in their programs with an uppercase spelling. This worked fine on case-insensitive Windows, but a user running Z Open Editor in Red Hat® CodeReady Workspaces would see errors as the underlying Linux® file system is case sensitive.
      We changed the behavior of Z Open Editor to be case-insensitive by default now, but also added the option for developers or teams to make Z Open Editor enforce the right casing as well. This is recommended to avoid potential issues such as files being created with the same name, but different cases in the same folder on Linux, which could lead to ambiguous behavior for COBOL copy statements.
       Added more flexible ways to deploy in your organization
      In addition to new product features, we are also addressing feedback about deploying our solutions in client organizations.
      We added more ways of getting our solution components by publishing our RSE API Zowe CLI plug-in in the public npmjs.comopen in new window registry that allows you now to install the plug-in with a simple zowe plugins install @ibm/rse-api-for-zowe-cli command without the need to first download and extract the plug-in from the IBM site. Although, this option of downloading from the IBM site is still available as well.
      We are also started publishing Z Open Editor at open-vsx.orgopen in new window, which is an alternative to the Microsoft Marketplace that is based on open source software. open-vsx.org is now the default for other open source editors in which Z Open Editor can run such as Eclipse Theiaopen in new window or VSCodiumopen in new window. Furthermore, organizations can install and host their own Open VSX serversopen in new window in-house allowing them to have full control over which extensions developers can install and which not.
      We also improved the way that users can migrate to new releases of our IBM Wazi Developer for Workspaces offering more easily by allowing them to subscribe to simple OpenShift® update feeds that that will deploy the new versions of Wazi Developer and CodeReady Workspacesopen in new window and migrate their workspaces.
       New ways to try our solutions
      Finally, we have new and improved ways of trying our solutions for evaluations.
      We provide a new version of the “Bring Your Own (BYO) IDE for Cloud Native Development" Z Trialopen in new window that walks you through a complete lifecycle and development pipeline with either VS Code or Eclipse-based tools.
      You can also easily try Red Hat OpenShift and CodeReady Workspaces with Z Open Editor and Zowe Explorer. To do that, sign-up for a trial account here at https://developers.redhat.com/developer-sandboxopen in new window. This will give you access to OpenShift as well CodeReady Workspaces (check the docs and video on that site for details). Once you have CodeReady Workspaces up, you can just follow the instructions here in our public GitHub for deploying Z Open Editor and Zowe Explorer: https://github.com/IBM/zopeneditor-about/tree/master/cheopen in new window. To use a mainframe, you could create an account with Master the Mainframe and connect that via a Zowe profile.
      Finally, we want to mention for developers who use Zowe SDKsopen in new window to create their own developments tools that you can now also try the Zowe SDK with RSE API Plug-in for Zowe CLI as well. We have created a very simple example here that uses the TSO SDK showing how you can write Node.js scripts that use z/OSMF as well as RSE API interchangeably to execute TSE commands programmatically: https://github.com/phaumer/zowe-cli-tso-rse-sampleopen in new window. Let us know if you would like to see more example such as these.
      We hope you enjoy all these new capabilities in IBM Z Open Editor and IBM Wazi Developer. Visit our site for more detailed information and to provide us with feedback on GitHubopen in new window or our Wazi Developer Community pageopen in new window.
      Last Updated: 
      Contributors: Peter Haumer, Min Huang, PETER HAUMER, Peter Haumer, kmaselli
      
-    
+    
      IBM Z® Open Editor
       Scaling up the audience with IBM Z Open Editor and Wazi Developer 1.2.0
      by Peter Haumer
       18 March 2021
      IBM Z® Open Editor 1.2, together with its companion application Zowe™ Explorer 1.13, and its packaging in IBM® Wazi Developer 1.2 are available now. This is already our eighth major release since we started publishing the editor in the VS Code Marketplaceopen in new window in September 2019. Since then, Z Open Editor has been installed almost 28.000 times by Enterprise Application developers and students from 85 different countries. We continue to add new features and refine the user experience based on the feedback we are getting. Therefore, several of the major capabilities added in this new release are some of the most frequently asked about enhancements, as well as address areas where we saw new users struggling. We hope that these capabilities will be attractive to users who have not considered our editor, yet. Here is a quick overview of the highlights.
       Added REXX as a new language
      We set out devising Z Open Editor with the vision of creating a great editing experience for z/OS® Enterprise languages that is really attractive to the next generation of developers. As we see big adoption numbers though educational offerings such as IBM's Master the Mainframe and the Open Mainframe Project's COBOL training classes, we also hear from experienced enterprise developers who use the editor and Zowe Explorer in their day-to-day activities. One request we heard from the experienced audience over and over is: can you support REXXopen in new window?
      With Z Open Editor 1.2, we are proud to announce that we are now shipping an all-new language server for REXX that gives you all the capabilities you expect: syntax errors and highlighting, code completion, outline view, navigate variable references etc. Plus, for all the enhancements that we added in the previous and current release around executing TSO and Unix commands for the IBM RSE API Plug-in for Zowe CLI, you can use them for your REXX development directly because they seamlessly integrate into the editor environment as a CLI.
      Our REXX support was realized by following the open language serveropen in new window protocol, just like our language support for COBOL, PL/I and High-Level Assembler. Therefore, we are also able to ship it with our flagship offering IBM Developer for z/OS 15.0.1open in new window at the same time giving developers the choice of using either a VS Code or Eclipse-based editing experience for REXX.
      To learn all about our REXX support, read our dedicated Blog postopen in new window and Tutorial.
       Full support of international EBCDIC code pages for all operations
      Another frequent request from developers is better support for code page conversions. Because Z Open Editor and Zowe Explorer pull program files from z/OS to edit them locally, the program files will be converted to UTF-8 and converted back to EBCDIC when written back. Particularly for MVS™, international users were asking for more options configuring the EBCDIC code pages to convert from and to.
      In previous releases of Zowe CLI, Zowe Explorer, and RSE API CLI plug-in, we added a parameter to specify the encoding to be used with your CLI profileopen in new window as well as specific uploadopen in new window and downloadopen in new window commands. These parameters are available to z/OSMF as well as RSE API users. However, they only covered a subset of use cases that people were telling us about. What if you uploaded whole directories with a mix of program and binary files or what if you had data sets using different code pages?
      Converted special characters
      Fig. 1: Z Open Editor converting special characters for EBCDIC code pages for remote MVS copybooks
      With Z Open Editor 1.2, we added special support for conversions with RSE API that allows you to configure conversion mappings based on various criteria such as based on local file name extensions or the names of the data set, using wildcards, you are interacting with. You can define such mapping rules on the organizational level as server defaults, on a project-level by managing the mappings files with your source code, for example in an SCM, as well as individual level by having a mapping file in your home directory. This will allow you to define different code pages for data sets used only by you versus data sets used by a team or project down to the member name level including mapping files as binary versus text.
      Conversion mappings can be used for all z/OS MVS interactions in Z Open Editor, Zowe Explorer, and RSE API CLI plug-in. For example, when you open a file in Zowe Explorer via an RSE API profile, when you resolve copybooks in COBOL programs using a remote property group, or executing a script using RSE API CLI plug-in commands. We also provide a similar mapping concept for USS when running Dependency-Based Builds using our User Build operations.
      To learn more about conversion mappings, see this new RSE API CLI blog post for this release as well as our detailed documentation page.
       A new onboarding experience for new developers
      For this release, we also had another look at typical stumbling blocks for new users. Particularly, the areas of ensuring the correct prerequisites are installed and configured on the developer's machine as well as Zowe CLI profiles are created and configured. We also see that users might either not be aware or have problems with correctly configuring property groups for resolving include files and copybooks.
      We decided to add a wizard in this release that welcomes new users, checks the installation and prerequisites, and makes recommendations for fixing. Plus, it provides pointers for getting started with various capabilities as well as how to provide feedback or ask questions. The Welcome page will open automatically the first time you install or upgrade to 1.2 and you can choose to disable or continue to see it at startup.
      Z Open Editor Welcome page
      Fig. 2: The new Welcome page for Z Open Editor 1.2
       Better support for teams working on different platforms
      Another area we saw users run into trouble with using include file resolution was specifying path and file names for include files, especially when different team members were working on different platforms. For example, a Windows user creating a COBOL copybook using a lowercase file name on the file system and in Git but referring to it in their programs with an uppercase spelling. This worked fine on case-insensitive Windows, but a user running Z Open Editor in Red Hat® CodeReady Workspaces would see errors as the underlying Linux® file system is case sensitive.
      We changed the behavior of Z Open Editor to be case-insensitive by default now, but also added the option for developers or teams to make Z Open Editor enforce the right casing as well. This is recommended to avoid potential issues such as files being created with the same name, but different cases in the same folder on Linux, which could lead to ambiguous behavior for COBOL copy statements.
       Added more flexible ways to deploy in your organization
      In addition to new product features, we are also addressing feedback about deploying our solutions in client organizations.
      We added more ways of getting our solution components by publishing our RSE API Zowe CLI plug-in in the public npmjs.comopen in new window registry that allows you now to install the plug-in with a simple zowe plugins install @ibm/rse-api-for-zowe-cli command without the need to first download and extract the plug-in from the IBM site. Although, this option of downloading from the IBM site is still available as well.
      We are also started publishing Z Open Editor at open-vsx.orgopen in new window, which is an alternative to the Microsoft Marketplace that is based on open source software. open-vsx.org is now the default for other open source editors in which Z Open Editor can run such as Eclipse Theiaopen in new window or VSCodiumopen in new window. Furthermore, organizations can install and host their own Open VSX serversopen in new window in-house allowing them to have full control over which extensions developers can install and which not.
      We also improved the way that users can migrate to new releases of our IBM Wazi Developer for Workspaces offering more easily by allowing them to subscribe to simple OpenShift® update feeds that that will deploy the new versions of Wazi Developer and CodeReady Workspacesopen in new window and migrate their workspaces.
       New ways to try our solutions
      Finally, we have new and improved ways of trying our solutions for evaluations.
      We provide a new version of the “Bring Your Own (BYO) IDE for Cloud Native Development" Z Trialopen in new window that walks you through a complete lifecycle and development pipeline with either VS Code or Eclipse-based tools.
      You can also easily try Red Hat OpenShift and CodeReady Workspaces with Z Open Editor and Zowe Explorer. To do that, sign-up for a trial account here at https://developers.redhat.com/developer-sandboxopen in new window. This will give you access to OpenShift as well CodeReady Workspaces (check the docs and video on that site for details). Once you have CodeReady Workspaces up, you can just follow the instructions here in our public GitHub for deploying Z Open Editor and Zowe Explorer: https://github.com/IBM/zopeneditor-about/tree/master/cheopen in new window. To use a mainframe, you could create an account with Master the Mainframe and connect that via a Zowe profile.
      Finally, we want to mention for developers who use Zowe SDKsopen in new window to create their own developments tools that you can now also try the Zowe SDK with RSE API Plug-in for Zowe CLI as well. We have created a very simple example here that uses the TSO SDK showing how you can write Node.js scripts that use z/OSMF as well as RSE API interchangeably to execute TSE commands programmatically: https://github.com/phaumer/zowe-cli-tso-rse-sampleopen in new window. Let us know if you would like to see more example such as these.
      We hope you enjoy all these new capabilities in IBM Z Open Editor and IBM Wazi Developer. Visit our site for more detailed information and to provide us with feedback on GitHubopen in new window or our Wazi Developer Community pageopen in new window.
      Last Updated: 
      Contributors: Peter Haumer, Min Huang, PETER HAUMER, Peter Haumer, kmaselli
      
+    
   
 
diff --git a/Docs/advanced_activation.html b/Docs/advanced_activation.html
index feb19bb0f..2fcbf4560 100644
--- a/Docs/advanced_activation.html
+++ b/Docs/advanced_activation.html
@@ -41,11 +41,11 @@
                 }
             )();
             Activating advanced capabilities | IBM Z® Open Editor
-    
+    
     
   
   
     
      IBM Z® Open Editor
       Activating advanced capabilities
      Z Open Editor's advanced capabilities require activation when the 60-day trial period ends. Currently, you can activate a permanent license key in two ways:
      1. Automatic activation using an RSE API server.
      2. Manual activation by importing an activation kit.
      The IBM Z Open Editor Welcome page is used to report on the status of the trial license, the status of the automatic activation, as well as provides the means to import a manual activation kit. If the Welcome page does not open automatically at startup or you have already closed it, you can open it by entering cmd/ctrl-shift-p and typing or selecting IBM Z Open Editor: Welcome.
       Automatic activation
      Automatic activation uses the same technology that development clients for IBM Developer for z/OS Enterprise Edition use. It is ideal for organizations who run IBM Remote Systems Explorer (RSE) and allow their developers to choose between an Eclipse and VS Code development client. A system programmer provisioning RSE will install activation tokens that the editors retrieve automatically when they connect to RSE.
      To enable activation tokens via RSE API on z/OS, the z/OS administrator needs to complete the following steps:
      1. Install and complete basic configuration of z/OS host component IBM z/OS Explorer Extensions, FMID HHOPxxx. For more information, see Installing and configuring the host componentsopen in new window.
      2. Install and complete basic configuration of z/OS host component IBM Remote System Explorer API (RSE API), FMID HAMAxxx.
      3. Make sure z/OS Explorer knows where to find z/OS Explorer Extensions. Depending on where z/OS Explorer Extensions was installed, this detection is automatic, or done via an environment variable in the configuration file rse.envopen in new window.
      4. Allow z/OS Explorer Extensions to register as ADFz or IDzEE. For more information, see Product enablement in IFAPRDxxopen in new window.
      5. Allow z/OS Explorer Extensions to write SM122 recordsopen in new window to track that it provided an activation token.
      You can find more detailed instruction in the documentation for system programmers, such as in IBM Shopzopen in new window.
      The Z Open Editor end users can then use the VS Code user setting zopeneditor.advancedCapabilities.enableRseApiActivationCheck to enable the automatic RSE check. The Z Open Editor Welcome page also provides a convenient check box to enable these settings.
      Once enabled, the next time you connect to the RSE API server via Zowe Explorer or Z Open Editor, an automatic check for activation will be executed. If successful, the Z Open Editor Welcome page will report the activation status in a table.
      Notes:
      • Host component IBM Explorer for z/OS, FMID HALGxxx, is a prerequisite for both IBM z/OS Explorer Extensions and IBM Remote System Explorer API (RSE API).
      • You can use the Host Configuration Assistant at https://zdev-hca.ibm.comopen in new window to guide you through the required host configuration.
      • The provided activation tokens operate for a limited time. However, activation tokens are automatically renewed each time the client connects to the z/OS host.
       Manual activation
      If your organization uses z/OSMF instead of RSE API, you can activate your Z Open Editor client with an activation kit. You receive the activation kit through Shopz and your administrative system programmer or directly from your IBM sales representative. The kit comprises a single file that needs to be imported by every Z Open Editor user to activate the advanced capabilities.
      1. Open the Z Open Editor Welcome page and scroll to the Advanced capabilities section.
      2. Click the Update activation key link below the table that presents the status of your trial.
      3. Click Browse in the dialog, and select the activation kit file that you received.
      4. Click Import in the dialog to finish activation.
      5. The table will now show information about the activation kit that you imported.
      Last Updated: 
      Contributors: Hestia Zhang, PETER HAUMER, Benjamin Santos, Peter Haumer
      
-    
+    
   
 
diff --git a/Docs/advanced_custom_macros.html b/Docs/advanced_custom_macros.html
index cf4ec3090..330eaf963 100644
--- a/Docs/advanced_custom_macros.html
+++ b/Docs/advanced_custom_macros.html
@@ -41,7 +41,7 @@
                 }
             )();
             Custom Macros for HLASM | IBM Z® Open Editor
-    
+    
     
   
   
@@ -53,6 +53,6 @@
       locations:
         - "**/ASMMAC"
 
      You can declare any number of locations, but they need to be under the maclib library to be scanned for macros.
       Accessing Custom Macros from HLASM Programs
      When the custom macros resolve correctly in your HLASM programs, you can see underlines (document links) appear under all the located custom macros in your program. You can hover over the macro to see the declaration and contents. If you want to directly access the macro, you can use Ctrl+Click (Windows) or Cmd+Click (Mac) to open it. Alternatively, you can right click and select Go to Definition and the editor will take you directly to the line where that macro is declared.
      The following gif shows this functionality:
      example of custom macro functionality
       Settings for Custom Macros
      The following settings are added to support the new custom macros feature:
      1. zopeneditor.hlasm.enableCustomMacrosWarnings: This setting is enabled by default and will place warnings under all custom macros that cannot be found in your HLASM programs. Disable this setting if you do not want to see these warnings.
      2. zopeneditor.hlasm.reduceCustomMacroLogging: This setting is disabled by default and will accelerate custom macro scanning performance at the cost of a reduced number of logs provided for the user. When the setting is disabled, you can debug and see which documents are being requested by the language server. Those document requests are not sent when the setting is enabled, allowing the language server to handle everything internally so that no communication is logged.
      Last Updated: 
      Contributors: Saile Daimwood
      
-    
+    
   
 
diff --git a/Docs/advanced_overview.html b/Docs/advanced_overview.html
index 16fa6b122..f54755776 100644
--- a/Docs/advanced_overview.html
+++ b/Docs/advanced_overview.html
@@ -41,11 +41,11 @@
                 }
             )();
             Overview | IBM Z® Open Editor
-    
+    
     
   
   
     
      IBM Z® Open Editor
       Overview
      IBM Z Open Editor v4 or later features enterprise-level advanced capabilities that cover use cases that go beyond programming and simple accessing of z/OS Resources. You would typically find such features in IBM's commercial zDevOps solutions such as IBM Developer for z/OS Enterprise Edition (IDzEE). While the core Z Open Editor experience continues to provide free full language support for COBOL, PL/I, REXX, HLASM, JCL and integrations with Zowe Explorer, these advanced capabilities require commercial licenses to activate. You can purchase the licenses through IBM Developer for z/OS Enterprise Editionopen in new window or IBM Application Delivery Foundation for z/OSopen in new window.
      To allow every user to try these features, Z Open Editor will activate a 60-day trial license when you start version 4 for the first time.
      For more information, see IBM Documentationopen in new window.
      Only the following new features documented in this section require such a license:
      1. z/OS Resources table: an all-new feature rich view that extends Zowe Explorer with a sortable table. Gain insights into your jobs, data sets, and UNIX files by listing, filtering, and sorting on many available properties.
      2. Preprocessor support for COBOL: run a preprocessor either on your local workstation or remotely on z/OS driven with 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.
      3. Advanced Dependency-Based user build error reporting: User build logs are now automatically downloaded, parsed, and presented in the editor's Problems view with descriptions and error codes. Navigate to warnings and errors in your code with a mouse click in the Problems view to review and fix your issue and then rerun your build.
      4. HLASM macros support: Use custom macro resolution in HLASM programs with references to macros in local files. The HLASM editor shows hovers, document links, go to definition, and code completion for macros. This feature works with one to many macro declarations per include file, which is achieved by pre-scanning macro files if they can be found in local ZAPP property groups.
      To access these capabilities beyond the trial period, you need to activate them in the Z Open Editor Welcome page. See Activating Advanced Capabilities for details.
      Last Updated: 
      Contributors: PETER HAUMER, Benjamin Santos, Ethan Mendel, Prasang Prajapati, Saile Daimwood
      
-    
+    
   
 
diff --git a/Docs/advanced_preprocessor.html b/Docs/advanced_preprocessor.html
index c5d903a48..d56c14298 100644
--- a/Docs/advanced_preprocessor.html
+++ b/Docs/advanced_preprocessor.html
@@ -41,12 +41,13 @@
                 }
             )();
             Preprocessor support | IBM Z® Open Editor
-    
+    
     
   
   
-    
      IBM Z® Open Editor
       Preprocessor support
      Z Open Editor provides the advanced capability to integrate parsing of COBOL programs with a custom preprocessor to allow editing programs that contain such preprocessor statements without causing the editor to show syntax errors. The preprocessor would be executed on either a developer machine by Z Open Editor in the background (local) or a z/OS system (remote), taking COBOL with custom code and transforming it to valid COBOL. Users can then continue editing such programs by using the preprocessor input to still provide full language support such as code completion, syntax error highlighting, and outline view for the regular COBOL statements. Then at each save or editor focus change the preprocessor can run automatically again to update the processed COBOL representation used by the editor. The editor would not learn the preprocessor language, but rather ensure that the resulting preprocessed output is still valid COBOL.
       Local preprocessor
       Example workflow
      The following workflow is written from the perspective of COBOL developer, Deb.
      1. Deb installs a command-line centric preprocessor program on her local development machine.
      2. Deb creates a zapp.yaml file with a preprocessor profile type. The profile specifies the command-line for running the preprocessor on the currently edited program file as well as the output path for the preprocessed program files.
      3. Deb edits a program file with preprocessor statements in Z Open Editor.
      4. Deb either manually starts preprocessing the program via a right-click menu command or creates a user setting to automatically run the preprocessor on Save.
      5. Z Open Editor starts the preprocessor command in the background and sends the output file to its COBOL parser.
      6. Z Open Editor's COBOL parser will compare the program in the editor with the output of the preprocessor command.
      7. Deb hovers over processor statements in Z Open Editor, which displays the resulting COBOL.
      8. Deb continues editing the program in Z Open Editor. Z Open Editor continues to provide full language support for all the parts of the program that are not preprocessor statements.
      To learn and explore this workflow, check out the example preprocessor and code samples in our Github repository at https://github.com/ibm/zopeneditor-sample/tree/wazi-main/preprocessoropen in new window. Review the Readmeopen in new window file in this folder with detailed instructions for building and running the sample.
       Requirements for the preprocessor
      To be able to integrate your preprocessor with Z Open Editor, it must fulfill these requirements:
      • It needs to run locally on your development machine where Z Open Editor is running.
      • You need to be able to run the processor via command-line.
      • The command-line operation needs to create an output file that contains valid COBOL.
      • The output path can be computed by specifying a new file extension to be used with the program file name.
       ZAPP profile
      The integration of the preprocessor with the editor is handled via a ZAPP file profile. Such a profile might look like this:
      - name: extended-cobol
+    
      IBM Z® Open Editor
       Preprocessor support
      Z Open Editor provides the advanced capability to integrate parsing of COBOL and PL/I programs with a custom preprocessor to allow editing programs that contain such preprocessor statements without causing the editor to show syntax errors. The preprocessor would be executed on either a developer machine by Z Open Editor in the background (local) or a z/OS system (remote), taking COBOL or PL/I with custom code and transforming it to a valid program. Users can then continue editing such programs by using the preprocessor input to still provide full language support such as code completion, syntax error highlighting, and outline view for the regular COBOL or PL/I statements. Then at each save or editor focus change the preprocessor can run automatically again to update the processed representation used by the editor. The editor would not learn the preprocessor language, but rather ensure that the resulting preprocessed output is still valid COBOL or PL/I.
       Local preprocessor
       Example workflow
      The following workflow is written from the perspective of developer, Deb.
      1. Deb installs a command-line centric preprocessor program on her local development machine.
      2. Deb creates a zapp.yaml file with a preprocessor profile type. The profile specifies the command-line for running the preprocessor on the currently edited program file as well as the output path for the preprocessed program files.
      3. Deb edits a program file with preprocessor statements in Z Open Editor.
      4. Deb either manually starts preprocessing the program via a right-click menu command or creates a user setting to automatically run the preprocessor on Save.
      5. Z Open Editor starts the preprocessor command in the background and sends the output file to its COBOL (PL/I) parser.
      6. Z Open Editor's COBOL (PL/I) parser will compare the program in the editor with the output of the preprocessor command.
      7. Deb hovers over processor statements in Z Open Editor, which displays the resulting COBOL (PL/I).
      8. Deb continues editing the program in Z Open Editor. Z Open Editor continues to provide full language support for all the parts of the program that are not preprocessor statements.
      To learn and explore this workflow, check out the example preprocessor and code samples in our Github repository at https://github.com/ibm/zopeneditor-sample/tree/wazi-main/preprocessoropen in new window. Review the Readmeopen in new window file in this folder with detailed instructions for building and running the sample.
       Requirements for the preprocessor
      To be able to integrate your preprocessor with Z Open Editor, it must fulfill these requirements:
      • It needs to run locally on your development machine where Z Open Editor is running.
      • You need to be able to run the processor via command-line.
      • The command-line operation needs to create an output file that contains valid COBOL.
      • The output path can be computed by specifying a new file extension to be used with the program file name.
       ZAPP profile
      The integration of the preprocessor with the editor is handled via a ZAPP file profile. Such a profile might look like this:
      - name: extended-cobol
   type: preprocessor
+  language: cobol
   location: local
   settings:
     command: ${JAVA_HOME}/bin/java -jar ${WORKSPACE}/preprocessor/my-preprocessor/target/my-preprocessor-1.0-SNAPSHOT.jar ${input_file} ${output_file}
@@ -54,16 +55,17 @@
     fileExtension: cee
     environmentVariables:
       VARIABLE1: value1
-
      In the settings object, the following properties can be used:
      PropertyDescription
      commandThe command line to be executed. You can mix the command line with ZAPP Variables as well as use the predefined variables ${input_file} and ${output_file}. You need to define ${JAVA_HOME} and ${WORKSPACE} in the example above as ZAPP variables. Environment variables can only be used by specifying them with the environmentVariables property.
      outputPathThe base path in which the output file should be created. This path must be inside the current VS Code workspace so that the editor can see and process the files.
      fileExtensionThe file extension to be used for the output files.
      environmentVariablesAn optional sub-object to specify the environment variables that should be created before executing the command.
       Running the preprocessor
      After you specify the ZAPP profile, you can run the preprocessor in the following ways:
      1. Right-click and choose Execute local preprocessor command to manually run the preprocessor in the program file editor.
      2. Automatically run the preprocessor via the VS Code user setting zopeneditor.cobol.autoPreprocessor. The setting can have one of the values: 
        • off: disables the automatic preprocessor execution.
        • open: when a program file is opened in the editor.
        • save: when a program file is saved in the editor.
        • both: when opening and saving a program file in the editor.
      When the preprocessor command runs, a progress dialog with a Cancel button is displayed. When the preprocessor finishes, it refreshes the editor and any syntax errors that were caused by preprocessor statements should go away or, if they contained problems, will show those instead.
      If the processor command execution failed and produced errors, a dialog will be shown with a button to open the Z Open Editor log file viewer which lists the detailed error message produced by the preprocessor command.
       Using the preprocessor output in the editor
      After the preprocessor is executed, you can hover the mouse of preprocessor statements in their program file to see the COBOL code that was generated for the statement. You can edit these statements and all other COBOL code in the program.
      Syntax errors for preprocessor statements will not be available until the preprocessor runs again. Syntax errors for other regular COBOL will be shown while typing as usual in Z Open Editor.
      To get a side-by-side view of the program before and after preprocessing, you can use the right-click menu option Compare preprocessor input and output files.
       Remote preprocessor
       Example workflow
      The following workflow is written from the perspective of COBOL developer, Deb.
      1. Deb sets up a z/OS centric preprocessor data member on her remote z/OS development machine. This data member must be either a REXX or CLIST program.
      2. Deb creates a zapp.yaml file with a preprocessor profile type. The profile specifies the TSO command for running the preprocessor on the currently edited program data member as well as the output dataset for the preprocessed data members.
      3. Deb edits a dataset member with preprocessor statements in Z Open Editor through Zowe.
      4. Deb either manually starts preprocessing the program via a right-click menu command or creates a user setting to automatically run the preprocessor on Save.
      5. Z Open Editor uses Zowe to start the preprocessor command in the background and sends the output file to its COBOL parser.
      6. Z Open Editor's COBOL parser will compare the program in the editor with the output of the preprocessor command.
      7. Deb hovers over processor statements in Z Open Editor, which displays the resulting COBOL.
      8. Deb continues editing the program in Z Open Editor. Z Open Editor continues to provide full language support for all the parts of the program that are not preprocessor statements.
      To learn and explore this sample workflow, check out the example preprocessor and code samples in our Github repository at https://github.com/ibm/zopeneditor-sample/tree/wazi-main/preprocessoropen in new window. Review the Readmeopen in new window file in this folder with detailed instructions for building and running the sample.
       Requirements for the preprocessor
      To be able to integrate your preprocessor with Z Open Editor, it must fulfill these requirements:
      • It needs to run remotely on your z/OS machine.
      • The remote preprocessor must be either a REXX or CLIST program.
      • You need a RSE API or z/OSMF Zowe profile available in your workspace and configured as a default for Z Open Editor.
      • You need to be able to run the processor via a Zowe TSO command. 
      • The TSO operation needs to create an output data member that contains valid COBOL.
      • The program file to be processed needs to be in a PDS that is recognized by Z Open Editor to contain COBOL and the COBOL language support must be active. See Remote file associations for more details.
       ZAPP profile
      The integration of the preprocessor with the editor is handled via a ZAPP file profile. Such a profile could look like this:
      - name: extended-cobol
+
      The language property is mandatory and allows the values cobol or pl1 only.
      In the settings object, the following properties can be used:
      PropertyDescription
      commandThe command line to be executed. You can mix the command line with ZAPP Variables as well as use the predefined variables ${input_file} and ${output_file}. You need to define ${JAVA_HOME} and ${WORKSPACE} in the example above as ZAPP variables. Environment variables can only be used by specifying them with the environmentVariables property.
      outputPathThe base path in which the output file should be created. This path must be inside the current VS Code workspace so that the editor can see and process the files.
      fileExtensionThe file extension to be used for the output files.
      environmentVariablesAn optional sub-object to specify the environment variables that should be created before executing the command.
       Running the preprocessor
      After you specify the ZAPP profile, you can run the preprocessor in the following ways:
      1. Right-click and choose Execute local preprocessor command to manually run the preprocessor in the program file editor.
      2. Automatically run the preprocessor via the VS Code user setting zopeneditor.autoPreprocessor. The setting can have one of the values: 
        • off: disables the automatic preprocessor execution.
        • open: when a program file is opened in the editor.
        • save: when a program file is saved in the editor.
        • both: when opening and saving a program file in the editor.
      When the preprocessor command runs, a progress dialog with a Cancel button is displayed. When the preprocessor finishes, it refreshes the editor and any syntax errors that were caused by preprocessor statements should go away or, if they contained problems, will show those instead.
      If the processor command execution failed and produced errors, a dialog will be shown with a button to open the Z Open Editor log file viewer which lists the detailed error message produced by the preprocessor command.
       Using the preprocessor output in the editor
      After the preprocessor is executed, you can hover the mouse of preprocessor statements in their program file to see the code that was generated for the statement. You can edit these statements and all other code in the program.
      Syntax errors for preprocessor statements will not be available until the preprocessor runs again. Syntax errors for other regular COBOL or PL/I code will be shown while typing as usual in Z Open Editor.
      To get a side-by-side view of the program before and after preprocessing, you can use the right-click menu option Compare preprocessor input and output files.
       Remote preprocessor
       Example workflow
      The following workflow is written from the perspective of developer, Deb.
      1. Deb sets up a z/OS centric preprocessor data member on her remote z/OS development machine. This data member must be either a REXX or CLIST program.
      2. Deb creates a zapp.yaml file with a preprocessor profile type. The profile specifies the TSO command for running the preprocessor on the currently edited program data member as well as the output dataset for the preprocessed data members.
      3. Deb edits a dataset member with preprocessor statements in Z Open Editor through Zowe.
      4. Deb either manually starts preprocessing the program via a right-click menu command or creates a user setting to automatically run the preprocessor on Save.
      5. Z Open Editor uses Zowe to start the preprocessor command in the background and sends the output file to its parser.
      6. Z Open Editor's COBOL or PL/I parser will compare the program in the editor with the output of the preprocessor command.
      7. Deb hovers over processor statements in Z Open Editor, which displays the resulting COBOL or PL/I.
      8. Deb continues editing the program in Z Open Editor. Z Open Editor continues to provide full language support for all the parts of the program that are not preprocessor statements.
      To learn and explore this sample workflow, check out the example preprocessor and code samples in our Github repository at https://github.com/ibm/zopeneditor-sample/tree/wazi-main/preprocessoropen in new window. Review the Readmeopen in new window file in this folder with detailed instructions for building and running the sample.
       Requirements for the preprocessor
      To be able to integrate your preprocessor with Z Open Editor, it must fulfill these requirements:
      • It needs to run remotely on your z/OS machine.
      • The remote preprocessor must be either a REXX or CLIST program.
      • You need a RSE API or z/OSMF Zowe profile available in your workspace and configured as a default for Z Open Editor.
      • You need to be able to run the processor via a Zowe TSO command. 
      • The TSO operation needs to create an output data member that contains valid COBOL or PL/I.
      • The program file to be processed needs to be in a PDS that is recognized by Z Open Editor to contain COBOL (PL/I) and the COBOL (PL/I) language support must be active. See Remote file associations for more details.
       ZAPP profile
      The integration of the preprocessor with the editor is handled via a ZAPP file profile. Such a profile could look like this:
      - name: extended-cobol
   type: preprocessor
+  language: cobol
   location: mvs
   settings:
     commandDataSet: ${HLQ}.PREPROC.REXX.(PREPROC)
     tempDataHLQ: ${HLQ}
     outputDataSet: ${HLQ}.PREPROC.OUTPUT()
     commandParameters: "var1=val1"
-
      In the settings object the following properties can be used:
      PropertyDescription
      commandDataSetThe data member to be executed. You can mix with ZAPP Variables. You need to define ${HLQ} in the example above as ZAPP variables. Environment variables can only be used by specifying them with the below commandParameters property.
      tempDataHLQThe High Level Qualifier (HLQ) to use to save an xml file that stores information for the commandDataSet to read from.
      outputDataSetThe output dataset to save the data member output file of the preprocessor.
      commandParametersAn optional parameter to specify any command parameters that should be used when executing the command.
       Running the preprocessor
      After you specify the ZAPP profile, you can run the preprocessor in the following ways:
      1. Right-click and choose Execute remote preprocessor command to manually run the preprocessor in the program file editor.
      2. Automatically run the preprocessor via the VS Code user setting zopeneditor.cobol.autoPreprocessor. The setting can have one of the values: 
        • off: disables the automatic preprocessor execution.
        • open: when a program file is opened in the editor.
        • save: when a program file is saved in the editor.
        • both: when opening and saving a program file in the editor.
      When the preprocessor command runs, a progress dialog with a Cancel button is displayed. A sequential data member is created using the tempDataHLQ to store information for the preprocessor to read. When the preprocessor finishes, it deletes the sequential data member and then refreshes the editor and any syntax errors that were caused by preprocessor statements should go away or, if they contained problems, will show those instead.
      If the processor command execution failed and produced errors, a dialog will be shown with a button to open the Z Open Editor log file viewer which lists the detailed error message produced by the preprocessor command and the sequential data member will not be deleted.
      The following is an example of the sequential data member that gets created for the remote preprocessor to read based on the above ZAPP profile:
      <PROGRAM>HLQ.COBOL(PRINTAPP)</PROGRAM><SYSLIB></SYSLIB><COMPILEOPTIONS></COMPILEOPTIONS><OUTPUT>HLQ.PREPROC.OUTPUT(PRINTAPP)</OUTPUT>
-
      • The ${HLQ} variable gets replaced with HLQ from user settings
      • The input data member's name was PRINTAPP
      • There were no mvs cobol libraries or compiler options specified in the ZAPP property groups
       Using the preprocessor output in the editor
      After the preprocessor is executed, you can hover the mouse of preprocessor statements in their program file to see the COBOL code that was generated for the statement. You can edit these statements and all other COBOL code in the program.
      Syntax errors for preprocessor statements will not be available until the preprocessor runs again. Syntax errors for other regular COBOL will be shown while typing as usual in Z Open Editor.
      To get a side-by-side view of the program before and after preprocessing, you can use the right-click menu option Compare preprocessor input and output files.
       Limitations
      Restriction: Several limitations are associated with using a preprocessor within Z Open Editor:
      • Code formatting will be disabled for files that contain preprocessor statements.
      • Not all preprocessor statements within an EXEC block might be identified.
      • All preprocessor statements might not be identified if the code is reorganized.
      • Preprocessor statements that modify text in another location of a program might not be identified.
      • Real-time syntax checking of programs that contain preprocessor statements that contain only the beginning or ending of a language comment might not be identified.
      • Remote preprocessor command dataset members must be either REXX or CLIST files.
      • The side-by-side comparison of program and preprocessed output is not yet available for the remote preprocessor support.
      Last Updated: 
      Contributors: Ethan Mendel, PETER HAUMER, Ankit Kumar, Hestia Zhang
      
-    
+
      The language property is mandatory and allows the values cobol or pl1 only.
      In the settings object the following properties can be used:
      PropertyDescription
      commandDataSetThe data member to be executed. You can mix with ZAPP Variables. You need to define ${HLQ} in the example above as ZAPP variables. Environment variables can only be used by specifying them with the below commandParameters property.
      tempDataHLQThe High Level Qualifier (HLQ) to use to save an xml file that stores information for the commandDataSet to read from.
      outputDataSetThe output dataset to save the data member output file of the preprocessor.
      commandParametersAn optional parameter to specify any command parameters that should be used when executing the command.
       Running the preprocessor
      After you specify the ZAPP profile, you can run the preprocessor in the following ways:
      1. Right-click and choose Execute remote preprocessor command to manually run the preprocessor in the program file editor.
      2. Automatically run the preprocessor via the VS Code user setting zopeneditor.autoPreprocessor. The setting can have one of the values: 
        • off: disables the automatic preprocessor execution.
        • open: when a program file is opened in the editor.
        • save: when a program file is saved in the editor.
        • both: when opening and saving a program file in the editor.
      When the preprocessor command runs, a progress dialog with a Cancel button is displayed. A sequential data member is created using the tempDataHLQ to store information for the preprocessor to read. When the preprocessor finishes, it deletes the sequential data member and then refreshes the editor and any syntax errors that were caused by preprocessor statements should go away or, if they contained problems, will show those instead.
      If the processor command execution failed and produced errors, a dialog will be shown with a button to open the Z Open Editor log file viewer which lists the detailed error message produced by the preprocessor command and the sequential data member will not be deleted.
      The following is an example of the sequential data member that gets created for the remote preprocessor to read based on the above ZAPP profile:
      <PROGRAM>HLQ.COBOL(PRINTAPP)</PROGRAM><SYSLIB></SYSLIB><COMPILEOPTIONS></COMPILEOPTIONS><OUTPUT>HLQ.PREPROC.OUTPUT(PRINTAPP)</OUTPUT>
+
      • The ${HLQ} variable gets replaced with HLQ from user settings
      • The input data member's name was PRINTAPP
      • There were no mvs cobol libraries or compiler options specified in the ZAPP property groups
       Using the preprocessor output in the editor
      After the preprocessor is executed, you can hover the mouse of preprocessor statements in their program file to see the code that was generated for the statement. You can edit these statements and all other code in the program.
      Syntax errors for preprocessor statements will not be available until the preprocessor runs again. Syntax errors for other regular COBOL or PL/I code will be shown while typing as usual in Z Open Editor.
      To get a side-by-side view of the program before and after preprocessing, you can use the right-click menu option Compare preprocessor input and output files.
       Limitations
      Restriction: Several limitations are associated with using a preprocessor within Z Open Editor:
      • COBOL code formatting will be disabled for files that contain preprocessor statements.
      • Not all preprocessor statements within a COBOL EXEC block might be identified.
      • All preprocessor statements might not be identified if the code is reorganized.
      • Preprocessor statements that modify text in another location of a program might not be identified.
      • Real-time syntax checking of programs that contain preprocessor statements that contain only the beginning or ending of a language comment might not be identified.
      • Remote preprocessor command dataset members must be either REXX or CLIST files.
      • The side-by-side comparison of program and preprocessed output is not yet available for the remote preprocessor support.
      Last Updated: 
      Contributors: Ethan Mendel, PETER HAUMER, Ankit Kumar, Hestia Zhang
      
+    
   
 
diff --git a/Docs/advanced_problems_view.html b/Docs/advanced_problems_view.html
index 7bd035e48..2523c1c2f 100644
--- a/Docs/advanced_problems_view.html
+++ b/Docs/advanced_problems_view.html
@@ -41,11 +41,11 @@
                 }
             )();
             User build Problems view | IBM Z® Open Editor
-    
+    
     
   
   
     
      IBM Z® Open Editor
       User build Problems view
      When you edit enterprise application code in Z Open Editor you get full language support provided by our language servers giving you code completion and real-time syntax errors. However, the parsers utilized in Z Open Editor can only identify problems that a compiler can detect. As a result, sometimes it is necessary to actually build the program and review the compiler output, which includes warnings that the editor was not able to produce.
      Z Open Editor provides an integration with IBM Dependency-Based Build called user buildopen in new window. You can run a build of a program directly from inside Z Open Editor via the context menu. When integrated with Zowe Explorer, the program will be uploaded to USS and then built with Dependency-Based Build. Until now the build would complete by downloading the build log files into the local development workspace. You would have to review the log file by opening it in the editor and scrolling through it.
      If you enable Z Open Editor's advanced capabilities, Dependency-Based Build log files will now be parsed by Z Open Editor and presented as errors and warnings in the regular VS Code Problems view. You can click entries in the Problems view to directly navigate to the line in the code for which the problem was reported. These error will be shown next to regular Z Open Editor errors side-by-side, but you can distinguish them by the compiler error number displayed next to them.
      The Problems view can be cleared manually via a right-click on any message or automatically when you rerun a build.
      User Build Problems View
      The screenshot above shows an example of the Problems view reporting a warning about a RECORD IS VARYING statement not matching the required range. The problem could only be found by building the program. CCombining parse with user build errors and warnings gives developers new ways to determine problems they could not have before.
      Last Updated: 
      Contributors: PETER HAUMER
      
-    
+    
   
 
diff --git a/Docs/advanced_resource_table.html b/Docs/advanced_resource_table.html
index 4e720a1c8..7811dc404 100644
--- a/Docs/advanced_resource_table.html
+++ b/Docs/advanced_resource_table.html
@@ -41,11 +41,11 @@
                 }
             )();
             z/OS Resources Table | IBM Z® Open Editor
-    
+    
     
   
   
-    
      IBM Z® Open Editor
       z/OS Resources Table
      The z/OS Resources Table provides a tabular view to interact with z/OS resources using your existing RSE API or z/OSMF Zowe profiles. It is an advanced capability available for users with an active license. It is designed to be both beginner-friendly for new mainframe application developers and to provide more experienced developers with the necessary tools and information to manage host resources.
       Setting up profiles for the z/OS Resources Table
      To use the z/OS Resources Table, you must create an RSE API or z/OSMF profile using Zowe Explorer. For more information on how to create profiles by using Zowe Explorer, see Connecting to z/OS with Zowe Explorer walkthrough.
       Opening the z/OS Resources Table
      You can open the z/OS Resources Table in one of the following ways:
      • Cmd ⌘/Ctrl + Shift + P to open the command prompt and run the command >IBM Z Open Editor: Open z/OS Resource Table.
      • After setting an active filter for a profile in the Zowe Explorer JOBS, DATA SETS, or USS view, right-click the active profile and select Show in z/OS Resource Table from the context menu. This will display items matching the filter in the table.
      • After setting an active filter for a profile in the Zowe Explorer JOBS, DATA SETS, or USS view, right-click a resource (e.g. a data set, a job) and select Show in z/OS Resource Table from the context menu. This will display the selected resource in the table.
      The first two methods will open the table and display the default Profiles view. The third method will display the data sets or jobs matching that filter.
       Views
       Profiles View
      The profiles view displays the RSE API and z/OSMF profiles defined in your Zowe Explorer team configuration file. To start accessing z/OS resources for a specific profile, click on the row of that profile.
      After clicking on a profile, a view is displayed that allows the user to select a z/OS resource to access: MVS, USS, and JES. Clicking on one of these rows will load the MVS view, USS view, or JES view, respectively.
       MVS View
      The MVS view consists of the following rows that perform the following actions when clicked:
      • Default User Data Sets: Displays all data sets that have the selected profile's user ID as their high-level qualifier (only available for profiles using password or passphrase authentication)
      • Filters: Opens the Filters view where users can create and use custom patterns for viewing data sets.
      • Favorites: Opens a view that displays data sets favorited by the user.
      • History: Opens a view that displays the five most recently used patterns to filter data sets.
      Clicking on the Default User Data Sets, a custom pattern in the Filters view, or a pattern in the History view will display data sets that match the selected pattern.
       JES View
      The JES view consists of the following rows that perform the following actions when clicked:
      • Default User Jobs: Displays all jobs that have the selected profile's user as their owner (only available for profiles using password or passphrase authentication)
      • Filters: Opens the Filters view where users can create and use custom patterns for viewing jobs.
      • Favorites: Opens a view that displays jobs favorited by the user.
      • History: Opens a view that displays the five most recently used queries to filter jobs.
      Clicking on the Default User Jobs, a custom query in the Filters view, or a query in the History view will display jobs that match the selected query.
       USS View
      The USS view consists of the following rows that perform the following actions when clicked:
      • User Files: Displays all items in the /u/user directory, where user is the selected profile's user (only available for profiles using password or passphrase authentication)
      • Filters: Opens the Filters view where users can use and save paths for viewing UNIX items.
      • Favorites: Opens a view that displays UNIX items favorited by the user.
      • History: Opens a view that displays the five most recently viewed UNIX items.
       Actions
      When viewing resources, there are different kinds of actions available in the table. These include toolbar actions, batch actions, and overflow menu actions.
      'zos-resource-table-actions'
      • Navigation actions are the same across all views. They can be used to navigate through the table's history or to return to the Profiles view.
      • Toolbar actions are unique to specific views. For example, the Create Data Set button is only available when viewing data sets. Hovering a toolbar action button will display popover text describing what the button does.
      • Overflow menu actions are available only in select views. Selecting an overflow menu action will perform the action for the selected resource. An overflow menu can be opened by clicking the three dots ⋮ on the right side of a row. These dots appear on row hover, and will not appear on rows that do not use overflow actions.
      • The input area is a special field available while viewing jobs, UNIX files, or data sets that enables users to quickly change the active filter pattern and display an updated list of resources matching that pattern.
      The last available kind of actions are batch actions.
      'zos-resource-table-batch-actions'
      Batch actions are only available for views with selectable rows. They are displayed after the user selects one or many rows using the checkboxes on the left side of the view. Batch actions are executed on every resource selected. For example, if you select the checkbox for multiple jobs and use the Delete batch action, all the selected jobs will be deleted.
       Search and Filter actions for partitioned and sequential data sets
      The z/OS Resources Table provides actions for searching and filtering partitioned and sequential data sets to refine the results of the data sets query.
      When viewing data sets, two new buttons for Search and Filter will be available in the toolbar.
      'zos-resources-table-search-filter-buttons'
      Clicking the Search button will open a menu that lets the user specify a string. After clicking Submit, a search is performed for sequential data sets containing the specified content. The results are displayed in the table in expandable rows, which include the sequential data set name and its attributes, the number of matches, and the line that contains the content.
      'zos-resources-table-search-results'
      This search is limited to the active filter's scope (which is displayed in the top-left of the table) and by any filters specified in the Filter menu. After a search is submitted, it will stay active until it is cleared. To clear the search, press the Reset button to the right of the Submit button.
      Clicking one of the matches in the search results will open the sequential data set in an editor. The matching content of that line will be selected and your cursor will be placed at the end of the content.
       Filter
      Clicking the Filter button will open a menu that contains checkboxes for controlling the visibility of partitioned and sequential data sets and an input field that accepts a data set name pattern. This input field accepts wildcards * and is used to limit the scope of the active filter further.
      For example, if the active filter is IBMUSER.* and *.SAMPLE.* is entered into the input field and submitted, only data sets with IBMUSER as the high-level qualifier that contain a SAMPLE qualifier anywhere in the data set name will be displayed in the table (e.g. IBMUSER.SAMPLE.COBOL, IBMUSER.X.Y.Z.SAMPLE).
      After you adjust the visibility of partitioned or sequential data sets and click Submit, only data sets that satisfy the filter(s) will be displayed in the table. This filter will stay active until it is cleared, even if the user changes the active filter. To clear the filter, press the Reset button to the right of the Submit button.
      'zos-resources-table-filter-results'
      Users can simultaneously specify and submit filters and a search to apply them to the active filter.
      Last Updated: 
      Contributors: Benjamin Santos, Hestia Zhang, PETER HAUMER, Peter Haumer, Saile Daimwood
      
-    
+    
      IBM Z® Open Editor
       z/OS Resources Table
      The z/OS Resources Table provides a tabular view to interact with z/OS resources using your existing RSE API or z/OSMF Zowe profiles. It is an advanced capability available for users with an active license. It is designed to be both beginner-friendly for new mainframe application developers and to provide more experienced developers with the necessary tools and information to manage host resources.
       Setting up profiles for the z/OS Resources Table
      To use the z/OS Resources Table, you must create an RSE API or z/OSMF profile using Zowe Explorer. For more information on how to create profiles by using Zowe Explorer, see Connecting to z/OS with Zowe Explorer walkthrough.
       Opening the z/OS Resources Table
      You can open the z/OS Resources Table in one of the following ways:
      • Cmd ⌘/Ctrl + Shift + P to open the command prompt and run the command >IBM Z Open Editor: Open z/OS Resource Table.
      • After setting an active filter for a profile in the Zowe Explorer JOBS, DATA SETS, or USS view, right-click the active profile and select Show in z/OS Resource Table from the context menu. This will display items matching the filter in the table.
      • After setting an active filter for a profile in the Zowe Explorer JOBS, DATA SETS, or USS view, right-click a resource (e.g. a data set, a job) and select Show in z/OS Resource Table from the context menu. This will display the selected resource in the table.
      The first two methods will open the table and display the default Profiles view. The third method will display the data sets or jobs matching that filter.
       Views
       Profiles View
      The profiles view displays the RSE API and z/OSMF profiles defined in your Zowe Explorer team configuration file. To start accessing z/OS resources for a specific profile, click on the row of that profile.
      After clicking on a profile, a view is displayed that allows you to select a z/OS resource to access: MVS, USS, and JES. Clicking on one of these rows will load the MVS view, USS view, or JES view, respectively.
       MVS View
      The MVS view consists of the following rows that perform the following actions when clicked:
      • Default User Data Sets: Displays all data sets that have the selected profile's user ID as their high-level qualifier (only available for profiles using password or passphrase authentication)
      • Filters: Opens the Filters view where users can create and use custom patterns for viewing data sets.
      • Favorites: Opens a view that displays data sets favorited by the user.
      • History: Opens a view that displays the five most recently used patterns to filter data sets.
      Clicking on the Default User Data Sets, a custom pattern in the Filters view, or a pattern in the History view will display data sets that match the selected pattern.
       JES View
      The JES view consists of the following rows that perform the following actions when clicked:
      • Default User Jobs: Displays all jobs that have the selected profile's user as their owner (only available for profiles using password or passphrase authentication)
      • Filters: Opens the Filters view where users can create and use custom patterns for viewing jobs.
      • Favorites: Opens a view that displays jobs favorited by the user.
      • History: Opens a view that displays the five most recently used queries to filter jobs.
      Clicking on the Default User Jobs, a custom query in the Filters view, or a query in the History view will display jobs that match the selected query.
       USS View
      The USS view consists of the following rows that perform the following actions when clicked:
      • User Files: Displays all items in the /u/user directory, where user is the selected profile's user (only available for profiles using password or passphrase authentication)
      • Filters: Opens the Filters view where users can use and save paths for viewing UNIX items.
      • Favorites: Opens a view that displays UNIX items favorited by the user.
      • History: Opens a view that displays the five most recently viewed UNIX items.
       Actions
      When viewing resources, there are different kinds of actions available in the table. These include toolbar actions, batch actions, and overflow menu actions.
      'zos-resource-table-actions'
      • Navigation actions are the same across all views. They can be used to navigate through the table's history or to return to the Profiles view.
      • Toolbar actions are unique to specific views. For example, the Create Data Set button is only available when viewing data sets. Hovering a toolbar action button will display popover text describing what the button does.
      • Overflow menu actions are available only in select views. Selecting an overflow menu action will perform the action for the selected resource. An overflow menu can be opened by clicking the three dots ⋮ on the right side of a row. These dots appear on row hover, and will not appear on rows that do not use overflow actions.
      • The input area is a special field available while viewing jobs, UNIX files, or data sets that enables users to quickly change the active filter pattern and display an updated list of resources matching that pattern.
      The last available kind of actions are batch actions.
      'zos-resource-table-batch-actions'
      Batch actions are only available for views with selectable rows. They are displayed after the user selects one or many rows using the checkboxes on the left side of the view. Batch actions are executed on every resource selected. For example, if a users selects checkboxes for multiple jobs and uses the Delete batch action, all the selected jobs will be deleted.
       Search and Filter actions
      The z/OS Resources Table provides actions for searching and filtering partitioned and sequential data sets to refine the results of the data sets query.
      When viewing data sets, two new buttons for Search and Filter will be available in the toolbar.
      'zos-resources-table-search-filter-buttons'
      Clicking the Search button will open a menu that allows users to perform a search for sequential data set content or partitioned data set members. After a search is submitted, it will stay active until it is cleared. To clear the search, press the Reset button to the right of the Submit button in the search menu.
      For sequential data sets, you can specify string content in the input field. After clicking Submit, a search is performed for sequential data sets containing the specified content. The results are displayed in the table in expandable rows, which include the sequential data set name and its attributes, the number of matches, and the line that contains the content.
      'zos-resources-table-sequential-search-results'
      This search is limited to the active filter's scope (which is displayed in the top-left of the table) and by any filters specified in the Filter menu.
      You can use the dropdown menu to switch the search from sequential data set content to partitioned data set members. This menu allows users to specify a member name pattern (accepts wildcards) and/or member content. After clicking Submit, only members matching that pattern and/or containing that content will be displayed in the table. Each member will be displayed in an expandable row, which includes the full member name, the number of matches, and the line that contains the matching content. Only members in partitioned data sets that match the active filter and any filters specified in the Filter menu will be included in the search.
      'zos-resources-table-members-search-results'
      You can also perform a member search within a partitioned data set. This search will only include members in the opened partitioned data set.
      Clicking one of the matches in the search results will open the sequential data set/member in a new editor. The matching content within that line will be selected and your cursor will be placed at the end of the content.
      While browsing USS, you can click the Search button to open a menu that allows users to perform a search for UNIX files. You can specify a file name pattern (accepts wild cards) and or file content to search for. After clicking Submit, only files matching the specified pattern and/or containing the specified content will be displayed in the table.
      'zos-resources-table-uss-search-results'
      Clicking one of the matches in the search results will open the file in a new editor. The matching content within that line will be selected and your cursor will be placed at the end of the content.
       Filter
      Clicking the Filter button will open a menu that contains checkboxes for controlling the visibility of partitioned and sequential data sets and an input field that accepts a data set name pattern. This input field accepts wildcards * and is used to limit the scope of the active filter further.
      For example, if the active filter is IBMUSER.* and *.SAMPLE.* is entered into the input field and submitted, only data sets with IBMUSER as the high-level qualifier that contain a SAMPLE qualifier anywhere in the data set name will be displayed in the table (e.g. IBMUSER.SAMPLE.COBOL, IBMUSER.X.Y.Z.SAMPLE).
      After adjusting the visibility of partitioned or sequential data sets and clicking Submit, only data sets that satisfy the filter(s) will be displayed in the table. This filter will stay active until it is cleared, even if the user changes the active filter. To clear the filter, press the Reset button to the right of the Submit button.
      'zos-resources-table-filter-results'
      You can simultaneously specify and submit filters and a search to apply them to the active filter.
       List of available actions
      Below is a comprehensive list of all actions available for each resource.
      • MVS data sets and members 
        • Create, delete, rename, migrate, edit, allocate copy, favorite/unfavorite, view members, submit members as jobs, upload members, filter data sets by name, partitioned data set and member search (by name or content), sequential data set search (by name or content)
      • USS files and directories 
        • Create, delete, edit, upload files, rename, copy and paste, edit attributes, favorite/unfavorite, file search (by name or content)
      • JES jobs 
        • Delete, get JCL, issue stop command, issue modify command, view and download spool files
      • All resources 
        • Change active filter/query, create and save filters/queries, sort by attribute, view filter/query history, view favorites
      Last Updated: 
      Contributors: Benjamin Santos, Hestia Zhang, PETER HAUMER, Peter Haumer, Saile Daimwood
      
+    
   
 
diff --git a/Docs/connect_to_zos_with_zowe_cli_e2e.html b/Docs/connect_to_zos_with_zowe_cli_e2e.html
index 87b4fd94d..e6bb22076 100644
--- a/Docs/connect_to_zos_with_zowe_cli_e2e.html
+++ b/Docs/connect_to_zos_with_zowe_cli_e2e.html
@@ -41,11 +41,11 @@
                 }
             )();
             Connecting to z/OS using Zowe CLI walk through | IBM Z® Open Editor
-    
+    
     
   
   
     
      IBM Z® Open Editor
       Connecting to z/OS using Zowe CLI walk through
       Creating a Zowe team configuration file
      1. Issue the zowe config init command and you will be prompted for profile information. After responding to the prompts, the zowe.config.json file will be added to your ~/.zowe directory.
        • Run zowe config init --global-config to create a global profile.
        • Run zowe config init --help to learn all options for editing profiles by using a command line.
        Note: This tutorial walks through creating a global profile. User scoped configuration is very similar except that the file is created in your project's folder and is named zowe.user.json. Run zowe config init --user-config to create a profile scoped to your project folder.
      2. If you responded to the prompts to enter a username and password for a mainframe service, your credentials are stored securely on your computer by default.
      3. Open the zowe.config.json file in any text editor that supports JSON files, and then update the host and port values and other information needed in the profiles that are listed in the configuration file.
      4. Fill out the rse or zosmf profile template inside zowe.config.json depending on which type of profile you are creating.
      5. You can also use the command line to set team configuration properties. For example, run zowe config set "profiles.host1.profiles.service1.properties.setting" "value" --global-configzowe config set --secure ... to set a secure property.
      6. If username and password were entered in step 1, you can use your profiles to access data sets, z/OS UNIX System Services files and directories, and jobs. If not entered, you will be prompted the first time you run a CLI command. If ‘autoStore:true’ is set in the configuration file, the credentials will be stored securely on your computer.
      For more information about team configuration profiles in Zowe, see Zowe CLI documentationopen in new window.
      For a Zowe team configuration file example, see here.
       Supported authentication methods
      Zowe supports many authentication mechanisms and you are not limited to username and password only. For more information, see Supported methods of authentication for z/OS using Zowe.
      Last Updated: 
      Contributors: KRISTINA MAYO, Chun Hong Zheng
      
-    
+    
   
 
diff --git a/Docs/connect_to_zos_with_zowe_explorer_e2e.html b/Docs/connect_to_zos_with_zowe_explorer_e2e.html
index b0e29dc61..4fdad7d19 100644
--- a/Docs/connect_to_zos_with_zowe_explorer_e2e.html
+++ b/Docs/connect_to_zos_with_zowe_explorer_e2e.html
@@ -41,7 +41,7 @@
                 }
             )();
             Connecting to z/OS with Zowe Explorer walk through | IBM Z® Open Editor
-    
+    
     
   
   
@@ -103,6 +103,6 @@
   "autoStore": true
 }
 
       Troubleshooting
      ErrorResolution
      When I click "Add profile", no profiles show upThis might happen when a team configuration file is invalid, for example, when there is a syntax error. Ensure that you team configuration file is saved and is valid.
      Error: Zowe REST Operations API Error: or http(s) request error event called or Error: connect ECONNREFUSED myzos.ibm.com:6800In most cases, the error occurs because your RSE API port is wrong. 
       
      • Ensure you access RSE API using correct port. Swagger API doc should be available on the port, for example: https://myzos.ibm.com:6800/rseapi/api-docs/.
      • If you have zowe cli with rse-api-for-zowe-cli plugin installed, use the following command to confirm RSE API is running on port specified in the profile: zowe rse check status.
      Error: z/OSMF REST API Error: or http(s) request error event called or Error: getaddrinfo ENOTFOUND myzos.ibm.comIf you are using an internal z/OS system behind a firewall, make sure you have connected through the firewall.
      Error: Zowe REST Operations API Error: or http(s) request error event called or Error: self signed certificate or Error: z/OSMF REST API Error: or http(s) request error event called or Error: certificate has expiredIf your z/OS is using self-signed certificates, make sure to set "rejectUnauthorized": false.
      Failed to load schema for profile type rse or Failed to load schema for config file /Users/user/.zowe/zowe.config.json: invalid schema fileIf you get any schema related error, your zowe.schema.json might be missing, not updated properly, or corrupted. For more information, see sharing team configuration files.
    Last Updated: 
    Contributors: KRISTINA MAYO, Chun Hong Zheng, Peter Haumer
    
-    
+    
   
 
diff --git a/Docs/creating_team_profiles.html b/Docs/creating_team_profiles.html
index 7d6800831..d25d42957 100644
--- a/Docs/creating_team_profiles.html
+++ b/Docs/creating_team_profiles.html
@@ -41,7 +41,7 @@
                 }
             )();
             Creating a configuration profile in Zowe Explorer v2.0.0 | IBM Z® Open Editor
-    
+    
     
   
   
@@ -120,6 +120,6 @@
 }

    For more information on other types of team configuration profiles, view Zowe CLI's documentation on Using team profilesopen in new window with example configurations.

Last Updated:
Contributors: Rudy Leonel Pichola Flores, Billie Simmons, kmaselli
- + diff --git a/Docs/customizing_the_outline_view.html b/Docs/customizing_the_outline_view.html index aa8cfa06c..0d6625293 100644 --- a/Docs/customizing_the_outline_view.html +++ b/Docs/customizing_the_outline_view.html @@ -41,11 +41,11 @@ } )(); Customizing the Outline view | IBM Z® Open Editor - + -
IBM Z® Open Editor

Customizing the Outline view

The Outline view shows a symbol tree of the currently active editor. IBM Z Open Editor maps each symbol to a language element of COBOL, PL/I, HLASM, and REXX.

However, you might not want every symbol to display in the Outline view. To control which ones appear, you can modify the User or Workspace settings. At this time, the REXX Outline view displays the internal routine symbol only.

Enabling or disabling Outline view symbols

  1. Navigate to your User and Workspace settings using the following VS Code menu command:

    • Windows/Linux: File > Preferences > Settings
    • MacOS: Code > Preferences > Settings

    Note: VS Code provides different scopes for defining these settings. For more information, see User preferences versus workspace preferences.

  2. Type Outline in the search box to filter the settings.

  3. Enable or disable the Outline view settings based on your needs. Refer to the Outline view symbol mapping reference to understand which settings affect which symbols.

If you would rather modify the Outline view settings in their raw JSON form, run one of the following commands using the Command Palette. Note that it is not recommended to change the Default settings.

Command Palette (⇧⌘P) (Ctrl+Shift+P)Settings
> Open Settings (JSON)User
> Open Default Settings (JSON)Default
> Open Workspace Settings (JSON)Workspace

Outline view symbol mapping reference

Note that some symbols are used more than once. This is expected behavior.

This table highlights the relationship between Outline view settings in JSON form and UI form.

JSONSettings Editor
"outline.showBooleans":trueoutline-view-setting

COBOL

SymbolCOBOL Language ElementVisual Studio Code Setting
symbol-booleanPROCEDURE_DIVISION"outline.showBooleans":true
symbol-classDIRECTIVE"outline.showClasses":true
symbol-constantPROG_ID"outline.showConstants":true
symbol-constructorDATA_DIVISION"outline.showConstructors":true
symbol-enum-memberMAINLINE_SECTION"outline.showEnumMembers":true
symbol-enumLINKAGE_SECTION"outline.showEnums":true
symbol-eventWORKING_STORAGE_SECTION"outline.showEvents":true
symbol-fieldPROCESS"outline.showFields":true
symbol-fileROOT"outline.showFiles":true
symbol-functionPARAGRAPH"outline.showFunctions":true
symbol-interfaceENVIRONMENT_DIVISION"outline.showInterfaces":true
symbol-keyDECLARATIVES"outline.showKeys":true
symbol-methodANY_OTHER_SECTION"outline.showMethods":true
symbol-moduleCONFIGURATION_SECTION"outline.showModules":true
symbol-namespaceCOPY"outline.showNamespaces":true
symbol-numberANY_OTHER_DIVISION"outline.showNumbers":true
symbol-objectLOCAL_STORAGE_SECTION"outline.showObjects":true
symbol-operatorEND"outline.showOperators":true
symbol-packagePROGRAM"outline.showPackages":true
symbol-propertyIDENTIFICATION_DIVISION, ID_DIVISION"outline.showProperties":true
symbol-stringLEVEL_1_HAS_SUBFIELDS, LEVEL_INDICATOR"outline.showStrings":true
symbol-structFILE_SECTION"outline.showStructs":true
symbol-type-parameterINPUT_OUTPUT_SECTION"outline.showTypeParameters":true
symbol-variableLEVEL_1_HAS_NO_SUBFIELDS, LEVEL_3, LEVEL_X"outline.showVariables":true

PL/I

SymbolPL/I Language ElementVisual Studio Code Setting
symbol-classPROCEDURE"outline.showClasses":true
symbol-eventEVENT"outline.showEvents":true
symbol-fieldDATAITEM_HAS_SUBFIELDS"outline.showFields":true
symbol-fileROOT"outline.showFiles":true
symbol-functionPACKAGE"outline.showFunctions":true
symbol-interfaceLABEL"outline.showInterfaces":true
symbol-methodREVERT"outline.showMethods":true
symbol-namespaceINCLUDE"outline.showNamespaces":true
symbol-operatorEND"outline.showOperators":true
symbol-packageBEGIN"outline.showPackages":true
symbol-variableDATAITEM_HAS_NO_SUBFIELDS"outline.showVariables":true

HLASM

SymbolHLASM Language ElementVisual Studio Code Setting
symbol-classBRANCH_LABELS"outline.showClasses":true
symbol-functionCSECT"outline.showFunctions":true
symbol-objectMACRO"outline.showObjects":true
symbol-structDSECT"outline.showStructs":true
symbol-structRSECT"outline.showStrings":true
symbol-structCOM"outline.showInterfaces":true
symbol-structLOCTR"outline.showProperties":true
symbol-structLABEL"outline.showVariables":true

REXX

SymbolREXX Language ElementVisual Studio Code Setting
symbol-objectINTERNAL ROUTINE"outline.showObjects":true

JCL

SymbolJCL Language ElementVisual Studio Code Setting
symbol-fieldDD Statement"outline.showFields":true
symbol-interfaceEXEC Statement"outline.showInteraces":true
symbol-eventJOB Statement"outline.showEvents":true
Last Updated:
Contributors: Bradley Knaysi, Greg Lambert, Peter Haumer, Saile Daimwood, Prasang Prajapati, Saile, Shi Kun Li
- +
IBM Z® Open Editor

Customizing the Outline view

The Outline view shows a symbol tree of the currently active editor. IBM Z Open Editor maps each symbol to a language element of COBOL, PL/I, HLASM, and REXX.

However, you might not want every symbol to display in the Outline view. To control which ones appear, you can modify the User or Workspace settings. At this time, the REXX Outline view displays the internal routine symbol only.

Enabling or disabling Outline view symbols

  1. Navigate to your User and Workspace settings using the following VS Code menu command:

    • Windows/Linux: File > Preferences > Settings
    • MacOS: Code > Preferences > Settings

    Note: VS Code provides different scopes for defining these settings. For more information, see User preferences versus workspace preferences.

  2. Type Outline in the search box to filter the settings.

  3. Enable or disable the Outline view settings based on your needs. Refer to the Outline view symbol mapping reference to understand which settings affect which symbols.

If you would rather modify the Outline view settings in their raw JSON form, run one of the following commands using the Command Palette. Note that it is not recommended to change the Default settings.

Command Palette (⇧⌘P) (Ctrl+Shift+P)Settings
> Open Settings (JSON)User
> Open Default Settings (JSON)Default
> Open Workspace Settings (JSON)Workspace

Outline view symbol mapping reference

Note that some symbols are used more than once. This is expected behavior.

This table highlights the relationship between Outline view settings in JSON form and UI form.

JSONSettings Editor
"outline.showBooleans":trueoutline-view-setting

COBOL

SymbolCOBOL Language ElementVisual Studio Code Setting
symbol-booleanPROCEDURE_DIVISION"outline.showBooleans":true
symbol-classDIRECTIVE"outline.showClasses":true
symbol-constantPROG_ID"outline.showConstants":true
symbol-constructorDATA_DIVISION"outline.showConstructors":true
symbol-enum-memberMAINLINE_SECTION"outline.showEnumMembers":true
symbol-enumLINKAGE_SECTION"outline.showEnums":true
symbol-eventWORKING_STORAGE_SECTION"outline.showEvents":true
symbol-fieldPROCESS"outline.showFields":true
symbol-fileROOT"outline.showFiles":true
symbol-functionPARAGRAPH"outline.showFunctions":true
symbol-interfaceENVIRONMENT_DIVISION"outline.showInterfaces":true
symbol-keyDECLARATIVES"outline.showKeys":true
symbol-methodANY_OTHER_SECTION"outline.showMethods":true
symbol-moduleCONFIGURATION_SECTION"outline.showModules":true
symbol-namespaceCOPY"outline.showNamespaces":true
symbol-numberANY_OTHER_DIVISION"outline.showNumbers":true
symbol-objectLOCAL_STORAGE_SECTION"outline.showObjects":true
symbol-operatorEND"outline.showOperators":true
symbol-packagePROGRAM"outline.showPackages":true
symbol-propertyIDENTIFICATION_DIVISION, ID_DIVISION"outline.showProperties":true
symbol-stringLEVEL_1_HAS_SUBFIELDS, LEVEL_INDICATOR"outline.showStrings":true
symbol-structFILE_SECTION"outline.showStructs":true
symbol-type-parameterINPUT_OUTPUT_SECTION"outline.showTypeParameters":true
symbol-variableLEVEL_1_HAS_NO_SUBFIELDS, LEVEL_3, LEVEL_X"outline.showVariables":true

PL/I

SymbolPL/I Language ElementVisual Studio Code Setting
symbol-classPROCEDURE"outline.showClasses":true
symbol-eventEVENT"outline.showEvents":true
symbol-fieldDATAITEM_HAS_SUBFIELDS"outline.showFields":true
symbol-fileROOT"outline.showFiles":true
symbol-functionPACKAGE"outline.showFunctions":true
symbol-interfaceLABEL"outline.showInterfaces":true
symbol-methodREVERT"outline.showMethods":true
symbol-namespaceINCLUDE"outline.showNamespaces":true
symbol-operatorEND"outline.showOperators":true
symbol-packageBEGIN"outline.showPackages":true
symbol-variableDATAITEM_HAS_NO_SUBFIELDS"outline.showVariables":true

HLASM

SymbolHLASM Language ElementVisual Studio Code Setting
symbol-classBRANCH_LABELS"outline.showClasses":true
symbol-functionCSECT"outline.showFunctions":true
symbol-objectMACRO"outline.showObjects":true
symbol-structDSECT"outline.showStructs":true
symbol-structRSECT"outline.showStrings":true
symbol-structCOM"outline.showInterfaces":true
symbol-structLOCTR"outline.showProperties":true
symbol-structLABEL"outline.showVariables":true

REXX

SymbolREXX Language ElementVisual Studio Code Setting
symbol-objectINTERNAL ROUTINE"outline.showObjects":true

JCL

SymbolJCL Language ElementVisual Studio Code Setting
symbol-fieldDD Statement"outline.showFields":true
symbol-interfaceEXEC Statement"outline.showInteraces":true
symbol-eventJOB Statement"outline.showEvents":true
Last Updated:
Contributors: Bradley Knaysi, Greg Lambert, Peter Haumer, Saile Daimwood, Prasang Prajapati, Saile, Shi Kun Li
+ diff --git a/Docs/ebcdic_encoding.html b/Docs/ebcdic_encoding.html index 338951e5a..4ad291a87 100644 --- a/Docs/ebcdic_encoding.html +++ b/Docs/ebcdic_encoding.html @@ -41,7 +41,7 @@ } )(); EBCDIC code pages and mappings files | IBM Z® Open Editor - + @@ -112,6 +112,6 @@ これはテストファイルです。 //* This is a test file. IBM-930エンコーディングを使用しています。 //* Using IBM-930 encoding. - + diff --git a/Docs/editor_codechanges.html b/Docs/editor_codechanges.html index 39ea323b6..4e9383454 100644 --- a/Docs/editor_codechanges.html +++ b/Docs/editor_codechanges.html @@ -41,11 +41,11 @@ } )(); Making COBOL and PL/I code changes | IBM Z® Open Editor - +
IBM Z® Open Editor

Making COBOL and PL/I code changes

IBM Z® Open Editor supports COBOL, PL/I, HLASM, and REXX editing. Select a program, copybook, include, or JCL file in the Explorer to open it in the editor. For HLASM specific details, see Making High Level Assembler code changes. For REXX specific details, see Making REXX code changes.

With the syntax highlighting capability, you can quickly distinguish reserved words, comments, constants, and variables of COBOL, PL/I and HLASM programs. With vertical rulers, which mark different areas, you can better determine the correct areas for comments and the boundaries for coding in areas A and B, and so on.

The editor provides the following features and capabilities:

Browsing code by using the Outline view

As you view the source, you can use the Outline view to efficiently explore and navigate the code of the program. By looking through the items in this view, you can get an idea of what the program does at a high level.

Illustration of using the Outline view

How to use it

You can use the Outline view only after you have opened a file or program. If the Outline view is not already expanded, you can open it by clicking View > Open view > Outline.

You can use this view to:

  • Expand and collapse sections such as Division Headings, Section Headings, and Variable Group Names in the Outline View.
  • Recognize includes, procedures, loops quickly via the icons located by the various items.
  • Go to a wanted location in the code by clicking that section header in the view.
  • Sort by Position, Name, or Type.
  • Search for identifiers within the outline by pressing Ctrl+Shift+O (Windows), or Cmd+Shift+O (Mac) within the Editor window.

When you move your cursor over the program, outline nodes are automatically selected. To toggle this and other features related to the Outline View, hover over the upper right corner of the Outline View. You can see the option ..., where you can click to find multiple options to organize your outline view such as Follow on Cursor, Filter by Type and Sort by Name, Position, and Type.

Code and variable completion suggestion

When you are typing code, code completion suggestion provides you with a matching list from which you can select commands, defined variable and paragraph names, and code snippets.

Illustration of code and variable completion

How to use it

The code completion suggestion is displayed automatically while you are typing or when you press Ctrl+Space (Windows and Mac) depending on your preferences settings.

Hovering for declaration

You can see the working storage definition or DCL definition and the parent group of a variable or paragraph name by moving your mouse cursor over to the variable or paragraph name.

Illustration of hovering for declaration

How to use it

The declaration hover is enabled by default.

Previewing copybooks and include files

You can preview the contents of a copybook or include file by moving your mouse cursor over the copybook name in a COPY statement in COBOL and HLASM, or the include file in a %INCLUDE statement in PL/I and REXX, without having to navigate away from the file you are working in. To open the file in a separate editor, press Ctrl+Click (Windows) or Cmd+Click (Mac).

Illustration of previewing copybooks and include files

How to use it

You must specify the filepath to the copybooks or include files in your ZAPP file property groups to resolve the references. The location can be a local one, such as another directory in your workspace or it can be an MVS data set on a remote z/OS system using Zowe connectivity to find an load the files.

If no filepath is specified or the copybooks or include files are not found in the provided filepath, an error (red squiggle) is shown. To resolve this, follow the instructions provided and our ZAPP overview and Property Groups pages.

Operations on variable and paragraph names

When you double-click a variable or paragraph name to highlight the entire name and then right-click it, you can see the available operations.

How to use it

  • Click Change All Occurrences: Ctrl+F2 (Windows) or Cmd+F2 (Mac)

    When you type the new name, all occurrences are changed simultaneously.

    NOTE: In the scroll bar on the right side of the editor, each occurrence is noted with a location bar.

  • Click Find All References: Alt+Shift+F12 (Windows) or Option+Shift+F12(Mac)

    A Results References view for the variable or paragraph is displayed on the left side of the screen. Click any result to go to that location in the file.

  • Click Peek References: Shift+F12 (Windows and Mac)

    This opens a Results References view in the CodeLens box underneath the variable or paragraph. Click any result to go to that location in the file.

    Illustration of peeking references

  • Click Go to Definition: F12 (Windows and Mac)

    Go to the location where the variable or paragraph is defined. It opens the copybook or include file if applicable.

  • Click Go to Symbol: Ctrl+Shift+O (Windows) or Cmd+Shift+O (Mac)

    When you enter an object name in the search bar or you scroll through the items to select the object, the cursor is moved to that location.

  • Click Peek Definition: Alt+F12 (Windows) or Option+F12 (Mac)

    This opens a CodeLens box that shows where the variable or paragraph was defined in the code. If you use the keyboard shortcut Alt+F12 (Windows) or Option+F12 (Mac), the variable or paragraph name is only clicked once before the keyboard shortcuts are pressed. Double-click any result to go to that location in the file.

    Illustration of peeking definition

  • Click Rename Symbol: F2 (Windows and Mac)

    Rename the selected symbol, and the changes are done in the whole program and copybook or include if it is attached to that symbol.

Syntax checking

The syntax checking feature underlines unrecognized statements and expressions in red, which helps you to make quick corrections and reduce compile errors.

Syntax checking also works for misspelled COBOL, PL/I reserved words and unknown variable names. For HLASM, there are syntax errors for improper spaces in a continuation line and unresolved copy statements.

How to use it

To see all the syntax errors in the open files, open the Problems view through the View menu or by clicking the error and warning icon at the bottom in the status bar. Double-click the list item to directly go to the problem.

Editing double-byte characters

When writing international applications with string constants that contain shift-in/shift-out double-byte characters, Z Open Editor will assist developers in ensuring that the COBOL program lines do not exceed the maximum line length configured for the editor.

It will do that in two ways:

  1. Any sets of characters that take up more than one byte will be automatically visualized in the editor with special guillemets (« ») annotations. These annotations only help you to identify the characters. They are not actual characters of the program and will not be stored with it. Also, when you copy and paste the text to another editor, they will not be added to the clipboard.
  2. When you start typing such characters, the status bar will automatically start displaying a Byte Count entry that shows you how many bytes you have left before reaching the maximum line length.

Editing strings with double-byte characters

Also review EBCDIC code pages and mappings files with examples for converting double-byte characters from EBCDIC to UTF-8 and vice versa when working with files from z/OS MVS and UNIX System Services.

Undoing and redoing

Undo your changes by pressing Ctrl+Z (Windows) or Cmd+Z (Mac). Redo your changes by pressing Ctrl+Shift+Z (Windows) or Cmd+Shift+Z (Mac).

Renumbering and unnumbering sequence numbers

The Renumber/Unnumber function applies only to COBOL and will renumber the lines in the COBOL file. There is an option in preferences to control which columns will have sequence numbers inserted and removed. The user selects either columns 1-6, 73-80, or both. The numbering will start with 100 and increment each line by 100 while preserving non-numeric markers. This function equates to turning on the number mode in ISPF.

The COBOL Unnumber function will remove the line numbering in either columns 1-6, 73-80, or both while preserving non-numeric markers. This function equates to turning off the number mode in ISPF.

How to use it

To configure the preferences in the Z Open Editor Settings for which columns you would like to renumber and unnumber, modify your settings as follows.

  1. Open your settings:

    • Windows: File > Preferences > Settings
    • Mac: Code > Preferences > Settings

  2. In the left side of the opened Settings interface, expand Extensions from the list of categories, and click IBM Z Open Editor. In the IBM Z Open Editor settings, under COBOL: Sequence Numbers, click the dropdown menu to select a preference.

  3. Click the appropriate option to specify the location of sequence numbers that are inserted and removed from a file by the Renumber and Unnumber editor actions. The options are as follows.

    • column-1: The sequence numbering begins at column 1, and will fill columns 1-6.
    • column-73: The sequence numbering begins at column 73, and will fill columns 73-80.
    • column-1-and-73: The sequence numbering begins at column 1 and 73, and will fill columns 1-6 and 73-80.

To number or renumber a COBOL file, right-click in the file in the editor and select the Renumber Sequence Numbers command. To unnumber the COBOL file, right-click in file in the editor and select the Unnumber Sequence Numbers command.

Commenting and uncommenting COBOL code

You can comment and uncomment COBOL code by using the keyboard shortcut. This method works for both single-line comments and multi-line block comments.

How to use it

To comment COBOL code:

  1. In a COBOL file, place your cursor where you want to add a single-line comment, or click and select the code or text where you want to comment out a code block.
  2. Press Ctrl+/ (Windows) or Cmd+/ (Mac).

To uncomment COBOL code:

  1. Select the code that is currently commented out.
  2. Press Ctrl+/ (Windows) or Cmd+/ (Mac).

COBOL Code Folding

Code folding is a feature that allows users to show or hide logical sections of the COBOL source code, which makes it easier for users to focus on the code they are working on. Logical sections of COBOL source code include but not limited to DIVISION, SECTION, PARAGRAPH, IF, ELSE, WHEN, DO, DATA-ITEMS, and EXEC SQL/CICS statements.

How to use it

You can fold regions of COBOL source code using the folding icons in the gutter between the line numbers and line start. Move the mouse over the gutter and click to fold and unfold regions. Use Shift + Click on the folding icon to fold or unfold the region and all regions inside. For more detailed information about code folding, refer to the VS Code code folding documentationopen in new window.

COBOL Code Folding Example

PL/I Code Folding

Code folding is a feature that allows users to show or hide logical sections of the PL/I source code which makes it easier for users to focus on the code they are working on. Logical sections of PL/I source code include IF, ELSE, DO, SELECT, WHEN, OTHERWISE, PACKAGE, BEGIN, PROCEDURE and ON blocks.

How to use it

You can fold regions of PL/I source code using the folding icons in the gutter between the line numbers and line start. Move the mouse over the gutter and click to fold and unfold regions. Use Shift + Click on the folding icon to fold or unfold the region and all regions inside. For more detailed information about code folding, refer to the VS Code code folding documentationopen in new window.

PL/I Code Folding Example

Commenting and uncommenting PL/I code

You can comment out one or multiple selected lines of code or a selected section of code by using the toggle comment function.

How to use it

To toggle comment for one or multiple selected lines of code, press Cmd+/ (Mac) or Ctrl+/ (Windows), or go to Edit > Toggle Line Comment.

To toggle comments for a selected section of code, press Option+Shift+A (Mac) or Alt+Shift+A (Windows), or go to Edit > Toggle Block Comment.

See the following example where we first toggle line comment on multiple selected lines, then toggle line comment on a single line, and finally toggle block comment on a selection:

pli toggle comment

Last Updated:
Contributors: Lauren Li, Prabhjeet Kaur, Shi Kun Li, Greg Lambert, Saile, PrasangAPrajapati, Keng-Hui Beall, Min Huang, Peter Haumer, Saile Daimwood, Chun Hong Zheng, Hestia Zhang, PETER HAUMER, Peter Haumer, kmaselli, Benjamin Santos, Bradley Knaysi, Prasang-A-Prajapati
- + diff --git a/Docs/editor_codechanges_hlasm.html b/Docs/editor_codechanges_hlasm.html index bd642f513..6d86ac214 100644 --- a/Docs/editor_codechanges_hlasm.html +++ b/Docs/editor_codechanges_hlasm.html @@ -41,11 +41,11 @@ } )(); Making High Level Assembler code changes | IBM Z® Open Editor - +
IBM Z® Open Editor

Making High Level Assembler code changes

In addition to COBOL and PL/I, IBM Z® Open Editor supports IBM Z High Level Assembler (HLASM) editing. You can use the following features to program in HLASM effectively.

With the syntax highlighting capability, you can quickly distinguish between labels, operations, operands, and comments in a HLASM program. With vertical rulers, which mark different areas, you can better determine correct areas for symbols, operations, operands, continuation line indicators, and sequence numbers.

The editor provides the following features and capabilities:

Browsing code by using the Outline view

You can use the Outline view to efficiently explore and browse the source code of a program. By looking through the items in this view, you can get an idea of what the program does at a high level and easily go to key instructions, branch labels, and symbols. We purposely chose not to include every symbol, because in large assembler programs, the Outline view often becomes extremely cluttered. For more information, see Customizing the Outline view.

HLASM Outline

How to use it

You can use the Outline view only after you have opened a file or program. If the Outline view is not expanded, you can open it by clicking View > Open view > Outline.

You can use this view to:

  • Recognize the following instructions quickly through the icons:
    • CSECT
    • DSECT
    • RSECT
    • COM
    • LOCTR
    • MACRO
  • Identify the following unique icons:
    • All labels used in a branch instruction
    • All labels, if enabled
  • Go to a location that you want in the code by clicking that section header in the view.
  • Sort by Position, Name, or Type.
  • Search for identifiers by pressing Ctrl+Shift+O on Windows or Cmd+Shift+O on Mac in the Editor window.

When you move your cursor over the program, outline nodes are automatically selected. To toggle this and other features related to the Outline View, hover over the upper-right corner of the Outline view. You can see the option ..., where you can click to find multiple options to organize your outline view such as Follow on Cursor, Filter by Type and Sort by Name, Position, and Type. To filter which icons to display in the Outline view, see Customizing the Outline view.

Code completion

When you are typing in an HLASM program, code completion provides you with a list from which you can select operations or labels depending on the current context. Currently, code completion for symbols works for symbols defined in the current file and copied files. Code completion for operations works for default (SYS1.MACLIB) macros, macros defined in the current file, and local custom macros.

When using code completion for instructions that have operands as well as macros with parameters, the HLASM language server will provide a snippet-style completion text that allows the user to use the tab key to modify and complete the operands or parameters as needed. See the following examples of operation and macro code completion.

Code completion While Typing

Code completion macro

How to use it

The code completion suggestion is displayed automatically while you are typing in an appropriate context.

Hovering for declaration

You can see hovers for operations and operands by moving your mouse cursor over the operation or operand.

HLASM Hover

How to use it

Operation and operand hovers are enabled by default. Simply move your mouse over an operation or operand. If the operand or operation is defined, a hover will appear.

Previewing copybooks

To preview the contents of a COPY statement move your mouse cursor over the copybook name. If the copybook cannot be resolved, a red error underline will appear on the copybook name. To open the file in a separate editor, press Ctrl+Click (Windows) or Cmd+Click (Mac).

HLASM Copy File Preview

How to use it

To resolve copybooks, you must specify the filepath to the copybooks or include files in your ZAPP file property groups to resolve the references. The location can be a local one, such as another directory in your workspace, or it can be an MVS data set on a remote z/OS system using Zowe connectivity to find an load the files.

If no filepath is specified the include files are not found in the provided filepath, an error (red squiggle) is shown. To resolve this, follow the instructions provided and our ZAPP overview and Property Groups pages.

Operations on symbols

When you double-click a symbol to highlight the entire name and then right-click it, you can see the available operations.

How to use it

  • Click Change All Occurrences: Ctrl+F2 (Windows) or Cmd+F2 (Mac)

    When you type the new name, all occurrences are changed simultaneously.

    NOTE: In the scroll bar on the right side of the editor, each occurrence is noted with a location bar.

  • Click Find All References: Alt+Shift+F12 (Windows) or Option+Shift+F12(Mac)

    A Results References view for the variable or paragraph is displayed on the left side of the screen. Click any result to go to that location in the file.

  • Click Peek References: Shift+F12 (Windows and Mac)

    This opens a Results References view in the CodeLens box underneath the variable or paragraph. Click any result to go to that location in the file.

    HLASM PEEK REFERENCES

  • Click Go to Definition: F12 (Windows and Mac)

    Go to the location where the variable or paragraph is defined. It opens the copybook or include file if applicable.

  • Click Go to Symbol: Ctrl+Shift+O (Windows) or Cmd+Shift+O (Mac)

    When you enter an object name in the search bar or you scroll through the items to select the object, the cursor is moved to that location.

  • Click Peek Definition: Alt+F12 (Windows) or Option+F12 (Mac)

    This opens a CodeLens box that shows where the variable or paragraph was defined in the code. If you use the keyboard shortcut Alt+F12 (Windows) or Option+F12 (Mac), the variable or paragraph name is only clicked once before the keyboard shortcuts are pressed. Double-click any result to go to that location in the file.

    HLASM PEEK DEFINITION

Remote macros

Macros in SYS1.MACLIB are available for code completion. In addition, if you configured Zowe Explorer to a z/OS MVS system that has a SYS1.MACLIB data set with a valid user z/OSMF or RSE API profile, you can preview remote macros in rich hovers. The tools will follow the same rules as for include file resolution, although no property groups need to be defined.

HLASM REMOTE MACRO

To enable the automatic lookup with your default Zowe CLI profile, go to Preferences > Settings, expand Extensions > IBM Z Open Editor and check the option Hlasm: Enable Resolving Macros. Additionally, you can adjust the lookup to use the z/OS 2.4, 2.5, or 3.1 version of SYS1.MACLIB using Hlasm: Zos Macros Version. This will ensure proper hover and code completion support for the macro set that you are using. See Setting preferences for more details on managing preferences.

If you do not have any connectivity, we recommend keeping this feature switched off; otherwise the editor will continue trying to resolve the file via your Zowe CLI profile.

If you want to use a different Zowe CLI profile than the default RSE API or z/OSMF profiles, specify the name of a different profile in the "zopeneditor.zowe" user setting. See the details in Setting up and using RSE profiles in IBM Z Open Editor.

Syntax checking

The syntax checking feature underlines unrecognized statements and expressions in red, which helps you to make quick corrections and reduce compile errors. Currently, there are syntax errors for improper spaces in a continuation line, unresolved copy statements, and an invalid number of operands.

How to use it

To see all the syntax errors in the open files, open the Problems view through the View menu or by clicking the error and warning icon at the bottom in the status bar. Double-click the list item to directly go to the problem.

  • Invalid number of operands

    This syntax error is currently supported for all machine instructions. Assembler instructions and macros are not currently supported.

Undoing and redoing

Undo your changes by pressing Ctrl+Z (Windows) or Cmd+Z (Mac). Redo your changes by pressing Ctrl+Shift+Z (Windows) or Cmd+Shift+Z (Mac).

Commenting and uncommenting HLASM code

You can comment and uncomment HLASM code by using the keyboard shortcut. This method works for both single-line comments and multi-line block comments.

How to use it

To comment HLASM code:

  1. In an HLASM file, place your cursor where you want to add a single-line comment, or click and select the code or text where you want to comment out a code block.
  2. Press Ctrl+/ (Windows) or Cmd+/ (Mac).

To uncomment HLASM code:

  1. Select the code that is currently commented out.
  2. Press Ctrl+/ (Windows) or Cmd+/ (Mac).
Last Updated:
Contributors: Saile Daimwood, Peter Haumer, Chun Hong Zheng, Keng-Hui Beall, Peter Haumer, Saile, kdbeall, Keng-Hui D Beall, Min Huang, PETER HAUMER, Shi Kun Li
- + diff --git a/Docs/editor_codechanges_jcl.html b/Docs/editor_codechanges_jcl.html index fdf308fe8..ebe6f658d 100644 --- a/Docs/editor_codechanges_jcl.html +++ b/Docs/editor_codechanges_jcl.html @@ -41,11 +41,11 @@ } )(); Making JCL code changes | IBM Z® Open Editor - +
IBM Z® Open Editor

Making JCL code changes

In addition to COBOL, PL/I, REXX, and High Level Assembler (HLASM), IBM Z® Open Editor supports z/OS MVS JCL editing. You can use the following features to edit JCL programs effectively.

With the syntax highlighting capability, you can quickly distinguish the comments, job, step (exec) and DD statements in a JCL program.

The editor provides the following features and capabilities:

Browsing code by using the Outline view

As you view the source, you can use the Outline view to efficiently explore and navigate the code of the program. By looking through the items in this view, you can see the Jobs, Steps, DD statements and directly navigate to one by selecting it.

JCL Outline

How to use it

You can use the Outline view only after you have opened a file or program. If the Outline view is not already expanded, you can open it by clicking View > Open view > Outline.

You can use this view to:

  • Recognize internal routines quickly via the icons in the outline view.
  • Go to a wanted location in the code by clicking the section header in the view.
  • Sort by Position or Name.
  • Search for identifiers within the outline by pressing Ctrl+Shift+O (Windows), or Cmd+Shift+O (Mac) within the Editor window.
  • Select the entire step/job/DD statement by double clicking on the symbol in the outline view.

When you move your cursor over the program, outline nodes are automatically selected. To toggle this and other features related to the Outline View, hover over the upper right corner of the Outline View. You can see the option ..., where you can click to find multiple options to organize your outline view such as Follow on Cursor, Filter by Type and Sort by Name, Position, and Type.

Code completion

The code completion feature suggests simple symbols, constant symbols, jobs, steps, DD statements, keyword instructions, and built-in functions. The editor applies a suggestion to the file based on the context of the cursor position. For a cursor position inside a stem, the suggestion replaces the entire symbol. For a cursor position inside the tail of a compound symbol, the suggestion replaces a segment of the symbol. The casing of the suggestion replaces the casing of the symbol in the file. The code completion suggestions are not filtered by case.

Code Completion

How to use it

The code completion suggestion is displayed automatically while you are typing outside of any comments or strings.

Syntax checking

The syntax checking feature underlines unrecognized statements and expressions in red, which helps you to make quick corrections and reduce compile errors.

How to use it

To see all the syntax errors in the open files, open the Problems view through the View menu or by clicking the error and warning icon in the status bar. Double-click the list item to directly go to the problem.

JCL Code Folding

Code folding is a feature that allows users to show or hide logical sections of the JCL source code, which makes it easier for users to focus on the code they are working on. Logical sections of JCL source code includes JOB, EXEC, and DD statements.

How to use it

You can fold regions of COBOL source code using the folding icons in the gutter between the line numbers and line start. Move the mouse over the gutter and click to fold and unfold regions. Use Shift + Click on the folding icon to fold or unfold the region and all regions inside. For more detailed information about code folding, refer to the VS Code code folding documentationopen in new window.

JCL Code Folding Example

Undoing and redoing

Undo your changes by pressing Ctrl+Z (Windows) or Cmd+Z (Mac). Redo your changes by pressing Ctrl+Shift+Z (Windows) or Cmd+Shift+Z (Mac).

Commenting and uncommenting JCL code

You can comment out one or multiple selected lines of code or a selected section of code by using the toggle comment function.

How to use it

To toggle comment for one or multiple selected lines of code, press Cmd+/ (Mac) or Ctrl+/ (Windows), or go to Edit > Toggle Line Comment.

To toggle comments for a selected section of code, press Option+Shift+A (Mac) or Alt+Shift+A (Windows), or go to Edit > Toggle Block Comment.

See the following example where we first toggle line comment on a single line, then toggle line comment on multiple selected lines, and finally toggle block comment on a selection:

jcl toggle comment

Last Updated:
Contributors: Prasang Prajapati, Prasang-A-Prajapati, Saile Daimwood
- + diff --git a/Docs/editor_codechanges_rexx.html b/Docs/editor_codechanges_rexx.html index 20c42496f..68d9f2541 100644 --- a/Docs/editor_codechanges_rexx.html +++ b/Docs/editor_codechanges_rexx.html @@ -41,11 +41,11 @@ } )(); Making REXX code changes | IBM Z® Open Editor - +
IBM Z® Open Editor

Making REXX code changes

In addition to COBOL, PL/I, and High Level Assembler (HLASM), IBM Z® Open Editor supports TSO/E REXX editing. You can use the following features to edit REXX programs effectively.

With the syntax highlighting capability, you can quickly distinguish the comments, strings, constants, variables, keywords, labels, functions, comparison, and arithmetic in a REXX program.

The editor provides the following features and capabilities:

Browsing code by using the Outline view

As you view the source, you can use the Outline view to efficiently explore and navigate the code of the program. By looking through the items in this view, you can see the internal routines, and directly navigate to one by selecting it.

REXX Outline

How to use it

You can use the Outline view only after you have opened a file or program. If the Outline view is not already expanded, you can open it by clicking View > Open view > Outline.

You can use this view to:

  • Recognize internal routines quickly via the icons in the outline view.
  • Go to a wanted location in the code by clicking that section header in the view.
  • Sort by Position or Name.
  • Search for identifiers within the outline by pressing Ctrl+Shift+O (Windows), or Cmd+Shift+O (Mac) within the Editor window.

When you move your cursor over the program, outline nodes are automatically selected. To toggle this and other features related to the Outline View, hover over the upper right corner of the Outline View. You can see the option ..., where you can click to find multiple options to organize your outline view such as Follow on Cursor, Filter by Type and Sort by Name, Position, and Type.

Code completion

The code completion feature suggests simple symbols, constant symbols, compound symbols, stems, function calls, keyword instructions, and built-in functions. The editor applies a suggestion to the file based on the context of the cursor position. For a cursor position inside a stem, the suggestion replaces the entire symbol. For a cursor position inside the tail of a compound symbol, the suggestion replaces a segment of the symbol. The casing of the suggestion replaces the casing of the symbol in the file. The code completion suggestions are not filtered by case.

Code Completion

How to use it

The code completion suggestion is displayed automatically while you are typing outside of any comments or strings.

Hovering for declaration

The hover feature provides rich information about keyword instructions and built-in functions. By moving your cursor over these elements, a small pop-up window is displayed containing a title, description, and example usage.

REXX Hover

How to use it

You can see hovers for keyword instructions and built-in functions by moving your cursor over the element. The hover disappears when your cursor moves elsewhere.

Previewing include control directives

To preview the contents of a %INCLUDE statement, point to the file name. If the file cannot be resolved, a red warning underline will appear on the file name. To open the file in a separate editor, press Ctrl and click (on Windows), or press Cmd and click (on Mac).

REXX INCLUDE File Preview

How to use it

To resolve include files, you must specify the filepath to the include files in your ZAPP file property groups to resolve the references. The location can be a local one such as another directory in your workspace, or it can be an MVS data set on a remote z/OS system using Zowe connectivity to find and load the files.

If no filepath is specified, the include files are not found in the provided filepath and an error is shown. To resolve this, follow the instructions provided and our ZAPP overview and Property Groups pages.

Operations on symbols

By right clicking on a symbol, you can see a list of available operations.

How to use it

  • Click Find All References: Alt+Shift+F12 (Windows) or Option+Shift+F12(Mac)
  • Click Peek References: Shift+F12 (Windows and Mac)

A reference is defined as any matching symbol not in a comment or string. Keywords and built-in functions do not appear as references. The matches are determined by the context of the symbol. Internal routines match to their calls. Stems match to other stems. Simple symbols match to other simple symbols. Constant symbols match to other constant symbols. For compound symbols, the tail is broken into separate pieces, delimited by its periods, and matched to other constant or simple symbols. Additionally, the derivation and scope of a symbol is not considered.

REXX PEEK REFERENCES

Syntax checking

The syntax checking feature underlines unrecognized statements and expressions in red, which helps you to make quick corrections and reduce compile errors.

How to use it

To see all the syntax errors in the open files, open the Problems view through the View menu or by clicking the error and warning icon at the bottom in the status bar. Double-click the list item to directly go to the problem.

Undoing and redoing

Undo your changes by pressing Ctrl+Z (Windows) or Cmd+Z (Mac). Redo your changes by pressing Ctrl+Shift+Z (Windows) or Cmd+Shift+Z (Mac).

Commenting and uncommenting REXX code

You can comment out one or multiple selected lines of code or a selected section of code by using the toggle comment function.

How to use it

To toggle comment for one or multiple selected lines of code, press Cmd+/ (Mac) or Ctrl+/ (Windows), or go to Edit > Toggle Line Comment.

To toggle comments for a selected section of code, press Option+Shift+A (Mac) or Alt+Shift+A (Windows), or go to Edit > Toggle Block Comment.

See the following example where we first toggle line comment on a single line, then toggle line comment on multiple selected lines, and finally toggle block comment on a selection:

rexx toggle comment

Last Updated:
Contributors: Bradley Knaysi, Greg Lambert, Saile Daimwood, Chun Hong Zheng, Peter Haumer
- + diff --git a/Docs/editor_search.html b/Docs/editor_search.html index c40e856da..3caf47ead 100644 --- a/Docs/editor_search.html +++ b/Docs/editor_search.html @@ -41,11 +41,11 @@ } )(); Searching for COBOL, PL/I, HLASM, and REXX components | IBM Z® Open Editor - +
IBM Z® Open Editor

Searching for COBOL, PL/I, HLASM, and REXX components

You can search for strings and regular expressions across all files or a specific subset of files based on location or name patterns by using the Search view. The Search view also enables you to preview side by side how each change would look like, giving you the option to perform and reject each change one by one, or all at once.

Take the sample files as an example. To search for components that generate and reference the "Daily Customer File Update" in the example program, take the following steps:

  1. Right-click the Explorer, and select Find in Folder....

  2. Enter the search term CUSTOMER-FILE and press the Return key.

    • Review some of the other search options such as using regular expressions and specifying patterns for files and folders to be excluded or included in the search.
    • To perform a regular expression search, select the .* icon and change the search term to CUST.*FILE and review the results.

  3. Results will appear in the Search Panel.

    • Clicking on the result will allow you to navigate to that location file in the Editor panel.

  4. (Optional) Perform a second search for the CRUNCH transaction to determine the affected components.

Last Updated:
Contributors: Greg Lambert, Lauren Li, Min Huang, Peter Haumer, Shi Kun Li
- + diff --git a/Docs/getting_started.html b/Docs/getting_started.html index cfa04c1d4..3955a6506 100644 --- a/Docs/getting_started.html +++ b/Docs/getting_started.html @@ -41,7 +41,7 @@ } )(); Getting started with IBM Z Open Editor | IBM Z® Open Editor - + @@ -49,6 +49,6 @@

On Windows:

"zopeneditor.JAVA_HOME": "C:\\Program Files\\Java\\jdk11.0.15+10"

Configuring the Java memory allocation

By default, the language server client that starts the individual language servers for COBOL, PL/I, HLASM, or REXX allocates a maximum of 512 MB of memory for each. The language servers will consume much less memory at startup, and then allocate and free memory when parsing programs. However, they might run out of memory when parsing very large program files and reach the predefined limit. To allow allocating more memory, use the following VS Code setting to specify a new maximum value:

"zopeneditor.server.memoryAllocation": 640

Keep in mind that this value is for each language you use, so when using both COBOL and PL/I, you might end up with a consumption of double the amount specified. If you are working with smaller programs or your computer might not support such a large amount of memory, you can also try values smaller than 512 with this setting.

Using IBM Z Open Editor in cloud-based editors

Z Open Editor can be installed and used with various cloud or browser-based editing environments that utilize VS Code as the editor. We list a couple of examples that we test with, but there might be more configurations that the editor would also work in.

Red Hat Dev Spaces for OpenShift

Our recommended cloud-based development environment is Red Hat OpenShift Dev Spaces that provides a cloud-based development environment that is fully integrated into Red Hat OpenShift. In fact, we have created a customized version of Dev Spaces for z/OS development called IBM Wazi for Dev Spaces that adds Z Open Editor, Z Open Debug as well as many additional zDevOps tools into one convenient solution package that can be easily deployed with an OpenShift operator and used with your z/OS LPARs as well as Wazi as a Serviceopen in new window cloud-based z/OS server instances, or emulated Wazi Sandbox z/OS instances. Wazi for Dev Spaces is part of the IBM Z and Cloud Modernization Stackopen in new window product offering.

To try Z Open Editor for free in Red Hat OpenShift Dev Spaces, you can sign up for a 30-day trial of the OpenShift Sandbox and Red Hat Developer Sandboxopen in new window. We have a full tutorial for signing up and using Z Open Editor hereopen in new window.

You can also try Wazi for Dev Spaces as part of a Wazi as a Service trial as documented hereopen in new window. For this we also provide a detailed tutorial in our new IBM Redbook "Hybrid Cloud with IBM Zopen in new window", Chapter 5.

GitPod

GitPodopen in new window is a cloud-based IDE offering by the GitPod company that can also utilize VS Code as the browser-based editor and integrate with all the major Git service providers such as GitLab, GitHub, and Bitbucket. After you sign in with an account from either of these Git services, you can easily start a workspace with Z Open Editor.

To try it out with our code samples repository, use this link https://gitpod.io/#https://github.com/phaumer/zopeneditor-sampleopen in new window. The workspace will start up and load a custom image prepared by our team that even contains Zowe CLI and Ansible CLI. After the editor is up, you might have to click F1 and select the command View: Focus Activity Bar to bring in the sidebar that allows you to find our sample programs. Z Open Editor was automatically installed for this workspace, so you can just open a program and start editing. Note that this is a paid-for service, but the first hours are free.

GitHub Codespaces

Z Open Editor can also be used with all of its capabilities in Microsoft's GitHub Codespacesopen in new window. After your start your development environment in Codespaces, you can find and install Z Open Editor from the integrated marketplace. You can also use extension recommendations.

Try it by using this link https://github.com/codespaces/new?machine=basicLinux32gb&repo=160883618&ref=wazi-main&location=WestUs2open in new window that loads our Z Open Editor sample repository. After the editor is up, click Install in the dialog that asks "Do you want to install the recommended extensions for this repository?". Note that this is a paid-for service, but the first hours are free.

Pure web-based editing in vscode.dev and github.dev

Z Open Editor can be used as a pure web extension with limited capabilities when using Visual Studio Code in a browser, such as on vscode.devopen in new window or github.devopen in new window.

Try it by going to https://vscode.dev/github/IBM/zopeneditor-sampleopen in new window and confirming in the dialog to install the recommended extensions by clicking Install. No language server capabilities will be available, but syntax highlighting for all our supported languages.

- + diff --git a/Docs/git_integration.html b/Docs/git_integration.html index 06958110c..d52850517 100644 --- a/Docs/git_integration.html +++ b/Docs/git_integration.html @@ -41,11 +41,11 @@ } )(); Using the integrated Git | IBM Z® Open Editor - +
IBM Z® Open Editor

Using the integrated Git

Prerequisites

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 https://git-scm.comopen in new window.

Creating Git branches

To manage your codes for parallel development, you can create a new branch using the integrated Git. To create a new Git branch:

  1. Select the branch icon at the lower left of the browser page in the colored status bar. A drop-down box at the top of the browser page appears with various options.
  2. Select the branch icon at the bottom again and then Create new branch....
  3. Enter the name of the new branch.

Committing changes into Git branches

After making code changes and refinements, you can commit changed files to the Git repository.

To commit changed files:

  1. Open the Git view by clicking View > Git, or pressing Ctrl+Shift+G (Windows and Mac), which lists all the files that you added or modified.

  2. To review changes to a changed file that is marked by the M, double-click the file to open a diff editor view.

  3. Take one of the following actions:

    • Open the file.
    • Discard changes.
    • Add your file for the next commit that is called Staging by clicking the + icon to stage it.

  4. Provide a short description in the Commit message text box at the top, such as Implemented Update Report.

  5. Make sure that the branch you want to commit to is selected at the bottom of the browser page.

  6. Click Commit on the top of the Git view. The list of files is empty now as all changes were committed to the branch.

You can review these changes in the Git History viewer after completing the commit.

For more information about using Git, see VS Code documentationopen in new window.

Last Updated:
Contributors: Peter Haumer, Shi Kun Li
- + diff --git a/Docs/interact_common_properties_cli.html b/Docs/interact_common_properties_cli.html index 43b1b909e..6094e7c9d 100644 --- a/Docs/interact_common_properties_cli.html +++ b/Docs/interact_common_properties_cli.html @@ -41,7 +41,7 @@ } )(); Interact with RSE Common Properties | IBM Z® Open Editor - + @@ -75,6 +75,6 @@ Property deleted successfully.

There are other commands to list, copy, rename, and delete namespace. You can check common-properties command help for a complete list of common-properties commands.

% zowe rse common-properties --help
- + diff --git a/Docs/interact_zos_cli.html b/Docs/interact_zos_cli.html index bba484508..7c15beada 100644 --- a/Docs/interact_zos_cli.html +++ b/Docs/interact_zos_cli.html @@ -41,7 +41,7 @@ } )(); Using command line to interact with z/OS | IBM Z® Open Editor - + @@ -122,6 +122,6 @@

  • Download members:

    zowe files download ds "USER1.SAMPLE.COBOL(SAM1)"

    You will see that new folders appear on the left with the names based on your data set that contains the file SAM1. You can rename it by adding a .cbl extension to edit it in the COBOL editor, and then upload it later using drag-and-drop or via the command line.

  • Check the status of your jobs:

    zowe jobs ls js | grep ACTIVE

    The preceding command shows an example of how Zowe CLI commands can be used in combination with other Linux commands and scripts. This example returns the complete list of jobs and pipes that list into the Linux grep command to filter it down to show only the active jobs. This kind of capability enables you to define all kinds of batch jobs and automation for remotely interacting with z/OS.

    • For an overview of available Zowe CLI commands, type zowe --help.

    To learn about all the capabilities of Zowe CLI, see Zowe CLI Online Documentationopen in new window.

    - + diff --git a/Docs/interact_zos_overview.html b/Docs/interact_zos_overview.html index 6909fbb55..d77e0c17c 100644 --- a/Docs/interact_zos_overview.html +++ b/Docs/interact_zos_overview.html @@ -41,11 +41,11 @@ } )(); Interacting with z/OS | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Interacting with z/OS

    In VS Code, you can interact with z/OS in the Terminal window by using commands provided by IBM RSE API plug-in for Zowe CLI (RSE CLI plug-in), Zowe CLI, or both. For more information about their differences, see Comparison between Zowe CLI and RSE CLI plug-in.

    Additionally, you can graphically navigate and access file and job resources on z/OS by using the Zowe Explorer VS Code extension. It is recommended to use Zowe Explorer, with which you can edit COBOL, PL/I, and HLASM files that are opened on z/OS MVS™ and z/OS UNIX System Services, and run JCL and browse job spool files.

    After you choose and install the prerequisites according to Setting up integrations to interact with z/OS, refer to the following usage instructions:

    Available host componentTo use command line, see...To use graphical interface, see...
    RSE APIUsing RSE CLI plug-in commandsUsing RSE API in Zowe Explorer and Using Zowe Explorer views
    z/OSMFUsing Zowe CLI z/OSMF commandsWorking with Zowe Explorer profilesopen in new window and Using Zowe Explorer views

    See Supported methods of authentication.

    Last Updated:
    Contributors: Shi Kun Li, KRISTINA MAYO, Billie Simmons, Chun Hong Zheng, Peter Haumer
    - + diff --git a/Docs/interact_zos_zopeneditor.html b/Docs/interact_zos_zopeneditor.html index df70b2f20..6e985bca5 100644 --- a/Docs/interact_zos_zopeneditor.html +++ b/Docs/interact_zos_zopeneditor.html @@ -41,7 +41,7 @@ } )(); Using Zowe profiles in Z Open Editor | IBM Z® Open Editor - + @@ -53,6 +53,6 @@ "defaultRseConversionMappingsFile": "~/wazi-sample/zapp.yaml" }

    These settings can also be edited by using this table in the graphical Settings editor:

    VS Code Settings editor for zopeneditor.zowe

    Changing the Zowe Profile using status bar button

    If no profile is specified in the settings, the default Zowe CLI profile is used by Z Open Editor in the VS Code status bar. You can find the name and type of the currently active Zowe CLI profile in the lower right of the editor window.

    'zowe-no-prof-status''zowe-rse-status'

    Hover over the status bar item for the Zowe profile to see information about the setting, and click the item to view a menu of options. These options are determined by the profile type that is selected when clicking the button. All profile types will show the options to change the Zowe CLI profile used by Z Open Editor.

    When choosing a z/OSMF profile for the defaultZoweCli, the user will also see the option to choose the accompanying SSH profile that is needed for some Z Open Editor actions along-side the z/OSMF profile.

    RSE profiles also have the option to change their password on the host for the profile. This option not only makes the change on the host side. If the host request is successful, it will update the credentials on the client side as well.

    'profile-management-options'

    When changing the RSE profile password on the host, the user will be prompted for their original user ID and password for authentication purposes.

    - + diff --git a/Docs/interact_zos_zowe_explorer.html b/Docs/interact_zos_zowe_explorer.html index 73dc6a10d..66892e0e2 100644 --- a/Docs/interact_zos_zowe_explorer.html +++ b/Docs/interact_zos_zowe_explorer.html @@ -41,7 +41,7 @@ } )(); Using the Zowe Explorer views | IBM Z® Open Editor - + @@ -51,6 +51,6 @@

    The value of defaultCliProfile is the name of the CLI profile that you specified in the create statement above.

    If you have v2 profiles in place and cannot remember the names, then you can run this command to get the information of all your profiles in the team configuration file:

    zowe config list

    If you have v1 profiles in place and cannot remember the names, then you can run this command to get the list of all your profiles and your default profile:

    zowe profiles list rse

    As we only use the profile name to find a profile, we require that you use unique names for profiles of different types. In other words, if you use the same name for your RSE API and z/OSMF profile, then the RSE API profile will always be picked if that name is used in the settings. If you want to switch between z/OSMF and RSE API profiles, you must use unique names.

    Using Zowe Explorer views to interact with z/OS

    When you connect to the host with either a z/OSMF profile or an RSE profile, you can view a tree list of data sets, members in the DATA SETS view, z/OS UNIX System Services files and directories in the UNIX SYSTEM SERVICES (USS) view, and jobs with spool files in the JOBS view.

    In the three views provided by Zowe Explorer, you can perform the following tasks:

    Example: How to manipulate data sets with Zowe Explorer

    When you are connected to Zowe with a z/OSMF profile or an RSE profile, you can work with your COBOL, PL/I, and HLASM data sets in Zowe Explorer.

    Switch to Zowe Explorer to see the DATA SETS view by clicking the Zowe icon on the Activity bar. If the DATA SETS view is not opened by default, right-click one of the headers, and select the checkbox Data Sets.

    Prerequisite: Before working on your data sets, you must connect to the Zowe server by expanding the node in the explorer that has the name of the connection profile you created. A list of existing profiles is shown.

    Creating data sets

    The data set is created with the parameters defined in the User Preferences. To create a data set, complete the following steps:

    1. Right-click on the preferred profile name and select Create New Data Set from the context menu.

    2. Provide a name such as USER1.SAMPLE.COBOL, replacing USER1 with the High Level Qualifier that should be used for the new data set. Then, press Enter to continue.

    3. Select one option from the menu such as Data Set Binary, Data Set C, Data Set Classic, Data Set Partitioned, Data Set Sequential.

    4. To allocate the data set with default attributes, press Enter or select Allocate Data Set. Alternatively, you can customize the new data set's attributes by clicking Edit Attributes.

    5. A new data set appears in the DATA SETS view. You might need to refresh the browser to see the new data set.

    Creating new data set members

    1. Right-click the PDS and select Create New Member.
    2. Provide a name for the new member and press Enter.
    3. Expand the PDS to see the new member.

    Migrating and recalling data sets

    To migrate a data set, right-click a data set and select Migrate Data Set. An informational message then appears stating Migration of dataset: USER1.SAMPLE.COBOL requested..

    To recall a data set, right-click a data set that has been migrated and select Recall Data Set. An informational message then appears stating Recall of dataset: USER1.SAMPLE.COBOL requested..

    You can verify the status with either of the following ways:

    Note: If the data set migration or recall does not work, contact your system administrator to ensure HSM is active on the host system.

    Deleting data sets or data set members

    1. Right-click the data set or member to delete.
    2. Select Delete from the context menu. A confirmation dialog appears and lists the item(s) you selected for deletion.
    3. Click Delete to confirm that you want to delete the listed item(s), or click Cancel to cancel the deletion.

    Adding or removing favorites

    1. Right-click a resource, for example, a data set, folder, job, or profile.
    2. Select Add to Favorites or Remove Favorite to add to or remove from the Favorites tree.

    Example: How to search for jobs in Zowe Explorer

    In the JOBS view of Zowe Explorer, you can query the jobs that you are interested in. You can filter job lists based on various combinations of criteria such as job owner, a job prefix sub-string, as well as values for job status such as Active, Input, or Output.

    To search for jobs in the JOBS view:

    1. Switch to Zowe Explorer to see the JOBS view by clicking the Zowe icon on the Activity bar. If the JOBS view is not opened by default, right-click one of the headers, and then select the JOBS checkbox.
    2. Click the Search Jobs icon on the profile that you want.
    3. Click Create a new filter. You'll see a menu where you can select parameters by which to search. Default parameters are all jobs under your name.
    4. Click each menu item to modify the prefix, user, or status.
    5. You can click each job search history item and modify the search criteria.
    6. You can also favorite a job search query by clicking Add to favorites.

    Editing attributes for UNIX SYSTEM SERVICES files or directories in Zowe Explorer

    You can change the properties for UNIX SYSTEM SERVICES files or directories in Zowe Explorer such as owner, group, and permissions by completing the following steps with your RSE profile:

    1. In the UNIX SYSTEM SERVICES view, find the file or directory that you want to edit attributes for.
    2. Right-click the file or directory and click Edit Attributes.
    3. Modify the properties in the attributes view, and then click Apply Changes.
    4. (Optional) To obtain the latest attributes of the file or directory opened in the view, click Refresh.

    'zowe-webviews-sample'

    Copying and pasting UNIX SYSTEM SERVICES files or directories in Zowe Explorer

    You can copy and paste UNIX SYSTEM SERVICES files or directories in Zowe Explorer by completing the following steps with your RSE profile:

    1. In the UNIX SYSTEM SERVICES view, find the file or directory that you want to copy and paste.
    2. Right-click the file or directory and click Copy.
    3. Search the new location to paste the file or directory, and then right-click the new location and click Paste.

    Copying and pasting data sets or members in DATA SETS view

    You can copy and paste data sets and members in the DATA SETS view by completing the following steps with your RSE profile:

    1. In the DATA SETS view, find the data set or the member that you want to copy.
    2. Right-click the data set or the member, and then click Copy.
    3. Search the new location to paste the data set or member, and then right-click the new location and click Paste.
    4. Specify the name of the pasted data set or member by entering a new one or keeping the existing one.

    Canceling jobs in Zowe Explorer

    You can cancel an ongoing job in Zowe Explorer by completing the following steps:

    1. In the JOBS view, search for the job you want to cancel by owner or prefix.
    2. Right-click the job and click Cancel Job.
    - + diff --git a/Docs/introduction.html b/Docs/introduction.html index 1eec97243..11ff4f9b7 100644 --- a/Docs/introduction.html +++ b/Docs/introduction.html @@ -41,11 +41,11 @@ } )(); Introduction | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Introduction

    IBM Z® Open Editor is an extension for Visual Studio Code that provides language support for the IBM® Enterprise COBOL 6.4open in new window, PL/I 6.1open in new window, High Level Assembler for z/OS 3.1open in new window, z/OS TSO/E REXXopen in new window, and z/OS MVS JCL (Job Control Language)open in new window programming languages for z/OS®. This also includes capabilities for embedded statements for CICS 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.

    The extension realizes its language support by implementing fully functional language serversopen in new window together with additional editor enhancements that enable mainframe 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
    • Outline view and outline search
    • For both variables and paragraphs:
      • Declaration hovers
      • Peek definition
      • Go to definition
      • Find all references
    • Code and variable completion
    • Finding and navigating references
    • Previewing of copybooks and include files
    • Navigate to copybooks and include files
    • Refactoring such as "rename symbol"
    • Custom code snippet support and more than 200 example code snippets out of the box
    • Search and replace refactoring across multiple program files

    Notes:

    • For HLASM, a significant subset of the capabilities that are available for COBOL and PL/I are supported.
    • For REXX, a smaller subset of the capabilities are supported
    • For Job Control Language (JCL)open in new window and job spool files, IBM Z Open Editor provides syntax highlighting.
      • For JCL, we now have added features such as an Outline view, real-time syntax checking, and code completion.

    For a list of the enabled LSP features and in-progress features, see Known issues and limitations.

    Key Capabilities

    These are the key features and benefits of IBM Z Open Editor:

    • Modern editing experience for COBOL, PL/I, HLASM, and REXX development

      IBM Z Open Editor is available as an extension for Visual Studio Code (VS Code), which is becoming the most popular development environment according to recent surveys. With so many current and next generation developers having experience with VS Code, IBM Enterprise language support in VS Code makes enterprise programming more attractive and productive by allowing developers to use this popular editor, with the option to integrate numerous other extensions from the VS Code Marketplace.

    • Full language support via the Language Server Protocol (LSP)

      The extension supports many COBOL, PL/I, HLASM, and REXX capabilities that were not available in traditional editing environments such as ISPFopen in new window, by providing Language Server Protocolopen in new window implementations. See above for the list of key features. Although supported by many other editors now, the Language Server Protocol was specifically created for VS Code and therefore is a good way for providing language support in the editor.

    • Extended language server capabilities for more productivity

      In addition to the capabilities specified in the Language Server Protocol, the implementation is extended with more capabilities that are useful to enterprise developers. For example, you can use hovers for COBOL COPY, PL/I %INCLUDE, and HLASM COPY statements to preview the contents of the copybooks without opening in separate editor tabs and navigating away from your current editing position.

    • Integration with modern Software Configuration Management (SCM)

      Even if your organization does not standardize on an SCM, using the Git that is integrated in VS Code or using popular extensions such as GitLensopen in new window locally in a workspace will boost your productivity. You can work on COBOL, PL/I, HLASM, and REXX programs on your local workspace and snapshot work at any point, go back or branch into alternative explorations, merge your or your colleagues' branches back in, or revert to any earlier state of your code in a flash. Use side-by-side views and "blame" annotations to explore the changes between snapshots, how they looked before, and the time of changes. See exactly for each line when it was last changed and by whom. Explore the entire history of all changes for a specific file or all files in your workspace in a chronological history viewer.

    • z/OS interactions using the open source Zowe clients

      If you have z/OSMF or IBM Remote System Explorer API (RSE API) configured, you can use Zowe CLIopen in new window, the Zowe Explorer VS Code Extension (Zowe Explorer)open in new window, or both, to load and edit your files directly from z/OS or download them into your local workspace and then upload the changed files into the same or new data sets to compile and run your application. You can do all of these operations from IBM Z Open Editor directly with right-clicks and dialog interactions, and perform command-line operations using the VS Code Terminal view that integrates right below your editor, giving you one central view to everything.

      After configuration, IBM Z Open Editor can also take advantage of the Zowe CLI protocol for resolving dependencies over the network. For example, you can edit your COBOL programs locally, but resolve copybook dependencies directly out of MVS™ using the same Zowe connections.

    • IBM User Build

      IBM User Build allows z/OS developers who have the IBM Dependency Based Build (DBB) host component to run user builds right from their local integrated development environment (IDE). With the User Build setting enabled in your IDE, you can access IBM User Build options simply by right-clicking inside a COBOL, PL/I, or HLASM file. Refer to the full IBM User Build documentationopen in new window to learn more about how to leverage User Build.

    • Enterprise-level advanced capabilities

      IBM Z Open Editor v4 introduces advanced capabilities for enterprise-level development use cases that go beyond programming and simple z/OS Resources access. You would typically find such features in IBM's commercial zDevOps solutions such as IBM Developer for z/OS Enterprise Edition (IDzEE). These are at the moment preprocessor support for COBOL, a new Web view built on top of Zowe Explorer that displays z/OS resources such as data sets, unix files and jobs in a sortable table, custom HLASM macro support and a new DBB user build VS Code Problems view integration. Find a detailed exploration of these features in the Advanced Capabilities section.

    Last Updated:
    Contributors: Peter Haumer, Shi Kun Li, Min Huang, Lauren Li, Greg Lambert, Lauren Li, Peter Haumer, KRISTINA MAYO, Saile Daimwood, Billie Simmons, Ethan Mendel, Evann Wu, Hestia Zhang, Lauren K. Li, PETER HAUMER, Prasang Prajapati, Prasang-A-Prajapati, PrasangAPrajapati, kmaselli
    - + diff --git a/Docs/knownissues.html b/Docs/knownissues.html index 4e4ed46af..e04492975 100644 --- a/Docs/knownissues.html +++ b/Docs/knownissues.html @@ -41,12 +41,12 @@ } )(); Known issues and limitations | IBM Z® Open Editor - + -
    IBM Z® Open Editor

    Known issues and limitations

    The IBM Z® Open Editor extension has some known issues and limitations. This page provides the status of the current release. Also review the list of open issues and enhancement requests in our Github repositoryopen in new window. It might list issues that are not yet documented here.

    Java™ 11 64-Bit JRE or SDK required

    If the right version of Java cannot be found in the current user's path or if no JAVA_HOME environment variable was defined, you might see error messages in the Output view of VS Code. Such errors could also be caused by other reasons such as not enough free memory for Java on your system.

    Go through all the steps described in the Getting Started page for configuring Java to try out different options.

    Java not found on Linux

    Z Open Editor starts by searching for Java in the following locations:

    • The path specified by the zopeneditor.JAVA_HOME value in your VS Code settings.
    • The path specified by the java.jdt.ls.java.home value in your VS Code settings.
    • The path specified by your JAVA_HOME environment variable.

    After searching these locations, Z Open Editor will run commands to try and find Java on your operating system.

    If your installation is not found and you see errors in the Welcome page, try specifying a path to your Java for your zopeneditor.JAVA_HOME or java.jdt.ls.java.home value in your VS Code settings or setting your system's JAVA_HOME environment variable. Ensure that you exclude the bin/java directory from your path. For more information, see Configuring Java.

    Resetting Language Servers or VS Code

    It might happen that the language servers provided by IBM Z Open Editor become inconsistent and do not behave as expected. For example, a language server might stop reporting syntax errors, or it cannot resolve copybooks anymore. Instead of quitting and restarting VS Code completely, you can try pressing the F1 key and type the following commands to reset one or more language servers.

    • IBM Z Open Editor: Pause the COBOL Language Server: Stops the COBOL language server and restarts it when you open a COBOL file again.
    • IBM Z Open Editor: Pause the PL/I Language Server: Stops the PL/I language server and restarts it when you open a PL/I file again.
    • IBM Z Open Editor: Pause the Assembler Language Server: Stops the HLASM language server and restarts it when you open an HLASM file again.
    • IBM Z Open Editor: Pause the REXX Language Server: Stops the REXX language server and restarts it when you open a REXX file again.
    • IBM Z Open Editor: Pause the JCL Language Server: Stops the JCL language server and restarts it when you open a JCL file again.
    • IBM Z Open Editor: Reload Zowe Profiles: If you have changed the password of your Zowe CLI profile that is used to load your remote include files such as copybooks, you need to run this command to refresh the Zowe profile.
    • Developer: Reload Window: Restarts the current VS Code window and all of its extensions. If you have many editor windows open at the same time, you can use this command to reset just the current window in which you run the command.

    Limitations for Visual Studio Code Multi-Root Workspaces

    IBM Z® Open Editor supports VS Code multi-root workspacesopen in new window, but there are some limits or special rules on how ZAPP files and settings are used in a multi-root workspace:

    • Property Groups: the multi-root workspace can load multiple zapp files located in the top-dir of each workspace. We search for property groups in each of these zapp files in the order the workspaces are listed in the .code-workspace .code-workspace file when resolving include files.
    • For user build the DBB ZAPP profile located in the workspace of the program being built is being used. The application-conf files (additional files listed in zapp profile) also need to be in the root of the workspace with the program.
    • For Z Open Editor's user buildopen in new window, local copybooks and include files that need to be uploaded to z/OS UNIX System Services for build can be located in any other workspace of the multi-root workspace. The location of the copybooks and include files must be specified in the ZAPP file of the workspace in which these include files are located in. A ZAPP file cannot provide property groups that point to locations outside of its workspace. The exception would be using absolute path names, but those might break the ability to share the ZAPP file with other team members as they might have their files in different locations.

    Limitations of using Z Open Editor with Eclipse Che and Red Hat OpenShift Dev Spaces

    Almost all capabilities described in this documentation are available when you use IBM Z Open Editor with Eclipse Che or Red Hat OpenShift Dev Spaces. However, note the following limitations.

    • Zowe CLI secure credentials are currently not supported with Z Open Editor on Eclipse Che and Red Hat OpenShift Dev Spaces. The Zowe Explorer setting "zowe.security.secureCredentialsEnabled": false must be used in these environments. See the section Setting up integrations to interact with z/OS > Managing credentials unsecured.

    • Path names specified for property groups in ZAPP files are always case-sensitive, even if the setting "zopeneditor.enforceCaseSensitiveIncludeFileNames" is set to false. However, this setting works for the file names that get matched in the folders that match the property groups.

    Language-specific features and limitations

    COBOL

    The following lists show the implementation status of the COBOL language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.

    Enabled features of COBOL program files

    Limitations of COBOL program files

    • False unreachable code warnings: In some cases, the editor incorrectly reports that code is unreachable in embedded SQL and CICS statements such as EXEC CICS HANDLE. One such case is reported in this issueopen in new window. You can use a user setting to disable warnings for unreachable code completely as described in Enabling and disabling unreachable COBOL code warnings.
    • Incomplete support for conditional compilation: Our community has reported various issuesopen in new window when programs contain conditional compilation statements. These types of programs are currently not fully supported.
    • For COBOL programs that load a large number of copybooks from MVS, downloading can take a long time. Consider as a workaround the user setting "zowe.files.temporaryDownloadsFolder.cleanup": false that will not re-download the files between editing sessions.

    Enabled features of COBOL copybook files

    • Syntax errors
    • Find all references in file
    • Peek references in file
    • Rename symbol in file
    • Outline view
    • Syntax highlighting
    • Code completion
    • Snippets
    • Embedded languages support such as SQL, CICS, and DLI

    Limitations of COBOL copybook files

    • No support for Hover
    • No support for Go to declaration
    • No support for Find all references across the multiple files
    • No support for Peek references across the multiple files
    • No support for Rename symbol from a copybook to the files that include it

    PL/I

    The following lists show the implementation status of the PL/I language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.

    Enabled features of PL/I program files

    Limitations of PL/I program files

    • No support for macros
    • The left margin is currently not fully configurable. The minimum value required is 2.
    • PL/I 6.1
      • No support is included for the MAXRUNONIF compiler option.
      • No support is included for the PROCINC directive. An alternative way to accomplish the purpose of the PROCINC directive is to use the PROCESS directive with the compiler option from the data set that you want to add for the PROCINC directive.
    • For PL/I programs that load a large number of include files from MVS, downloading can take a long time. Consider as a workaround the user setting "zowe.files.temporaryDownloadsFolder.cleanup": false that will not re-download the files between editing sessions.

    The following legal PL/I syntactic constructions are marked as errors:

    • Invalid PL/I syntax in macro preprocessor input when the macro preprocessor output is legal PL/I
    • Labels on preprocessor directives
    • Entry constants
    • Type functions
    • Factoring of attributes when you declare structures
    • An isub option with defined attribute
    • A tstack attribute of the attach statement
    • Implicit variable declarations

    The following invalid PL/I syntactic constructions are not marked as errors:

    • Condition prefixes for do statements
    • Label prefixes for declare, default, when, otherwise, and on statements
    • Scaling factors for float or fixed
    • Duplicate attributes for declaration statements
    • Syntax errors in macro preprocessor output

    Enabled features of PL/I include files

    • Syntax errors (lexing and parsing)
    • Find all references in file
    • Peek references in file
    • Rename symbol in file
    • Outline view
    • Syntax highlighting
    • Code completion
    • Embedded languages support such as SQL, CICS, and DLI

    Limitations of PL/I include files

    • No support for showing syntax errors for resolving variables
    • No support for Hover
    • No support for Go to declaration
    • No support for Find all references across the multiple files
    • No support for Peek references across the multiple files
    • No support for Rename symbol across the multiple files

    HLASM

    The following lists show the implementation status of the HLASM language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.

    Enabled features of HLASM program files

    • Syntax highlighting
    • Syntax errors, which currently only include the following:
      • Copy statements not resolved
      • Spaces in continuation line
      • Invalid number of operands
    • Document highlighting
    • Hover on operations and operands
    • Go to declaration for all operands, including those from copy members
    • Find all references in file
    • Peek references in file
    • Outline view for macros, CSECTs, and DSECTs
    • Code completion, including snippet-style completion for operations and macros
    • Copy member file resolving and copy member file hover support
    • SYS1.MACLIB Macro remote file resolving and content hover support
      • The z/OS version for SYS1.MACLIB is configurable between 2.4, 2.5, and 3.1 with the user setting "zopeneditor.hlasm.zosMacrosVersion".
    • Custom Macro file resolving, code completion, and content hover support for local macros.
    • Document link support to open copybook file by using Ctrl+Click (Windows) or Cmd+Click (Mac)
    • Quick fix hints for lines that are too long and spaces in the continuation line
    • Commenting and uncommenting HLASM code

    Limitations of HLASM program files

    • Limited syntax checks such as no errors for undeclared variables
    • Syntax highlighting limitations on multi-line strings
    • Syntax highlighting limitations on non-continuation lines that begin at column 16
    • Syntax highlighting does not recognize continuation lines that begin at column 17 and later as comments
    • Keyword based HLASM code folding: Currently VS Code default code folding is based on indentation levels, not keywords.
    • Custom Macro file resolving is not currently available for remote macros.

    REXX

    The following lists show the implementation status of the REXX language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.

    Enabled features of REXX program files

    • Syntax highlighting
    • Syntax errors
    • Hover
    • Find all references
    • Outline view
    • Code completion
    • Include control directive resolution and hover support
    • Syntax Highlighting for Include control directives
    • Commenting and uncommenting REXX code

    Limitations of REXX program files

    • No support for the 'END' keyword as a variable
    • No support for embedded languages
    • Code Completion and Hover do not support keywords that are not keyword instructions
    • Some color themes may not highlight all symbols correctly
    • Files that contain the replacement character (�) are not parsed correctly
    • The simple symbol, constant symbol, compound symbol, stem, and internal routine suggestions are restricted to the current file in the editor
    • Code Completion inserts an extra pair of parenthesis when an existing function call in the editor is replaced with a built-in function
    • Changing the contents of a resolved include control directive will not necessarily clear errors
    • The language features do not consider the contents of a resolved include control directive
    • Keyword based REXX code folding: Currently VS Code default code folding is based on indentation levels, not keywords.

    JCL

    The following lists show the implementation status of the JCL language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.

    Enabled features of JCL program files

    • Syntax highlighting
    • Syntax errors
    • Outline view
    • Code completion
    • Snippets
    • Code folding

    IBM RSE API Plug-in for Zowe CLI

    Known issues and limitations for IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in)

    HTTP protocol support for RSE profiles

    As of Zowe CLI 6.31.0, HTTP support is not available for RSE profile connections. There is a Zowe CLI issueopen in new window that can be tracked for solution to bring this support back.

    npm WARN for peer dependencies

    When installing RSE CLI plug-in, you may encounter an npm WARN for an unmet peer dependency of Zowe CLI even though you have an accommodating version installed. There is due to a known bug in npm versions prior to 7. Having the warnings will not interfere with the successful installation of the plug-in; however, these warnings can be eliminated by running the command npm install npm@latest -g to obtain the latest version of npm.

    RSE CLI plug-in with ZAPP

    • When using the --mappings-file tag to state the location of a mappings file to use for upload and download of MVS files, if you have a zapp.json and a zapp.yaml in the same directory, the zapp.yaml will take precedence over the JSON file. It is recommended that you have only one zapp.yaml or zapp.json file when using ZAPP files at a project level.

    RSE CLI plug-in with JSON Web Tokens

    • JSON Web Tokens are not supported by Zowe Explorer 1.9.0 or previous versions.
    • If you created an RSE profile by using Zowe Explorer 1.11.1 or lower and left the username and password values blank and have empty strings stored within the profile's YAML, you will be required to add the --user and --password tags with the appropriate values when you use command line operations with that profile, even if a JWT has been issued for the profile at this time. We recommend creating the profile using command line operations or editing the profile with Zowe Explorer 1.12.0 or higher to omit the empty strings in the profile's YAML file.
    • The JWT logout command zowe rse auth logout is not supported by the host component RSE API 1.0.0.
    • If VS Code is opened during the auth login and auth logout is submitted using the CLI command with v1 profiles, a refresh of VS Code is required to grab the changes to the profile's YAML file for profile updates to be used in Zowe Explorer.
    • When using token authentication in Wazi Dev Spaces, the login action will fail if the team configuration profile is opened. To prevent this, make sure that the team configuration file is closed and the "autoSave" setting of editor is set to true.

    RSE CLI plug-in TSO and UNIX commands

    • The command zowe rse issue command {COMMAND}, which can be used to issue a TSO command, is not supported by the host component RSE API 1.0.0.
    • Issuing a UNIX command with an RSE profile via Zowe Explorer is not supported yet.

    Known issues with z/OS UNIX System Services

    • z/OS UNIX System Services does not accept the upload of a directory or file names with spaces in them.

    • An error occurs when you specify z/OS UNIX System Services paths in a Window's Bash terminal (for example: /u/userid). To solve the issue, create an environment variable MSYS_NO_PATHCONV with a value of 1 in User Variables and restart the terminal.

    Using z/OSMF with Z Open Editor and Zowe Explorer

    IBM Z Open Editor can download remote files that are included in your programs through the RSE API or z/OSMF. If you are using z/OSMF to download remote files, it is recommended that you configure the host system with the following values at a minimum for z/OSMF:

    ParameterValue
    MAXSESSIONS250
    MAXUSERS25

    These recommendations ensure that optimal performance will be maintained even if many users are requesting remote downloads concurrently.

    If your development demands typically see more than 25 users requesting remote files concurrently, it is recommended that you increase MAXUSERS to meet your needs and increase MAXSESSIONS to a value equal to MAXUSERS*10.

    For more information on where to set these values or solutions if your host system is running into resource problems, see this blogopen in new window.

    Known issues for user build

    Using an older version of IBM Dependency-Based Build

    IBM Z Open Editor v3+ is optimized for working with IBM Dependency-Based Build (DBB) v2. However, it can also still work with DBB v1. To be able run builds with v2 you need to use the main branch of the https://github.com/IBM/dbb-zappbuildopen in new window zAppBuild git repository. To build with DBB v1 you must checkout the branch called zAppBuild_2_x. Here the 2 stands for zAppBuild version 2 as the latest version in the main branch of zAppBuild is v3, which is the one that works with DBB v2.

    Using an older version of DBB zAppBuild

    If you are not using the latest branches of zAppBuild or have your own fork that was based on an older version than DBB zAppBuild 2.3.0 then consider the following. The encoding of the dependency file generated during an IBM User Build was recently changed from IBM-1047 to a standard UTF-8 encoding. This change means that if the latest version of IBM Z Open Editor is not paired with DBB zAppBuild 2.3.0 or greater you will have to add the previously required IBM-1047 encoding to the dependency file being generated, by adding the following to your .gitattributes file in your project in order to run an IBM User Build successfully:

    *.userbuilddependencies zos-working-tree-encoding=ibm-1047 git-encoding=utf-8

    Additionally, when using DBB v1 and zAppBuild v2, when you build a program file that contains spaces in the file path or name, you get the following error:

    java.util.MissingFormatArgumentException: Format specifier ‘%s’
-

    At the moment, zAppBuild v2 does not support spaces or URI encoded space character %20 in the build file path or name. See the issue Support spaces in build file directory pathsopen in new window for updates.

    Other known issues

    • Some programs fail building on z/OS with the error Missing required dependency file field 'isCICS'. when using the --dependencyFile ${dependencyFile}" build script arguments in the ZAPP profile. As a workaround remove this parameter for now until we can provide a fix. This parameters is an optional performance improvement. Builds can work without it as well.

    Reporting issues

    If you want to provide feedback or report an issue, open an issue in the GitHub repositoryopen in new window. Any report and feedback is appreciated.

    Last Updated:
    Contributors: Billie Simmons, Peter Haumer, Shi Kun Li, Billie Simmons, Greg Lambert, Lauren Li, Min Huang, Peter Haumer, Bradley Knaysi, Lauren Li, Prasang-A-Prajapati, Chun Hong Zheng, Benjamin Santos, Saile Daimwood, Rudy Leonel Pichola Flores, BillieJean-Simmons, PETER HAUMER, Saile, Billie Jean Simmons, kmaselli, Arvin Bhatnagar, Hestia Zhang, Lauren K Li, Prasang Prajapati, PrasangAPrajapati, shikunli, KRISTINA MAYO, Keng-Hui Beall
    - +
    IBM Z® Open Editor

    Known issues and limitations

    The IBM Z® Open Editor extension has some known issues and limitations. This page provides the status of the current release. Also review the list of open issues and enhancement requests in our Github repositoryopen in new window. It might list issues that are not yet documented here.

    Java™ 11 64-Bit JRE or SDK required

    If the right version of Java cannot be found in the current user's path or if no JAVA_HOME environment variable was defined, you might see error messages in the Output view of VS Code. Such errors could also be caused by other reasons such as not enough free memory for Java on your system.

    Go through all the steps described in the Getting Started page for configuring Java to try out different options.

    Java not found on Linux

    Z Open Editor starts by searching for Java in the following locations:

    • The path specified by the zopeneditor.JAVA_HOME value in your VS Code settings.
    • The path specified by the java.jdt.ls.java.home value in your VS Code settings.
    • The path specified by your JAVA_HOME environment variable.

    After searching these locations, Z Open Editor will run commands to try and find Java on your operating system.

    If your installation is not found and you see errors in the Welcome page, try specifying a path to your Java for your zopeneditor.JAVA_HOME or java.jdt.ls.java.home value in your VS Code settings or setting your system's JAVA_HOME environment variable. Ensure that you exclude the bin/java directory from your path. For more information, see Configuring Java.

    Resetting Language Servers or VS Code

    It might happen that the language servers provided by IBM Z Open Editor become inconsistent and do not behave as expected. For example, a language server might stop reporting syntax errors, or it cannot resolve copybooks anymore. Instead of quitting and restarting VS Code completely, you can try pressing the F1 key and type the following commands to reset one or more language servers.

    • IBM Z Open Editor: Pause the COBOL Language Server: Stops the COBOL language server and restarts it when you open a COBOL file again.
    • IBM Z Open Editor: Pause the PL/I Language Server: Stops the PL/I language server and restarts it when you open a PL/I file again.
    • IBM Z Open Editor: Pause the Assembler Language Server: Stops the HLASM language server and restarts it when you open an HLASM file again.
    • IBM Z Open Editor: Pause the REXX Language Server: Stops the REXX language server and restarts it when you open a REXX file again.
    • IBM Z Open Editor: Pause the JCL Language Server: Stops the JCL language server and restarts it when you open a JCL file again.
    • IBM Z Open Editor: Reload Zowe Profiles: If you have changed the password of your Zowe CLI profile that is used to load your remote include files such as copybooks, you need to run this command to refresh the Zowe profile.
    • Developer: Reload Window: Restarts the current VS Code window and all of its extensions. If you have many editor windows open at the same time, you can use this command to reset just the current window in which you run the command.

    Limitations for Visual Studio Code Multi-Root Workspaces

    IBM Z® Open Editor supports VS Code multi-root workspacesopen in new window, but there are some limits or special rules on how ZAPP files and settings are used in a multi-root workspace:

    • Property Groups: the multi-root workspace can load multiple zapp files located in the top-dir of each workspace. We search for property groups in each of these zapp files in the order the workspaces are listed in the .code-workspace .code-workspace file when resolving include files.
    • For user build the DBB ZAPP profile located in the workspace of the program being built is being used. The application-conf files (additional files listed in zapp profile) also need to be in the root of the workspace with the program.
    • For Z Open Editor's user buildopen in new window, local copybooks and include files that need to be uploaded to z/OS UNIX System Services for build can be located in any other workspace of the multi-root workspace. The location of the copybooks and include files must be specified in the ZAPP file of the workspace in which these include files are located in. A ZAPP file cannot provide property groups that point to locations outside of its workspace. The exception would be using absolute path names, but those might break the ability to share the ZAPP file with other team members as they might have their files in different locations.

    Limitations of using Z Open Editor with Eclipse Che and Red Hat OpenShift Dev Spaces

    Almost all capabilities described in this documentation are available when you use IBM Z Open Editor with Eclipse Che or Red Hat OpenShift Dev Spaces. However, note the following limitations.

    • Zowe CLI secure credentials are currently not supported with Z Open Editor on Eclipse Che and Red Hat OpenShift Dev Spaces. The Zowe Explorer setting "zowe.security.secureCredentialsEnabled": false must be used in these environments. See the section Setting up integrations to interact with z/OS > Managing credentials unsecured.

    • Path names specified for property groups in ZAPP files are always case-sensitive, even if the setting "zopeneditor.enforceCaseSensitiveIncludeFileNames" is set to false. However, this setting works for the file names that get matched in the folders that match the property groups.

    Language-specific features and limitations

    COBOL

    The following lists show the implementation status of the COBOL language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.

    Enabled features of COBOL program files

    Limitations of COBOL program files

    • False unreachable code warnings: In some cases, the editor incorrectly reports that code is unreachable when more than one entry point is present. One such case is reported in this issueopen in new window. You can use a user setting to disable warnings for unreachable code completely as described in Enabling and disabling unreachable COBOL code warnings.
    • Incomplete support for conditional compilation: Our community has reported various issuesopen in new window when programs contain conditional compilation statements. These types of programs are currently not fully supported.
    • For COBOL programs that load a large number of copybooks from MVS, downloading can take a long time. Consider as a workaround the user setting "zowe.files.temporaryDownloadsFolder.cleanup": false that will not re-download the files between editing sessions.

    Enabled features of COBOL copybook files

    • Syntax errors
    • Find all references in file
    • Peek references in file
    • Rename symbol in file
    • Outline view
    • Syntax highlighting
    • Code completion
    • Snippets
    • Embedded languages support such as SQL, CICS, and DLI

    Limitations of COBOL copybook files

    • No support for Hover
    • No support for Go to declaration
    • No support for Find all references across the multiple files
    • No support for Peek references across the multiple files
    • No support for Rename symbol from a copybook to the files that include it

    PL/I

    The following lists show the implementation status of the PL/I language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.

    Enabled features of PL/I program files

    Limitations of PL/I program files

    • No support for macros
    • The left margin is currently not fully configurable. The minimum value required is 2.
    • PL/I 6.1
      • No support is included for the MAXRUNONIF compiler option.
      • No support is included for the PROCINC directive. An alternative way to accomplish the purpose of the PROCINC directive is to use the PROCESS directive with the compiler option from the data set that you want to add for the PROCINC directive.
    • For PL/I programs that load a large number of include files from MVS, downloading can take a long time. Consider as a workaround the user setting "zowe.files.temporaryDownloadsFolder.cleanup": false that will not re-download the files between editing sessions.

    The following legal PL/I syntactic constructions are marked as errors:

    • Invalid PL/I syntax in macro preprocessor input when the macro preprocessor output is legal PL/I
    • Labels on preprocessor directives
    • Entry constants
    • Type functions
    • Factoring of attributes when you declare structures
    • An isub option with defined attribute
    • A tstack attribute of the attach statement
    • Implicit variable declarations

    The following invalid PL/I syntactic constructions are not marked as errors:

    • Condition prefixes for do statements
    • Label prefixes for declare, default, when, otherwise, and on statements
    • Scaling factors for float or fixed
    • Duplicate attributes for declaration statements
    • Syntax errors in macro preprocessor output

    Enabled features of PL/I include files

    • Syntax errors (lexing and parsing)
    • Find all references in file
    • Peek references in file
    • Rename symbol in file
    • Outline view
    • Syntax highlighting
    • Code completion
    • Embedded languages support such as SQL, CICS, and DLI

    Limitations of PL/I include files

    • No support for showing syntax errors for resolving variables
    • No support for Hover
    • No support for Go to declaration
    • No support for Find all references across the multiple files
    • No support for Peek references across the multiple files
    • No support for Rename symbol across the multiple files

    HLASM

    The following lists show the implementation status of the HLASM language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.

    Enabled features of HLASM program files

    • Syntax highlighting
    • Syntax errors, which currently only include the following:
      • Copy statements not resolved
      • Spaces in continuation line
      • Invalid number of operands
    • Document highlighting
    • Hover on operations and operands
    • Go to declaration for all operands, including those from copy members
    • Find all references in file
    • Peek references in file
    • Outline view for macros, CSECTs, and DSECTs
    • Code completion, including snippet-style completion for operations and macros
    • Copy member file resolving and copy member file hover support
    • SYS1.MACLIB Macro remote file resolving and content hover support
      • The z/OS version for SYS1.MACLIB is configurable between 2.4, 2.5, and 3.1 with the user setting "zopeneditor.hlasm.zosMacrosVersion".
    • Custom Macro file resolving, code completion, and content hover support for local macros.
    • Document link support to open copybook file by using Ctrl+Click (Windows) or Cmd+Click (Mac)
    • Quick fix hints for lines that are too long and spaces in the continuation line
    • Commenting and uncommenting HLASM code

    Limitations of HLASM program files

    • Limited syntax checks such as no errors for undeclared variables
    • Syntax highlighting limitations on multi-line strings
    • Syntax highlighting limitations on non-continuation lines that begin at column 16
    • Syntax highlighting does not recognize continuation lines that begin at column 17 and later as comments
    • Keyword based HLASM code folding: Currently VS Code default code folding is based on indentation levels, not keywords.
    • Custom Macro file resolving is not currently available for remote macros.

    REXX

    The following lists show the implementation status of the REXX language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.

    Enabled features of REXX program files

    • Syntax highlighting
    • Syntax errors
    • Hover
    • Find all references
    • Outline view
    • Code completion
    • Include control directive resolution and hover support
    • Syntax Highlighting for Include control directives
    • Commenting and uncommenting REXX code

    Limitations of REXX program files

    • No support for the 'END' keyword as a variable
    • No support for embedded languages
    • Code Completion and Hover do not support keywords that are not keyword instructions
    • Some color themes may not highlight all symbols correctly
    • Files that contain the replacement character (�) are not parsed correctly
    • The simple symbol, constant symbol, compound symbol, stem, and internal routine suggestions are restricted to the current file in the editor
    • Code Completion inserts an extra pair of parenthesis when an existing function call in the editor is replaced with a built-in function
    • Changing the contents of a resolved include control directive will not necessarily clear errors
    • The language features do not consider the contents of a resolved include control directive
    • Keyword based REXX code folding: Currently VS Code default code folding is based on indentation levels, not keywords.

    JCL

    The following lists show the implementation status of the JCL language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.

    Enabled features of JCL program files

    • Syntax highlighting
    • Syntax errors
    • Outline view
    • Code completion
    • Snippets
    • Code folding

    IBM RSE API Plug-in for Zowe CLI

    Known issues and limitations for IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in)

    HTTP protocol support for RSE profiles

    As of Zowe CLI 6.31.0, HTTP support is not available for RSE profile connections. There is a Zowe CLI issueopen in new window that can be tracked for solution to bring this support back.

    npm WARN for peer dependencies

    When installing RSE CLI plug-in, you may encounter an npm WARN for an unmet peer dependency of Zowe CLI even though you have an accommodating version installed. There is due to a known bug in npm versions prior to 7. Having the warnings will not interfere with the successful installation of the plug-in; however, these warnings can be eliminated by running the command npm install npm@latest -g to obtain the latest version of npm.

    RSE CLI plug-in with ZAPP

    • When using the --mappings-file tag to state the location of a mappings file to use for upload and download of MVS files, if you have a zapp.json and a zapp.yaml in the same directory, the zapp.yaml will take precedence over the JSON file. It is recommended that you have only one zapp.yaml or zapp.json file when using ZAPP files at a project level.

    RSE CLI plug-in with JSON Web Tokens

    • JSON Web Tokens are not supported by Zowe Explorer 1.9.0 or previous versions.
    • If you created an RSE profile by using Zowe Explorer 1.11.1 or lower and left the username and password values blank and have empty strings stored within the profile's YAML, you will be required to add the --user and --password tags with the appropriate values when you use command line operations with that profile, even if a JWT has been issued for the profile at this time. We recommend creating the profile using command line operations or editing the profile with Zowe Explorer 1.12.0 or higher to omit the empty strings in the profile's YAML file.
    • The JWT logout command zowe rse auth logout is not supported by the host component RSE API 1.0.0.
    • If VS Code is opened during the auth login and auth logout is submitted using the CLI command with v1 profiles, a refresh of VS Code is required to grab the changes to the profile's YAML file for profile updates to be used in Zowe Explorer.
    • When using token authentication in Wazi Dev Spaces, the login action will fail if the team configuration profile is opened. To prevent this, make sure that the team configuration file is closed and the "autoSave" setting of editor is set to true.

    RSE CLI plug-in TSO and UNIX commands

    • The command zowe rse issue command {COMMAND}, which can be used to issue a TSO command, is not supported by the host component RSE API 1.0.0.
    • Issuing a UNIX command with an RSE profile via Zowe Explorer is not supported yet.

    RSE CLI plug-in COPY DATASETS CROSS LPAR command

    • The command zowe rse copy data-set-cross-lpar {COMMAND}, which can be used to copy datasets across lpars, does prompt for entering the username and password of the service twice which actually generates from the zowe cli side, but doesnot specify which LPAR it corresponds to.

    Known issues with z/OS UNIX System Services

    • z/OS UNIX System Services does not accept the upload of a directory or file names with spaces in them.

    • An error occurs when you specify z/OS UNIX System Services paths in a Window's Bash terminal (for example: /u/userid). To solve the issue, create an environment variable MSYS_NO_PATHCONV with a value of 1 in User Variables and restart the terminal.

    Using z/OSMF with Z Open Editor and Zowe Explorer

    IBM Z Open Editor can download remote files that are included in your programs through the RSE API or z/OSMF. If you are using z/OSMF to download remote files, it is recommended that you configure the host system with the following values at a minimum for z/OSMF:

    ParameterValue
    MAXSESSIONS250
    MAXUSERS25

    These recommendations ensure that optimal performance will be maintained even if many users are requesting remote downloads concurrently.

    If your development demands typically see more than 25 users requesting remote files concurrently, it is recommended that you increase MAXUSERS to meet your needs and increase MAXSESSIONS to a value equal to MAXUSERS*10.

    For more information on where to set these values or solutions if your host system is running into resource problems, see this blogopen in new window.

    Known issues for user build

    Using an older version of IBM Dependency-Based Build

    IBM Z Open Editor v3+ is optimized for working with IBM Dependency-Based Build (DBB) v2. However, it can also still work with DBB v1. To be able run builds with v2 you need to use the main branch of the https://github.com/IBM/dbb-zappbuildopen in new window zAppBuild git repository. To build with DBB v1 you must checkout the branch called zAppBuild_2_x. Here the 2 stands for zAppBuild version 2 as the latest version in the main branch of zAppBuild is v3, which is the one that works with DBB v2.

    Using an older version of DBB zAppBuild

    If you are not using the latest branches of zAppBuild or have your own fork that was based on an older version than DBB zAppBuild 2.3.0 then consider the following. The encoding of the dependency file generated during an IBM User Build was recently changed from IBM-1047 to a standard UTF-8 encoding. This change means that if the latest version of IBM Z Open Editor is not paired with DBB zAppBuild 2.3.0 or greater you will have to add the previously required IBM-1047 encoding to the dependency file being generated, by adding the following to your .gitattributes file in your project in order to run an IBM User Build successfully:

    *.userbuilddependencies zos-working-tree-encoding=ibm-1047 git-encoding=utf-8

    Additionally, when using DBB v1 and zAppBuild v2, when you build a program file that contains spaces in the file path or name, you get the following error:

    java.util.MissingFormatArgumentException: Format specifier ‘%s’
+

    At the moment, zAppBuild v2 does not support spaces or URI encoded space character %20 in the build file path or name. See the issue Support spaces in build file directory pathsopen in new window for updates.

    Other known issues

    • Some programs fail building on z/OS with the error Missing required dependency file field 'isCICS'. when using the --dependencyFile ${dependencyFile}" build script arguments in the ZAPP profile. As a workaround remove this parameter for now until we can provide a fix. This parameters is an optional performance improvement. Builds can work without it as well.

    Reporting issues

    If you want to provide feedback or report an issue, open an issue in the GitHub repositoryopen in new window. Any report and feedback is appreciated.

    Last Updated:
    Contributors: Billie Simmons, Peter Haumer, Shi Kun Li, Billie Simmons, Greg Lambert, Lauren Li, Min Huang, Peter Haumer, Bradley Knaysi, Lauren Li, Prasang-A-Prajapati, Chun Hong Zheng, Saile Daimwood, Benjamin Santos, Rudy Leonel Pichola Flores, BillieJean-Simmons, PETER HAUMER, Saile, Billie Jean Simmons, kmaselli, Arvin Bhatnagar, Hestia Zhang, Lauren K Li, Prasang Prajapati, PrasangAPrajapati, shikunli, KRISTINA MAYO, Keng-Hui Beall, Nimma Likhitha
    + diff --git a/Docs/language_references.html b/Docs/language_references.html index 733676878..1ea0cd791 100644 --- a/Docs/language_references.html +++ b/Docs/language_references.html @@ -41,11 +41,11 @@ } )(); Language References | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Language References

    The IBM Z Open Editor ships with IBM language servers for COBOL, PL/I, HLASM, and REXX. These language servers follow the language specification as documented here:

    Last Updated:
    Contributors: Greg Lambert, Peter Haumer, Peter Haumer, Prasang Prajapati, PrasangAPrajapati, Saile Daimwood, kmaselli
    - + diff --git a/Docs/locating_local_client_logs.html b/Docs/locating_local_client_logs.html index 4e609f9d1..b57a0f4de 100644 --- a/Docs/locating_local_client_logs.html +++ b/Docs/locating_local_client_logs.html @@ -41,11 +41,11 @@ } )(); Troubleshooting using log files | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Troubleshooting using log files

    You can enable logging for IBM Z Open Editor to produce detailed logs that can be used to troubleshoot problems by providing more information and a trace about the activities the editor is performing.

    You can enable logging through a user preference setting called zopeneditor.logger. In the VS Code Preferences editor, select from the allowed log levels: DEBUG, INFO (default), WARN, ERROR, and OFF.

    After logging is enabled, you can find the logging output in two places:

    • In the VS Code Output panel, by selecting IBM Z Open Editor from the drop-down list.
    • A log file written to your disk that can be shared with technical support (if you are entitled to it) or attached to the issue you file against our public issues repository on GitHubopen in new window. The first line in the VS Code Output panel will contain the absolute path to where the file is located on your system.

    Use the log file for troubleshooting issues with the information provided. For example, when trying to understand why a specific include file was not found by the editor, the log file produced under the DEBUG log level will give you a trace of the editor's activities for finding ZAPP files in your workspaces, the property groups it used, as well as in which locations it is looking. You can search in the log to see where an initial request for a specific file was made, the steps of processing the request, as well as any errors that were reported. Because the requests for all the include files in a program happen in parallel, each request will have a unique request ID that will help in distinguishing the concurrent events in the log.

    Finding versions of all VS Code extensions installed

    Enabling logging also provides information that technical support will be asking for. To retrieve it:

    1. Ensure that your IBM Z Open Editor logger preference is set to DEBUG.

    2. In the Output console window, select IBM Z Open Editor from the drop-down list. The following information will be listed:

      • IBM Z Open Editor version
      • Editor platform and version
      • Editor Installation information
      • Java SDK configuration location and memory allocation
      • Key user settings
      • Zowe Explorer VS Code Extension version
      • Other VS Code Extensions visible

      CRW Log Info

    Locating VS Code extension and LSP log files on the local client

    In addition to the Z Open Editor log file, there are other log files that can help with troubleshooting. For example, Zowe Explorer has implemented the same mechanism of selecting the log level from Settings, showing the content in the VS Code Output view, and writing it to a file that you can find by looking at the first line. Here a reference for where the extension and other relevant log files are typically located:

    Log typeLocation
    Main logThe location is specified in output console window on 2nd line.
    ** The log file is available at...
    • Windows example: C:\Users\username\AppData\Roaming\Code\logs\20200921T153526\exthost1\IBM.zopeneditor\zopeneditor-1-1-0.log
    • Mac example: /Users/username/Library/Application Support/Code/logs/20200928T093225/exthost5/IBM.zopeneditor/zopeneditor-1-1-0.log
    Language Server Protocol (LSP) logFind the line that begins with the following sentence to locate the LSP logs:
    ** ZLanguageServer: Will start a language server with command...

    Then, find the -data, tag which immediately precedes the LSP log file location.
    • Windows example: C:\Users\username\AppData\Local\Temp\_ws_<id>\.metadata/.log
    • Mac example: /var/folders/sr/qztfyx3d39z50jgl50ls_b0r0000gn/T/_ws_<id>/.metadata/.log
    Zowe Explorer log
    • Windows example: C:\Users\username\.vscode\extensions\zowe.vscode-extension-for-zowe-1.9.0\logs
    • Mac example: /Users/username/.vscode/extensions/zowe.vscode-extension-for-zowe-1.9.0/logs
    RSE API plug-in for Zowe CLI (RSE CLI plug-in) logsLog files can be found in two locations:
    • ~\.zowe\zowe\logs\
    • ~\.zowe\imperative\logs\

    Finding Zowe CLI version and RSE CLI plug-in version

    In the VS Code Terminal window, enter the applicable commands:

    • Command for Zowe CLI: zowe --version
    • Command for RSE CLI plug-in: zowe plugins list

    Log levels

    IBM Z Open Editor uses the log levels described in the following chart. These levels are listed in order of most to least detailed (with the exception of OFF, which turns off all logging). For example, the DEBUG setting will output detailed debug information as well as messages from the other levels below it: INFO, WARN, and ERROR. In contrast, the ERROR setting will only log important errors.

    Log levelDescription
    DebugIdentifies detailed informational events that are useful for troubleshooting the editor's behavior.
    InfoProvides informative messages that are of general interest to the end user for observing activities performed by the editor.
    WarnIndicates potentially problematic situations that could cause unexpected behaviors or errors.
    ErrorDesignates error events that interrupted the editor in executing an operation as intended.
    OffNothing is logged.
    Last Updated:
    Contributors: Greg Lambert, Lauren Li, Lauren Li, Peter Haumer, Chun Hong Zheng, Kimberlee Maselli, Min Huang, Peter Haumer, Prasang-A-Prajapati, shikunli
    - + diff --git a/Docs/migrating_profiles.html b/Docs/migrating_profiles.html index 7fdd43a7b..465abfb58 100644 --- a/Docs/migrating_profiles.html +++ b/Docs/migrating_profiles.html @@ -41,11 +41,11 @@ } )(); Migrating your old Zowe yaml profiles for Zowe v2.0 | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Migrating your old Zowe yaml profiles for Zowe v2.0

    When upgrading to Zowe Explorer v2.0, you are still able to use your old YAML based profiles. The following steps are provided in order to keep your old profiles working and utilize them in your workspace:

    Migrating through Zowe CLI

    1. Review your installed Zowe plugins from Zowe CLI by running zowe plugins list and verify that the secure credential store plugin is not installed.

    2. Issue the following command in your terminal zowe scs revert --force.

    3. If the secure credential store plugin is installed, run the following command to uninstall zowe plugins uninstall @zowe/secure-credential-store-for-zowe-cli.

    4. Verify your plugins are updated to a version compatible with Zowe CLI v7.0.0, otherwise you can uninstall your installed Zowe plugins by using zowe plugins uninstall <your zowe plugin name> for each plugin installed.

    5. Install the new version of Zowe CLI by running npm update -g @zowe/cli@zowe-v2-lts.

    Migrating through Zowe Explorer VS Code Extension

    1. If auto-install is disabled, update Zowe Explorer by going to "extensions > Zowe Explorer" in Visual Studio Code and clicking the Update button.

    After performing the previous steps, your old YAML based profiles can be migrated to a team config file with the following command: zowe config convert-profiles.

    Last Updated:
    Contributors: Rudy Leonel Pichola Flores, Kimberlee Maselli
    - + diff --git a/Docs/notices.html b/Docs/notices.html index 55dca2e41..dfa10f947 100644 --- a/Docs/notices.html +++ b/Docs/notices.html @@ -41,11 +41,11 @@ } )(); Notices | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Notices

    This information was developed for products and services offered in the US. This material might be available from IBM® in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it.

    IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user’s responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

    IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

    IBM Director of Licensing, IBM Corporation, North Castle Drive, MD-NC119, Armonk, NY 10504-1785, US

    INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

    This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

    Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.

    IBM may use or distribute any of the information you provide in any way it believes appropriate without incurring any obligation to you.

    The performance data and client examples cited are presented for illustrative purposes only. Actual performance results may vary depending on specific configurations and operating conditions.

    Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

    Statements regarding IBM’s future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

    This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to actual people or business enterprises is entirely coincidental.

    COPYRIGHT LICENSE:

    This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS”, without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.

    Last Updated:
    Contributors: Min Huang, Peter Haumer, enzi
    - + diff --git a/Docs/other_extensions.html b/Docs/other_extensions.html index 4fdbe3e15..44d29e84e 100644 --- a/Docs/other_extensions.html +++ b/Docs/other_extensions.html @@ -41,11 +41,11 @@ } )(); Other Visual Studio Code extensions | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Other Visual Studio Code extensions

    In addition to IBM Z Open Editor and Zowe Explorer, there are some other Visual Studio Code extensions that provide added value and integrations with technology relevant for enterprise application developers. The following table shows some examples.

    Note: These extensions are independent of IBM Z Open Editor and supported by the respective publishers according to their specific terms.

    Extension nameDescription
    AnsibleThis extension adds language support for Ansible to Visual Studio Code. It can be used to write Ansible playbooks as well as Red Hat Ansible Certified Content for IBM Zopen in new window. To install this extension, see Ansibleopen in new window.
    GitLensThis is the ultimate extension for using Visual Studio Code with Git providing graphical views and commands for almost all Git capabilities. To install this extension, see GitLens — Git superchargedopen in new window.
    IBM Db2 for z/OS Developer ExtensionThis is an extension for Visual Studio Code that provides language support for developing Db2 for z/OS SQL applications. To install this extension, see IBM Db2 for z/OS Developer Extensionopen in new window.
    IBM Z Open DebugThis extension provides a Debugger user interface in Visual Studio Code for COBOL and other languages using the IBM Z Debugger. It consists of two extensions: the core IBM Z Open Debugopen in new window and the graphical IBM Z Open Debug Profiles viewopen in new window.
    Todo TreeThis is a popular extension for navigating and managing comment tags such as TODO in source code. To install this extension, see Todo Treeopen in new window.
    YAMLZ Open Editor uses YAML for configuration files such as ZAPP. The YAML extension provides comprehensive YAML language support to Visual Studio Code to read the JSON/YAML schema and provide code completion and validation. To install this extension, see YAMLopen in new window.
    Zowe Explorer Extension for FTPZowe Explorer is loaded by Z Open Editor and supports RSE API and z/OSMF, but if you want to use FTP as a transfer protocol, you can install Zowe Explorer Extension for FTPopen in new window.
    Zowe Explorer for IBM CICSThis CICS Extension for Zowe Explorer adds additional functionality to the popular Visual Studio Code extension, Zowe Explorer. This extension allows interactions with CICS regions and programs and provides the ability to run commands against them. To install this extension, see Zowe Explorer for IBM CICSopen in new window.
    Last Updated:
    Contributors: Peter Haumer, Chun Hong Zheng, ClaireZheng, PETER HAUMER
    - + diff --git a/Docs/privacypolicy.html b/Docs/privacypolicy.html index 18687de77..d8a9f0052 100644 --- a/Docs/privacypolicy.html +++ b/Docs/privacypolicy.html @@ -41,11 +41,11 @@ } )(); Privacy policy considerations | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Privacy policy considerations

    IBM® Software products, including software as a service solutions, ("Software Offerings”) may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user, or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering’s use of cookies is set forth below.

    This Software Offering does not use cookies or other technologies to collect personally identifiable information.

    If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent.

    For more information about the use of various technologies, including cookies, for these purposes, see IBM’s Privacy Policy at http://www.ibm.com/privacy and IBM’s Online Privacy Statement at http://www.ibm.com/privacy/details the section entitled "Cookies, Web Beacons and Other Technologies” and the "IBM Software Products and Software-as-a-Service Privacy Statement” at http://www.ibm.com/software/info/product-privacy.

    This doc site provides content search capability by using DocSearch by Algoliaopen in new window. For data that DocSearch collects, check DocSearch FAQopen in new window. This doc site is a subscriber of Aloglia's service, and you can refer to the applicable section of Privacy policy of Algoliaopen in new window.

    Last Updated:
    Contributors: Min Huang, Peter Haumer, enzi, shikunli
    - + diff --git a/Docs/rse_cli_command.html b/Docs/rse_cli_command.html index 2cc1a477c..0d3775069 100644 --- a/Docs/rse_cli_command.html +++ b/Docs/rse_cli_command.html @@ -41,11 +41,11 @@ } )(); IBM RSE API Plug-in for Zowe CLI commands | IBM Z® Open Editor - + -
    IBM Z® Open Editor

    IBM RSE API Plug-in for Zowe CLI commands

    Refer to the following tables for commands that are available in the IBM® RSE API Plug-in for Zowe™ CLI (RSE CLI plug-in) and their equivalent Zowe CLI z/OSMF commands.

    z/OS UNIX System Services

    RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version available
    zowe rse ls uss "/u/user"zowe files ls uss "/u/user"List z/OS UNIX System Services files using a path to search.v1.0.0
    zowe rse create file "/u/user/newFile"zowe files create file "/u/user/newFile"--modeCreate a z/OS UNIX System Services file. --mode states the permissions of the file. If permissions are not entered, the default will be rwxrw-r--.v1.0.0
    zowe rse create dir "/u/user/newDirectory"zowe files create dir "/u/user/newDirectory"--modeCreate a z/OS UNIX System Services directory. --mode states the permissions of the directory. If permissions are not entered, the default will be rwxrw-r--.v1.0.0
    zowe rse del uss "/u/user/fileName"zowe files del uss "/u/user/fileName"Delete z/OS UNIX System Services files.v1.0.0
    zowe rse del uss "/u/user/directoryName"zowe files del uss "/u/user/directoryName"Delete z/OS UNIX System Services directories or folders.v1.0.0
    zowe rse dl uf "/path/to/fileName"zowe files dl uf "/path/to/fileName"-f, -b, --ecDownload a file from the host to local. To download files to a specific location on local, specify the option -f followed by a path and file name of location on local. Specify -b for binary download. The --ec command is to specify an encoding.v1.0.0
    zowe rse ul ftu "localFile.txt" "/u/user/fileName"zowe files ul ftu "localFile.txt" "/u/user/fileName"-b, --ecUpload a local file to z/OS UNIX System Services. Specify -b for binary download. The --ec command is to specify an encoding on the host.v1.0.0
    zowe rse ul dtu "/path/to/localDir" "/path/to/dirName"zowe files ul dtu "/path/to/localDir" "/path/to/dirName"-r, -b, --ecUpload a directory to z/OS UNIX System Services. To upload the directory recursively, specify the option -r. Specify -b for binary download. The --ec command is to specify an encoding on the host.v1.0.0
    zowe rse rename uss "/u/user/fileName" "newFileName"Rename a z/OS UNIX System Services file or directory.v1.0.0
    zowe rse change properties "/u/user/fileName"--owner, --group, --permissionChange properties of a z/OS UNIX System Services file or directory.v1.1.3
    zowe rse search uss "/u/user/fileName" "fileName"N/A--text, --regex-file-name, --regex-content, --case-sensitive-file-name, --case-sensitive-content, --path-results-onlySearch for UNIX files by specifying the path, file name, and text pattern.v1.1.4
    zowe rse change clear-tag "/u/user/fileName.txt"N/AClear the tag of the UNIX file specified.v1.0.1

    MVS

    RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version available
    zowe rse ls ds filterzowe files ls ds filter-aList data sets by using a filter to search, for example, name, name.*. To list the data set's attributes, specify the option -a.v1.0.0
    zowe rse ls am "hlq.dsname"zowe files ls am "hlq.dsname"--patternList all members of a PDS by using the data set name to search. The --pattern tag can be used for a member filter search on the data set.--pattern available with v1.0.1
    zowe rse create ds "hlq.dsname" --like "hlq.originaldszowe files create ds "hlq.dsname" --like "hlq.originalds--bs, --db, --dt, --rf, --rl, --ss, --vs, --au, --ab, --psAllocate a data set like another data set. Options include: block size (bs), device type (dt), directory blocks (db), record format (rf), record length (rl), secondary space (ss), allocation unit (au), average block (ab), primary (ps), and volume serial (vs). If no options are specified to overwritten, all attributes from the like data set will be used.v1.0.7
    zowe rse create ps "hlq.dsname"zowe files create ps "hlq.dsname"--bs, --db, --dt, --rf, --rl, --ss, --vs, --au, --ab, --psCreate a sequential data set (PS). Options include: block size (bs), device type (dt), directory blocks (db), record format (rf), record length (rl), secondary space (ss), allocation unit (au), average block (ab), primary (ps), and volume serial (vs). If no options are specified, a default option will be used.v1.0.0
    zowe rse create pds "hlq.dsname"zowe files create pds "hlq.dsname"--bs, --db, --dt, --rf, --rl, --ss, --vs, --au, --ab, --psCreate a partitioned data set (PO). Options include: block size (bs), device type (dt), directory blocks (db), record format (rf), record length (rl), secondary space (ss), allocation unit (au), average block (ab), primary (ps), and volume serial (vs). If no options are specified, a default option will be used.v1.0.0
    zowe rse create member "hlq.dsname(newmember)"Create a member for a partitioned data set.v1.0.0
    zowe rse del ds "hlq.dsname"zowe files del ds "hlq.dsname"Delete sequential (PS) and partitioned (PO) data sets or members.v1.0.0
    zowe rse dl ds "hlq.dsname(member)"zowe files dl ds "hlq.dsname(member)"-f, -b, --ec, -e, --mappings-fileDownload a PS data set or a single member of a PO data set from the host to local. Specify -f to indicate the path on local to download to. Specify -e to indicate the extension of the file downloaded on local; if the extension is not indicated, the file will be saved as a text file. Specify -b for binary download. The --ec command is to specify an encoding. The --mappings-file tag will specify location of a non-default mappings file.-b available with v1.0.3
    zowe rse dl am "hlq.dsname"zowe files dl am "hlq.dsname"-d, -b, --ec, -e, --mappings-fileDownload all members of a PO data set from the host to local. Specify -d to indicate the directory on local to download to. Specify -e to indicate the extension of the file downloaded on local; if the extension is not indicated, the file will be saved as a text file. Specify -b for binary download. The --ec command is to specify an encoding. The --mappings-file tag will specify location of a non-default mappings file.-b available with v1.0.3
    zowe rse ul ftds "localFile.txt" "hlq.dsname"zowe files ul ftds "localFile.txt" "hlq.dsname"--ec, -b, --mappings-fileUpload a local file to the host as a data set. The --ec command is to specify an encoding on the host. Specify -b for binary upload. The --mappings-file tag will specify location of a non-default mappings file.v1.0.0
    zowe rse ul dtp "localDirectory" "hlq.dsname"zowe files ul dtp "localDirectory" "hlq.dsname"--ec, -b, --mappings-fileUpload a directory to a PDS. The --ec command is to specify an encoding on the host. Specify -b for binary upload. The --mappings-file tag will specify location of a non-default mappings file.v1.0.0
    zowe rse rename data-set "hlq.dsname" "hlq.newdsname"Rename a data set.v1.0.0
    zowe rse rename data-set-member "hlq.dsname(memberName)" "newMemberName"Rename a data set member.v1.0.0
    zowe rse migrate data-set "hlq.dsname"zowe files migrate data-set "hlq.dsname"Migrate data sets.v1.0.0
    zowe rse recall data-set "hlq.dsname"zowe files recall data-set "hlq.dsname"Recall migrated data sets.v1.0.0
    zowe rse copy data-set fromDataSetName toDataSetNamezowe files copy data-set fromDataSetName toDataSetNameCopy a data set or data set member to another data set.v1.0.3

    JES

    RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version available
    zowe rse ls jszowe jobs ls js-o, -p, -s, -aList jobs on JES spool or queues. The option -o indicates the owner of the jobs. The option -p indicates the job's name prefix. The option -s indicates the status of the listed jobs (ALL, ACTIVE, OUTPUT, or INPUT). The option -a shows the additional job attributes of the listed jobs.v1.0.0
    zowe rse ls sfbj "jobId"zowe jobs ls sfbj "jobId"List the spool files (DDs) for a z/OS® job on the JES or spool queues for a z/OS job ID.v1.0.0
    zowe rse delete job "jobId"zowe jobs delete job "jobId"Delete a single job by job ID.v1.0.0
    zowe rse dl o "jobId"zowe jobs dl o "jobId"-d, -e, --ojdDownload job output by job ID. Use the option -d to specify a local directory for the download. Use the option -e to specify a files extension to save the job output with. Use the option --ojd to save the output directly to the specified directory without creating a subdirectory named after the ID of the job.v1.0.0
    zowe rse submit data-set "hlq.datasetName(jclMember)zowe jobs submit data-set "hlq.datasetName(jclMember)--wfo , --wfa , --vasc , -d , -e, --jsSubmit a JCL job contained in a data set. The data set can be physical sequential or a PDS member.--js available with v1.0.9
    zowe rse submit local-file "path/to/local/file"zowe jobs submit local-file "path/to/local/file"--wfo , --wfa , --vasc , -d , -e, --jsSubmit a JCL job contained in a local file.--js available with v1.0.9
    zowe rse submit stdinzowe jobs submit stdin--wfo , --wfa , --vasc , -d , -e, --jsSubmit a JCL job passed to the command via the stdin stream.--js available with v1.0.9
    zowe rse view job-status-by-jobid JOB00123zowe jobs view job-status-by-jobid JOB00123-aView status details of a single z/OS job on spool or JES queues. The option -a shows the additional job attributes of the job.v1.0.0
    zowe rse view spool-file-by-id JOB00123 4zowe jobs view spool-file-by-id JOB00123 4View the contents of a spool file from a z/OS job on spool or JES queues.v1.0.0
    zowe rse cancel job JOB03456zowe jobs cancel job JOB03456Cancel a single job by job ID.v1.0.0

    System

    RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version availablez/OS Explorer version available
    zowe rse check statuszowe zosmf check statusGet system and API information.v1.0.1v3.1.1.26
    zowe rse auth loginzowe auth loginLog in to an authentication service to obtain a JSON Web Token.v1.0.0v3.1.1.26
    zowe rse auth queryGet back JSON Web Token information if it is not yet expired.v1.0.0v3.1.1.26
    zowe rse auth logoutzowe auth logoutLog out of the authentication service and retire the JSON Web Token.v1.0.3v3.1.1.26
    zowe rse issue command "<COMMAND>"zowe tso issue command "<COMMAND>"--shell-idIssue a TSO command. The --shell-id tag allows interactive TSO commands using an Interactive ISPF Gatewayopen in new window.v1.0.1, --shell-id available v1.0.8v3.1.1.26
    zowe rse issue unix "<COMMAND>" --cwd "/uss/path/toIssue"Issue a UNIX command.v1.0.0v3.1.1.26
    zowe rse issue unix-shell "<COMMAND>" --cwd "/uss/path/toIssue"--envIssue a UNIX command with streaming output. Use the option --env to specify a comma-separated list of environment variables for the executing shell.v1.0.5v3.2.0.16
    zowe rse check conversion-mappingsDownload Mappings file from RSE API server.v1.0.3v3.1.1.26
    zowe rse change password currentPassword newPasswordChange z/OS User Password on the Host and update profile's yaml if saved locally.v1.0.2v3.1.1.26
    zowe rse check system-address-spaceDisplay active system address space information.v1.0.5v3.2.0.16
    zowe rse check job-address-space--asid, --asidx, --bytes, --cpu, --cpu%, --description, --dp, --elapsed, --frames, --hvcomhwm, --hvcomused, --io, --name, --page, --position, --stepio, --subtype, --swapin, --sysName, --task, --task%, --type, --userIdDisplay all active job address space information. Option tags are used to filter the returned list of data.v1.0.5, filter options: v1.0.9v3.2.0.16
    zowe rse check password-expiryDisplays expiration date of user id's password.v1.1.2v3.1.1.26

    RSE Common Properties

    RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version available
    zowe rse cm copy "global-ns" "backup-ns"--privateCopy a Common Properties namespace. Use the option --private to specify for private namespace.v1.1.3
    zowe rse cm create "global-ns"--privateCreate a Common Properties namespace. Use the option --private to specify for private namespace.v1.1.3
    zowe rse cm delete "global-ns" --path "/path/to/property"--path, --privateDelete a Common Properties namespace, or delete a property in the namespace indicated by the --path option. Use the option --private to specify for private namespace.v1.1.3
    zowe rse cm list--privateList all Common Properties namespaces. Use the option --private to specify for private namespace.v1.1.3
    zowe rse cm rename "global-ns" "backup-ns"--privateRename a Common Properties namespace. Use the option --private to specify for private namespace.v1.1.3
    zowe rse cm set "global-ns" "/path/to/property" "some-value"--private, --value-typeSet a property in the namespace. If the value is not a simple string but a number, boolean or JSON string, use --value-type to specify the type. Use the option --private to specify for private namespace.v1.1.3
    zowe rse cm view "global-ns" --path "/path/to/property"--path, --privateView all properties in a Common Properties namespace, or a property in the namespace specified by the --path option. Use the option --private to specify for private namespace.v1.1.3
    Last Updated:
    Contributors: Billie Simmons, Billie Simmons, Billie Jean Simmons, Rudy Leonel Pichola Flores, Lauren Li, Min Huang, Patrick Tiu, Alvin So, Billie, Chun Hong Zheng, Hestia Zhang, Nimma Likhitha, Rudy Pichola Flores, Shi Kun Li, shikunli
    - +
    IBM Z® Open Editor

    IBM RSE API Plug-in for Zowe CLI commands

    Refer to the following tables for commands that are available in the IBM® RSE API Plug-in for Zowe™ CLI (RSE CLI plug-in) and their equivalent Zowe CLI z/OSMF commands.

    z/OS UNIX System Services

    RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version available
    zowe rse ls uss "/u/user"zowe files ls uss "/u/user"List z/OS UNIX System Services files using a path to search.v1.0.0
    zowe rse create file "/u/user/newFile"zowe files create file "/u/user/newFile"--modeCreate a z/OS UNIX System Services file. --mode states the permissions of the file. If permissions are not entered, the default will be rwxrw-r--.v1.0.0
    zowe rse create dir "/u/user/newDirectory"zowe files create dir "/u/user/newDirectory"--modeCreate a z/OS UNIX System Services directory. --mode states the permissions of the directory. If permissions are not entered, the default will be rwxrw-r--.v1.0.0
    zowe rse del uss "/u/user/fileName"zowe files del uss "/u/user/fileName"Delete z/OS UNIX System Services files.v1.0.0
    zowe rse del uss "/u/user/directoryName"zowe files del uss "/u/user/directoryName"Delete z/OS UNIX System Services directories or folders.v1.0.0
    zowe rse dl uf "/path/to/fileName"zowe files dl uf "/path/to/fileName"-f, -b, --ec,--lcDownload a file from the host to local. To download files to a specific location on local, specify the option -f followed by a path and file name of location on local. Specify -b for binary download. The --ec command is to specify an encoding. The --lc command is to specify local encoding.v1.0.0
    zowe rse ul ftu "localFile.txt" "/u/user/fileName"zowe files ul ftu "localFile.txt" "/u/user/fileName"-b, --ec,--lcUpload a local file to z/OS UNIX System Services. Specify -b for binary download. The --ec command is to specify an encoding on the host. The --lc command is to specify local encoding.v1.0.0
    zowe rse ul dtu "/path/to/localDir" "/path/to/dirName"zowe files ul dtu "/path/to/localDir" "/path/to/dirName"-r, -b, --ec, --lcUpload a directory to z/OS UNIX System Services. To upload the directory recursively, specify the option -r. Specify -b for binary download. The --ec command is to specify an encoding on the host. The --lc command is to specify local encoding.v1.0.0
    zowe rse rename uss "/u/user/fileName" "newFileName"Rename a z/OS UNIX System Services file or directory.v1.0.0
    zowe rse change properties "/u/user/fileName"--owner, --group, --permissionChange properties of a z/OS UNIX System Services file or directory.v1.1.3
    zowe rse search uss "/u/user/fileName" "fileName"N/A--text, --regex-file-name, --regex-content, --case-sensitive-file-name, --case-sensitive-content, --path-results-onlySearch for UNIX files by specifying the path, file name, and text pattern.v1.1.4
    zowe rse change clear-tag "/u/user/fileName.txt"N/AClear the tag of the UNIX file specified.v1.1.4
    zowe rse convert unix-file-encoding "/u/user/fileName.txt" 'hostEncoding' 'targetEncoding'N/AConverts the encoding of the specified Unix file to target encoding.v1.0.1

    MVS

    RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version available
    zowe rse ls ds filterzowe files ls ds filter-aList data sets by using a filter to search, for example, name, name.*. To list the data set's attributes, specify the option -a.v1.0.0
    zowe rse ls am "hlq.dsname"zowe files ls am "hlq.dsname"--patternList all members of a PDS by using the data set name to search. The --pattern tag can be used for a member filter search on the data set.--pattern available with v1.0.1
    zowe rse create ds "hlq.dsname" --like "hlq.originaldszowe files create ds "hlq.dsname" --like "hlq.originalds--bs, --db, --dt, --rf, --rl, --ss, --vs, --au, --ab, --psAllocate a data set like another data set. Options include: block size (bs), device type (dt), directory blocks (db), record format (rf), record length (rl), secondary space (ss), allocation unit (au), average block (ab), primary (ps), and volume serial (vs). If no options are specified to overwritten, all attributes from the like data set will be used.v1.0.7
    zowe rse create ps "hlq.dsname"zowe files create ps "hlq.dsname"--bs, --db, --dt, --rf, --rl, --ss, --vs, --au, --ab, --psCreate a sequential data set (PS). Options include: block size (bs), device type (dt), directory blocks (db), record format (rf), record length (rl), secondary space (ss), allocation unit (au), average block (ab), primary (ps), and volume serial (vs). If no options are specified, a default option will be used.v1.0.0
    zowe rse create pds "hlq.dsname"zowe files create pds "hlq.dsname"--bs, --db, --dt, --rf, --rl, --ss, --vs, --au, --ab, --psCreate a partitioned data set (PO). Options include: block size (bs), device type (dt), directory blocks (db), record format (rf), record length (rl), secondary space (ss), allocation unit (au), average block (ab), primary (ps), and volume serial (vs). If no options are specified, a default option will be used.v1.0.0
    zowe rse create member "hlq.dsname(newmember)"Create a member for a partitioned data set.v1.0.0
    zowe rse del ds "hlq.dsname"zowe files del ds "hlq.dsname"Delete sequential (PS) and partitioned (PO) data sets or members.v1.0.0
    zowe rse dl ds "hlq.dsname(member)"zowe files dl ds "hlq.dsname(member)"-f, -b, --ec, -e, --mappings-file,--lcDownload a PS data set or a single member of a PO data set from the host to local. Specify -f to indicate the path on local to download to. Specify -e to indicate the extension of the file downloaded on local; if the extension is not indicated, the file will be saved as a text file. Specify -b for binary download. The --ec command is to specify an encoding. The --lc command is to specify local encoding. The --mappings-file tag will specify location of a non-default mappings file.-b available with v1.0.3
    zowe rse dl am "hlq.dsname"zowe files dl am "hlq.dsname"-d, -b, --ec, -e, --mappings-file, --lcDownload all members of a PO data set from the host to local. Specify -d to indicate the directory on local to download to. Specify -e to indicate the extension of the file downloaded on local; if the extension is not indicated, the file will be saved as a text file. Specify -b for binary download. The --ec command is to specify an encoding. The --mappings-file tag will specify location of a non-default mappings file. The --lc command is to specify local encoding.-b available with v1.0.3
    zowe rse ul ftds "localFile.txt" "hlq.dsname"zowe files ul ftds "localFile.txt" "hlq.dsname"--ec, -b, --mappings-file,--lcUpload a local file to the host as a data set. The --ec command is to specify an encoding on the host. Specify -b for binary upload. The --mappings-file tag will specify location of a non-default mappings file. The --lc command is to specify local encoding.v1.0.0
    zowe rse ul dtp "localDirectory" "hlq.dsname"zowe files ul dtp "localDirectory" "hlq.dsname"--ec, -b, --mappings-file, --lcUpload a directory to a PDS. The --ec command is to specify an encoding on the host. Specify -b for binary upload. The --mappings-file tag will specify location of a non-default mappings file. The --lc command is to specify local encoding.v1.0.0
    zowe rse rename data-set "hlq.dsname" "hlq.newdsname"Rename a data set.v1.0.0
    zowe rse rename data-set-member "hlq.dsname(memberName)" "newMemberName"Rename a data set member.v1.0.0
    zowe rse migrate data-set "hlq.dsname"zowe files migrate data-set "hlq.dsname"Migrate data sets.v1.0.0
    zowe rse recall data-set "hlq.dsname"zowe files recall data-set "hlq.dsname"Recall migrated data sets.v1.0.0
    zowe rse copy data-set fromDataSetName toDataSetNamezowe files copy data-set fromDataSetName toDataSetNameCopy a data set or data set member to another data set.v1.0.3
    zowe rse copy data-set-cross-lpar fromDataSetName toDataSetNamezowe files copy data-set-cross-lpar fromDataSetName toDataSetName--target-host, --target-port, --target-user, --target-password, --target-rse-p, --replaceCopy a data set or data set member to another data set on the same or different LPAR. Specify --target-host, --target-port, --target-user, --target-password for the target LPAR. Specify --target-rse-p for the target rse profile. Specify --replace in order to replace the existing targetDataset.v1.0.3

    JES

    RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version available
    zowe rse ls jszowe jobs ls js-o, -p, -s, -aList jobs on JES spool or queues. The option -o indicates the owner of the jobs. The option -p indicates the job's name prefix. The option -s indicates the status of the listed jobs (ALL, ACTIVE, OUTPUT, or INPUT). The option -a shows the additional job attributes of the listed jobs.v1.0.0
    zowe rse ls sfbj "jobId"zowe jobs ls sfbj "jobId"List the spool files (DDs) for a z/OS® job on the JES or spool queues for a z/OS job ID.v1.0.0
    zowe rse delete job "jobId"zowe jobs delete job "jobId"Delete a single job by job ID.v1.0.0
    zowe rse dl o "jobId"zowe jobs dl o "jobId"-d, -e, --ojdDownload job output by job ID. Use the option -d to specify a local directory for the download. Use the option -e to specify a files extension to save the job output with. Use the option --ojd to save the output directly to the specified directory without creating a subdirectory named after the ID of the job.v1.0.0
    zowe rse submit data-set "hlq.datasetName(jclMember)zowe jobs submit data-set "hlq.datasetName(jclMember)--wfo , --wfa , --vasc , -d , -e, --jsSubmit a JCL job contained in a data set. The data set can be physical sequential or a PDS member.--js available with v1.0.9
    zowe rse submit local-file "path/to/local/file"zowe jobs submit local-file "path/to/local/file"--wfo , --wfa , --vasc , -d , -e, --jsSubmit a JCL job contained in a local file.--js available with v1.0.9
    zowe rse submit stdinzowe jobs submit stdin--wfo , --wfa , --vasc , -d , -e, --jsSubmit a JCL job passed to the command via the stdin stream.--js available with v1.0.9
    zowe rse view job-status-by-jobid JOB00123zowe jobs view job-status-by-jobid JOB00123-aView status details of a single z/OS job on spool or JES queues. The option -a shows the additional job attributes of the job.v1.0.0
    zowe rse view spool-file-by-id JOB00123 4zowe jobs view spool-file-by-id JOB00123 4View the contents of a spool file from a z/OS job on spool or JES queues.v1.0.0
    zowe rse cancel job JOB03456zowe jobs cancel job JOB03456Cancel a single job by job ID.v1.0.0

    System

    RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version availablez/OS Explorer version available
    zowe rse check statuszowe zosmf check statusGet system and API information.v1.0.1v3.1.1.26
    zowe rse auth loginzowe auth loginLog in to an authentication service to obtain a JSON Web Token.v1.0.0v3.1.1.26
    zowe rse auth queryGet back JSON Web Token information if it is not yet expired.v1.0.0v3.1.1.26
    zowe rse auth logoutzowe auth logoutLog out of the authentication service and retire the JSON Web Token.v1.0.3v3.1.1.26
    zowe rse issue command "<COMMAND>"zowe tso issue command "<COMMAND>"--shell-idIssue a TSO command. The --shell-id tag allows interactive TSO commands using an Interactive ISPF Gatewayopen in new window.v1.0.1, --shell-id available v1.0.8v3.1.1.26
    zowe rse issue unix "<COMMAND>" --cwd "/uss/path/toIssue"Issue a UNIX command.v1.0.0v3.1.1.26
    zowe rse issue unix-shell "<COMMAND>" --cwd "/uss/path/toIssue"--envIssue a UNIX command with streaming output. Use the option --env to specify a comma-separated list of environment variables for the executing shell.v1.0.5v3.2.0.16
    zowe rse check conversion-mappingsDownload Mappings file from RSE API server.v1.0.3v3.1.1.26
    zowe rse change password currentPassword newPasswordChange z/OS User Password on the Host and update profile's yaml if saved locally.v1.0.2v3.1.1.26
    zowe rse check system-address-spaceDisplay active system address space information.v1.0.5v3.2.0.16
    zowe rse check job-address-space--asid, --asidx, --bytes, --cpu, --cpu%, --description, --dp, --elapsed, --frames, --hvcomhwm, --hvcomused, --io, --name, --page, --position, --stepio, --subtype, --swapin, --sysName, --task, --task%, --type, --userIdDisplay all active job address space information. Option tags are used to filter the returned list of data.v1.0.5, filter options: v1.0.9v3.2.0.16
    zowe rse check password-expiryDisplays expiration date of user id's password.v1.1.2v3.1.1.26

    RSE Common Properties

    RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version available
    zowe rse cm copy "global-ns" "backup-ns"--privateCopy a Common Properties namespace. Use the option --private to specify for private namespace.v1.1.3
    zowe rse cm create "global-ns"--privateCreate a Common Properties namespace. Use the option --private to specify for private namespace.v1.1.3
    zowe rse cm delete "global-ns" --path "/path/to/property"--path, --privateDelete a Common Properties namespace, or delete a property in the namespace indicated by the --path option. Use the option --private to specify for private namespace.v1.1.3
    zowe rse cm list--privateList all Common Properties namespaces. Use the option --private to specify for private namespace.v1.1.3
    zowe rse cm rename "global-ns" "backup-ns"--privateRename a Common Properties namespace. Use the option --private to specify for private namespace.v1.1.3
    zowe rse cm set "global-ns" "/path/to/property" "some-value"--private, --value-typeSet a property in the namespace. If the value is not a simple string but a number, boolean or JSON string, use --value-type to specify the type. Use the option --private to specify for private namespace.v1.1.3
    zowe rse cm view "global-ns" --path "/path/to/property"--path, --privateView all properties in a Common Properties namespace, or a property in the namespace specified by the --path option. Use the option --private to specify for private namespace.v1.1.3
    Last Updated:
    Contributors: Billie Simmons, Billie Simmons, Nimma Likhitha, Billie Jean Simmons, Rudy Leonel Pichola Flores, Lauren Li, Min Huang, Patrick Tiu, Alvin So, Benjamin Santos, Billie, Chun Hong Zheng, Hestia Zhang, Rudy Pichola Flores, Shi Kun Li, shikunli
    + diff --git a/Docs/rse_tutorial.html b/Docs/rse_tutorial.html index 2fd8052d1..43e001094 100644 --- a/Docs/rse_tutorial.html +++ b/Docs/rse_tutorial.html @@ -41,7 +41,7 @@ } )(); Managing z/OS resources with IBM RSE API Plug-in for Zowe CLI tutorial | IBM Z® Open Editor - + @@ -70,6 +70,6 @@

  • When the status of the job is complete, download the files that result from the job with the following commands:

    zowe rse download data-set "HLQ.SAMPLE.CUSTOUT"
 zowe rse download data-set "HLQ.SAMPLE.CUSTRPT"

    To see the downloaded files enter the command ls (Mac) or dir (Windows).

    • Approach 3: Using a script to automate command-line operations against z/OS resources

    You can do the same actions as described in approach 1 in a shell script. This section describes how to create and use the script.

    1. Edit the ALLOCATE.jcl file on line 16 and set the HLQ.

    2. Perform the same modification to the RUN.jcl on line 30 and set the HLQ with the same one used in ALLOCATE.jcl. You might or might not need to modify the other symbolics depending on the compile and link libraries your host system uses. You might or might not change the SPACE1 and SPACE2 symbolics, and save the file.

    3. The script zowecli-cobol-upload-run-tutorial.sh is located in the SCRIPTS directory of the cloned repo. Edit the HLQ variable in the code on line 12 to match the modification to the JCL files.

    4. Open a terminal in VS Code and enter SCRIPTS/zowecli-cobol-upload-run-tutorial.sh.

      Using Command Line Operations in a Script

    Alternatively, you can run this script with Zowe CLI, which uses z/OSMF on the host instead of RSE API. To adapt the script for use in Zowe CLI, change the values of the variables FILES_CMD and JOBS_CMD in the script to the following:

    The RSE CLI plug-in also has support for Interactive TSO commands, you can read more about this under Run interactive TSO commands.

    - + diff --git a/Docs/samplefiles.html b/Docs/samplefiles.html index 49d792514..c667bf4bf 100644 --- a/Docs/samplefiles.html +++ b/Docs/samplefiles.html @@ -41,12 +41,12 @@ } )(); Exploring the sample files | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Exploring the sample files

    Within this documentation we refer to a set of sample files that you can use to explore the editor features. These samples are provided on Github.com.

    Get the sample files

    Assuming that you have Git installed as described in the Prerequisites, create a work directory somewhere on your machine and clone the sample repository:

    git clone https://github.com/IBM/zopeneditor-sample.git

    Then open the directory zopeneditor-sample using the File > Open... menu. The sample files in this directory will be referred to throughout the rest of the documentation.

    Understand the Git repository branches

    The sample Git repository contains seven branches with variants of our sample programs for different evaluation use cases.

    • main: provides code and configuration file examples that can be used with the basic IBM Z Open Editor installation obtains from the VS Code Marketplace.
    • tutorial_complete: extends the examples from the main branch with code changes that you can use to simulate a before and after view of making changes to source code.
    • wazi-main: provides additional configuration file examples for commercial extensions to IBM Z Open Editor such as IBM Open Debug, User Build with IBM Dependency-Based Build, Red Hat Ansible Certified Content for IBM Z collection, and GitLab CI. The IBM Documentationopen in new window has more details for using these tools and examples.
    • wazi-tutorial-complete: provides an after-changes-view of the examples in wazi-main with the same advanced configurations files.
    • devfile: contains a variant of wazi-main that can be used in Red Hat's Dev Spaces for OpenShift v3 environment. See a tutorial for trying Z Open Editor running in Dev Spaces on Red Hat's free Developer Sandbox in our GitHub repositoryopen in new window.

    Examine the sample files

    The sample application in the main and tutorial-complete branches consists of the following files:

    • COBOL programs: SAM1, SAM2, and SAM1LIB

      SAM1 reads in both the CUSTFILE and TRANFILE data files, and then performs different actions on the CUSTFILE based on transactions from the TRANFILE. Valid transactions are ADD, UPDATE, and DELETE. When an UPDATE transaction is processed, SAM1 calls SAM2 to perform the requested update.

      SAM2 includes some base code in place for CRUNCH transactions, which can be enhanced using Instructions provided later in this document . At the end of processing the TRANFILE, SAM1 generates a report on the transactions processed and produces an updated CUSTFILE.

      SAM1LIB is included to demonstrate the editor's ability to resolve copybooks that are part of a library. It is a copy of SAM1 with the exception of the library-based copybooks.

    • Copybooks: CUSTCOPY, REGISTRS, and TRANREC

    • Libraries Copybooks: DATETIME (local) and REPTTOTL (MVS). These copybooks demonstrate using the libraries option in a COPY <copybook> IN <library> statement for local and MVS copybooks

    • PL/I programs: PSAM1, PSAM2, and PSAM1LIB

      PSAM1 reads in both the PLI.CUSTFILE and PLI.TRANFILE data files, and then produces a report with customer information and a Totals summary section. Valid transactions are PRINT and TOTALS. A PRINT transaction prints the Customer records to the Customer section of the report. When PSAM1 reads in a TOTALS transaction, it generates the Totals Report section. The instructions, provided later in this document, guide you through making the necessary code changes to allow PSAM1 to process a new type of Customer record called a Product record and generate a new line for the Service Calls in the Totals Report section.

      PSAM1LIB is included to demonstrate the editor's ability to resolve includes that are part of a library. It is a copy of PSAM1 with the exception of the library-based includes.

    • Include files: BALSTATS and CUSTPLI

    • Libraries Includes: DATETIME (local) and REPTTOTL (MVS) - these includes demonstrate using the libraries option in an %INCLUDE <library> (<include>); statement for local and MVS includes

    • HLASM programs: ASAM1 and ASAM2

      ASAM1 reads the ASM.FILEIN data file and will write out the record number, column number heading records, and the input string to ASM.FILEOUT. Instructions provided later in this document will guide you through making the necessary code changes to have ASAM1 call ASAM2 which will take the input string, convert it to hexadecimal format and pass it back to ASAM1, which will then write the hex value for the string to the ASM.FILEOUT data file.

    • REXX program: RSAM1

      RSAM1 reads the REXX.FILEIN1 and REXX.FILEIN2 data files and will write out the records to REXX.FILEOUT. Instructions provided later in this document will guide you through making the necessary code changes to create a new subroutine in RSAM1 to have it read through REXX.FILEOUT and display all of the records.

    • JCL members that set up and run the applications: ALLOCATE, RUN, PLIALLOC, RUNPSAM1, ASMALLOC, RUNASAM1, and REXALLOC.

    • Data source files: CUSTFILE, TRANFILE, PLI.TRANFILE, PLI.CUSTFILE, ASM.FILEIN, REXX.FILEIN1, and REXX.FILEIN2.

    • Script Files:

      • zowecli-create-profiles.sh - This shell script will create Zowe CLI RSE and SSH profiles and then set them as the default profiles.

        • Parameters necessary to run the script:
          • TSO USER ID and Password
          • Z host address
          • RSE API port number
          • SSH port number

      • zowecli-cobol-upload-run-simple.sh - This shell script will run the sample COBOL application.

        • Submits the JCL to allocate the required MVS datasets
        • Uploads the application components from the local directory to the MVS datasets
        • Submits the JCL to run the application

      • zowecli-cobol-upload-run-tutorial.sh - This shell script will run the sample COBOL application and download the output files.

        • Submits the JCL to allocate the required MVS datasets
        • Uploads the application components from the local directory to the MVS datasets
        • Submits the JCL to run the application
        • Downloads the output data files once the JES job is complete

      • zowecli-cobol-clean.sh - This shell script will delete the MVS data sets allocated and created during the execution of the sample application.

    Last Updated:
    Contributors: Shi Kun Li, Greg Lambert, Lauren Li, Peter Haumer, Peter Haumer, Greg Lambert, Gregory Lambert, Hestia Zhang, Kimberlee Maselli, Lauren K Li, PETER HAUMER, kmaselli
    - + diff --git a/Docs/setting_compiler_options.html b/Docs/setting_compiler_options.html index 668f1f32c..359efa9b9 100644 --- a/Docs/setting_compiler_options.html +++ b/Docs/setting_compiler_options.html @@ -41,7 +41,7 @@ } )(); Setting compiler options | IBM Z® Open Editor - + @@ -71,6 +71,6 @@ compilerOptions: "OR(|)"

    After proper definition, you are ready to use your custom OR symbol in your program. For example:

        if (xyz | yz)

    References

    - + diff --git a/Docs/setting_disableproblems.html b/Docs/setting_disableproblems.html index 8cd5be7f0..ce6d28471 100644 --- a/Docs/setting_disableproblems.html +++ b/Docs/setting_disableproblems.html @@ -41,12 +41,12 @@ } )(); Enabling and disabling problems in IBM Z Open Editor | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Enabling and disabling problems in IBM Z Open Editor

    IBM Z Open Editor performs real-time syntax checking and provides annotations that describe problems or errors in COBOL, HLASM, PL/I, REXX, and JCL code:

    • To see the annotations that describe a specific error, hover over the red underlined code in the editor.
    • To see annotations for all errors and warnings for all opened editors, open the Problems view by pressing Ctrl+Shift+M (on Windows) or Cmd+Shift+M (on Mac).

    You can enable or disable the showing of problems in your programs when you are maintaining other language features by using the settings provided by IBM Z Open Editor. The showing of problems is enabled by default. To disable the showing of problems in a specific language, specify the following preference setting:

    "zopeneditor.<language>.disableProblems": true

    Note: Disabling COBOL's problems will also disable unreachable code warnings. For more information, see Enabling and disabling unreachable COBOL code warnings.

    Last Updated:
    Contributors: Ethan Mendel, Chun Hong Zheng, Prasang Prajapati
    - + diff --git a/Docs/setting_fileassociations.html b/Docs/setting_fileassociations.html index 5ab9c8c0f..ca80c76d4 100644 --- a/Docs/setting_fileassociations.html +++ b/Docs/setting_fileassociations.html @@ -41,7 +41,7 @@ } )(); Setting file associations | IBM Z® Open Editor - + @@ -102,6 +102,6 @@ "*.REXXINC*": "rexx" }

    Again, if you prefer COPYBOOK data sets be opened as hlasm data sets, you can designate that in this setting.

    The resulting behavior for Zowe Explorer is now that using these settings, you can navigate to an MVS data set that matches these patterns and select a member, which is then opened in Z Open Editor in the mapped language. To achieve that Zowe Explorer downloads the file into a temporary directory that contains the mapped data set name pattern as well and opens it in the correct language, because of the files.associations mapping pattern. When you save these local files with changes Zowe Explorer will automatically write them back to MVS. When you quit the editor then Zowe Explorer will delete all temporary files for you source code security.

    - + diff --git a/Docs/setting_maximum_line_length.html b/Docs/setting_maximum_line_length.html index 38d650f31..5de546389 100644 --- a/Docs/setting_maximum_line_length.html +++ b/Docs/setting_maximum_line_length.html @@ -41,7 +41,7 @@ } )(); Setting language-specific maximum line length | IBM Z® Open Editor - + @@ -52,6 +52,6 @@

    The default maximum line length setting for HLASM is 80.

    Setting the REXX maximum line length

    To configure the REXX maximum line length, add zopeneditor.rexx.maximumLineLength in settings.json and provide 0-based column number to your user or workspace settings:

    "zopeneditor.rexx.maximumLineLength": 80

    The default maximum line length setting for REXX is 80.

    Setting the JCL maximum line length

    To configure the JCL maximum line length, add zopeneditor.jcl.maximumLineLength in settings.json and provide 0-based column number to your user or workspace settings:

    "zopeneditor.jcl.maximumLineLength": 80

    The default maximum line length setting for JCL is 80.

    - + diff --git a/Docs/setting_preferences.html b/Docs/setting_preferences.html index d6c6b241d..7adb62bbc 100644 --- a/Docs/setting_preferences.html +++ b/Docs/setting_preferences.html @@ -41,11 +41,11 @@ } )(); Setting preferences | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Setting preferences

    Before using IBM Z Open Editor, you can set preferences to control the characteristics of your environment. Preferences can be defined in various places depending on their scope - from user-specific settings to team project settings for files being edited. Z Open Editor distinguishes between settings provided via VS Code Preferences with settings provided in ZAPP files that are scoped to the application level and stored with your source code files. Application-specific settings, such as build flags, are typically shared with your team in ZAPP files. Personal settings, such as which Zowe profile to use for the user build, are usually in VS Code user settings.

    Accessing VS Code settings for IBM Z® Open Editor

    To open the settings for IBM Z Open Editor in VS Code, follow the steps below:

    1. In VS Code, open Settings.

      • On Windows, click File > Preferences > Settings.
      • On Mac, click Code > Preferences > Settings.

    2. To display the setting options for IBM Z Open Editor, expand the Extensions dropdown in the list on the left. Click on the entry IBM Z Open Editor.

    3. All the preferences shown in the visual editor are represented as JSON. Complex preferences that are not just simple values must be entered by using the JSON editor itself. To open it, select the scope tab first: User tab or Workspace tab, and then open the JSON view by clicking Edit in settings.json, or by clicking on the Open Settings (JSON) icon on the upper-right of the editor.

    VS Code user preferences versus workspace preferences

    In the editor panel, a list of preference groups is displayed, along with editor tabs for both the User and Workspace Preferences. Switch between these tabs to decide in which scope you want to add a preference.

    User preferences

    User preferences apply to the current user across different workspaces. They include not only typical user preferences related to accessibility, such as font sizes and editor behavior for code completion, but also Zowe Profiles defining z/OS® host connection information and personal high-level qualifiers. The settings are stored for the user in their home directory, apply to all the open VS Code windows, and are not shared with other users.

    Workspace preferences

    Workspace preferences apply to the current workspace and are stored inside the .vscode directory at the root of the workspace. If you share the workspace with other users through Git, you would also share the settings if the intent is for them to be the same across users. For example, preference settings such as tab size or file extensions would apply regardless of who edits the files.

    Note: The workspace preferences always override user preferences.

    VS Code also supports the concept of multi-root workspacesopen in new window that can also be utilized for Z Open Editor. Multi-root workspaces allow you to work with multiple folders, each representing a workspace in Visual Studio Code. This is helpful when you are working on several related projects at one time. Each workspace can use a different Git repository and be located anywhere on your development machine. A multi-root workspace basically combines all the individual and independent folders into one tree view in the File Explorer. Settings are defined for the entire multi-root workspace in a .code-workspace file, as well as for each individual workspace. In the case of a conflict, determining which setting has precedence over another depends on the setting type.

    For more details and information on types of settings available to VS Code in general, refer to the User and Workspace Settingsopen in new window and Multi-root Workspaces: Settingsopen in new window VS Code documentation pages.

    Details about specific Z Open Editor settings and behavior are provided in the following section, and also in the Settings Reference.

    VS Code user preferences versus ZAPP files

    Some preferences in Z Open Editor are specific to the application under development and should be stored independent of the editor being used to edit the program files. Examples are the search path for folders in which include files such as COBOL copybooks are located, or what compiler options should be used to parse the programs to show syntax errors in the editor. These preferences are stored in a file called ZAPP (Z APPlication) file. The section Configure your applications with ZAPP files provides a full overview.

    Last Updated:
    Contributors: Shi Kun Li, Lauren Li, Min Huang, Peter Haumer, Peter Haumer, Greg Lambert, Lauren K Li, PrasangAPrajapati, kmaselli
    - + diff --git a/Docs/setting_propertygroup.html b/Docs/setting_propertygroup.html index d5e12eef8..cca8b650b 100644 --- a/Docs/setting_propertygroup.html +++ b/Docs/setting_propertygroup.html @@ -41,7 +41,7 @@ } )(); Setting property groups | IBM Z® Open Editor - + @@ -113,6 +113,6 @@ - "/Users/<username>/Desktop/zopeneditor-sample/COPYLIB", - "/Users/<username>/Desktop/zopeneditor-sample/INCLUDELIB"

    Enforcing case-sensitive file name matching

    Starting from IBM Z Open Editor 1.2.0, file names to be matched via local libraries items are case-insensitive by default. For example, if you have a local copybook file named book1.cpy in a workspace folder specified by a local property group, then the COBOL statement COPY BOOK1. would still resolve the file, even on a case-sensitive operating system such as Linux or Macs using a case-sensitive disk format. In earlier versions of Z Open Editor, this was strictly case-sensitive on case-sensitive operating systems.

    Although this new behavior provides more flexibility for users who create copybooks and include files in lowercase, it could lead to problems in a team where members use different operating systems or switch from VS Code to Eclipse Che. For example, on a case-sensitive operating system files could be created in the same folder that are only different in their casing, such as Book1 and BOOK1, but this would cause problems on case-insensitive file systems such as Windows. Therefore, to enforce exact case matching, you can enable the user setting "zopeneditor.enforceCaseSensitiveIncludeFileNames", which by default is false. Setting it to true means that even on Windows the exact same casing of the file name as specified in the program's code is required. This applies to COBOL, PL/I, and HLASM.

    Note: This behavior also applies to the path names specified in property groups, which are case-insensitive by default, but can be made case-sensitive with this setting. However, this currently only works on Windows and Mac. On Linux and therefore Eclipse Che the property group path names are always cases-sensitive. Only the file names on the file system are matched case-insensitive when configured that way on Linux.

    SQLCA and SQLDA includes/copybooks

    A COBOL or PL/I program can be written to use the SQL communication area (SQLCA)open in new window and SQL descriptor area (SQLDA)open in new window to check return status for embedded SQL statements, or the program can use the SQL diagnostics area to check return status.

    SQLCA and SQLDA includes are usually in-built and not added in the zopeneditor property groups. In IBM Z Open Editor, SQLCA and SQLDA copybooks are excluded from the searches because they do not exist, or because they are not of interest for development. It will not find these copybooks from the mentioned syslib or libraries in the property groups.

    - + diff --git a/Docs/setting_tabstops.html b/Docs/setting_tabstops.html index b5e89504c..adb7da5e8 100644 --- a/Docs/setting_tabstops.html +++ b/Docs/setting_tabstops.html @@ -41,7 +41,7 @@ } )(); Setting language-specific tab stops and rulers | IBM Z® Open Editor - + @@ -66,6 +66,6 @@ ] }

    You can also set the following rulers:

    where array is an array of numbers representing the column numbers at which you want a ruler to appear.

    - + diff --git a/Docs/setting_unreachablecodewarnings.html b/Docs/setting_unreachablecodewarnings.html index d1d869127..f13a54a41 100644 --- a/Docs/setting_unreachablecodewarnings.html +++ b/Docs/setting_unreachablecodewarnings.html @@ -41,12 +41,12 @@ } )(); Enabling and disabling unreachable COBOL code warnings | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Enabling and disabling unreachable COBOL code warnings

    IBM Z Open editor performs real-time syntax checking and provides annotations that describe errors or warnings in COBOL code. To see the annotations that describe a specific error or warning, hover your mouse over the red or yellow underlined code in the editor. To see annotations for all errors and warnings for all opened editors, open the Problems view by pressing Ctrl+Shift+M (Windows) or Cmd+Shift+M (Mac).

    IBM Z Open Editor provides settings to enable or disable unreachable code warnings in your COBOL program. Unreachable code in a program is code that can never be executed because there is no path to the code from the rest of the program.

    IBM Z Open Editor performs real-time checking for unreachable COBOL code, but there are currently some limitations to what can be detected and there can be false positives. See the Known issues and limitations page for details. If you suffer from false warnings and want to disable the feature altogether, you can disable unreachable COBOL code warnings by specifying the following preference setting:

    "zopeneditor.cobol.enableUnreachableCodeWarnings": false
    Last Updated:
    Contributors: Shi Kun Li, Min Huang, Peter Haumer, Lauren Li, Prasang-A-Prajapati
    - + diff --git a/Docs/settings.html b/Docs/settings.html index 715c4a9b3..e28656868 100644 --- a/Docs/settings.html +++ b/Docs/settings.html @@ -41,11 +41,11 @@ } )(); settings.json properties | IBM Z® Open Editor - + -
    IBM Z® Open Editor

    settings.json properties

    You can control the characteristics of your environment by setting the following preferences in settings.json by using the JSON editor. For more information, see Accessing settings for IBM Z Open Editor.

    List of settings.json properties

    PropertyDescription
    [cobol]Use "[cobol]": {"editor.rulers": [array]} to set rulers for COBOL in the editor. array is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see Setting language specific tab stops and rulers.
    [hlasm]Use "[hlasm]": {"editor.rulers": [array]} to set rulers for HLASM in the editor. array is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see Setting language specific tab stops and rulers.
    [jcl]Use "[jcl]": {"editor.rulers": [array]} to set rulers for JCL in the editor. array is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see Setting language specific tab stops and rulers.
    [pl1]Use "[pl1]": {"editor.rulers": [array]} to set rulers for PL/I in the editor. array is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see Setting language specific tab stops and rulers.
    [rexx]Use "[rexx]": {"editor.rulers": [array]} to set rulers for REXX in the editor. array is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see Setting language specific tab stops and rulers.
    files.associationsSpecifies file names, including data set and member names, that contain certain strings as the appropriate type of file. For detailed usage, see Setting file associations.
    zopeneditor.cobol.enableUnreachableCodeWarningsEnables unreachable code warnings in the COBOL programs. For more information, see Enabling and disabling unreachable COBOL code warnings.
    zopeneditor.cobol.disableProblemsDisables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. It will also disable unreachable code warnings. The default value is false. For more information, see Enabling and disabling problems in IBM Z Open Editor.
    zopeneditor.cobol.includeFileExtensionsSpecifies a list of file name extensions for COBOL include files. For more information, see Defining Include file associations.
    zopeneditor.cobol.maximumLineLengthProvides a maximum line length for the COBOL editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see Setting language-specific maximum line length.
    zopeneditor.cobol.sequenceNumbersChoose which columns will have sequence numbers inserted and removed from a file by using the Renumber and Unnumber functions in the COBOL editor. The following values are allowed:
    • zopeneditor.cobol.sequenceNumbers.column1: Numbering starts at column 1
    • zopeneditor.cobol.sequenceNumbers.column73: Numbering starts at column 73
    • zopeneditor.cobol.sequenceNumbers.column1and73: Numbering starts at column 1 and 73
    zopeneditor.cobol.tabstopsAdds custom COBOL tab stops in the editor. For more information, see Setting language specific tab stops and rulers.
    zopeneditor.datasetsSpecifies data set names that should contain COBOL or PL/I programs, copybooks, include files, and JCL. For detailed usage, see Setting file associations.
    zopeneditor.enforceCaseSensitiveIncludeFileNamesEnforce case-sensitive matching of local copybooks and include file names in property groups. Default is false to match files with all cases in the path. Set it to true to avoid ambiguous matching on case-insensitive file systems.
    zopeneditor.hlasm.disableProblemsDisables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. The default value is false. For more information, see Enabling and disabling problems in IBM Z Open Editor.
    zopeneditor.hlasm.enableResolvingMacrosEnables the automatic resolution of SYS1.MACLIB macro files from MVS using your Zowe Explorer profiles. See the Remote Macros section for more details. The default value is false. To use this feature, you need to set it to true.
    zopeneditor.hlasm.enableCustomMacrosWarningsEnables warnings under all custom macros that can not be found in your HLASM programs. The default value is true. For more information, see Custom Macros for HLASM.
    zopeneditor.hlasm.includeFileExtensionsSpecifies a list of file name extensions for HLASM include files. For more information, see Defining Include file associations.
    zopeneditor.hlasm.instructionsFilePathAllows you to specify a custom HLASM instructions file. Contact IBM Support for questions about the format of such a file or updates to our out of the box file, for example, for a new hardware versions.
    zopeneditor.hlasm.macrosFilePathAllows you to specify a custom macro definitions file. This option is currently used internally only, but the schema for this format will be provided in a future release so that users can provide their own custom macro references.
    zopeneditor.hlasm.maximumLineLengthProvides a maximum line length for the HLASM editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see Setting language-specific maximum line length.
    zopeneditor.hlasm.reduceCustomMacroLoggingReduces the amount of logs that are sent between the HLASM language server and the Z Open Editor client. This increases the performance for scanning and resolving custom macro libraries. The default value is false. For more information, see Custom Macros for HLASM.
    zopeneditor.hlasm.tabstopsDefines custom HLASM tab stops in the editor. For more information, see Setting language specific tab stops and rulers.
    zopeneditor.hlasm.zosMacrosVersionDefines the version of z/OS to use for macro definitions. This allows for more accurate results for the hover and code completion features in HLASM. For more information, see Remote Macros.
    zopeneditor.JAVA_HOMESpecifies a different Java for IBM Z Open Editor other than the default of your computer. For more information, see section Selecting the Java installation to use in Getting started.
    zopeneditor.jcl.maximumLineLengthProvides a maximum line length for the JCL editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see Setting language-specific maximum line length.
    zopeneditor.jcl.tabstopsDefines custom JCL tab stops in the editor. For more information, see Setting language specific tab stops and rulers.
    zopeneditor.jcl.disableProblemsDisables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. The default value is false. For more information, see Enabling and disabling problems in IBM Z Open Editor.
    zopeneditor.loggerEnables a logging output. See Troubleshooting using log files for details.
    zopeneditor.pl1.disableProblemsDisables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. The default value is false. For more information, see Enabling and disabling problems in IBM Z Open Editor.
    zopeneditor.pl1.includeFileExtensionsSpecifies a list of file name extensions for PL/I include files. For more information, see Defining Include file associations.
    zopeneditor.pl1.maximumLineLengthProvides a maximum line length for the PL/I editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see Setting language-specific maximum line length.
    zopeneditor.rexx.disableProblemsDisables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. The default value is false. For more information, see Enabling and disabling problems in IBM Z Open Editor.
    zopeneditor.rexx.maximumLineLengthProvides a maximum line length for the REXX editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see Setting language-specific maximum line length.
    zopeneditor.server.memoryAllocationSpecifies the maximum value of the memory that language servers are allowed to allocate. For more information, see section Configuring the Java memory allocation in Getting started.
    zopeneditor.server.startupOptionsConfigure additional startup parameters for Java virtual machines started for running language servers. These might have been provided by tech support for troubleshooting. Leave blank by default.
    zopeneditor.userbuild.enabledEnable User Build capabilities that utilize IBM Dependency Based Build. When enabled, you can run a user build to compile and link programs during coding and unit testing simply by right-clicking inside a COBOL, PL/I, or HLASM file.
    zopeneditor.userbuild.userSettingsSettings for IBM User Build. See the IBM Documentationopen in new window for details.
    zopeneditor.watsonx.watsonxCodeAssistantForZ.enableEnables and disables the IBM watsonx Code Assistant for Z feature.
    zopeneditor.watsonx.watsonxCodeAssistantForZ.authenticationURLOverrides the IBM Cloud IAM Identity Services URL. Leave it unassigned to use the default service.
    zopeneditor.watsonx.watsonxCodeAssistantForZ.URLOverrides the URL to the IBM watsonx Code Assistant for Z service. Leave it unassigned to use the default service.
    zopeneditor.watsonx.watsonxCodeAssistantForZ.logLevelSets the logging level for IBM watsonx Code Assistant for Z. Technical support might instruct you to change this value for problem analysis.
    zopeneditor.watsonx.watsonxCodeAssistantForZ.timeoutOverrides the timeout value in milliseconds for requests sent to IBM watsonx Code Assistant for Z.
    zopeneditor.welcomePage.showShow the welcome page on VS Code startup.
    zopeneditor.zapp.useDefaultOnlineZappSchemaZ Open Editor comes with the built-in ZAPP JSON schema. It can be used for YAML files using Red Hat's YAML VS Code extension, and for JSON files with the built-in editor. If you encounter issues locating this built-in schema on deployments like Eclipse Che, such as being unable to see syntax errors with the Red Hat YAML extension, enable this option to load the schema from the internet.
    zopeneditor.zapp.customZappSchemaLocationWhen you work offline but have to provide a path to the ZAPP schema yourself, such as in a custom Che deployment, specify a valid HTTP or file URL to the location of the ZAPP JSON schema. If specified, the Use Default Online Zapp Schema option will be ignored.
    zopeneditor.zapp.generateZappOnDemandWhen you open a COBOL, PL/I, HLASM, or REXX program and none is found in all the open workspaces, a generic ZAPP file is automatically generated. This file will search for include files in all workspaces and folders.
    zopeneditor.zapp.variablesUse to specify variable names with values that will be substituted in your ZAPP files. To reference a variable defined here in a ZAPP file, write ${variable-name}. For example, define a variable here called HLQ with a value that represents your personal high-level qualifier on z/OS MVS. In your ZAPP file, reference the variable in a property group's location entry like this: ${HLQ}.COBOL.COPYBOOKs. Do not use single or double-quote characters for variable names and values. Note that all users need to define all the variables in their user settings that are used by the ZAPP file to avoid errors. You can place these properties in VS Code user and workspace settings.
    zopeneditor.zcodeformat.useDefaultOnlineZCodeFormatSchemaZ Open Editor comes with the built-in zCodeFormat JSON schema. It can be used for YAML files using Red Hat's YAML VS Code extension, and for JSON files with the built-in editor. If you encounter issues locating this built-in schema on deployments like Eclipse Che, such as being unable to see syntax errors with the Red Hat YAML extension, enable this option to load the schema from the internet.
    zopeneditor.zcodeformat.customZCodeFormatSchemaLocationWhen you work offline but have to provide a path to the zCodeFormat schema yourself, such as in a custom Che deployment, specify a valid HTTP or file URL to the location of the zCodeFormat JSON schema. If specified, the Use Default Online zCodeFormat Schema option will be ignored.
    zopeneditor.zoweThe zopeneditor.zowe setting can be used at a user or workspace level. Typically every user specifies these in their user settings using their personal profile names. If defined in workspace settings then it is assumed that all users of this workspace have defined the same standardized profile names on their systems. If set at both levels, the user and workspace level, the workspace level will override the user level.
    • Use "zopeneditor.zowe": {"defaultCliProfile": "<profile_name>"} to specify the name of the profile you want to use for IBM Z Open Editor operations. If this is not defined, IBM Z Open Editor follows the precedence rules described in Setting up and using RSE profiles in IBM Z Open Editor to identify which CLI profile to use.
    • Use "zopeneditor.zowe": {"defaultSshCliProfile": "<profile_name>"} to specify the name of the Zowe CLI SSH profile used for remote execution of commands on UNIX System Services of your z/OS system. If no valid profile name is provided, the default SSH profile will be used.
    • Use "zopeneditor.zowe": {"defaultRseConversionMappingsFile": "<absolute pathname>"} to specify the path to a valid RSE API mappings file or ZAPP file that contains RSE API mappings. These mappings will be used for Zowe Explorer MVS file content read/write operations for RSE API profiles. Note, that property groups for remote include file resolution and user build will not use this setting, but look for a workspace-local ZAPP file or if not found, a mappings file in the user's .zowe/profiles/rse directory.
    • Use the boolean setting "zopeneditor.zowe": {"listBeforeDownload": "<true-or-false>"} to modify Z Open Editor's behavior when requesting a file from MVS: - When the setting is set to true, the editor will first try to confirm that whether the requested file actually exists by performing a list operation for that file. If the requested file exists, the editor will send another request to download it. If the requested file does not exist, the editor will move on to test the next location listed in the property group. - When the setting is set to false, the editor will directly try to download the file from MVS without checking whether it actually exists. If the response from z/OS is a Not Found error, the editor will move on to the next location listed in the property group. In some cases when using z/OSMF as the protocol, this Not Found error will cause entries in z/OS log files, which you can avoid by specifying the value of the setting to true. However, this extra round-trip to the server to check the existence will have performance impact. Because the logging is not an issue when using the RSE API protocol and because of the performance advantage, the default value for this setting is false.
    • Use the integer setting "zopeneditor.zowe": {"maximumParallelFileDownloads": "<1-to-10>"} to specify how many parallel downloads Z Open Editor should perform when requesting include files from MVS. Downloading several files in parallel can significantly improve performance, especially when you edit programs with many include files. The downside is that some protocols such as z/OSMF will allocate more address spaces for the parallel requests, which causes more resources being used and more logging on the z/OS side. The RSE API protocol does not have that problem because it achieves scalability in other ways that are documented in the RSE documentation. The default value for this setting is 5, and the maximum value is 10. Set it to 1 to disable parallel downloads requesting one include file at the time.
    zowe.files.temporaryDownloadsFolder.cleanupThe zowe.files.temporaryDownloadsFolder.cleanup setting is adopted from Zowe Explorer settings to support the use of multiple VS Code windows showing the same files opened via Zowe Explorer so you can see different parts of the same program on two different screens. Note that disabling the cleanup will result in files downloaded from z/OS not being removed when the editor is closed or restarted, so when you open a file via Zowe Explorer you may be viewing an outdated local version. Use the right-click "Pull from Mainframe" command to ensure you are working with the latest files.
    zopeneditor.advancedCapabilities.enableRseApiActivationCheckThe zopeneditor.advancedCapabilities.enableRseApiActivationCheck setting is used to enable advanced capabilities activation using an RSE API server. To learn if you should enable this setting, read the documentation for advanced capabilities activation.
    zopeneditor.cobol.autoPreprocessorThe zopeneditor.cobol.autoPreprocessor setting is used to specify when the COBOL preprocessor is invoked.
    Last Updated:
    Contributors: Shi Kun Li, Peter Haumer, Chun Hong Zheng, Lauren Li, Peter Haumer, Bradley Knaysi, Ethan Mendel, Hestia Zhang, Lauren Li, Saile Daimwood, Benjamin Santos, Billie Jean Simmons, KRISTINA MAYO, Min Huang, Prasang Prajapati, Saile, kmaselli
    - +
    IBM Z® Open Editor

    settings.json properties

    You can control the characteristics of your environment by setting the following preferences in settings.json by using the JSON editor. For more information, see Accessing settings for IBM Z Open Editor.

    List of settings.json properties

    PropertyDescription
    [cobol]Use "[cobol]": {"editor.rulers": [array]} to set rulers for COBOL in the editor. array is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see Setting language specific tab stops and rulers.
    [hlasm]Use "[hlasm]": {"editor.rulers": [array]} to set rulers for HLASM in the editor. array is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see Setting language specific tab stops and rulers.
    [jcl]Use "[jcl]": {"editor.rulers": [array]} to set rulers for JCL in the editor. array is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see Setting language specific tab stops and rulers.
    [pl1]Use "[pl1]": {"editor.rulers": [array]} to set rulers for PL/I in the editor. array is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see Setting language specific tab stops and rulers.
    [rexx]Use "[rexx]": {"editor.rulers": [array]} to set rulers for REXX in the editor. array is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see Setting language specific tab stops and rulers.
    files.associationsSpecifies file names, including data set and member names, that contain certain strings as the appropriate type of file. For detailed usage, see Setting file associations.
    zopeneditor.cobol.enableUnreachableCodeWarningsEnables unreachable code warnings in the COBOL programs. For more information, see Enabling and disabling unreachable COBOL code warnings.
    zopeneditor.cobol.disableProblemsDisables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. It will also disable unreachable code warnings. The default value is false. For more information, see Enabling and disabling problems in IBM Z Open Editor.
    zopeneditor.cobol.includeFileExtensionsSpecifies a list of file name extensions for COBOL include files. For more information, see Defining Include file associations.
    zopeneditor.cobol.maximumLineLengthProvides a maximum line length for the COBOL editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see Setting language-specific maximum line length.
    zopeneditor.cobol.sequenceNumbersChoose which columns will have sequence numbers inserted and removed from a file by using the Renumber and Unnumber functions in the COBOL editor. The following values are allowed:
    • zopeneditor.cobol.sequenceNumbers.column1: Numbering starts at column 1
    • zopeneditor.cobol.sequenceNumbers.column73: Numbering starts at column 73
    • zopeneditor.cobol.sequenceNumbers.column1and73: Numbering starts at column 1 and 73
    zopeneditor.cobol.tabstopsAdds custom COBOL tab stops in the editor. For more information, see Setting language specific tab stops and rulers.
    zopeneditor.datasetsSpecifies data set names that should contain COBOL or PL/I programs, copybooks, include files, and JCL. For detailed usage, see Setting file associations.
    zopeneditor.enforceCaseSensitiveIncludeFileNamesEnforce case-sensitive matching of local copybooks and include file names in property groups. Default is false to match files with all cases in the path. Set it to true to avoid ambiguous matching on case-insensitive file systems.
    zopeneditor.hlasm.disableProblemsDisables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. The default value is false. For more information, see Enabling and disabling problems in IBM Z Open Editor.
    zopeneditor.hlasm.enableResolvingMacrosEnables the automatic resolution of SYS1.MACLIB macro files from MVS using your Zowe Explorer profiles. See the Remote Macros section for more details. The default value is false. To use this feature, you need to set it to true.
    zopeneditor.hlasm.enableCustomMacrosWarningsEnables warnings under all custom macros that can not be found in your HLASM programs. The default value is true. For more information, see Custom Macros for HLASM.
    zopeneditor.hlasm.includeFileExtensionsSpecifies a list of file name extensions for HLASM include files. For more information, see Defining Include file associations.
    zopeneditor.hlasm.instructionsFilePathAllows you to specify a custom HLASM instructions file. Contact IBM Support for questions about the format of such a file or updates to our out of the box file, for example, for a new hardware versions.
    zopeneditor.hlasm.macrosFilePathAllows you to specify a custom macro definitions file. This option is currently used internally only, but the schema for this format will be provided in a future release so that users can provide their own custom macro references.
    zopeneditor.hlasm.maximumLineLengthProvides a maximum line length for the HLASM editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see Setting language-specific maximum line length.
    zopeneditor.hlasm.reduceCustomMacroLoggingReduces the amount of logs that are sent between the HLASM language server and the Z Open Editor client. This increases the performance for scanning and resolving custom macro libraries. The default value is false. For more information, see Custom Macros for HLASM.
    zopeneditor.hlasm.tabstopsDefines custom HLASM tab stops in the editor. For more information, see Setting language specific tab stops and rulers.
    zopeneditor.hlasm.zosMacrosVersionDefines the version of z/OS to use for macro definitions. This allows for more accurate results for the hover and code completion features in HLASM. For more information, see Remote Macros.
    zopeneditor.JAVA_HOMESpecifies a different Java for IBM Z Open Editor other than the default of your computer. For more information, see section Selecting the Java installation to use in Getting started.
    zopeneditor.jcl.maximumLineLengthProvides a maximum line length for the JCL editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see Setting language-specific maximum line length.
    zopeneditor.jcl.tabstopsDefines custom JCL tab stops in the editor. For more information, see Setting language specific tab stops and rulers.
    zopeneditor.jcl.disableProblemsDisables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. The default value is false. For more information, see Enabling and disabling problems in IBM Z Open Editor.
    zopeneditor.loggerEnables a logging output. See Troubleshooting using log files for details.
    zopeneditor.pl1.disableProblemsDisables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. The default value is false. For more information, see Enabling and disabling problems in IBM Z Open Editor.
    zopeneditor.pl1.includeFileExtensionsSpecifies a list of file name extensions for PL/I include files. For more information, see Defining Include file associations.
    zopeneditor.pl1.maximumLineLengthProvides a maximum line length for the PL/I editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see Setting language-specific maximum line length.
    zopeneditor.rexx.disableProblemsDisables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. The default value is false. For more information, see Enabling and disabling problems in IBM Z Open Editor.
    zopeneditor.rexx.maximumLineLengthProvides a maximum line length for the REXX editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see Setting language-specific maximum line length.
    zopeneditor.server.memoryAllocationSpecifies the maximum value of the memory that language servers are allowed to allocate. For more information, see section Configuring the Java memory allocation in Getting started.
    zopeneditor.server.startupOptionsConfigure additional startup parameters for Java virtual machines started for running language servers. These might have been provided by tech support for troubleshooting. Leave blank by default.
    zopeneditor.userbuild.enabledEnable User Build capabilities that utilize IBM Dependency Based Build. When enabled, you can run a user build to compile and link programs during coding and unit testing simply by right-clicking inside a COBOL, PL/I, or HLASM file.
    zopeneditor.userbuild.userSettingsSettings for IBM User Build. See the IBM Documentationopen in new window for details.
    zopeneditor.watsonx.watsonxCodeAssistantForZ.enableEnables and disables the IBM watsonx Code Assistant for Z feature.
    zopeneditor.watsonx.watsonxCodeAssistantForZ.authenticationURLOverrides the IBM Cloud IAM Identity Services URL. Leave it unassigned to use the default service.
    zopeneditor.watsonx.watsonxCodeAssistantForZ.URLOverrides the URL to the IBM watsonx Code Assistant for Z service. Leave it unassigned to use the default service.
    zopeneditor.watsonx.watsonxCodeAssistantForZ.logLevelSets the logging level for IBM watsonx Code Assistant for Z. Technical support might instruct you to change this value for problem analysis.
    zopeneditor.watsonx.watsonxCodeAssistantForZ.timeoutOverrides the timeout value in milliseconds for requests sent to IBM watsonx Code Assistant for Z.
    zopeneditor.welcomePage.showShow the welcome page on VS Code startup.
    zopeneditor.zapp.useDefaultOnlineZappSchemaZ Open Editor comes with the built-in ZAPP JSON schema. It can be used for YAML files using Red Hat's YAML VS Code extension, and for JSON files with the built-in editor. If you encounter issues locating this built-in schema on deployments like Eclipse Che, such as being unable to see syntax errors with the Red Hat YAML extension, enable this option to load the schema from the internet.
    zopeneditor.zapp.customZappSchemaLocationWhen you work offline but have to provide a path to the ZAPP schema yourself, such as in a custom Che deployment, specify a valid HTTP or file URL to the location of the ZAPP JSON schema. If specified, the Use Default Online Zapp Schema option will be ignored.
    zopeneditor.zapp.generateZappOnDemandWhen you open a COBOL, PL/I, HLASM, or REXX program and none is found in all the open workspaces, a generic ZAPP file is automatically generated. This file will search for include files in all workspaces and folders.
    zopeneditor.zapp.variablesUse to specify variable names with values that will be substituted in your ZAPP files. To reference a variable defined here in a ZAPP file, write ${variable-name}. For example, define a variable here called HLQ with a value that represents your personal high-level qualifier on z/OS MVS. In your ZAPP file, reference the variable in a property group's location entry like this: ${HLQ}.COBOL.COPYBOOKs. Do not use single or double-quote characters for variable names and values. Note that all users need to define all the variables in their user settings that are used by the ZAPP file to avoid errors. You can place these properties in VS Code user and workspace settings.
    zopeneditor.zcodeformat.useDefaultOnlineZCodeFormatSchemaZ Open Editor comes with the built-in zCodeFormat JSON schema. It can be used for YAML files using Red Hat's YAML VS Code extension, and for JSON files with the built-in editor. If you encounter issues locating this built-in schema on deployments like Eclipse Che, such as being unable to see syntax errors with the Red Hat YAML extension, enable this option to load the schema from the internet.
    zopeneditor.zcodeformat.customZCodeFormatSchemaLocationWhen you work offline but have to provide a path to the zCodeFormat schema yourself, such as in a custom Che deployment, specify a valid HTTP or file URL to the location of the zCodeFormat JSON schema. If specified, the Use Default Online zCodeFormat Schema option will be ignored.
    zopeneditor.zoweThe zopeneditor.zowe setting can be used at a user or workspace level. Typically every user specifies these in their user settings using their personal profile names. If defined in workspace settings then it is assumed that all users of this workspace have defined the same standardized profile names on their systems. If set at both levels, the user and workspace level, the workspace level will override the user level.
    • Use "zopeneditor.zowe": {"defaultCliProfile": "<profile_name>"} to specify the name of the profile you want to use for IBM Z Open Editor operations. If this is not defined, IBM Z Open Editor follows the precedence rules described in Setting up and using RSE profiles in IBM Z Open Editor to identify which CLI profile to use.
    • Use "zopeneditor.zowe": {"defaultSshCliProfile": "<profile_name>"} to specify the name of the Zowe CLI SSH profile used for remote execution of commands on UNIX System Services of your z/OS system. If no valid profile name is provided, the default SSH profile will be used.
    • Use "zopeneditor.zowe": {"defaultRseConversionMappingsFile": "<absolute pathname>"} to specify the path to a valid RSE API mappings file or ZAPP file that contains RSE API mappings. These mappings will be used for Zowe Explorer MVS file content read/write operations for RSE API profiles. Note, that property groups for remote include file resolution and user build will not use this setting, but look for a workspace-local ZAPP file or if not found, a mappings file in the user's .zowe/profiles/rse directory.
    • Use the boolean setting "zopeneditor.zowe": {"listBeforeDownload": "<true-or-false>"} to modify Z Open Editor's behavior when requesting a file from MVS: - When the setting is set to true, the editor will first try to confirm that whether the requested file actually exists by performing a list operation for that file. If the requested file exists, the editor will send another request to download it. If the requested file does not exist, the editor will move on to test the next location listed in the property group. - When the setting is set to false, the editor will directly try to download the file from MVS without checking whether it actually exists. If the response from z/OS is a Not Found error, the editor will move on to the next location listed in the property group. In some cases when using z/OSMF as the protocol, this Not Found error will cause entries in z/OS log files, which you can avoid by specifying the value of the setting to true. However, this extra round-trip to the server to check the existence will have performance impact. Because the logging is not an issue when using the RSE API protocol and because of the performance advantage, the default value for this setting is false.
    • Use the integer setting "zopeneditor.zowe": {"maximumParallelFileDownloads": "<1-to-10>"} to specify how many parallel downloads Z Open Editor should perform when requesting include files from MVS. Downloading several files in parallel can significantly improve performance, especially when you edit programs with many include files. The downside is that some protocols such as z/OSMF will allocate more address spaces for the parallel requests, which causes more resources being used and more logging on the z/OS side. The RSE API protocol does not have that problem because it achieves scalability in other ways that are documented in the RSE documentation. The default value for this setting is 5, and the maximum value is 10. Set it to 1 to disable parallel downloads requesting one include file at the time.
    zowe.files.temporaryDownloadsFolder.cleanupThe zowe.files.temporaryDownloadsFolder.cleanup setting is adopted from Zowe Explorer settings to support the use of multiple VS Code windows showing the same files opened via Zowe Explorer so you can see different parts of the same program on two different screens. Note that disabling the cleanup will result in files downloaded from z/OS not being removed when the editor is closed or restarted, so when you open a file via Zowe Explorer you may be viewing an outdated local version. Use the right-click "Pull from Mainframe" command to ensure you are working with the latest files.
    zopeneditor.advancedCapabilities.enableRseApiActivationCheckThe zopeneditor.advancedCapabilities.enableRseApiActivationCheck setting is used to enable advanced capabilities activation using an RSE API server. To learn if you should enable this setting, read the documentation for advanced capabilities activation.
    zopeneditor.autoPreprocessorThe zopeneditor.autoPreprocessor setting is used to specify when the COBOL or PL/I preprocessor is invoked.
    Last Updated:
    Contributors: Shi Kun Li, Peter Haumer, Chun Hong Zheng, Lauren Li, Peter Haumer, Bradley Knaysi, Ethan Mendel, Hestia Zhang, Lauren Li, Saile Daimwood, Benjamin Santos, Billie Jean Simmons, KRISTINA MAYO, Min Huang, PETER HAUMER, Prasang Prajapati, Saile, kmaselli
    + diff --git a/Docs/setup_integration.html b/Docs/setup_integration.html index 5054d25ed..9d9f0d0c7 100644 --- a/Docs/setup_integration.html +++ b/Docs/setup_integration.html @@ -41,7 +41,7 @@ } )(); Setting up integrations to interact with z/OS | IBM Z® Open Editor - + @@ -91,6 +91,6 @@ "autoStore": true }

    Known Issues

    If any issues or concerns arise during installation or while working with the RSE CLI plug-in, refer to the known issues documentation for the RSE CLI plug-in here.

    - + diff --git a/Docs/sharing_team_configuration_files.html b/Docs/sharing_team_configuration_files.html index 6d734da27..df46c37c9 100644 --- a/Docs/sharing_team_configuration_files.html +++ b/Docs/sharing_team_configuration_files.html @@ -41,11 +41,11 @@ } )(); Sharing team configuration files | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Sharing team configuration files

    Team configuration files can be shared with others using a git project. For faster setup, a team lead can include a team configuration file with connection details in the code repository without any secure values. Each developer would enter their own secure values once they start using profiles. A team configuration file needs to be at the top level of project so that it can be read correctly in VS Code. An important thing to note is in order for the configuration profile to work properly the zowe.schema.json file needs to be included in the same folder as the team configuration profile.

    Take a look at the location where your team configuration file resides.

    • If you created a global zowe.config.json, it was placed in ~/.zowe folder.
    • If you created a user configuration file scoped to 1 repository zowe.config.user.json, it was placed inside that repository.

    In both cases, a zowe.schema.json file should have been automatically created and placed in the same folder. If the schema file is missing, team configuration files will not work. The schema file has definitions of the supported profile attributes. If you add an extender, such as RSE CLI plug-in, the extender will update the schema file to support new profile types. Therefore, make sure to share both the team configuration file and the zowe.schema.json file.

    For more information about methods for sharing team configuration files, see Zowe documentationopen in new window.

    Troubleshooting tips

    You might run into situation wherethe zowe.schema.json file is not automatically updated by the extender, and extender profiles are not working. You can check by opening the schema file and looking for your extender defintions.

    • Use zowe config update-schemas to manually update the schema.
    • Use zowe config update-schemas --help for more options.

    If your schema file is missing, the easiest solution is to re-create the team configuration file by using Zowe Explorer or Zowe CLI, and then the schema file will be automatically created in the same location.

    Last Updated:
    Contributors: KRISTINA MAYO, Chun Hong Zheng
    - + diff --git a/Docs/sharingfiles.html b/Docs/sharingfiles.html index 9d25b131c..480b5c6ae 100644 --- a/Docs/sharingfiles.html +++ b/Docs/sharingfiles.html @@ -41,7 +41,7 @@ } )(); Sharing files between VS Code extensions | IBM Z® Open Editor - + @@ -49,6 +49,6 @@ "folderPath": "/path/to/local/directory" }

    Using this setting, you can navigate to the path specified, and see a downloaded copy of all remote files edited via the Zowe VS Code extension.

    Note: All files temp are deleted on startup and shutdown.

    - + diff --git a/Docs/shortcut.html b/Docs/shortcut.html index 061532083..f16d360b8 100644 --- a/Docs/shortcut.html +++ b/Docs/shortcut.html @@ -41,11 +41,11 @@ } )(); Keyboard shortcuts reference | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Keyboard shortcuts reference

    DescriptionWindowsMac
    Search for identifiers within the Outline view and go to symbolCtrl+Shift+OCmd+Shift+O
    Show the list of available code completionCtrl+SpaceCtrl+Space
    Open copybook/include files in a separate editorCtrl+ClickCmd+Click
    Change all occurrencesCtrl+F2Cmd+F2
    Find all referencesAlt+Shift+F12Option+Shift+F12
    Peek referencesShift+F12Shift+F12
    Go to definitionF12F12
    Peek definitionAlt+F12Option+F12
    Rename symbolsF2F2
    UndoCtrl+ZCmd+Z
    RedoCtrl+Shift+ZCmd+Shift+Z
    Open the VS Code command paletteCtrl+Shift+PCtrl+Shift+P
    Open the Problems viewCtrl+Shift+MCmd+Shift+M
    Open the Git viewCtrl+Shift+GCtrl+Shift+G
    Open the Terminal windowCtrl+Back quote1Ctrl+Back quote1

    Note:

    1. The back quote key is labeled as ` on your keyboard.
    Last Updated:
    Contributors: Shi Kun Li, Lauren Li, Min Huang, Peter Haumer
    - + diff --git a/Docs/snippets.html b/Docs/snippets.html index 0b7e3879c..a5e3a73cf 100644 --- a/Docs/snippets.html +++ b/Docs/snippets.html @@ -41,11 +41,11 @@ } )(); Using and managing code snippets | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Using and managing code snippets

    IBM Z Open Editor ships with a library of reusable code snippets for COBOL, PL/I, and JCL to help you improve your productivity, as well as to standardize on code patterns and best practices. In addition to these out-of-the-box snippets, you can also create your own snippets and import snippets from IBM Developer for z/OS.

    IBM Z Open Editor utilizes the Snippet facilities provided by VS Code. To learn more about this code snippet support, refer to the VS Code Online Help pagesopen in new window.

    Using code snippets

    To explore and insert a code snippet that ships with IBM Z Open Editor, use either the VS Code Snippet picker or the code completion feature while editing a program file.

    Inserting a code snippet with a picker

    1. Place the cursor on Column 1 in the editor as COBOL snippets come with indentations based on that column.

    2. Open the VS Code command palette with Ctrl+Shift+P (Windows) or Cmd+Shift+P (Mac).

    3. Type Insert Snippet until the command appears, and select it.

    4. Based on the language that you are working with, it will then show a picker drop-down with the available snippets. All snippets are organized into a group of related snippets such as COBOL Embedded SQL or COBOL CICS. Each snippet also has a descriptive name and summary.

      1. Scroll down through the list or just type any substring of the snippet your are looking for.
      2. Select the snippet you want to insert and it will be added to the current cursor location.

    5. Many snippets have place holders for variables or terminals. You can use the Tab key or Shift-Tab to navigate between them.

    6. Type the new value to replace this and all other occurrences of the place holder and press Enter to finish.

    Inserting a code snippet using code completion

    1. When you edit a program, press Ctrl+Space to start code completion.

    2. In the drop-down list, you will see first the list of context-sensitive code completion suggestions provided by the language server assuming you are working either in COBOL or PL/I. If you scroll down, you see the list of code snippets below.

    3. Again, you can just type for any code snippet substring to search for a snippet that you are looking for to jump ahead in the drop-down.

    4. Select the snippet and it will be inserted at your current cursor location.

    Creating your own code snippets

    You can easily complement the list of code snippets with your own as follows.

    1. Follow the VS Code instructionsopen in new window to create your own snippets collection.

    2. In the language drop-down, select type cobol, pl1, hlasm, or jcl as the language identifiers to start a snippet collection in that language. VS Code will open an editor window with instructions for how to write your own snippets. The help page listed above will also provide you with detailed guidance.

    3. Once you have added your first snippet, save it. It will appear in the Snippet Picker described above placed before the IBM snippets.

    Importing code snippets from IBM Developer for z/OS

    If you are using the IBM Developer for z/OS (IDz) and have created custom code snippets there, you can export these code snippets and import them into the Z Open Editor.

    Exporting code snippets in IDz

    1. To display the available snippets in IDz, use the menu Window > Show View > Snippets.

    2. Right-click anywhere in the Snippets view and select Customize...

    3. In the dialog, find the Snippet group you want to export and click the Export button.

    4. Specify the name and location for the export file, which will be an XML file.

    Importing IDz code snippets into IBM Z Open Editor

    1. In IBM Z Open Editor, open the VS Code command palette with Ctrl+Shift+P (Windows) or Cmd+Shift+P (Mac).

    2. Start typing IBM Z Open Editor: Import IBM Developer for Z Code Snippets until you see this command and select it.

    3. A drop-down picker appears asking you for the program language of the snippets you want to import. Select one from the drop-down menu.

    4. A file dialog appears. Navigate to and select the file that exported from IDz in the previous step.

    5. Then a final text drop down appears asking you for a prefix string for the imported snippets. This prefix will be placed in front of the name of every snippet to be imported, which allows you to group the snippets by name in the resulting Snippet picker. You can leave this value empty and/or edit it again after the import.

    If the import succeeds, it opens a JSON file editor with the imported snippets in the Microsoft VS Code format as documented in the help page listed above. You can now edit and make changes to polish the snippets and to add place holders.

    If there were errors during the import, those errors will be displayed in a separate JSON file. That file will show up only if there were indeed any errors.

    Last Updated:
    Contributors: Shi Kun Li, Peter Haumer, Min Huang, Peter Haumer
    - + diff --git a/Docs/trademarks.html b/Docs/trademarks.html index 93d613223..2f1d6b981 100644 --- a/Docs/trademarks.html +++ b/Docs/trademarks.html @@ -41,11 +41,11 @@ } )(); Trademarks | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Trademarks

    IBM®, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" hereopen in new window.

    Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

    Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

    Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

    Last Updated:
    Contributors: Min Huang
    - + diff --git a/Docs/tutorial_assembler.html b/Docs/tutorial_assembler.html index 664df9eb3..c087c70d9 100644 --- a/Docs/tutorial_assembler.html +++ b/Docs/tutorial_assembler.html @@ -41,13 +41,13 @@ } )(); HLASM editing tutorial | IBM Z® Open Editor - +
    IBM Z® Open Editor

    HLASM editing tutorial

    About this tutorial

    For the tutorial, you will assume the role of an HLASM developer who has received a requirement to enhance the output from ASAM1 to also write the hexedecimal value of a character string. The current version simply reads in a string from an input file, and writes the record number, column number headings, and the input string to an output file.

    Prerequisites

    Install IBM Z Open Editor and its prerequisites such as Java as described in Getting Started.

    Procedure

    1. To enhance the report, you need to import the source code first.

      1. In VS Code, click Terminal > New Terminal to open a terminal.
      2. In the Terminal window, navigate to the desired directory for the source code by entering, for example, the following command:
        cd /c/Users/Public
      3. To clone the source code from the Git repository, enter the git repository of the sample files:
        git clone https://github.com/IBM/zopeneditor-sample.git
      4. After the clone is completed, click File > Open Folder. Then, in the Open Folder window, select the C:/Users/Public/zopeneditor-sample directory that you cloned, and click Select Folder.

    2. Review the source code.

      The current sample application consists of one HLASM program (ASAM1), one copybook (REGISTRS), two JCL members to set up and run the application (ASMALLOC, RUNASAM1), and the input data file (FILEIN).

      ASAM1 reads in the FILEIN data file record as a character string, and then simply writes out the string to the output file FILEOUT.

    3. (Optional) As you view the source in VS Code, you can use the Outline view to efficiently explore and navigate the code of the program. Note that the Outline view can be used only after you have opened a file or program in VS Code.

      If the Outline view is not already expanded, you can open it by clicking View > Open view > Outline. By looking through the items in this view, you can get an idea of what the program does at a high level.

      Note: ASAM1.asm is a simple program to use in the editing tutorial. To see a more robust Outline view, you can open the IRR@XACS.asm file, an example from SYS1.SAMPLIB. The IRR@XACS.asm file serves as a better example to demonstrate the the Outline view and its capabilities, and you can further explore it as follows:

      • Expand and collapse sections such as Dummy Sections (DSECT) and Control Sections (CSECT), and Macros in the Outline View.
      • Go to a desired location in the code by clicking that section header in the view.
      • Sort by Position, Name, or Type.
      • See Customizing the Outline view to configure what types of symbols to appear in the Outline view.

    4. (Optional) In the ASAM1.asm file, you will see code syntax highlighting in the opened file, which helps you quickly distinguish between HLASM reserved words, comments, constants, and variables.

      To see all the syntax errors in the open files, click View > Problems or click the error and warning icon at the bottom in the status bar. Click the list item to directly go to the problem.

    5. (Optional) Another visual feature of the editor is the grey lines that help with formatting as you code. You will notice the column 72 for the continuation character and the line at column 16 to show where a continued line can begin.

    6. Modify the code in the ASAM1.asm file to also write the hexedecimal value of a character string to the output. When you enter code, the code completion capability provides you with matching lists from which you can select commands, defined variables, and code snippets.

      For example, place your cursor at the end of line 40, and hit the Enter key to begin a new line on line 41. Try typing the command BALR, and as you type, you can select from the lists of code completion suggestions that appear. You will also see a pop-up that displays the name of the command and the format of the command. Delete the new line you just typed on line 41 and continue with the tutorial.

    7. (Optional) The hover feature works on variables and copybooks. You can hover over a variable to see its definition. You can hover over a copybook after configuring your ZAPP file and the editor will resolve it and display it in a pop-up window. After the copybook is opened, you can press Ctrl+Click on Windows or Cmd+Click on Mac to open the copybook in an editor window. Alternatively, you can use F12 or right click the copybook and select Go to Definition. Copybook resolution is based on ZAPP file property groups.

    8. (Optional) The editor can show you all references of a variable or section in your code. When you double-click a variable or section name to highlight the entire name and then right-click it, you can see the following available actions:

      • Click Change All Occurrences: Ctrl+F2 (Windows) or Cmd+F2 (Mac)

        When you type the new name, all occurrences are changed simultaneously.

        Note: In the scroll bar on the right side of the editor, each occurrence is noted with a location bar.

      • Click Find All References: Alt+Shift+F12 (Windows) or Option+Shift+F12 (Mac)

        A Results References view for the variable or paragraph is displayed on the left side of the screen. Click any result to go to that location in the file.

      • Click Peek References: Shift+F12 (Windows and Mac)

        A Results References view is displayed in the CodeLens box underneath the variable or paragraph. Click any result to go to that location in the file.

      • Click Go to Definition: F12 (Windows and Mac)

        Go to the location where the variable or paragraph is defined. It opens the copybook or include if applicable.

      • Click Go to Symbol: Ctrl+Shift+O (Windows) or Cmd+Shift+O (Mac)

        When you enter an object name in the search bar or you scroll through the items to select the object, the cursor is moved to that location.

      • Click Peek Definition: Alt+F12 (Windows) or Option+F12 (Mac)

        This opens a CodeLens box that shows where the variable or paragraph was defined in the code.

    9. Examine your code to analyze the impact of the requirement you received to determine the modifications needed. As you are to modify ASAM1, you need to search for all components that refer to the program.

      To search for components referencing ASAM1, you can use the advanced search capabilities provided by the VS Code editor. Its Search view allows searching for strings and regular expressions across all files or a specific subset of files based on location or name patterns.

      In the Explorer view, right-click in the background of the zopeneditor-sample, not showing any particular file or folder to initiate a search on all files:

      1. Select Find in Folder...

      2. Input the search term ASAM1 and press Enter.

        You can review some of the other search options such as using regular expressions and specifying patterns for files and folders to be excluded or included in the search.

        For example, to perform a regular expression search, select the .* icon and change the search term to ASAM1.* and review the results. Results will appear in the Search panel.

      3. Click on the result to navigate to that location file in the Editor panel.

    10. Open the integrated Git in VS Code, and create an isolated branch called write-hex-value, where no one but yourself can access the source code before you push the changes to the origin repository.

      To create the branch:

      1. In VS Code on the lower left hand corner, click create branch.
      2. Then, from the drop-down menu that is displayed at the top of VS Code, click Create new branch.
      3. Specify a branch name of write-hex-value, and then press enter to confirm. The workspace is switched to the isolated write-hex-value branch now.

    11. Commit your changes into your write-hex-value branch.

      Now that you have performed various code changes and refinements you can commit this file version of the application to the SCM to preserve and share it.

      To commit your changes, click the Source Control icon on the left of VS Code. In the Source Control panel that opens, the changed program is listed in the CHANGES section. In the CHANGES section, hover on the ASAM1.asm program name and click the Stage changes (+) icon to move your changes to the staging area. In the Message text box, enter a comment for the changes such as Implemented Hex Value, and then click the Commit icon to commit your changes.

    12. (Optional) Z Open Editor also supports custom macros for HLASM as an advanced feature. You can hover over a macro after configuring your ZAPP file and the editor will resolve it and display it in a pop-up window. After the macro is opened, you can press Ctrl+Click on Windows or Cmd+Click on Mac to open the macro in an editor window. Alternatively, you can use F12 or right click the macro and select Go to Definition . See Custom Macros for HLASM for more information. To see an example of custom macros working in the zopeneditor-sample repository, follow these steps:

      1. Change your branch to wazi-main.
      2. Open the zapp.yaml in the root of the workspace. There is an entry for a library named maclib.
      3. Open /ASM/MASAM1.asm.
      4. Scroll throughout the program and notice the various custom macros that are used. Key macros to look for: MCLOSE, MOPEN, MPUT, MGET, and REGS.

    Congratulations on completing the tutorial. For a more comprehensive list of the available features for code editing, see Making code changes.

    Last Updated:
    Contributors: Shi Kun Li, Peter Haumer, Peter Haumer, Saile Daimwood, Chun Hong Zheng, Hestia Zhang
    - + diff --git a/Docs/tutorial_cobol.html b/Docs/tutorial_cobol.html index 2611e779b..4317374f2 100644 --- a/Docs/tutorial_cobol.html +++ b/Docs/tutorial_cobol.html @@ -41,13 +41,13 @@ } )(); COBOL editing tutorial | IBM Z® Open Editor - +
    IBM Z® Open Editor

    COBOL editing tutorial

    About this tutorial

    For the tutorial, you will assume the role of COBOL developer who has received requirements to enhance the Daily Customer File Update Report of the SAM application located at https://github.com/IBM/zopeneditor-sampleopen in new window.

    Prerequisites

    1. Install IBM Z Open Editor and its prerequisites such as Java as described in Getting Started.

    Procedure

    1. To enhance the report, you need to import the source code of the sample application first.

      • In VS Code, click Terminal > New Terminal to open a terminal.

      • In the terminal window, navigate to the desired directory for the source code by entering, for example:

        cd /c/Users/Public

      • To clone the source code from the Git repository, enter the Git repository of the provided sample files:

        git clone https://github.com/IBM/zopeneditor-sample.git

      • After the clone is completed, click File > Open Folder. Then, in the Open Folder window, select the C:/Users/Public/zopeneditor-sample directory that you cloned, and then click Select Folder. The folder is now opened in the Explorer view on the left of VS Code.

        The current sample application consists of the following files:

        • COBOL programs: SAM1 and SAM2
        • COPYBOOKS: CUSTCOPY and TRANREC
        • JCL that set up and run the application: ALLOCATE, RUN
        • Datasource files: CUSTFILE and TRANFILE

        As mentioned in the Exploring the Sample Filesopen in new window page, a program called SAM1LIB (a copy of SAM1) is included to demonstrate the ability to resolve library-based copybooks, whether they be on a local file system or a remote Z host. SAM1LIB uses the COPYBOOKS, DATETIME (local), and REPTTOTL (MVS).

        SAM1 reads in both the CUSTFILE and TRANFILE data files, then performs different actions on the CUSTFILE based on transactions from TRANFILE. Valid transactions are ADD, UPDATE, and DELETE. When encountering an UPDATE transaction, SAM1 will call SAM2 to perform the requested update.

        As you review SAM2, you will notice there is already some base code in place for CRUNCH transactions which will be enhanced later in the following exercise. At the end of processing the TRANFILE, SAM1 will then generate a report on the transactions processed and will also produce an updated CUSTFILE.

    2. Search for components that generate and reference the "Daily Customer File Update" with the advanced Search capabilities provided by the VS Code editor out of the box. Its Search view allows searching for strings as well as regular expression across all files or a specific subset of files based on location or name patterns.

      In the Explorer right-click in the background of the WAZI-SAMPLE, not showing any particular file or folder to initiate a search on all files:

      • Select Find in Folder...
      • Enter the search term CUSTOMER-FILE and start the search with the Return key.
      • Review some of the other search options such as using regular expression and specifying patterns for files and folders to be excluded or included in the search.
      • To perform a regular expression search select the .* icon and change the search term to CUST.*FILE and review the results.
      • Results will appear in the Search Panel.
      • Clicking on the result will allow the user to navigate to that location file in the Editor panel.

    3. Now that you have determined the file that need to be modified - SAM1.cbl. Open the SAM1.cbl program in the editor, you will see syntax highlighting in the program, which allows you to quickly distinguish between COBOL reserved words, comments, constants, and variables. You will also see unrecognized statements and expressions in red, which enables you to make quick corrections and reduce compile errors. Syntax checking also works for misspelled COBOL reserved words and unknown variable names. To see all the syntax errors in the open files, open the Problems view through the View menu or by clicking the error and warning icon at the bottom in the status bar. Click the list item to directly go to the problem.

      If you specified the filepath to the copybooks in your ZAPP file property groups to resolve the references, you can also preview the contents of a copybook by moving your mouse cursor over the copybook name in a COPY statement, for example COPY TRANREC, in the COBOL program without having to navigate away. This also applies to copybooks that reside in libraries and reference in COBOL programs as demonstrated in SAM1.cbl with the COPY DATETIME IN MYFILE (for local) and COPY REPTTOTL IN MYLIB (for MVS) statements.

    4. To understand this program at a high level and efficiently explore and navigate the code of the program, use the Outline view. If the Outline view is not automatically expanded, open it by clicking View > Open view > Outline. You can use this view to perform the following actions:

      • Expand and collapse sections such as Division Headings, Section Headings, and Variable Group Names in the Outline View.
      • Recognize includes, procedures, and loops quickly via the icons located by the various items.
      • Go to a desired location in the code by clicking that section header in the view.
      • Sort by Position, Name, or Type.

      Note: The Outline view can be used only after you have opened a file or program in VS Code.

    5. After efficiently navigating through the program, you know that you have to insert code in the SAM1.cbl program to fix the issue. Now, you can use the integrated Git in VS Code to create an isolated branch called update-report where no one but yourself can access the source code in it unless you push the changes to the origin repository. To create the branch:

      • In VS Code on the lower left hand corner, click the main branch at the lower left.
      • Then, from the drop-down menu that is displayed at the top of VS Code, click Create new branch.
      • Specify a branch name of update-report, and then press enter to confirm. The workspace is switched to the isolated update-report branch now.

    6. You are now ready to insert code. When you are entering code, code completion provides you with matching lists from which you can select commands, defined variable and paragraph names, and code snippets. For example, place your cursor at the end of line 216, and press Enter to begin a new line on line 217. Try typing the command ACCEPT CURRENT-TIME FROM TIME. As you type, note that you can select from the lists of code completion suggestions that appear.

      You can also use the code snippets that are shipped with IBM Z Open Editor. To use it, navigate to the File Control section of the SAM1.cbl program, press F1, select Insert Snippet, and then enter VSAM in the Search bar. You will see a list of VSAM snippets. For example, scroll to the VSAM: KSDS Select/Assign Clause snippet and press Enter. A pre-formatted SELECT/ASSIGN clause will be inserted.

    7. Now that you have performed code changes and refinements, you can commit your changes into your update-report branch to preserve it. To commit your changes, click the Source Control icon on the left of VS Code. In the Source Control panel that opens, the changed program is listed in the CHANGES section. In the CHANGES section, hover on the SAM1.cbl program name and click the Stage changes (+) icon to move your changes to the staging area. In the Message text box, enter a comment for the changes such as Implemented Update Report, and then click the Commit icon to commit your changes.

    Congratulations on completing the tutorial. For a more comprehensive list of the available features for code editing, see Making code changes.

    Last Updated:
    Contributors: Shi Kun Li, Greg Lambert, Min Huang, Peter Haumer, Peter Haumer
    - + diff --git a/Docs/tutorial_overview.html b/Docs/tutorial_overview.html index 83951c613..6847865c9 100644 --- a/Docs/tutorial_overview.html +++ b/Docs/tutorial_overview.html @@ -41,11 +41,11 @@ } )(); Tutorial overview | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Tutorial overview

    If you are new to Microsoft Visual Studio Code, you might want to first explore the user interface to learn about its key user interface capabilities and views, which are most relevant for working with COBOL, PL/I, HLASM, and REXX program files.

    If you are ready to get hands-on with IBM Z Open Editor, you can use the sample repository of COBOL, PL/I, HLASM, and REXX files to walk through the tutorials and explore the features of IBM Z Open Editor.

    Once you have the sample files, you can start by making code changes to COBOL, HLASM, and REXX programs to learn about the editing capabilities.

    After you complete code changes on your machine, you might want to go ahead and manage z/OS resources. To learn more about how to interact with z/OS using IBM Z Open Editor and its integrations, refer to the following tutorials:

    Last Updated:
    Contributors: Shi Kun Li, Greg Lambert
    - + diff --git a/Docs/tutorial_rexx.html b/Docs/tutorial_rexx.html index 13a3eb7f5..56990d852 100644 --- a/Docs/tutorial_rexx.html +++ b/Docs/tutorial_rexx.html @@ -41,13 +41,13 @@ } )(); REXX editing tutorial | IBM Z® Open Editor - +
    IBM Z® Open Editor

    REXX editing tutorial

    About this tutorial

    For the tutorial, you will assume the role of a REXX developer who has received a requirement to enhance the output from RSAM1 to display the contents of the output file which is a combination of the two input files. The current version simply reads in two files and writes the records to an output file. The RSAM application is located at https://github.com/IBM/zopeneditor-sampleopen in new window.

    Prerequisites

    1. Install IBM Z Open Editor and its prerequisites such as Java as described in Getting Started.

    Procedure

    1. To enhance the report, you need to import the source code of the sample application first.

      • In VS Code, click Terminal > New Terminal to open a terminal.

      • In the terminal window, navigate to the desired directory for the source code by entering, for example:

        cd /c/Users/Public

      • To clone the source code from the Git repository, enter the git repository of the provided sample files:

        git clone https://github.com/IBM/zopeneditor-sample.git

      • After the clone is completed, click File > Open Folder. Then, in the Open Folder window, select the C:/Users/Public/zopeneditor-sample directory that you cloned, and then click Select Folder. The folder is now opened in the Explorer view on the left of VS Code.

        The current sample application consists of a REXX program, RSAM1, and JCL to set up the application files (REXALLOC), and the datasource files (FILEIN1 and FILEIN2).

        RSAM1 reads in the FILEIN1 data file and writes the records to the FILEOUT datafile. It then reads in FILEIN2 and writes the records to FILEOUT.

    2. (Optional) As you view the source in VS Code, you can use the Outline view to efficiently explore and navigate the code of the program. Note that the Outline view can be used only after you have opened a file or program in VS Code.

      If the Outline view is not already expanded, you can open it by clicking View > Open view > Outline. By looking through the items in this view, you can get an idea of what the program does at a high level.

      Note: The REXX Outline view only shows internal routines. RSAM1.rexx is a simple program to use in the editing tutorial so only two internal routines show up in the Outline view.

    3. (Optional) In the RSAM1.rexx file, you will see code syntax highlighting in the opened file, which helps you quickly distinguish between comments, strings, constants, variables, keywords, labels, functions, comparison, and arithmetic.

      Unrecognized statements and expressions are highlighted in red, with which you can make quick corrections accordingly and reduce compile errors. To see all the syntax errors in the open files, click View > Problems or click the error and warning icon at the bottom in the status bar. Click the list item to directly go to the problem.

    4. Modify the code in the RSAM1.rexx file to add a new internal routine fileout, which will read through FILEOUT and display each record that is in the file.

      For example, place your cursor on line 42 and hit the Enter key to begin a new line on line 43. Begin typing the command CALL fileout, and as you type, you can select from the lists of code completion suggestions that appear. You will also see a pop-up that displays the name of the command and the format of the command.

    5. (Optional) The hover feature works on REXX keyword instructions. You can hover over a keyword to see its definition and format.

    6. (Optional) The editor can show you all references of a variable or internal routine in your code. When you double-click a variable or internal routine name to highlight the entire name and then right-click it, you can see the following available actions:

      • Click Find All References: Alt+Shift+F12 (Windows) or Option+Shift+F12(Mac)

        A Results References view for the variable or paragraph is displayed on the left side of the screen. Click any result to go to that location in the file.

      • Click Peek References: Shift+F12 (Windows and Mac)

        A Results References view is displayed in the CodeLens box underneath the variable or paragraph. Click any result to go to that location in the file.

    7. Open the integrated Git in VS Code, and create an isolated branch called display-fileout-content, where no one but yourself can access the source code before you push the changes to the origin repository.

      To create the branch:

      1. In VS Code on the lower left hand corner, click create branch.
      2. Then, from the drop-down menu that is displayed at the top of VS Code, click Create new branch.
      3. Specify a branch name of display-fileout-content, and then press enter to confirm. The workspace is switched to the isolated display-fileout-content branch now.

    8. Commit your changes into your display-fileout-content branch.

      Now that you have performed various code changes and refinements you can commit this file version of the application to the SCM to preserve and share it.

      To commit your changes, click the Source Control icon on the left of VS Code. In the Source Control panel that opens, the changed program is listed in the CHANGES section. In the CHANGES section, hover on the RSAM1.rexx program name and click the Stage changes (+) icon to move your changes to the staging area. In the Message text box, enter a comment for the changes such as Display fileout content, and then click the Commit icon to commit your changes.

    Congratulations on completing the tutorial. For a more comprehensive list of the available features for code editing, see Making REXX code changes.

    The RSE CLI plug-in also has support for Interactive TSO commands, you can read more about this under Run interactive TSO commands.

    Last Updated:
    Contributors: Greg Lambert, Bradley Knaysi, Billie Simmons
    - + diff --git a/Docs/uninstalling.html b/Docs/uninstalling.html index 0ec57e670..0b5b1cbef 100644 --- a/Docs/uninstalling.html +++ b/Docs/uninstalling.html @@ -41,13 +41,13 @@ } )(); Uninstalling CLI plugins and VS Code extensions | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Uninstalling CLI plugins and VS Code extensions

    Follow this procedure to uninstall IBM RSE API Plug-in for Zowe CLI and IBM Z Open Editor from your workstation.

    Uninstalling RSE CLI plug-in

    To uninstall IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in) from your development machine, complete the following steps:

    1. Check that the RSE CLI plug-in is currently installed by running the following Zowe CLI command:

      zowe plugins list

    2. Uninstall the RSE CLI plug-in by running the following command:

      zowe plugins uninstall @ibm/rse-api-for-zowe-cli

    Uninstalling Z Open Editor and Zowe Explorer

    To uninstall IBM Z Open Editor and Zowe Explorer, complete the following steps:

    1. In VS Code, navigate to the Extensions activity group by click the icon on the left toolbar or by clicking Code > Settings > Extensions.
    2. From the Extensions: Installed list, select IBM Z Open Editor.
    3. In the details view appearing on the right, click Uninstall.
    4. From the list on the left, select Zowe Explorer.
    5. In the details view appearing on the right, click Uninstall.
    6. Quit and restart VS Code.
    Last Updated:
    Contributors: Peter Haumer, Chun Hong Zheng
    - + diff --git a/Docs/userinterface.html b/Docs/userinterface.html index d4deed5ae..dd1cbac32 100644 --- a/Docs/userinterface.html +++ b/Docs/userinterface.html @@ -41,11 +41,11 @@ } )(); Exploring the user interface | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Exploring the user interface

    If you have not worked with Microsoft Visual Studio Code before, we recommend you orient yourself reviewing the editor's Get Startedopen in new window sections first.

    Then get familiar with the following key user interface capabilities and views that are most relevant for working with COBOL, PL/I, HLASM, REXX, and JCL program files:

    • Activity bar: Groups different views. You can click the icons on the bar a second time to hide its views.

    • Status bar: Displays the active Zowe CLI profile being used for z/OS actions such resolving remote include files or running user builds. It will pick profiles listed in user settings first, if not found any default RSE API profiles available next, and if not found the default z/OSMF profiles.

    • File explorer: Manages your projects and files.

    • Search: Provides various search capabilities.

    • Git: Manages changes to the repository. This is the default SCM tool.

    • Zowe Explorer: Lets you interact with z/OS.

    • Problems: Displays errors of files. You can open the Problems view via the View menu or by clicking the error and warning icons in the editor status bar at the bottom.

    • Terminal: Provides a command line interface that you can use to type any shell command, including advanced Git commands and Zowe Command Line operations to interact with z/OS. You can open the terminal through the Terminal menu or by pressing Ctrl+` (Windows and Mac).

    • Edit and Selection: Provides essential operations for editing.

    • Go: Provides essential navigation controls.

    Last Updated:
    Contributors: Peter Haumer, Rudy Leonel Pichola Flores, Greg Lambert, Min Huang, Shi Kun Li, Peter Haumer, Prasang Prajapati
    - + diff --git a/Docs/using_code_snippets.html b/Docs/using_code_snippets.html index fdde1895d..a6cb264aa 100644 --- a/Docs/using_code_snippets.html +++ b/Docs/using_code_snippets.html @@ -41,11 +41,11 @@ } )(); Explore code snippets | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Explore code snippets

    If you would like to explore using code snippets, you can add some complexity to this exercise. For instance, you can make the Customer File a VSAM file. The editor provides a full list of VSAM statments that can be inserted into your code. To start, you can navigate to the File Control section of SAM1.cbl, then F1, select Insert Snippet, then enter VSAM in the Search bar. You will see a list of VSAM snippets. Scroll to the VSAM: KSDS Select/Assign Clause snippet and hit Enter. A pre-formatted SELECT/ASSIGN clause will be inserted. Notice that hitting the TAB key will send the cursor to each variable/operand that needs to be defined.

    From there, you can use the OPEN, READ, WRITE, REWRITE, and CLOSE VSAM snippets where appropriate.

    You can also explore using subsystem snippets, such as CICS, IMS, and DB2. For instance, you need to create another COBOL subroutine which will be called by SAM1 to make DB2 updates. You can create a new file in your COBOL folder named SAM3.cbl, then insert the model subroutine snippet (Search for Model) which will give you a template for a new subroutine program. You can explore the various Embedded SQL snippets by searching for SQL in the list. You can insert code to declare a cursor, open a cursor, select records, update, etc. There is even a snippet for a generic DB2 error handling routine.

    If you need to modify a CICS program, you can search for CICS snippets and you will notice all of the EXEC CICS statements available. Likewise, for IMS, you will see options for the many Working-Storage definition areas, as well as CALL statements with the many different functions available.

    Last Updated:
    Contributors: Greg Lambert, Peter Haumer
    - + diff --git a/Docs/whatsnew.html b/Docs/whatsnew.html index 40766e004..12baff044 100644 --- a/Docs/whatsnew.html +++ b/Docs/whatsnew.html @@ -41,11 +41,11 @@ } )(); Updates and user feedback | IBM Z® Open Editor - + -
    IBM Z® Open Editor

    Updates and user feedback

    IBM Z® Open Editor and its related components are on continuous delivery. Check out the following resources to stay current:

    Versions and change logs

    ComponentCurrent versionRelease dateDownloadChange log
    IBM Z Open Editor4.4.012 August 2024VS Code Marketplaceopen in new windowChange log on VS Code Marketplaceopen in new window
    IBM® RSE API Plug-in for Zowe™ CLI4.4.012 August 2024NPMjsopen in new windowChange log on VS Code Marketplaceopen in new window
    Zowe Explorer2.17.023 July 2024VS Code Marketplaceopen in new windowChange log on VS Code Marketplaceopen in new window
    Zowe CLI7.26.111 June 2024Zowe websiteopen in new windowChange log on Zowe CLI repositoryopen in new window

    Other updates and user feedback

    Last Updated:
    Contributors: Peter Haumer, Peter Haumer, Lauren Li, PETER HAUMER, Min Huang, Hestia Zhang, Lauren Li, Prasang-A-Prajapati
    - +
    IBM Z® Open Editor

    Updates and user feedback

    IBM Z® Open Editor and its related components are on continuous delivery. Check out the following resources to stay current:

    Versions and change logs

    ComponentCurrent versionRelease dateDownloadChange log
    IBM Z Open Editor4.5.019 September 2024VS Code Marketplaceopen in new windowChange log on VS Code Marketplaceopen in new window
    IBM® RSE API Plug-in for Zowe™ CLI4.5.019 September 2024NPMjsopen in new windowChange log on VS Code Marketplaceopen in new window
    Zowe Explorer2.18.05 September 2024VS Code Marketplaceopen in new windowChange log on VS Code Marketplaceopen in new window
    Zowe CLI7.29.1September 2024Zowe websiteopen in new windowChange log on Zowe CLI repositoryopen in new window

    Other updates and user feedback

    Last Updated:
    Contributors: Peter Haumer, Peter Haumer, Lauren Li, PETER HAUMER, Min Huang, Hestia Zhang, Lauren Li, Prasang-A-Prajapati
    + diff --git a/Docs/zapp.html b/Docs/zapp.html index b6f879b4f..f885f9340 100644 --- a/Docs/zapp.html +++ b/Docs/zapp.html @@ -41,7 +41,7 @@ } )(); Configuring your applications with ZAPP files | IBM Z® Open Editor - + @@ -142,6 +142,6 @@ - "${buildFile.basename}.log" - "BuildReport.*"

    The details for these profiles for User Build are documented in the Setting up the user buildopen in new window.

    Editing the zapp.yaml file with code completion

    Code completion requires that you have the Red Hat VS Code YAML extension installed and configured as outlined above. You can try it out as follows:

    1. Place your cursor behind the line with language: cobol (around Line 18) and press Enter to start a new line.
    2. Press Ctrl+Space to open up the code completion drop-down.

    It then shows one property that was not yet used in this property group, compilerOptions, that could still be added here. You can add it by simply clicking the item or you the keyboard's arrow and return keys.

    The same will also work with property values if they are enumeration types or boolean.

    1. Move the cursor at the end of the line type: local (around Line 21).
    2. Delete the word local and do another Ctrl+Space.

    It now shows you the two allowed options local and mvs in the drop-down that you can choose from.

    You also see in the drop-down various code snippets that could be inserted here. However, you see that properties are listed context-sensitive, i.e. the drop-down only shows entries that are allowed to be inserted here. Code snippets are not context sensitive and will always be displayed. You need to make sure you use them syntactically correct. The YAML editor extension will tell you with syntax errors when you insert incorrectly.

    Editing the zapp.yaml file with property group code snippets

    ZAPP also provides code snippets so that you can enter new property groups rapidly. The code snippets are only available in the code editor when you edit a zapp.yaml file. You will not find them in the VS Code Snippets gallery, because VS Code currently cannot distinguish between different YAML file types in their snippet gallery.

    To use these code snippets:

    1. Place your cursor at the empty line at the end of the property groups in the file (around Line 85).
    2. Press Ctrl+Space and you will see four code snippets listed in the drop-down.
    3. Navigate down and select ZAPP Remote MVS Property Groups by pressing the Enter key.
    4. You can see that a new property group is inserted with highlighted placeholders.
    5. Before clicking or typing anything else, while the placeholders are still highlighted, use the Tab and Shift+Tab keys to navigate between the placeholders and enter values for name, language (using another drop down), and syslib entries.
    6. At the end of the new property group, add another locations entry by adding a new line and entering a new value such as - USER1.SAMPLE.INCLUDES.

    Remember that you need to provide a valid YAML file. As the locations entry requires a string array in JSON, it now needs to be entered in YAML as an ordered list using - for each value.

    There is also a code snippet template for a complete ZAPP file. You can try it out as follows:

    1. In the current editor window for zapp.yaml, do a Select-All and delete all the contents of the file. You can withdraw the deletion later as the file is managed in Git.
    2. In the first line and column of the empty document, press Ctrl+Space and select the ZAPP Template snippet. Instead of scrolling all the way to the bottom, you can type that snippet name instead.
    3. You see that a snippet was inserted that contains general properties at the top as well as one property group with a local libraries entry. You can then modify as needed or add more property group entries using the respective snippets.

    Editing the zapp.yaml file with User Build code snippets

    You can specify all the workspace settings for a user build in ZAPP files as documented in Setting up the user buildopen in new window. User settings are still required to be stored in the VS Code user settings files in this release, but all workspace settings are available as tools profile in ZAPP.

    You can find an example for a DBB profile at the end of the sample ZAPP file from the zopeneditor-sample GitHub repository. If you removed all content as mentioned in the previous section, you can create a tools profile yourself as follows:

    1. Go to the end of your file behind the last property group to column 1.
    2. Type the key word profiles: and press Enter.
    3. As you can specify an ordered list of many profiles, start a new list by indenting and typing - followed by any of the properties proposed by the code completion.
    4. When you select the mandatory type property, you can use a drop-down to select the type of the profile. Right now, only the type dbb is supported.
    5. Once you selected the type dbb, you can add a settings: property, which defines an object of unordered properties that you can also enter after indentation with code completion.

    Instead of entering a DBB profile all manually, you can also use a code snippet provided by Z Open Editor as follows:

    1. In the column after the profiles: entry, press Ctrl+Space and select the ZAPP User Build Profile snippet.
    2. The snippets contain a full DBB profile with placeholders. You can then navigate by pressing Tab and replace the placeholders with your specific values.

    Reviewing syntax errors

    When you create an invalid zapp.yaml file by typing incorrect YAML or misspelling property names, the Red Hat YAML extensionopen in new window will show you syntax errors in the Problems view. You can try it out as follows:

    1. Remove a few letters from any of the properties to misspell it.
    2. Switch to the VS Code Problems view. Use the View > Problems View menu if you do not see it. This view will now show you the exact syntax error as well as the line and column it happened in.

    If you do not have the Red Hat YAML extension installed, you can still find simple error lists provided by Z Open Editor in the Output view as follows:

    1. Switch to the Output view. Use the View > Output View menu if you do not see it.
    2. On the right side of the Output view, select IBM Z Open Editor from the drop-down.
    3. Make some syntax errors. Note that whereas the Red Hat extension will show you errors right away, here you will not see any errors until you attempt a save.
    4. Save your file with the syntax error. Now the Output View will show you error messages such as should NOT have additional properties(additionalProperty:lauage).

    As you can see, the output here is much simpler and does not have line numbers. The Red Hat extension is by far the superior solution for editing ZAPP files as that extension includes a full YAML Language Server that generates an Outline view.

    Formatting your zapp.yaml file

    Another capability of the Red Hat YAML extension is the ability to format your ZAPP file consistently. If you used different indentations in places, you can simply correct the formatting of the entire file by using one of the following two ways to format:

    - + diff --git a/Docs/zcodeformatting.html b/Docs/zcodeformatting.html index a915d3999..6b802098d 100644 --- a/Docs/zcodeformatting.html +++ b/Docs/zcodeformatting.html @@ -41,7 +41,7 @@ } )(); Experimental: Formatting COBOL source code | IBM Z® Open Editor - + @@ -82,6 +82,6 @@ blocks: indentExecBlock: 5

    In this case, indentForAllBlocks is not allowed because indentExecBlocks is specified.

    Note: the indentForAllBlocks property is not allowed if any child properties underneath blocks are present.

    Learning the schema

    The built-in schema support of VS Code provides you with code completion and rich hovers that, together with the available code templates, allow you to learn the details behind the zcodeformat schema for writing these files. However, the formatter and schema is based on the code formatter available in IBM Developer for z/OS. See this documentation page a for a referenceopen in new window to learn how the different formatting options behave.

    Formatting your zcodeformat.yaml file

    Another capability of the Red Hat YAML extension is the ability to format your zcodeformat file consistently. For example, if you inadvertently used different indentations, you can simply correct the formatting of the entire file by using one of the following two formatting commands:

    - + diff --git a/Docs/zopeneditor_v3.html b/Docs/zopeneditor_v3.html index 90deff7e4..b99134ce1 100644 --- a/Docs/zopeneditor_v3.html +++ b/Docs/zopeneditor_v3.html @@ -41,7 +41,7 @@ } )(); Migrating from Z Open Editor v2 to v3 | IBM Z® Open Editor - + @@ -89,6 +89,6 @@ additionalDependencies: - application-conf

    As you can see in the example, the value of the new application setting can be referenced as a variable ${application} within the profile, such as for the Groovy command argument. Since user build requires IBM Dependency Based Build, the documentation with user build changes and enhancements is only available in IBM Documentationopen in new window.

    - + diff --git a/Docs/zowe_advanced_connection_scenarious.html b/Docs/zowe_advanced_connection_scenarious.html index 54dad15e9..8d797998f 100644 --- a/Docs/zowe_advanced_connection_scenarious.html +++ b/Docs/zowe_advanced_connection_scenarious.html @@ -41,11 +41,11 @@ } )(); Supported methods of authentication for z/OS using Zowe | IBM Z® Open Editor - +
    IBM Z® Open Editor

    Supported methods of authentication for z/OS using Zowe

    Zowe CLI and it's plug-ins have numerous ways available for users to authenticate and secure credentials. Secure credential encryptionopen in new window is now included in Zowe CLI, storing credentials and other values set by the user to be stored securely, using the local device's credential manager.

    Types of authentication supported by Zowe include passwords, passphrases, JSON web token (JWT) authentication, single sign-on (SSO), and multi-factor authentication (MFA). Zowe CLI requires authenticating with the Zowe API Mediation Layer (ML)open in new window for SSO, JWT, and MFA support.

    The RSE CLI plug-in supports passwords, passphrases, and JWT authentication directly with the RSE API host component. If the RSE API host component is registered with the Zowe API ML, all of the methods of authentication supported by the API ML will be available for RSE profiles as well.

    Single sign-on support

    After an RSE profile is created and is accessible in Zowe Explorer, users can use single sign-on (SSO) for connecting to the RSE API host component in Zowe Explorer 1.22.0 and later versions. JWTs are stored securely in the profile's file. For RSE profiles connecting directly to the RSE API, follow the steps below:

    Logging in to authentication service

    Zowe Explorer UI:

    1. Right-click the profile name in the Zowe Explorer tree view and click Login to Authentication Service.
    2. Enter credentials for z/OS connection when prompted.

    When the login is successful, you will receive the message Login to authentication service was successful. from Zowe Explorer.

    Zowe CLI:

    1. In the terminal, enter the command zowe rse auth login.
    2. Enter credentials for z/OS connection when prompted.

    When the login is successful, you will receive a message with information about the JWT, including the expiration date and time as well as the creation date and time of it.

    Logging out of authentication service

    Zowe Explorer UI:

    Right-click on the profile name in the Zowe Explorer tree view and select Logout from Authentication Service.

    When the logoff is successful, you will receive the message Logout from authentication service was successful. from Zowe Explorer.

    Zowe CLI:

    In the terminal, enter the command zowe rse auth logout.

    When the logoff is successful, you will receive the message JWT Token has been retired..

    If you are obtaining authentication tokens from the API Mediation Layer, see Connecting profiles to API Mediation Layeropen in new window.

    For an example of the team configuration file with RSE profile authenticating with API Mediation Layer, see Single sign-on support for IBM RSE CLI plugin.

    Multi-factor authentication

    You can do multi-factor authentication (MFA) and use Zowe team configuration profiles. MFA is supprted when API Meditation Layer is enabled on the host side. Zowe Explorer supports multi-factor authentication login. Simply use your temporary code as a password or choose the "Log into Authentication Service" option.

    Last Updated:
    Contributors: KRISTINA MAYO, Chun Hong Zheng
    - + diff --git a/Docs/zowe_explorer_v2.html b/Docs/zowe_explorer_v2.html index c4d98287f..df012c83c 100644 --- a/Docs/zowe_explorer_v2.html +++ b/Docs/zowe_explorer_v2.html @@ -41,7 +41,7 @@ } )(); Getting started with Zowe 2.0 | IBM Z® Open Editor - + @@ -51,6 +51,6 @@ } }

    Then make sure that the configuration files do not define any secure fields at all.

    - + diff --git a/Docs/zowe_submitjcl.html b/Docs/zowe_submitjcl.html index 637688eb6..a328d246b 100644 --- a/Docs/zowe_submitjcl.html +++ b/Docs/zowe_submitjcl.html @@ -41,7 +41,7 @@ } )(); Submitting JCL to compile, link, and run jobs tutorial | IBM Z® Open Editor - + @@ -68,6 +68,6 @@ zowe files download ds "USER1.SAMPLE.CUSTRPT"

    These two downloaded files are now on the left in your editor and ready for review. You also can open these files directly from the Remote Systems explorer by double-clicking each file or dragging these files to the editor.

    If you are exploring the REXX tutorial, you will notice a JCL called REXALLOC.jcl exists for allocating the necessary data sets to run the sample REXX program. There is not a JCL member to compile or run the REXX exec. After uploading RSAM1 and the input data files to your TSO data set, you can run it by using the following Zowe CLI command:

    zowe tso issue command "exec 'user1.sample.rexx(rsam1)'" -a <ACCT#>

    Note: If you create a TSO profile, -a ACCT# is not needed because it will be stored in that profile.

    While this REXX example is not interactive, it is possible to execute interactive REXX execs (and other commands) with the RSE CLI plug-in as demonstrated in Run interactive TSO commands.

    - + diff --git a/assets/404.233222d2.js b/assets/404.130cdeb2.js similarity index 89% rename from assets/404.233222d2.js rename to assets/404.130cdeb2.js index 216ea9080..26e255e8e 100644 --- a/assets/404.233222d2.js +++ b/assets/404.130cdeb2.js @@ -1 +1 @@ -import{f as i,u as _,g as p,r as f,o as k,a as v,b as o,t as c,d as L,w as g,h as l,e as x}from"./app.f6cb3ed9.js";const B={class:"theme-container"},N={class:"theme-default-content"},T=o("h1",null,"404",-1),V=i({setup(b){var a,s,n;const u=_(),e=p(),t=(a=e.value.notFound)!=null?a:["Not Found"],r=()=>t[Math.floor(Math.random()*t.length)],h=(s=e.value.home)!=null?s:u.value,m=(n=e.value.backToHome)!=null?n:"Back to home";return(C,M)=>{const d=f("RouterLink");return k(),v("div",B,[o("div",N,[T,o("blockquote",null,c(r()),1),L(d,{to:l(h)},{default:g(()=>[x(c(l(m)),1)]),_:1},8,["to"])])])}}});export{V as default}; +import{f as i,u as _,g as p,r as f,o as k,a as v,b as o,t as c,d as L,w as g,h as l,e as x}from"./app.daa93c96.js";const B={class:"theme-container"},N={class:"theme-default-content"},T=o("h1",null,"404",-1),V=i({setup(b){var a,s,n;const u=_(),e=p(),t=(a=e.value.notFound)!=null?a:["Not Found"],r=()=>t[Math.floor(Math.random()*t.length)],h=(s=e.value.home)!=null?s:u.value,m=(n=e.value.backToHome)!=null?n:"Back to home";return(C,M)=>{const d=f("RouterLink");return k(),v("div",B,[o("div",N,[T,o("blockquote",null,c(r()),1),L(d,{to:l(h)},{default:g(()=>[x(c(l(m)),1)]),_:1},8,["to"])])])}}});export{V as default}; diff --git a/assets/Layout.006ebc38.js b/assets/Layout.b8d46050.js similarity index 99% rename from assets/Layout.006ebc38.js rename to assets/Layout.b8d46050.js index f2f040be0..51c606e9f 100644 --- a/assets/Layout.006ebc38.js +++ b/assets/Layout.b8d46050.js @@ -1 +1 @@ -var Be=Object.defineProperty,Me=Object.defineProperties;var De=Object.getOwnPropertyDescriptors;var de=Object.getOwnPropertySymbols;var Ne=Object.prototype.hasOwnProperty,Ee=Object.prototype.propertyIsEnumerable;var ve=(l,t,e)=>t in l?Be(l,t,{enumerable:!0,configurable:!0,writable:!0,value:e}):l[t]=e,X=(l,t)=>{for(var e in t||(t={}))Ne.call(t,e)&&ve(l,e,t[e]);if(de)for(var e of de(t))Ee.call(t,e)&&ve(l,e,t[e]);return l},Y=(l,t)=>Me(l,De(t));import{r as R,o as a,a as c,d as $,f as x,i as I,j as p,k as _e,h as n,F as D,l as A,m as w,b as g,t as T,n as G,p as J,q as C,w as B,s as pe,v as y,e as U,x as q,y as Ie,z as Pe,A as Re,B as Q,C as Z,D as V,E as fe,G as me,H as P,u as be,g as M,T as ge,I as O,J as Ae,K as j,L as K,M as He,N as Oe,O as ee,P as ke,Q as $e,c as ze,R as Le,S as Fe,U as W,V as te,W as We,X as Ue,Y as Ve,Z as je}from"./app.f6cb3ed9.js";import{_ as Ke}from"./plugin-vue_export-helper.21dcd24c.js";const Ge={},qe={class:"theme-default-content custom"};function Xe(l,t){const e=R("Content");return a(),c("div",qe,[$(e)])}var Ye=Ke(Ge,[["render",Xe]]);const Je={key:0,class:"features"},Qe=x({setup(l){const t=I(),e=p(()=>_e(t.value.features)?t.value.features:[]);return(i,r)=>n(e).length?(a(),c("div",Je,[(a(!0),c(D,null,A(n(e),_=>(a(),c("div",{key:_.title,class:"feature"},[g("h2",null,T(_.title),1),g("p",null,T(_.details),1)]))),128))])):w("",!0)}}),Ze=["innerHTML"],et=["textContent"],tt=x({setup(l){const t=I(),e=p(()=>t.value.footer),i=p(()=>t.value.footerHtml);return(r,_)=>n(e)?(a(),c(D,{key:0},[n(i)?(a(),c("div",{key:0,class:"footer",innerHTML:n(e)},null,8,Ze)):(a(),c("div",{key:1,class:"footer",textContent:T(n(e))},null,8,et))],64)):w("",!0)}}),nt=["href","rel","target","aria-label"],at=x({inheritAttrs:!1}),E=x(Y(X({},at),{props:{item:{type:Object,required:!0}},setup(l){const t=l,e=G(),i=Re(),{item:r}=J(t),_=p(()=>q(r.value.link)),f=p(()=>Ie(r.value.link)||Pe(r.value.link)),h=p(()=>{if(!f.value){if(r.value.target)return r.value.target;if(_.value)return"_blank"}}),s=p(()=>h.value==="_blank"),o=p(()=>!_.value&&!f.value&&!s.value),u=p(()=>{if(!f.value){if(r.value.rel)return r.value.rel;if(s.value)return"noopener noreferrer"}}),d=p(()=>r.value.ariaLabel||r.value.text),v=p(()=>{const L=Object.keys(i.value.locales);return L.length?!L.some(m=>m===r.value.link):r.value.link!=="/"}),b=p(()=>v.value?e.path.startsWith(r.value.link):!1),k=p(()=>o.value?r.value.activeMatch?new RegExp(r.value.activeMatch).test(e.path):b.value:!1);return(L,m)=>{const S=R("RouterLink"),N=R("ExternalLinkIcon");return n(o)?(a(),C(S,pe({key:0,class:{"router-link-active":n(k)},to:n(r).link,"aria-label":n(d)},L.$attrs),{default:B(()=>[y(L.$slots,"before"),U(" "+T(n(r).text)+" ",1),y(L.$slots,"after")]),_:3},16,["class","to","aria-label"])):(a(),c("a",pe({key:1,class:"external-link",href:n(r).link,rel:n(u),target:n(h),"aria-label":n(d)},L.$attrs),[y(L.$slots,"before"),U(" "+T(n(r).text)+" ",1),n(s)?(a(),C(N,{key:0})):w("",!0),y(L.$slots,"after")],16,nt))}}})),st={class:"hero"},rt={key:0,id:"main-title"},ot={key:1,class:"description"},lt={key:2,class:"actions"},ut=x({setup(l){const t=I(),e=Q(),i=Z(),r=p(()=>i.value&&t.value.heroImageDark!==void 0?t.value.heroImageDark:t.value.heroImage),_=p(()=>t.value.heroText===null?null:t.value.heroText||e.value.title||"Hello"),f=p(()=>t.value.heroAlt||_.value||"hero"),h=p(()=>t.value.tagline===null?null:t.value.tagline||e.value.description||"Welcome to your VuePress site"),s=p(()=>_e(t.value.actions)?t.value.actions.map(({text:u,link:d,type:v="primary"})=>({text:u,link:d,type:v})):[]),o=()=>{if(!r.value)return null;const u=V("img",{src:fe(r.value),alt:f.value});return t.value.heroImageDark===void 0?u:V(me,()=>u)};return(u,d)=>(a(),c("header",st,[$(o),n(_)?(a(),c("h1",rt,T(n(_)),1)):w("",!0),n(h)?(a(),c("p",ot,T(n(h)),1)):w("",!0),n(s).length?(a(),c("p",lt,[(a(!0),c(D,null,A(n(s),v=>(a(),C(E,{key:v.text,class:P(["action-button",[v.type]]),item:v},null,8,["class","item"]))),128))])):w("",!0)]))}}),it={class:"home"},ct=x({setup(l){return(t,e)=>(a(),c("main",it,[$(ut),$(Qe),$(Ye),$(tt)]))}}),dt=x({setup(l){const t=be(),e=Q(),i=M(),r=Z(),_=p(()=>i.value.home||t.value),f=p(()=>e.value.title),h=p(()=>r.value&&i.value.logoDark!==void 0?i.value.logoDark:i.value.logo),s=()=>{if(!h.value)return null;const o=V("img",{class:"logo",src:fe(h.value),alt:f.value});return i.value.logoDark===void 0?o:V(me,()=>o)};return(o,u)=>{const d=R("RouterLink");return a(),C(d,{to:n(_)},{default:B(()=>[$(s),n(f)?(a(),c("span",{key:0,class:P(["site-name",{"can-hide":n(h)}])},T(n(f)),3)):w("",!0)]),_:1},8,["to"])}}}),ye=x({setup(l){const t=i=>{i.style.height=i.scrollHeight+"px"},e=i=>{i.style.height=""};return(i,r)=>(a(),C(ge,{name:"dropdown",onEnter:t,onAfterEnter:e,onBeforeLeave:t},{default:B(()=>[y(i.$slots,"default")]),_:3}))}}),vt=["aria-label"],pt={class:"title"},ht=g("span",{class:"arrow down"},null,-1),_t=["aria-label"],ft={class:"title"},mt={class:"navbar-dropdown"},bt={class:"navbar-dropdown-subtitle"},gt={key:1},kt={class:"navbar-dropdown-subitem-wrapper"},$t=x({props:{item:{type:Object,required:!0}},setup(l){const t=l,{item:e}=J(t),i=p(()=>e.value.ariaLabel||e.value.text),r=O(!1),_=G();Ae(()=>_.path,()=>{r.value=!1});const f=s=>{s.detail===0?r.value=!r.value:r.value=!1},h=(s,o)=>o[o.length-1]===s;return(s,o)=>(a(),c("div",{class:P(["navbar-dropdown-wrapper",{open:r.value}])},[g("button",{class:"navbar-dropdown-title",type:"button","aria-label":n(i),onClick:f},[g("span",pt,T(n(e).text),1),ht],8,vt),g("button",{class:"navbar-dropdown-title-mobile",type:"button","aria-label":n(i),onClick:o[0]||(o[0]=u=>r.value=!r.value)},[g("span",ft,T(n(e).text),1),g("span",{class:P(["arrow",r.value?"down":"right"])},null,2)],8,_t),$(ye,null,{default:B(()=>[j(g("ul",mt,[(a(!0),c(D,null,A(n(e).children,u=>(a(),c("li",{key:u.text,class:"navbar-dropdown-item"},[u.children?(a(),c(D,{key:0},[g("h4",bt,[u.link?(a(),C(E,{key:0,item:u,onFocusout:d=>h(u,n(e).children)&&u.children.length===0&&(r.value=!1)},null,8,["item","onFocusout"])):(a(),c("span",gt,T(u.text),1))]),g("ul",kt,[(a(!0),c(D,null,A(u.children,d=>(a(),c("li",{key:d.link,class:"navbar-dropdown-subitem"},[$(E,{item:d,onFocusout:v=>h(d,u.children)&&h(u,n(e).children)&&(r.value=!1)},null,8,["item","onFocusout"])]))),128))])],64)):(a(),C(E,{key:1,item:u,onFocusout:d=>h(u,n(e).children)&&(r.value=!1)},null,8,["item","onFocusout"]))]))),128))],512),[[K,r.value]])]),_:1})],2))}}),he=l=>decodeURI(l).replace(/#.*$/,"").replace(/(index)?\.(md|html)$/,""),Lt=(l,t)=>{if(t.hash===l)return!0;const e=he(t.path),i=he(l);return e===i},we=(l,t)=>l.link&&Lt(l.link,t)?!0:l.children?l.children.some(e=>we(e,t)):!1,xe=l=>!q(l)||/github\.com/.test(l)?"GitHub":/bitbucket\.org/.test(l)?"Bitbucket":/gitlab\.com/.test(l)?"GitLab":/gitee\.com/.test(l)?"Gitee":null,yt={GitHub:":repo/edit/:branch/:path",GitLab:":repo/-/edit/:branch/:path",Gitee:":repo/edit/:branch/:path",Bitbucket:":repo/src/:branch/:path?mode=edit&spa=0&at=:branch&fileviewer=file-view-default"},wt=({docsRepo:l,editLinkPattern:t})=>{if(t)return t;const e=xe(l);return e!==null?yt[e]:null},xt=({docsRepo:l,docsBranch:t,docsDir:e,filePathRelative:i,editLinkPattern:r})=>{if(!i)return null;const _=wt({docsRepo:l,editLinkPattern:r});return _?_.replace(/:repo/,q(l)?l:`https://github.com/${l}`).replace(/:branch/,t).replace(/:path/,He(`${Oe(e)}/${i}`)):null},Ct={key:0,class:"navbar-items"},Ce=x({setup(l){const t=()=>{const o=ee(),u=be(),d=Q(),v=M();return p(()=>{var S,N;const b=Object.keys(d.value.locales);if(b.length<2)return[];const k=o.currentRoute.value.path,L=o.currentRoute.value.fullPath;return[{text:(S=v.value.selectLanguageText)!=null?S:"unknown language",ariaLabel:(N=v.value.selectLanguageAriaLabel)!=null?N:"unkown language",children:b.map(H=>{var se,re,oe,le,ue,ie;const z=(re=(se=d.value.locales)==null?void 0:se[H])!=null?re:{},ne=(le=(oe=v.value.locales)==null?void 0:oe[H])!=null?le:{},ae=`${z.lang}`,Te=(ue=ne.selectLanguageName)!=null?ue:ae;let F;if(ae===d.value.lang)F=L;else{const ce=k.replace(u.value,H);o.getRoutes().some(Se=>Se.path===ce)?F=ce:F=(ie=ne.home)!=null?ie:H}return{text:Te,link:F}})}]})},e=()=>{const o=M(),u=p(()=>o.value.repo),d=p(()=>u.value?xe(u.value):null),v=p(()=>u.value&&!q(u.value)?`https://github.com/${u.value}`:u.value),b=p(()=>v.value?o.value.repoLabel?o.value.repoLabel:d.value===null?"Source":d.value:null);return p(()=>!v.value||!b.value?[]:[{text:b.value,link:v.value}])},i=o=>ke(o)?$e(o):o.children?Y(X({},o),{children:o.children.map(i)}):o,_=(()=>{const o=M();return p(()=>(o.value.navbar||[]).map(i))})(),f=t(),h=e(),s=p(()=>[..._.value,...f.value,...h.value]);return(o,u)=>n(s).length?(a(),c("nav",Ct,[(a(!0),c(D,null,A(n(s),d=>(a(),c("div",{key:d.text,class:"navbar-item"},[d.children?(a(),C($t,{key:0,item:d},null,8,["item"])):(a(),C(E,{key:1,item:d},null,8,["item"]))]))),128))])):w("",!0)}}),Tt=["title"],St={class:"icon",focusable:"false",viewBox:"0 0 32 32"},Bt=ze('',9),Mt=[Bt],Dt={class:"icon",focusable:"false",viewBox:"0 0 32 32"},Nt=g("path",{d:"M13.502 5.414a15.075 15.075 0 0 0 11.594 18.194a11.113 11.113 0 0 1-7.975 3.39c-.138 0-.278.005-.418 0a11.094 11.094 0 0 1-3.2-21.584M14.98 3a1.002 1.002 0 0 0-.175.016a13.096 13.096 0 0 0 1.825 25.981c.164.006.328 0 .49 0a13.072 13.072 0 0 0 10.703-5.555a1.01 1.01 0 0 0-.783-1.565A13.08 13.08 0 0 1 15.89 4.38A1.015 1.015 0 0 0 14.98 3z",fill:"currentColor"},null,-1),Et=[Nt],It=x({setup(l){const t=M(),e=Z(),i=()=>{e.value=!e.value};return(r,_)=>(a(),c("button",{class:"toggle-dark-button",title:n(t).toggleDarkMode,onClick:i},[j((a(),c("svg",St,Mt,512)),[[K,!n(e)]]),j((a(),c("svg",Dt,Et,512)),[[K,n(e)]])],8,Tt))}}),Pt=["title"],Rt=g("div",{class:"icon","aria-hidden":"true"},[g("span"),g("span"),g("span")],-1),At=[Rt],Ht=x({emits:["toggle"],setup(l){const t=M();return(e,i)=>(a(),c("div",{class:"toggle-sidebar-button",title:n(t).toggleSidebar,"aria-expanded":"false",role:"button",tabindex:"0",onClick:i[0]||(i[0]=r=>e.$emit("toggle"))},At,8,Pt))}}),Ot=x({emits:["toggle-sidebar"],setup(l){const t=M(),e=O(null),i=O(null),r=O(0),_=p(()=>r.value?{maxWidth:r.value+"px"}:{}),f=p(()=>t.value.darkMode);Le(()=>{const o=h(e.value,"paddingLeft")+h(e.value,"paddingRight"),u=()=>{var d;window.innerWidth<=719?r.value=0:r.value=e.value.offsetWidth-o-(((d=i.value)==null?void 0:d.offsetWidth)||0)};u(),window.addEventListener("resize",u,!1),window.addEventListener("orientationchange",u,!1)});function h(s,o){var v,b,k;const u=(k=(b=(v=s==null?void 0:s.ownerDocument)==null?void 0:v.defaultView)==null?void 0:b.getComputedStyle(s,null))==null?void 0:k[o],d=Number.parseInt(u,10);return Number.isNaN(d)?0:d}return(s,o)=>{const u=R("NavbarSearch");return a(),c("header",{ref_key:"navbar",ref:e,class:"navbar"},[$(Ht,{onToggle:o[0]||(o[0]=d=>s.$emit("toggle-sidebar"))}),g("span",{ref_key:"navbarBrand",ref:i},[$(dt)],512),g("div",{class:"navbar-items-wrapper",style:Fe(n(_))},[y(s.$slots,"before"),$(Ce,{class:"can-hide"}),y(s.$slots,"after"),n(f)?(a(),C(It,{key:0})):w("",!0),$(u)],4)],512)}}}),zt={class:"page-meta"},Ft={key:0,class:"meta-item edit-link"},Wt={key:1,class:"meta-item last-updated"},Ut={class:"meta-item-label"},Vt={class:"meta-item-info"},jt={key:2,class:"meta-item contributors"},Kt={class:"meta-item-label"},Gt={class:"meta-item-info"},qt=["title"],Xt=U(", "),Yt=x({setup(l){const t=()=>{const s=M(),o=W(),u=I();return p(()=>{var N,H,z;if(!((H=(N=u.value.editLink)!=null?N:s.value.editLink)!=null?H:!0))return null;const{repo:v,docsRepo:b=v,docsBranch:k="main",docsDir:L="",editLinkText:m}=s.value;if(!b)return null;const S=xt({docsRepo:b,docsBranch:k,docsDir:L,filePathRelative:o.value.filePathRelative,editLinkPattern:(z=u.value.editLinkPattern)!=null?z:s.value.editLinkPattern});return S?{text:m!=null?m:"Edit this page",link:S}:null})},e=()=>{const s=M(),o=W(),u=I();return p(()=>{var b,k,L,m;return!((k=(b=u.value.lastUpdated)!=null?b:s.value.lastUpdated)!=null?k:!0)||!((L=o.value.git)!=null&&L.updatedTime)?null:new Date((m=o.value.git)==null?void 0:m.updatedTime).toLocaleString()})},i=()=>{const s=M(),o=W(),u=I();return p(()=>{var v,b,k,L;return((b=(v=u.value.contributors)!=null?v:s.value.contributors)!=null?b:!0)&&(L=(k=o.value.git)==null?void 0:k.contributors)!=null?L:null})},r=M(),_=t(),f=e(),h=i();return(s,o)=>{const u=R("ClientOnly");return a(),c("footer",zt,[n(_)?(a(),c("div",Ft,[$(E,{class:"meta-item-label",item:n(_)},null,8,["item"])])):w("",!0),n(f)?(a(),c("div",Wt,[g("span",Ut,T(n(r).lastUpdatedText)+": ",1),$(u,null,{default:B(()=>[g("span",Vt,T(n(f)),1)]),_:1})])):w("",!0),n(h)&&n(h).length?(a(),c("div",jt,[g("span",Kt,T(n(r).contributorsText)+": ",1),g("span",Gt,[(a(!0),c(D,null,A(n(h),(d,v)=>(a(),c(D,{key:v},[g("span",{class:"contributor",title:`email: ${d.email}`},T(d.name),9,qt),v!==n(h).length-1?(a(),c(D,{key:0},[Xt],64)):w("",!0)],64))),128))])])):w("",!0)])}}}),Jt={key:0,class:"page-nav"},Qt={class:"inner"},Zt={key:0,class:"prev"},en={key:1,class:"next"},tn=x({setup(l){const t=s=>s===!1?null:ke(s)?$e(s):We(s)?s:!1,e=(s,o,u)=>{const d=s.findIndex(v=>v.link===o);if(d!==-1){const v=s[d+u];return v!=null&&v.link?v:null}for(const v of s)if(v.children){const b=e(v.children,o,u);if(b)return b}return null},i=I(),r=te(),_=G(),f=p(()=>{const s=t(i.value.prev);return s!==!1?s:e(r.value,_.path,-1)}),h=p(()=>{const s=t(i.value.next);return s!==!1?s:e(r.value,_.path,1)});return(s,o)=>n(f)||n(h)?(a(),c("nav",Jt,[g("p",Qt,[n(f)?(a(),c("span",Zt,[$(E,{item:n(f)},null,8,["item"])])):w("",!0),n(h)?(a(),c("span",en,[$(E,{item:n(h)},null,8,["item"])])):w("",!0)])])):w("",!0)}}),nn={class:"page"},an={class:"theme-default-content"},sn=x({setup(l){return(t,e)=>{const i=R("Content");return a(),c("main",nn,[y(t.$slots,"top"),g("div",an,[$(i)]),$(Yt),$(tn),y(t.$slots,"bottom")])}}}),rn={class:"sidebar-item-children"},on=x({props:{item:{type:Object,required:!0},depth:{type:Number,required:!1,default:0}},setup(l){const t=l,{item:e,depth:i}=J(t),r=G(),_=ee(),f=p(()=>we(e.value,r)),h=p(()=>({"sidebar-item":!0,"sidebar-heading":i.value===0,active:f.value,collapsible:e.value.collapsible})),s=O(!0),o=O(void 0);return e.value.collapsible&&(s.value=f.value,o.value=()=>{s.value=!s.value},_.afterEach(()=>{s.value=f.value})),(u,d)=>{var b;const v=R("SidebarItem",!0);return a(),c("li",null,[n(e).link?(a(),C(E,{key:0,class:P(n(h)),item:n(e)},null,8,["class","item"])):(a(),c("p",{key:1,tabindex:"0",class:P(n(h)),onClick:d[0]||(d[0]=(...k)=>o.value&&o.value(...k)),onKeydown:d[1]||(d[1]=Ue((...k)=>o.value&&o.value(...k),["enter"]))},[U(T(n(e).text)+" ",1),n(e).collapsible?(a(),c("span",{key:0,class:P(["arrow",s.value?"down":"right"])},null,2)):w("",!0)],34)),(b=n(e).children)!=null&&b.length?(a(),C(ye,{key:2},{default:B(()=>[j(g("ul",rn,[(a(!0),c(D,null,A(n(e).children,k=>(a(),C(v,{key:`${n(i)}${k.text}${k.link}`,item:k,depth:n(i)+1},null,8,["item","depth"]))),128))],512),[[K,s.value]])]),_:1})):w("",!0)])}}}),ln={key:0,class:"sidebar-items"},un=x({setup(l){const t=te();return(e,i)=>n(t).length?(a(),c("ul",ln,[(a(!0),c(D,null,A(n(t),r=>(a(),C(on,{key:r.link||r.text,item:r},null,8,["item"]))),128))])):w("",!0)}}),cn={class:"sidebar"},dn=x({setup(l){return(t,e)=>(a(),c("aside",cn,[$(Ce),y(t.$slots,"top"),$(un),y(t.$slots,"bottom")]))}}),_n=x({setup(l){const t=W(),e=I(),i=M(),r=p(()=>e.value.navbar!==!1&&i.value.navbar!==!1),_=te(),f=O(!1),h=m=>{f.value=typeof m=="boolean"?m:!f.value},s={x:0,y:0},o=m=>{s.x=m.changedTouches[0].clientX,s.y=m.changedTouches[0].clientY},u=m=>{const S=m.changedTouches[0].clientX-s.x,N=m.changedTouches[0].clientY-s.y;Math.abs(S)>Math.abs(N)&&Math.abs(S)>40&&(S>0&&s.x<=80?h(!0):h(!1))},d=p(()=>[{"no-navbar":!r.value,"no-sidebar":!_.value.length,"sidebar-open":f.value},e.value.pageClass]);let v;Le(()=>{v=ee().afterEach(()=>{h(!1)})}),Ve(()=>{v()});const b=je(),k=b.resolve,L=b.pending;return(m,S)=>(a(),c("div",{class:P(["theme-container",n(d)]),onTouchstart:o,onTouchend:u},[y(m.$slots,"navbar",{},()=>[n(r)?(a(),C(Ot,{key:0,onToggleSidebar:h},{before:B(()=>[y(m.$slots,"navbar-before")]),after:B(()=>[y(m.$slots,"navbar-after")]),_:3})):w("",!0)]),g("div",{class:"sidebar-mask",onClick:S[0]||(S[0]=N=>h(!1))}),y(m.$slots,"sidebar",{},()=>[$(dn,null,{top:B(()=>[y(m.$slots,"sidebar-top")]),bottom:B(()=>[y(m.$slots,"sidebar-bottom")]),_:3})]),y(m.$slots,"page",{},()=>[n(e).home?(a(),C(ct,{key:0})):(a(),C(ge,{key:1,name:"fade-slide-y",mode:"out-in",onBeforeEnter:n(k),onBeforeLeave:n(L)},{default:B(()=>[(a(),C(sn,{key:n(t).path},{top:B(()=>[y(m.$slots,"page-top")]),bottom:B(()=>[y(m.$slots,"page-bottom")]),_:3}))]),_:3},8,["onBeforeEnter","onBeforeLeave"]))])],34))}});export{_n as default}; +var Be=Object.defineProperty,Me=Object.defineProperties;var De=Object.getOwnPropertyDescriptors;var de=Object.getOwnPropertySymbols;var Ne=Object.prototype.hasOwnProperty,Ee=Object.prototype.propertyIsEnumerable;var ve=(l,t,e)=>t in l?Be(l,t,{enumerable:!0,configurable:!0,writable:!0,value:e}):l[t]=e,X=(l,t)=>{for(var e in t||(t={}))Ne.call(t,e)&&ve(l,e,t[e]);if(de)for(var e of de(t))Ee.call(t,e)&&ve(l,e,t[e]);return l},Y=(l,t)=>Me(l,De(t));import{r as R,o as a,a as c,d as $,f as x,i as I,j as p,k as _e,h as n,F as D,l as A,m as w,b as g,t as T,n as G,p as J,q as C,w as B,s as pe,v as y,e as U,x as q,y as Ie,z as Pe,A as Re,B as Q,C as Z,D as V,E as fe,G as me,H as P,u as be,g as M,T as ge,I as O,J as Ae,K as j,L as K,M as He,N as Oe,O as ee,P as ke,Q as $e,c as ze,R as Le,S as Fe,U as W,V as te,W as We,X as Ue,Y as Ve,Z as je}from"./app.daa93c96.js";import{_ as Ke}from"./plugin-vue_export-helper.21dcd24c.js";const Ge={},qe={class:"theme-default-content custom"};function Xe(l,t){const e=R("Content");return a(),c("div",qe,[$(e)])}var Ye=Ke(Ge,[["render",Xe]]);const Je={key:0,class:"features"},Qe=x({setup(l){const t=I(),e=p(()=>_e(t.value.features)?t.value.features:[]);return(i,r)=>n(e).length?(a(),c("div",Je,[(a(!0),c(D,null,A(n(e),_=>(a(),c("div",{key:_.title,class:"feature"},[g("h2",null,T(_.title),1),g("p",null,T(_.details),1)]))),128))])):w("",!0)}}),Ze=["innerHTML"],et=["textContent"],tt=x({setup(l){const t=I(),e=p(()=>t.value.footer),i=p(()=>t.value.footerHtml);return(r,_)=>n(e)?(a(),c(D,{key:0},[n(i)?(a(),c("div",{key:0,class:"footer",innerHTML:n(e)},null,8,Ze)):(a(),c("div",{key:1,class:"footer",textContent:T(n(e))},null,8,et))],64)):w("",!0)}}),nt=["href","rel","target","aria-label"],at=x({inheritAttrs:!1}),E=x(Y(X({},at),{props:{item:{type:Object,required:!0}},setup(l){const t=l,e=G(),i=Re(),{item:r}=J(t),_=p(()=>q(r.value.link)),f=p(()=>Ie(r.value.link)||Pe(r.value.link)),h=p(()=>{if(!f.value){if(r.value.target)return r.value.target;if(_.value)return"_blank"}}),s=p(()=>h.value==="_blank"),o=p(()=>!_.value&&!f.value&&!s.value),u=p(()=>{if(!f.value){if(r.value.rel)return r.value.rel;if(s.value)return"noopener noreferrer"}}),d=p(()=>r.value.ariaLabel||r.value.text),v=p(()=>{const L=Object.keys(i.value.locales);return L.length?!L.some(m=>m===r.value.link):r.value.link!=="/"}),b=p(()=>v.value?e.path.startsWith(r.value.link):!1),k=p(()=>o.value?r.value.activeMatch?new RegExp(r.value.activeMatch).test(e.path):b.value:!1);return(L,m)=>{const S=R("RouterLink"),N=R("ExternalLinkIcon");return n(o)?(a(),C(S,pe({key:0,class:{"router-link-active":n(k)},to:n(r).link,"aria-label":n(d)},L.$attrs),{default:B(()=>[y(L.$slots,"before"),U(" "+T(n(r).text)+" ",1),y(L.$slots,"after")]),_:3},16,["class","to","aria-label"])):(a(),c("a",pe({key:1,class:"external-link",href:n(r).link,rel:n(u),target:n(h),"aria-label":n(d)},L.$attrs),[y(L.$slots,"before"),U(" "+T(n(r).text)+" ",1),n(s)?(a(),C(N,{key:0})):w("",!0),y(L.$slots,"after")],16,nt))}}})),st={class:"hero"},rt={key:0,id:"main-title"},ot={key:1,class:"description"},lt={key:2,class:"actions"},ut=x({setup(l){const t=I(),e=Q(),i=Z(),r=p(()=>i.value&&t.value.heroImageDark!==void 0?t.value.heroImageDark:t.value.heroImage),_=p(()=>t.value.heroText===null?null:t.value.heroText||e.value.title||"Hello"),f=p(()=>t.value.heroAlt||_.value||"hero"),h=p(()=>t.value.tagline===null?null:t.value.tagline||e.value.description||"Welcome to your VuePress site"),s=p(()=>_e(t.value.actions)?t.value.actions.map(({text:u,link:d,type:v="primary"})=>({text:u,link:d,type:v})):[]),o=()=>{if(!r.value)return null;const u=V("img",{src:fe(r.value),alt:f.value});return t.value.heroImageDark===void 0?u:V(me,()=>u)};return(u,d)=>(a(),c("header",st,[$(o),n(_)?(a(),c("h1",rt,T(n(_)),1)):w("",!0),n(h)?(a(),c("p",ot,T(n(h)),1)):w("",!0),n(s).length?(a(),c("p",lt,[(a(!0),c(D,null,A(n(s),v=>(a(),C(E,{key:v.text,class:P(["action-button",[v.type]]),item:v},null,8,["class","item"]))),128))])):w("",!0)]))}}),it={class:"home"},ct=x({setup(l){return(t,e)=>(a(),c("main",it,[$(ut),$(Qe),$(Ye),$(tt)]))}}),dt=x({setup(l){const t=be(),e=Q(),i=M(),r=Z(),_=p(()=>i.value.home||t.value),f=p(()=>e.value.title),h=p(()=>r.value&&i.value.logoDark!==void 0?i.value.logoDark:i.value.logo),s=()=>{if(!h.value)return null;const o=V("img",{class:"logo",src:fe(h.value),alt:f.value});return i.value.logoDark===void 0?o:V(me,()=>o)};return(o,u)=>{const d=R("RouterLink");return a(),C(d,{to:n(_)},{default:B(()=>[$(s),n(f)?(a(),c("span",{key:0,class:P(["site-name",{"can-hide":n(h)}])},T(n(f)),3)):w("",!0)]),_:1},8,["to"])}}}),ye=x({setup(l){const t=i=>{i.style.height=i.scrollHeight+"px"},e=i=>{i.style.height=""};return(i,r)=>(a(),C(ge,{name:"dropdown",onEnter:t,onAfterEnter:e,onBeforeLeave:t},{default:B(()=>[y(i.$slots,"default")]),_:3}))}}),vt=["aria-label"],pt={class:"title"},ht=g("span",{class:"arrow down"},null,-1),_t=["aria-label"],ft={class:"title"},mt={class:"navbar-dropdown"},bt={class:"navbar-dropdown-subtitle"},gt={key:1},kt={class:"navbar-dropdown-subitem-wrapper"},$t=x({props:{item:{type:Object,required:!0}},setup(l){const t=l,{item:e}=J(t),i=p(()=>e.value.ariaLabel||e.value.text),r=O(!1),_=G();Ae(()=>_.path,()=>{r.value=!1});const f=s=>{s.detail===0?r.value=!r.value:r.value=!1},h=(s,o)=>o[o.length-1]===s;return(s,o)=>(a(),c("div",{class:P(["navbar-dropdown-wrapper",{open:r.value}])},[g("button",{class:"navbar-dropdown-title",type:"button","aria-label":n(i),onClick:f},[g("span",pt,T(n(e).text),1),ht],8,vt),g("button",{class:"navbar-dropdown-title-mobile",type:"button","aria-label":n(i),onClick:o[0]||(o[0]=u=>r.value=!r.value)},[g("span",ft,T(n(e).text),1),g("span",{class:P(["arrow",r.value?"down":"right"])},null,2)],8,_t),$(ye,null,{default:B(()=>[j(g("ul",mt,[(a(!0),c(D,null,A(n(e).children,u=>(a(),c("li",{key:u.text,class:"navbar-dropdown-item"},[u.children?(a(),c(D,{key:0},[g("h4",bt,[u.link?(a(),C(E,{key:0,item:u,onFocusout:d=>h(u,n(e).children)&&u.children.length===0&&(r.value=!1)},null,8,["item","onFocusout"])):(a(),c("span",gt,T(u.text),1))]),g("ul",kt,[(a(!0),c(D,null,A(u.children,d=>(a(),c("li",{key:d.link,class:"navbar-dropdown-subitem"},[$(E,{item:d,onFocusout:v=>h(d,u.children)&&h(u,n(e).children)&&(r.value=!1)},null,8,["item","onFocusout"])]))),128))])],64)):(a(),C(E,{key:1,item:u,onFocusout:d=>h(u,n(e).children)&&(r.value=!1)},null,8,["item","onFocusout"]))]))),128))],512),[[K,r.value]])]),_:1})],2))}}),he=l=>decodeURI(l).replace(/#.*$/,"").replace(/(index)?\.(md|html)$/,""),Lt=(l,t)=>{if(t.hash===l)return!0;const e=he(t.path),i=he(l);return e===i},we=(l,t)=>l.link&&Lt(l.link,t)?!0:l.children?l.children.some(e=>we(e,t)):!1,xe=l=>!q(l)||/github\.com/.test(l)?"GitHub":/bitbucket\.org/.test(l)?"Bitbucket":/gitlab\.com/.test(l)?"GitLab":/gitee\.com/.test(l)?"Gitee":null,yt={GitHub:":repo/edit/:branch/:path",GitLab:":repo/-/edit/:branch/:path",Gitee:":repo/edit/:branch/:path",Bitbucket:":repo/src/:branch/:path?mode=edit&spa=0&at=:branch&fileviewer=file-view-default"},wt=({docsRepo:l,editLinkPattern:t})=>{if(t)return t;const e=xe(l);return e!==null?yt[e]:null},xt=({docsRepo:l,docsBranch:t,docsDir:e,filePathRelative:i,editLinkPattern:r})=>{if(!i)return null;const _=wt({docsRepo:l,editLinkPattern:r});return _?_.replace(/:repo/,q(l)?l:`https://github.com/${l}`).replace(/:branch/,t).replace(/:path/,He(`${Oe(e)}/${i}`)):null},Ct={key:0,class:"navbar-items"},Ce=x({setup(l){const t=()=>{const o=ee(),u=be(),d=Q(),v=M();return p(()=>{var S,N;const b=Object.keys(d.value.locales);if(b.length<2)return[];const k=o.currentRoute.value.path,L=o.currentRoute.value.fullPath;return[{text:(S=v.value.selectLanguageText)!=null?S:"unknown language",ariaLabel:(N=v.value.selectLanguageAriaLabel)!=null?N:"unkown language",children:b.map(H=>{var se,re,oe,le,ue,ie;const z=(re=(se=d.value.locales)==null?void 0:se[H])!=null?re:{},ne=(le=(oe=v.value.locales)==null?void 0:oe[H])!=null?le:{},ae=`${z.lang}`,Te=(ue=ne.selectLanguageName)!=null?ue:ae;let F;if(ae===d.value.lang)F=L;else{const ce=k.replace(u.value,H);o.getRoutes().some(Se=>Se.path===ce)?F=ce:F=(ie=ne.home)!=null?ie:H}return{text:Te,link:F}})}]})},e=()=>{const o=M(),u=p(()=>o.value.repo),d=p(()=>u.value?xe(u.value):null),v=p(()=>u.value&&!q(u.value)?`https://github.com/${u.value}`:u.value),b=p(()=>v.value?o.value.repoLabel?o.value.repoLabel:d.value===null?"Source":d.value:null);return p(()=>!v.value||!b.value?[]:[{text:b.value,link:v.value}])},i=o=>ke(o)?$e(o):o.children?Y(X({},o),{children:o.children.map(i)}):o,_=(()=>{const o=M();return p(()=>(o.value.navbar||[]).map(i))})(),f=t(),h=e(),s=p(()=>[..._.value,...f.value,...h.value]);return(o,u)=>n(s).length?(a(),c("nav",Ct,[(a(!0),c(D,null,A(n(s),d=>(a(),c("div",{key:d.text,class:"navbar-item"},[d.children?(a(),C($t,{key:0,item:d},null,8,["item"])):(a(),C(E,{key:1,item:d},null,8,["item"]))]))),128))])):w("",!0)}}),Tt=["title"],St={class:"icon",focusable:"false",viewBox:"0 0 32 32"},Bt=ze('',9),Mt=[Bt],Dt={class:"icon",focusable:"false",viewBox:"0 0 32 32"},Nt=g("path",{d:"M13.502 5.414a15.075 15.075 0 0 0 11.594 18.194a11.113 11.113 0 0 1-7.975 3.39c-.138 0-.278.005-.418 0a11.094 11.094 0 0 1-3.2-21.584M14.98 3a1.002 1.002 0 0 0-.175.016a13.096 13.096 0 0 0 1.825 25.981c.164.006.328 0 .49 0a13.072 13.072 0 0 0 10.703-5.555a1.01 1.01 0 0 0-.783-1.565A13.08 13.08 0 0 1 15.89 4.38A1.015 1.015 0 0 0 14.98 3z",fill:"currentColor"},null,-1),Et=[Nt],It=x({setup(l){const t=M(),e=Z(),i=()=>{e.value=!e.value};return(r,_)=>(a(),c("button",{class:"toggle-dark-button",title:n(t).toggleDarkMode,onClick:i},[j((a(),c("svg",St,Mt,512)),[[K,!n(e)]]),j((a(),c("svg",Dt,Et,512)),[[K,n(e)]])],8,Tt))}}),Pt=["title"],Rt=g("div",{class:"icon","aria-hidden":"true"},[g("span"),g("span"),g("span")],-1),At=[Rt],Ht=x({emits:["toggle"],setup(l){const t=M();return(e,i)=>(a(),c("div",{class:"toggle-sidebar-button",title:n(t).toggleSidebar,"aria-expanded":"false",role:"button",tabindex:"0",onClick:i[0]||(i[0]=r=>e.$emit("toggle"))},At,8,Pt))}}),Ot=x({emits:["toggle-sidebar"],setup(l){const t=M(),e=O(null),i=O(null),r=O(0),_=p(()=>r.value?{maxWidth:r.value+"px"}:{}),f=p(()=>t.value.darkMode);Le(()=>{const o=h(e.value,"paddingLeft")+h(e.value,"paddingRight"),u=()=>{var d;window.innerWidth<=719?r.value=0:r.value=e.value.offsetWidth-o-(((d=i.value)==null?void 0:d.offsetWidth)||0)};u(),window.addEventListener("resize",u,!1),window.addEventListener("orientationchange",u,!1)});function h(s,o){var v,b,k;const u=(k=(b=(v=s==null?void 0:s.ownerDocument)==null?void 0:v.defaultView)==null?void 0:b.getComputedStyle(s,null))==null?void 0:k[o],d=Number.parseInt(u,10);return Number.isNaN(d)?0:d}return(s,o)=>{const u=R("NavbarSearch");return a(),c("header",{ref_key:"navbar",ref:e,class:"navbar"},[$(Ht,{onToggle:o[0]||(o[0]=d=>s.$emit("toggle-sidebar"))}),g("span",{ref_key:"navbarBrand",ref:i},[$(dt)],512),g("div",{class:"navbar-items-wrapper",style:Fe(n(_))},[y(s.$slots,"before"),$(Ce,{class:"can-hide"}),y(s.$slots,"after"),n(f)?(a(),C(It,{key:0})):w("",!0),$(u)],4)],512)}}}),zt={class:"page-meta"},Ft={key:0,class:"meta-item edit-link"},Wt={key:1,class:"meta-item last-updated"},Ut={class:"meta-item-label"},Vt={class:"meta-item-info"},jt={key:2,class:"meta-item contributors"},Kt={class:"meta-item-label"},Gt={class:"meta-item-info"},qt=["title"],Xt=U(", "),Yt=x({setup(l){const t=()=>{const s=M(),o=W(),u=I();return p(()=>{var N,H,z;if(!((H=(N=u.value.editLink)!=null?N:s.value.editLink)!=null?H:!0))return null;const{repo:v,docsRepo:b=v,docsBranch:k="main",docsDir:L="",editLinkText:m}=s.value;if(!b)return null;const S=xt({docsRepo:b,docsBranch:k,docsDir:L,filePathRelative:o.value.filePathRelative,editLinkPattern:(z=u.value.editLinkPattern)!=null?z:s.value.editLinkPattern});return S?{text:m!=null?m:"Edit this page",link:S}:null})},e=()=>{const s=M(),o=W(),u=I();return p(()=>{var b,k,L,m;return!((k=(b=u.value.lastUpdated)!=null?b:s.value.lastUpdated)!=null?k:!0)||!((L=o.value.git)!=null&&L.updatedTime)?null:new Date((m=o.value.git)==null?void 0:m.updatedTime).toLocaleString()})},i=()=>{const s=M(),o=W(),u=I();return p(()=>{var v,b,k,L;return((b=(v=u.value.contributors)!=null?v:s.value.contributors)!=null?b:!0)&&(L=(k=o.value.git)==null?void 0:k.contributors)!=null?L:null})},r=M(),_=t(),f=e(),h=i();return(s,o)=>{const u=R("ClientOnly");return a(),c("footer",zt,[n(_)?(a(),c("div",Ft,[$(E,{class:"meta-item-label",item:n(_)},null,8,["item"])])):w("",!0),n(f)?(a(),c("div",Wt,[g("span",Ut,T(n(r).lastUpdatedText)+": ",1),$(u,null,{default:B(()=>[g("span",Vt,T(n(f)),1)]),_:1})])):w("",!0),n(h)&&n(h).length?(a(),c("div",jt,[g("span",Kt,T(n(r).contributorsText)+": ",1),g("span",Gt,[(a(!0),c(D,null,A(n(h),(d,v)=>(a(),c(D,{key:v},[g("span",{class:"contributor",title:`email: ${d.email}`},T(d.name),9,qt),v!==n(h).length-1?(a(),c(D,{key:0},[Xt],64)):w("",!0)],64))),128))])])):w("",!0)])}}}),Jt={key:0,class:"page-nav"},Qt={class:"inner"},Zt={key:0,class:"prev"},en={key:1,class:"next"},tn=x({setup(l){const t=s=>s===!1?null:ke(s)?$e(s):We(s)?s:!1,e=(s,o,u)=>{const d=s.findIndex(v=>v.link===o);if(d!==-1){const v=s[d+u];return v!=null&&v.link?v:null}for(const v of s)if(v.children){const b=e(v.children,o,u);if(b)return b}return null},i=I(),r=te(),_=G(),f=p(()=>{const s=t(i.value.prev);return s!==!1?s:e(r.value,_.path,-1)}),h=p(()=>{const s=t(i.value.next);return s!==!1?s:e(r.value,_.path,1)});return(s,o)=>n(f)||n(h)?(a(),c("nav",Jt,[g("p",Qt,[n(f)?(a(),c("span",Zt,[$(E,{item:n(f)},null,8,["item"])])):w("",!0),n(h)?(a(),c("span",en,[$(E,{item:n(h)},null,8,["item"])])):w("",!0)])])):w("",!0)}}),nn={class:"page"},an={class:"theme-default-content"},sn=x({setup(l){return(t,e)=>{const i=R("Content");return a(),c("main",nn,[y(t.$slots,"top"),g("div",an,[$(i)]),$(Yt),$(tn),y(t.$slots,"bottom")])}}}),rn={class:"sidebar-item-children"},on=x({props:{item:{type:Object,required:!0},depth:{type:Number,required:!1,default:0}},setup(l){const t=l,{item:e,depth:i}=J(t),r=G(),_=ee(),f=p(()=>we(e.value,r)),h=p(()=>({"sidebar-item":!0,"sidebar-heading":i.value===0,active:f.value,collapsible:e.value.collapsible})),s=O(!0),o=O(void 0);return e.value.collapsible&&(s.value=f.value,o.value=()=>{s.value=!s.value},_.afterEach(()=>{s.value=f.value})),(u,d)=>{var b;const v=R("SidebarItem",!0);return a(),c("li",null,[n(e).link?(a(),C(E,{key:0,class:P(n(h)),item:n(e)},null,8,["class","item"])):(a(),c("p",{key:1,tabindex:"0",class:P(n(h)),onClick:d[0]||(d[0]=(...k)=>o.value&&o.value(...k)),onKeydown:d[1]||(d[1]=Ue((...k)=>o.value&&o.value(...k),["enter"]))},[U(T(n(e).text)+" ",1),n(e).collapsible?(a(),c("span",{key:0,class:P(["arrow",s.value?"down":"right"])},null,2)):w("",!0)],34)),(b=n(e).children)!=null&&b.length?(a(),C(ye,{key:2},{default:B(()=>[j(g("ul",rn,[(a(!0),c(D,null,A(n(e).children,k=>(a(),C(v,{key:`${n(i)}${k.text}${k.link}`,item:k,depth:n(i)+1},null,8,["item","depth"]))),128))],512),[[K,s.value]])]),_:1})):w("",!0)])}}}),ln={key:0,class:"sidebar-items"},un=x({setup(l){const t=te();return(e,i)=>n(t).length?(a(),c("ul",ln,[(a(!0),c(D,null,A(n(t),r=>(a(),C(on,{key:r.link||r.text,item:r},null,8,["item"]))),128))])):w("",!0)}}),cn={class:"sidebar"},dn=x({setup(l){return(t,e)=>(a(),c("aside",cn,[$(Ce),y(t.$slots,"top"),$(un),y(t.$slots,"bottom")]))}}),_n=x({setup(l){const t=W(),e=I(),i=M(),r=p(()=>e.value.navbar!==!1&&i.value.navbar!==!1),_=te(),f=O(!1),h=m=>{f.value=typeof m=="boolean"?m:!f.value},s={x:0,y:0},o=m=>{s.x=m.changedTouches[0].clientX,s.y=m.changedTouches[0].clientY},u=m=>{const S=m.changedTouches[0].clientX-s.x,N=m.changedTouches[0].clientY-s.y;Math.abs(S)>Math.abs(N)&&Math.abs(S)>40&&(S>0&&s.x<=80?h(!0):h(!1))},d=p(()=>[{"no-navbar":!r.value,"no-sidebar":!_.value.length,"sidebar-open":f.value},e.value.pageClass]);let v;Le(()=>{v=ee().afterEach(()=>{h(!1)})}),Ve(()=>{v()});const b=je(),k=b.resolve,L=b.pending;return(m,S)=>(a(),c("div",{class:P(["theme-container",n(d)]),onTouchstart:o,onTouchend:u},[y(m.$slots,"navbar",{},()=>[n(r)?(a(),C(Ot,{key:0,onToggleSidebar:h},{before:B(()=>[y(m.$slots,"navbar-before")]),after:B(()=>[y(m.$slots,"navbar-after")]),_:3})):w("",!0)]),g("div",{class:"sidebar-mask",onClick:S[0]||(S[0]=N=>h(!1))}),y(m.$slots,"sidebar",{},()=>[$(dn,null,{top:B(()=>[y(m.$slots,"sidebar-top")]),bottom:B(()=>[y(m.$slots,"sidebar-bottom")]),_:3})]),y(m.$slots,"page",{},()=>[n(e).home?(a(),C(ct,{key:0})):(a(),C(ge,{key:1,name:"fade-slide-y",mode:"out-in",onBeforeEnter:n(k),onBeforeLeave:n(L)},{default:B(()=>[(a(),C(sn,{key:n(t).path},{top:B(()=>[y(m.$slots,"page-top")]),bottom:B(()=>[y(m.$slots,"page-bottom")]),_:3}))]),_:3},8,["onBeforeEnter","onBeforeLeave"]))])],34))}});export{_n as default}; diff --git a/assets/advanced_activation.html.9df33d17.js b/assets/advanced_activation.html.b14ae790.js similarity index 98% rename from assets/advanced_activation.html.9df33d17.js rename to assets/advanced_activation.html.b14ae790.js index ee515fe23..4efe2ac8b 100644 --- a/assets/advanced_activation.html.9df33d17.js +++ b/assets/advanced_activation.html.b14ae790.js @@ -1 +1 @@ -import{r as a,o as s,a as r,b as e,d as n,F as c,c as i,e as t}from"./app.f6cb3ed9.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";const d={},h=i('

    Activating advanced capabilities

    Z Open Editor's advanced capabilities require activation when the 60-day trial period ends. Currently, you can activate a permanent license key in two ways:

    1. Automatic activation using an RSE API server.
    2. Manual activation by importing an activation kit.

    The IBM Z Open Editor Welcome page is used to report on the status of the trial license, the status of the automatic activation, as well as provides the means to import a manual activation kit. If the Welcome page does not open automatically at startup or you have already closed it, you can open it by entering cmd/ctrl-shift-p and typing or selecting IBM Z Open Editor: Welcome.

    Automatic activation

    Automatic activation uses the same technology that development clients for IBM Developer for z/OS Enterprise Edition use. It is ideal for organizations who run IBM Remote Systems Explorer (RSE) and allow their developers to choose between an Eclipse and VS Code development client. A system programmer provisioning RSE will install activation tokens that the editors retrieve automatically when they connect to RSE.

    To enable activation tokens via RSE API on z/OS, the z/OS administrator needs to complete the following steps:

    ',7),p=t("Install and complete basic configuration of z/OS host component IBM z/OS Explorer Extensions, "),u=e("code",null,"FMID HHOPxxx",-1),m=t(". For more information, see "),_={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=installing-configuring-host-components",target:"_blank",rel:"noopener noreferrer"},v=t("Installing and configuring the host components"),f=t("."),g=e("li",null,[t("Install and complete basic configuration of z/OS host component IBM Remote System Explorer API (RSE API), "),e("code",null,"FMID HAMAxxx"),t(".")],-1),b=t("Make sure z/OS Explorer knows where to find z/OS Explorer Extensions. Depending on where z/OS Explorer Extensions was installed, this detection is automatic, or done via an environment variable in the configuration file "),x={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=customization-rseenv-zos-explorer-configuration-file",target:"_blank",rel:"noopener noreferrer"},E=e("code",null,"rse.env",-1),w=t("."),y=t("Allow z/OS Explorer Extensions to register as ADFz or IDzEE. For more information, see "),k={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=changes-product-enablement-in-ifaprdxx",target:"_blank",rel:"noopener noreferrer"},I=t("Product enablement in IFAPRDxx"),S=t("."),z=t("Allow z/OS Explorer Extensions to write "),O={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=changes-smf-record-collection-in-smfprmxx",target:"_blank",rel:"noopener noreferrer"},A=t("SM122 records"),M=t(" to track that it provided an activation token."),B=t("You can find more detailed instruction in the documentation for system programmers, such as in "),R={href:"https://www.ibm.com/mysupport/s/topic/0TO0z0000006uw0GAA/shopz",target:"_blank",rel:"noopener noreferrer"},P=t("IBM Shopz"),Z=t("."),C=e("p",null,[t("The Z Open Editor end users can then use the VS Code user setting "),e("code",null,"zopeneditor.advancedCapabilities.enableRseApiActivationCheck"),t(" to enable the automatic RSE check. The Z Open Editor Welcome page also provides a convenient check box to enable these settings.")],-1),F=e("p",null,"Once enabled, the next time you connect to the RSE API server via Zowe Explorer or Z Open Editor, an automatic check for activation will be executed. If successful, the Z Open Editor Welcome page will report the activation status in a table.",-1),T=e("p",null,"Notes:",-1),D=e("li",null,"Host component IBM Explorer for z/OS, FMID HALGxxx, is a prerequisite for both IBM z/OS Explorer Extensions and IBM Remote System Explorer API (RSE API).",-1),H=t("You can use the Host Configuration Assistant at "),V={href:"https://zdev-hca.ibm.com",target:"_blank",rel:"noopener noreferrer"},W=t("https://zdev-hca.ibm.com"),N=t(" to guide you through the required host configuration."),q=e("li",null,"The provided activation tokens operate for a limited time. However, activation tokens are automatically renewed each time the client connects to the z/OS host.",-1),L=i('

    Manual activation

    If your organization uses z/OSMF instead of RSE API, you can activate your Z Open Editor client with an activation kit. You receive the activation kit through Shopz and your administrative system programmer or directly from your IBM sales representative. The kit comprises a single file that needs to be imported by every Z Open Editor user to activate the advanced capabilities.

    1. Open the Z Open Editor Welcome page and scroll to the Advanced capabilities section.
    2. Click the Update activation key link below the table that presents the status of your trial.
    3. Click Browse in the dialog, and select the activation kit file that you received.
    4. Click Import in the dialog to finish activation.
    5. The table will now show information about the activation kit that you imported.
    ',3);function Y(G,U){const o=a("ExternalLinkIcon");return s(),r(c,null,[h,e("ol",null,[e("li",null,[p,u,m,e("a",_,[v,n(o)]),f]),g,e("li",null,[b,e("a",x,[E,n(o)]),w]),e("li",null,[y,e("a",k,[I,n(o)]),S]),e("li",null,[z,e("a",O,[A,n(o)]),M])]),e("p",null,[B,e("a",R,[P,n(o)]),Z]),C,F,T,e("ul",null,[D,e("li",null,[H,e("a",V,[W,n(o)]),N]),q]),L],64)}var K=l(d,[["render",Y]]);export{K as default}; +import{r as a,o as s,a as r,b as e,d as n,F as c,c as i,e as t}from"./app.daa93c96.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";const d={},h=i('

    Activating advanced capabilities

    Z Open Editor's advanced capabilities require activation when the 60-day trial period ends. Currently, you can activate a permanent license key in two ways:

    1. Automatic activation using an RSE API server.
    2. Manual activation by importing an activation kit.

    The IBM Z Open Editor Welcome page is used to report on the status of the trial license, the status of the automatic activation, as well as provides the means to import a manual activation kit. If the Welcome page does not open automatically at startup or you have already closed it, you can open it by entering cmd/ctrl-shift-p and typing or selecting IBM Z Open Editor: Welcome.

    Automatic activation

    Automatic activation uses the same technology that development clients for IBM Developer for z/OS Enterprise Edition use. It is ideal for organizations who run IBM Remote Systems Explorer (RSE) and allow their developers to choose between an Eclipse and VS Code development client. A system programmer provisioning RSE will install activation tokens that the editors retrieve automatically when they connect to RSE.

    To enable activation tokens via RSE API on z/OS, the z/OS administrator needs to complete the following steps:

    ',7),p=t("Install and complete basic configuration of z/OS host component IBM z/OS Explorer Extensions, "),u=e("code",null,"FMID HHOPxxx",-1),m=t(". For more information, see "),_={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=installing-configuring-host-components",target:"_blank",rel:"noopener noreferrer"},v=t("Installing and configuring the host components"),f=t("."),g=e("li",null,[t("Install and complete basic configuration of z/OS host component IBM Remote System Explorer API (RSE API), "),e("code",null,"FMID HAMAxxx"),t(".")],-1),b=t("Make sure z/OS Explorer knows where to find z/OS Explorer Extensions. Depending on where z/OS Explorer Extensions was installed, this detection is automatic, or done via an environment variable in the configuration file "),x={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=customization-rseenv-zos-explorer-configuration-file",target:"_blank",rel:"noopener noreferrer"},E=e("code",null,"rse.env",-1),w=t("."),y=t("Allow z/OS Explorer Extensions to register as ADFz or IDzEE. For more information, see "),k={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=changes-product-enablement-in-ifaprdxx",target:"_blank",rel:"noopener noreferrer"},I=t("Product enablement in IFAPRDxx"),S=t("."),z=t("Allow z/OS Explorer Extensions to write "),O={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=changes-smf-record-collection-in-smfprmxx",target:"_blank",rel:"noopener noreferrer"},A=t("SM122 records"),M=t(" to track that it provided an activation token."),B=t("You can find more detailed instruction in the documentation for system programmers, such as in "),R={href:"https://www.ibm.com/mysupport/s/topic/0TO0z0000006uw0GAA/shopz",target:"_blank",rel:"noopener noreferrer"},P=t("IBM Shopz"),Z=t("."),C=e("p",null,[t("The Z Open Editor end users can then use the VS Code user setting "),e("code",null,"zopeneditor.advancedCapabilities.enableRseApiActivationCheck"),t(" to enable the automatic RSE check. The Z Open Editor Welcome page also provides a convenient check box to enable these settings.")],-1),F=e("p",null,"Once enabled, the next time you connect to the RSE API server via Zowe Explorer or Z Open Editor, an automatic check for activation will be executed. If successful, the Z Open Editor Welcome page will report the activation status in a table.",-1),T=e("p",null,"Notes:",-1),D=e("li",null,"Host component IBM Explorer for z/OS, FMID HALGxxx, is a prerequisite for both IBM z/OS Explorer Extensions and IBM Remote System Explorer API (RSE API).",-1),H=t("You can use the Host Configuration Assistant at "),V={href:"https://zdev-hca.ibm.com",target:"_blank",rel:"noopener noreferrer"},W=t("https://zdev-hca.ibm.com"),N=t(" to guide you through the required host configuration."),q=e("li",null,"The provided activation tokens operate for a limited time. However, activation tokens are automatically renewed each time the client connects to the z/OS host.",-1),L=i('

    Manual activation

    If your organization uses z/OSMF instead of RSE API, you can activate your Z Open Editor client with an activation kit. You receive the activation kit through Shopz and your administrative system programmer or directly from your IBM sales representative. The kit comprises a single file that needs to be imported by every Z Open Editor user to activate the advanced capabilities.

    1. Open the Z Open Editor Welcome page and scroll to the Advanced capabilities section.
    2. Click the Update activation key link below the table that presents the status of your trial.
    3. Click Browse in the dialog, and select the activation kit file that you received.
    4. Click Import in the dialog to finish activation.
    5. The table will now show information about the activation kit that you imported.
    ',3);function Y(G,U){const o=a("ExternalLinkIcon");return s(),r(c,null,[h,e("ol",null,[e("li",null,[p,u,m,e("a",_,[v,n(o)]),f]),g,e("li",null,[b,e("a",x,[E,n(o)]),w]),e("li",null,[y,e("a",k,[I,n(o)]),S]),e("li",null,[z,e("a",O,[A,n(o)]),M])]),e("p",null,[B,e("a",R,[P,n(o)]),Z]),C,F,T,e("ul",null,[D,e("li",null,[H,e("a",V,[W,n(o)]),N]),q]),L],64)}var K=l(d,[["render",Y]]);export{K as default}; diff --git a/assets/advanced_custom_macros.html.c5056122.js b/assets/advanced_custom_macros.html.14afaf7a.js similarity index 98% rename from assets/advanced_custom_macros.html.c5056122.js rename to assets/advanced_custom_macros.html.14afaf7a.js index 050b20657..b5dc9c9a2 100644 --- a/assets/advanced_custom_macros.html.c5056122.js +++ b/assets/advanced_custom_macros.html.14afaf7a.js @@ -1,4 +1,4 @@ -import{c as a}from"./app.f6cb3ed9.js";import{_ as e}from"./plugin-vue_export-helper.21dcd24c.js";var n="/zopeneditor-about/assets/macro-functionality.c0137f84.gif";const s={},o=a(`

    Custom Macros for HLASM

    With the release of IBM Z Open Editor 4.2.0, custom macros are now supported for your HLASM programs. Macro libraries will be declared in your zapp.yaml file and used to find your custom macros. All macros that are located in your macro library will now support hover, document links, and Go to Definition. If a custom macro is found and used at least once in a program, it will also be available when using code completion and content assist.

    Files that contain multiple macros are supported as well as single macro files. Currently, only local macro libraries are supported.

    Declaring Macro Libraries in your zapp.yaml file

    To locate macros from your MACLIB, you need to create a new library in your ZAPP named maclib.

    The following ZAPP snippet shows a property group declaration for HLASM containing a MACLIB entry:

    - name: hlasm-local
+import{c as a}from"./app.daa93c96.js";import{_ as e}from"./plugin-vue_export-helper.21dcd24c.js";var n="/zopeneditor-about/assets/macro-functionality.c0137f84.gif";const s={},o=a(`
     Custom Macros for HLASM
    With the release of IBM Z Open Editor 4.2.0, custom macros are now supported for your HLASM programs. Macro libraries will be declared in your zapp.yaml file and used to find your custom macros. All macros that are located in your macro library will now support hover, document links, and Go to Definition. If a custom macro is found and used at least once in a program, it will also be available when using code completion and content assist.
    Files that contain multiple macros are supported as well as single macro files. Currently, only local macro libraries are supported.
     Declaring Macro Libraries in your zapp.yaml file
    To locate macros from your MACLIB, you need to create a new library in your ZAPP named maclib.
    The following ZAPP snippet shows a property group declaration for HLASM containing a MACLIB entry:
    - name: hlasm-local
   language: hlasm
   libraries:
     - name: maclib
diff --git a/assets/advanced_overview.html.691fbecc.js b/assets/advanced_overview.html.e5020286.js
similarity index 98%
rename from assets/advanced_overview.html.691fbecc.js
rename to assets/advanced_overview.html.e5020286.js
index df14918a3..7c872ec69 100644
--- a/assets/advanced_overview.html.691fbecc.js
+++ b/assets/advanced_overview.html.e5020286.js
@@ -1 +1 @@
-import{r as i,o as a,a as c,b as o,d as t,w as n,F as l,e}from"./app.f6cb3ed9.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const h={},p=o("h1",{id:"overview",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#overview","aria-hidden":"true"},"#"),e(" Overview")],-1),u=e("IBM Z Open Editor v4 or later features enterprise-level advanced capabilities that cover use cases that go beyond programming and simple accessing of z/OS Resources. You would typically find such features in IBM's commercial zDevOps solutions such as IBM Developer for z/OS Enterprise Edition (IDzEE). While the core Z Open Editor experience continues to provide free full language support for COBOL, PL/I, REXX, HLASM, JCL and integrations with Zowe Explorer, these advanced capabilities require commercial licenses to activate. You can purchase the licenses through "),_={href:"https://www.ibm.com/products/developer-for-zos",target:"_blank",rel:"noopener noreferrer"},m=e("IBM Developer for z/OS Enterprise Edition"),f=e(" or "),v={href:"https://www.ibm.com/products/app-delivery-foundation-for-zos",target:"_blank",rel:"noopener noreferrer"},w=e("IBM Application Delivery Foundation for z/OS"),g=e("."),y=o("p",null,"To allow every user to try these features, Z Open Editor will activate a 60-day trial license when you start version 4 for the first time.",-1),b=e("For more information, see "),O={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-whats-new-in-wazi-vs",target:"_blank",rel:"noopener noreferrer"},E=e("IBM Documentation"),x=e("."),k=o("p",null,"Only the following new features documented in this section require such a license:",-1),z=e("z/OS Resources table"),B=e(": an all-new feature rich view that extends Zowe Explorer with a sortable table. Gain insights into your jobs, data sets, and UNIX files by listing, filtering, and sorting on many available properties."),D=e("Preprocessor support for COBOL"),L=e(": run a preprocessor either on your local workstation or remotely on z/OS driven with 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."),I=e("Advanced Dependency-Based user build error reporting"),S=e(": User build logs are now automatically downloaded, parsed, and presented in the editor's Problems view with descriptions and error codes. Navigate to warnings and errors in your code with a mouse click in the Problems view to review and fix your issue and then rerun your build."),A=e("HLASM macros support"),M=e(": Use custom macro resolution in HLASM programs with references to macros in local files. The HLASM editor shows hovers, document links, go to definition, and code completion for macros. This feature works with one to many macro declarations per include file, which is achieved by pre-scanning macro files if they can be found in local ZAPP property groups."),P=e("To access these capabilities beyond the trial period, you need to activate them in the Z Open Editor Welcome page. See "),Z=e("Activating Advanced Capabilities"),C=e(" for details.");function N(R,T){const s=i("ExternalLinkIcon"),r=i("RouterLink");return a(),c(l,null,[p,o("p",null,[u,o("a",_,[m,t(s)]),f,o("a",v,[w,t(s)]),g]),y,o("p",null,[b,o("a",O,[E,t(s)]),x]),k,o("ol",null,[o("li",null,[t(r,{to:"/Docs/advanced_resource_table.html"},{default:n(()=>[z]),_:1}),B]),o("li",null,[t(r,{to:"/Docs/advanced_preprocessor.html"},{default:n(()=>[D]),_:1}),L]),o("li",null,[t(r,{to:"/Docs/advanced_problems_view.html"},{default:n(()=>[I]),_:1}),S]),o("li",null,[t(r,{to:"/Docs/advanced_custom_macros.html"},{default:n(()=>[A]),_:1}),M])]),o("p",null,[P,t(r,{to:"/Docs/advanced_activation.html"},{default:n(()=>[Z]),_:1}),C])],64)}var U=d(h,[["render",N]]);export{U as default};
+import{r as i,o as a,a as c,b as o,d as t,w as n,F as l,e}from"./app.daa93c96.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const h={},p=o("h1",{id:"overview",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#overview","aria-hidden":"true"},"#"),e(" Overview")],-1),u=e("IBM Z Open Editor v4 or later features enterprise-level advanced capabilities that cover use cases that go beyond programming and simple accessing of z/OS Resources. You would typically find such features in IBM's commercial zDevOps solutions such as IBM Developer for z/OS Enterprise Edition (IDzEE). While the core Z Open Editor experience continues to provide free full language support for COBOL, PL/I, REXX, HLASM, JCL and integrations with Zowe Explorer, these advanced capabilities require commercial licenses to activate. You can purchase the licenses through "),_={href:"https://www.ibm.com/products/developer-for-zos",target:"_blank",rel:"noopener noreferrer"},m=e("IBM Developer for z/OS Enterprise Edition"),f=e(" or "),v={href:"https://www.ibm.com/products/app-delivery-foundation-for-zos",target:"_blank",rel:"noopener noreferrer"},w=e("IBM Application Delivery Foundation for z/OS"),g=e("."),y=o("p",null,"To allow every user to try these features, Z Open Editor will activate a 60-day trial license when you start version 4 for the first time.",-1),b=e("For more information, see "),O={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-whats-new-in-wazi-vs",target:"_blank",rel:"noopener noreferrer"},E=e("IBM Documentation"),x=e("."),k=o("p",null,"Only the following new features documented in this section require such a license:",-1),z=e("z/OS Resources table"),B=e(": an all-new feature rich view that extends Zowe Explorer with a sortable table. Gain insights into your jobs, data sets, and UNIX files by listing, filtering, and sorting on many available properties."),D=e("Preprocessor support for COBOL"),L=e(": run a preprocessor either on your local workstation or remotely on z/OS driven with 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."),I=e("Advanced Dependency-Based user build error reporting"),S=e(": User build logs are now automatically downloaded, parsed, and presented in the editor's Problems view with descriptions and error codes. Navigate to warnings and errors in your code with a mouse click in the Problems view to review and fix your issue and then rerun your build."),A=e("HLASM macros support"),M=e(": Use custom macro resolution in HLASM programs with references to macros in local files. The HLASM editor shows hovers, document links, go to definition, and code completion for macros. This feature works with one to many macro declarations per include file, which is achieved by pre-scanning macro files if they can be found in local ZAPP property groups."),P=e("To access these capabilities beyond the trial period, you need to activate them in the Z Open Editor Welcome page. See "),Z=e("Activating Advanced Capabilities"),C=e(" for details.");function N(R,T){const s=i("ExternalLinkIcon"),r=i("RouterLink");return a(),c(l,null,[p,o("p",null,[u,o("a",_,[m,t(s)]),f,o("a",v,[w,t(s)]),g]),y,o("p",null,[b,o("a",O,[E,t(s)]),x]),k,o("ol",null,[o("li",null,[t(r,{to:"/Docs/advanced_resource_table.html"},{default:n(()=>[z]),_:1}),B]),o("li",null,[t(r,{to:"/Docs/advanced_preprocessor.html"},{default:n(()=>[D]),_:1}),L]),o("li",null,[t(r,{to:"/Docs/advanced_problems_view.html"},{default:n(()=>[I]),_:1}),S]),o("li",null,[t(r,{to:"/Docs/advanced_custom_macros.html"},{default:n(()=>[A]),_:1}),M])]),o("p",null,[P,t(r,{to:"/Docs/advanced_activation.html"},{default:n(()=>[Z]),_:1}),C])],64)}var U=d(h,[["render",N]]);export{U as default};
diff --git a/assets/advanced_preprocessor.html.a9f9190c.js b/assets/advanced_preprocessor.html.57016ed4.js
similarity index 56%
rename from assets/advanced_preprocessor.html.a9f9190c.js
rename to assets/advanced_preprocessor.html.57016ed4.js
index 23de0f3fa..b336c479c 100644
--- a/assets/advanced_preprocessor.html.a9f9190c.js
+++ b/assets/advanced_preprocessor.html.57016ed4.js
@@ -1 +1 @@
-const e={key:"v-a6691fb0",path:"/Docs/advanced_preprocessor.html",title:"Preprocessor support",lang:"en-US",frontmatter:{},excerpt:"",headers:[{level:1,title:"Preprocessor support",slug:"preprocessor-support",children:[{level:2,title:"Local preprocessor",slug:"local-preprocessor",children:[]},{level:2,title:"Remote preprocessor",slug:"remote-preprocessor",children:[]},{level:2,title:"Limitations",slug:"limitations",children:[]}]}],git:{updatedTime:1723684879e3,contributors:[{name:"Ethan Mendel",email:"Ethan.Mendel@ibm.com",commits:3},{name:"PETER HAUMER",email:"phaumer@us.ibm.com",commits:2},{name:"Ankit Kumar",email:"xfankit@ibm.com",commits:1},{name:"Hestia Zhang",email:"Hestia.Zhang@ibm.com",commits:1}]},filePathRelative:"Docs/advanced_preprocessor.md"};export{e as data};
+const e={key:"v-a6691fb0",path:"/Docs/advanced_preprocessor.html",title:"Preprocessor support",lang:"en-US",frontmatter:{},excerpt:"",headers:[{level:1,title:"Preprocessor support",slug:"preprocessor-support",children:[{level:2,title:"Local preprocessor",slug:"local-preprocessor",children:[]},{level:2,title:"Remote preprocessor",slug:"remote-preprocessor",children:[]},{level:2,title:"Limitations",slug:"limitations",children:[]}]}],git:{updatedTime:172669751e4,contributors:[{name:"Ethan Mendel",email:"Ethan.Mendel@ibm.com",commits:3},{name:"PETER HAUMER",email:"phaumer@us.ibm.com",commits:3},{name:"Ankit Kumar",email:"xfankit@ibm.com",commits:1},{name:"Hestia Zhang",email:"Hestia.Zhang@ibm.com",commits:1}]},filePathRelative:"Docs/advanced_preprocessor.md"};export{e as data};
diff --git a/assets/advanced_preprocessor.html.a5970554.js b/assets/advanced_preprocessor.html.a5970554.js
deleted file mode 100644
index b297a54ad..000000000
--- a/assets/advanced_preprocessor.html.a5970554.js
+++ /dev/null
@@ -1,18 +0,0 @@
-import{r as i,o as p,a as l,b as e,d as s,w as a,F as c,c as r,e as t}from"./app.f6cb3ed9.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";const d={},u=r('
     Preprocessor support
    Z Open Editor provides the advanced capability to integrate parsing of COBOL programs with a custom preprocessor to allow editing programs that contain such preprocessor statements without causing the editor to show syntax errors. The preprocessor would be executed on either a developer machine by Z Open Editor in the background (local) or a z/OS system (remote), taking COBOL with custom code and transforming it to valid COBOL. Users can then continue editing such programs by using the preprocessor input to still provide full language support such as code completion, syntax error highlighting, and outline view for the regular COBOL statements. Then at each save or editor focus change the preprocessor can run automatically again to update the processed COBOL representation used by the editor. The editor would not learn the preprocessor language, but rather ensure that the resulting preprocessed output is still valid COBOL.
     Local preprocessor
     Example workflow
    The following workflow is written from the perspective of COBOL developer, Deb.
    1. Deb installs a command-line centric preprocessor program on her local development machine.
    2. Deb creates a zapp.yaml file with a preprocessor profile type. The profile specifies the command-line for running the preprocessor on the currently edited program file as well as the output path for the preprocessed program files.
    3. Deb edits a program file with preprocessor statements in Z Open Editor.
    4. Deb either manually starts preprocessing the program via a right-click menu command or creates a user setting to automatically run the preprocessor on Save.
    5. Z Open Editor starts the preprocessor command in the background and sends the output file to its COBOL parser.
    6. Z Open Editor's COBOL parser will compare the program in the editor with the output of the preprocessor command.
    7. Deb hovers over processor statements in Z Open Editor, which displays the resulting COBOL.
    8. Deb continues editing the program in Z Open Editor. Z Open Editor continues to provide full language support for all the parts of the program that are not preprocessor statements.
    ',6),m=t("To learn and explore this workflow, check out the example preprocessor and code samples in our Github repository at "),f={href:"https://github.com/ibm/zopeneditor-sample/tree/wazi-main/preprocessor",target:"_blank",rel:"noopener noreferrer"},g=t("https://github.com/ibm/zopeneditor-sample/tree/wazi-main/preprocessor"),b=t(". Review the "),_={href:"https://github.com/ibm/zopeneditor-sample/tree/wazi-main/preprocessor/README.md",target:"_blank",rel:"noopener noreferrer"},k=t("Readme"),w=t(" file in this folder with detailed instructions for building and running the sample."),y=e("h3",{id:"requirements-for-the-preprocessor",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#requirements-for-the-preprocessor","aria-hidden":"true"},"#"),t(" Requirements for the preprocessor")],-1),O=e("p",null,"To be able to integrate your preprocessor with Z Open Editor, it must fulfill these requirements:",-1),v=e("ul",null,[e("li",null,"It needs to run locally on your development machine where Z Open Editor is running."),e("li",null,"You need to be able to run the processor via command-line."),e("li",null,"The command-line operation needs to create an output file that contains valid COBOL."),e("li",null,"The output path can be computed by specifying a new file extension to be used with the program file name.")],-1),x=e("h3",{id:"zapp-profile",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#zapp-profile","aria-hidden":"true"},"#"),t(" ZAPP profile")],-1),P=t("The integration of the preprocessor with the editor is handled via a "),T=t("ZAPP file profile"),E=t(". Such a profile might look like this:"),L=r(`
    - name: extended-cobol
-  type: preprocessor
-  location: local
-  settings:
-    command: ${JAVA_HOME}/bin/java -jar ${WORKSPACE}/preprocessor/my-preprocessor/target/my-preprocessor-1.0-SNAPSHOT.jar ${input_file} ${output_file}
-    outputPath: ./preprocessor/output
-    fileExtension: cee
-    environmentVariables:
-      VARIABLE1: value1
-
    In the settings object, the following properties can be used:
    `,2),C=e("thead",null,[e("tr",null,[e("th",null,"Property"),e("th",null,"Description")])],-1),S=e("td",null,"command",-1),R=t("The command line to be executed. You can mix the command line with "),Z=t("ZAPP Variables"),z=t(" as well as use the predefined variables "),A=e("code",null,"${input_file}",-1),D=t(" and "),B=e("code",null,"${output_file}",-1),I=t(". You need to define "),H=e("code",null,"${JAVA_HOME}",-1),V=t(" and "),q=e("code",null,"${WORKSPACE}",-1),Q=t(" in the example above as ZAPP variables. Environment variables can only be used by specifying them with the "),$=e("code",null,"environmentVariables",-1),Y=t(" property."),N=e("tr",null,[e("td",null,"outputPath"),e("td",null,"The base path in which the output file should be created. This path must be inside the current VS Code workspace so that the editor can see and process the files.")],-1),U=e("tr",null,[e("td",null,"fileExtension"),e("td",null,"The file extension to be used for the output files.")],-1),M=e("tr",null,[e("td",null,"environmentVariables"),e("td",null,"An optional sub-object to specify the environment variables that should be created before executing the command.")],-1),X=r('
     Running the preprocessor
    After you specify the ZAPP profile, you can run the preprocessor in the following ways:
    1. Right-click and choose Execute local preprocessor command to manually run the preprocessor in the program file editor.
    2. Automatically run the preprocessor via the VS Code user setting zopeneditor.cobol.autoPreprocessor. The setting can have one of the values: 
      • off: disables the automatic preprocessor execution.
      • open: when a program file is opened in the editor.
      • save: when a program file is saved in the editor.
      • both: when opening and saving a program file in the editor.
    When the preprocessor command runs, a progress dialog with a Cancel button is displayed. When the preprocessor finishes, it refreshes the editor and any syntax errors that were caused by preprocessor statements should go away or, if they contained problems, will show those instead.
    If the processor command execution failed and produced errors, a dialog will be shown with a button to open the Z Open Editor log file viewer which lists the detailed error message produced by the preprocessor command.
     Using the preprocessor output in the editor
    After the preprocessor is executed, you can hover the mouse of preprocessor statements in their program file to see the COBOL code that was generated for the statement. You can edit these statements and all other COBOL code in the program.
    Syntax errors for preprocessor statements will not be available until the preprocessor runs again. Syntax errors for other regular COBOL will be shown while typing as usual in Z Open Editor.
    To get a side-by-side view of the program before and after preprocessing, you can use the right-click menu option Compare preprocessor input and output files.
     Remote preprocessor
     Example workflow
    The following workflow is written from the perspective of COBOL developer, Deb.
    1. Deb sets up a z/OS centric preprocessor data member on her remote z/OS development machine. This data member must be either a REXX or CLIST program.
    2. Deb creates a zapp.yaml file with a preprocessor profile type. The profile specifies the TSO command for running the preprocessor on the currently edited program data member as well as the output dataset for the preprocessed data members.
    3. Deb edits a dataset member with preprocessor statements in Z Open Editor through Zowe.
    4. Deb either manually starts preprocessing the program via a right-click menu command or creates a user setting to automatically run the preprocessor on Save.
    5. Z Open Editor uses Zowe to start the preprocessor command in the background and sends the output file to its COBOL parser.
    6. Z Open Editor's COBOL parser will compare the program in the editor with the output of the preprocessor command.
    7. Deb hovers over processor statements in Z Open Editor, which displays the resulting COBOL.
    8. Deb continues editing the program in Z Open Editor. Z Open Editor continues to provide full language support for all the parts of the program that are not preprocessor statements.
    ',13),j=t("To learn and explore this sample workflow, check out the example preprocessor and code samples in our Github repository at "),W={href:"https://github.com/ibm/zopeneditor-sample/tree/wazi-main/preprocessor",target:"_blank",rel:"noopener noreferrer"},G=t("https://github.com/ibm/zopeneditor-sample/tree/wazi-main/preprocessor"),F=t(". Review the "),J={href:"https://github.com/ibm/zopeneditor-sample/tree/wazi-main/preprocessor/README.md",target:"_blank",rel:"noopener noreferrer"},K=t("Readme"),ee=t(" file in this folder with detailed instructions for building and running the sample."),te=e("h3",{id:"requirements-for-the-preprocessor-1",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#requirements-for-the-preprocessor-1","aria-hidden":"true"},"#"),t(" Requirements for the preprocessor")],-1),se=e("p",null,"To be able to integrate your preprocessor with Z Open Editor, it must fulfill these requirements:",-1),oe=e("li",null,"It needs to run remotely on your z/OS machine.",-1),ne=e("li",null,"The remote preprocessor must be either a REXX or CLIST program.",-1),ae=t("You need a RSE API or z/OSMF Zowe profile available in your workspace and "),re=t("configured as a default for Z Open Editor"),ie=t("."),pe=t("You need to be able to run the processor via a Zowe TSO command. "),le=t("You can read more about TSO commands and Zowe TSO profiles "),ce={href:"https://ibm.github.io/zopeneditor-about/Docs/interact_zos_cli.html#run-interactive-tso-commands",target:"_blank",rel:"noopener noreferrer"},he=t("in the documentation"),de=t(", and explore some examples in this "),ue={href:"https://medium.com/zowe/zowe-ci-and-tso-commands-14e5445fca1e",target:"_blank",rel:"noopener noreferrer"},me=t("blog"),fe=t("."),ge=e("li",null,"The TSO operation needs to create an output data member that contains valid COBOL.",-1),be=t("The program file to be processed needs to be in a PDS that is recognized by Z Open Editor to contain COBOL and the COBOL language support must be active. See "),_e=t("Remote file associations"),ke=t(" for more details."),we=e("h3",{id:"zapp-profile-1",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#zapp-profile-1","aria-hidden":"true"},"#"),t(" ZAPP profile")],-1),ye=t("The integration of the preprocessor with the editor is handled via a "),Oe=t("ZAPP file profile"),ve=t(". Such a profile could look like this:"),xe=r(`
    - name: extended-cobol
-  type: preprocessor
-  location: mvs
-  settings:
-    commandDataSet: ${HLQ}.PREPROC.REXX.(PREPROC)
-    tempDataHLQ: ${HLQ}
-    outputDataSet: ${HLQ}.PREPROC.OUTPUT()
-    commandParameters: "var1=val1"
-
    In the settings object the following properties can be used:
    `,2),Pe=e("thead",null,[e("tr",null,[e("th",null,"Property"),e("th",null,"Description")])],-1),Te=e("td",null,"commandDataSet",-1),Ee=t("The data member to be executed. You can mix with "),Le=t("ZAPP Variables"),Ce=t(". You need to define "),Se=e("code",null,"${HLQ}",-1),Re=t(" in the example above as ZAPP variables. Environment variables can only be used by specifying them with the below "),Ze=e("code",null,"commandParameters",-1),ze=t(" property."),Ae=e("tr",null,[e("td",null,"tempDataHLQ"),e("td",null,[t("The High Level Qualifier (HLQ) to use to save an xml file that stores information for the "),e("code",null,"commandDataSet"),t(" to read from.")])],-1),De=e("tr",null,[e("td",null,"outputDataSet"),e("td",null,"The output dataset to save the data member output file of the preprocessor.")],-1),Be=e("tr",null,[e("td",null,"commandParameters"),e("td",null,"An optional parameter to specify any command parameters that should be used when executing the command.")],-1),Ie=r('
     Running the preprocessor
    After you specify the ZAPP profile, you can run the preprocessor in the following ways:
    1. Right-click and choose Execute remote preprocessor command to manually run the preprocessor in the program file editor.
    2. Automatically run the preprocessor via the VS Code user setting zopeneditor.cobol.autoPreprocessor. The setting can have one of the values: 
      • off: disables the automatic preprocessor execution.
      • open: when a program file is opened in the editor.
      • save: when a program file is saved in the editor.
      • both: when opening and saving a program file in the editor.
    When the preprocessor command runs, a progress dialog with a Cancel button is displayed. A sequential data member is created using the tempDataHLQ to store information for the preprocessor to read. When the preprocessor finishes, it deletes the sequential data member and then refreshes the editor and any syntax errors that were caused by preprocessor statements should go away or, if they contained problems, will show those instead.
    If the processor command execution failed and produced errors, a dialog will be shown with a button to open the Z Open Editor log file viewer which lists the detailed error message produced by the preprocessor command and the sequential data member will not be deleted.
    The following is an example of the sequential data member that gets created for the remote preprocessor to read based on the above ZAPP profile:
    <PROGRAM>HLQ.COBOL(PRINTAPP)</PROGRAM><SYSLIB></SYSLIB><COMPILEOPTIONS></COMPILEOPTIONS><OUTPUT>HLQ.PREPROC.OUTPUT(PRINTAPP)</OUTPUT>\n
    • The ${HLQ} variable gets replaced with HLQ from user settings
    • The input data member's name was PRINTAPP
    • There were no mvs cobol libraries or compiler options specified in the ZAPP property groups
     Using the preprocessor output in the editor
    After the preprocessor is executed, you can hover the mouse of preprocessor statements in their program file to see the COBOL code that was generated for the statement. You can edit these statements and all other COBOL code in the program.
    Syntax errors for preprocessor statements will not be available until the preprocessor runs again. Syntax errors for other regular COBOL will be shown while typing as usual in Z Open Editor.
    To get a side-by-side view of the program before and after preprocessing, you can use the right-click menu option Compare preprocessor input and output files.
     Limitations
    Restriction: Several limitations are associated with using a preprocessor within Z Open Editor:
    • Code formatting will be disabled for files that contain preprocessor statements.
    • Not all preprocessor statements within an EXEC block might be identified.
    • All preprocessor statements might not be identified if the code is reorganized.
    • Preprocessor statements that modify text in another location of a program might not be identified.
    • Real-time syntax checking of programs that contain preprocessor statements that contain only the beginning or ending of a language comment might not be identified.
    • Remote preprocessor command dataset members must be either REXX or CLIST files.
    • The side-by-side comparison of program and preprocessed output is not yet available for the remote preprocessor support.
    ',15);function He(Ve,qe){const o=i("ExternalLinkIcon"),n=i("RouterLink");return p(),l(c,null,[u,e("p",null,[m,e("a",f,[g,s(o)]),b,e("a",_,[k,s(o)]),w]),y,O,v,x,e("p",null,[P,s(n,{to:"/Docs/zapp.html"},{default:a(()=>[T]),_:1}),E]),L,e("table",null,[C,e("tbody",null,[e("tr",null,[S,e("td",null,[R,s(n,{to:"/Docs/zapp.html#configure-zapp-files-with-user-setting-variables"},{default:a(()=>[Z]),_:1}),z,A,D,B,I,H,V,q,Q,$,Y])]),N,U,M])]),X,e("p",null,[j,e("a",W,[G,s(o)]),F,e("a",J,[K,s(o)]),ee]),te,se,e("ul",null,[oe,ne,e("li",null,[ae,s(n,{to:"/Docs/interact_zos_zopeneditor.html"},{default:a(()=>[re]),_:1}),ie]),e("li",null,[pe,e("ul",null,[e("li",null,[le,e("a",ce,[he,s(o)]),de,e("a",ue,[me,s(o)]),fe])])]),ge,e("li",null,[be,s(n,{to:"/Docs/setting_fileassociations.html#remote-file-associations"},{default:a(()=>[_e]),_:1}),ke])]),we,e("p",null,[ye,s(n,{to:"/Docs/zapp.html"},{default:a(()=>[Oe]),_:1}),ve]),xe,e("table",null,[Pe,e("tbody",null,[e("tr",null,[Te,e("td",null,[Ee,s(n,{to:"/Docs/zapp.html#configure-zapp-files-with-user-setting-variables"},{default:a(()=>[Le]),_:1}),Ce,Se,Re,Ze,ze])]),Ae,De,Be])]),Ie],64)}var Ye=h(d,[["render",He]]);export{Ye as default};
diff --git a/assets/advanced_preprocessor.html.d7c4d6f2.js b/assets/advanced_preprocessor.html.d7c4d6f2.js
new file mode 100644
index 000000000..38c6c6a36
--- /dev/null
+++ b/assets/advanced_preprocessor.html.d7c4d6f2.js
@@ -0,0 +1,20 @@
+import{r as i,o as p,a as l,b as e,d as o,w as a,F as c,c as r,e as t}from"./app.daa93c96.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const u={},h=r('
     Preprocessor support
    Z Open Editor provides the advanced capability to integrate parsing of COBOL and PL/I programs with a custom preprocessor to allow editing programs that contain such preprocessor statements without causing the editor to show syntax errors. The preprocessor would be executed on either a developer machine by Z Open Editor in the background (local) or a z/OS system (remote), taking COBOL or PL/I with custom code and transforming it to a valid program. Users can then continue editing such programs by using the preprocessor input to still provide full language support such as code completion, syntax error highlighting, and outline view for the regular COBOL or PL/I statements. Then at each save or editor focus change the preprocessor can run automatically again to update the processed representation used by the editor. The editor would not learn the preprocessor language, but rather ensure that the resulting preprocessed output is still valid COBOL or PL/I.
     Local preprocessor
     Example workflow
    The following workflow is written from the perspective of developer, Deb.
    1. Deb installs a command-line centric preprocessor program on her local development machine.
    2. Deb creates a zapp.yaml file with a preprocessor profile type. The profile specifies the command-line for running the preprocessor on the currently edited program file as well as the output path for the preprocessed program files.
    3. Deb edits a program file with preprocessor statements in Z Open Editor.
    4. Deb either manually starts preprocessing the program via a right-click menu command or creates a user setting to automatically run the preprocessor on Save.
    5. Z Open Editor starts the preprocessor command in the background and sends the output file to its COBOL (PL/I) parser.
    6. Z Open Editor's COBOL (PL/I) parser will compare the program in the editor with the output of the preprocessor command.
    7. Deb hovers over processor statements in Z Open Editor, which displays the resulting COBOL (PL/I).
    8. Deb continues editing the program in Z Open Editor. Z Open Editor continues to provide full language support for all the parts of the program that are not preprocessor statements.
    ',6),m=t("To learn and explore this workflow, check out the example preprocessor and code samples in our Github repository at "),g={href:"https://github.com/ibm/zopeneditor-sample/tree/wazi-main/preprocessor",target:"_blank",rel:"noopener noreferrer"},f=t("https://github.com/ibm/zopeneditor-sample/tree/wazi-main/preprocessor"),b=t(". Review the "),_={href:"https://github.com/ibm/zopeneditor-sample/tree/wazi-main/preprocessor/README.md",target:"_blank",rel:"noopener noreferrer"},k=t("Readme"),w=t(" file in this folder with detailed instructions for building and running the sample."),y=e("h3",{id:"requirements-for-the-preprocessor",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#requirements-for-the-preprocessor","aria-hidden":"true"},"#"),t(" Requirements for the preprocessor")],-1),v=e("p",null,"To be able to integrate your preprocessor with Z Open Editor, it must fulfill these requirements:",-1),O=e("ul",null,[e("li",null,"It needs to run locally on your development machine where Z Open Editor is running."),e("li",null,"You need to be able to run the processor via command-line."),e("li",null,"The command-line operation needs to create an output file that contains valid COBOL."),e("li",null,"The output path can be computed by specifying a new file extension to be used with the program file name.")],-1),P=e("h3",{id:"zapp-profile",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#zapp-profile","aria-hidden":"true"},"#"),t(" ZAPP profile")],-1),x=t("The integration of the preprocessor with the editor is handled via a "),T=t("ZAPP file profile"),L=t(". Such a profile might look like this:"),E=r(`
    - name: extended-cobol
+  type: preprocessor
+  language: cobol
+  location: local
+  settings:
+    command: ${JAVA_HOME}/bin/java -jar ${WORKSPACE}/preprocessor/my-preprocessor/target/my-preprocessor-1.0-SNAPSHOT.jar ${input_file} ${output_file}
+    outputPath: ./preprocessor/output
+    fileExtension: cee
+    environmentVariables:
+      VARIABLE1: value1
+
    The language property is mandatory and allows the values cobol or pl1 only.
    In the settings object, the following properties can be used:
    `,3),S=e("thead",null,[e("tr",null,[e("th",null,"Property"),e("th",null,"Description")])],-1),R=e("td",null,"command",-1),Z=t("The command line to be executed. You can mix the command line with "),z=t("ZAPP Variables"),A=t(" as well as use the predefined variables "),C=e("code",null,"${input_file}",-1),I=t(" and "),D=e("code",null,"${output_file}",-1),B=t(". You need to define "),H=e("code",null,"${JAVA_HOME}",-1),V=t(" and "),q=e("code",null,"${WORKSPACE}",-1),Q=t(" in the example above as ZAPP variables. Environment variables can only be used by specifying them with the "),$=e("code",null,"environmentVariables",-1),Y=t(" property."),N=e("tr",null,[e("td",null,"outputPath"),e("td",null,"The base path in which the output file should be created. This path must be inside the current VS Code workspace so that the editor can see and process the files.")],-1),U=e("tr",null,[e("td",null,"fileExtension"),e("td",null,"The file extension to be used for the output files.")],-1),M=e("tr",null,[e("td",null,"environmentVariables"),e("td",null,"An optional sub-object to specify the environment variables that should be created before executing the command.")],-1),X=r('
     Running the preprocessor
    After you specify the ZAPP profile, you can run the preprocessor in the following ways:
    1. Right-click and choose Execute local preprocessor command to manually run the preprocessor in the program file editor.
    2. Automatically run the preprocessor via the VS Code user setting zopeneditor.autoPreprocessor. The setting can have one of the values: 
      • off: disables the automatic preprocessor execution.
      • open: when a program file is opened in the editor.
      • save: when a program file is saved in the editor.
      • both: when opening and saving a program file in the editor.
    When the preprocessor command runs, a progress dialog with a Cancel button is displayed. When the preprocessor finishes, it refreshes the editor and any syntax errors that were caused by preprocessor statements should go away or, if they contained problems, will show those instead.
    If the processor command execution failed and produced errors, a dialog will be shown with a button to open the Z Open Editor log file viewer which lists the detailed error message produced by the preprocessor command.
     Using the preprocessor output in the editor
    After the preprocessor is executed, you can hover the mouse of preprocessor statements in their program file to see the code that was generated for the statement. You can edit these statements and all other code in the program.
    Syntax errors for preprocessor statements will not be available until the preprocessor runs again. Syntax errors for other regular COBOL or PL/I code will be shown while typing as usual in Z Open Editor.
    To get a side-by-side view of the program before and after preprocessing, you can use the right-click menu option Compare preprocessor input and output files.
     Remote preprocessor
     Example workflow
    The following workflow is written from the perspective of developer, Deb.
    1. Deb sets up a z/OS centric preprocessor data member on her remote z/OS development machine. This data member must be either a REXX or CLIST program.
    2. Deb creates a zapp.yaml file with a preprocessor profile type. The profile specifies the TSO command for running the preprocessor on the currently edited program data member as well as the output dataset for the preprocessed data members.
    3. Deb edits a dataset member with preprocessor statements in Z Open Editor through Zowe.
    4. Deb either manually starts preprocessing the program via a right-click menu command or creates a user setting to automatically run the preprocessor on Save.
    5. Z Open Editor uses Zowe to start the preprocessor command in the background and sends the output file to its parser.
    6. Z Open Editor's COBOL or PL/I parser will compare the program in the editor with the output of the preprocessor command.
    7. Deb hovers over processor statements in Z Open Editor, which displays the resulting COBOL or PL/I.
    8. Deb continues editing the program in Z Open Editor. Z Open Editor continues to provide full language support for all the parts of the program that are not preprocessor statements.
    ',13),j=t("To learn and explore this sample workflow, check out the example preprocessor and code samples in our Github repository at "),W={href:"https://github.com/ibm/zopeneditor-sample/tree/wazi-main/preprocessor",target:"_blank",rel:"noopener noreferrer"},G=t("https://github.com/ibm/zopeneditor-sample/tree/wazi-main/preprocessor"),F=t(". Review the "),J={href:"https://github.com/ibm/zopeneditor-sample/tree/wazi-main/preprocessor/README.md",target:"_blank",rel:"noopener noreferrer"},K=t("Readme"),ee=t(" file in this folder with detailed instructions for building and running the sample."),te=e("h3",{id:"requirements-for-the-preprocessor-1",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#requirements-for-the-preprocessor-1","aria-hidden":"true"},"#"),t(" Requirements for the preprocessor")],-1),oe=e("p",null,"To be able to integrate your preprocessor with Z Open Editor, it must fulfill these requirements:",-1),se=e("li",null,"It needs to run remotely on your z/OS machine.",-1),ne=e("li",null,"The remote preprocessor must be either a REXX or CLIST program.",-1),ae=t("You need a RSE API or z/OSMF Zowe profile available in your workspace and "),re=t("configured as a default for Z Open Editor"),ie=t("."),pe=t("You need to be able to run the processor via a Zowe TSO command. "),le=t("You can read more about TSO commands and Zowe TSO profiles "),ce={href:"https://ibm.github.io/zopeneditor-about/Docs/interact_zos_cli.html#run-interactive-tso-commands",target:"_blank",rel:"noopener noreferrer"},de=t("in the documentation"),ue=t(", and explore some examples in this "),he={href:"https://medium.com/zowe/zowe-ci-and-tso-commands-14e5445fca1e",target:"_blank",rel:"noopener noreferrer"},me=t("blog"),ge=t("."),fe=e("li",null,"The TSO operation needs to create an output data member that contains valid COBOL or PL/I.",-1),be=t("The program file to be processed needs to be in a PDS that is recognized by Z Open Editor to contain COBOL (PL/I) and the COBOL (PL/I) language support must be active. See "),_e=t("Remote file associations"),ke=t(" for more details."),we=e("h3",{id:"zapp-profile-1",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#zapp-profile-1","aria-hidden":"true"},"#"),t(" ZAPP profile")],-1),ye=t("The integration of the preprocessor with the editor is handled via a "),ve=t("ZAPP file profile"),Oe=t(". Such a profile could look like this:"),Pe=r(`
    - name: extended-cobol
+  type: preprocessor
+  language: cobol
+  location: mvs
+  settings:
+    commandDataSet: ${HLQ}.PREPROC.REXX.(PREPROC)
+    tempDataHLQ: ${HLQ}
+    outputDataSet: ${HLQ}.PREPROC.OUTPUT()
+    commandParameters: "var1=val1"
+
    The language property is mandatory and allows the values cobol or pl1 only.
    In the settings object the following properties can be used:
    `,3),xe=e("thead",null,[e("tr",null,[e("th",null,"Property"),e("th",null,"Description")])],-1),Te=e("td",null,"commandDataSet",-1),Le=t("The data member to be executed. You can mix with "),Ee=t("ZAPP Variables"),Se=t(". You need to define "),Re=e("code",null,"${HLQ}",-1),Ze=t(" in the example above as ZAPP variables. Environment variables can only be used by specifying them with the below "),ze=e("code",null,"commandParameters",-1),Ae=t(" property."),Ce=e("tr",null,[e("td",null,"tempDataHLQ"),e("td",null,[t("The High Level Qualifier (HLQ) to use to save an xml file that stores information for the "),e("code",null,"commandDataSet"),t(" to read from.")])],-1),Ie=e("tr",null,[e("td",null,"outputDataSet"),e("td",null,"The output dataset to save the data member output file of the preprocessor.")],-1),De=e("tr",null,[e("td",null,"commandParameters"),e("td",null,"An optional parameter to specify any command parameters that should be used when executing the command.")],-1),Be=r('
     Running the preprocessor
    After you specify the ZAPP profile, you can run the preprocessor in the following ways:
    1. Right-click and choose Execute remote preprocessor command to manually run the preprocessor in the program file editor.
    2. Automatically run the preprocessor via the VS Code user setting zopeneditor.autoPreprocessor. The setting can have one of the values: 
      • off: disables the automatic preprocessor execution.
      • open: when a program file is opened in the editor.
      • save: when a program file is saved in the editor.
      • both: when opening and saving a program file in the editor.
    When the preprocessor command runs, a progress dialog with a Cancel button is displayed. A sequential data member is created using the tempDataHLQ to store information for the preprocessor to read. When the preprocessor finishes, it deletes the sequential data member and then refreshes the editor and any syntax errors that were caused by preprocessor statements should go away or, if they contained problems, will show those instead.
    If the processor command execution failed and produced errors, a dialog will be shown with a button to open the Z Open Editor log file viewer which lists the detailed error message produced by the preprocessor command and the sequential data member will not be deleted.
    The following is an example of the sequential data member that gets created for the remote preprocessor to read based on the above ZAPP profile:
    <PROGRAM>HLQ.COBOL(PRINTAPP)</PROGRAM><SYSLIB></SYSLIB><COMPILEOPTIONS></COMPILEOPTIONS><OUTPUT>HLQ.PREPROC.OUTPUT(PRINTAPP)</OUTPUT>\n
    • The ${HLQ} variable gets replaced with HLQ from user settings
    • The input data member's name was PRINTAPP
    • There were no mvs cobol libraries or compiler options specified in the ZAPP property groups
     Using the preprocessor output in the editor
    After the preprocessor is executed, you can hover the mouse of preprocessor statements in their program file to see the code that was generated for the statement. You can edit these statements and all other code in the program.
    Syntax errors for preprocessor statements will not be available until the preprocessor runs again. Syntax errors for other regular COBOL or PL/I code will be shown while typing as usual in Z Open Editor.
    To get a side-by-side view of the program before and after preprocessing, you can use the right-click menu option Compare preprocessor input and output files.
     Limitations
    Restriction: Several limitations are associated with using a preprocessor within Z Open Editor:
    • COBOL code formatting will be disabled for files that contain preprocessor statements.
    • Not all preprocessor statements within a COBOL EXEC block might be identified.
    • All preprocessor statements might not be identified if the code is reorganized.
    • Preprocessor statements that modify text in another location of a program might not be identified.
    • Real-time syntax checking of programs that contain preprocessor statements that contain only the beginning or ending of a language comment might not be identified.
    • Remote preprocessor command dataset members must be either REXX or CLIST files.
    • The side-by-side comparison of program and preprocessed output is not yet available for the remote preprocessor support.
    ',15);function He(Ve,qe){const s=i("ExternalLinkIcon"),n=i("RouterLink");return p(),l(c,null,[h,e("p",null,[m,e("a",g,[f,o(s)]),b,e("a",_,[k,o(s)]),w]),y,v,O,P,e("p",null,[x,o(n,{to:"/Docs/zapp.html"},{default:a(()=>[T]),_:1}),L]),E,e("table",null,[S,e("tbody",null,[e("tr",null,[R,e("td",null,[Z,o(n,{to:"/Docs/zapp.html#configure-zapp-files-with-user-setting-variables"},{default:a(()=>[z]),_:1}),A,C,I,D,B,H,V,q,Q,$,Y])]),N,U,M])]),X,e("p",null,[j,e("a",W,[G,o(s)]),F,e("a",J,[K,o(s)]),ee]),te,oe,e("ul",null,[se,ne,e("li",null,[ae,o(n,{to:"/Docs/interact_zos_zopeneditor.html"},{default:a(()=>[re]),_:1}),ie]),e("li",null,[pe,e("ul",null,[e("li",null,[le,e("a",ce,[de,o(s)]),ue,e("a",he,[me,o(s)]),ge])])]),fe,e("li",null,[be,o(n,{to:"/Docs/setting_fileassociations.html#remote-file-associations"},{default:a(()=>[_e]),_:1}),ke])]),we,e("p",null,[ye,o(n,{to:"/Docs/zapp.html"},{default:a(()=>[ve]),_:1}),Oe]),Pe,e("table",null,[xe,e("tbody",null,[e("tr",null,[Te,e("td",null,[Le,o(n,{to:"/Docs/zapp.html#configure-zapp-files-with-user-setting-variables"},{default:a(()=>[Ee]),_:1}),Se,Re,Ze,ze,Ae])]),Ce,Ie,De])]),Be],64)}var Ye=d(u,[["render",He]]);export{Ye as default};
diff --git a/assets/advanced_problems_view.html.b377706d.js b/assets/advanced_problems_view.html.090028b4.js
similarity index 97%
rename from assets/advanced_problems_view.html.b377706d.js
rename to assets/advanced_problems_view.html.090028b4.js
index 7c8d740eb..b48715bdf 100644
--- a/assets/advanced_problems_view.html.b377706d.js
+++ b/assets/advanced_problems_view.html.090028b4.js
@@ -1 +1 @@
-import{r as t,o as n,a as i,b as e,d as a,F as l,e as o}from"./app.f6cb3ed9.js";import{_ as s}from"./plugin-vue_export-helper.21dcd24c.js";var d="/zopeneditor-about/assets/user-build-problems.b55ed528.png";const c={},u=e("h1",{id:"user-build-problems-view",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#user-build-problems-view","aria-hidden":"true"},"#"),o(" User build Problems view")],-1),p=e("p",null,"When you edit enterprise application code in Z Open Editor you get full language support provided by our language servers giving you code completion and real-time syntax errors. However, the parsers utilized in Z Open Editor can only identify problems that a compiler can detect. As a result, sometimes it is necessary to actually build the program and review the compiler output, which includes warnings that the editor was not able to produce.",-1),h=o("Z Open Editor provides an integration with IBM Dependency-Based Build called "),b={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-building-cobol-pli-hlasm-programs-user-build",target:"_blank",rel:"noopener noreferrer"},m=o("user build"),g=o(". You can run a build of a program directly from inside Z Open Editor via the context menu. When integrated with Zowe Explorer, the program will be uploaded to USS and then built with Dependency-Based Build. Until now the build would complete by downloading the build log files into the local development workspace. You would have to review the log file by opening it in the editor and scrolling through it."),w=e("p",null,"If you enable Z Open Editor's advanced capabilities, Dependency-Based Build log files will now be parsed by Z Open Editor and presented as errors and warnings in the regular VS Code Problems view. You can click entries in the Problems view to directly navigate to the line in the code for which the problem was reported. These error will be shown next to regular Z Open Editor errors side-by-side, but you can distinguish them by the compiler error number displayed next to them.",-1),_=e("p",null,"The Problems view can be cleared manually via a right-click on any message or automatically when you rerun a build.",-1),v=e("p",null,[e("img",{src:d,alt:"User Build Problems View"})],-1),y=e("p",null,[o("The screenshot above shows an example of the Problems view reporting a warning about a "),e("code",null,"RECORD IS VARYING"),o(" statement not matching the required range. The problem could only be found by building the program. CCombining parse with user build errors and warnings gives developers new ways to determine problems they could not have before.")],-1);function f(x,E){const r=t("ExternalLinkIcon");return n(),i(l,null,[u,p,e("p",null,[h,e("a",b,[m,a(r)]),g]),w,_,v,y],64)}var O=s(c,[["render",f]]);export{O as default};
+import{r as t,o as n,a as i,b as e,d as a,F as l,e as o}from"./app.daa93c96.js";import{_ as s}from"./plugin-vue_export-helper.21dcd24c.js";var d="/zopeneditor-about/assets/user-build-problems.b55ed528.png";const c={},u=e("h1",{id:"user-build-problems-view",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#user-build-problems-view","aria-hidden":"true"},"#"),o(" User build Problems view")],-1),p=e("p",null,"When you edit enterprise application code in Z Open Editor you get full language support provided by our language servers giving you code completion and real-time syntax errors. However, the parsers utilized in Z Open Editor can only identify problems that a compiler can detect. As a result, sometimes it is necessary to actually build the program and review the compiler output, which includes warnings that the editor was not able to produce.",-1),h=o("Z Open Editor provides an integration with IBM Dependency-Based Build called "),b={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-building-cobol-pli-hlasm-programs-user-build",target:"_blank",rel:"noopener noreferrer"},m=o("user build"),g=o(". You can run a build of a program directly from inside Z Open Editor via the context menu. When integrated with Zowe Explorer, the program will be uploaded to USS and then built with Dependency-Based Build. Until now the build would complete by downloading the build log files into the local development workspace. You would have to review the log file by opening it in the editor and scrolling through it."),w=e("p",null,"If you enable Z Open Editor's advanced capabilities, Dependency-Based Build log files will now be parsed by Z Open Editor and presented as errors and warnings in the regular VS Code Problems view. You can click entries in the Problems view to directly navigate to the line in the code for which the problem was reported. These error will be shown next to regular Z Open Editor errors side-by-side, but you can distinguish them by the compiler error number displayed next to them.",-1),_=e("p",null,"The Problems view can be cleared manually via a right-click on any message or automatically when you rerun a build.",-1),v=e("p",null,[e("img",{src:d,alt:"User Build Problems View"})],-1),y=e("p",null,[o("The screenshot above shows an example of the Problems view reporting a warning about a "),e("code",null,"RECORD IS VARYING"),o(" statement not matching the required range. The problem could only be found by building the program. CCombining parse with user build errors and warnings gives developers new ways to determine problems they could not have before.")],-1);function f(x,E){const r=t("ExternalLinkIcon");return n(),i(l,null,[u,p,e("p",null,[h,e("a",b,[m,a(r)]),g]),w,_,v,y],64)}var O=s(c,[["render",f]]);export{O as default};
diff --git a/assets/advanced_resource_table.html.2552a95f.js b/assets/advanced_resource_table.html.56d32fb5.js
similarity index 57%
rename from assets/advanced_resource_table.html.2552a95f.js
rename to assets/advanced_resource_table.html.56d32fb5.js
index c1cf5620d..691767d98 100644
--- a/assets/advanced_resource_table.html.2552a95f.js
+++ b/assets/advanced_resource_table.html.56d32fb5.js
@@ -1 +1 @@
-const e={key:"v-01e2125a",path:"/Docs/advanced_resource_table.html",title:"z/OS Resources Table",lang:"en-US",frontmatter:{},excerpt:"",headers:[{level:1,title:"z/OS Resources Table",slug:"z-os-resources-table",children:[{level:2,title:"Setting up profiles for the z/OS Resources Table",slug:"setting-up-profiles-for-the-z-os-resources-table",children:[]},{level:2,title:"Opening the z/OS Resources Table",slug:"opening-the-z-os-resources-table",children:[]},{level:2,title:"Views",slug:"views",children:[]},{level:2,title:"Actions",slug:"actions",children:[]}]}],git:{updatedTime:1723085172e3,contributors:[{name:"Benjamin Santos",email:"Benjamin.Santos@ibm.com",commits:4},{name:"Hestia Zhang",email:"Hestia.Zhang@ibm.com",commits:2},{name:"PETER HAUMER",email:"phaumer@us.ibm.com",commits:2},{name:"Peter Haumer",email:"4391934+phaumer@users.noreply.github.com",commits:1},{name:"Saile Daimwood",email:"sdaimwood@ibm.com",commits:1}]},filePathRelative:"Docs/advanced_resource_table.md"};export{e as data};
+const e={key:"v-01e2125a",path:"/Docs/advanced_resource_table.html",title:"z/OS Resources Table",lang:"en-US",frontmatter:{},excerpt:"",headers:[{level:1,title:"z/OS Resources Table",slug:"z-os-resources-table",children:[{level:2,title:"Setting up profiles for the z/OS Resources Table",slug:"setting-up-profiles-for-the-z-os-resources-table",children:[]},{level:2,title:"Opening the z/OS Resources Table",slug:"opening-the-z-os-resources-table",children:[]},{level:2,title:"Views",slug:"views",children:[]},{level:2,title:"Actions",slug:"actions",children:[]}]}],git:{updatedTime:172669763e4,contributors:[{name:"Benjamin Santos",email:"Benjamin.Santos@ibm.com",commits:6},{name:"Hestia Zhang",email:"Hestia.Zhang@ibm.com",commits:2},{name:"PETER HAUMER",email:"phaumer@us.ibm.com",commits:2},{name:"Peter Haumer",email:"4391934+phaumer@users.noreply.github.com",commits:1},{name:"Saile Daimwood",email:"sdaimwood@ibm.com",commits:1}]},filePathRelative:"Docs/advanced_resource_table.md"};export{e as data};
diff --git a/assets/advanced_resource_table.html.b412833a.js b/assets/advanced_resource_table.html.b412833a.js
deleted file mode 100644
index 465e8a082..000000000
--- a/assets/advanced_resource_table.html.b412833a.js
+++ /dev/null
@@ -1 +0,0 @@
-import{r as o,o as r,a as n,b as t,d as a,w as i,F as l,e,c as h}from"./app.f6cb3ed9.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";var d="/zopeneditor-about/assets/zos-resources-table-actions.060ab674.png",p="/zopeneditor-about/assets/zos-resource-table-batch-actions.8f480e3b.png",u="/zopeneditor-about/assets/zos-resources-table-search-filter-buttons.1f1aff9d.png",f="/zopeneditor-about/assets/zos-resources-table-sequential-data-set-search-results.0ba133b2.png",g="/zopeneditor-about/assets/zos-resources-table-filter-results.ab1f00ed.png";const w={},b=t("h1",{id:"z-os-resources-table",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#z-os-resources-table","aria-hidden":"true"},"#"),e(" z/OS Resources Table")],-1),v=e("The z/OS Resources Table provides a tabular view to interact with z/OS resources using "),m=e("your existing RSE API or z/OSMF Zowe profiles"),y=e(". It is an advanced capability available for users with an "),S=e("active license"),_=e(". It is designed to be both beginner-friendly for new mainframe application developers and to provide more experienced developers with the necessary tools and information to manage host resources."),z=t("h2",{id:"setting-up-profiles-for-the-z-os-resources-table",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#setting-up-profiles-for-the-z-os-resources-table","aria-hidden":"true"},"#"),e(" Setting up profiles for the z/OS Resources Table")],-1),T=e("To use the z/OS Resources Table, you must create an RSE API or z/OSMF profile using Zowe Explorer. For more information on how to create profiles by using Zowe Explorer, see "),x=e("Connecting to z/OS with Zowe Explorer walkthrough"),O=e("."),k=h('
     Opening the z/OS Resources Table
    You can open the z/OS Resources Table in one of the following ways:
    • Cmd \u2318/Ctrl + Shift + P to open the command prompt and run the command >IBM Z Open Editor: Open z/OS Resource Table.
    • After setting an active filter for a profile in the Zowe Explorer JOBS, DATA SETS, or USS view, right-click the active profile and select Show in z/OS Resource Table from the context menu. This will display items matching the filter in the table.
    • After setting an active filter for a profile in the Zowe Explorer JOBS, DATA SETS, or USS view, right-click a resource (e.g. a data set, a job) and select Show in z/OS Resource Table from the context menu. This will display the selected resource in the table.
    The first two methods will open the table and display the default Profiles view. The third method will display the data sets or jobs matching that filter.
     Views
     Profiles View
    The profiles view displays the RSE API and z/OSMF profiles defined in your Zowe Explorer team configuration file. To start accessing z/OS resources for a specific profile, click on the row of that profile.
    After clicking on a profile, a view is displayed that allows the user to select a z/OS resource to access: MVS, USS, and JES. Clicking on one of these rows will load the MVS view, USS view, or JES view, respectively.
     MVS View
    The MVS view consists of the following rows that perform the following actions when clicked:
    • Default User Data Sets: Displays all data sets that have the selected profile's user ID as their high-level qualifier (only available for profiles using password or passphrase authentication)
    • Filters: Opens the Filters view where users can create and use custom patterns for viewing data sets.
    • Favorites: Opens a view that displays data sets favorited by the user.
    • History: Opens a view that displays the five most recently used patterns to filter data sets.
    Clicking on the Default User Data Sets, a custom pattern in the Filters view, or a pattern in the History view will display data sets that match the selected pattern.
     JES View
    The JES view consists of the following rows that perform the following actions when clicked:
    • Default User Jobs: Displays all jobs that have the selected profile's user as their owner (only available for profiles using password or passphrase authentication)
    • Filters: Opens the Filters view where users can create and use custom patterns for viewing jobs.
    • Favorites: Opens a view that displays jobs favorited by the user.
    • History: Opens a view that displays the five most recently used queries to filter jobs.
    Clicking on the Default User Jobs, a custom query in the Filters view, or a query in the History view will display jobs that match the selected query.
     USS View
    The USS view consists of the following rows that perform the following actions when clicked:
    • User Files: Displays all items in the /u/user directory, where user is the selected profile's user (only available for profiles using password or passphrase authentication)
    • Filters: Opens the Filters view where users can use and save paths for viewing UNIX items.
    • Favorites: Opens a view that displays UNIX items favorited by the user.
    • History: Opens a view that displays the five most recently viewed UNIX items.
     Actions
    When viewing resources, there are different kinds of actions available in the table. These include toolbar actions, batch actions, and overflow menu actions.
    'zos-resource-table-actions'
    • Navigation actions are the same across all views. They can be used to navigate through the table's history or to return to the Profiles view.
    • Toolbar actions are unique to specific views. For example, the Create Data Set button is only available when viewing data sets. Hovering a toolbar action button will display popover text describing what the button does.
    • Overflow menu actions are available only in select views. Selecting an overflow menu action will perform the action for the selected resource. An overflow menu can be opened by clicking the three dots \u22EE on the right side of a row. These dots appear on row hover, and will not appear on rows that do not use overflow actions.
    • The input area is a special field available while viewing jobs, UNIX files, or data sets that enables users to quickly change the active filter pattern and display an updated list of resources matching that pattern.
    The last available kind of actions are batch actions.
    'zos-resource-table-batch-actions'
    Batch actions are only available for views with selectable rows. They are displayed after the user selects one or many rows using the checkboxes on the left side of the view. Batch actions are executed on every resource selected. For example, if you select the checkbox for multiple jobs and use the Delete batch action, all the selected jobs will be deleted.
     Search and Filter actions for partitioned and sequential data sets
    The z/OS Resources Table provides actions for searching and filtering partitioned and sequential data sets to refine the results of the data sets query.
    When viewing data sets, two new buttons for Search and Filter will be available in the toolbar.
    'zos-resources-table-search-filter-buttons'
    Clicking the Search button will open a menu that lets the user specify a string. After clicking Submit, a search is performed for sequential data sets containing the specified content. The results are displayed in the table in expandable rows, which include the sequential data set name and its attributes, the number of matches, and the line that contains the content.
    'zos-resources-table-search-results'
    This search is limited to the active filter's scope (which is displayed in the top-left of the table) and by any filters specified in the Filter menu. After a search is submitted, it will stay active until it is cleared. To clear the search, press the Reset button to the right of the Submit button.
    Clicking one of the matches in the search results will open the sequential data set in an editor. The matching content of that line will be selected and your cursor will be placed at the end of the content.
     Filter
    Clicking the Filter button will open a menu that contains checkboxes for controlling the visibility of partitioned and sequential data sets and an input field that accepts a data set name pattern. This input field accepts wildcards * and is used to limit the scope of the active filter further.
    For example, if the active filter is IBMUSER.* and *.SAMPLE.* is entered into the input field and submitted, only data sets with IBMUSER as the high-level qualifier that contain a SAMPLE qualifier anywhere in the data set name will be displayed in the table (e.g. IBMUSER.SAMPLE.COBOL, IBMUSER.X.Y.Z.SAMPLE).
    After you adjust the visibility of partitioned or sequential data sets and click Submit, only data sets that satisfy the filter(s) will be displayed in the table. This filter will stay active until it is cleared, even if the user changes the active filter. To clear the filter, press the Reset button to the right of the Submit button.
    'zos-resources-table-filter-results'
    Users can simultaneously specify and submit filters and a search to apply them to the active filter.
    ',41);function F(E,R){const s=o("RouterLink");return r(),n(l,null,[b,t("p",null,[v,a(s,{to:"/Docs/interact_zos_overview.html"},{default:i(()=>[m]),_:1}),y,a(s,{to:"/Docs/advanced_activation.html"},{default:i(()=>[S]),_:1}),_]),z,t("p",null,[T,a(s,{to:"/Docs/connect_to_zos_with_zowe_explorer_e2e.html"},{default:i(()=>[x]),_:1}),O]),k],64)}var A=c(w,[["render",F]]);export{A as default};
diff --git a/assets/advanced_resource_table.html.cac10c8e.js b/assets/advanced_resource_table.html.cac10c8e.js
new file mode 100644
index 000000000..b736af57c
--- /dev/null
+++ b/assets/advanced_resource_table.html.cac10c8e.js
@@ -0,0 +1 @@
+import{r as o,o as r,a as n,b as t,d as s,w as i,F as l,e,c}from"./app.daa93c96.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";var d="/zopeneditor-about/assets/zos-resources-table-actions.060ab674.png",p="/zopeneditor-about/assets/zos-resource-table-batch-actions.8f480e3b.png",u="/zopeneditor-about/assets/zos-resources-table-search-filter-buttons.1f1aff9d.png",f="/zopeneditor-about/assets/zos-resources-table-sequential-data-set-search-results.0ba133b2.png",b="/zopeneditor-about/assets/zos-resources-table-member-search-results.6177dd0d.png",m="/zopeneditor-about/assets/uss-search-log-files.7b27b27c.png",w="/zopeneditor-about/assets/zos-resources-table-filter-results.ab1f00ed.png";const g={},v=t("h1",{id:"z-os-resources-table",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#z-os-resources-table","aria-hidden":"true"},"#"),e(" z/OS Resources Table")],-1),y=e("The z/OS Resources Table provides a tabular view to interact with z/OS resources using "),S=e("your existing RSE API or z/OSMF Zowe profiles"),_=e(". It is an advanced capability available for users with an "),z=e("active license"),T=e(". It is designed to be both beginner-friendly for new mainframe application developers and to provide more experienced developers with the necessary tools and information to manage host resources."),x=t("h2",{id:"setting-up-profiles-for-the-z-os-resources-table",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#setting-up-profiles-for-the-z-os-resources-table","aria-hidden":"true"},"#"),e(" Setting up profiles for the z/OS Resources Table")],-1),O=e("To use the z/OS Resources Table, you must create an RSE API or z/OSMF profile using Zowe Explorer. For more information on how to create profiles by using Zowe Explorer, see "),k=e("Connecting to z/OS with Zowe Explorer walkthrough"),q=e("."),F=c('
     Opening the z/OS Resources Table
    You can open the z/OS Resources Table in one of the following ways:
    • Cmd \u2318/Ctrl + Shift + P to open the command prompt and run the command >IBM Z Open Editor: Open z/OS Resource Table.
    • After setting an active filter for a profile in the Zowe Explorer JOBS, DATA SETS, or USS view, right-click the active profile and select Show in z/OS Resource Table from the context menu. This will display items matching the filter in the table.
    • After setting an active filter for a profile in the Zowe Explorer JOBS, DATA SETS, or USS view, right-click a resource (e.g. a data set, a job) and select Show in z/OS Resource Table from the context menu. This will display the selected resource in the table.
    The first two methods will open the table and display the default Profiles view. The third method will display the data sets or jobs matching that filter.
     Views
     Profiles View
    The profiles view displays the RSE API and z/OSMF profiles defined in your Zowe Explorer team configuration file. To start accessing z/OS resources for a specific profile, click on the row of that profile.
    After clicking on a profile, a view is displayed that allows you to select a z/OS resource to access: MVS, USS, and JES. Clicking on one of these rows will load the MVS view, USS view, or JES view, respectively.
     MVS View
    The MVS view consists of the following rows that perform the following actions when clicked:
    • Default User Data Sets: Displays all data sets that have the selected profile's user ID as their high-level qualifier (only available for profiles using password or passphrase authentication)
    • Filters: Opens the Filters view where users can create and use custom patterns for viewing data sets.
    • Favorites: Opens a view that displays data sets favorited by the user.
    • History: Opens a view that displays the five most recently used patterns to filter data sets.
    Clicking on the Default User Data Sets, a custom pattern in the Filters view, or a pattern in the History view will display data sets that match the selected pattern.
     JES View
    The JES view consists of the following rows that perform the following actions when clicked:
    • Default User Jobs: Displays all jobs that have the selected profile's user as their owner (only available for profiles using password or passphrase authentication)
    • Filters: Opens the Filters view where users can create and use custom patterns for viewing jobs.
    • Favorites: Opens a view that displays jobs favorited by the user.
    • History: Opens a view that displays the five most recently used queries to filter jobs.
    Clicking on the Default User Jobs, a custom query in the Filters view, or a query in the History view will display jobs that match the selected query.
     USS View
    The USS view consists of the following rows that perform the following actions when clicked:
    • User Files: Displays all items in the /u/user directory, where user is the selected profile's user (only available for profiles using password or passphrase authentication)
    • Filters: Opens the Filters view where users can use and save paths for viewing UNIX items.
    • Favorites: Opens a view that displays UNIX items favorited by the user.
    • History: Opens a view that displays the five most recently viewed UNIX items.
     Actions
    When viewing resources, there are different kinds of actions available in the table. These include toolbar actions, batch actions, and overflow menu actions.
    'zos-resource-table-actions'
    • Navigation actions are the same across all views. They can be used to navigate through the table's history or to return to the Profiles view.
    • Toolbar actions are unique to specific views. For example, the Create Data Set button is only available when viewing data sets. Hovering a toolbar action button will display popover text describing what the button does.
    • Overflow menu actions are available only in select views. Selecting an overflow menu action will perform the action for the selected resource. An overflow menu can be opened by clicking the three dots \u22EE on the right side of a row. These dots appear on row hover, and will not appear on rows that do not use overflow actions.
    • The input area is a special field available while viewing jobs, UNIX files, or data sets that enables users to quickly change the active filter pattern and display an updated list of resources matching that pattern.
    The last available kind of actions are batch actions.
    'zos-resource-table-batch-actions'
    Batch actions are only available for views with selectable rows. They are displayed after the user selects one or many rows using the checkboxes on the left side of the view. Batch actions are executed on every resource selected. For example, if a users selects checkboxes for multiple jobs and uses the Delete batch action, all the selected jobs will be deleted.
     Search and Filter actions
    The z/OS Resources Table provides actions for searching and filtering partitioned and sequential data sets to refine the results of the data sets query.
    When viewing data sets, two new buttons for Search and Filter will be available in the toolbar.
    'zos-resources-table-search-filter-buttons'
    Clicking the Search button will open a menu that allows users to perform a search for sequential data set content or partitioned data set members. After a search is submitted, it will stay active until it is cleared. To clear the search, press the Reset button to the right of the Submit button in the search menu.
    For sequential data sets, you can specify string content in the input field. After clicking Submit, a search is performed for sequential data sets containing the specified content. The results are displayed in the table in expandable rows, which include the sequential data set name and its attributes, the number of matches, and the line that contains the content.
    'zos-resources-table-sequential-search-results'
    This search is limited to the active filter's scope (which is displayed in the top-left of the table) and by any filters specified in the Filter menu.
    You can use the dropdown menu to switch the search from sequential data set content to partitioned data set members. This menu allows users to specify a member name pattern (accepts wildcards) and/or member content. After clicking Submit, only members matching that pattern and/or containing that content will be displayed in the table. Each member will be displayed in an expandable row, which includes the full member name, the number of matches, and the line that contains the matching content. Only members in partitioned data sets that match the active filter and any filters specified in the Filter menu will be included in the search.
    'zos-resources-table-members-search-results'
    You can also perform a member search within a partitioned data set. This search will only include members in the opened partitioned data set.
    Clicking one of the matches in the search results will open the sequential data set/member in a new editor. The matching content within that line will be selected and your cursor will be placed at the end of the content.
    While browsing USS, you can click the Search button to open a menu that allows users to perform a search for UNIX files. You can specify a file name pattern (accepts wild cards) and or file content to search for. After clicking Submit, only files matching the specified pattern and/or containing the specified content will be displayed in the table.
    'zos-resources-table-uss-search-results'
    Clicking one of the matches in the search results will open the file in a new editor. The matching content within that line will be selected and your cursor will be placed at the end of the content.
     Filter
    Clicking the Filter button will open a menu that contains checkboxes for controlling the visibility of partitioned and sequential data sets and an input field that accepts a data set name pattern. This input field accepts wildcards * and is used to limit the scope of the active filter further.
    For example, if the active filter is IBMUSER.* and *.SAMPLE.* is entered into the input field and submitted, only data sets with IBMUSER as the high-level qualifier that contain a SAMPLE qualifier anywhere in the data set name will be displayed in the table (e.g. IBMUSER.SAMPLE.COBOL, IBMUSER.X.Y.Z.SAMPLE).
    After adjusting the visibility of partitioned or sequential data sets and clicking Submit, only data sets that satisfy the filter(s) will be displayed in the table. This filter will stay active until it is cleared, even if the user changes the active filter. To clear the filter, press the Reset button to the right of the Submit button.
    'zos-resources-table-filter-results'
    You can simultaneously specify and submit filters and a search to apply them to the active filter.
     List of available actions
    Below is a comprehensive list of all actions available for each resource.
    • MVS data sets and members 
      • Create, delete, rename, migrate, edit, allocate copy, favorite/unfavorite, view members, submit members as jobs, upload members, filter data sets by name, partitioned data set and member search (by name or content), sequential data set search (by name or content)
    • USS files and directories 
      • Create, delete, edit, upload files, rename, copy and paste, edit attributes, favorite/unfavorite, file search (by name or content)
    • JES jobs 
      • Delete, get JCL, issue stop command, issue modify command, view and download spool files
    • All resources 
      • Change active filter/query, create and save filters/queries, sort by attribute, view filter/query history, view favorites
    ',53);function E(U,A){const a=o("RouterLink");return r(),n(l,null,[v,t("p",null,[y,s(a,{to:"/Docs/interact_zos_overview.html"},{default:i(()=>[S]),_:1}),_,s(a,{to:"/Docs/advanced_activation.html"},{default:i(()=>[z]),_:1}),T]),x,t("p",null,[O,s(a,{to:"/Docs/connect_to_zos_with_zowe_explorer_e2e.html"},{default:i(()=>[k]),_:1}),q]),F],64)}var D=h(g,[["render",E]]);export{D as default};
diff --git a/assets/announcing-jcl.html.f0aaa040.js b/assets/announcing-jcl.html.2d4b575d.js
similarity index 98%
rename from assets/announcing-jcl.html.f0aaa040.js
rename to assets/announcing-jcl.html.2d4b575d.js
index 53969c742..dd56be29c 100644
--- a/assets/announcing-jcl.html.f0aaa040.js
+++ b/assets/announcing-jcl.html.2d4b575d.js
@@ -1 +1 @@
-import{r as n,o as i,a as r,b as e,d as a,F as s,e as t,c as l}from"./app.f6cb3ed9.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";var d="/zopeneditor-about/assets/jcl-coloring.207e5a70.png",h="/zopeneditor-about/assets/jcl-errors.3d54f9e4.png",m="/zopeneditor-about/assets/jcl-completion.a66212f2.gif",g="/zopeneditor-about/assets/jcl-outline.7501ea05.gif",p="/zopeneditor-about/assets/jcl-toggle-comment.0dbcbaff.gif";const u={},f=e("h1",{id:"a-modern-jcl-job-control-language-editor",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#a-modern-jcl-job-control-language-editor","aria-hidden":"true"},"#"),t(" A Modern JCL (Job Control Language) Editor")],-1),b=e("blockquote",null,[e("p",null,[t("by Prasang Prajapati"),e("br"),t(" 18 June 2024")])],-1),y=t("In the ongoing effort to bring z/OS\xAE application development into the rich ecosystem of modern code editors, the JCL (Job Control Language) programming language is the next major addition. Enabled in IBM Z\xAE Open Editor 4.3.0 and "),_={href:"https://www.ibm.com/products/wazi-developer",target:"_blank",rel:"noopener noreferrer"},w=t("IBM\xAE Wazi Developer 4.3.0"),v=t(", you will be able to benefit from our "),C={href:"https://langserver.org",target:"_blank",rel:"noopener noreferrer"},J=t("Language Server Protocol (LSP)"),L=t(" implementation for JCL. This brings a plethora of language features to the editor, which make JCL development easier and more accessible."),x=l('
    There are several language features now available to augment the JCL editing experience.
     Syntax highlighting
    Arguably the most important of the bunch, the colorization of code is hard to go without these days. It's quite surprising how far a little color variance can go to make distinguishing symbols easier. Bringing visual clarity to the syntactically wild JCL programming language, this feature undeniably improves the speed and precision of development.
    JCL syntax highlighting
     Syntax errors
    Out of the many mainframe programming languages, JCL is truly the free spirit. Job control language (JCL) is used to tell the system what program to execute, followed by a description of program inputs and outputs. Basic JCL contains three types of statements: JOB, EXEC, and DD. A job can contain several EXEC statements (steps) and each step might have several DD statements. JCL provides a wide range of parameters and controls, but you will find that you use only a subset most of the time. Making a small typing mistake in adding mentioned JCL statements can lead to a major failure in submitting a JOB about which z/OS resources will be needed to process a batch job pr to start a system task. Syntax errors in an editor can help users identify mistakes that have been made in the program easily.
    JCL syntax errors
     Code completion
    Writing code can be a tedious process, and one that requires incredible memory and focus. Some of the simplest mistakes are misspelled statements, and given that JCL does not require JOB statement before steps (EXEC statement), these spelling errors can go completely unnoticed until some strange runtime errors occur. To alleviate this problem, you can utilize code completion to see INCLUDE statement, JCL Library statement, JOB statement, PROC statements and much more as you type. This incredibly powerful feature gives you the confidence to know that the symbol you type is the right one.
    JCL code completion
     Outline view
    A highly underrated feature, the outline view provides an overview of a program. We did the research, studying real JCL developers, to find out how to make this feature actually useful. What we found, it can be a powerful navigation tool for quickly going a step (an EXEC statement). Instead of crowding the outline view with every EXEC statement to find a DD statement that is inside a step, it was significantly more useful when users could glance over and see what EXEC and DD statements were defined in a JOB, and if they wanted, navigate there with one click.
    JCL Outline
     Commenting and uncommenting JCL code
    You can comment out one or multiple selected lines of code or a selected section of code by using the toggle comment function.
    How to use it
    To toggle comment for one or multiple selected lines of code, press Cmd+/ (Mac) or Ctrl+/ (Windows), or go to Edit > Toggle Line Comment.
    To toggle comments for a selected section of code, press Option+Shift+A (Mac) or Alt+Shift+A (Windows), or go to Edit > Toggle Block Comment.
    See the following example where we first toggle line comment on a single line, then toggle line comment on multiple selected lines, and finally toggle block comment on a selection:
    jcl toggle comment
     More information
    For information about how to utilize the different language features, see Making JCL code changes.
    ',22);function k(E,j){const o=n("ExternalLinkIcon");return i(),r(s,null,[f,b,e("p",null,[y,e("a",_,[w,a(o)]),v,e("a",C,[J,a(o)]),L]),x],64)}var z=c(u,[["render",k]]);export{z as default};
+import{r as n,o as i,a as r,b as e,d as a,F as s,e as t,c as l}from"./app.daa93c96.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";var d="/zopeneditor-about/assets/jcl-coloring.207e5a70.png",h="/zopeneditor-about/assets/jcl-errors.3d54f9e4.png",m="/zopeneditor-about/assets/jcl-completion.a66212f2.gif",g="/zopeneditor-about/assets/jcl-outline.7501ea05.gif",p="/zopeneditor-about/assets/jcl-toggle-comment.0dbcbaff.gif";const u={},f=e("h1",{id:"a-modern-jcl-job-control-language-editor",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#a-modern-jcl-job-control-language-editor","aria-hidden":"true"},"#"),t(" A Modern JCL (Job Control Language) Editor")],-1),b=e("blockquote",null,[e("p",null,[t("by Prasang Prajapati"),e("br"),t(" 18 June 2024")])],-1),y=t("In the ongoing effort to bring z/OS\xAE application development into the rich ecosystem of modern code editors, the JCL (Job Control Language) programming language is the next major addition. Enabled in IBM Z\xAE Open Editor 4.3.0 and "),_={href:"https://www.ibm.com/products/wazi-developer",target:"_blank",rel:"noopener noreferrer"},w=t("IBM\xAE Wazi Developer 4.3.0"),v=t(", you will be able to benefit from our "),C={href:"https://langserver.org",target:"_blank",rel:"noopener noreferrer"},J=t("Language Server Protocol (LSP)"),L=t(" implementation for JCL. This brings a plethora of language features to the editor, which make JCL development easier and more accessible."),x=l('
    There are several language features now available to augment the JCL editing experience.
     Syntax highlighting
    Arguably the most important of the bunch, the colorization of code is hard to go without these days. It's quite surprising how far a little color variance can go to make distinguishing symbols easier. Bringing visual clarity to the syntactically wild JCL programming language, this feature undeniably improves the speed and precision of development.
    JCL syntax highlighting
     Syntax errors
    Out of the many mainframe programming languages, JCL is truly the free spirit. Job control language (JCL) is used to tell the system what program to execute, followed by a description of program inputs and outputs. Basic JCL contains three types of statements: JOB, EXEC, and DD. A job can contain several EXEC statements (steps) and each step might have several DD statements. JCL provides a wide range of parameters and controls, but you will find that you use only a subset most of the time. Making a small typing mistake in adding mentioned JCL statements can lead to a major failure in submitting a JOB about which z/OS resources will be needed to process a batch job pr to start a system task. Syntax errors in an editor can help users identify mistakes that have been made in the program easily.
    JCL syntax errors
     Code completion
    Writing code can be a tedious process, and one that requires incredible memory and focus. Some of the simplest mistakes are misspelled statements, and given that JCL does not require JOB statement before steps (EXEC statement), these spelling errors can go completely unnoticed until some strange runtime errors occur. To alleviate this problem, you can utilize code completion to see INCLUDE statement, JCL Library statement, JOB statement, PROC statements and much more as you type. This incredibly powerful feature gives you the confidence to know that the symbol you type is the right one.
    JCL code completion
     Outline view
    A highly underrated feature, the outline view provides an overview of a program. We did the research, studying real JCL developers, to find out how to make this feature actually useful. What we found, it can be a powerful navigation tool for quickly going a step (an EXEC statement). Instead of crowding the outline view with every EXEC statement to find a DD statement that is inside a step, it was significantly more useful when users could glance over and see what EXEC and DD statements were defined in a JOB, and if they wanted, navigate there with one click.
    JCL Outline
     Commenting and uncommenting JCL code
    You can comment out one or multiple selected lines of code or a selected section of code by using the toggle comment function.
    How to use it
    To toggle comment for one or multiple selected lines of code, press Cmd+/ (Mac) or Ctrl+/ (Windows), or go to Edit > Toggle Line Comment.
    To toggle comments for a selected section of code, press Option+Shift+A (Mac) or Alt+Shift+A (Windows), or go to Edit > Toggle Block Comment.
    See the following example where we first toggle line comment on a single line, then toggle line comment on multiple selected lines, and finally toggle block comment on a selection:
    jcl toggle comment
     More information
    For information about how to utilize the different language features, see Making JCL code changes.
    ',22);function k(E,j){const o=n("ExternalLinkIcon");return i(),r(s,null,[f,b,e("p",null,[y,e("a",_,[w,a(o)]),v,e("a",C,[J,a(o)]),L]),x],64)}var z=c(u,[["render",k]]);export{z as default};
diff --git a/assets/announcing-rexx.html.47753f24.js b/assets/announcing-rexx.html.bcf7782b.js
similarity index 98%
rename from assets/announcing-rexx.html.47753f24.js
rename to assets/announcing-rexx.html.bcf7782b.js
index 9055eb940..f203c39c1 100644
--- a/assets/announcing-rexx.html.47753f24.js
+++ b/assets/announcing-rexx.html.bcf7782b.js
@@ -1 +1 @@
-import{r as a,o as n,a as r,b as t,d as i,F as s,e,c as h}from"./app.f6cb3ed9.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const l={},c=t("h1",{id:"a-modern-rexx-editor",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#a-modern-rexx-editor","aria-hidden":"true"},"#"),e(" A Modern REXX Editor")],-1),u=t("blockquote",null,[t("p",null,[e("by Bradley Knaysi"),t("br"),e(" 18 March 2021")])],-1),g=e("In the ongoing effort to bring z/OS\xAE application development into the rich ecosystem of modern code editors, the REXX programming language is the next major addition. Enabled in IBM Z\xAE Open Editor 1.2.0, "),f={href:"https://www.ibm.com/products/wazi-developer",target:"_blank",rel:"noopener noreferrer"},m=e("IBM\xAE Wazi Developer 1.2.0"),p=e(", and "),y={href:"https://www.ibm.com/products/developer-for-zos",target:"_blank",rel:"noopener noreferrer"},v=e("IBM Developer for z/OS 15.0.1"),b=e(", you will be able to benefit from our "),w={href:"https://langserver.org",target:"_blank",rel:"noopener noreferrer"},_=e("Language Server Protocol (LSP)"),x=e(" implementation for REXX. This brings a plethora of language features to the editor, which make REXX development easier and more accessible."),X=h('
    There are several language features now available to augment the REXX editing experience.
     Syntax highlighting
    Arguably the most important of the bunch, the colorization of code is hard to go without these days. It's quite surprising how far a little color variance can go to make distinguishing symbols easier. Bringing visual clarity to the syntactically wild REXX programming language, this feature undeniably improves the speed and precision of development.
     Syntax errors
    Out of the many mainframe programming languages, REXX is truly the free spirit. While many languages enforce spacing, tabbing, and case-sensitivity to parse elements of the code, REXX has little to no such constraints. The result is a wide variety of programming styles, which leave the developer wondering what valid syntax is and is not. This is where syntax errors shine, bringing visual clarity to common and sometimes frustratingly trivial mistakes.
     Code completion
    Writing code can be a tedious process, and one that requires incredible memory and focus. Some of the simplest mistakes are misspelled symbols, and given that REXX does not require variable declaration before definition, these spelling errors can go completely unnoticed until some strange runtime error occurs. To alleviate this problem, you can utilize code completion to see variables, keyword instructions, internal routines, and built-in functions as suggestions as you type. This incredibly powerful feature gives you the confidence to know that the symbol you type is the right one.
     Hover
    REXX can be a daunting language to learn. Oftentimes, all you need is a little information about what an element is, what it does, and how to use it, in order to understand it. With the addition of the hover feature, moving your mouse over any keyword instruction or built-in function will reveal these critical bits of information. This brings documentation directly into the editor, letting you work in one place without having to navigate elsewhere to find knowledge.
     Find references
    It's fairly common to want to find matching symbols in a REXX program. Without relying on CTRL+F to navigate comments and partial matches, you can quickly find references on a symbol to get a quick view of all occurrences. This handy feature makes searching for other symbols easier than ever, without having to lose your place in the file.
     Outline view
    A highly underrated feature, the outline view provides an overview of a program. We did the research, studying real REXX developers, to find out how to make this feature actually useful. What we found, it can be a powerful navigation tool for quickly going to internal routine definitions. Instead of crowding the outline view with every loop and switch statement, it was significantly more useful when user's could glance over and see what internal routines were defined, and if they so desired, navigate there with one click.
     More information
    For information about how to edit REXX programs, see the REXX editing tutorial.
    For information about how to utilize the different language features, see the Making REXX code changes page.
    ',16);function k(E,R){const o=a("ExternalLinkIcon");return n(),r(s,null,[c,u,t("p",null,[g,t("a",f,[m,i(o)]),p,t("a",y,[v,i(o)]),b,t("a",w,[_,i(o)]),x]),X],64)}var z=d(l,[["render",k]]);export{z as default};
+import{r as a,o as n,a as r,b as t,d as i,F as s,e,c as h}from"./app.daa93c96.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const l={},c=t("h1",{id:"a-modern-rexx-editor",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#a-modern-rexx-editor","aria-hidden":"true"},"#"),e(" A Modern REXX Editor")],-1),u=t("blockquote",null,[t("p",null,[e("by Bradley Knaysi"),t("br"),e(" 18 March 2021")])],-1),g=e("In the ongoing effort to bring z/OS\xAE application development into the rich ecosystem of modern code editors, the REXX programming language is the next major addition. Enabled in IBM Z\xAE Open Editor 1.2.0, "),f={href:"https://www.ibm.com/products/wazi-developer",target:"_blank",rel:"noopener noreferrer"},m=e("IBM\xAE Wazi Developer 1.2.0"),p=e(", and "),y={href:"https://www.ibm.com/products/developer-for-zos",target:"_blank",rel:"noopener noreferrer"},v=e("IBM Developer for z/OS 15.0.1"),b=e(", you will be able to benefit from our "),w={href:"https://langserver.org",target:"_blank",rel:"noopener noreferrer"},_=e("Language Server Protocol (LSP)"),x=e(" implementation for REXX. This brings a plethora of language features to the editor, which make REXX development easier and more accessible."),X=h('
    There are several language features now available to augment the REXX editing experience.
     Syntax highlighting
    Arguably the most important of the bunch, the colorization of code is hard to go without these days. It's quite surprising how far a little color variance can go to make distinguishing symbols easier. Bringing visual clarity to the syntactically wild REXX programming language, this feature undeniably improves the speed and precision of development.
     Syntax errors
    Out of the many mainframe programming languages, REXX is truly the free spirit. While many languages enforce spacing, tabbing, and case-sensitivity to parse elements of the code, REXX has little to no such constraints. The result is a wide variety of programming styles, which leave the developer wondering what valid syntax is and is not. This is where syntax errors shine, bringing visual clarity to common and sometimes frustratingly trivial mistakes.
     Code completion
    Writing code can be a tedious process, and one that requires incredible memory and focus. Some of the simplest mistakes are misspelled symbols, and given that REXX does not require variable declaration before definition, these spelling errors can go completely unnoticed until some strange runtime error occurs. To alleviate this problem, you can utilize code completion to see variables, keyword instructions, internal routines, and built-in functions as suggestions as you type. This incredibly powerful feature gives you the confidence to know that the symbol you type is the right one.
     Hover
    REXX can be a daunting language to learn. Oftentimes, all you need is a little information about what an element is, what it does, and how to use it, in order to understand it. With the addition of the hover feature, moving your mouse over any keyword instruction or built-in function will reveal these critical bits of information. This brings documentation directly into the editor, letting you work in one place without having to navigate elsewhere to find knowledge.
     Find references
    It's fairly common to want to find matching symbols in a REXX program. Without relying on CTRL+F to navigate comments and partial matches, you can quickly find references on a symbol to get a quick view of all occurrences. This handy feature makes searching for other symbols easier than ever, without having to lose your place in the file.
     Outline view
    A highly underrated feature, the outline view provides an overview of a program. We did the research, studying real REXX developers, to find out how to make this feature actually useful. What we found, it can be a powerful navigation tool for quickly going to internal routine definitions. Instead of crowding the outline view with every loop and switch statement, it was significantly more useful when user's could glance over and see what internal routines were defined, and if they so desired, navigate there with one click.
     More information
    For information about how to edit REXX programs, see the REXX editing tutorial.
    For information about how to utilize the different language features, see the Making REXX code changes page.
    ',16);function k(E,R){const o=a("ExternalLinkIcon");return n(),r(s,null,[c,u,t("p",null,[g,t("a",f,[m,i(o)]),p,t("a",y,[v,i(o)]),b,t("a",w,[_,i(o)]),x]),X],64)}var z=d(l,[["render",k]]);export{z as default};
diff --git a/assets/announcing-zos-resources-table.html.e2b19ed3.js b/assets/announcing-zos-resources-table.html.e2b19ed3.js
new file mode 100644
index 000000000..55a9dded6
--- /dev/null
+++ b/assets/announcing-zos-resources-table.html.e2b19ed3.js
@@ -0,0 +1 @@
+const e={key:"v-ed9f4f96",path:"/Blog/announcing-zos-resources-table.html",title:"Managing data sets, jobs, and UNIX files in Z Open Editor with the z/OS Resources Table",lang:"en-US",frontmatter:{},excerpt:"",headers:[{level:1,title:"Managing data sets, jobs, and UNIX files in Z Open Editor with the z/OS Resources Table",slug:"managing-data-sets-jobs-and-unix-files-in-z-open-editor-with-the-z-os-resources-table",children:[{level:2,title:"Getting Started",slug:"getting-started",children:[]},{level:2,title:"MVS, UNIX System Services, and JES views",slug:"mvs-unix-system-services-and-jes-views",children:[]},{level:2,title:"Learn More",slug:"learn-more",children:[]}]}],git:{updatedTime:1726615592e3,contributors:[{name:"Benjamin Santos",email:"Benjamin.Santos@ibm.com",commits:1}]},filePathRelative:"Blog/announcing-zos-resources-table.md"};export{e as data};
diff --git a/assets/announcing-zos-resources-table.html.e554df87.js b/assets/announcing-zos-resources-table.html.e554df87.js
new file mode 100644
index 000000000..7618b7ef4
--- /dev/null
+++ b/assets/announcing-zos-resources-table.html.e554df87.js
@@ -0,0 +1 @@
+import{r as s,o as i,a as n,b as e,d as a,F as r,e as t,c as l}from"./app.daa93c96.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";var d="/zopeneditor-about/assets/table-submit-members-as-jobs.987c9308.gif",h="/zopeneditor-about/assets/table-search-custcopy.aa1be4ee.gif",u="/zopeneditor-about/assets/table-submit-job-view-spool-files.da1dd3a5.gif",p="/zopeneditor-about/assets/table-uss-search-dbb-error.4f71e355.gif";const m={},b=e("h1",{id:"managing-data-sets-jobs-and-unix-files-in-z-open-editor-with-the-z-os-resources-table",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#managing-data-sets-jobs-and-unix-files-in-z-open-editor-with-the-z-os-resources-table","aria-hidden":"true"},"#"),t(" Managing data sets, jobs, and UNIX files in Z Open Editor with the z/OS Resources Table")],-1),g=e("blockquote",null,[e("p",null,[t("by Benjamin Santos"),e("br"),t(" 18 September 2024")])],-1),f=e("p",null,"Speaking from experience, mainframe development has a steep learning curve. Starting out, I had no experience with z/OS or with many of the programming languages that run on z/OS. On top of that, the tools used in mainframe development seemed daunting. I had grown accustomed to the modern IDEs I used while studying computer science in college and I felt hesitant to give them up to use traditional tools like ISPF instead.",-1),w=e("p",null,"IBM Z Open Editor is a great option for developers who prefer programming in a modern development environment (like me). It is a Visual Studio Code extension that combines the out-of-the-box capabilities of VS Code with language support for popular z/OS programming languages. From the beginning, Z Open Editor has used Zowe Explorer APIs for interacting with z/OS. Zowe Explorer relies on VS Code tree views for displaying and managing z/OS resources, which are very limited when it comes to sorting and filtering large amounts of resources. To address these shortcomings, we set out to provide a richer user experience that addresses many of our customer's requirements for dealing with large amounts of resources while still delivering a modern development experience. This was the design philosophy of the z/OS Resources Table.",-1),v=e("p",null,"The z/OS Resources Table is a tabular view that you can use to manage z/OS data sets, UNIX files, and jobs. It is intended to make the mainframe onboarding experience easier while still providing capabilities that are useful for more experienced developers.",-1),_=e("h2",{id:"getting-started",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#getting-started","aria-hidden":"true"},"#"),t(" Getting Started")],-1),y=t("To get started with the z/OS Resources Table, you need to "),S={href:"https://ibm.github.io/zopeneditor-about/Docs/interact_zos_zowe_explorer.html#setting-up-and-using-profiles-in-zowe-explorer",target:"_blank",rel:"noopener noreferrer"},x=t("create a Zowe Explorer profile"),O=t(". These profiles contain information necessary for Z Open Editor to connect to your z/OS host. If you have already created a Zowe Explorer profile, you can begin using the table without any additional setup."),z=l('
     MVS, UNIX System Services, and JES views
    When you open the table, you will be prompted to select a profile and a resource to interact with. You can select one of the three following resources:
    • MVS for managing data sets and data set members
    • USS for managing UNIX files
    • JES for managing jobs
    Each view in the table will provide you with a set of actions you can use. Some actions are available across all resources, such as the navigation actions in the table's top-left which work like a web browser's navigation toolbar. Other actions are only available for the specific resource you are accessing, some of which we demonstrate below.
     MVS
    The MVS view is used to manage data sets. The table supports many basic data set operations (create, delete, edit, etc.) and more complex operations for filtering and viewing data sets. Click on a partitioned data set to view its members and clicking a sequential data set or data set member will open it in the editor.
    Using the MVS view to submit data set members as jobs.Using the MVS view to submit data set members as jobs.
    As demonstrated in the GIF above, you can quickly edit and submit the table\u2019s active filter to control what resources are visible. You can also easily apply actions to multiple resources at once using batch actions. To sort the table, you can click on any column header to sort the table alphanumerically by that attribute, as you would in an Excel spreadsheet.
    In Z Open Editor v4.5.0, we released new MVS search capabilities for RSE API users. You can specify string content to search for across sequential data sets or data set members. You can also specify a data set or member name pattern to narrow down their search results further.
    Using the MVS Search and Filter menus to find COBOL programs that include the copybook CUSTCOPY.Using the MVS Search and Filter menus to find COBOL programs that include the copybook CUSTCOPY.
     JES
    The JES view is used for managing jobs and viewing job output. The table supports many basic job operations (canceling jobs, issuing stop or modify commands, viewing spool files, etc.) and provides capabilities for filtering jobs by name or status.
    Viewing spool files of an active job.Submitting a JCL job in the MVS view. Using the JES to view filter jobs and view spool files to see why the submitted job failed.
    Overflow menu actions, unlike batch actions, can be used to perform an action on a specific resource. The overflow menu can be opened by clicking on the three dots \u22EE on the right side of a table row as demonstrated in the GIF above.
     UNIX System Services
    The USS view is used for accessing and editing your host's UNIX files. You can navigate through the table by clicking on rows. Clicking a directory will display its contents and clicking a file will open it in a new editor, similar to how you would navigate directories using Windows File Explorer. The table supports basic UNIX operations (creating new files and directories, changing permissions, etc.) and more complex operations, including searching for files. With the new UNIX System Services search capabilities released in Z Open Editor v4.5.0, you can search for files by name and/or content.
    Locating a user build log file by searching for a DBB error code.Locating a user build log file by searching for a DBB error code.
     Learn More
    ',18),k=t("This blog was meant to give you a high-level overview of what is available in the z/OS Resources Table. Many available actions are not covered here and the table is receiving new features and capabilities with each release. Try it out, and if there is a missing feature that you would like to be added, you can create an enhancement request on the Z Open Editor "),I={href:"https://github.com/IBM/zopeneditor-about",target:"_blank",rel:"noopener noreferrer"},T=t("public repository"),E=t(". For more information on the z/OS Resources Table, see its "),j={href:"https://ibm.github.io/zopeneditor-about/Docs/advanced_resource_table.html#setting-up-profiles-for-the-z-os-resources-table",target:"_blank",rel:"noopener noreferrer"},V=t("documentation"),U=t(".");function M(C,B){const o=s("ExternalLinkIcon");return i(),n(r,null,[b,g,f,w,v,_,e("p",null,[y,e("a",S,[x,a(o)]),O]),z,e("p",null,[k,e("a",I,[T,a(o)]),E,e("a",j,[V,a(o)]),U])],64)}var F=c(m,[["render",M]]);export{F as default};
diff --git a/assets/app.f6cb3ed9.js b/assets/app.daa93c96.js
similarity index 82%
rename from assets/app.f6cb3ed9.js
rename to assets/app.daa93c96.js
index db6d8d5f0..917494ceb 100644
--- a/assets/app.f6cb3ed9.js
+++ b/assets/app.daa93c96.js
@@ -2,7 +2,7 @@ var bu=Object.defineProperty,Eu=Object.defineProperties;var Ou=Object.getOwnProp
   * vue-router v4.0.13
   * (c) 2022 Eduardo San Martin Morote
   * @license MIT
-  */const il=typeof Symbol=="function"&&typeof Symbol.toStringTag=="symbol",vn=e=>il?Symbol(e):"_vr_"+e,tp=vn("rvlm"),Ss=vn("rvd"),eo=vn("r"),Ti=vn("rl"),Ho=vn("rvl"),Gt=typeof window!="undefined";function np(e){return e.__esModule||il&&e[Symbol.toStringTag]==="Module"}const he=Object.assign;function ho(e,t){const n={};for(const r in t){const o=t[r];n[r]=Array.isArray(o)?o.map(e):e(o)}return n}const kn=()=>{},rp=/\/$/,op=e=>e.replace(rp,"");function _o(e,t,n="/"){let r,o={},i="",s="";const a=t.indexOf("?"),c=t.indexOf("#",a>-1?a:0);return a>-1&&(r=t.slice(0,a),i=t.slice(a+1,c>-1?c:t.length),o=e(i)),c>-1&&(r=r||t.slice(0,c),s=t.slice(c,t.length)),r=cp(r!=null?r:t,n),{fullPath:r+(i&&"?")+i+s,path:r,query:o,hash:s}}function ip(e,t){const n=t.query?e(t.query):"";return t.path+(n&&"?")+n+(t.hash||"")}function Ps(e,t){return!t||!e.toLowerCase().startsWith(t.toLowerCase())?e:e.slice(t.length)||"/"}function sp(e,t,n){const r=t.matched.length-1,o=n.matched.length-1;return r>-1&&r===o&&fn(t.matched[r],n.matched[o])&&sl(t.params,n.params)&&e(t.query)===e(n.query)&&t.hash===n.hash}function fn(e,t){return(e.aliasOf||e)===(t.aliasOf||t)}function sl(e,t){if(Object.keys(e).length!==Object.keys(t).length)return!1;for(const n in e)if(!ap(e[n],t[n]))return!1;return!0}function ap(e,t){return Array.isArray(e)?Ds(e,t):Array.isArray(t)?Ds(t,e):e===t}function Ds(e,t){return Array.isArray(t)?e.length===t.length&&e.every((n,r)=>n===t[r]):e.length===1&&e[0]===t}function cp(e,t){if(e.startsWith("/"))return e;if(!e)return t;const n=t.split("/"),r=e.split("/");let o=n.length-1,i,s;for(i=0;i({left:window.pageXOffset,top:window.pageYOffset});function pp(e){let t;if("el"in e){const n=e.el,r=typeof n=="string"&&n.startsWith("#"),o=typeof n=="string"?r?document.getElementById(n.slice(1)):document.querySelector(n):n;if(!o)return;t=dp(o,e)}else t=e;"scrollBehavior"in document.documentElement.style?window.scrollTo(t):window.scrollTo(t.left!=null?t.left:window.pageXOffset,t.top!=null?t.top:window.pageYOffset)}function Is(e,t){return(history.state?history.state.position-t:-1)+e}const Bo=new Map;function mp(e,t){Bo.set(e,t)}function hp(e){const t=Bo.get(e);return Bo.delete(e),t}let _p=()=>location.protocol+"//"+location.host;function al(e,t){const{pathname:n,search:r,hash:o}=t,i=e.indexOf("#");if(i>-1){let a=o.includes(e.slice(i))?e.slice(i).length:1,c=o.slice(a);return c[0]!=="/"&&(c="/"+c),Ps(c,"")}return Ps(n,e)+r+o}function vp(e,t,n,r){let o=[],i=[],s=null;const a=({state:f})=>{const h=al(e,location),m=n.value,v=t.value;let _=0;if(f){if(n.value=h,t.value=f,s&&s===m){s=null;return}_=v?f.position-v.position:0}else r(h);o.forEach(g=>{g(n.value,m,{delta:_,type:qn.pop,direction:_?_>0?Nn.forward:Nn.back:Nn.unknown})})};function c(){s=n.value}function l(f){o.push(f);const h=()=>{const m=o.indexOf(f);m>-1&&o.splice(m,1)};return i.push(h),h}function u(){const{history:f}=window;!f.state||f.replaceState(he({},f.state,{scroll:to()}),"")}function d(){for(const f of i)f();i=[],window.removeEventListener("popstate",a),window.removeEventListener("beforeunload",u)}return window.addEventListener("popstate",a),window.addEventListener("beforeunload",u),{pauseListeners:c,listen:l,destroy:d}}function As(e,t,n,r=!1,o=!1){return{back:e,current:t,forward:n,replaced:r,position:window.history.length,scroll:o?to():null}}function gp(e){const{history:t,location:n}=window,r={value:al(e,n)},o={value:t.state};o.value||i(r.value,{back:null,current:r.value,forward:null,position:t.length-1,replaced:!0,scroll:null},!0);function i(c,l,u){const d=e.indexOf("#"),f=d>-1?(n.host&&document.querySelector("base")?e:e.slice(d))+c:_p()+e+c;try{t[u?"replaceState":"pushState"](l,"",f),o.value=l}catch(h){console.error(h),n[u?"replace":"assign"](f)}}function s(c,l){const u=he({},t.state,As(o.value.back,c,o.value.forward,!0),l,{position:o.value.position});i(c,u,!0),r.value=c}function a(c,l){const u=he({},o.value,t.state,{forward:c,scroll:to()});i(u.current,u,!0);const d=he({},As(r.value,c,null),{position:u.position+1},l);i(c,d,!1),r.value=c}return{location:r,state:o,push:a,replace:s}}function yp(e){e=lp(e);const t=gp(e),n=vp(e,t.state,t.location,t.replace);function r(i,s=!0){s||n.pauseListeners(),history.go(i)}const o=he({location:"",base:e,go:r,createHref:fp.bind(null,e)},t,n);return Object.defineProperty(o,"location",{enumerable:!0,get:()=>t.location.value}),Object.defineProperty(o,"state",{enumerable:!0,get:()=>t.state.value}),o}function bp(e){return typeof e=="string"||e&&typeof e=="object"}function cl(e){return typeof e=="string"||typeof e=="symbol"}const ct={path:"/",name:void 0,params:{},query:{},hash:"",fullPath:"/",matched:[],meta:{},redirectedFrom:void 0},ll=vn("nf");var Cs;(function(e){e[e.aborted=4]="aborted",e[e.cancelled=8]="cancelled",e[e.duplicated=16]="duplicated"})(Cs||(Cs={}));function dn(e,t){return he(new Error,{type:e,[ll]:!0},t)}function yt(e,t){return e instanceof Error&&ll in e&&(t==null||!!(e.type&t))}const Ts="[^/]+?",Ep={sensitive:!1,strict:!1,start:!0,end:!0},Op=/[.+*?^${}()[\]/\\]/g;function wp(e,t){const n=he({},Ep,t),r=[];let o=n.start?"^":"";const i=[];for(const l of e){const u=l.length?[]:[90];n.strict&&!l.length&&(o+="/");for(let d=0;dt.length?t.length===1&&t[0]===40+40?1:-1:0}function Pp(e,t){let n=0;const r=e.score,o=t.score;for(;n1&&(c==="*"||c==="+")&&t(`A repeatable param (${l}) must be alone in its segment. eg: '/:ids+.`),i.push({type:1,value:l,regexp:u,repeatable:c==="*"||c==="+",optional:c==="*"||c==="?"})):t("Invalid state to consume buffer"),l="")}function f(){l+=c}for(;a{s(E)}:kn}function s(u){if(cl(u)){const d=r.get(u);d&&(r.delete(u),n.splice(n.indexOf(d),1),d.children.forEach(s),d.alias.forEach(s))}else{const d=n.indexOf(u);d>-1&&(n.splice(d,1),u.record.name&&r.delete(u.record.name),u.children.forEach(s),u.alias.forEach(s))}}function a(){return n}function c(u){let d=0;for(;d=0&&(u.record.path!==n[d].record.path||!ul(u,n[d]));)d++;n.splice(d,0,u),u.record.name&&!Rs(u)&&r.set(u.record.name,u)}function l(u,d){let f,h={},m,v;if("name"in u&&u.name){if(f=r.get(u.name),!f)throw dn(1,{location:u});v=f.record.name,h=he(Rp(d.params,f.keys.filter(E=>!E.optional).map(E=>E.name)),u.params),m=f.stringify(h)}else if("path"in u)m=u.path,f=n.find(E=>E.re.test(m)),f&&(h=f.parse(m),v=f.record.name);else{if(f=d.name?r.get(d.name):n.find(E=>E.re.test(d.path)),!f)throw dn(1,{location:u,currentLocation:d});v=f.record.name,h=he({},d.params,u.params),m=f.stringify(h)}const _=[];let g=f;for(;g;)_.unshift(g.record),g=g.parent;return{name:v,path:m,params:h,matched:_,meta:jp(_)}}return e.forEach(u=>i(u)),{addRoute:i,resolve:l,removeRoute:s,getRoutes:a,getRecordMatcher:o}}function Rp(e,t){const n={};for(const r of t)r in e&&(n[r]=e[r]);return n}function xp(e){return{path:e.path,redirect:e.redirect,name:e.name,meta:e.meta||{},aliasOf:void 0,beforeEnter:e.beforeEnter,props:Lp(e),children:e.children||[],instances:{},leaveGuards:new Set,updateGuards:new Set,enterCallbacks:{},components:"components"in e?e.components||{}:{default:e.component}}}function Lp(e){const t={},n=e.props||!1;if("component"in e)t.default=n;else for(const r in e.components)t[r]=typeof n=="boolean"?n:n[r];return t}function Rs(e){for(;e;){if(e.record.aliasOf)return!0;e=e.parent}return!1}function jp(e){return e.reduce((t,n)=>he(t,n.meta),{})}function xs(e,t){const n={};for(const r in e)n[r]=r in t?t[r]:e[r];return n}function ul(e,t){return t.children.some(n=>n===e||ul(e,n))}const fl=/#/g,kp=/&/g,Np=/\//g,Mp=/=/g,zp=/\?/g,dl=/\+/g,Vp=/%5B/g,Hp=/%5D/g,pl=/%5E/g,Bp=/%60/g,ml=/%7B/g,Fp=/%7C/g,hl=/%7D/g,Up=/%20/g;function Ri(e){return encodeURI(""+e).replace(Fp,"|").replace(Vp,"[").replace(Hp,"]")}function $p(e){return Ri(e).replace(ml,"{").replace(hl,"}").replace(pl,"^")}function Fo(e){return Ri(e).replace(dl,"%2B").replace(Up,"+").replace(fl,"%23").replace(kp,"%26").replace(Bp,"`").replace(ml,"{").replace(hl,"}").replace(pl,"^")}function qp(e){return Fo(e).replace(Mp,"%3D")}function Kp(e){return Ri(e).replace(fl,"%23").replace(zp,"%3F")}function Wp(e){return e==null?"":Kp(e).replace(Np,"%2F")}function Nr(e){try{return decodeURIComponent(""+e)}catch{}return""+e}function Zp(e){const t={};if(e===""||e==="?")return t;const r=(e[0]==="?"?e.slice(1):e).split("&");for(let o=0;oi&&Fo(i)):[r&&Fo(r)]).forEach(i=>{i!==void 0&&(t+=(t.length?"&":"")+n,i!=null&&(t+="="+i))})}return t}function Jp(e){const t={};for(const n in e){const r=e[n];r!==void 0&&(t[n]=Array.isArray(r)?r.map(o=>o==null?null:""+o):r==null?r:""+r)}return t}function En(){let e=[];function t(r){return e.push(r),()=>{const o=e.indexOf(r);o>-1&&e.splice(o,1)}}function n(){e=[]}return{add:t,list:()=>e,reset:n}}function Ot(e,t,n,r,o){const i=r&&(r.enterCallbacks[o]=r.enterCallbacks[o]||[]);return()=>new Promise((s,a)=>{const c=d=>{d===!1?a(dn(4,{from:n,to:t})):d instanceof Error?a(d):bp(d)?a(dn(2,{from:t,to:d})):(i&&r.enterCallbacks[o]===i&&typeof d=="function"&&i.push(d),s())},l=e.call(r&&r.instances[o],t,n,c);let u=Promise.resolve(l);e.length<3&&(u=u.then(c)),u.catch(d=>a(d))})}function vo(e,t,n,r){const o=[];for(const i of e)for(const s in i.components){let a=i.components[s];if(!(t!=="beforeRouteEnter"&&!i.instances[s]))if(Qp(a)){const l=(a.__vccOpts||a)[t];l&&o.push(Ot(l,n,r,i,s))}else{let c=a();o.push(()=>c.then(l=>{if(!l)return Promise.reject(new Error(`Couldn't resolve component "${s}" at "${i.path}"`));const u=np(l)?l.default:l;i.components[s]=u;const f=(u.__vccOpts||u)[t];return f&&Ot(f,n,r,i,s)()}))}}return o}function Qp(e){return typeof e=="object"||"displayName"in e||"props"in e||"__vccOpts"in e}function js(e){const t=Te(eo),n=Te(Ti),r=Oe(()=>t.resolve(Ht(e.to))),o=Oe(()=>{const{matched:c}=r.value,{length:l}=c,u=c[l-1],d=n.matched;if(!u||!d.length)return-1;const f=d.findIndex(fn.bind(null,u));if(f>-1)return f;const h=ks(c[l-2]);return l>1&&ks(u)===h&&d[d.length-1].path!==h?d.findIndex(fn.bind(null,c[l-2])):f}),i=Oe(()=>o.value>-1&&em(n.params,r.value.params)),s=Oe(()=>o.value>-1&&o.value===n.matched.length-1&&sl(n.params,r.value.params));function a(c={}){return Gp(c)?t[Ht(e.replace)?"replace":"push"](Ht(e.to)).catch(kn):Promise.resolve()}return{route:r,href:Oe(()=>r.value.href),isActive:i,isExactActive:s,navigate:a}}const Yp=Qe({name:"RouterLink",props:{to:{type:[String,Object],required:!0},replace:Boolean,activeClass:String,exactActiveClass:String,custom:Boolean,ariaCurrentValue:{type:String,default:"page"}},useLink:js,setup(e,{slots:t}){const n=_n(js(e)),{options:r}=Te(eo),o=Oe(()=>({[Ns(e.activeClass,r.linkActiveClass,"router-link-active")]:n.isActive,[Ns(e.exactActiveClass,r.linkExactActiveClass,"router-link-exact-active")]:n.isExactActive}));return()=>{const i=t.default&&t.default(n);return e.custom?i:be("a",{"aria-current":n.isExactActive?e.ariaCurrentValue:null,href:n.href,onClick:n.navigate,class:o.value},i)}}}),Xp=Yp;function Gp(e){if(!(e.metaKey||e.altKey||e.ctrlKey||e.shiftKey)&&!e.defaultPrevented&&!(e.button!==void 0&&e.button!==0)){if(e.currentTarget&&e.currentTarget.getAttribute){const t=e.currentTarget.getAttribute("target");if(/\b_blank\b/i.test(t))return}return e.preventDefault&&e.preventDefault(),!0}}function em(e,t){for(const n in t){const r=t[n],o=e[n];if(typeof r=="string"){if(r!==o)return!1}else if(!Array.isArray(o)||o.length!==r.length||r.some((i,s)=>i!==o[s]))return!1}return!0}function ks(e){return e?e.aliasOf?e.aliasOf.path:e.path:""}const Ns=(e,t,n)=>e!=null?e:t!=null?t:n,tm=Qe({name:"RouterView",inheritAttrs:!1,props:{name:{type:String,default:"default"},route:Object},setup(e,{attrs:t,slots:n}){const r=Te(Ho),o=Oe(()=>e.route||r.value),i=Te(Ss,0),s=Oe(()=>o.value.matched[i]);Bt(Ss,i+1),Bt(tp,s),Bt(Ho,o);const a=Ne();return et(()=>[a.value,s.value,e.name],([c,l,u],[d,f,h])=>{l&&(l.instances[u]=c,f&&f!==l&&c&&c===d&&(l.leaveGuards.size||(l.leaveGuards=f.leaveGuards),l.updateGuards.size||(l.updateGuards=f.updateGuards))),c&&l&&(!f||!fn(l,f)||!d)&&(l.enterCallbacks[u]||[]).forEach(m=>m(c))},{flush:"post"}),()=>{const c=o.value,l=s.value,u=l&&l.components[e.name],d=e.name;if(!u)return Ms(n.default,{Component:u,route:c});const f=l.props[e.name],h=f?f===!0?c.params:typeof f=="function"?f(c):f:null,v=be(u,he({},h,t,{onVnodeUnmounted:_=>{_.component.isUnmounted&&(l.instances[d]=null)},ref:a}));return Ms(n.default,{Component:v,route:c})||v}}});function Ms(e,t){if(!e)return null;const n=e(t);return n.length===1?n[0]:n}const _l=tm;function nm(e){const t=Tp(e.routes,e),n=e.parseQuery||Zp,r=e.stringifyQuery||Ls,o=e.history,i=En(),s=En(),a=En(),c=Ec(ct);let l=ct;Gt&&e.scrollBehavior&&"scrollRestoration"in history&&(history.scrollRestoration="manual");const u=ho.bind(null,R=>""+R),d=ho.bind(null,Wp),f=ho.bind(null,Nr);function h(R,U){let M,q;return cl(R)?(M=t.getRecordMatcher(R),q=U):q=R,t.addRoute(q,M)}function m(R){const U=t.getRecordMatcher(R);U&&t.removeRoute(U)}function v(){return t.getRoutes().map(R=>R.record)}function _(R){return!!t.getRecordMatcher(R)}function g(R,U){if(U=he({},U||c.value),typeof R=="string"){const te=_o(n,R,U.path),p=t.resolve({path:te.path},U),y=o.createHref(te.fullPath);return he(te,p,{params:f(p.params),hash:Nr(te.hash),redirectedFrom:void 0,href:y})}let M;if("path"in R)M=he({},R,{path:_o(n,R.path,U.path).path});else{const te=he({},R.params);for(const p in te)te[p]==null&&delete te[p];M=he({},R,{params:d(R.params)}),U.params=d(U.params)}const q=t.resolve(M,U),le=R.hash||"";q.params=u(f(q.params));const pe=ip(r,he({},R,{hash:$p(le),path:q.path})),oe=o.createHref(pe);return he({fullPath:pe,hash:le,query:r===Ls?Jp(R.query):R.query||{}},q,{redirectedFrom:void 0,href:oe})}function E(R){return typeof R=="string"?_o(n,R,c.value.path):he({},R)}function S(R,U){if(l!==R)return dn(8,{from:U,to:R})}function P(R){return A(R)}function T(R){return P(he(E(R),{replace:!0}))}function N(R){const U=R.matched[R.matched.length-1];if(U&&U.redirect){const{redirect:M}=U;let q=typeof M=="function"?M(R):M;return typeof q=="string"&&(q=q.includes("?")||q.includes("#")?q=E(q):{path:q},q.params={}),he({query:R.query,hash:R.hash,params:R.params},q)}}function A(R,U){const M=l=g(R),q=c.value,le=R.state,pe=R.force,oe=R.replace===!0,te=N(M);if(te)return A(he(E(te),{state:le,force:pe,replace:oe}),U||M);const p=M;p.redirectedFrom=U;let y;return!pe&&sp(r,q,M)&&(y=dn(16,{to:p,from:q}),Pe(q,q,!0,!1)),(y?Promise.resolve(y):$(p,q)).catch(w=>yt(w)?yt(w,2)?w:Ee(w):ne(w,p,q)).then(w=>{if(w){if(yt(w,2))return A(he(E(w.to),{state:le,force:pe,replace:oe}),U||p)}else w=K(p,q,!0,oe,le);return F(p,q,w),w})}function D(R,U){const M=S(R,U);return M?Promise.reject(M):Promise.resolve()}function $(R,U){let M;const[q,le,pe]=rm(R,U);M=vo(q.reverse(),"beforeRouteLeave",R,U);for(const te of q)te.leaveGuards.forEach(p=>{M.push(Ot(p,R,U))});const oe=D.bind(null,R,U);return M.push(oe),Wt(M).then(()=>{M=[];for(const te of i.list())M.push(Ot(te,R,U));return M.push(oe),Wt(M)}).then(()=>{M=vo(le,"beforeRouteUpdate",R,U);for(const te of le)te.updateGuards.forEach(p=>{M.push(Ot(p,R,U))});return M.push(oe),Wt(M)}).then(()=>{M=[];for(const te of R.matched)if(te.beforeEnter&&!U.matched.includes(te))if(Array.isArray(te.beforeEnter))for(const p of te.beforeEnter)M.push(Ot(p,R,U));else M.push(Ot(te.beforeEnter,R,U));return M.push(oe),Wt(M)}).then(()=>(R.matched.forEach(te=>te.enterCallbacks={}),M=vo(pe,"beforeRouteEnter",R,U),M.push(oe),Wt(M))).then(()=>{M=[];for(const te of s.list())M.push(Ot(te,R,U));return M.push(oe),Wt(M)}).catch(te=>yt(te,8)?te:Promise.reject(te))}function F(R,U,M){for(const q of a.list())q(R,U,M)}function K(R,U,M,q,le){const pe=S(R,U);if(pe)return pe;const oe=U===ct,te=Gt?history.state:{};M&&(q||oe?o.replace(R.fullPath,he({scroll:oe&&te&&te.scroll},le)):o.push(R.fullPath,le)),c.value=R,Pe(R,U,M,oe),Ee()}let I;function B(){I=o.listen((R,U,M)=>{const q=g(R),le=N(q);if(le){A(he(le,{replace:!0}),q).catch(kn);return}l=q;const pe=c.value;Gt&&mp(Is(pe.fullPath,M.delta),to()),$(q,pe).catch(oe=>yt(oe,12)?oe:yt(oe,2)?(A(oe.to,q).then(te=>{yt(te,20)&&!M.delta&&M.type===qn.pop&&o.go(-1,!1)}).catch(kn),Promise.reject()):(M.delta&&o.go(-M.delta,!1),ne(oe,q,pe))).then(oe=>{oe=oe||K(q,pe,!1),oe&&(M.delta?o.go(-M.delta,!1):M.type===qn.pop&&yt(oe,20)&&o.go(-1,!1)),F(q,pe,oe)}).catch(kn)})}let Y=En(),ae=En(),J;function ne(R,U,M){Ee(R);const q=ae.list();return q.length?q.forEach(le=>le(R,U,M)):console.error(R),Promise.reject(R)}function re(){return J&&c.value!==ct?Promise.resolve():new Promise((R,U)=>{Y.add([R,U])})}function Ee(R){return J||(J=!R,B(),Y.list().forEach(([U,M])=>R?M(R):U()),Y.reset()),R}function Pe(R,U,M,q){const{scrollBehavior:le}=e;if(!Gt||!le)return Promise.resolve();const pe=!M&&hp(Is(R.fullPath,0))||(q||!M)&&history.state&&history.state.scroll||null;return yi().then(()=>le(R,U,pe)).then(oe=>oe&&pp(oe)).catch(oe=>ne(oe,R,U))}const Ie=R=>o.go(R);let we;const Re=new Set;return{currentRoute:c,addRoute:h,removeRoute:m,hasRoute:_,getRoutes:v,resolve:g,options:e,push:P,replace:T,go:Ie,back:()=>Ie(-1),forward:()=>Ie(1),beforeEach:i.add,beforeResolve:s.add,afterEach:a.add,onError:ae.add,isReady:re,install(R){const U=this;R.component("RouterLink",Xp),R.component("RouterView",_l),R.config.globalProperties.$router=U,Object.defineProperty(R.config.globalProperties,"$route",{enumerable:!0,get:()=>Ht(c)}),Gt&&!we&&c.value===ct&&(we=!0,P(o.location).catch(le=>{}));const M={};for(const le in ct)M[le]=Oe(()=>c.value[le]);R.provide(eo,U),R.provide(Ti,_n(M)),R.provide(Ho,c);const q=R.unmount;Re.add(R),R.unmount=function(){Re.delete(R),Re.size<1&&(l=ct,I&&I(),c.value=ct,we=!1,J=!1),q()}}}}function Wt(e){return e.reduce((t,n)=>t.then(()=>n()),Promise.resolve())}function rm(e,t){const n=[],r=[],o=[],i=Math.max(t.matched.length,e.matched.length);for(let s=0;sfn(l,a))?r.push(a):n.push(a));const c=e.matched[s];c&&(t.matched.find(l=>fn(l,c))||o.push(c))}return[n,r,o]}function no(){return Te(eo)}function xi(){return Te(Ti)}const om=Qe({setup(e,t){const n=Ne(!1);return at(()=>{n.value=!0}),()=>{var r,o;return n.value?(o=(r=t.slots).default)===null||o===void 0?void 0:o.call(r):null}}}),im="modulepreload",zs={},sm="/zopeneditor-about/",O=function(t,n){return!n||n.length===0?t():Promise.all(n.map(r=>{if(r=`${sm}${r}`,r in zs)return;zs[r]=!0;const o=r.endsWith(".css"),i=o?'[rel="stylesheet"]':"";if(document.querySelector(`link[href="${r}"]${i}`))return;const s=document.createElement("link");if(s.rel=o?"stylesheet":im,o||(s.as="script",s.crossOrigin=""),s.href=r,document.head.appendChild(s),o)return new Promise((a,c)=>{s.addEventListener("load",a),s.addEventListener("error",()=>c(new Error(`Unable to preload CSS for ${r}`)))})})).then(()=>t())},vl={"v-8daa1a0e":V(()=>O(()=>import("./index.html.94ae7a7a.js"),["assets/index.html.94ae7a7a.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-a38aa0ce":V(()=>O(()=>import("./announcing-jcl.html.f0aaa040.js"),["assets/announcing-jcl.html.f0aaa040.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-fe48651a":V(()=>O(()=>import("./announcing-rexx.html.47753f24.js"),["assets/announcing-rexx.html.47753f24.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-8a4247d2":V(()=>O(()=>import("./code-snippets.html.2aa24f4f.js"),["assets/code-snippets.html.2aa24f4f.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-0baade54":V(()=>O(()=>import("./external-posts.html.910c17a1.js"),["assets/external-posts.html.910c17a1.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-1af1d74d":V(()=>O(()=>import("./hlasm-blog.html.d0be3dd3.js"),["assets/hlasm-blog.html.d0be3dd3.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-48cb972d":V(()=>O(()=>import("./ibm-wazi-development-client-introduction-blog.html.ae1364bf.js"),["assets/ibm-wazi-development-client-introduction-blog.html.ae1364bf.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-00ed1fd0":V(()=>O(()=>import("./in-the-cloud-with-che.html.44ae56df.js"),["assets/in-the-cloud-with-che.html.44ae56df.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-5a3683a7":V(()=>O(()=>import("./learning.html.b7c3f27c.js"),["assets/learning.html.b7c3f27c.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-4c46bc61":V(()=>O(()=>import("./new-content.html.78851d14.js"),["assets/new-content.html.78851d14.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-7e9516cc":V(()=>O(()=>import("./new-releases.html.5ed0be94.js"),["assets/new-releases.html.5ed0be94.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-a63a2e22":V(()=>O(()=>import("./ocp-ssl-cert.html.a6eed13d.js"),["assets/ocp-ssl-cert.html.a6eed13d.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-6fa9df51":V(()=>O(()=>import("./rse-march-120.html.620ce554.js"),["assets/rse-march-120.html.620ce554.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-0d011afc":V(()=>O(()=>import("./rse-march-beta.html.8a9f3fcc.js"),["assets/rse-march-beta.html.8a9f3fcc.js","assets/rse-help-web.56c77c6d.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-8483065a":V(()=>O(()=>import("./rse-october-110.html.c685cff7.js"),["assets/rse-october-110.html.c685cff7.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-5fac84d9":V(()=>O(()=>import("./userbuild-blog.html.b0a68b35.js"),["assets/userbuild-blog.html.b0a68b35.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-4b9415f0":V(()=>O(()=>import("./web-based-with-theia.html.e4c1a862.js"),["assets/web-based-with-theia.html.e4c1a862.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-68af98c9":V(()=>O(()=>import("./whats-new-120.html.a46d7959.js"),["assets/whats-new-120.html.a46d7959.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-0ffb677e":V(()=>O(()=>import("./advanced_activation.html.9df33d17.js"),["assets/advanced_activation.html.9df33d17.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-4066bbc6":V(()=>O(()=>import("./advanced_custom_macros.html.c5056122.js"),["assets/advanced_custom_macros.html.c5056122.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-20708584":V(()=>O(()=>import("./advanced_overview.html.691fbecc.js"),["assets/advanced_overview.html.691fbecc.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-a6691fb0":V(()=>O(()=>import("./advanced_preprocessor.html.a5970554.js"),["assets/advanced_preprocessor.html.a5970554.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-ae2b9dea":V(()=>O(()=>import("./advanced_problems_view.html.b377706d.js"),["assets/advanced_problems_view.html.b377706d.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-01e2125a":V(()=>O(()=>import("./advanced_resource_table.html.b412833a.js"),["assets/advanced_resource_table.html.b412833a.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-2a14c510":V(()=>O(()=>import("./connect_to_zos_with_zowe_cli_e2e.html.f95d0eea.js"),["assets/connect_to_zos_with_zowe_cli_e2e.html.f95d0eea.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-175f1e49":V(()=>O(()=>import("./connect_to_zos_with_zowe_explorer_e2e.html.2dc20d7e.js"),["assets/connect_to_zos_with_zowe_explorer_e2e.html.2dc20d7e.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-26fabd50":V(()=>O(()=>import("./creating_team_profiles.html.434e681f.js"),["assets/creating_team_profiles.html.434e681f.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-e76197e2":V(()=>O(()=>import("./customizing_the_outline_view.html.bee5c0a0.js"),["assets/customizing_the_outline_view.html.bee5c0a0.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-a2f185cc":V(()=>O(()=>import("./ebcdic_encoding.html.15b62784.js"),["assets/ebcdic_encoding.html.15b62784.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-391d428c":V(()=>O(()=>import("./editor_codechanges.html.6a1c862f.js"),["assets/editor_codechanges.html.6a1c862f.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-1c58a9fc":V(()=>O(()=>import("./editor_codechanges_hlasm.html.3ba7e8c6.js"),["assets/editor_codechanges_hlasm.html.3ba7e8c6.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-bb18cdb4":V(()=>O(()=>import("./editor_codechanges_jcl.html.c5fe40ac.js"),["assets/editor_codechanges_jcl.html.c5fe40ac.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-13c01586":V(()=>O(()=>import("./editor_codechanges_rexx.html.9f36838f.js"),["assets/editor_codechanges_rexx.html.9f36838f.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-10307d7a":V(()=>O(()=>import("./editor_search.html.8465aab1.js"),["assets/editor_search.html.8465aab1.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-9b8c1724":V(()=>O(()=>import("./getting_started.html.5530d381.js"),["assets/getting_started.html.5530d381.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-afd18aa6":V(()=>O(()=>import("./git_integration.html.b7128f18.js"),["assets/git_integration.html.b7128f18.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-1251ae42":V(()=>O(()=>import("./interact_common_properties_cli.html.1a7bccf8.js"),["assets/interact_common_properties_cli.html.1a7bccf8.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-f89d1930":V(()=>O(()=>import("./interact_zos_cli.html.f30565d5.js"),["assets/interact_zos_cli.html.f30565d5.js","assets/rse-help-web.56c77c6d.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-30184cb1":V(()=>O(()=>import("./interact_zos_overview.html.f369dafa.js"),["assets/interact_zos_overview.html.f369dafa.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-3c830012":V(()=>O(()=>import("./interact_zos_zopeneditor.html.b1952528.js"),["assets/interact_zos_zopeneditor.html.b1952528.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-60c4e326":V(()=>O(()=>import("./interact_zos_zowe_explorer.html.ea329571.js"),["assets/interact_zos_zowe_explorer.html.ea329571.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-22d1c484":V(()=>O(()=>import("./introduction.html.1ba0e870.js"),["assets/introduction.html.1ba0e870.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-823d11d2":V(()=>O(()=>import("./knownissues.html.913faaf1.js"),["assets/knownissues.html.913faaf1.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-93378d76":V(()=>O(()=>import("./language_references.html.4d36ef0c.js"),["assets/language_references.html.4d36ef0c.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-ab2cfe42":V(()=>O(()=>import("./locating_local_client_logs.html.e1a883b2.js"),["assets/locating_local_client_logs.html.e1a883b2.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-f90f4ac6":V(()=>O(()=>import("./migrating_profiles.html.dda1c8c1.js"),["assets/migrating_profiles.html.dda1c8c1.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-065bea79":V(()=>O(()=>import("./notices.html.e6f11260.js"),["assets/notices.html.e6f11260.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-e100f1ca":V(()=>O(()=>import("./other_extensions.html.c1f9d46d.js"),["assets/other_extensions.html.c1f9d46d.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-9629110c":V(()=>O(()=>import("./privacypolicy.html.0065f368.js"),["assets/privacypolicy.html.0065f368.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-4aeeafba":V(()=>O(()=>import("./rse_cli_command.html.1e4311e9.js"),["assets/rse_cli_command.html.1e4311e9.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-52b0a105":V(()=>O(()=>import("./rse_tutorial.html.8e8f3dc0.js"),["assets/rse_tutorial.html.8e8f3dc0.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-9498fc72":V(()=>O(()=>import("./samplefiles.html.3e8b1a83.js"),["assets/samplefiles.html.3e8b1a83.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-9dcc581e":V(()=>O(()=>import("./setting_compiler_options.html.79ec5ce5.js"),["assets/setting_compiler_options.html.79ec5ce5.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-522078b2":V(()=>O(()=>import("./setting_disableproblems.html.951054d5.js"),["assets/setting_disableproblems.html.951054d5.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-348a2d3e":V(()=>O(()=>import("./setting_fileassociations.html.c145a7e0.js"),["assets/setting_fileassociations.html.c145a7e0.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-3f4d9f11":V(()=>O(()=>import("./setting_maximum_line_length.html.4cc75ee6.js"),["assets/setting_maximum_line_length.html.4cc75ee6.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-3ae1cfcb":V(()=>O(()=>import("./setting_preferences.html.52fc78b8.js"),["assets/setting_preferences.html.52fc78b8.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-b824cc8e":V(()=>O(()=>import("./setting_propertygroup.html.f62b7e80.js"),["assets/setting_propertygroup.html.f62b7e80.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-0dd03d73":V(()=>O(()=>import("./setting_tabstops.html.5806099a.js"),["assets/setting_tabstops.html.5806099a.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-2a63b1ab":V(()=>O(()=>import("./setting_unreachablecodewarnings.html.d2b1a2f9.js"),["assets/setting_unreachablecodewarnings.html.d2b1a2f9.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-8fabeeca":V(()=>O(()=>import("./settings.html.0cfb3304.js"),["assets/settings.html.0cfb3304.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-14aa9ebc":V(()=>O(()=>import("./setup_integration.html.b808ca31.js"),["assets/setup_integration.html.b808ca31.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-0791b3a2":V(()=>O(()=>import("./sharing_team_configuration_files.html.d1ee5fad.js"),["assets/sharing_team_configuration_files.html.d1ee5fad.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-d9943bba":V(()=>O(()=>import("./sharingfiles.html.2003b9d7.js"),["assets/sharingfiles.html.2003b9d7.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-6676f350":V(()=>O(()=>import("./shortcut.html.d940e3c7.js"),["assets/shortcut.html.d940e3c7.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-45d644b0":V(()=>O(()=>import("./snippets.html.a3e40b12.js"),["assets/snippets.html.a3e40b12.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-7982067c":V(()=>O(()=>import("./trademarks.html.1200a3b5.js"),["assets/trademarks.html.1200a3b5.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-492a8ebf":V(()=>O(()=>import("./tutorial_assembler.html.93a6a76a.js"),["assets/tutorial_assembler.html.93a6a76a.js","assets/createbranch.c5e1488b.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-035874ac":V(()=>O(()=>import("./tutorial_cobol.html.121d9584.js"),["assets/tutorial_cobol.html.121d9584.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-70c1277a":V(()=>O(()=>import("./tutorial_overview.html.f84e0fa1.js"),["assets/tutorial_overview.html.f84e0fa1.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-6ab451c0":V(()=>O(()=>import("./tutorial_rexx.html.94025c05.js"),["assets/tutorial_rexx.html.94025c05.js","assets/createbranch.c5e1488b.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-64756ec4":V(()=>O(()=>import("./uninstalling.html.a1faa6c5.js"),["assets/uninstalling.html.a1faa6c5.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-99d69e34":V(()=>O(()=>import("./userinterface.html.9d008bb5.js"),["assets/userinterface.html.9d008bb5.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-da074572":V(()=>O(()=>import("./using_code_snippets.html.424b0956.js"),["assets/using_code_snippets.html.424b0956.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-37f5df26":V(()=>O(()=>import("./whatsnew.html.e3e857ff.js"),["assets/whatsnew.html.e3e857ff.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-43ab0a57":V(()=>O(()=>import("./zapp.html.e15d90b5.js"),["assets/zapp.html.e15d90b5.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-4d589ea8":V(()=>O(()=>import("./zcodeformatting.html.398b7274.js"),["assets/zcodeformatting.html.398b7274.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-2d85c4b3":V(()=>O(()=>import("./zopeneditor_v3.html.ee59cc1d.js"),["assets/zopeneditor_v3.html.ee59cc1d.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-41c85ba6":V(()=>O(()=>import("./zowe_advanced_connection_scenarious.html.083a0c71.js"),["assets/zowe_advanced_connection_scenarious.html.083a0c71.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-4b11bcde":V(()=>O(()=>import("./zowe_explorer_v2.html.13e8d264.js"),["assets/zowe_explorer_v2.html.13e8d264.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-60b2a3bf":V(()=>O(()=>import("./zowe_submitjcl.html.3d487255.js"),["assets/zowe_submitjcl.html.3d487255.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-3706649a":V(()=>O(()=>import("./404.html.74b16cef.js"),["assets/404.html.74b16cef.js","assets/plugin-vue_export-helper.21dcd24c.js"]))},am={"v-8daa1a0e":()=>O(()=>import("./index.html.3ac4de35.js"),[]).then(({data:e})=>e),"v-a38aa0ce":()=>O(()=>import("./announcing-jcl.html.18c0ed35.js"),[]).then(({data:e})=>e),"v-fe48651a":()=>O(()=>import("./announcing-rexx.html.7f07edc2.js"),[]).then(({data:e})=>e),"v-8a4247d2":()=>O(()=>import("./code-snippets.html.b35039d1.js"),[]).then(({data:e})=>e),"v-0baade54":()=>O(()=>import("./external-posts.html.e8cf9791.js"),[]).then(({data:e})=>e),"v-1af1d74d":()=>O(()=>import("./hlasm-blog.html.2b659071.js"),[]).then(({data:e})=>e),"v-48cb972d":()=>O(()=>import("./ibm-wazi-development-client-introduction-blog.html.cfab7f14.js"),[]).then(({data:e})=>e),"v-00ed1fd0":()=>O(()=>import("./in-the-cloud-with-che.html.4286b16d.js"),[]).then(({data:e})=>e),"v-5a3683a7":()=>O(()=>import("./learning.html.986f01ac.js"),[]).then(({data:e})=>e),"v-4c46bc61":()=>O(()=>import("./new-content.html.3dffb483.js"),[]).then(({data:e})=>e),"v-7e9516cc":()=>O(()=>import("./new-releases.html.943c2e0c.js"),[]).then(({data:e})=>e),"v-a63a2e22":()=>O(()=>import("./ocp-ssl-cert.html.72eec9e1.js"),[]).then(({data:e})=>e),"v-6fa9df51":()=>O(()=>import("./rse-march-120.html.5426b66f.js"),[]).then(({data:e})=>e),"v-0d011afc":()=>O(()=>import("./rse-march-beta.html.4845308d.js"),[]).then(({data:e})=>e),"v-8483065a":()=>O(()=>import("./rse-october-110.html.548b92bb.js"),[]).then(({data:e})=>e),"v-5fac84d9":()=>O(()=>import("./userbuild-blog.html.2f09f33e.js"),[]).then(({data:e})=>e),"v-4b9415f0":()=>O(()=>import("./web-based-with-theia.html.b5ed8430.js"),[]).then(({data:e})=>e),"v-68af98c9":()=>O(()=>import("./whats-new-120.html.6568abcb.js"),[]).then(({data:e})=>e),"v-0ffb677e":()=>O(()=>import("./advanced_activation.html.a5808ffb.js"),[]).then(({data:e})=>e),"v-4066bbc6":()=>O(()=>import("./advanced_custom_macros.html.7f52e802.js"),[]).then(({data:e})=>e),"v-20708584":()=>O(()=>import("./advanced_overview.html.8507f257.js"),[]).then(({data:e})=>e),"v-a6691fb0":()=>O(()=>import("./advanced_preprocessor.html.a9f9190c.js"),[]).then(({data:e})=>e),"v-ae2b9dea":()=>O(()=>import("./advanced_problems_view.html.ccbd31e1.js"),[]).then(({data:e})=>e),"v-01e2125a":()=>O(()=>import("./advanced_resource_table.html.2552a95f.js"),[]).then(({data:e})=>e),"v-2a14c510":()=>O(()=>import("./connect_to_zos_with_zowe_cli_e2e.html.af5cc4c5.js"),[]).then(({data:e})=>e),"v-175f1e49":()=>O(()=>import("./connect_to_zos_with_zowe_explorer_e2e.html.178ef3f5.js"),[]).then(({data:e})=>e),"v-26fabd50":()=>O(()=>import("./creating_team_profiles.html.41cf0f73.js"),[]).then(({data:e})=>e),"v-e76197e2":()=>O(()=>import("./customizing_the_outline_view.html.f3e642b6.js"),[]).then(({data:e})=>e),"v-a2f185cc":()=>O(()=>import("./ebcdic_encoding.html.62a5eda6.js"),[]).then(({data:e})=>e),"v-391d428c":()=>O(()=>import("./editor_codechanges.html.2d2fe0de.js"),[]).then(({data:e})=>e),"v-1c58a9fc":()=>O(()=>import("./editor_codechanges_hlasm.html.d3e47b90.js"),[]).then(({data:e})=>e),"v-bb18cdb4":()=>O(()=>import("./editor_codechanges_jcl.html.80cbce3f.js"),[]).then(({data:e})=>e),"v-13c01586":()=>O(()=>import("./editor_codechanges_rexx.html.69d65a68.js"),[]).then(({data:e})=>e),"v-10307d7a":()=>O(()=>import("./editor_search.html.da2e21be.js"),[]).then(({data:e})=>e),"v-9b8c1724":()=>O(()=>import("./getting_started.html.42bb6dc4.js"),[]).then(({data:e})=>e),"v-afd18aa6":()=>O(()=>import("./git_integration.html.c9f41b18.js"),[]).then(({data:e})=>e),"v-1251ae42":()=>O(()=>import("./interact_common_properties_cli.html.4060a20b.js"),[]).then(({data:e})=>e),"v-f89d1930":()=>O(()=>import("./interact_zos_cli.html.91a26918.js"),[]).then(({data:e})=>e),"v-30184cb1":()=>O(()=>import("./interact_zos_overview.html.7ee849b5.js"),[]).then(({data:e})=>e),"v-3c830012":()=>O(()=>import("./interact_zos_zopeneditor.html.ec31013f.js"),[]).then(({data:e})=>e),"v-60c4e326":()=>O(()=>import("./interact_zos_zowe_explorer.html.2dc036e5.js"),[]).then(({data:e})=>e),"v-22d1c484":()=>O(()=>import("./introduction.html.89fa2796.js"),[]).then(({data:e})=>e),"v-823d11d2":()=>O(()=>import("./knownissues.html.8474e59f.js"),[]).then(({data:e})=>e),"v-93378d76":()=>O(()=>import("./language_references.html.848e8284.js"),[]).then(({data:e})=>e),"v-ab2cfe42":()=>O(()=>import("./locating_local_client_logs.html.1c2cb5dd.js"),[]).then(({data:e})=>e),"v-f90f4ac6":()=>O(()=>import("./migrating_profiles.html.da583f28.js"),[]).then(({data:e})=>e),"v-065bea79":()=>O(()=>import("./notices.html.f0768ed8.js"),[]).then(({data:e})=>e),"v-e100f1ca":()=>O(()=>import("./other_extensions.html.5f52b5c4.js"),[]).then(({data:e})=>e),"v-9629110c":()=>O(()=>import("./privacypolicy.html.058a21d1.js"),[]).then(({data:e})=>e),"v-4aeeafba":()=>O(()=>import("./rse_cli_command.html.cbf3613e.js"),[]).then(({data:e})=>e),"v-52b0a105":()=>O(()=>import("./rse_tutorial.html.cf75455e.js"),[]).then(({data:e})=>e),"v-9498fc72":()=>O(()=>import("./samplefiles.html.286dd5d0.js"),[]).then(({data:e})=>e),"v-9dcc581e":()=>O(()=>import("./setting_compiler_options.html.7fc5b9a1.js"),[]).then(({data:e})=>e),"v-522078b2":()=>O(()=>import("./setting_disableproblems.html.bc75fa0e.js"),[]).then(({data:e})=>e),"v-348a2d3e":()=>O(()=>import("./setting_fileassociations.html.8d6872d5.js"),[]).then(({data:e})=>e),"v-3f4d9f11":()=>O(()=>import("./setting_maximum_line_length.html.3383ac30.js"),[]).then(({data:e})=>e),"v-3ae1cfcb":()=>O(()=>import("./setting_preferences.html.c9708706.js"),[]).then(({data:e})=>e),"v-b824cc8e":()=>O(()=>import("./setting_propertygroup.html.b218f9a1.js"),[]).then(({data:e})=>e),"v-0dd03d73":()=>O(()=>import("./setting_tabstops.html.662c9129.js"),[]).then(({data:e})=>e),"v-2a63b1ab":()=>O(()=>import("./setting_unreachablecodewarnings.html.cf69f816.js"),[]).then(({data:e})=>e),"v-8fabeeca":()=>O(()=>import("./settings.html.3f7de99b.js"),[]).then(({data:e})=>e),"v-14aa9ebc":()=>O(()=>import("./setup_integration.html.b8af3e48.js"),[]).then(({data:e})=>e),"v-0791b3a2":()=>O(()=>import("./sharing_team_configuration_files.html.40fb76ab.js"),[]).then(({data:e})=>e),"v-d9943bba":()=>O(()=>import("./sharingfiles.html.3ad6f744.js"),[]).then(({data:e})=>e),"v-6676f350":()=>O(()=>import("./shortcut.html.d694f8cd.js"),[]).then(({data:e})=>e),"v-45d644b0":()=>O(()=>import("./snippets.html.18b69914.js"),[]).then(({data:e})=>e),"v-7982067c":()=>O(()=>import("./trademarks.html.ea86a4af.js"),[]).then(({data:e})=>e),"v-492a8ebf":()=>O(()=>import("./tutorial_assembler.html.4c0ed640.js"),[]).then(({data:e})=>e),"v-035874ac":()=>O(()=>import("./tutorial_cobol.html.faab05d7.js"),[]).then(({data:e})=>e),"v-70c1277a":()=>O(()=>import("./tutorial_overview.html.7f140b81.js"),[]).then(({data:e})=>e),"v-6ab451c0":()=>O(()=>import("./tutorial_rexx.html.c3ddb259.js"),[]).then(({data:e})=>e),"v-64756ec4":()=>O(()=>import("./uninstalling.html.1a506d72.js"),[]).then(({data:e})=>e),"v-99d69e34":()=>O(()=>import("./userinterface.html.08973d08.js"),[]).then(({data:e})=>e),"v-da074572":()=>O(()=>import("./using_code_snippets.html.3eaca8dd.js"),[]).then(({data:e})=>e),"v-37f5df26":()=>O(()=>import("./whatsnew.html.320005e4.js"),[]).then(({data:e})=>e),"v-43ab0a57":()=>O(()=>import("./zapp.html.dd3eb1c6.js"),[]).then(({data:e})=>e),"v-4d589ea8":()=>O(()=>import("./zcodeformatting.html.f9619a10.js"),[]).then(({data:e})=>e),"v-2d85c4b3":()=>O(()=>import("./zopeneditor_v3.html.36632b1e.js"),[]).then(({data:e})=>e),"v-41c85ba6":()=>O(()=>import("./zowe_advanced_connection_scenarious.html.4bee0dd3.js"),[]).then(({data:e})=>e),"v-4b11bcde":()=>O(()=>import("./zowe_explorer_v2.html.02aff825.js"),[]).then(({data:e})=>e),"v-60b2a3bf":()=>O(()=>import("./zowe_submitjcl.html.14c9f11b.js"),[]).then(({data:e})=>e),"v-3706649a":()=>O(()=>import("./404.html.10ca2252.js"),[]).then(({data:e})=>e)},gl=Ne(am),yl=hi({key:"",path:"",title:"",lang:"",frontmatter:{},excerpt:"",headers:[]}),ut=Ne(yl),tr=()=>ut;Hi.webpackHot&&(__VUE_HMR_RUNTIME__.updatePageData=e=>{gl.value[e.key]=()=>Promise.resolve(e),e.key===ut.value.key&&(ut.value=e)});const bl=Symbol(""),cm=()=>{const e=Te(bl);if(!e)throw new Error("usePageFrontmatter() is called without provider.");return e},El=Symbol(""),lm=()=>{const e=Te(El);if(!e)throw new Error("usePageHead() is called without provider.");return e},um=Symbol(""),Ol=Symbol(""),wl=()=>{const e=Te(Ol);if(!e)throw new Error("usePageLang() is called without provider.");return e},Li=Symbol(""),Sl=()=>{const e=Te(Li);if(!e)throw new Error("useRouteLocale() is called without provider.");return e},fm={base:"/zopeneditor-about/",lang:"en-US",title:"IBM Z\xAE Open Editor",description:"IBM enterprise language support for COBOL, PL/I, HLASM, and REXX in VS Code\u201D",head:[["meta",{charset:"utf-8"}],["meta",{name:"viewport",content:"width=device-width,initial-scale=1"}],["link",{rel:"icon",type:"image/png",sizes:"32x32",href:"/zopeneditor-about/assets/img/favicon-32x32.png"}],["meta",{name:"keywords",content:"IBM, COBOL, PL/I, PLI, PL1, JCL, jesjcl, jesmsglg, jesysmsg, IDE, LSP, language-server, keybindings, snippet, z/OS, zOS, Z Software, Zowe, Mainframe, Visual Studio Code, VS Code, VSCode, Git, Open Source, Development, Extension, Theia, Che, REXX, Zowe Explorer, Zowe CLI, RSE API, Remote System Explorer,  HLASM, ASM, IBM Z"}],["meta",{name:"google-site-verification",content:"Ona_2rMxidYRtJWAlzNHkfKFB3f9DkKKNTJCYLZVei8"}],["link",{rel:"stylesheet",href:"https://fonts.googleapis.com/css2?family=IBM+Plex+Sans:wght@200;300;400;500;600;700&display=swap"}],["link",{rel:"stylesheet",href:"https://cdn.jsdelivr.net/npm/@docsearch/css@alpha"}],["link",{rel:"stylesheet",href:"/zopeneditor-about/assets/css/foundation.css"}],["link",{rel:"stylesheet",href:"/zopeneditor-about/assets/css/animate.css"}],["link",{rel:"stylesheet",href:"/zopeneditor-about/assets/css/custom.css"}],["script",{src:"https://code.jquery.com/jquery-3.5.1.min.js"},`
+  */const il=typeof Symbol=="function"&&typeof Symbol.toStringTag=="symbol",vn=e=>il?Symbol(e):"_vr_"+e,tp=vn("rvlm"),Ss=vn("rvd"),eo=vn("r"),Ti=vn("rl"),Ho=vn("rvl"),Gt=typeof window!="undefined";function np(e){return e.__esModule||il&&e[Symbol.toStringTag]==="Module"}const he=Object.assign;function ho(e,t){const n={};for(const r in t){const o=t[r];n[r]=Array.isArray(o)?o.map(e):e(o)}return n}const kn=()=>{},rp=/\/$/,op=e=>e.replace(rp,"");function _o(e,t,n="/"){let r,o={},i="",s="";const a=t.indexOf("?"),c=t.indexOf("#",a>-1?a:0);return a>-1&&(r=t.slice(0,a),i=t.slice(a+1,c>-1?c:t.length),o=e(i)),c>-1&&(r=r||t.slice(0,c),s=t.slice(c,t.length)),r=cp(r!=null?r:t,n),{fullPath:r+(i&&"?")+i+s,path:r,query:o,hash:s}}function ip(e,t){const n=t.query?e(t.query):"";return t.path+(n&&"?")+n+(t.hash||"")}function Ps(e,t){return!t||!e.toLowerCase().startsWith(t.toLowerCase())?e:e.slice(t.length)||"/"}function sp(e,t,n){const r=t.matched.length-1,o=n.matched.length-1;return r>-1&&r===o&&fn(t.matched[r],n.matched[o])&&sl(t.params,n.params)&&e(t.query)===e(n.query)&&t.hash===n.hash}function fn(e,t){return(e.aliasOf||e)===(t.aliasOf||t)}function sl(e,t){if(Object.keys(e).length!==Object.keys(t).length)return!1;for(const n in e)if(!ap(e[n],t[n]))return!1;return!0}function ap(e,t){return Array.isArray(e)?Ds(e,t):Array.isArray(t)?Ds(t,e):e===t}function Ds(e,t){return Array.isArray(t)?e.length===t.length&&e.every((n,r)=>n===t[r]):e.length===1&&e[0]===t}function cp(e,t){if(e.startsWith("/"))return e;if(!e)return t;const n=t.split("/"),r=e.split("/");let o=n.length-1,i,s;for(i=0;i({left:window.pageXOffset,top:window.pageYOffset});function pp(e){let t;if("el"in e){const n=e.el,r=typeof n=="string"&&n.startsWith("#"),o=typeof n=="string"?r?document.getElementById(n.slice(1)):document.querySelector(n):n;if(!o)return;t=dp(o,e)}else t=e;"scrollBehavior"in document.documentElement.style?window.scrollTo(t):window.scrollTo(t.left!=null?t.left:window.pageXOffset,t.top!=null?t.top:window.pageYOffset)}function Is(e,t){return(history.state?history.state.position-t:-1)+e}const Bo=new Map;function mp(e,t){Bo.set(e,t)}function hp(e){const t=Bo.get(e);return Bo.delete(e),t}let _p=()=>location.protocol+"//"+location.host;function al(e,t){const{pathname:n,search:r,hash:o}=t,i=e.indexOf("#");if(i>-1){let a=o.includes(e.slice(i))?e.slice(i).length:1,c=o.slice(a);return c[0]!=="/"&&(c="/"+c),Ps(c,"")}return Ps(n,e)+r+o}function vp(e,t,n,r){let o=[],i=[],s=null;const a=({state:f})=>{const h=al(e,location),m=n.value,v=t.value;let _=0;if(f){if(n.value=h,t.value=f,s&&s===m){s=null;return}_=v?f.position-v.position:0}else r(h);o.forEach(g=>{g(n.value,m,{delta:_,type:qn.pop,direction:_?_>0?Nn.forward:Nn.back:Nn.unknown})})};function c(){s=n.value}function l(f){o.push(f);const h=()=>{const m=o.indexOf(f);m>-1&&o.splice(m,1)};return i.push(h),h}function u(){const{history:f}=window;!f.state||f.replaceState(he({},f.state,{scroll:to()}),"")}function d(){for(const f of i)f();i=[],window.removeEventListener("popstate",a),window.removeEventListener("beforeunload",u)}return window.addEventListener("popstate",a),window.addEventListener("beforeunload",u),{pauseListeners:c,listen:l,destroy:d}}function As(e,t,n,r=!1,o=!1){return{back:e,current:t,forward:n,replaced:r,position:window.history.length,scroll:o?to():null}}function gp(e){const{history:t,location:n}=window,r={value:al(e,n)},o={value:t.state};o.value||i(r.value,{back:null,current:r.value,forward:null,position:t.length-1,replaced:!0,scroll:null},!0);function i(c,l,u){const d=e.indexOf("#"),f=d>-1?(n.host&&document.querySelector("base")?e:e.slice(d))+c:_p()+e+c;try{t[u?"replaceState":"pushState"](l,"",f),o.value=l}catch(h){console.error(h),n[u?"replace":"assign"](f)}}function s(c,l){const u=he({},t.state,As(o.value.back,c,o.value.forward,!0),l,{position:o.value.position});i(c,u,!0),r.value=c}function a(c,l){const u=he({},o.value,t.state,{forward:c,scroll:to()});i(u.current,u,!0);const d=he({},As(r.value,c,null),{position:u.position+1},l);i(c,d,!1),r.value=c}return{location:r,state:o,push:a,replace:s}}function yp(e){e=lp(e);const t=gp(e),n=vp(e,t.state,t.location,t.replace);function r(i,s=!0){s||n.pauseListeners(),history.go(i)}const o=he({location:"",base:e,go:r,createHref:fp.bind(null,e)},t,n);return Object.defineProperty(o,"location",{enumerable:!0,get:()=>t.location.value}),Object.defineProperty(o,"state",{enumerable:!0,get:()=>t.state.value}),o}function bp(e){return typeof e=="string"||e&&typeof e=="object"}function cl(e){return typeof e=="string"||typeof e=="symbol"}const ct={path:"/",name:void 0,params:{},query:{},hash:"",fullPath:"/",matched:[],meta:{},redirectedFrom:void 0},ll=vn("nf");var Cs;(function(e){e[e.aborted=4]="aborted",e[e.cancelled=8]="cancelled",e[e.duplicated=16]="duplicated"})(Cs||(Cs={}));function dn(e,t){return he(new Error,{type:e,[ll]:!0},t)}function yt(e,t){return e instanceof Error&&ll in e&&(t==null||!!(e.type&t))}const Ts="[^/]+?",Ep={sensitive:!1,strict:!1,start:!0,end:!0},Op=/[.+*?^${}()[\]/\\]/g;function wp(e,t){const n=he({},Ep,t),r=[];let o=n.start?"^":"";const i=[];for(const l of e){const u=l.length?[]:[90];n.strict&&!l.length&&(o+="/");for(let d=0;dt.length?t.length===1&&t[0]===40+40?1:-1:0}function Pp(e,t){let n=0;const r=e.score,o=t.score;for(;n1&&(c==="*"||c==="+")&&t(`A repeatable param (${l}) must be alone in its segment. eg: '/:ids+.`),i.push({type:1,value:l,regexp:u,repeatable:c==="*"||c==="+",optional:c==="*"||c==="?"})):t("Invalid state to consume buffer"),l="")}function f(){l+=c}for(;a{s(E)}:kn}function s(u){if(cl(u)){const d=r.get(u);d&&(r.delete(u),n.splice(n.indexOf(d),1),d.children.forEach(s),d.alias.forEach(s))}else{const d=n.indexOf(u);d>-1&&(n.splice(d,1),u.record.name&&r.delete(u.record.name),u.children.forEach(s),u.alias.forEach(s))}}function a(){return n}function c(u){let d=0;for(;d=0&&(u.record.path!==n[d].record.path||!ul(u,n[d]));)d++;n.splice(d,0,u),u.record.name&&!Rs(u)&&r.set(u.record.name,u)}function l(u,d){let f,h={},m,v;if("name"in u&&u.name){if(f=r.get(u.name),!f)throw dn(1,{location:u});v=f.record.name,h=he(Rp(d.params,f.keys.filter(E=>!E.optional).map(E=>E.name)),u.params),m=f.stringify(h)}else if("path"in u)m=u.path,f=n.find(E=>E.re.test(m)),f&&(h=f.parse(m),v=f.record.name);else{if(f=d.name?r.get(d.name):n.find(E=>E.re.test(d.path)),!f)throw dn(1,{location:u,currentLocation:d});v=f.record.name,h=he({},d.params,u.params),m=f.stringify(h)}const _=[];let g=f;for(;g;)_.unshift(g.record),g=g.parent;return{name:v,path:m,params:h,matched:_,meta:jp(_)}}return e.forEach(u=>i(u)),{addRoute:i,resolve:l,removeRoute:s,getRoutes:a,getRecordMatcher:o}}function Rp(e,t){const n={};for(const r of t)r in e&&(n[r]=e[r]);return n}function xp(e){return{path:e.path,redirect:e.redirect,name:e.name,meta:e.meta||{},aliasOf:void 0,beforeEnter:e.beforeEnter,props:Lp(e),children:e.children||[],instances:{},leaveGuards:new Set,updateGuards:new Set,enterCallbacks:{},components:"components"in e?e.components||{}:{default:e.component}}}function Lp(e){const t={},n=e.props||!1;if("component"in e)t.default=n;else for(const r in e.components)t[r]=typeof n=="boolean"?n:n[r];return t}function Rs(e){for(;e;){if(e.record.aliasOf)return!0;e=e.parent}return!1}function jp(e){return e.reduce((t,n)=>he(t,n.meta),{})}function xs(e,t){const n={};for(const r in e)n[r]=r in t?t[r]:e[r];return n}function ul(e,t){return t.children.some(n=>n===e||ul(e,n))}const fl=/#/g,kp=/&/g,Np=/\//g,Mp=/=/g,zp=/\?/g,dl=/\+/g,Vp=/%5B/g,Hp=/%5D/g,pl=/%5E/g,Bp=/%60/g,ml=/%7B/g,Fp=/%7C/g,hl=/%7D/g,Up=/%20/g;function Ri(e){return encodeURI(""+e).replace(Fp,"|").replace(Vp,"[").replace(Hp,"]")}function $p(e){return Ri(e).replace(ml,"{").replace(hl,"}").replace(pl,"^")}function Fo(e){return Ri(e).replace(dl,"%2B").replace(Up,"+").replace(fl,"%23").replace(kp,"%26").replace(Bp,"`").replace(ml,"{").replace(hl,"}").replace(pl,"^")}function qp(e){return Fo(e).replace(Mp,"%3D")}function Kp(e){return Ri(e).replace(fl,"%23").replace(zp,"%3F")}function Wp(e){return e==null?"":Kp(e).replace(Np,"%2F")}function Nr(e){try{return decodeURIComponent(""+e)}catch{}return""+e}function Zp(e){const t={};if(e===""||e==="?")return t;const r=(e[0]==="?"?e.slice(1):e).split("&");for(let o=0;oi&&Fo(i)):[r&&Fo(r)]).forEach(i=>{i!==void 0&&(t+=(t.length?"&":"")+n,i!=null&&(t+="="+i))})}return t}function Jp(e){const t={};for(const n in e){const r=e[n];r!==void 0&&(t[n]=Array.isArray(r)?r.map(o=>o==null?null:""+o):r==null?r:""+r)}return t}function En(){let e=[];function t(r){return e.push(r),()=>{const o=e.indexOf(r);o>-1&&e.splice(o,1)}}function n(){e=[]}return{add:t,list:()=>e,reset:n}}function Ot(e,t,n,r,o){const i=r&&(r.enterCallbacks[o]=r.enterCallbacks[o]||[]);return()=>new Promise((s,a)=>{const c=d=>{d===!1?a(dn(4,{from:n,to:t})):d instanceof Error?a(d):bp(d)?a(dn(2,{from:t,to:d})):(i&&r.enterCallbacks[o]===i&&typeof d=="function"&&i.push(d),s())},l=e.call(r&&r.instances[o],t,n,c);let u=Promise.resolve(l);e.length<3&&(u=u.then(c)),u.catch(d=>a(d))})}function vo(e,t,n,r){const o=[];for(const i of e)for(const s in i.components){let a=i.components[s];if(!(t!=="beforeRouteEnter"&&!i.instances[s]))if(Qp(a)){const l=(a.__vccOpts||a)[t];l&&o.push(Ot(l,n,r,i,s))}else{let c=a();o.push(()=>c.then(l=>{if(!l)return Promise.reject(new Error(`Couldn't resolve component "${s}" at "${i.path}"`));const u=np(l)?l.default:l;i.components[s]=u;const f=(u.__vccOpts||u)[t];return f&&Ot(f,n,r,i,s)()}))}}return o}function Qp(e){return typeof e=="object"||"displayName"in e||"props"in e||"__vccOpts"in e}function js(e){const t=Te(eo),n=Te(Ti),r=Oe(()=>t.resolve(Ht(e.to))),o=Oe(()=>{const{matched:c}=r.value,{length:l}=c,u=c[l-1],d=n.matched;if(!u||!d.length)return-1;const f=d.findIndex(fn.bind(null,u));if(f>-1)return f;const h=ks(c[l-2]);return l>1&&ks(u)===h&&d[d.length-1].path!==h?d.findIndex(fn.bind(null,c[l-2])):f}),i=Oe(()=>o.value>-1&&em(n.params,r.value.params)),s=Oe(()=>o.value>-1&&o.value===n.matched.length-1&&sl(n.params,r.value.params));function a(c={}){return Gp(c)?t[Ht(e.replace)?"replace":"push"](Ht(e.to)).catch(kn):Promise.resolve()}return{route:r,href:Oe(()=>r.value.href),isActive:i,isExactActive:s,navigate:a}}const Yp=Qe({name:"RouterLink",props:{to:{type:[String,Object],required:!0},replace:Boolean,activeClass:String,exactActiveClass:String,custom:Boolean,ariaCurrentValue:{type:String,default:"page"}},useLink:js,setup(e,{slots:t}){const n=_n(js(e)),{options:r}=Te(eo),o=Oe(()=>({[Ns(e.activeClass,r.linkActiveClass,"router-link-active")]:n.isActive,[Ns(e.exactActiveClass,r.linkExactActiveClass,"router-link-exact-active")]:n.isExactActive}));return()=>{const i=t.default&&t.default(n);return e.custom?i:be("a",{"aria-current":n.isExactActive?e.ariaCurrentValue:null,href:n.href,onClick:n.navigate,class:o.value},i)}}}),Xp=Yp;function Gp(e){if(!(e.metaKey||e.altKey||e.ctrlKey||e.shiftKey)&&!e.defaultPrevented&&!(e.button!==void 0&&e.button!==0)){if(e.currentTarget&&e.currentTarget.getAttribute){const t=e.currentTarget.getAttribute("target");if(/\b_blank\b/i.test(t))return}return e.preventDefault&&e.preventDefault(),!0}}function em(e,t){for(const n in t){const r=t[n],o=e[n];if(typeof r=="string"){if(r!==o)return!1}else if(!Array.isArray(o)||o.length!==r.length||r.some((i,s)=>i!==o[s]))return!1}return!0}function ks(e){return e?e.aliasOf?e.aliasOf.path:e.path:""}const Ns=(e,t,n)=>e!=null?e:t!=null?t:n,tm=Qe({name:"RouterView",inheritAttrs:!1,props:{name:{type:String,default:"default"},route:Object},setup(e,{attrs:t,slots:n}){const r=Te(Ho),o=Oe(()=>e.route||r.value),i=Te(Ss,0),s=Oe(()=>o.value.matched[i]);Bt(Ss,i+1),Bt(tp,s),Bt(Ho,o);const a=Ne();return et(()=>[a.value,s.value,e.name],([c,l,u],[d,f,h])=>{l&&(l.instances[u]=c,f&&f!==l&&c&&c===d&&(l.leaveGuards.size||(l.leaveGuards=f.leaveGuards),l.updateGuards.size||(l.updateGuards=f.updateGuards))),c&&l&&(!f||!fn(l,f)||!d)&&(l.enterCallbacks[u]||[]).forEach(m=>m(c))},{flush:"post"}),()=>{const c=o.value,l=s.value,u=l&&l.components[e.name],d=e.name;if(!u)return Ms(n.default,{Component:u,route:c});const f=l.props[e.name],h=f?f===!0?c.params:typeof f=="function"?f(c):f:null,v=be(u,he({},h,t,{onVnodeUnmounted:_=>{_.component.isUnmounted&&(l.instances[d]=null)},ref:a}));return Ms(n.default,{Component:v,route:c})||v}}});function Ms(e,t){if(!e)return null;const n=e(t);return n.length===1?n[0]:n}const _l=tm;function nm(e){const t=Tp(e.routes,e),n=e.parseQuery||Zp,r=e.stringifyQuery||Ls,o=e.history,i=En(),s=En(),a=En(),c=Ec(ct);let l=ct;Gt&&e.scrollBehavior&&"scrollRestoration"in history&&(history.scrollRestoration="manual");const u=ho.bind(null,R=>""+R),d=ho.bind(null,Wp),f=ho.bind(null,Nr);function h(R,U){let M,q;return cl(R)?(M=t.getRecordMatcher(R),q=U):q=R,t.addRoute(q,M)}function m(R){const U=t.getRecordMatcher(R);U&&t.removeRoute(U)}function v(){return t.getRoutes().map(R=>R.record)}function _(R){return!!t.getRecordMatcher(R)}function g(R,U){if(U=he({},U||c.value),typeof R=="string"){const te=_o(n,R,U.path),p=t.resolve({path:te.path},U),y=o.createHref(te.fullPath);return he(te,p,{params:f(p.params),hash:Nr(te.hash),redirectedFrom:void 0,href:y})}let M;if("path"in R)M=he({},R,{path:_o(n,R.path,U.path).path});else{const te=he({},R.params);for(const p in te)te[p]==null&&delete te[p];M=he({},R,{params:d(R.params)}),U.params=d(U.params)}const q=t.resolve(M,U),le=R.hash||"";q.params=u(f(q.params));const pe=ip(r,he({},R,{hash:$p(le),path:q.path})),oe=o.createHref(pe);return he({fullPath:pe,hash:le,query:r===Ls?Jp(R.query):R.query||{}},q,{redirectedFrom:void 0,href:oe})}function E(R){return typeof R=="string"?_o(n,R,c.value.path):he({},R)}function S(R,U){if(l!==R)return dn(8,{from:U,to:R})}function P(R){return A(R)}function T(R){return P(he(E(R),{replace:!0}))}function N(R){const U=R.matched[R.matched.length-1];if(U&&U.redirect){const{redirect:M}=U;let q=typeof M=="function"?M(R):M;return typeof q=="string"&&(q=q.includes("?")||q.includes("#")?q=E(q):{path:q},q.params={}),he({query:R.query,hash:R.hash,params:R.params},q)}}function A(R,U){const M=l=g(R),q=c.value,le=R.state,pe=R.force,oe=R.replace===!0,te=N(M);if(te)return A(he(E(te),{state:le,force:pe,replace:oe}),U||M);const p=M;p.redirectedFrom=U;let y;return!pe&&sp(r,q,M)&&(y=dn(16,{to:p,from:q}),Pe(q,q,!0,!1)),(y?Promise.resolve(y):$(p,q)).catch(w=>yt(w)?yt(w,2)?w:Ee(w):ne(w,p,q)).then(w=>{if(w){if(yt(w,2))return A(he(E(w.to),{state:le,force:pe,replace:oe}),U||p)}else w=K(p,q,!0,oe,le);return F(p,q,w),w})}function D(R,U){const M=S(R,U);return M?Promise.reject(M):Promise.resolve()}function $(R,U){let M;const[q,le,pe]=rm(R,U);M=vo(q.reverse(),"beforeRouteLeave",R,U);for(const te of q)te.leaveGuards.forEach(p=>{M.push(Ot(p,R,U))});const oe=D.bind(null,R,U);return M.push(oe),Wt(M).then(()=>{M=[];for(const te of i.list())M.push(Ot(te,R,U));return M.push(oe),Wt(M)}).then(()=>{M=vo(le,"beforeRouteUpdate",R,U);for(const te of le)te.updateGuards.forEach(p=>{M.push(Ot(p,R,U))});return M.push(oe),Wt(M)}).then(()=>{M=[];for(const te of R.matched)if(te.beforeEnter&&!U.matched.includes(te))if(Array.isArray(te.beforeEnter))for(const p of te.beforeEnter)M.push(Ot(p,R,U));else M.push(Ot(te.beforeEnter,R,U));return M.push(oe),Wt(M)}).then(()=>(R.matched.forEach(te=>te.enterCallbacks={}),M=vo(pe,"beforeRouteEnter",R,U),M.push(oe),Wt(M))).then(()=>{M=[];for(const te of s.list())M.push(Ot(te,R,U));return M.push(oe),Wt(M)}).catch(te=>yt(te,8)?te:Promise.reject(te))}function F(R,U,M){for(const q of a.list())q(R,U,M)}function K(R,U,M,q,le){const pe=S(R,U);if(pe)return pe;const oe=U===ct,te=Gt?history.state:{};M&&(q||oe?o.replace(R.fullPath,he({scroll:oe&&te&&te.scroll},le)):o.push(R.fullPath,le)),c.value=R,Pe(R,U,M,oe),Ee()}let I;function B(){I=o.listen((R,U,M)=>{const q=g(R),le=N(q);if(le){A(he(le,{replace:!0}),q).catch(kn);return}l=q;const pe=c.value;Gt&&mp(Is(pe.fullPath,M.delta),to()),$(q,pe).catch(oe=>yt(oe,12)?oe:yt(oe,2)?(A(oe.to,q).then(te=>{yt(te,20)&&!M.delta&&M.type===qn.pop&&o.go(-1,!1)}).catch(kn),Promise.reject()):(M.delta&&o.go(-M.delta,!1),ne(oe,q,pe))).then(oe=>{oe=oe||K(q,pe,!1),oe&&(M.delta?o.go(-M.delta,!1):M.type===qn.pop&&yt(oe,20)&&o.go(-1,!1)),F(q,pe,oe)}).catch(kn)})}let Y=En(),ae=En(),J;function ne(R,U,M){Ee(R);const q=ae.list();return q.length?q.forEach(le=>le(R,U,M)):console.error(R),Promise.reject(R)}function re(){return J&&c.value!==ct?Promise.resolve():new Promise((R,U)=>{Y.add([R,U])})}function Ee(R){return J||(J=!R,B(),Y.list().forEach(([U,M])=>R?M(R):U()),Y.reset()),R}function Pe(R,U,M,q){const{scrollBehavior:le}=e;if(!Gt||!le)return Promise.resolve();const pe=!M&&hp(Is(R.fullPath,0))||(q||!M)&&history.state&&history.state.scroll||null;return yi().then(()=>le(R,U,pe)).then(oe=>oe&&pp(oe)).catch(oe=>ne(oe,R,U))}const Ie=R=>o.go(R);let we;const Re=new Set;return{currentRoute:c,addRoute:h,removeRoute:m,hasRoute:_,getRoutes:v,resolve:g,options:e,push:P,replace:T,go:Ie,back:()=>Ie(-1),forward:()=>Ie(1),beforeEach:i.add,beforeResolve:s.add,afterEach:a.add,onError:ae.add,isReady:re,install(R){const U=this;R.component("RouterLink",Xp),R.component("RouterView",_l),R.config.globalProperties.$router=U,Object.defineProperty(R.config.globalProperties,"$route",{enumerable:!0,get:()=>Ht(c)}),Gt&&!we&&c.value===ct&&(we=!0,P(o.location).catch(le=>{}));const M={};for(const le in ct)M[le]=Oe(()=>c.value[le]);R.provide(eo,U),R.provide(Ti,_n(M)),R.provide(Ho,c);const q=R.unmount;Re.add(R),R.unmount=function(){Re.delete(R),Re.size<1&&(l=ct,I&&I(),c.value=ct,we=!1,J=!1),q()}}}}function Wt(e){return e.reduce((t,n)=>t.then(()=>n()),Promise.resolve())}function rm(e,t){const n=[],r=[],o=[],i=Math.max(t.matched.length,e.matched.length);for(let s=0;sfn(l,a))?r.push(a):n.push(a));const c=e.matched[s];c&&(t.matched.find(l=>fn(l,c))||o.push(c))}return[n,r,o]}function no(){return Te(eo)}function xi(){return Te(Ti)}const om=Qe({setup(e,t){const n=Ne(!1);return at(()=>{n.value=!0}),()=>{var r,o;return n.value?(o=(r=t.slots).default)===null||o===void 0?void 0:o.call(r):null}}}),im="modulepreload",zs={},sm="/zopeneditor-about/",O=function(t,n){return!n||n.length===0?t():Promise.all(n.map(r=>{if(r=`${sm}${r}`,r in zs)return;zs[r]=!0;const o=r.endsWith(".css"),i=o?'[rel="stylesheet"]':"";if(document.querySelector(`link[href="${r}"]${i}`))return;const s=document.createElement("link");if(s.rel=o?"stylesheet":im,o||(s.as="script",s.crossOrigin=""),s.href=r,document.head.appendChild(s),o)return new Promise((a,c)=>{s.addEventListener("load",a),s.addEventListener("error",()=>c(new Error(`Unable to preload CSS for ${r}`)))})})).then(()=>t())},vl={"v-8daa1a0e":V(()=>O(()=>import("./index.html.f7b6c1dc.js"),["assets/index.html.f7b6c1dc.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-a38aa0ce":V(()=>O(()=>import("./announcing-jcl.html.2d4b575d.js"),["assets/announcing-jcl.html.2d4b575d.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-fe48651a":V(()=>O(()=>import("./announcing-rexx.html.bcf7782b.js"),["assets/announcing-rexx.html.bcf7782b.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-ed9f4f96":V(()=>O(()=>import("./announcing-zos-resources-table.html.e554df87.js"),["assets/announcing-zos-resources-table.html.e554df87.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-8a4247d2":V(()=>O(()=>import("./code-snippets.html.773a7c6a.js"),["assets/code-snippets.html.773a7c6a.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-0baade54":V(()=>O(()=>import("./external-posts.html.fa85d592.js"),["assets/external-posts.html.fa85d592.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-1af1d74d":V(()=>O(()=>import("./hlasm-blog.html.4a6e4d92.js"),["assets/hlasm-blog.html.4a6e4d92.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-48cb972d":V(()=>O(()=>import("./ibm-wazi-development-client-introduction-blog.html.71dcd92b.js"),["assets/ibm-wazi-development-client-introduction-blog.html.71dcd92b.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-00ed1fd0":V(()=>O(()=>import("./in-the-cloud-with-che.html.37d18f64.js"),["assets/in-the-cloud-with-che.html.37d18f64.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-5a3683a7":V(()=>O(()=>import("./learning.html.1c26815c.js"),["assets/learning.html.1c26815c.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-4c46bc61":V(()=>O(()=>import("./new-content.html.14310bc6.js"),["assets/new-content.html.14310bc6.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-7e9516cc":V(()=>O(()=>import("./new-releases.html.e21383d2.js"),["assets/new-releases.html.e21383d2.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-a63a2e22":V(()=>O(()=>import("./ocp-ssl-cert.html.9c458041.js"),["assets/ocp-ssl-cert.html.9c458041.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-6fa9df51":V(()=>O(()=>import("./rse-march-120.html.d44ba81e.js"),["assets/rse-march-120.html.d44ba81e.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-0d011afc":V(()=>O(()=>import("./rse-march-beta.html.26161367.js"),["assets/rse-march-beta.html.26161367.js","assets/rse-help-web.56c77c6d.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-8483065a":V(()=>O(()=>import("./rse-october-110.html.eb06bfc1.js"),["assets/rse-october-110.html.eb06bfc1.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-5fac84d9":V(()=>O(()=>import("./userbuild-blog.html.23b2eadd.js"),["assets/userbuild-blog.html.23b2eadd.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-4b9415f0":V(()=>O(()=>import("./web-based-with-theia.html.80701632.js"),["assets/web-based-with-theia.html.80701632.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-68af98c9":V(()=>O(()=>import("./whats-new-120.html.6fee15fa.js"),["assets/whats-new-120.html.6fee15fa.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-0ffb677e":V(()=>O(()=>import("./advanced_activation.html.b14ae790.js"),["assets/advanced_activation.html.b14ae790.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-4066bbc6":V(()=>O(()=>import("./advanced_custom_macros.html.14afaf7a.js"),["assets/advanced_custom_macros.html.14afaf7a.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-20708584":V(()=>O(()=>import("./advanced_overview.html.e5020286.js"),["assets/advanced_overview.html.e5020286.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-a6691fb0":V(()=>O(()=>import("./advanced_preprocessor.html.d7c4d6f2.js"),["assets/advanced_preprocessor.html.d7c4d6f2.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-ae2b9dea":V(()=>O(()=>import("./advanced_problems_view.html.090028b4.js"),["assets/advanced_problems_view.html.090028b4.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-01e2125a":V(()=>O(()=>import("./advanced_resource_table.html.cac10c8e.js"),["assets/advanced_resource_table.html.cac10c8e.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-2a14c510":V(()=>O(()=>import("./connect_to_zos_with_zowe_cli_e2e.html.a8e70c31.js"),["assets/connect_to_zos_with_zowe_cli_e2e.html.a8e70c31.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-175f1e49":V(()=>O(()=>import("./connect_to_zos_with_zowe_explorer_e2e.html.8894ef57.js"),["assets/connect_to_zos_with_zowe_explorer_e2e.html.8894ef57.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-26fabd50":V(()=>O(()=>import("./creating_team_profiles.html.1f9ba16f.js"),["assets/creating_team_profiles.html.1f9ba16f.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-e76197e2":V(()=>O(()=>import("./customizing_the_outline_view.html.12952224.js"),["assets/customizing_the_outline_view.html.12952224.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-a2f185cc":V(()=>O(()=>import("./ebcdic_encoding.html.bde230cb.js"),["assets/ebcdic_encoding.html.bde230cb.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-391d428c":V(()=>O(()=>import("./editor_codechanges.html.ff6ce7c8.js"),["assets/editor_codechanges.html.ff6ce7c8.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-1c58a9fc":V(()=>O(()=>import("./editor_codechanges_hlasm.html.0d36a43a.js"),["assets/editor_codechanges_hlasm.html.0d36a43a.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-bb18cdb4":V(()=>O(()=>import("./editor_codechanges_jcl.html.3b1e2582.js"),["assets/editor_codechanges_jcl.html.3b1e2582.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-13c01586":V(()=>O(()=>import("./editor_codechanges_rexx.html.375e0978.js"),["assets/editor_codechanges_rexx.html.375e0978.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-10307d7a":V(()=>O(()=>import("./editor_search.html.4bb9cfa8.js"),["assets/editor_search.html.4bb9cfa8.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-9b8c1724":V(()=>O(()=>import("./getting_started.html.ffa40eee.js"),["assets/getting_started.html.ffa40eee.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-afd18aa6":V(()=>O(()=>import("./git_integration.html.7a2bdb12.js"),["assets/git_integration.html.7a2bdb12.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-1251ae42":V(()=>O(()=>import("./interact_common_properties_cli.html.ebe56c0e.js"),["assets/interact_common_properties_cli.html.ebe56c0e.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-f89d1930":V(()=>O(()=>import("./interact_zos_cli.html.afca56ce.js"),["assets/interact_zos_cli.html.afca56ce.js","assets/rse-help-web.56c77c6d.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-30184cb1":V(()=>O(()=>import("./interact_zos_overview.html.286dac9b.js"),["assets/interact_zos_overview.html.286dac9b.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-3c830012":V(()=>O(()=>import("./interact_zos_zopeneditor.html.31626061.js"),["assets/interact_zos_zopeneditor.html.31626061.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-60c4e326":V(()=>O(()=>import("./interact_zos_zowe_explorer.html.d2bc6dd2.js"),["assets/interact_zos_zowe_explorer.html.d2bc6dd2.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-22d1c484":V(()=>O(()=>import("./introduction.html.a978a099.js"),["assets/introduction.html.a978a099.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-823d11d2":V(()=>O(()=>import("./knownissues.html.648ac969.js"),["assets/knownissues.html.648ac969.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-93378d76":V(()=>O(()=>import("./language_references.html.04872726.js"),["assets/language_references.html.04872726.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-ab2cfe42":V(()=>O(()=>import("./locating_local_client_logs.html.f487be4e.js"),["assets/locating_local_client_logs.html.f487be4e.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-f90f4ac6":V(()=>O(()=>import("./migrating_profiles.html.c03adcd7.js"),["assets/migrating_profiles.html.c03adcd7.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-065bea79":V(()=>O(()=>import("./notices.html.8c7eb4f7.js"),["assets/notices.html.8c7eb4f7.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-e100f1ca":V(()=>O(()=>import("./other_extensions.html.3b14f121.js"),["assets/other_extensions.html.3b14f121.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-9629110c":V(()=>O(()=>import("./privacypolicy.html.a8014a83.js"),["assets/privacypolicy.html.a8014a83.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-4aeeafba":V(()=>O(()=>import("./rse_cli_command.html.da0a133a.js"),["assets/rse_cli_command.html.da0a133a.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-52b0a105":V(()=>O(()=>import("./rse_tutorial.html.2bcfb7dd.js"),["assets/rse_tutorial.html.2bcfb7dd.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-9498fc72":V(()=>O(()=>import("./samplefiles.html.0f622c14.js"),["assets/samplefiles.html.0f622c14.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-9dcc581e":V(()=>O(()=>import("./setting_compiler_options.html.c0208ac5.js"),["assets/setting_compiler_options.html.c0208ac5.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-522078b2":V(()=>O(()=>import("./setting_disableproblems.html.1122c286.js"),["assets/setting_disableproblems.html.1122c286.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-348a2d3e":V(()=>O(()=>import("./setting_fileassociations.html.3121d46c.js"),["assets/setting_fileassociations.html.3121d46c.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-3f4d9f11":V(()=>O(()=>import("./setting_maximum_line_length.html.5947d19c.js"),["assets/setting_maximum_line_length.html.5947d19c.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-3ae1cfcb":V(()=>O(()=>import("./setting_preferences.html.c7693b1e.js"),["assets/setting_preferences.html.c7693b1e.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-b824cc8e":V(()=>O(()=>import("./setting_propertygroup.html.34e159f2.js"),["assets/setting_propertygroup.html.34e159f2.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-0dd03d73":V(()=>O(()=>import("./setting_tabstops.html.48761a85.js"),["assets/setting_tabstops.html.48761a85.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-2a63b1ab":V(()=>O(()=>import("./setting_unreachablecodewarnings.html.b7f525ec.js"),["assets/setting_unreachablecodewarnings.html.b7f525ec.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-8fabeeca":V(()=>O(()=>import("./settings.html.a9d7c76c.js"),["assets/settings.html.a9d7c76c.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-14aa9ebc":V(()=>O(()=>import("./setup_integration.html.5653902f.js"),["assets/setup_integration.html.5653902f.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-0791b3a2":V(()=>O(()=>import("./sharing_team_configuration_files.html.7464eef7.js"),["assets/sharing_team_configuration_files.html.7464eef7.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-d9943bba":V(()=>O(()=>import("./sharingfiles.html.b4e52542.js"),["assets/sharingfiles.html.b4e52542.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-6676f350":V(()=>O(()=>import("./shortcut.html.6659b779.js"),["assets/shortcut.html.6659b779.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-45d644b0":V(()=>O(()=>import("./snippets.html.b17f2d5b.js"),["assets/snippets.html.b17f2d5b.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-7982067c":V(()=>O(()=>import("./trademarks.html.008e3827.js"),["assets/trademarks.html.008e3827.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-492a8ebf":V(()=>O(()=>import("./tutorial_assembler.html.7dcb0297.js"),["assets/tutorial_assembler.html.7dcb0297.js","assets/createbranch.c5e1488b.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-035874ac":V(()=>O(()=>import("./tutorial_cobol.html.975f720a.js"),["assets/tutorial_cobol.html.975f720a.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-70c1277a":V(()=>O(()=>import("./tutorial_overview.html.5a8c9afe.js"),["assets/tutorial_overview.html.5a8c9afe.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-6ab451c0":V(()=>O(()=>import("./tutorial_rexx.html.b7165cf6.js"),["assets/tutorial_rexx.html.b7165cf6.js","assets/createbranch.c5e1488b.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-64756ec4":V(()=>O(()=>import("./uninstalling.html.18615d66.js"),["assets/uninstalling.html.18615d66.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-99d69e34":V(()=>O(()=>import("./userinterface.html.d4a7f7f6.js"),["assets/userinterface.html.d4a7f7f6.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-da074572":V(()=>O(()=>import("./using_code_snippets.html.7cb84f6c.js"),["assets/using_code_snippets.html.7cb84f6c.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-37f5df26":V(()=>O(()=>import("./whatsnew.html.2392e1ae.js"),["assets/whatsnew.html.2392e1ae.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-43ab0a57":V(()=>O(()=>import("./zapp.html.7b153c97.js"),["assets/zapp.html.7b153c97.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-4d589ea8":V(()=>O(()=>import("./zcodeformatting.html.02d19d48.js"),["assets/zcodeformatting.html.02d19d48.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-2d85c4b3":V(()=>O(()=>import("./zopeneditor_v3.html.30921b7b.js"),["assets/zopeneditor_v3.html.30921b7b.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-41c85ba6":V(()=>O(()=>import("./zowe_advanced_connection_scenarious.html.d4ce32c4.js"),["assets/zowe_advanced_connection_scenarious.html.d4ce32c4.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-4b11bcde":V(()=>O(()=>import("./zowe_explorer_v2.html.6cf5ba2a.js"),["assets/zowe_explorer_v2.html.6cf5ba2a.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-60b2a3bf":V(()=>O(()=>import("./zowe_submitjcl.html.052fc861.js"),["assets/zowe_submitjcl.html.052fc861.js","assets/plugin-vue_export-helper.21dcd24c.js"])),"v-3706649a":V(()=>O(()=>import("./404.html.74b16cef.js"),["assets/404.html.74b16cef.js","assets/plugin-vue_export-helper.21dcd24c.js"]))},am={"v-8daa1a0e":()=>O(()=>import("./index.html.73039857.js"),[]).then(({data:e})=>e),"v-a38aa0ce":()=>O(()=>import("./announcing-jcl.html.18c0ed35.js"),[]).then(({data:e})=>e),"v-fe48651a":()=>O(()=>import("./announcing-rexx.html.7f07edc2.js"),[]).then(({data:e})=>e),"v-ed9f4f96":()=>O(()=>import("./announcing-zos-resources-table.html.e2b19ed3.js"),[]).then(({data:e})=>e),"v-8a4247d2":()=>O(()=>import("./code-snippets.html.b35039d1.js"),[]).then(({data:e})=>e),"v-0baade54":()=>O(()=>import("./external-posts.html.e8cf9791.js"),[]).then(({data:e})=>e),"v-1af1d74d":()=>O(()=>import("./hlasm-blog.html.2b659071.js"),[]).then(({data:e})=>e),"v-48cb972d":()=>O(()=>import("./ibm-wazi-development-client-introduction-blog.html.cfab7f14.js"),[]).then(({data:e})=>e),"v-00ed1fd0":()=>O(()=>import("./in-the-cloud-with-che.html.4286b16d.js"),[]).then(({data:e})=>e),"v-5a3683a7":()=>O(()=>import("./learning.html.986f01ac.js"),[]).then(({data:e})=>e),"v-4c46bc61":()=>O(()=>import("./new-content.html.51179cd8.js"),[]).then(({data:e})=>e),"v-7e9516cc":()=>O(()=>import("./new-releases.html.50a21e1d.js"),[]).then(({data:e})=>e),"v-a63a2e22":()=>O(()=>import("./ocp-ssl-cert.html.72eec9e1.js"),[]).then(({data:e})=>e),"v-6fa9df51":()=>O(()=>import("./rse-march-120.html.5426b66f.js"),[]).then(({data:e})=>e),"v-0d011afc":()=>O(()=>import("./rse-march-beta.html.4845308d.js"),[]).then(({data:e})=>e),"v-8483065a":()=>O(()=>import("./rse-october-110.html.548b92bb.js"),[]).then(({data:e})=>e),"v-5fac84d9":()=>O(()=>import("./userbuild-blog.html.2f09f33e.js"),[]).then(({data:e})=>e),"v-4b9415f0":()=>O(()=>import("./web-based-with-theia.html.b5ed8430.js"),[]).then(({data:e})=>e),"v-68af98c9":()=>O(()=>import("./whats-new-120.html.6568abcb.js"),[]).then(({data:e})=>e),"v-0ffb677e":()=>O(()=>import("./advanced_activation.html.a5808ffb.js"),[]).then(({data:e})=>e),"v-4066bbc6":()=>O(()=>import("./advanced_custom_macros.html.7f52e802.js"),[]).then(({data:e})=>e),"v-20708584":()=>O(()=>import("./advanced_overview.html.8507f257.js"),[]).then(({data:e})=>e),"v-a6691fb0":()=>O(()=>import("./advanced_preprocessor.html.57016ed4.js"),[]).then(({data:e})=>e),"v-ae2b9dea":()=>O(()=>import("./advanced_problems_view.html.ccbd31e1.js"),[]).then(({data:e})=>e),"v-01e2125a":()=>O(()=>import("./advanced_resource_table.html.56d32fb5.js"),[]).then(({data:e})=>e),"v-2a14c510":()=>O(()=>import("./connect_to_zos_with_zowe_cli_e2e.html.af5cc4c5.js"),[]).then(({data:e})=>e),"v-175f1e49":()=>O(()=>import("./connect_to_zos_with_zowe_explorer_e2e.html.178ef3f5.js"),[]).then(({data:e})=>e),"v-26fabd50":()=>O(()=>import("./creating_team_profiles.html.41cf0f73.js"),[]).then(({data:e})=>e),"v-e76197e2":()=>O(()=>import("./customizing_the_outline_view.html.f3e642b6.js"),[]).then(({data:e})=>e),"v-a2f185cc":()=>O(()=>import("./ebcdic_encoding.html.62a5eda6.js"),[]).then(({data:e})=>e),"v-391d428c":()=>O(()=>import("./editor_codechanges.html.2d2fe0de.js"),[]).then(({data:e})=>e),"v-1c58a9fc":()=>O(()=>import("./editor_codechanges_hlasm.html.d3e47b90.js"),[]).then(({data:e})=>e),"v-bb18cdb4":()=>O(()=>import("./editor_codechanges_jcl.html.80cbce3f.js"),[]).then(({data:e})=>e),"v-13c01586":()=>O(()=>import("./editor_codechanges_rexx.html.69d65a68.js"),[]).then(({data:e})=>e),"v-10307d7a":()=>O(()=>import("./editor_search.html.da2e21be.js"),[]).then(({data:e})=>e),"v-9b8c1724":()=>O(()=>import("./getting_started.html.42bb6dc4.js"),[]).then(({data:e})=>e),"v-afd18aa6":()=>O(()=>import("./git_integration.html.c9f41b18.js"),[]).then(({data:e})=>e),"v-1251ae42":()=>O(()=>import("./interact_common_properties_cli.html.4060a20b.js"),[]).then(({data:e})=>e),"v-f89d1930":()=>O(()=>import("./interact_zos_cli.html.91a26918.js"),[]).then(({data:e})=>e),"v-30184cb1":()=>O(()=>import("./interact_zos_overview.html.7ee849b5.js"),[]).then(({data:e})=>e),"v-3c830012":()=>O(()=>import("./interact_zos_zopeneditor.html.ec31013f.js"),[]).then(({data:e})=>e),"v-60c4e326":()=>O(()=>import("./interact_zos_zowe_explorer.html.2dc036e5.js"),[]).then(({data:e})=>e),"v-22d1c484":()=>O(()=>import("./introduction.html.89fa2796.js"),[]).then(({data:e})=>e),"v-823d11d2":()=>O(()=>import("./knownissues.html.d646b074.js"),[]).then(({data:e})=>e),"v-93378d76":()=>O(()=>import("./language_references.html.848e8284.js"),[]).then(({data:e})=>e),"v-ab2cfe42":()=>O(()=>import("./locating_local_client_logs.html.1c2cb5dd.js"),[]).then(({data:e})=>e),"v-f90f4ac6":()=>O(()=>import("./migrating_profiles.html.da583f28.js"),[]).then(({data:e})=>e),"v-065bea79":()=>O(()=>import("./notices.html.f0768ed8.js"),[]).then(({data:e})=>e),"v-e100f1ca":()=>O(()=>import("./other_extensions.html.5f52b5c4.js"),[]).then(({data:e})=>e),"v-9629110c":()=>O(()=>import("./privacypolicy.html.058a21d1.js"),[]).then(({data:e})=>e),"v-4aeeafba":()=>O(()=>import("./rse_cli_command.html.45be7e34.js"),[]).then(({data:e})=>e),"v-52b0a105":()=>O(()=>import("./rse_tutorial.html.cf75455e.js"),[]).then(({data:e})=>e),"v-9498fc72":()=>O(()=>import("./samplefiles.html.286dd5d0.js"),[]).then(({data:e})=>e),"v-9dcc581e":()=>O(()=>import("./setting_compiler_options.html.7fc5b9a1.js"),[]).then(({data:e})=>e),"v-522078b2":()=>O(()=>import("./setting_disableproblems.html.bc75fa0e.js"),[]).then(({data:e})=>e),"v-348a2d3e":()=>O(()=>import("./setting_fileassociations.html.8d6872d5.js"),[]).then(({data:e})=>e),"v-3f4d9f11":()=>O(()=>import("./setting_maximum_line_length.html.3383ac30.js"),[]).then(({data:e})=>e),"v-3ae1cfcb":()=>O(()=>import("./setting_preferences.html.c9708706.js"),[]).then(({data:e})=>e),"v-b824cc8e":()=>O(()=>import("./setting_propertygroup.html.b218f9a1.js"),[]).then(({data:e})=>e),"v-0dd03d73":()=>O(()=>import("./setting_tabstops.html.662c9129.js"),[]).then(({data:e})=>e),"v-2a63b1ab":()=>O(()=>import("./setting_unreachablecodewarnings.html.cf69f816.js"),[]).then(({data:e})=>e),"v-8fabeeca":()=>O(()=>import("./settings.html.9d25b897.js"),[]).then(({data:e})=>e),"v-14aa9ebc":()=>O(()=>import("./setup_integration.html.b8af3e48.js"),[]).then(({data:e})=>e),"v-0791b3a2":()=>O(()=>import("./sharing_team_configuration_files.html.40fb76ab.js"),[]).then(({data:e})=>e),"v-d9943bba":()=>O(()=>import("./sharingfiles.html.3ad6f744.js"),[]).then(({data:e})=>e),"v-6676f350":()=>O(()=>import("./shortcut.html.d694f8cd.js"),[]).then(({data:e})=>e),"v-45d644b0":()=>O(()=>import("./snippets.html.18b69914.js"),[]).then(({data:e})=>e),"v-7982067c":()=>O(()=>import("./trademarks.html.ea86a4af.js"),[]).then(({data:e})=>e),"v-492a8ebf":()=>O(()=>import("./tutorial_assembler.html.4c0ed640.js"),[]).then(({data:e})=>e),"v-035874ac":()=>O(()=>import("./tutorial_cobol.html.faab05d7.js"),[]).then(({data:e})=>e),"v-70c1277a":()=>O(()=>import("./tutorial_overview.html.7f140b81.js"),[]).then(({data:e})=>e),"v-6ab451c0":()=>O(()=>import("./tutorial_rexx.html.c3ddb259.js"),[]).then(({data:e})=>e),"v-64756ec4":()=>O(()=>import("./uninstalling.html.1a506d72.js"),[]).then(({data:e})=>e),"v-99d69e34":()=>O(()=>import("./userinterface.html.08973d08.js"),[]).then(({data:e})=>e),"v-da074572":()=>O(()=>import("./using_code_snippets.html.3eaca8dd.js"),[]).then(({data:e})=>e),"v-37f5df26":()=>O(()=>import("./whatsnew.html.98bdcc78.js"),[]).then(({data:e})=>e),"v-43ab0a57":()=>O(()=>import("./zapp.html.dd3eb1c6.js"),[]).then(({data:e})=>e),"v-4d589ea8":()=>O(()=>import("./zcodeformatting.html.f9619a10.js"),[]).then(({data:e})=>e),"v-2d85c4b3":()=>O(()=>import("./zopeneditor_v3.html.36632b1e.js"),[]).then(({data:e})=>e),"v-41c85ba6":()=>O(()=>import("./zowe_advanced_connection_scenarious.html.4bee0dd3.js"),[]).then(({data:e})=>e),"v-4b11bcde":()=>O(()=>import("./zowe_explorer_v2.html.02aff825.js"),[]).then(({data:e})=>e),"v-60b2a3bf":()=>O(()=>import("./zowe_submitjcl.html.14c9f11b.js"),[]).then(({data:e})=>e),"v-3706649a":()=>O(()=>import("./404.html.10ca2252.js"),[]).then(({data:e})=>e)},gl=Ne(am),yl=hi({key:"",path:"",title:"",lang:"",frontmatter:{},excerpt:"",headers:[]}),ut=Ne(yl),tr=()=>ut;Hi.webpackHot&&(__VUE_HMR_RUNTIME__.updatePageData=e=>{gl.value[e.key]=()=>Promise.resolve(e),e.key===ut.value.key&&(ut.value=e)});const bl=Symbol(""),cm=()=>{const e=Te(bl);if(!e)throw new Error("usePageFrontmatter() is called without provider.");return e},El=Symbol(""),lm=()=>{const e=Te(El);if(!e)throw new Error("usePageHead() is called without provider.");return e},um=Symbol(""),Ol=Symbol(""),wl=()=>{const e=Te(Ol);if(!e)throw new Error("usePageLang() is called without provider.");return e},Li=Symbol(""),Sl=()=>{const e=Te(Li);if(!e)throw new Error("useRouteLocale() is called without provider.");return e},fm={base:"/zopeneditor-about/",lang:"en-US",title:"IBM Z\xAE Open Editor",description:"IBM enterprise language support for COBOL, PL/I, HLASM, and REXX in VS Code\u201D",head:[["meta",{charset:"utf-8"}],["meta",{name:"viewport",content:"width=device-width,initial-scale=1"}],["link",{rel:"icon",type:"image/png",sizes:"32x32",href:"/zopeneditor-about/assets/img/favicon-32x32.png"}],["meta",{name:"keywords",content:"IBM, COBOL, PL/I, PLI, PL1, JCL, jesjcl, jesmsglg, jesysmsg, IDE, LSP, language-server, keybindings, snippet, z/OS, zOS, Z Software, Zowe, Mainframe, Visual Studio Code, VS Code, VSCode, Git, Open Source, Development, Extension, Theia, Che, REXX, Zowe Explorer, Zowe CLI, RSE API, Remote System Explorer,  HLASM, ASM, IBM Z"}],["meta",{name:"google-site-verification",content:"Ona_2rMxidYRtJWAlzNHkfKFB3f9DkKKNTJCYLZVei8"}],["link",{rel:"stylesheet",href:"https://fonts.googleapis.com/css2?family=IBM+Plex+Sans:wght@200;300;400;500;600;700&display=swap"}],["link",{rel:"stylesheet",href:"https://cdn.jsdelivr.net/npm/@docsearch/css@alpha"}],["link",{rel:"stylesheet",href:"/zopeneditor-about/assets/css/foundation.css"}],["link",{rel:"stylesheet",href:"/zopeneditor-about/assets/css/animate.css"}],["link",{rel:"stylesheet",href:"/zopeneditor-about/assets/css/custom.css"}],["script",{src:"https://code.jquery.com/jquery-3.5.1.min.js"},`
             (
                 /* workaround for adding script tags at the end with the head feature */
                 function() { 
@@ -20,9 +20,9 @@ var bu=Object.defineProperty,Eu=Object.defineProperties;var Ou=Object.getOwnProp
                     });
                 }
             )();
-            `]],locales:{}},wt=Ne(fm),Pl=()=>wt;Hi.webpackHot&&(__VUE_HMR_RUNTIME__.updateSiteData=e=>{wt.value=e});const Dl=Symbol(""),yg=()=>{const e=Te(Dl);if(!e)throw new Error("useSiteLocaleData() is called without provider.");return e},dm=Symbol(""),ji=e=>{let t;e.pageKey?t=e.pageKey:t=tr().value.key;const n=vl[t];return n?be(n):be("div","404 Not Found")};ji.displayName="Content";ji.props={pageKey:{type:String,required:!1}};const pm={"404":V(()=>O(()=>import("./404.233222d2.js"),[])),Layout:V(()=>O(()=>import("./Layout.006ebc38.js"),["assets/Layout.006ebc38.js","assets/plugin-vue_export-helper.21dcd24c.js"]))},mm=([e,t,n])=>e==="meta"&&t.name?`${e}.${t.name}`:["title","base"].includes(e)?e:e==="template"&&t.id?`${e}.${t.id}`:JSON.stringify([e,t,n]),hm=e=>{const t=new Set,n=[];return e.forEach(r=>{const o=mm(r);t.has(o)||(t.add(o),n.push(r))}),n},_m=e=>/^(https?:)?\/\//.test(e),bg=e=>/^mailto:/.test(e),Eg=e=>/^tel:/.test(e),Il=e=>Object.prototype.toString.call(e)==="[object Object]",vm=e=>e.replace(/\/$/,""),gm=e=>e.replace(/^\//,""),Al=(e,t)=>{const n=Object.keys(e).sort((r,o)=>{const i=o.split("/").length-r.split("/").length;return i!==0?i:o.length-r.length});for(const r of n)if(t.startsWith(r))return r;return"/"},ym=(e,t="/")=>e.replace(/^(https?:)?\/\/[^/]*/,"").replace(new RegExp(`^${t}`),"/"),Vs=Qe({name:"Vuepress",setup(){const e=tr(),t=Oe(()=>{let n;if(e.value.path){const r=e.value.frontmatter.layout;ve(r)?n=r:n="Layout"}else n="404";return pm[n]||ld(n,!1)});return()=>be(t.value)}}),nr=e=>e,ki=e=>e,bm=e=>_m(e)?e:`${Pl().value.base}${gm(e)}`,jt=_n({resolvePageData:async e=>{const t=gl.value[e],n=await(t==null?void 0:t());return n!=null?n:yl},resolvePageFrontmatter:e=>e.frontmatter,resolvePageHead:(e,t,n)=>{const r=ve(t.description)?t.description:n.description,o=[...ee(t.head)?t.head:[],...n.head,["title",{},e],["meta",{name:"description",content:r}]];return hm(o)},resolvePageHeadTitle:(e,t)=>`${e.title?`${e.title} | `:""}${t.title}`,resolvePageLang:e=>e.lang||"en",resolveRouteLocale:(e,t)=>Al(e,t),resolveSiteLocaleData:(e,t)=>je(je({},e),e.locales[t])});const Em=be("svg",{class:"external-link-icon",xmlns:"http://www.w3.org/2000/svg","aria-hidden":"true",focusable:"false",x:"0px",y:"0px",viewBox:"0 0 100 100",width:"15",height:"15"},[be("path",{fill:"currentColor",d:"M18.8,85.1h56l0,0c2.2,0,4-1.8,4-4v-32h-8v28h-48v-48h28v-8h-32l0,0c-2.2,0-4,1.8-4,4v56C14.8,83.3,16.6,85.1,18.8,85.1z"}),be("polygon",{fill:"currentColor",points:"45.7,48.7 51.3,54.3 77.2,28.5 77.2,37.2 85.2,37.2 85.2,14.9 62.8,14.9 62.8,22.9 71.5,22.9"})]),Om=Qe({name:"ExternalLinkIcon",props:{locales:{type:Object,required:!1,default:()=>({})}},setup(e){const t=Sl(),n=Oe(()=>{var r;return(r=e.locales[t.value])!==null&&r!==void 0?r:{openInNewWindow:"open in new window"}});return()=>be("span",[Em,be("span",{class:"external-link-icon-sr-only"},n.value.openInNewWindow)])}}),wm={"/":{openInNewWindow:"open in new window"}};var Sm=nr(({app:e})=>{e.component("ExternalLinkIcon",be(Om,{locales:wm}))});/*! medium-zoom 1.0.6 | MIT License | https://github.com/francoischalifour/medium-zoom */var kt=Object.assign||function(e){for(var t=1;twt;Hi.webpackHot&&(__VUE_HMR_RUNTIME__.updateSiteData=e=>{wt.value=e});const Dl=Symbol(""),yg=()=>{const e=Te(Dl);if(!e)throw new Error("useSiteLocaleData() is called without provider.");return e},dm=Symbol(""),ji=e=>{let t;e.pageKey?t=e.pageKey:t=tr().value.key;const n=vl[t];return n?be(n):be("div","404 Not Found")};ji.displayName="Content";ji.props={pageKey:{type:String,required:!1}};const pm={"404":V(()=>O(()=>import("./404.130cdeb2.js"),[])),Layout:V(()=>O(()=>import("./Layout.b8d46050.js"),["assets/Layout.b8d46050.js","assets/plugin-vue_export-helper.21dcd24c.js"]))},mm=([e,t,n])=>e==="meta"&&t.name?`${e}.${t.name}`:["title","base"].includes(e)?e:e==="template"&&t.id?`${e}.${t.id}`:JSON.stringify([e,t,n]),hm=e=>{const t=new Set,n=[];return e.forEach(r=>{const o=mm(r);t.has(o)||(t.add(o),n.push(r))}),n},_m=e=>/^(https?:)?\/\//.test(e),bg=e=>/^mailto:/.test(e),Eg=e=>/^tel:/.test(e),Il=e=>Object.prototype.toString.call(e)==="[object Object]",vm=e=>e.replace(/\/$/,""),gm=e=>e.replace(/^\//,""),Al=(e,t)=>{const n=Object.keys(e).sort((r,o)=>{const i=o.split("/").length-r.split("/").length;return i!==0?i:o.length-r.length});for(const r of n)if(t.startsWith(r))return r;return"/"},ym=(e,t="/")=>e.replace(/^(https?:)?\/\/[^/]*/,"").replace(new RegExp(`^${t}`),"/"),Vs=Qe({name:"Vuepress",setup(){const e=tr(),t=Oe(()=>{let n;if(e.value.path){const r=e.value.frontmatter.layout;ve(r)?n=r:n="Layout"}else n="404";return pm[n]||ld(n,!1)});return()=>be(t.value)}}),nr=e=>e,ki=e=>e,bm=e=>_m(e)?e:`${Pl().value.base}${gm(e)}`,jt=_n({resolvePageData:async e=>{const t=gl.value[e],n=await(t==null?void 0:t());return n!=null?n:yl},resolvePageFrontmatter:e=>e.frontmatter,resolvePageHead:(e,t,n)=>{const r=ve(t.description)?t.description:n.description,o=[...ee(t.head)?t.head:[],...n.head,["title",{},e],["meta",{name:"description",content:r}]];return hm(o)},resolvePageHeadTitle:(e,t)=>`${e.title?`${e.title} | `:""}${t.title}`,resolvePageLang:e=>e.lang||"en",resolveRouteLocale:(e,t)=>Al(e,t),resolveSiteLocaleData:(e,t)=>je(je({},e),e.locales[t])});const Em=be("svg",{class:"external-link-icon",xmlns:"http://www.w3.org/2000/svg","aria-hidden":"true",focusable:"false",x:"0px",y:"0px",viewBox:"0 0 100 100",width:"15",height:"15"},[be("path",{fill:"currentColor",d:"M18.8,85.1h56l0,0c2.2,0,4-1.8,4-4v-32h-8v28h-48v-48h28v-8h-32l0,0c-2.2,0-4,1.8-4,4v56C14.8,83.3,16.6,85.1,18.8,85.1z"}),be("polygon",{fill:"currentColor",points:"45.7,48.7 51.3,54.3 77.2,28.5 77.2,37.2 85.2,37.2 85.2,14.9 62.8,14.9 62.8,22.9 71.5,22.9"})]),Om=Qe({name:"ExternalLinkIcon",props:{locales:{type:Object,required:!1,default:()=>({})}},setup(e){const t=Sl(),n=Oe(()=>{var r;return(r=e.locales[t.value])!==null&&r!==void 0?r:{openInNewWindow:"open in new window"}});return()=>be("span",[Em,be("span",{class:"external-link-icon-sr-only"},n.value.openInNewWindow)])}}),wm={"/":{openInNewWindow:"open in new window"}};var Sm=nr(({app:e})=>{e.component("ExternalLinkIcon",be(Om,{locales:wm}))});/*! medium-zoom 1.0.6 | MIT License | https://github.com/francoischalifour/medium-zoom */var kt=Object.assign||function(e){for(var t=1;t1&&arguments[1]!==void 0?arguments[1]:{},r=window.Promise||function(I){function B(){}I(B,B)},o=function(I){var B=I.target;if(B===$){m();return}S.indexOf(B)!==-1&&v({target:B})},i=function(){if(!(T||!D.original)){var I=window.pageYOffset||document.documentElement.scrollTop||document.body.scrollTop||0;Math.abs(N-I)>A.scrollOffset&&setTimeout(m,150)}},s=function(I){var B=I.key||I.keyCode;(B==="Escape"||B==="Esc"||B===27)&&m()},a=function(){var I=arguments.length>0&&arguments[0]!==void 0?arguments[0]:{},B=I;if(I.background&&($.style.background=I.background),I.container&&I.container instanceof Object&&(B.container=kt({},A.container,I.container)),I.template){var Y=yr(I.template)?I.template:document.querySelector(I.template);B.template=Y}return A=kt({},A,B),S.forEach(function(ae){ae.dispatchEvent(Zt("medium-zoom:update",{detail:{zoom:F}}))}),F},c=function(){var I=arguments.length>0&&arguments[0]!==void 0?arguments[0]:{};return e(kt({},A,I))},l=function(){for(var I=arguments.length,B=Array(I),Y=0;Y0?B.reduce(function(J,ne){return[].concat(J,Bs(ne))},[]):S;return ae.forEach(function(J){J.classList.remove("medium-zoom-image"),J.dispatchEvent(Zt("medium-zoom:detach",{detail:{zoom:F}}))}),S=S.filter(function(J){return ae.indexOf(J)===-1}),F},d=function(I,B){var Y=arguments.length>2&&arguments[2]!==void 0?arguments[2]:{};return S.forEach(function(ae){ae.addEventListener("medium-zoom:"+I,B,Y)}),P.push({type:"medium-zoom:"+I,listener:B,options:Y}),F},f=function(I,B){var Y=arguments.length>2&&arguments[2]!==void 0?arguments[2]:{};return S.forEach(function(ae){ae.removeEventListener("medium-zoom:"+I,B,Y)}),P=P.filter(function(ae){return!(ae.type==="medium-zoom:"+I&&ae.listener.toString()===B.toString())}),F},h=function(){var I=arguments.length>0&&arguments[0]!==void 0?arguments[0]:{},B=I.target,Y=function(){var J={width:document.documentElement.clientWidth,height:document.documentElement.clientHeight,left:0,top:0,right:0,bottom:0},ne=void 0,re=void 0;if(A.container)if(A.container instanceof Object)J=kt({},J,A.container),ne=J.width-J.left-J.right-A.margin*2,re=J.height-J.top-J.bottom-A.margin*2;else{var Ee=yr(A.container)?A.container:document.querySelector(A.container),Pe=Ee.getBoundingClientRect(),Ie=Pe.width,we=Pe.height,Re=Pe.left,He=Pe.top;J=kt({},J,{width:Ie,height:we,left:Re,top:He})}ne=ne||J.width-A.margin*2,re=re||J.height-A.margin*2;var R=D.zoomedHd||D.original,U=Hs(R)?ne:R.naturalWidth||ne,M=Hs(R)?re:R.naturalHeight||re,q=R.getBoundingClientRect(),le=q.top,pe=q.left,oe=q.width,te=q.height,p=Math.min(U,ne)/oe,y=Math.min(M,re)/te,w=Math.min(p,y),C=(-pe+(ne-oe)/2+A.margin+J.left)/w,x=(-le+(re-te)/2+A.margin+J.top)/w,L="scale("+w+") translate3d("+C+"px, "+x+"px, 0)";D.zoomed.style.transform=L,D.zoomedHd&&(D.zoomedHd.style.transform=L)};return new r(function(ae){if(B&&S.indexOf(B)===-1){ae(F);return}var J=function Ie(){T=!1,D.zoomed.removeEventListener("transitionend",Ie),D.original.dispatchEvent(Zt("medium-zoom:opened",{detail:{zoom:F}})),ae(F)};if(D.zoomed){ae(F);return}if(B)D.original=B;else if(S.length>0){var ne=S;D.original=ne[0]}else{ae(F);return}if(D.original.dispatchEvent(Zt("medium-zoom:open",{detail:{zoom:F}})),N=window.pageYOffset||document.documentElement.scrollTop||document.body.scrollTop||0,T=!0,D.zoomed=Im(D.original),document.body.appendChild($),A.template){var re=yr(A.template)?A.template:document.querySelector(A.template);D.template=document.createElement("div"),D.template.appendChild(re.content.cloneNode(!0)),document.body.appendChild(D.template)}if(document.body.appendChild(D.zoomed),window.requestAnimationFrame(function(){document.body.classList.add("medium-zoom--opened")}),D.original.classList.add("medium-zoom-image--hidden"),D.zoomed.classList.add("medium-zoom-image--opened"),D.zoomed.addEventListener("click",m),D.zoomed.addEventListener("transitionend",J),D.original.getAttribute("data-zoom-src")){D.zoomedHd=D.zoomed.cloneNode(),D.zoomedHd.removeAttribute("srcset"),D.zoomedHd.removeAttribute("sizes"),D.zoomedHd.src=D.zoomed.getAttribute("data-zoom-src"),D.zoomedHd.onerror=function(){clearInterval(Ee),console.warn("Unable to reach the zoom image target "+D.zoomedHd.src),D.zoomedHd=null,Y()};var Ee=setInterval(function(){D.zoomedHd.complete&&(clearInterval(Ee),D.zoomedHd.classList.add("medium-zoom-image--opened"),D.zoomedHd.addEventListener("click",m),document.body.appendChild(D.zoomedHd),Y())},10)}else if(D.original.hasAttribute("srcset")){D.zoomedHd=D.zoomed.cloneNode(),D.zoomedHd.removeAttribute("sizes"),D.zoomedHd.removeAttribute("loading");var Pe=D.zoomedHd.addEventListener("load",function(){D.zoomedHd.removeEventListener("load",Pe),D.zoomedHd.classList.add("medium-zoom-image--opened"),D.zoomedHd.addEventListener("click",m),document.body.appendChild(D.zoomedHd),Y()})}else Y()})},m=function(){return new r(function(I){if(T||!D.original){I(F);return}var B=function Y(){D.original.classList.remove("medium-zoom-image--hidden"),document.body.removeChild(D.zoomed),D.zoomedHd&&document.body.removeChild(D.zoomedHd),document.body.removeChild($),D.zoomed.classList.remove("medium-zoom-image--opened"),D.template&&document.body.removeChild(D.template),T=!1,D.zoomed.removeEventListener("transitionend",Y),D.original.dispatchEvent(Zt("medium-zoom:closed",{detail:{zoom:F}})),D.original=null,D.zoomed=null,D.zoomedHd=null,D.template=null,I(F)};T=!0,document.body.classList.remove("medium-zoom--opened"),D.zoomed.style.transform="",D.zoomedHd&&(D.zoomedHd.style.transform=""),D.template&&(D.template.style.transition="opacity 150ms",D.template.style.opacity=0),D.original.dispatchEvent(Zt("medium-zoom:close",{detail:{zoom:F}})),D.zoomed.addEventListener("transitionend",B)})},v=function(){var I=arguments.length>0&&arguments[0]!==void 0?arguments[0]:{},B=I.target;return D.original?m():h({target:B})},_=function(){return A},g=function(){return S},E=function(){return D.original},S=[],P=[],T=!1,N=0,A=n,D={original:null,zoomed:null,zoomedHd:null,template:null};Object.prototype.toString.call(t)==="[object Object]"?A=t:(t||typeof t=="string")&&l(t),A=kt({margin:0,background:"#fff",scrollOffset:40,container:null,template:null},A);var $=Dm(A.background);document.addEventListener("click",o),document.addEventListener("keyup",s),document.addEventListener("scroll",i),window.addEventListener("resize",m);var F={open:h,close:m,toggle:v,update:a,clone:c,attach:l,detach:u,on:d,off:f,getOptions:_,getImages:g,getZoomedImage:E};return F};function Cm(e,t){t===void 0&&(t={});var n=t.insertAt;if(!(!e||typeof document=="undefined")){var r=document.head||document.getElementsByTagName("head")[0],o=document.createElement("style");o.type="text/css",n==="top"&&r.firstChild?r.insertBefore(o,r.firstChild):r.appendChild(o),o.styleSheet?o.styleSheet.cssText=e:o.appendChild(document.createTextNode(e))}}var Tm=".medium-zoom-overlay{position:fixed;top:0;right:0;bottom:0;left:0;opacity:0;transition:opacity .3s;will-change:opacity}.medium-zoom--opened .medium-zoom-overlay{cursor:pointer;cursor:zoom-out;opacity:1}.medium-zoom-image{cursor:pointer;cursor:zoom-in;transition:transform .3s cubic-bezier(.2,0,.2,1)!important}.medium-zoom-image--hidden{visibility:hidden}.medium-zoom-image--opened{position:relative;cursor:pointer;cursor:zoom-out;will-change:transform}";Cm(Tm);var Rm=Am;const xm=Symbol("mediumZoom");const Lm=".theme-default-content > img, .theme-default-content :not(a) > img",jm={},km=300;var Nm=nr(({app:e,router:t})=>{const n=Rm(jm);n.refresh=(r=Lm)=>{n.detach(),n.attach(r)},e.provide(xm,n),t.afterEach(()=>{setTimeout(()=>n.refresh(),km)})});const Mm={docsDir:"zopeneditor-docs",repo:"https://github.com/IBM/zopeneditor-about/issues",editLink:!1,lastUpdated:!0,sidebarDepth:2,navbar:[{text:"Docs",link:"/Docs/introduction"},{text:"News and Blogs",link:"/Blog/new-content"},{text:"IBM Downloads",link:"https://ibm.github.io/mainframe-downloads/downloads.html"},{text:"VS Code Marketplace",link:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor"}],sidebar:{"/Docs/":[{text:"Overview",collapsible:!0,children:["introduction","whatsnew"]},{text:"Getting Started",collapsible:!0,children:["getting_started","setup_integration","zopeneditor_v3","zowe_explorer_v2"]},{text:"Configuration",collapsible:!0,children:["setting_preferences","zapp","setting_propertygroup","setting_compiler_options","setting_fileassociations","setting_tabstops","setting_disableproblems","setting_unreachablecodewarnings","customizing_the_outline_view","setting_maximum_line_length","ebcdic_encoding","zcodeformatting"]},{text:"Tutorials",collapsible:!0,children:["tutorial_overview","userinterface","samplefiles","tutorial_cobol","tutorial_assembler","tutorial_rexx","rse_tutorial","zowe_submitjcl"]},{text:"Editing program files",collapsible:!0,children:["language_references","editor_codechanges","editor_codechanges_hlasm","editor_codechanges_rexx","editor_codechanges_jcl","snippets","git_integration","editor_search"]},{text:"Interacting with z/OS using Zowe",collapsible:!0,children:["interact_zos_overview","connect_to_zos_with_zowe_explorer_e2e","connect_to_zos_with_zowe_cli_e2e","interact_zos_zopeneditor","zowe_advanced_connection_scenarious","sharing_team_configuration_files","interact_zos_cli","interact_common_properties_cli","interact_zos_zowe_explorer","migrating_profiles","creating_team_profiles"]},{text:"Advanced Capabilities",collapsible:!0,children:["advanced_overview","advanced_activation","advanced_resource_table","advanced_preprocessor","advanced_problems_view","advanced_custom_macros"]},{text:"Troubleshooting",collapsible:!0,children:["knownissues","locating_local_client_logs","uninstalling"]},{text:"Reference",collapsible:!0,children:["rse_cli_command","shortcut","settings","other_extensions"]},{text:"Legal information",collapsible:!0,children:["notices","trademarks","privacypolicy"]}],"/Blog/":[{text:"What's New",collapsible:!0,children:["new-content","new-releases"]},{text:"Team Blog",collapsible:!0,children:["announcing-jcl","whats-new-120","announcing-rexx","rse-march-120","userbuild-blog","ocp-ssl-cert","rse-october-110","ibm-wazi-development-client-introduction-blog","hlasm-blog","rse-march-beta","code-snippets","in-the-cloud-with-che","web-based-with-theia"]},{text:"Other Resources",collapsible:!1,children:["learning"]}]},darkMode:!0,locales:{"/":{selectLanguageName:"English"}},logo:null,selectLanguageText:"Languages",selectLanguageAriaLabel:"Select language",editLinkText:"Edit this page",lastUpdatedText:"Last Updated",contributors:!0,contributorsText:"Contributors",notFound:["There's nothing here.","How did we get here?","That's a Four-Oh-Four.","Looks like we've got some broken links."],backToHome:"Take me home",openInNewWindow:"open in new window",toggleDarkMode:"toggle dark mode",toggleSidebar:"toggle sidebar"},Cl=Ne(Mm),zm=()=>Cl;Hi.webpackHot&&(__VUE_HMR_RUNTIME__.updateThemeData=e=>{Cl.value=e});const Tl=Symbol(""),Vm=()=>{const e=Te(Tl);if(!e)throw new Error("useThemeLocaleData() is called without provider.");return e},Hm=(e,t)=>{var n;return je(je({},e),(n=e.locales)===null||n===void 0?void 0:n[t])};var Bm=nr(({app:e})=>{const t=zm(),n=e._context.provides[Li],r=Oe(()=>Hm(t.value,n.value));e.provide(Tl,r),Object.defineProperties(e.config.globalProperties,{$theme:{get(){return t.value}},$themeLocale:{get(){return r.value}}})});const Fm=Qe({props:{type:{type:String,required:!1,default:"tip"},text:{type:String,required:!1,default:""},vertical:{type:String,required:!1,default:void 0}},setup(e){return(t,n)=>(Xr(),Zc("span",{class:Yn(["badge",e.type]),style:Kr({verticalAlign:e.vertical})},[Xc(t.$slots,"default",{},()=>[Di(Tu(e.text),1)])],6))}});var Um=Qe({name:"CodeGroup",setup(e,{slots:t}){const n=Ne(-1),r=Ne([]),o=(a=n.value)=>{a{a>0?n.value=a-1:n.value=r.value.length-1,r.value[n.value].focus()},s=(a,c)=>{a.key===" "||a.key==="Enter"?(a.preventDefault(),n.value=c):a.key==="ArrowRight"?(a.preventDefault(),o(c)):a.key==="ArrowLeft"&&(a.preventDefault(),i(c))};return()=>{var a;const c=(((a=t.default)===null||a===void 0?void 0:a.call(t))||[]).filter(l=>l.type.name==="CodeGroupItem").map(l=>(l.props===null&&(l.props={}),l));return c.length===0?null:(n.value<0||n.value>c.length-1?(n.value=c.findIndex(l=>l.props.active===""||l.props.active===!0),n.value===-1&&(n.value=0)):c.forEach((l,u)=>{l.props.active=u===n.value}),be("div",{class:"code-group"},[be("div",{class:"code-group__nav"},be("ul",{class:"code-group__ul"},c.map((l,u)=>{const d=u===n.value;return be("li",{class:"code-group__li"},be("button",{ref:f=>{f&&(r.value[u]=f)},class:{"code-group__nav-tab":!0,"code-group__nav-tab-active":d},ariaPressed:d,ariaExpanded:d,onClick:()=>n.value=u,onKeydown:f=>s(f,u)},l.props.title))}))),c]))}}});const $m=["aria-selected"],qm=Qe({name:"CodeGroupItem"}),Km=Qe(At(je({},qm),{props:{title:{type:String,required:!0},active:{type:Boolean,required:!1,default:!1}},setup(e){return(t,n)=>(Xr(),Zc("div",{class:Yn(["code-group-item",{"code-group-item__active":e.active}]),"aria-selected":e.active},[Xc(t.$slots,"default")],10,$m))}}));function Rl(e){return Hu()?(Bu(e),!0):!1}const rr=typeof window!="undefined",Wm=e=>typeof e=="string",go=()=>{};function Zm(e,t){function n(...r){e(()=>t.apply(this,r),{fn:t,thisArg:this,args:r})}return n}const Jm=e=>e();var Fs=Object.getOwnPropertySymbols,Qm=Object.prototype.hasOwnProperty,Ym=Object.prototype.propertyIsEnumerable,Xm=(e,t)=>{var n={};for(var r in e)Qm.call(e,r)&&t.indexOf(r)<0&&(n[r]=e[r]);if(e!=null&&Fs)for(var r of Fs(e))t.indexOf(r)<0&&Ym.call(e,r)&&(n[r]=e[r]);return n};function Gm(e,t,n={}){const r=n,{eventFilter:o=Jm}=r,i=Xm(r,["eventFilter"]);return et(e,Zm(o,t),i)}function eh(e,t=!0){el()?at(e):t?e():yi(e)}const Mr=rr?window:void 0;rr&&window.document;rr&&window.navigator;rr&&window.location;function th(...e){let t,n,r,o;if(Wm(e[0])?([n,r,o]=e,t=Mr):[t,n,r,o]=e,!t)return go;let i=go;const s=et(()=>Ht(t),c=>{i(),c&&(c.addEventListener(n,r,o),i=()=>{c.removeEventListener(n,r,o),i=go})},{immediate:!0,flush:"post"}),a=()=>{s(),i()};return Rl(a),a}function nh(e,t={}){const{window:n=Mr}=t;let r;const o=Ne(!1),i=()=>{!n||(r||(r=n.matchMedia(e)),o.value=r.matches)};return eh(()=>{i(),r&&("addEventListener"in r?r.addEventListener("change",i):r.addListener(i),Rl(()=>{"removeEventListener"in i?r.removeEventListener("change",i):r.removeListener(i)}))}),o}const Uo=typeof globalThis!="undefined"?globalThis:typeof window!="undefined"?window:typeof global!="undefined"?global:typeof self!="undefined"?self:{},$o="__vueuse_ssr_handlers__";Uo[$o]=Uo[$o]||{};const rh=Uo[$o];function oh(e,t){return rh[e]||t}function ih(e){return e==null?"any":e instanceof Set?"set":e instanceof Map?"map":typeof e=="boolean"?"boolean":typeof e=="string"?"string":typeof e=="object"||Array.isArray(e)?"object":Number.isNaN(e)?"any":"number"}const sh={boolean:{read:e=>e==="true",write:e=>String(e)},object:{read:e=>JSON.parse(e),write:e=>JSON.stringify(e)},number:{read:e=>Number.parseFloat(e),write:e=>String(e)},any:{read:e=>e,write:e=>String(e)},string:{read:e=>e,write:e=>String(e)},map:{read:e=>new Map(JSON.parse(e)),write:e=>JSON.stringify(Array.from(e.entries()))},set:{read:e=>new Set(JSON.parse(e)),write:e=>JSON.stringify(Array.from(e.entries()))}};function ah(e,t,n,r={}){var o;const{flush:i="pre",deep:s=!0,listenToStorageChanges:a=!0,writeDefaults:c=!0,shallow:l,window:u=Mr,eventFilter:d,onError:f=E=>{console.error(E)}}=r,h=Ht(t),m=ih(h),v=(l?Ec:Ne)(t),_=(o=r.serializer)!=null?o:sh[m];if(!n)try{n=oh("getDefaultStorage",()=>{var E;return(E=Mr)==null?void 0:E.localStorage})()}catch(E){f(E)}function g(E){if(!(!n||E&&E.key!==e))try{const S=E?E.newValue:n.getItem(e);S==null?(v.value=h,c&&h!==null&&n.setItem(e,_.write(h))):typeof S!="string"?v.value=S:v.value=_.read(S)}catch(S){f(S)}}return g(),u&&a&&th(u,"storage",E=>setTimeout(()=>g(E),0)),n&&Gm(v,()=>{try{v.value==null?n.removeItem(e):n.setItem(e,_.write(v.value))}catch(E){f(E)}},{flush:i,deep:s,eventFilter:d}),v}function ch(e){return nh("(prefers-color-scheme: dark)",e)}var Us,$s;rr&&(window==null?void 0:window.navigator)&&((Us=window==null?void 0:window.navigator)==null?void 0:Us.platform)&&/iP(ad|hone|od)/.test(($s=window==null?void 0:window.navigator)==null?void 0:$s.platform);var lh=Object.defineProperty,qs=Object.getOwnPropertySymbols,uh=Object.prototype.hasOwnProperty,fh=Object.prototype.propertyIsEnumerable,Ks=(e,t,n)=>t in e?lh(e,t,{enumerable:!0,configurable:!0,writable:!0,value:n}):e[t]=n,dh=(e,t)=>{for(var n in t||(t={}))uh.call(t,n)&&Ks(e,n,t[n]);if(qs)for(var n of qs(t))fh.call(t,n)&&Ks(e,n,t[n]);return e};const ph={top:0,left:0,bottom:0,right:0,height:0,width:0};dh({text:""},ph);const xl=Symbol(""),Og=()=>{const e=Te(xl);if(!e)throw new Error("useDarkMode() is called without provider.");return e},mh=()=>{const e=Nl(),t=ch(),n=ah("vuepress-color-scheme","auto"),r=Oe({get(){return e.value.darkMode?n.value==="auto"?t.value:n.value==="dark":!1},set(o){o===t.value?n.value="auto":n.value=o?"dark":"light"}});Bt(xl,r),hh(r)},hh=e=>{const t=(n=e.value)=>{const r=window==null?void 0:window.document.querySelector("html");r==null||r.classList.toggle("dark",n)};at(()=>{et(e,t,{immediate:!0})}),Si(()=>t())},Ll=(...e)=>{const n=no().resolve(...e),r=n.matched[n.matched.length-1];if(!(r!=null&&r.redirect))return n;const{redirect:o}=r,i=ie(o)?o(n):o,s=ve(i)?{path:i}:i;return Ll(je({hash:n.hash,query:n.query,params:n.params},s))},_h=e=>{const t=Ll(e);return{text:t.meta.title||e,link:t.name==="404"?e:t.fullPath}};let yo=null,On=null;const vh={wait:()=>yo,pending:()=>{yo=new Promise(e=>On=e)},resolve:()=>{On==null||On(),yo=null,On=null}},gh=()=>vh,jl=Symbol("sidebarItems"),wg=()=>{const e=Te(jl);if(!e)throw new Error("useSidebarItems() is called without provider.");return e},yh=()=>{const e=Nl(),t=cm(),n=Oe(()=>bh(t.value,e.value));Bt(jl,n)},bh=(e,t)=>{var n,r,o,i;const s=(r=(n=e.sidebar)!==null&&n!==void 0?n:t.sidebar)!==null&&r!==void 0?r:"auto",a=(i=(o=e.sidebarDepth)!==null&&o!==void 0?o:t.sidebarDepth)!==null&&i!==void 0?i:2;return e.home||s===!1?[]:s==="auto"?Oh(a):ee(s)?kl(s,a):Il(s)?wh(s,a):[]},Eh=(e,t)=>({text:e.title,link:`#${e.slug}`,children:Ni(e.children,t)}),Ni=(e,t)=>t>0?e.map(n=>Eh(n,t-1)):[],Oh=e=>{const t=tr();return[{text:t.value.title,children:Ni(t.value.headers,e)}]},kl=(e,t)=>{const n=xi(),r=tr(),o=i=>{var s;let a;if(ve(i)?a=_h(i):a=i,a.children)return At(je({},a),{children:a.children.map(c=>o(c))});if(a.link===n.path){const c=((s=r.value.headers[0])===null||s===void 0?void 0:s.level)===1?r.value.headers[0].children:r.value.headers;return At(je({},a),{children:Ni(c,t)})}return a};return e.map(i=>o(i))},wh=(e,t)=>{var n;const r=xi(),o=Al(e,r.path),i=(n=e[o])!==null&&n!==void 0?n:[];return kl(i,t)},Nl=()=>Vm();var Sh=nr(({app:e,router:t})=>{e.component("Badge",Fm),e.component("CodeGroup",Um),e.component("CodeGroupItem",Km),e.component("NavbarSearch",()=>{const r=e.component("Docsearch")||e.component("SearchBox");return r?be(r):null});const n=t.options.scrollBehavior;t.options.scrollBehavior=async(...r)=>(await gh().wait(),n(...r))});/*! @docsearch/js 3.0.0-alpha.42 | MIT License | © Algolia, Inc. and contributors | https://docsearch.algolia.com */function Kn(e){return Kn=typeof Symbol=="function"&&typeof Symbol.iterator=="symbol"?function(t){return typeof t}:function(t){return t&&typeof Symbol=="function"&&t.constructor===Symbol&&t!==Symbol.prototype?"symbol":typeof t},Kn(e)}function Ph(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function qo(){return qo=Object.assign||function(e){for(var t=1;t=0||(u[c]=s[c]);return u}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}function zr(e,t){return function(n){if(Array.isArray(n))return n}(e)||function(n,r){if(!(typeof Symbol=="undefined"||!(Symbol.iterator in Object(n)))){var o=[],i=!0,s=!1,a=void 0;try{for(var c,l=n[Symbol.iterator]();!(i=(c=l.next()).done)&&(o.push(c.value),!r||o.length!==r);i=!0);}catch(u){s=!0,a=u}finally{try{i||l.return==null||l.return()}finally{if(s)throw a}}return o}}(e,t)||Ml(e,t)||function(){throw new TypeError(`Invalid attempt to destructure non-iterable instance.
+See: https://github.com/francoischalifour/medium-zoom`)}},Dm=function(t){var n=document.createElement("div");return n.classList.add("medium-zoom-overlay"),n.style.background=t,n},Im=function(t){var n=t.getBoundingClientRect(),r=n.top,o=n.left,i=n.width,s=n.height,a=t.cloneNode(),c=window.pageYOffset||document.documentElement.scrollTop||document.body.scrollTop||0,l=window.pageXOffset||document.documentElement.scrollLeft||document.body.scrollLeft||0;return a.removeAttribute("id"),a.style.position="absolute",a.style.top=r+c+"px",a.style.left=o+l+"px",a.style.width=i+"px",a.style.height=s+"px",a.style.transform="",a},Zt=function(t,n){var r=kt({bubbles:!1,cancelable:!1,detail:void 0},n);if(typeof window.CustomEvent=="function")return new CustomEvent(t,r);var o=document.createEvent("CustomEvent");return o.initCustomEvent(t,r.bubbles,r.cancelable,r.detail),o},Am=function e(t){var n=arguments.length>1&&arguments[1]!==void 0?arguments[1]:{},r=window.Promise||function(I){function B(){}I(B,B)},o=function(I){var B=I.target;if(B===$){m();return}S.indexOf(B)!==-1&&v({target:B})},i=function(){if(!(T||!D.original)){var I=window.pageYOffset||document.documentElement.scrollTop||document.body.scrollTop||0;Math.abs(N-I)>A.scrollOffset&&setTimeout(m,150)}},s=function(I){var B=I.key||I.keyCode;(B==="Escape"||B==="Esc"||B===27)&&m()},a=function(){var I=arguments.length>0&&arguments[0]!==void 0?arguments[0]:{},B=I;if(I.background&&($.style.background=I.background),I.container&&I.container instanceof Object&&(B.container=kt({},A.container,I.container)),I.template){var Y=yr(I.template)?I.template:document.querySelector(I.template);B.template=Y}return A=kt({},A,B),S.forEach(function(ae){ae.dispatchEvent(Zt("medium-zoom:update",{detail:{zoom:F}}))}),F},c=function(){var I=arguments.length>0&&arguments[0]!==void 0?arguments[0]:{};return e(kt({},A,I))},l=function(){for(var I=arguments.length,B=Array(I),Y=0;Y0?B.reduce(function(J,ne){return[].concat(J,Bs(ne))},[]):S;return ae.forEach(function(J){J.classList.remove("medium-zoom-image"),J.dispatchEvent(Zt("medium-zoom:detach",{detail:{zoom:F}}))}),S=S.filter(function(J){return ae.indexOf(J)===-1}),F},d=function(I,B){var Y=arguments.length>2&&arguments[2]!==void 0?arguments[2]:{};return S.forEach(function(ae){ae.addEventListener("medium-zoom:"+I,B,Y)}),P.push({type:"medium-zoom:"+I,listener:B,options:Y}),F},f=function(I,B){var Y=arguments.length>2&&arguments[2]!==void 0?arguments[2]:{};return S.forEach(function(ae){ae.removeEventListener("medium-zoom:"+I,B,Y)}),P=P.filter(function(ae){return!(ae.type==="medium-zoom:"+I&&ae.listener.toString()===B.toString())}),F},h=function(){var I=arguments.length>0&&arguments[0]!==void 0?arguments[0]:{},B=I.target,Y=function(){var J={width:document.documentElement.clientWidth,height:document.documentElement.clientHeight,left:0,top:0,right:0,bottom:0},ne=void 0,re=void 0;if(A.container)if(A.container instanceof Object)J=kt({},J,A.container),ne=J.width-J.left-J.right-A.margin*2,re=J.height-J.top-J.bottom-A.margin*2;else{var Ee=yr(A.container)?A.container:document.querySelector(A.container),Pe=Ee.getBoundingClientRect(),Ie=Pe.width,we=Pe.height,Re=Pe.left,He=Pe.top;J=kt({},J,{width:Ie,height:we,left:Re,top:He})}ne=ne||J.width-A.margin*2,re=re||J.height-A.margin*2;var R=D.zoomedHd||D.original,U=Hs(R)?ne:R.naturalWidth||ne,M=Hs(R)?re:R.naturalHeight||re,q=R.getBoundingClientRect(),le=q.top,pe=q.left,oe=q.width,te=q.height,p=Math.min(U,ne)/oe,y=Math.min(M,re)/te,w=Math.min(p,y),C=(-pe+(ne-oe)/2+A.margin+J.left)/w,x=(-le+(re-te)/2+A.margin+J.top)/w,L="scale("+w+") translate3d("+C+"px, "+x+"px, 0)";D.zoomed.style.transform=L,D.zoomedHd&&(D.zoomedHd.style.transform=L)};return new r(function(ae){if(B&&S.indexOf(B)===-1){ae(F);return}var J=function Ie(){T=!1,D.zoomed.removeEventListener("transitionend",Ie),D.original.dispatchEvent(Zt("medium-zoom:opened",{detail:{zoom:F}})),ae(F)};if(D.zoomed){ae(F);return}if(B)D.original=B;else if(S.length>0){var ne=S;D.original=ne[0]}else{ae(F);return}if(D.original.dispatchEvent(Zt("medium-zoom:open",{detail:{zoom:F}})),N=window.pageYOffset||document.documentElement.scrollTop||document.body.scrollTop||0,T=!0,D.zoomed=Im(D.original),document.body.appendChild($),A.template){var re=yr(A.template)?A.template:document.querySelector(A.template);D.template=document.createElement("div"),D.template.appendChild(re.content.cloneNode(!0)),document.body.appendChild(D.template)}if(document.body.appendChild(D.zoomed),window.requestAnimationFrame(function(){document.body.classList.add("medium-zoom--opened")}),D.original.classList.add("medium-zoom-image--hidden"),D.zoomed.classList.add("medium-zoom-image--opened"),D.zoomed.addEventListener("click",m),D.zoomed.addEventListener("transitionend",J),D.original.getAttribute("data-zoom-src")){D.zoomedHd=D.zoomed.cloneNode(),D.zoomedHd.removeAttribute("srcset"),D.zoomedHd.removeAttribute("sizes"),D.zoomedHd.src=D.zoomed.getAttribute("data-zoom-src"),D.zoomedHd.onerror=function(){clearInterval(Ee),console.warn("Unable to reach the zoom image target "+D.zoomedHd.src),D.zoomedHd=null,Y()};var Ee=setInterval(function(){D.zoomedHd.complete&&(clearInterval(Ee),D.zoomedHd.classList.add("medium-zoom-image--opened"),D.zoomedHd.addEventListener("click",m),document.body.appendChild(D.zoomedHd),Y())},10)}else if(D.original.hasAttribute("srcset")){D.zoomedHd=D.zoomed.cloneNode(),D.zoomedHd.removeAttribute("sizes"),D.zoomedHd.removeAttribute("loading");var Pe=D.zoomedHd.addEventListener("load",function(){D.zoomedHd.removeEventListener("load",Pe),D.zoomedHd.classList.add("medium-zoom-image--opened"),D.zoomedHd.addEventListener("click",m),document.body.appendChild(D.zoomedHd),Y()})}else Y()})},m=function(){return new r(function(I){if(T||!D.original){I(F);return}var B=function Y(){D.original.classList.remove("medium-zoom-image--hidden"),document.body.removeChild(D.zoomed),D.zoomedHd&&document.body.removeChild(D.zoomedHd),document.body.removeChild($),D.zoomed.classList.remove("medium-zoom-image--opened"),D.template&&document.body.removeChild(D.template),T=!1,D.zoomed.removeEventListener("transitionend",Y),D.original.dispatchEvent(Zt("medium-zoom:closed",{detail:{zoom:F}})),D.original=null,D.zoomed=null,D.zoomedHd=null,D.template=null,I(F)};T=!0,document.body.classList.remove("medium-zoom--opened"),D.zoomed.style.transform="",D.zoomedHd&&(D.zoomedHd.style.transform=""),D.template&&(D.template.style.transition="opacity 150ms",D.template.style.opacity=0),D.original.dispatchEvent(Zt("medium-zoom:close",{detail:{zoom:F}})),D.zoomed.addEventListener("transitionend",B)})},v=function(){var I=arguments.length>0&&arguments[0]!==void 0?arguments[0]:{},B=I.target;return D.original?m():h({target:B})},_=function(){return A},g=function(){return S},E=function(){return D.original},S=[],P=[],T=!1,N=0,A=n,D={original:null,zoomed:null,zoomedHd:null,template:null};Object.prototype.toString.call(t)==="[object Object]"?A=t:(t||typeof t=="string")&&l(t),A=kt({margin:0,background:"#fff",scrollOffset:40,container:null,template:null},A);var $=Dm(A.background);document.addEventListener("click",o),document.addEventListener("keyup",s),document.addEventListener("scroll",i),window.addEventListener("resize",m);var F={open:h,close:m,toggle:v,update:a,clone:c,attach:l,detach:u,on:d,off:f,getOptions:_,getImages:g,getZoomedImage:E};return F};function Cm(e,t){t===void 0&&(t={});var n=t.insertAt;if(!(!e||typeof document=="undefined")){var r=document.head||document.getElementsByTagName("head")[0],o=document.createElement("style");o.type="text/css",n==="top"&&r.firstChild?r.insertBefore(o,r.firstChild):r.appendChild(o),o.styleSheet?o.styleSheet.cssText=e:o.appendChild(document.createTextNode(e))}}var Tm=".medium-zoom-overlay{position:fixed;top:0;right:0;bottom:0;left:0;opacity:0;transition:opacity .3s;will-change:opacity}.medium-zoom--opened .medium-zoom-overlay{cursor:pointer;cursor:zoom-out;opacity:1}.medium-zoom-image{cursor:pointer;cursor:zoom-in;transition:transform .3s cubic-bezier(.2,0,.2,1)!important}.medium-zoom-image--hidden{visibility:hidden}.medium-zoom-image--opened{position:relative;cursor:pointer;cursor:zoom-out;will-change:transform}";Cm(Tm);var Rm=Am;const xm=Symbol("mediumZoom");const Lm=".theme-default-content > img, .theme-default-content :not(a) > img",jm={},km=300;var Nm=nr(({app:e,router:t})=>{const n=Rm(jm);n.refresh=(r=Lm)=>{n.detach(),n.attach(r)},e.provide(xm,n),t.afterEach(()=>{setTimeout(()=>n.refresh(),km)})});const Mm={docsDir:"zopeneditor-docs",repo:"https://github.com/IBM/zopeneditor-about/issues",editLink:!1,lastUpdated:!0,sidebarDepth:2,navbar:[{text:"Docs",link:"/Docs/introduction"},{text:"News and Blogs",link:"/Blog/new-content"},{text:"IBM Downloads",link:"https://ibm.github.io/mainframe-downloads/downloads.html"},{text:"VS Code Marketplace",link:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor"}],sidebar:{"/Docs/":[{text:"Overview",collapsible:!0,children:["introduction","whatsnew"]},{text:"Getting Started",collapsible:!0,children:["getting_started","setup_integration","zopeneditor_v3","zowe_explorer_v2"]},{text:"Configuration",collapsible:!0,children:["setting_preferences","zapp","setting_propertygroup","setting_compiler_options","setting_fileassociations","setting_tabstops","setting_disableproblems","setting_unreachablecodewarnings","customizing_the_outline_view","setting_maximum_line_length","ebcdic_encoding","zcodeformatting"]},{text:"Tutorials",collapsible:!0,children:["tutorial_overview","userinterface","samplefiles","tutorial_cobol","tutorial_assembler","tutorial_rexx","rse_tutorial","zowe_submitjcl"]},{text:"Editing program files",collapsible:!0,children:["language_references","editor_codechanges","editor_codechanges_hlasm","editor_codechanges_rexx","editor_codechanges_jcl","snippets","git_integration","editor_search"]},{text:"Interacting with z/OS using Zowe",collapsible:!0,children:["interact_zos_overview","connect_to_zos_with_zowe_explorer_e2e","connect_to_zos_with_zowe_cli_e2e","interact_zos_zopeneditor","zowe_advanced_connection_scenarious","sharing_team_configuration_files","interact_zos_cli","interact_common_properties_cli","interact_zos_zowe_explorer","migrating_profiles","creating_team_profiles"]},{text:"Advanced Capabilities",collapsible:!0,children:["advanced_overview","advanced_activation","advanced_resource_table","advanced_preprocessor","advanced_problems_view","advanced_custom_macros"]},{text:"Troubleshooting",collapsible:!0,children:["knownissues","locating_local_client_logs","uninstalling"]},{text:"Reference",collapsible:!0,children:["rse_cli_command","shortcut","settings","other_extensions"]},{text:"Legal information",collapsible:!0,children:["notices","trademarks","privacypolicy"]}],"/Blog/":[{text:"What's New",collapsible:!0,children:["new-content","new-releases"]},{text:"Team Blog",collapsible:!0,children:["announcing-zos-resources-table","announcing-jcl","whats-new-120","announcing-rexx","rse-march-120","userbuild-blog","ocp-ssl-cert","rse-october-110","ibm-wazi-development-client-introduction-blog","hlasm-blog","rse-march-beta","code-snippets","in-the-cloud-with-che","web-based-with-theia"]},{text:"Other Resources",collapsible:!1,children:["learning"]}]},darkMode:!0,locales:{"/":{selectLanguageName:"English"}},logo:null,selectLanguageText:"Languages",selectLanguageAriaLabel:"Select language",editLinkText:"Edit this page",lastUpdatedText:"Last Updated",contributors:!0,contributorsText:"Contributors",notFound:["There's nothing here.","How did we get here?","That's a Four-Oh-Four.","Looks like we've got some broken links."],backToHome:"Take me home",openInNewWindow:"open in new window",toggleDarkMode:"toggle dark mode",toggleSidebar:"toggle sidebar"},Cl=Ne(Mm),zm=()=>Cl;Hi.webpackHot&&(__VUE_HMR_RUNTIME__.updateThemeData=e=>{Cl.value=e});const Tl=Symbol(""),Vm=()=>{const e=Te(Tl);if(!e)throw new Error("useThemeLocaleData() is called without provider.");return e},Hm=(e,t)=>{var n;return je(je({},e),(n=e.locales)===null||n===void 0?void 0:n[t])};var Bm=nr(({app:e})=>{const t=zm(),n=e._context.provides[Li],r=Oe(()=>Hm(t.value,n.value));e.provide(Tl,r),Object.defineProperties(e.config.globalProperties,{$theme:{get(){return t.value}},$themeLocale:{get(){return r.value}}})});const Fm=Qe({props:{type:{type:String,required:!1,default:"tip"},text:{type:String,required:!1,default:""},vertical:{type:String,required:!1,default:void 0}},setup(e){return(t,n)=>(Xr(),Zc("span",{class:Yn(["badge",e.type]),style:Kr({verticalAlign:e.vertical})},[Xc(t.$slots,"default",{},()=>[Di(Tu(e.text),1)])],6))}});var Um=Qe({name:"CodeGroup",setup(e,{slots:t}){const n=Ne(-1),r=Ne([]),o=(a=n.value)=>{a{a>0?n.value=a-1:n.value=r.value.length-1,r.value[n.value].focus()},s=(a,c)=>{a.key===" "||a.key==="Enter"?(a.preventDefault(),n.value=c):a.key==="ArrowRight"?(a.preventDefault(),o(c)):a.key==="ArrowLeft"&&(a.preventDefault(),i(c))};return()=>{var a;const c=(((a=t.default)===null||a===void 0?void 0:a.call(t))||[]).filter(l=>l.type.name==="CodeGroupItem").map(l=>(l.props===null&&(l.props={}),l));return c.length===0?null:(n.value<0||n.value>c.length-1?(n.value=c.findIndex(l=>l.props.active===""||l.props.active===!0),n.value===-1&&(n.value=0)):c.forEach((l,u)=>{l.props.active=u===n.value}),be("div",{class:"code-group"},[be("div",{class:"code-group__nav"},be("ul",{class:"code-group__ul"},c.map((l,u)=>{const d=u===n.value;return be("li",{class:"code-group__li"},be("button",{ref:f=>{f&&(r.value[u]=f)},class:{"code-group__nav-tab":!0,"code-group__nav-tab-active":d},ariaPressed:d,ariaExpanded:d,onClick:()=>n.value=u,onKeydown:f=>s(f,u)},l.props.title))}))),c]))}}});const $m=["aria-selected"],qm=Qe({name:"CodeGroupItem"}),Km=Qe(At(je({},qm),{props:{title:{type:String,required:!0},active:{type:Boolean,required:!1,default:!1}},setup(e){return(t,n)=>(Xr(),Zc("div",{class:Yn(["code-group-item",{"code-group-item__active":e.active}]),"aria-selected":e.active},[Xc(t.$slots,"default")],10,$m))}}));function Rl(e){return Hu()?(Bu(e),!0):!1}const rr=typeof window!="undefined",Wm=e=>typeof e=="string",go=()=>{};function Zm(e,t){function n(...r){e(()=>t.apply(this,r),{fn:t,thisArg:this,args:r})}return n}const Jm=e=>e();var Fs=Object.getOwnPropertySymbols,Qm=Object.prototype.hasOwnProperty,Ym=Object.prototype.propertyIsEnumerable,Xm=(e,t)=>{var n={};for(var r in e)Qm.call(e,r)&&t.indexOf(r)<0&&(n[r]=e[r]);if(e!=null&&Fs)for(var r of Fs(e))t.indexOf(r)<0&&Ym.call(e,r)&&(n[r]=e[r]);return n};function Gm(e,t,n={}){const r=n,{eventFilter:o=Jm}=r,i=Xm(r,["eventFilter"]);return et(e,Zm(o,t),i)}function eh(e,t=!0){el()?at(e):t?e():yi(e)}const Mr=rr?window:void 0;rr&&window.document;rr&&window.navigator;rr&&window.location;function th(...e){let t,n,r,o;if(Wm(e[0])?([n,r,o]=e,t=Mr):[t,n,r,o]=e,!t)return go;let i=go;const s=et(()=>Ht(t),c=>{i(),c&&(c.addEventListener(n,r,o),i=()=>{c.removeEventListener(n,r,o),i=go})},{immediate:!0,flush:"post"}),a=()=>{s(),i()};return Rl(a),a}function nh(e,t={}){const{window:n=Mr}=t;let r;const o=Ne(!1),i=()=>{!n||(r||(r=n.matchMedia(e)),o.value=r.matches)};return eh(()=>{i(),r&&("addEventListener"in r?r.addEventListener("change",i):r.addListener(i),Rl(()=>{"removeEventListener"in i?r.removeEventListener("change",i):r.removeListener(i)}))}),o}const Uo=typeof globalThis!="undefined"?globalThis:typeof window!="undefined"?window:typeof global!="undefined"?global:typeof self!="undefined"?self:{},$o="__vueuse_ssr_handlers__";Uo[$o]=Uo[$o]||{};const rh=Uo[$o];function oh(e,t){return rh[e]||t}function ih(e){return e==null?"any":e instanceof Set?"set":e instanceof Map?"map":typeof e=="boolean"?"boolean":typeof e=="string"?"string":typeof e=="object"||Array.isArray(e)?"object":Number.isNaN(e)?"any":"number"}const sh={boolean:{read:e=>e==="true",write:e=>String(e)},object:{read:e=>JSON.parse(e),write:e=>JSON.stringify(e)},number:{read:e=>Number.parseFloat(e),write:e=>String(e)},any:{read:e=>e,write:e=>String(e)},string:{read:e=>e,write:e=>String(e)},map:{read:e=>new Map(JSON.parse(e)),write:e=>JSON.stringify(Array.from(e.entries()))},set:{read:e=>new Set(JSON.parse(e)),write:e=>JSON.stringify(Array.from(e.entries()))}};function ah(e,t,n,r={}){var o;const{flush:i="pre",deep:s=!0,listenToStorageChanges:a=!0,writeDefaults:c=!0,shallow:l,window:u=Mr,eventFilter:d,onError:f=E=>{console.error(E)}}=r,h=Ht(t),m=ih(h),v=(l?Ec:Ne)(t),_=(o=r.serializer)!=null?o:sh[m];if(!n)try{n=oh("getDefaultStorage",()=>{var E;return(E=Mr)==null?void 0:E.localStorage})()}catch(E){f(E)}function g(E){if(!(!n||E&&E.key!==e))try{const S=E?E.newValue:n.getItem(e);S==null?(v.value=h,c&&h!==null&&n.setItem(e,_.write(h))):typeof S!="string"?v.value=S:v.value=_.read(S)}catch(S){f(S)}}return g(),u&&a&&th(u,"storage",E=>setTimeout(()=>g(E),0)),n&&Gm(v,()=>{try{v.value==null?n.removeItem(e):n.setItem(e,_.write(v.value))}catch(E){f(E)}},{flush:i,deep:s,eventFilter:d}),v}function ch(e){return nh("(prefers-color-scheme: dark)",e)}var Us,$s;rr&&(window==null?void 0:window.navigator)&&((Us=window==null?void 0:window.navigator)==null?void 0:Us.platform)&&/iP(ad|hone|od)/.test(($s=window==null?void 0:window.navigator)==null?void 0:$s.platform);var lh=Object.defineProperty,qs=Object.getOwnPropertySymbols,uh=Object.prototype.hasOwnProperty,fh=Object.prototype.propertyIsEnumerable,Ks=(e,t,n)=>t in e?lh(e,t,{enumerable:!0,configurable:!0,writable:!0,value:n}):e[t]=n,dh=(e,t)=>{for(var n in t||(t={}))uh.call(t,n)&&Ks(e,n,t[n]);if(qs)for(var n of qs(t))fh.call(t,n)&&Ks(e,n,t[n]);return e};const ph={top:0,left:0,bottom:0,right:0,height:0,width:0};dh({text:""},ph);const xl=Symbol(""),Og=()=>{const e=Te(xl);if(!e)throw new Error("useDarkMode() is called without provider.");return e},mh=()=>{const e=Nl(),t=ch(),n=ah("vuepress-color-scheme","auto"),r=Oe({get(){return e.value.darkMode?n.value==="auto"?t.value:n.value==="dark":!1},set(o){o===t.value?n.value="auto":n.value=o?"dark":"light"}});Bt(xl,r),hh(r)},hh=e=>{const t=(n=e.value)=>{const r=window==null?void 0:window.document.querySelector("html");r==null||r.classList.toggle("dark",n)};at(()=>{et(e,t,{immediate:!0})}),Si(()=>t())},Ll=(...e)=>{const n=no().resolve(...e),r=n.matched[n.matched.length-1];if(!(r!=null&&r.redirect))return n;const{redirect:o}=r,i=ie(o)?o(n):o,s=ve(i)?{path:i}:i;return Ll(je({hash:n.hash,query:n.query,params:n.params},s))},_h=e=>{const t=Ll(e);return{text:t.meta.title||e,link:t.name==="404"?e:t.fullPath}};let yo=null,On=null;const vh={wait:()=>yo,pending:()=>{yo=new Promise(e=>On=e)},resolve:()=>{On==null||On(),yo=null,On=null}},gh=()=>vh,jl=Symbol("sidebarItems"),wg=()=>{const e=Te(jl);if(!e)throw new Error("useSidebarItems() is called without provider.");return e},yh=()=>{const e=Nl(),t=cm(),n=Oe(()=>bh(t.value,e.value));Bt(jl,n)},bh=(e,t)=>{var n,r,o,i;const s=(r=(n=e.sidebar)!==null&&n!==void 0?n:t.sidebar)!==null&&r!==void 0?r:"auto",a=(i=(o=e.sidebarDepth)!==null&&o!==void 0?o:t.sidebarDepth)!==null&&i!==void 0?i:2;return e.home||s===!1?[]:s==="auto"?Oh(a):ee(s)?kl(s,a):Il(s)?wh(s,a):[]},Eh=(e,t)=>({text:e.title,link:`#${e.slug}`,children:Ni(e.children,t)}),Ni=(e,t)=>t>0?e.map(n=>Eh(n,t-1)):[],Oh=e=>{const t=tr();return[{text:t.value.title,children:Ni(t.value.headers,e)}]},kl=(e,t)=>{const n=xi(),r=tr(),o=i=>{var s;let a;if(ve(i)?a=_h(i):a=i,a.children)return At(je({},a),{children:a.children.map(c=>o(c))});if(a.link===n.path){const c=((s=r.value.headers[0])===null||s===void 0?void 0:s.level)===1?r.value.headers[0].children:r.value.headers;return At(je({},a),{children:Ni(c,t)})}return a};return e.map(i=>o(i))},wh=(e,t)=>{var n;const r=xi(),o=Al(e,r.path),i=(n=e[o])!==null&&n!==void 0?n:[];return kl(i,t)},Nl=()=>Vm();var Sh=nr(({app:e,router:t})=>{e.component("Badge",Fm),e.component("CodeGroup",Um),e.component("CodeGroupItem",Km),e.component("NavbarSearch",()=>{const r=e.component("Docsearch")||e.component("SearchBox");return r?be(r):null});const n=t.options.scrollBehavior;t.options.scrollBehavior=async(...r)=>(await gh().wait(),n(...r))});/*! @docsearch/js 3.0.0-alpha.42 | MIT License | © Algolia, Inc. and contributors | https://docsearch.algolia.com */function Kn(e){return Kn=typeof Symbol=="function"&&typeof Symbol.iterator=="symbol"?function(t){return typeof t}:function(t){return t&&typeof Symbol=="function"&&t.constructor===Symbol&&t!==Symbol.prototype?"symbol":typeof t},Kn(e)}function Ph(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function qo(){return qo=Object.assign||function(e){for(var t=1;t=0||(u[c]=s[c]);return u}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}function zr(e,t){return function(n){if(Array.isArray(n))return n}(e)||function(n,r){if(!(typeof Symbol=="undefined"||!(Symbol.iterator in Object(n)))){var o=[],i=!0,s=!1,a=void 0;try{for(var c,l=n[Symbol.iterator]();!(i=(c=l.next()).done)&&(o.push(c.value),!r||o.length!==r);i=!0);}catch(u){s=!0,a=u}finally{try{i||l.return==null||l.return()}finally{if(s)throw a}}return o}}(e,t)||Ml(e,t)||function(){throw new TypeError(`Invalid attempt to destructure non-iterable instance.
 In order to be iterable, non-array objects must have a [Symbol.iterator]() method.`)}()}function Vr(e){return function(t){if(Array.isArray(t))return Ko(t)}(e)||function(t){if(typeof Symbol!="undefined"&&Symbol.iterator in Object(t))return Array.from(t)}(e)||Ml(e)||function(){throw new TypeError(`Invalid attempt to spread non-iterable instance.
 In order to be iterable, non-array objects must have a [Symbol.iterator]() method.`)}()}function Ml(e,t){if(e){if(typeof e=="string")return Ko(e,t);var n=Object.prototype.toString.call(e).slice(8,-1);return n==="Object"&&e.constructor&&(n=e.constructor.name),n==="Map"||n==="Set"?Array.from(e):n==="Arguments"||/^(?:Ui|I)nt(?:8|16|32)(?:Clamped)?Array$/.test(n)?Ko(e,t):void 0}}function Ko(e,t){(t==null||t>e.length)&&(t=e.length);for(var n=0,r=new Array(t);n3)for(n=[n],i=3;i0?zn(h.type,h.props,h.key,null,h.__v):h)!=null){if(h.__=n,h.__b=n.__b+1,(f=g[u])===null||f&&h.key==f.key&&h.type===f.type)g[u]=void 0;else for(d=0;d3)for(n=[n],i=3;i=n.__.length&&n.__.push({}),n.__[e]}function oa(e,t,n){var r=Jn(pn++,2);return r.t=e,r.__c||(r.__=[n?n(t):Jl(void 0,t),function(o){var i=r.t(r.__[0],o);r.__[0]!==i&&(r.__=[i,r.__[1]],r.__c.setState({}))}],r.__c=Me),r.__}function ia(e,t){var n=Jn(pn++,4);!X.__s&&Vi(n.__H,t)&&(n.__=e,n.__H=t,Me.__h.push(n))}function br(e,t){var n=Jn(pn++,7);return Vi(n.__H,t)&&(n.__=e(),n.__H=t,n.__h=e),n.__}function Rh(){Zo.forEach(function(e){if(e.__P)try{e.__H.__h.forEach(Er),e.__H.__h.forEach(Jo),e.__H.__h=[]}catch(t){e.__H.__h=[],X.__e(t,e.__v)}}),Zo=[]}X.__b=function(e){Me=null,Gs&&Gs(e)},X.__r=function(e){ea&&ea(e),pn=0;var t=(Me=e.__c).__H;t&&(t.__h.forEach(Er),t.__h.forEach(Jo),t.__h=[])},X.diffed=function(e){ta&&ta(e);var t=e.__c;t&&t.__H&&t.__H.__h.length&&(Zo.push(t)!==1&&Xs===X.requestAnimationFrame||((Xs=X.requestAnimationFrame)||function(n){var r,o=function(){clearTimeout(i),sa&&cancelAnimationFrame(r),setTimeout(n)},i=setTimeout(o,100);sa&&(r=requestAnimationFrame(o))})(Rh)),Me=void 0},X.__c=function(e,t){t.some(function(n){try{n.__h.forEach(Er),n.__h=n.__h.filter(function(r){return!r.__||Jo(r)})}catch(r){t.some(function(o){o.__h&&(o.__h=[])}),t=[],X.__e(r,n.__v)}}),na&&na(e,t)},X.unmount=function(e){ra&&ra(e);var t=e.__c;if(t&&t.__H)try{t.__H.__.forEach(Er)}catch(n){X.__e(n,t.__v)}};var sa=typeof requestAnimationFrame=="function";function Er(e){var t=Me;typeof e.__c=="function"&&e.__c(),Me=t}function Jo(e){var t=Me;e.__c=e.__(),Me=t}function Vi(e,t){return!e||e.length!==t.length||t.some(function(n,r){return n!==e[r]})}function Jl(e,t){return typeof t=="function"?t(e):t}function Ql(e,t){for(var n in t)e[n]=t[n];return e}function Qo(e,t){for(var n in e)if(n!=="__source"&&!(n in t))return!0;for(var r in t)if(r!=="__source"&&e[r]!==t[r])return!0;return!1}function Yo(e){this.props=e}(Yo.prototype=new it).isPureReactComponent=!0,Yo.prototype.shouldComponentUpdate=function(e,t){return Qo(this.props,e)||Qo(this.state,t)};var aa=X.__b;X.__b=function(e){e.type&&e.type.__f&&e.ref&&(e.props.ref=e.ref,e.ref=null),aa&&aa(e)};var xh=typeof Symbol!="undefined"&&Symbol.for&&Symbol.for("react.forward_ref")||3911,ca=function(e,t){return e==null?null:dt(dt(e).map(t))},Lh={map:ca,forEach:ca,count:function(e){return e?dt(e).length:0},only:function(e){var t=dt(e);if(t.length!==1)throw"Children.only";return t[0]},toArray:dt},jh=X.__e;function Or(){this.__u=0,this.t=null,this.__b=null}function Yl(e){var t=e.__.__c;return t&&t.__e&&t.__e(e)}function An(){this.u=null,this.o=null}X.__e=function(e,t,n){if(e.then){for(var r,o=t;o=o.__;)if((r=o.__c)&&r.__c)return t.__e==null&&(t.__e=n.__e,t.__k=n.__k),r.__c(e,t)}jh(e,t,n)},(Or.prototype=new it).__c=function(e,t){var n=t.__c,r=this;r.t==null&&(r.t=[]),r.t.push(n);var o=Yl(r.__v),i=!1,s=function(){i||(i=!0,n.componentWillUnmount=n.__c,o?o(a):a())};n.__c=n.componentWillUnmount,n.componentWillUnmount=function(){s(),n.__c&&n.__c()};var a=function(){if(!--r.__u){if(r.state.__e){var l=r.state.__e;r.__v.__k[0]=function d(f,h,m){return f&&(f.__v=null,f.__k=f.__k&&f.__k.map(function(v){return d(v,h,m)}),f.__c&&f.__c.__P===h&&(f.__e&&m.insertBefore(f.__e,f.__d),f.__c.__e=!0,f.__c.__P=m)),f}(l,l.__c.__P,l.__c.__O)}var u;for(r.setState({__e:r.__b=null});u=r.t.pop();)u.forceUpdate()}},c=t.__h===!0;r.__u++||c||r.setState({__e:r.__b=r.__v.__k[0]}),e.then(s,s)},Or.prototype.componentWillUnmount=function(){this.t=[]},Or.prototype.render=function(e,t){if(this.__b){if(this.__v.__k){var n=document.createElement("div"),r=this.__v.__k[0].__c;this.__v.__k[0]=function i(s,a,c){return s&&(s.__c&&s.__c.__H&&(s.__c.__H.__.forEach(function(l){typeof l.__c=="function"&&l.__c()}),s.__c.__H=null),(s=Ql({},s)).__c!=null&&(s.__c.__P===c&&(s.__c.__P=a),s.__c=null),s.__k=s.__k&&s.__k.map(function(l){return i(l,a,c)})),s}(this.__b,n,r.__O=r.__P)}this.__b=null}var o=t.__e&&ot(It,null,e.fallback);return o&&(o.__h=null),[ot(It,null,t.__e?null:e.children),o]};var la=function(e,t,n){if(++n[1]===n[0]&&e.o.delete(t),e.props.revealOrder&&(e.props.revealOrder[0]!=="t"||!e.o.size))for(n=e.u;n;){for(;n.length>3;)n.pop()();if(n[1]>>1,1),t.i.removeChild(r)}}),Zn(ot(kh,{context:t.context},e.__v),t.l)):t.l&&t.componentWillUnmount()}function Xl(e,t){return ot(Nh,{__v:e,i:t})}(An.prototype=new it).__e=function(e){var t=this,n=Yl(t.__v),r=t.o.get(e);return r[0]++,function(o){var i=function(){t.props.revealOrder?(r.push(o),la(t,e,r)):o()};n?n(i):i()}},An.prototype.render=function(e){this.u=null,this.o=new Map;var t=dt(e.children);e.revealOrder&&e.revealOrder[0]==="b"&&t.reverse();for(var n=t.length;n--;)this.o.set(t[n],this.u=[1,0,this.u]);return e.children},An.prototype.componentDidUpdate=An.prototype.componentDidMount=function(){var e=this;this.o.forEach(function(t,n){la(e,n,t)})};var Gl=typeof Symbol!="undefined"&&Symbol.for&&Symbol.for("react.element")||60103,Mh=/^(?:accent|alignment|arabic|baseline|cap|clip(?!PathU)|color|fill|flood|font|glyph(?!R)|horiz|marker(?!H|W|U)|overline|paint|stop|strikethrough|stroke|text(?!L)|underline|unicode|units|v|vector|vert|word|writing|x(?!C))[A-Z]/,zh=function(e){return(typeof Symbol!="undefined"&&Kn(Symbol())=="symbol"?/fil|che|rad/i:/fil|che|ra/i).test(e)};function eu(e,t,n){return t.__k==null&&(t.textContent=""),Zn(e,t),typeof n=="function"&&n(),e?e.__c:null}it.prototype.isReactComponent={},["componentWillMount","componentWillReceiveProps","componentWillUpdate"].forEach(function(e){Object.defineProperty(it.prototype,e,{configurable:!0,get:function(){return this["UNSAFE_"+e]},set:function(t){Object.defineProperty(this,e,{configurable:!0,writable:!0,value:t})}})});var ua=X.event;function Vh(){}function Hh(){return this.cancelBubble}function Bh(){return this.defaultPrevented}X.event=function(e){return ua&&(e=ua(e)),e.persist=Vh,e.isPropagationStopped=Hh,e.isDefaultPrevented=Bh,e.nativeEvent=e};var tu,fa={configurable:!0,get:function(){return this.class}},da=X.vnode;X.vnode=function(e){var t=e.type,n=e.props,r=n;if(typeof t=="string"){for(var o in r={},n){var i=n[o];o==="value"&&"defaultValue"in n&&i==null||(o==="defaultValue"&&"value"in n&&n.value==null?o="value":o==="download"&&i===!0?i="":/ondoubleclick/i.test(o)?o="ondblclick":/^onchange(textarea|input)/i.test(o+t)&&!zh(n.type)?o="oninput":/^on(Ani|Tra|Tou|BeforeInp)/.test(o)?o=o.toLowerCase():Mh.test(o)?o=o.replace(/[A-Z0-9]/,"-$&").toLowerCase():i===null&&(i=void 0),r[o]=i)}t=="select"&&r.multiple&&Array.isArray(r.value)&&(r.value=dt(n.children).forEach(function(s){s.props.selected=r.value.indexOf(s.props.value)!=-1})),t=="select"&&r.defaultValue!=null&&(r.value=dt(n.children).forEach(function(s){s.props.selected=r.multiple?r.defaultValue.indexOf(s.props.value)!=-1:r.defaultValue==s.props.value})),e.props=r}t&&n.class!=n.className&&(fa.enumerable="className"in n,n.className!=null&&(r.class=n.className),Object.defineProperty(r,"className",fa)),e.$$typeof=Gl,da&&da(e)};var pa=X.__r;X.__r=function(e){pa&&pa(e),tu=e.__c};var Fh={ReactCurrentDispatcher:{current:{readContext:function(e){return tu.__n[e.__c].props.value}}}};(typeof performance=="undefined"?"undefined":Kn(performance))=="object"&&typeof performance.now=="function"&&performance.now.bind(performance);function ma(e){return!!e&&e.$$typeof===Gl}var b={useState:function(e){return tn=1,oa(Jl,e)},useReducer:oa,useEffect:function(e,t){var n=Jn(pn++,3);!X.__s&&Vi(n.__H,t)&&(n.__=e,n.__H=t,Me.__H.__h.push(n))},useLayoutEffect:ia,useRef:function(e){return tn=5,br(function(){return{current:e}},[])},useImperativeHandle:function(e,t,n){tn=6,ia(function(){typeof e=="function"?e(t()):e&&(e.current=t())},n==null?n:n.concat(e))},useMemo:br,useCallback:function(e,t){return tn=8,br(function(){return e},t)},useContext:function(e){var t=Me.context[e.__c],n=Jn(pn++,9);return n.__c=e,t?(n.__==null&&(n.__=!0,t.sub(Me)),t.props.value):e.__},useDebugValue:function(e,t){X.useDebugValue&&X.useDebugValue(t?t(e):e)},version:"16.8.0",Children:Lh,render:eu,hydrate:function(e,t,n){return Zl(e,t),typeof n=="function"&&n(),e?e.__c:null},unmountComponentAtNode:function(e){return!!e.__k&&(Zn(null,e),!0)},createPortal:Xl,createElement:ot,createContext:function(e,t){var n={__c:t="__cC"+Vl++,__:e,Consumer:function(r,o){return r.children(o)},Provider:function(r){var o,i;return this.getChildContext||(o=[],(i={})[t]=this,this.getChildContext=function(){return i},this.shouldComponentUpdate=function(s){this.props.value!==s.value&&o.some(Wo)},this.sub=function(s){o.push(s);var a=s.componentWillUnmount;s.componentWillUnmount=function(){o.splice(o.indexOf(s),1),a&&a.call(s)}}),r.children}};return n.Provider.__=n.Consumer.contextType=n},createFactory:function(e){return ot.bind(null,e)},cloneElement:function(e){return ma(e)?Th.apply(null,arguments):e},createRef:function(){return{current:null}},Fragment:It,isValidElement:ma,findDOMNode:function(e){return e&&(e.base||e.nodeType===1&&e)||null},Component:it,PureComponent:Yo,memo:function(e,t){function n(o){var i=this.props.ref,s=i==o.ref;return!s&&i&&(i.call?i(null):i.current=null),t?!t(this.props,o)||!s:Qo(this.props,o)}function r(o){return this.shouldComponentUpdate=n,ot(e,o)}return r.displayName="Memo("+(e.displayName||e.name)+")",r.prototype.isReactComponent=!0,r.__f=!0,r},forwardRef:function(e){function t(n,r){var o=Ql({},n);return delete o.ref,e(o,(r=n.ref||r)&&(Kn(r)!="object"||"current"in r)?r:null)}return t.$$typeof=xh,t.render=t,t.prototype.isReactComponent=t.__f=!0,t.displayName="ForwardRef("+(e.displayName||e.name)+")",t},unstable_batchedUpdates:function(e,t){return e(t)},StrictMode:It,Suspense:Or,SuspenseList:An,lazy:function(e){var t,n,r;function o(i){if(t||(t=e()).then(function(s){n=s.default||s},function(s){r=s}),r)throw r;if(!n)throw t;return ot(n,i)}return o.displayName="Lazy",o.__f=!0,o},__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED:Fh};function Uh(){return b.createElement("svg",{width:"15",height:"15",className:"DocSearch-Control-Key-Icon"},b.createElement("path",{d:"M4.505 4.496h2M5.505 5.496v5M8.216 4.496l.055 5.993M10 7.5c.333.333.5.667.5 1v2M12.326 4.5v5.996M8.384 4.496c1.674 0 2.116 0 2.116 1.5s-.442 1.5-2.116 1.5M3.205 9.303c-.09.448-.277 1.21-1.241 1.203C1 10.5.5 9.513.5 8V7c0-1.57.5-2.5 1.464-2.494.964.006 1.134.598 1.24 1.342M12.553 10.5h1.953",strokeWidth:"1.2",stroke:"currentColor",fill:"none",strokeLinecap:"square"}))}function nu(){return b.createElement("svg",{width:"20",height:"20",className:"DocSearch-Search-Icon",viewBox:"0 0 20 20"},b.createElement("path",{d:"M14.386 14.386l4.0877 4.0877-4.0877-4.0877c-2.9418 2.9419-7.7115 2.9419-10.6533 0-2.9419-2.9418-2.9419-7.7115 0-10.6533 2.9418-2.9419 7.7115-2.9419 10.6533 0 2.9419 2.9418 2.9419 7.7115 0 10.6533z",stroke:"currentColor",fill:"none",fillRule:"evenodd",strokeLinecap:"round",strokeLinejoin:"round"}))}var $h=["translations"];function Xo(){return Xo=Object.assign||function(e){for(var t=1;t=0||(u[c]=s[c]);return u}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}var Kh=b.forwardRef(function(e,t){var n=e.translations,r=n===void 0?{}:n,o=qh(e,$h),i=r.buttonText,s=i===void 0?"Search":i,a=r.buttonAriaLabel,c=a===void 0?"Search":a,l=br(function(){return typeof navigator!="undefined"?/(Mac|iPhone|iPod|iPad)/i.test(navigator.platform)?"\u2318":"Ctrl":null},[]);return b.createElement("button",Xo({type:"button",className:"DocSearch DocSearch-Button","aria-label":c},o,{ref:t}),b.createElement("span",{className:"DocSearch-Button-Container"},b.createElement(nu,null),b.createElement("span",{className:"DocSearch-Button-Placeholder"},s)),b.createElement("span",{className:"DocSearch-Button-Keys"},l!==null&&b.createElement(b.Fragment,null,b.createElement("span",{className:"DocSearch-Button-Key"},l==="Ctrl"?b.createElement(Uh,null):l),b.createElement("span",{className:"DocSearch-Button-Key"},"K"))))});function Qn(e){return e.reduce(function(t,n){return t.concat(n)},[])}var Wh=0;function Go(e){return e.collections.length===0?0:e.collections.reduce(function(t,n){return t+n.items.length},0)}var Zh=function(){},Jh=[{segment:"autocomplete-core",version:"1.5.0"}];function ha(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter(function(o){return Object.getOwnPropertyDescriptor(e,o).enumerable})),n.push.apply(n,r)}return n}function Qh(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function Yh(e,t,n){var r=t.initialState;return{getState:function(){return r},dispatch:function(o,i){var s=function(a){for(var c=1;c=n?r===null?null:0:o}function ga(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter(function(o){return Object.getOwnPropertyDescriptor(e,o).enumerable})),n.push.apply(n,r)}return n}function Gh(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function e_(e,t){var n=[];return Promise.resolve(e(t)).then(function(r){return Promise.all(r.filter(function(o){return Boolean(o)}).map(function(o){if(o.sourceId,n.includes(o.sourceId))throw new Error("[Autocomplete] The `sourceId` ".concat(JSON.stringify(o.sourceId)," is not unique."));n.push(o.sourceId);var i=function(s){for(var a=1;ae.length)&&(t=e.length);for(var n=0,r=new Array(t);ne.length)&&(t=e.length);for(var n=0,r=new Array(t);n|<\/mark>)/g,Q_=RegExp(iu.source);function su(e){var t,n,r,o,i,s=e;if(!s.__docsearch_parent&&!e._highlightResult)return e.hierarchy.lvl0;var a=((s.__docsearch_parent?(t=s.__docsearch_parent)===null||t===void 0||(n=t._highlightResult)===null||n===void 0||(r=n.hierarchy)===null||r===void 0?void 0:r.lvl0:(o=e._highlightResult)===null||o===void 0||(i=o.hierarchy)===null||i===void 0?void 0:i.lvl0)||{}).value;return a&&Q_.test(a)?a.replace(iu,""):a}function ni(){return ni=Object.assign||function(e){for(var t=1;t=0||(u[c]=s[c]);return u}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}function ev(e){var t=e.translations,n=t===void 0?{}:t,r=G_(e,X_),o=n.recentSearchesTitle,i=o===void 0?"Recent":o,s=n.noRecentSearchesText,a=s===void 0?"No recent searches":s,c=n.saveRecentSearchButtonTitle,l=c===void 0?"Save this search":c,u=n.removeRecentSearchButtonTitle,d=u===void 0?"Remove this search from history":u,f=n.favoriteSearchesTitle,h=f===void 0?"Favorite":f,m=n.removeFavoriteSearchButtonTitle,v=m===void 0?"Remove this search from favorites":m;return r.state.status==="idle"&&r.hasCollections===!1?r.disableUserPersonalization?null:b.createElement("div",{className:"DocSearch-StartScreen"},b.createElement("p",{className:"DocSearch-Help"},a)):r.hasCollections===!1?null:b.createElement("div",{className:"DocSearch-Dropdown-Container"},b.createElement(ti,Ur({},r,{title:i,collection:r.state.collections[0],renderIcon:function(){return b.createElement("div",{className:"DocSearch-Hit-icon"},b.createElement(x_,null))},renderAction:function(_){var g=_.item,E=_.runFavoriteTransition,S=_.runDeleteTransition;return b.createElement(b.Fragment,null,b.createElement("div",{className:"DocSearch-Hit-action"},b.createElement("button",{className:"DocSearch-Hit-action-button",title:l,type:"submit",onClick:function(P){P.preventDefault(),P.stopPropagation(),E(function(){r.favoriteSearches.add(g),r.recentSearches.remove(g),r.refresh()})}},b.createElement(La,null))),b.createElement("div",{className:"DocSearch-Hit-action"},b.createElement("button",{className:"DocSearch-Hit-action-button",title:d,type:"submit",onClick:function(P){P.preventDefault(),P.stopPropagation(),S(function(){r.recentSearches.remove(g),r.refresh()})}},b.createElement(ei,null))))}})),b.createElement(ti,Ur({},r,{title:h,collection:r.state.collections[1],renderIcon:function(){return b.createElement("div",{className:"DocSearch-Hit-icon"},b.createElement(La,null))},renderAction:function(_){var g=_.item,E=_.runDeleteTransition;return b.createElement("div",{className:"DocSearch-Hit-action"},b.createElement("button",{className:"DocSearch-Hit-action-button",title:v,type:"submit",onClick:function(S){S.preventDefault(),S.stopPropagation(),E(function(){r.favoriteSearches.remove(g),r.refresh()})}},b.createElement(ei,null)))}})))}var tv=["translations"];function $r(){return $r=Object.assign||function(e){for(var t=1;t=0||(u[c]=s[c]);return u}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}var rv=b.memo(function(e){var t=e.translations,n=t===void 0?{}:t,r=nv(e,tv);if(r.state.status==="error")return b.createElement(H_,{translations:n==null?void 0:n.errorScreen});var o=r.state.collections.some(function(i){return i.items.length>0});return r.state.query?o===!1?b.createElement($_,$r({},r,{translations:n==null?void 0:n.noResultsScreen})):b.createElement(Y_,r):b.createElement(ev,$r({},r,{hasCollections:o,translations:n==null?void 0:n.startScreen}))},function(e,t){return t.state.status==="loading"||t.state.status==="stalled"}),ov=["translations"];function qr(){return qr=Object.assign||function(e){for(var t=1;t=0||(u[c]=s[c]);return u}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}function sv(e){var t=e.translations,n=t===void 0?{}:t,r=iv(e,ov),o=n.resetButtonTitle,i=o===void 0?"Clear the query":o,s=n.resetButtonAriaLabel,a=s===void 0?"Clear the query":s,c=n.cancelButtonText,l=c===void 0?"Cancel":c,u=n.cancelButtonAriaLabel,d=u===void 0?"Cancel":u,f=r.getFormProps({inputElement:r.inputRef.current}).onReset;return b.useEffect(function(){r.autoFocus&&r.inputRef.current&&r.inputRef.current.focus()},[r.autoFocus,r.inputRef]),b.useEffect(function(){r.isFromSelection&&r.inputRef.current&&r.inputRef.current.select()},[r.isFromSelection,r.inputRef]),b.createElement(b.Fragment,null,b.createElement("form",{className:"DocSearch-Form",onSubmit:function(h){h.preventDefault()},onReset:f},b.createElement("label",qr({className:"DocSearch-MagnifierLabel"},r.getLabelProps()),b.createElement(nu,null)),b.createElement("div",{className:"DocSearch-LoadingIndicator"},b.createElement(R_,null)),b.createElement("input",qr({className:"DocSearch-Input",ref:r.inputRef},r.getInputProps({inputElement:r.inputRef.current,autoFocus:r.autoFocus,maxLength:64}))),b.createElement("button",{type:"reset",title:i,className:"DocSearch-Reset","aria-label":a,hidden:!r.state.query},b.createElement(ei,null))),b.createElement("button",{className:"DocSearch-Cancel",type:"reset","aria-label":d,onClick:r.onClose},l))}var av=["_highlightResult","_snippetResult"];function cv(e,t){if(e==null)return{};var n,r,o=function(s,a){if(s==null)return{};var c,l,u={},d=Object.keys(s);for(l=0;l=0||(u[c]=s[c]);return u}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}function lv(e){return function(){var t="__TEST_KEY__";try{return localStorage.setItem(t,""),localStorage.removeItem(t),!0}catch{return!1}}()===!1?{setItem:function(){},getItem:function(){return[]}}:{setItem:function(t){return window.localStorage.setItem(e,JSON.stringify(t))},getItem:function(){var t=window.localStorage.getItem(e);return t?JSON.parse(t):[]}}}function Ba(e){var t=e.key,n=e.limit,r=n===void 0?5:n,o=lv(t),i=o.getItem().slice(0,r);return{add:function(s){var a=s,c=(a._highlightResult,a._snippetResult,cv(a,av)),l=i.findIndex(function(u){return u.objectID===c.objectID});l>-1&&i.splice(l,1),i.unshift(c),i=i.slice(0,r),o.setItem(i)},remove:function(s){i=i.filter(function(a){return a.objectID!==s.objectID}),o.setItem(i)},getAll:function(){return i}}}var uv=["facetName","facetQuery"];function fv(e){var t,n="algoliasearch-client-js-".concat(e.key),r=function(){return t===void 0&&(t=e.localStorage||window.localStorage),t},o=function(){return JSON.parse(r().getItem(n)||"{}")};return{get:function(i,s){var a=arguments.length>2&&arguments[2]!==void 0?arguments[2]:{miss:function(){return Promise.resolve()}};return Promise.resolve().then(function(){var c=JSON.stringify(i),l=o()[c];return Promise.all([l||s(),l!==void 0])}).then(function(c){var l=zr(c,2),u=l[0],d=l[1];return Promise.all([u,d||a.miss(u)])}).then(function(c){return zr(c,1)[0]})},set:function(i,s){return Promise.resolve().then(function(){var a=o();return a[JSON.stringify(i)]=s,r().setItem(n,JSON.stringify(a)),s})},delete:function(i){return Promise.resolve().then(function(){var s=o();delete s[JSON.stringify(i)],r().setItem(n,JSON.stringify(s))})},clear:function(){return Promise.resolve().then(function(){r().removeItem(n)})}}}function Cn(e){var t=Vr(e.caches),n=t.shift();return n===void 0?{get:function(r,o){var i=arguments.length>2&&arguments[2]!==void 0?arguments[2]:{miss:function(){return Promise.resolve()}};return o().then(function(s){return Promise.all([s,i.miss(s)])}).then(function(s){return zr(s,1)[0]})},set:function(r,o){return Promise.resolve(o)},delete:function(r){return Promise.resolve()},clear:function(){return Promise.resolve()}}:{get:function(r,o){var i=arguments.length>2&&arguments[2]!==void 0?arguments[2]:{miss:function(){return Promise.resolve()}};return n.get(r,o,i).catch(function(){return Cn({caches:t}).get(r,o,i)})},set:function(r,o){return n.set(r,o).catch(function(){return Cn({caches:t}).set(r,o)})},delete:function(r){return n.delete(r).catch(function(){return Cn({caches:t}).delete(r)})},clear:function(){return n.clear().catch(function(){return Cn({caches:t}).clear()})}}}function So(){var e=arguments.length>0&&arguments[0]!==void 0?arguments[0]:{serializable:!0},t={};return{get:function(n,r){var o=arguments.length>2&&arguments[2]!==void 0?arguments[2]:{miss:function(){return Promise.resolve()}},i=JSON.stringify(n);if(i in t)return Promise.resolve(e.serializable?JSON.parse(t[i]):t[i]);var s=r(),a=o&&o.miss||function(){return Promise.resolve()};return s.then(function(c){return a(c)}).then(function(){return s})},set:function(n,r){return t[JSON.stringify(n)]=e.serializable?JSON.stringify(r):r,Promise.resolve(r)},delete:function(n){return delete t[JSON.stringify(n)],Promise.resolve()},clear:function(){return t={},Promise.resolve()}}}function dv(e){for(var t=e.length-1;t>0;t--){var n=Math.floor(Math.random()*(t+1)),r=e[t];e[t]=e[n],e[n]=r}return e}function au(e,t){return t&&Object.keys(t).forEach(function(n){e[n]=t[n](e)}),e}function ro(e){for(var t=arguments.length,n=new Array(t>1?t-1:0),r=1;r0?r:void 0,timeout:n.timeout||t,headers:n.headers||{},queryParameters:n.queryParameters||{},cacheable:n.cacheable}}var rn={Read:1,Write:2,Any:3},cu=1,pv=2,lu=3;function uu(e){var t=arguments.length>1&&arguments[1]!==void 0?arguments[1]:cu;return fe(fe({},e),{},{status:t,lastUpdate:Date.now()})}function fu(e){return typeof e=="string"?{protocol:"https",url:e,accept:rn.Any}:{protocol:e.protocol||"https",url:e.url,accept:e.accept||rn.Any}}var Ua="GET",oo="POST";function mv(e,t){return Promise.all(t.map(function(n){return e.get(n,function(){return Promise.resolve(uu(n))})})).then(function(n){var r=n.filter(function(s){return function(a){return a.status===cu||Date.now()-a.lastUpdate>12e4}(s)}),o=n.filter(function(s){return function(a){return a.status===lu&&Date.now()-a.lastUpdate<=12e4}(s)}),i=[].concat(Vr(r),Vr(o));return{getTimeout:function(s,a){return(o.length===0&&s===0?1:o.length+3+s)*a},statelessHosts:i.length>0?i.map(function(s){return fu(s)}):t}})}function $a(e,t,n,r){var o=[],i=function(f,h){if(!(f.method===Ua||f.data===void 0&&h.data===void 0)){var m=Array.isArray(f.data)?f.data:fe(fe({},f.data),h.data);return JSON.stringify(m)}}(n,r),s=function(f,h){var m=fe(fe({},f.headers),h.headers),v={};return Object.keys(m).forEach(function(_){var g=m[_];v[_.toLowerCase()]=g}),v}(e,r),a=n.method,c=n.method!==Ua?{}:fe(fe({},n.data),r.data),l=fe(fe(fe({"x-algolia-agent":e.userAgent.value},e.queryParameters),c),r.queryParameters),u=0,d=function f(h,m){var v=h.pop();if(v===void 0)throw{name:"RetryError",message:"Unreachable hosts - your application id may be incorrect. If the error persists, contact support@algolia.com.",transporterStackTrace:qa(o)};var _={data:i,headers:s,method:a,url:_v(v,n.path,l),connectTimeout:m(u,e.timeouts.connect),responseTimeout:m(u,r.timeout)},g=function(S){var P={request:_,response:S,host:v,triesLeft:h.length};return o.push(P),P},E={onSucess:function(S){return function(P){try{return JSON.parse(P.content)}catch(T){throw function(N,A){return{name:"DeserializationError",message:N,response:A}}(T.message,P)}}(S)},onRetry:function(S){var P=g(S);return S.isTimedOut&&u++,Promise.all([e.logger.info("Retryable failure",pu(P)),e.hostsCache.set(v,uu(v,S.isTimedOut?lu:pv))]).then(function(){return f(h,m)})},onFail:function(S){throw g(S),function(P,T){var N=P.content,A=P.status,D=N;try{D=JSON.parse(N).message}catch{}return function($,F,K){return{name:"ApiError",message:$,status:F,transporterStackTrace:K}}(D,A,T)}(S,qa(o))}};return e.requester.send(_).then(function(S){return function(P,T){return function(N){var A=N.status;return N.isTimedOut||function(D){var $=D.isTimedOut,F=D.status;return!$&&~~F==0}(N)||~~(A/100)!=2&&~~(A/100)!=4}(P)?T.onRetry(P):~~(P.status/100)==2?T.onSucess(P):T.onFail(P)}(S,E)})};return mv(e.hostsCache,t).then(function(f){return d(Vr(f.statelessHosts).reverse(),f.getTimeout)})}function hv(e){var t={value:"Algolia for JavaScript (".concat(e,")"),add:function(n){var r="; ".concat(n.segment).concat(n.version!==void 0?" (".concat(n.version,")"):"");return t.value.indexOf(r)===-1&&(t.value="".concat(t.value).concat(r)),t}};return t}function _v(e,t,n){var r=du(n),o="".concat(e.protocol,"://").concat(e.url,"/").concat(t.charAt(0)==="/"?t.substr(1):t);return r.length&&(o+="?".concat(r)),o}function du(e){return Object.keys(e).map(function(t){return ro("%s=%s",t,(n=e[t],Object.prototype.toString.call(n)==="[object Object]"||Object.prototype.toString.call(n)==="[object Array]"?JSON.stringify(e[t]):e[t]));var n}).join("&")}function qa(e){return e.map(function(t){return pu(t)})}function pu(e){var t=e.request.headers["x-algolia-api-key"]?{"x-algolia-api-key":"*****"}:{};return fe(fe({},e),{},{request:fe(fe({},e.request),{},{headers:fe(fe({},e.request.headers),t)})})}var vv=function(e){var t=e.appId,n=function(i,s,a){var c={"x-algolia-api-key":a,"x-algolia-application-id":s};return{headers:function(){return i===wr.WithinHeaders?c:{}},queryParameters:function(){return i===wr.WithinQueryParameters?c:{}}}}(e.authMode!==void 0?e.authMode:wr.WithinHeaders,t,e.apiKey),r=function(i){var s=i.hostsCache,a=i.logger,c=i.requester,l=i.requestsCache,u=i.responsesCache,d=i.timeouts,f=i.userAgent,h=i.hosts,m=i.queryParameters,v={hostsCache:s,logger:a,requester:c,requestsCache:l,responsesCache:u,timeouts:d,userAgent:f,headers:i.headers,queryParameters:m,hosts:h.map(function(_){return fu(_)}),read:function(_,g){var E=Fa(g,v.timeouts.read),S=function(){return $a(v,v.hosts.filter(function(T){return(T.accept&rn.Read)!=0}),_,E)};if((E.cacheable!==void 0?E.cacheable:_.cacheable)!==!0)return S();var P={request:_,mappedRequestOptions:E,transporter:{queryParameters:v.queryParameters,headers:v.headers}};return v.responsesCache.get(P,function(){return v.requestsCache.get(P,function(){return v.requestsCache.set(P,S()).then(function(T){return Promise.all([v.requestsCache.delete(P),T])},function(T){return Promise.all([v.requestsCache.delete(P),Promise.reject(T)])}).then(function(T){var N=zr(T,2);return N[0],N[1]})})},{miss:function(T){return v.responsesCache.set(P,T)}})},write:function(_,g){return $a(v,v.hosts.filter(function(E){return(E.accept&rn.Write)!=0}),_,Fa(g,v.timeouts.write))}};return v}(fe(fe({hosts:[{url:"".concat(t,"-dsn.algolia.net"),accept:rn.Read},{url:"".concat(t,".algolia.net"),accept:rn.Write}].concat(dv([{url:"".concat(t,"-1.algolianet.com")},{url:"".concat(t,"-2.algolianet.com")},{url:"".concat(t,"-3.algolianet.com")}]))},e),{},{headers:fe(fe(fe({},n.headers()),{"content-type":"application/x-www-form-urlencoded"}),e.headers),queryParameters:fe(fe({},n.queryParameters()),e.queryParameters)})),o={transporter:r,appId:t,addAlgoliaAgent:function(i,s){r.userAgent.add({segment:i,version:s})},clearCache:function(){return Promise.all([r.requestsCache.clear(),r.responsesCache.clear()]).then(function(){})}};return au(o,e.methods)},mu=function(e){return function(t){var n=arguments.length>1&&arguments[1]!==void 0?arguments[1]:{},r={transporter:e.transporter,appId:e.appId,indexName:t};return au(r,n.methods)}},Ka=function(e){return function(t,n){var r=t.map(function(o){return fe(fe({},o),{},{params:du(o.params||{})})});return e.transporter.read({method:oo,path:"1/indexes/*/queries",data:{requests:r},cacheable:!0},n)}},Wa=function(e){return function(t,n){return Promise.all(t.map(function(r){var o=r.params,i=o.facetName,s=o.facetQuery,a=Dh(o,uv);return mu(e)(r.indexName,{methods:{searchForFacetValues:hu}}).searchForFacetValues(i,s,fe(fe({},n),a))}))}},gv=function(e){return function(t,n,r){return e.transporter.read({method:oo,path:ro("1/answers/%s/prediction",e.indexName),data:{query:t,queryLanguages:n},cacheable:!0},r)}},yv=function(e){return function(t,n){return e.transporter.read({method:oo,path:ro("1/indexes/%s/query",e.indexName),data:{query:t},cacheable:!0},n)}},hu=function(e){return function(t,n,r){return e.transporter.read({method:oo,path:ro("1/indexes/%s/facets/%s/query",e.indexName,t),data:{facetQuery:n},cacheable:!0},r)}},bv=1,Ev=2,Ov=3;function _u(e,t,n){var r,o={appId:e,apiKey:t,timeouts:{connect:1,read:2,write:30},requester:{send:function(i){return new Promise(function(s){var a=new XMLHttpRequest;a.open(i.method,i.url,!0),Object.keys(i.headers).forEach(function(d){return a.setRequestHeader(d,i.headers[d])});var c,l=function(d,f){return setTimeout(function(){a.abort(),s({status:0,content:f,isTimedOut:!0})},1e3*d)},u=l(i.connectTimeout,"Connection timeout");a.onreadystatechange=function(){a.readyState>a.OPENED&&c===void 0&&(clearTimeout(u),c=l(i.responseTimeout,"Socket timeout"))},a.onerror=function(){a.status===0&&(clearTimeout(u),clearTimeout(c),s({content:a.responseText||"Network request failed",status:a.status,isTimedOut:!1}))},a.onload=function(){clearTimeout(u),clearTimeout(c),s({content:a.responseText,status:a.status,isTimedOut:!1})},a.send(i.data)})}},logger:(r=Ov,{debug:function(i,s){return bv>=r&&console.debug(i,s),Promise.resolve()},info:function(i,s){return Ev>=r&&console.info(i,s),Promise.resolve()},error:function(i,s){return console.error(i,s),Promise.resolve()}}),responsesCache:So(),requestsCache:So({serializable:!1}),hostsCache:Cn({caches:[fv({key:"".concat("4.8.5","-").concat(e)}),So()]}),userAgent:hv("4.8.5").add({segment:"Browser",version:"lite"}),authMode:wr.WithinQueryParameters};return vv(fe(fe(fe({},o),n),{},{methods:{search:Ka,searchForFacetValues:Wa,multipleQueries:Ka,multipleSearchForFacetValues:Wa,initIndex:function(i){return function(s){return mu(i)(s,{methods:{search:yv,searchForFacetValues:hu,findAnswers:gv}})}}}}))}_u.version="4.8.5";var wv=["footer","searchBox"];function Vn(){return Vn=Object.assign||function(e){for(var t=1;te.length)&&(t=e.length);for(var n=0,r=new Array(t);n=0||(u[c]=s[c]);return u}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}function Iv(e){var t=e.appId,n=t===void 0?"BH4D9OD16A":t,r=e.apiKey,o=e.indexName,i=e.placeholder,s=i===void 0?"Search docs":i,a=e.searchParameters,c=e.onClose,l=c===void 0?J_:c,u=e.transformItems,d=u===void 0?Ha:u,f=e.hitComponent,h=f===void 0?T_:f,m=e.resultsFooterComponent,v=m===void 0?function(){return null}:m,_=e.navigator,g=e.initialScrollY,E=g===void 0?0:g,S=e.transformSearchClient,P=S===void 0?Ha:S,T=e.disableUserPersonalization,N=T!==void 0&&T,A=e.initialQuery,D=A===void 0?"":A,$=e.translations,F=$===void 0?{}:$,K=F.footer,I=F.searchBox,B=Dv(F,wv),Y=Pv(b.useState({query:"",collections:[],completion:null,context:{},isOpen:!1,activeItemId:null,status:"idle"}),2),ae=Y[0],J=Y[1],ne=b.useRef(null),re=b.useRef(null),Ee=b.useRef(null),Pe=b.useRef(null),Ie=b.useRef(null),we=b.useRef(10),Re=b.useRef(typeof window!="undefined"?window.getSelection().toString().slice(0,64):"").current,He=b.useRef(D||Re).current,R=function(p,y,w){return b.useMemo(function(){var C=_u(p,y);return C.addAlgoliaAgent("docsearch","3.0.0-alpha.42"),/docsearch.js \(.*\)/.test(C.transporter.userAgent.value)===!1&&C.addAlgoliaAgent("docsearch-react","3.0.0-alpha.42"),w(C)},[p,y,w])}(n,r,P),U=b.useRef(Ba({key:"__DOCSEARCH_FAVORITE_SEARCHES__".concat(o),limit:10})).current,M=b.useRef(Ba({key:"__DOCSEARCH_RECENT_SEARCHES__".concat(o),limit:U.getAll().length===0?7:4})).current,q=b.useCallback(function(p){if(!N){var y=p.type==="content"?p.__docsearch_parent:p;y&&U.getAll().findIndex(function(w){return w.objectID===y.objectID})===-1&&M.add(y)}},[U,M,N]),le=b.useMemo(function(){return I_({id:"docsearch",defaultActiveItemId:0,placeholder:s,openOnFocus:!0,initialState:{query:He,context:{searchSuggestions:[]}},navigator:_,onStateChange:function(p){J(p.state)},getSources:function(p){var y=p.query,w=p.state,C=p.setContext,x=p.setStatus;return y?R.search([{query:y,indexName:o,params:Po({attributesToRetrieve:["hierarchy.lvl0","hierarchy.lvl1","hierarchy.lvl2","hierarchy.lvl3","hierarchy.lvl4","hierarchy.lvl5","hierarchy.lvl6","content","type","url"],attributesToSnippet:["hierarchy.lvl1:".concat(we.current),"hierarchy.lvl2:".concat(we.current),"hierarchy.lvl3:".concat(we.current),"hierarchy.lvl4:".concat(we.current),"hierarchy.lvl5:".concat(we.current),"hierarchy.lvl6:".concat(we.current),"content:".concat(we.current)],snippetEllipsisText:"\u2026",highlightPreTag:"",highlightPostTag:"",hitsPerPage:20},a)}]).catch(function(L){throw L.name==="RetryError"&&x("error"),L}).then(function(L){var z=L.results[0],j=z.hits,H=z.nbHits,k=Va(j,function(Q){return su(Q)});return w.context.searchSuggestions.length0&&(te(),Ie.current&&Ie.current.focus())},[He,te]),b.useEffect(function(){function p(){if(re.current){var y=.01*window.innerHeight;re.current.style.setProperty("--docsearch-vh","".concat(y,"px"))}}return p(),window.addEventListener("resize",p),function(){window.removeEventListener("resize",p)}},[]),b.createElement("div",Vn({ref:ne},oe({"aria-expanded":!0}),{className:["DocSearch","DocSearch-Container",ae.status==="stalled"&&"DocSearch-Container--Stalled",ae.status==="error"&&"DocSearch-Container--Errored"].filter(Boolean).join(" "),role:"button",tabIndex:0,onMouseDown:function(p){p.target===p.currentTarget&&l()}}),b.createElement("div",{className:"DocSearch-Modal",ref:re},b.createElement("header",{className:"DocSearch-SearchBar",ref:Ee},b.createElement(sv,Vn({},le,{state:ae,autoFocus:He.length===0,inputRef:Ie,isFromSelection:Boolean(He)&&He===Re,translations:I,onClose:l}))),b.createElement("div",{className:"DocSearch-Dropdown",ref:Pe},b.createElement(rv,Vn({},le,{indexName:o,state:ae,hitComponent:h,resultsFooterComponent:v,disableUserPersonalization:N,recentSearches:M,favoriteSearches:U,inputRef:Ie,translations:B,onItemClick:function(p){q(p),l()}}))),b.createElement("footer",{className:"DocSearch-Footer"},b.createElement(C_,{translations:K}))))}function ri(){return ri=Object.assign||function(e){for(var t=1;te.length)&&(t=e.length);for(var n=0,r=new Array(t);n1&&arguments[1]!==void 0?arguments[1]:window;return typeof t=="string"?n.document.querySelector(t):t}(e.container,e.environment))}var vu,oi,gu,Tv=[];function Rv(e,t,n){var r,o,i,s={};for(i in t)i=="key"?r=t[i]:i=="ref"?o=t[i]:s[i]=t[i];if(arguments.length>2&&(s.children=arguments.length>3?vu.call(arguments,2):n),typeof e=="function"&&e.defaultProps!=null)for(i in e.defaultProps)s[i]===void 0&&(s[i]=e.defaultProps[i]);return xv(e,s,r,o,null)}function xv(e,t,n,r,o){var i={type:e,props:t,key:n,ref:r,__k:null,__:null,__b:0,__e:null,__d:void 0,__c:null,__h:null,constructor:void 0,__v:o==null?++gu:o};return o==null&&oi.vnode!=null&&oi.vnode(i),i}vu=Tv.slice,oi={__e:function(e,t){for(var n,r,o;t=t.__;)if((n=t.__c)&&!n.__)try{if((r=n.constructor)&&r.getDerivedStateFromError!=null&&(n.setState(r.getDerivedStateFromError(e)),o=n.__d),n.componentDidCatch!=null&&(n.componentDidCatch(e),o=n.__d),o)return n.__E=n}catch(i){e=i}throw e}},gu=0,typeof Promise=="function"&&Promise.prototype.then.bind(Promise.resolve());const Lv=e=>e.button===1||e.altKey||e.ctrlKey||e.metaKey||e.shiftKey,jv=()=>{const e=no(),t=Pl();return{transformItems:n=>n.map(r=>At(je({},r),{url:ym(r.url,t.value.base)})),hitComponent:({hit:n,children:r})=>Rv("a",{href:n.url,onClick:o=>{Lv(o)||(o.preventDefault(),e.push(n.url))}},r),navigator:{navigate:({itemUrl:n})=>{e.push(n)}}}};const kv=Qe({name:"Docsearch",props:{options:{type:Object,required:!0}},setup(e){const t=Sl(),n=wl(),r=jv(),o=Oe(()=>{var a;return je(je({},e.options),(a=e.options.locales)===null||a===void 0?void 0:a[t.value])}),i=[],s=()=>{var a,c;const l=(c=(a=o.value.searchParameters)===null||a===void 0?void 0:a.facetFilters)!==null&&c!==void 0?c:[];i.splice(0,i.length,`lang:${n.value}`,...ee(l)?l:[l]),Cv(At(je(je({},r),o.value),{container:"#docsearch-container",searchParameters:At(je({},o.value.searchParameters),{facetFilters:i})}))};return at(()=>{s(),et([t,o],([a,c],[l,u])=>{a!==l&&JSON.stringify(c)!==JSON.stringify(u)&&s()}),et(n,(a,c)=>{if(a!==c){const l=i.findIndex(u=>u===`lang:${c}`);l>-1&&i.splice(l,1,`lang:${a}`)}})}),()=>be("div",{id:"docsearch-container"})}}),Nv={apiKey:"847c13a2e60987ce337f3eead65b66b4",indexName:"ibm_z_open_editor",placeholder:"Lookup documentation"};var Mv=nr(({app:e})=>{e.component("Docsearch",()=>be(kv,{options:Nv}))});const zv=[Sm,Nm,Bm,Sh,Mv];function yu(e,t,n){var r,o,i;t===void 0&&(t=50),n===void 0&&(n={});var s=(r=n.isImmediate)!=null&&r,a=(o=n.callback)!=null&&o,c=n.maxWait,l=Date.now(),u=[];function d(){if(c!==void 0){var h=Date.now()-l;if(h+t>=c)return c-h}return t}var f=function(){var h=[].slice.call(arguments),m=this;return new Promise(function(v,_){var g=s&&i===void 0;if(i!==void 0&&clearTimeout(i),i=setTimeout(function(){if(i=void 0,l=Date.now(),!s){var S=e.apply(m,h);a&&a(S),u.forEach(function(P){return(0,P.resolve)(S)}),u=[]}},d()),g){var E=e.apply(m,h);return a&&a(E),v(E)}u.push({resolve:v,reject:_})})};return f.cancel=function(h){i!==void 0&&clearTimeout(i),u.forEach(function(m){return(0,m.reject)(h)}),u=[]},f}const Xa=()=>window.pageYOffset||document.documentElement.scrollTop||document.body.scrollTop||0,Vv=()=>window.scrollTo({top:0,behavior:"smooth"});const Hv=Qe({name:"BackToTop",setup(){const e=Ne(0),t=Oe(()=>e.value>300),n=yu(()=>{e.value=Xa()},100);at(()=>{e.value=Xa(),window.addEventListener("scroll",()=>n())});const r=be("div",{class:"back-to-top",onClick:Vv});return()=>be(Ci,{name:"back-to-top"},()=>t.value?r:null)}}),Bv=[Hv],Fv=({headerLinkSelector:e,headerAnchorSelector:t,delay:n,offset:r=5})=>{const o=no(),i=tr(),a=yu(()=>{var c,l,u,d;const f=Array.from(document.querySelectorAll(e)),m=Array.from(document.querySelectorAll(t)).filter(S=>f.some(P=>P.hash===S.hash)),v=Math.max(window.pageYOffset,document.documentElement.scrollTop,document.body.scrollTop),_=window.innerHeight+v,g=Math.max(document.documentElement.scrollHeight,document.body.scrollHeight),E=Math.abs(g-_)=((l=(c=P.parentElement)===null||c===void 0?void 0:c.offsetTop)!==null&&l!==void 0?l:0)-r,D=!T||v<((d=(u=T.parentElement)===null||u===void 0?void 0:u.offsetTop)!==null&&d!==void 0?d:0)-r;if(!(N||A&&D))continue;const F=decodeURIComponent(o.currentRoute.value.hash),K=decodeURIComponent(P.hash);if(F===K)return;if(E){for(let I=S+1;I{a(),window.addEventListener("scroll",a)}),wi(()=>{window.removeEventListener("scroll",a)}),et(()=>i.value.path,a)},Uv=async(e,...t)=>{const{scrollBehavior:n}=e.options;e.options.scrollBehavior=void 0,await e.replace(...t).finally(()=>e.options.scrollBehavior=n)},$v="a.sidebar-item",qv=".header-anchor",Kv=300,Wv=5;var Zv=ki(()=>{Fv({headerLinkSelector:$v,headerAnchorSelector:qv,delay:Kv,offset:Wv})}),Jv=typeof globalThis!="undefined"?globalThis:typeof window!="undefined"?window:typeof global!="undefined"?global:typeof self!="undefined"?self:{},Sr={exports:{}};/* NProgress, (c) 2013, 2014 Rico Sta. Cruz - http://ricostacruz.com/nprogress
- * @license MIT */(function(e,t){(function(n,r){e.exports=r()})(Jv,function(){var n={};n.version="0.2.0";var r=n.settings={minimum:.08,easing:"ease",positionUsing:"",speed:200,trickle:!0,trickleRate:.02,trickleSpeed:800,showSpinner:!0,barSelector:'[role="bar"]',spinnerSelector:'[role="spinner"]',parent:"body",template:'
    '};n.configure=function(m){var v,_;for(v in m)_=m[v],_!==void 0&&m.hasOwnProperty(v)&&(r[v]=_);return this},n.status=null,n.set=function(m){var v=n.isStarted();m=o(m,r.minimum,1),n.status=m===1?null:m;var _=n.render(!v),g=_.querySelector(r.barSelector),E=r.speed,S=r.easing;return _.offsetWidth,a(function(P){r.positionUsing===""&&(r.positionUsing=n.getPositioningCSS()),c(g,s(m,E,S)),m===1?(c(_,{transition:"none",opacity:1}),_.offsetWidth,setTimeout(function(){c(_,{transition:"all "+E+"ms linear",opacity:0}),setTimeout(function(){n.remove(),P()},E)},E)):setTimeout(P,E)}),this},n.isStarted=function(){return typeof n.status=="number"},n.start=function(){n.status||n.set(0);var m=function(){setTimeout(function(){!n.status||(n.trickle(),m())},r.trickleSpeed)};return r.trickle&&m(),this},n.done=function(m){return!m&&!n.status?this:n.inc(.3+.5*Math.random()).set(1)},n.inc=function(m){var v=n.status;return v?(typeof m!="number"&&(m=(1-v)*o(Math.random()*v,.1,.95)),v=o(v+m,0,.994),n.set(v)):n.start()},n.trickle=function(){return n.inc(Math.random()*r.trickleRate)},function(){var m=0,v=0;n.promise=function(_){return!_||_.state()==="resolved"?this:(v===0&&n.start(),m++,v++,_.always(function(){v--,v===0?(m=0,n.done()):n.set((m-v)/m)}),this)}}(),n.render=function(m){if(n.isRendered())return document.getElementById("nprogress");u(document.documentElement,"nprogress-busy");var v=document.createElement("div");v.id="nprogress",v.innerHTML=r.template;var _=v.querySelector(r.barSelector),g=m?"-100":i(n.status||0),E=document.querySelector(r.parent),S;return c(_,{transition:"all 0 linear",transform:"translate3d("+g+"%,0,0)"}),r.showSpinner||(S=v.querySelector(r.spinnerSelector),S&&h(S)),E!=document.body&&u(E,"nprogress-custom-parent"),E.appendChild(v),v},n.remove=function(){d(document.documentElement,"nprogress-busy"),d(document.querySelector(r.parent),"nprogress-custom-parent");var m=document.getElementById("nprogress");m&&h(m)},n.isRendered=function(){return!!document.getElementById("nprogress")},n.getPositioningCSS=function(){var m=document.body.style,v="WebkitTransform"in m?"Webkit":"MozTransform"in m?"Moz":"msTransform"in m?"ms":"OTransform"in m?"O":"";return v+"Perspective"in m?"translate3d":v+"Transform"in m?"translate":"margin"};function o(m,v,_){return m_?_:m}function i(m){return(-1+m)*100}function s(m,v,_){var g;return r.positionUsing==="translate3d"?g={transform:"translate3d("+i(m)+"%,0,0)"}:r.positionUsing==="translate"?g={transform:"translate("+i(m)+"%,0)"}:g={"margin-left":i(m)+"%"},g.transition="all "+v+"ms "+_,g}var a=function(){var m=[];function v(){var _=m.shift();_&&_(v)}return function(_){m.push(_),m.length==1&&v()}}(),c=function(){var m=["Webkit","O","Moz","ms"],v={};function _(P){return P.replace(/^-ms-/,"ms-").replace(/-([\da-z])/gi,function(T,N){return N.toUpperCase()})}function g(P){var T=document.body.style;if(P in T)return P;for(var N=m.length,A=P.charAt(0).toUpperCase()+P.slice(1),D;N--;)if(D=m[N]+A,D in T)return D;return P}function E(P){return P=_(P),v[P]||(v[P]=g(P))}function S(P,T,N){T=E(T),P.style[T]=N}return function(P,T){var N=arguments,A,D;if(N.length==2)for(A in T)D=T[A],D!==void 0&&T.hasOwnProperty(A)&&S(P,A,D);else S(P,N[1],N[2])}}();function l(m,v){var _=typeof m=="string"?m:f(m);return _.indexOf(" "+v+" ")>=0}function u(m,v){var _=f(m),g=_+v;l(_,v)||(m.className=g.substring(1))}function d(m,v){var _=f(m),g;!l(m,v)||(g=_.replace(" "+v+" "," "),m.className=g.substring(1,g.length-1))}function f(m){return(" "+(m.className||"")+" ").replace(/\s+/gi," ")}function h(m){m&&m.parentNode&&m.parentNode.removeChild(m)}return n})})(Sr);const Qv=()=>{at(()=>{const e=no(),t=new Set;t.add(e.currentRoute.value.path),Sr.exports.configure({showSpinner:!1}),e.beforeEach(n=>{t.has(n.path)||Sr.exports.start()}),e.afterEach(n=>{t.add(n.path),Sr.exports.done()})})};var Yv=ki(()=>{Qv()}),Xv=ki(()=>{mh(),yh()});const Gv=[Zv,Yv,Xv],eg=[["v-8daa1a0e","/",{title:""},["/index.html","/README.md"]],["v-a38aa0ce","/Blog/announcing-jcl.html",{title:"A Modern JCL (Job Control Language) Editor"},["/Blog/announcing-jcl","/Blog/announcing-jcl.md"]],["v-fe48651a","/Blog/announcing-rexx.html",{title:"A Modern REXX Editor"},["/Blog/announcing-rexx","/Blog/announcing-rexx.md"]],["v-8a4247d2","/Blog/code-snippets.html",{title:"Improve your z/OS enterprise developer productivity with IBM Z Open Editor\u2018s code snippets library"},["/Blog/code-snippets","/Blog/code-snippets.md"]],["v-0baade54","/Blog/external-posts.html",{title:"External Blog Posts and Articles"},["/Blog/external-posts","/Blog/external-posts.md"]],["v-1af1d74d","/Blog/hlasm-blog.html",{title:"IBM Z Open Editor: A modern IDE for IBM High Level Assembler"},["/Blog/hlasm-blog","/Blog/hlasm-blog.md"]],["v-48cb972d","/Blog/ibm-wazi-development-client-introduction-blog.html",{title:"Kubernetes-Native Integrated Z Developer Environment with IBM Wazi for Red Hat CodeReady Workspaces Development Client"},["/Blog/ibm-wazi-development-client-introduction-blog","/Blog/ibm-wazi-development-client-introduction-blog.md"]],["v-00ed1fd0","/Blog/in-the-cloud-with-che.html",{title:"IBM Z\xAE Open Editor in the cloud with Eclipse Che"},["/Blog/in-the-cloud-with-che","/Blog/in-the-cloud-with-che.md"]],["v-5a3683a7","/Blog/learning.html",{title:"Learning Resources"},["/Blog/learning","/Blog/learning.md"]],["v-4c46bc61","/Blog/new-content.html",{title:"New Content and Blog Posts"},["/Blog/new-content","/Blog/new-content.md"]],["v-7e9516cc","/Blog/new-releases.html",{title:"IBM Z Open Editor Releases"},["/Blog/new-releases","/Blog/new-releases.md"]],["v-a63a2e22","/Blog/ocp-ssl-cert.html",{title:"IBM Wazi Developer for Red Hat CodeReady Workspaces: Set up an SSL Certificate in an OpenShift Container Platform"},["/Blog/ocp-ssl-cert","/Blog/ocp-ssl-cert.md"]],["v-6fa9df51","/Blog/rse-march-120.html",{title:"Everything you need to know about IBM RSE API Plug-in for Zowe CLI 1.2.0"},["/Blog/rse-march-120","/Blog/rse-march-120.md"]],["v-0d011afc","/Blog/rse-march-beta.html",{title:"Interacting with z/OS using IBM RSE API Plug-in for Zowe CLI"},["/Blog/rse-march-beta","/Blog/rse-march-beta.md"]],["v-8483065a","/Blog/rse-october-110.html",{title:"What's new with IBM RSE API Plug-in for Zowe CLI 1.1.0"},["/Blog/rse-october-110","/Blog/rse-october-110.md"]],["v-5fac84d9","/Blog/userbuild-blog.html",{title:"IBM Z\xAE Open Editor makes building COBOL, PL/I, and HLASM applications easier with User Build"},["/Blog/userbuild-blog","/Blog/userbuild-blog.md"]],["v-4b9415f0","/Blog/web-based-with-theia.html",{title:"Running IBM Z\xAE Open Editor in the browser with Eclipse Theia"},["/Blog/web-based-with-theia","/Blog/web-based-with-theia.md"]],["v-68af98c9","/Blog/whats-new-120.html",{title:"Scaling up the audience with IBM Z Open Editor and Wazi Developer 1.2.0"},["/Blog/whats-new-120","/Blog/whats-new-120.md"]],["v-0ffb677e","/Docs/advanced_activation.html",{title:"Activating advanced capabilities"},["/Docs/advanced_activation","/Docs/advanced_activation.md"]],["v-4066bbc6","/Docs/advanced_custom_macros.html",{title:"Custom Macros for HLASM"},["/Docs/advanced_custom_macros","/Docs/advanced_custom_macros.md"]],["v-20708584","/Docs/advanced_overview.html",{title:"Overview"},["/Docs/advanced_overview","/Docs/advanced_overview.md"]],["v-a6691fb0","/Docs/advanced_preprocessor.html",{title:"Preprocessor support"},["/Docs/advanced_preprocessor","/Docs/advanced_preprocessor.md"]],["v-ae2b9dea","/Docs/advanced_problems_view.html",{title:"User build Problems view"},["/Docs/advanced_problems_view","/Docs/advanced_problems_view.md"]],["v-01e2125a","/Docs/advanced_resource_table.html",{title:"z/OS Resources Table"},["/Docs/advanced_resource_table","/Docs/advanced_resource_table.md"]],["v-2a14c510","/Docs/connect_to_zos_with_zowe_cli_e2e.html",{title:"Connecting to z/OS using Zowe CLI walk through"},["/Docs/connect_to_zos_with_zowe_cli_e2e","/Docs/connect_to_zos_with_zowe_cli_e2e.md"]],["v-175f1e49","/Docs/connect_to_zos_with_zowe_explorer_e2e.html",{title:"Connecting to z/OS with Zowe Explorer walk through"},["/Docs/connect_to_zos_with_zowe_explorer_e2e","/Docs/connect_to_zos_with_zowe_explorer_e2e.md"]],["v-26fabd50","/Docs/creating_team_profiles.html",{title:"Creating a configuration profile in Zowe Explorer v2.0.0"},["/Docs/creating_team_profiles","/Docs/creating_team_profiles.md"]],["v-e76197e2","/Docs/customizing_the_outline_view.html",{title:"Customizing the Outline view"},["/Docs/customizing_the_outline_view","/Docs/customizing_the_outline_view.md"]],["v-a2f185cc","/Docs/ebcdic_encoding.html",{title:"EBCDIC code pages and mappings files"},["/Docs/ebcdic_encoding","/Docs/ebcdic_encoding.md"]],["v-391d428c","/Docs/editor_codechanges.html",{title:"Making COBOL and PL/I code changes"},["/Docs/editor_codechanges","/Docs/editor_codechanges.md"]],["v-1c58a9fc","/Docs/editor_codechanges_hlasm.html",{title:"Making High Level Assembler code changes"},["/Docs/editor_codechanges_hlasm","/Docs/editor_codechanges_hlasm.md"]],["v-bb18cdb4","/Docs/editor_codechanges_jcl.html",{title:"Making JCL code changes"},["/Docs/editor_codechanges_jcl","/Docs/editor_codechanges_jcl.md"]],["v-13c01586","/Docs/editor_codechanges_rexx.html",{title:"Making REXX code changes"},["/Docs/editor_codechanges_rexx","/Docs/editor_codechanges_rexx.md"]],["v-10307d7a","/Docs/editor_search.html",{title:"Searching for COBOL, PL/I, HLASM, and REXX components"},["/Docs/editor_search","/Docs/editor_search.md"]],["v-9b8c1724","/Docs/getting_started.html",{title:"Getting started with IBM Z Open Editor"},["/Docs/getting_started","/Docs/getting_started.md"]],["v-afd18aa6","/Docs/git_integration.html",{title:"Using the integrated Git"},["/Docs/git_integration","/Docs/git_integration.md"]],["v-1251ae42","/Docs/interact_common_properties_cli.html",{title:"Interact with RSE Common Properties"},["/Docs/interact_common_properties_cli","/Docs/interact_common_properties_cli.md"]],["v-f89d1930","/Docs/interact_zos_cli.html",{title:"Using command line to interact with z/OS"},["/Docs/interact_zos_cli","/Docs/interact_zos_cli.md"]],["v-30184cb1","/Docs/interact_zos_overview.html",{title:"Interacting with z/OS"},["/Docs/interact_zos_overview","/Docs/interact_zos_overview.md"]],["v-3c830012","/Docs/interact_zos_zopeneditor.html",{title:"Using Zowe profiles in Z Open Editor"},["/Docs/interact_zos_zopeneditor","/Docs/interact_zos_zopeneditor.md"]],["v-60c4e326","/Docs/interact_zos_zowe_explorer.html",{title:"Using the Zowe Explorer views"},["/Docs/interact_zos_zowe_explorer","/Docs/interact_zos_zowe_explorer.md"]],["v-22d1c484","/Docs/introduction.html",{title:"Introduction"},["/Docs/introduction","/Docs/introduction.md"]],["v-823d11d2","/Docs/knownissues.html",{title:"Known issues and limitations"},["/Docs/knownissues","/Docs/knownissues.md"]],["v-93378d76","/Docs/language_references.html",{title:"Language References"},["/Docs/language_references","/Docs/language_references.md"]],["v-ab2cfe42","/Docs/locating_local_client_logs.html",{title:"Troubleshooting using log files"},["/Docs/locating_local_client_logs","/Docs/locating_local_client_logs.md"]],["v-f90f4ac6","/Docs/migrating_profiles.html",{title:"Migrating your old Zowe yaml profiles for Zowe v2.0"},["/Docs/migrating_profiles","/Docs/migrating_profiles.md"]],["v-065bea79","/Docs/notices.html",{title:"Notices"},["/Docs/notices","/Docs/notices.md"]],["v-e100f1ca","/Docs/other_extensions.html",{title:"Other Visual Studio Code extensions"},["/Docs/other_extensions","/Docs/other_extensions.md"]],["v-9629110c","/Docs/privacypolicy.html",{title:"Privacy policy considerations"},["/Docs/privacypolicy","/Docs/privacypolicy.md"]],["v-4aeeafba","/Docs/rse_cli_command.html",{title:"IBM RSE API Plug-in for Zowe CLI commands"},["/Docs/rse_cli_command","/Docs/rse_cli_command.md"]],["v-52b0a105","/Docs/rse_tutorial.html",{title:"Managing z/OS resources with IBM RSE API Plug-in for Zowe CLI tutorial"},["/Docs/rse_tutorial","/Docs/rse_tutorial.md"]],["v-9498fc72","/Docs/samplefiles.html",{title:"Exploring the sample files"},["/Docs/samplefiles","/Docs/samplefiles.md"]],["v-9dcc581e","/Docs/setting_compiler_options.html",{title:"Setting compiler options"},["/Docs/setting_compiler_options","/Docs/setting_compiler_options.md"]],["v-522078b2","/Docs/setting_disableproblems.html",{title:"Enabling and disabling problems in IBM Z Open Editor"},["/Docs/setting_disableproblems","/Docs/setting_disableproblems.md"]],["v-348a2d3e","/Docs/setting_fileassociations.html",{title:"Setting file associations"},["/Docs/setting_fileassociations","/Docs/setting_fileassociations.md"]],["v-3f4d9f11","/Docs/setting_maximum_line_length.html",{title:"Setting language-specific maximum line length"},["/Docs/setting_maximum_line_length","/Docs/setting_maximum_line_length.md"]],["v-3ae1cfcb","/Docs/setting_preferences.html",{title:"Setting preferences"},["/Docs/setting_preferences","/Docs/setting_preferences.md"]],["v-b824cc8e","/Docs/setting_propertygroup.html",{title:"Setting property groups"},["/Docs/setting_propertygroup","/Docs/setting_propertygroup.md"]],["v-0dd03d73","/Docs/setting_tabstops.html",{title:"Setting language-specific tab stops and rulers"},["/Docs/setting_tabstops","/Docs/setting_tabstops.md"]],["v-2a63b1ab","/Docs/setting_unreachablecodewarnings.html",{title:"Enabling and disabling unreachable COBOL code warnings"},["/Docs/setting_unreachablecodewarnings","/Docs/setting_unreachablecodewarnings.md"]],["v-8fabeeca","/Docs/settings.html",{title:"settings.json properties"},["/Docs/settings","/Docs/settings.md"]],["v-14aa9ebc","/Docs/setup_integration.html",{title:"Setting up integrations to interact with z/OS"},["/Docs/setup_integration","/Docs/setup_integration.md"]],["v-0791b3a2","/Docs/sharing_team_configuration_files.html",{title:"Sharing team configuration files"},["/Docs/sharing_team_configuration_files","/Docs/sharing_team_configuration_files.md"]],["v-d9943bba","/Docs/sharingfiles.html",{title:"Sharing files between VS Code extensions"},["/Docs/sharingfiles","/Docs/sharingfiles.md"]],["v-6676f350","/Docs/shortcut.html",{title:"Keyboard shortcuts reference"},["/Docs/shortcut","/Docs/shortcut.md"]],["v-45d644b0","/Docs/snippets.html",{title:"Using and managing code snippets"},["/Docs/snippets","/Docs/snippets.md"]],["v-7982067c","/Docs/trademarks.html",{title:"Trademarks"},["/Docs/trademarks","/Docs/trademarks.md"]],["v-492a8ebf","/Docs/tutorial_assembler.html",{title:"HLASM editing tutorial"},["/Docs/tutorial_assembler","/Docs/tutorial_assembler.md"]],["v-035874ac","/Docs/tutorial_cobol.html",{title:"COBOL editing tutorial"},["/Docs/tutorial_cobol","/Docs/tutorial_cobol.md"]],["v-70c1277a","/Docs/tutorial_overview.html",{title:"Tutorial overview"},["/Docs/tutorial_overview","/Docs/tutorial_overview.md"]],["v-6ab451c0","/Docs/tutorial_rexx.html",{title:"REXX editing tutorial"},["/Docs/tutorial_rexx","/Docs/tutorial_rexx.md"]],["v-64756ec4","/Docs/uninstalling.html",{title:"Uninstalling CLI plugins and VS Code extensions"},["/Docs/uninstalling","/Docs/uninstalling.md"]],["v-99d69e34","/Docs/userinterface.html",{title:"Exploring the user interface"},["/Docs/userinterface","/Docs/userinterface.md"]],["v-da074572","/Docs/using_code_snippets.html",{title:"Explore code snippets"},["/Docs/using_code_snippets","/Docs/using_code_snippets.md"]],["v-37f5df26","/Docs/whatsnew.html",{title:"Updates and user feedback"},["/Docs/whatsnew","/Docs/whatsnew.md"]],["v-43ab0a57","/Docs/zapp.html",{title:"Configuring your applications with ZAPP files"},["/Docs/zapp","/Docs/zapp.md"]],["v-4d589ea8","/Docs/zcodeformatting.html",{title:"Experimental: Formatting COBOL source code"},["/Docs/zcodeformatting","/Docs/zcodeformatting.md"]],["v-2d85c4b3","/Docs/zopeneditor_v3.html",{title:"Migrating from Z Open Editor v2 to v3"},["/Docs/zopeneditor_v3","/Docs/zopeneditor_v3.md"]],["v-41c85ba6","/Docs/zowe_advanced_connection_scenarious.html",{title:"Supported methods of authentication for z/OS using Zowe"},["/Docs/zowe_advanced_connection_scenarious","/Docs/zowe_advanced_connection_scenarious.md"]],["v-4b11bcde","/Docs/zowe_explorer_v2.html",{title:"Getting started with Zowe 2.0"},["/Docs/zowe_explorer_v2","/Docs/zowe_explorer_v2.md"]],["v-60b2a3bf","/Docs/zowe_submitjcl.html",{title:"Submitting JCL to compile, link, and run jobs tutorial"},["/Docs/zowe_submitjcl","/Docs/zowe_submitjcl.md"]],["v-3706649a","/404.html",{title:""},["/404"]]],tg=eg.reduce((e,[t,n,r,o])=>(e.push({name:t,path:n,component:Vs,meta:r},...o.map(i=>({path:i,redirect:n}))),e),[{name:"404",path:"/:catchAll(.*)",component:Vs}]),ng=yp,rg=()=>{const e=nm({history:ng(vm(wt.value.base)),routes:tg,scrollBehavior:(t,n,r)=>r||(t.hash?{el:t.hash}:{top:0})});return e.beforeResolve(async(t,n)=>{var r;(t.path!==n.path||n===ct)&&([ut.value]=await Promise.all([jt.resolvePageData(t.name),(r=vl[t.name])===null||r===void 0?void 0:r.__asyncLoader()]))}),e},og=e=>{e.component("ClientOnly",om),e.component("Content",ji)},ig=(e,t)=>{const n=Oe(()=>jt.resolveRouteLocale(wt.value.locales,t.currentRoute.value.path)),r=Oe(()=>jt.resolveSiteLocaleData(wt.value,n.value)),o=Oe(()=>jt.resolvePageFrontmatter(ut.value)),i=Oe(()=>jt.resolvePageHeadTitle(ut.value,r.value)),s=Oe(()=>jt.resolvePageHead(i.value,o.value,r.value)),a=Oe(()=>jt.resolvePageLang(ut.value));return e.provide(Li,n),e.provide(Dl,r),e.provide(bl,o),e.provide(um,i),e.provide(El,s),e.provide(Ol,a),Object.defineProperties(e.config.globalProperties,{$frontmatter:{get:()=>o.value},$head:{get:()=>s.value},$headTitle:{get:()=>i.value},$lang:{get:()=>a.value},$page:{get:()=>ut.value},$routeLocale:{get:()=>n.value},$site:{get:()=>wt.value},$siteLocale:{get:()=>r.value},$withBase:{get:()=>bm}}),{pageData:ut,pageFrontmatter:o,pageHead:s,pageHeadTitle:i,pageLang:a,routeLocale:n,siteData:wt,siteLocaleData:r}},sg=()=>{const e=xi(),t=lm(),n=wl(),r=Ne([]),o=()=>{t.value.forEach(s=>{const a=ag(s);a&&r.value.push(a)})},i=()=>{document.documentElement.lang=n.value,r.value.forEach(s=>{s.parentNode===document.head&&document.head.removeChild(s)}),r.value.splice(0,r.value.length),t.value.forEach(s=>{const a=cg(s);a!==null&&(document.head.appendChild(a),r.value.push(a))})};Bt(dm,i),at(()=>{o(),i(),et(()=>e.path,()=>i())})},ag=([e,t,n=""])=>{const r=Object.entries(t).map(([a,c])=>ve(c)?`[${a}="${c}"]`:c===!0?`[${a}]`:"").join(""),o=`head > ${e}${r}`;return Array.from(document.querySelectorAll(o)).find(a=>a.innerText===n)||null},cg=([e,t,n])=>{if(!ve(e))return null;const r=document.createElement(e);return Il(t)&&Object.entries(t).forEach(([o,i])=>{ve(i)?r.setAttribute(o,i):i===!0&&r.setAttribute(o,"")}),ve(n)&&r.appendChild(document.createTextNode(n)),r},lg=Gd,ug=async()=>{const e=lg({name:"VuepressApp",setup(){sg();for(const n of Gv)n();return()=>[be(_l),...Bv.map(n=>be(n))]}}),t=rg();og(e),ig(e,t);for(const n of zv)await n({app:e,router:t,siteData:wt});return e.use(t),{app:e,router:t}};ug().then(({app:e,router:t})=>{t.isReady().then(()=>{e.mount("#app")})});export{Pl as A,yg as B,Og as C,be as D,bm as E,Ve as F,om as G,Yn as H,Ne as I,et as J,pg as K,gg as L,gm as M,vm as N,no as O,ve as P,_h as Q,at as R,Kr as S,Ci as T,tr as U,wg as V,Il as W,vg as X,Si as Y,gh as Z,Zc as a,Yc as b,mg as c,ug as createVueApp,Se as d,Di as e,Qe as f,Nl as g,Ht as h,cm as i,Oe as j,ee as k,_g as l,hg as m,xi as n,Xr as o,dg as p,Jc as q,ld as r,hd as s,Tu as t,Sl as u,Xc as v,If as w,_m as x,bg as y,Eg as z};
+ * @license MIT */(function(e,t){(function(n,r){e.exports=r()})(Jv,function(){var n={};n.version="0.2.0";var r=n.settings={minimum:.08,easing:"ease",positionUsing:"",speed:200,trickle:!0,trickleRate:.02,trickleSpeed:800,showSpinner:!0,barSelector:'[role="bar"]',spinnerSelector:'[role="spinner"]',parent:"body",template:'
    '};n.configure=function(m){var v,_;for(v in m)_=m[v],_!==void 0&&m.hasOwnProperty(v)&&(r[v]=_);return this},n.status=null,n.set=function(m){var v=n.isStarted();m=o(m,r.minimum,1),n.status=m===1?null:m;var _=n.render(!v),g=_.querySelector(r.barSelector),E=r.speed,S=r.easing;return _.offsetWidth,a(function(P){r.positionUsing===""&&(r.positionUsing=n.getPositioningCSS()),c(g,s(m,E,S)),m===1?(c(_,{transition:"none",opacity:1}),_.offsetWidth,setTimeout(function(){c(_,{transition:"all "+E+"ms linear",opacity:0}),setTimeout(function(){n.remove(),P()},E)},E)):setTimeout(P,E)}),this},n.isStarted=function(){return typeof n.status=="number"},n.start=function(){n.status||n.set(0);var m=function(){setTimeout(function(){!n.status||(n.trickle(),m())},r.trickleSpeed)};return r.trickle&&m(),this},n.done=function(m){return!m&&!n.status?this:n.inc(.3+.5*Math.random()).set(1)},n.inc=function(m){var v=n.status;return v?(typeof m!="number"&&(m=(1-v)*o(Math.random()*v,.1,.95)),v=o(v+m,0,.994),n.set(v)):n.start()},n.trickle=function(){return n.inc(Math.random()*r.trickleRate)},function(){var m=0,v=0;n.promise=function(_){return!_||_.state()==="resolved"?this:(v===0&&n.start(),m++,v++,_.always(function(){v--,v===0?(m=0,n.done()):n.set((m-v)/m)}),this)}}(),n.render=function(m){if(n.isRendered())return document.getElementById("nprogress");u(document.documentElement,"nprogress-busy");var v=document.createElement("div");v.id="nprogress",v.innerHTML=r.template;var _=v.querySelector(r.barSelector),g=m?"-100":i(n.status||0),E=document.querySelector(r.parent),S;return c(_,{transition:"all 0 linear",transform:"translate3d("+g+"%,0,0)"}),r.showSpinner||(S=v.querySelector(r.spinnerSelector),S&&h(S)),E!=document.body&&u(E,"nprogress-custom-parent"),E.appendChild(v),v},n.remove=function(){d(document.documentElement,"nprogress-busy"),d(document.querySelector(r.parent),"nprogress-custom-parent");var m=document.getElementById("nprogress");m&&h(m)},n.isRendered=function(){return!!document.getElementById("nprogress")},n.getPositioningCSS=function(){var m=document.body.style,v="WebkitTransform"in m?"Webkit":"MozTransform"in m?"Moz":"msTransform"in m?"ms":"OTransform"in m?"O":"";return v+"Perspective"in m?"translate3d":v+"Transform"in m?"translate":"margin"};function o(m,v,_){return m_?_:m}function i(m){return(-1+m)*100}function s(m,v,_){var g;return r.positionUsing==="translate3d"?g={transform:"translate3d("+i(m)+"%,0,0)"}:r.positionUsing==="translate"?g={transform:"translate("+i(m)+"%,0)"}:g={"margin-left":i(m)+"%"},g.transition="all "+v+"ms "+_,g}var a=function(){var m=[];function v(){var _=m.shift();_&&_(v)}return function(_){m.push(_),m.length==1&&v()}}(),c=function(){var m=["Webkit","O","Moz","ms"],v={};function _(P){return P.replace(/^-ms-/,"ms-").replace(/-([\da-z])/gi,function(T,N){return N.toUpperCase()})}function g(P){var T=document.body.style;if(P in T)return P;for(var N=m.length,A=P.charAt(0).toUpperCase()+P.slice(1),D;N--;)if(D=m[N]+A,D in T)return D;return P}function E(P){return P=_(P),v[P]||(v[P]=g(P))}function S(P,T,N){T=E(T),P.style[T]=N}return function(P,T){var N=arguments,A,D;if(N.length==2)for(A in T)D=T[A],D!==void 0&&T.hasOwnProperty(A)&&S(P,A,D);else S(P,N[1],N[2])}}();function l(m,v){var _=typeof m=="string"?m:f(m);return _.indexOf(" "+v+" ")>=0}function u(m,v){var _=f(m),g=_+v;l(_,v)||(m.className=g.substring(1))}function d(m,v){var _=f(m),g;!l(m,v)||(g=_.replace(" "+v+" "," "),m.className=g.substring(1,g.length-1))}function f(m){return(" "+(m.className||"")+" ").replace(/\s+/gi," ")}function h(m){m&&m.parentNode&&m.parentNode.removeChild(m)}return n})})(Sr);const Qv=()=>{at(()=>{const e=no(),t=new Set;t.add(e.currentRoute.value.path),Sr.exports.configure({showSpinner:!1}),e.beforeEach(n=>{t.has(n.path)||Sr.exports.start()}),e.afterEach(n=>{t.add(n.path),Sr.exports.done()})})};var Yv=ki(()=>{Qv()}),Xv=ki(()=>{mh(),yh()});const Gv=[Zv,Yv,Xv],eg=[["v-8daa1a0e","/",{title:""},["/index.html","/README.md"]],["v-a38aa0ce","/Blog/announcing-jcl.html",{title:"A Modern JCL (Job Control Language) Editor"},["/Blog/announcing-jcl","/Blog/announcing-jcl.md"]],["v-fe48651a","/Blog/announcing-rexx.html",{title:"A Modern REXX Editor"},["/Blog/announcing-rexx","/Blog/announcing-rexx.md"]],["v-ed9f4f96","/Blog/announcing-zos-resources-table.html",{title:"Managing data sets, jobs, and UNIX files in Z Open Editor with the z/OS Resources Table"},["/Blog/announcing-zos-resources-table","/Blog/announcing-zos-resources-table.md"]],["v-8a4247d2","/Blog/code-snippets.html",{title:"Improve your z/OS enterprise developer productivity with IBM Z Open Editor\u2018s code snippets library"},["/Blog/code-snippets","/Blog/code-snippets.md"]],["v-0baade54","/Blog/external-posts.html",{title:"External Blog Posts and Articles"},["/Blog/external-posts","/Blog/external-posts.md"]],["v-1af1d74d","/Blog/hlasm-blog.html",{title:"IBM Z Open Editor: A modern IDE for IBM High Level Assembler"},["/Blog/hlasm-blog","/Blog/hlasm-blog.md"]],["v-48cb972d","/Blog/ibm-wazi-development-client-introduction-blog.html",{title:"Kubernetes-Native Integrated Z Developer Environment with IBM Wazi for Red Hat CodeReady Workspaces Development Client"},["/Blog/ibm-wazi-development-client-introduction-blog","/Blog/ibm-wazi-development-client-introduction-blog.md"]],["v-00ed1fd0","/Blog/in-the-cloud-with-che.html",{title:"IBM Z\xAE Open Editor in the cloud with Eclipse Che"},["/Blog/in-the-cloud-with-che","/Blog/in-the-cloud-with-che.md"]],["v-5a3683a7","/Blog/learning.html",{title:"Learning Resources"},["/Blog/learning","/Blog/learning.md"]],["v-4c46bc61","/Blog/new-content.html",{title:"New Content and Blog Posts"},["/Blog/new-content","/Blog/new-content.md"]],["v-7e9516cc","/Blog/new-releases.html",{title:"IBM Z Open Editor Releases"},["/Blog/new-releases","/Blog/new-releases.md"]],["v-a63a2e22","/Blog/ocp-ssl-cert.html",{title:"IBM Wazi Developer for Red Hat CodeReady Workspaces: Set up an SSL Certificate in an OpenShift Container Platform"},["/Blog/ocp-ssl-cert","/Blog/ocp-ssl-cert.md"]],["v-6fa9df51","/Blog/rse-march-120.html",{title:"Everything you need to know about IBM RSE API Plug-in for Zowe CLI 1.2.0"},["/Blog/rse-march-120","/Blog/rse-march-120.md"]],["v-0d011afc","/Blog/rse-march-beta.html",{title:"Interacting with z/OS using IBM RSE API Plug-in for Zowe CLI"},["/Blog/rse-march-beta","/Blog/rse-march-beta.md"]],["v-8483065a","/Blog/rse-october-110.html",{title:"What's new with IBM RSE API Plug-in for Zowe CLI 1.1.0"},["/Blog/rse-october-110","/Blog/rse-october-110.md"]],["v-5fac84d9","/Blog/userbuild-blog.html",{title:"IBM Z\xAE Open Editor makes building COBOL, PL/I, and HLASM applications easier with User Build"},["/Blog/userbuild-blog","/Blog/userbuild-blog.md"]],["v-4b9415f0","/Blog/web-based-with-theia.html",{title:"Running IBM Z\xAE Open Editor in the browser with Eclipse Theia"},["/Blog/web-based-with-theia","/Blog/web-based-with-theia.md"]],["v-68af98c9","/Blog/whats-new-120.html",{title:"Scaling up the audience with IBM Z Open Editor and Wazi Developer 1.2.0"},["/Blog/whats-new-120","/Blog/whats-new-120.md"]],["v-0ffb677e","/Docs/advanced_activation.html",{title:"Activating advanced capabilities"},["/Docs/advanced_activation","/Docs/advanced_activation.md"]],["v-4066bbc6","/Docs/advanced_custom_macros.html",{title:"Custom Macros for HLASM"},["/Docs/advanced_custom_macros","/Docs/advanced_custom_macros.md"]],["v-20708584","/Docs/advanced_overview.html",{title:"Overview"},["/Docs/advanced_overview","/Docs/advanced_overview.md"]],["v-a6691fb0","/Docs/advanced_preprocessor.html",{title:"Preprocessor support"},["/Docs/advanced_preprocessor","/Docs/advanced_preprocessor.md"]],["v-ae2b9dea","/Docs/advanced_problems_view.html",{title:"User build Problems view"},["/Docs/advanced_problems_view","/Docs/advanced_problems_view.md"]],["v-01e2125a","/Docs/advanced_resource_table.html",{title:"z/OS Resources Table"},["/Docs/advanced_resource_table","/Docs/advanced_resource_table.md"]],["v-2a14c510","/Docs/connect_to_zos_with_zowe_cli_e2e.html",{title:"Connecting to z/OS using Zowe CLI walk through"},["/Docs/connect_to_zos_with_zowe_cli_e2e","/Docs/connect_to_zos_with_zowe_cli_e2e.md"]],["v-175f1e49","/Docs/connect_to_zos_with_zowe_explorer_e2e.html",{title:"Connecting to z/OS with Zowe Explorer walk through"},["/Docs/connect_to_zos_with_zowe_explorer_e2e","/Docs/connect_to_zos_with_zowe_explorer_e2e.md"]],["v-26fabd50","/Docs/creating_team_profiles.html",{title:"Creating a configuration profile in Zowe Explorer v2.0.0"},["/Docs/creating_team_profiles","/Docs/creating_team_profiles.md"]],["v-e76197e2","/Docs/customizing_the_outline_view.html",{title:"Customizing the Outline view"},["/Docs/customizing_the_outline_view","/Docs/customizing_the_outline_view.md"]],["v-a2f185cc","/Docs/ebcdic_encoding.html",{title:"EBCDIC code pages and mappings files"},["/Docs/ebcdic_encoding","/Docs/ebcdic_encoding.md"]],["v-391d428c","/Docs/editor_codechanges.html",{title:"Making COBOL and PL/I code changes"},["/Docs/editor_codechanges","/Docs/editor_codechanges.md"]],["v-1c58a9fc","/Docs/editor_codechanges_hlasm.html",{title:"Making High Level Assembler code changes"},["/Docs/editor_codechanges_hlasm","/Docs/editor_codechanges_hlasm.md"]],["v-bb18cdb4","/Docs/editor_codechanges_jcl.html",{title:"Making JCL code changes"},["/Docs/editor_codechanges_jcl","/Docs/editor_codechanges_jcl.md"]],["v-13c01586","/Docs/editor_codechanges_rexx.html",{title:"Making REXX code changes"},["/Docs/editor_codechanges_rexx","/Docs/editor_codechanges_rexx.md"]],["v-10307d7a","/Docs/editor_search.html",{title:"Searching for COBOL, PL/I, HLASM, and REXX components"},["/Docs/editor_search","/Docs/editor_search.md"]],["v-9b8c1724","/Docs/getting_started.html",{title:"Getting started with IBM Z Open Editor"},["/Docs/getting_started","/Docs/getting_started.md"]],["v-afd18aa6","/Docs/git_integration.html",{title:"Using the integrated Git"},["/Docs/git_integration","/Docs/git_integration.md"]],["v-1251ae42","/Docs/interact_common_properties_cli.html",{title:"Interact with RSE Common Properties"},["/Docs/interact_common_properties_cli","/Docs/interact_common_properties_cli.md"]],["v-f89d1930","/Docs/interact_zos_cli.html",{title:"Using command line to interact with z/OS"},["/Docs/interact_zos_cli","/Docs/interact_zos_cli.md"]],["v-30184cb1","/Docs/interact_zos_overview.html",{title:"Interacting with z/OS"},["/Docs/interact_zos_overview","/Docs/interact_zos_overview.md"]],["v-3c830012","/Docs/interact_zos_zopeneditor.html",{title:"Using Zowe profiles in Z Open Editor"},["/Docs/interact_zos_zopeneditor","/Docs/interact_zos_zopeneditor.md"]],["v-60c4e326","/Docs/interact_zos_zowe_explorer.html",{title:"Using the Zowe Explorer views"},["/Docs/interact_zos_zowe_explorer","/Docs/interact_zos_zowe_explorer.md"]],["v-22d1c484","/Docs/introduction.html",{title:"Introduction"},["/Docs/introduction","/Docs/introduction.md"]],["v-823d11d2","/Docs/knownissues.html",{title:"Known issues and limitations"},["/Docs/knownissues","/Docs/knownissues.md"]],["v-93378d76","/Docs/language_references.html",{title:"Language References"},["/Docs/language_references","/Docs/language_references.md"]],["v-ab2cfe42","/Docs/locating_local_client_logs.html",{title:"Troubleshooting using log files"},["/Docs/locating_local_client_logs","/Docs/locating_local_client_logs.md"]],["v-f90f4ac6","/Docs/migrating_profiles.html",{title:"Migrating your old Zowe yaml profiles for Zowe v2.0"},["/Docs/migrating_profiles","/Docs/migrating_profiles.md"]],["v-065bea79","/Docs/notices.html",{title:"Notices"},["/Docs/notices","/Docs/notices.md"]],["v-e100f1ca","/Docs/other_extensions.html",{title:"Other Visual Studio Code extensions"},["/Docs/other_extensions","/Docs/other_extensions.md"]],["v-9629110c","/Docs/privacypolicy.html",{title:"Privacy policy considerations"},["/Docs/privacypolicy","/Docs/privacypolicy.md"]],["v-4aeeafba","/Docs/rse_cli_command.html",{title:"IBM RSE API Plug-in for Zowe CLI commands"},["/Docs/rse_cli_command","/Docs/rse_cli_command.md"]],["v-52b0a105","/Docs/rse_tutorial.html",{title:"Managing z/OS resources with IBM RSE API Plug-in for Zowe CLI tutorial"},["/Docs/rse_tutorial","/Docs/rse_tutorial.md"]],["v-9498fc72","/Docs/samplefiles.html",{title:"Exploring the sample files"},["/Docs/samplefiles","/Docs/samplefiles.md"]],["v-9dcc581e","/Docs/setting_compiler_options.html",{title:"Setting compiler options"},["/Docs/setting_compiler_options","/Docs/setting_compiler_options.md"]],["v-522078b2","/Docs/setting_disableproblems.html",{title:"Enabling and disabling problems in IBM Z Open Editor"},["/Docs/setting_disableproblems","/Docs/setting_disableproblems.md"]],["v-348a2d3e","/Docs/setting_fileassociations.html",{title:"Setting file associations"},["/Docs/setting_fileassociations","/Docs/setting_fileassociations.md"]],["v-3f4d9f11","/Docs/setting_maximum_line_length.html",{title:"Setting language-specific maximum line length"},["/Docs/setting_maximum_line_length","/Docs/setting_maximum_line_length.md"]],["v-3ae1cfcb","/Docs/setting_preferences.html",{title:"Setting preferences"},["/Docs/setting_preferences","/Docs/setting_preferences.md"]],["v-b824cc8e","/Docs/setting_propertygroup.html",{title:"Setting property groups"},["/Docs/setting_propertygroup","/Docs/setting_propertygroup.md"]],["v-0dd03d73","/Docs/setting_tabstops.html",{title:"Setting language-specific tab stops and rulers"},["/Docs/setting_tabstops","/Docs/setting_tabstops.md"]],["v-2a63b1ab","/Docs/setting_unreachablecodewarnings.html",{title:"Enabling and disabling unreachable COBOL code warnings"},["/Docs/setting_unreachablecodewarnings","/Docs/setting_unreachablecodewarnings.md"]],["v-8fabeeca","/Docs/settings.html",{title:"settings.json properties"},["/Docs/settings","/Docs/settings.md"]],["v-14aa9ebc","/Docs/setup_integration.html",{title:"Setting up integrations to interact with z/OS"},["/Docs/setup_integration","/Docs/setup_integration.md"]],["v-0791b3a2","/Docs/sharing_team_configuration_files.html",{title:"Sharing team configuration files"},["/Docs/sharing_team_configuration_files","/Docs/sharing_team_configuration_files.md"]],["v-d9943bba","/Docs/sharingfiles.html",{title:"Sharing files between VS Code extensions"},["/Docs/sharingfiles","/Docs/sharingfiles.md"]],["v-6676f350","/Docs/shortcut.html",{title:"Keyboard shortcuts reference"},["/Docs/shortcut","/Docs/shortcut.md"]],["v-45d644b0","/Docs/snippets.html",{title:"Using and managing code snippets"},["/Docs/snippets","/Docs/snippets.md"]],["v-7982067c","/Docs/trademarks.html",{title:"Trademarks"},["/Docs/trademarks","/Docs/trademarks.md"]],["v-492a8ebf","/Docs/tutorial_assembler.html",{title:"HLASM editing tutorial"},["/Docs/tutorial_assembler","/Docs/tutorial_assembler.md"]],["v-035874ac","/Docs/tutorial_cobol.html",{title:"COBOL editing tutorial"},["/Docs/tutorial_cobol","/Docs/tutorial_cobol.md"]],["v-70c1277a","/Docs/tutorial_overview.html",{title:"Tutorial overview"},["/Docs/tutorial_overview","/Docs/tutorial_overview.md"]],["v-6ab451c0","/Docs/tutorial_rexx.html",{title:"REXX editing tutorial"},["/Docs/tutorial_rexx","/Docs/tutorial_rexx.md"]],["v-64756ec4","/Docs/uninstalling.html",{title:"Uninstalling CLI plugins and VS Code extensions"},["/Docs/uninstalling","/Docs/uninstalling.md"]],["v-99d69e34","/Docs/userinterface.html",{title:"Exploring the user interface"},["/Docs/userinterface","/Docs/userinterface.md"]],["v-da074572","/Docs/using_code_snippets.html",{title:"Explore code snippets"},["/Docs/using_code_snippets","/Docs/using_code_snippets.md"]],["v-37f5df26","/Docs/whatsnew.html",{title:"Updates and user feedback"},["/Docs/whatsnew","/Docs/whatsnew.md"]],["v-43ab0a57","/Docs/zapp.html",{title:"Configuring your applications with ZAPP files"},["/Docs/zapp","/Docs/zapp.md"]],["v-4d589ea8","/Docs/zcodeformatting.html",{title:"Experimental: Formatting COBOL source code"},["/Docs/zcodeformatting","/Docs/zcodeformatting.md"]],["v-2d85c4b3","/Docs/zopeneditor_v3.html",{title:"Migrating from Z Open Editor v2 to v3"},["/Docs/zopeneditor_v3","/Docs/zopeneditor_v3.md"]],["v-41c85ba6","/Docs/zowe_advanced_connection_scenarious.html",{title:"Supported methods of authentication for z/OS using Zowe"},["/Docs/zowe_advanced_connection_scenarious","/Docs/zowe_advanced_connection_scenarious.md"]],["v-4b11bcde","/Docs/zowe_explorer_v2.html",{title:"Getting started with Zowe 2.0"},["/Docs/zowe_explorer_v2","/Docs/zowe_explorer_v2.md"]],["v-60b2a3bf","/Docs/zowe_submitjcl.html",{title:"Submitting JCL to compile, link, and run jobs tutorial"},["/Docs/zowe_submitjcl","/Docs/zowe_submitjcl.md"]],["v-3706649a","/404.html",{title:""},["/404"]]],tg=eg.reduce((e,[t,n,r,o])=>(e.push({name:t,path:n,component:Vs,meta:r},...o.map(i=>({path:i,redirect:n}))),e),[{name:"404",path:"/:catchAll(.*)",component:Vs}]),ng=yp,rg=()=>{const e=nm({history:ng(vm(wt.value.base)),routes:tg,scrollBehavior:(t,n,r)=>r||(t.hash?{el:t.hash}:{top:0})});return e.beforeResolve(async(t,n)=>{var r;(t.path!==n.path||n===ct)&&([ut.value]=await Promise.all([jt.resolvePageData(t.name),(r=vl[t.name])===null||r===void 0?void 0:r.__asyncLoader()]))}),e},og=e=>{e.component("ClientOnly",om),e.component("Content",ji)},ig=(e,t)=>{const n=Oe(()=>jt.resolveRouteLocale(wt.value.locales,t.currentRoute.value.path)),r=Oe(()=>jt.resolveSiteLocaleData(wt.value,n.value)),o=Oe(()=>jt.resolvePageFrontmatter(ut.value)),i=Oe(()=>jt.resolvePageHeadTitle(ut.value,r.value)),s=Oe(()=>jt.resolvePageHead(i.value,o.value,r.value)),a=Oe(()=>jt.resolvePageLang(ut.value));return e.provide(Li,n),e.provide(Dl,r),e.provide(bl,o),e.provide(um,i),e.provide(El,s),e.provide(Ol,a),Object.defineProperties(e.config.globalProperties,{$frontmatter:{get:()=>o.value},$head:{get:()=>s.value},$headTitle:{get:()=>i.value},$lang:{get:()=>a.value},$page:{get:()=>ut.value},$routeLocale:{get:()=>n.value},$site:{get:()=>wt.value},$siteLocale:{get:()=>r.value},$withBase:{get:()=>bm}}),{pageData:ut,pageFrontmatter:o,pageHead:s,pageHeadTitle:i,pageLang:a,routeLocale:n,siteData:wt,siteLocaleData:r}},sg=()=>{const e=xi(),t=lm(),n=wl(),r=Ne([]),o=()=>{t.value.forEach(s=>{const a=ag(s);a&&r.value.push(a)})},i=()=>{document.documentElement.lang=n.value,r.value.forEach(s=>{s.parentNode===document.head&&document.head.removeChild(s)}),r.value.splice(0,r.value.length),t.value.forEach(s=>{const a=cg(s);a!==null&&(document.head.appendChild(a),r.value.push(a))})};Bt(dm,i),at(()=>{o(),i(),et(()=>e.path,()=>i())})},ag=([e,t,n=""])=>{const r=Object.entries(t).map(([a,c])=>ve(c)?`[${a}="${c}"]`:c===!0?`[${a}]`:"").join(""),o=`head > ${e}${r}`;return Array.from(document.querySelectorAll(o)).find(a=>a.innerText===n)||null},cg=([e,t,n])=>{if(!ve(e))return null;const r=document.createElement(e);return Il(t)&&Object.entries(t).forEach(([o,i])=>{ve(i)?r.setAttribute(o,i):i===!0&&r.setAttribute(o,"")}),ve(n)&&r.appendChild(document.createTextNode(n)),r},lg=Gd,ug=async()=>{const e=lg({name:"VuepressApp",setup(){sg();for(const n of Gv)n();return()=>[be(_l),...Bv.map(n=>be(n))]}}),t=rg();og(e),ig(e,t);for(const n of zv)await n({app:e,router:t,siteData:wt});return e.use(t),{app:e,router:t}};ug().then(({app:e,router:t})=>{t.isReady().then(()=>{e.mount("#app")})});export{Pl as A,yg as B,Og as C,be as D,bm as E,Ve as F,om as G,Yn as H,Ne as I,et as J,pg as K,gg as L,gm as M,vm as N,no as O,ve as P,_h as Q,at as R,Kr as S,Ci as T,tr as U,wg as V,Il as W,vg as X,Si as Y,gh as Z,Zc as a,Yc as b,mg as c,ug as createVueApp,Se as d,Di as e,Qe as f,Nl as g,Ht as h,cm as i,Oe as j,ee as k,_g as l,hg as m,xi as n,Xr as o,dg as p,Jc as q,ld as r,hd as s,Tu as t,Sl as u,Xc as v,If as w,_m as x,bg as y,Eg as z};
diff --git a/assets/code-snippets.html.2aa24f4f.js b/assets/code-snippets.html.773a7c6a.js
similarity index 97%
rename from assets/code-snippets.html.2aa24f4f.js
rename to assets/code-snippets.html.773a7c6a.js
index b3256c074..eb099dd3d 100644
--- a/assets/code-snippets.html.2aa24f4f.js
+++ b/assets/code-snippets.html.773a7c6a.js
@@ -1 +1 @@
-import{r as n,o as r,a,b as e,d as s,F as i,e as t}from"./app.f6cb3ed9.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";var l="/zopeneditor-about/assets/zopeneditor-snippets.441c1cb7.gif";const p={},c=e("h1",{id:"improve-your-z-os-enterprise-developer-productivity-with-ibm-z-open-editor-s-code-snippets-library",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#improve-your-z-os-enterprise-developer-productivity-with-ibm-z-open-editor-s-code-snippets-library","aria-hidden":"true"},"#"),t(" Improve your z/OS enterprise developer productivity with IBM Z Open Editor\u2018s code snippets library")],-1),h=e("blockquote",null,[e("p",null,"by Peter Haumer and Jonathan Sayles")],-1),u=t("Learning a new technology such as a new programming language with its SDKs and APIs can be a daunting task. Even developers with years of experience often start a new programming assignment by first researching code in previous projects they worked on or other related work. The massive popularity of sites such as "),g={href:"https://stackoverflow.com",target:"_blank",rel:"noopener noreferrer"},m=t("https://stackoverflow.com"),_=t(" with its 11 M registered users shows that there is a big need for looking up best practices and standard solution patterns."),f=e("p",null,'For z/OS enterprise developers, this problem is worse as there is not a lot of information out there. We currently count only 440 question about z/OS on Stack Overflow out of a total of 19 M. So many new enterprise developers start new assignments by first going on an "archaeological dig\u201D in their organization following the popular "Monkey See, Monkey Do" development pattern, hunting down an existing program, copying the entire file, then cannibalizing the source, deleting most of the PROCEDURE and DATA DIVISION, editing the ENVIRONMENT and IDENTIFICATION DIVISIONs, etc. We might even have thought of this as a kind of haphazard "code reuse\u201D. Occasionally we might have wondered if there are some better and more structured ways to reuse production code in order to jump start program development.',-1),v=t("Production "),w={href:"https://en.wikipedia.org/wiki/Code_reuse",target:"_blank",rel:"noopener noreferrer"},b=t("code reuse"),y=t(" has long been an objective for software developers. There are at least three important reasons given for this:"),I=e("ul",null,[e("li",null,"Productivity: Reusing syntactically correct and working code takes less time to develop and test."),e("li",null,"Consistency and standards conformance: Maintenance and support costs are lowered as reusable code consists of recognizable patterns."),e("li",null,"Education: By leveraging a catalog of reusable functions, developers who are new to z/OS can be given working examples of advanced language, statements, and code patterns accelerating time to mastery.")],-1),k=t("With "),O={href:"https://ibm.github.io/zopeneditor-about",target:"_blank",rel:"noopener noreferrer"},S=t("IBM Z Open Editor"),M=t(", we want to provide a development environment that feels natural and modern for the next generation of enterprise developers and gives them the tools they need. So, in addition to providing the latest language and editing features, we also want to help new developers to get started quicker as well as experienced developers to have access to best practices."),z=t("To achieve that goal, we enlisted IBM's most experienced educators and services consultants to give use their treasure trove of code patterns that they felt provided the largest value to COBOL, PL/I, and JCL practitioners. Greg Lambert, form the IBM Z Open Editor team, curated these collections and provided them as code snippets available in the "),B={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},C=t("latest release of IBM Z Open Editor"),E=t(". The result is a library with a total of 186 snippets categorized as follows:"),x=e("ul",null,[e("li",null,"COBOL: 27 general COBOL language support snippets, 12 embedded SQL snippets, 29 CICS, 12 IMS, and 8 VSAM"),e("li",null,"PL/I: 12 general PL/I language support snippets, 29 CICS, 11 IMS, and 7 VSAM"),e("li",null,"JCL: 27 code snippets")],-1),L=e("p",null,"These snippets provide everything you need from elemental basic statement groups, to full sets of routines and paragraphs of business logic with full computations and complex conditional logic, and frequently used statements such as job cards, database routines, or complex COBOL code such as UNSTRING and many more.",-1),N=t("You can use these snippets for learning and as starting points for your own projects as well as use VS Code\u2019s ability to manage your own library of user-created snippets based on these. If you have already used code snippets with IBM Developer for Z (IDz), we even provide an Import command to load these snippets into IBM Z Open Editor as well. For information about how to insert code snippets, create your own code snippets, and import code snippets from IBM Developer for z/OS, see the "),T={href:"https://ibm.github.io/zopeneditor-about/Docs/snippets.html",target:"_blank",rel:"noopener noreferrer"},D=t("documentation"),V=t("."),Z=e("p",null,"The following animated GIF shows you a few examples for how to use IBM Z Open Editor's snippets.",-1),P=e("p",null,[e("img",{src:l,alt:"IBM Z Open Editor Code Snippets"})],-1),A=e("p",null,"Fig. 1: IBM Z Open Editor Code Snippets in action.",-1),F=t("Although we provide these snippets as-is, we would love to hear from you about the value of the current stack, what issues you found, as well as what other snippets we should add. You can submit issues to our "),j={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},R=t("github site"),q=t(" to start the discussion.");function G(J,W){const o=n("ExternalLinkIcon");return r(),a(i,null,[c,h,e("p",null,[u,e("a",g,[m,s(o)]),_]),f,e("p",null,[v,e("a",w,[b,s(o)]),y]),I,e("p",null,[k,e("a",O,[S,s(o)]),M]),e("p",null,[z,e("a",B,[C,s(o)]),E]),x,L,e("p",null,[N,e("a",T,[D,s(o)]),V]),Z,P,A,e("p",null,[F,e("a",j,[R,s(o)]),q])],64)}var H=d(p,[["render",G]]);export{H as default};
+import{r as n,o as r,a,b as e,d as s,F as i,e as t}from"./app.daa93c96.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";var l="/zopeneditor-about/assets/zopeneditor-snippets.441c1cb7.gif";const p={},c=e("h1",{id:"improve-your-z-os-enterprise-developer-productivity-with-ibm-z-open-editor-s-code-snippets-library",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#improve-your-z-os-enterprise-developer-productivity-with-ibm-z-open-editor-s-code-snippets-library","aria-hidden":"true"},"#"),t(" Improve your z/OS enterprise developer productivity with IBM Z Open Editor\u2018s code snippets library")],-1),h=e("blockquote",null,[e("p",null,"by Peter Haumer and Jonathan Sayles")],-1),u=t("Learning a new technology such as a new programming language with its SDKs and APIs can be a daunting task. Even developers with years of experience often start a new programming assignment by first researching code in previous projects they worked on or other related work. The massive popularity of sites such as "),g={href:"https://stackoverflow.com",target:"_blank",rel:"noopener noreferrer"},m=t("https://stackoverflow.com"),_=t(" with its 11 M registered users shows that there is a big need for looking up best practices and standard solution patterns."),f=e("p",null,'For z/OS enterprise developers, this problem is worse as there is not a lot of information out there. We currently count only 440 question about z/OS on Stack Overflow out of a total of 19 M. So many new enterprise developers start new assignments by first going on an "archaeological dig\u201D in their organization following the popular "Monkey See, Monkey Do" development pattern, hunting down an existing program, copying the entire file, then cannibalizing the source, deleting most of the PROCEDURE and DATA DIVISION, editing the ENVIRONMENT and IDENTIFICATION DIVISIONs, etc. We might even have thought of this as a kind of haphazard "code reuse\u201D. Occasionally we might have wondered if there are some better and more structured ways to reuse production code in order to jump start program development.',-1),v=t("Production "),w={href:"https://en.wikipedia.org/wiki/Code_reuse",target:"_blank",rel:"noopener noreferrer"},b=t("code reuse"),y=t(" has long been an objective for software developers. There are at least three important reasons given for this:"),I=e("ul",null,[e("li",null,"Productivity: Reusing syntactically correct and working code takes less time to develop and test."),e("li",null,"Consistency and standards conformance: Maintenance and support costs are lowered as reusable code consists of recognizable patterns."),e("li",null,"Education: By leveraging a catalog of reusable functions, developers who are new to z/OS can be given working examples of advanced language, statements, and code patterns accelerating time to mastery.")],-1),k=t("With "),O={href:"https://ibm.github.io/zopeneditor-about",target:"_blank",rel:"noopener noreferrer"},S=t("IBM Z Open Editor"),M=t(", we want to provide a development environment that feels natural and modern for the next generation of enterprise developers and gives them the tools they need. So, in addition to providing the latest language and editing features, we also want to help new developers to get started quicker as well as experienced developers to have access to best practices."),z=t("To achieve that goal, we enlisted IBM's most experienced educators and services consultants to give use their treasure trove of code patterns that they felt provided the largest value to COBOL, PL/I, and JCL practitioners. Greg Lambert, form the IBM Z Open Editor team, curated these collections and provided them as code snippets available in the "),B={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},C=t("latest release of IBM Z Open Editor"),E=t(". The result is a library with a total of 186 snippets categorized as follows:"),x=e("ul",null,[e("li",null,"COBOL: 27 general COBOL language support snippets, 12 embedded SQL snippets, 29 CICS, 12 IMS, and 8 VSAM"),e("li",null,"PL/I: 12 general PL/I language support snippets, 29 CICS, 11 IMS, and 7 VSAM"),e("li",null,"JCL: 27 code snippets")],-1),L=e("p",null,"These snippets provide everything you need from elemental basic statement groups, to full sets of routines and paragraphs of business logic with full computations and complex conditional logic, and frequently used statements such as job cards, database routines, or complex COBOL code such as UNSTRING and many more.",-1),N=t("You can use these snippets for learning and as starting points for your own projects as well as use VS Code\u2019s ability to manage your own library of user-created snippets based on these. If you have already used code snippets with IBM Developer for Z (IDz), we even provide an Import command to load these snippets into IBM Z Open Editor as well. For information about how to insert code snippets, create your own code snippets, and import code snippets from IBM Developer for z/OS, see the "),T={href:"https://ibm.github.io/zopeneditor-about/Docs/snippets.html",target:"_blank",rel:"noopener noreferrer"},D=t("documentation"),V=t("."),Z=e("p",null,"The following animated GIF shows you a few examples for how to use IBM Z Open Editor's snippets.",-1),P=e("p",null,[e("img",{src:l,alt:"IBM Z Open Editor Code Snippets"})],-1),A=e("p",null,"Fig. 1: IBM Z Open Editor Code Snippets in action.",-1),F=t("Although we provide these snippets as-is, we would love to hear from you about the value of the current stack, what issues you found, as well as what other snippets we should add. You can submit issues to our "),j={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},R=t("github site"),q=t(" to start the discussion.");function G(J,W){const o=n("ExternalLinkIcon");return r(),a(i,null,[c,h,e("p",null,[u,e("a",g,[m,s(o)]),_]),f,e("p",null,[v,e("a",w,[b,s(o)]),y]),I,e("p",null,[k,e("a",O,[S,s(o)]),M]),e("p",null,[z,e("a",B,[C,s(o)]),E]),x,L,e("p",null,[N,e("a",T,[D,s(o)]),V]),Z,P,A,e("p",null,[F,e("a",j,[R,s(o)]),q])],64)}var H=d(p,[["render",G]]);export{H as default};
diff --git a/assets/connect_to_zos_with_zowe_cli_e2e.html.f95d0eea.js b/assets/connect_to_zos_with_zowe_cli_e2e.html.a8e70c31.js
similarity index 98%
rename from assets/connect_to_zos_with_zowe_cli_e2e.html.f95d0eea.js
rename to assets/connect_to_zos_with_zowe_cli_e2e.html.a8e70c31.js
index b4c4e0877..60d73c94e 100644
--- a/assets/connect_to_zos_with_zowe_cli_e2e.html.f95d0eea.js
+++ b/assets/connect_to_zos_with_zowe_cli_e2e.html.a8e70c31.js
@@ -1 +1 @@
-import{r as n,o as s,a as c,b as o,d as t,w as r,F as d,c as l,e}from"./app.f6cb3ed9.js";import{_ as u}from"./plugin-vue_export-helper.21dcd24c.js";const p={},f=l('
     Connecting to z/OS using Zowe CLI walk through
     Creating a Zowe team configuration file
    1. Issue the zowe config init command and you will be prompted for profile information. After responding to the prompts, the zowe.config.json file will be added to your ~/.zowe directory.
      • Run zowe config init --global-config to create a global profile.
      • Run zowe config init --help to learn all options for editing profiles by using a command line.
      Note: This tutorial walks through creating a global profile. User scoped configuration is very similar except that the file is created in your project's folder and is named zowe.user.json. Run zowe config init --user-config to create a profile scoped to your project folder.
    2. If you responded to the prompts to enter a username and password for a mainframe service, your credentials are stored securely on your computer by default.
    3. Open the zowe.config.json file in any text editor that supports JSON files, and then update the host and port values and other information needed in the profiles that are listed in the configuration file.
    4. Fill out the rse or zosmf profile template inside zowe.config.json depending on which type of profile you are creating.
    5. You can also use the command line to set team configuration properties. For example, run zowe config set "profiles.host1.profiles.service1.properties.setting" "value" --global-configzowe config set --secure ... to set a secure property.
    6. If username and password were entered in step 1, you can use your profiles to access data sets, z/OS UNIX System Services files and directories, and jobs. If not entered, you will be prompted the first time you run a CLI command. If \u2018autoStore:true\u2019 is set in the configuration file, the credentials will be stored securely on your computer.
    ',3),h=e("For more information about team configuration profiles in Zowe, see "),m={href:"https://docs.zowe.org/stable/user-guide/cli-using-initializing-team-configuration",target:"_blank",rel:"noopener noreferrer"},_=e("Zowe CLI documentation"),g=e("."),w=e("For a Zowe team configuration file example, see "),z=e("here"),y=e("."),b=o("h2",{id:"supported-authentication-methods",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#supported-authentication-methods","aria-hidden":"true"},"#"),e(" Supported authentication methods")],-1),x=e("Zowe supports many authentication mechanisms and you are not limited to username and password only. For more information, see "),k=e("Supported methods of authentication for z/OS using Zowe"),I=e(".");function S(v,C){const a=n("ExternalLinkIcon"),i=n("RouterLink");return s(),c(d,null,[f,o("p",null,[h,o("a",m,[_,t(a)]),g]),o("p",null,[w,t(i,{to:"/Docs/connect_to_zos_with_zowe_explorer_e2e.html#Zowe-Team-Configuration-file-example"},{default:r(()=>[z]),_:1}),y]),b,o("p",null,[x,t(i,{to:"/Docs/zowe_advanced_connection_scenarious.html"},{default:r(()=>[k]),_:1}),I])],64)}var F=u(p,[["render",S]]);export{F as default};
+import{r as n,o as s,a as c,b as o,d as t,w as r,F as d,c as l,e}from"./app.daa93c96.js";import{_ as u}from"./plugin-vue_export-helper.21dcd24c.js";const p={},f=l('
     Connecting to z/OS using Zowe CLI walk through
     Creating a Zowe team configuration file
    1. Issue the zowe config init command and you will be prompted for profile information. After responding to the prompts, the zowe.config.json file will be added to your ~/.zowe directory.
      • Run zowe config init --global-config to create a global profile.
      • Run zowe config init --help to learn all options for editing profiles by using a command line.
      Note: This tutorial walks through creating a global profile. User scoped configuration is very similar except that the file is created in your project's folder and is named zowe.user.json. Run zowe config init --user-config to create a profile scoped to your project folder.
    2. If you responded to the prompts to enter a username and password for a mainframe service, your credentials are stored securely on your computer by default.
    3. Open the zowe.config.json file in any text editor that supports JSON files, and then update the host and port values and other information needed in the profiles that are listed in the configuration file.
    4. Fill out the rse or zosmf profile template inside zowe.config.json depending on which type of profile you are creating.
    5. You can also use the command line to set team configuration properties. For example, run zowe config set "profiles.host1.profiles.service1.properties.setting" "value" --global-configzowe config set --secure ... to set a secure property.
    6. If username and password were entered in step 1, you can use your profiles to access data sets, z/OS UNIX System Services files and directories, and jobs. If not entered, you will be prompted the first time you run a CLI command. If \u2018autoStore:true\u2019 is set in the configuration file, the credentials will be stored securely on your computer.
    ',3),h=e("For more information about team configuration profiles in Zowe, see "),m={href:"https://docs.zowe.org/stable/user-guide/cli-using-initializing-team-configuration",target:"_blank",rel:"noopener noreferrer"},_=e("Zowe CLI documentation"),g=e("."),w=e("For a Zowe team configuration file example, see "),z=e("here"),y=e("."),b=o("h2",{id:"supported-authentication-methods",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#supported-authentication-methods","aria-hidden":"true"},"#"),e(" Supported authentication methods")],-1),x=e("Zowe supports many authentication mechanisms and you are not limited to username and password only. For more information, see "),k=e("Supported methods of authentication for z/OS using Zowe"),I=e(".");function S(v,C){const a=n("ExternalLinkIcon"),i=n("RouterLink");return s(),c(d,null,[f,o("p",null,[h,o("a",m,[_,t(a)]),g]),o("p",null,[w,t(i,{to:"/Docs/connect_to_zos_with_zowe_explorer_e2e.html#Zowe-Team-Configuration-file-example"},{default:r(()=>[z]),_:1}),y]),b,o("p",null,[x,t(i,{to:"/Docs/zowe_advanced_connection_scenarious.html"},{default:r(()=>[k]),_:1}),I])],64)}var F=u(p,[["render",S]]);export{F as default};
diff --git a/assets/connect_to_zos_with_zowe_explorer_e2e.html.2dc20d7e.js b/assets/connect_to_zos_with_zowe_explorer_e2e.html.8894ef57.js
similarity index 99%
rename from assets/connect_to_zos_with_zowe_explorer_e2e.html.2dc20d7e.js
rename to assets/connect_to_zos_with_zowe_explorer_e2e.html.8894ef57.js
index ddd7dc3d6..d9489a0a2 100644
--- a/assets/connect_to_zos_with_zowe_explorer_e2e.html.2dc20d7e.js
+++ b/assets/connect_to_zos_with_zowe_explorer_e2e.html.8894ef57.js
@@ -1,4 +1,4 @@
-import{r as p,o as l,a as c,b as n,d as e,w as r,F as i,c as o,e as s}from"./app.f6cb3ed9.js";import{_ as u}from"./plugin-vue_export-helper.21dcd24c.js";const d={},h=o('
     Connecting to z/OS with Zowe Explorer walk through
     Overview
    Zowe Explorer VS Code extension adds support for connecting to z/OS, and the connection details are specified in the team configuration file. The team configuration file is a JSON file that contains definitions for profiles to connect to z/OS by using different methods such as RSE API, z/OSMF API, SSH, and FTP. Zowe framework is open source and supports extenders, so there might be more ways to connect in the future. One team configuration file can contain many individual profiles, and it can be located in your home directory .zowe folder or added to a Git repository.
    You can create and edit a team configuration file in multiple ways such as Zowe CLI. This tutorial will walk you through the steps on how to manage connection profiles by using Zowe Explorer UI.
     Prerequisites
    ',5),k=n("li",null,"On the client side: Ensure that Z Open Editor and Zowe Explorer VS Code extension are installed in your VS Code.",-1),m=s("On the server side: Check with your system administrator to ensure RSE API or z/OSMF api is installed and which ports it can be accessed on. Often, RSE API is installed on port 7395, sometimes 8195 or 6800, and z/OSMF is often available on port 443 or 10443. Those default ports can be changed. For more information, see "),b={href:"https://www.ibm.com/docs/en/explorer-for-zos/3.3?topic=documentation-rse-api",target:"_blank",rel:"noopener noreferrer"},f=s("installing RSE API"),g=s(" and "),q={href:"https://www.ibm.com/docs/en/zos/2.3.0?topic=guide-configuration",target:"_blank",rel:"noopener noreferrer"},y=s("installing z/OSMF API"),_=s("."),w=n("h2",{id:"creating-a-team-configuration-file",tabindex:"-1"},[n("a",{class:"header-anchor",href:"#creating-a-team-configuration-file","aria-hidden":"true"},"#"),s(" Creating a team configuration file")],-1),z=n("p",null,"You can create a team configuration file by using Zowe Explorer UI. After the team configuration file is created, it can be used by both Zowe Explorer and Zowe CLI.",-1),E=o("
  • Open the Zowe Explorer view in VS Code.
  • Click the Add profile... plus button in the Data sets, UNIX System Services, or Jobs view.
  • Click Create a new Team Configuration file.
  • Choose if you want a file to be accesed globally or just in the current project.
    • If you want to access the file in any project, select Global.
    • If you want to access the file in the current Git project only, select Project.
    Now Zowe Explorer will create zowe.config.json in ~/.zowe directory or zowe.config.user.json inside your repo. This file contains default values and supported extender profile definitions. Because Z Open editor is installed, the team configuration file is created with the RSE profile template.
  • Specify the profiles with your connection details. You can enter common values such as host in the base profile, which will then be applied to the entire team configuration file.
  • You can hover over each JSON key in the file for explanation of each option.
    • ",6),S=n("p",null,"Specify the values as needed according to your connection type.",-1),x=n("li",null,[s("Connect to zOS with RSE API "),n("ul",null,[n("li",null,[s("Ensure that you can access RSE API using correct port. Swagger API doc should be available on the port, for example, "),n("code",null,"https://myzos.ibm.com:6800/rseapi/api-docs/"),s(".")]),n("li",null,[s("If you have "),n("code",null,"zowe cli"),s(" with "),n("code",null,"rse-api-for-zowe-cli"),s(" plug-in installed, use the "),n("code",null,"zowe rse check status"),s(" command to confirm that RSE API is running on port specified in the profile.")])])],-1),v=s("Connect to z/OS z/OSMF API "),I=s("Check out "),O={href:"https://docs.zowe.org/stable/troubleshoot/cli/z/OSMF-cli/",target:"_blank",rel:"noopener noreferrer"},P=s("z/OSMF connection troubleshooting guide"),A=s("."),C=n("li",null,[n("p",null,"Save your changes. Profiles should be ready to be added to each tree view.")],-1),Z=n("li",null,[n("p",null,"In Zowe Explorer, go to the tree of your choice and add the profile by clicking the plus button.")],-1),R=n("li",null,[n("p",null,[s("To re-open and update team configuration file, click "),n("strong",null,"Add profile... > Edit Team Configuration file"),s(".")])],-1),F=s("After you start using the Zowe Explorer tree views, you will be prompted to enter username and password. On the desktop, Zowe Explorer stores encrypted credentials on the user's local system in the local operation system specific way, such as the Keychain on Mac OS. If you are using a different authentication method, see "),j=s("Supported methods of authentication for z/OS using Zowe"),T=s("."),N=o(`
     Zowe team configuration file example
    {
+import{r as p,o as l,a as c,b as n,d as e,w as r,F as i,c as o,e as s}from"./app.daa93c96.js";import{_ as u}from"./plugin-vue_export-helper.21dcd24c.js";const d={},h=o('
     Connecting to z/OS with Zowe Explorer walk through
     Overview
    Zowe Explorer VS Code extension adds support for connecting to z/OS, and the connection details are specified in the team configuration file. The team configuration file is a JSON file that contains definitions for profiles to connect to z/OS by using different methods such as RSE API, z/OSMF API, SSH, and FTP. Zowe framework is open source and supports extenders, so there might be more ways to connect in the future. One team configuration file can contain many individual profiles, and it can be located in your home directory .zowe folder or added to a Git repository.
    You can create and edit a team configuration file in multiple ways such as Zowe CLI. This tutorial will walk you through the steps on how to manage connection profiles by using Zowe Explorer UI.
     Prerequisites
    ',5),k=n("li",null,"On the client side: Ensure that Z Open Editor and Zowe Explorer VS Code extension are installed in your VS Code.",-1),m=s("On the server side: Check with your system administrator to ensure RSE API or z/OSMF api is installed and which ports it can be accessed on. Often, RSE API is installed on port 7395, sometimes 8195 or 6800, and z/OSMF is often available on port 443 or 10443. Those default ports can be changed. For more information, see "),b={href:"https://www.ibm.com/docs/en/explorer-for-zos/3.3?topic=documentation-rse-api",target:"_blank",rel:"noopener noreferrer"},f=s("installing RSE API"),g=s(" and "),q={href:"https://www.ibm.com/docs/en/zos/2.3.0?topic=guide-configuration",target:"_blank",rel:"noopener noreferrer"},y=s("installing z/OSMF API"),_=s("."),w=n("h2",{id:"creating-a-team-configuration-file",tabindex:"-1"},[n("a",{class:"header-anchor",href:"#creating-a-team-configuration-file","aria-hidden":"true"},"#"),s(" Creating a team configuration file")],-1),z=n("p",null,"You can create a team configuration file by using Zowe Explorer UI. After the team configuration file is created, it can be used by both Zowe Explorer and Zowe CLI.",-1),E=o("
  • Open the Zowe Explorer view in VS Code.
  • Click the Add profile... plus button in the Data sets, UNIX System Services, or Jobs view.
  • Click Create a new Team Configuration file.
  • Choose if you want a file to be accesed globally or just in the current project.
    • If you want to access the file in any project, select Global.
    • If you want to access the file in the current Git project only, select Project.
    Now Zowe Explorer will create zowe.config.json in ~/.zowe directory or zowe.config.user.json inside your repo. This file contains default values and supported extender profile definitions. Because Z Open editor is installed, the team configuration file is created with the RSE profile template.
  • Specify the profiles with your connection details. You can enter common values such as host in the base profile, which will then be applied to the entire team configuration file.
  • You can hover over each JSON key in the file for explanation of each option.
    • ",6),S=n("p",null,"Specify the values as needed according to your connection type.",-1),x=n("li",null,[s("Connect to zOS with RSE API "),n("ul",null,[n("li",null,[s("Ensure that you can access RSE API using correct port. Swagger API doc should be available on the port, for example, "),n("code",null,"https://myzos.ibm.com:6800/rseapi/api-docs/"),s(".")]),n("li",null,[s("If you have "),n("code",null,"zowe cli"),s(" with "),n("code",null,"rse-api-for-zowe-cli"),s(" plug-in installed, use the "),n("code",null,"zowe rse check status"),s(" command to confirm that RSE API is running on port specified in the profile.")])])],-1),v=s("Connect to z/OS z/OSMF API "),I=s("Check out "),O={href:"https://docs.zowe.org/stable/troubleshoot/cli/z/OSMF-cli/",target:"_blank",rel:"noopener noreferrer"},P=s("z/OSMF connection troubleshooting guide"),A=s("."),C=n("li",null,[n("p",null,"Save your changes. Profiles should be ready to be added to each tree view.")],-1),Z=n("li",null,[n("p",null,"In Zowe Explorer, go to the tree of your choice and add the profile by clicking the plus button.")],-1),R=n("li",null,[n("p",null,[s("To re-open and update team configuration file, click "),n("strong",null,"Add profile... > Edit Team Configuration file"),s(".")])],-1),F=s("After you start using the Zowe Explorer tree views, you will be prompted to enter username and password. On the desktop, Zowe Explorer stores encrypted credentials on the user's local system in the local operation system specific way, such as the Keychain on Mac OS. If you are using a different authentication method, see "),j=s("Supported methods of authentication for z/OS using Zowe"),T=s("."),N=o(`
     Zowe team configuration file example
    {
   "$schema": "./zowe.schema.json",
   "profiles": {
     "zosmf": {
diff --git a/assets/creating_team_profiles.html.434e681f.js b/assets/creating_team_profiles.html.1f9ba16f.js
similarity index 99%
rename from assets/creating_team_profiles.html.434e681f.js
rename to assets/creating_team_profiles.html.1f9ba16f.js
index 23cb80889..efcc0e69c 100644
--- a/assets/creating_team_profiles.html.434e681f.js
+++ b/assets/creating_team_profiles.html.1f9ba16f.js
@@ -1,4 +1,4 @@
-import{r as a,o,a as r,b as e,d as t,F as u,c as i,e as n}from"./app.f6cb3ed9.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";const p={},c=i(`
     Creating a configuration profile in Zowe Explorer v2.0.0
     Initializing the configuration file
    A team configuration profile can be created using Zowe CLI or Zowe Explorer VS Code Extension in the following ways:
     Zowe CLI
    Run zowe config init --global-config which will prompt for a username and password once the command is issued.
     Zowe Explorer VS Code Extension
    1. Click the Zowe icon on the left side bar of your VS Code window.
    2. Click the + symbol in tree view of Zowe Explorer.
    3. Select Create a New Team Configuration File when prompted in the input box shown.
    4. If no workspace is opened a global configuration will be created in your ~/.zowe directory and opened in the VS Code text editor. If a workspace is opened a following prompt will be presented for the user to select global or project level config, a project level config will be created in the top level of the workspace. After selecting the appropriate file, the file will be opened in the text editor.
    5. Add host and port properties to the loaded file after creating the configuration file.
     Examples of configuration files
    A default team configuration file will look like this upon creation:
    {
+import{r as a,o,a as r,b as e,d as t,F as u,c as i,e as n}from"./app.daa93c96.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";const p={},c=i(`
     Creating a configuration profile in Zowe Explorer v2.0.0
     Initializing the configuration file
    A team configuration profile can be created using Zowe CLI or Zowe Explorer VS Code Extension in the following ways:
     Zowe CLI
    Run zowe config init --global-config which will prompt for a username and password once the command is issued.
     Zowe Explorer VS Code Extension
    1. Click the Zowe icon on the left side bar of your VS Code window.
    2. Click the + symbol in tree view of Zowe Explorer.
    3. Select Create a New Team Configuration File when prompted in the input box shown.
    4. If no workspace is opened a global configuration will be created in your ~/.zowe directory and opened in the VS Code text editor. If a workspace is opened a following prompt will be presented for the user to select global or project level config, a project level config will be created in the top level of the workspace. After selecting the appropriate file, the file will be opened in the text editor.
    5. Add host and port properties to the loaded file after creating the configuration file.
     Examples of configuration files
    A default team configuration file will look like this upon creation:
    {
     "$schema": "./zowe.schema.json",
     "profiles": {
         "zosmf": {
diff --git a/assets/customizing_the_outline_view.html.bee5c0a0.js b/assets/customizing_the_outline_view.html.12952224.js
similarity index 99%
rename from assets/customizing_the_outline_view.html.bee5c0a0.js
rename to assets/customizing_the_outline_view.html.12952224.js
index a62871f31..c3b63481d 100644
--- a/assets/customizing_the_outline_view.html.bee5c0a0.js
+++ b/assets/customizing_the_outline_view.html.12952224.js
@@ -1 +1 @@
-import{r as _,o as q,a as v,b as t,d as w,w as E,F as f,e,c as S}from"./app.f6cb3ed9.js";import{_ as x}from"./plugin-vue_export-helper.21dcd24c.js";var O="/zopeneditor-about/assets/outline-view-setting.b4ce3a90.png",I="/zopeneditor-about/assets/symbol-boolean.67fe0ec5.svg",s="/zopeneditor-about/assets/symbol-class.1c1e7bad.svg",N="/zopeneditor-about/assets/symbol-constant.9230d4cc.svg",C="/zopeneditor-about/assets/symbol-constructor.aa1a521a.svg",L="/zopeneditor-about/assets/symbol-enum-member.c679be34.svg",T="/zopeneditor-about/assets/symbol-enum.c3b0e764.svg",d="/zopeneditor-about/assets/symbol-event.9857cb6a.svg",r="/zopeneditor-about/assets/symbol-field.1539335c.svg",i="/zopeneditor-about/assets/symbol-file.99381fd8.svg",l="/zopeneditor-about/assets/symbol-constructor.aa1a521a.svg",o="/zopeneditor-about/assets/symbol-interface.00c4e4d1.svg",A="/zopeneditor-about/assets/symbol-key.bd8968a2.svg",c="/zopeneditor-about/assets/symbol-constructor.aa1a521a.svg",R="/zopeneditor-about/assets/symbol-module.f4bddde3.svg",u="/zopeneditor-about/assets/symbol-module.f4bddde3.svg",D="/zopeneditor-about/assets/symbol-number.e0ff525e.svg",a="/zopeneditor-about/assets/symbol-module.f4bddde3.svg",m="/zopeneditor-about/assets/symbol-operator.38b9457e.svg",h="/zopeneditor-about/assets/symbol-module.f4bddde3.svg",b="/zopeneditor-about/assets/symbol-property.cfa06206.svg",g="/zopeneditor-about/assets/symbol-string.393a611a.svg",y="/zopeneditor-about/assets/symbol-struct.e9fb1591.svg",V="/zopeneditor-about/assets/symbol-type-parameter.b47038bb.svg",n="/zopeneditor-about/assets/symbol-variable.8eabb338.svg";const z={},P=t("h1",{id:"customizing-the-outline-view",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#customizing-the-outline-view","aria-hidden":"true"},"#"),e(" Customizing the Outline view")],-1),B=t("p",null,"The Outline view shows a symbol tree of the currently active editor. IBM Z Open Editor maps each symbol to a language element of COBOL, PL/I, HLASM, and REXX.",-1),F=t("p",null,"However, you might not want every symbol to display in the Outline view. To control which ones appear, you can modify the User or Workspace settings. At this time, the REXX Outline view displays the internal routine symbol only.",-1),U=t("h2",{id:"enabling-or-disabling-outline-view-symbols",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#enabling-or-disabling-outline-view-symbols","aria-hidden":"true"},"#"),e(" Enabling or disabling Outline view symbols")],-1),k=t("p",null,"Navigate to your User and Workspace settings using the following VS Code menu command:",-1),M=t("ul",null,[t("li",null,[e("Windows/Linux: "),t("strong",null,"File > Preferences > Settings")]),t("li",null,[e("MacOS: "),t("strong",null,"Code > Preferences > Settings")])],-1),H=e("Note: VS Code provides different scopes for defining these settings. For more information, see "),G=e("User preferences versus workspace preferences"),X=e("."),J=t("li",null,[t("p",null,[e("Type "),t("code",null,"Outline"),e(" in the search box to filter the settings.")])],-1),j=t("li",null,[t("p",null,[e("Enable or disable the Outline view settings based on your needs. Refer to the "),t("a",{href:"#outline-view-symbol-mapping-reference"},"Outline view symbol mapping reference"),e(" to understand which settings affect which symbols.")])],-1),W=S('
    If you would rather modify the Outline view settings in their raw JSON form, run one of the following commands using the Command Palette. Note that it is not recommended to change the Default settings.
    Command Palette (\u21E7\u2318P) (Ctrl+Shift+P)Settings
    > Open Settings (JSON)User
    > Open Default Settings (JSON)Default
    > Open Workspace Settings (JSON)Workspace
     Outline view symbol mapping reference
    Note that some symbols are used more than once. This is expected behavior.
    This table highlights the relationship between Outline view settings in JSON form and UI form.
    JSONSettings Editor
    "outline.showBooleans":trueoutline-view-setting
     COBOL
    SymbolCOBOL Language ElementVisual Studio Code Setting
    symbol-booleanPROCEDURE_DIVISION"outline.showBooleans":true
    symbol-classDIRECTIVE"outline.showClasses":true
    symbol-constantPROG_ID"outline.showConstants":true
    symbol-constructorDATA_DIVISION"outline.showConstructors":true
    symbol-enum-memberMAINLINE_SECTION"outline.showEnumMembers":true
    symbol-enumLINKAGE_SECTION"outline.showEnums":true
    symbol-eventWORKING_STORAGE_SECTION"outline.showEvents":true
    symbol-fieldPROCESS"outline.showFields":true
    symbol-fileROOT"outline.showFiles":true
    symbol-functionPARAGRAPH"outline.showFunctions":true
    symbol-interfaceENVIRONMENT_DIVISION"outline.showInterfaces":true
    symbol-keyDECLARATIVES"outline.showKeys":true
    symbol-methodANY_OTHER_SECTION"outline.showMethods":true
    symbol-moduleCONFIGURATION_SECTION"outline.showModules":true
    symbol-namespaceCOPY"outline.showNamespaces":true
    symbol-numberANY_OTHER_DIVISION"outline.showNumbers":true
    symbol-objectLOCAL_STORAGE_SECTION"outline.showObjects":true
    symbol-operatorEND"outline.showOperators":true
    symbol-packagePROGRAM"outline.showPackages":true
    symbol-propertyIDENTIFICATION_DIVISION, ID_DIVISION"outline.showProperties":true
    symbol-stringLEVEL_1_HAS_SUBFIELDS, LEVEL_INDICATOR"outline.showStrings":true
    symbol-structFILE_SECTION"outline.showStructs":true
    symbol-type-parameterINPUT_OUTPUT_SECTION"outline.showTypeParameters":true
    symbol-variableLEVEL_1_HAS_NO_SUBFIELDS, LEVEL_3, LEVEL_X"outline.showVariables":true
     PL/I
    SymbolPL/I Language ElementVisual Studio Code Setting
    symbol-classPROCEDURE"outline.showClasses":true
    symbol-eventEVENT"outline.showEvents":true
    symbol-fieldDATAITEM_HAS_SUBFIELDS"outline.showFields":true
    symbol-fileROOT"outline.showFiles":true
    symbol-functionPACKAGE"outline.showFunctions":true
    symbol-interfaceLABEL"outline.showInterfaces":true
    symbol-methodREVERT"outline.showMethods":true
    symbol-namespaceINCLUDE"outline.showNamespaces":true
    symbol-operatorEND"outline.showOperators":true
    symbol-packageBEGIN"outline.showPackages":true
    symbol-variableDATAITEM_HAS_NO_SUBFIELDS"outline.showVariables":true
     HLASM
    SymbolHLASM Language ElementVisual Studio Code Setting
    symbol-classBRANCH_LABELS"outline.showClasses":true
    symbol-functionCSECT"outline.showFunctions":true
    symbol-objectMACRO"outline.showObjects":true
    symbol-structDSECT"outline.showStructs":true
    symbol-structRSECT"outline.showStrings":true
    symbol-structCOM"outline.showInterfaces":true
    symbol-structLOCTR"outline.showProperties":true
    symbol-structLABEL"outline.showVariables":true
     REXX
    SymbolREXX Language ElementVisual Studio Code Setting
    symbol-objectINTERNAL ROUTINE"outline.showObjects":true
     JCL
    SymbolJCL Language ElementVisual Studio Code Setting
    symbol-fieldDD Statement"outline.showFields":true
    symbol-interfaceEXEC Statement"outline.showInteraces":true
    symbol-eventJOB Statement"outline.showEvents":true
    ',16);function K(Y,Z){const p=_("RouterLink");return q(),v(f,null,[P,B,F,U,t("ol",null,[t("li",null,[k,M,t("p",null,[H,w(p,{to:"/Docs/setting_preferences.html#user-preferences-versus-workspace-preferences"},{default:E(()=>[G]),_:1}),X])]),J,j]),W],64)}var tt=x(z,[["render",K]]);export{tt as default};
+import{r as _,o as q,a as v,b as t,d as w,w as E,F as f,e,c as S}from"./app.daa93c96.js";import{_ as x}from"./plugin-vue_export-helper.21dcd24c.js";var O="/zopeneditor-about/assets/outline-view-setting.b4ce3a90.png",I="/zopeneditor-about/assets/symbol-boolean.67fe0ec5.svg",s="/zopeneditor-about/assets/symbol-class.1c1e7bad.svg",N="/zopeneditor-about/assets/symbol-constant.9230d4cc.svg",C="/zopeneditor-about/assets/symbol-constructor.aa1a521a.svg",L="/zopeneditor-about/assets/symbol-enum-member.c679be34.svg",T="/zopeneditor-about/assets/symbol-enum.c3b0e764.svg",d="/zopeneditor-about/assets/symbol-event.9857cb6a.svg",r="/zopeneditor-about/assets/symbol-field.1539335c.svg",i="/zopeneditor-about/assets/symbol-file.99381fd8.svg",l="/zopeneditor-about/assets/symbol-constructor.aa1a521a.svg",o="/zopeneditor-about/assets/symbol-interface.00c4e4d1.svg",A="/zopeneditor-about/assets/symbol-key.bd8968a2.svg",c="/zopeneditor-about/assets/symbol-constructor.aa1a521a.svg",R="/zopeneditor-about/assets/symbol-module.f4bddde3.svg",u="/zopeneditor-about/assets/symbol-module.f4bddde3.svg",D="/zopeneditor-about/assets/symbol-number.e0ff525e.svg",a="/zopeneditor-about/assets/symbol-module.f4bddde3.svg",m="/zopeneditor-about/assets/symbol-operator.38b9457e.svg",h="/zopeneditor-about/assets/symbol-module.f4bddde3.svg",b="/zopeneditor-about/assets/symbol-property.cfa06206.svg",g="/zopeneditor-about/assets/symbol-string.393a611a.svg",y="/zopeneditor-about/assets/symbol-struct.e9fb1591.svg",V="/zopeneditor-about/assets/symbol-type-parameter.b47038bb.svg",n="/zopeneditor-about/assets/symbol-variable.8eabb338.svg";const z={},P=t("h1",{id:"customizing-the-outline-view",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#customizing-the-outline-view","aria-hidden":"true"},"#"),e(" Customizing the Outline view")],-1),B=t("p",null,"The Outline view shows a symbol tree of the currently active editor. IBM Z Open Editor maps each symbol to a language element of COBOL, PL/I, HLASM, and REXX.",-1),F=t("p",null,"However, you might not want every symbol to display in the Outline view. To control which ones appear, you can modify the User or Workspace settings. At this time, the REXX Outline view displays the internal routine symbol only.",-1),U=t("h2",{id:"enabling-or-disabling-outline-view-symbols",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#enabling-or-disabling-outline-view-symbols","aria-hidden":"true"},"#"),e(" Enabling or disabling Outline view symbols")],-1),k=t("p",null,"Navigate to your User and Workspace settings using the following VS Code menu command:",-1),M=t("ul",null,[t("li",null,[e("Windows/Linux: "),t("strong",null,"File > Preferences > Settings")]),t("li",null,[e("MacOS: "),t("strong",null,"Code > Preferences > Settings")])],-1),H=e("Note: VS Code provides different scopes for defining these settings. For more information, see "),G=e("User preferences versus workspace preferences"),X=e("."),J=t("li",null,[t("p",null,[e("Type "),t("code",null,"Outline"),e(" in the search box to filter the settings.")])],-1),j=t("li",null,[t("p",null,[e("Enable or disable the Outline view settings based on your needs. Refer to the "),t("a",{href:"#outline-view-symbol-mapping-reference"},"Outline view symbol mapping reference"),e(" to understand which settings affect which symbols.")])],-1),W=S('
    If you would rather modify the Outline view settings in their raw JSON form, run one of the following commands using the Command Palette. Note that it is not recommended to change the Default settings.
    Command Palette (\u21E7\u2318P) (Ctrl+Shift+P)Settings
    > Open Settings (JSON)User
    > Open Default Settings (JSON)Default
    > Open Workspace Settings (JSON)Workspace
     Outline view symbol mapping reference
    Note that some symbols are used more than once. This is expected behavior.
    This table highlights the relationship between Outline view settings in JSON form and UI form.
    JSONSettings Editor
    "outline.showBooleans":trueoutline-view-setting
     COBOL
    SymbolCOBOL Language ElementVisual Studio Code Setting
    symbol-booleanPROCEDURE_DIVISION"outline.showBooleans":true
    symbol-classDIRECTIVE"outline.showClasses":true
    symbol-constantPROG_ID"outline.showConstants":true
    symbol-constructorDATA_DIVISION"outline.showConstructors":true
    symbol-enum-memberMAINLINE_SECTION"outline.showEnumMembers":true
    symbol-enumLINKAGE_SECTION"outline.showEnums":true
    symbol-eventWORKING_STORAGE_SECTION"outline.showEvents":true
    symbol-fieldPROCESS"outline.showFields":true
    symbol-fileROOT"outline.showFiles":true
    symbol-functionPARAGRAPH"outline.showFunctions":true
    symbol-interfaceENVIRONMENT_DIVISION"outline.showInterfaces":true
    symbol-keyDECLARATIVES"outline.showKeys":true
    symbol-methodANY_OTHER_SECTION"outline.showMethods":true
    symbol-moduleCONFIGURATION_SECTION"outline.showModules":true
    symbol-namespaceCOPY"outline.showNamespaces":true
    symbol-numberANY_OTHER_DIVISION"outline.showNumbers":true
    symbol-objectLOCAL_STORAGE_SECTION"outline.showObjects":true
    symbol-operatorEND"outline.showOperators":true
    symbol-packagePROGRAM"outline.showPackages":true
    symbol-propertyIDENTIFICATION_DIVISION, ID_DIVISION"outline.showProperties":true
    symbol-stringLEVEL_1_HAS_SUBFIELDS, LEVEL_INDICATOR"outline.showStrings":true
    symbol-structFILE_SECTION"outline.showStructs":true
    symbol-type-parameterINPUT_OUTPUT_SECTION"outline.showTypeParameters":true
    symbol-variableLEVEL_1_HAS_NO_SUBFIELDS, LEVEL_3, LEVEL_X"outline.showVariables":true
     PL/I
    SymbolPL/I Language ElementVisual Studio Code Setting
    symbol-classPROCEDURE"outline.showClasses":true
    symbol-eventEVENT"outline.showEvents":true
    symbol-fieldDATAITEM_HAS_SUBFIELDS"outline.showFields":true
    symbol-fileROOT"outline.showFiles":true
    symbol-functionPACKAGE"outline.showFunctions":true
    symbol-interfaceLABEL"outline.showInterfaces":true
    symbol-methodREVERT"outline.showMethods":true
    symbol-namespaceINCLUDE"outline.showNamespaces":true
    symbol-operatorEND"outline.showOperators":true
    symbol-packageBEGIN"outline.showPackages":true
    symbol-variableDATAITEM_HAS_NO_SUBFIELDS"outline.showVariables":true
     HLASM
    SymbolHLASM Language ElementVisual Studio Code Setting
    symbol-classBRANCH_LABELS"outline.showClasses":true
    symbol-functionCSECT"outline.showFunctions":true
    symbol-objectMACRO"outline.showObjects":true
    symbol-structDSECT"outline.showStructs":true
    symbol-structRSECT"outline.showStrings":true
    symbol-structCOM"outline.showInterfaces":true
    symbol-structLOCTR"outline.showProperties":true
    symbol-structLABEL"outline.showVariables":true
     REXX
    SymbolREXX Language ElementVisual Studio Code Setting
    symbol-objectINTERNAL ROUTINE"outline.showObjects":true
     JCL
    SymbolJCL Language ElementVisual Studio Code Setting
    symbol-fieldDD Statement"outline.showFields":true
    symbol-interfaceEXEC Statement"outline.showInteraces":true
    symbol-eventJOB Statement"outline.showEvents":true
    ',16);function K(Y,Z){const p=_("RouterLink");return q(),v(f,null,[P,B,F,U,t("ol",null,[t("li",null,[k,M,t("p",null,[H,w(p,{to:"/Docs/setting_preferences.html#user-preferences-versus-workspace-preferences"},{default:E(()=>[G]),_:1}),X])]),J,j]),W],64)}var tt=x(z,[["render",K]]);export{tt as default};
diff --git a/assets/ebcdic_encoding.html.15b62784.js b/assets/ebcdic_encoding.html.bde230cb.js
similarity index 99%
rename from assets/ebcdic_encoding.html.15b62784.js
rename to assets/ebcdic_encoding.html.bde230cb.js
index 4ed06bd8e..d87b44907 100644
--- a/assets/ebcdic_encoding.html.15b62784.js
+++ b/assets/ebcdic_encoding.html.bde230cb.js
@@ -1,4 +1,4 @@
-import{r as p,o as r,a as l,b as n,d as s,w as t,F as c,e,c as a}from"./app.f6cb3ed9.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";var u="/zopeneditor-about/assets/zapp-rseapi.e541dd7d.png";const h={},m=n("h1",{id:"ebcdic-code-pages-and-mappings-files",tabindex:"-1"},[n("a",{class:"header-anchor",href:"#ebcdic-code-pages-and-mappings-files","aria-hidden":"true"},"#"),e(" EBCDIC code pages and mappings files")],-1),f=e("IBM Z Open Editor and RSE API Plug-in for Zowe CLI (RSE CLI plug-in) can handle EBCDIC code page conversion mappings for MVS and UNIX System Services files. You can set an encoding default in the RSE profile, use an encoding tag with Upload and Download MVS commands, use "),g=n("code",null,".gitattributes",-1),b=e(" files for uploading and downloading files from UNIX System Services, and use mappings files either provided by the RSE API host component or used at a project level. See "),k={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=mapping-supported-host-code-pages",target:"_blank",rel:"noopener noreferrer"},w=e("this page with the list of all the supported code pages"),y=e("."),v=a(`
     Zowe capabilities
    Many commands for Zowe CLI as well as the IBM RSE API Plug-in for Zowe CLI have additional parameters for specifying a code page directly or specifying a mappings file to be used for computing the code page encoding.
    For example, assuming the member SAM1 was written and stored on MVS using the IBM-273 EBCDIC encoding, you can work with it via the following commands.
    • To download the member SAM1 as a UTF-8 file (converting from IBM-273), issue the following command:
      zowe rse download ds "IBMUSER.SAMPLE.COBOL(SAM1)" --ec IBM-273
+import{r as p,o as r,a as l,b as n,d as s,w as t,F as c,e,c as a}from"./app.daa93c96.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";var u="/zopeneditor-about/assets/zapp-rseapi.e541dd7d.png";const h={},m=n("h1",{id:"ebcdic-code-pages-and-mappings-files",tabindex:"-1"},[n("a",{class:"header-anchor",href:"#ebcdic-code-pages-and-mappings-files","aria-hidden":"true"},"#"),e(" EBCDIC code pages and mappings files")],-1),f=e("IBM Z Open Editor and RSE API Plug-in for Zowe CLI (RSE CLI plug-in) can handle EBCDIC code page conversion mappings for MVS and UNIX System Services files. You can set an encoding default in the RSE profile, use an encoding tag with Upload and Download MVS commands, use "),g=n("code",null,".gitattributes",-1),b=e(" files for uploading and downloading files from UNIX System Services, and use mappings files either provided by the RSE API host component or used at a project level. See "),k={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=mapping-supported-host-code-pages",target:"_blank",rel:"noopener noreferrer"},w=e("this page with the list of all the supported code pages"),y=e("."),v=a(`
       Zowe capabilities
      Many commands for Zowe CLI as well as the IBM RSE API Plug-in for Zowe CLI have additional parameters for specifying a code page directly or specifying a mappings file to be used for computing the code page encoding.
      For example, assuming the member SAM1 was written and stored on MVS using the IBM-273 EBCDIC encoding, you can work with it via the following commands.
      • To download the member SAM1 as a UTF-8 file (converting from IBM-273), issue the following command:
        zowe rse download ds "IBMUSER.SAMPLE.COBOL(SAM1)" --ec IBM-273
 
      • To upload the member SAM1 using the IBM-273 EBCDIC encoding, issue the following command:
         zowe rse upload ftds ./ibmuser/sample/cobol/SAM1.txt "IBMUSER.SAMPLE.COBOL(SAM1)" --ec IBM-273
 
      You can also provide a default encoding value to be used for your Zowe CLI commands as well as Zowe Explorer operations in your Zowe profiles themselves. To do that, complete the following steps:
      `,5),_=e("Create or locate your "),I=e("Zowe team configuration file"),S=e("."),q=n("li",null,[n("p",null,'Insert the encoding property under the "properties" object of the relevant profile.')],-1),x=a(`
      Following is an example of how to do this:
      {
   "profiles": {
diff --git a/assets/editor_codechanges.html.6a1c862f.js b/assets/editor_codechanges.html.ff6ce7c8.js
similarity index 99%
rename from assets/editor_codechanges.html.6a1c862f.js
rename to assets/editor_codechanges.html.ff6ce7c8.js
index 965eeb3a0..d4677e0e9 100644
--- a/assets/editor_codechanges.html.6a1c862f.js
+++ b/assets/editor_codechanges.html.ff6ce7c8.js
@@ -1 +1 @@
-import{r as s,o as l,a as c,b as o,d as t,w as i,F as d,e,c as r}from"./app.f6cb3ed9.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";var p="/zopeneditor-about/assets/outline-explorer.b627b471.gif",u="/zopeneditor-about/assets/code-complete.80474fa5.gif",g="/zopeneditor-about/assets/declaration-hover.7c4db833.gif",m="/zopeneditor-about/assets/preview-cpy.b2972b87.gif",f="/zopeneditor-about/assets/peek-references.e1027ab6.gif",b="/zopeneditor-about/assets/peek-definition.46a952a9.gif",w="/zopeneditor-about/assets/dbc-editing.a44e336b.png",y="/zopeneditor-about/assets/cobol-code-folding.cb3828fd.gif",v="/zopeneditor-about/assets/pli-code-folding.d1610344.gif",_="/zopeneditor-about/assets/pli-toggle-comment.59dde837.gif";const k={},C=o("h1",{id:"making-cobol-and-pl-i-code-changes",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#making-cobol-and-pl-i-code-changes","aria-hidden":"true"},"#"),e(" Making COBOL and PL/I code changes")],-1),O=e("IBM Z\xAE Open Editor supports COBOL, PL/I, HLASM, and REXX editing. Select a program, copybook, include, or JCL file in the Explorer to open it in the editor. For HLASM specific details, see "),S=e("Making High Level Assembler code changes"),L=e(". For REXX specific details, see "),x=e("Making REXX code changes"),I=e("."),T=r('
      With the syntax highlighting capability, you can quickly distinguish reserved words, comments, constants, and variables of COBOL, PL/I and HLASM programs. With vertical rulers, which mark different areas, you can better determine the correct areas for comments and the boundaries for coding in areas A and B, and so on.
      The editor provides the following features and capabilities:
       Browsing code by using the Outline view
      As you view the source, you can use the Outline view to efficiently explore and navigate the code of the program. By looking through the items in this view, you can get an idea of what the program does at a high level.
      Illustration of using the Outline view
      How to use it
      You can use the Outline view only after you have opened a file or program. If the Outline view is not already expanded, you can open it by clicking View > Open view > Outline.
      You can use this view to:
      • Expand and collapse sections such as Division Headings, Section Headings, and Variable Group Names in the Outline View.
      • Recognize includes, procedures, loops quickly via the icons located by the various items.
      • Go to a wanted location in the code by clicking that section header in the view.
      • Sort by Position, Name, or Type.
      • Search for identifiers within the outline by pressing Ctrl+Shift+O (Windows), or Cmd+Shift+O (Mac) within the Editor window.
      When you move your cursor over the program, outline nodes are automatically selected. To toggle this and other features related to the Outline View, hover over the upper right corner of the Outline View. You can see the option ..., where you can click to find multiple options to organize your outline view such as Follow on Cursor, Filter by Type and Sort by Name, Position, and Type.
       Code and variable completion suggestion
      When you are typing code, code completion suggestion provides you with a matching list from which you can select commands, defined variable and paragraph names, and code snippets.
      Illustration of code and variable completion
      How to use it
      The code completion suggestion is displayed automatically while you are typing or when you press Ctrl+Space (Windows and Mac) depending on your preferences settings.
       Hovering for declaration
      You can see the working storage definition or DCL definition and the parent group of a variable or paragraph name by moving your mouse cursor over to the variable or paragraph name.
      Illustration of hovering for declaration
      How to use it
      The declaration hover is enabled by default.
       Previewing copybooks and include files
      You can preview the contents of a copybook or include file by moving your mouse cursor over the copybook name in a COPY statement in COBOL and HLASM, or the include file in a %INCLUDE statement in PL/I and REXX, without having to navigate away from the file you are working in. To open the file in a separate editor, press Ctrl+Click (Windows) or Cmd+Click (Mac).
      Illustration of previewing copybooks and include files
      How to use it
      You must specify the filepath to the copybooks or include files in your ZAPP file property groups to resolve the references. The location can be a local one, such as another directory in your workspace or it can be an MVS data set on a remote z/OS system using Zowe connectivity to find an load the files.
      If no filepath is specified or the copybooks or include files are not found in the provided filepath, an error (red squiggle) is shown. To resolve this, follow the instructions provided and our ZAPP overview and Property Groups pages.
       Operations on variable and paragraph names
      When you double-click a variable or paragraph name to highlight the entire name and then right-click it, you can see the available operations.
      How to use it
      • Click Change All Occurrences: Ctrl+F2 (Windows) or Cmd+F2 (Mac)
        When you type the new name, all occurrences are changed simultaneously.
        NOTE: In the scroll bar on the right side of the editor, each occurrence is noted with a location bar.
      • Click Find All References: Alt+Shift+F12 (Windows) or Option+Shift+F12(Mac)
        A Results References view for the variable or paragraph is displayed on the left side of the screen. Click any result to go to that location in the file.
      • Click Peek References: Shift+F12 (Windows and Mac)
        This opens a Results References view in the CodeLens box underneath the variable or paragraph. Click any result to go to that location in the file.
        Illustration of peeking references
      • Click Go to Definition: F12 (Windows and Mac)
        Go to the location where the variable or paragraph is defined. It opens the copybook or include file if applicable.
      • Click Go to Symbol: Ctrl+Shift+O (Windows) or Cmd+Shift+O (Mac)
        When you enter an object name in the search bar or you scroll through the items to select the object, the cursor is moved to that location.
      • Click Peek Definition: Alt+F12 (Windows) or Option+F12 (Mac)
        This opens a CodeLens box that shows where the variable or paragraph was defined in the code. If you use the keyboard shortcut Alt+F12 (Windows) or Option+F12 (Mac), the variable or paragraph name is only clicked once before the keyboard shortcuts are pressed. Double-click any result to go to that location in the file.
        Illustration of peeking definition
      • Click Rename Symbol: F2 (Windows and Mac)
        Rename the selected symbol, and the changes are done in the whole program and copybook or include if it is attached to that symbol.
       Syntax checking
      The syntax checking feature underlines unrecognized statements and expressions in red, which helps you to make quick corrections and reduce compile errors.
      Syntax checking also works for misspelled COBOL, PL/I reserved words and unknown variable names. For HLASM, there are syntax errors for improper spaces in a continuation line and unresolved copy statements.
      How to use it
      To see all the syntax errors in the open files, open the Problems view through the View menu or by clicking the error and warning icon at the bottom in the status bar. Double-click the list item to directly go to the problem.
       Editing double-byte characters
      When writing international applications with string constants that contain shift-in/shift-out double-byte characters, Z Open Editor will assist developers in ensuring that the COBOL program lines do not exceed the maximum line length configured for the editor.
      It will do that in two ways:
      1. Any sets of characters that take up more than one byte will be automatically visualized in the editor with special guillemets (\xAB \xBB) annotations. These annotations only help you to identify the characters. They are not actual characters of the program and will not be stored with it. Also, when you copy and paste the text to another editor, they will not be added to the clipboard.
      2. When you start typing such characters, the status bar will automatically start displaying a Byte Count entry that shows you how many bytes you have left before reaching the maximum line length.
      Editing strings with double-byte characters
      ',40),E=e("Also review "),B=e("EBCDIC code pages and mappings files"),M=e(" with examples for converting double-byte characters from EBCDIC to UTF-8 and vice versa when working with files from z/OS MVS and UNIX System Services."),P=r('
       Undoing and redoing
      Undo your changes by pressing Ctrl+Z (Windows) or Cmd+Z (Mac). Redo your changes by pressing Ctrl+Shift+Z (Windows) or Cmd+Shift+Z (Mac).
       Renumbering and unnumbering sequence numbers
      The Renumber/Unnumber function applies only to COBOL and will renumber the lines in the COBOL file. There is an option in preferences to control which columns will have sequence numbers inserted and removed. The user selects either columns 1-6, 73-80, or both. The numbering will start with 100 and increment each line by 100 while preserving non-numeric markers. This function equates to turning on the number mode in ISPF.
      The COBOL Unnumber function will remove the line numbering in either columns 1-6, 73-80, or both while preserving non-numeric markers. This function equates to turning off the number mode in ISPF.
      How to use it
      To configure the preferences in the Z Open Editor Settings for which columns you would like to renumber and unnumber, modify your settings as follows.
      1. Open your settings:
        • Windows: File > Preferences > Settings
        • Mac: Code > Preferences > Settings
      2. In the left side of the opened Settings interface, expand Extensions from the list of categories, and click IBM Z Open Editor. In the IBM Z Open Editor settings, under COBOL: Sequence Numbers, click the dropdown menu to select a preference.
      3. Click the appropriate option to specify the location of sequence numbers that are inserted and removed from a file by the Renumber and Unnumber editor actions. The options are as follows.
        • column-1: The sequence numbering begins at column 1, and will fill columns 1-6.
        • column-73: The sequence numbering begins at column 73, and will fill columns 73-80.
        • column-1-and-73: The sequence numbering begins at column 1 and 73, and will fill columns 1-6 and 73-80.
      To number or renumber a COBOL file, right-click in the file in the editor and select the Renumber Sequence Numbers command. To unnumber the COBOL file, right-click in file in the editor and select the Unnumber Sequence Numbers command.
       Commenting and uncommenting COBOL code
      You can comment and uncomment COBOL code by using the keyboard shortcut. This method works for both single-line comments and multi-line block comments.
      How to use it
      To comment COBOL code:
      1. In a COBOL file, place your cursor where you want to add a single-line comment, or click and select the code or text where you want to comment out a code block.
      2. Press Ctrl+/ (Windows) or Cmd+/ (Mac).
      To uncomment COBOL code:
      1. Select the code that is currently commented out.
      2. Press Ctrl+/ (Windows) or Cmd+/ (Mac).
       COBOL Code Folding
      Code folding is a feature that allows users to show or hide logical sections of the COBOL source code, which makes it easier for users to focus on the code they are working on. Logical sections of COBOL source code include but not limited to DIVISION, SECTION, PARAGRAPH, IF, ELSE, WHEN, DO, DATA-ITEMS, and EXEC SQL/CICS statements.
      How to use it
      ',19),F=e("You can fold regions of COBOL source code using the folding icons in the gutter between the line numbers and line start. Move the mouse over the gutter and click to fold and unfold regions. Use "),W=o("code",null,"Shift + Click",-1),A=e(" on the folding icon to fold or unfold the region and all regions inside. For more detailed information about code folding, refer to the "),R={href:"https://code.visualstudio.com/docs/editor/codebasics#_folding",target:"_blank",rel:"noopener noreferrer"},H=e("VS Code code folding documentation"),N=e("."),q=o("p",null,[o("img",{src:y,alt:"COBOL Code Folding Example"})],-1),z=o("h2",{id:"pl-i-code-folding",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#pl-i-code-folding","aria-hidden":"true"},"#"),e(" PL/I Code Folding")],-1),D=o("p",null,"Code folding is a feature that allows users to show or hide logical sections of the PL/I source code which makes it easier for users to focus on the code they are working on. Logical sections of PL/I source code include IF, ELSE, DO, SELECT, WHEN, OTHERWISE, PACKAGE, BEGIN, PROCEDURE and ON blocks.",-1),V=o("p",null,[o("strong",null,"How to use it")],-1),U=e("You can fold regions of PL/I source code using the folding icons in the gutter between the line numbers and line start. Move the mouse over the gutter and click to fold and unfold regions. Use "),Z=o("code",null,"Shift + Click",-1),Y=e(" on the folding icon to fold or unfold the region and all regions inside. For more detailed information about code folding, refer to the "),X={href:"https://code.visualstudio.com/docs/editor/codebasics#_folding",target:"_blank",rel:"noopener noreferrer"},G=e("VS Code code folding documentation"),j=e("."),J=r('
      PL/I Code Folding Example
       Commenting and uncommenting PL/I code
      You can comment out one or multiple selected lines of code or a selected section of code by using the toggle comment function.
      How to use it
      To toggle comment for one or multiple selected lines of code, press Cmd+/ (Mac) or Ctrl+/ (Windows), or go to Edit > Toggle Line Comment.
      To toggle comments for a selected section of code, press Option+Shift+A (Mac) or Alt+Shift+A (Windows), or go to Edit > Toggle Block Comment.
      See the following example where we first toggle line comment on multiple selected lines, then toggle line comment on a single line, and finally toggle block comment on a selection:
      pli toggle comment
      ',8);function K(Q,$){const n=s("RouterLink"),a=s("ExternalLinkIcon");return l(),c(d,null,[C,o("p",null,[O,t(n,{to:"/Docs/editor_codechanges_hlasm.html"},{default:i(()=>[S]),_:1}),L,t(n,{to:"/Docs/editor_codechanges_rexx.html"},{default:i(()=>[x]),_:1}),I]),T,o("p",null,[E,t(n,{to:"/Docs/ebcdic_encoding.html"},{default:i(()=>[B]),_:1}),M]),P,o("p",null,[F,W,A,o("a",R,[H,t(a)]),N]),q,z,D,V,o("p",null,[U,Z,Y,o("a",X,[G,t(a)]),j]),J],64)}var te=h(k,[["render",K]]);export{te as default};
+import{r as s,o as l,a as c,b as o,d as t,w as i,F as d,e,c as r}from"./app.daa93c96.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";var p="/zopeneditor-about/assets/outline-explorer.b627b471.gif",u="/zopeneditor-about/assets/code-complete.80474fa5.gif",g="/zopeneditor-about/assets/declaration-hover.7c4db833.gif",m="/zopeneditor-about/assets/preview-cpy.b2972b87.gif",f="/zopeneditor-about/assets/peek-references.e1027ab6.gif",b="/zopeneditor-about/assets/peek-definition.46a952a9.gif",w="/zopeneditor-about/assets/dbc-editing.a44e336b.png",y="/zopeneditor-about/assets/cobol-code-folding.cb3828fd.gif",v="/zopeneditor-about/assets/pli-code-folding.d1610344.gif",_="/zopeneditor-about/assets/pli-toggle-comment.59dde837.gif";const k={},C=o("h1",{id:"making-cobol-and-pl-i-code-changes",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#making-cobol-and-pl-i-code-changes","aria-hidden":"true"},"#"),e(" Making COBOL and PL/I code changes")],-1),O=e("IBM Z\xAE Open Editor supports COBOL, PL/I, HLASM, and REXX editing. Select a program, copybook, include, or JCL file in the Explorer to open it in the editor. For HLASM specific details, see "),S=e("Making High Level Assembler code changes"),L=e(". For REXX specific details, see "),x=e("Making REXX code changes"),I=e("."),T=r('
      With the syntax highlighting capability, you can quickly distinguish reserved words, comments, constants, and variables of COBOL, PL/I and HLASM programs. With vertical rulers, which mark different areas, you can better determine the correct areas for comments and the boundaries for coding in areas A and B, and so on.
      The editor provides the following features and capabilities:
       Browsing code by using the Outline view
      As you view the source, you can use the Outline view to efficiently explore and navigate the code of the program. By looking through the items in this view, you can get an idea of what the program does at a high level.
      Illustration of using the Outline view
      How to use it
      You can use the Outline view only after you have opened a file or program. If the Outline view is not already expanded, you can open it by clicking View > Open view > Outline.
      You can use this view to:
      • Expand and collapse sections such as Division Headings, Section Headings, and Variable Group Names in the Outline View.
      • Recognize includes, procedures, loops quickly via the icons located by the various items.
      • Go to a wanted location in the code by clicking that section header in the view.
      • Sort by Position, Name, or Type.
      • Search for identifiers within the outline by pressing Ctrl+Shift+O (Windows), or Cmd+Shift+O (Mac) within the Editor window.
      When you move your cursor over the program, outline nodes are automatically selected. To toggle this and other features related to the Outline View, hover over the upper right corner of the Outline View. You can see the option ..., where you can click to find multiple options to organize your outline view such as Follow on Cursor, Filter by Type and Sort by Name, Position, and Type.
       Code and variable completion suggestion
      When you are typing code, code completion suggestion provides you with a matching list from which you can select commands, defined variable and paragraph names, and code snippets.
      Illustration of code and variable completion
      How to use it
      The code completion suggestion is displayed automatically while you are typing or when you press Ctrl+Space (Windows and Mac) depending on your preferences settings.
       Hovering for declaration
      You can see the working storage definition or DCL definition and the parent group of a variable or paragraph name by moving your mouse cursor over to the variable or paragraph name.
      Illustration of hovering for declaration
      How to use it
      The declaration hover is enabled by default.
       Previewing copybooks and include files
      You can preview the contents of a copybook or include file by moving your mouse cursor over the copybook name in a COPY statement in COBOL and HLASM, or the include file in a %INCLUDE statement in PL/I and REXX, without having to navigate away from the file you are working in. To open the file in a separate editor, press Ctrl+Click (Windows) or Cmd+Click (Mac).
      Illustration of previewing copybooks and include files
      How to use it
      You must specify the filepath to the copybooks or include files in your ZAPP file property groups to resolve the references. The location can be a local one, such as another directory in your workspace or it can be an MVS data set on a remote z/OS system using Zowe connectivity to find an load the files.
      If no filepath is specified or the copybooks or include files are not found in the provided filepath, an error (red squiggle) is shown. To resolve this, follow the instructions provided and our ZAPP overview and Property Groups pages.
       Operations on variable and paragraph names
      When you double-click a variable or paragraph name to highlight the entire name and then right-click it, you can see the available operations.
      How to use it
      • Click Change All Occurrences: Ctrl+F2 (Windows) or Cmd+F2 (Mac)
        When you type the new name, all occurrences are changed simultaneously.
        NOTE: In the scroll bar on the right side of the editor, each occurrence is noted with a location bar.
      • Click Find All References: Alt+Shift+F12 (Windows) or Option+Shift+F12(Mac)
        A Results References view for the variable or paragraph is displayed on the left side of the screen. Click any result to go to that location in the file.
      • Click Peek References: Shift+F12 (Windows and Mac)
        This opens a Results References view in the CodeLens box underneath the variable or paragraph. Click any result to go to that location in the file.
        Illustration of peeking references
      • Click Go to Definition: F12 (Windows and Mac)
        Go to the location where the variable or paragraph is defined. It opens the copybook or include file if applicable.
      • Click Go to Symbol: Ctrl+Shift+O (Windows) or Cmd+Shift+O (Mac)
        When you enter an object name in the search bar or you scroll through the items to select the object, the cursor is moved to that location.
      • Click Peek Definition: Alt+F12 (Windows) or Option+F12 (Mac)
        This opens a CodeLens box that shows where the variable or paragraph was defined in the code. If you use the keyboard shortcut Alt+F12 (Windows) or Option+F12 (Mac), the variable or paragraph name is only clicked once before the keyboard shortcuts are pressed. Double-click any result to go to that location in the file.
        Illustration of peeking definition
      • Click Rename Symbol: F2 (Windows and Mac)
        Rename the selected symbol, and the changes are done in the whole program and copybook or include if it is attached to that symbol.
       Syntax checking
      The syntax checking feature underlines unrecognized statements and expressions in red, which helps you to make quick corrections and reduce compile errors.
      Syntax checking also works for misspelled COBOL, PL/I reserved words and unknown variable names. For HLASM, there are syntax errors for improper spaces in a continuation line and unresolved copy statements.
      How to use it
      To see all the syntax errors in the open files, open the Problems view through the View menu or by clicking the error and warning icon at the bottom in the status bar. Double-click the list item to directly go to the problem.
       Editing double-byte characters
      When writing international applications with string constants that contain shift-in/shift-out double-byte characters, Z Open Editor will assist developers in ensuring that the COBOL program lines do not exceed the maximum line length configured for the editor.
      It will do that in two ways:
      1. Any sets of characters that take up more than one byte will be automatically visualized in the editor with special guillemets (\xAB \xBB) annotations. These annotations only help you to identify the characters. They are not actual characters of the program and will not be stored with it. Also, when you copy and paste the text to another editor, they will not be added to the clipboard.
      2. When you start typing such characters, the status bar will automatically start displaying a Byte Count entry that shows you how many bytes you have left before reaching the maximum line length.
      Editing strings with double-byte characters
      ',40),E=e("Also review "),B=e("EBCDIC code pages and mappings files"),M=e(" with examples for converting double-byte characters from EBCDIC to UTF-8 and vice versa when working with files from z/OS MVS and UNIX System Services."),P=r('
       Undoing and redoing
      Undo your changes by pressing Ctrl+Z (Windows) or Cmd+Z (Mac). Redo your changes by pressing Ctrl+Shift+Z (Windows) or Cmd+Shift+Z (Mac).
       Renumbering and unnumbering sequence numbers
      The Renumber/Unnumber function applies only to COBOL and will renumber the lines in the COBOL file. There is an option in preferences to control which columns will have sequence numbers inserted and removed. The user selects either columns 1-6, 73-80, or both. The numbering will start with 100 and increment each line by 100 while preserving non-numeric markers. This function equates to turning on the number mode in ISPF.
      The COBOL Unnumber function will remove the line numbering in either columns 1-6, 73-80, or both while preserving non-numeric markers. This function equates to turning off the number mode in ISPF.
      How to use it
      To configure the preferences in the Z Open Editor Settings for which columns you would like to renumber and unnumber, modify your settings as follows.
      1. Open your settings:
        • Windows: File > Preferences > Settings
        • Mac: Code > Preferences > Settings
      2. In the left side of the opened Settings interface, expand Extensions from the list of categories, and click IBM Z Open Editor. In the IBM Z Open Editor settings, under COBOL: Sequence Numbers, click the dropdown menu to select a preference.
      3. Click the appropriate option to specify the location of sequence numbers that are inserted and removed from a file by the Renumber and Unnumber editor actions. The options are as follows.
        • column-1: The sequence numbering begins at column 1, and will fill columns 1-6.
        • column-73: The sequence numbering begins at column 73, and will fill columns 73-80.
        • column-1-and-73: The sequence numbering begins at column 1 and 73, and will fill columns 1-6 and 73-80.
      To number or renumber a COBOL file, right-click in the file in the editor and select the Renumber Sequence Numbers command. To unnumber the COBOL file, right-click in file in the editor and select the Unnumber Sequence Numbers command.
       Commenting and uncommenting COBOL code
      You can comment and uncomment COBOL code by using the keyboard shortcut. This method works for both single-line comments and multi-line block comments.
      How to use it
      To comment COBOL code:
      1. In a COBOL file, place your cursor where you want to add a single-line comment, or click and select the code or text where you want to comment out a code block.
      2. Press Ctrl+/ (Windows) or Cmd+/ (Mac).
      To uncomment COBOL code:
      1. Select the code that is currently commented out.
      2. Press Ctrl+/ (Windows) or Cmd+/ (Mac).
       COBOL Code Folding
      Code folding is a feature that allows users to show or hide logical sections of the COBOL source code, which makes it easier for users to focus on the code they are working on. Logical sections of COBOL source code include but not limited to DIVISION, SECTION, PARAGRAPH, IF, ELSE, WHEN, DO, DATA-ITEMS, and EXEC SQL/CICS statements.
      How to use it
      ',19),F=e("You can fold regions of COBOL source code using the folding icons in the gutter between the line numbers and line start. Move the mouse over the gutter and click to fold and unfold regions. Use "),W=o("code",null,"Shift + Click",-1),A=e(" on the folding icon to fold or unfold the region and all regions inside. For more detailed information about code folding, refer to the "),R={href:"https://code.visualstudio.com/docs/editor/codebasics#_folding",target:"_blank",rel:"noopener noreferrer"},H=e("VS Code code folding documentation"),N=e("."),q=o("p",null,[o("img",{src:y,alt:"COBOL Code Folding Example"})],-1),z=o("h2",{id:"pl-i-code-folding",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#pl-i-code-folding","aria-hidden":"true"},"#"),e(" PL/I Code Folding")],-1),D=o("p",null,"Code folding is a feature that allows users to show or hide logical sections of the PL/I source code which makes it easier for users to focus on the code they are working on. Logical sections of PL/I source code include IF, ELSE, DO, SELECT, WHEN, OTHERWISE, PACKAGE, BEGIN, PROCEDURE and ON blocks.",-1),V=o("p",null,[o("strong",null,"How to use it")],-1),U=e("You can fold regions of PL/I source code using the folding icons in the gutter between the line numbers and line start. Move the mouse over the gutter and click to fold and unfold regions. Use "),Z=o("code",null,"Shift + Click",-1),Y=e(" on the folding icon to fold or unfold the region and all regions inside. For more detailed information about code folding, refer to the "),X={href:"https://code.visualstudio.com/docs/editor/codebasics#_folding",target:"_blank",rel:"noopener noreferrer"},G=e("VS Code code folding documentation"),j=e("."),J=r('
      PL/I Code Folding Example
       Commenting and uncommenting PL/I code
      You can comment out one or multiple selected lines of code or a selected section of code by using the toggle comment function.
      How to use it
      To toggle comment for one or multiple selected lines of code, press Cmd+/ (Mac) or Ctrl+/ (Windows), or go to Edit > Toggle Line Comment.
      To toggle comments for a selected section of code, press Option+Shift+A (Mac) or Alt+Shift+A (Windows), or go to Edit > Toggle Block Comment.
      See the following example where we first toggle line comment on multiple selected lines, then toggle line comment on a single line, and finally toggle block comment on a selection:
      pli toggle comment
      ',8);function K(Q,$){const n=s("RouterLink"),a=s("ExternalLinkIcon");return l(),c(d,null,[C,o("p",null,[O,t(n,{to:"/Docs/editor_codechanges_hlasm.html"},{default:i(()=>[S]),_:1}),L,t(n,{to:"/Docs/editor_codechanges_rexx.html"},{default:i(()=>[x]),_:1}),I]),T,o("p",null,[E,t(n,{to:"/Docs/ebcdic_encoding.html"},{default:i(()=>[B]),_:1}),M]),P,o("p",null,[F,W,A,o("a",R,[H,t(a)]),N]),q,z,D,V,o("p",null,[U,Z,Y,o("a",X,[G,t(a)]),j]),J],64)}var te=h(k,[["render",K]]);export{te as default};
diff --git a/assets/editor_codechanges_hlasm.html.3ba7e8c6.js b/assets/editor_codechanges_hlasm.html.0d36a43a.js
similarity index 99%
rename from assets/editor_codechanges_hlasm.html.3ba7e8c6.js
rename to assets/editor_codechanges_hlasm.html.0d36a43a.js
index c4ee15dfa..6ecc68a2f 100644
--- a/assets/editor_codechanges_hlasm.html.3ba7e8c6.js
+++ b/assets/editor_codechanges_hlasm.html.0d36a43a.js
@@ -1 +1 @@
-import{r as s,o as a,a as l,b as e,d as i,w as n,F as c,e as o,c as r}from"./app.f6cb3ed9.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";var d="/zopeneditor-about/assets/hlasm-outline.62567372.gif",p="/zopeneditor-about/assets/hlasm-completion-operation.675e522f.gif",u="/zopeneditor-about/assets/hlasm-completion-macro.09eacdeb.gif",m="/zopeneditor-about/assets/hlasm-hover.19402729.gif",g="/zopeneditor-about/assets/hlasm-copy.7b7a1315.gif",f="/zopeneditor-about/assets/hlasm-references.8a795b5e.gif",y="/zopeneditor-about/assets/hlasm-peek-definition.ad097ffd.gif",b="/zopeneditor-about/assets/hlasm-macro-resolution.d2ec1e50.gif";const w={},_=e("h1",{id:"making-high-level-assembler-code-changes",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#making-high-level-assembler-code-changes","aria-hidden":"true"},"#"),o(" Making High Level Assembler code changes")],-1),v=e("p",null,"In addition to COBOL and PL/I, IBM Z\xAE Open Editor supports IBM Z High Level Assembler (HLASM) editing. You can use the following features to program in HLASM effectively.",-1),k=e("p",null,"With the syntax highlighting capability, you can quickly distinguish between labels, operations, operands, and comments in a HLASM program. With vertical rulers, which mark different areas, you can better determine correct areas for symbols, operations, operands, continuation line indicators, and sequence numbers.",-1),S=e("p",null,"The editor provides the following features and capabilities:",-1),C=e("h2",{id:"browsing-code-by-using-the-outline-view",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#browsing-code-by-using-the-outline-view","aria-hidden":"true"},"#"),o(" Browsing code by using the Outline view")],-1),M=o("You can use the Outline view to efficiently explore and browse the source code of a program. By looking through the items in this view, you can get an idea of what the program does at a high level and easily go to key instructions, branch labels, and symbols. We purposely chose not to include every symbol, because in large assembler programs, the Outline view often becomes extremely cluttered. For more information, see "),O=o("Customizing the Outline view"),x=o("."),A=r('
      HLASM Outline
      How to use it
      You can use the Outline view only after you have opened a file or program. If the Outline view is not expanded, you can open it by clicking View > Open view > Outline.
      You can use this view to:
      • Recognize the following instructions quickly through the icons: 
        • CSECT
        • DSECT
        • RSECT
        • COM
        • LOCTR
        • MACRO
      • Identify the following unique icons: 
        • All labels used in a branch instruction
        • All labels, if enabled
      • Go to a location that you want in the code by clicking that section header in the view.
      • Sort by Position, Name, or Type.
      • Search for identifiers by pressing Ctrl+Shift+O on Windows or Cmd+Shift+O on Mac in the Editor window.
      When you move your cursor over the program, outline nodes are automatically selected. To toggle this and other features related to the Outline View, hover over the upper-right corner of the Outline view. You can see the option ..., where you can click to find multiple options to organize your outline view such as Follow on Cursor, Filter by Type and Sort by Name, Position, and Type. To filter which icons to display in the Outline view, see Customizing the Outline view.
       Code completion
      When you are typing in an HLASM program, code completion provides you with a list from which you can select operations or labels depending on the current context. Currently, code completion for symbols works for symbols defined in the current file and copied files. Code completion for operations works for default (SYS1.MACLIB) macros, macros defined in the current file, and local custom macros.
      When using code completion for instructions that have operands as well as macros with parameters, the HLASM language server will provide a snippet-style completion text that allows the user to use the tab key to modify and complete the operands or parameters as needed. See the following examples of operation and macro code completion.
      Code completion While Typing
      Code completion macro
      How to use it
      The code completion suggestion is displayed automatically while you are typing in an appropriate context.
       Hovering for declaration
      You can see hovers for operations and operands by moving your mouse cursor over the operation or operand.
      HLASM Hover
      How to use it
      Operation and operand hovers are enabled by default. Simply move your mouse over an operation or operand. If the operand or operation is defined, a hover will appear.
       Previewing copybooks
      To preview the contents of a COPY statement move your mouse cursor over the copybook name. If the copybook cannot be resolved, a red error underline will appear on the copybook name. To open the file in a separate editor, press Ctrl+Click (Windows) or Cmd+Click (Mac).
      HLASM Copy File Preview
      How to use it
      To resolve copybooks, you must specify the filepath to the copybooks or include files in your ZAPP file property groups to resolve the references. The location can be a local one, such as another directory in your workspace, or it can be an MVS data set on a remote z/OS system using Zowe connectivity to find an load the files.
      If no filepath is specified the include files are not found in the provided filepath, an error (red squiggle) is shown. To resolve this, follow the instructions provided and our ZAPP overview and Property Groups pages.
       Operations on symbols
      When you double-click a symbol to highlight the entire name and then right-click it, you can see the available operations.
      How to use it
      • Click Change All Occurrences: Ctrl+F2 (Windows) or Cmd+F2 (Mac)
        When you type the new name, all occurrences are changed simultaneously.
        NOTE: In the scroll bar on the right side of the editor, each occurrence is noted with a location bar.
      • Click Find All References: Alt+Shift+F12 (Windows) or Option+Shift+F12(Mac)
        A Results References view for the variable or paragraph is displayed on the left side of the screen. Click any result to go to that location in the file.
      • Click Peek References: Shift+F12 (Windows and Mac)
        This opens a Results References view in the CodeLens box underneath the variable or paragraph. Click any result to go to that location in the file.
        HLASM PEEK REFERENCES
      • Click Go to Definition: F12 (Windows and Mac)
        Go to the location where the variable or paragraph is defined. It opens the copybook or include file if applicable.
      • Click Go to Symbol: Ctrl+Shift+O (Windows) or Cmd+Shift+O (Mac)
        When you enter an object name in the search bar or you scroll through the items to select the object, the cursor is moved to that location.
      • Click Peek Definition: Alt+F12 (Windows) or Option+F12 (Mac)
        This opens a CodeLens box that shows where the variable or paragraph was defined in the code. If you use the keyboard shortcut Alt+F12 (Windows) or Option+F12 (Mac), the variable or paragraph name is only clicked once before the keyboard shortcuts are pressed. Double-click any result to go to that location in the file.
        HLASM PEEK DEFINITION
       Remote macros
      Macros in SYS1.MACLIB are available for code completion. In addition, if you configured Zowe Explorer to a z/OS MVS system that has a SYS1.MACLIB data set with a valid user z/OSMF or RSE API profile, you can preview remote macros in rich hovers. The tools will follow the same rules as for include file resolution, although no property groups need to be defined.
      HLASM REMOTE MACRO
      ',31),L=o("To enable the automatic lookup with your default Zowe CLI profile, go to "),T=e("strong",null,"Preferences > Settings",-1),I=o(", expand "),H=e("strong",null,"Extensions > IBM Z Open Editor",-1),z=o(" and check the option "),E=e("strong",null,"Hlasm: Enable Resolving Macros",-1),W=o(". Additionally, you can adjust the lookup to use the z/OS 2.4, 2.5, or 3.1 version of "),R=e("code",null,"SYS1.MACLIB",-1),F=o(" using "),P=e("strong",null,"Hlasm: Zos Macros Version",-1),Z=o(". This will ensure proper hover and code completion support for the macro set that you are using. See "),B=o("Setting preferences"),Y=o(" for more details on managing preferences."),N=e("p",null,"If you do not have any connectivity, we recommend keeping this feature switched off; otherwise the editor will continue trying to resolve the file via your Zowe CLI profile.",-1),V=o("If you want to use a different Zowe CLI profile than the default RSE API or z/OSMF profiles, specify the name of a different profile in the "),D=e("code",null,'"zopeneditor.zowe"',-1),q=o(" user setting. See the details in "),G=o("Setting up and using RSE profiles in IBM Z Open Editor"),j=o("."),K=r('
       Syntax checking
      The syntax checking feature underlines unrecognized statements and expressions in red, which helps you to make quick corrections and reduce compile errors. Currently, there are syntax errors for improper spaces in a continuation line, unresolved copy statements, and an invalid number of operands.
      How to use it
      To see all the syntax errors in the open files, open the Problems view through the View menu or by clicking the error and warning icon at the bottom in the status bar. Double-click the list item to directly go to the problem.
      • Invalid number of operands
        This syntax error is currently supported for all machine instructions. Assembler instructions and macros are not currently supported.
       Undoing and redoing
      Undo your changes by pressing Ctrl+Z (Windows) or Cmd+Z (Mac). Redo your changes by pressing Ctrl+Shift+Z (Windows) or Cmd+Shift+Z (Mac).
       Commenting and uncommenting HLASM code
      You can comment and uncomment HLASM code by using the keyboard shortcut. This method works for both single-line comments and multi-line block comments.
      How to use it
      To comment HLASM code:
      1. In an HLASM file, place your cursor where you want to add a single-line comment, or click and select the code or text where you want to comment out a code block.
      2. Press Ctrl+/ (Windows) or Cmd+/ (Mac).
      To uncomment HLASM code:
      1. Select the code that is currently commented out.
      2. Press Ctrl+/ (Windows) or Cmd+/ (Mac).
      ',14);function U(J,Q){const t=s("RouterLink");return a(),l(c,null,[_,v,k,S,C,e("p",null,[M,i(t,{to:"/Docs/customizing_the_outline_view.html"},{default:n(()=>[O]),_:1}),x]),A,e("p",null,[L,T,I,H,z,E,W,R,F,P,Z,i(t,{to:"/Docs/setting_preferences.html"},{default:n(()=>[B]),_:1}),Y]),N,e("p",null,[V,D,q,i(t,{to:"/Docs/interact_zos_zowe_explorer.html#setting-up-and-using-rse-profiles-in-ibm-z-open-editor"},{default:n(()=>[G]),_:1}),j]),K],64)}var ee=h(w,[["render",U]]);export{ee as default};
+import{r as s,o as a,a as l,b as e,d as i,w as n,F as c,e as o,c as r}from"./app.daa93c96.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";var d="/zopeneditor-about/assets/hlasm-outline.62567372.gif",p="/zopeneditor-about/assets/hlasm-completion-operation.675e522f.gif",u="/zopeneditor-about/assets/hlasm-completion-macro.09eacdeb.gif",m="/zopeneditor-about/assets/hlasm-hover.19402729.gif",g="/zopeneditor-about/assets/hlasm-copy.7b7a1315.gif",f="/zopeneditor-about/assets/hlasm-references.8a795b5e.gif",y="/zopeneditor-about/assets/hlasm-peek-definition.ad097ffd.gif",b="/zopeneditor-about/assets/hlasm-macro-resolution.d2ec1e50.gif";const w={},_=e("h1",{id:"making-high-level-assembler-code-changes",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#making-high-level-assembler-code-changes","aria-hidden":"true"},"#"),o(" Making High Level Assembler code changes")],-1),v=e("p",null,"In addition to COBOL and PL/I, IBM Z\xAE Open Editor supports IBM Z High Level Assembler (HLASM) editing. You can use the following features to program in HLASM effectively.",-1),k=e("p",null,"With the syntax highlighting capability, you can quickly distinguish between labels, operations, operands, and comments in a HLASM program. With vertical rulers, which mark different areas, you can better determine correct areas for symbols, operations, operands, continuation line indicators, and sequence numbers.",-1),S=e("p",null,"The editor provides the following features and capabilities:",-1),C=e("h2",{id:"browsing-code-by-using-the-outline-view",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#browsing-code-by-using-the-outline-view","aria-hidden":"true"},"#"),o(" Browsing code by using the Outline view")],-1),M=o("You can use the Outline view to efficiently explore and browse the source code of a program. By looking through the items in this view, you can get an idea of what the program does at a high level and easily go to key instructions, branch labels, and symbols. We purposely chose not to include every symbol, because in large assembler programs, the Outline view often becomes extremely cluttered. For more information, see "),O=o("Customizing the Outline view"),x=o("."),A=r('
      HLASM Outline
      How to use it
      You can use the Outline view only after you have opened a file or program. If the Outline view is not expanded, you can open it by clicking View > Open view > Outline.
      You can use this view to:
      • Recognize the following instructions quickly through the icons: 
        • CSECT
        • DSECT
        • RSECT
        • COM
        • LOCTR
        • MACRO
      • Identify the following unique icons: 
        • All labels used in a branch instruction
        • All labels, if enabled
      • Go to a location that you want in the code by clicking that section header in the view.
      • Sort by Position, Name, or Type.
      • Search for identifiers by pressing Ctrl+Shift+O on Windows or Cmd+Shift+O on Mac in the Editor window.
      When you move your cursor over the program, outline nodes are automatically selected. To toggle this and other features related to the Outline View, hover over the upper-right corner of the Outline view. You can see the option ..., where you can click to find multiple options to organize your outline view such as Follow on Cursor, Filter by Type and Sort by Name, Position, and Type. To filter which icons to display in the Outline view, see Customizing the Outline view.
       Code completion
      When you are typing in an HLASM program, code completion provides you with a list from which you can select operations or labels depending on the current context. Currently, code completion for symbols works for symbols defined in the current file and copied files. Code completion for operations works for default (SYS1.MACLIB) macros, macros defined in the current file, and local custom macros.
      When using code completion for instructions that have operands as well as macros with parameters, the HLASM language server will provide a snippet-style completion text that allows the user to use the tab key to modify and complete the operands or parameters as needed. See the following examples of operation and macro code completion.
      Code completion While Typing
      Code completion macro
      How to use it
      The code completion suggestion is displayed automatically while you are typing in an appropriate context.
       Hovering for declaration
      You can see hovers for operations and operands by moving your mouse cursor over the operation or operand.
      HLASM Hover
      How to use it
      Operation and operand hovers are enabled by default. Simply move your mouse over an operation or operand. If the operand or operation is defined, a hover will appear.
       Previewing copybooks
      To preview the contents of a COPY statement move your mouse cursor over the copybook name. If the copybook cannot be resolved, a red error underline will appear on the copybook name. To open the file in a separate editor, press Ctrl+Click (Windows) or Cmd+Click (Mac).
      HLASM Copy File Preview
      How to use it
      To resolve copybooks, you must specify the filepath to the copybooks or include files in your ZAPP file property groups to resolve the references. The location can be a local one, such as another directory in your workspace, or it can be an MVS data set on a remote z/OS system using Zowe connectivity to find an load the files.
      If no filepath is specified the include files are not found in the provided filepath, an error (red squiggle) is shown. To resolve this, follow the instructions provided and our ZAPP overview and Property Groups pages.
       Operations on symbols
      When you double-click a symbol to highlight the entire name and then right-click it, you can see the available operations.
      How to use it
      • Click Change All Occurrences: Ctrl+F2 (Windows) or Cmd+F2 (Mac)
        When you type the new name, all occurrences are changed simultaneously.
        NOTE: In the scroll bar on the right side of the editor, each occurrence is noted with a location bar.
      • Click Find All References: Alt+Shift+F12 (Windows) or Option+Shift+F12(Mac)
        A Results References view for the variable or paragraph is displayed on the left side of the screen. Click any result to go to that location in the file.
      • Click Peek References: Shift+F12 (Windows and Mac)
        This opens a Results References view in the CodeLens box underneath the variable or paragraph. Click any result to go to that location in the file.
        HLASM PEEK REFERENCES
      • Click Go to Definition: F12 (Windows and Mac)
        Go to the location where the variable or paragraph is defined. It opens the copybook or include file if applicable.
      • Click Go to Symbol: Ctrl+Shift+O (Windows) or Cmd+Shift+O (Mac)
        When you enter an object name in the search bar or you scroll through the items to select the object, the cursor is moved to that location.
      • Click Peek Definition: Alt+F12 (Windows) or Option+F12 (Mac)
        This opens a CodeLens box that shows where the variable or paragraph was defined in the code. If you use the keyboard shortcut Alt+F12 (Windows) or Option+F12 (Mac), the variable or paragraph name is only clicked once before the keyboard shortcuts are pressed. Double-click any result to go to that location in the file.
        HLASM PEEK DEFINITION
       Remote macros
      Macros in SYS1.MACLIB are available for code completion. In addition, if you configured Zowe Explorer to a z/OS MVS system that has a SYS1.MACLIB data set with a valid user z/OSMF or RSE API profile, you can preview remote macros in rich hovers. The tools will follow the same rules as for include file resolution, although no property groups need to be defined.
      HLASM REMOTE MACRO
      ',31),L=o("To enable the automatic lookup with your default Zowe CLI profile, go to "),T=e("strong",null,"Preferences > Settings",-1),I=o(", expand "),H=e("strong",null,"Extensions > IBM Z Open Editor",-1),z=o(" and check the option "),E=e("strong",null,"Hlasm: Enable Resolving Macros",-1),W=o(". Additionally, you can adjust the lookup to use the z/OS 2.4, 2.5, or 3.1 version of "),R=e("code",null,"SYS1.MACLIB",-1),F=o(" using "),P=e("strong",null,"Hlasm: Zos Macros Version",-1),Z=o(". This will ensure proper hover and code completion support for the macro set that you are using. See "),B=o("Setting preferences"),Y=o(" for more details on managing preferences."),N=e("p",null,"If you do not have any connectivity, we recommend keeping this feature switched off; otherwise the editor will continue trying to resolve the file via your Zowe CLI profile.",-1),V=o("If you want to use a different Zowe CLI profile than the default RSE API or z/OSMF profiles, specify the name of a different profile in the "),D=e("code",null,'"zopeneditor.zowe"',-1),q=o(" user setting. See the details in "),G=o("Setting up and using RSE profiles in IBM Z Open Editor"),j=o("."),K=r('
       Syntax checking
      The syntax checking feature underlines unrecognized statements and expressions in red, which helps you to make quick corrections and reduce compile errors. Currently, there are syntax errors for improper spaces in a continuation line, unresolved copy statements, and an invalid number of operands.
      How to use it
      To see all the syntax errors in the open files, open the Problems view through the View menu or by clicking the error and warning icon at the bottom in the status bar. Double-click the list item to directly go to the problem.
      • Invalid number of operands
        This syntax error is currently supported for all machine instructions. Assembler instructions and macros are not currently supported.
       Undoing and redoing
      Undo your changes by pressing Ctrl+Z (Windows) or Cmd+Z (Mac). Redo your changes by pressing Ctrl+Shift+Z (Windows) or Cmd+Shift+Z (Mac).
       Commenting and uncommenting HLASM code
      You can comment and uncomment HLASM code by using the keyboard shortcut. This method works for both single-line comments and multi-line block comments.
      How to use it
      To comment HLASM code:
      1. In an HLASM file, place your cursor where you want to add a single-line comment, or click and select the code or text where you want to comment out a code block.
      2. Press Ctrl+/ (Windows) or Cmd+/ (Mac).
      To uncomment HLASM code:
      1. Select the code that is currently commented out.
      2. Press Ctrl+/ (Windows) or Cmd+/ (Mac).
      ',14);function U(J,Q){const t=s("RouterLink");return a(),l(c,null,[_,v,k,S,C,e("p",null,[M,i(t,{to:"/Docs/customizing_the_outline_view.html"},{default:n(()=>[O]),_:1}),x]),A,e("p",null,[L,T,I,H,z,E,W,R,F,P,Z,i(t,{to:"/Docs/setting_preferences.html"},{default:n(()=>[B]),_:1}),Y]),N,e("p",null,[V,D,q,i(t,{to:"/Docs/interact_zos_zowe_explorer.html#setting-up-and-using-rse-profiles-in-ibm-z-open-editor"},{default:n(()=>[G]),_:1}),j]),K],64)}var ee=h(w,[["render",U]]);export{ee as default};
diff --git a/assets/editor_codechanges_jcl.html.c5fe40ac.js b/assets/editor_codechanges_jcl.html.3b1e2582.js
similarity index 99%
rename from assets/editor_codechanges_jcl.html.c5fe40ac.js
rename to assets/editor_codechanges_jcl.html.3b1e2582.js
index deea6641c..de3ded1ee 100644
--- a/assets/editor_codechanges_jcl.html.c5fe40ac.js
+++ b/assets/editor_codechanges_jcl.html.3b1e2582.js
@@ -1 +1 @@
-import{r as i,o as s,a,b as o,d as r,F as c,c as t,e}from"./app.f6cb3ed9.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";var d="/zopeneditor-about/assets/jcl-outline.7501ea05.gif",h="/zopeneditor-about/assets/jcl-completion.a66212f2.gif",g="/zopeneditor-about/assets/jcl-code-folding.9cae3e19.gif",u="/zopeneditor-about/assets/jcl-toggle-comment.0dbcbaff.gif";const p={},m=t('
       Making JCL code changes
      In addition to COBOL, PL/I, REXX, and High Level Assembler (HLASM), IBM Z\xAE Open Editor supports z/OS MVS JCL editing. You can use the following features to edit JCL programs effectively.
      With the syntax highlighting capability, you can quickly distinguish the comments, job, step (exec) and DD statements in a JCL program.
      The editor provides the following features and capabilities:
       Browsing code by using the Outline view
      As you view the source, you can use the Outline view to efficiently explore and navigate the code of the program. By looking through the items in this view, you can see the Jobs, Steps, DD statements and directly navigate to one by selecting it.
      JCL Outline
      How to use it
      You can use the Outline view only after you have opened a file or program. If the Outline view is not already expanded, you can open it by clicking View > Open view > Outline.
      You can use this view to:
      • Recognize internal routines quickly via the icons in the outline view.
      • Go to a wanted location in the code by clicking the section header in the view.
      • Sort by Position or Name.
      • Search for identifiers within the outline by pressing Ctrl+Shift+O (Windows), or Cmd+Shift+O (Mac) within the Editor window.
      • Select the entire step/job/DD statement by double clicking on the symbol in the outline view.
      When you move your cursor over the program, outline nodes are automatically selected. To toggle this and other features related to the Outline View, hover over the upper right corner of the Outline View. You can see the option ..., where you can click to find multiple options to organize your outline view such as Follow on Cursor, Filter by Type and Sort by Name, Position, and Type.
       Code completion
      The code completion feature suggests simple symbols, constant symbols, jobs, steps, DD statements, keyword instructions, and built-in functions. The editor applies a suggestion to the file based on the context of the cursor position. For a cursor position inside a stem, the suggestion replaces the entire symbol. For a cursor position inside the tail of a compound symbol, the suggestion replaces a segment of the symbol. The casing of the suggestion replaces the casing of the symbol in the file. The code completion suggestions are not filtered by case.
      Code Completion
      How to use it
      The code completion suggestion is displayed automatically while you are typing outside of any comments or strings.
       Syntax checking
      The syntax checking feature underlines unrecognized statements and expressions in red, which helps you to make quick corrections and reduce compile errors.
      How to use it
      To see all the syntax errors in the open files, open the Problems view through the View menu or by clicking the error and warning icon in the status bar. Double-click the list item to directly go to the problem.
       JCL Code Folding
      Code folding is a feature that allows users to show or hide logical sections of the JCL source code, which makes it easier for users to focus on the code they are working on. Logical sections of JCL source code includes JOB, EXEC, and DD statements.
      How to use it
      ',24),f=e("You can fold regions of COBOL source code using the folding icons in the gutter between the line numbers and line start. Move the mouse over the gutter and click to fold and unfold regions. Use "),y=o("code",null,"Shift + Click",-1),b=e(" on the folding icon to fold or unfold the region and all regions inside. For more detailed information about code folding, refer to the "),w={href:"https://code.visualstudio.com/docs/editor/codebasics#_folding",target:"_blank",rel:"noopener noreferrer"},_=e("VS Code code folding documentation"),v=e("."),C=t('
      JCL Code Folding Example
       Undoing and redoing
      Undo your changes by pressing Ctrl+Z (Windows) or Cmd+Z (Mac). Redo your changes by pressing Ctrl+Shift+Z (Windows) or Cmd+Shift+Z (Mac).
       Commenting and uncommenting JCL code
      You can comment out one or multiple selected lines of code or a selected section of code by using the toggle comment function.
      How to use it
      To toggle comment for one or multiple selected lines of code, press Cmd+/ (Mac) or Ctrl+/ (Windows), or go to Edit > Toggle Line Comment.
      To toggle comments for a selected section of code, press Option+Shift+A (Mac) or Alt+Shift+A (Windows), or go to Edit > Toggle Block Comment.
      See the following example where we first toggle line comment on a single line, then toggle line comment on multiple selected lines, and finally toggle block comment on a selection:
      jcl toggle comment
      ',10);function k(x,L){const n=i("ExternalLinkIcon");return s(),a(c,null,[m,o("p",null,[f,y,b,o("a",w,[_,r(n)]),v]),C],64)}var T=l(p,[["render",k]]);export{T as default};
+import{r as i,o as s,a,b as o,d as r,F as c,c as t,e}from"./app.daa93c96.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";var d="/zopeneditor-about/assets/jcl-outline.7501ea05.gif",h="/zopeneditor-about/assets/jcl-completion.a66212f2.gif",g="/zopeneditor-about/assets/jcl-code-folding.9cae3e19.gif",u="/zopeneditor-about/assets/jcl-toggle-comment.0dbcbaff.gif";const p={},m=t('
       Making JCL code changes
      In addition to COBOL, PL/I, REXX, and High Level Assembler (HLASM), IBM Z\xAE Open Editor supports z/OS MVS JCL editing. You can use the following features to edit JCL programs effectively.
      With the syntax highlighting capability, you can quickly distinguish the comments, job, step (exec) and DD statements in a JCL program.
      The editor provides the following features and capabilities:
       Browsing code by using the Outline view
      As you view the source, you can use the Outline view to efficiently explore and navigate the code of the program. By looking through the items in this view, you can see the Jobs, Steps, DD statements and directly navigate to one by selecting it.
      JCL Outline
      How to use it
      You can use the Outline view only after you have opened a file or program. If the Outline view is not already expanded, you can open it by clicking View > Open view > Outline.
      You can use this view to:
      • Recognize internal routines quickly via the icons in the outline view.
      • Go to a wanted location in the code by clicking the section header in the view.
      • Sort by Position or Name.
      • Search for identifiers within the outline by pressing Ctrl+Shift+O (Windows), or Cmd+Shift+O (Mac) within the Editor window.
      • Select the entire step/job/DD statement by double clicking on the symbol in the outline view.
      When you move your cursor over the program, outline nodes are automatically selected. To toggle this and other features related to the Outline View, hover over the upper right corner of the Outline View. You can see the option ..., where you can click to find multiple options to organize your outline view such as Follow on Cursor, Filter by Type and Sort by Name, Position, and Type.
       Code completion
      The code completion feature suggests simple symbols, constant symbols, jobs, steps, DD statements, keyword instructions, and built-in functions. The editor applies a suggestion to the file based on the context of the cursor position. For a cursor position inside a stem, the suggestion replaces the entire symbol. For a cursor position inside the tail of a compound symbol, the suggestion replaces a segment of the symbol. The casing of the suggestion replaces the casing of the symbol in the file. The code completion suggestions are not filtered by case.
      Code Completion
      How to use it
      The code completion suggestion is displayed automatically while you are typing outside of any comments or strings.
       Syntax checking
      The syntax checking feature underlines unrecognized statements and expressions in red, which helps you to make quick corrections and reduce compile errors.
      How to use it
      To see all the syntax errors in the open files, open the Problems view through the View menu or by clicking the error and warning icon in the status bar. Double-click the list item to directly go to the problem.
       JCL Code Folding
      Code folding is a feature that allows users to show or hide logical sections of the JCL source code, which makes it easier for users to focus on the code they are working on. Logical sections of JCL source code includes JOB, EXEC, and DD statements.
      How to use it
      ',24),f=e("You can fold regions of COBOL source code using the folding icons in the gutter between the line numbers and line start. Move the mouse over the gutter and click to fold and unfold regions. Use "),y=o("code",null,"Shift + Click",-1),b=e(" on the folding icon to fold or unfold the region and all regions inside. For more detailed information about code folding, refer to the "),w={href:"https://code.visualstudio.com/docs/editor/codebasics#_folding",target:"_blank",rel:"noopener noreferrer"},_=e("VS Code code folding documentation"),v=e("."),C=t('
      JCL Code Folding Example
       Undoing and redoing
      Undo your changes by pressing Ctrl+Z (Windows) or Cmd+Z (Mac). Redo your changes by pressing Ctrl+Shift+Z (Windows) or Cmd+Shift+Z (Mac).
       Commenting and uncommenting JCL code
      You can comment out one or multiple selected lines of code or a selected section of code by using the toggle comment function.
      How to use it
      To toggle comment for one or multiple selected lines of code, press Cmd+/ (Mac) or Ctrl+/ (Windows), or go to Edit > Toggle Line Comment.
      To toggle comments for a selected section of code, press Option+Shift+A (Mac) or Alt+Shift+A (Windows), or go to Edit > Toggle Block Comment.
      See the following example where we first toggle line comment on a single line, then toggle line comment on multiple selected lines, and finally toggle block comment on a selection:
      jcl toggle comment
      ',10);function k(x,L){const n=i("ExternalLinkIcon");return s(),a(c,null,[m,o("p",null,[f,y,b,o("a",w,[_,r(n)]),v]),C],64)}var T=l(p,[["render",k]]);export{T as default};
diff --git a/assets/editor_codechanges_rexx.html.9f36838f.js b/assets/editor_codechanges_rexx.html.375e0978.js
similarity index 99%
rename from assets/editor_codechanges_rexx.html.9f36838f.js
rename to assets/editor_codechanges_rexx.html.375e0978.js
index 47329781f..24be32a3e 100644
--- a/assets/editor_codechanges_rexx.html.9f36838f.js
+++ b/assets/editor_codechanges_rexx.html.375e0978.js
@@ -1 +1 @@
-import{r,o as a,a as c,b as n,d as t,w as i,F as l,c as s,e}from"./app.f6cb3ed9.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";var h="/zopeneditor-about/assets/rexx-outline.874bbe03.gif",p="/zopeneditor-about/assets/rexx-completion.d6ede0cc.gif",u="/zopeneditor-about/assets/rexx-hover.177d05b4.gif",g="/zopeneditor-about/assets/rexx-copy.3e497dfe.gif",m="/zopeneditor-about/assets/rexx-references.c3178797.gif",f="/zopeneditor-about/assets/rexx-toggle-comment.af36ebf3.gif";const y={},b=s('
       Making REXX code changes
      In addition to COBOL, PL/I, and High Level Assembler (HLASM), IBM Z\xAE Open Editor supports TSO/E REXX editing. You can use the following features to edit REXX programs effectively.
      With the syntax highlighting capability, you can quickly distinguish the comments, strings, constants, variables, keywords, labels, functions, comparison, and arithmetic in a REXX program.
      The editor provides the following features and capabilities:
       Browsing code by using the Outline view
      As you view the source, you can use the Outline view to efficiently explore and navigate the code of the program. By looking through the items in this view, you can see the internal routines, and directly navigate to one by selecting it.
      REXX Outline
      How to use it
      You can use the Outline view only after you have opened a file or program. If the Outline view is not already expanded, you can open it by clicking View > Open view > Outline.
      You can use this view to:
      • Recognize internal routines quickly via the icons in the outline view.
      • Go to a wanted location in the code by clicking that section header in the view.
      • Sort by Position or Name.
      • Search for identifiers within the outline by pressing Ctrl+Shift+O (Windows), or Cmd+Shift+O (Mac) within the Editor window.
      When you move your cursor over the program, outline nodes are automatically selected. To toggle this and other features related to the Outline View, hover over the upper right corner of the Outline View. You can see the option ..., where you can click to find multiple options to organize your outline view such as Follow on Cursor, Filter by Type and Sort by Name, Position, and Type.
       Code completion
      The code completion feature suggests simple symbols, constant symbols, compound symbols, stems, function calls, keyword instructions, and built-in functions. The editor applies a suggestion to the file based on the context of the cursor position. For a cursor position inside a stem, the suggestion replaces the entire symbol. For a cursor position inside the tail of a compound symbol, the suggestion replaces a segment of the symbol. The casing of the suggestion replaces the casing of the symbol in the file. The code completion suggestions are not filtered by case.
      Code Completion
      How to use it
      The code completion suggestion is displayed automatically while you are typing outside of any comments or strings.
       Hovering for declaration
      The hover feature provides rich information about keyword instructions and built-in functions. By moving your cursor over these elements, a small pop-up window is displayed containing a title, description, and example usage.
      REXX Hover
      How to use it
      You can see hovers for keyword instructions and built-in functions by moving your cursor over the element. The hover disappears when your cursor moves elsewhere.
       Previewing include control directives
      To preview the contents of a %INCLUDE statement, point to the file name. If the file cannot be resolved, a red warning underline will appear on the file name. To open the file in a separate editor, press Ctrl and click (on Windows), or press Cmd and click (on Mac).
      REXX INCLUDE File Preview
      How to use it
      ',26),w=e("To resolve include files, you must specify the filepath to the include files in your "),v=e("ZAPP file property groups"),x=e(" to resolve the references. The location can be a local one such as another directory in your workspace, or it can be an MVS data set on a remote z/OS system using Zowe connectivity to find and load the files."),_=e("If no filepath is specified, the include files are not found in the provided filepath and an error is shown. To resolve this, follow the instructions provided and our "),k=e("ZAPP overview"),C=e(" and "),T=e("Property Groups"),E=e(" pages."),S=s('
       Operations on symbols
      By right clicking on a symbol, you can see a list of available operations.
      How to use it
      • Click Find All References: Alt+Shift+F12 (Windows) or Option+Shift+F12(Mac)
      • Click Peek References: Shift+F12 (Windows and Mac)
      A reference is defined as any matching symbol not in a comment or string. Keywords and built-in functions do not appear as references. The matches are determined by the context of the symbol. Internal routines match to their calls. Stems match to other stems. Simple symbols match to other simple symbols. Constant symbols match to other constant symbols. For compound symbols, the tail is broken into separate pieces, delimited by its periods, and matched to other constant or simple symbols. Additionally, the derivation and scope of a symbol is not considered.
      REXX PEEK REFERENCES
       Syntax checking
      The syntax checking feature underlines unrecognized statements and expressions in red, which helps you to make quick corrections and reduce compile errors.
      How to use it
      To see all the syntax errors in the open files, open the Problems view through the View menu or by clicking the error and warning icon at the bottom in the status bar. Double-click the list item to directly go to the problem.
       Undoing and redoing
      Undo your changes by pressing Ctrl+Z (Windows) or Cmd+Z (Mac). Redo your changes by pressing Ctrl+Shift+Z (Windows) or Cmd+Shift+Z (Mac).
       Commenting and uncommenting REXX code
      You can comment out one or multiple selected lines of code or a selected section of code by using the toggle comment function.
      How to use it
      To toggle comment for one or multiple selected lines of code, press Cmd+/ (Mac) or Ctrl+/ (Windows), or go to Edit > Toggle Line Comment.
      To toggle comments for a selected section of code, press Option+Shift+A (Mac) or Alt+Shift+A (Windows), or go to Edit > Toggle Block Comment.
      See the following example where we first toggle line comment on a single line, then toggle line comment on multiple selected lines, and finally toggle block comment on a selection:
      rexx toggle comment
      ',19);function O(X,R){const o=r("RouterLink");return a(),c(l,null,[b,n("p",null,[w,t(o,{to:"/Docs/setting_propertygroup.html"},{default:i(()=>[v]),_:1}),x]),n("p",null,[_,t(o,{to:"/Docs/zapp.html"},{default:i(()=>[k]),_:1}),C,t(o,{to:"/Docs/setting_propertygroup.html"},{default:i(()=>[T]),_:1}),E]),S],64)}var A=d(y,[["render",O]]);export{A as default};
+import{r,o as a,a as c,b as n,d as t,w as i,F as l,c as s,e}from"./app.daa93c96.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";var h="/zopeneditor-about/assets/rexx-outline.874bbe03.gif",p="/zopeneditor-about/assets/rexx-completion.d6ede0cc.gif",u="/zopeneditor-about/assets/rexx-hover.177d05b4.gif",g="/zopeneditor-about/assets/rexx-copy.3e497dfe.gif",m="/zopeneditor-about/assets/rexx-references.c3178797.gif",f="/zopeneditor-about/assets/rexx-toggle-comment.af36ebf3.gif";const y={},b=s('
       Making REXX code changes
      In addition to COBOL, PL/I, and High Level Assembler (HLASM), IBM Z\xAE Open Editor supports TSO/E REXX editing. You can use the following features to edit REXX programs effectively.
      With the syntax highlighting capability, you can quickly distinguish the comments, strings, constants, variables, keywords, labels, functions, comparison, and arithmetic in a REXX program.
      The editor provides the following features and capabilities:
       Browsing code by using the Outline view
      As you view the source, you can use the Outline view to efficiently explore and navigate the code of the program. By looking through the items in this view, you can see the internal routines, and directly navigate to one by selecting it.
      REXX Outline
      How to use it
      You can use the Outline view only after you have opened a file or program. If the Outline view is not already expanded, you can open it by clicking View > Open view > Outline.
      You can use this view to:
      • Recognize internal routines quickly via the icons in the outline view.
      • Go to a wanted location in the code by clicking that section header in the view.
      • Sort by Position or Name.
      • Search for identifiers within the outline by pressing Ctrl+Shift+O (Windows), or Cmd+Shift+O (Mac) within the Editor window.
      When you move your cursor over the program, outline nodes are automatically selected. To toggle this and other features related to the Outline View, hover over the upper right corner of the Outline View. You can see the option ..., where you can click to find multiple options to organize your outline view such as Follow on Cursor, Filter by Type and Sort by Name, Position, and Type.
       Code completion
      The code completion feature suggests simple symbols, constant symbols, compound symbols, stems, function calls, keyword instructions, and built-in functions. The editor applies a suggestion to the file based on the context of the cursor position. For a cursor position inside a stem, the suggestion replaces the entire symbol. For a cursor position inside the tail of a compound symbol, the suggestion replaces a segment of the symbol. The casing of the suggestion replaces the casing of the symbol in the file. The code completion suggestions are not filtered by case.
      Code Completion
      How to use it
      The code completion suggestion is displayed automatically while you are typing outside of any comments or strings.
       Hovering for declaration
      The hover feature provides rich information about keyword instructions and built-in functions. By moving your cursor over these elements, a small pop-up window is displayed containing a title, description, and example usage.
      REXX Hover
      How to use it
      You can see hovers for keyword instructions and built-in functions by moving your cursor over the element. The hover disappears when your cursor moves elsewhere.
       Previewing include control directives
      To preview the contents of a %INCLUDE statement, point to the file name. If the file cannot be resolved, a red warning underline will appear on the file name. To open the file in a separate editor, press Ctrl and click (on Windows), or press Cmd and click (on Mac).
      REXX INCLUDE File Preview
      How to use it
      ',26),w=e("To resolve include files, you must specify the filepath to the include files in your "),v=e("ZAPP file property groups"),x=e(" to resolve the references. The location can be a local one such as another directory in your workspace, or it can be an MVS data set on a remote z/OS system using Zowe connectivity to find and load the files."),_=e("If no filepath is specified, the include files are not found in the provided filepath and an error is shown. To resolve this, follow the instructions provided and our "),k=e("ZAPP overview"),C=e(" and "),T=e("Property Groups"),E=e(" pages."),S=s('
       Operations on symbols
      By right clicking on a symbol, you can see a list of available operations.
      How to use it
      • Click Find All References: Alt+Shift+F12 (Windows) or Option+Shift+F12(Mac)
      • Click Peek References: Shift+F12 (Windows and Mac)
      A reference is defined as any matching symbol not in a comment or string. Keywords and built-in functions do not appear as references. The matches are determined by the context of the symbol. Internal routines match to their calls. Stems match to other stems. Simple symbols match to other simple symbols. Constant symbols match to other constant symbols. For compound symbols, the tail is broken into separate pieces, delimited by its periods, and matched to other constant or simple symbols. Additionally, the derivation and scope of a symbol is not considered.
      REXX PEEK REFERENCES
       Syntax checking
      The syntax checking feature underlines unrecognized statements and expressions in red, which helps you to make quick corrections and reduce compile errors.
      How to use it
      To see all the syntax errors in the open files, open the Problems view through the View menu or by clicking the error and warning icon at the bottom in the status bar. Double-click the list item to directly go to the problem.
       Undoing and redoing
      Undo your changes by pressing Ctrl+Z (Windows) or Cmd+Z (Mac). Redo your changes by pressing Ctrl+Shift+Z (Windows) or Cmd+Shift+Z (Mac).
       Commenting and uncommenting REXX code
      You can comment out one or multiple selected lines of code or a selected section of code by using the toggle comment function.
      How to use it
      To toggle comment for one or multiple selected lines of code, press Cmd+/ (Mac) or Ctrl+/ (Windows), or go to Edit > Toggle Line Comment.
      To toggle comments for a selected section of code, press Option+Shift+A (Mac) or Alt+Shift+A (Windows), or go to Edit > Toggle Block Comment.
      See the following example where we first toggle line comment on a single line, then toggle line comment on multiple selected lines, and finally toggle block comment on a selection:
      rexx toggle comment
      ',19);function O(X,R){const o=r("RouterLink");return a(),c(l,null,[b,n("p",null,[w,t(o,{to:"/Docs/setting_propertygroup.html"},{default:i(()=>[v]),_:1}),x]),n("p",null,[_,t(o,{to:"/Docs/zapp.html"},{default:i(()=>[k]),_:1}),C,t(o,{to:"/Docs/setting_propertygroup.html"},{default:i(()=>[T]),_:1}),E]),S],64)}var A=d(y,[["render",O]]);export{A as default};
diff --git a/assets/editor_search.html.8465aab1.js b/assets/editor_search.html.4bb9cfa8.js
similarity index 96%
rename from assets/editor_search.html.8465aab1.js
rename to assets/editor_search.html.4bb9cfa8.js
index b274cb119..d1e1ef354 100644
--- a/assets/editor_search.html.8465aab1.js
+++ b/assets/editor_search.html.4bb9cfa8.js
@@ -1 +1 @@
-import{c as e}from"./app.f6cb3ed9.js";import{_ as o}from"./plugin-vue_export-helper.21dcd24c.js";const r={},a=e('
       Searching for COBOL, PL/I, HLASM, and REXX components
      You can search for strings and regular expressions across all files or a specific subset of files based on location or name patterns by using the Search view. The Search view also enables you to preview side by side how each change would look like, giving you the option to perform and reject each change one by one, or all at once.
      Take the sample files as an example. To search for components that generate and reference the "Daily Customer File Update" in the example program, take the following steps:
      1. Right-click the Explorer, and select Find in Folder....
      2. Enter the search term CUSTOMER-FILE and press the Return key.
        • Review some of the other search options such as using regular expressions and specifying patterns for files and folders to be excluded or included in the search.
        • To perform a regular expression search, select the .* icon and change the search term to CUST.*FILE and review the results.
      3. Results will appear in the Search Panel.
        • Clicking on the result will allow you to navigate to that location file in the Editor panel.
      4. (Optional) Perform a second search for the CRUNCH transaction to determine the affected components.
      ',4);function t(n,s){return a}var c=o(r,[["render",t]]);export{c as default};
+import{c as e}from"./app.daa93c96.js";import{_ as o}from"./plugin-vue_export-helper.21dcd24c.js";const r={},a=e('
       Searching for COBOL, PL/I, HLASM, and REXX components
      You can search for strings and regular expressions across all files or a specific subset of files based on location or name patterns by using the Search view. The Search view also enables you to preview side by side how each change would look like, giving you the option to perform and reject each change one by one, or all at once.
      Take the sample files as an example. To search for components that generate and reference the "Daily Customer File Update" in the example program, take the following steps:
      1. Right-click the Explorer, and select Find in Folder....
      2. Enter the search term CUSTOMER-FILE and press the Return key.
        • Review some of the other search options such as using regular expressions and specifying patterns for files and folders to be excluded or included in the search.
        • To perform a regular expression search, select the .* icon and change the search term to CUST.*FILE and review the results.
      3. Results will appear in the Search Panel.
        • Clicking on the result will allow you to navigate to that location file in the Editor panel.
      4. (Optional) Perform a second search for the CRUNCH transaction to determine the affected components.
      ',4);function t(n,s){return a}var c=o(r,[["render",t]]);export{c as default};
diff --git a/assets/external-posts.html.910c17a1.js b/assets/external-posts.html.fa85d592.js
similarity index 95%
rename from assets/external-posts.html.910c17a1.js
rename to assets/external-posts.html.fa85d592.js
index 78444d442..4a4cbc224 100644
--- a/assets/external-posts.html.910c17a1.js
+++ b/assets/external-posts.html.fa85d592.js
@@ -1 +1 @@
-import{r as n,o as s,a,b as e,d as t,F as i,e as o}from"./app.f6cb3ed9.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";const c={},d=e("h1",{id:"external-blog-posts-and-articles",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#external-blog-posts-and-articles","aria-hidden":"true"},"#"),o(" External Blog Posts and Articles")],-1),h=e("h2",{id:"announcements-and-official-communications",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#announcements-and-official-communications","aria-hidden":"true"},"#"),o(" Announcements and Official Communications")],-1),_={href:"https://developer.ibm.com/mainframe/category/ibm-z-open-editor/",target:"_blank",rel:"noopener noreferrer"},m=o("IBM Z Open Editor posts at developer.ibm.com"),p=e("h2",{id:"articles",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#articles","aria-hidden":"true"},"#"),o(" Articles")],-1),f=o("Sanjay Chandru, "),u={href:"https://ibmsystemsmag.com/IBM-Z/9/2019/ibm-z-open-editor",target:"_blank",rel:"noopener noreferrer"},b=o('"The fundamental underpinnings of an open approach to cloud-native development driven by DevOps practices"'),g=o(", IBM Systems Magazine, 09/2019."),v=o("William Pereira, "),k={href:"https://medium.com/@williampereira_80651/zowe-and-vscode-we-love-it-b5b4b8fdc1c1",target:"_blank",rel:"noopener noreferrer"},x=o('"Zowe and VSCode - We love it!"'),B=o(", Medium.com, 03/15/2020."),w=e("h2",{id:"ibm-z-devops-blogs",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-devops-blogs","aria-hidden":"true"},"#"),o(" IBM Z DevOps Blogs")],-1),M={href:"https://developer.ibm.com/mainframe/",target:"_blank",rel:"noopener noreferrer"},z=o("Mainframe Home @ developer.ibm.com"),y={href:"https://developer.ibm.com/mainframe/category/rdz/",target:"_blank",rel:"noopener noreferrer"},I=o("IBM Developer for z/OS Blog post."),O={href:"https://makingdeveloperslivesbetter.wordpress.com/",target:"_blank",rel:"noopener noreferrer"},Z=o("Mike Fulton's Making Developers Lives Better"),D={href:"https://developer.ibm.com/mainframe/category/podcasts/",target:"_blank",rel:"noopener noreferrer"},E=o("Z DevOps Postcasts"),P=e("h2",{id:"other-useful-resources",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#other-useful-resources","aria-hidden":"true"},"#"),o(" Other Useful Resources")],-1),C={href:"https://www.zowe.org/",target:"_blank",rel:"noopener noreferrer"},S=o("Zowe Project");function V(A,F){const r=n("ExternalLinkIcon");return s(),a(i,null,[d,h,e("ul",null,[e("li",null,[e("a",_,[m,t(r)])])]),p,e("ul",null,[e("li",null,[f,e("a",u,[b,t(r)]),g]),e("li",null,[v,e("a",k,[x,t(r)]),B])]),w,e("ul",null,[e("li",null,[e("a",M,[z,t(r)])]),e("li",null,[e("a",y,[I,t(r)])]),e("li",null,[e("a",O,[Z,t(r)])]),e("li",null,[e("a",D,[E,t(r)])])]),P,e("ul",null,[e("li",null,[e("a",C,[S,t(r)])])])],64)}var j=l(c,[["render",V]]);export{j as default};
+import{r as n,o as s,a,b as e,d as t,F as i,e as o}from"./app.daa93c96.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";const c={},d=e("h1",{id:"external-blog-posts-and-articles",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#external-blog-posts-and-articles","aria-hidden":"true"},"#"),o(" External Blog Posts and Articles")],-1),h=e("h2",{id:"announcements-and-official-communications",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#announcements-and-official-communications","aria-hidden":"true"},"#"),o(" Announcements and Official Communications")],-1),_={href:"https://developer.ibm.com/mainframe/category/ibm-z-open-editor/",target:"_blank",rel:"noopener noreferrer"},m=o("IBM Z Open Editor posts at developer.ibm.com"),p=e("h2",{id:"articles",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#articles","aria-hidden":"true"},"#"),o(" Articles")],-1),f=o("Sanjay Chandru, "),u={href:"https://ibmsystemsmag.com/IBM-Z/9/2019/ibm-z-open-editor",target:"_blank",rel:"noopener noreferrer"},b=o('"The fundamental underpinnings of an open approach to cloud-native development driven by DevOps practices"'),g=o(", IBM Systems Magazine, 09/2019."),v=o("William Pereira, "),k={href:"https://medium.com/@williampereira_80651/zowe-and-vscode-we-love-it-b5b4b8fdc1c1",target:"_blank",rel:"noopener noreferrer"},x=o('"Zowe and VSCode - We love it!"'),B=o(", Medium.com, 03/15/2020."),w=e("h2",{id:"ibm-z-devops-blogs",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-devops-blogs","aria-hidden":"true"},"#"),o(" IBM Z DevOps Blogs")],-1),M={href:"https://developer.ibm.com/mainframe/",target:"_blank",rel:"noopener noreferrer"},z=o("Mainframe Home @ developer.ibm.com"),y={href:"https://developer.ibm.com/mainframe/category/rdz/",target:"_blank",rel:"noopener noreferrer"},I=o("IBM Developer for z/OS Blog post."),O={href:"https://makingdeveloperslivesbetter.wordpress.com/",target:"_blank",rel:"noopener noreferrer"},Z=o("Mike Fulton's Making Developers Lives Better"),D={href:"https://developer.ibm.com/mainframe/category/podcasts/",target:"_blank",rel:"noopener noreferrer"},E=o("Z DevOps Postcasts"),P=e("h2",{id:"other-useful-resources",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#other-useful-resources","aria-hidden":"true"},"#"),o(" Other Useful Resources")],-1),C={href:"https://www.zowe.org/",target:"_blank",rel:"noopener noreferrer"},S=o("Zowe Project");function V(A,F){const r=n("ExternalLinkIcon");return s(),a(i,null,[d,h,e("ul",null,[e("li",null,[e("a",_,[m,t(r)])])]),p,e("ul",null,[e("li",null,[f,e("a",u,[b,t(r)]),g]),e("li",null,[v,e("a",k,[x,t(r)]),B])]),w,e("ul",null,[e("li",null,[e("a",M,[z,t(r)])]),e("li",null,[e("a",y,[I,t(r)])]),e("li",null,[e("a",O,[Z,t(r)])]),e("li",null,[e("a",D,[E,t(r)])])]),P,e("ul",null,[e("li",null,[e("a",C,[S,t(r)])])])],64)}var j=l(c,[["render",V]]);export{j as default};
diff --git a/assets/getting_started.html.5530d381.js b/assets/getting_started.html.ffa40eee.js
similarity index 99%
rename from assets/getting_started.html.5530d381.js
rename to assets/getting_started.html.ffa40eee.js
index cb55a5781..0e4f42ad2 100644
--- a/assets/getting_started.html.5530d381.js
+++ b/assets/getting_started.html.ffa40eee.js
@@ -1,4 +1,4 @@
-import{r,o as l,a as d,b as t,d as o,w as s,F as h,e,c as a}from"./app.f6cb3ed9.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const u={},p=t("h1",{id:"getting-started-with-ibm-z-open-editor",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#getting-started-with-ibm-z-open-editor","aria-hidden":"true"},"#"),e(" Getting started with IBM Z Open Editor")],-1),_=t("p",null,"The procedure to get started with IBM Z\xAE Open Editor is summarized as follows:",-1),m=t("li",null,"Get the latest version of Microsoft Visual Studio Code (VS Code)",-1),g=t("li",null,[t("a",{href:"#prerequisites"},"Install the prerequisites"),e(" (a Java\u2122 11 runtime environment as a minimum)")],-1),f=t("li",null,[t("a",{href:"#installing-ibm-z-open-editor"},"Install the IBM Z Open Editor VS Code extension from the VS Code Marketplace")],-1),v=e("(Optional) "),b=e("Set up integrations"),y=e(" for extended capabilities, such as installing IBM RSE API Plug-in for Zowe CLI to interact with z/OS"),w=t("h2",{id:"privacy-notice",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#privacy-notice","aria-hidden":"true"},"#"),e(" Privacy notice")],-1),S=t("p",null,"IBM Z Open Editor is provided free of charge, but we ask you to provide us feedback via the various means available including:",-1),k=e("Submit an "),O={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},I=e("issue in our GitHub repository"),x=e("Provide a review in the "),C={href:"https://marketplace.visualstudio.com/items?itemName=ibm.zopeneditor#review-details",target:"_blank",rel:"noopener noreferrer"},M=e("VS Code Marketplace"),E=t("li",null,"Keep the built-in telemetry and crash reports enabled",-1),V=e("This editor uses "),z={href:"https://code.visualstudio.com/docs/getstarted/telemetry",target:"_blank",rel:"noopener noreferrer"},B=e("Microsoft VS Code's Telemetry"),Z=e(" solution that collects anonymized telemetry data, which is used to help understand how to improve the product. While we appreciate the insights this data provides, we also know that not everyone wants to send usage data and you can disable telemetry as described in "),J={href:"https://code.visualstudio.com/docs/getstarted/telemetry#_disable-telemetry-reporting",target:"_blank",rel:"noopener noreferrer"},T=e("Disable Telemetry Reporting"),L=e(". You can also read "),A={href:"https://www.ibm.com/us-en/privacy",target:"_blank",rel:"noopener noreferrer"},j=e("IBM\xAE's General Privacy Statement"),R=e(" to learn more about our policies."),D=a('
      This current release of IBM Z Open Editor will collect anonymous data for the following events:
      • Activation of this VS Code extension
      • 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
      • 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:
      • Event time
      • Operating system and version
      • Country or region
      • Anonymous user and session ID
      • The type of editor used (VS Code, Eclipse Theia, Red Hat Dev Spaces)
      • Version numbers of Microsoft VS Code and IBM Z Open Editor
      • The major Java version and vendor used by the language servers
      • The name of the Z programming language used
      • The name of the operation performed
      • The type of z/OS protocol used (z/OSMF vs RSE API)
       Installing the IBM Z Open Editor VS Code extension
      IBM Z Open Editor is an extension for VS Code. Before installation, ensure that you have installed and configured the prerequisites, most importantly a Java runtime as main parts of the extension are implemented in the Java programming language.
       Prerequisites
      ',7),P=e("Review the "),W={href:"https://github.com/IBM/zopeneditor-about/raw/main/product-licenses/LICENSE.txt",target:"_blank",rel:"noopener noreferrer"},H=e("IBM Z Open Editor License Agreement"),q=e(" and "),X={href:"https://github.com/IBM/zopeneditor-about/raw/main/product-licenses/NOTICES.txt",target:"_blank",rel:"noopener noreferrer"},G=e("Third Party Notices"),N=e(" before downloading."),F=t("p",null,"Prerequisites for the installation:",-1),U=e("Visual Studio Code version 1.81.0 or later: IBM Z Open Editor is delivered as an extension to VS Code instead of a stand-alone editor, so you must install and configure VS Code first. We recommend always using the latest version of VS Code available. If you do not have VS Code installed we recommend using the "),K={href:"https://code.visualstudio.com/docs/languages/java#_install-visual-studio-code-for-java",target:"_blank",rel:"noopener noreferrer"},Y=e("Visual Studio Code for Java Installer"),Q=e(" provided by Microsoft, because it automatically downloads and installs a Java SDK together with VS Code. (You can skip the next bullet about Java dependency if you use this option.) For information about installation and configuration of VS Code, see its "),$={href:"https://code.visualstudio.com/docs/setup/setup-overview",target:"_blank",rel:"noopener noreferrer"},ee=e("documentation"),te=e("."),oe=t("p",null,"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 the extension 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:",-1),ne=e("We highly recommend using versions 11 or 17 of "),ie={href:"https://developer.ibm.com/languages/java/semeru-runtimes/",target:"_blank",rel:"noopener noreferrer"},se=e("IBM's Semeru Runtime"),ae=e(" that can be "),re={href:"https://developer.ibm.com/languages/java/semeru-runtimes/downloads",target:"_blank",rel:"noopener noreferrer"},le=e("downloaded here"),de=e(". IBM Semeru Runtimes enable developers to build and deploy Java applications that will start quickly and deliver great performance - all while using less memory. We use it ourselves for development."),he=e("Alternatively, you can use the LTS versions 11 or 17 of "),ce={href:"https://www.oracle.com/java/technologies/downloads",target:"_blank",rel:"noopener noreferrer"},ue=e("Oracle Java"),pe=e(" or the "),_e={href:"https://adoptium.net/releases.html",target:"_blank",rel:"noopener noreferrer"},me=e("OpenJDK"),ge=e("."),fe=t("li",null,"Newer versions of Java should also work, but are not tested with Z Open Editor.",-1),ve=t("p",null,[e("Various settings are provided to configure how the extension uses Java. See the "),t("a",{href:"#configuring-java"},"Configuring Java"),e(" section below for more details.")],-1),be=e("Zowe Explorer VS Code extension 2.17.0 or later and Zowe CLI 7.26.1 or later (optional): To make use of "),ye={href:"https://zowe.org",target:"_blank",rel:"noopener noreferrer"},we=e("Zowe"),Se=e(" to open and edit files directly from z/OS\xAE MVS\u2122 or z/OS UNIX System Services, you need Zowe client software and host components configured. More information on setting up Zowe can be found at "),ke=e("Setting up integrations to interact with z/OS"),Oe=e(". Once installed, you can access z/OS resources as documented in "),Ie=e("Interacting with z/OS"),xe=e("."),Ce=t("blockquote",null,[t("p",null,"Note: When you install IBM Z Open Editor from the VS Code Marketplace into your VS Code, the latest version of the Zowe Explorer VS Code extension is automatically co-installed as it is a mandatory prerequisite for running Z Open Editor.")],-1),Me=e("(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 "),Ee={href:"https://git-scm.com",target:"_blank",rel:"noopener noreferrer"},Ve=e("https://git-scm.com"),ze=e("."),Be=t("h3",{id:"installing-ibm-z-open-editor",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#installing-ibm-z-open-editor","aria-hidden":"true"},"#"),e(" Installing IBM Z Open Editor")],-1),Ze=e("There are three ways to download and install IBM Z Open Editor. If you are planning to use or evaluate the non-warranty and unsupported version of IBM Z Open Editor then you can install it directly from the "),Je={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},Te=e("VS Code Marketplace"),Le=e(" or the "),Ae={href:"https://open-vsx.org/extension/IBM/zopeneditor",target:"_blank",rel:"noopener noreferrer"},je=e("Open VSX Registry"),Re=e(". If you are an IBM Developer for Z Enterprise Edition or IBM Wazi customer, or are entitled to support for Z Open Editor in any other way, we recommend you download from our "),De={href:"https://ibm.github.io/mainframe-downloads/downloads.html",target:"_blank",rel:"noopener noreferrer"},Pe=e("Mainframe DEV Download site"),We=e(". This convenient zip file download includes code signing signature files and all related software components such as the IBM Open Debug VS Code extension, the IBM RSE API Plugin for Zowe CLI and the IBM distribution of Zowe CLI (a support entitlement that is also available for purchase)."),He=t("h4",{id:"installing-ibm-z-open-editor-from-the-vs-code-marketplace",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#installing-ibm-z-open-editor-from-the-vs-code-marketplace","aria-hidden":"true"},"#"),e(" Installing IBM Z Open Editor from the VS Code marketplace")],-1),qe=t("p",null,"When a Java runtime is installed, you can use either of the following ways to get versions of IBM Z Open Editor that are available in the VS Code Marketplace:",-1),Xe=t("li",null,[e("Start VS Code, open the Extensions view by clicking the "),t("strong",null,"Extensions"),e(" icon on the activity bar, or by clicking the menu "),t("strong",null,"File > Preferences > Extensions"),e(", and search for "),t("code",null,"IBM Z Open Editor"),e(".")],-1),Ge=e("Go to the "),Ne={href:"https://marketplace.visualstudio.com/items?itemName=ibm.zopeneditor",target:"_blank",rel:"noopener noreferrer"},Fe=e("VS Code Marketplace website that hosts IBM Z Open Editor"),Ue=e("."),Ke=t("p",null,[e("Then, click the "),t("strong",null,"Install"),e(" button and wait for the installation to complete.")],-1),Ye=t("h4",{id:"installing-ibm-z-open-editor-from-the-open-vsx-registry",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#installing-ibm-z-open-editor-from-the-open-vsx-registry","aria-hidden":"true"},"#"),e(" Installing IBM Z Open Editor from the Open VSX Registry")],-1),Qe=e("If you already have or want to configure VS Code to use the alternative public or a private on-site Open VSX Registry, or if you are using a VS Code compatible editor such as VSCodium or Eclipse Theia that use it by default, then you can find and install "),$e={href:"https://open-vsx.org/extension/IBM/zopeneditor",target:"_blank",rel:"noopener noreferrer"},et=e("IBM Z Open Editor"),tt=e(" and install it from there as well. See the "),ot={href:"https://github.com/eclipse/openvsx/wiki/Using-Open-VSX-in-VS-Code",target:"_blank",rel:"noopener noreferrer"},nt=e("Open VSX documentation"),it=e(" for how to configure and use this registry instead."),st=t("h4",{id:"installing-ibm-z-open-editor-from-a-vsix-file",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#installing-ibm-z-open-editor-from-a-vsix-file","aria-hidden":"true"},"#"),e(" Installing IBM Z Open Editor from a VSIX file")],-1),at=e("If you have downloaded the "),rt={href:"https://ibm.github.io/mainframe-downloads/downloads.html#wazi",target:"_blank",rel:"noopener noreferrer"},lt=e("Mainframe DEV Center's Download for VS Code"),dt=e(", you can install it with the following steps in VS Code."),ht=a('
      1. Unzip the downloaded zip file.
      2. Open the README.txt file in a text editor and follow the (optional) steps described there to verify the individual files with the provided code signing signatures.
      3. To install the zopeneditor-<version>.vsix file in VS Code, click the Extensions icon in VS Code's activity bar to open the Extensions view.
      4. Click the ... icon in the Extensions view's upper-right corner to reveal a drop-down menu of more actions.
      5. In the drop-down menu that appears, click Install from VSIX....
      6. Use the file picker that pops up to navigate to and select the VSIX file you downloaded, and then click Install.
      7. The extension should be installed from the VSIX file.
       Verifying the installation of IBM Z Open Editor
      ',2),ct=e("To quickly test whether IBM Z Open Editor is installed correctly, you can open a COBOL, PL/I, HLASM, REXX, or JCL program file on your machine. If you do not have such files on your machine, you can clone the sample repository as described in the "),ut=e("Exploring the sample files"),pt=e(" section and open its COBOL, PL/I, HLASM, REXX, or JCL program files. If you see syntax highlighting on COBOL, PL/I, HLASM, REXX, or JCL code, the extension is working correctly."),_t=a('
       Configuring Java
      The IBM Z Open Editor Welcome page will show you if Java was found successfully. To open the Welcome page, press Ctrl+Shift+P (Windows) or Cmd+Shift+P (MacOS), and type IBM Z Open Editor: Welcome. Check the prerequisites table on the page, and click the Java section to expand.
      The COBOL, PL/I, HLASM, REXX, and JCL language servers used 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 uses 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.
       Selecting the Java installation to use
      Before starting a language server, the language server clients in the IBM Z Open Editor VS Code extension try looking in different places to find a matching Java installation. They will look in the following places in this specific order and pick the first Java installation that is at least version 11 and 64-bit. If it finds a Java that fails the test against these criteria, it will continue searching.
      1. The zopeneditor.JAVA_HOME VS Code user setting.
      2. The java.home VS Code user setting.
      3. The JAVA_HOME environment variable.
      4. The PATH defined for the environment in which Z Open Editor runs, that is, you default Windows or MacOS path.
      5. A typical platform-specific location. For example, on MacOS, execute the /usr/libexec/java_home -V; on Windows, run the where java.exe commands to locate a valid Java installation.
      ',6),mt=e("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 versions. If you used the recommended "),gt={href:"https://code.visualstudio.com/docs/languages/java#_install-visual-studio-code-for-java",target:"_blank",rel:"noopener noreferrer"},ft=e("Visual Studio Code for Java Installer"),vt=e(", the "),bt=t("code",null,"java.home",-1),yt=e(" 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."),wt=a(`
      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 creating an entry in your VS Code user settings.
      To define a user setting, use the Preferences > Settings menu and either locate the setting in the graphical editor under IBM Z Open Editor or edit the setting JSON file directly by adding an entry as follows using an absolute path name to the Java installation directory.
      On MacOS:
      "zopeneditor.JAVA_HOME": "/Library/Java/JavaVirtualMachines/jdk11.0.15+10.jdk/Contents/Home"
+import{r,o as l,a as d,b as t,d as o,w as s,F as h,e,c as a}from"./app.daa93c96.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const u={},p=t("h1",{id:"getting-started-with-ibm-z-open-editor",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#getting-started-with-ibm-z-open-editor","aria-hidden":"true"},"#"),e(" Getting started with IBM Z Open Editor")],-1),_=t("p",null,"The procedure to get started with IBM Z\xAE Open Editor is summarized as follows:",-1),m=t("li",null,"Get the latest version of Microsoft Visual Studio Code (VS Code)",-1),g=t("li",null,[t("a",{href:"#prerequisites"},"Install the prerequisites"),e(" (a Java\u2122 11 runtime environment as a minimum)")],-1),f=t("li",null,[t("a",{href:"#installing-ibm-z-open-editor"},"Install the IBM Z Open Editor VS Code extension from the VS Code Marketplace")],-1),v=e("(Optional) "),b=e("Set up integrations"),y=e(" for extended capabilities, such as installing IBM RSE API Plug-in for Zowe CLI to interact with z/OS"),w=t("h2",{id:"privacy-notice",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#privacy-notice","aria-hidden":"true"},"#"),e(" Privacy notice")],-1),S=t("p",null,"IBM Z Open Editor is provided free of charge, but we ask you to provide us feedback via the various means available including:",-1),k=e("Submit an "),O={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},I=e("issue in our GitHub repository"),x=e("Provide a review in the "),C={href:"https://marketplace.visualstudio.com/items?itemName=ibm.zopeneditor#review-details",target:"_blank",rel:"noopener noreferrer"},M=e("VS Code Marketplace"),E=t("li",null,"Keep the built-in telemetry and crash reports enabled",-1),V=e("This editor uses "),z={href:"https://code.visualstudio.com/docs/getstarted/telemetry",target:"_blank",rel:"noopener noreferrer"},B=e("Microsoft VS Code's Telemetry"),Z=e(" solution that collects anonymized telemetry data, which is used to help understand how to improve the product. While we appreciate the insights this data provides, we also know that not everyone wants to send usage data and you can disable telemetry as described in "),J={href:"https://code.visualstudio.com/docs/getstarted/telemetry#_disable-telemetry-reporting",target:"_blank",rel:"noopener noreferrer"},T=e("Disable Telemetry Reporting"),L=e(". You can also read "),A={href:"https://www.ibm.com/us-en/privacy",target:"_blank",rel:"noopener noreferrer"},j=e("IBM\xAE's General Privacy Statement"),R=e(" to learn more about our policies."),D=a('
      This current release of IBM Z Open Editor will collect anonymous data for the following events:
      • Activation of this VS Code extension
      • 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
      • 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:
      • Event time
      • Operating system and version
      • Country or region
      • Anonymous user and session ID
      • The type of editor used (VS Code, Eclipse Theia, Red Hat Dev Spaces)
      • Version numbers of Microsoft VS Code and IBM Z Open Editor
      • The major Java version and vendor used by the language servers
      • The name of the Z programming language used
      • The name of the operation performed
      • The type of z/OS protocol used (z/OSMF vs RSE API)
       Installing the IBM Z Open Editor VS Code extension
      IBM Z Open Editor is an extension for VS Code. Before installation, ensure that you have installed and configured the prerequisites, most importantly a Java runtime as main parts of the extension are implemented in the Java programming language.
       Prerequisites
      ',7),P=e("Review the "),W={href:"https://github.com/IBM/zopeneditor-about/raw/main/product-licenses/LICENSE.txt",target:"_blank",rel:"noopener noreferrer"},H=e("IBM Z Open Editor License Agreement"),q=e(" and "),X={href:"https://github.com/IBM/zopeneditor-about/raw/main/product-licenses/NOTICES.txt",target:"_blank",rel:"noopener noreferrer"},G=e("Third Party Notices"),N=e(" before downloading."),F=t("p",null,"Prerequisites for the installation:",-1),U=e("Visual Studio Code version 1.81.0 or later: IBM Z Open Editor is delivered as an extension to VS Code instead of a stand-alone editor, so you must install and configure VS Code first. We recommend always using the latest version of VS Code available. If you do not have VS Code installed we recommend using the "),K={href:"https://code.visualstudio.com/docs/languages/java#_install-visual-studio-code-for-java",target:"_blank",rel:"noopener noreferrer"},Y=e("Visual Studio Code for Java Installer"),Q=e(" provided by Microsoft, because it automatically downloads and installs a Java SDK together with VS Code. (You can skip the next bullet about Java dependency if you use this option.) For information about installation and configuration of VS Code, see its "),$={href:"https://code.visualstudio.com/docs/setup/setup-overview",target:"_blank",rel:"noopener noreferrer"},ee=e("documentation"),te=e("."),oe=t("p",null,"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 the extension 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:",-1),ne=e("We highly recommend using versions 11 or 17 of "),ie={href:"https://developer.ibm.com/languages/java/semeru-runtimes/",target:"_blank",rel:"noopener noreferrer"},se=e("IBM's Semeru Runtime"),ae=e(" that can be "),re={href:"https://developer.ibm.com/languages/java/semeru-runtimes/downloads",target:"_blank",rel:"noopener noreferrer"},le=e("downloaded here"),de=e(". IBM Semeru Runtimes enable developers to build and deploy Java applications that will start quickly and deliver great performance - all while using less memory. We use it ourselves for development."),he=e("Alternatively, you can use the LTS versions 11 or 17 of "),ce={href:"https://www.oracle.com/java/technologies/downloads",target:"_blank",rel:"noopener noreferrer"},ue=e("Oracle Java"),pe=e(" or the "),_e={href:"https://adoptium.net/releases.html",target:"_blank",rel:"noopener noreferrer"},me=e("OpenJDK"),ge=e("."),fe=t("li",null,"Newer versions of Java should also work, but are not tested with Z Open Editor.",-1),ve=t("p",null,[e("Various settings are provided to configure how the extension uses Java. See the "),t("a",{href:"#configuring-java"},"Configuring Java"),e(" section below for more details.")],-1),be=e("Zowe Explorer VS Code extension 2.17.0 or later and Zowe CLI 7.26.1 or later (optional): To make use of "),ye={href:"https://zowe.org",target:"_blank",rel:"noopener noreferrer"},we=e("Zowe"),Se=e(" to open and edit files directly from z/OS\xAE MVS\u2122 or z/OS UNIX System Services, you need Zowe client software and host components configured. More information on setting up Zowe can be found at "),ke=e("Setting up integrations to interact with z/OS"),Oe=e(". Once installed, you can access z/OS resources as documented in "),Ie=e("Interacting with z/OS"),xe=e("."),Ce=t("blockquote",null,[t("p",null,"Note: When you install IBM Z Open Editor from the VS Code Marketplace into your VS Code, the latest version of the Zowe Explorer VS Code extension is automatically co-installed as it is a mandatory prerequisite for running Z Open Editor.")],-1),Me=e("(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 "),Ee={href:"https://git-scm.com",target:"_blank",rel:"noopener noreferrer"},Ve=e("https://git-scm.com"),ze=e("."),Be=t("h3",{id:"installing-ibm-z-open-editor",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#installing-ibm-z-open-editor","aria-hidden":"true"},"#"),e(" Installing IBM Z Open Editor")],-1),Ze=e("There are three ways to download and install IBM Z Open Editor. If you are planning to use or evaluate the non-warranty and unsupported version of IBM Z Open Editor then you can install it directly from the "),Je={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},Te=e("VS Code Marketplace"),Le=e(" or the "),Ae={href:"https://open-vsx.org/extension/IBM/zopeneditor",target:"_blank",rel:"noopener noreferrer"},je=e("Open VSX Registry"),Re=e(". If you are an IBM Developer for Z Enterprise Edition or IBM Wazi customer, or are entitled to support for Z Open Editor in any other way, we recommend you download from our "),De={href:"https://ibm.github.io/mainframe-downloads/downloads.html",target:"_blank",rel:"noopener noreferrer"},Pe=e("Mainframe DEV Download site"),We=e(". This convenient zip file download includes code signing signature files and all related software components such as the IBM Open Debug VS Code extension, the IBM RSE API Plugin for Zowe CLI and the IBM distribution of Zowe CLI (a support entitlement that is also available for purchase)."),He=t("h4",{id:"installing-ibm-z-open-editor-from-the-vs-code-marketplace",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#installing-ibm-z-open-editor-from-the-vs-code-marketplace","aria-hidden":"true"},"#"),e(" Installing IBM Z Open Editor from the VS Code marketplace")],-1),qe=t("p",null,"When a Java runtime is installed, you can use either of the following ways to get versions of IBM Z Open Editor that are available in the VS Code Marketplace:",-1),Xe=t("li",null,[e("Start VS Code, open the Extensions view by clicking the "),t("strong",null,"Extensions"),e(" icon on the activity bar, or by clicking the menu "),t("strong",null,"File > Preferences > Extensions"),e(", and search for "),t("code",null,"IBM Z Open Editor"),e(".")],-1),Ge=e("Go to the "),Ne={href:"https://marketplace.visualstudio.com/items?itemName=ibm.zopeneditor",target:"_blank",rel:"noopener noreferrer"},Fe=e("VS Code Marketplace website that hosts IBM Z Open Editor"),Ue=e("."),Ke=t("p",null,[e("Then, click the "),t("strong",null,"Install"),e(" button and wait for the installation to complete.")],-1),Ye=t("h4",{id:"installing-ibm-z-open-editor-from-the-open-vsx-registry",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#installing-ibm-z-open-editor-from-the-open-vsx-registry","aria-hidden":"true"},"#"),e(" Installing IBM Z Open Editor from the Open VSX Registry")],-1),Qe=e("If you already have or want to configure VS Code to use the alternative public or a private on-site Open VSX Registry, or if you are using a VS Code compatible editor such as VSCodium or Eclipse Theia that use it by default, then you can find and install "),$e={href:"https://open-vsx.org/extension/IBM/zopeneditor",target:"_blank",rel:"noopener noreferrer"},et=e("IBM Z Open Editor"),tt=e(" and install it from there as well. See the "),ot={href:"https://github.com/eclipse/openvsx/wiki/Using-Open-VSX-in-VS-Code",target:"_blank",rel:"noopener noreferrer"},nt=e("Open VSX documentation"),it=e(" for how to configure and use this registry instead."),st=t("h4",{id:"installing-ibm-z-open-editor-from-a-vsix-file",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#installing-ibm-z-open-editor-from-a-vsix-file","aria-hidden":"true"},"#"),e(" Installing IBM Z Open Editor from a VSIX file")],-1),at=e("If you have downloaded the "),rt={href:"https://ibm.github.io/mainframe-downloads/downloads.html#wazi",target:"_blank",rel:"noopener noreferrer"},lt=e("Mainframe DEV Center's Download for VS Code"),dt=e(", you can install it with the following steps in VS Code."),ht=a('
      1. Unzip the downloaded zip file.
      2. Open the README.txt file in a text editor and follow the (optional) steps described there to verify the individual files with the provided code signing signatures.
      3. To install the zopeneditor-<version>.vsix file in VS Code, click the Extensions icon in VS Code's activity bar to open the Extensions view.
      4. Click the ... icon in the Extensions view's upper-right corner to reveal a drop-down menu of more actions.
      5. In the drop-down menu that appears, click Install from VSIX....
      6. Use the file picker that pops up to navigate to and select the VSIX file you downloaded, and then click Install.
      7. The extension should be installed from the VSIX file.
       Verifying the installation of IBM Z Open Editor
      ',2),ct=e("To quickly test whether IBM Z Open Editor is installed correctly, you can open a COBOL, PL/I, HLASM, REXX, or JCL program file on your machine. If you do not have such files on your machine, you can clone the sample repository as described in the "),ut=e("Exploring the sample files"),pt=e(" section and open its COBOL, PL/I, HLASM, REXX, or JCL program files. If you see syntax highlighting on COBOL, PL/I, HLASM, REXX, or JCL code, the extension is working correctly."),_t=a('
       Configuring Java
      The IBM Z Open Editor Welcome page will show you if Java was found successfully. To open the Welcome page, press Ctrl+Shift+P (Windows) or Cmd+Shift+P (MacOS), and type IBM Z Open Editor: Welcome. Check the prerequisites table on the page, and click the Java section to expand.
      The COBOL, PL/I, HLASM, REXX, and JCL language servers used 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 uses 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.
       Selecting the Java installation to use
      Before starting a language server, the language server clients in the IBM Z Open Editor VS Code extension try looking in different places to find a matching Java installation. They will look in the following places in this specific order and pick the first Java installation that is at least version 11 and 64-bit. If it finds a Java that fails the test against these criteria, it will continue searching.
      1. The zopeneditor.JAVA_HOME VS Code user setting.
      2. The java.home VS Code user setting.
      3. The JAVA_HOME environment variable.
      4. The PATH defined for the environment in which Z Open Editor runs, that is, you default Windows or MacOS path.
      5. A typical platform-specific location. For example, on MacOS, execute the /usr/libexec/java_home -V; on Windows, run the where java.exe commands to locate a valid Java installation.
      ',6),mt=e("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 versions. If you used the recommended "),gt={href:"https://code.visualstudio.com/docs/languages/java#_install-visual-studio-code-for-java",target:"_blank",rel:"noopener noreferrer"},ft=e("Visual Studio Code for Java Installer"),vt=e(", the "),bt=t("code",null,"java.home",-1),yt=e(" 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."),wt=a(`
      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 creating an entry in your VS Code user settings.
      To define a user setting, use the Preferences > Settings menu and either locate the setting in the graphical editor under IBM Z Open Editor or edit the setting JSON file directly by adding an entry as follows using an absolute path name to the Java installation directory.
      On MacOS:
      "zopeneditor.JAVA_HOME": "/Library/Java/JavaVirtualMachines/jdk11.0.15+10.jdk/Contents/Home"
 
      On Windows:
      "zopeneditor.JAVA_HOME": "C:\\\\Program Files\\\\Java\\\\jdk11.0.15+10"
 
       Configuring the Java memory allocation
      By default, the language server client that starts the individual language servers for COBOL, PL/I, HLASM, or REXX allocates a maximum of 512 MB of memory for each. The language servers will consume much less memory at startup, and then allocate and free memory when parsing programs. However, they might run out of memory when parsing very large program files and reach the predefined limit. To allow allocating more memory, use the following VS Code setting to specify a new maximum value:
      "zopeneditor.server.memoryAllocation": 640
 
      Keep in mind that this value is for each language you use, so when using both COBOL and PL/I, you might end up with a consumption of double the amount specified. If you are working with smaller programs or your computer might not support such a large amount of memory, you can also try values smaller than 512 with this setting.
       Using IBM Z Open Editor in cloud-based editors
      Z Open Editor can be installed and used with various cloud or browser-based editing environments that utilize VS Code as the editor. We list a couple of examples that we test with, but there might be more configurations that the editor would also work in.
       Red Hat Dev Spaces for OpenShift
      `,13),St=e("Our recommended cloud-based development environment is Red Hat OpenShift Dev Spaces that provides a cloud-based development environment that is fully integrated into Red Hat OpenShift. In fact, we have created a customized version of Dev Spaces for z/OS development called IBM Wazi for Dev Spaces that adds Z Open Editor, Z Open Debug as well as many additional zDevOps tools into one convenient solution package that can be easily deployed with an OpenShift operator and used with your z/OS LPARs as well as "),kt={href:"https://www.ibm.com/cloud/wazi-as-a-service",target:"_blank",rel:"noopener noreferrer"},Ot=e("Wazi as a Service"),It=e(" cloud-based z/OS server instances, or emulated Wazi Sandbox z/OS instances. Wazi for Dev Spaces is part of the "),xt={href:"https://www.ibm.com/products/z-and-cloud-modernization-stack",target:"_blank",rel:"noopener noreferrer"},Ct=e("IBM Z and Cloud Modernization Stack"),Mt=e(" product offering."),Et=e("To try Z Open Editor for free in Red Hat OpenShift Dev Spaces, you can sign up for a 30-day trial of the "),Vt={href:"https://developers.redhat.com/developer-sandbox",target:"_blank",rel:"noopener noreferrer"},zt=e("OpenShift Sandbox and Red Hat Developer Sandbox"),Bt=e(". We have a "),Zt={href:"https://github.com/IBM/zopeneditor-about/tree/main/che",target:"_blank",rel:"noopener noreferrer"},Jt=e("full tutorial for signing up and using Z Open Editor here"),Tt=e("."),Lt=e("You can also try Wazi for Dev Spaces as part of a "),At={href:"https://www.ibm.com/docs/en/wazi-aas/1.0.0?topic=getting-started-wazi-as-service",target:"_blank",rel:"noopener noreferrer"},jt=e("Wazi as a Service trial as documented here"),Rt=e('. For this we also provide a detailed tutorial in our new IBM Redbook "'),Dt={href:"https://www.redbooks.ibm.com/abstracts/sg248532.html",target:"_blank",rel:"noopener noreferrer"},Pt=e("Hybrid Cloud with IBM Z"),Wt=e('", Chapter 5.'),Ht=t("h3",{id:"gitpod",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#gitpod","aria-hidden":"true"},"#"),e(" GitPod")],-1),qt={href:"https://www.gitpod.io/",target:"_blank",rel:"noopener noreferrer"},Xt=e("GitPod"),Gt=e(" is a cloud-based IDE offering by the GitPod company that can also utilize VS Code as the browser-based editor and integrate with all the major Git service providers such as GitLab, GitHub, and Bitbucket. After you sign in with an account from either of these Git services, you can easily start a workspace with Z Open Editor."),Nt=e("To try it out with our code samples repository, use this link "),Ft={href:"https://gitpod.io/#https://github.com/phaumer/zopeneditor-sample",target:"_blank",rel:"noopener noreferrer"},Ut=e("https://gitpod.io/#https://github.com/phaumer/zopeneditor-sample"),Kt=e(". The workspace will start up and load a custom image prepared by our team that even contains Zowe CLI and Ansible CLI. After the editor is up, you might have to click F1 and select the command "),Yt=t("code",null,"View: Focus Activity Bar",-1),Qt=e(" to bring in the sidebar that allows you to find our sample programs. Z Open Editor was automatically installed for this workspace, so you can just open a program and start editing. Note that this is a paid-for service, but the first hours are free."),$t=t("h3",{id:"github-codespaces",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#github-codespaces","aria-hidden":"true"},"#"),e(" GitHub Codespaces")],-1),eo=e("Z Open Editor can also be used with all of its capabilities in Microsoft's "),to={href:"https://github.com/codespaces",target:"_blank",rel:"noopener noreferrer"},oo=e("GitHub Codespaces"),no=e(". After your start your development environment in Codespaces, you can find and install Z Open Editor from the integrated marketplace. You can also use extension recommendations."),io=e("Try it by using this link "),so={href:"https://github.com/codespaces/new?machine=basicLinux32gb&repo=160883618&ref=wazi-main&location=WestUs2",target:"_blank",rel:"noopener noreferrer"},ao=e("https://github.com/codespaces/new?machine=basicLinux32gb&repo=160883618&ref=wazi-main&location=WestUs2"),ro=e(" that loads our Z Open Editor sample repository. After the editor is up, click "),lo=t("strong",null,"Install",-1),ho=e(' in the dialog that asks "Do you want to install the recommended extensions for this repository?". Note that this is a paid-for service, but the first hours are free.'),co=t("h3",{id:"pure-web-based-editing-in-vscode-dev-and-github-dev",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#pure-web-based-editing-in-vscode-dev-and-github-dev","aria-hidden":"true"},"#"),e(" Pure web-based editing in vscode.dev and github.dev")],-1),uo=e("Z Open Editor can be used as a pure web extension with limited capabilities when using Visual Studio Code in a browser, such as on "),po={href:"https://vscode.dev/",target:"_blank",rel:"noopener noreferrer"},_o=e("vscode.dev"),mo=e(" or "),go={href:"https://github.dev/github/dev",target:"_blank",rel:"noopener noreferrer"},fo=e("github.dev"),vo=e("."),bo=e("Try it by going to "),yo={href:"https://vscode.dev/github/IBM/zopeneditor-sample",target:"_blank",rel:"noopener noreferrer"},wo=e("https://vscode.dev/github/IBM/zopeneditor-sample"),So=e(" and confirming in the dialog to install the recommended extensions by clicking "),ko=t("strong",null,"Install",-1),Oo=e(". No language server capabilities will be available, but syntax highlighting for all our supported languages.");function Io(xo,Co){const i=r("RouterLink"),n=r("ExternalLinkIcon");return l(),d(h,null,[p,_,t("ol",null,[m,g,f,t("li",null,[v,o(i,{to:"/Docs/setup_integration.html"},{default:s(()=>[b]),_:1}),y])]),w,S,t("ul",null,[t("li",null,[k,t("a",O,[I,o(n)])]),t("li",null,[x,t("a",C,[M,o(n)])]),E]),t("p",null,[V,t("a",z,[B,o(n)]),Z,t("a",J,[T,o(n)]),L,t("a",A,[j,o(n)]),R]),D,t("p",null,[P,t("a",W,[H,o(n)]),q,t("a",X,[G,o(n)]),N]),F,t("ul",null,[t("li",null,[t("p",null,[U,t("a",K,[Y,o(n)]),Q,t("a",$,[ee,o(n)]),te])]),t("li",null,[oe,t("ul",null,[t("li",null,[ne,t("a",ie,[se,o(n)]),ae,t("a",re,[le,o(n)]),de]),t("li",null,[he,t("a",ce,[ue,o(n)]),pe,t("a",_e,[me,o(n)]),ge]),fe]),ve]),t("li",null,[t("p",null,[be,t("a",ye,[we,o(n)]),Se,o(i,{to:"/Docs/setup_integration.html"},{default:s(()=>[ke]),_:1}),Oe,o(i,{to:"/Docs/interact_zos_overview.html"},{default:s(()=>[Ie]),_:1}),xe]),Ce]),t("li",null,[t("p",null,[Me,t("a",Ee,[Ve,o(n)]),ze])])]),Be,t("p",null,[Ze,t("a",Je,[Te,o(n)]),Le,t("a",Ae,[je,o(n)]),Re,t("a",De,[Pe,o(n)]),We]),He,qe,t("ul",null,[Xe,t("li",null,[Ge,t("a",Ne,[Fe,o(n)]),Ue])]),Ke,Ye,t("p",null,[Qe,t("a",$e,[et,o(n)]),tt,t("a",ot,[nt,o(n)]),it]),st,t("p",null,[at,t("a",rt,[lt,o(n)]),dt]),ht,t("p",null,[ct,o(i,{to:"/Docs/samplefiles.html"},{default:s(()=>[ut]),_:1}),pt]),_t,t("p",null,[mt,t("a",gt,[ft,o(n)]),vt,bt,yt]),wt,t("p",null,[St,t("a",kt,[Ot,o(n)]),It,t("a",xt,[Ct,o(n)]),Mt]),t("p",null,[Et,t("a",Vt,[zt,o(n)]),Bt,t("a",Zt,[Jt,o(n)]),Tt]),t("p",null,[Lt,t("a",At,[jt,o(n)]),Rt,t("a",Dt,[Pt,o(n)]),Wt]),Ht,t("p",null,[t("a",qt,[Xt,o(n)]),Gt]),t("p",null,[Nt,t("a",Ft,[Ut,o(n)]),Kt,Yt,Qt]),$t,t("p",null,[eo,t("a",to,[oo,o(n)]),no]),t("p",null,[io,t("a",so,[ao,o(n)]),ro,lo,ho]),co,t("p",null,[uo,t("a",po,[_o,o(n)]),mo,t("a",go,[fo,o(n)]),vo]),t("p",null,[bo,t("a",yo,[wo,o(n)]),So,ko,Oo])],64)}var Vo=c(u,[["render",Io]]);export{Vo as default};
diff --git a/assets/git_integration.html.b7128f18.js b/assets/git_integration.html.7a2bdb12.js
similarity index 98%
rename from assets/git_integration.html.b7128f18.js
rename to assets/git_integration.html.7a2bdb12.js
index e67424113..83b867a35 100644
--- a/assets/git_integration.html.b7128f18.js
+++ b/assets/git_integration.html.7a2bdb12.js
@@ -1 +1 @@
-import{r as a,o as n,a as r,b as e,d as o,F as c,e as t,c as s}from"./app.f6cb3ed9.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";const d={},l=e("h1",{id:"using-the-integrated-git",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-the-integrated-git","aria-hidden":"true"},"#"),t(" Using the integrated Git")],-1),p=e("h2",{id:"prerequisites",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#prerequisites","aria-hidden":"true"},"#"),t(" Prerequisites")],-1),m=t("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 "),g={href:"https://git-scm.com",target:"_blank",rel:"noopener noreferrer"},u=t("https://git-scm.com"),f=t("."),b=s('
       Creating Git branches
      To manage your codes for parallel development, you can create a new branch using the integrated Git. To create a new Git branch:
      1. Select the branch icon at the lower left of the browser page in the colored status bar. A drop-down box at the top of the browser page appears with various options.
      2. Select the branch icon at the bottom again and then Create new branch....
      3. Enter the name of the new branch.
       Committing changes into Git branches
      After making code changes and refinements, you can commit changed files to the Git repository.
      To commit changed files:
      1. Open the Git view by clicking View > Git, or pressing Ctrl+Shift+G (Windows and Mac), which lists all the files that you added or modified.
      2. To review changes to a changed file that is marked by the M, double-click the file to open a diff editor view.
      3. Take one of the following actions:
        • Open the file.
        • Discard changes.
        • Add your file for the next commit that is called Staging by clicking the + icon to stage it.
      4. Provide a short description in the Commit message text box at the top, such as Implemented Update Report.
      5. Make sure that the branch you want to commit to is selected at the bottom of the browser page.
      6. Click Commit on the top of the Git view. The list of files is empty now as all changes were committed to the branch.
      You can review these changes in the Git History viewer after completing the commit.
      ',8),_=t("For more information about using Git, see "),w={href:"https://code.visualstudio.com/docs/editor/versioncontrol",target:"_blank",rel:"noopener noreferrer"},y=t("VS Code documentation"),v=t(".");function G(x,k){const i=a("ExternalLinkIcon");return n(),r(c,null,[l,p,e("p",null,[m,e("a",g,[u,o(i)]),f]),b,e("p",null,[_,e("a",w,[y,o(i)]),v])],64)}var S=h(d,[["render",G]]);export{S as default};
+import{r as a,o as n,a as r,b as e,d as o,F as c,e as t,c as s}from"./app.daa93c96.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";const d={},l=e("h1",{id:"using-the-integrated-git",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-the-integrated-git","aria-hidden":"true"},"#"),t(" Using the integrated Git")],-1),p=e("h2",{id:"prerequisites",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#prerequisites","aria-hidden":"true"},"#"),t(" Prerequisites")],-1),m=t("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 "),g={href:"https://git-scm.com",target:"_blank",rel:"noopener noreferrer"},u=t("https://git-scm.com"),f=t("."),b=s('
       Creating Git branches
      To manage your codes for parallel development, you can create a new branch using the integrated Git. To create a new Git branch:
      1. Select the branch icon at the lower left of the browser page in the colored status bar. A drop-down box at the top of the browser page appears with various options.
      2. Select the branch icon at the bottom again and then Create new branch....
      3. Enter the name of the new branch.
       Committing changes into Git branches
      After making code changes and refinements, you can commit changed files to the Git repository.
      To commit changed files:
      1. Open the Git view by clicking View > Git, or pressing Ctrl+Shift+G (Windows and Mac), which lists all the files that you added or modified.
      2. To review changes to a changed file that is marked by the M, double-click the file to open a diff editor view.
      3. Take one of the following actions:
        • Open the file.
        • Discard changes.
        • Add your file for the next commit that is called Staging by clicking the + icon to stage it.
      4. Provide a short description in the Commit message text box at the top, such as Implemented Update Report.
      5. Make sure that the branch you want to commit to is selected at the bottom of the browser page.
      6. Click Commit on the top of the Git view. The list of files is empty now as all changes were committed to the branch.
      You can review these changes in the Git History viewer after completing the commit.
      ',8),_=t("For more information about using Git, see "),w={href:"https://code.visualstudio.com/docs/editor/versioncontrol",target:"_blank",rel:"noopener noreferrer"},y=t("VS Code documentation"),v=t(".");function G(x,k){const i=a("ExternalLinkIcon");return n(),r(c,null,[l,p,e("p",null,[m,e("a",g,[u,o(i)]),f]),b,e("p",null,[_,e("a",w,[y,o(i)]),v])],64)}var S=h(d,[["render",G]]);export{S as default};
diff --git a/assets/hlasm-blog.html.d0be3dd3.js b/assets/hlasm-blog.html.4a6e4d92.js
similarity index 99%
rename from assets/hlasm-blog.html.d0be3dd3.js
rename to assets/hlasm-blog.html.4a6e4d92.js
index 7fdb0931d..ef0260769 100644
--- a/assets/hlasm-blog.html.d0be3dd3.js
+++ b/assets/hlasm-blog.html.4a6e4d92.js
@@ -1 +1 @@
-import{r as s,o as n,a,b as e,d as r,F as i,e as o,c as l}from"./app.f6cb3ed9.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";var h="/zopeneditor-about/assets/hlasm-completion.d984eb2b.gif",c="/zopeneditor-about/assets/hlasm-hover.19402729.gif",u="/zopeneditor-about/assets/hlasm-definition.8666e341.gif",p="/zopeneditor-about/assets/hlasm-copy.7b7a1315.gif",m="/zopeneditor-about/assets/hlasm-references.8a795b5e.gif",_="/zopeneditor-about/assets/hlasm-outline.62567372.gif",b="/zopeneditor-about/assets/hlasm-tabs.151c5141.gif";const f={},g=e("h1",{id:"ibm-z-open-editor-a-modern-ide-for-ibm-high-level-assembler",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-a-modern-ide-for-ibm-high-level-assembler","aria-hidden":"true"},"#"),o(" IBM Z Open Editor: A modern IDE for IBM High Level Assembler")],-1),w=e("blockquote",null,[e("p",null,"By Daniel Beall")],-1),v=o("It may seem that an assembler editor simply needs syntax highlighting. After all, don't assembler programmers need only the most spartan of tools? However, after collaborating with IBMer assembler experts Brenton Belmar, a Senior Technical Staff Member of the IBM zMilicode team, Mike Fulton, an IBM Distinguished Engineer and "),y={href:"https://makingdeveloperslivesbetter.wordpress.com/2019/09/09/ibm-z-open-automation-utilities/",target:"_blank",rel:"noopener noreferrer"},k=o("IBM Z Open Automation Utilities"),M=o(" creator, and Walter Church of the IBM z/VM team, this sentiment could not be proven more wrong. We found that assembler deserves, just like COBOL and PL/I (two languages our IBM Z Open Editor also supports), much more attention. The IBM Z Open Editor adds, with version 1.0 available on June 12th, 2020, a new language server for IBM High Level Assembler (HLASM), bringing support for developers who want to use Visual Studio Code or "),I={href:"https://www.ibm.com/products/wazi-for-red-hat-codeready-workspaces",target:"_blank",rel:"noopener noreferrer"},B=o("Red Hat CodeReady Workspaces"),C=o(" to develop and maintain their applications."),E=o("Before we dive into the specifics of our assembler support, you might be wondering what exactly language servers and the Z Open Editor are. "),x={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},S=o("The Z Open Editor"),z=o(' is an extension for Visual Studio Code that provides language support for IBM Enterprise COBOL and PL/I. The language server is what "powers" our tooling for languages like COBOL, PL/I, and now HLASM. Language servers are implementations of language server protocol which is an initiative to standardize communication between editors and programming language tooling.'),T=e("p",null,"The process of building a language server for HLASM and adding it to our extension was not trivial, and we could not have done it without listening to users. From Brenton, Mike, and Walter, we discovered several important points about assembler:",-1),O=e("li",null,[e("p",null,"HLASM has very advanced features compared to traditional assembly languages such as macros, copybooks, and conditional assembler.")],-1),L=e("li",null,[e("p",null,"HLASM programs can be very large. We found assembler programs with upwards of thirty thousand lines of code and of symbols. Navigating and exploring such large programs requires the ability to have indexes in the form of outline views and cross-refencing support in the editor that is language aware and goes beyond simple search.")],-1),A=o("z/Architecture is a CISC, or complex instruction set computer-architecture, with a myriad of instructions. In addition to bread-and-butter instructions, the latest mainframes support state-of-the-art "),H={href:"https://www.ibm.com/support/pages/sites/default/files/support/swg/swgtech.nsf/0/7df1aa86f5dbfd3085257ac0004ef2e6/%24FILE/Transactional_Execution_Facility.pdf",target:"_blank",rel:"noopener noreferrer"},F=o("hardware transactional memory"),D=o(", cryptographic, and SIMD instructions. The programmer must be able tohave code completion for instructions as well as inspect them."),P=l('
      It's clear the collaborative process helped us keep the uniqueness of assembler in mind. While designing the outline view, we experimented with including every symbol within a program. However, after better learning our user's needs, we found that it is better to simply have only CSECTs, DSECTs, and macros in the outline view. Often, if every symbol were to be included, the outline view would become extremely cluttered. The outline view is not the only feature where we've kept assembler's distinctiveness firmly in mind. In our code completion, we include reference information about assembler instructions. And, last but not least, we have included configurable vertical bars and tab stops to help users easily 'eyeball' sequence numbers and continuation line indicators. We feel these features will help assembler programmers, both veterans and novices alike, have a better experience working with language in our editor.
       Editor Features
      Let me walk you through some of the capabilities we added and how we think they can be useful for assembler developers.
      Code Completion: When typing an instruction or operand, the editor will suggest instructions or symbol names. Since HLASM has over a thousand instructions, we found this to be very useful for quickly searching for relevant instructions.
      COMPLETION GIF
      Hover: Never worry about having to scroll to find the contents of a symbol again. To preview the contents of an operand symbol, simply move your mouse cursor over the symbol.
      HOVER GIF
      Go to Definition: To go to where a symbol is defined, simply right click an operand symbol, and click 'Go to Definition.' This is very convenient for large assembler programs. Having to scroll through a program or press Ctrl +F (Windows) or Cmd+F (Mac) to search through every use of a symbol is very tedious in comparison.
      GO TO DEFINITION GIF
      ',9),W=o("Copybook Resolution: To preview the contents of a copybook, move your mouse cursor over the copybook name in a COPY statement. You can also open the copybook in a separate editor by pressing Ctrl+Click (Windows) or Cmd+Click (Mac). To use this feature "),N={href:"https://ibm.github.io/zopeneditor-about/Docs/setting_propertygroup.html",target:"_blank",rel:"noopener noreferrer"},R=o("property groups"),G=o(" will have to be set."),V=e("p",null,[e("img",{src:p,alt:"COPYBOOK GIF"})],-1),Z=e("p",null,"Peek References: A results references view is displayed underneath symbols. Click any result to go to that location within a file.",-1),q=e("p",null,[e("img",{src:m,alt:"HLASM PEEK REFERENCES GIF"})],-1),U=e("p",null,"Outline View: Explore and navigate assembler code. Relevant macros, CSECTs, and DSECTs are shown in the outline view.",-1),Y=e("p",null,[e("img",{src:_,alt:"HLASM OUTLINE GIF"})],-1),j=o("Configurable Vertical Rulers and Tabstops: Easily navigate within a line. Press Tab to move forward and Shift+Tab to move backwards. Vertical rulers are included by default. Please see our "),K={href:"https://ibm.github.io/zopeneditor-about/Docs/setting_tabstops.html",target:"_blank",rel:"noopener noreferrer"},J=o("documentation"),Q=o(" to adjust vertical rulers and tabstops from defaults."),X=e("p",null,[e("img",{src:b,alt:"HLASM RULERS AND TABSTOPS GIF"})],-1),$=e("p",null,[e("strong",null,"Excited to try the Z Open Editor with HLASM support? Here's how")],-1),ee=o("First, find out more about our editor at our "),oe={href:"https://ibm.github.io/zopeneditor-about/",target:"_blank",rel:"noopener noreferrer"},te=o("About Page"),re=o(", and then see a full list of features on our "),se={href:"https://ibm.github.io/zopeneditor-about/Docs/introduction.html",target:"_blank",rel:"noopener noreferrer"},ne=o("Documentation Page"),ae=o(". Next, please ensure "),ie={href:"https://ibm.github.io/zopeneditor-about/Docs/getting_started.html#prerequisites",target:"_blank",rel:"noopener noreferrer"},le=o("prerequisites"),de=o(" for our editor are installed. Then, download the extension through the "),he={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},ce=o("Visual Studio Code Marketplace"),ue=o(". Once the extension is installed, open an assembler file of your choice, or one of our "),pe={href:"https://github.com/IBM/zopeneditor-sample",target:"_blank",rel:"noopener noreferrer"},me=o("samples"),_e=o(". The editor should offer syntax highlighting and the features described above."),be=e("h2",{id:"we-would-love-to-hear-from-you",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#we-would-love-to-hear-from-you","aria-hidden":"true"},"#"),o(" We would love to hear from you")],-1),fe=e("p",null,"We're incredibly thankful for having the opportunity to work with assembler experts such as Brenton, Walter, and Mike. But, at the same time, we want to better meet the needs of users external to IBM. We greatly welcome any feedback about our editor and how you and your organization are using assembler.",-1),ge=e("p",null,"Having said that, we've created two ways for you to easily provide your comments:",-1),we=o("1. Take our "),ve={href:"http://ibm.biz/HLASMsurvey",target:"_blank",rel:"noopener noreferrer"},ye=o("survey"),ke=o(" about HLASM editors and tooling."),Me=o("2. For any questions, issues, or enhancement ideas, please do not hesitate to open an issue at our "),Ie={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},Be=o("GitHub page"),Ce=o("."),Ee=e("p",null,"We're looking forward to hearing from you and appreciate any feedback to improve this solution and help you be more productive.",-1),xe=e("h2",{id:"further-resources",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#further-resources","aria-hidden":"true"},"#"),o(" Further Resources")],-1),Se=e("p",null,"In addition to trying our editor, we invite you to sample further resources related to mainframe hardware, the Z Open Editor, and HLASM.",-1),ze=o("Blog post about "),Te={href:"https://www.ibm.com/cloud/blog/announcements/ibm-wazi-for-red-hat-codeready-workspaces",target:"_blank",rel:"noopener noreferrer"},Oe=o("IBM Wazi for Red Hat CodeReady Workspaces"),Le=o(" by IBM Vice President Danny Mace"),Ae={href:"http://terminaltalk.net/PodcastGenerator/index.php?name=2017-07-22_episode_6_-_brenton_belmar_-_mainframe_millicode_-_7_24_2017.mp3",target:"_blank",rel:"noopener noreferrer"},He=o("Mainframe Milicode Podcast"),Fe=o(" with Brenton Belmar"),De={href:"http://terminaltalk.net/PodcastGenerator/index.php?name=anne_dames_-_z_crypto.mp3",target:"_blank",rel:"noopener noreferrer"},Pe=o("Z Crypto Podcast"),We=o(" with Anne Dames"),Ne={href:"https://ibm.github.io/zopeneditor-about/Docs/tutorial_hlasm.html",target:"_blank",rel:"noopener noreferrer"},Re=o("Assembler Tutorial"),Ge={href:"https://github.com/IBM/zopeneditor-sample",target:"_blank",rel:"noopener noreferrer"},Ve=o("Z Open Editor Assembler Code Samples");function Ze(qe,Ue){const t=s("ExternalLinkIcon");return n(),a(i,null,[g,w,e("p",null,[v,e("a",y,[k,r(t)]),M,e("a",I,[B,r(t)]),C]),e("p",null,[E,e("a",x,[S,r(t)]),z]),T,e("ul",null,[O,L,e("li",null,[e("p",null,[A,e("a",H,[F,r(t)]),D])])]),P,e("p",null,[W,e("a",N,[R,r(t)]),G]),V,Z,q,U,Y,e("p",null,[j,e("a",K,[J,r(t)]),Q]),X,$,e("p",null,[ee,e("a",oe,[te,r(t)]),re,e("a",se,[ne,r(t)]),ae,e("a",ie,[le,r(t)]),de,e("a",he,[ce,r(t)]),ue,e("a",pe,[me,r(t)]),_e]),be,fe,ge,e("p",null,[we,e("a",ve,[ye,r(t)]),ke]),e("p",null,[Me,e("a",Ie,[Be,r(t)]),Ce]),Ee,xe,Se,e("ul",null,[e("li",null,[ze,e("a",Te,[Oe,r(t)]),Le]),e("li",null,[e("a",Ae,[He,r(t)]),Fe]),e("li",null,[e("a",De,[Pe,r(t)]),We]),e("li",null,[e("a",Ne,[Re,r(t)])]),e("li",null,[e("a",Ge,[Ve,r(t)])])])],64)}var Ke=d(f,[["render",Ze]]);export{Ke as default};
+import{r as s,o as n,a,b as e,d as r,F as i,e as o,c as l}from"./app.daa93c96.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";var h="/zopeneditor-about/assets/hlasm-completion.d984eb2b.gif",c="/zopeneditor-about/assets/hlasm-hover.19402729.gif",u="/zopeneditor-about/assets/hlasm-definition.8666e341.gif",p="/zopeneditor-about/assets/hlasm-copy.7b7a1315.gif",m="/zopeneditor-about/assets/hlasm-references.8a795b5e.gif",_="/zopeneditor-about/assets/hlasm-outline.62567372.gif",b="/zopeneditor-about/assets/hlasm-tabs.151c5141.gif";const f={},g=e("h1",{id:"ibm-z-open-editor-a-modern-ide-for-ibm-high-level-assembler",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-a-modern-ide-for-ibm-high-level-assembler","aria-hidden":"true"},"#"),o(" IBM Z Open Editor: A modern IDE for IBM High Level Assembler")],-1),w=e("blockquote",null,[e("p",null,"By Daniel Beall")],-1),v=o("It may seem that an assembler editor simply needs syntax highlighting. After all, don't assembler programmers need only the most spartan of tools? However, after collaborating with IBMer assembler experts Brenton Belmar, a Senior Technical Staff Member of the IBM zMilicode team, Mike Fulton, an IBM Distinguished Engineer and "),y={href:"https://makingdeveloperslivesbetter.wordpress.com/2019/09/09/ibm-z-open-automation-utilities/",target:"_blank",rel:"noopener noreferrer"},k=o("IBM Z Open Automation Utilities"),M=o(" creator, and Walter Church of the IBM z/VM team, this sentiment could not be proven more wrong. We found that assembler deserves, just like COBOL and PL/I (two languages our IBM Z Open Editor also supports), much more attention. The IBM Z Open Editor adds, with version 1.0 available on June 12th, 2020, a new language server for IBM High Level Assembler (HLASM), bringing support for developers who want to use Visual Studio Code or "),I={href:"https://www.ibm.com/products/wazi-for-red-hat-codeready-workspaces",target:"_blank",rel:"noopener noreferrer"},B=o("Red Hat CodeReady Workspaces"),C=o(" to develop and maintain their applications."),E=o("Before we dive into the specifics of our assembler support, you might be wondering what exactly language servers and the Z Open Editor are. "),x={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},S=o("The Z Open Editor"),z=o(' is an extension for Visual Studio Code that provides language support for IBM Enterprise COBOL and PL/I. The language server is what "powers" our tooling for languages like COBOL, PL/I, and now HLASM. Language servers are implementations of language server protocol which is an initiative to standardize communication between editors and programming language tooling.'),T=e("p",null,"The process of building a language server for HLASM and adding it to our extension was not trivial, and we could not have done it without listening to users. From Brenton, Mike, and Walter, we discovered several important points about assembler:",-1),O=e("li",null,[e("p",null,"HLASM has very advanced features compared to traditional assembly languages such as macros, copybooks, and conditional assembler.")],-1),L=e("li",null,[e("p",null,"HLASM programs can be very large. We found assembler programs with upwards of thirty thousand lines of code and of symbols. Navigating and exploring such large programs requires the ability to have indexes in the form of outline views and cross-refencing support in the editor that is language aware and goes beyond simple search.")],-1),A=o("z/Architecture is a CISC, or complex instruction set computer-architecture, with a myriad of instructions. In addition to bread-and-butter instructions, the latest mainframes support state-of-the-art "),H={href:"https://www.ibm.com/support/pages/sites/default/files/support/swg/swgtech.nsf/0/7df1aa86f5dbfd3085257ac0004ef2e6/%24FILE/Transactional_Execution_Facility.pdf",target:"_blank",rel:"noopener noreferrer"},F=o("hardware transactional memory"),D=o(", cryptographic, and SIMD instructions. The programmer must be able tohave code completion for instructions as well as inspect them."),P=l('
      It's clear the collaborative process helped us keep the uniqueness of assembler in mind. While designing the outline view, we experimented with including every symbol within a program. However, after better learning our user's needs, we found that it is better to simply have only CSECTs, DSECTs, and macros in the outline view. Often, if every symbol were to be included, the outline view would become extremely cluttered. The outline view is not the only feature where we've kept assembler's distinctiveness firmly in mind. In our code completion, we include reference information about assembler instructions. And, last but not least, we have included configurable vertical bars and tab stops to help users easily 'eyeball' sequence numbers and continuation line indicators. We feel these features will help assembler programmers, both veterans and novices alike, have a better experience working with language in our editor.
       Editor Features
      Let me walk you through some of the capabilities we added and how we think they can be useful for assembler developers.
      Code Completion: When typing an instruction or operand, the editor will suggest instructions or symbol names. Since HLASM has over a thousand instructions, we found this to be very useful for quickly searching for relevant instructions.
      COMPLETION GIF
      Hover: Never worry about having to scroll to find the contents of a symbol again. To preview the contents of an operand symbol, simply move your mouse cursor over the symbol.
      HOVER GIF
      Go to Definition: To go to where a symbol is defined, simply right click an operand symbol, and click 'Go to Definition.' This is very convenient for large assembler programs. Having to scroll through a program or press Ctrl +F (Windows) or Cmd+F (Mac) to search through every use of a symbol is very tedious in comparison.
      GO TO DEFINITION GIF
      ',9),W=o("Copybook Resolution: To preview the contents of a copybook, move your mouse cursor over the copybook name in a COPY statement. You can also open the copybook in a separate editor by pressing Ctrl+Click (Windows) or Cmd+Click (Mac). To use this feature "),N={href:"https://ibm.github.io/zopeneditor-about/Docs/setting_propertygroup.html",target:"_blank",rel:"noopener noreferrer"},R=o("property groups"),G=o(" will have to be set."),V=e("p",null,[e("img",{src:p,alt:"COPYBOOK GIF"})],-1),Z=e("p",null,"Peek References: A results references view is displayed underneath symbols. Click any result to go to that location within a file.",-1),q=e("p",null,[e("img",{src:m,alt:"HLASM PEEK REFERENCES GIF"})],-1),U=e("p",null,"Outline View: Explore and navigate assembler code. Relevant macros, CSECTs, and DSECTs are shown in the outline view.",-1),Y=e("p",null,[e("img",{src:_,alt:"HLASM OUTLINE GIF"})],-1),j=o("Configurable Vertical Rulers and Tabstops: Easily navigate within a line. Press Tab to move forward and Shift+Tab to move backwards. Vertical rulers are included by default. Please see our "),K={href:"https://ibm.github.io/zopeneditor-about/Docs/setting_tabstops.html",target:"_blank",rel:"noopener noreferrer"},J=o("documentation"),Q=o(" to adjust vertical rulers and tabstops from defaults."),X=e("p",null,[e("img",{src:b,alt:"HLASM RULERS AND TABSTOPS GIF"})],-1),$=e("p",null,[e("strong",null,"Excited to try the Z Open Editor with HLASM support? Here's how")],-1),ee=o("First, find out more about our editor at our "),oe={href:"https://ibm.github.io/zopeneditor-about/",target:"_blank",rel:"noopener noreferrer"},te=o("About Page"),re=o(", and then see a full list of features on our "),se={href:"https://ibm.github.io/zopeneditor-about/Docs/introduction.html",target:"_blank",rel:"noopener noreferrer"},ne=o("Documentation Page"),ae=o(". Next, please ensure "),ie={href:"https://ibm.github.io/zopeneditor-about/Docs/getting_started.html#prerequisites",target:"_blank",rel:"noopener noreferrer"},le=o("prerequisites"),de=o(" for our editor are installed. Then, download the extension through the "),he={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},ce=o("Visual Studio Code Marketplace"),ue=o(". Once the extension is installed, open an assembler file of your choice, or one of our "),pe={href:"https://github.com/IBM/zopeneditor-sample",target:"_blank",rel:"noopener noreferrer"},me=o("samples"),_e=o(". The editor should offer syntax highlighting and the features described above."),be=e("h2",{id:"we-would-love-to-hear-from-you",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#we-would-love-to-hear-from-you","aria-hidden":"true"},"#"),o(" We would love to hear from you")],-1),fe=e("p",null,"We're incredibly thankful for having the opportunity to work with assembler experts such as Brenton, Walter, and Mike. But, at the same time, we want to better meet the needs of users external to IBM. We greatly welcome any feedback about our editor and how you and your organization are using assembler.",-1),ge=e("p",null,"Having said that, we've created two ways for you to easily provide your comments:",-1),we=o("1. Take our "),ve={href:"http://ibm.biz/HLASMsurvey",target:"_blank",rel:"noopener noreferrer"},ye=o("survey"),ke=o(" about HLASM editors and tooling."),Me=o("2. For any questions, issues, or enhancement ideas, please do not hesitate to open an issue at our "),Ie={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},Be=o("GitHub page"),Ce=o("."),Ee=e("p",null,"We're looking forward to hearing from you and appreciate any feedback to improve this solution and help you be more productive.",-1),xe=e("h2",{id:"further-resources",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#further-resources","aria-hidden":"true"},"#"),o(" Further Resources")],-1),Se=e("p",null,"In addition to trying our editor, we invite you to sample further resources related to mainframe hardware, the Z Open Editor, and HLASM.",-1),ze=o("Blog post about "),Te={href:"https://www.ibm.com/cloud/blog/announcements/ibm-wazi-for-red-hat-codeready-workspaces",target:"_blank",rel:"noopener noreferrer"},Oe=o("IBM Wazi for Red Hat CodeReady Workspaces"),Le=o(" by IBM Vice President Danny Mace"),Ae={href:"http://terminaltalk.net/PodcastGenerator/index.php?name=2017-07-22_episode_6_-_brenton_belmar_-_mainframe_millicode_-_7_24_2017.mp3",target:"_blank",rel:"noopener noreferrer"},He=o("Mainframe Milicode Podcast"),Fe=o(" with Brenton Belmar"),De={href:"http://terminaltalk.net/PodcastGenerator/index.php?name=anne_dames_-_z_crypto.mp3",target:"_blank",rel:"noopener noreferrer"},Pe=o("Z Crypto Podcast"),We=o(" with Anne Dames"),Ne={href:"https://ibm.github.io/zopeneditor-about/Docs/tutorial_hlasm.html",target:"_blank",rel:"noopener noreferrer"},Re=o("Assembler Tutorial"),Ge={href:"https://github.com/IBM/zopeneditor-sample",target:"_blank",rel:"noopener noreferrer"},Ve=o("Z Open Editor Assembler Code Samples");function Ze(qe,Ue){const t=s("ExternalLinkIcon");return n(),a(i,null,[g,w,e("p",null,[v,e("a",y,[k,r(t)]),M,e("a",I,[B,r(t)]),C]),e("p",null,[E,e("a",x,[S,r(t)]),z]),T,e("ul",null,[O,L,e("li",null,[e("p",null,[A,e("a",H,[F,r(t)]),D])])]),P,e("p",null,[W,e("a",N,[R,r(t)]),G]),V,Z,q,U,Y,e("p",null,[j,e("a",K,[J,r(t)]),Q]),X,$,e("p",null,[ee,e("a",oe,[te,r(t)]),re,e("a",se,[ne,r(t)]),ae,e("a",ie,[le,r(t)]),de,e("a",he,[ce,r(t)]),ue,e("a",pe,[me,r(t)]),_e]),be,fe,ge,e("p",null,[we,e("a",ve,[ye,r(t)]),ke]),e("p",null,[Me,e("a",Ie,[Be,r(t)]),Ce]),Ee,xe,Se,e("ul",null,[e("li",null,[ze,e("a",Te,[Oe,r(t)]),Le]),e("li",null,[e("a",Ae,[He,r(t)]),Fe]),e("li",null,[e("a",De,[Pe,r(t)]),We]),e("li",null,[e("a",Ne,[Re,r(t)])]),e("li",null,[e("a",Ge,[Ve,r(t)])])])],64)}var Ke=d(f,[["render",Ze]]);export{Ke as default};
diff --git a/assets/ibm-wazi-development-client-introduction-blog.html.ae1364bf.js b/assets/ibm-wazi-development-client-introduction-blog.html.71dcd92b.js
similarity index 99%
rename from assets/ibm-wazi-development-client-introduction-blog.html.ae1364bf.js
rename to assets/ibm-wazi-development-client-introduction-blog.html.71dcd92b.js
index fb6cfeba0..fdec07988 100644
--- a/assets/ibm-wazi-development-client-introduction-blog.html.ae1364bf.js
+++ b/assets/ibm-wazi-development-client-introduction-blog.html.71dcd92b.js
@@ -1 +1 @@
-import{r,o as a,a as l,b as e,d as o,w as i,F as d,e as t,c}from"./app.f6cb3ed9.js";import{_ as p}from"./plugin-vue_export-helper.21dcd24c.js";var h="/zopeneditor-about/assets/wazi-development-client-arch.c0e1097d.png",m="/zopeneditor-about/assets/wazi-development-client-dashboard.c803a64e.png",u="/zopeneditor-about/assets/wazi-development-client-ibm-z-open-editor-cobol.d7d448eb.png",_="/zopeneditor-about/assets/wazi-development-client-ibm-z-open-editor-pl1.e5d0f743.png",f="/zopeneditor-about/assets/wazi-development-client-ibm-z-open-editor-assembler.096864fe.png",g="/zopeneditor-about/assets/wazi-development-client-ibm-user-build.8353f08e.png",v="/zopeneditor-about/assets/wazi-development-client-zowe-explorer.89a406ac.png",w="/zopeneditor-about/assets/wazi-development-client-zowe-cli.e82a9082.png",b="/zopeneditor-about/assets/wazi-development-client-ibm-rse-api.eae5c176.png";const I={},z=e("h1",{id:"kubernetes-native-integrated-z-developer-environment-with-ibm-wazi-for-red-hat-codeready-workspaces-development-client",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#kubernetes-native-integrated-z-developer-environment-with-ibm-wazi-for-red-hat-codeready-workspaces-development-client","aria-hidden":"true"},"#"),t(" Kubernetes-Native Integrated Z Developer Environment with IBM Wazi for Red Hat CodeReady Workspaces Development Client")],-1),B=e("blockquote",null,[e("p",null,"By Prasang A Prajapati")],-1),k=e("p",null,'Have you ever experienced problems in setting up a development environment? Also, have you ever heard this excuse when reporting a bug to a colleague? "It works on my machine!"',-1),C=e("p",null,"You are joining a new development team or project and you have spent the first couple of days or longer just with installing the right tools, getting access to the right system and configuring your development profiles. Similarly, when starting a new project, a large portion of time and energy is spent on setting up the development environment. Think about how inefficient it could be if this type of set up routine is repeated for every new team member or new project every time.",-1),y=t("To address this problem, there is an amazing tool called "),M={href:"https://www.ibm.com/products/wazi-for-red-hat-codeready-workspaces",target:"_blank",rel:"noopener noreferrer"},S=t("IBM\xAE Wazi for Red Hat\xAE CodeReady Workspaces Development Client"),D=t(" (IBM Wazi Development Client). IBM Wazi Development Client is built on the Red Hat CodeReady Workspaces project. IBM Wazi Development Client uses Kubernetes and containers to provide any member of the development or IT team with a consistent, secure, and zero-configuration development environment for the IBM Z\xAE Platform. The user experience is as fast and familiar as an integrated development environment (IDE) on their laptop."),x=t("IBM Wazi Development Client provides a modern experience for mainframe software developers working with z/OS\xAE applications in the cloud by leveraging the available Visual Studio Code (VS Code) extensions "),E={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},W=t("IBM Z Open Editor"),R=t(", "),Z={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=build-running-user",target:"_blank",rel:"noopener noreferrer"},L=t("IBM User Build"),O=t(" and "),P={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},F=t("Zowe\u2122 Explorer"),A=t(", as well as the command-line tools "),N={href:"https://docs.zowe.org/stable/user-guide/cli-usingcli.html",target:"_blank",rel:"noopener noreferrer"},V=t("Zowe CLI"),j=t(" and "),U=t("IBM RSE API Plug-in for Zowe CLI"),T=t(". Developers can use these Visual Studio Code extensions and command line tools on their local machine with the "),H={href:"https://code.visualstudio.com/",target:"_blank",rel:"noopener noreferrer"},q=t("Visual Studio Code"),J=t(" desktop IDE. Now, IBM Wazi Development Client makes this experience also available in the cloud. Powered by the open-source projects Zowe and Red Hat CodeReady Workspaces, IBM Wazi Development Client offers an easy, streamlined on-boarding process to get new mainframe developers using the tools they need. Using container technology and stacks, IBM Wazi Development Client brings the necessary technology to the task at hand."),K=t("Mainframe developers can now have rich language support for COBOL, PL/I, Assembler and JCL using "),G={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},Y=t("IBM Z Open Editor"),Q=t(" as well as connectivity to Z host using "),X={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},$=t("Zowe Explorer"),ee=t(", run user builds using "),te={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=build-running-user",target:"_blank",rel:"noopener noreferrer"},oe=t("IBM User Build"),ne=t(", and interact with the "),se=t("IBM Remote System Explorer API"),ie=t(", all in one Mainframe Development package using the "),re={href:"https://github.com/IBM/wazi-codeready-workspaces",target:"_blank",rel:"noopener noreferrer"},ae=t("IBM Wazi Development Client stack"),le=t(" with custom plugin and devfile registry support."),de=c('
      wazi-development-client
      Fig 1: IBM Wazi for Red Hat CodeReady Workspaces Development Client controller architecture
      The above figure explains workspaces controller architecture for the IBM Wazi Development Client. OpenShift\xAE leverages the Kubernetes concept of a pod, which is one or more containers deployed together on one host, and the smallest compute unit that can be defined, deployed, and managed. In the IBM Wazi Development Client, when the user creates a workspace using Wazi Development Client Stack, it creates a workspace with deployed user runtime as well as a plugin sidecar container.
       IBM Wazi Development Client Dashboard
      wazi-development-client-dashboard
      Fig 2: Screen capture of IBM Wazi Development Client Dashboard
       Features
      Here are the main features that IBM Wazi Development Client offers.
      ',8),ce={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},pe=t("IBM Z Open Editor"),he=t("IBM Z Open Editor is a free Visual Studio Code extension that provides a modern editing experience for IBM Z Enterprise languages. IBM Z Open Editor gives developers the freedom to code in COBOL, PL/I and Assembler using the same editor they use for other languages such as Java\u2122 and JavaScript. "),me={href:"https://ibm.github.io/zopeneditor-about/",target:"_blank",rel:"noopener noreferrer"},ue=t("Learn more"),_e=e("p",null,[e("img",{src:u,alt:"ibm-z-open-editor-cobol"}),e("em",null,"Fig 3: Editing experience of COBOL files using IBM Z Open Editor in IBM Wazi Development Client")],-1),fe=e("p",null,[e("img",{src:_,alt:"ibm-z-open-editor-pl1"}),e("em",null,"Fig 4: Editing experience of PL/I files using IBM Z Open Editor in IBM Wazi Development Client")],-1),ge=e("p",null,[e("img",{src:f,alt:"ibm-z-open-editor-assembler"}),e("em",null,"Fig 5: Editing experience of Assembler files using IBM Z Open Editor in IBM Wazi Development Client")],-1),ve={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=build-running-user",target:"_blank",rel:"noopener noreferrer"},we=t("IBM User Build"),be=t("The IBM User Build VS Code extension helps COBOL developers leverage the IBM Dependency Based Build (DBB) toolkit right from their local VS Code or IBM Wazi Development Client enviroment. "),Ie={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=build-running-user",target:"_blank",rel:"noopener noreferrer"},ze=t("Learn more"),Be=e("p",null,[e("img",{src:g,alt:"ibm-user-build"}),e("em",null,"Fig 6: User Build using IBM User Build in IBM Wazi Development Client")],-1),ke={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},Ce=t("Zowe Explorer"),ye=t("Zowe Explorer is a free Visual Studio Code extension that lets you interact with data sets, USS files and jobs that are stored on IBM z/OS mainframes. You can explore data sets, USS files and jobs to view their contents, make changes, and upload the changes to the mainframe. Interacting with data sets, USS files and jobs from VS Code can be more convenient than using command-line interfaces or 3270 emulators. "),Me={href:"https://docs.zowe.org/stable/user-guide/ze-install.html#software-requirements",target:"_blank",rel:"noopener noreferrer"},Se=t("Learn more"),De=e("p",null,[e("img",{src:v,alt:"zowe-explorer"}),e("em",null,"Fig 7: Interacting with data sets, USS files and jobs that are stored on IBM z/OS mainframes using Zowe Explorer in IBM Wazi Development Client")],-1),xe={href:"https://docs.zowe.org/stable/user-guide/cli-usingcli.html",target:"_blank",rel:"noopener noreferrer"},Ee=t("Zowe CLI"),We=t("Zowe CLI is a command-line interface that lets you interact with the mainframe in a familiar, off-platform format. Zowe CLI helps to increase overall productivity, reduce the learning curve for developing mainframe applications, and exploit the ease-of-use of off-platform tools. Zowe CLI lets you use common tools such as Integrated Development Environments (IDEs), shell commands, bash scripts, and build tools for mainframe development. Through its ecosystem of plug-ins, you can automate actions on systems such as IBM Db2\xAE, IBM CICS\xAE, and more. It provides a set of utilities and services for users who want to become efficient in supporting and building z/OS applications quickly. "),Re={href:"https://docs.zowe.org/stable/user-guide/cli-usingcli.html",target:"_blank",rel:"noopener noreferrer"},Ze=t("Learn more"),Le=e("p",null,[e("img",{src:w,alt:"zowe-cli"}),e("em",null,"Fig 8: Running Zowe commands to create, delete, or update profiles using Zowe CLI in IBM Wazi Development Client")],-1),Oe=t("IBM RSE API Plug-in for Zowe CLI"),Pe=t("IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in) extends Zowe CLI to let you interact with z/OS resources. The RSE CLI plug-in interacts with z/OS by using IBM Remote System Explorer API (RSE API) instead of using z/OSMF. The RSE API is a collection of REST APIs that allow a client to work with various components on the z/OS host system, including MVS\u2122 data sets, z/OS UNIX files and commands, JES jobs, and more. The overall solution results in a complete set of operations that allows you to do everything with RSE API that you could do with z/OSMF. It is therefore a great alternative if you have already used the Remote System Explorer with other IBM offerings such as IBM Developer for z/OS or IBM Explorer for z/OS. "),Fe=t("Learn more"),Ae=e("p",null,[e("img",{src:b,alt:"ibm-rse-api"}),e("em",null,"Fig 9: Create, delete or update RSE profiles using the RSE CLI plug-in in IBM Wazi Development Client")],-1),Ne=e("h2",{id:"documentation",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#documentation","aria-hidden":"true"},"#"),t(" Documentation")],-1),Ve=t("For more information or to learn more about IBM Wazi for Red Hat CodeReady Workspaces Development Client, see "),je={href:"https://www.ibm.com/docs/en/wdfrhcw/1.4.0",target:"_blank",rel:"noopener noreferrer"},Ue=t("IBM Wazi for Red Hat CodeReady Workspaces Development Client Documentation"),Te=t("."),He=e("strong",null,"Note:",-1),qe=t(" IBM Wazi Development Client is built on top of "),Je={href:"https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces",target:"_blank",rel:"noopener noreferrer"},Ke=t("Red Hat CodeReady Workspaces"),Ge=t(". For more information on what else can be done with workspaces, see the "),Ye={href:"https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/2.1/html/end-user_guide/index",target:"_blank",rel:"noopener noreferrer"},Qe=t("End-User Guide"),Xe=t("."),$e=e("h2",{id:"questions-or-feedback",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#questions-or-feedback","aria-hidden":"true"},"#"),t(" Questions or feedback")],-1),et=t("We would love to hear what you think of this solution. For any questions, issues, or enhancement ideas, you can open an issue in the "),tt={href:"https://github.com/IBM/wazi-codeready-workspaces",target:"_blank",rel:"noopener noreferrer"},ot=t("Wazi Codeready WorkSpaces Github repository"),nt=t("."),st=e("p",null,"We are always looking for ways to improve.",-1);function it(rt,at){const n=r("ExternalLinkIcon"),s=r("RouterLink");return a(),l(d,null,[z,B,k,C,e("p",null,[y,e("a",M,[S,o(n)]),D]),e("p",null,[x,e("a",E,[W,o(n)]),R,e("a",Z,[L,o(n)]),O,e("a",P,[F,o(n)]),A,e("a",N,[V,o(n)]),j,o(s,{to:"/Docs/setup_integration.html"},{default:i(()=>[U]),_:1}),T,e("a",H,[q,o(n)]),J]),e("p",null,[K,e("a",G,[Y,o(n)]),Q,e("a",X,[$,o(n)]),ee,e("a",te,[oe,o(n)]),ne,o(s,{to:"/Docs/setup_integration.html"},{default:i(()=>[se]),_:1}),ie,e("a",re,[ae,o(n)]),le]),de,e("ol",null,[e("li",null,[e("p",null,[e("a",ce,[pe,o(n)])]),e("p",null,[he,e("a",me,[ue,o(n)])]),_e,fe,ge]),e("li",null,[e("p",null,[e("a",ve,[we,o(n)])]),e("p",null,[be,e("a",Ie,[ze,o(n)])]),Be]),e("li",null,[e("p",null,[e("a",ke,[Ce,o(n)])]),e("p",null,[ye,e("a",Me,[Se,o(n)])]),De]),e("li",null,[e("p",null,[e("a",xe,[Ee,o(n)])]),e("p",null,[We,e("a",Re,[Ze,o(n)])]),Le]),e("li",null,[e("p",null,[o(s,{to:"/Docs/setup_integration.html"},{default:i(()=>[Oe]),_:1})]),e("p",null,[Pe,o(s,{to:"/Docs/setup_integration.html"},{default:i(()=>[Fe]),_:1})]),Ae])]),Ne,e("p",null,[Ve,e("a",je,[Ue,o(n)]),Te]),e("p",null,[He,qe,e("a",Je,[Ke,o(n)]),Ge,e("a",Ye,[Qe,o(n)]),Xe]),$e,e("p",null,[et,e("a",tt,[ot,o(n)]),nt]),st],64)}var ct=p(I,[["render",it]]);export{ct as default};
+import{r,o as a,a as l,b as e,d as o,w as i,F as d,e as t,c}from"./app.daa93c96.js";import{_ as p}from"./plugin-vue_export-helper.21dcd24c.js";var h="/zopeneditor-about/assets/wazi-development-client-arch.c0e1097d.png",m="/zopeneditor-about/assets/wazi-development-client-dashboard.c803a64e.png",u="/zopeneditor-about/assets/wazi-development-client-ibm-z-open-editor-cobol.d7d448eb.png",_="/zopeneditor-about/assets/wazi-development-client-ibm-z-open-editor-pl1.e5d0f743.png",f="/zopeneditor-about/assets/wazi-development-client-ibm-z-open-editor-assembler.096864fe.png",g="/zopeneditor-about/assets/wazi-development-client-ibm-user-build.8353f08e.png",v="/zopeneditor-about/assets/wazi-development-client-zowe-explorer.89a406ac.png",w="/zopeneditor-about/assets/wazi-development-client-zowe-cli.e82a9082.png",b="/zopeneditor-about/assets/wazi-development-client-ibm-rse-api.eae5c176.png";const I={},z=e("h1",{id:"kubernetes-native-integrated-z-developer-environment-with-ibm-wazi-for-red-hat-codeready-workspaces-development-client",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#kubernetes-native-integrated-z-developer-environment-with-ibm-wazi-for-red-hat-codeready-workspaces-development-client","aria-hidden":"true"},"#"),t(" Kubernetes-Native Integrated Z Developer Environment with IBM Wazi for Red Hat CodeReady Workspaces Development Client")],-1),B=e("blockquote",null,[e("p",null,"By Prasang A Prajapati")],-1),k=e("p",null,'Have you ever experienced problems in setting up a development environment? Also, have you ever heard this excuse when reporting a bug to a colleague? "It works on my machine!"',-1),C=e("p",null,"You are joining a new development team or project and you have spent the first couple of days or longer just with installing the right tools, getting access to the right system and configuring your development profiles. Similarly, when starting a new project, a large portion of time and energy is spent on setting up the development environment. Think about how inefficient it could be if this type of set up routine is repeated for every new team member or new project every time.",-1),y=t("To address this problem, there is an amazing tool called "),M={href:"https://www.ibm.com/products/wazi-for-red-hat-codeready-workspaces",target:"_blank",rel:"noopener noreferrer"},S=t("IBM\xAE Wazi for Red Hat\xAE CodeReady Workspaces Development Client"),D=t(" (IBM Wazi Development Client). IBM Wazi Development Client is built on the Red Hat CodeReady Workspaces project. IBM Wazi Development Client uses Kubernetes and containers to provide any member of the development or IT team with a consistent, secure, and zero-configuration development environment for the IBM Z\xAE Platform. The user experience is as fast and familiar as an integrated development environment (IDE) on their laptop."),x=t("IBM Wazi Development Client provides a modern experience for mainframe software developers working with z/OS\xAE applications in the cloud by leveraging the available Visual Studio Code (VS Code) extensions "),E={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},W=t("IBM Z Open Editor"),R=t(", "),Z={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=build-running-user",target:"_blank",rel:"noopener noreferrer"},L=t("IBM User Build"),O=t(" and "),P={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},F=t("Zowe\u2122 Explorer"),A=t(", as well as the command-line tools "),N={href:"https://docs.zowe.org/stable/user-guide/cli-usingcli.html",target:"_blank",rel:"noopener noreferrer"},V=t("Zowe CLI"),j=t(" and "),U=t("IBM RSE API Plug-in for Zowe CLI"),T=t(". Developers can use these Visual Studio Code extensions and command line tools on their local machine with the "),H={href:"https://code.visualstudio.com/",target:"_blank",rel:"noopener noreferrer"},q=t("Visual Studio Code"),J=t(" desktop IDE. Now, IBM Wazi Development Client makes this experience also available in the cloud. Powered by the open-source projects Zowe and Red Hat CodeReady Workspaces, IBM Wazi Development Client offers an easy, streamlined on-boarding process to get new mainframe developers using the tools they need. Using container technology and stacks, IBM Wazi Development Client brings the necessary technology to the task at hand."),K=t("Mainframe developers can now have rich language support for COBOL, PL/I, Assembler and JCL using "),G={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},Y=t("IBM Z Open Editor"),Q=t(" as well as connectivity to Z host using "),X={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},$=t("Zowe Explorer"),ee=t(", run user builds using "),te={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=build-running-user",target:"_blank",rel:"noopener noreferrer"},oe=t("IBM User Build"),ne=t(", and interact with the "),se=t("IBM Remote System Explorer API"),ie=t(", all in one Mainframe Development package using the "),re={href:"https://github.com/IBM/wazi-codeready-workspaces",target:"_blank",rel:"noopener noreferrer"},ae=t("IBM Wazi Development Client stack"),le=t(" with custom plugin and devfile registry support."),de=c('
      wazi-development-client
      Fig 1: IBM Wazi for Red Hat CodeReady Workspaces Development Client controller architecture
      The above figure explains workspaces controller architecture for the IBM Wazi Development Client. OpenShift\xAE leverages the Kubernetes concept of a pod, which is one or more containers deployed together on one host, and the smallest compute unit that can be defined, deployed, and managed. In the IBM Wazi Development Client, when the user creates a workspace using Wazi Development Client Stack, it creates a workspace with deployed user runtime as well as a plugin sidecar container.
       IBM Wazi Development Client Dashboard
      wazi-development-client-dashboard
      Fig 2: Screen capture of IBM Wazi Development Client Dashboard
       Features
      Here are the main features that IBM Wazi Development Client offers.
      ',8),ce={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},pe=t("IBM Z Open Editor"),he=t("IBM Z Open Editor is a free Visual Studio Code extension that provides a modern editing experience for IBM Z Enterprise languages. IBM Z Open Editor gives developers the freedom to code in COBOL, PL/I and Assembler using the same editor they use for other languages such as Java\u2122 and JavaScript. "),me={href:"https://ibm.github.io/zopeneditor-about/",target:"_blank",rel:"noopener noreferrer"},ue=t("Learn more"),_e=e("p",null,[e("img",{src:u,alt:"ibm-z-open-editor-cobol"}),e("em",null,"Fig 3: Editing experience of COBOL files using IBM Z Open Editor in IBM Wazi Development Client")],-1),fe=e("p",null,[e("img",{src:_,alt:"ibm-z-open-editor-pl1"}),e("em",null,"Fig 4: Editing experience of PL/I files using IBM Z Open Editor in IBM Wazi Development Client")],-1),ge=e("p",null,[e("img",{src:f,alt:"ibm-z-open-editor-assembler"}),e("em",null,"Fig 5: Editing experience of Assembler files using IBM Z Open Editor in IBM Wazi Development Client")],-1),ve={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=build-running-user",target:"_blank",rel:"noopener noreferrer"},we=t("IBM User Build"),be=t("The IBM User Build VS Code extension helps COBOL developers leverage the IBM Dependency Based Build (DBB) toolkit right from their local VS Code or IBM Wazi Development Client enviroment. "),Ie={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=build-running-user",target:"_blank",rel:"noopener noreferrer"},ze=t("Learn more"),Be=e("p",null,[e("img",{src:g,alt:"ibm-user-build"}),e("em",null,"Fig 6: User Build using IBM User Build in IBM Wazi Development Client")],-1),ke={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},Ce=t("Zowe Explorer"),ye=t("Zowe Explorer is a free Visual Studio Code extension that lets you interact with data sets, USS files and jobs that are stored on IBM z/OS mainframes. You can explore data sets, USS files and jobs to view their contents, make changes, and upload the changes to the mainframe. Interacting with data sets, USS files and jobs from VS Code can be more convenient than using command-line interfaces or 3270 emulators. "),Me={href:"https://docs.zowe.org/stable/user-guide/ze-install.html#software-requirements",target:"_blank",rel:"noopener noreferrer"},Se=t("Learn more"),De=e("p",null,[e("img",{src:v,alt:"zowe-explorer"}),e("em",null,"Fig 7: Interacting with data sets, USS files and jobs that are stored on IBM z/OS mainframes using Zowe Explorer in IBM Wazi Development Client")],-1),xe={href:"https://docs.zowe.org/stable/user-guide/cli-usingcli.html",target:"_blank",rel:"noopener noreferrer"},Ee=t("Zowe CLI"),We=t("Zowe CLI is a command-line interface that lets you interact with the mainframe in a familiar, off-platform format. Zowe CLI helps to increase overall productivity, reduce the learning curve for developing mainframe applications, and exploit the ease-of-use of off-platform tools. Zowe CLI lets you use common tools such as Integrated Development Environments (IDEs), shell commands, bash scripts, and build tools for mainframe development. Through its ecosystem of plug-ins, you can automate actions on systems such as IBM Db2\xAE, IBM CICS\xAE, and more. It provides a set of utilities and services for users who want to become efficient in supporting and building z/OS applications quickly. "),Re={href:"https://docs.zowe.org/stable/user-guide/cli-usingcli.html",target:"_blank",rel:"noopener noreferrer"},Ze=t("Learn more"),Le=e("p",null,[e("img",{src:w,alt:"zowe-cli"}),e("em",null,"Fig 8: Running Zowe commands to create, delete, or update profiles using Zowe CLI in IBM Wazi Development Client")],-1),Oe=t("IBM RSE API Plug-in for Zowe CLI"),Pe=t("IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in) extends Zowe CLI to let you interact with z/OS resources. The RSE CLI plug-in interacts with z/OS by using IBM Remote System Explorer API (RSE API) instead of using z/OSMF. The RSE API is a collection of REST APIs that allow a client to work with various components on the z/OS host system, including MVS\u2122 data sets, z/OS UNIX files and commands, JES jobs, and more. The overall solution results in a complete set of operations that allows you to do everything with RSE API that you could do with z/OSMF. It is therefore a great alternative if you have already used the Remote System Explorer with other IBM offerings such as IBM Developer for z/OS or IBM Explorer for z/OS. "),Fe=t("Learn more"),Ae=e("p",null,[e("img",{src:b,alt:"ibm-rse-api"}),e("em",null,"Fig 9: Create, delete or update RSE profiles using the RSE CLI plug-in in IBM Wazi Development Client")],-1),Ne=e("h2",{id:"documentation",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#documentation","aria-hidden":"true"},"#"),t(" Documentation")],-1),Ve=t("For more information or to learn more about IBM Wazi for Red Hat CodeReady Workspaces Development Client, see "),je={href:"https://www.ibm.com/docs/en/wdfrhcw/1.4.0",target:"_blank",rel:"noopener noreferrer"},Ue=t("IBM Wazi for Red Hat CodeReady Workspaces Development Client Documentation"),Te=t("."),He=e("strong",null,"Note:",-1),qe=t(" IBM Wazi Development Client is built on top of "),Je={href:"https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces",target:"_blank",rel:"noopener noreferrer"},Ke=t("Red Hat CodeReady Workspaces"),Ge=t(". For more information on what else can be done with workspaces, see the "),Ye={href:"https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/2.1/html/end-user_guide/index",target:"_blank",rel:"noopener noreferrer"},Qe=t("End-User Guide"),Xe=t("."),$e=e("h2",{id:"questions-or-feedback",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#questions-or-feedback","aria-hidden":"true"},"#"),t(" Questions or feedback")],-1),et=t("We would love to hear what you think of this solution. For any questions, issues, or enhancement ideas, you can open an issue in the "),tt={href:"https://github.com/IBM/wazi-codeready-workspaces",target:"_blank",rel:"noopener noreferrer"},ot=t("Wazi Codeready WorkSpaces Github repository"),nt=t("."),st=e("p",null,"We are always looking for ways to improve.",-1);function it(rt,at){const n=r("ExternalLinkIcon"),s=r("RouterLink");return a(),l(d,null,[z,B,k,C,e("p",null,[y,e("a",M,[S,o(n)]),D]),e("p",null,[x,e("a",E,[W,o(n)]),R,e("a",Z,[L,o(n)]),O,e("a",P,[F,o(n)]),A,e("a",N,[V,o(n)]),j,o(s,{to:"/Docs/setup_integration.html"},{default:i(()=>[U]),_:1}),T,e("a",H,[q,o(n)]),J]),e("p",null,[K,e("a",G,[Y,o(n)]),Q,e("a",X,[$,o(n)]),ee,e("a",te,[oe,o(n)]),ne,o(s,{to:"/Docs/setup_integration.html"},{default:i(()=>[se]),_:1}),ie,e("a",re,[ae,o(n)]),le]),de,e("ol",null,[e("li",null,[e("p",null,[e("a",ce,[pe,o(n)])]),e("p",null,[he,e("a",me,[ue,o(n)])]),_e,fe,ge]),e("li",null,[e("p",null,[e("a",ve,[we,o(n)])]),e("p",null,[be,e("a",Ie,[ze,o(n)])]),Be]),e("li",null,[e("p",null,[e("a",ke,[Ce,o(n)])]),e("p",null,[ye,e("a",Me,[Se,o(n)])]),De]),e("li",null,[e("p",null,[e("a",xe,[Ee,o(n)])]),e("p",null,[We,e("a",Re,[Ze,o(n)])]),Le]),e("li",null,[e("p",null,[o(s,{to:"/Docs/setup_integration.html"},{default:i(()=>[Oe]),_:1})]),e("p",null,[Pe,o(s,{to:"/Docs/setup_integration.html"},{default:i(()=>[Fe]),_:1})]),Ae])]),Ne,e("p",null,[Ve,e("a",je,[Ue,o(n)]),Te]),e("p",null,[He,qe,e("a",Je,[Ke,o(n)]),Ge,e("a",Ye,[Qe,o(n)]),Xe]),$e,e("p",null,[et,e("a",tt,[ot,o(n)]),nt]),st],64)}var ct=p(I,[["render",it]]);export{ct as default};
diff --git a/assets/in-the-cloud-with-che.html.44ae56df.js b/assets/in-the-cloud-with-che.html.37d18f64.js
similarity index 99%
rename from assets/in-the-cloud-with-che.html.44ae56df.js
rename to assets/in-the-cloud-with-che.html.37d18f64.js
index 5bc74cb67..014ac7c3b 100644
--- a/assets/in-the-cloud-with-che.html.44ae56df.js
+++ b/assets/in-the-cloud-with-che.html.37d18f64.js
@@ -1,4 +1,4 @@
-import{r as i,o as r,a,b as e,d as n,F as l,e as o,c as s}from"./app.f6cb3ed9.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";var h="/zopeneditor-about/assets/ibmzopeneditorinche.13b929bd.png",d="/zopeneditor-about/assets/workspace-using-ibmzstack.75a77fb4.png",p="/zopeneditor-about/assets/wazi-development-client-zowe-explorer.89a406ac.png";const u={},m=e("h1",{id:"ibm-z\xAE-open-editor-in-the-cloud-with-eclipse-che",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z\xAE-open-editor-in-the-cloud-with-eclipse-che","aria-hidden":"true"},"#"),o(" IBM Z\xAE Open Editor in the cloud with Eclipse Che")],-1),f=e("blockquote",null,[e("p",null,[o("by Prasang A. Prajapati, Eric Subah, and Peter Haumer."),e("br"),o(" Last updated: 3 December 2019")])],-1),g={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},_=o("IBM Z Open Editor"),w=o(" is a free Visual Studio Code extension that provides a modern editing experience for IBM Z Enterprise languages. It gives developers the freedom to code in COBOL and PL/I using the same editor they use for other languages such as Java and JavaScript. "),y={href:"https://ibm.github.io/zopeneditor-about/",target:"_blank",rel:"noopener noreferrer"},b=o("Learn more"),v=o("."),k=e("p",null,"However, Visual Studio Code is a rich client editor that needs to be installed and configured by every development team member on their development machines. In addition to installing the editor, enterprise developers also have to get access to source code and other resources residing in SCMs and on z/OS.",-1),O=e("p",null,"What if you could avoid all this and developers could just join a project by getting access and logging on to a website? After logging on, the source code, access to z/OS, and the development environment required for maintaining the project would just be there and developers can just dive in?",-1),C=o("To realize on this vision, there is an excellent open source tool platform called "),S={href:"https://www.eclipse.org/che/",target:"_blank",rel:"noopener noreferrer"},I=o("Eclipse Che"),E=o(". It was built to make Kubernetes development accessible for development teams, providing one-click developer workspaces and eliminating the need for local environment configurations for the entire team. This use case applies not only to Kubernetes development, but by utilizing z/OS connectivity features such as the ones provided by the "),x={href:"https://zowe.org",target:"_blank",rel:"noopener noreferrer"},z=o("Zowe"),T=o(" open source project also fits with the requirements for z/OS Mainframe development projects."),M=o("You can run Eclipse Che in the public cloud, private cloud, or install it on a large list of distributed OS (Ubuntu/Linux/MacOS/Windows). To learn more about Eclipse Che, see "),B={href:"https://www.eclipse.org/che/docs/",target:"_blank",rel:"noopener noreferrer"},j=o("Introduction to Eclipse Che"),L=o(". It is also built for extensibility allowing organizations to create and plug-in additional enhancements or features."),F=o("In the following, we want to show you how easy it is to set up such an Eclipse Che environment in IBM Cloud using OpenShift that is fully integrated with "),W={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},A=o("IBM Z Open Editor"),Z=o(" as well as "),P={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},q=o("Zowe Explorer"),N=o(" in three simple steps. We will provide a sample application that you can use for exploration, but once you have it up and running, you can explore other possibilities for this new kind of development style using your own source code. We would love to hear your feedback and engage into a discussion on how we can make this work for your teams."),D=e("p",null,[e("img",{src:h,alt:"Screen capture for IBM Z Open Editor in Eclipse Che"}),o(" Fig. 1: The user experience of IBM Z Open Editor in Eclipse Che")],-1),U=e("h2",{id:"step-1-getting-started-with-ibm-cloud-and-openshift",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#step-1-getting-started-with-ibm-cloud-and-openshift","aria-hidden":"true"},"#"),o(" Step 1: Getting started with IBM Cloud and OpenShift")],-1),R=o("We recommend exploring Eclipse Che on IBM Cloud utilizing IBM's OpenShift V3.11 offering available there. However, the instruction provided here should also work on any other OpenShift or Kubernetes hosting platforms that can run Eclipse Che. If in fact you have Eclipse Che running somewhere in your organization or a Cloud account of your own, you can directly jump to "),G=e("a",{href:"#step-3:-creating-a-development-workspace-for-z"},"Step 3",-1),V=o(" now. Note that although the cluster and Che environment you are using needs to have at least 3 GB of memory available, the standard Che trial servers at "),Y={href:"https://che.openshift.io",target:"_blank",rel:"noopener noreferrer"},K=o("https://che.openshift.io"),H=o(" do not provide enough resources at the moment unfortunately."),J=e("h3",{id:"introducing-openshift",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#introducing-openshift","aria-hidden":"true"},"#"),o(" Introducing OpenShift")],-1),Q=o("An open source containerized platform developed by "),$={href:"https://www.redhat.com/en",target:"_blank",rel:"noopener noreferrer"},X=o("Red Hat"),ee=o("."),oe=o("It is "),te={href:"https://en.wikipedia.org/wiki/Platform_as_a_service",target:"_blank",rel:"noopener noreferrer"},ne=o("platform as a service (PaaS)"),se=o(". PaaS is a category of cloud computing services which provides an environment for customers to develop, run and manage their applications without the complex infrastructure of building and managing applications."),ie=e("li",null,"OpenShift container platform is a service which can be deployed on public, private or hybrid cloud which will help customers to deploy applications using docker containers.",-1),re=o("It is built on top of "),ae={href:"https://kubernetes.io/",target:"_blank",rel:"noopener noreferrer"},le=o("Kubernetes"),ce=o(" and provides you tools like OpenShift web console or OpenShift CLI to manage projects and deployments."),he=e("li",null,"It simplifies development and operations for cloud native applications.",-1),de=o("It provides a web console to access and manage all the projects using built-in catalogs as well as OpenShift Container Platform templates. To learn more about OpenShift Web Console, you can view the "),pe={href:"https://docs.openshift.com/container-platform/3.7/getting_started/developers_console.html",target:"_blank",rel:"noopener noreferrer"},ue=o("OpenShift web console Walkthrough documentation"),me=o("."),fe=e("h3",{id:"creating-an-openshift-cluster-on-ibm-cloud",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#creating-an-openshift-cluster-on-ibm-cloud","aria-hidden":"true"},"#"),o(" Creating an OpenShift cluster on IBM Cloud")],-1),ge=e("p",null,"Prerequisite: To run Eclipse Che on IBM Cloud using OpenShift, you need have a full IBM Cloud account because the IBM Cloud trial accounts do not have the option to create OpenShift clusters at the moment.",-1),_e=e("p",null,"After you have a full IBM Cloud account, follow the steps below to create an OpenShift cluster:",-1),we=o("Log in to your "),ye={href:"https://cloud.ibm.com/",target:"_blank",rel:"noopener noreferrer"},be=o("IBM Cloud account"),ve=o("."),ke=o("From the Services Catalog, select "),Oe={href:"https://cloud.ibm.com/kubernetes/catalog/openshiftcluster",target:"_blank",rel:"noopener noreferrer"},Ce=o("Red Hat OpenShift Cluster"),Se=o(". Then, click "),Ie=e("strong",null,"Create",-1),Ee=o(" in the summary page."),xe=s("
    • In the Create a new OpenShift cluster page, choose your cluster setup details and name:
      1. For the Location, select the Single zone, which should be enough for evaluation. Set the Geography and then select any of the Worker zones.
      2. Enter a unique name for your cluster and select the resource group that you want to assign to your cluster.
      3. For Default worker pool, choose an available flavor for your worker nodes. Red Hat OpenShift on IBM Cloud supports OpenShift version 3.11 only, which includes Kubernetes version 1.11. The operating system is Red Hat Enterprise Linux 7.
      4. Set a number of worker nodes to create per zone, such as 3.
    • To finish, click Create cluster.
      • ",2),ze=e("p",null,[e("strong",null,"Notes"),o(":")],-1),Te=e("ul",null,[e("li",null,[e("p",null,[o("Your cluster creation might take some time to complete. After the cluster state shows "),e("strong",null,"Normal"),o(", the cluster network and load-balancing component take about 10 more minutes to deploy and update the cluster domain that you use for the OpenShift web console and other routes.")])]),e("li",null,[e("p",null,[o("Verify that your cluster setup is finished before you continue to the next step by checking that the Ingress subdomain on the cluster details page follows a pattern of "),e("code",null,"..containers.appdomain.cloud"),o(".")])])],-1),Me=e("strong",null,"Tip",-1),Be=o(": If you want to learn more about customizing your cluster setup with the CLI, check out "),je={href:"https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-create-cluster",target:"_blank",rel:"noopener noreferrer"},Le=o("Creating an OpenShift cluster"),Fe=o("."),We=e("h2",{id:"step-2-deploying-eclipse-che",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#step-2-deploying-eclipse-che","aria-hidden":"true"},"#"),o(" Step 2: Deploying Eclipse Che")],-1),Ae=e("p",null,"Once you have an OpenShift cluster, you can deploy Eclipse Che on it. This will be done with just a few command-line operations. To be able to execute these commands, there are two prerequisites that you need to install:",-1),Ze=o("Git: To use the features that involve Git, you must install Git and have it available in your system path so that Visual Studio 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 "),Pe={href:"https://git-scm.com",target:"_blank",rel:"noopener noreferrer"},qe=o("https://git-scm.com"),Ne=o("OpenShift CLI: OpenShift CLI is used to manage projects and their deployments. The easiest way to download the CLI is by accessing the About page on the web console if your cluster administrator has enabled the download links. To install OpenShift CLI, you can follow the "),De={href:"https://docs.openshift.com/container-platform/3.7/cli_reference/get_started_cli.html",target:"_blank",rel:"noopener noreferrer"},Ue=o("OpenShift CLI reference documentation"),Re=o(". The steps basically consist of downloading a .zip file with two binary files that you need to place in the right location of your command path."),Ge=e("p",null,"Once you have these two in place, your can perform these installation steps:",-1),Ve=o("Using a command line shell, find a location for your home directory and clone the "),Ye={href:"https://github.com/eclipse/che-operator",target:"_blank",rel:"noopener noreferrer"},Ke=o("che-operator"),He=o(" repository by running this command:"),Je=s(`
      git clone https://github.com/eclipse/che-operator.git
+import{r as i,o as r,a,b as e,d as n,F as l,e as o,c as s}from"./app.daa93c96.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";var h="/zopeneditor-about/assets/ibmzopeneditorinche.13b929bd.png",d="/zopeneditor-about/assets/workspace-using-ibmzstack.75a77fb4.png",p="/zopeneditor-about/assets/wazi-development-client-zowe-explorer.89a406ac.png";const u={},m=e("h1",{id:"ibm-z\xAE-open-editor-in-the-cloud-with-eclipse-che",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z\xAE-open-editor-in-the-cloud-with-eclipse-che","aria-hidden":"true"},"#"),o(" IBM Z\xAE Open Editor in the cloud with Eclipse Che")],-1),f=e("blockquote",null,[e("p",null,[o("by Prasang A. Prajapati, Eric Subah, and Peter Haumer."),e("br"),o(" Last updated: 3 December 2019")])],-1),g={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},_=o("IBM Z Open Editor"),w=o(" is a free Visual Studio Code extension that provides a modern editing experience for IBM Z Enterprise languages. It gives developers the freedom to code in COBOL and PL/I using the same editor they use for other languages such as Java and JavaScript. "),y={href:"https://ibm.github.io/zopeneditor-about/",target:"_blank",rel:"noopener noreferrer"},b=o("Learn more"),v=o("."),k=e("p",null,"However, Visual Studio Code is a rich client editor that needs to be installed and configured by every development team member on their development machines. In addition to installing the editor, enterprise developers also have to get access to source code and other resources residing in SCMs and on z/OS.",-1),O=e("p",null,"What if you could avoid all this and developers could just join a project by getting access and logging on to a website? After logging on, the source code, access to z/OS, and the development environment required for maintaining the project would just be there and developers can just dive in?",-1),C=o("To realize on this vision, there is an excellent open source tool platform called "),S={href:"https://www.eclipse.org/che/",target:"_blank",rel:"noopener noreferrer"},I=o("Eclipse Che"),E=o(". It was built to make Kubernetes development accessible for development teams, providing one-click developer workspaces and eliminating the need for local environment configurations for the entire team. This use case applies not only to Kubernetes development, but by utilizing z/OS connectivity features such as the ones provided by the "),x={href:"https://zowe.org",target:"_blank",rel:"noopener noreferrer"},z=o("Zowe"),T=o(" open source project also fits with the requirements for z/OS Mainframe development projects."),M=o("You can run Eclipse Che in the public cloud, private cloud, or install it on a large list of distributed OS (Ubuntu/Linux/MacOS/Windows). To learn more about Eclipse Che, see "),B={href:"https://www.eclipse.org/che/docs/",target:"_blank",rel:"noopener noreferrer"},j=o("Introduction to Eclipse Che"),L=o(". It is also built for extensibility allowing organizations to create and plug-in additional enhancements or features."),F=o("In the following, we want to show you how easy it is to set up such an Eclipse Che environment in IBM Cloud using OpenShift that is fully integrated with "),W={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},A=o("IBM Z Open Editor"),Z=o(" as well as "),P={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},q=o("Zowe Explorer"),N=o(" in three simple steps. We will provide a sample application that you can use for exploration, but once you have it up and running, you can explore other possibilities for this new kind of development style using your own source code. We would love to hear your feedback and engage into a discussion on how we can make this work for your teams."),D=e("p",null,[e("img",{src:h,alt:"Screen capture for IBM Z Open Editor in Eclipse Che"}),o(" Fig. 1: The user experience of IBM Z Open Editor in Eclipse Che")],-1),U=e("h2",{id:"step-1-getting-started-with-ibm-cloud-and-openshift",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#step-1-getting-started-with-ibm-cloud-and-openshift","aria-hidden":"true"},"#"),o(" Step 1: Getting started with IBM Cloud and OpenShift")],-1),R=o("We recommend exploring Eclipse Che on IBM Cloud utilizing IBM's OpenShift V3.11 offering available there. However, the instruction provided here should also work on any other OpenShift or Kubernetes hosting platforms that can run Eclipse Che. If in fact you have Eclipse Che running somewhere in your organization or a Cloud account of your own, you can directly jump to "),G=e("a",{href:"#step-3:-creating-a-development-workspace-for-z"},"Step 3",-1),V=o(" now. Note that although the cluster and Che environment you are using needs to have at least 3 GB of memory available, the standard Che trial servers at "),Y={href:"https://che.openshift.io",target:"_blank",rel:"noopener noreferrer"},K=o("https://che.openshift.io"),H=o(" do not provide enough resources at the moment unfortunately."),J=e("h3",{id:"introducing-openshift",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#introducing-openshift","aria-hidden":"true"},"#"),o(" Introducing OpenShift")],-1),Q=o("An open source containerized platform developed by "),$={href:"https://www.redhat.com/en",target:"_blank",rel:"noopener noreferrer"},X=o("Red Hat"),ee=o("."),oe=o("It is "),te={href:"https://en.wikipedia.org/wiki/Platform_as_a_service",target:"_blank",rel:"noopener noreferrer"},ne=o("platform as a service (PaaS)"),se=o(". PaaS is a category of cloud computing services which provides an environment for customers to develop, run and manage their applications without the complex infrastructure of building and managing applications."),ie=e("li",null,"OpenShift container platform is a service which can be deployed on public, private or hybrid cloud which will help customers to deploy applications using docker containers.",-1),re=o("It is built on top of "),ae={href:"https://kubernetes.io/",target:"_blank",rel:"noopener noreferrer"},le=o("Kubernetes"),ce=o(" and provides you tools like OpenShift web console or OpenShift CLI to manage projects and deployments."),he=e("li",null,"It simplifies development and operations for cloud native applications.",-1),de=o("It provides a web console to access and manage all the projects using built-in catalogs as well as OpenShift Container Platform templates. To learn more about OpenShift Web Console, you can view the "),pe={href:"https://docs.openshift.com/container-platform/3.7/getting_started/developers_console.html",target:"_blank",rel:"noopener noreferrer"},ue=o("OpenShift web console Walkthrough documentation"),me=o("."),fe=e("h3",{id:"creating-an-openshift-cluster-on-ibm-cloud",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#creating-an-openshift-cluster-on-ibm-cloud","aria-hidden":"true"},"#"),o(" Creating an OpenShift cluster on IBM Cloud")],-1),ge=e("p",null,"Prerequisite: To run Eclipse Che on IBM Cloud using OpenShift, you need have a full IBM Cloud account because the IBM Cloud trial accounts do not have the option to create OpenShift clusters at the moment.",-1),_e=e("p",null,"After you have a full IBM Cloud account, follow the steps below to create an OpenShift cluster:",-1),we=o("Log in to your "),ye={href:"https://cloud.ibm.com/",target:"_blank",rel:"noopener noreferrer"},be=o("IBM Cloud account"),ve=o("."),ke=o("From the Services Catalog, select "),Oe={href:"https://cloud.ibm.com/kubernetes/catalog/openshiftcluster",target:"_blank",rel:"noopener noreferrer"},Ce=o("Red Hat OpenShift Cluster"),Se=o(". Then, click "),Ie=e("strong",null,"Create",-1),Ee=o(" in the summary page."),xe=s("
    • In the Create a new OpenShift cluster page, choose your cluster setup details and name:
      1. For the Location, select the Single zone, which should be enough for evaluation. Set the Geography and then select any of the Worker zones.
      2. Enter a unique name for your cluster and select the resource group that you want to assign to your cluster.
      3. For Default worker pool, choose an available flavor for your worker nodes. Red Hat OpenShift on IBM Cloud supports OpenShift version 3.11 only, which includes Kubernetes version 1.11. The operating system is Red Hat Enterprise Linux 7.
      4. Set a number of worker nodes to create per zone, such as 3.
    • To finish, click Create cluster.
      • ",2),ze=e("p",null,[e("strong",null,"Notes"),o(":")],-1),Te=e("ul",null,[e("li",null,[e("p",null,[o("Your cluster creation might take some time to complete. After the cluster state shows "),e("strong",null,"Normal"),o(", the cluster network and load-balancing component take about 10 more minutes to deploy and update the cluster domain that you use for the OpenShift web console and other routes.")])]),e("li",null,[e("p",null,[o("Verify that your cluster setup is finished before you continue to the next step by checking that the Ingress subdomain on the cluster details page follows a pattern of "),e("code",null,"..containers.appdomain.cloud"),o(".")])])],-1),Me=e("strong",null,"Tip",-1),Be=o(": If you want to learn more about customizing your cluster setup with the CLI, check out "),je={href:"https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-create-cluster",target:"_blank",rel:"noopener noreferrer"},Le=o("Creating an OpenShift cluster"),Fe=o("."),We=e("h2",{id:"step-2-deploying-eclipse-che",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#step-2-deploying-eclipse-che","aria-hidden":"true"},"#"),o(" Step 2: Deploying Eclipse Che")],-1),Ae=e("p",null,"Once you have an OpenShift cluster, you can deploy Eclipse Che on it. This will be done with just a few command-line operations. To be able to execute these commands, there are two prerequisites that you need to install:",-1),Ze=o("Git: To use the features that involve Git, you must install Git and have it available in your system path so that Visual Studio 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 "),Pe={href:"https://git-scm.com",target:"_blank",rel:"noopener noreferrer"},qe=o("https://git-scm.com"),Ne=o("OpenShift CLI: OpenShift CLI is used to manage projects and their deployments. The easiest way to download the CLI is by accessing the About page on the web console if your cluster administrator has enabled the download links. To install OpenShift CLI, you can follow the "),De={href:"https://docs.openshift.com/container-platform/3.7/cli_reference/get_started_cli.html",target:"_blank",rel:"noopener noreferrer"},Ue=o("OpenShift CLI reference documentation"),Re=o(". The steps basically consist of downloading a .zip file with two binary files that you need to place in the right location of your command path."),Ge=e("p",null,"Once you have these two in place, your can perform these installation steps:",-1),Ve=o("Using a command line shell, find a location for your home directory and clone the "),Ye={href:"https://github.com/eclipse/che-operator",target:"_blank",rel:"noopener noreferrer"},Ke=o("che-operator"),He=o(" repository by running this command:"),Je=s(`
      git clone https://github.com/eclipse/che-operator.git
 
      `,1),Qe=o("This repository contains all the scripts and configuration files needed to deploy Eclipse Che and all of its components to your cluster. Refer to "),$e={href:"https://github.com/eclipse/che-operator/blob/master/README.md",target:"_blank",rel:"noopener noreferrer"},Xe=o("Che/Codeready Workspaces Operator Documentation"),eo=o(" to learn more about che-operator. Then, navigate to the new directory with"),oo=s(`
      cd che-operator
 
      as you will execute commands form there further below.
      `,2),to=o("Using the OpenShift command line tool you need to now first log in to your cluster. The OpenShift web console provides a user-friendly way to do so using access token generating the entire login command for you to copy-paste. To find that, go back to your OpenShift web console browser screen and open user menu in the upper right corner. There you find the option "),no=e("code",null,"Copy Login Command",-1),so=o(", which will copy the command to your clipboard. Go back to your command line shell and paste the login command and run it. For more information, see "),io={href:"https://docs.openshift.com/container-platform/3.11/getting_started/developers_cli.html#developers-cli-creating-a-project",target:"_blank",rel:"noopener noreferrer"},ro=o("Creating a Project"),ao=o("."),lo=o("Now you are ready to create a namespace in your cluster and deploy Che in that namespace. A namespace is a virtual cluster in which multiple resources exist. Each resource can be referenced by its unique name. Therefore, namespaces avoid basic naming collisions. A Project in OpenShift is equivalent to a Kubernetes namespace. However, in addition to the namespace name, OpenShift projects can also manage a user-friendly display name and description. For details, see "),co={href:"https://docs.openshift.com/enterprise/3.0/architecture/core_concepts/projects_and_users.html",target:"_blank",rel:"noopener noreferrer"},ho=o("Users, Namespaces, and Projects"),po=o("."),uo=s(`
      oc create namespace <your_namespace_name>
 
      Then, navigate with your cluster login to the newly created namespace:
      oc project <your_namespace_name>
diff --git a/assets/index.html.3ac4de35.js b/assets/index.html.73039857.js
similarity index 75%
rename from assets/index.html.3ac4de35.js
rename to assets/index.html.73039857.js
index 83d9d3869..51ba47148 100644
--- a/assets/index.html.3ac4de35.js
+++ b/assets/index.html.73039857.js
@@ -1 +1 @@
-const m={key:"v-8daa1a0e",path:"/",title:"",lang:"en-US",frontmatter:{home:!0},excerpt:"",headers:[],git:{updatedTime:172304606e4,contributors:[{name:"Peter Haumer",email:"4391934+phaumer@users.noreply.github.com",commits:23},{name:"Peter Haumer",email:"phaumer@us.ibm.com",commits:13},{name:"enzi",email:"enzi@ca.ibm.com",commits:13},{name:"Lauren Li",email:"Lauren.Li@ibm.com",commits:5},{name:"PETER HAUMER",email:"phaumer@us.ibm.com",commits:5},{name:"Lauren Li",email:"45975633+lauren-li@users.noreply.github.com",commits:2},{name:"Min Huang",email:"minhsh@cn.ibm.com",commits:2},{name:"Rudy Leonel Pichola Flores",email:"rudyflores@ibm.com",commits:2},{name:"kmaselli",email:"81706519+kmaselli@users.noreply.github.com",commits:2},{name:"Chun Hong Zheng",email:"chunhzh@cn.ibm.com",commits:1},{name:"KRISTINA MAYO",email:"ktopchi@us.ibm.com",commits:1},{name:"Prasang Prajapati",email:"Prasang.A.Prajapati@ibm.com",commits:1},{name:"Prasang-A-Prajapati",email:"Prasang.A.Prajapati@ibm.com",commits:1}]},filePathRelative:"README.md"};export{m as data};
+const m={key:"v-8daa1a0e",path:"/",title:"",lang:"en-US",frontmatter:{home:!0},excerpt:"",headers:[],git:{updatedTime:172669794e4,contributors:[{name:"Peter Haumer",email:"4391934+phaumer@users.noreply.github.com",commits:24},{name:"Peter Haumer",email:"phaumer@us.ibm.com",commits:13},{name:"enzi",email:"enzi@ca.ibm.com",commits:13},{name:"PETER HAUMER",email:"phaumer@us.ibm.com",commits:6},{name:"Lauren Li",email:"Lauren.Li@ibm.com",commits:5},{name:"Lauren Li",email:"45975633+lauren-li@users.noreply.github.com",commits:2},{name:"Min Huang",email:"minhsh@cn.ibm.com",commits:2},{name:"Rudy Leonel Pichola Flores",email:"rudyflores@ibm.com",commits:2},{name:"kmaselli",email:"81706519+kmaselli@users.noreply.github.com",commits:2},{name:"Chun Hong Zheng",email:"chunhzh@cn.ibm.com",commits:1},{name:"KRISTINA MAYO",email:"ktopchi@us.ibm.com",commits:1},{name:"Prasang Prajapati",email:"Prasang.A.Prajapati@ibm.com",commits:1},{name:"Prasang-A-Prajapati",email:"Prasang.A.Prajapati@ibm.com",commits:1}]},filePathRelative:"README.md"};export{m as data};
diff --git a/assets/index.html.94ae7a7a.js b/assets/index.html.94ae7a7a.js
deleted file mode 100644
index 70a4474d1..000000000
--- a/assets/index.html.94ae7a7a.js
+++ /dev/null
@@ -1 +0,0 @@
-import{c as r}from"./app.f6cb3ed9.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";var o="/zopeneditor-about/assets/img/code_identifier.png",e="/zopeneditor-about/assets/img/chevron-left.svg",i="/zopeneditor-about/assets/img/chevron-right.svg",n="/zopeneditor-about/assets/img/monitor.png",t="/zopeneditor-about/assets/img/vscode.svg",c="/zopeneditor-about/assets/img/zowe.svg",s="/zopeneditor-about/assets/img/syntax.svg",m="/zopeneditor-about/assets/img/theia_che2.svg",g="/zopeneditor-about/assets/img/copybook.svg",l="/zopeneditor-about/assets/img/cobol_pl1.svg",v="/zopeneditor-about/assets/img/explorers.svg",u="/zopeneditor-about/assets/img/tile_rse.svg",h="/zopeneditor-about/assets/img/git.svg",p="/zopeneditor-about/assets/img/outline.svg",b="/zopeneditor-about/assets/img/codelens.svg",f="/zopeneditor-about/assets/img/refactor.svg",w="/zopeneditor-about/assets/img/snipets.svg",_="/zopeneditor-about/assets/img/terminal.svg",a="/zopeneditor-about/assets/img/arrow-double.png",x="/zopeneditor-about/assets/img/arrow-single.png",k="/zopeneditor-about/assets/img/checkmark--filled.svg",z="/zopeneditor-about/assets/img/ibm-wazi-developer.svg",y="/zopeneditor-about/assets/img/logo--github.svg",I="/zopeneditor-about/assets/img/nav_title.svg",C="/zopeneditor-about/assets/img/zowe-footer-logo.svg",S="/zopeneditor-about/assets/img/vscode-footer-logo.svg";const L={},M=r('

      IBM Z\xAE Open Editor
      A free modern editing experience for IBM Z Enterprise languages
      Getting Started
      About
      IBM Z Open Editor is for developers interested in Z enterprise application development, especially those who prefer a modern development environment. By bringing IBM z/OS language support to one of today\u2019s most popular code editors, Visual Studio Code (VS Code), IBM Z Open Editor gives developers the freedom to code in COBOL, PL/I, High-Level Assembler, REXX, or JCL using the same editor they can use for languages such as Java and JavaScript. IBM Z Open Editor is a FREE, easily downloadable extension in Visual Studio Code\u2019s marketplace.
      Features
      vs code
      zowe
      explorers
      explorers
      explorers
      Feedback
       Your feedback is important to us. Tell us what you think about the experience by taking the survey or creating an issue in GitHub. Join the Wazi Developer Community and stay up-to-date with the latest news and discussions. 
      ',4);function B(E,O){return M}var A=d(L,[["render",B]]);export{A as default};
diff --git a/assets/index.html.f7b6c1dc.js b/assets/index.html.f7b6c1dc.js
new file mode 100644
index 000000000..72b5ef50c
--- /dev/null
+++ b/assets/index.html.f7b6c1dc.js
@@ -0,0 +1 @@
+import{c as r}from"./app.daa93c96.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";var o="/zopeneditor-about/assets/img/code_identifier.png",e="/zopeneditor-about/assets/img/chevron-left.svg",i="/zopeneditor-about/assets/img/chevron-right.svg",n="/zopeneditor-about/assets/img/monitor.png",t="/zopeneditor-about/assets/img/vscode.svg",c="/zopeneditor-about/assets/img/zowe.svg",s="/zopeneditor-about/assets/img/syntax.svg",m="/zopeneditor-about/assets/img/theia_che2.svg",g="/zopeneditor-about/assets/img/copybook.svg",l="/zopeneditor-about/assets/img/cobol_pl1.svg",v="/zopeneditor-about/assets/img/explorers.svg",u="/zopeneditor-about/assets/img/tile_rse.svg",h="/zopeneditor-about/assets/img/git.svg",p="/zopeneditor-about/assets/img/outline.svg",b="/zopeneditor-about/assets/img/codelens.svg",f="/zopeneditor-about/assets/img/refactor.svg",_="/zopeneditor-about/assets/img/snipets.svg",w="/zopeneditor-about/assets/img/terminal.svg",a="/zopeneditor-about/assets/img/arrow-double.png",x="/zopeneditor-about/assets/img/arrow-single.png",k="/zopeneditor-about/assets/img/checkmark--filled.svg",z="/zopeneditor-about/assets/img/ibm-wazi-developer.svg",y="/zopeneditor-about/assets/img/logo--github.svg",S="/zopeneditor-about/assets/img/nav_title.svg",I="/zopeneditor-about/assets/img/zowe-footer-logo.svg",C="/zopeneditor-about/assets/img/vscode-footer-logo.svg";const L={},M=r('

      IBM Z\xAE Open Editor
      A free modern editing experience for IBM Z Enterprise languages
      Getting Started
      About
      IBM Z Open Editor is for developers interested in Z enterprise application development, especially those who prefer a modern development environment. By bringing IBM z/OS language support to one of today\u2019s most popular code editors, Visual Studio Code (VS Code), IBM Z Open Editor gives developers the freedom to code in COBOL, PL/I, High-Level Assembler, REXX, or JCL using the same editor they can use for languages such as Java and JavaScript. IBM Z Open Editor is a FREE, easily downloadable extension in Visual Studio Code\u2019s marketplace.
      Features
      vs code
      zowe
      explorers
      explorers
      explorers
      Feedback
       Your feedback is important to us. Tell us what you think about the experience by taking the survey or creating an issue in GitHub. Join the Wazi Developer Community and stay up-to-date with the latest news and discussions. 
      ',4);function O(B,E){return M}var A=d(L,[["render",O]]);export{A as default};
diff --git a/assets/interact_common_properties_cli.html.1a7bccf8.js b/assets/interact_common_properties_cli.html.ebe56c0e.js
similarity index 99%
rename from assets/interact_common_properties_cli.html.1a7bccf8.js
rename to assets/interact_common_properties_cli.html.ebe56c0e.js
index 27d802343..c8d7eab95 100644
--- a/assets/interact_common_properties_cli.html.1a7bccf8.js
+++ b/assets/interact_common_properties_cli.html.ebe56c0e.js
@@ -1,4 +1,4 @@
-import{c as e}from"./app.f6cb3ed9.js";import{_ as s}from"./plugin-vue_export-helper.21dcd24c.js";const n={},r=e(`
       Interact with RSE Common Properties
      The Common Properties service is an optional feature available in IBM z/OS Explorer and must be configured and enabled in the host configuration file (rse.env).
      To enable the Common Properties service, a system programmer must set the RSE_COMMON_PROPERTIES variable in the rse.env file. For example, RSE_COMMON_PROPERTIES=/usr/shared/common.properties.
      Common Properties provides services for users to store JSON objects in different namespaces. The namespace can be globally accessible by all users or only accessible by the creator of the namespace. Namespace is implemented internally as a JSON document. You can interact with the Common Properties service by using commands that are provided by the IBM\xAE RSE API plug-in for Zowe\u2122 CLI (RSE CLI plug-in) in the Terminal window.
       Using RSE CLI plug-in commands
      RSE API Plug-in for Zowe CLI allows users to store JSON configuration or any key-value properties in a namespace that can be shared globally with all users. The namespace can also be created as nonsharable and only accessible by the creator.
      Here is a use case for storing and retrieving server configuration properties by using the RSE Common Properties service. First, create a global namespace to be shared for all users. If you need to create a private namespace without sharing, you need to include the --private option in the commands.
      % zowe rse common-properties create ns1
+import{c as e}from"./app.daa93c96.js";import{_ as s}from"./plugin-vue_export-helper.21dcd24c.js";const n={},r=e(`
       Interact with RSE Common Properties
      The Common Properties service is an optional feature available in IBM z/OS Explorer and must be configured and enabled in the host configuration file (rse.env).
      To enable the Common Properties service, a system programmer must set the RSE_COMMON_PROPERTIES variable in the rse.env file. For example, RSE_COMMON_PROPERTIES=/usr/shared/common.properties.
      Common Properties provides services for users to store JSON objects in different namespaces. The namespace can be globally accessible by all users or only accessible by the creator of the namespace. Namespace is implemented internally as a JSON document. You can interact with the Common Properties service by using commands that are provided by the IBM\xAE RSE API plug-in for Zowe\u2122 CLI (RSE CLI plug-in) in the Terminal window.
       Using RSE CLI plug-in commands
      RSE API Plug-in for Zowe CLI allows users to store JSON configuration or any key-value properties in a namespace that can be shared globally with all users. The namespace can also be created as nonsharable and only accessible by the creator.
      Here is a use case for storing and retrieving server configuration properties by using the RSE Common Properties service. First, create a global namespace to be shared for all users. If you need to create a private namespace without sharing, you need to include the --private option in the commands.
      % zowe rse common-properties create ns1
 Namespace created successfully.
 
      Next, save the test server configuration with hostname and port number as one JSON object at the path of /test-server in the namespace.
      $ zowe rse common-properties set ns1 /test-server '{"hostname" : "www.test.com", "port" : 1234}' --type json
 Property set successfully.
diff --git a/assets/interact_zos_cli.html.f30565d5.js b/assets/interact_zos_cli.html.afca56ce.js
similarity index 99%
rename from assets/interact_zos_cli.html.f30565d5.js
rename to assets/interact_zos_cli.html.afca56ce.js
index 9ee8d6c74..9122ae03b 100644
--- a/assets/interact_zos_cli.html.f30565d5.js
+++ b/assets/interact_zos_cli.html.afca56ce.js
@@ -1,4 +1,4 @@
-import{r as l,o as r,a as c,b as e,d as s,w as o,F as d,e as n,c as i}from"./app.f6cb3ed9.js";import{_ as p}from"./rse-help-web.56c77c6d.js";import{_ as u}from"./plugin-vue_export-helper.21dcd24c.js";const m={},h=e("h1",{id:"using-command-line-to-interact-with-z-os",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-command-line-to-interact-with-z-os","aria-hidden":"true"},"#"),n(" Using command line to interact with z/OS")],-1),b=n("You can use the Terminal window in VS Code to run command-line operations on your client. For example, you can use the terminal to perform file-based operations and execute any kind of "),g={href:"https://git-scm.com/docs",target:"_blank",rel:"noopener noreferrer"},f=n("Git commands"),w=n(" on your local files right from this terminal."),_=i('
      In addition, you can interact with z/OS\xAE by using commands that are provided by IBM\xAE RSE API plug-in for Zowe\u2122 CLI (RSE CLI plug-in), Zowe CLI, or both in the Terminal window. These commands provide various capabilities for interacting with z/OS resources that include MVS\u2122, jobs, and z/OS UNIX System Services.
      To open the Terminal window, click Terminal > New Terminal or press Ctrl+`. It is opened at the bottom below the editor and inside the working directory that contains all the files that are shown in the Files view.
       Comparison between Zowe CLI and RSE CLI plug-in
      Both of Zowe CLI and RSE CLI plug-in provide the commands, with slight differences in command names and options, to let you perform the following tasks:
      • List, create, rename, delete z/OS UNIX System Services files and directories and MVS data sets and members
      • Run JCL jobs
      • Browse job spool files
      Though the capabilities of Zowe CLI and RSE CLI plug-in are similar, the installation and configuration requirements are different:
      ',6),v=n("To use the commands provided by Zowe CLI to interact with z/OS, you must "),S={href:"https://docs.zowe.org/stable/user-guide/systemrequirements-zosmf.html",target:"_blank",rel:"noopener noreferrer"},y=n("configure z/OSMF"),x=n(" before you install Zowe CLI."),L=e("li",null,[e("p",null,"RSE CLI plug-in extends Zowe CLI to let you interact with z/OS resources by using IBM Remote System Explorer API (RSE API) as an alternative to using z/OSMF. The RSE API is a collection of REST APIs that allow a client to work with various components on the z/OS host system, including MVS data sets, z/OS UNIX files and commands, JES jobs, and more. The overall solution results in a complete set of operations that allows you to do everything as you could do with z/OSMF. Therefore, RSE CLI plug-in is a great alternative if you have used the Remote System Explorer API with other IBM offerings such as IBM Developer for z/OS or IBM Explorer for z/OS.")],-1),I=n("For more information about the commands provided by Zowe CLI and RSE CLI plug-in, see the "),C=n("command mapping table"),z=n("."),O=e("h2",{id:"using-rse-cli-plug-in-commands",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-rse-cli-plug-in-commands","aria-hidden":"true"},"#"),n(" Using RSE CLI plug-in commands")],-1),E=e("h3",{id:"prerequisites",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#prerequisites","aria-hidden":"true"},"#"),n(" Prerequisites")],-1),R=n("Installing IBM RSE API Plug-in for Zowe CLI"),T=n("Creating a RSE or z/OSMF profile by using Zowe CLI to connect to z/OS"),k=i(`
       Running RSE CLI plug-in commands
      After installing RSE CLI plug-in, you can use it in a command-line window on your development machine. You can issue commands to perform the following tasks:
      • List, create, download, upload, and delete MVS data sets and members as well as z/OS UNIX System Services files and directories.
      • Submit jobs, list jobs and spool files, download or view spool content, view job status, cancel a job, and delete a job.
      For example, after you created your RSE profile for the user USER1 and a data set with your COBOL programs called USER1.SAMPLE.COBOL, you can work on your MVS data sets with the following commands:
      List your data sets and members:
      zowe rse ls ds USER1
+import{r as l,o as r,a as c,b as e,d as s,w as o,F as d,e as n,c as i}from"./app.daa93c96.js";import{_ as p}from"./rse-help-web.56c77c6d.js";import{_ as u}from"./plugin-vue_export-helper.21dcd24c.js";const m={},h=e("h1",{id:"using-command-line-to-interact-with-z-os",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-command-line-to-interact-with-z-os","aria-hidden":"true"},"#"),n(" Using command line to interact with z/OS")],-1),b=n("You can use the Terminal window in VS Code to run command-line operations on your client. For example, you can use the terminal to perform file-based operations and execute any kind of "),g={href:"https://git-scm.com/docs",target:"_blank",rel:"noopener noreferrer"},f=n("Git commands"),w=n(" on your local files right from this terminal."),_=i('
      In addition, you can interact with z/OS\xAE by using commands that are provided by IBM\xAE RSE API plug-in for Zowe\u2122 CLI (RSE CLI plug-in), Zowe CLI, or both in the Terminal window. These commands provide various capabilities for interacting with z/OS resources that include MVS\u2122, jobs, and z/OS UNIX System Services.
      To open the Terminal window, click Terminal > New Terminal or press Ctrl+`. It is opened at the bottom below the editor and inside the working directory that contains all the files that are shown in the Files view.
       Comparison between Zowe CLI and RSE CLI plug-in
      Both of Zowe CLI and RSE CLI plug-in provide the commands, with slight differences in command names and options, to let you perform the following tasks:
      • List, create, rename, delete z/OS UNIX System Services files and directories and MVS data sets and members
      • Run JCL jobs
      • Browse job spool files
      Though the capabilities of Zowe CLI and RSE CLI plug-in are similar, the installation and configuration requirements are different:
      ',6),v=n("To use the commands provided by Zowe CLI to interact with z/OS, you must "),S={href:"https://docs.zowe.org/stable/user-guide/systemrequirements-zosmf.html",target:"_blank",rel:"noopener noreferrer"},y=n("configure z/OSMF"),x=n(" before you install Zowe CLI."),L=e("li",null,[e("p",null,"RSE CLI plug-in extends Zowe CLI to let you interact with z/OS resources by using IBM Remote System Explorer API (RSE API) as an alternative to using z/OSMF. The RSE API is a collection of REST APIs that allow a client to work with various components on the z/OS host system, including MVS data sets, z/OS UNIX files and commands, JES jobs, and more. The overall solution results in a complete set of operations that allows you to do everything as you could do with z/OSMF. Therefore, RSE CLI plug-in is a great alternative if you have used the Remote System Explorer API with other IBM offerings such as IBM Developer for z/OS or IBM Explorer for z/OS.")],-1),I=n("For more information about the commands provided by Zowe CLI and RSE CLI plug-in, see the "),C=n("command mapping table"),z=n("."),O=e("h2",{id:"using-rse-cli-plug-in-commands",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-rse-cli-plug-in-commands","aria-hidden":"true"},"#"),n(" Using RSE CLI plug-in commands")],-1),E=e("h3",{id:"prerequisites",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#prerequisites","aria-hidden":"true"},"#"),n(" Prerequisites")],-1),R=n("Installing IBM RSE API Plug-in for Zowe CLI"),T=n("Creating a RSE or z/OSMF profile by using Zowe CLI to connect to z/OS"),k=i(`
       Running RSE CLI plug-in commands
      After installing RSE CLI plug-in, you can use it in a command-line window on your development machine. You can issue commands to perform the following tasks:
      • List, create, download, upload, and delete MVS data sets and members as well as z/OS UNIX System Services files and directories.
      • Submit jobs, list jobs and spool files, download or view spool content, view job status, cancel a job, and delete a job.
      For example, after you created your RSE profile for the user USER1 and a data set with your COBOL programs called USER1.SAMPLE.COBOL, you can work on your MVS data sets with the following commands:
      List your data sets and members:
      zowe rse ls ds USER1
 zowe rse ls all-members USER1.SAMPLE.COBOL
 
      Download members:
      zowe rse download ds "USER1.SAMPLE.COBOL(SAM1)"
 
      You will see that new folders appear on the left with the names based on your data set that contains the file SAM1. You can rename it by adding a .cbl extension to edit it in the COBOL editor, and then upload it later using drag-and-drop or via the command line.
      Check the status of your jobs:
      zowe rse ls js | grep ACTIVE
diff --git a/assets/interact_zos_overview.html.f369dafa.js b/assets/interact_zos_overview.html.286dac9b.js
similarity index 97%
rename from assets/interact_zos_overview.html.f369dafa.js
rename to assets/interact_zos_overview.html.286dac9b.js
index 55549fb94..e45dd01c0 100644
--- a/assets/interact_zos_overview.html.f369dafa.js
+++ b/assets/interact_zos_overview.html.286dac9b.js
@@ -1 +1 @@
-import{r as i,o as l,a,b as e,d as t,w as s,F as c,e as o}from"./app.f6cb3ed9.js";import{_}from"./plugin-vue_export-helper.21dcd24c.js";const d={},h=e("h1",{id:"interacting-with-z-os",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#interacting-with-z-os","aria-hidden":"true"},"#"),o(" Interacting with z/OS")],-1),u=o("In VS Code, you can interact with z/OS in the Terminal window by using commands provided by IBM RSE API plug-in for Zowe CLI (RSE CLI plug-in), Zowe CLI, or both. For more information about their differences, see "),p=o("Comparison between Zowe CLI and RSE CLI plug-in"),w=o("."),m=e("p",null,"Additionally, you can graphically navigate and access file and job resources on z/OS by using the Zowe Explorer VS Code extension. It is recommended to use Zowe Explorer, with which you can edit COBOL, PL/I, and HLASM files that are opened on z/OS MVS\u2122 and z/OS UNIX System Services, and run JCL and browse job spool files.",-1),g=o("After you choose and install the prerequisites according to "),f=o("Setting up integrations to interact with z/OS"),z=o(", refer to the following usage instructions:"),S=e("thead",null,[e("tr",null,[e("th",null,"Available host component"),e("th",null,"To use command line, see..."),e("th",null,"To use graphical interface, see...")])],-1),x=e("td",null,"RSE API",-1),I=o("Using RSE CLI plug-in commands"),b=o("Using RSE API in Zowe Explorer"),E=o(" and "),L=o("Using Zowe Explorer views"),C=e("td",null,"z/OSMF",-1),v=o("Using Zowe CLI z/OSMF commands"),y={href:"https://docs.zowe.org/stable/user-guide/ze-profiles.html#working-with-zowe-explorer-profiles",target:"_blank",rel:"noopener noreferrer"},O=o("Working with Zowe Explorer profiles"),Z=o(" and "),k=o("Using Zowe Explorer views"),D=o("See "),R=o("Supported methods of authentication"),A=o(".");function U(V,B){const n=i("RouterLink"),r=i("ExternalLinkIcon");return l(),a(c,null,[h,e("p",null,[u,t(n,{to:"/Docs/interact_zos_cli.html#comparison-between-zowe-cli-and-rse-cli-plug-in"},{default:s(()=>[p]),_:1}),w]),m,e("p",null,[g,t(n,{to:"/Docs/setup_integration.html"},{default:s(()=>[f]),_:1}),z]),e("table",null,[S,e("tbody",null,[e("tr",null,[x,e("td",null,[t(n,{to:"/Docs/interact_zos_cli.html#using-rse-cli-plug-in-commands"},{default:s(()=>[I]),_:1})]),e("td",null,[t(n,{to:"/Docs/interact_zos_zowe_explorer.html#using-rse-api-in-zowe-explorer"},{default:s(()=>[b]),_:1}),E,t(n,{to:"/Docs/interact_zos_zowe_explorer.html#using-zowe-explorer-views-to-interact-with-z-os"},{default:s(()=>[L]),_:1})])]),e("tr",null,[C,e("td",null,[t(n,{to:"/Docs/interact_zos_cli.html#using-zowe-cli-z-osmf-commands"},{default:s(()=>[v]),_:1})]),e("td",null,[e("a",y,[O,t(r)]),Z,t(n,{to:"/Docs/interact_zos_zowe_explorer.html#using-zowe-explorer-views-to-interact-with-z-os"},{default:s(()=>[k]),_:1})])])])]),e("p",null,[D,t(n,{to:"/Docs/zowe_advanced_connection_scenarious.html"},{default:s(()=>[R]),_:1}),A])],64)}var N=_(d,[["render",U]]);export{N as default};
+import{r as i,o as l,a,b as e,d as t,w as s,F as c,e as o}from"./app.daa93c96.js";import{_}from"./plugin-vue_export-helper.21dcd24c.js";const d={},h=e("h1",{id:"interacting-with-z-os",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#interacting-with-z-os","aria-hidden":"true"},"#"),o(" Interacting with z/OS")],-1),u=o("In VS Code, you can interact with z/OS in the Terminal window by using commands provided by IBM RSE API plug-in for Zowe CLI (RSE CLI plug-in), Zowe CLI, or both. For more information about their differences, see "),p=o("Comparison between Zowe CLI and RSE CLI plug-in"),w=o("."),m=e("p",null,"Additionally, you can graphically navigate and access file and job resources on z/OS by using the Zowe Explorer VS Code extension. It is recommended to use Zowe Explorer, with which you can edit COBOL, PL/I, and HLASM files that are opened on z/OS MVS\u2122 and z/OS UNIX System Services, and run JCL and browse job spool files.",-1),g=o("After you choose and install the prerequisites according to "),f=o("Setting up integrations to interact with z/OS"),z=o(", refer to the following usage instructions:"),S=e("thead",null,[e("tr",null,[e("th",null,"Available host component"),e("th",null,"To use command line, see..."),e("th",null,"To use graphical interface, see...")])],-1),x=e("td",null,"RSE API",-1),I=o("Using RSE CLI plug-in commands"),b=o("Using RSE API in Zowe Explorer"),E=o(" and "),L=o("Using Zowe Explorer views"),C=e("td",null,"z/OSMF",-1),v=o("Using Zowe CLI z/OSMF commands"),y={href:"https://docs.zowe.org/stable/user-guide/ze-profiles.html#working-with-zowe-explorer-profiles",target:"_blank",rel:"noopener noreferrer"},O=o("Working with Zowe Explorer profiles"),Z=o(" and "),k=o("Using Zowe Explorer views"),D=o("See "),R=o("Supported methods of authentication"),A=o(".");function U(V,B){const n=i("RouterLink"),r=i("ExternalLinkIcon");return l(),a(c,null,[h,e("p",null,[u,t(n,{to:"/Docs/interact_zos_cli.html#comparison-between-zowe-cli-and-rse-cli-plug-in"},{default:s(()=>[p]),_:1}),w]),m,e("p",null,[g,t(n,{to:"/Docs/setup_integration.html"},{default:s(()=>[f]),_:1}),z]),e("table",null,[S,e("tbody",null,[e("tr",null,[x,e("td",null,[t(n,{to:"/Docs/interact_zos_cli.html#using-rse-cli-plug-in-commands"},{default:s(()=>[I]),_:1})]),e("td",null,[t(n,{to:"/Docs/interact_zos_zowe_explorer.html#using-rse-api-in-zowe-explorer"},{default:s(()=>[b]),_:1}),E,t(n,{to:"/Docs/interact_zos_zowe_explorer.html#using-zowe-explorer-views-to-interact-with-z-os"},{default:s(()=>[L]),_:1})])]),e("tr",null,[C,e("td",null,[t(n,{to:"/Docs/interact_zos_cli.html#using-zowe-cli-z-osmf-commands"},{default:s(()=>[v]),_:1})]),e("td",null,[e("a",y,[O,t(r)]),Z,t(n,{to:"/Docs/interact_zos_zowe_explorer.html#using-zowe-explorer-views-to-interact-with-z-os"},{default:s(()=>[k]),_:1})])])])]),e("p",null,[D,t(n,{to:"/Docs/zowe_advanced_connection_scenarious.html"},{default:s(()=>[R]),_:1}),A])],64)}var N=_(d,[["render",U]]);export{N as default};
diff --git a/assets/interact_zos_zopeneditor.html.b1952528.js b/assets/interact_zos_zopeneditor.html.31626061.js
similarity index 99%
rename from assets/interact_zos_zopeneditor.html.b1952528.js
rename to assets/interact_zos_zopeneditor.html.31626061.js
index 27feb5a0a..a1616ba39 100644
--- a/assets/interact_zos_zopeneditor.html.b1952528.js
+++ b/assets/interact_zos_zopeneditor.html.31626061.js
@@ -1,4 +1,4 @@
-import{r as n,o as i,a,b as e,d as l,w as r,F as p,c as t,e as o}from"./app.f6cb3ed9.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";var h="/zopeneditor-about/assets/zowe-settings.136506c4.png",c="/zopeneditor-about/assets/zowe-no-prof-status.449ce1d3.png",u="/zopeneditor-about/assets/zowe-rse-status.8c65c6dd.png",f="/zopeneditor-about/assets/profile-management-opts.2e84d181.png";const g={},m=t('
       Using Zowe profiles in Z Open Editor
      Z Open Editor extends Zowe Explorer functionality by making use of the Zowe profiles for z/OS connections to complete certain tasks. The profiles that are used by Z Open Editor are stored in the zopeneditor.zowe settings along with other lower-level settings that deal with connecting to z/OS.
      IBM Z Open Editor will by default follow these precedence rules to identify which Zowe profile to use:
      1. Use the profile specified by the zopeneditor.zowe user setting.
      2. If no profile is defined in the user setting, then use the default RSE profile if available.
      3. If the default RSE profile is not available, then use the default z/OSMF profile if available. If the default z/OSMF profile is not defined, errors are shown.
       zopeneditor.zowe settings explained
      ',5),w=e("li",null,[e("p",null,[e("code",null,"defaultCliProfile"),o(": The value is the name of the Zowe RSE or z/OSMF profile that you want to use. If you cannot remember the names, you can find the profile name using Zowe Explorer GUI or run the following Zowe CLI commands to get the list of all your profiles and your default profile:")]),e("ul",null,[e("li",null,[o("List RSE profiles: "),e("code",null,"zowe profiles list rse")]),e("li",null,[o("List z/OSMF profiles: "),e("code",null,"zowe profiles list zosmf")])])],-1),b=e("li",null,[e("p",null,[e("code",null,"defaultSshCliProfile"),o(": The value is the name of the Zowe SSH profile that you want to use. Some functionalities offered by Z Open Editor may require a Zowe SSH profile to be specified.")])],-1),z=e("code",null,"defaultRseConversionMappingsFile",-1),y=o(": discussed in detail in the "),S=o("MVS EBCDIC code pages and mappings files"),v=o(" help section."),_=t("
    • listBeforeDownload: The value is boolean and modifies Z Open Editor's behavior when requesting a file from MVS:
      • When the setting is set to true, the editor will first try to confirm whether the requested file exists by performing a list operation for that file. If the requested file exists, the editor will send another request to download it. If the requested file does not exist, the editor will move on to test the next location listed in the property group.
      • When the setting is set to false, the editor will directly try to download the file from MVS without checking whether it exists. If the response from z/OS is a Not Found error, the editor will move on to the next location listed in the property group. In some cases when using z/OSMF as the protocol, this Not Found error will cause entries in z/OS log files, which you can avoid by specifying the value of the setting to true.
      This extra round trip to the server when set to true to check the existence will have a performance impact. Because the logging is not always an issue for all z/OSMF users and not an issue when using the RSE API protocol, and because of the performance advantage, the default value for this setting is false.
    • maximumParallelFileDownloads: The value can be used to specify how many parallel downloads Z Open Editor should perform when requesting include files from MVS. Downloading several files in parallel can significantly improve performance, especially when you edit programs with many include files. The downside is that some protocols such as z/OSMF will allocate more address spaces for the parallel requests, which causes more resources to be used and more logging on the z/OS side. The RSE API protocol does not have that problem because it achieves scalability in other ways that are outlined in the RSE documentation. The default value for this setting is 5, and the maximum value is 10. Set it to 1 to disable parallel downloads and request one include file at a time.
      • ",2),k=t(`
       Changing the Zowe Profile using VS Code settings
      The format of the zopeneditor.zowe user setting is as follows:
      "zopeneditor.zowe": {
+import{r as n,o as i,a,b as e,d as l,w as r,F as p,c as t,e as o}from"./app.daa93c96.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";var h="/zopeneditor-about/assets/zowe-settings.136506c4.png",c="/zopeneditor-about/assets/zowe-no-prof-status.449ce1d3.png",u="/zopeneditor-about/assets/zowe-rse-status.8c65c6dd.png",f="/zopeneditor-about/assets/profile-management-opts.2e84d181.png";const g={},m=t('
       Using Zowe profiles in Z Open Editor
      Z Open Editor extends Zowe Explorer functionality by making use of the Zowe profiles for z/OS connections to complete certain tasks. The profiles that are used by Z Open Editor are stored in the zopeneditor.zowe settings along with other lower-level settings that deal with connecting to z/OS.
      IBM Z Open Editor will by default follow these precedence rules to identify which Zowe profile to use:
      1. Use the profile specified by the zopeneditor.zowe user setting.
      2. If no profile is defined in the user setting, then use the default RSE profile if available.
      3. If the default RSE profile is not available, then use the default z/OSMF profile if available. If the default z/OSMF profile is not defined, errors are shown.
       zopeneditor.zowe settings explained
      ',5),w=e("li",null,[e("p",null,[e("code",null,"defaultCliProfile"),o(": The value is the name of the Zowe RSE or z/OSMF profile that you want to use. If you cannot remember the names, you can find the profile name using Zowe Explorer GUI or run the following Zowe CLI commands to get the list of all your profiles and your default profile:")]),e("ul",null,[e("li",null,[o("List RSE profiles: "),e("code",null,"zowe profiles list rse")]),e("li",null,[o("List z/OSMF profiles: "),e("code",null,"zowe profiles list zosmf")])])],-1),b=e("li",null,[e("p",null,[e("code",null,"defaultSshCliProfile"),o(": The value is the name of the Zowe SSH profile that you want to use. Some functionalities offered by Z Open Editor may require a Zowe SSH profile to be specified.")])],-1),z=e("code",null,"defaultRseConversionMappingsFile",-1),y=o(": discussed in detail in the "),S=o("MVS EBCDIC code pages and mappings files"),v=o(" help section."),_=t("
    • listBeforeDownload: The value is boolean and modifies Z Open Editor's behavior when requesting a file from MVS:
      • When the setting is set to true, the editor will first try to confirm whether the requested file exists by performing a list operation for that file. If the requested file exists, the editor will send another request to download it. If the requested file does not exist, the editor will move on to test the next location listed in the property group.
      • When the setting is set to false, the editor will directly try to download the file from MVS without checking whether it exists. If the response from z/OS is a Not Found error, the editor will move on to the next location listed in the property group. In some cases when using z/OSMF as the protocol, this Not Found error will cause entries in z/OS log files, which you can avoid by specifying the value of the setting to true.
      This extra round trip to the server when set to true to check the existence will have a performance impact. Because the logging is not always an issue for all z/OSMF users and not an issue when using the RSE API protocol, and because of the performance advantage, the default value for this setting is false.
    • maximumParallelFileDownloads: The value can be used to specify how many parallel downloads Z Open Editor should perform when requesting include files from MVS. Downloading several files in parallel can significantly improve performance, especially when you edit programs with many include files. The downside is that some protocols such as z/OSMF will allocate more address spaces for the parallel requests, which causes more resources to be used and more logging on the z/OS side. The RSE API protocol does not have that problem because it achieves scalability in other ways that are outlined in the RSE documentation. The default value for this setting is 5, and the maximum value is 10. Set it to 1 to disable parallel downloads and request one include file at a time.
      • ",2),k=t(`
       Changing the Zowe Profile using VS Code settings
      The format of the zopeneditor.zowe user setting is as follows:
      "zopeneditor.zowe": {
   "defaultCliProfile": "mySandbox.rseapi",
   "defaultSshCliProfile": "mySandbox.ssh",
   "listBeforeDownload": false,
diff --git a/assets/interact_zos_zowe_explorer.html.ea329571.js b/assets/interact_zos_zowe_explorer.html.d2bc6dd2.js
similarity index 99%
rename from assets/interact_zos_zowe_explorer.html.ea329571.js
rename to assets/interact_zos_zowe_explorer.html.d2bc6dd2.js
index ca7d89f2f..b475236d3 100644
--- a/assets/interact_zos_zowe_explorer.html.ea329571.js
+++ b/assets/interact_zos_zowe_explorer.html.d2bc6dd2.js
@@ -1,4 +1,4 @@
-import{r,o as n,a as l,b as e,d as o,w as a,F as d,e as t,c}from"./app.f6cb3ed9.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";var p="/zopeneditor-about/assets/zowe-webviews-sample.73729aec.png";const u={},f=e("h1",{id:"using-the-zowe-explorer-views",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-the-zowe-explorer-views","aria-hidden":"true"},"#"),t(" Using the Zowe Explorer views")],-1),g=e("p",null,"You can use Zowe Explorer to graphically navigate to resources on z/OS using RSE API. When you have the Zowe Explorer VS Code extension installed, you can open the following three views by clicking the Zowe icon on the VS Code Activity bar to interact with z/OS resources:",-1),w=e("ul",null,[e("li",null,"DATA SETS view that shows your data sets and members and allows you to directly open, edit, and save your programs against MVS\u2122."),e("li",null,"UNIX SYSTEM SERVICES view that shows you z/OS UNIX System Services folders and files that you can also directly open, edit, and save."),e("li",null,"JOBS view that gives you access to your jobs and spool files.")],-1),m=t("See the "),b={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},S=t("documentation in the VS Code Marketplace"),y=t(" for details on using and configuring each view. More examples are available in the section "),v=e("a",{href:"#example-how-to-manipulate-data-sets-with-zowe-explorer"},"How to manipulate data sets with Zowe Explorer",-1),x=t(" and "),E=t("Submitting JCL to compile, link, and run jobs"),_=t(" sections."),k=e("p",null,"When you install IBM Z Open Editor from the VS Code marketplace into your VS Code, the latest version of Zowe Explorer is automatically co-installed.",-1),z=e("h2",{id:"setting-up-and-using-profiles-in-zowe-explorer",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#setting-up-and-using-profiles-in-zowe-explorer","aria-hidden":"true"},"#"),t(" Setting up and using profiles in Zowe Explorer")],-1),I=e("p",null,"To use Zowe Explorer, you must create an RSE or z/OSMF profile. You can also have multiple profiles of different types. For example, you can access one LPAR with z/OSMF and another with RSE API from within the same VS Code workspace using Zowe Explorer and IBM Z Open Editor. IBM Z Open Editor capabilities such as COBOL copybook or PL/I include file resolving is supported with both types of profiles.",-1),C=e("h3",{id:"setting-up-rse-profiles-for-zowe-explorer-and-ibm-z-open-editor",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#setting-up-rse-profiles-for-zowe-explorer-and-ibm-z-open-editor","aria-hidden":"true"},"#"),t(" Setting up RSE profiles for Zowe Explorer and IBM Z Open Editor")],-1),A=t("There are multiple ways to create and edit a team configuration file for connecting to z/OS. For a walk-through of steps on how to create profiles by using Zowe Explorer, see "),O=t("Connecting to z/OS with Zowe Explorer walk through"),R=e("h3",{id:"specifying-which-profile-to-use-in-ibm-z-open-editor",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#specifying-which-profile-to-use-in-ibm-z-open-editor","aria-hidden":"true"},"#"),t(" Specifying which profile to use in IBM Z Open Editor")],-1),T=t("You can use RSE profiles for IBM Z Open Editor operations. For example, if you edit a COBOL program and have defined "),Z=t("property groups"),M=t(" to dynamically retrieve contents of copybooks from MVS, then you can use your RSE profile for that access operation instead of the default z/OSMF CLI profile. The default precedence rules to identify which CLI profile to use are as follows:"),D=c(`
      1. Use the profile that is specified by the zopeneditor.zowe workspace settings.
      2. Use the profile that is specified by the zopeneditor.zowe user settings.
      3. If no profile was specified in the locations above or the specified name of these profiles could not be found, then use the default RSE profile if available.
      4. If the default RSE profile is not available, then use the default z/OSMF profile if available. If the default z/OSMF profile is not defined, errors are shown.
      The format of the zopeneditor.zowe user setting is as follows:
      "zopeneditor.zowe": {
+import{r,o as n,a as l,b as e,d as o,w as a,F as d,e as t,c}from"./app.daa93c96.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";var p="/zopeneditor-about/assets/zowe-webviews-sample.73729aec.png";const u={},f=e("h1",{id:"using-the-zowe-explorer-views",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-the-zowe-explorer-views","aria-hidden":"true"},"#"),t(" Using the Zowe Explorer views")],-1),g=e("p",null,"You can use Zowe Explorer to graphically navigate to resources on z/OS using RSE API. When you have the Zowe Explorer VS Code extension installed, you can open the following three views by clicking the Zowe icon on the VS Code Activity bar to interact with z/OS resources:",-1),w=e("ul",null,[e("li",null,"DATA SETS view that shows your data sets and members and allows you to directly open, edit, and save your programs against MVS\u2122."),e("li",null,"UNIX SYSTEM SERVICES view that shows you z/OS UNIX System Services folders and files that you can also directly open, edit, and save."),e("li",null,"JOBS view that gives you access to your jobs and spool files.")],-1),m=t("See the "),b={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},S=t("documentation in the VS Code Marketplace"),y=t(" for details on using and configuring each view. More examples are available in the section "),v=e("a",{href:"#example-how-to-manipulate-data-sets-with-zowe-explorer"},"How to manipulate data sets with Zowe Explorer",-1),x=t(" and "),E=t("Submitting JCL to compile, link, and run jobs"),_=t(" sections."),k=e("p",null,"When you install IBM Z Open Editor from the VS Code marketplace into your VS Code, the latest version of Zowe Explorer is automatically co-installed.",-1),z=e("h2",{id:"setting-up-and-using-profiles-in-zowe-explorer",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#setting-up-and-using-profiles-in-zowe-explorer","aria-hidden":"true"},"#"),t(" Setting up and using profiles in Zowe Explorer")],-1),I=e("p",null,"To use Zowe Explorer, you must create an RSE or z/OSMF profile. You can also have multiple profiles of different types. For example, you can access one LPAR with z/OSMF and another with RSE API from within the same VS Code workspace using Zowe Explorer and IBM Z Open Editor. IBM Z Open Editor capabilities such as COBOL copybook or PL/I include file resolving is supported with both types of profiles.",-1),C=e("h3",{id:"setting-up-rse-profiles-for-zowe-explorer-and-ibm-z-open-editor",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#setting-up-rse-profiles-for-zowe-explorer-and-ibm-z-open-editor","aria-hidden":"true"},"#"),t(" Setting up RSE profiles for Zowe Explorer and IBM Z Open Editor")],-1),A=t("There are multiple ways to create and edit a team configuration file for connecting to z/OS. For a walk-through of steps on how to create profiles by using Zowe Explorer, see "),O=t("Connecting to z/OS with Zowe Explorer walk through"),R=e("h3",{id:"specifying-which-profile-to-use-in-ibm-z-open-editor",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#specifying-which-profile-to-use-in-ibm-z-open-editor","aria-hidden":"true"},"#"),t(" Specifying which profile to use in IBM Z Open Editor")],-1),T=t("You can use RSE profiles for IBM Z Open Editor operations. For example, if you edit a COBOL program and have defined "),Z=t("property groups"),M=t(" to dynamically retrieve contents of copybooks from MVS, then you can use your RSE profile for that access operation instead of the default z/OSMF CLI profile. The default precedence rules to identify which CLI profile to use are as follows:"),D=c(`
      1. Use the profile that is specified by the zopeneditor.zowe workspace settings.
      2. Use the profile that is specified by the zopeneditor.zowe user settings.
      3. If no profile was specified in the locations above or the specified name of these profiles could not be found, then use the default RSE profile if available.
      4. If the default RSE profile is not available, then use the default z/OSMF profile if available. If the default z/OSMF profile is not defined, errors are shown.
      The format of the zopeneditor.zowe user setting is as follows:
      "zopeneditor.zowe": {
     "defaultCliProfile": "rseCLI",
 },
 
      The value of defaultCliProfile is the name of the CLI profile that you specified in the create statement above.
      If you have v2 profiles in place and cannot remember the names, then you can run this command to get the information of all your profiles in the team configuration file:
      zowe config list
diff --git a/assets/introduction.html.1ba0e870.js b/assets/introduction.html.a978a099.js
similarity index 99%
rename from assets/introduction.html.1ba0e870.js
rename to assets/introduction.html.a978a099.js
index 92099c1e0..006635431 100644
--- a/assets/introduction.html.1ba0e870.js
+++ b/assets/introduction.html.a978a099.js
@@ -1 +1 @@
-import{r,o as a,a as l,b as e,d as t,w as s,F as d,e as o,c}from"./app.f6cb3ed9.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";const p={},u=e("h1",{id:"introduction",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#introduction","aria-hidden":"true"},"#"),o(" Introduction")],-1),_=o("IBM Z\xAE Open Editor is an extension for Visual Studio Code that provides language support for the IBM\xAE Enterprise "),g={href:"https://www.ibm.com/docs/en/cobol-zos/6.4",target:"_blank",rel:"noopener noreferrer"},f=o("COBOL 6.4"),m=o(", "),b={href:"https://www.ibm.com/docs/en/epfz/6.1",target:"_blank",rel:"noopener noreferrer"},w=o("PL/I 6.1"),v=o(", "),y={href:"https://www.ibm.com/docs/en/hla-and-tf/1.6",target:"_blank",rel:"noopener noreferrer"},S=o("High Level Assembler for z/OS 3.1"),k=o(", "),L={href:"https://www.ibm.com/docs/en/zos/3.1.0?topic=tsoe-zos-rexx-users-guide",target:"_blank",rel:"noopener noreferrer"},B=o("z/OS TSO/E REXX"),O=o(", and "),C={href:"https://www.ibm.com/docs/en/SSLTBW_3.1.0/pdf/ieab600_v3r1.pdf",target:"_blank",rel:"noopener noreferrer"},x=o("z/OS MVS JCL (Job Control Language)"),I=o(" programming languages for z/OS\xAE. This also includes capabilities for embedded statements for CICS 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."),E=o("The extension realizes its language support by implementing fully functional "),M={href:"https://langserver.org/",target:"_blank",rel:"noopener noreferrer"},z=o("language servers"),P=o(" together with additional editor enhancements that enable mainframe developers to utilize features such as:"),V=c("
      • Real-time syntax checking and highlighting while you type
      • Problems view with all syntax errors and (in COBOL) unreachable code
      • Outline view and outline search
      • For both variables and paragraphs: 
        • Declaration hovers
        • Peek definition
        • Go to definition
        • Find all references
      • Code and variable completion
      • Finding and navigating references
      • Previewing of copybooks and include files
      • Navigate to copybooks and include files
      • Refactoring such as "rename symbol"
      • Custom code snippet support and more than 200 example code snippets out of the box
      • Search and replace refactoring across multiple program files
      Notes:
      ",2),F=e("li",null,"For HLASM, a significant subset of the capabilities that are available for COBOL and PL/I are supported.",-1),D=e("li",null,"For REXX, a smaller subset of the capabilities are supported",-1),Z=o("For "),A={href:"https://www.ibm.com/docs/en/zos-basic-skills?topic=sdsf-what-is-jcl",target:"_blank",rel:"noopener noreferrer"},R=o("Job Control Language (JCL)"),X=o(" and job spool files, IBM Z Open Editor provides syntax highlighting. "),T=e("ul",null,[e("li",null,"For JCL, we now have added features such as an Outline view, real-time syntax checking, and code completion.")],-1),H=o("For a list of the enabled LSP features and in-progress features, see "),N=o("Known issues and limitations"),U=o("."),J=e("h2",{id:"key-capabilities",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#key-capabilities","aria-hidden":"true"},"#"),o(" Key Capabilities")],-1),Y=e("p",null,"These are the key features and benefits of IBM Z Open Editor:",-1),W=e("li",null,[e("p",null,"Modern editing experience for COBOL, PL/I, HLASM, and REXX development"),e("p",null,"IBM Z Open Editor is available as an extension for Visual Studio Code (VS Code), which is becoming the most popular development environment according to recent surveys. With so many current and next generation developers having experience with VS Code, IBM Enterprise language support in VS Code makes enterprise programming more attractive and productive by allowing developers to use this popular editor, with the option to integrate numerous other extensions from the VS Code Marketplace.")],-1),j=e("p",null,"Full language support via the Language Server Protocol (LSP)",-1),q=o("The extension supports many COBOL, PL/I, HLASM, and REXX capabilities that were not available in traditional editing environments such as "),G={href:"https://www.ibm.com/docs/en/zos-basic-skills?topic=ispf-editor",target:"_blank",rel:"noopener noreferrer"},K=o("ISPF"),Q=o(", by providing "),$={href:"https://langserver.org/",target:"_blank",rel:"noopener noreferrer"},ee=o("Language Server Protocol"),oe=o(" implementations. See above for the list of key features. Although supported by many other editors now, the Language Server Protocol was specifically created for VS Code and therefore is a good way for providing language support in the editor."),te=e("li",null,[e("p",null,"Extended language server capabilities for more productivity"),e("p",null,[o("In addition to the capabilities specified in the Language Server Protocol, the implementation is extended with more capabilities that are useful to enterprise developers. For example, you can use hovers for COBOL "),e("code",null,"COPY"),o(", PL/I "),e("code",null,"%INCLUDE"),o(", and HLASM "),e("code",null,"COPY"),o(" statements to preview the contents of the copybooks without opening in separate editor tabs and navigating away from your current editing position.")])],-1),ne=e("p",null,"Integration with modern Software Configuration Management (SCM)",-1),ie=o("Even if your organization does not standardize on an SCM, using the Git that is integrated in VS Code or using popular extensions such as "),se={href:"https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens",target:"_blank",rel:"noopener noreferrer"},re=o("GitLens"),ae=o(` locally in a workspace will boost your productivity. You can work on COBOL, PL/I, HLASM, and REXX programs on your local workspace and snapshot work at any point, go back or branch into alternative explorations, merge your or your colleagues' branches back in, or revert to any earlier state of your code in a flash. Use side-by-side views and "blame" annotations to explore the changes between snapshots, how they looked before, and the time of changes. See exactly for each line when it was last changed and by whom. Explore the entire history of all changes for a specific file or all files in your workspace in a chronological history viewer.`),le=e("p",null,"z/OS interactions using the open source Zowe clients",-1),de=o("If you have z/OSMF or "),ce=o("IBM Remote System Explorer API (RSE API)"),he=o(" configured, you can use "),pe={href:"https://docs.zowe.org/stable/user-guide/cli-using-usingcli",target:"_blank",rel:"noopener noreferrer"},ue=o("Zowe CLI"),_e=o(", the "),ge={href:"https://docs.zowe.org/stable/user-guide/ze-install.html",target:"_blank",rel:"noopener noreferrer"},fe=o("Zowe Explorer VS Code Extension (Zowe Explorer)"),me=o(", or both, to load and edit your files directly from z/OS or download them into your local workspace and then upload the changed files into the same or new data sets to compile and run your application. You can do all of these operations from IBM Z Open Editor directly with right-clicks and dialog interactions, and perform command-line operations using the VS Code Terminal view that integrates right below your editor, giving you one central view to everything."),be=e("p",null,"After configuration, IBM Z Open Editor can also take advantage of the Zowe CLI protocol for resolving dependencies over the network. For example, you can edit your COBOL programs locally, but resolve copybook dependencies directly out of MVS\u2122 using the same Zowe connections.",-1),we=e("p",null,"IBM User Build",-1),ve=o("IBM User Build allows z/OS developers who have the IBM Dependency Based Build (DBB) host component to run user builds right from their local integrated development environment (IDE). With the User Build setting enabled in your IDE, you can access IBM User Build options simply by right-clicking inside a COBOL, PL/I, or HLASM file. Refer to the "),ye={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-setting-up-user-build",target:"_blank",rel:"noopener noreferrer"},Se=o("full IBM User Build documentation"),ke=o(" to learn more about how to leverage User Build."),Le=e("p",null,"Enterprise-level advanced capabilities",-1),Be=o("IBM Z Open Editor v4 introduces advanced capabilities for enterprise-level development use cases that go beyond programming and simple z/OS Resources access. You would typically find such features in IBM's commercial zDevOps solutions such as IBM Developer for z/OS Enterprise Edition (IDzEE). These are at the moment preprocessor support for COBOL, a new Web view built on top of Zowe Explorer that displays z/OS resources such as data sets, unix files and jobs in a sortable table, custom HLASM macro support and a new DBB user build VS Code Problems view integration. Find a detailed exploration of these features in the "),Oe=o("Advanced Capabilities"),Ce=o(" section.");function xe(Ie,Ee){const n=r("ExternalLinkIcon"),i=r("RouterLink");return a(),l(d,null,[u,e("p",null,[_,e("a",g,[f,t(n)]),m,e("a",b,[w,t(n)]),v,e("a",y,[S,t(n)]),k,e("a",L,[B,t(n)]),O,e("a",C,[x,t(n)]),I]),e("p",null,[E,e("a",M,[z,t(n)]),P]),V,e("ul",null,[F,D,e("li",null,[Z,e("a",A,[R,t(n)]),X,T])]),e("p",null,[H,t(i,{to:"/Docs/knownissues.html"},{default:s(()=>[N]),_:1}),U]),J,Y,e("ul",null,[W,e("li",null,[j,e("p",null,[q,e("a",G,[K,t(n)]),Q,e("a",$,[ee,t(n)]),oe])]),te,e("li",null,[ne,e("p",null,[ie,e("a",se,[re,t(n)]),ae])]),e("li",null,[le,e("p",null,[de,t(i,{to:"/Docs/setup_integration.html#installing-the-requisite-ibm-rse-api-z-os-host-component"},{default:s(()=>[ce]),_:1}),he,e("a",pe,[ue,t(n)]),_e,e("a",ge,[fe,t(n)]),me]),be]),e("li",null,[we,e("p",null,[ve,e("a",ye,[Se,t(n)]),ke])]),e("li",null,[Le,e("p",null,[Be,t(i,{to:"/Docs/advanced_overview.html"},{default:s(()=>[Oe]),_:1}),Ce])])])],64)}var Pe=h(p,[["render",xe]]);export{Pe as default};
+import{r,o as a,a as l,b as e,d as t,w as s,F as d,e as o,c}from"./app.daa93c96.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";const p={},u=e("h1",{id:"introduction",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#introduction","aria-hidden":"true"},"#"),o(" Introduction")],-1),_=o("IBM Z\xAE Open Editor is an extension for Visual Studio Code that provides language support for the IBM\xAE Enterprise "),g={href:"https://www.ibm.com/docs/en/cobol-zos/6.4",target:"_blank",rel:"noopener noreferrer"},f=o("COBOL 6.4"),m=o(", "),b={href:"https://www.ibm.com/docs/en/epfz/6.1",target:"_blank",rel:"noopener noreferrer"},w=o("PL/I 6.1"),v=o(", "),y={href:"https://www.ibm.com/docs/en/hla-and-tf/1.6",target:"_blank",rel:"noopener noreferrer"},S=o("High Level Assembler for z/OS 3.1"),k=o(", "),L={href:"https://www.ibm.com/docs/en/zos/3.1.0?topic=tsoe-zos-rexx-users-guide",target:"_blank",rel:"noopener noreferrer"},B=o("z/OS TSO/E REXX"),O=o(", and "),C={href:"https://www.ibm.com/docs/en/SSLTBW_3.1.0/pdf/ieab600_v3r1.pdf",target:"_blank",rel:"noopener noreferrer"},x=o("z/OS MVS JCL (Job Control Language)"),I=o(" programming languages for z/OS\xAE. This also includes capabilities for embedded statements for CICS 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."),E=o("The extension realizes its language support by implementing fully functional "),M={href:"https://langserver.org/",target:"_blank",rel:"noopener noreferrer"},z=o("language servers"),P=o(" together with additional editor enhancements that enable mainframe developers to utilize features such as:"),V=c("
      • Real-time syntax checking and highlighting while you type
      • Problems view with all syntax errors and (in COBOL) unreachable code
      • Outline view and outline search
      • For both variables and paragraphs: 
        • Declaration hovers
        • Peek definition
        • Go to definition
        • Find all references
      • Code and variable completion
      • Finding and navigating references
      • Previewing of copybooks and include files
      • Navigate to copybooks and include files
      • Refactoring such as "rename symbol"
      • Custom code snippet support and more than 200 example code snippets out of the box
      • Search and replace refactoring across multiple program files
      Notes:
      ",2),F=e("li",null,"For HLASM, a significant subset of the capabilities that are available for COBOL and PL/I are supported.",-1),D=e("li",null,"For REXX, a smaller subset of the capabilities are supported",-1),Z=o("For "),A={href:"https://www.ibm.com/docs/en/zos-basic-skills?topic=sdsf-what-is-jcl",target:"_blank",rel:"noopener noreferrer"},R=o("Job Control Language (JCL)"),X=o(" and job spool files, IBM Z Open Editor provides syntax highlighting. "),T=e("ul",null,[e("li",null,"For JCL, we now have added features such as an Outline view, real-time syntax checking, and code completion.")],-1),H=o("For a list of the enabled LSP features and in-progress features, see "),N=o("Known issues and limitations"),U=o("."),J=e("h2",{id:"key-capabilities",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#key-capabilities","aria-hidden":"true"},"#"),o(" Key Capabilities")],-1),Y=e("p",null,"These are the key features and benefits of IBM Z Open Editor:",-1),W=e("li",null,[e("p",null,"Modern editing experience for COBOL, PL/I, HLASM, and REXX development"),e("p",null,"IBM Z Open Editor is available as an extension for Visual Studio Code (VS Code), which is becoming the most popular development environment according to recent surveys. With so many current and next generation developers having experience with VS Code, IBM Enterprise language support in VS Code makes enterprise programming more attractive and productive by allowing developers to use this popular editor, with the option to integrate numerous other extensions from the VS Code Marketplace.")],-1),j=e("p",null,"Full language support via the Language Server Protocol (LSP)",-1),q=o("The extension supports many COBOL, PL/I, HLASM, and REXX capabilities that were not available in traditional editing environments such as "),G={href:"https://www.ibm.com/docs/en/zos-basic-skills?topic=ispf-editor",target:"_blank",rel:"noopener noreferrer"},K=o("ISPF"),Q=o(", by providing "),$={href:"https://langserver.org/",target:"_blank",rel:"noopener noreferrer"},ee=o("Language Server Protocol"),oe=o(" implementations. See above for the list of key features. Although supported by many other editors now, the Language Server Protocol was specifically created for VS Code and therefore is a good way for providing language support in the editor."),te=e("li",null,[e("p",null,"Extended language server capabilities for more productivity"),e("p",null,[o("In addition to the capabilities specified in the Language Server Protocol, the implementation is extended with more capabilities that are useful to enterprise developers. For example, you can use hovers for COBOL "),e("code",null,"COPY"),o(", PL/I "),e("code",null,"%INCLUDE"),o(", and HLASM "),e("code",null,"COPY"),o(" statements to preview the contents of the copybooks without opening in separate editor tabs and navigating away from your current editing position.")])],-1),ne=e("p",null,"Integration with modern Software Configuration Management (SCM)",-1),ie=o("Even if your organization does not standardize on an SCM, using the Git that is integrated in VS Code or using popular extensions such as "),se={href:"https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens",target:"_blank",rel:"noopener noreferrer"},re=o("GitLens"),ae=o(` locally in a workspace will boost your productivity. You can work on COBOL, PL/I, HLASM, and REXX programs on your local workspace and snapshot work at any point, go back or branch into alternative explorations, merge your or your colleagues' branches back in, or revert to any earlier state of your code in a flash. Use side-by-side views and "blame" annotations to explore the changes between snapshots, how they looked before, and the time of changes. See exactly for each line when it was last changed and by whom. Explore the entire history of all changes for a specific file or all files in your workspace in a chronological history viewer.`),le=e("p",null,"z/OS interactions using the open source Zowe clients",-1),de=o("If you have z/OSMF or "),ce=o("IBM Remote System Explorer API (RSE API)"),he=o(" configured, you can use "),pe={href:"https://docs.zowe.org/stable/user-guide/cli-using-usingcli",target:"_blank",rel:"noopener noreferrer"},ue=o("Zowe CLI"),_e=o(", the "),ge={href:"https://docs.zowe.org/stable/user-guide/ze-install.html",target:"_blank",rel:"noopener noreferrer"},fe=o("Zowe Explorer VS Code Extension (Zowe Explorer)"),me=o(", or both, to load and edit your files directly from z/OS or download them into your local workspace and then upload the changed files into the same or new data sets to compile and run your application. You can do all of these operations from IBM Z Open Editor directly with right-clicks and dialog interactions, and perform command-line operations using the VS Code Terminal view that integrates right below your editor, giving you one central view to everything."),be=e("p",null,"After configuration, IBM Z Open Editor can also take advantage of the Zowe CLI protocol for resolving dependencies over the network. For example, you can edit your COBOL programs locally, but resolve copybook dependencies directly out of MVS\u2122 using the same Zowe connections.",-1),we=e("p",null,"IBM User Build",-1),ve=o("IBM User Build allows z/OS developers who have the IBM Dependency Based Build (DBB) host component to run user builds right from their local integrated development environment (IDE). With the User Build setting enabled in your IDE, you can access IBM User Build options simply by right-clicking inside a COBOL, PL/I, or HLASM file. Refer to the "),ye={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-setting-up-user-build",target:"_blank",rel:"noopener noreferrer"},Se=o("full IBM User Build documentation"),ke=o(" to learn more about how to leverage User Build."),Le=e("p",null,"Enterprise-level advanced capabilities",-1),Be=o("IBM Z Open Editor v4 introduces advanced capabilities for enterprise-level development use cases that go beyond programming and simple z/OS Resources access. You would typically find such features in IBM's commercial zDevOps solutions such as IBM Developer for z/OS Enterprise Edition (IDzEE). These are at the moment preprocessor support for COBOL, a new Web view built on top of Zowe Explorer that displays z/OS resources such as data sets, unix files and jobs in a sortable table, custom HLASM macro support and a new DBB user build VS Code Problems view integration. Find a detailed exploration of these features in the "),Oe=o("Advanced Capabilities"),Ce=o(" section.");function xe(Ie,Ee){const n=r("ExternalLinkIcon"),i=r("RouterLink");return a(),l(d,null,[u,e("p",null,[_,e("a",g,[f,t(n)]),m,e("a",b,[w,t(n)]),v,e("a",y,[S,t(n)]),k,e("a",L,[B,t(n)]),O,e("a",C,[x,t(n)]),I]),e("p",null,[E,e("a",M,[z,t(n)]),P]),V,e("ul",null,[F,D,e("li",null,[Z,e("a",A,[R,t(n)]),X,T])]),e("p",null,[H,t(i,{to:"/Docs/knownissues.html"},{default:s(()=>[N]),_:1}),U]),J,Y,e("ul",null,[W,e("li",null,[j,e("p",null,[q,e("a",G,[K,t(n)]),Q,e("a",$,[ee,t(n)]),oe])]),te,e("li",null,[ne,e("p",null,[ie,e("a",se,[re,t(n)]),ae])]),e("li",null,[le,e("p",null,[de,t(i,{to:"/Docs/setup_integration.html#installing-the-requisite-ibm-rse-api-z-os-host-component"},{default:s(()=>[ce]),_:1}),he,e("a",pe,[ue,t(n)]),_e,e("a",ge,[fe,t(n)]),me]),be]),e("li",null,[we,e("p",null,[ve,e("a",ye,[Se,t(n)]),ke])]),e("li",null,[Le,e("p",null,[Be,t(i,{to:"/Docs/advanced_overview.html"},{default:s(()=>[Oe]),_:1}),Ce])])])],64)}var Pe=h(p,[["render",xe]]);export{Pe as default};
diff --git a/assets/knownissues.html.648ac969.js b/assets/knownissues.html.648ac969.js
new file mode 100644
index 000000000..a0104f465
--- /dev/null
+++ b/assets/knownissues.html.648ac969.js
@@ -0,0 +1,2 @@
+import{r as a,o as l,a as d,b as e,d as i,w as r,F as c,e as o,c as n}from"./app.daa93c96.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";const u={},p=e("h1",{id:"known-issues-and-limitations",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#known-issues-and-limitations","aria-hidden":"true"},"#"),o(" Known issues and limitations")],-1),f=o("The IBM Z\xAE Open Editor extension has some known issues and limitations. This page provides the status of the current release. Also review the list of open issues and enhancement requests in our "),m={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},g=o("Github repository"),b=o(". It might list issues that are not yet documented here."),_=n('
       Java\u2122 11 64-Bit JRE or SDK required
      If the right version of Java cannot be found in the current user's path or if no JAVA_HOME environment variable was defined, you might see error messages in the Output view of VS Code. Such errors could also be caused by other reasons such as not enough free memory for Java on your system.
      Go through all the steps described in the Getting Started page for configuring Java to try out different options.
       Java not found on Linux
      Z Open Editor starts by searching for Java in the following locations:
      • The path specified by the zopeneditor.JAVA_HOME value in your VS Code settings.
      • The path specified by the java.jdt.ls.java.home value in your VS Code settings.
      • The path specified by your JAVA_HOME environment variable.
      After searching these locations, Z Open Editor will run commands to try and find Java on your operating system.
      ',7),w=o("If your installation is not found and you see errors in the Welcome page, try specifying a path to your Java for your "),y=e("code",null,"zopeneditor.JAVA_HOME",-1),v=o(" or "),S=e("code",null,"java.jdt.ls.java.home",-1),k=o(" value in your VS Code settings or setting your system's "),C=e("code",null,"JAVA_HOME",-1),x=o(" environment variable. Ensure that you exclude the "),I=e("code",null,"bin/java",-1),L=o(" directory from your path. For more information, see "),O=o("Configuring Java"),E=o("."),B=n('
       Resetting Language Servers or VS Code
      It might happen that the language servers provided by IBM Z Open Editor become inconsistent and do not behave as expected. For example, a language server might stop reporting syntax errors, or it cannot resolve copybooks anymore. Instead of quitting and restarting VS Code completely, you can try pressing the F1 key and type the following commands to reset one or more language servers.
      • IBM Z Open Editor: Pause the COBOL Language Server: Stops the COBOL language server and restarts it when you open a COBOL file again.
      • IBM Z Open Editor: Pause the PL/I Language Server: Stops the PL/I language server and restarts it when you open a PL/I file again.
      • IBM Z Open Editor: Pause the Assembler Language Server: Stops the HLASM language server and restarts it when you open an HLASM file again.
      • IBM Z Open Editor: Pause the REXX Language Server: Stops the REXX language server and restarts it when you open a REXX file again.
      • IBM Z Open Editor: Pause the JCL Language Server: Stops the JCL language server and restarts it when you open a JCL file again.
      • IBM Z Open Editor: Reload Zowe Profiles: If you have changed the password of your Zowe CLI profile that is used to load your remote include files such as copybooks, you need to run this command to refresh the Zowe profile.
      • Developer: Reload Window: Restarts the current VS Code window and all of its extensions. If you have many editor windows open at the same time, you can use this command to reset just the current window in which you run the command.
       Limitations for Visual Studio Code Multi-Root Workspaces
      ',4),z=o("IBM Z\xAE Open Editor supports "),A={href:"https://code.visualstudio.com/docs/editor/multi-root-workspaces",target:"_blank",rel:"noopener noreferrer"},M=o("VS Code multi-root workspaces"),P=o(", but there are some limits or special rules on how ZAPP files and settings are used in a multi-root workspace:"),T=e("li",null,[o("Property Groups: the multi-root workspace can load multiple zapp files located in the top-dir of each workspace. We search for property groups in each of these zapp files in the order the workspaces are listed in the "),e("code",null,".code-workspace .code-workspace"),o(" file when resolving include files.")],-1),R=e("li",null,"For user build the DBB ZAPP profile located in the workspace of the program being built is being used. The application-conf files (additional files listed in zapp profile) also need to be in the root of the workspace with the program.",-1),N=o("For "),Z={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-building-cobol-pli-hlasm-programs-user-build",target:"_blank",rel:"noopener noreferrer"},D=o("Z Open Editor's user build"),F=o(", local copybooks and include files that need to be uploaded to z/OS UNIX System Services for build can be located in any other workspace of the multi-root workspace. The location of the copybooks and include files must be specified in the ZAPP file of the workspace in which these include files are located in. A ZAPP file cannot provide property groups that point to locations outside of its workspace. The exception would be using absolute path names, but those might break the ability to share the ZAPP file with other team members as they might have their files in different locations."),H=e("h2",{id:"limitations-of-using-z-open-editor-with-eclipse-che-and-red-hat-openshift-dev-spaces",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#limitations-of-using-z-open-editor-with-eclipse-che-and-red-hat-openshift-dev-spaces","aria-hidden":"true"},"#"),o(" Limitations of using Z Open Editor with Eclipse Che and Red Hat OpenShift Dev Spaces")],-1),X=e("p",null,"Almost all capabilities described in this documentation are available when you use IBM Z Open Editor with Eclipse Che or Red Hat OpenShift Dev Spaces. However, note the following limitations.",-1),V=o("Zowe CLI secure credentials are currently not supported with Z Open Editor on Eclipse Che and Red Hat OpenShift Dev Spaces. The Zowe Explorer setting "),j=e("code",null,'"zowe.security.secureCredentialsEnabled": false',-1),J=o(" must be used in these environments. See the section "),U=o("Setting up integrations to interact with z/OS > Managing credentials unsecured"),q=o("."),W=e("li",null,[e("p",null,[o("Path names specified for property groups in ZAPP files are always case-sensitive, even if the setting "),e("code",null,'"zopeneditor.enforceCaseSensitiveIncludeFileNames"'),o(" is set to "),e("code",null,"false"),o(". However, this setting works for the file names that get matched in the folders that match the property groups.")])],-1),G=n('
       Language-specific features and limitations
       COBOL
      The following lists show the implementation status of the COBOL language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.
       Enabled features of COBOL program files
      ',4),Y=n("
    • Syntax highlighting
    • Syntax errors
    • Document highlighting
    • Hover
    • Go to declaration
    • Find all references in file and across the multiple files
    • Peek references in file and across the multiple files
    • Rename symbol in file and across the multiple files
    • Outline view
    • Code completion
    • Snippets
    • Copybook resolving and copybook hover support
    • Document link support to open copybook by using Ctrl+Click (Windows) or Cmd+Click (Mac)
    • Embedded languages support such as SQL, CICS\xAE, and DLI
    • Renumber and Unnumber sequence numbers
    • Syntax highlighting support for Sequence Numbers (1-6 and 73-80 columns)
      • ",16),K=o("Latest COBOL 6.4 PTF language support, up to and including the "),Q={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/dan-zhang1/2024/02/26/february-2024-documentation-refresh-for-enterprise",target:"_blank",rel:"noopener noreferrer"},$=o("February 2024 PTF"),ee=o("."),oe={href:"https://www.ibm.com/docs/en/cics-ts/beta?topic=whats-new",target:"_blank",rel:"noopener noreferrer"},ie=o("Embedded Language Support for CICS 6.2 in COBOL"),te=o("COBOL "),ne={href:"https://www.ibm.com/docs/en/cobol-zos/6.4?topic=applications-using-user-defined-functions",target:"_blank",rel:"noopener noreferrer"},se=o("User defined functions"),re=o(" support including "),ae={href:"https://www.ibm.com/docs/en/cobol-zos/6.4?topic=applications-using-function-prototypes",target:"_blank",rel:"noopener noreferrer"},le=o("function prototypes"),de=e("li",null,"Code folding",-1),ce=e("h4",{id:"limitations-of-cobol-program-files",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#limitations-of-cobol-program-files","aria-hidden":"true"},"#"),o(" Limitations of COBOL program files")],-1),he=o("False unreachable code warnings: In some cases, the editor incorrectly reports that code is unreachable when more than one entry point is present. One such case is reported in "),ue={href:"https://github.com/IBM/zopeneditor-about/issues/212",target:"_blank",rel:"noopener noreferrer"},pe=o("this issue"),fe=o(". You can use a user setting to disable warnings for unreachable code completely as described in "),me=o("Enabling and disabling unreachable COBOL code warnings"),ge=o("."),be=o("Incomplete support for conditional compilation: Our community has reported various "),_e={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},we=o("issues"),ye=o(" when programs contain conditional compilation statements. These types of programs are currently not fully supported."),ve=e("li",null,[o("For COBOL programs that load a large number of copybooks from MVS, downloading can take a long time. Consider as a workaround the user setting "),e("code",null,'"zowe.files.temporaryDownloadsFolder.cleanup": false'),o(" that will not re-download the files between editing sessions.")],-1),Se=n('
       Enabled features of COBOL copybook files
      • Syntax errors
      • Find all references in file
      • Peek references in file
      • Rename symbol in file
      • Outline view
      • Syntax highlighting
      • Code completion
      • Snippets
      • Embedded languages support such as SQL, CICS, and DLI
       Limitations of COBOL copybook files
      • No support for Hover
      • No support for Go to declaration
      • No support for Find all references across the multiple files
      • No support for Peek references across the multiple files
      • No support for Rename symbol from a copybook to the files that include it
       PL/I
      The following lists show the implementation status of the PL/I language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.
       Enabled features of PL/I program files
      ',7),ke=n("
    • Syntax highlighting
    • Syntax errors
    • Document highlighting
    • Hover
    • Go to declaration
    • Find all references in file and across the multiple files
    • Peek references in file and across the multiple files
    • Rename symbol in file and across the multiple files
    • Outline view
    • Code completion
    • Include file resolving and include file hover support
    • Document link support to open include file by using Ctrl+Click (Windows) or Cmd+Click (Mac)
    • Embedded languages support such as SQL, CICS, and DLI
      • ",13),Ce=e("code",null,"*process",-1),xe=o(" (or "),Ie=e("code",null,"%process",-1),Le=o(") compile options statements, such as: "),Oe=e("li",null,[e("code",null,"*process source MARGINS(2,120);")],-1),Ee=e("li",null,[e("code",null,"*process SYSTEM(CIS, DB2);")],-1),Be=e("li",null,[e("code",null,"*process LIST TEST;")],-1),ze=o("Syntax and other supported compiler options can be found in: "),Ae={href:"https://www.ibm.com/docs/en/epfz/5.3?topic=directives-process-directive",target:"_blank",rel:"noopener noreferrer"},Me=o("%PROCESS directive"),Pe={href:"https://www.ibm.com/docs/en/epfz/5.3?topic=facilities-compile-time-option-descriptions",target:"_blank",rel:"noopener noreferrer"},Te=o("Compile-time option descriptions"),Re=o("Commenting and uncommenting PL/I code"),Ne=o("Latest Pl/I 6.1 PTF language support, up to and including the "),Ze={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/di-hu1/2024/01/31/january-2024-documentation-refresh-for-enterprise",target:"_blank",rel:"noopener noreferrer"},De=o("January 2024 PTF"),Fe=o("."),He={href:"https://www.ibm.com/docs/en/cics-ts/beta?topic=whats-new",target:"_blank",rel:"noopener noreferrer"},Xe=o("Embedded Language Support for CICS 6.2 Beta version in PL/I"),Ve=n('
       Limitations of PL/I program files
      • No support for macros
      • The left margin is currently not fully configurable. The minimum value required is 2.
      • PL/I 6.1 
        • No support is included for the MAXRUNONIF compiler option.
        • No support is included for the PROCINC directive. An alternative way to accomplish the purpose of the PROCINC directive is to use the PROCESS directive with the compiler option from the data set that you want to add for the PROCINC directive.
      • For PL/I programs that load a large number of include files from MVS, downloading can take a long time. Consider as a workaround the user setting "zowe.files.temporaryDownloadsFolder.cleanup": false that will not re-download the files between editing sessions.
      The following legal PL/I syntactic constructions are marked as errors:
      • Invalid PL/I syntax in macro preprocessor input when the macro preprocessor output is legal PL/I
      • Labels on preprocessor directives
      • Entry constants
      • Type functions
      • Factoring of attributes when you declare structures
      • An isub option with defined attribute
      • A tstack attribute of the attach statement
      • Implicit variable declarations
      The following invalid PL/I syntactic constructions are not marked as errors:
      • Condition prefixes for do statements
      • Label prefixes for declare, default, when, otherwise, and on statements
      • Scaling factors for float or fixed
      • Duplicate attributes for declaration statements
      • Syntax errors in macro preprocessor output
       Enabled features of PL/I include files
      • Syntax errors (lexing and parsing)
      • Find all references in file
      • Peek references in file
      • Rename symbol in file
      • Outline view
      • Syntax highlighting
      • Code completion
      • Embedded languages support such as SQL, CICS, and DLI
       Limitations of PL/I include files
      • No support for showing syntax errors for resolving variables
      • No support for Hover
      • No support for Go to declaration
      • No support for Find all references across the multiple files
      • No support for Peek references across the multiple files
      • No support for Rename symbol across the multiple files
       HLASM
      The following lists show the implementation status of the HLASM language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.
       Enabled features of HLASM program files
      ',13),je=n("
    • Syntax highlighting
    • Syntax errors, which currently only include the following: 
      • Copy statements not resolved
      • Spaces in continuation line
      • Invalid number of operands
    • Document highlighting
    • Hover on operations and operands
    • Go to declaration for all operands, including those from copy members
    • Find all references in file
    • Peek references in file
    • Outline view for macros, CSECTs, and DSECTs
    • Code completion, including snippet-style completion for operations and macros
    • Copy member file resolving and copy member file hover support
    • SYS1.MACLIB Macro remote file resolving and content hover support 
      • The z/OS version for SYS1.MACLIB is configurable between 2.4, 2.5, and 3.1 with the user setting "zopeneditor.hlasm.zosMacrosVersion".
    • Custom Macro file resolving, code completion, and content hover support for local macros.
    • Document link support to open copybook file by using Ctrl+Click (Windows) or Cmd+Click (Mac)
    • Quick fix hints for lines that are too long and spaces in the continuation line
      • ",14),Je=o("Commenting and uncommenting HLASM code"),Ue=n('
       Limitations of HLASM program files
      • Limited syntax checks such as no errors for undeclared variables
      • Syntax highlighting limitations on multi-line strings
      • Syntax highlighting limitations on non-continuation lines that begin at column 16
      • Syntax highlighting does not recognize continuation lines that begin at column 17 and later as comments
      • Keyword based HLASM code folding: Currently VS Code default code folding is based on indentation levels, not keywords.
      • Custom Macro file resolving is not currently available for remote macros.
       REXX
      The following lists show the implementation status of the REXX language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.
       Enabled features of REXX program files
      ',5),qe=e("li",null,"Syntax highlighting",-1),We=e("li",null,"Syntax errors",-1),Ge=e("li",null,"Hover",-1),Ye=e("li",null,"Find all references",-1),Ke=e("li",null,"Outline view",-1),Qe=e("li",null,"Code completion",-1),$e=e("li",null,"Include control directive resolution and hover support",-1),eo=e("li",null,"Syntax Highlighting for Include control directives",-1),oo=o("Commenting and uncommenting REXX code"),io=n('
       Limitations of REXX program files
      • No support for the 'END' keyword as a variable
      • No support for embedded languages
      • Code Completion and Hover do not support keywords that are not keyword instructions
      • Some color themes may not highlight all symbols correctly
      • Files that contain the replacement character (\uFFFD) are not parsed correctly
      • The simple symbol, constant symbol, compound symbol, stem, and internal routine suggestions are restricted to the current file in the editor
      • Code Completion inserts an extra pair of parenthesis when an existing function call in the editor is replaced with a built-in function
      • Changing the contents of a resolved include control directive will not necessarily clear errors
      • The language features do not consider the contents of a resolved include control directive
      • Keyword based REXX code folding: Currently VS Code default code folding is based on indentation levels, not keywords.
       JCL
      The following lists show the implementation status of the JCL language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.
       Enabled features of JCL program files
      • Syntax highlighting
      • Syntax errors
      • Outline view
      • Code completion
      • Snippets
      • Code folding
       IBM RSE API Plug-in for Zowe CLI
      Known issues and limitations for IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in)
       HTTP protocol support for RSE profiles
      ',9),to=o("As of Zowe CLI 6.31.0, HTTP support is not available for RSE profile connections. There is a "),no={href:"https://github.com/zowe/zowe-cli/issues/1329",target:"_blank",rel:"noopener noreferrer"},so=o("Zowe CLI issue"),ro=o(" that can be tracked for solution to bring this support back."),ao=n('
       npm WARN for peer dependencies
      When installing RSE CLI plug-in, you may encounter an npm WARN for an unmet peer dependency of Zowe CLI even though you have an accommodating version installed. There is due to a known bug in npm versions prior to 7. Having the warnings will not interfere with the successful installation of the plug-in; however, these warnings can be eliminated by running the command npm install npm@latest -g to obtain the latest version of npm.
       RSE CLI plug-in with ZAPP
      • When using the --mappings-file tag to state the location of a mappings file to use for upload and download of MVS files, if you have a zapp.json and a zapp.yaml in the same directory, the zapp.yaml will take precedence over the JSON file. It is recommended that you have only one zapp.yaml or zapp.json file when using ZAPP files at a project level.
       RSE CLI plug-in with JSON Web Tokens
      • JSON Web Tokens are not supported by Zowe Explorer 1.9.0 or previous versions.
      • If you created an RSE profile by using Zowe Explorer 1.11.1 or lower and left the username and password values blank and have empty strings stored within the profile's YAML, you will be required to add the --user and --password tags with the appropriate values when you use command line operations with that profile, even if a JWT has been issued for the profile at this time. We recommend creating the profile using command line operations or editing the profile with Zowe Explorer 1.12.0 or higher to omit the empty strings in the profile's YAML file.
      • The JWT logout command zowe rse auth logout is not supported by the host component RSE API 1.0.0.
      • If VS Code is opened during the auth login and auth logout is submitted using the CLI command with v1 profiles, a refresh of VS Code is required to grab the changes to the profile's YAML file for profile updates to be used in Zowe Explorer.
      • When using token authentication in Wazi Dev Spaces, the login action will fail if the team configuration profile is opened. To prevent this, make sure that the team configuration file is closed and the "autoSave" setting of editor is set to true.
       RSE CLI plug-in TSO and UNIX commands
      • The command zowe rse issue command {COMMAND}, which can be used to issue a TSO command, is not supported by the host component RSE API 1.0.0.
      • Issuing a UNIX command with an RSE profile via Zowe Explorer is not supported yet.
       RSE CLI plug-in COPY DATASETS CROSS LPAR command
      • The command zowe rse copy data-set-cross-lpar {COMMAND}, which can be used to copy datasets across lpars, does prompt for entering the username and password of the service twice which actually generates from the zowe cli side, but doesnot specify which LPAR it corresponds to.
       Known issues with z/OS UNIX System Services
      • z/OS UNIX System Services does not accept the upload of a directory or file names with spaces in them.
      • An error occurs when you specify z/OS UNIX System Services paths in a Window's Bash terminal (for example: /u/userid). To solve the issue, create an environment variable MSYS_NO_PATHCONV with a value of 1 in User Variables and restart the terminal.
       Using z/OSMF with Z Open Editor and Zowe Explorer
      IBM Z Open Editor can download remote files that are included in your programs through the RSE API or z/OSMF. If you are using z/OSMF to download remote files, it is recommended that you configure the host system with the following values at a minimum for z/OSMF:
      ParameterValue
      MAXSESSIONS250
      MAXUSERS25
      These recommendations ensure that optimal performance will be maintained even if many users are requesting remote downloads concurrently.
      If your development demands typically see more than 25 users requesting remote files concurrently, it is recommended that you increase MAXUSERS to meet your needs and increase MAXSESSIONS to a value equal to MAXUSERS*10.
      ',17),lo=o("For more information on where to set these values or solutions if your host system is running into resource problems, see "),co={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/hong-liang-zhao1/2020/10/13/tune-zosmf-rest-service",target:"_blank",rel:"noopener noreferrer"},ho=o("this blog"),uo=o("."),po=e("h2",{id:"known-issues-for-user-build",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#known-issues-for-user-build","aria-hidden":"true"},"#"),o(" Known issues for user build")],-1),fo=e("h3",{id:"using-an-older-version-of-ibm-dependency-based-build",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-an-older-version-of-ibm-dependency-based-build","aria-hidden":"true"},"#"),o(" Using an older version of IBM Dependency-Based Build")],-1),mo=o("IBM Z Open Editor v3+ is optimized for working with IBM Dependency-Based Build (DBB) v2. However, it can also still work with DBB v1. To be able run builds with v2 you need to use the "),go=e("code",null,"main",-1),bo=o(" branch of the "),_o={href:"https://github.com/IBM/dbb-zappbuild",target:"_blank",rel:"noopener noreferrer"},wo=o("https://github.com/IBM/dbb-zappbuild"),yo=o(" zAppBuild git repository. To build with DBB v1 you must checkout the branch called "),vo=e("code",null,"zAppBuild_2_x",-1),So=o(". Here the "),ko=e("code",null,"2",-1),Co=o(" stands for zAppBuild version 2 as the latest version in the "),xo=e("code",null,"main",-1),Io=o(" branch of zAppBuild is v3, which is the one that works with DBB v2."),Lo=n(`
       Using an older version of DBB zAppBuild
      If you are not using the latest branches of zAppBuild or have your own fork that was based on an older version than DBB zAppBuild 2.3.0 then consider the following. The encoding of the dependency file generated during an IBM User Build was recently changed from IBM-1047 to a standard UTF-8 encoding. This change means that if the latest version of IBM Z Open Editor is not paired with DBB zAppBuild 2.3.0 or greater you will have to add the previously required IBM-1047 encoding to the dependency file being generated, by adding the following to your .gitattributes file in your project in order to run an IBM User Build successfully:
      *.userbuilddependencies zos-working-tree-encoding=ibm-1047 git-encoding=utf-8
      Additionally, when using DBB v1 and zAppBuild v2, when you build a program file that contains spaces in the file path or name, you get the following error:
      java.util.MissingFormatArgumentException: Format specifier \u2018%s\u2019
+
      `,5),Oo=o("At the moment, zAppBuild v2 does not support spaces or URI encoded space character "),Eo=e("code",null,"%20",-1),Bo=o(" in the build file path or name. See the issue "),zo={href:"https://github.com/IBM/dbb-zappbuild/issues/234",target:"_blank",rel:"noopener noreferrer"},Ao=o("Support spaces in build file directory paths"),Mo=o(" for updates."),Po=e("h3",{id:"other-known-issues",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#other-known-issues","aria-hidden":"true"},"#"),o(" Other known issues")],-1),To=e("ul",null,[e("li",null,[o("Some programs fail building on z/OS with the error "),e("code",null,"Missing required dependency file field 'isCICS'."),o(" when using the "),e("code",null,'--dependencyFile ${dependencyFile}"'),o(" build script arguments in the ZAPP profile. As a workaround remove this parameter for now until we can provide a fix. This parameters is an optional performance improvement. Builds can work without it as well.")])],-1),Ro=e("h2",{id:"reporting-issues",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#reporting-issues","aria-hidden":"true"},"#"),o(" Reporting issues")],-1),No=o("If you want to provide feedback or report an issue, open an issue in the "),Zo={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},Do=o("GitHub repository"),Fo=o(". Any report and feedback is appreciated.");function Ho(Xo,Vo){const t=a("ExternalLinkIcon"),s=a("RouterLink");return l(),d(c,null,[p,e("p",null,[f,e("a",m,[g,i(t)]),b]),_,e("p",null,[w,y,v,S,k,C,x,I,L,i(s,{to:"/Docs/getting_started.html#configuring-java"},{default:r(()=>[O]),_:1}),E]),B,e("p",null,[z,e("a",A,[M,i(t)]),P]),e("ul",null,[T,R,e("li",null,[N,e("a",Z,[D,i(t)]),F])]),H,X,e("ul",null,[e("li",null,[e("p",null,[V,j,J,i(s,{to:"/Docs/setup_integration.html#authentication-using-zowe"},{default:r(()=>[U]),_:1}),q])]),W]),G,e("ul",null,[Y,e("li",null,[K,e("a",Q,[$,i(t)]),ee]),e("li",null,[e("a",oe,[ie,i(t)])]),e("li",null,[te,e("a",ne,[se,i(t)]),re,e("a",ae,[le,i(t)])]),de]),ce,e("ul",null,[e("li",null,[he,e("a",ue,[pe,i(t)]),fe,i(s,{to:"/Docs/setting_unreachablecodewarnings.html"},{default:r(()=>[me]),_:1}),ge]),e("li",null,[be,e("a",_e,[we,i(t)]),ye]),ve]),Se,e("ul",null,[ke,e("li",null,[Ce,xe,Ie,Le,e("ul",null,[Oe,Ee,Be,e("li",null,[ze,e("ul",null,[e("li",null,[e("a",Ae,[Me,i(t)])]),e("li",null,[e("a",Pe,[Te,i(t)])])])])])]),e("li",null,[i(s,{to:"/Docs/editor_codechanges.html#commenting-and-uncommenting-pli-code"},{default:r(()=>[Re]),_:1})]),e("li",null,[Ne,e("a",Ze,[De,i(t)]),Fe]),e("li",null,[e("a",He,[Xe,i(t)])])]),Ve,e("ul",null,[je,e("li",null,[i(s,{to:"/Docs/editor_codechanges_hlasm.html#commenting-and-uncommenting-hlasm-code"},{default:r(()=>[Je]),_:1})])]),Ue,e("ul",null,[qe,We,Ge,Ye,Ke,Qe,$e,eo,e("li",null,[i(s,{to:"/Docs/editor_codechanges_rexx.html#commenting-and-uncommenting-rexx-code"},{default:r(()=>[oo]),_:1})])]),io,e("p",null,[to,e("a",no,[so,i(t)]),ro]),ao,e("p",null,[lo,e("a",co,[ho,i(t)]),uo]),po,fo,e("p",null,[mo,go,bo,e("a",_o,[wo,i(t)]),yo,vo,So,ko,Co,xo,Io]),Lo,e("p",null,[Oo,Eo,Bo,e("a",zo,[Ao,i(t)]),Mo]),Po,To,Ro,e("p",null,[No,e("a",Zo,[Do,i(t)]),Fo])],64)}var Uo=h(u,[["render",Ho]]);export{Uo as default};
diff --git a/assets/knownissues.html.913faaf1.js b/assets/knownissues.html.913faaf1.js
deleted file mode 100644
index 52696a069..000000000
--- a/assets/knownissues.html.913faaf1.js
+++ /dev/null
@@ -1,2 +0,0 @@
-import{r as a,o as l,a as d,b as e,d as i,w as r,F as h,e as o,c as n}from"./app.f6cb3ed9.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const u={},p=e("h1",{id:"known-issues-and-limitations",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#known-issues-and-limitations","aria-hidden":"true"},"#"),o(" Known issues and limitations")],-1),f=o("The IBM Z\xAE Open Editor extension has some known issues and limitations. This page provides the status of the current release. Also review the list of open issues and enhancement requests in our "),m={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},g=o("Github repository"),b=o(". It might list issues that are not yet documented here."),_=n('
       Java\u2122 11 64-Bit JRE or SDK required
      If the right version of Java cannot be found in the current user's path or if no JAVA_HOME environment variable was defined, you might see error messages in the Output view of VS Code. Such errors could also be caused by other reasons such as not enough free memory for Java on your system.
      Go through all the steps described in the Getting Started page for configuring Java to try out different options.
       Java not found on Linux
      Z Open Editor starts by searching for Java in the following locations:
      • The path specified by the zopeneditor.JAVA_HOME value in your VS Code settings.
      • The path specified by the java.jdt.ls.java.home value in your VS Code settings.
      • The path specified by your JAVA_HOME environment variable.
      After searching these locations, Z Open Editor will run commands to try and find Java on your operating system.
      ',7),w=o("If your installation is not found and you see errors in the Welcome page, try specifying a path to your Java for your "),y=e("code",null,"zopeneditor.JAVA_HOME",-1),v=o(" or "),S=e("code",null,"java.jdt.ls.java.home",-1),k=o(" value in your VS Code settings or setting your system's "),C=e("code",null,"JAVA_HOME",-1),x=o(" environment variable. Ensure that you exclude the "),I=e("code",null,"bin/java",-1),L=o(" directory from your path. For more information, see "),E=o("Configuring Java"),O=o("."),B=n('
       Resetting Language Servers or VS Code
      It might happen that the language servers provided by IBM Z Open Editor become inconsistent and do not behave as expected. For example, a language server might stop reporting syntax errors, or it cannot resolve copybooks anymore. Instead of quitting and restarting VS Code completely, you can try pressing the F1 key and type the following commands to reset one or more language servers.
      • IBM Z Open Editor: Pause the COBOL Language Server: Stops the COBOL language server and restarts it when you open a COBOL file again.
      • IBM Z Open Editor: Pause the PL/I Language Server: Stops the PL/I language server and restarts it when you open a PL/I file again.
      • IBM Z Open Editor: Pause the Assembler Language Server: Stops the HLASM language server and restarts it when you open an HLASM file again.
      • IBM Z Open Editor: Pause the REXX Language Server: Stops the REXX language server and restarts it when you open a REXX file again.
      • IBM Z Open Editor: Pause the JCL Language Server: Stops the JCL language server and restarts it when you open a JCL file again.
      • IBM Z Open Editor: Reload Zowe Profiles: If you have changed the password of your Zowe CLI profile that is used to load your remote include files such as copybooks, you need to run this command to refresh the Zowe profile.
      • Developer: Reload Window: Restarts the current VS Code window and all of its extensions. If you have many editor windows open at the same time, you can use this command to reset just the current window in which you run the command.
       Limitations for Visual Studio Code Multi-Root Workspaces
      ',4),z=o("IBM Z\xAE Open Editor supports "),M={href:"https://code.visualstudio.com/docs/editor/multi-root-workspaces",target:"_blank",rel:"noopener noreferrer"},A=o("VS Code multi-root workspaces"),P=o(", but there are some limits or special rules on how ZAPP files and settings are used in a multi-root workspace:"),T=e("li",null,[o("Property Groups: the multi-root workspace can load multiple zapp files located in the top-dir of each workspace. We search for property groups in each of these zapp files in the order the workspaces are listed in the "),e("code",null,".code-workspace .code-workspace"),o(" file when resolving include files.")],-1),R=e("li",null,"For user build the DBB ZAPP profile located in the workspace of the program being built is being used. The application-conf files (additional files listed in zapp profile) also need to be in the root of the workspace with the program.",-1),N=o("For "),Z={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-building-cobol-pli-hlasm-programs-user-build",target:"_blank",rel:"noopener noreferrer"},D=o("Z Open Editor's user build"),F=o(", local copybooks and include files that need to be uploaded to z/OS UNIX System Services for build can be located in any other workspace of the multi-root workspace. The location of the copybooks and include files must be specified in the ZAPP file of the workspace in which these include files are located in. A ZAPP file cannot provide property groups that point to locations outside of its workspace. The exception would be using absolute path names, but those might break the ability to share the ZAPP file with other team members as they might have their files in different locations."),H=e("h2",{id:"limitations-of-using-z-open-editor-with-eclipse-che-and-red-hat-openshift-dev-spaces",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#limitations-of-using-z-open-editor-with-eclipse-che-and-red-hat-openshift-dev-spaces","aria-hidden":"true"},"#"),o(" Limitations of using Z Open Editor with Eclipse Che and Red Hat OpenShift Dev Spaces")],-1),X=e("p",null,"Almost all capabilities described in this documentation are available when you use IBM Z Open Editor with Eclipse Che or Red Hat OpenShift Dev Spaces. However, note the following limitations.",-1),V=o("Zowe CLI secure credentials are currently not supported with Z Open Editor on Eclipse Che and Red Hat OpenShift Dev Spaces. The Zowe Explorer setting "),j=e("code",null,'"zowe.security.secureCredentialsEnabled": false',-1),J=o(" must be used in these environments. See the section "),U=o("Setting up integrations to interact with z/OS > Managing credentials unsecured"),q=o("."),W=e("li",null,[e("p",null,[o("Path names specified for property groups in ZAPP files are always case-sensitive, even if the setting "),e("code",null,'"zopeneditor.enforceCaseSensitiveIncludeFileNames"'),o(" is set to "),e("code",null,"false"),o(". However, this setting works for the file names that get matched in the folders that match the property groups.")])],-1),G=n('
       Language-specific features and limitations
       COBOL
      The following lists show the implementation status of the COBOL language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.
       Enabled features of COBOL program files
      ',4),Y=n("
    • Syntax highlighting
    • Syntax errors
    • Document highlighting
    • Hover
    • Go to declaration
    • Find all references in file and across the multiple files
    • Peek references in file and across the multiple files
    • Rename symbol in file and across the multiple files
    • Outline view
    • Code completion
    • Snippets
    • Copybook resolving and copybook hover support
    • Document link support to open copybook by using Ctrl+Click (Windows) or Cmd+Click (Mac)
    • Embedded languages support such as SQL, CICS\xAE, and DLI
    • Renumber and Unnumber sequence numbers
    • Syntax highlighting support for Sequence Numbers (1-6 and 73-80 columns)
      • ",16),K=o("Latest COBOL 6.4 PTF language support, up to and including the "),Q={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/dan-zhang1/2024/02/26/february-2024-documentation-refresh-for-enterprise",target:"_blank",rel:"noopener noreferrer"},$=o("February 2024 PTF"),ee=o("."),oe={href:"https://www.ibm.com/docs/en/cics-ts/beta?topic=whats-new",target:"_blank",rel:"noopener noreferrer"},ie=o("Embedded Language Support for CICS 6.2 in COBOL"),te=o("COBOL "),ne={href:"https://www.ibm.com/docs/en/cobol-zos/6.4?topic=applications-using-user-defined-functions",target:"_blank",rel:"noopener noreferrer"},se=o("User defined functions"),re=o(" support including "),ae={href:"https://www.ibm.com/docs/en/cobol-zos/6.4?topic=applications-using-function-prototypes",target:"_blank",rel:"noopener noreferrer"},le=o("function prototypes"),de=e("li",null,"Code folding",-1),he=e("h4",{id:"limitations-of-cobol-program-files",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#limitations-of-cobol-program-files","aria-hidden":"true"},"#"),o(" Limitations of COBOL program files")],-1),ce=o("False unreachable code warnings: In some cases, the editor incorrectly reports that code is unreachable in embedded SQL and CICS statements such as "),ue=e("code",null,"EXEC CICS HANDLE",-1),pe=o(". One such case is reported in "),fe={href:"https://github.com/IBM/zopeneditor-about/issues/52",target:"_blank",rel:"noopener noreferrer"},me=o("this issue"),ge=o(". You can use a user setting to disable warnings for unreachable code completely as described in "),be=o("Enabling and disabling unreachable COBOL code warnings"),_e=o("."),we=o("Incomplete support for conditional compilation: Our community has reported various "),ye={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},ve=o("issues"),Se=o(" when programs contain conditional compilation statements. These types of programs are currently not fully supported."),ke=e("li",null,[o("For COBOL programs that load a large number of copybooks from MVS, downloading can take a long time. Consider as a workaround the user setting "),e("code",null,'"zowe.files.temporaryDownloadsFolder.cleanup": false'),o(" that will not re-download the files between editing sessions.")],-1),Ce=n('
       Enabled features of COBOL copybook files
      • Syntax errors
      • Find all references in file
      • Peek references in file
      • Rename symbol in file
      • Outline view
      • Syntax highlighting
      • Code completion
      • Snippets
      • Embedded languages support such as SQL, CICS, and DLI
       Limitations of COBOL copybook files
      • No support for Hover
      • No support for Go to declaration
      • No support for Find all references across the multiple files
      • No support for Peek references across the multiple files
      • No support for Rename symbol from a copybook to the files that include it
       PL/I
      The following lists show the implementation status of the PL/I language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.
       Enabled features of PL/I program files
      ',7),xe=n("
    • Syntax highlighting
    • Syntax errors
    • Document highlighting
    • Hover
    • Go to declaration
    • Find all references in file and across the multiple files
    • Peek references in file and across the multiple files
    • Rename symbol in file and across the multiple files
    • Outline view
    • Code completion
    • Include file resolving and include file hover support
    • Document link support to open include file by using Ctrl+Click (Windows) or Cmd+Click (Mac)
    • Embedded languages support such as SQL, CICS, and DLI
      • ",13),Ie=e("code",null,"*process",-1),Le=o(" (or "),Ee=e("code",null,"%process",-1),Oe=o(") compile options statements, such as: "),Be=e("li",null,[e("code",null,"*process source MARGINS(2,120);")],-1),ze=e("li",null,[e("code",null,"*process SYSTEM(CIS, DB2);")],-1),Me=e("li",null,[e("code",null,"*process LIST TEST;")],-1),Ae=o("Syntax and other supported compiler options can be found in: "),Pe={href:"https://www.ibm.com/docs/en/epfz/5.3?topic=directives-process-directive",target:"_blank",rel:"noopener noreferrer"},Te=o("%PROCESS directive"),Re={href:"https://www.ibm.com/docs/en/epfz/5.3?topic=facilities-compile-time-option-descriptions",target:"_blank",rel:"noopener noreferrer"},Ne=o("Compile-time option descriptions"),Ze=o("Commenting and uncommenting PL/I code"),De=o("Latest Pl/I 6.1 PTF language support, up to and including the "),Fe={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/di-hu1/2024/01/31/january-2024-documentation-refresh-for-enterprise",target:"_blank",rel:"noopener noreferrer"},He=o("January 2024 PTF"),Xe=o("."),Ve={href:"https://www.ibm.com/docs/en/cics-ts/beta?topic=whats-new",target:"_blank",rel:"noopener noreferrer"},je=o("Embedded Language Support for CICS 6.2 Beta version in PL/I"),Je=n('
       Limitations of PL/I program files
      • No support for macros
      • The left margin is currently not fully configurable. The minimum value required is 2.
      • PL/I 6.1 
        • No support is included for the MAXRUNONIF compiler option.
        • No support is included for the PROCINC directive. An alternative way to accomplish the purpose of the PROCINC directive is to use the PROCESS directive with the compiler option from the data set that you want to add for the PROCINC directive.
      • For PL/I programs that load a large number of include files from MVS, downloading can take a long time. Consider as a workaround the user setting "zowe.files.temporaryDownloadsFolder.cleanup": false that will not re-download the files between editing sessions.
      The following legal PL/I syntactic constructions are marked as errors:
      • Invalid PL/I syntax in macro preprocessor input when the macro preprocessor output is legal PL/I
      • Labels on preprocessor directives
      • Entry constants
      • Type functions
      • Factoring of attributes when you declare structures
      • An isub option with defined attribute
      • A tstack attribute of the attach statement
      • Implicit variable declarations
      The following invalid PL/I syntactic constructions are not marked as errors:
      • Condition prefixes for do statements
      • Label prefixes for declare, default, when, otherwise, and on statements
      • Scaling factors for float or fixed
      • Duplicate attributes for declaration statements
      • Syntax errors in macro preprocessor output
       Enabled features of PL/I include files
      • Syntax errors (lexing and parsing)
      • Find all references in file
      • Peek references in file
      • Rename symbol in file
      • Outline view
      • Syntax highlighting
      • Code completion
      • Embedded languages support such as SQL, CICS, and DLI
       Limitations of PL/I include files
      • No support for showing syntax errors for resolving variables
      • No support for Hover
      • No support for Go to declaration
      • No support for Find all references across the multiple files
      • No support for Peek references across the multiple files
      • No support for Rename symbol across the multiple files
       HLASM
      The following lists show the implementation status of the HLASM language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.
       Enabled features of HLASM program files
      ',13),Ue=n("
    • Syntax highlighting
    • Syntax errors, which currently only include the following: 
      • Copy statements not resolved
      • Spaces in continuation line
      • Invalid number of operands
    • Document highlighting
    • Hover on operations and operands
    • Go to declaration for all operands, including those from copy members
    • Find all references in file
    • Peek references in file
    • Outline view for macros, CSECTs, and DSECTs
    • Code completion, including snippet-style completion for operations and macros
    • Copy member file resolving and copy member file hover support
    • SYS1.MACLIB Macro remote file resolving and content hover support 
      • The z/OS version for SYS1.MACLIB is configurable between 2.4, 2.5, and 3.1 with the user setting "zopeneditor.hlasm.zosMacrosVersion".
    • Custom Macro file resolving, code completion, and content hover support for local macros.
    • Document link support to open copybook file by using Ctrl+Click (Windows) or Cmd+Click (Mac)
    • Quick fix hints for lines that are too long and spaces in the continuation line
      • ",14),qe=o("Commenting and uncommenting HLASM code"),We=n('
       Limitations of HLASM program files
      • Limited syntax checks such as no errors for undeclared variables
      • Syntax highlighting limitations on multi-line strings
      • Syntax highlighting limitations on non-continuation lines that begin at column 16
      • Syntax highlighting does not recognize continuation lines that begin at column 17 and later as comments
      • Keyword based HLASM code folding: Currently VS Code default code folding is based on indentation levels, not keywords.
      • Custom Macro file resolving is not currently available for remote macros.
       REXX
      The following lists show the implementation status of the REXX language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.
       Enabled features of REXX program files
      ',5),Ge=e("li",null,"Syntax highlighting",-1),Ye=e("li",null,"Syntax errors",-1),Ke=e("li",null,"Hover",-1),Qe=e("li",null,"Find all references",-1),$e=e("li",null,"Outline view",-1),eo=e("li",null,"Code completion",-1),oo=e("li",null,"Include control directive resolution and hover support",-1),io=e("li",null,"Syntax Highlighting for Include control directives",-1),to=o("Commenting and uncommenting REXX code"),no=n('
       Limitations of REXX program files
      • No support for the 'END' keyword as a variable
      • No support for embedded languages
      • Code Completion and Hover do not support keywords that are not keyword instructions
      • Some color themes may not highlight all symbols correctly
      • Files that contain the replacement character (\uFFFD) are not parsed correctly
      • The simple symbol, constant symbol, compound symbol, stem, and internal routine suggestions are restricted to the current file in the editor
      • Code Completion inserts an extra pair of parenthesis when an existing function call in the editor is replaced with a built-in function
      • Changing the contents of a resolved include control directive will not necessarily clear errors
      • The language features do not consider the contents of a resolved include control directive
      • Keyword based REXX code folding: Currently VS Code default code folding is based on indentation levels, not keywords.
       JCL
      The following lists show the implementation status of the JCL language server. Use these lists to check that the feature that you are looking for was implemented or is regarded as a known issue. Let us know if you have any additional issues.
       Enabled features of JCL program files
      • Syntax highlighting
      • Syntax errors
      • Outline view
      • Code completion
      • Snippets
      • Code folding
       IBM RSE API Plug-in for Zowe CLI
      Known issues and limitations for IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in)
       HTTP protocol support for RSE profiles
      ',9),so=o("As of Zowe CLI 6.31.0, HTTP support is not available for RSE profile connections. There is a "),ro={href:"https://github.com/zowe/zowe-cli/issues/1329",target:"_blank",rel:"noopener noreferrer"},ao=o("Zowe CLI issue"),lo=o(" that can be tracked for solution to bring this support back."),ho=n('
       npm WARN for peer dependencies
      When installing RSE CLI plug-in, you may encounter an npm WARN for an unmet peer dependency of Zowe CLI even though you have an accommodating version installed. There is due to a known bug in npm versions prior to 7. Having the warnings will not interfere with the successful installation of the plug-in; however, these warnings can be eliminated by running the command npm install npm@latest -g to obtain the latest version of npm.
       RSE CLI plug-in with ZAPP
      • When using the --mappings-file tag to state the location of a mappings file to use for upload and download of MVS files, if you have a zapp.json and a zapp.yaml in the same directory, the zapp.yaml will take precedence over the JSON file. It is recommended that you have only one zapp.yaml or zapp.json file when using ZAPP files at a project level.
       RSE CLI plug-in with JSON Web Tokens
      • JSON Web Tokens are not supported by Zowe Explorer 1.9.0 or previous versions.
      • If you created an RSE profile by using Zowe Explorer 1.11.1 or lower and left the username and password values blank and have empty strings stored within the profile's YAML, you will be required to add the --user and --password tags with the appropriate values when you use command line operations with that profile, even if a JWT has been issued for the profile at this time. We recommend creating the profile using command line operations or editing the profile with Zowe Explorer 1.12.0 or higher to omit the empty strings in the profile's YAML file.
      • The JWT logout command zowe rse auth logout is not supported by the host component RSE API 1.0.0.
      • If VS Code is opened during the auth login and auth logout is submitted using the CLI command with v1 profiles, a refresh of VS Code is required to grab the changes to the profile's YAML file for profile updates to be used in Zowe Explorer.
      • When using token authentication in Wazi Dev Spaces, the login action will fail if the team configuration profile is opened. To prevent this, make sure that the team configuration file is closed and the "autoSave" setting of editor is set to true.
       RSE CLI plug-in TSO and UNIX commands
      • The command zowe rse issue command {COMMAND}, which can be used to issue a TSO command, is not supported by the host component RSE API 1.0.0.
      • Issuing a UNIX command with an RSE profile via Zowe Explorer is not supported yet.
       Known issues with z/OS UNIX System Services
      • z/OS UNIX System Services does not accept the upload of a directory or file names with spaces in them.
      • An error occurs when you specify z/OS UNIX System Services paths in a Window's Bash terminal (for example: /u/userid). To solve the issue, create an environment variable MSYS_NO_PATHCONV with a value of 1 in User Variables and restart the terminal.
       Using z/OSMF with Z Open Editor and Zowe Explorer
      IBM Z Open Editor can download remote files that are included in your programs through the RSE API or z/OSMF. If you are using z/OSMF to download remote files, it is recommended that you configure the host system with the following values at a minimum for z/OSMF:
      ParameterValue
      MAXSESSIONS250
      MAXUSERS25
      These recommendations ensure that optimal performance will be maintained even if many users are requesting remote downloads concurrently.
      If your development demands typically see more than 25 users requesting remote files concurrently, it is recommended that you increase MAXUSERS to meet your needs and increase MAXSESSIONS to a value equal to MAXUSERS*10.
      ',15),co=o("For more information on where to set these values or solutions if your host system is running into resource problems, see "),uo={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/hong-liang-zhao1/2020/10/13/tune-zosmf-rest-service",target:"_blank",rel:"noopener noreferrer"},po=o("this blog"),fo=o("."),mo=e("h2",{id:"known-issues-for-user-build",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#known-issues-for-user-build","aria-hidden":"true"},"#"),o(" Known issues for user build")],-1),go=e("h3",{id:"using-an-older-version-of-ibm-dependency-based-build",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-an-older-version-of-ibm-dependency-based-build","aria-hidden":"true"},"#"),o(" Using an older version of IBM Dependency-Based Build")],-1),bo=o("IBM Z Open Editor v3+ is optimized for working with IBM Dependency-Based Build (DBB) v2. However, it can also still work with DBB v1. To be able run builds with v2 you need to use the "),_o=e("code",null,"main",-1),wo=o(" branch of the "),yo={href:"https://github.com/IBM/dbb-zappbuild",target:"_blank",rel:"noopener noreferrer"},vo=o("https://github.com/IBM/dbb-zappbuild"),So=o(" zAppBuild git repository. To build with DBB v1 you must checkout the branch called "),ko=e("code",null,"zAppBuild_2_x",-1),Co=o(". Here the "),xo=e("code",null,"2",-1),Io=o(" stands for zAppBuild version 2 as the latest version in the "),Lo=e("code",null,"main",-1),Eo=o(" branch of zAppBuild is v3, which is the one that works with DBB v2."),Oo=n(`
       Using an older version of DBB zAppBuild
      If you are not using the latest branches of zAppBuild or have your own fork that was based on an older version than DBB zAppBuild 2.3.0 then consider the following. The encoding of the dependency file generated during an IBM User Build was recently changed from IBM-1047 to a standard UTF-8 encoding. This change means that if the latest version of IBM Z Open Editor is not paired with DBB zAppBuild 2.3.0 or greater you will have to add the previously required IBM-1047 encoding to the dependency file being generated, by adding the following to your .gitattributes file in your project in order to run an IBM User Build successfully:
      *.userbuilddependencies zos-working-tree-encoding=ibm-1047 git-encoding=utf-8
      Additionally, when using DBB v1 and zAppBuild v2, when you build a program file that contains spaces in the file path or name, you get the following error:
      java.util.MissingFormatArgumentException: Format specifier \u2018%s\u2019
-
      `,5),Bo=o("At the moment, zAppBuild v2 does not support spaces or URI encoded space character "),zo=e("code",null,"%20",-1),Mo=o(" in the build file path or name. See the issue "),Ao={href:"https://github.com/IBM/dbb-zappbuild/issues/234",target:"_blank",rel:"noopener noreferrer"},Po=o("Support spaces in build file directory paths"),To=o(" for updates."),Ro=e("h3",{id:"other-known-issues",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#other-known-issues","aria-hidden":"true"},"#"),o(" Other known issues")],-1),No=e("ul",null,[e("li",null,[o("Some programs fail building on z/OS with the error "),e("code",null,"Missing required dependency file field 'isCICS'."),o(" when using the "),e("code",null,'--dependencyFile ${dependencyFile}"'),o(" build script arguments in the ZAPP profile. As a workaround remove this parameter for now until we can provide a fix. This parameters is an optional performance improvement. Builds can work without it as well.")])],-1),Zo=e("h2",{id:"reporting-issues",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#reporting-issues","aria-hidden":"true"},"#"),o(" Reporting issues")],-1),Do=o("If you want to provide feedback or report an issue, open an issue in the "),Fo={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},Ho=o("GitHub repository"),Xo=o(". Any report and feedback is appreciated.");function Vo(jo,Jo){const t=a("ExternalLinkIcon"),s=a("RouterLink");return l(),d(h,null,[p,e("p",null,[f,e("a",m,[g,i(t)]),b]),_,e("p",null,[w,y,v,S,k,C,x,I,L,i(s,{to:"/Docs/getting_started.html#configuring-java"},{default:r(()=>[E]),_:1}),O]),B,e("p",null,[z,e("a",M,[A,i(t)]),P]),e("ul",null,[T,R,e("li",null,[N,e("a",Z,[D,i(t)]),F])]),H,X,e("ul",null,[e("li",null,[e("p",null,[V,j,J,i(s,{to:"/Docs/setup_integration.html#authentication-using-zowe"},{default:r(()=>[U]),_:1}),q])]),W]),G,e("ul",null,[Y,e("li",null,[K,e("a",Q,[$,i(t)]),ee]),e("li",null,[e("a",oe,[ie,i(t)])]),e("li",null,[te,e("a",ne,[se,i(t)]),re,e("a",ae,[le,i(t)])]),de]),he,e("ul",null,[e("li",null,[ce,ue,pe,e("a",fe,[me,i(t)]),ge,i(s,{to:"/Docs/setting_unreachablecodewarnings.html"},{default:r(()=>[be]),_:1}),_e]),e("li",null,[we,e("a",ye,[ve,i(t)]),Se]),ke]),Ce,e("ul",null,[xe,e("li",null,[Ie,Le,Ee,Oe,e("ul",null,[Be,ze,Me,e("li",null,[Ae,e("ul",null,[e("li",null,[e("a",Pe,[Te,i(t)])]),e("li",null,[e("a",Re,[Ne,i(t)])])])])])]),e("li",null,[i(s,{to:"/Docs/editor_codechanges.html#commenting-and-uncommenting-pli-code"},{default:r(()=>[Ze]),_:1})]),e("li",null,[De,e("a",Fe,[He,i(t)]),Xe]),e("li",null,[e("a",Ve,[je,i(t)])])]),Je,e("ul",null,[Ue,e("li",null,[i(s,{to:"/Docs/editor_codechanges_hlasm.html#commenting-and-uncommenting-hlasm-code"},{default:r(()=>[qe]),_:1})])]),We,e("ul",null,[Ge,Ye,Ke,Qe,$e,eo,oo,io,e("li",null,[i(s,{to:"/Docs/editor_codechanges_rexx.html#commenting-and-uncommenting-rexx-code"},{default:r(()=>[to]),_:1})])]),no,e("p",null,[so,e("a",ro,[ao,i(t)]),lo]),ho,e("p",null,[co,e("a",uo,[po,i(t)]),fo]),mo,go,e("p",null,[bo,_o,wo,e("a",yo,[vo,i(t)]),So,ko,Co,xo,Io,Lo,Eo]),Oo,e("p",null,[Bo,zo,Mo,e("a",Ao,[Po,i(t)]),To]),Ro,No,Zo,e("p",null,[Do,e("a",Fo,[Ho,i(t)]),Xo])],64)}var Wo=c(u,[["render",Vo]]);export{Wo as default};
diff --git a/assets/knownissues.html.8474e59f.js b/assets/knownissues.html.d646b074.js
similarity index 89%
rename from assets/knownissues.html.8474e59f.js
rename to assets/knownissues.html.d646b074.js
index f6856703e..9b2071ac3 100644
--- a/assets/knownissues.html.8474e59f.js
+++ b/assets/knownissues.html.d646b074.js
@@ -1 +1 @@
-const i={key:"v-823d11d2",path:"/Docs/knownissues.html",title:"Known issues and limitations",lang:"en-US",frontmatter:{},excerpt:"",headers:[{level:1,title:"Known issues and limitations",slug:"known-issues-and-limitations",children:[{level:2,title:"Java\u2122 11 64-Bit JRE or SDK required",slug:"javatm-11-64-bit-jre-or-sdk-required",children:[]},{level:2,title:"Resetting Language Servers or VS Code",slug:"resetting-language-servers-or-vs-code",children:[]},{level:2,title:"Limitations for Visual Studio Code Multi-Root Workspaces",slug:"limitations-for-visual-studio-code-multi-root-workspaces",children:[]},{level:2,title:"Limitations of using Z Open Editor with Eclipse Che and Red Hat OpenShift Dev Spaces",slug:"limitations-of-using-z-open-editor-with-eclipse-che-and-red-hat-openshift-dev-spaces",children:[]},{level:2,title:"Language-specific features and limitations",slug:"language-specific-features-and-limitations",children:[]},{level:2,title:"IBM RSE API Plug-in for Zowe CLI",slug:"ibm-rse-api-plug-in-for-zowe-cli",children:[]},{level:2,title:"Using z/OSMF with Z Open Editor and Zowe Explorer",slug:"using-z-osmf-with-z-open-editor-and-zowe-explorer",children:[]},{level:2,title:"Known issues for user build",slug:"known-issues-for-user-build",children:[]},{level:2,title:"Reporting issues",slug:"reporting-issues",children:[]}]}],git:{updatedTime:1723684879e3,contributors:[{name:"Billie Simmons",email:"billiejean.simmons@ibm.com",commits:30},{name:"Peter Haumer",email:"phaumer@us.ibm.com",commits:14},{name:"Shi Kun Li",email:"shikunli@cn.ibm.com",commits:14},{name:"Billie Simmons",email:"BillieJean.Simmons@ibm.com",commits:13},{name:"Greg Lambert",email:"Gregory.Lambert@ibm.com",commits:13},{name:"Lauren Li",email:"45975633+lauren-li@users.noreply.github.com",commits:11},{name:"Min Huang",email:"minhsh@cn.ibm.com",commits:11},{name:"Peter Haumer",email:"4391934+phaumer@users.noreply.github.com",commits:11},{name:"Bradley Knaysi",email:"bknaysi@ibm.com",commits:10},{name:"Lauren Li",email:"Lauren.Li@ibm.com",commits:9},{name:"Prasang-A-Prajapati",email:"Prasang.A.Prajapati@ibm.com",commits:9},{name:"Chun Hong Zheng",email:"chunhzh@cn.ibm.com",commits:7},{name:"Benjamin Santos",email:"Benjamin.Santos@ibm.com",commits:6},{name:"Saile Daimwood",email:"sdaimwood@ibm.com",commits:6},{name:"Rudy Leonel Pichola Flores",email:"rudyflores@ibm.com",commits:5},{name:"BillieJean-Simmons",email:"BillieJean.Simmons@ibm.com",commits:4},{name:"PETER HAUMER",email:"phaumer@us.ibm.com",commits:4},{name:"Saile",email:"sdaimwood@ibm.com",commits:4},{name:"Billie Jean Simmons",email:"billiejean.simmons@ibm.com",commits:3},{name:"kmaselli",email:"81706519+kmaselli@users.noreply.github.com",commits:3},{name:"Arvin Bhatnagar",email:"abhatnag@us.ibm.com",commits:2},{name:"Hestia Zhang",email:"Hestia.Zhang@ibm.com",commits:2},{name:"Lauren K Li",email:"Lauren.Li@ibm.com",commits:2},{name:"Prasang Prajapati",email:"Prasang.A.Prajapati@ibm.com",commits:2},{name:"PrasangAPrajapati",email:"Prasang.A.Prajapati@ibm.com",commits:2},{name:"shikunli",email:"shikunli@cn.ibm.com",commits:2},{name:"KRISTINA MAYO",email:"ktopchi@us.ibm.com",commits:1},{name:"Keng-Hui Beall",email:"kdbeall@ibm.com",commits:1}]},filePathRelative:"Docs/knownissues.md"};export{i as data};
+const i={key:"v-823d11d2",path:"/Docs/knownissues.html",title:"Known issues and limitations",lang:"en-US",frontmatter:{},excerpt:"",headers:[{level:1,title:"Known issues and limitations",slug:"known-issues-and-limitations",children:[{level:2,title:"Java\u2122 11 64-Bit JRE or SDK required",slug:"javatm-11-64-bit-jre-or-sdk-required",children:[]},{level:2,title:"Resetting Language Servers or VS Code",slug:"resetting-language-servers-or-vs-code",children:[]},{level:2,title:"Limitations for Visual Studio Code Multi-Root Workspaces",slug:"limitations-for-visual-studio-code-multi-root-workspaces",children:[]},{level:2,title:"Limitations of using Z Open Editor with Eclipse Che and Red Hat OpenShift Dev Spaces",slug:"limitations-of-using-z-open-editor-with-eclipse-che-and-red-hat-openshift-dev-spaces",children:[]},{level:2,title:"Language-specific features and limitations",slug:"language-specific-features-and-limitations",children:[]},{level:2,title:"IBM RSE API Plug-in for Zowe CLI",slug:"ibm-rse-api-plug-in-for-zowe-cli",children:[]},{level:2,title:"Using z/OSMF with Z Open Editor and Zowe Explorer",slug:"using-z-osmf-with-z-open-editor-and-zowe-explorer",children:[]},{level:2,title:"Known issues for user build",slug:"known-issues-for-user-build",children:[]},{level:2,title:"Reporting issues",slug:"reporting-issues",children:[]}]}],git:{updatedTime:1726615703e3,contributors:[{name:"Billie Simmons",email:"billiejean.simmons@ibm.com",commits:30},{name:"Peter Haumer",email:"phaumer@us.ibm.com",commits:14},{name:"Shi Kun Li",email:"shikunli@cn.ibm.com",commits:14},{name:"Billie Simmons",email:"BillieJean.Simmons@ibm.com",commits:13},{name:"Greg Lambert",email:"Gregory.Lambert@ibm.com",commits:13},{name:"Lauren Li",email:"45975633+lauren-li@users.noreply.github.com",commits:11},{name:"Min Huang",email:"minhsh@cn.ibm.com",commits:11},{name:"Peter Haumer",email:"4391934+phaumer@users.noreply.github.com",commits:11},{name:"Bradley Knaysi",email:"bknaysi@ibm.com",commits:10},{name:"Lauren Li",email:"Lauren.Li@ibm.com",commits:9},{name:"Prasang-A-Prajapati",email:"Prasang.A.Prajapati@ibm.com",commits:9},{name:"Chun Hong Zheng",email:"chunhzh@cn.ibm.com",commits:7},{name:"Saile Daimwood",email:"sdaimwood@ibm.com",commits:7},{name:"Benjamin Santos",email:"Benjamin.Santos@ibm.com",commits:6},{name:"Rudy Leonel Pichola Flores",email:"rudyflores@ibm.com",commits:5},{name:"BillieJean-Simmons",email:"BillieJean.Simmons@ibm.com",commits:4},{name:"PETER HAUMER",email:"phaumer@us.ibm.com",commits:4},{name:"Saile",email:"sdaimwood@ibm.com",commits:4},{name:"Billie Jean Simmons",email:"billiejean.simmons@ibm.com",commits:3},{name:"kmaselli",email:"81706519+kmaselli@users.noreply.github.com",commits:3},{name:"Arvin Bhatnagar",email:"abhatnag@us.ibm.com",commits:2},{name:"Hestia Zhang",email:"Hestia.Zhang@ibm.com",commits:2},{name:"Lauren K Li",email:"Lauren.Li@ibm.com",commits:2},{name:"Prasang Prajapati",email:"Prasang.A.Prajapati@ibm.com",commits:2},{name:"PrasangAPrajapati",email:"Prasang.A.Prajapati@ibm.com",commits:2},{name:"shikunli",email:"shikunli@cn.ibm.com",commits:2},{name:"KRISTINA MAYO",email:"ktopchi@us.ibm.com",commits:1},{name:"Keng-Hui Beall",email:"kdbeall@ibm.com",commits:1},{name:"Nimma Likhitha",email:"Likhitha.Nimma@ibm.com",commits:1}]},filePathRelative:"Docs/knownissues.md"};export{i as data};
diff --git a/assets/language_references.html.4d36ef0c.js b/assets/language_references.html.04872726.js
similarity index 91%
rename from assets/language_references.html.4d36ef0c.js
rename to assets/language_references.html.04872726.js
index 81b17d5a9..33be97542 100644
--- a/assets/language_references.html.4d36ef0c.js
+++ b/assets/language_references.html.04872726.js
@@ -1 +1 @@
-import{r as t,o as s,a,b as e,d as r,F as l,e as o}from"./app.f6cb3ed9.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const i={},_=e("h1",{id:"language-references",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#language-references","aria-hidden":"true"},"#"),o(" Language References")],-1),d=e("p",null,"The IBM Z Open Editor ships with IBM language servers for COBOL, PL/I, HLASM, and REXX. These language servers follow the language specification as documented here:",-1),h={href:"https://www.ibm.com/docs/en/cobol-zos/6.4",target:"_blank",rel:"noopener noreferrer"},f=o("Enterprise COBOL for z/OS V6.4 documentation"),p={href:"https://www.ibm.com/docs/en/epfz/6.1",target:"_blank",rel:"noopener noreferrer"},u=o("Enterprise PL/I for z/OS V6.1 documentation"),m={href:"https://www.ibm.com/docs/en/hla-and-tf/1.6",target:"_blank",rel:"noopener noreferrer"},g=o("High Level Assembler and Toolkit V1.6"),w={href:"https://www.ibm.com/docs/en/zos/3.1.0?topic=tsoe-zos-rexx-users-guide",target:"_blank",rel:"noopener noreferrer"},b=o("z/OS 3.1 TSO/E REXX"),L={href:"https://www.ibm.com/docs/en/SSLTBW_3.1.0/pdf/ieab600_v3r1.pdf",target:"_blank",rel:"noopener noreferrer"},k=o("z/OS MVS JCL (Job Control Language) 3.1 documentation");function O(x,E){const n=t("ExternalLinkIcon");return s(),a(l,null,[_,d,e("ul",null,[e("li",null,[e("a",h,[f,r(n)])]),e("li",null,[e("a",p,[u,r(n)])]),e("li",null,[e("a",m,[g,r(n)])]),e("li",null,[e("a",w,[b,r(n)])]),e("li",null,[e("a",L,[k,r(n)])])])],64)}var B=c(i,[["render",O]]);export{B as default};
+import{r as t,o as s,a,b as e,d as r,F as l,e as o}from"./app.daa93c96.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const i={},_=e("h1",{id:"language-references",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#language-references","aria-hidden":"true"},"#"),o(" Language References")],-1),d=e("p",null,"The IBM Z Open Editor ships with IBM language servers for COBOL, PL/I, HLASM, and REXX. These language servers follow the language specification as documented here:",-1),h={href:"https://www.ibm.com/docs/en/cobol-zos/6.4",target:"_blank",rel:"noopener noreferrer"},f=o("Enterprise COBOL for z/OS V6.4 documentation"),p={href:"https://www.ibm.com/docs/en/epfz/6.1",target:"_blank",rel:"noopener noreferrer"},u=o("Enterprise PL/I for z/OS V6.1 documentation"),m={href:"https://www.ibm.com/docs/en/hla-and-tf/1.6",target:"_blank",rel:"noopener noreferrer"},g=o("High Level Assembler and Toolkit V1.6"),w={href:"https://www.ibm.com/docs/en/zos/3.1.0?topic=tsoe-zos-rexx-users-guide",target:"_blank",rel:"noopener noreferrer"},b=o("z/OS 3.1 TSO/E REXX"),L={href:"https://www.ibm.com/docs/en/SSLTBW_3.1.0/pdf/ieab600_v3r1.pdf",target:"_blank",rel:"noopener noreferrer"},k=o("z/OS MVS JCL (Job Control Language) 3.1 documentation");function O(x,E){const n=t("ExternalLinkIcon");return s(),a(l,null,[_,d,e("ul",null,[e("li",null,[e("a",h,[f,r(n)])]),e("li",null,[e("a",p,[u,r(n)])]),e("li",null,[e("a",m,[g,r(n)])]),e("li",null,[e("a",w,[b,r(n)])]),e("li",null,[e("a",L,[k,r(n)])])])],64)}var B=c(i,[["render",O]]);export{B as default};
diff --git a/assets/learning.html.b7c3f27c.js b/assets/learning.html.1c26815c.js
similarity index 96%
rename from assets/learning.html.b7c3f27c.js
rename to assets/learning.html.1c26815c.js
index d4d751be4..45c69f533 100644
--- a/assets/learning.html.b7c3f27c.js
+++ b/assets/learning.html.1c26815c.js
@@ -1 +1 @@
-import{r as t,o as a,a as s,b as e,d as o,F as i,e as r}from"./app.f6cb3ed9.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const l={},d=e("h1",{id:"learning-resources",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#learning-resources","aria-hidden":"true"},"#"),r(" Learning Resources")],-1),h=e("h2",{id:"references",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#references","aria-hidden":"true"},"#"),r(" References")],-1),_={href:"https://www.ibm.com/docs/en/cobol-zos/6.3",target:"_blank",rel:"noopener noreferrer"},f=r("Enterprise COBOL for z/OS V6.3 documentation"),m={href:"https://www.ibm.com/docs/en/epfz/5.3",target:"_blank",rel:"noopener noreferrer"},p=r("Enterprise PL/I for z/OS V5.3 documentation"),u={href:"https://www.ibm.com/docs/en/hla-and-tf/1.6",target:"_blank",rel:"noopener noreferrer"},b=r("IBM High Level Assembler for z/OS documentation"),g={href:"https://www.ibm.com/docs/en/zos/2.5.0?topic=tsoe-zos-rexx-reference",target:"_blank",rel:"noopener noreferrer"},w=r("IBM z/OS TSO/E REXX Reference"),x=e("h2",{id:"training",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#training","aria-hidden":"true"},"#"),r(" Training")],-1),k={href:"https://masterthemainframe.com/",target:"_blank",rel:"noopener noreferrer"},z=r("Master the Mainframe"),E=r(" education program and competition.");function O(B,L){const n=t("ExternalLinkIcon");return a(),s(i,null,[d,h,e("ul",null,[e("li",null,[e("a",_,[f,o(n)])]),e("li",null,[e("a",m,[p,o(n)])]),e("li",null,[e("a",u,[b,o(n)])]),e("li",null,[e("a",g,[w,o(n)])])]),x,e("ul",null,[e("li",null,[e("a",k,[z,o(n)]),E])])],64)}var V=c(l,[["render",O]]);export{V as default};
+import{r as t,o as a,a as s,b as e,d as o,F as i,e as r}from"./app.daa93c96.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const l={},d=e("h1",{id:"learning-resources",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#learning-resources","aria-hidden":"true"},"#"),r(" Learning Resources")],-1),h=e("h2",{id:"references",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#references","aria-hidden":"true"},"#"),r(" References")],-1),_={href:"https://www.ibm.com/docs/en/cobol-zos/6.3",target:"_blank",rel:"noopener noreferrer"},f=r("Enterprise COBOL for z/OS V6.3 documentation"),m={href:"https://www.ibm.com/docs/en/epfz/5.3",target:"_blank",rel:"noopener noreferrer"},p=r("Enterprise PL/I for z/OS V5.3 documentation"),u={href:"https://www.ibm.com/docs/en/hla-and-tf/1.6",target:"_blank",rel:"noopener noreferrer"},b=r("IBM High Level Assembler for z/OS documentation"),g={href:"https://www.ibm.com/docs/en/zos/2.5.0?topic=tsoe-zos-rexx-reference",target:"_blank",rel:"noopener noreferrer"},w=r("IBM z/OS TSO/E REXX Reference"),x=e("h2",{id:"training",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#training","aria-hidden":"true"},"#"),r(" Training")],-1),k={href:"https://masterthemainframe.com/",target:"_blank",rel:"noopener noreferrer"},z=r("Master the Mainframe"),E=r(" education program and competition.");function O(B,L){const n=t("ExternalLinkIcon");return a(),s(i,null,[d,h,e("ul",null,[e("li",null,[e("a",_,[f,o(n)])]),e("li",null,[e("a",m,[p,o(n)])]),e("li",null,[e("a",u,[b,o(n)])]),e("li",null,[e("a",g,[w,o(n)])])]),x,e("ul",null,[e("li",null,[e("a",k,[z,o(n)]),E])])],64)}var V=c(l,[["render",O]]);export{V as default};
diff --git a/assets/locating_local_client_logs.html.e1a883b2.js b/assets/locating_local_client_logs.html.f487be4e.js
similarity index 99%
rename from assets/locating_local_client_logs.html.e1a883b2.js
rename to assets/locating_local_client_logs.html.f487be4e.js
index 1d8e31996..7135745db 100644
--- a/assets/locating_local_client_logs.html.e1a883b2.js
+++ b/assets/locating_local_client_logs.html.f487be4e.js
@@ -1 +1 @@
-import{r as t,o as s,a,b as e,d as i,w as d,F as c,e as o,c as n}from"./app.f6cb3ed9.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";var g="/zopeneditor-about/assets/editor-log-info.f9d45119.png";const u={},p=e("h1",{id:"troubleshooting-using-log-files",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#troubleshooting-using-log-files","aria-hidden":"true"},"#"),o(" Troubleshooting using log files")],-1),f=e("p",null,"You can enable logging for IBM Z Open Editor to produce detailed logs that can be used to troubleshoot problems by providing more information and a trace about the activities the editor is performing.",-1),m=o("You can enable logging through a "),w=o("user preference setting"),b=n(' called zopeneditor.logger. In the VS Code Preferences editor, select from the allowed log levels: DEBUG, INFO (default), WARN, ERROR, and OFF.',15),v=e("p",null,"After logging is enabled, you can find the logging output in two places:",-1),_=e("li",null,[o("In the VS Code Output panel, by selecting "),e("code",null,"IBM Z Open Editor"),o(" from the drop-down list.")],-1),x=o("A log file written to your disk that can be shared with technical support (if you are entitled to it) or attached to the issue you file against our "),y={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},I=o("public issues repository on GitHub"),E=o(". The first line in the VS Code Output panel will contain the absolute path to where the file is located on your system."),C=n('
      Use the log file for troubleshooting issues with the information provided. For example, when trying to understand why a specific include file was not found by the editor, the log file produced under the DEBUG log level will give you a trace of the editor's activities for finding ZAPP files in your workspaces, the property groups it used, as well as in which locations it is looking. You can search in the log to see where an initial request for a specific file was made, the steps of processing the request, as well as any errors that were reported. Because the requests for all the include files in a program happen in parallel, each request will have a unique request ID that will help in distinguishing the concurrent events in the log.
       Finding versions of all VS Code extensions installed
      Enabling logging also provides information that technical support will be asking for. To retrieve it:
      1. Ensure that your IBM Z Open Editor logger preference is set to DEBUG.
      2. In the Output console window, select IBM Z Open Editor from the drop-down list. The following information will be listed:
        • IBM Z Open Editor version
        • Editor platform and version
        • Editor Installation information
        • Java SDK configuration location and memory allocation
        • Key user settings
        • Zowe Explorer VS Code Extension version
        • Other VS Code Extensions visible
        CRW Log Info
       Locating VS Code extension and LSP log files on the local client
      In addition to the Z Open Editor log file, there are other log files that can help with troubleshooting. For example, Zowe Explorer has implemented the same mechanism of selecting the log level from Settings, showing the content in the VS Code Output view, and writing it to a file that you can find by looking at the first line. Here a reference for where the extension and other relevant log files are typically located:
      Log typeLocation
      Main logThe location is specified in output console window on 2nd line. 
      ** The log file is available at...
      • Windows example: C:\\Users\\username\\AppData\\Roaming\\Code\\logs\\20200921T153526\\exthost1\\IBM.zopeneditor\\zopeneditor-1-1-0.log
      • Mac example: /Users/username/Library/Application Support/Code/logs/20200928T093225/exthost5/IBM.zopeneditor/zopeneditor-1-1-0.log
      Language Server Protocol (LSP) logFind the line that begins with the following sentence to locate the LSP logs: 
       ** ZLanguageServer: Will start a language server with command... 

      Then, find the -data, tag which immediately precedes the LSP log file location.
      • Windows example: C:\\Users\\username\\AppData\\Local\\Temp\\_ws_<id>\\.metadata/.log
      • Mac example: /var/folders/sr/qztfyx3d39z50jgl50ls_b0r0000gn/T/_ws_<id>/.metadata/.log
      Zowe Explorer log
      • Windows example: C:\\Users\\username\\.vscode\\extensions\\zowe.vscode-extension-for-zowe-1.9.0\\logs
      • Mac example: /Users/username/.vscode/extensions/zowe.vscode-extension-for-zowe-1.9.0/logs
      RSE API plug-in for Zowe CLI (RSE CLI plug-in) logsLog files can be found in two locations: 
      • ~\\.zowe\\zowe\\logs\\
      • ~\\.zowe\\imperative\\logs\\
       Finding Zowe CLI version and RSE CLI plug-in version
      In the VS Code Terminal window, enter the applicable commands:
      • Command for Zowe CLI: zowe --version
      • Command for RSE CLI plug-in: zowe plugins list
       Log levels
      IBM Z Open Editor uses the log levels described in the following chart. These levels are listed in order of most to least detailed (with the exception of OFF, which turns off all logging). For example, the DEBUG setting will output detailed debug information as well as messages from the other levels below it: INFO, WARN, and ERROR. In contrast, the ERROR setting will only log important errors.
      Log levelDescription
      DebugIdentifies detailed informational events that are useful for troubleshooting the editor's behavior.
      InfoProvides informative messages that are of general interest to the end user for observing activities performed by the editor.
      WarnIndicates potentially problematic situations that could cause unexpected behaviors or errors.
      ErrorDesignates error events that interrupted the editor in executing an operation as intended.
      OffNothing is logged.
      ',13);function L(S,z){const l=t("RouterLink"),r=t("ExternalLinkIcon");return s(),a(c,null,[p,f,e("p",null,[m,i(l,{to:"/Docs/setting_preferences.html#user-preferences"},{default:d(()=>[w]),_:1}),b]),v,e("ul",null,[_,e("li",null,[x,e("a",y,[I,i(r)]),E])]),C],64)}var B=h(u,[["render",L]]);export{B as default};
+import{r as t,o as s,a,b as e,d as i,w as d,F as c,e as o,c as n}from"./app.daa93c96.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";var g="/zopeneditor-about/assets/editor-log-info.f9d45119.png";const u={},p=e("h1",{id:"troubleshooting-using-log-files",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#troubleshooting-using-log-files","aria-hidden":"true"},"#"),o(" Troubleshooting using log files")],-1),f=e("p",null,"You can enable logging for IBM Z Open Editor to produce detailed logs that can be used to troubleshoot problems by providing more information and a trace about the activities the editor is performing.",-1),m=o("You can enable logging through a "),w=o("user preference setting"),b=n(' called zopeneditor.logger. In the VS Code Preferences editor, select from the allowed log levels: DEBUG, INFO (default), WARN, ERROR, and OFF.',15),v=e("p",null,"After logging is enabled, you can find the logging output in two places:",-1),_=e("li",null,[o("In the VS Code Output panel, by selecting "),e("code",null,"IBM Z Open Editor"),o(" from the drop-down list.")],-1),x=o("A log file written to your disk that can be shared with technical support (if you are entitled to it) or attached to the issue you file against our "),y={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},I=o("public issues repository on GitHub"),E=o(". The first line in the VS Code Output panel will contain the absolute path to where the file is located on your system."),C=n('
      Use the log file for troubleshooting issues with the information provided. For example, when trying to understand why a specific include file was not found by the editor, the log file produced under the DEBUG log level will give you a trace of the editor's activities for finding ZAPP files in your workspaces, the property groups it used, as well as in which locations it is looking. You can search in the log to see where an initial request for a specific file was made, the steps of processing the request, as well as any errors that were reported. Because the requests for all the include files in a program happen in parallel, each request will have a unique request ID that will help in distinguishing the concurrent events in the log.
       Finding versions of all VS Code extensions installed
      Enabling logging also provides information that technical support will be asking for. To retrieve it:
      1. Ensure that your IBM Z Open Editor logger preference is set to DEBUG.
      2. In the Output console window, select IBM Z Open Editor from the drop-down list. The following information will be listed:
        • IBM Z Open Editor version
        • Editor platform and version
        • Editor Installation information
        • Java SDK configuration location and memory allocation
        • Key user settings
        • Zowe Explorer VS Code Extension version
        • Other VS Code Extensions visible
        CRW Log Info
       Locating VS Code extension and LSP log files on the local client
      In addition to the Z Open Editor log file, there are other log files that can help with troubleshooting. For example, Zowe Explorer has implemented the same mechanism of selecting the log level from Settings, showing the content in the VS Code Output view, and writing it to a file that you can find by looking at the first line. Here a reference for where the extension and other relevant log files are typically located:
      Log typeLocation
      Main logThe location is specified in output console window on 2nd line. 
      ** The log file is available at...
      • Windows example: C:\\Users\\username\\AppData\\Roaming\\Code\\logs\\20200921T153526\\exthost1\\IBM.zopeneditor\\zopeneditor-1-1-0.log
      • Mac example: /Users/username/Library/Application Support/Code/logs/20200928T093225/exthost5/IBM.zopeneditor/zopeneditor-1-1-0.log
      Language Server Protocol (LSP) logFind the line that begins with the following sentence to locate the LSP logs: 
       ** ZLanguageServer: Will start a language server with command... 

      Then, find the -data, tag which immediately precedes the LSP log file location.
      • Windows example: C:\\Users\\username\\AppData\\Local\\Temp\\_ws_<id>\\.metadata/.log
      • Mac example: /var/folders/sr/qztfyx3d39z50jgl50ls_b0r0000gn/T/_ws_<id>/.metadata/.log
      Zowe Explorer log
      • Windows example: C:\\Users\\username\\.vscode\\extensions\\zowe.vscode-extension-for-zowe-1.9.0\\logs
      • Mac example: /Users/username/.vscode/extensions/zowe.vscode-extension-for-zowe-1.9.0/logs
      RSE API plug-in for Zowe CLI (RSE CLI plug-in) logsLog files can be found in two locations: 
      • ~\\.zowe\\zowe\\logs\\
      • ~\\.zowe\\imperative\\logs\\
       Finding Zowe CLI version and RSE CLI plug-in version
      In the VS Code Terminal window, enter the applicable commands:
      • Command for Zowe CLI: zowe --version
      • Command for RSE CLI plug-in: zowe plugins list
       Log levels
      IBM Z Open Editor uses the log levels described in the following chart. These levels are listed in order of most to least detailed (with the exception of OFF, which turns off all logging). For example, the DEBUG setting will output detailed debug information as well as messages from the other levels below it: INFO, WARN, and ERROR. In contrast, the ERROR setting will only log important errors.
      Log levelDescription
      DebugIdentifies detailed informational events that are useful for troubleshooting the editor's behavior.
      InfoProvides informative messages that are of general interest to the end user for observing activities performed by the editor.
      WarnIndicates potentially problematic situations that could cause unexpected behaviors or errors.
      ErrorDesignates error events that interrupted the editor in executing an operation as intended.
      OffNothing is logged.
      ',13);function L(S,z){const l=t("RouterLink"),r=t("ExternalLinkIcon");return s(),a(c,null,[p,f,e("p",null,[m,i(l,{to:"/Docs/setting_preferences.html#user-preferences"},{default:d(()=>[w]),_:1}),b]),v,e("ul",null,[_,e("li",null,[x,e("a",y,[I,i(r)]),E])]),C],64)}var B=h(u,[["render",L]]);export{B as default};
diff --git a/assets/migrating_profiles.html.dda1c8c1.js b/assets/migrating_profiles.html.c03adcd7.js
similarity index 97%
rename from assets/migrating_profiles.html.dda1c8c1.js
rename to assets/migrating_profiles.html.c03adcd7.js
index a890e2077..d3f24056b 100644
--- a/assets/migrating_profiles.html.dda1c8c1.js
+++ b/assets/migrating_profiles.html.c03adcd7.js
@@ -1 +1 @@
-import{c as e}from"./app.f6cb3ed9.js";import{_ as o}from"./plugin-vue_export-helper.21dcd24c.js";const i={},r=e('
       Migrating your old Zowe yaml profiles for Zowe v2.0
      When upgrading to Zowe Explorer v2.0, you are still able to use your old YAML based profiles. The following steps are provided in order to keep your old profiles working and utilize them in your workspace:
       Migrating through Zowe CLI
      1. Review your installed Zowe plugins from Zowe CLI by running zowe plugins list and verify that the secure credential store plugin is not installed.
      2. Issue the following command in your terminal zowe scs revert --force.
      3. If the secure credential store plugin is installed, run the following command to uninstall zowe plugins uninstall @zowe/secure-credential-store-for-zowe-cli.
      4. Verify your plugins are updated to a version compatible with Zowe CLI v7.0.0, otherwise you can uninstall your installed Zowe plugins by using zowe plugins uninstall <your zowe plugin name> for each plugin installed.
      5. Install the new version of Zowe CLI by running npm update -g @zowe/cli@zowe-v2-lts.
       Migrating through Zowe Explorer VS Code Extension
      1. If auto-install is disabled, update Zowe Explorer by going to "extensions > Zowe Explorer" in Visual Studio Code and clicking the Update button.
      After performing the previous steps, your old YAML based profiles can be migrated to a team config file with the following command: zowe config convert-profiles.
      ',7);function t(l,n){return r}var d=o(i,[["render",t]]);export{d as default};
+import{c as e}from"./app.daa93c96.js";import{_ as o}from"./plugin-vue_export-helper.21dcd24c.js";const i={},r=e('
       Migrating your old Zowe yaml profiles for Zowe v2.0
      When upgrading to Zowe Explorer v2.0, you are still able to use your old YAML based profiles. The following steps are provided in order to keep your old profiles working and utilize them in your workspace:
       Migrating through Zowe CLI
      1. Review your installed Zowe plugins from Zowe CLI by running zowe plugins list and verify that the secure credential store plugin is not installed.
      2. Issue the following command in your terminal zowe scs revert --force.
      3. If the secure credential store plugin is installed, run the following command to uninstall zowe plugins uninstall @zowe/secure-credential-store-for-zowe-cli.
      4. Verify your plugins are updated to a version compatible with Zowe CLI v7.0.0, otherwise you can uninstall your installed Zowe plugins by using zowe plugins uninstall <your zowe plugin name> for each plugin installed.
      5. Install the new version of Zowe CLI by running npm update -g @zowe/cli@zowe-v2-lts.
       Migrating through Zowe Explorer VS Code Extension
      1. If auto-install is disabled, update Zowe Explorer by going to "extensions > Zowe Explorer" in Visual Studio Code and clicking the Update button.
      After performing the previous steps, your old YAML based profiles can be migrated to a team config file with the following command: zowe config convert-profiles.
      ',7);function t(l,n){return r}var d=o(i,[["render",t]]);export{d as default};
diff --git a/assets/new-content.html.14310bc6.js b/assets/new-content.html.14310bc6.js
new file mode 100644
index 000000000..53eea8872
--- /dev/null
+++ b/assets/new-content.html.14310bc6.js
@@ -0,0 +1 @@
+import{r as a,o as d,a as l,b as e,d as t,w as i,F as h,c as r,e as o}from"./app.daa93c96.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const p={},u=r('
       New Content and Blog Posts
      Welcome to the IBM Z\xAE Open Editor Team Blog. Bookmark this page as we update it regularly with new content such as blog posts, articles, and videos.
       IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.5.0 released
      September 19th, 2023
      For the September 2024 release we reached a major milestone for completing our z/OS Resource Table and summarized all the new capabilities in a new Blog post. Please, share it with all your users. In particular, we are completed our Search capabilities for the table by adding content search for PDS members as well as UNIX System Services files.
      ',5),_=o("The second advanced feature that got significant enhancements is our preprocessor support, which we extended to also work with PL/I programs. Our "),m={href:"https://github.com/IBM/zopeneditor-sample/tree/wazi-main/preprocessor",target:"_blank",rel:"noopener noreferrer"},f=o("samples repository"),w=o(" now provides preprocessor examples in Java and REXX for both target languages as well."),g=e("p",null,"On the free features side we added a new experimental content menu action to expand a COBOL program embedding all the nested copybooks and substituting REPLACING values. The feature is not complete as does not yet cover conditional compilation, but we are looking forward to your feedback.",-1),b=e("p",null,"Finally, we added new commands and options to our RSE API Plugin for Zowe CLI, such as copying content between LPARs, new encoding conversion options, as well as performance tweaks.",-1),v=o("See the full changelog "),I=o("here"),z=o("."),y=e("h3",{id:"ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-4-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-4-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.4.0 released")],-1),B=e("p",null,[e("em",null,"August 12th, 2024")],-1),M=o("Our August 2024 release of Z Open Editor and RSE API Plugin focuses on incremental refinements and fixes. We added many improvements to our "),k=o("Advanced Capabilities"),E=o(" such as the following:"),S=e("li",null,"z/OS Resources Tables, which now features content search and new filter options.",-1),x=e("li",null,"Our Preprocessor support, which now adds support for z/OSMF, a Cancel button, as well as many fixes and small refinements.",-1),C=o("As another highlight, our HLASM editor has been extended to now support "),Z=o("code completion for local macros"),O=o(" showing you all the macros parameters allowing you to use the tab key to navigate from parameter to parameter to fill in values. For operations the code completion mechanism is now also utilized for syntax errors."),P=e("p",null,"For our free content we fix language support issues for PL/I, HLASM, as well as our all new JCL language server. For COBOL we added a first implementation of a long requested feature: code folding. We also made improvements to our RSE API Plugin for Zowe CLI by adding a new command for UNIX System Services and finally providing an installation option for air gap, i.e. installing the plugin without access to the public internet.",-1),L=o("As always see the full changelog "),A=o("here"),W=o("."),D=e("h3",{id:"ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-3-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-3-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.3.0 released")],-1),R=e("p",null,[e("em",null,"June 18th, 2024")],-1),T=o("IBM Z Open Editor 4.3.0 is now available adding support for another language: Job Control Language (JCL). The new language server is a first increment that provides most frequently requested features such as an Outline view, real-time syntax checking, and code completion. We are planning to add more capabilities in the future and look forward to your feedback. See this "),H=o("Blog post"),N=o(" for an overview."),V=o("In addition to this free new language feature, we are also adding to the advanced capabilities for our IDzEE/ADFz audience by completing our preprocessor story with remote preprocessor execution. Run a custom preprocessor on z/OS, perhaps implemented in REXX, using a TSO command that reads a program file in a data set to produce a processed output file to be used by our COBOL language server for editing the program with the preprocessor statements. See our "),J={href:"https://github.com/IBM/zopeneditor-sample/tree/wazi-main/preprocessor",target:"_blank",rel:"noopener noreferrer"},F=o("examples GitHub repository"),j=o(" for demo preprocessor implementations in Java and REXX to get started."),U=o("As always, we also improved our language support addressing changes for the latest PL/I v6.1 January 2024 compiler refresh, fixed bugs reported by the community, and added minor enhancements requested by customers, such as an improved support for editing strings with double-byte characters to avoid truncation issues. See the full list of changes "),G=o("here"),q=o("."),X=e("h3",{id:"ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-2-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-2-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.2.0 released")],-1),Y=e("p",null,[e("em",null,"May 16th, 2024")],-1),K=e("p",null,"We released Z Open Editor and RSE API CLI plugin 4.2.0 with two more additions to our Advanced Features set:",-1),Q=e("ol",null,[e("li",null,"We added a brand new capability for HLASM developers to work with macro files showing hovers, document links, go to definition, and code completion for macros provided in local files."),e("li",null,"We also updated the z/OS Resource table with UNIX System Services support to provide you with the same capabilities to browse, filter, sort, open, download, upload, create, and copy your unix folders and files with the same user experience that we added in the 4.0.0 release for MVS and JES.")],-1),$=o("In addition to the usual bug fixes and refinements, we also added COBOL User Defined Functions support to Z Open Editor as well as enhancements and fixes for our watsonx Code Assistant for Z integration. Find the complete list of changes "),ee=o("here"),oe=o("."),te=e("h3",{id:"ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-1-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-1-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.1.0 released")],-1),ne=e("p",null,[e("em",null,"March 28th, 2024")],-1),se=e("p",null,"Just two weeks after our major 4.0.0 update that focused on adding advanced features to Z Open Editor, we are releasing v4.1.0 with key updates for our watsonx Code Assistant for Z integration and the RSE API Plugin for Zowe CLI.",-1),ie=e("p",null,"We added a graphical end-to-end walkthrough for how to get started and set up for using the Code Assistant's Transform features in Z Open Editor. We also added new ways of navigating from the generated Java code back to the COBOL sources using a VS Code CodeLens. Plus, we fixed various bugs and issues reported by our watsonx users.",-1),re=e("p",null,"For our Zowe CLI plugin we added powerful new commands for performing content searches on the UNIX System Services files. The CLI also introduces new command to a special RSE API for storing key-value pairs. RSE provides this mini key-value database feature that any system programmer or developer can use for their own purposes. You can store configuration information for private use in personal automation scripts or provide data to shared scripts across your team.",-1),ae=o("Also check this "),de={href:"https://medium.com/zowe/custom-credential-managers-in-zowe-explorer-b37faeee4c29",target:"_blank",rel:"noopener noreferrer"},le=o("new Blog post"),he=o(" about how to create your own credentials managers for Zowe CLI. This approach was used in "),ce={href:"https://github.com/zowe/zowe-cli-secrets-for-kubernetes",target:"_blank",rel:"noopener noreferrer"},pe=o("the Kubernetes-based manager that we created in the Zowe project"),ue=o(" that you can run in IBM Wazi for Dev Spaces utilizing OpenShift secrets."),_e=e("h3",{id:"ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-0-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-0-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.0.0 released")],-1),me=e("p",null,[e("em",null,"March 15th, 2024")],-1),fe=o("We released a major update to Z Open Editor. In addition to featuring support for all the latest COBOL, PL/I, CICS, and HLASM languages refresh releases for z/OS 3.1, many RSE API enhancements, IBM Z Open Editor v4.0.0 is now 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 to add 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 the "),we={href:"https://ibm.biz/code-whatsnew",target:"_blank",rel:"noopener noreferrer"},ge=o("IBM Developer for z/OS Documentation"),be=o("."),ve=e("p",null,"To emphasize, none of the other features that you were using in previous releases are impacted by the update. Previous features are still available for free and will still be maintained and enhanced as always. We are also still fully committed to supporting z/OSMF and RSE API for the free as well as advanced capabilities.",-1),Ie=e("p",null,"Only the following three new features require a license. Our goal is to provide more and more advanced features such as these to Z Open Editor in the future:",-1),ze=e("ol",null,[e("li",null,"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."),e("li",null,"z/OS Resources table: an all-new feature rich 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."),e("li",null,"Advanced Dependency-Based user build error reporting: User build logs are now automatically downloaded, parsed, and presented in the editor's Problems view with 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.")],-1),ye=o("See the "),Be=o("Advanced Capabilities"),Me=o(" section in our docs for a complete overview of these new capabilities."),ke=e("p",null,"As this is a major version release, we also upgraded some of our dependencies requiring newer versions of VS Code (1.81.0), Zowe CLI (7.21.3), and Zowe Explorer (2.14.1).",-1),Ee=o("Go "),Se=o("here"),xe=o(" for the full list of changes."),Ce=o("Also check out the completely redesigned "),Ze={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopendebug",target:"_blank",rel:"noopener noreferrer"},Oe=o("IBM Z Open Debug v4.0.0"),Pe=o(" VS Code extension. It is now using Zowe CLI profiles as well and provides an all-new Zowe Explorer inspired Debugger Profiles view for a seamless integration of the IBM z/OS Debugger into the Z Open Editor/Zowe Explorer-based user experience."),Le=e("h3",{id:"ibm-z-open-editor-with-ibm-watsonx-code-assistant-for-z-v3-4-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-with-ibm-watsonx-code-assistant-for-z-v3-4-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor with IBM watsonx Code Assistant for Z v3.4.0 released")],-1),Ae=e("p",null,[e("em",null,"February 29th, 2024")],-1),We=e("p",null,"We released IBM Z Open Editor v3.4.0. It introduces an all new user experience for generating Java classes in watsonx Code Assistant for Z. The COBOL-centric class generation preview of previous releases has been replaced with an all new Java-centric presentation. Users can now preview the Java classes to be generated in an expandable table view that outlines the variable and method member names next to their mapped COBOL names. They can click hyperlinks within the mapping view to navigate directly back to the COBOL source code files for comparison. We also redesigned the watsonx Code Assistant for Z tree view to show a breakdown of method members per Java class that can be generated by the assistant's AI component. These methods are based on COBOL section and paragraph names and become available after the initial Java class generation step has been completed. This will make it easy for developer to find the methods in the generated Java classes that they still need to generate using the AI-based transformation.",-1),De=o("We also fixed eight bugs for the core Z Open Editor language support, which were reported by our community. Keep the feedback coming on "),Re={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},Te=o("GitHub"),He=o(". See the "),Ne=o("detailed list of fixes here"),Ve=o("."),Je=e("h3",{id:"ibm-z-open-editor-with-ibm-watsonx-code-assistant-for-z-v3-3-3-and-ibm-rse-api-plug-in-for-zowe-cli-v3-3-3-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-with-ibm-watsonx-code-assistant-for-z-v3-3-3-and-ibm-rse-api-plug-in-for-zowe-cli-v3-3-3-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor with IBM watsonx Code Assistant for Z v3.3.3 and IBM RSE API Plug-in for Zowe CLI v3.3.3 released")],-1),Fe=e("p",null,[e("em",null,"December 15th, 2023")],-1),je=o("We released IBM Z Open Editor v3.3.3 with various fixes for the editor as well as the watsonx Code Assistant integration. Find the "),Ue=o("detailed list of changes here"),Ge=o("."),qe=e("h3",{id:"ibm-z-open-editor-with-ibm-watsonx-code-assistant-for-z-and-ibm-rse-api-plug-in-for-zowe-cli-v3-3-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-with-ibm-watsonx-code-assistant-for-z-and-ibm-rse-api-plug-in-for-zowe-cli-v3-3-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor with IBM watsonx Code Assistant for Z and IBM RSE API Plug-in for Zowe CLI v3.3.0 released")],-1),Xe=e("p",null,[e("em",null,"October 25th, 2023")],-1),Ye=o("Our next major release of Z Open Editor and the RSE API Plug-in for Zowe CLI is now available. We added many new features such as support for CICS 6.2 Beta and automatic generation of a default ZAPP file if none exists, improved syntax errors for HLASM, added support for SSH keys for user builds, and addressed many enhancement requests and bugs reported by our community. See the complete "),Ke=o("list of changes here"),Qe=o("."),$e=o("This is also the first release that integrates client capabilities for the new IBM watsonx Code Assistant for Z product offering. IBM watsonx Code Assistant uses generative AI to accelerate code generation and increase developer productivity for application modernization. IBM watsonx Code Assistant for Z is now enabled in IBM Z Open Editor to drive the selective and incremental transformation of COBOL business services into Java code. It uses the inventory and analysis tools of IBM Application Discovery and Delivery Intelligence (ADDI) to support development teams in refactoring business services in COBOL, transforming COBOL code to Java code, and validating the resulting outcome. It is a separate product offering that you can purchase and then use with Z Open Editor. Learn more at "),eo={href:"https://www.ibm.com/products/watsonx-code-assistant-zos",target:"_blank",rel:"noopener noreferrer"},oo=o("https://www.ibm.com/products/watsonx-code-assistant-zos"),to=o("."),no=e("h3",{id:"ibm-z-open-editor-v3-2-2-and-ibm-rse-api-plug-in-for-zowe-cli-v3-2-2-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-v3-2-2-and-ibm-rse-api-plug-in-for-zowe-cli-v3-2-2-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor v3.2.2 and IBM RSE API Plug-in for Zowe CLI v3.2.2 released")],-1),so=e("p",null,[e("em",null,"September 15th, 2023")],-1),io=o("We released a fix pack for our Z Open Editor and the RSE API CLI addressing feedback, fixing bugs, and incrementally improving our language support, by fixing two more issues related to conditional compilation. Find the detailed list of fixes with links to Github issues "),ro=o("here"),ao=o("."),lo=e("h3",{id:"ibm-z-open-editor-v3-2-1-and-ibm-rse-api-plug-in-for-zowe-cli-v3-2-1-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-v3-2-1-and-ibm-rse-api-plug-in-for-zowe-cli-v3-2-1-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor v3.2.1 and IBM RSE API Plug-in for Zowe CLI v3.2.1 released")],-1),ho=e("p",null,[e("em",null,"July 19th, 2023")],-1),co=o("We released a fix pack for our Z Open Editor and the RSE API CLI addressing feedback and one regression report we received for v3.2.0. We also incorporated various language fixes for CICS, PL/I, and HLASM. Find the detailed list of fixes with links to Github issues "),po=o("here"),uo=o("."),_o=e("h3",{id:"ibm-z-open-editor-v3-2-0-ibm-rse-api-plug-in-for-zowe-cli-v3-2-0-and-wazi-for-dev-spaces-v3-0-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-v3-2-0-ibm-rse-api-plug-in-for-zowe-cli-v3-2-0-and-wazi-for-dev-spaces-v3-0-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor v3.2.0, IBM RSE API Plug-in for Zowe CLI v3.2.0, and Wazi for Dev Spaces v3.0.0 released")],-1),mo=e("p",null,[e("em",null,"June 16th, 2023")],-1),fo=o("We released version 3.2.0 of Z Open Editor and RSE API Plug-in for Zowe CLI and we shipped the Q2 release of "),wo={href:"https://www.ibm.com/products/z-and-cloud-modernization-stack",target:"_blank",rel:"noopener noreferrer"},go=o("IBM Z and Cloud Modernization Stack"),bo=o(" that features Wazi for Code 3.0.0 that comprises of Wazi for VS Code and Wazi for Dev Spaces. Wazi for Dev Spaces ships as a major release update with version 3.0.0, which is now based on the new Red Hat OpenShift Dev Spaces version 3.6. It is a zero-install experience of a full z/OS Enterprise Application development environment that just completely runs in the browser featuring our Z Open Editor, Z Open Debug, Wazi Analyze, Ansible for z/OS, Zowe Explorer and CLI as well as many more capabilities."),vo=o("With this version we replaced the Eclipse Theia editor that ran our Z Open Editor with VS Code in the browser, which provides the same great user experience of VS Code on the desktop, such as multi-root workspaces and the code snippet gallery. It also now provides full compatibility to most of the extensions from the VS Code marketplace. You are now finally able to utilize great extensions such as "),Io={href:"https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens",target:"_blank",rel:"noopener noreferrer"},zo=o("GitLens"),yo=o(" or the latest "),Bo={href:"https://marketplace.visualstudio.com/items?itemName=redhat.ansible",target:"_blank",rel:"noopener noreferrer"},Mo=o("Red Hat Ansible language extension"),ko=o(", which did not work with Theia. As always you can give our browser-based experience a try using a Red Hat Sandbox as well as other browser-based solutions such as GitHub Codespaces or GitPod. See our "),Eo=o("Getting Started page"),So=o(" for details."),xo=o("As we were preparing for Wazi for Dev Spaces 3.0.0, we did not have a May fix pack release, but we did not stop working on fixes for the issues reported by our community. As you can see from the large size of our detailed "),Co=o("Changelog"),Zo=o(", we addressed 13 issues reported by our "),Oo={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},Po=o("GitHub community"),Lo=o(" as well as many more reported through other channels. We also added many new enhancements such as language updates for COBOL and PL/I:"),Ao=o("For COBOL, we caught up with the "),Wo={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/yuan-jie-song1/2023/04/28/april-2023-documentation-refresh-for-enterprise-co",target:"_blank",rel:"noopener noreferrer"},Do=o("April language refresh for 6.4"),Ro=o("."),To=o("For PL/I, we caught up with the "),Ho={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/di-hu1/2023/03/09/march-2023-documentation-refresh",target:"_blank",rel:"noopener noreferrer"},No=o("March language refresh for 6.1"),Vo=o("."),Jo=e("p",null,[o("We also added various new configuration options based on user feedback. For example, for each language to enable or disable the Problems view and syntax errors shown within the editor using "),e("code",null,"zopeneditor..disableProblems"),o(" while maintaining other language features. It will allow users to continue working in the program with some language features despite parsing issues. We also added user-defined variables to ZAPP files as well as various options to control how include files will be downloaded via Zowe from MVS for user to tweak performance and reliability.")],-1),Fo=e("h3",{id:"ibm-z-open-editor-v3-1-1-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-v3-1-1-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor v3.1.1 released")],-1),jo=e("p",null,[e("em",null,"March 30th, 2023")],-1),Uo=o("We released version 3.1.1 of Z Open Editor with fixes for some regressions found in v3.1.0. See the "),Go=o("list of fixes here"),qo=o("."),Xo=e("h3",{id:"ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v3-1-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v3-1-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v3.1.0 released")],-1),Yo=e("p",null,[e("em",null,"March 10th, 2023")],-1),Ko=e("p",null,"We released version 3.1.0 of Z Open Editor and RSE API Plug-in for Zowe CLI. The main focus of this release were language improvements and fixes as well as scalability and performance.",-1),Qo=o("For PL/I, we caught up with the "),$o={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/di-hu1/2022/10/27/october-2022-documentation-refresh-for-enterprise",target:"_blank",rel:"noopener noreferrer"},et=o("October language refresh for v6.1"),ot=o(". For COBOL, we worked through a long list of issues that you can see in the "),tt=o("detailed Changelog here"),nt=o(". We also added one more set of options to our experimental COBOL source code formatter that allows you to specify how TO and INTO clauses should be formatted and aligned."),st=o("We also tackled various performance issues that users reported when editing very large programs. In particular, issues around using wildcard/glob pattern expressions in the ZAPP file, which could lead to a lot of local directories and files being searched. Through caching we were able to improve load times significantly. On a test system with slow I/O, by editing a program that includes 1000 copybooks located in a large repository with many sub-directories searched using wildcards (e.g. "),it=e("code",null,"**/COPYBOOK/**",-1),rt=o("), we measured a performance gain from 8 minutes to 30 seconds for opening the program and loading the files. On a Mac with a fast SSD, it was just 4 seconds. We also added the same improvements that we made in "),at=o("v3.0.1"),dt=o(" for loading remote include files from MVS in parallel for COBOL to the PL/I language server as well, which leads to a significant performance improvement when opening files with many include files as well as opening several programs at the same time."),lt=e("p",null,"We also added file watchers to ZAPP property groups that monitor local files for changes. Now if you change, add, or delete a local included file in any of our languages that are used by programs opened in the editor, the programs will be updated with the changes immediately on Mac while you type or after you save on Windows.",-1),ht=o("In addition to these changes, you can find in our "),ct=o("Changelog"),pt=o(" many more fixes and refinements for user build, ZAPP, COBOL code formatter, Zowe Explorer's JES view with RSE API, and more."),ut=o("Finally, you are now able to use Z Open Editor in Microsoft's GitHub Codespaces and GitPod with all our capabilities. You can even use it with limited capabilities as a web extension when using Visual Studio Code in a browser, such as vscode.dev or github.dev. We documented how you can try all these browser-based and cloud-based options for free on our "),_t=o("Getting started page"),mt=o("."),ft=e("h3",{id:"ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v3-0-1-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v3-0-1-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v3.0.1 released")],-1),wt=e("p",null,[e("em",null,"January 18th, 2023")],-1),gt=o("Version 3.0.1 is now available fixing several user-reported bugs. See the detailed list "),bt=o("here"),vt=o("."),It=e("h3",{id:"ibm-z-open-editor-v3-0-0-ibm-rse-api-plug-in-for-zowe-cli-v3-0-0-and-wazi-for-dev-spaces-v2-3-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-v3-0-0-ibm-rse-api-plug-in-for-zowe-cli-v3-0-0-and-wazi-for-dev-spaces-v2-3-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor v3.0.0, IBM RSE API Plug-in for Zowe CLI v3.0.0, and Wazi for Dev Spaces v2.3.0 released")],-1),zt=e("p",null,[e("em",null,"November 22nd, 2022")],-1),yt=e("p",null,"IBM Z Open Editor v3.0.0 is a major new release that provides many improvements for end users as well as many optimizations to make it run even better in the cloud on all supported platforms (s390x, x86).",-1),Bt=o("Together with Zowe Explorer 2.4 we improved and simplified the setup of team configuration files in Wazi for Dev Spaces and made a lot of robustness improvements. We also updated user build with IBM Dependency-Based Build adding more features for multi-root workspaces, scoping your builds and filtering the files to upload and download. We removed redundancies between user settings and ZAPP in favor of ZAPP files and simplified the data model for property groups that require a "),Mt=o("simple migration"),kt=o("."),Et=o("We completely refactored our language parsers and reduced the overall size of the extension by another 25% to now just 37.4MB (remember the times when we were way over a 100MB?), improving load times in Red Hat CodeReady Workspaces and Wazi for Dev Spaces even further. The language servers are up-to-date using on the parsers from IBM Developer for z/OS version 16 that are compiled with Java 11 requiring users to upgrade in this release to a Java 11 or newer runtime. With this update comes also a large number of language fixes and improvements for IBM's latest enterprise language versions and particular CICS 6.1. See our "),St=o("release notes"),xt=o(" for the complete list of fixes."),Ct=e("h3",{id:"ibm-z-open-editor-ibm-rse-api-plug-in-for-zowe-cli-and-wazi-for-dev-spaces-v2-2-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-ibm-rse-api-plug-in-for-zowe-cli-and-wazi-for-dev-spaces-v2-2-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi for Dev Spaces v2.2.0 released")],-1),Zt=e("p",null,[e("em",null,"September 20th, 2022")],-1),Ot={href:"https://www.ibm.com/products/z-and-cloud-modernization-stack",target:"_blank",rel:"noopener noreferrer"},Pt=o("IBM Z and Cloud Modernization Stack v2022.3.1"),Lt=o(" is released today and with it updated versions 2.2.0 of IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi for Dev Spaces v2.2.0. Check out the "),At=e("a",{href:"./new-releases"},"Changelog for Z Open Editor and RSE API CLI",-1),Wt=o(" with the details."),Dt=r('
       IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI v2.1.1 released
      August 4th, 2022
      Version 2.1.1 is now available. This release fixed several IBM User Build issues which include adding support for COBOL nested copybooks, enabled user to enter Zowe CLI profile credentials in a popup dialog inside VS Code, fixed handling of file paths with spaces, and fixed various issues running User Build in multi-root workspaces. Check out the full Changelog here.
       IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi for Dev Spaces v2.1.0 released
      June 14th, 2022
      Version 2.1.0 is now available, which adds support for COBOL v6.4, PL/I v6.1, CICS v6.1, and HLASM for IBM z16 and z/OS 2.5. We also fixed many bugs, improved our support for Zowe 2, and implemented various community enhancement requests. See the detailed list here.
      ',6),Rt=o("This release also adds an "),Tt=e("a",{href:"../Docs/zcodeformatting"},"experimental COBOL code formatter",-1),Ht=o(" that is consistent to formatting in IBM Developer for z/OS. We are very interested in "),Nt={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},Vt=o("feedback and ideas for improvements"),Jt=o("."),Ft=r('
       Zowe 2 support added with version 2.0.2
      April 25th, 2022
      IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI version 2.0.2 are now available. This release adds now full support for Zowe 2.0 in particular Zowe Explorer 2, Zowe CLI 7, Zowe API Mediation Layer 2. You can continue using your Zowe CLI 6.x profiles for backwards compatibility, but you must update Zowe Explorer to version 2 to do so. Review our Getting Started with Zowe 2.0 section in the Documentation for details and instructions for how to migrate your 6.x profiles to the new 7.x format.
       IBM Z Open Editor 2.0.0 released
      March 15th, 2022
      ',5),jt=o("IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI version 2.0.0 are now available. They have been released as a major version update to celebrate their availability in IBM Wazi Developer for Workspaces 2.0.0, which is now part of the new "),Ut={href:"https://www.ibm.com/products/z-and-cloud-modernization-stack",target:"_blank",rel:"noopener noreferrer"},Gt=o("IBM Z and Cloud Modernization Stack"),qt=o(" offering. Together with the recently announced "),Xt={href:"https://www.ibm.com/cloud/wazi-as-a-service",target:"_blank",rel:"noopener noreferrer"},Yt=o("IBM Wazi as a Service"),Kt=o(" initiative, you can see how IBM Wazi is enabling the developer experience for Z to be more increasingly run from the Cloud - accelerating how organizations can provide flexible and modern development environments to their developers."),Qt=e("p",null,"A key enhancement of the Z and Cloud Modernization Stack offering is that Z Open Editor now fully supports OpenShift on Linux on Z when running as part of IBM Wazi. This allows you to now access your entire development environment with a browser-based VS Code-like experience all on Z.",-1),$t=o("In addition to supporting the s390x platform, this release focused on quality updates addressing defects, performance improvements, feedback, and enhancement requests submitted by the "),en={href:"https://github.com/IBM/zopeneditor-about/issues?q=is%3Aissue+is%3Aclosed",target:"_blank",rel:"noopener noreferrer"},on=o("Z Open Editor community on GitHub"),tn=o(". See our "),nn=o("Changelog here"),sn=o(" for a full breakdown of all the issues addressed."),rn=e("p",null,"Note, that because Zowe 2.0 was delayed to late April 2022, Z Open Editor 2.0.0 and the RSE API CLI Plug-in still have to be updated to support it. This version still requires Zowe version 1.x. We plan to release a fully Zowe 2.0 supported update of the editor and CLI plugin with the Zowe 2.0 release.",-1),an=e("h3",{id:"ibm-z-open-editor-1-4-1-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-1-4-1-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor 1.4.1 released")],-1),dn=e("p",null,[e("em",null,"November 19th, 2021")],-1),ln=o("IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI 1.4.1 are now available. This release fixes several language support and User Build issues. Additionally, password prompts for invalid or empty credentials during remote copybook and include file resolving have been added to prevent accidental MVS user account lock-outs and allow the use of Zowe profiles without stored credentials. You can find a detailed view of the updates contained in this release in our "),hn=o("Changelog"),cn=o("."),pn=e("h3",{id:"ibm-z-open-editor-1-4-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-1-4-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor 1.4.0 released")],-1),un=e("p",null,[e("em",null,"October 29th, 2021")],-1),_n=o("IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI 1.4.0 are now available. A key focus area of this release was performance. We reduced the size of the VS Code extension to half, which users will see in reduced start-up times and memory footprint. Find the details of the many other fixes and enhancements "),mn=o("here"),fn=o("."),wn=e("h3",{id:"ibm-z-open-editor-1-2-6-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-1-2-6-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor 1.2.6 released")],-1),gn=e("p",null,[e("em",null,"August 19th, 2021")],-1),bn=o("IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI 1.2.6 are now available. We fixed several defects and addressed minor enhancement requests from our community. Plus, we made sure everything still works with Zowe Explorer 1.18.0, which was going through API changes to prepare for its "),vn={href:"https://github.com/zowe/zowe-explorer-vscode/wiki/v2-Conformance-Criteria",target:"_blank",rel:"noopener noreferrer"},In=o("Conformance Criteria"),zn=o(" support. See the detailed "),yn=o("Changelog here"),Bn=o("."),Mn=o('There is also a new Blog post from Scott Davis called "'),kn={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/annalisa-cesa/2021/08/02/ibm-wazi-developer-shortened-to-wazi-developer-wha",target:"_blank",rel:"noopener noreferrer"},En=o("Wazi Developer \u2013 what is behind this name?"),Sn=o('" that offers a larger scope of the positioning of Z Open Editor in Wazi Developer.'),xn=e("h3",{id:"ibm-z-open-editor-1-2-5-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-1-2-5-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor 1.2.5 released")],-1),Cn=e("p",null,[e("em",null,"June 18th, 2021")],-1),Zn=o("IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi Developer 1.2.5 are now available. In addition to various fixes and performance improvements detailed in our "),On=o("Changelog here"),Pn=o(", Wazi Developer for Workspaces is now based on Red Hat CodeReady Workspaces 2.8 and packages Zowe Explorer 1.15.1 as well as Zowe CLI 6.31."),Ln=e("h3",{id:"ibm-z-open-editor-1-2-1-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-1-2-1-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor 1.2.1 released")],-1),An=e("p",null,[e("em",null,"April 21st, 2021")],-1),Wn=o("We released fixes for IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in) with version 1.2.1. For the editor, you will find various "),Dn=o("fixes and improvements"),Rn=o(" for REXX language support in 1.2.1. For the RSE CLI plug-in, we revised and cleaned up output, error and log messages, and implemented various enhancements for single sign-on with the Zowe API Mediation Layer (APIML). For an introduction to using our tools with the Zowe APIML, read "),Tn={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/joe-winchester1/2021/04/14/using-the-ibm-remote-system-explorer-apis-with-the",target:"_blank",rel:"noopener noreferrer"},Hn=o("this new blog post"),Nn=o(" by Joe Winchester, IBM's Zowe technical lead."),Vn=e("h3",{id:"ibm-z-open-editor-ibm-rse-api-plug-in-for-zowe-cli-and-wazi-developer-v1-2-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-ibm-rse-api-plug-in-for-zowe-cli-and-wazi-developer-v1-2-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi Developer v1.2.0 released")],-1),Jn=e("p",null,[e("em",null,"March 19th, 2021")],-1),Fn=o("We released v1.2.0 of our tools today. See this "),jn=e("a",{href:"whats-new-120"},"blog post",-1),Un=o(" for an overview to the main things we added, as well as our Z Open Editor "),Gn={href:"https://marketplace.visualstudio.com/items/IBM.zopeneditor/changelog",target:"_blank",rel:"noopener noreferrer"},qn=o("Changelog"),Xn=o(" for the list of fixes."),Yn=e("p",null,[o("There are also two new blog posts giving you an in-depth look at the "),e("a",{href:"announcing-rexx"},"all new REXX language support"),o(" we added in this release as well as all the "),e("a",{href:"rse-march-120"},"new enhancements for IBM RSE API Plug-in for Zowe CLI"),o(".")],-1),Kn=e("h3",{id:"ibm-db2-for-z-os-developer-extension-v1-1-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-db2-for-z-os-developer-extension-v1-1-0-released","aria-hidden":"true"},"#"),o(" IBM Db2 for z/OS Developer Extension v1.1.0 released")],-1),Qn=e("p",null,[e("em",null,"February 23rd, 2021")],-1),$n=o("The latest release of IBM Db2 for z/OS Developer Extension is now available on the "),es={href:"https://marketplace.visualstudio.com/items?itemName=IBM.db2forzosdeveloperextension",target:"_blank",rel:"noopener noreferrer"},os=o("Visual Studio Code marketplace"),ts=o(". In this release, the extension delivers the following key features:"),ns=e("ol",null,[e("li",null,"Full support on native SQL stored procedure (NSP). Developers can deploy the NSP with different options, debug the NSP (including nested NSP) and run the NSP."),e("li",null,"Run SQL from anywhere. Developers can highlight and run SQL DIRECTLY from other types of language source code files, like Cobol file, C file, Java file, JavaScript/Python files, and so on (you name it), so that they don\u2019t need to copy/paste the statement to another .sql file or twist the SQLs to validate the result."),e("li",null,"More commit/rollback setting for SQL execution.")],-1),ss=o("You can read more about these new features "),is={href:"https://community.ibm.com/community/user/hybriddatamanagement/blogs/calene-janacek1/2021/02/23/announcing-ibm-db2-for-zos-developer-extension-11",target:"_blank",rel:"noopener noreferrer"},rs=o("here"),as=o("."),ds=e("h3",{id:"ibm-z-open-editor-and-rse-cli-plug-in-release-1-1-2-and-new-blog-of-ibm-user-build",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-rse-cli-plug-in-release-1-1-2-and-new-blog-of-ibm-user-build","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and RSE CLI Plug-in release 1.1.2, and new blog of IBM User Build")],-1),ls=e("p",null,[e("em",null,"December 9th, 2020")],-1),hs=o("We released v1.1.2 of Z Open Editor and the RSE CLI plug-in adding "),cs={href:"https://marketplace.visualstudio.com/items/IBM.zopeneditor/changelog",target:"_blank",rel:"noopener noreferrer"},ps=o("some exciting new features"),us=o(" for High Level Assembler developers working with macros and international customers working with special characters in EBCDIC."),_s=e("p",null,[o("We also added a new post to our team blog giving you an introduction and overview to Z Open Editor's User Build capability: "),e("a",{href:"userbuild-blog"},"IBM Z\xAE Open Editor makes building COBOL, PL/I, and HLASM applications easier with User Build"),o(".")],-1),ms=e("h3",{id:"ibm-z-open-editor-and-rse-api-plug-in-for-zowe-cli-1-1-1-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-rse-api-plug-in-for-zowe-cli-1-1-1-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and RSE API Plug-in for Zowe CLI 1.1.1 released")],-1),fs=e("p",null,[e("em",null,"November 6th, 2020")],-1),ws=o("We released v1.1.1 of Z Open Editor and the RSE API Plug-in to catch up with the latest v1.10.1 release of Zowe Explorer fully supporting now "),gs={href:"https://docs.zowe.org/stable/user-guide/cli-usingcli.html#base-profiles",target:"_blank",rel:"noopener noreferrer"},bs=o("Zowe CLI Base Profiles"),vs=o(" with "),Is={href:"https://ibm.github.io/zopeneditor-about/Blog/rse-october-110.html#use-json-web-tokens-jwt-for-authentication-with-the-host",target:"_blank",rel:"noopener noreferrer"},zs=o("RSE API JWT tokens"),ys=o(" as well. Plus, we fixed "),Bs={href:"https://marketplace.visualstudio.com/items/IBM.zopeneditor/changelog",target:"_blank",rel:"noopener noreferrer"},Ms=o("a couple of bugs"),ks=o(" reported by "),Es={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},Ss=o("our community"),xs=o("."),Cs=o("To get the full package go to our download site here: "),Zs={href:"https://ibm.github.io/mainframe-downloads/downloads.html#wazi",target:"_blank",rel:"noopener noreferrer"},Os=o("https://ibm.github.io/mainframe-downloads/downloads.html#wazi"),Ps=e("p",null,[o("In the coming weeks we will also be publishing more media content around Wazi Developer. We start today with a new blog post about "),e("a",{href:"./ocp-ssl-cert"},"configuring Wazi Developer for Workspaces in OpenShift with certificates"),o(".")],-1),Ls=e("h3",{id:"ibm-wazi-developer-for-red-hat-codeready-workspaces-1-1-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-wazi-developer-for-red-hat-codeready-workspaces-1-1-released","aria-hidden":"true"},"#"),o(" IBM Wazi Developer for Red Hat CodeReady Workspaces 1.1 released")],-1),As=e("p",null,[e("em",null,"October 30th, 2020")],-1),Ws=o("IBM Z Open Editor is part of the overall "),Ds={href:"https://www.ibm.com/docs/en/wdfrhcw/1.4.0?topic=whats-new",target:"_blank",rel:"noopener noreferrer"},Rs=o("IBM Wazi Developer for Red Hat CodeReady Workspaces 1.1"),Ts=o(" offering now, which was released today. Wazi Developer is a packaging of various developer components for VS Code as well as Eclipse. If you are a Z Open Editor user you might particularly interested in the Z Debug extension for VS Code and the updated RSE API Zowe CLI Plug-in v1.1.0. We have a "),Hs=e("a",{href:"rse-october-110"},"detailed Blog post here",-1),Ns=o(" with all the new features we added to the RSE API CLI Plug-in."),Vs=e("p",null,[o("Wazi Developer also contains solution components for "),e("a",{href:"./ibm-wazi-development-client-introduction-blog"},"developing from the Hybrid Cloud"),o(" utilizing Red Hat CodeReady Workspaces 2.3 on OpenShift 4.3 with our Z Open Editor and Debug. Plus, the Wazi Sandbox component that provides a fully virtualized z/OS environment, which enables development and testing of z/OS applications on Red Hat OpenShift running on x86 hardware.")],-1),Js=o("Go here for an overview with videos and blog post: "),Fs={href:"https://www.ibm.com/products/wazi-developer",target:"_blank",rel:"noopener noreferrer"},js=o("https://www.ibm.com/products/wazi-developer"),Us=o("The downloads of the client tools as well as links to the Cloud solution installation instructions are available on our new "),Gs={href:"https://ibm.github.io/mainframe-downloads/downloads.html#wazi",target:"_blank",rel:"noopener noreferrer"},qs=o("Mainframe Downloads site"),Xs=o("."),Ys=e("p",null,[o("Also check the "),e("a",{href:"(https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/5/899/ENUSLP20-0515/index.html&request_locale=en)"},"original announcement"),o(" with more details for what is exactly included in this offering.")],-1),Ks=e("h3",{id:"ibm-db2-for-z-os-developer-extension-0-5-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-db2-for-z-os-developer-extension-0-5-0-released","aria-hidden":"true"},"#"),o(" IBM Db2 for z/OS Developer Extension 0.5.0 released")],-1),Qs=e("p",null,[e("em",null,"October 27th, 2020")],-1),$s=o("The latest release of IBM Db2 for z/OS Developer Extension is now available on the "),ei={href:"https://marketplace.visualstudio.com/items?itemName=IBM.db2forzosdeveloperextension",target:"_blank",rel:"noopener noreferrer"},oi=o("Visual Studio Code Marketplace"),ti=o("."),ni=e("p",null,"Db2 Developer Extension 0.5.0 continues to simplify and modernize the experience of developing SQL applications for Db2 for z/OS by providing the ability to create Db2 connections, SQL execution support, syntax checking, code completion, and signature help.",-1),si=o("You can read more about these new features "),ii={href:"https://community.ibm.com/community/user/hybriddatamanagement/blogs/eric-radzinski1/2020/10/27/announcing-ibm-db2-for-zos-developer-extension-050?CommunityKey=621c2a2a-01f9-4b5",target:"_blank",rel:"noopener noreferrer"},ri=o("here"),ai=o("."),di=e("h3",{id:"z-open-editor-1-1-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#z-open-editor-1-1-0-released","aria-hidden":"true"},"#"),o(" Z Open Editor 1.1.0 released")],-1),li=e("p",null,[e("em",null,"October 23rd, 2020")],-1),hi=o("IBM Z Open Editor 1.1.0 was released to the "),ci={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},pi=o("VS Code Marketplace"),ui=o(". This release fully integrates the IBM User Build extension and expands its capabilities to support building PL/I and HLASM applications as well. We are also adding new features to property groups such as language-specific scoping with compiler options that configure the editor, as well as a complete new representation of property groups called "),_i=e("a",{href:"../Docs/zapp"},"ZAPP files",-1),mi=o(". We also finally added full support for the "),fi={href:"https://docs.zowe.org/stable/user-guide/cli-scsplugin.html",target:"_blank",rel:"noopener noreferrer"},wi=o("Zowe Secure Credentials Store Plug-in"),gi=o(" for all Z Open Editor functions such as remote include file resolution or user build."),bi=o("See the complete list of changes "),vi={href:"https://marketplace.visualstudio.com/items/IBM.zopeneditor/changelog",target:"_blank",rel:"noopener noreferrer"},Ii=o("here"),zi=o("."),yi=e("h3",{id:"z-open-editor-1-0-3-released-and-new-eclipse-che-trial",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#z-open-editor-1-0-3-released-and-new-eclipse-che-trial","aria-hidden":"true"},"#"),o(" Z Open Editor 1.0.3 released and new Eclipse Che trial")],-1),Bi=e("p",null,[e("em",null,"August 7th, 2020")],-1),Mi=o("IBM Z Open Editor 1.0.3 was released to the "),ki={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},Ei=o("VS Code Marketplace"),Si=o(" fixing various defects, adding branch labels to the "),xi=o("HLASM Outline view"),Ci=o(", as well as introducing "),Zi=o("custom include file extensions"),Oi=o("."),Pi=o("We also updated our Eclipse Che trial described in "),Li=o("this blog post"),Ai=o(". Now you can use the free Red Hat trial accounts at "),Wi={href:"https://che.openshift.io",target:"_blank",rel:"noopener noreferrer"},Di=o("https://che.openshift.io"),Ri=o(" to run Eclipse Che. With just a few mouse-clicks you can now deploy Z Open Editor there. It is really simple (paste a URL, Go) as it loads everything from the Cloud. See the instructions and our Che Devfile here: "),Ti={href:"https://github.com/IBM/zopeneditor-about/tree/main/che",target:"_blank",rel:"noopener noreferrer"},Hi=o("https://github.com/IBM/zopeneditor-about/tree/main/che"),Ni=e("h3",{id:"new-ibm-vs-code-extension-for-db2-sql-available-now",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#new-ibm-vs-code-extension-for-db2-sql-available-now","aria-hidden":"true"},"#"),o(" New IBM VS Code extension for Db2 SQL available now")],-1),Vi=e("p",null,[e("em",null,"July 30th, 2020")],-1),Ji=o("The first release of IBM Db2 for z/OS Developer Extension is now available on the "),Fi={href:"https://marketplace.visualstudio.com/items?itemName=ibm.db2forzosdeveloperextension",target:"_blank",rel:"noopener noreferrer"},ji=o("Visual Studio Code Marketplace"),Ui=o(". Db2 Developer Extension brings SQL language support to VS Code and to Eclipse Theia."),Gi=o("You can read more about this new extension "),qi={href:"https://developer.ibm.com/mainframe/2020/07/29/announcing-ibm-db2-for-z-os-developer-extension-for-microsoft-visual-studio-code/",target:"_blank",rel:"noopener noreferrer"},Xi=o("here"),Yi=o("."),Ki=e("h3",{id:"vs-code-marketplace-update",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#vs-code-marketplace-update","aria-hidden":"true"},"#"),o(" VS Code Marketplace update")],-1),Qi=e("p",null,[e("em",null,"June 30th, 2020")],-1),$i=o("IBM Z Open Editor 1.0.2 was released to the "),er={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},or=o("VS Code Marketplace"),tr=o(" adding "),nr=o("High Level Assembler"),sr=o(" support now to that version as well."),ir=e("h3",{id:"ibm-wazi-in-the-news",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-wazi-in-the-news","aria-hidden":"true"},"#"),o(" IBM Wazi in the News")],-1),rr=e("p",null,[e("em",null,"June 24th, 2020")],-1),ar=e("p",null,"We released a small bug fix update for IBM Z Open Editor v0.5.2/1.0.1 today that addresses an issue with running our language servers with a Java newer than version 8. Now it works again with Java SDKs released since then, such as LTS 11, 14 etc.",-1),dr=e("p",null,"Since the release of IBM Wazi for Red Hat\xAE CodeReady Workspaces the overall solution and its components have been mentioned and featured throughout the Web in various publications:",-1),lr=o('Patrick Moorhead, "'),hr={href:"https://www.forbes.com/sites/moorinsights/2020/06/22/ibm-wazi-seeks-to-empowers-even-more-developers-on-ibm-z-mainframes/#2589f82d1895",target:"_blank",rel:"noopener noreferrer"},cr=o("IBM Wazi Seeks To Empowers Even More Developers On IBM Z Mainframes"),pr=o('", Forbes Magazine.'),ur=o('Willie Tejada, "'),_r={href:"https://developer.ibm.com/components/ibmz/blogs/willie-tejada-ibm-wazi-announcement/",target:"_blank",rel:"noopener noreferrer"},mr=o("Accelerate cloud-native development with IBM Wazi for Red Hat CodeReady Workspaces"),fr=o(", IBM Developer."),wr=o('Ed Scannell, "'),gr={href:"https://searchdatacenter.techtarget.com/news/252484620/Tool-helps-mainframe-developers-create-cloud-native-apps",target:"_blank",rel:"noopener noreferrer"},br=o("Tool helps mainframe developers create cloud-native apps"),vr=o('", TechTarget Network at SearchDataCenter.com.'),Ir=o('"'),zr={href:"https://www.dbta.com/Editorial/News-Flashes/IBM-Wazi-for-Red-Hat-Code-Ready-Workspaces-Enables-Cloud-Native-Development-on-Z-141420.aspx",target:"_blank",rel:"noopener noreferrer"},yr=o("IBM Wazi for Red Hat Code-Ready Workspaces Enables Cloud-Native Development on Z"),Br=o('", Database Trends and Applications.'),Mr=o('Alan Radding, "'),kr={href:"https://dancingdinosaur.wordpress.com/2020/06/12/ibm-wazi-cloud-native-devops-for-z/",target:"_blank",rel:"noopener noreferrer"},Er=o("IBM Wazi cloud-native devops for Z"),Sr=o('", DancingDinosaur, June 12th.'),xr=o('Danny Mace, "'),Cr={href:"https://www.ibm.com/cloud/blog/announcements/ibm-wazi-for-red-hat-codeready-workspaces",target:"_blank",rel:"noopener noreferrer"},Zr=o("Making Cloud Native Development a Reality for IBM Z"),Or=o('", IBM Cloud.'),Pr=o('Barry Baker, "'),Lr={href:"https://www.ibm.com/blogs/systems/gain-business-agility-with-new-cloud-enabling-solutions-on-ibm-z/",target:"_blank",rel:"noopener noreferrer"},Ar=o("Enhance business agility with new cloud-enabling solutions on IBM Z"),Wr=o(", IBM IT Infrastructure."),Dr=o('Sanjay Chandru, "'),Rr={href:"https://developer.ibm.com/mainframe/2020/05/05/cloud-native-development-on-z-is-real-with-ibm-wazi-for-red-hat-codeready-workspaces/",target:"_blank",rel:"noopener noreferrer"},Tr=o("Cloud native development on Z is real with IBM Wazi for Red Hat CodeReady Workspaces!"),Hr=o('",'),Nr=o('Minaz Merali, "'),Vr={href:"https://mediacenter.ibm.com/media/t/1_dl6sbihe",target:"_blank",rel:"noopener noreferrer"},Jr=o('Introducing IBM Wazi for Red Hat CodeReady Workspaces"'),Fr=o('", IBM Media Center'),jr=o('Z DevOps Talks, "'),Ur={href:"https://developer.ibm.com/mainframe/2020/06/19/z-devops-talks-s1-e13-peter-haumer-talks-wazi-workspaces-bring-your-own-ide-and-much-more/",target:"_blank",rel:"noopener noreferrer"},Gr=o("S1 E13: Peter Haumer talks Wazi Workspaces, Bring Your Own IDE, and Much More"),qr=o('", IBM Mainframe DEV.'),Xr=o('Bill Alexander, "'),Yr={href:"https://developer.ibm.com/mainframe/2020/06/12/whats-new-in-ibm-developer-for-z-os-v14-2-3/",target:"_blank",rel:"noopener noreferrer"},Kr=o("What\u2019s new in IBM Developer for z/OS V14.2.3"),Qr=o('", IBM Mainframe DEV.'),$r=o('Dave McKnight, "'),ea={href:"https://developer.ibm.com/mainframe/2020/06/12/introducing-ibm-remote-system-explorer-api/",target:"_blank",rel:"noopener noreferrer"},oa=o("Introducing IBM Remote System Explorer API"),ta=o('", IBM Mainframe DEV.'),na=o('Rosalind Radcliffe, "'),sa={href:"https://developer.ibm.com/conferences/digital-developer-conference-security-na/devsecops-na/",target:"_blank",rel:"noopener noreferrer"},ia=o("Keynote - DevSecOps for Cloud Native development on IBM Z"),ra=o(", DevSecOps Conference, Day 1, 2:00."),aa=o('Peter Haumer, "'),da={href:"https://developer.ibm.com/conferences/digital-developer-conference-security-na/devsecops-na/",target:"_blank",rel:"noopener noreferrer"},la=o("IBM Z development on IBM Wazi for Red Hat CodeReady Workspaces"),ha=o(", DevSecOps Conference, Day 1, 2:35."),ca=o('Prasang A Prajapati, "'),pa={href:"https://ibm.github.io/zopeneditor-about/Blog/ibm-wazi-development-client-introduction-blog.html",target:"_blank",rel:"noopener noreferrer"},ua=o("Kubernetes-Native Integrated Z Developer Environment with IBM Wazi for Red Hat CodeReady Workspaces Development Client"),_a=o('", Z Open Editor About.'),ma=o('Peter Haumer, "'),fa={href:"https://www.youtube.com/watch?v=9-3oZXmYiNU",target:"_blank",rel:"noopener noreferrer"},wa=o("IBM Wazi for Red Hat CodeReady Workspaces Demo"),ga=o('", YouTube.'),ba=o('Daniel Beall, "'),va={href:"https://ibm.github.io/zopeneditor-about/Blog/hlasm-blog.html",target:"_blank",rel:"noopener noreferrer"},Ia=o("IBM Z Open Editor: A modern IDE for IBM High Level Assembler"),za=o('", Z Open Editor About.'),ya=e("p",null,"(List updated on 6/28.)",-1),Ba=o("Finally, our IBM RSE API Plug-in for Zowe CLI v.1.0.0 has been approved as fully Zowe CLI conformant and is now featured in the Open Mainframe Project's "),Ma={href:"https://www.openmainframeproject.org/projects/zowe/conformance",target:"_blank",rel:"noopener noreferrer"},ka=o("Conformance Gallery"),Ea=o("."),Sa=e("h3",{id:"ibm-wazi-for-red-hat\xAE-codeready-workspaces-available-now",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-wazi-for-red-hat\xAE-codeready-workspaces-available-now","aria-hidden":"true"},"#"),o(" IBM Wazi for Red Hat\xAE CodeReady Workspaces available now")],-1),xa=e("p",null,[e("em",null,"June 19th, 2020")],-1),Ca=o("You can now try out IBM Wazi for Red Hat CodeReady Workspaces Development Client (IBM Wazi Development Client) for a productive in-cloud development experience. The technical preview for IBM Wazi Development Client can be found at the "),Za={href:"https://ibm.github.io/mainframe-downloads/downloads.html/#wazi",target:"_blank",rel:"noopener noreferrer"},Oa=o("Mainframe DEV Center's Downloads page"),Pa=o("."),La=o("Read our new blog post "),Aa=o("Kubernetes-Native Integrated Z Developer Environment with IBM Wazi for Red Hat\xAE CodeReady Workspaces Development Client"),Wa=o(" for an overview to learn more about the features and components of IBM Wazi Development Client."),Da=e("h3",{id:"ibm-z-open-editor-0-5-0-and-1-0-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-0-5-0-and-1-0-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor 0.5.0 and 1.0.0 released")],-1),Ra=e("p",null,[e("em",null,"June 12th, 2020")],-1),Ta=o("IBM Z Open Editor v0.5.0 is released to the VS Code Marketplace. See "),Ha=o("here"),Na=o(" for all the enhancements and fixes."),Va=o("IBM Z Open Editor v1.0.0 adds a new IBM High Level Assembler language server. Unfortunately, by adding this capability our VS Code extension exceeds the maximum code size allowed for VS Code extensions on the Microsoft VS Code Marketplace. Until we reduce the file size you can get the v1.0.0 release only as a "),Ja={href:"https://ibm.github.io/mainframe-downloads/downloads.html/",target:"_blank",rel:"noopener noreferrer"},Fa=o("free download from IBM"),ja=o("."),Ua=o("IBM Z Open Editor v1.0.0 is also part of "),Ga={href:"https://ibm.github.io/mainframe-downloads/downloads.html/",target:"_blank",rel:"noopener noreferrer"},qa=o("IBM Developer for z/OS Enterprise Edition"),Xa=o(". Customers who purchase this edition will then be able to receive technical support for Z Open Editor."),Ya=e("p",null,"To learn more about the new High Level Assembler language server see our Blog post:",-1),Ka=o("IBM Z Open Editor: A modern IDE for IBM High Level Assembler"),Qa=e("h3",{id:"ibm-wazi-for-red-hat-codeready-workspaces-announcement",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-wazi-for-red-hat-codeready-workspaces-announcement","aria-hidden":"true"},"#"),o(" IBM Wazi for Red Hat CodeReady Workspaces announcement")],-1),$a=e("p",null,[e("em",null,"May 5th, 2020")],-1),ed=e("p",null,"We announced today IBM Wazi for Red Hat CodeReady Workspaces in which the Z Open Editor will play a critical part. See the following resources:",-1),od={href:"https://www.ibm.com/products/wazi-for-red-hat-codeready-workspaces",target:"_blank",rel:"noopener noreferrer"},td=o("Main Products page"),nd={href:"https://www.ibm.com/downloads/cas/KLNRXG6N",target:"_blank",rel:"noopener noreferrer"},sd=o("Solution Brief"),id={href:"https://mediacenter.ibm.com/media/t/1_3q7ce3ba",target:"_blank",rel:"noopener noreferrer"},rd=o("Overview Video"),ad={href:"https://mediacenter.ibm.com/media/t/1_iy379suo",target:"_blank",rel:"noopener noreferrer"},dd=o("IBM Think presentation"),ld={href:"https://mediacenter.ibm.com/media/t/1_8roweeco",target:"_blank",rel:"noopener noreferrer"},hd=o("Intro to Cloud Native Development for Z video"),cd=e("h3",{id:"new-z-open-editor-release-and-public-beta-of-ibm-rse-api",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#new-z-open-editor-release-and-public-beta-of-ibm-rse-api","aria-hidden":"true"},"#"),o(" New Z Open Editor release and public beta of IBM RSE API")],-1),pd=e("p",null,[e("em",null,"March 26th, 2020")],-1),ud=o("We released "),_d={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},md=o("IBM Z Open Editor v0.4.7"),fd=o(" with Beta support for "),wd={href:"https://epwt-www.mybluemix.net/software/support/trial/cst/welcomepage.wss?siteId=536&tabId=1045&w=1&_ga=2.68641937.1484814543.1584987187-1152815028.1571427049",target:"_blank",rel:"noopener noreferrer"},gd=o("IBM Remote System Explorer API and the new IBM RSE API Plug-in for Zowe CLI"),bd=o("."),vd=o("See our new Blog post "),Id=o("Interacting with z/OS using IBM RSE API Plug-in for Zowe CLI"),zd=o(" for an overview as well as links to demo videos."),yd=e("h3",{id:"new-article-about-zowe-and-z-open-editor",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#new-article-about-zowe-and-z-open-editor","aria-hidden":"true"},"#"),o(" New article about Zowe and Z Open Editor")],-1),Bd=e("p",null,[e("em",null,"March 16th, 2020")],-1),Md=o("We added a link to "),kd={href:"https://medium.com/@williampereira_80651/zowe-and-vscode-we-love-it-b5b4b8fdc1c1",target:"_blank",rel:"noopener noreferrer"},Ed=o("a new article"),Sd=o(" with videos about using Z Open Editor with Zowe Explorer and other VS Code extensions to our "),xd=o("External Blog Posts and Articles"),Cd=o(" page."),Zd=o("Made various copyedits and refinements to our "),Od=o("Online Help"),Pd=o(" pages."),Ld=e("h3",{id:"updated-code-snippet-library-in-ibm-z\xAE-open-editor-v0-4-3",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#updated-code-snippet-library-in-ibm-z\xAE-open-editor-v0-4-3","aria-hidden":"true"},"#"),o(" Updated Code Snippet library in IBM Z\xAE Open Editor v0.4.3")],-1),Ad=e("p",null,[e("em",null,"December 23rd, 2019")],-1),Wd=o("We released v0.4.3 to "),Dd={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},Rd=o("the marketplace"),Td=o(" with an all new set of code snippets. To read more about it see our latest blog post:"),Hd=o("Improve your z/OS Enterprise developer productivity with IBM Z Open Editor\u2018s code snippets library"),Nd=e("h3",{id:"updated-che-devfile-to-use-ibm-z\xAE-open-editor-v0-4-3-and-zowe-explorer-1-0-1",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#updated-che-devfile-to-use-ibm-z\xAE-open-editor-v0-4-3-and-zowe-explorer-1-0-1","aria-hidden":"true"},"#"),o(" Updated Che devfile to use IBM Z\xAE Open Editor v0.4.3 and Zowe Explorer 1.0.1")],-1),Vd=e("p",null,[e("em",null,"December 23rd, 2019")],-1),Jd=o("If you follow the instructions in our "),Fd=o("Using IBM Z\xAE Open Editor in Eclipse Che"),jd=o(" blog post for creating a new Che Workpspace using our "),Ud={href:"https://raw.githubusercontent.com/IBM/zopeneditor-about/main/che/ibm-z-devfile.yaml",target:"_blank",rel:"noopener noreferrer"},Gd=o("devfile"),qd=o(", you now get the latest releases of the editor (v0.4.3) the Zowe Explorer (v1.0.1)."),Xd=e("h3",{id:"devops-com-article-featuring-ibm-z\xAE-open-editor-s-lsp-capabilities",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#devops-com-article-featuring-ibm-z\xAE-open-editor-s-lsp-capabilities","aria-hidden":"true"},"#"),o(" DevOps.com article featuring IBM Z\xAE Open Editor's LSP capabilities")],-1),Yd=e("p",null,[e("em",null,"December 18th, 2019")],-1),Kd=o("Bob Reselman published "),Qd={href:"https://devops.com/ibm-z-open-editor-support-for-language-server-protocol-is-a-game-changer/",target:"_blank",rel:"noopener noreferrer"},$d=o("a great article about the Language Server Protocol"),el=o(" and uses Z Open Editor as an example."),ol=e("h3",{id:"using-ibm-z\xAE-open-editor-on-the-web",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-ibm-z\xAE-open-editor-on-the-web","aria-hidden":"true"},"#"),o(" Using IBM Z\xAE Open Editor on the Web")],-1),tl=e("p",null,[e("em",null,"December 4th, 2019")],-1),nl=e("p",null,"We added two new articles describing how you can use the IBM Z Open Editor VS Code extension outside of VS Code on Web running in a browser. We show you how to do it with two very popular frameworks:",-1),sl=o("Using Eclipse Che"),il=o("Using Eclipse Theia"),rl=e("h3",{id:"z-devops-talks-podcast",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#z-devops-talks-podcast","aria-hidden":"true"},"#"),o(" Z DevOps Talks podcast")],-1),al=e("p",null,[e("em",null,"December 3rd, 2019")],-1),dl={href:"https://developer.ibm.com/mainframe/2019/12/03/ibm-z-devops-talks-with-rosalind-radcliffe/",target:"_blank",rel:"noopener noreferrer"},ll=o("Rosalind Radcliffe talks"),hl=o(" about our editor, bring-your-own-IDE, DevOps, and future trends."),cl=e("h3",{id:"ibm-systems-magazine-article",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-systems-magazine-article","aria-hidden":"true"},"#"),o(" IBM Systems Magazine Article")],-1),pl=e("p",null,[e("em",null,"September 26th, 2019")],-1),ul=o("Sanjay Chandru published an "),_l={href:"https://ibmsystemsmag.com/IBM-Z/9/2019/ibm-z-open-editor",target:"_blank",rel:"noopener noreferrer"},ml=o("article about IBM Z Open Editor"),fl=o(" and how it fits in perfectly with DevOps for IBM Z."),wl=e("h3",{id:"ibm-z\xAE-open-editor-release-announcement",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z\xAE-open-editor-release-announcement","aria-hidden":"true"},"#"),o(" IBM Z\xAE Open Editor Release Announcement")],-1),gl=e("p",null,[e("em",null,"September 19th, 2019")],-1),bl=o("Read the "),vl={href:"https://developer.ibm.com/mainframe/2019/09/19/ibm-z-open-editor-brings-cobol-and-pl-i-language-support-to-microsoft-visual-studio-code/",target:"_blank",rel:"noopener noreferrer"},Il=o("official announcement"),zl=o(" for the IBM Z Open Editor's first release.");function yl(Bl,Ml){const n=a("ExternalLinkIcon"),s=a("RouterLink");return d(),l(h,null,[u,e("p",null,[_,e("a",m,[f,t(n)]),w]),g,b,e("p",null,[v,t(s,{to:"/Blog/new-releases.html#_4-5-0-2024-09-19"},{default:i(()=>[I]),_:1}),z]),y,B,e("p",null,[M,t(s,{to:"/Docs/advanced_overview.html"},{default:i(()=>[k]),_:1}),E]),e("ul",null,[S,x,e("li",null,[C,t(s,{to:"/Docs/editor_codechanges_hlasm.html#code-completion"},{default:i(()=>[Z]),_:1}),O])]),P,e("p",null,[L,t(s,{to:"/Blog/new-releases.html#_4-4-0-2024-08-12"},{default:i(()=>[A]),_:1}),W]),D,R,e("p",null,[T,t(s,{to:"/Blog/announcing-jcl.html"},{default:i(()=>[H]),_:1}),N]),e("p",null,[V,e("a",J,[F,t(n)]),j]),e("p",null,[U,t(s,{to:"/Blog/new-releases.html#_4-3-0-2024-06-18"},{default:i(()=>[G]),_:1}),q]),X,Y,K,Q,e("p",null,[$,t(s,{to:"/Blog/new-releases.html#_4-2-0-2024-05-16"},{default:i(()=>[ee]),_:1}),oe]),te,ne,se,ie,re,e("p",null,[ae,e("a",de,[le,t(n)]),he,e("a",ce,[pe,t(n)]),ue]),_e,me,e("p",null,[fe,e("a",we,[ge,t(n)]),be]),ve,Ie,ze,e("p",null,[ye,t(s,{to:"/Docs/advanced_overview.html"},{default:i(()=>[Be]),_:1}),Me]),ke,e("p",null,[Ee,t(s,{to:"/Blog/new-releases.html#_4-0-0-2024-03-15"},{default:i(()=>[Se]),_:1}),xe]),e("p",null,[Ce,e("a",Ze,[Oe,t(n)]),Pe]),Le,Ae,We,e("p",null,[De,e("a",Re,[Te,t(n)]),He,t(s,{to:"/Blog/new-releases.html#_3-4-0-2024-02-29"},{default:i(()=>[Ne]),_:1}),Ve]),Je,Fe,e("p",null,[je,t(s,{to:"/Blog/new-releases.html#333---20231215"},{default:i(()=>[Ue]),_:1}),Ge]),qe,Xe,e("p",null,[Ye,t(s,{to:"/Blog/new-releases.html#330---20231025"},{default:i(()=>[Ke]),_:1}),Qe]),e("p",null,[$e,e("a",eo,[oo,t(n)]),to]),no,so,e("p",null,[io,t(s,{to:"/Blog/new-releases.html#_3-2-2-2023-09-15"},{default:i(()=>[ro]),_:1}),ao]),lo,ho,e("p",null,[co,t(s,{to:"/Blog/new-releases.html#_3-2-1-2023-07-19"},{default:i(()=>[po]),_:1}),uo]),_o,mo,e("p",null,[fo,e("a",wo,[go,t(n)]),bo]),e("p",null,[vo,e("a",Io,[zo,t(n)]),yo,e("a",Bo,[Mo,t(n)]),ko,t(s,{to:"/Docs/getting_started.html#using-ibm-z-open-editor-in-cloud-based-editors"},{default:i(()=>[Eo]),_:1}),So]),e("p",null,[xo,t(s,{to:"/Blog/new-releases.html#_3-2-0-2023-06-16"},{default:i(()=>[Co]),_:1}),Zo,e("a",Oo,[Po,t(n)]),Lo]),e("ul",null,[e("li",null,[Ao,e("a",Wo,[Do,t(n)]),Ro]),e("li",null,[To,e("a",Ho,[No,t(n)]),Vo])]),Jo,Fo,jo,e("p",null,[Uo,t(s,{to:"/Blog/new-releases.html#_3-1-1-2023-03-30"},{default:i(()=>[Go]),_:1}),qo]),Xo,Yo,Ko,e("p",null,[Qo,e("a",$o,[et,t(n)]),ot,t(s,{to:"/Blog/new-releases.html#_3-1-0-2023-03-10"},{default:i(()=>[tt]),_:1}),nt]),e("p",null,[st,it,rt,t(s,{to:"/Blog/new-releases.html#_3-0-1-2023-01-18"},{default:i(()=>[at]),_:1}),dt]),lt,e("p",null,[ht,t(s,{to:"/Blog/new-releases.html#_3-1-0-2023-03-10"},{default:i(()=>[ct]),_:1}),pt]),e("p",null,[ut,t(s,{to:"/Docs/getting_started.html#using-ibm-z-open-editor-in-cloud-based-editors"},{default:i(()=>[_t]),_:1}),mt]),ft,wt,e("p",null,[gt,t(s,{to:"/Blog/new-releases.html#_3-0-1-2023-01-18"},{default:i(()=>[bt]),_:1}),vt]),It,zt,yt,e("p",null,[Bt,t(s,{to:"/Docs/zopeneditor_v3.html"},{default:i(()=>[Mt]),_:1}),kt]),e("p",null,[Et,t(s,{to:"/Blog/new-releases.html#_3-0-0-2022-11-22"},{default:i(()=>[St]),_:1}),xt]),Ct,Zt,e("p",null,[e("a",Ot,[Pt,t(n)]),Lt,At,Wt]),Dt,e("p",null,[Rt,Tt,Ht,e("a",Nt,[Vt,t(n)]),Jt]),Ft,e("p",null,[jt,e("a",Ut,[Gt,t(n)]),qt,e("a",Xt,[Yt,t(n)]),Kt]),Qt,e("p",null,[$t,e("a",en,[on,t(n)]),tn,t(s,{to:"/Blog/new-releases.html#_2-0-0-2022-03-15"},{default:i(()=>[nn]),_:1}),sn]),rn,an,dn,e("p",null,[ln,t(s,{to:"/Blog/new-releases.html#_1-4-1-2021-11-19"},{default:i(()=>[hn]),_:1}),cn]),pn,un,e("p",null,[_n,t(s,{to:"/Blog/new-releases.html#_1-4-0-2021-10-29"},{default:i(()=>[mn]),_:1}),fn]),wn,gn,e("p",null,[bn,e("a",vn,[In,t(n)]),zn,t(s,{to:"/Blog/new-releases.html#_1-2-6-2021-08-19"},{default:i(()=>[yn]),_:1}),Bn]),e("p",null,[Mn,e("a",kn,[En,t(n)]),Sn]),xn,Cn,e("p",null,[Zn,t(s,{to:"/Blog/new-releases.html#_1-2-5-2021-06-18"},{default:i(()=>[On]),_:1}),Pn]),Ln,An,e("p",null,[Wn,t(s,{to:"/Blog/new-releases.html#_1-2-1-2021-04-21"},{default:i(()=>[Dn]),_:1}),Rn,e("a",Tn,[Hn,t(n)]),Nn]),Vn,Jn,e("p",null,[Fn,jn,Un,e("a",Gn,[qn,t(n)]),Xn]),Yn,Kn,Qn,e("p",null,[$n,e("a",es,[os,t(n)]),ts]),ns,e("p",null,[ss,e("a",is,[rs,t(n)]),as]),ds,ls,e("p",null,[hs,e("a",cs,[ps,t(n)]),us]),_s,ms,fs,e("p",null,[ws,e("a",gs,[bs,t(n)]),vs,e("a",Is,[zs,t(n)]),ys,e("a",Bs,[Ms,t(n)]),ks,e("a",Es,[Ss,t(n)]),xs]),e("p",null,[Cs,e("a",Zs,[Os,t(n)])]),Ps,Ls,As,e("p",null,[Ws,e("a",Ds,[Rs,t(n)]),Ts,Hs,Ns]),Vs,e("p",null,[Js,e("a",Fs,[js,t(n)])]),e("p",null,[Us,e("a",Gs,[qs,t(n)]),Xs]),Ys,Ks,Qs,e("p",null,[$s,e("a",ei,[oi,t(n)]),ti]),ni,e("p",null,[si,e("a",ii,[ri,t(n)]),ai]),di,li,e("p",null,[hi,e("a",ci,[pi,t(n)]),ui,_i,mi,e("a",fi,[wi,t(n)]),gi]),e("p",null,[bi,e("a",vi,[Ii,t(n)]),zi]),yi,Bi,e("p",null,[Mi,e("a",ki,[Ei,t(n)]),Si,t(s,{to:"/Docs/customizing_the_outline_view.html#hlasm"},{default:i(()=>[xi]),_:1}),Ci,t(s,{to:"/Docs/setting_fileassociations.html"},{default:i(()=>[Zi]),_:1}),Oi]),e("p",null,[Pi,t(s,{to:"/Blog/in-the-cloud-with-che.html"},{default:i(()=>[Li]),_:1}),Ai,e("a",Wi,[Di,t(n)]),Ri,e("a",Ti,[Hi,t(n)])]),Ni,Vi,e("p",null,[Ji,e("a",Fi,[ji,t(n)]),Ui]),e("p",null,[Gi,e("a",qi,[Xi,t(n)]),Yi]),Ki,Qi,e("p",null,[$i,e("a",er,[or,t(n)]),tr,t(s,{to:"/Docs/editor_codechanges_hlasm.html"},{default:i(()=>[nr]),_:1}),sr]),ir,rr,ar,dr,e("ul",null,[e("li",null,[lr,e("a",hr,[cr,t(n)]),pr]),e("li",null,[ur,e("a",_r,[mr,t(n)]),fr]),e("li",null,[wr,e("a",gr,[br,t(n)]),vr]),e("li",null,[Ir,e("a",zr,[yr,t(n)]),Br]),e("li",null,[Mr,e("a",kr,[Er,t(n)]),Sr]),e("li",null,[xr,e("a",Cr,[Zr,t(n)]),Or]),e("li",null,[Pr,e("a",Lr,[Ar,t(n)]),Wr]),e("li",null,[Dr,e("a",Rr,[Tr,t(n)]),Hr]),e("li",null,[Nr,e("a",Vr,[Jr,t(n)]),Fr]),e("li",null,[jr,e("a",Ur,[Gr,t(n)]),qr]),e("li",null,[Xr,e("a",Yr,[Kr,t(n)]),Qr]),e("li",null,[$r,e("a",ea,[oa,t(n)]),ta]),e("li",null,[na,e("a",sa,[ia,t(n)]),ra]),e("li",null,[aa,e("a",da,[la,t(n)]),ha]),e("li",null,[ca,e("a",pa,[ua,t(n)]),_a]),e("li",null,[ma,e("a",fa,[wa,t(n)]),ga]),e("li",null,[ba,e("a",va,[Ia,t(n)]),za])]),ya,e("p",null,[Ba,e("a",Ma,[ka,t(n)]),Ea]),Sa,xa,e("p",null,[Ca,e("a",Za,[Oa,t(n)]),Pa]),e("p",null,[La,t(s,{to:"/Blog/ibm-wazi-development-client-introduction-blog.html"},{default:i(()=>[Aa]),_:1}),Wa]),Da,Ra,e("p",null,[Ta,t(s,{to:"/Blog/new-releases.html#_0-5-0-2020-06-12"},{default:i(()=>[Ha]),_:1}),Na]),e("p",null,[Va,e("a",Ja,[Fa,t(n)]),ja]),e("p",null,[Ua,e("a",Ga,[qa,t(n)]),Xa]),Ya,e("ul",null,[e("li",null,[t(s,{to:"/Blog/hlasm-blog.html"},{default:i(()=>[Ka]),_:1})])]),Qa,$a,ed,e("ul",null,[e("li",null,[e("a",od,[td,t(n)])]),e("li",null,[e("a",nd,[sd,t(n)])]),e("li",null,[e("a",id,[rd,t(n)])]),e("li",null,[e("a",ad,[dd,t(n)])]),e("li",null,[e("a",ld,[hd,t(n)])])]),cd,pd,e("p",null,[ud,e("a",_d,[md,t(n)]),fd,e("a",wd,[gd,t(n)]),bd]),e("p",null,[vd,t(s,{to:"/Blog/rse-march-beta.html"},{default:i(()=>[Id]),_:1}),zd]),yd,Bd,e("ul",null,[e("li",null,[Md,e("a",kd,[Ed,t(n)]),Sd,t(s,{to:"/Blog/external-posts.html"},{default:i(()=>[xd]),_:1}),Cd]),e("li",null,[Zd,t(s,{to:"/Docs/editor_codechanges.html"},{default:i(()=>[Od]),_:1}),Pd])]),Ld,Ad,e("p",null,[Wd,e("a",Dd,[Rd,t(n)]),Td]),e("ul",null,[e("li",null,[t(s,{to:"/Blog/code-snippets.html"},{default:i(()=>[Hd]),_:1})])]),Nd,Vd,e("p",null,[Jd,t(s,{to:"/Blog/in-the-cloud-with-che.html"},{default:i(()=>[Fd]),_:1}),jd,e("a",Ud,[Gd,t(n)]),qd]),Xd,Yd,e("p",null,[Kd,e("a",Qd,[$d,t(n)]),el]),ol,tl,nl,e("ul",null,[e("li",null,[t(s,{to:"/Blog/in-the-cloud-with-che.html"},{default:i(()=>[sl]),_:1})]),e("li",null,[t(s,{to:"/Blog/web-based-with-theia.html"},{default:i(()=>[il]),_:1})])]),rl,al,e("p",null,[e("a",dl,[ll,t(n)]),hl]),cl,pl,e("p",null,[ul,e("a",_l,[ml,t(n)]),fl]),wl,gl,e("p",null,[bl,e("a",vl,[Il,t(n)]),zl])],64)}var Sl=c(p,[["render",yl]]);export{Sl as default};
diff --git a/assets/new-content.html.3dffb483.js b/assets/new-content.html.51179cd8.js
similarity index 75%
rename from assets/new-content.html.3dffb483.js
rename to assets/new-content.html.51179cd8.js
index 1b74b1ad6..75d680949 100644
--- a/assets/new-content.html.3dffb483.js
+++ b/assets/new-content.html.51179cd8.js
@@ -1 +1 @@
-const m={key:"v-4c46bc61",path:"/Blog/new-content.html",title:"New Content and Blog Posts",lang:"en-US",frontmatter:{},excerpt:"",headers:[{level:1,title:"New Content and Blog Posts",slug:"new-content-and-blog-posts",children:[]}],git:{updatedTime:172304606e4,contributors:[{name:"Peter Haumer",email:"phaumer@us.ibm.com",commits:31},{name:"Peter Haumer",email:"4391934+phaumer@users.noreply.github.com",commits:24},{name:"kmaselli",email:"81706519+kmaselli@users.noreply.github.com",commits:7},{name:"Lauren Li",email:"45975633+lauren-li@users.noreply.github.com",commits:6},{name:"Chun Hong Zheng",email:"chunhzh@cn.ibm.com",commits:5},{name:"PETER HAUMER",email:"phaumer@us.ibm.com",commits:5},{name:"Lauren Li",email:"Lauren.Li@ibm.com",commits:2},{name:"Shi Kun Li",email:"shikunli@cn.ibm.com",commits:2},{name:"Billie",email:"BillieJean.Simmons@ibm.com",commits:1},{name:"Billie Simmons",email:"BillieJean.Simmons@ibm.com",commits:1},{name:"KRISTINA MAYO",email:"ktopchi@us.ibm.com",commits:1},{name:"Lauren K Li",email:"Lauren.Li@ibm.com",commits:1},{name:"Min Huang",email:"minhsh@cn.ibm.com",commits:1},{name:"Prasang-A-Prajapati",email:"Prasang.A.Prajapati@ibm.com",commits:1},{name:"shikunli",email:"shikunli@cn.ibm.com",commits:1}]},filePathRelative:"Blog/new-content.md"};export{m as data};
+const m={key:"v-4c46bc61",path:"/Blog/new-content.html",title:"New Content and Blog Posts",lang:"en-US",frontmatter:{},excerpt:"",headers:[{level:1,title:"New Content and Blog Posts",slug:"new-content-and-blog-posts",children:[]}],git:{updatedTime:172669794e4,contributors:[{name:"Peter Haumer",email:"phaumer@us.ibm.com",commits:31},{name:"Peter Haumer",email:"4391934+phaumer@users.noreply.github.com",commits:25},{name:"kmaselli",email:"81706519+kmaselli@users.noreply.github.com",commits:7},{name:"Lauren Li",email:"45975633+lauren-li@users.noreply.github.com",commits:6},{name:"PETER HAUMER",email:"phaumer@us.ibm.com",commits:6},{name:"Chun Hong Zheng",email:"chunhzh@cn.ibm.com",commits:5},{name:"Lauren Li",email:"Lauren.Li@ibm.com",commits:2},{name:"Shi Kun Li",email:"shikunli@cn.ibm.com",commits:2},{name:"Billie",email:"BillieJean.Simmons@ibm.com",commits:1},{name:"Billie Simmons",email:"BillieJean.Simmons@ibm.com",commits:1},{name:"KRISTINA MAYO",email:"ktopchi@us.ibm.com",commits:1},{name:"Lauren K Li",email:"Lauren.Li@ibm.com",commits:1},{name:"Min Huang",email:"minhsh@cn.ibm.com",commits:1},{name:"Prasang-A-Prajapati",email:"Prasang.A.Prajapati@ibm.com",commits:1},{name:"shikunli",email:"shikunli@cn.ibm.com",commits:1}]},filePathRelative:"Blog/new-content.md"};export{m as data};
diff --git a/assets/new-content.html.78851d14.js b/assets/new-content.html.78851d14.js
deleted file mode 100644
index 01573d59f..000000000
--- a/assets/new-content.html.78851d14.js
+++ /dev/null
@@ -1 +0,0 @@
-import{r,o as d,a as l,b as e,d as t,w as i,F as h,e as o,c as a}from"./app.f6cb3ed9.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const p={},u=e("h1",{id:"new-content-and-blog-posts",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#new-content-and-blog-posts","aria-hidden":"true"},"#"),o(" New Content and Blog Posts")],-1),_=e("p",null,"Welcome to the IBM Z\xAE Open Editor Team Blog. Bookmark this page as we update it regularly with new content such as blog posts, articles, and videos.",-1),m=e("h3",{id:"ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-4-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-4-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.4.0 released")],-1),f=e("p",null,[e("em",null,"August 12th, 2024")],-1),w=o("Our August 2024 release of Z Open Editor and RSE API Plugin focuses on incremental refinements and fixes. We added many improvements to our "),g=o("Advanced Capabilities"),b=o(" such as the following:"),v=e("li",null,"z/OS Resources Tables, which now features content search and new filter options.",-1),I=e("li",null,"Our Preprocessor support, which now adds support for z/OSMF, a Cancel button, as well as many fixes and small refinements.",-1),z=o("As another highlight, our HLASM editor has been extended to now support "),y=o("code completion for local macros"),B=o(" showing you all the macros parameters allowing you to use the tab key to navigate from parameter to parameter to fill in values. For operations the code completion mechanism is now also utilized for syntax errors."),M=e("p",null,"For our free content we fix language support issues for PL/I, HLASM, as well as our all new JCL language server. For COBOL we added a first implementation of a long requested feature: code folding. We also made improvements to our RSE API Plugin for Zowe CLI by adding a new command for UNIX System Services and finally providing an installation option for air gap, i.e. installing the plugin without access to the public internet.",-1),k=o("As always see the full changelog "),E=o("here"),x=o("."),S=e("h3",{id:"ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-3-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-3-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.3.0 released")],-1),Z=e("p",null,[e("em",null,"June 18th, 2024")],-1),C=o("IBM Z Open Editor 4.3.0 is now available adding support for another language: Job Control Language (JCL). The new language server is a first increment that provides most frequently requested features such as an Outline view, real-time syntax checking, and code completion. We are planning to add more capabilities in the future and look forward to your feedback. See this "),O=o("Blog post"),P=o(" for an overview."),A=o("In addition to this free new language feature, we are also adding to the advanced capabilities for our IDzEE/ADFz audience by completing our preprocessor story with remote preprocessor execution. Run a custom preprocessor on z/OS, perhaps implemented in REXX, using a TSO command that reads a program file in a data set to produce a processed output file to be used by our COBOL language server for editing the program with the preprocessor statements. See our "),L={href:"https://github.com/IBM/zopeneditor-sample/tree/wazi-main/preprocessor",target:"_blank",rel:"noopener noreferrer"},W=o("examples GitHub repository"),D=o(" for demo preprocessor implementations in Java and REXX to get started."),R=o("As always, we also improved our language support addressing changes for the latest PL/I v6.1 January 2024 compiler refresh, fixed bugs reported by the community, and added minor enhancements requested by customers, such as an improved support for editing strings with double-byte characters to avoid truncation issues. See the full list of changes "),T=o("here"),H=o("."),N=e("h3",{id:"ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-2-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-2-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.2.0 released")],-1),V=e("p",null,[e("em",null,"May 16th, 2024")],-1),J=e("p",null,"We released Z Open Editor and RSE API CLI plugin 4.2.0 with two more additions to our Advanced Features set:",-1),F=e("ol",null,[e("li",null,"We added a brand new capability for HLASM developers to work with macro files showing hovers, document links, go to definition, and code completion for macros provided in local files."),e("li",null,"We also updated the z/OS Resource table with UNIX System Services support to provide you with the same capabilities to browse, filter, sort, open, download, upload, create, and copy your unix folders and files with the same user experience that we added in the 4.0.0 release for MVS and JES.")],-1),j=o("In addition to the usual bug fixes and refinements, we also added COBOL User Defined Functions support to Z Open Editor as well as enhancements and fixes for our watsonx Code Assistant for Z integration. Find the complete list of changes "),U=o("here"),q=o("."),G=e("h3",{id:"ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-1-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-1-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.1.0 released")],-1),X=e("p",null,[e("em",null,"March 28th, 2024")],-1),Y=e("p",null,"Just two weeks after our major 4.0.0 update that focused on adding advanced features to Z Open Editor, we are releasing v4.1.0 with key updates for our watsonx Code Assistant for Z integration and the RSE API Plugin for Zowe CLI.",-1),K=e("p",null,"We added a graphical end-to-end walkthrough for how to get started and set up for using the Code Assistant's Transform features in Z Open Editor. We also added new ways of navigating from the generated Java code back to the COBOL sources using a VS Code CodeLens. Plus, we fixed various bugs and issues reported by our watsonx users.",-1),Q=e("p",null,"For our Zowe CLI plugin we added powerful new commands for performing content searches on the UNIX System Services files. The CLI also introduces new command to a special RSE API for storing key-value pairs. RSE provides this mini key-value database feature that any system programmer or developer can use for their own purposes. You can store configuration information for private use in personal automation scripts or provide data to shared scripts across your team.",-1),$=o("Also check this "),ee={href:"https://medium.com/zowe/custom-credential-managers-in-zowe-explorer-b37faeee4c29",target:"_blank",rel:"noopener noreferrer"},oe=o("new Blog post"),te=o(" about how to create your own credentials managers for Zowe CLI. This approach was used in "),ne={href:"https://github.com/zowe/zowe-cli-secrets-for-kubernetes",target:"_blank",rel:"noopener noreferrer"},se=o("the Kubernetes-based manager that we created in the Zowe project"),ie=o(" that you can run in IBM Wazi for Dev Spaces utilizing OpenShift secrets."),re=e("h3",{id:"ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-0-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v4-0-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v4.0.0 released")],-1),ae=e("p",null,[e("em",null,"March 15th, 2024")],-1),de=o("We released a major update to Z Open Editor. In addition to featuring support for all the latest COBOL, PL/I, CICS, and HLASM languages refresh releases for z/OS 3.1, many RSE API enhancements, IBM Z Open Editor v4.0.0 is now 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 to add 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 the "),le={href:"https://ibm.biz/code-whatsnew",target:"_blank",rel:"noopener noreferrer"},he=o("IBM Developer for z/OS Documentation"),ce=o("."),pe=e("p",null,"To emphasize, none of the other features that you were using in previous releases are impacted by the update. Previous features are still available for free and will still be maintained and enhanced as always. We are also still fully committed to supporting z/OSMF and RSE API for the free as well as advanced capabilities.",-1),ue=e("p",null,"Only the following three new features require a license. Our goal is to provide more and more advanced features such as these to Z Open Editor in the future:",-1),_e=e("ol",null,[e("li",null,"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."),e("li",null,"z/OS Resources table: an all-new feature rich 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."),e("li",null,"Advanced Dependency-Based user build error reporting: User build logs are now automatically downloaded, parsed, and presented in the editor's Problems view with 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.")],-1),me=o("See the "),fe=o("Advanced Capabilities"),we=o(" section in our docs for a complete overview of these new capabilities."),ge=e("p",null,"As this is a major version release, we also upgraded some of our dependencies requiring newer versions of VS Code (1.81.0), Zowe CLI (7.21.3), and Zowe Explorer (2.14.1).",-1),be=o("Go "),ve=o("here"),Ie=o(" for the full list of changes."),ze=o("Also check out the completely redesigned "),ye={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopendebug",target:"_blank",rel:"noopener noreferrer"},Be=o("IBM Z Open Debug v4.0.0"),Me=o(" VS Code extension. It is now using Zowe CLI profiles as well and provides an all-new Zowe Explorer inspired Debugger Profiles view for a seamless integration of the IBM z/OS Debugger into the Z Open Editor/Zowe Explorer-based user experience."),ke=e("h3",{id:"ibm-z-open-editor-with-ibm-watsonx-code-assistant-for-z-v3-4-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-with-ibm-watsonx-code-assistant-for-z-v3-4-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor with IBM watsonx Code Assistant for Z v3.4.0 released")],-1),Ee=e("p",null,[e("em",null,"February 29th, 2024")],-1),xe=e("p",null,"We released IBM Z Open Editor v3.4.0. It introduces an all new user experience for generating Java classes in watsonx Code Assistant for Z. The COBOL-centric class generation preview of previous releases has been replaced with an all new Java-centric presentation. Users can now preview the Java classes to be generated in an expandable table view that outlines the variable and method member names next to their mapped COBOL names. They can click hyperlinks within the mapping view to navigate directly back to the COBOL source code files for comparison. We also redesigned the watsonx Code Assistant for Z tree view to show a breakdown of method members per Java class that can be generated by the assistant's AI component. These methods are based on COBOL section and paragraph names and become available after the initial Java class generation step has been completed. This will make it easy for developer to find the methods in the generated Java classes that they still need to generate using the AI-based transformation.",-1),Se=o("We also fixed eight bugs for the core Z Open Editor language support, which were reported by our community. Keep the feedback coming on "),Ze={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},Ce=o("GitHub"),Oe=o(". See the "),Pe=o("detailed list of fixes here"),Ae=o("."),Le=e("h3",{id:"ibm-z-open-editor-with-ibm-watsonx-code-assistant-for-z-v3-3-3-and-ibm-rse-api-plug-in-for-zowe-cli-v3-3-3-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-with-ibm-watsonx-code-assistant-for-z-v3-3-3-and-ibm-rse-api-plug-in-for-zowe-cli-v3-3-3-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor with IBM watsonx Code Assistant for Z v3.3.3 and IBM RSE API Plug-in for Zowe CLI v3.3.3 released")],-1),We=e("p",null,[e("em",null,"December 15th, 2023")],-1),De=o("We released IBM Z Open Editor v3.3.3 with various fixes for the editor as well as the watsonx Code Assistant integration. Find the "),Re=o("detailed list of changes here"),Te=o("."),He=e("h3",{id:"ibm-z-open-editor-with-ibm-watsonx-code-assistant-for-z-and-ibm-rse-api-plug-in-for-zowe-cli-v3-3-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-with-ibm-watsonx-code-assistant-for-z-and-ibm-rse-api-plug-in-for-zowe-cli-v3-3-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor with IBM watsonx Code Assistant for Z and IBM RSE API Plug-in for Zowe CLI v3.3.0 released")],-1),Ne=e("p",null,[e("em",null,"October 25th, 2023")],-1),Ve=o("Our next major release of Z Open Editor and the RSE API Plug-in for Zowe CLI is now available. We added many new features such as support for CICS 6.2 Beta and automatic generation of a default ZAPP file if none exists, improved syntax errors for HLASM, added support for SSH keys for user builds, and addressed many enhancement requests and bugs reported by our community. See the complete "),Je=o("list of changes here"),Fe=o("."),je=o("This is also the first release that integrates client capabilities for the new IBM watsonx Code Assistant for Z product offering. IBM watsonx Code Assistant uses generative AI to accelerate code generation and increase developer productivity for application modernization. IBM watsonx Code Assistant for Z is now enabled in IBM Z Open Editor to drive the selective and incremental transformation of COBOL business services into Java code. It uses the inventory and analysis tools of IBM Application Discovery and Delivery Intelligence (ADDI) to support development teams in refactoring business services in COBOL, transforming COBOL code to Java code, and validating the resulting outcome. It is a separate product offering that you can purchase and then use with Z Open Editor. Learn more at "),Ue={href:"https://www.ibm.com/products/watsonx-code-assistant-zos",target:"_blank",rel:"noopener noreferrer"},qe=o("https://www.ibm.com/products/watsonx-code-assistant-zos"),Ge=o("."),Xe=e("h3",{id:"ibm-z-open-editor-v3-2-2-and-ibm-rse-api-plug-in-for-zowe-cli-v3-2-2-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-v3-2-2-and-ibm-rse-api-plug-in-for-zowe-cli-v3-2-2-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor v3.2.2 and IBM RSE API Plug-in for Zowe CLI v3.2.2 released")],-1),Ye=e("p",null,[e("em",null,"September 15th, 2023")],-1),Ke=o("We released a fix pack for our Z Open Editor and the RSE API CLI addressing feedback, fixing bugs, and incrementally improving our language support, by fixing two more issues related to conditional compilation. Find the detailed list of fixes with links to Github issues "),Qe=o("here"),$e=o("."),eo=e("h3",{id:"ibm-z-open-editor-v3-2-1-and-ibm-rse-api-plug-in-for-zowe-cli-v3-2-1-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-v3-2-1-and-ibm-rse-api-plug-in-for-zowe-cli-v3-2-1-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor v3.2.1 and IBM RSE API Plug-in for Zowe CLI v3.2.1 released")],-1),oo=e("p",null,[e("em",null,"July 19th, 2023")],-1),to=o("We released a fix pack for our Z Open Editor and the RSE API CLI addressing feedback and one regression report we received for v3.2.0. We also incorporated various language fixes for CICS, PL/I, and HLASM. Find the detailed list of fixes with links to Github issues "),no=o("here"),so=o("."),io=e("h3",{id:"ibm-z-open-editor-v3-2-0-ibm-rse-api-plug-in-for-zowe-cli-v3-2-0-and-wazi-for-dev-spaces-v3-0-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-v3-2-0-ibm-rse-api-plug-in-for-zowe-cli-v3-2-0-and-wazi-for-dev-spaces-v3-0-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor v3.2.0, IBM RSE API Plug-in for Zowe CLI v3.2.0, and Wazi for Dev Spaces v3.0.0 released")],-1),ro=e("p",null,[e("em",null,"June 16th, 2023")],-1),ao=o("We released version 3.2.0 of Z Open Editor and RSE API Plug-in for Zowe CLI and we shipped the Q2 release of "),lo={href:"https://www.ibm.com/products/z-and-cloud-modernization-stack",target:"_blank",rel:"noopener noreferrer"},ho=o("IBM Z and Cloud Modernization Stack"),co=o(" that features Wazi for Code 3.0.0 that comprises of Wazi for VS Code and Wazi for Dev Spaces. Wazi for Dev Spaces ships as a major release update with version 3.0.0, which is now based on the new Red Hat OpenShift Dev Spaces version 3.6. It is a zero-install experience of a full z/OS Enterprise Application development environment that just completely runs in the browser featuring our Z Open Editor, Z Open Debug, Wazi Analyze, Ansible for z/OS, Zowe Explorer and CLI as well as many more capabilities."),po=o("With this version we replaced the Eclipse Theia editor that ran our Z Open Editor with VS Code in the browser, which provides the same great user experience of VS Code on the desktop, such as multi-root workspaces and the code snippet gallery. It also now provides full compatibility to most of the extensions from the VS Code marketplace. You are now finally able to utilize great extensions such as "),uo={href:"https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens",target:"_blank",rel:"noopener noreferrer"},_o=o("GitLens"),mo=o(" or the latest "),fo={href:"https://marketplace.visualstudio.com/items?itemName=redhat.ansible",target:"_blank",rel:"noopener noreferrer"},wo=o("Red Hat Ansible language extension"),go=o(", which did not work with Theia. As always you can give our browser-based experience a try using a Red Hat Sandbox as well as other browser-based solutions such as GitHub Codespaces or GitPod. See our "),bo=o("Getting Started page"),vo=o(" for details."),Io=o("As we were preparing for Wazi for Dev Spaces 3.0.0, we did not have a May fix pack release, but we did not stop working on fixes for the issues reported by our community. As you can see from the large size of our detailed "),zo=o("Changelog"),yo=o(", we addressed 13 issues reported by our "),Bo={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},Mo=o("GitHub community"),ko=o(" as well as many more reported through other channels. We also added many new enhancements such as language updates for COBOL and PL/I:"),Eo=o("For COBOL, we caught up with the "),xo={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/yuan-jie-song1/2023/04/28/april-2023-documentation-refresh-for-enterprise-co",target:"_blank",rel:"noopener noreferrer"},So=o("April language refresh for 6.4"),Zo=o("."),Co=o("For PL/I, we caught up with the "),Oo={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/di-hu1/2023/03/09/march-2023-documentation-refresh",target:"_blank",rel:"noopener noreferrer"},Po=o("March language refresh for 6.1"),Ao=o("."),Lo=e("p",null,[o("We also added various new configuration options based on user feedback. For example, for each language to enable or disable the Problems view and syntax errors shown within the editor using "),e("code",null,"zopeneditor..disableProblems"),o(" while maintaining other language features. It will allow users to continue working in the program with some language features despite parsing issues. We also added user-defined variables to ZAPP files as well as various options to control how include files will be downloaded via Zowe from MVS for user to tweak performance and reliability.")],-1),Wo=e("h3",{id:"ibm-z-open-editor-v3-1-1-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-v3-1-1-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor v3.1.1 released")],-1),Do=e("p",null,[e("em",null,"March 30th, 2023")],-1),Ro=o("We released version 3.1.1 of Z Open Editor with fixes for some regressions found in v3.1.0. See the "),To=o("list of fixes here"),Ho=o("."),No=e("h3",{id:"ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v3-1-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v3-1-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v3.1.0 released")],-1),Vo=e("p",null,[e("em",null,"March 10th, 2023")],-1),Jo=e("p",null,"We released version 3.1.0 of Z Open Editor and RSE API Plug-in for Zowe CLI. The main focus of this release were language improvements and fixes as well as scalability and performance.",-1),Fo=o("For PL/I, we caught up with the "),jo={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/di-hu1/2022/10/27/october-2022-documentation-refresh-for-enterprise",target:"_blank",rel:"noopener noreferrer"},Uo=o("October language refresh for v6.1"),qo=o(". For COBOL, we worked through a long list of issues that you can see in the "),Go=o("detailed Changelog here"),Xo=o(". We also added one more set of options to our experimental COBOL source code formatter that allows you to specify how TO and INTO clauses should be formatted and aligned."),Yo=o("We also tackled various performance issues that users reported when editing very large programs. In particular, issues around using wildcard/glob pattern expressions in the ZAPP file, which could lead to a lot of local directories and files being searched. Through caching we were able to improve load times significantly. On a test system with slow I/O, by editing a program that includes 1000 copybooks located in a large repository with many sub-directories searched using wildcards (e.g. "),Ko=e("code",null,"**/COPYBOOK/**",-1),Qo=o("), we measured a performance gain from 8 minutes to 30 seconds for opening the program and loading the files. On a Mac with a fast SSD, it was just 4 seconds. We also added the same improvements that we made in "),$o=o("v3.0.1"),et=o(" for loading remote include files from MVS in parallel for COBOL to the PL/I language server as well, which leads to a significant performance improvement when opening files with many include files as well as opening several programs at the same time."),ot=e("p",null,"We also added file watchers to ZAPP property groups that monitor local files for changes. Now if you change, add, or delete a local included file in any of our languages that are used by programs opened in the editor, the programs will be updated with the changes immediately on Mac while you type or after you save on Windows.",-1),tt=o("In addition to these changes, you can find in our "),nt=o("Changelog"),st=o(" many more fixes and refinements for user build, ZAPP, COBOL code formatter, Zowe Explorer's JES view with RSE API, and more."),it=o("Finally, you are now able to use Z Open Editor in Microsoft's GitHub Codespaces and GitPod with all our capabilities. You can even use it with limited capabilities as a web extension when using Visual Studio Code in a browser, such as vscode.dev or github.dev. We documented how you can try all these browser-based and cloud-based options for free on our "),rt=o("Getting started page"),at=o("."),dt=e("h3",{id:"ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v3-0-1-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-ibm-rse-api-plug-in-for-zowe-cli-v3-0-1-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI v3.0.1 released")],-1),lt=e("p",null,[e("em",null,"January 18th, 2023")],-1),ht=o("Version 3.0.1 is now available fixing several user-reported bugs. See the detailed list "),ct=o("here"),pt=o("."),ut=e("h3",{id:"ibm-z-open-editor-v3-0-0-ibm-rse-api-plug-in-for-zowe-cli-v3-0-0-and-wazi-for-dev-spaces-v2-3-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-v3-0-0-ibm-rse-api-plug-in-for-zowe-cli-v3-0-0-and-wazi-for-dev-spaces-v2-3-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor v3.0.0, IBM RSE API Plug-in for Zowe CLI v3.0.0, and Wazi for Dev Spaces v2.3.0 released")],-1),_t=e("p",null,[e("em",null,"November 22nd, 2022")],-1),mt=e("p",null,"IBM Z Open Editor v3.0.0 is a major new release that provides many improvements for end users as well as many optimizations to make it run even better in the cloud on all supported platforms (s390x, x86).",-1),ft=o("Together with Zowe Explorer 2.4 we improved and simplified the setup of team configuration files in Wazi for Dev Spaces and made a lot of robustness improvements. We also updated user build with IBM Dependency-Based Build adding more features for multi-root workspaces, scoping your builds and filtering the files to upload and download. We removed redundancies between user settings and ZAPP in favor of ZAPP files and simplified the data model for property groups that require a "),wt=o("simple migration"),gt=o("."),bt=o("We completely refactored our language parsers and reduced the overall size of the extension by another 25% to now just 37.4MB (remember the times when we were way over a 100MB?), improving load times in Red Hat CodeReady Workspaces and Wazi for Dev Spaces even further. The language servers are up-to-date using on the parsers from IBM Developer for z/OS version 16 that are compiled with Java 11 requiring users to upgrade in this release to a Java 11 or newer runtime. With this update comes also a large number of language fixes and improvements for IBM's latest enterprise language versions and particular CICS 6.1. See our "),vt=o("release notes"),It=o(" for the complete list of fixes."),zt=e("h3",{id:"ibm-z-open-editor-ibm-rse-api-plug-in-for-zowe-cli-and-wazi-for-dev-spaces-v2-2-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-ibm-rse-api-plug-in-for-zowe-cli-and-wazi-for-dev-spaces-v2-2-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi for Dev Spaces v2.2.0 released")],-1),yt=e("p",null,[e("em",null,"September 20th, 2022")],-1),Bt={href:"https://www.ibm.com/products/z-and-cloud-modernization-stack",target:"_blank",rel:"noopener noreferrer"},Mt=o("IBM Z and Cloud Modernization Stack v2022.3.1"),kt=o(" is released today and with it updated versions 2.2.0 of IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi for Dev Spaces v2.2.0. Check out the "),Et=e("a",{href:"./new-releases"},"Changelog for Z Open Editor and RSE API CLI",-1),xt=o(" with the details."),St=a('
       IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI v2.1.1 released
      August 4th, 2022
      Version 2.1.1 is now available. This release fixed several IBM User Build issues which include adding support for COBOL nested copybooks, enabled user to enter Zowe CLI profile credentials in a popup dialog inside VS Code, fixed handling of file paths with spaces, and fixed various issues running User Build in multi-root workspaces. Check out the full Changelog here.
       IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi for Dev Spaces v2.1.0 released
      June 14th, 2022
      Version 2.1.0 is now available, which adds support for COBOL v6.4, PL/I v6.1, CICS v6.1, and HLASM for IBM z16 and z/OS 2.5. We also fixed many bugs, improved our support for Zowe 2, and implemented various community enhancement requests. See the detailed list here.
      ',6),Zt=o("This release also adds an "),Ct=e("a",{href:"../Docs/zcodeformatting"},"experimental COBOL code formatter",-1),Ot=o(" that is consistent to formatting in IBM Developer for z/OS. We are very interested in "),Pt={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},At=o("feedback and ideas for improvements"),Lt=o("."),Wt=a('
       Zowe 2 support added with version 2.0.2
      April 25th, 2022
      IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI version 2.0.2 are now available. This release adds now full support for Zowe 2.0 in particular Zowe Explorer 2, Zowe CLI 7, Zowe API Mediation Layer 2. You can continue using your Zowe CLI 6.x profiles for backwards compatibility, but you must update Zowe Explorer to version 2 to do so. Review our Getting Started with Zowe 2.0 section in the Documentation for details and instructions for how to migrate your 6.x profiles to the new 7.x format.
       IBM Z Open Editor 2.0.0 released
      March 15th, 2022
      ',5),Dt=o("IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI version 2.0.0 are now available. They have been released as a major version update to celebrate their availability in IBM Wazi Developer for Workspaces 2.0.0, which is now part of the new "),Rt={href:"https://www.ibm.com/products/z-and-cloud-modernization-stack",target:"_blank",rel:"noopener noreferrer"},Tt=o("IBM Z and Cloud Modernization Stack"),Ht=o(" offering. Together with the recently announced "),Nt={href:"https://www.ibm.com/cloud/wazi-as-a-service",target:"_blank",rel:"noopener noreferrer"},Vt=o("IBM Wazi as a Service"),Jt=o(" initiative, you can see how IBM Wazi is enabling the developer experience for Z to be more increasingly run from the Cloud - accelerating how organizations can provide flexible and modern development environments to their developers."),Ft=e("p",null,"A key enhancement of the Z and Cloud Modernization Stack offering is that Z Open Editor now fully supports OpenShift on Linux on Z when running as part of IBM Wazi. This allows you to now access your entire development environment with a browser-based VS Code-like experience all on Z.",-1),jt=o("In addition to supporting the s390x platform, this release focused on quality updates addressing defects, performance improvements, feedback, and enhancement requests submitted by the "),Ut={href:"https://github.com/IBM/zopeneditor-about/issues?q=is%3Aissue+is%3Aclosed",target:"_blank",rel:"noopener noreferrer"},qt=o("Z Open Editor community on GitHub"),Gt=o(". See our "),Xt=o("Changelog here"),Yt=o(" for a full breakdown of all the issues addressed."),Kt=e("p",null,"Note, that because Zowe 2.0 was delayed to late April 2022, Z Open Editor 2.0.0 and the RSE API CLI Plug-in still have to be updated to support it. This version still requires Zowe version 1.x. We plan to release a fully Zowe 2.0 supported update of the editor and CLI plugin with the Zowe 2.0 release.",-1),Qt=e("h3",{id:"ibm-z-open-editor-1-4-1-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-1-4-1-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor 1.4.1 released")],-1),$t=e("p",null,[e("em",null,"November 19th, 2021")],-1),en=o("IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI 1.4.1 are now available. This release fixes several language support and User Build issues. Additionally, password prompts for invalid or empty credentials during remote copybook and include file resolving have been added to prevent accidental MVS user account lock-outs and allow the use of Zowe profiles without stored credentials. You can find a detailed view of the updates contained in this release in our "),on=o("Changelog"),tn=o("."),nn=e("h3",{id:"ibm-z-open-editor-1-4-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-1-4-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor 1.4.0 released")],-1),sn=e("p",null,[e("em",null,"October 29th, 2021")],-1),rn=o("IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI 1.4.0 are now available. A key focus area of this release was performance. We reduced the size of the VS Code extension to half, which users will see in reduced start-up times and memory footprint. Find the details of the many other fixes and enhancements "),an=o("here"),dn=o("."),ln=e("h3",{id:"ibm-z-open-editor-1-2-6-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-1-2-6-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor 1.2.6 released")],-1),hn=e("p",null,[e("em",null,"August 19th, 2021")],-1),cn=o("IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI 1.2.6 are now available. We fixed several defects and addressed minor enhancement requests from our community. Plus, we made sure everything still works with Zowe Explorer 1.18.0, which was going through API changes to prepare for its "),pn={href:"https://github.com/zowe/zowe-explorer-vscode/wiki/v2-Conformance-Criteria",target:"_blank",rel:"noopener noreferrer"},un=o("Conformance Criteria"),_n=o(" support. See the detailed "),mn=o("Changelog here"),fn=o("."),wn=o('There is also a new Blog post from Scott Davis called "'),gn={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/annalisa-cesa/2021/08/02/ibm-wazi-developer-shortened-to-wazi-developer-wha",target:"_blank",rel:"noopener noreferrer"},bn=o("Wazi Developer \u2013 what is behind this name?"),vn=o('" that offers a larger scope of the positioning of Z Open Editor in Wazi Developer.'),In=e("h3",{id:"ibm-z-open-editor-1-2-5-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-1-2-5-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor 1.2.5 released")],-1),zn=e("p",null,[e("em",null,"June 18th, 2021")],-1),yn=o("IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi Developer 1.2.5 are now available. In addition to various fixes and performance improvements detailed in our "),Bn=o("Changelog here"),Mn=o(", Wazi Developer for Workspaces is now based on Red Hat CodeReady Workspaces 2.8 and packages Zowe Explorer 1.15.1 as well as Zowe CLI 6.31."),kn=e("h3",{id:"ibm-z-open-editor-1-2-1-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-1-2-1-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor 1.2.1 released")],-1),En=e("p",null,[e("em",null,"April 21st, 2021")],-1),xn=o("We released fixes for IBM Z Open Editor and IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in) with version 1.2.1. For the editor, you will find various "),Sn=o("fixes and improvements"),Zn=o(" for REXX language support in 1.2.1. For the RSE CLI plug-in, we revised and cleaned up output, error and log messages, and implemented various enhancements for single sign-on with the Zowe API Mediation Layer (APIML). For an introduction to using our tools with the Zowe APIML, read "),Cn={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/joe-winchester1/2021/04/14/using-the-ibm-remote-system-explorer-apis-with-the",target:"_blank",rel:"noopener noreferrer"},On=o("this new blog post"),Pn=o(" by Joe Winchester, IBM's Zowe technical lead."),An=e("h3",{id:"ibm-z-open-editor-ibm-rse-api-plug-in-for-zowe-cli-and-wazi-developer-v1-2-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-ibm-rse-api-plug-in-for-zowe-cli-and-wazi-developer-v1-2-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor, IBM RSE API Plug-in for Zowe CLI, and Wazi Developer v1.2.0 released")],-1),Ln=e("p",null,[e("em",null,"March 19th, 2021")],-1),Wn=o("We released v1.2.0 of our tools today. See this "),Dn=e("a",{href:"whats-new-120"},"blog post",-1),Rn=o(" for an overview to the main things we added, as well as our Z Open Editor "),Tn={href:"https://marketplace.visualstudio.com/items/IBM.zopeneditor/changelog",target:"_blank",rel:"noopener noreferrer"},Hn=o("Changelog"),Nn=o(" for the list of fixes."),Vn=e("p",null,[o("There are also two new blog posts giving you an in-depth look at the "),e("a",{href:"announcing-rexx"},"all new REXX language support"),o(" we added in this release as well as all the "),e("a",{href:"rse-march-120"},"new enhancements for IBM RSE API Plug-in for Zowe CLI"),o(".")],-1),Jn=e("h3",{id:"ibm-db2-for-z-os-developer-extension-v1-1-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-db2-for-z-os-developer-extension-v1-1-0-released","aria-hidden":"true"},"#"),o(" IBM Db2 for z/OS Developer Extension v1.1.0 released")],-1),Fn=e("p",null,[e("em",null,"February 23rd, 2021")],-1),jn=o("The latest release of IBM Db2 for z/OS Developer Extension is now available on the "),Un={href:"https://marketplace.visualstudio.com/items?itemName=IBM.db2forzosdeveloperextension",target:"_blank",rel:"noopener noreferrer"},qn=o("Visual Studio Code marketplace"),Gn=o(". In this release, the extension delivers the following key features:"),Xn=e("ol",null,[e("li",null,"Full support on native SQL stored procedure (NSP). Developers can deploy the NSP with different options, debug the NSP (including nested NSP) and run the NSP."),e("li",null,"Run SQL from anywhere. Developers can highlight and run SQL DIRECTLY from other types of language source code files, like Cobol file, C file, Java file, JavaScript/Python files, and so on (you name it), so that they don\u2019t need to copy/paste the statement to another .sql file or twist the SQLs to validate the result."),e("li",null,"More commit/rollback setting for SQL execution.")],-1),Yn=o("You can read more about these new features "),Kn={href:"https://community.ibm.com/community/user/hybriddatamanagement/blogs/calene-janacek1/2021/02/23/announcing-ibm-db2-for-zos-developer-extension-11",target:"_blank",rel:"noopener noreferrer"},Qn=o("here"),$n=o("."),es=e("h3",{id:"ibm-z-open-editor-and-rse-cli-plug-in-release-1-1-2-and-new-blog-of-ibm-user-build",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-rse-cli-plug-in-release-1-1-2-and-new-blog-of-ibm-user-build","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and RSE CLI Plug-in release 1.1.2, and new blog of IBM User Build")],-1),os=e("p",null,[e("em",null,"December 9th, 2020")],-1),ts=o("We released v1.1.2 of Z Open Editor and the RSE CLI plug-in adding "),ns={href:"https://marketplace.visualstudio.com/items/IBM.zopeneditor/changelog",target:"_blank",rel:"noopener noreferrer"},ss=o("some exciting new features"),is=o(" for High Level Assembler developers working with macros and international customers working with special characters in EBCDIC."),rs=e("p",null,[o("We also added a new post to our team blog giving you an introduction and overview to Z Open Editor's User Build capability: "),e("a",{href:"userbuild-blog"},"IBM Z\xAE Open Editor makes building COBOL, PL/I, and HLASM applications easier with User Build"),o(".")],-1),as=e("h3",{id:"ibm-z-open-editor-and-rse-api-plug-in-for-zowe-cli-1-1-1-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-and-rse-api-plug-in-for-zowe-cli-1-1-1-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor and RSE API Plug-in for Zowe CLI 1.1.1 released")],-1),ds=e("p",null,[e("em",null,"November 6th, 2020")],-1),ls=o("We released v1.1.1 of Z Open Editor and the RSE API Plug-in to catch up with the latest v1.10.1 release of Zowe Explorer fully supporting now "),hs={href:"https://docs.zowe.org/stable/user-guide/cli-usingcli.html#base-profiles",target:"_blank",rel:"noopener noreferrer"},cs=o("Zowe CLI Base Profiles"),ps=o(" with "),us={href:"https://ibm.github.io/zopeneditor-about/Blog/rse-october-110.html#use-json-web-tokens-jwt-for-authentication-with-the-host",target:"_blank",rel:"noopener noreferrer"},_s=o("RSE API JWT tokens"),ms=o(" as well. Plus, we fixed "),fs={href:"https://marketplace.visualstudio.com/items/IBM.zopeneditor/changelog",target:"_blank",rel:"noopener noreferrer"},ws=o("a couple of bugs"),gs=o(" reported by "),bs={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},vs=o("our community"),Is=o("."),zs=o("To get the full package go to our download site here: "),ys={href:"https://ibm.github.io/mainframe-downloads/downloads.html#wazi",target:"_blank",rel:"noopener noreferrer"},Bs=o("https://ibm.github.io/mainframe-downloads/downloads.html#wazi"),Ms=e("p",null,[o("In the coming weeks we will also be publishing more media content around Wazi Developer. We start today with a new blog post about "),e("a",{href:"./ocp-ssl-cert"},"configuring Wazi Developer for Workspaces in OpenShift with certificates"),o(".")],-1),ks=e("h3",{id:"ibm-wazi-developer-for-red-hat-codeready-workspaces-1-1-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-wazi-developer-for-red-hat-codeready-workspaces-1-1-released","aria-hidden":"true"},"#"),o(" IBM Wazi Developer for Red Hat CodeReady Workspaces 1.1 released")],-1),Es=e("p",null,[e("em",null,"October 30th, 2020")],-1),xs=o("IBM Z Open Editor is part of the overall "),Ss={href:"https://www.ibm.com/docs/en/wdfrhcw/1.4.0?topic=whats-new",target:"_blank",rel:"noopener noreferrer"},Zs=o("IBM Wazi Developer for Red Hat CodeReady Workspaces 1.1"),Cs=o(" offering now, which was released today. Wazi Developer is a packaging of various developer components for VS Code as well as Eclipse. If you are a Z Open Editor user you might particularly interested in the Z Debug extension for VS Code and the updated RSE API Zowe CLI Plug-in v1.1.0. We have a "),Os=e("a",{href:"rse-october-110"},"detailed Blog post here",-1),Ps=o(" with all the new features we added to the RSE API CLI Plug-in."),As=e("p",null,[o("Wazi Developer also contains solution components for "),e("a",{href:"./ibm-wazi-development-client-introduction-blog"},"developing from the Hybrid Cloud"),o(" utilizing Red Hat CodeReady Workspaces 2.3 on OpenShift 4.3 with our Z Open Editor and Debug. Plus, the Wazi Sandbox component that provides a fully virtualized z/OS environment, which enables development and testing of z/OS applications on Red Hat OpenShift running on x86 hardware.")],-1),Ls=o("Go here for an overview with videos and blog post: "),Ws={href:"https://www.ibm.com/products/wazi-developer",target:"_blank",rel:"noopener noreferrer"},Ds=o("https://www.ibm.com/products/wazi-developer"),Rs=o("The downloads of the client tools as well as links to the Cloud solution installation instructions are available on our new "),Ts={href:"https://ibm.github.io/mainframe-downloads/downloads.html#wazi",target:"_blank",rel:"noopener noreferrer"},Hs=o("Mainframe Downloads site"),Ns=o("."),Vs=e("p",null,[o("Also check the "),e("a",{href:"(https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/5/899/ENUSLP20-0515/index.html&request_locale=en)"},"original announcement"),o(" with more details for what is exactly included in this offering.")],-1),Js=e("h3",{id:"ibm-db2-for-z-os-developer-extension-0-5-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-db2-for-z-os-developer-extension-0-5-0-released","aria-hidden":"true"},"#"),o(" IBM Db2 for z/OS Developer Extension 0.5.0 released")],-1),Fs=e("p",null,[e("em",null,"October 27th, 2020")],-1),js=o("The latest release of IBM Db2 for z/OS Developer Extension is now available on the "),Us={href:"https://marketplace.visualstudio.com/items?itemName=IBM.db2forzosdeveloperextension",target:"_blank",rel:"noopener noreferrer"},qs=o("Visual Studio Code Marketplace"),Gs=o("."),Xs=e("p",null,"Db2 Developer Extension 0.5.0 continues to simplify and modernize the experience of developing SQL applications for Db2 for z/OS by providing the ability to create Db2 connections, SQL execution support, syntax checking, code completion, and signature help.",-1),Ys=o("You can read more about these new features "),Ks={href:"https://community.ibm.com/community/user/hybriddatamanagement/blogs/eric-radzinski1/2020/10/27/announcing-ibm-db2-for-zos-developer-extension-050?CommunityKey=621c2a2a-01f9-4b5",target:"_blank",rel:"noopener noreferrer"},Qs=o("here"),$s=o("."),ei=e("h3",{id:"z-open-editor-1-1-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#z-open-editor-1-1-0-released","aria-hidden":"true"},"#"),o(" Z Open Editor 1.1.0 released")],-1),oi=e("p",null,[e("em",null,"October 23rd, 2020")],-1),ti=o("IBM Z Open Editor 1.1.0 was released to the "),ni={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},si=o("VS Code Marketplace"),ii=o(". This release fully integrates the IBM User Build extension and expands its capabilities to support building PL/I and HLASM applications as well. We are also adding new features to property groups such as language-specific scoping with compiler options that configure the editor, as well as a complete new representation of property groups called "),ri=e("a",{href:"../Docs/zapp"},"ZAPP files",-1),ai=o(". We also finally added full support for the "),di={href:"https://docs.zowe.org/stable/user-guide/cli-scsplugin.html",target:"_blank",rel:"noopener noreferrer"},li=o("Zowe Secure Credentials Store Plug-in"),hi=o(" for all Z Open Editor functions such as remote include file resolution or user build."),ci=o("See the complete list of changes "),pi={href:"https://marketplace.visualstudio.com/items/IBM.zopeneditor/changelog",target:"_blank",rel:"noopener noreferrer"},ui=o("here"),_i=o("."),mi=e("h3",{id:"z-open-editor-1-0-3-released-and-new-eclipse-che-trial",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#z-open-editor-1-0-3-released-and-new-eclipse-che-trial","aria-hidden":"true"},"#"),o(" Z Open Editor 1.0.3 released and new Eclipse Che trial")],-1),fi=e("p",null,[e("em",null,"August 7th, 2020")],-1),wi=o("IBM Z Open Editor 1.0.3 was released to the "),gi={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},bi=o("VS Code Marketplace"),vi=o(" fixing various defects, adding branch labels to the "),Ii=o("HLASM Outline view"),zi=o(", as well as introducing "),yi=o("custom include file extensions"),Bi=o("."),Mi=o("We also updated our Eclipse Che trial described in "),ki=o("this blog post"),Ei=o(". Now you can use the free Red Hat trial accounts at "),xi={href:"https://che.openshift.io",target:"_blank",rel:"noopener noreferrer"},Si=o("https://che.openshift.io"),Zi=o(" to run Eclipse Che. With just a few mouse-clicks you can now deploy Z Open Editor there. It is really simple (paste a URL, Go) as it loads everything from the Cloud. See the instructions and our Che Devfile here: "),Ci={href:"https://github.com/IBM/zopeneditor-about/tree/main/che",target:"_blank",rel:"noopener noreferrer"},Oi=o("https://github.com/IBM/zopeneditor-about/tree/main/che"),Pi=e("h3",{id:"new-ibm-vs-code-extension-for-db2-sql-available-now",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#new-ibm-vs-code-extension-for-db2-sql-available-now","aria-hidden":"true"},"#"),o(" New IBM VS Code extension for Db2 SQL available now")],-1),Ai=e("p",null,[e("em",null,"July 30th, 2020")],-1),Li=o("The first release of IBM Db2 for z/OS Developer Extension is now available on the "),Wi={href:"https://marketplace.visualstudio.com/items?itemName=ibm.db2forzosdeveloperextension",target:"_blank",rel:"noopener noreferrer"},Di=o("Visual Studio Code Marketplace"),Ri=o(". Db2 Developer Extension brings SQL language support to VS Code and to Eclipse Theia."),Ti=o("You can read more about this new extension "),Hi={href:"https://developer.ibm.com/mainframe/2020/07/29/announcing-ibm-db2-for-z-os-developer-extension-for-microsoft-visual-studio-code/",target:"_blank",rel:"noopener noreferrer"},Ni=o("here"),Vi=o("."),Ji=e("h3",{id:"vs-code-marketplace-update",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#vs-code-marketplace-update","aria-hidden":"true"},"#"),o(" VS Code Marketplace update")],-1),Fi=e("p",null,[e("em",null,"June 30th, 2020")],-1),ji=o("IBM Z Open Editor 1.0.2 was released to the "),Ui={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},qi=o("VS Code Marketplace"),Gi=o(" adding "),Xi=o("High Level Assembler"),Yi=o(" support now to that version as well."),Ki=e("h3",{id:"ibm-wazi-in-the-news",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-wazi-in-the-news","aria-hidden":"true"},"#"),o(" IBM Wazi in the News")],-1),Qi=e("p",null,[e("em",null,"June 24th, 2020")],-1),$i=e("p",null,"We released a small bug fix update for IBM Z Open Editor v0.5.2/1.0.1 today that addresses an issue with running our language servers with a Java newer than version 8. Now it works again with Java SDKs released since then, such as LTS 11, 14 etc.",-1),er=e("p",null,"Since the release of IBM Wazi for Red Hat\xAE CodeReady Workspaces the overall solution and its components have been mentioned and featured throughout the Web in various publications:",-1),or=o('Patrick Moorhead, "'),tr={href:"https://www.forbes.com/sites/moorinsights/2020/06/22/ibm-wazi-seeks-to-empowers-even-more-developers-on-ibm-z-mainframes/#2589f82d1895",target:"_blank",rel:"noopener noreferrer"},nr=o("IBM Wazi Seeks To Empowers Even More Developers On IBM Z Mainframes"),sr=o('", Forbes Magazine.'),ir=o('Willie Tejada, "'),rr={href:"https://developer.ibm.com/components/ibmz/blogs/willie-tejada-ibm-wazi-announcement/",target:"_blank",rel:"noopener noreferrer"},ar=o("Accelerate cloud-native development with IBM Wazi for Red Hat CodeReady Workspaces"),dr=o(", IBM Developer."),lr=o('Ed Scannell, "'),hr={href:"https://searchdatacenter.techtarget.com/news/252484620/Tool-helps-mainframe-developers-create-cloud-native-apps",target:"_blank",rel:"noopener noreferrer"},cr=o("Tool helps mainframe developers create cloud-native apps"),pr=o('", TechTarget Network at SearchDataCenter.com.'),ur=o('"'),_r={href:"https://www.dbta.com/Editorial/News-Flashes/IBM-Wazi-for-Red-Hat-Code-Ready-Workspaces-Enables-Cloud-Native-Development-on-Z-141420.aspx",target:"_blank",rel:"noopener noreferrer"},mr=o("IBM Wazi for Red Hat Code-Ready Workspaces Enables Cloud-Native Development on Z"),fr=o('", Database Trends and Applications.'),wr=o('Alan Radding, "'),gr={href:"https://dancingdinosaur.wordpress.com/2020/06/12/ibm-wazi-cloud-native-devops-for-z/",target:"_blank",rel:"noopener noreferrer"},br=o("IBM Wazi cloud-native devops for Z"),vr=o('", DancingDinosaur, June 12th.'),Ir=o('Danny Mace, "'),zr={href:"https://www.ibm.com/cloud/blog/announcements/ibm-wazi-for-red-hat-codeready-workspaces",target:"_blank",rel:"noopener noreferrer"},yr=o("Making Cloud Native Development a Reality for IBM Z"),Br=o('", IBM Cloud.'),Mr=o('Barry Baker, "'),kr={href:"https://www.ibm.com/blogs/systems/gain-business-agility-with-new-cloud-enabling-solutions-on-ibm-z/",target:"_blank",rel:"noopener noreferrer"},Er=o("Enhance business agility with new cloud-enabling solutions on IBM Z"),xr=o(", IBM IT Infrastructure."),Sr=o('Sanjay Chandru, "'),Zr={href:"https://developer.ibm.com/mainframe/2020/05/05/cloud-native-development-on-z-is-real-with-ibm-wazi-for-red-hat-codeready-workspaces/",target:"_blank",rel:"noopener noreferrer"},Cr=o("Cloud native development on Z is real with IBM Wazi for Red Hat CodeReady Workspaces!"),Or=o('",'),Pr=o('Minaz Merali, "'),Ar={href:"https://mediacenter.ibm.com/media/t/1_dl6sbihe",target:"_blank",rel:"noopener noreferrer"},Lr=o('Introducing IBM Wazi for Red Hat CodeReady Workspaces"'),Wr=o('", IBM Media Center'),Dr=o('Z DevOps Talks, "'),Rr={href:"https://developer.ibm.com/mainframe/2020/06/19/z-devops-talks-s1-e13-peter-haumer-talks-wazi-workspaces-bring-your-own-ide-and-much-more/",target:"_blank",rel:"noopener noreferrer"},Tr=o("S1 E13: Peter Haumer talks Wazi Workspaces, Bring Your Own IDE, and Much More"),Hr=o('", IBM Mainframe DEV.'),Nr=o('Bill Alexander, "'),Vr={href:"https://developer.ibm.com/mainframe/2020/06/12/whats-new-in-ibm-developer-for-z-os-v14-2-3/",target:"_blank",rel:"noopener noreferrer"},Jr=o("What\u2019s new in IBM Developer for z/OS V14.2.3"),Fr=o('", IBM Mainframe DEV.'),jr=o('Dave McKnight, "'),Ur={href:"https://developer.ibm.com/mainframe/2020/06/12/introducing-ibm-remote-system-explorer-api/",target:"_blank",rel:"noopener noreferrer"},qr=o("Introducing IBM Remote System Explorer API"),Gr=o('", IBM Mainframe DEV.'),Xr=o('Rosalind Radcliffe, "'),Yr={href:"https://developer.ibm.com/conferences/digital-developer-conference-security-na/devsecops-na/",target:"_blank",rel:"noopener noreferrer"},Kr=o("Keynote - DevSecOps for Cloud Native development on IBM Z"),Qr=o(", DevSecOps Conference, Day 1, 2:00."),$r=o('Peter Haumer, "'),ea={href:"https://developer.ibm.com/conferences/digital-developer-conference-security-na/devsecops-na/",target:"_blank",rel:"noopener noreferrer"},oa=o("IBM Z development on IBM Wazi for Red Hat CodeReady Workspaces"),ta=o(", DevSecOps Conference, Day 1, 2:35."),na=o('Prasang A Prajapati, "'),sa={href:"https://ibm.github.io/zopeneditor-about/Blog/ibm-wazi-development-client-introduction-blog.html",target:"_blank",rel:"noopener noreferrer"},ia=o("Kubernetes-Native Integrated Z Developer Environment with IBM Wazi for Red Hat CodeReady Workspaces Development Client"),ra=o('", Z Open Editor About.'),aa=o('Peter Haumer, "'),da={href:"https://www.youtube.com/watch?v=9-3oZXmYiNU",target:"_blank",rel:"noopener noreferrer"},la=o("IBM Wazi for Red Hat CodeReady Workspaces Demo"),ha=o('", YouTube.'),ca=o('Daniel Beall, "'),pa={href:"https://ibm.github.io/zopeneditor-about/Blog/hlasm-blog.html",target:"_blank",rel:"noopener noreferrer"},ua=o("IBM Z Open Editor: A modern IDE for IBM High Level Assembler"),_a=o('", Z Open Editor About.'),ma=e("p",null,"(List updated on 6/28.)",-1),fa=o("Finally, our IBM RSE API Plug-in for Zowe CLI v.1.0.0 has been approved as fully Zowe CLI conformant and is now featured in the Open Mainframe Project's "),wa={href:"https://www.openmainframeproject.org/projects/zowe/conformance",target:"_blank",rel:"noopener noreferrer"},ga=o("Conformance Gallery"),ba=o("."),va=e("h3",{id:"ibm-wazi-for-red-hat\xAE-codeready-workspaces-available-now",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-wazi-for-red-hat\xAE-codeready-workspaces-available-now","aria-hidden":"true"},"#"),o(" IBM Wazi for Red Hat\xAE CodeReady Workspaces available now")],-1),Ia=e("p",null,[e("em",null,"June 19th, 2020")],-1),za=o("You can now try out IBM Wazi for Red Hat CodeReady Workspaces Development Client (IBM Wazi Development Client) for a productive in-cloud development experience. The technical preview for IBM Wazi Development Client can be found at the "),ya={href:"https://ibm.github.io/mainframe-downloads/downloads.html/#wazi",target:"_blank",rel:"noopener noreferrer"},Ba=o("Mainframe DEV Center's Downloads page"),Ma=o("."),ka=o("Read our new blog post "),Ea=o("Kubernetes-Native Integrated Z Developer Environment with IBM Wazi for Red Hat\xAE CodeReady Workspaces Development Client"),xa=o(" for an overview to learn more about the features and components of IBM Wazi Development Client."),Sa=e("h3",{id:"ibm-z-open-editor-0-5-0-and-1-0-0-released",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-0-5-0-and-1-0-0-released","aria-hidden":"true"},"#"),o(" IBM Z Open Editor 0.5.0 and 1.0.0 released")],-1),Za=e("p",null,[e("em",null,"June 12th, 2020")],-1),Ca=o("IBM Z Open Editor v0.5.0 is released to the VS Code Marketplace. See "),Oa=o("here"),Pa=o(" for all the enhancements and fixes."),Aa=o("IBM Z Open Editor v1.0.0 adds a new IBM High Level Assembler language server. Unfortunately, by adding this capability our VS Code extension exceeds the maximum code size allowed for VS Code extensions on the Microsoft VS Code Marketplace. Until we reduce the file size you can get the v1.0.0 release only as a "),La={href:"https://ibm.github.io/mainframe-downloads/downloads.html/",target:"_blank",rel:"noopener noreferrer"},Wa=o("free download from IBM"),Da=o("."),Ra=o("IBM Z Open Editor v1.0.0 is also part of "),Ta={href:"https://ibm.github.io/mainframe-downloads/downloads.html/",target:"_blank",rel:"noopener noreferrer"},Ha=o("IBM Developer for z/OS Enterprise Edition"),Na=o(". Customers who purchase this edition will then be able to receive technical support for Z Open Editor."),Va=e("p",null,"To learn more about the new High Level Assembler language server see our Blog post:",-1),Ja=o("IBM Z Open Editor: A modern IDE for IBM High Level Assembler"),Fa=e("h3",{id:"ibm-wazi-for-red-hat-codeready-workspaces-announcement",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-wazi-for-red-hat-codeready-workspaces-announcement","aria-hidden":"true"},"#"),o(" IBM Wazi for Red Hat CodeReady Workspaces announcement")],-1),ja=e("p",null,[e("em",null,"May 5th, 2020")],-1),Ua=e("p",null,"We announced today IBM Wazi for Red Hat CodeReady Workspaces in which the Z Open Editor will play a critical part. See the following resources:",-1),qa={href:"https://www.ibm.com/products/wazi-for-red-hat-codeready-workspaces",target:"_blank",rel:"noopener noreferrer"},Ga=o("Main Products page"),Xa={href:"https://www.ibm.com/downloads/cas/KLNRXG6N",target:"_blank",rel:"noopener noreferrer"},Ya=o("Solution Brief"),Ka={href:"https://mediacenter.ibm.com/media/t/1_3q7ce3ba",target:"_blank",rel:"noopener noreferrer"},Qa=o("Overview Video"),$a={href:"https://mediacenter.ibm.com/media/t/1_iy379suo",target:"_blank",rel:"noopener noreferrer"},ed=o("IBM Think presentation"),od={href:"https://mediacenter.ibm.com/media/t/1_8roweeco",target:"_blank",rel:"noopener noreferrer"},td=o("Intro to Cloud Native Development for Z video"),nd=e("h3",{id:"new-z-open-editor-release-and-public-beta-of-ibm-rse-api",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#new-z-open-editor-release-and-public-beta-of-ibm-rse-api","aria-hidden":"true"},"#"),o(" New Z Open Editor release and public beta of IBM RSE API")],-1),sd=e("p",null,[e("em",null,"March 26th, 2020")],-1),id=o("We released "),rd={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},ad=o("IBM Z Open Editor v0.4.7"),dd=o(" with Beta support for "),ld={href:"https://epwt-www.mybluemix.net/software/support/trial/cst/welcomepage.wss?siteId=536&tabId=1045&w=1&_ga=2.68641937.1484814543.1584987187-1152815028.1571427049",target:"_blank",rel:"noopener noreferrer"},hd=o("IBM Remote System Explorer API and the new IBM RSE API Plug-in for Zowe CLI"),cd=o("."),pd=o("See our new Blog post "),ud=o("Interacting with z/OS using IBM RSE API Plug-in for Zowe CLI"),_d=o(" for an overview as well as links to demo videos."),md=e("h3",{id:"new-article-about-zowe-and-z-open-editor",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#new-article-about-zowe-and-z-open-editor","aria-hidden":"true"},"#"),o(" New article about Zowe and Z Open Editor")],-1),fd=e("p",null,[e("em",null,"March 16th, 2020")],-1),wd=o("We added a link to "),gd={href:"https://medium.com/@williampereira_80651/zowe-and-vscode-we-love-it-b5b4b8fdc1c1",target:"_blank",rel:"noopener noreferrer"},bd=o("a new article"),vd=o(" with videos about using Z Open Editor with Zowe Explorer and other VS Code extensions to our "),Id=o("External Blog Posts and Articles"),zd=o(" page."),yd=o("Made various copyedits and refinements to our "),Bd=o("Online Help"),Md=o(" pages."),kd=e("h3",{id:"updated-code-snippet-library-in-ibm-z\xAE-open-editor-v0-4-3",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#updated-code-snippet-library-in-ibm-z\xAE-open-editor-v0-4-3","aria-hidden":"true"},"#"),o(" Updated Code Snippet library in IBM Z\xAE Open Editor v0.4.3")],-1),Ed=e("p",null,[e("em",null,"December 23rd, 2019")],-1),xd=o("We released v0.4.3 to "),Sd={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},Zd=o("the marketplace"),Cd=o(" with an all new set of code snippets. To read more about it see our latest blog post:"),Od=o("Improve your z/OS Enterprise developer productivity with IBM Z Open Editor\u2018s code snippets library"),Pd=e("h3",{id:"updated-che-devfile-to-use-ibm-z\xAE-open-editor-v0-4-3-and-zowe-explorer-1-0-1",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#updated-che-devfile-to-use-ibm-z\xAE-open-editor-v0-4-3-and-zowe-explorer-1-0-1","aria-hidden":"true"},"#"),o(" Updated Che devfile to use IBM Z\xAE Open Editor v0.4.3 and Zowe Explorer 1.0.1")],-1),Ad=e("p",null,[e("em",null,"December 23rd, 2019")],-1),Ld=o("If you follow the instructions in our "),Wd=o("Using IBM Z\xAE Open Editor in Eclipse Che"),Dd=o(" blog post for creating a new Che Workpspace using our "),Rd={href:"https://raw.githubusercontent.com/IBM/zopeneditor-about/main/che/ibm-z-devfile.yaml",target:"_blank",rel:"noopener noreferrer"},Td=o("devfile"),Hd=o(", you now get the latest releases of the editor (v0.4.3) the Zowe Explorer (v1.0.1)."),Nd=e("h3",{id:"devops-com-article-featuring-ibm-z\xAE-open-editor-s-lsp-capabilities",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#devops-com-article-featuring-ibm-z\xAE-open-editor-s-lsp-capabilities","aria-hidden":"true"},"#"),o(" DevOps.com article featuring IBM Z\xAE Open Editor's LSP capabilities")],-1),Vd=e("p",null,[e("em",null,"December 18th, 2019")],-1),Jd=o("Bob Reselman published "),Fd={href:"https://devops.com/ibm-z-open-editor-support-for-language-server-protocol-is-a-game-changer/",target:"_blank",rel:"noopener noreferrer"},jd=o("a great article about the Language Server Protocol"),Ud=o(" and uses Z Open Editor as an example."),qd=e("h3",{id:"using-ibm-z\xAE-open-editor-on-the-web",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-ibm-z\xAE-open-editor-on-the-web","aria-hidden":"true"},"#"),o(" Using IBM Z\xAE Open Editor on the Web")],-1),Gd=e("p",null,[e("em",null,"December 4th, 2019")],-1),Xd=e("p",null,"We added two new articles describing how you can use the IBM Z Open Editor VS Code extension outside of VS Code on Web running in a browser. We show you how to do it with two very popular frameworks:",-1),Yd=o("Using Eclipse Che"),Kd=o("Using Eclipse Theia"),Qd=e("h3",{id:"z-devops-talks-podcast",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#z-devops-talks-podcast","aria-hidden":"true"},"#"),o(" Z DevOps Talks podcast")],-1),$d=e("p",null,[e("em",null,"December 3rd, 2019")],-1),el={href:"https://developer.ibm.com/mainframe/2019/12/03/ibm-z-devops-talks-with-rosalind-radcliffe/",target:"_blank",rel:"noopener noreferrer"},ol=o("Rosalind Radcliffe talks"),tl=o(" about our editor, bring-your-own-IDE, DevOps, and future trends."),nl=e("h3",{id:"ibm-systems-magazine-article",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-systems-magazine-article","aria-hidden":"true"},"#"),o(" IBM Systems Magazine Article")],-1),sl=e("p",null,[e("em",null,"September 26th, 2019")],-1),il=o("Sanjay Chandru published an "),rl={href:"https://ibmsystemsmag.com/IBM-Z/9/2019/ibm-z-open-editor",target:"_blank",rel:"noopener noreferrer"},al=o("article about IBM Z Open Editor"),dl=o(" and how it fits in perfectly with DevOps for IBM Z."),ll=e("h3",{id:"ibm-z\xAE-open-editor-release-announcement",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z\xAE-open-editor-release-announcement","aria-hidden":"true"},"#"),o(" IBM Z\xAE Open Editor Release Announcement")],-1),hl=e("p",null,[e("em",null,"September 19th, 2019")],-1),cl=o("Read the "),pl={href:"https://developer.ibm.com/mainframe/2019/09/19/ibm-z-open-editor-brings-cobol-and-pl-i-language-support-to-microsoft-visual-studio-code/",target:"_blank",rel:"noopener noreferrer"},ul=o("official announcement"),_l=o(" for the IBM Z Open Editor's first release.");function ml(fl,wl){const s=r("RouterLink"),n=r("ExternalLinkIcon");return d(),l(h,null,[u,_,m,f,e("p",null,[w,t(s,{to:"/Docs/advanced_overview.html"},{default:i(()=>[g]),_:1}),b]),e("ul",null,[v,I,e("li",null,[z,t(s,{to:"/Docs/editor_codechanges_hlasm.html#code-completion"},{default:i(()=>[y]),_:1}),B])]),M,e("p",null,[k,t(s,{to:"/Blog/new-releases.html#_4-4-0-2024-08-12"},{default:i(()=>[E]),_:1}),x]),S,Z,e("p",null,[C,t(s,{to:"/Blog/announcing-jcl.html"},{default:i(()=>[O]),_:1}),P]),e("p",null,[A,e("a",L,[W,t(n)]),D]),e("p",null,[R,t(s,{to:"/Blog/new-releases.html#_4-3-0-2024-06-18"},{default:i(()=>[T]),_:1}),H]),N,V,J,F,e("p",null,[j,t(s,{to:"/Blog/new-releases.html#_4-2-0-2024-05-16"},{default:i(()=>[U]),_:1}),q]),G,X,Y,K,Q,e("p",null,[$,e("a",ee,[oe,t(n)]),te,e("a",ne,[se,t(n)]),ie]),re,ae,e("p",null,[de,e("a",le,[he,t(n)]),ce]),pe,ue,_e,e("p",null,[me,t(s,{to:"/Docs/advanced_overview.html"},{default:i(()=>[fe]),_:1}),we]),ge,e("p",null,[be,t(s,{to:"/Blog/new-releases.html#_4-0-0-2024-03-15"},{default:i(()=>[ve]),_:1}),Ie]),e("p",null,[ze,e("a",ye,[Be,t(n)]),Me]),ke,Ee,xe,e("p",null,[Se,e("a",Ze,[Ce,t(n)]),Oe,t(s,{to:"/Blog/new-releases.html#_3-4-0-2024-02-29"},{default:i(()=>[Pe]),_:1}),Ae]),Le,We,e("p",null,[De,t(s,{to:"/Blog/new-releases.html#333---20231215"},{default:i(()=>[Re]),_:1}),Te]),He,Ne,e("p",null,[Ve,t(s,{to:"/Blog/new-releases.html#330---20231025"},{default:i(()=>[Je]),_:1}),Fe]),e("p",null,[je,e("a",Ue,[qe,t(n)]),Ge]),Xe,Ye,e("p",null,[Ke,t(s,{to:"/Blog/new-releases.html#_3-2-2-2023-09-15"},{default:i(()=>[Qe]),_:1}),$e]),eo,oo,e("p",null,[to,t(s,{to:"/Blog/new-releases.html#_3-2-1-2023-07-19"},{default:i(()=>[no]),_:1}),so]),io,ro,e("p",null,[ao,e("a",lo,[ho,t(n)]),co]),e("p",null,[po,e("a",uo,[_o,t(n)]),mo,e("a",fo,[wo,t(n)]),go,t(s,{to:"/Docs/getting_started.html#using-ibm-z-open-editor-in-cloud-based-editors"},{default:i(()=>[bo]),_:1}),vo]),e("p",null,[Io,t(s,{to:"/Blog/new-releases.html#_3-2-0-2023-06-16"},{default:i(()=>[zo]),_:1}),yo,e("a",Bo,[Mo,t(n)]),ko]),e("ul",null,[e("li",null,[Eo,e("a",xo,[So,t(n)]),Zo]),e("li",null,[Co,e("a",Oo,[Po,t(n)]),Ao])]),Lo,Wo,Do,e("p",null,[Ro,t(s,{to:"/Blog/new-releases.html#_3-1-1-2023-03-30"},{default:i(()=>[To]),_:1}),Ho]),No,Vo,Jo,e("p",null,[Fo,e("a",jo,[Uo,t(n)]),qo,t(s,{to:"/Blog/new-releases.html#_3-1-0-2023-03-10"},{default:i(()=>[Go]),_:1}),Xo]),e("p",null,[Yo,Ko,Qo,t(s,{to:"/Blog/new-releases.html#_3-0-1-2023-01-18"},{default:i(()=>[$o]),_:1}),et]),ot,e("p",null,[tt,t(s,{to:"/Blog/new-releases.html#_3-1-0-2023-03-10"},{default:i(()=>[nt]),_:1}),st]),e("p",null,[it,t(s,{to:"/Docs/getting_started.html#using-ibm-z-open-editor-in-cloud-based-editors"},{default:i(()=>[rt]),_:1}),at]),dt,lt,e("p",null,[ht,t(s,{to:"/Blog/new-releases.html#_3-0-1-2023-01-18"},{default:i(()=>[ct]),_:1}),pt]),ut,_t,mt,e("p",null,[ft,t(s,{to:"/Docs/zopeneditor_v3.html"},{default:i(()=>[wt]),_:1}),gt]),e("p",null,[bt,t(s,{to:"/Blog/new-releases.html#_3-0-0-2022-11-22"},{default:i(()=>[vt]),_:1}),It]),zt,yt,e("p",null,[e("a",Bt,[Mt,t(n)]),kt,Et,xt]),St,e("p",null,[Zt,Ct,Ot,e("a",Pt,[At,t(n)]),Lt]),Wt,e("p",null,[Dt,e("a",Rt,[Tt,t(n)]),Ht,e("a",Nt,[Vt,t(n)]),Jt]),Ft,e("p",null,[jt,e("a",Ut,[qt,t(n)]),Gt,t(s,{to:"/Blog/new-releases.html#_2-0-0-2022-03-15"},{default:i(()=>[Xt]),_:1}),Yt]),Kt,Qt,$t,e("p",null,[en,t(s,{to:"/Blog/new-releases.html#_1-4-1-2021-11-19"},{default:i(()=>[on]),_:1}),tn]),nn,sn,e("p",null,[rn,t(s,{to:"/Blog/new-releases.html#_1-4-0-2021-10-29"},{default:i(()=>[an]),_:1}),dn]),ln,hn,e("p",null,[cn,e("a",pn,[un,t(n)]),_n,t(s,{to:"/Blog/new-releases.html#_1-2-6-2021-08-19"},{default:i(()=>[mn]),_:1}),fn]),e("p",null,[wn,e("a",gn,[bn,t(n)]),vn]),In,zn,e("p",null,[yn,t(s,{to:"/Blog/new-releases.html#_1-2-5-2021-06-18"},{default:i(()=>[Bn]),_:1}),Mn]),kn,En,e("p",null,[xn,t(s,{to:"/Blog/new-releases.html#_1-2-1-2021-04-21"},{default:i(()=>[Sn]),_:1}),Zn,e("a",Cn,[On,t(n)]),Pn]),An,Ln,e("p",null,[Wn,Dn,Rn,e("a",Tn,[Hn,t(n)]),Nn]),Vn,Jn,Fn,e("p",null,[jn,e("a",Un,[qn,t(n)]),Gn]),Xn,e("p",null,[Yn,e("a",Kn,[Qn,t(n)]),$n]),es,os,e("p",null,[ts,e("a",ns,[ss,t(n)]),is]),rs,as,ds,e("p",null,[ls,e("a",hs,[cs,t(n)]),ps,e("a",us,[_s,t(n)]),ms,e("a",fs,[ws,t(n)]),gs,e("a",bs,[vs,t(n)]),Is]),e("p",null,[zs,e("a",ys,[Bs,t(n)])]),Ms,ks,Es,e("p",null,[xs,e("a",Ss,[Zs,t(n)]),Cs,Os,Ps]),As,e("p",null,[Ls,e("a",Ws,[Ds,t(n)])]),e("p",null,[Rs,e("a",Ts,[Hs,t(n)]),Ns]),Vs,Js,Fs,e("p",null,[js,e("a",Us,[qs,t(n)]),Gs]),Xs,e("p",null,[Ys,e("a",Ks,[Qs,t(n)]),$s]),ei,oi,e("p",null,[ti,e("a",ni,[si,t(n)]),ii,ri,ai,e("a",di,[li,t(n)]),hi]),e("p",null,[ci,e("a",pi,[ui,t(n)]),_i]),mi,fi,e("p",null,[wi,e("a",gi,[bi,t(n)]),vi,t(s,{to:"/Docs/customizing_the_outline_view.html#hlasm"},{default:i(()=>[Ii]),_:1}),zi,t(s,{to:"/Docs/setting_fileassociations.html"},{default:i(()=>[yi]),_:1}),Bi]),e("p",null,[Mi,t(s,{to:"/Blog/in-the-cloud-with-che.html"},{default:i(()=>[ki]),_:1}),Ei,e("a",xi,[Si,t(n)]),Zi,e("a",Ci,[Oi,t(n)])]),Pi,Ai,e("p",null,[Li,e("a",Wi,[Di,t(n)]),Ri]),e("p",null,[Ti,e("a",Hi,[Ni,t(n)]),Vi]),Ji,Fi,e("p",null,[ji,e("a",Ui,[qi,t(n)]),Gi,t(s,{to:"/Docs/editor_codechanges_hlasm.html"},{default:i(()=>[Xi]),_:1}),Yi]),Ki,Qi,$i,er,e("ul",null,[e("li",null,[or,e("a",tr,[nr,t(n)]),sr]),e("li",null,[ir,e("a",rr,[ar,t(n)]),dr]),e("li",null,[lr,e("a",hr,[cr,t(n)]),pr]),e("li",null,[ur,e("a",_r,[mr,t(n)]),fr]),e("li",null,[wr,e("a",gr,[br,t(n)]),vr]),e("li",null,[Ir,e("a",zr,[yr,t(n)]),Br]),e("li",null,[Mr,e("a",kr,[Er,t(n)]),xr]),e("li",null,[Sr,e("a",Zr,[Cr,t(n)]),Or]),e("li",null,[Pr,e("a",Ar,[Lr,t(n)]),Wr]),e("li",null,[Dr,e("a",Rr,[Tr,t(n)]),Hr]),e("li",null,[Nr,e("a",Vr,[Jr,t(n)]),Fr]),e("li",null,[jr,e("a",Ur,[qr,t(n)]),Gr]),e("li",null,[Xr,e("a",Yr,[Kr,t(n)]),Qr]),e("li",null,[$r,e("a",ea,[oa,t(n)]),ta]),e("li",null,[na,e("a",sa,[ia,t(n)]),ra]),e("li",null,[aa,e("a",da,[la,t(n)]),ha]),e("li",null,[ca,e("a",pa,[ua,t(n)]),_a])]),ma,e("p",null,[fa,e("a",wa,[ga,t(n)]),ba]),va,Ia,e("p",null,[za,e("a",ya,[Ba,t(n)]),Ma]),e("p",null,[ka,t(s,{to:"/Blog/ibm-wazi-development-client-introduction-blog.html"},{default:i(()=>[Ea]),_:1}),xa]),Sa,Za,e("p",null,[Ca,t(s,{to:"/Blog/new-releases.html#_0-5-0-2020-06-12"},{default:i(()=>[Oa]),_:1}),Pa]),e("p",null,[Aa,e("a",La,[Wa,t(n)]),Da]),e("p",null,[Ra,e("a",Ta,[Ha,t(n)]),Na]),Va,e("ul",null,[e("li",null,[t(s,{to:"/Blog/hlasm-blog.html"},{default:i(()=>[Ja]),_:1})])]),Fa,ja,Ua,e("ul",null,[e("li",null,[e("a",qa,[Ga,t(n)])]),e("li",null,[e("a",Xa,[Ya,t(n)])]),e("li",null,[e("a",Ka,[Qa,t(n)])]),e("li",null,[e("a",$a,[ed,t(n)])]),e("li",null,[e("a",od,[td,t(n)])])]),nd,sd,e("p",null,[id,e("a",rd,[ad,t(n)]),dd,e("a",ld,[hd,t(n)]),cd]),e("p",null,[pd,t(s,{to:"/Blog/rse-march-beta.html"},{default:i(()=>[ud]),_:1}),_d]),md,fd,e("ul",null,[e("li",null,[wd,e("a",gd,[bd,t(n)]),vd,t(s,{to:"/Blog/external-posts.html"},{default:i(()=>[Id]),_:1}),zd]),e("li",null,[yd,t(s,{to:"/Docs/editor_codechanges.html"},{default:i(()=>[Bd]),_:1}),Md])]),kd,Ed,e("p",null,[xd,e("a",Sd,[Zd,t(n)]),Cd]),e("ul",null,[e("li",null,[t(s,{to:"/Blog/code-snippets.html"},{default:i(()=>[Od]),_:1})])]),Pd,Ad,e("p",null,[Ld,t(s,{to:"/Blog/in-the-cloud-with-che.html"},{default:i(()=>[Wd]),_:1}),Dd,e("a",Rd,[Td,t(n)]),Hd]),Nd,Vd,e("p",null,[Jd,e("a",Fd,[jd,t(n)]),Ud]),qd,Gd,Xd,e("ul",null,[e("li",null,[t(s,{to:"/Blog/in-the-cloud-with-che.html"},{default:i(()=>[Yd]),_:1})]),e("li",null,[t(s,{to:"/Blog/web-based-with-theia.html"},{default:i(()=>[Kd]),_:1})])]),Qd,$d,e("p",null,[e("a",el,[ol,t(n)]),tl]),nl,sl,e("p",null,[il,e("a",rl,[al,t(n)]),dl]),ll,hl,e("p",null,[cl,e("a",pl,[ul,t(n)]),_l])],64)}var vl=c(p,[["render",ml]]);export{vl as default};
diff --git a/assets/new-releases.html.50a21e1d.js b/assets/new-releases.html.50a21e1d.js
new file mode 100644
index 000000000..dabc4592d
--- /dev/null
+++ b/assets/new-releases.html.50a21e1d.js
@@ -0,0 +1 @@
+const e={key:"v-7e9516cc",path:"/Blog/new-releases.html",title:"IBM Z Open Editor Releases",lang:"en-US",frontmatter:{},excerpt:"",headers:[{level:1,title:"IBM Z Open Editor Releases",slug:"ibm-z-open-editor-releases",children:[{level:2,title:"4.5.0 - 2024/09/19",slug:"_4-5-0-2024-09-19",children:[]},{level:2,title:"4.4.0 - 2024/08/12",slug:"_4-4-0-2024-08-12",children:[]},{level:2,title:"4.3.0 - 2024/06/18",slug:"_4-3-0-2024-06-18",children:[]},{level:2,title:"4.2.0 - 2024/05/16",slug:"_4-2-0-2024-05-16",children:[]},{level:2,title:"4.1.0 - 2024/03/28",slug:"_4-1-0-2024-03-28",children:[]},{level:2,title:"4.0.0 - 2024/03/15",slug:"_4-0-0-2024-03-15",children:[]},{level:2,title:"3.4.0 - 2024/02/29",slug:"_3-4-0-2024-02-29",children:[]},{level:2,title:"3.3.3 - 2023/12/15",slug:"_3-3-3-2023-12-15",children:[]},{level:2,title:"3.3.2 - 2023/11/28",slug:"_3-3-2-2023-11-28",children:[]},{level:2,title:"3.3.1 - 2023/11/07",slug:"_3-3-1-2023-11-07",children:[]},{level:2,title:"3.3.0 - 2023/10/25",slug:"_3-3-0-2023-10-25",children:[]},{level:2,title:"3.2.3 - 2023/10/11",slug:"_3-2-3-2023-10-11",children:[]},{level:2,title:"3.2.2 - 2023/09/15",slug:"_3-2-2-2023-09-15",children:[]},{level:2,title:"3.2.1 - 2023/07/19",slug:"_3-2-1-2023-07-19",children:[]},{level:2,title:"3.2.0 - 2023/06/16",slug:"_3-2-0-2023-06-16",children:[]},{level:2,title:"3.1.1 - 2023/03/30",slug:"_3-1-1-2023-03-30",children:[]},{level:2,title:"3.1.0 - 2023/03/10",slug:"_3-1-0-2023-03-10",children:[]},{level:2,title:"3.0.1 - 2023/01/18",slug:"_3-0-1-2023-01-18",children:[]},{level:2,title:"3.0.0 - 2022/11/22",slug:"_3-0-0-2022-11-22",children:[]},{level:2,title:"2.2.0 - 2022/09/20",slug:"_2-2-0-2022-09-20",children:[]},{level:2,title:"2.1.1 - 2022/08/14",slug:"_2-1-1-2022-08-14",children:[]},{level:2,title:"2.1.0 - 2022/06/14",slug:"_2-1-0-2022-06-14",children:[]},{level:2,title:"2.0.3 - 2022/05/20",slug:"_2-0-3-2022-05-20",children:[]},{level:2,title:"2.0.2 - 2022/04/25",slug:"_2-0-2-2022-04-25",children:[]},{level:2,title:"2.0.0 - 2022/03/15",slug:"_2-0-0-2022-03-15",children:[]},{level:2,title:"1.4.1 - 2021/11/19",slug:"_1-4-1-2021-11-19",children:[]},{level:2,title:"1.4.0 - 2021/10/29",slug:"_1-4-0-2021-10-29",children:[]},{level:2,title:"1.2.6 - 2021/08/19",slug:"_1-2-6-2021-08-19",children:[]},{level:2,title:"1.2.5 - 2021/06/18",slug:"_1-2-5-2021-06-18",children:[]},{level:2,title:"1.2.1 - 2021/04/21",slug:"_1-2-1-2021-04-21",children:[]},{level:2,title:"1.2.0 - 2021/03/19",slug:"_1-2-0-2021-03-19",children:[]},{level:2,title:"1.1.3 - 2020/12/12",slug:"_1-1-3-2020-12-12",children:[]},{level:2,title:"1.1.2 - 2020/12/09",slug:"_1-1-2-2020-12-09",children:[]},{level:2,title:"1.1.1 - 2020/11/6",slug:"_1-1-1-2020-11-6",children:[]},{level:2,title:"1.1.0 - 2020/10/23",slug:"_1-1-0-2020-10-23",children:[]},{level:2,title:"1.0.3 - 2020/08/07",slug:"_1-0-3-2020-08-07",children:[]},{level:2,title:"1.0.2 - 2020/06/30",slug:"_1-0-2-2020-06-30",children:[]},{level:2,title:"1.0.1/0.5.2 - 2020/06/23",slug:"_1-0-1-0-5-2-2020-06-23",children:[]},{level:2,title:"1.0.0 - 2020/06/12",slug:"_1-0-0-2020-06-12",children:[]},{level:2,title:"0.5.0 - 2020/06/12",slug:"_0-5-0-2020-06-12",children:[]},{level:2,title:"0.4.9 - 2020/04/23",slug:"_0-4-9-2020-04-23",children:[]},{level:2,title:"0.4.7 - 2020/03/27",slug:"_0-4-7-2020-03-27",children:[]},{level:2,title:"0.4.5 - 2020/01/07",slug:"_0-4-5-2020-01-07",children:[]},{level:2,title:"0.4.3 - 2019/12/18",slug:"_0-4-3-2019-12-18",children:[]},{level:2,title:"0.4.1 - 2019/11/21",slug:"_0-4-1-2019-11-21",children:[]},{level:2,title:"0.3.11 - 2019/09/27",slug:"_0-3-11-2019-09-27",children:[]},{level:2,title:"0.3.9 - 2019/09/23",slug:"_0-3-9-2019-09-23",children:[]},{level:2,title:"0.3.7 - 2019/09/17",slug:"_0-3-7-2019-09-17",children:[]},{level:2,title:"0.3.5 - 2019/09/13",slug:"_0-3-5-2019-09-13",children:[]}]}],git:{updatedTime:1726695456e3,contributors:[{name:"Peter Haumer",email:"4391934+phaumer@users.noreply.github.com",commits:19},{name:"Peter Haumer",email:"phaumer@us.ibm.com",commits:18},{name:"PETER HAUMER",email:"phaumer@us.ibm.com",commits:6},{name:"kmaselli",email:"81706519+kmaselli@users.noreply.github.com",commits:6},{name:"Billie Jean Simmons",email:"billiejean.simmons@ibm.com",commits:5},{name:"Chun Hong Zheng",email:"chunhzh@cn.ibm.com",commits:3},{name:"Lauren Li",email:"45975633+lauren-li@users.noreply.github.com",commits:3},{name:"Hestia Zhang",email:"Hestia.Zhang@ibm.com",commits:2},{name:"KRISTINA MAYO",email:"ktopchi@us.ibm.com",commits:1},{name:"Lauren Li",email:"Lauren.Li@ibm.com",commits:1},{name:"Min Huang",email:"minhsh@cn.ibm.com",commits:1},{name:"Prasang-A-Prajapati",email:"Prasang.A.Prajapati@ibm.com",commits:1},{name:"Saile Daimwood",email:"sdaimwood@ibm.com",commits:1},{name:"Shi Kun Li",email:"shikunli@cn.ibm.com",commits:1},{name:"shikunli",email:"shikunli@cn.ibm.com",commits:1}]},filePathRelative:"Blog/new-releases.md"};export{e as data};
diff --git a/assets/new-releases.html.5ed0be94.js b/assets/new-releases.html.5ed0be94.js
deleted file mode 100644
index df42c519c..000000000
--- a/assets/new-releases.html.5ed0be94.js
+++ /dev/null
@@ -1 +0,0 @@
-import{r as n,o as a,a as l,b as e,d as t,w as d,F as h,e as o,c as i}from"./app.f6cb3ed9.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const u={},_=e("h1",{id:"ibm-z-open-editor-releases",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z-open-editor-releases","aria-hidden":"true"},"#"),o(" IBM Z Open Editor Releases")],-1),p=e("h2",{id:"_4-4-0-2024-08-12",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_4-4-0-2024-08-12","aria-hidden":"true"},"#"),o(" 4.4.0 - 2024/08/12")],-1),f=o("Fixed the issue where Java was not being found on Windows or Linux when Z Open Editor searched the user's system. ("),g={href:"https://github.com/IBM/zopeneditor-about/issues/420",target:"_blank",rel:"noopener noreferrer"},m=o("Issue 420"),b=o(")"),w=i("
    • Added code folding to our COBOL language server, which features folding for Divisions, Sections, Paragraphs, Data-items, and EXEC SQL/CICS statements. Also added code folding range support to JCL.
    • Improved the COBOL and JCL Outline views to include comments in the selection ranges when clicking an outline node.
    • Fixed the issue with the resolution order for the NAMES() compiler option in PL/I when it was listed before include file locations.
    • Added the file extension .dbd, .mfs, and .pcb to the defaults for our HLASM editor.
    • We now provide snippet style code completion for HLASM operations and macros. Use tab to fill out or remove various parameters when the operation or macro is selected from the code completion list. The editor will then also show syntax errors when manually typing operation parameters incorrectly.
    • Added Go to References support for HLASM Operations and Macros to see references within the same file for a selected operation.
    • Fixed the issue in JCL where an incorrect error was shown for DD statement: "JCL incorrectly highlights empty DD line as error".
    • Fixed the issue in JCL where an incorrect error was shown for EXEC DLI and XOPTS(DLI) statements.
    • Performance improvements for language server document requests when finding the copybooks/include files. The language server now prioritizes requesting the most recently opened documents.
    • Experimental: all Z Open Editor VS Code extension strings have been localized to French and German using IBM's AI machine translation. Let us know if you like these translations.
      • ",10),I=e("p",null,"Advanced features:",-1),y=e("ul",null,[e("li",null,"New feature: added filter and search operations to the z/OS Resources table. You can now search within the content of sequential data sets that are currently listed in your table; search requires using IBM's RSE API. We also added new filter options to the table for RSE API and z/OSMF to help you refine the list displayed for the Zowe query directly in the table. More search and filter capabilities will be added for RSE API users soon."),e("li",null,'Combined "last modified" date and "last modified" time columns into "last modified" in z/OSMF PDS member views of the z/OS Resources Table.'),e("li",null,"Fixed the issue where the z/OS Resources Table was not compatible with MVS date formats in RSE API v1.1.5."),e("li",null,"Various fixes, refinements and improvements for remote preprocessor support such as improved logging of the remote preprocessor execution output, better error handling, support for z/OSMF with TSO Zowe profiles, added the 'Compare preprocessor input and output files' command to remote preprocessor files as well as improvements for managing the output file."),e("li",null,"Added a progress bar and a Cancel button to user build operations. After clicking the Cancel button, user build will wait until any remote operation is completed and then stop.")],-1),v=e("p",null,"IBM RSE API Plug-in for Zowe CLI:",-1),x=o("We are now providing a variant of the RSE API CLI Plug-in that can be used for installation in air gapped development environments. Find "),S=e("code",null,"ibm-rse-api-for-zowe-cli-airgap-4.4.0.tgz",-1),B=o(" in our IBM Wazi for VS Code Zip file at "),A={href:"https://ibm.github.io/mainframe-downloads/downloads.html",target:"_blank",rel:"noopener noreferrer"},C=o("https://ibm.github.io/mainframe-downloads/downloads.html"),E=o("."),k=e("li",null,"Fixed the issue with multiple items included in data set filter search with RSE profiles.",-1),O=o("Fixed the issue reported using RSE CLI for downloading files when using Nodejs v20. ("),L={href:"https://github.com/IBM/zopeneditor-about/issues/427",target:"_blank",rel:"noopener noreferrer"},M=o("Issue 427"),z=o(")"),P=e("li",null,[o("Added a new "),e("code",null,"change"),o(" sub-command: "),e("code",null,"clear-tag"),o(" which clears the tags of the specified UNIX System Services file.")],-1),F=e("h2",{id:"_4-3-0-2024-06-18",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_4-3-0-2024-06-18","aria-hidden":"true"},"#"),o(" 4.3.0 - 2024/06/18")],-1),R=e("strong",null,"Note",-1),Z=o(": Import update for the release of version 4.3.0 of IBM Z Open Editor: "),U={href:"https://www.ibm.com/products/watsonx-code-assistant-z",target:"_blank",rel:"noopener noreferrer"},T=o("IBM watsonx Code Assistant for Z"),D=o(", which supports AI-assisted transformation of COBOL to Java for modernizing applications, has now been moved into it's own VS Code extension IBM watsonx Code Assistant for Z version 2.0.0. All functionality has been migrated into this new dedicated extension. Receive your copy of the Z Code Assistant via your Passport Advantage Online account. See the "),X={href:"https://www.ibm.com/docs/en/watsonx-code-assistant-4z",target:"_blank",rel:"noopener noreferrer"},N=o("Documentation"),H=o(" for more details."),J=e("li",null,"New advanced feature: run your custom COBOL preprocessor on z/OS directly from our editor and edit your files without any syntax errors caused by preprocessor statements. We now offer local preprocessor execution and editor integrations as well as remote execution via TSO commands on z/OS.",-1),V=o("All new JCL language server: with this release we add language support for "),q={href:"https://www.ibm.com/docs/en/SSLTBW_3.1.0/pdf/ieab600_v3r1.pdf",target:"_blank",rel:"noopener noreferrer"},W=o("z/OS MVS JCL"),G=i(". This first version includes the following features: 
      • Improved syntax highlighting
      • Real-time syntax errors
      • Code completion using Ctrl/Cmd + Space
      • Outline view
      • On-enter rules in Textmate grammar for JCL 
        • Auto prefix newline with // if previous line prefixed with // (except for in-stream declarations i.e. DD *). Indentation is inherited (up to column 16 for non-empty lines). JOB declarations are automatically indented to column 16
        • Auto comment continuation for lines prefixed with //*
      • Vertical rulers at significant JCL column numbers (2, 10, 11, 15, 16, 72, 80)
      • JCL Custom tabstops (Default tabstops are: [0, 2, 10, 15, 19, 29, 39, 49, 59, 71, 72])
      • Support for commenting and uncommenting highlighted selections using Ctrl/Cmd + /
      ",2),j=o("Completed support for PL/I v6.1 January 2024 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this "),Y={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/di-hu1/2024/01/31/january-2024-documentation-refresh-for-enterprise",target:"_blank",rel:"noopener noreferrer"},Q=o("blog post"),K=o(" for details. Additionally, support for the new "),$=e("code",null,"JSONIGNORE",-1),ee=o(", "),oe=e("code",null,"JSONNULL",-1),te=o(" keywords was added."),se=e("li",null,"Fixed the issue in the PL/I editor evaluating the names for include files differently than the compiler if the name includes special characters.",-1),ie=o("Fixed the issue of false unreachable code warnings around EXEC CICS PERFORM + HANDLE statements. ("),ne={href:"https://github.com/IBM/zopeneditor-about/issues/52",target:"_blank",rel:"noopener noreferrer"},re=o("Issue 52"),ae=o(")"),le=o("Fixed the issue of false unreachable code warnings around EXEC SQL WHENEVER statements. "),de={href:"https://github.com/IBM/zopeneditor-about/issues/63",target:"_blank",rel:"noopener noreferrer"},he=o("Issue 63"),ce=o(")"),ue=e("li",null,[o("Fixed the issue in the REXX editor showing incorrect syntax errors for "),e("code",null,"ELSE"),o(" statements in certain scenarios.")],-1),_e=o("Fixed the issue in HLASM where optional operands were not correctly accounted for when evaluating the number of operands provided. ("),pe={href:"https://github.com/IBM/zopeneditor-about/issues/418",target:"_blank",rel:"noopener noreferrer"},fe=o("Issue 418"),ge=o(")"),me=e("li",null,"Added support for double-byte character editing. The editor will decorate double-byte character strings using guillemets icons and display a byte counter in the status bar giving users information about how many bytes they have left for the current line to avoid truncation.",-1),be=e("li",null,"Extended the status bar information for the active Zowe profiles, making it an active button with options to change the profile selection. For RSE API profiles, it provides the option to update the z/OS password.",-1),we=e("li",null,"Fixed the issue where renaming sequential data sets using the z/OS resources tables would temporarily show empty attributes for the renamed data set.",-1),Ie=e("p",null,"IBM RSE API Plug-in for Zowe:",-1),ye=e("ul",null,[e("li",null,"Added a check for Zowe CLI version compatibility that is executed by the RSE API plugin for Zowe CLI during installation."),e("li",null,"Uploading files to z/OS UNIX System Service using RSE API profiles can now automatically detect if the file is binary."),e("li",null,"Fixed the issue of showing an incorrect error message when no data sets were found that match a search pattern.")],-1),ve=e("h2",{id:"_4-2-0-2024-05-16",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_4-2-0-2024-05-16","aria-hidden":"true"},"#"),o(" 4.2.0 - 2024/05/16")],-1),xe=o("New advanced feature: custom macro resolution in HLASM programs with references to macros in local files. The HLASM editor shows hovers, document links, go to definition, and code completion for macros. This feature works with one to many macro declarations per include file, which is achieved by pre-scanning macro files if they can be found in local ZAPP property groups. For more information, see "),Se=o("Custom Macros for HLASM"),Be=o("."),Ae=e("li",null,[o("Improved advanced feature: the z/OS resources table is updated to also support UNIX System Services. You can browse, filter, sort, open, download, upload, create, and copy your unix folders and files with the same user experience as in our previous release for MVS and JES. In addition, you find many UX refinements and polish for all views of this table. We also fixed "),e("ul",null,[e("li",null,"presenting and sorting numbers and dates based on the user's locale."),e("li",null,"presenting DSNTYPE for MVS data sets, even if the value is not provided by z/OSMF.")])],-1),Ce=o("Added support for COBOL User Defined Function Prototypes. See "),Ee={href:"https://www.ibm.com/docs/en/cobol-zos/6.4?topic=applications-using-function-prototypes",target:"_blank",rel:"noopener noreferrer"},ke=o("COBOL documentation"),Oe=o(" for details."),Le=o("Fix the issue where formatting EXEC SQL statements resulted in incorrect syntax ("),Me={href:"https://github.com/IBM/zopeneditor-about/issues/400",target:"_blank",rel:"noopener noreferrer"},ze=o("Issue 400"),Pe=o(")."),Fe=o("Reorganized our startup and restart code to avoid problems such as "),Re={href:"https://github.com/IBM/zopeneditor-about/issues/403",target:"_blank",rel:"noopener noreferrer"},Ze=o("Issue 403"),Ue=o("."),Te=i('
      IBM RSE API Plug-in for Zowe:
      • Fixed the issue of spool files not being correctly exported when their record length exceeded that of the destination dataset, resulting in truncation.
      • Fixed typographical errors in the new common-properties commands.
      • Fixed the issue that is seen downloading all members of a data set.
      IBM watsonx Code Assistant for Z:
      • Added editing of local variable names during class generation that will then be used during Java method generation.
      • Added editing of method input parameters during class generation that will then be used during Java class and method generation.
      • Improved Java method generation by sanitizing the COBOL code, such as removing comments and contents from columns 1-6 and 73-80.
      • Fixed the issue where for some edge cases the Java method generation was returning an empty code block.
      • Fix the issue where Java classes and methods were not appearing in the watsonx Code Assistant for Z tree view when the COBOL program was located in the top-level workspace folder.
      • Fixed the issue of the editor opening the same Java file in multiple editor tabs when using the watsonx Code Assistant for Z tree view.
      • Added support for proxy servers for watsonx interactions utilizing the VS Code settings http.proxy, http.proxyStrictSSL, http.proxyAuthorization when http.proxySupport is switched to on.
      • Various fixes and refinements for the watsonx tree view interactions related to item and source code selection.
       4.1.0 - 2024/03/28
      ',5),De=o("Fixed the issue where SETC values were causing the HLASM parser to fail in certain scenarios. ("),Xe={href:"https://github.com/IBM/zopeneditor-about/issues/396",target:"_blank",rel:"noopener noreferrer"},Ne=o("Issue 396"),He=o(")"),Je=e("li",null,"Added new options for listing additional job attributes in RSE API Plug-in for Zowe CLI.",-1),Ve=e("li",null,"Added ability to search files in UNIX System Services by file name or content in RSE API Plug-in for Zowe CLI.",-1),qe=e("li",null,"Added new commands for storing and retrieving name/value pairs with RSE's Common Properties service in RSE API Plug-in for Zowe CLI.",-1),We=e("li",null,"Fixed the issue of failed downloads from z/OS for some file types using RSE API profiles.",-1),Ge=e("li",null,"Fixed the issue where downloading spool files with RSE API profiles would be stored with invalid file extensions.",-1),je=e("p",null,"IBM watsonx Code Assistant for Z updates:",-1),Ye=e("ul",null,[e("li",null,"Added a walkthrough for new users to get a step-by-step guide on how to use watsonx Code Assistant for Z. You can access the walkthrough from the Z Open Editor Welcome page or from the VS Code Welcome page."),e("li",null,"Added a new CodeLens when editing generated Java code to view and navigate to the COBOL source that watsonx Code Assistant for Z was using to generate a Java method."),e("li",null,"COBOL files selected for Transformation in watsonx Code Assistant for Z will no longer open in read-only mode.")],-1),Qe=e("h2",{id:"_4-0-0-2024-03-15",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_4-0-0-2024-03-15","aria-hidden":"true"},"#"),o(" 4.0.0 - 2024/03/15")],-1),Ke=o("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 "),$e={href:"https://ibm.biz/code-whatsnew",target:"_blank",rel:"noopener noreferrer"},eo=o("IBM Documentation"),oo=o("."),to=e("p",null,"To emphasize, none of the other features that you were using in previous releases are impacted by the update. Previous features are still available for free and will still be maintained and enhanced as always. We are also still fully committed to supporting z/OSMF and RSE API for the free as well as advanced capabilities.",-1),so=e("p",null,"Only the following three new features require a license. Our goal is to provide more and more advanced features such as these to Z Open Editor in the future:",-1),io=e("ol",null,[e("li",null,"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."),e("li",null,"z/OS Resources table: an all-new feature rich 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."),e("li",null,"Advanced Dependency-Based user build error reporting: User build logs are now automatically downloaded, parsed, and presented in the editor's Problems view with 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.")],-1),no=e("p",null,"We reorganized the Z Open Editor Welcome page for you to see the status of your trial license. You can unlock the features by importing an activation kit or connecting to an RSE API server with configured IDzEE licenses.",-1),ro=e("p",null,"Free languages updates:",-1),ao=o("Added support for the COBOL v6.4 February 2024 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this "),lo={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/dan-zhang1/2024/02/26/february-2024-documentation-refresh-for-enterprise",target:"_blank",rel:"noopener noreferrer"},ho=o("blog post"),co=o(" for details."),uo=o("Added support for the COBOL v6.4 October 2023 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this "),_o={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/jun-qian-zhou1/2023/10/31/october-2023-documentation-refresh-for-enterprise",target:"_blank",rel:"noopener noreferrer"},po=o("blog post"),fo=o(" for details."),go=o("Added support for the PL/I v6.1 January 2024 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this "),mo={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/di-hu1/2024/01/31/january-2024-documentation-refresh-for-enterprise",target:"_blank",rel:"noopener noreferrer"},bo=o("blog post"),wo=o(" for details."),Io=e("li",null,"Added support for the CICS v6.2 Beta Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features.",-1),yo=e("li",null,[o("Added support for the z/OS 3.1 default HLASM macros. z/OS 3.1 is now the default option. To change your z/OS level, search "),e("code",null,"zopeneditor.hlasm.zosMacrosVersion"),o(" in settings.")],-1),vo=o("Fixed the issue where the HLASM Language Server did not parse non-english characters correctly. ("),xo={href:"https://github.com/IBM/zopeneditor-about/issues/389",target:"_blank",rel:"noopener noreferrer"},So=o("#389"),Bo=o(")"),Ao=o("Added the debug scheme to our language clients, enabling full language server support providing you with features such as Outline view, Go to Definition, Find All References even when running IBM Z Open Debug sessions. ("),Co={href:"https://github.com/IBM/zopeneditor-about/issues/360",target:"_blank",rel:"noopener noreferrer"},Eo=o("#360"),ko=o(")"),Oo=e("p",null,"Free RSE API Plug-in for Zowe CLI updates:",-1),Lo=i("
    • Z Open Editor extends the Zowe Explorer's Jobs view experience: open a spool file in Zowe Explorer and Z Open Editor will automatically provide JCL and messages syntax highlighting.
    • Added support for changing file tags on USS for RSE API profiles in Zowe Explorer.
    • Added support to show partitioned data set member attributes for RSE API profiles in Zowe Explorer.
    • Added support for creating a data sets for RSE API profiles using the new templates from Zowe Explorer.
    • Added support for Zowe profile encoding with DBB User Build download of log files.
    • Added new command issue unix-shell for RSE API profiles that utilizes a streaming command output and allows users to set environment variables for the executing shell.
    • Added new command export spool-file for RSE API profiles allowing export of job spool files to a sequential data set or data set members.
    • Added support for refreshToken and auto-refresh-token for RSE API profiles in Zowe Explorer.
    • Switched to using RSE API streaming for raw content when uploading to and downloading from MVS, UNIX System Services, and JES files.
    • Fixed the issue with creating a partitioned data set of the type LIBRARY for RSE API profiles did not work correctly.
    • Fixed the issue of command issue unix returning an incorrect exit code.
      • ",11),Mo=o("Fixed the error when submitting jobs using the "),zo=e("code",null,"--wfo",-1),Po=o(" (wait for output) option using RSE API profiles. ("),Fo={href:"https://github.com/IBM/zopeneditor-about/issues/385",target:"_blank",rel:"noopener noreferrer"},Ro=o("#385"),Zo=o(")"),Uo=e("h2",{id:"_3-4-0-2024-02-29",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-4-0-2024-02-29","aria-hidden":"true"},"#"),o(" 3.4.0 - 2024/02/29")],-1),To=o('Fixed the issue with Embedded EXEC CICS statements where EXEC CICS GET CHANNEL was marked with the error "RESP expected instead of this input". ('),Do={href:"https://github.com/IBM/zopeneditor-about/issues/361",target:"_blank",rel:"noopener noreferrer"},Xo=o("Issue 361"),No=o(")"),Ho=e("li",null,'Fixed the issue with Embedded CICS EXCI statements where CICS EXCI was marked with the error "RESP expected instead of this input".',-1),Jo=o('Fixed the issue with Embedded SQL statements where SQLCA symbols were not resolved when an "EXEC SQL INCLUDE SQLCA" statement was inside of a conditional compilation block. ('),Vo={href:"https://github.com/IBM/zopeneditor-about/issues/379",target:"_blank",rel:"noopener noreferrer"},qo=o("Issue 379"),Wo=o(")"),Go=o('Fixed the issue of incorrectly showing an error about the absence of an end directive when the conditional compilation directive ">>define" was on the last line of a Copybook file. ('),jo={href:"https://github.com/IBM/zopeneditor-about/issues/374",target:"_blank",rel:"noopener noreferrer"},Yo=o("Issue 374"),Qo=o(")"),Ko=e("li",null,'Fixed the issue where COBOL COPY statements with a "." but without a whitespace were marked with an error.',-1),$o=o("Fixed the issue where document links were not resolving correctly when multiple documents were opened in parallel that pointed to the same include files in COBOL, PL/I, and HLASM files. ("),et={href:"https://github.com/IBM/zopeneditor-about/issues/363",target:"_blank",rel:"noopener noreferrer"},ot=o("Issue 363"),tt=o(")"),st=o("Fixed an issue where document links would not remove the red underline for an include file after loading correctly in COBOL, PL/I, and HLASM files. ("),it={href:"https://github.com/IBM/zopeneditor-about/issues/363",target:"_blank",rel:"noopener noreferrer"},nt=o("Issue 363"),rt=o(")"),at=o("Fixed the issue where REXX syntax highlighting would break when an empty comment statement was present "),lt=e("code",null,"/**/",-1),dt=o(". ("),ht={href:"https://github.com/IBM/zopeneditor-about/issues/384",target:"_blank",rel:"noopener noreferrer"},ct=o("Issue 384"),ut=o(")."),_t=e("p",null,"IBM watsonx Code Assistant for Z updates:",-1),pt=e("ul",null,[e("li",null,"Replaced the COBOL-centric class generation preview with a new Java-centric presentation for watsonx Code Assistant for Z. Users can now preview the Java classes to be generated in an expandable table view that outlines the variable and method member names next to their mapped COBOL names. They can click hyperlinks within the mapping view to navigate directly back to the COBOL source code files for comparison."),e("li",null,"Updated the watsonx Code Assistant for Z tree view to show a breakdown of method members per Java class that can be generated by the assistant's AI component. These methods are based on COBOL section and paragraph names and become available after the initial Java class generation step has been completed."),e("li",null,"Updated the watsonx Code Assistant for Z tree view to support a new workflow for reopening saved COBOL-to-Java mappings and regenerating Java code."),e("li",null,"Updated the watsonx Code Assistant for Z tree view with new icons and icon decorators that visualize which Java members mapped from COBOL paragraphs have already been generated and which not."),e("li",null,"Updated error handling, error message dialogs, and log file messages."),e("li",null,"Fixed the issue of the Welcome page checkbox for enabling/disabling watsonx Code Assistant for Z not being synchronized with the respective user setting.")],-1),ft=e("h2",{id:"_3-3-3-2023-12-15",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-3-3-2023-12-15","aria-hidden":"true"},"#"),o(" 3.3.3 - 2023/12/15")],-1),gt=o("Fixed the issue for COBOL where SKIP1, SKIP2, SKIP3, and EJECT tokens were not being handled correctly when placed within other statements to control white space. ("),mt={href:"https://github.com/IBM/zopeneditor-about/issues/307",target:"_blank",rel:"noopener noreferrer"},bt=o("Issue 307"),wt=o(")"),It=o("Fixed the issue where conditional compilation statements were not being handled correctly when placed in a "),yt=e("code",null,">>WHEN OTHER",-1),vt=o(" phrase. ("),xt={href:"https://github.com/IBM/zopeneditor-about/issues/366",target:"_blank",rel:"noopener noreferrer"},St=o("Issue 366"),Bt=o(")"),At=e("li",null,"Fixed the issue where the COBOL parser could hang or crash when a file's final line ended with a character in column 7.",-1),Ct=o("Fixed the issue where a language server would start before all ZAPP files were processed missing settings such as compiler options. ("),Et={href:"https://github.com/IBM/zopeneditor-about/issues/364",target:"_blank",rel:"noopener noreferrer"},kt=o("Issue 364"),Ot=o(")"),Lt=e("li",null,"Fixed the issue where the RSE API plugin for Zowe CLI command to upload a file to a UNIX System Services directory would show an error.",-1),Mt=e("li",null,"Various bug and serviceability fixes as well as UI refinements for IBM watsonx Code Assistant for Z. Generate Java classes now by using the icon next to the COBOL program name or by using the context menu. When entering an API key you will now receive a confirmation message after a server-side validation check.",-1),zt=e("h2",{id:"_3-3-2-2023-11-28",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-3-2-2023-11-28","aria-hidden":"true"},"#"),o(" 3.3.2 - 2023/11/28")],-1),Pt=e("li",null,"Required security updates for third party dependencies.",-1),Ft=o("Fixed the COBOL parsing issue where intermediate data names would be using an incorrect context. ("),Rt={href:"https://github.com/IBM/zopeneditor-about/issues/362",target:"_blank",rel:"noopener noreferrer"},Zt=o("Issue 362"),Ut=o(")"),Tt=o("Fixed multiple issues related to COBOL conditional compilation that caused incorrect syntax error messages. ("),Dt={href:"https://github.com/IBM/zopeneditor-about/issues/154",target:"_blank",rel:"noopener noreferrer"},Xt=o("Issue 154"),Nt=o(", "),Ht={href:"https://github.com/IBM/zopeneditor-about/issues/329",target:"_blank",rel:"noopener noreferrer"},Jt=o("Issue 329"),Vt=o(")"),qt=e("h2",{id:"_3-3-1-2023-11-07",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-3-1-2023-11-07","aria-hidden":"true"},"#"),o(" 3.3.1 - 2023/11/07")],-1),Wt=e("ul",null,[e("li",null,"Corrected the default URL for the IBM watsonx Code Assistant for Z server setting.")],-1),Gt=e("h2",{id:"_3-3-0-2023-10-25",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-3-0-2023-10-25","aria-hidden":"true"},"#"),o(" 3.3.0 - 2023/10/25")],-1),jt=o("New: IBM watsonx Code Assistant uses generative AI to accelerate code generation and increase developer productivity for application modernization. IBM watsonx Code Assistant for Z is now enabled in IBM Z Open Editor to drive the selective and incremental transformation of COBOL business services into well-architected high-quality Java code. It uses the inventory and analysis tools of IBM Application Discovery and Delivery Intelligence (ADDI) to support development teams in refactoring business services in COBOL, transforming COBOL code to Java code, and validating the resulting outcome. Learn more and sign up for a trial at "),Yt={href:"https://www.ibm.com/products/watsonx-code-assistant-zos",target:"_blank",rel:"noopener noreferrer"},Qt=o("https://www.ibm.com/products/watsonx-code-assistant-zos"),Kt=o("."),$t=e("p",null,"Other fixes and enhancements in this release:",-1),es=i("
    • Added support for CICS v6.2 Beta to COBOL and PL/I language servers.
    • Added support for line and block comment shortcuts in PL/I and REXX.
    • Machine instruction statements in HLASM are now identified when the number of operands is incorrect. Assembler instructions are not supported at the moment.
    • Improved the parsing behavior of HLASM language servers, particularly around continuation lines. Symbols that are continued should now have that reflected when you hover over references. Symbols that are used in continuation lines now support language functionalities, such as hover, Go to Definition, and Find References.
    • Fixed the bug where lowercase and mixed-case macros were not correctly displaying document links in HLASM.
    • Added support for internal macros that are declared in an HLASM file. Macros that are declared in an HLASM file now support code completion, hover, and Go to Definition in the file. Note that macros declared with the same name as a default SYS1.MACLIB macro will take precedence over the default macro.
    • Added .mac as another default file extension for HLASM program files.
    • Improved syntax highlighting around %INCLUDE statements in REXX.
    • A ZAPP file will now be automatically generated if none can be found in any of your workspaces when a COBOL, PL/I, HLASM, or REXX file is opened for the first time. This ZAPP file will search in all your local folders for include files, such as copybooks, so you should modify it for a more specific path or remote MVS locations afterwards. This behavior can be disabled with the new user setting "zopeneditor.zapp.generateZappOnDemand". Include file statements in all of these languages now also have the Quick Fix menu entry to open ZAPP files for troubleshooting and to open the ZAPP documentation for quick reference.
      • ",9),os=o('Changed the behavior of the "Run user build with full upload" command to now upload also all files that are specified with '),ts=e("code",null,"additionalDependencies",-1),ss=o(" in the ZAPP file. ("),is={href:"https://github.com/IBM/zopeneditor-about/issues/297",target:"_blank",rel:"noopener noreferrer"},ns=o("Issue 297"),rs=o(")"),as=o("Fixed the issue where user build did not properly filter search results for logs. ("),ls={href:"https://github.com/IBM/zopeneditor-about/issues/353",target:"_blank",rel:"noopener noreferrer"},ds=o("Issue 353"),hs=o(")"),cs=e("li",null,"Fixed the issue where user build related editor menu items and command palette items were displayed for COBOL and PL/I include files.",-1),us=o("Fixed the issue where user build menu items and command palette items were not displayed for VS Code 1.76 and earlier versions. ("),_s={href:"https://github.com/IBM/zopeneditor-about/issues/349",target:"_blank",rel:"noopener noreferrer"},ps=o("Issue 349"),fs=o(")"),gs=o("Fixed the issue where user build did not handle SSH keys for authentication in Zowe SSH profile. ("),ms={href:"https://github.com/IBM/zopeneditor-about/issues/355",target:"_blank",rel:"noopener noreferrer"},bs=o("Issue 355"),ws=o(")"),Is=i("
    • Fixed the issue with RSE API in Zowe Explorer where the user was prompted for username and password when using a token for authentication.
    • Added the ability to change owner, group, and permissions of Unix files on RSE CLI.
    • Added the ability to check a user's password expiration date with RSE CLI.
    • Fixed the issue where default RSE profiles were not displayed by default in Zowe Explorer's tree views when the team configuration profile did not contain z/OSMF profiles.
    • Added functionalities for RSE profiles, including copying files and directories in z/OS UNIX System Services, copying data sets, and cancelling jobs.
    • Added support for editing attributes in z/OS UNIX System Services for RSE profiles in Zowe Explorer.
    • Fixed the issue where RSE API Plug-in for Zowe CLI returned duplicate values when executing the list all members command using wildcard pattern parameters.
    • Fixed the issue where RSE API Plug-in for Zowe CLI did not return the correct error messages when executing the list or download all members command using incorrect parameters.
    • Fixed the issue where the Zowe profile status bar was not updated after edits were made to the team configuration profiles for RSE API profiles.
    • Added job timestamp to the output of the list jobs command for RSE API Plug-in for Zowe CLI when running commands against RSE API server v1.1.3.
      • ",10),ys=e("h2",{id:"_3-2-3-2023-10-11",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-2-3-2023-10-11","aria-hidden":"true"},"#"),o(" 3.2.3 - 2023/10/11")],-1),vs=o("Fixed the issue where Z Open Editor showed an incorrect warning about initializing secure credentials. ("),xs={href:"https://github.com/IBM/zopeneditor-about/issues/359",target:"_blank",rel:"noopener noreferrer"},Ss=o("Issue 359"),Bs=o(")"),As=e("li",null,"Fixed the issue where RSE API profiles that were using token-based authentication stored token details incorrectly in certain situations.",-1),Cs=e("li",null,"Fixed the issue where building projects that were not managed with Git produced Git errors. The fix changes the behavior that when no Git repository can be found then all .gitattributes files are ignored.",-1),Es=e("h2",{id:"_3-2-2-2023-09-15",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-2-2-2023-09-15","aria-hidden":"true"},"#"),o(" 3.2.2 - 2023/09/15")],-1),ks=o("Fixed the issue in COBOL where "),Os=e("code",null,"DEFINE(compilation-variable-name)",-1),Ls=o(" was not applying the default value "),Ms=e("code",null,"B'1'",-1),zs=o(". (part of "),Ps={href:"https://github.com/IBM/zopeneditor-about/issues/154",target:"_blank",rel:"noopener noreferrer"},Fs=o("Issue 154"),Rs=o(")"),Zs=o("Fixed the issue in COBOL where COBOL keywords are not able to be used as compilation-variable-name before a "),Us=e("code",null,">>DEFINE",-1),Ts=o(" statement. (part of "),Ds={href:"https://github.com/IBM/zopeneditor-about/issues/154",target:"_blank",rel:"noopener noreferrer"},Xs=o("Issue 154"),Ns=o(")"),Hs=o("Fixed the issue where IBM User Build was not properly filtering search results for logs. ("),Js={href:"https://github.com/IBM/zopeneditor-about/issues/353",target:"_blank",rel:"noopener noreferrer"},Vs=o("Issue 353"),qs=o(")"),Ws=e("li",null,"Fixed the issue where RSE API plugin for Zowe CLI returned duplicate values for list all members.",-1),Gs=e("li",null,"Fixed the issue where the Zowe profile status bar field would not get updated after making edits to RSE API profiles in team configuration files.",-1),js=e("li",null,"Security fix limiting telemetry data volumes.",-1),Ys=e("h2",{id:"_3-2-1-2023-07-19",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-2-1-2023-07-19","aria-hidden":"true"},"#"),o(" 3.2.1 - 2023/07/19")],-1),Qs=e("li",null,[o("Added syntax and content assist support for the "),e("code",null,"LOCATION"),o(" options ("),e("code",null,"LOC24"),o(" and "),e("code",null,"LOC31"),o(") in the "),e("code",null,"GETMAIN64 EXEC CICS"),o(" embedded CICS command.")],-1),Ks=o("Fixed the issue where the PL/I "),$s=e("code",null,"PROCESS MAR/MARGIN",-1),ei=o(" options did not accept a third parameter. ("),oi={href:"https://github.com/IBM/zopeneditor-about/issues/344",target:"_blank",rel:"noopener noreferrer"},ti=o("Issue 344"),si=o(")"),ii=e("li",null,[o("Fixed issues in the HLASM outline view to correctly handle duplicate elements such as "),e("code",null,"CSECTS"),o(" and "),e("code",null,"DSECTS"),o(" that are continued. Symbols that are reassigned will still point to the final declaration to prevent the outline from becoming overcrowded.")],-1),ni=o("Fixed the issue in User Build where menu items and commands were not available when VS Code 1.76 or earlier versions were used. ("),ri={href:"https://github.com/IBM/zopeneditor-about/issues/349",target:"_blank",rel:"noopener noreferrer"},ai=o("Issue 349"),li=o(")"),di=e("li",null,"Fixed the issue in User Build for COBOL and PL/I where a copybook or include file with a name that was a substring of another copybook or include file name was not identified as a dependency correctly.",-1),hi=e("li",null,"Fixed the issue that prevented the default RSE API Zowe CLI profiles to be displayed in Zowe Explorer's tree views at startup when Zowe team configuration profile files did not contain a z/OSMF profile.",-1),ci=e("h2",{id:"_3-2-0-2023-06-16",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-2-0-2023-06-16","aria-hidden":"true"},"#"),o(" 3.2.0 - 2023/06/16")],-1),ui=o("Added support for the COBOL v6.4 April 2023 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this "),_i={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/yuan-jie-song1/2023/04/28/april-2023-documentation-refresh-for-enterprise-co",target:"_blank",rel:"noopener noreferrer"},pi=o("blog post"),fi=o(" for details."),gi=o("Fixed the coloring of the keyword "),mi=e("code",null,"NOT",-1),bi=o(" in COBOL. ("),wi={href:"https://github.com/IBM/zopeneditor-about/issues/328",target:"_blank",rel:"noopener noreferrer"},Ii=o("Issue 328"),yi=o(")"),vi=o("Fixed the missing syntax errors when statements (such as "),xi=e("code",null,"COPY",-1),Si=o(") start to the left of Area A and overflowing data names (for example in "),Bi=e("code",null,"USING",-1),Ai=o(" statements) start to left of Area B. ("),Ci={href:"https://github.com/IBM/zopeneditor-about/issues/340",target:"_blank",rel:"noopener noreferrer"},Ei=o("Issue 340"),ki=o(")"),Oi=o("Fix the issue where comments were misinterpreted within a COPY statement when using an empty quoted pseudo text and the == identifier. ("),Li={href:"https://github.com/IBM/zopeneditor-about/issues/248",target:"_blank",rel:"noopener noreferrer"},Mi=o("Issue 248"),zi=o(")"),Pi=o("Removed the ability to perform Number and Unnumber actions when COBOL Language Server is not running. ("),Fi={href:"https://github.com/IBM/zopeneditor-about/issues/189",target:"_blank",rel:"noopener noreferrer"},Ri=o("Issue 189"),Zi=o(")"),Ui=o("Fixed certain COBOL words not highlighting correctly when placed at the end of a line. ("),Ti={href:"https://github.com/IBM/zopeneditor-about/issues/346",target:"_blank",rel:"noopener noreferrer"},Di=o("Issue 346"),Xi=o(")"),Ni=o("Added support for the PL/I v6.1 March 2023 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this "),Hi={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/di-hu1/2023/03/09/march-2023-documentation-refresh",target:"_blank",rel:"noopener noreferrer"},Ji=o("blog post"),Vi=o(" for details."),qi=o("Fixed the issue that caused PL/I comments to show a report when starting in column 1. ("),Wi={href:"https://github.com/IBM/zopeneditor-about/issues/135",target:"_blank",rel:"noopener noreferrer"},Gi=o("Issue 135"),ji=o(")"),Yi=e("li",null,"Fixed the issue with PL/I code completion when a variable is in the same column with a DCL statement.",-1),Qi=e("li",null,"Added preview hovers and clickable hyperlinks to open include files in REXX.",-1),Ki=e("li",null,[o("Added support for jump targets as well as "),e("code",null,"RSECT"),o(", "),e("code",null,"LOCTR"),o(", and "),e("code",null,"COM"),o(" control sections in the HLASM outline view.")],-1),$i=e("li",null,"Fixed the issue where preview hovers failed to load for HLASM COPY statements when the copied document was closed after previously being opened by using the hover's hyperlink.",-1),en=o('Added the user settings "zopeneditor..disableProblems" for each language to enable/disable the Problems view and syntax errors shown within the editor while maintaining other language features. It will allow users to continue working in the program with some language features despite parsing issues. This will not work in all circumstances as some syntax errors will also break other language features. ('),on={href:"https://github.com/IBM/zopeneditor-about/issues/199",target:"_blank",rel:"noopener noreferrer"},tn=o("Issue 199"),sn=o(" and "),nn={href:"https://github.com/IBM/zopeneditor-about/issues/203",target:"_blank",rel:"noopener noreferrer"},rn=o("Issue 203"),an=o(")"),ln=e("li",null,[o("Added the ability to define custom ZAPP variables in your personal user or workspace settings. Define variables in a new mappings table under "),e("code",null,"zopeneditor.zapp.variables"),o(" in the VS Code settings editor and then reference them in your ZAPP files with "),e("code",null,"${variable-name}"),o(". For example, define a variable here called "),e("code",null,"HLQ"),o(" with a value that represents your personal high-level qualifier on z/OS MVS. In your ZAPP file, reference it in a property group's location entry, such as "),e("code",null,"${HLQ}.COBOL.COPYBOOKs"),o(".")],-1),dn=e("li",null,"Fixed a copybook and include file watcher limitation about file precedence in remote and local non-syslib libraries.",-1),hn=o('Added the user setting "zopeneditor.zowe.maximumParallelFileDownloads" to specify how many parallel downloads Z Open Editor should perform when requesting include files from MVS. This will help minimize address spaces being allocated by z/OSMF. The default value of the setting is 5, and the maximum value is 10. Set it to 1 to disable parallel downloads. ('),cn={href:"https://github.com/IBM/zopeneditor-about/issues/134",target:"_blank",rel:"noopener noreferrer"},un=o("Issue 134"),_n=o(")"),pn=o('Added the user setting "zopeneditor.zowe.listBeforeDownload" to enable Z Open Editor to first search for the existence of a data set member before trying to download it when resolving include files. This will slow down performance, but will cause less logging on z/OS when using z/OSMF. The default is off to preserve performance. ('),fn={href:"https://github.com/IBM/zopeneditor-about/issues/134",target:"_blank",rel:"noopener noreferrer"},gn=o("Issue 134"),mn=o(")"),bn=e("li",null,"Fixed the issue where COBOL copybook requests were not sent in parallel in certain cases where Unix-style line endings were used on Windows.",-1),wn=e("li",null,"Fixed the issue where COBOL and PL/I include file requests were sometimes sent twice if a document could not be found.",-1),In=o("Fixed the issue that language server errors and exceptions caused by a timing issue are displayed. ("),yn={href:"https://github.com/IBM/zopeneditor-about/discussions/332",target:"_blank",rel:"noopener noreferrer"},vn=o("Issue 332"),xn=o(")"),Sn=e("li",null,"Fixed the issue where COPY or INCLUDE statements using custom libraries were in some cases resolved with syslib libraries.",-1),Bn=e("li",null,"Improved the folder watching performance. When folders within the scope of the current ZAPP property groups are deleted or created, open program files will be re-parsed instead of a complete extension restart.",-1),An=o("Added the ability for User Build to automatically run the "),Cn=e("code",null,"git check-attr",-1),En=o(" command in the background to evaluate "),kn=e("code",null,".gitattributes",-1),On=o(" in any folder of the workspace to upload files to UNIX System Services with the correct file encoding. If Git is not installed or cannot be found by the editor, Z Open Editor will continue trying to evaluate encoding itself. ("),Ln={href:"https://github.com/IBM/zopeneditor-about/issues/331",target:"_blank",rel:"noopener noreferrer"},Mn=o("Issue 331"),zn=o(")"),Pn=i("
    • Fixed the issue in User Build where files specified in a ZAPP file as additionalDependencies were not converted and tagged correctly when being uploaded to UNIX System Services.
    • Fixed the issue where User Build failed to run when dbbLogDir does not exist on UNIX System Services.
    • Added a warning message to the User Build output view to inform the user when the language server is stopped, because the language server will then not be able to compute dependencies such as copybooks and cannot upload them to z/OS.
    • Fixed the issue where User Build would not download any log files when the logFilePatterns property was not specified in the ZAPP file. Added a default that will download all files that match the pattern *.log.
      • ",4),Fn=o("Fixed an issue where user build menu was not always hidden when user build was disabled via settings. ("),Rn={href:"https://github.com/IBM/zopeneditor-about/issues/347",target:"_blank",rel:"noopener noreferrer"},Zn=o("Issue 347"),Un=o(")"),Tn=e("li",null,"Fixed an issue where ZAPP and ZCodeFormat code snippets would not show when editing in multi-root workspaces.",-1),Dn=e("li",null,"Updated dependencies for security audits.",-1),Xn=e("li",null,"Added support for JCL symbols as a parameter for jobs on RSE CLI.",-1),Nn=e("li",null,"Fixed an issue when saving files to z/OS with Zowe Explorer using RSE API and resolving conflicts with changes done by other users to the same file. VS Code will now properly show the conflicts in its differences editor allowing you to merge and save.",-1),Hn=e("h2",{id:"_3-1-1-2023-03-30",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-1-1-2023-03-30","aria-hidden":"true"},"#"),o(" 3.1.1 - 2023/03/30")],-1),Jn=e("li",null,"Fixed an issue with COBOL language code completion where code completion was not working on the first line of a COBOL file.",-1),Vn=o("Added support for "),qn=e("code",null,"$",-1),Wn=o(" and "),Gn=e("code",null,"<",-1),jn=o("/"),Yn=e("code",null,">",-1),Qn=o(" to be used as pseudo-text boundaries for the REPLACING strings in COBOL copybooks. ("),Kn={href:"https://github.com/IBM/zopeneditor-about/issues/305",target:"_blank",rel:"noopener noreferrer"},$n=o("Issue 305"),er=o(")"),or=o("Fixed an issue where COBOL literals were not being highlighted correctly when single quotes and double quotes were mixed. ("),tr={href:"https://github.com/IBM/zopeneditor-about/issues/308",target:"_blank",rel:"noopener noreferrer"},sr=o("Issue 308"),ir=o(")"),nr=o("Fixed an issue where the connection to the language server got disposed showing errors in the output view. ("),rr={href:"https://github.com/IBM/zopeneditor-about/discussions/332",target:"_blank",rel:"noopener noreferrer"},ar=o("Issue 332"),lr=o(")"),dr=e("li",null,"Fixed an issue where COBOL copybook requests did not download remote copybooks in parallel for non-syslib libraries.",-1),hr=o("Fixed an issue with "),cr=e("code",null,".gitattributes",-1),ur=o(" where "),_r=e("code",null,"*",-1),pr=o(" could not be used as a pattern for encoding the selection of files. ("),fr={href:"https://github.com/IBM/zopeneditor-about/issues/331",target:"_blank",rel:"noopener noreferrer"},gr=o("Issue 331"),mr=o(")"),br=o("Fixed an issue where the Zowe team configuration's encoding property was not used when no "),wr=e("code",null,".gitattributes",-1),Ir=o(" file was present or no match was found. ("),yr={href:"https://github.com/IBM/zopeneditor-about/issues/331",target:"_blank",rel:"noopener noreferrer"},vr=o("Issue 331"),xr=o(")"),Sr=o("Fixed an issue where User Build on Windows uploaded remote copybooks to USS. ("),Br={href:"https://github.com/IBM/zopeneditor-about/issues/333",target:"_blank",rel:"noopener noreferrer"},Ar=o("Issue 333"),Cr=o(")"),Er=e("li",null,"Updated Zowe and third-party dependencies addressing security scan results.",-1),kr=e("h2",{id:"_3-1-0-2023-03-10",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-1-0-2023-03-10","aria-hidden":"true"},"#"),o(" 3.1.0 - 2023/03/10")],-1),Or=o("Added support for the PL/I v6.1 October 2022 Refresh with updated syntax highlighting, outline view, real-time syntax checking, and other language related features. See this "),Lr={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/di-hu1/2022/10/27/october-2022-documentation-refresh-for-enterprise",target:"_blank",rel:"noopener noreferrer"},Mr=o("blog post"),zr=o(" for details."),Pr=o("Added support for using comma in the DEFINE compiler option syntax for COBOL. ("),Fr={href:"https://github.com/IBM/zopeneditor-about/issues/278",target:"_blank",rel:"noopener noreferrer"},Rr=o("Issue 278"),Zr=o(")"),Ur=e("li",null,"Added code completion support for statements containing Unicode Strings in COBOL.",-1),Tr=e("li",null,"Added code completion support for Compiler Directing statements (Compiler Options) in COBOL.",-1),Dr=e("li",null,[o("Added code completion support for "),e("code",null,"ENABLE PROGAM"),o(" in "),e("code",null,"EXEC CICS"),o(" Statements in COBOL.")],-1),Xr=o("Fixed an issue with COBOL where CBL or PROCESS service directive was not being recognized. ("),Nr={href:"https://github.com/IBM/zopeneditor-about/issues/253",target:"_blank",rel:"noopener noreferrer"},Hr=o("Issue 253"),Jr=o(")"),Vr=o("Fixed an issue with COBOL language showing false syntax errors for not correctly handling condition expressions on compilation variables in boolean format compared with the constant b'0' or b'1'. ("),qr={href:"https://github.com/IBM/zopeneditor-about/issues/321",target:"_blank",rel:"noopener noreferrer"},Wr=o("Issue 321"),Gr=o(")"),jr=o("Reverted syntax highlighting changes from last release for unsupported Boolean literals ("),Yr=e("code",null,"b",-1),Qr=o(" and "),Kr=e("code",null,"bx",-1),$r=o("). The IBM COBOL compiler currently does not support them. ("),ea={href:"https://github.com/IBM/zopeneditor-about/issues/308",target:"_blank",rel:"noopener noreferrer"},oa=o("Issue 308"),ta=o(")"),sa=e("li",null,[o("Added new option "),e("code",null,"alignToClauses"),o(" to "),e("code",null,"zcodeformat.yaml"),o(" files to support aligning TO clauses, aligning INTO clauses, and aligning TO clauses into column.")],-1),ia=o("Added file watching support for all languages so that programs with INCLUDE and COPY statements are now automatically re-parsed when local included files or copybooks are edited, created, or deleted. ("),na={href:"https://github.com/IBM/zopeneditor-about/issues/108",target:"_blank",rel:"noopener noreferrer"},ra=o("Issue 108"),aa=o("). See "),la={href:"https://ibm.github.io/zopeneditor-about/Docs/knownissues.html",target:"_blank",rel:"noopener noreferrer"},da=o("Known Issues"),ha=o(" for a limitation involving file precedence in remote and local non-syslib libraries."),ca=o("Improved performance for loading PL/I include files. Include files that are being downloaded from a remote z/OS system will now resolve much faster as download requests are performed in parallel to a maximum of five files at once. ("),ua={href:"https://github.com/IBM/zopeneditor-about/issues/269",target:"_blank",rel:"noopener noreferrer"},_a=o("Issue 269"),pa=o(")"),fa=o("Significantly improved performance for searching for local copybooks and include files via property groups that use glob patterns that expand to many results. ("),ga={href:"https://github.com/IBM/zopeneditor-about/issues/315",target:"_blank",rel:"noopener noreferrer"},ma=o("Issue 315"),ba=o(", "),wa={href:"https://github.com/IBM/zopeneditor-about/issues/293",target:"_blank",rel:"noopener noreferrer"},Ia=o("Issue 293"),ya=o(")"),va=o("Fixed an issue with no hover content of the copybook when COBOL source contains any errors in the COBOL program. ("),xa={href:"https://github.com/IBM/zopeneditor-about/issues/300",target:"_blank",rel:"noopener noreferrer"},Sa=o("Issue 300"),Ba=o(")"),Aa=o("Fixed a bug where large copybooks and include files were not completely resolved, resulting in errors such as "),Ca=e("code",null,"Unable to resolve reference",-1),Ea=o(" to variables included from copybooks. ("),ka={href:"https://github.com/IBM/zopeneditor-about/issues/313",target:"_blank",rel:"noopener noreferrer"},Oa=o("Issue 313"),La=o(")"),Ma=e("li",null,"Fixed a bug when editing REXX programs with remote REXX include files, which were resolved and saved with an incorrect file extension.",-1),za=e("li",null,"Full support for all the new Zowe Explorer JES filtering options when using RSE API profiles.",-1),Pa=o("Fixed issue where user build logs in nested directories were not being found ("),Fa={href:"https://github.com/IBM/zopeneditor-about/issues/296",target:"_blank",rel:"noopener noreferrer"},Ra=o("Issue 296"),Za=o(")."),Ua=o("Updated the user build output view and log file formatter to include timestamps when Z Open Editor's log level ("),Ta=e("code",null,"zopeneditor.logger",-1),Da=o(") is set to "),Xa=e("code",null,"DEBUG",-1),Na=o(" to help with trouble-shooting and measuring build times. ("),Ha={href:"https://github.com/IBM/zopeneditor-about/issues/292",target:"_blank",rel:"noopener noreferrer"},Ja=o("Issue 292"),Va=o(")"),qa=i("
    • Added support for path name specification for .gitattributes in IBM User Build.
    • Added new option for tagging files using working-tree-encoding os=zos in .gitattributes in IBM User Build as an alternative to zos-working-tree-encoding.
    • Addressed a concern that code snippets for ZAPP and ZCodeFormat files appeared in the code completion for all YAML files being edited. We therefore removed them from the Snippet Gallery and provided them as pure context-sensitive code completion items for <ctrl-space>.
      • ",3),Wa=o("Z Open Editor is now available to install as a web extension with limited capabilities when using Visual Studio Code in a browser, such as "),Ga=e("code",null,"vscode.dev",-1),ja=o(" or "),Ya=e("code",null,"github.dev",-1),Qa=o(". Try it by going to "),Ka={href:"https://vscode.dev/github/IBM/zopeneditor-sample",target:"_blank",rel:"noopener noreferrer"},$a=o("https://vscode.dev/github/IBM/zopeneditor-sample"),el=o(" and confirming to install the recommended extensions."),ol=e("h2",{id:"_3-0-1-2023-01-18",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-0-1-2023-01-18","aria-hidden":"true"},"#"),o(" 3.0.1 - 2023/01/18")],-1),tl=o("Performance improvements for loading COBOL copybooks. Copybooks that are being downloaded from a remote z/OS system will now resolve much faster as download requests are performed in parallel to a maximum of five files at once. PL/I will be updated with this capability in a later release. ("),sl={href:"https://github.com/IBM/zopeneditor-about/issues/269",target:"_blank",rel:"noopener noreferrer"},il=o("Issue 269"),nl=o(")"),rl=o('Fixed invalid "REDEFINES clause must begin in Area B" error shown in COBOL editor when using the REPLACING clause with a REDEFINES. ('),al={href:"https://github.com/IBM/zopeneditor-about/issues/287",target:"_blank",rel:"noopener noreferrer"},ll=o("Issue 287"),dl=o(")"),hl=o("Fixed issues with COBOL syntax highlighting when using literal delimiters. Respective language server fixes will be provided at a later date. ("),cl={href:"https://github.com/IBM/zopeneditor-about/issues/308",target:"_blank",rel:"noopener noreferrer"},ul=o("Issue 308"),_l=o(")"),pl=o("Fixed spelling in COBOL code snippets. ("),fl={href:"https://github.com/IBM/zopeneditor-about/issues/286",target:"_blank",rel:"noopener noreferrer"},gl=o("Issue 286"),ml=o(")"),bl=o("Fixed issue with "),wl=e("code",null,"%Replace",-1),Il=o(" in PL/I when using a minus sign in expression. ("),yl={href:"https://github.com/IBM/zopeneditor-about/issues/299",target:"_blank",rel:"noopener noreferrer"},vl=o("Issue 299"),xl=o(")"),Sl=o("Fixed an issue in User Build evaluating file names with special characters, such as "),Bl=e("code",null,"$",-1),Al=o(", in command shell expression. The DBB Daemon might also be effected by this problem. Remove the "),Cl=e("code",null,"-DBB_PERSONAL_DAEMON",-1),El=o(" command line parameter from the ZAPP file if you still run into this problem. ("),kl={href:"https://github.com/IBM/zopeneditor-about/issues/288",target:"_blank",rel:"noopener noreferrer"},Ol=o("Issue 288"),Ll=o(")"),Ml=o("Fixed an issue with User Build not downloading log files for programs with lower or mixed case filenames, because "),zl={href:"https://github.com/IBM/dbb-zappbuild",target:"_blank",rel:"noopener noreferrer"},Pl=o("dbb-zappbuild"),Fl=o(" will automatically capitalize log file names. User Build will now also automatically capitalize the build file name when using the "),Rl=e("code",null,"${buildFile.basename}",-1),Zl=o(" variable under "),Ul=e("code",null,"logFilePatterns",-1),Tl=o(" in the ZAPP file."),Dl=e("li",null,"Fixed syntax error in ZAPP code snippet for the dbb user build profile.",-1),Xl=e("li",null,"Fixed issues in our RSE API support when using special characters in z/OS file or directory names.",-1),Nl=e("li",null,"Fixed bugs and improved the usability of the change password command in the IBM RSE API Plug-in for Zowe CLI.",-1),Hl=e("li",null,"Fixed error being thrown in Zowe Explorer when RSE API list of all members returns no members.",-1),Jl=e("h2",{id:"_3-0-0-2022-11-22",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-0-0-2022-11-22","aria-hidden":"true"},"#"),o(" 3.0.0 - 2022/11/22")],-1),Vl=e("h3",{id:"breaking-changes",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#breaking-changes","aria-hidden":"true"},"#"),o(" Breaking Changes")],-1),ql=o("For more details on breaking changes and the required manual migration steps see our "),Wl={href:"https://ibm.github.io/zopeneditor-about/Docs/zopeneditor_v3.html",target:"_blank",rel:"noopener noreferrer"},Gl=o("user documentation"),jl=o("."),Yl=o("Z Open Editor now requires as a minimum a Java 11 runtime for running language servers. Users must upgrade their installed Java 8 runtime or Z Open Editor's language capabilities will not be available. See the "),Ql={href:"https://ibm.github.io/zopeneditor-about/Docs/getting_started.html",target:"_blank",rel:"noopener noreferrer"},Kl=o("documentation"),$l=o(" for the recommend Java Runtime Environments that you can use."),ed=e("li",null,'ZAPP files are now replacing various user settings and cannot be disabled enabled anymore. The user setting "zopeneditor.zapp.enabled" has been removed.',-1),od=e("li",null,[o("Property Groups have been removed from VS Code user and workspace settings. The setting "),e("code",null,'"zopeneditor.propertygroups"'),o(" is no longer available. Users must now use ZAPP files for specifying locations for include files. When only using Zowe Explorer to edit program files you need create a workspace folder with a ZAPP file as well.")],-1),td=o("Property Groups have been updated to contain references to local files as well as remote MVS files in the same property group item applying the same compiler options to each. The schema for a property group item has changed and users must update their ZAPP files. Please, check the "),sd={href:"https://ibm.github.io/zopeneditor-about/Docs/setting_propertygroup.html",target:"_blank",rel:"noopener noreferrer"},id=o("documentation"),nd=o(" for the details and our "),rd={href:"https://ibm.github.io/zopeneditor-about/Docs/zopeneditor_v3.html",target:"_blank",rel:"noopener noreferrer"},ad=o("migration page"),ld=o(" for how to upgrade."),dd=o("User Build settings have been updated to allow more configuration options such as allowing glob patterns to define files for uploading and downloading. See the "),hd={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-building-cobol-pli-hlasm-programs-user-build",target:"_blank",rel:"noopener noreferrer"},cd=o("IBM Wazi for VS Code User Build documentation"),ud=o(" for more details."),_d=e("h3",{id:"other-changes-and-fixes",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#other-changes-and-fixes","aria-hidden":"true"},"#"),o(" Other changes and fixes")],-1),pd=o("Fixed syntax of "),fd=e("code",null,"EXEC CICS INQUIRE SYSTEM MAXOPENTCBS",-1),gd=o(". ("),md={href:"https://github.com/IBM/zopeneditor-about/issues/257",target:"_blank",rel:"noopener noreferrer"},bd=o("Issue 257"),wd=o(")"),Id=i("
    • Added missing CICS v6.1 INQUIRE SYSTEM options: SRRTASKS, MEMLIMIT and MQCONN that used to cause syntax errors.
    • Fixed CICS v6.1 EXEC CICS CREATE DB2ENTRY ATTRIBUTES option incorrectly flagged as an error.
    • Fixed CICS v6.1 EXEC CICS SET TAGS REFRESH with NOHANDLE and RESP options incorrectly flagged as an error.
      • ",3),yd=o("Fixed an issue in COBOL syntax checking for a working storage variable starting with "),vd=e("code",null,"REMARKS",-1),xd=o(". It would be incorrectly identified as a REMARKS paragraph. ("),Sd={href:"https://github.com/IBM/zopeneditor-about/issues/276",target:"_blank",rel:"noopener noreferrer"},Bd=o("Issue 276"),Ad=o(")"),Cd=o("Fixed an issue with COBOL Syntax Highlighting in the sequence number fields (1-6 and 73-80). ("),Ed={href:"https://github.com/IBM/zopeneditor-about/issues/193",target:"_blank",rel:"noopener noreferrer"},kd=o("Issue 193"),Od=o(")"),Ld=o("Fixed a NullPointerException caused by the PL/I Code Folding feature when opening copybook/include file from PL/I Editor. ("),Md={href:"https://github.com/IBM/zopeneditor-about/issues/277",target:"_blank",rel:"noopener noreferrer"},zd=o("Issue 277"),Pd=o(")"),Fd=o("Fixed a NullPointerException caused by the PL/I Code Folding feature when the currently selected word matches a code completion suggestion that would alter the outline view. ("),Rd={href:"https://github.com/IBM/zopeneditor-about/issues/283",target:"_blank",rel:"noopener noreferrer"},Zd=o("Issue 283"),Ud=o(")"),Td=e("li",null,[o("Fixed an issue with syntax checking for PL/I related to function parameters of type File as well as a "),e("code",null,"DEFINE ORDINAL"),o(" containing signed integers in the VALUE attribute.")],-1),Dd=e("li",null,"Added REXX syntax highlighting for matching pairs of parenthesis. Auto-close parenthesis when typing.",-1),Xd=e("li",null,"Fixed an issue with improper error logging regarding the list command in RSE CLI.",-1),Nd=e("h2",{id:"_2-2-0-2022-09-20",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_2-2-0-2022-09-20","aria-hidden":"true"},"#"),o(" 2.2.0 - 2022/09/20")],-1),Hd=o(`Fixed User Build and the RSE API CLI's upload command to correctly encode file names with special characters. Files such as "T@A#R$C" will now be correctly uploaded to USS. (`),Jd={href:"https://github.com/IBM/zopeneditor-about/issues/266",target:"_blank",rel:"noopener noreferrer"},Vd=o("Issue 266"),qd=o(")"),Wd=o("Performance improvements for the REXX language server via parser optimizations. ("),Gd={href:"https://github.com/IBM/zopeneditor-about/issues/256",target:"_blank",rel:"noopener noreferrer"},jd=o("Issue 256"),Yd=o(")"),Qd=e("li",null,"Updated the REXX hover hyperlinks to point to the z/OS 2.5.0 reference.",-1),Kd=e("li",null,"Improved performance and reliability for the HLASM language server by implementing cancellation support for requests that are no longer valid, as well as optimizing handling of document-link requests for macros.",-1),$d=e("li",null,"Fixed a bug where mixed case variables were not handled correctly in HLASM.",-1),eh=e("li",null,"Fixed a bug where hovers sometimes did not show the correct code snippet for SYS1.MACLIB macros in HLASM.",-1),oh=o("Fixed a bug where document link underlines were not showing for HLASM macros when a file is first opened. Similar to a problem fixed for COBOL in ("),th={href:"https://github.com/IBM/zopeneditor-about/issues/81",target:"_blank",rel:"noopener noreferrer"},sh=o("Issue 81"),ih=o(") and ("),nh={href:"https://github.com/IBM/zopeneditor-about/issues/114",target:"_blank",rel:"noopener noreferrer"},rh=o("Issue 114"),ah=o(")."),lh=e("li",null,'Fixed a bug where "Failed to fetch COPYBOOK" errors were causing slowdowns across the HLASM language server.',-1),dh=e("li",null,"Added initial support for code folding for control statements to the PL/I language server.",-1),hh=e("h2",{id:"_2-1-1-2022-08-14",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_2-1-1-2022-08-14","aria-hidden":"true"},"#"),o(" 2.1.1 - 2022/08/14")],-1),ch=o("Added support for running User Builds with nested copybooks for COBOL. "),uh={href:"https://github.com/IBM/zopeneditor-about/issues/251",target:"_blank",rel:"noopener noreferrer"},_h=o("Issue 251"),ph=o("Fixed User Build issues with credential dialogs and storing credentials for remote include file resolution using z/OSMF or RSE API. ("),fh={href:"https://github.com/IBM/zopeneditor-about/issues/245",target:"_blank",rel:"noopener noreferrer"},gh=o("Issue 245"),mh=o(", "),bh={href:"https://github.com/IBM/zopeneditor-about/issues/255",target:"_blank",rel:"noopener noreferrer"},wh=o("Issue 255"),Ih=o(")"),yh=e("li",null,"Fixed User Build issues with credential dialogs and storing credentials for SSH commands when using z/OSMF.",-1),vh=o("Fixed User Build issues when attempting to build from workspaces with spaces in the file path. ("),xh={href:"https://github.com/IBM/zopeneditor-about/issues/252",target:"_blank",rel:"noopener noreferrer"},Sh=o("Issue 252"),Bh=o(")"),Ah=o("Fixed various issues when using ZAPP and User Build in a multi-root workspace. You can now use multi-root workspaces as long as you use a single ZAPP file and provide it together with the application-conf folder in the same workspace as your program. Include files such as copybooks can be in many other multi-root workspace folders. The ZAPP file needs to specify property groups with a workspace folder relative path even for include files located in other workspaces. User Build with user settings in multi-root workspaces is not supported. Please, switch to ZAPP files. See our "),Ch={href:"https://github.com/IBM/zopeneditor-sample",target:"_blank",rel:"noopener noreferrer"},Eh=o("Sample GitHub repository"),kh=i(" for more details and a examples for single-root workspaces, in the wazi-main branch as well as multi-root in the multiroot folder of the wazi-main branch. Also note, that for single as well as multi-root the value for the DBB buildScriptArgs parameter has changed for the --application parameter to be now just a relative path to the application-conf directory. So in most cases you can just use --application ., which makes it much easier as you do not have to provide the folder name of your workspace root in the ZAPP file anymore. Finally, the zopeneditor.userbuild.userSettings.localWorkspacePath user setting has been deprecated is not used anymore.",15),Oh=e("li",null,"Fixed an issue in the Z Open Editor output log not always reporting the correct Zowe profile management version in use.",-1),Lh=e("li",null,"Fixed issue in the COBOL Code Formatter producing incorrect Area B alignments for USING statements.",-1),Mh=e("h2",{id:"_2-1-0-2022-06-14",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_2-1-0-2022-06-14","aria-hidden":"true"},"#"),o(" 2.1.0 - 2022/06/14")],-1),zh=o("Added language support for COBOL v6.4, PL/I v6.1, and CICS v6.1 with updated syntax highlighting, outline view, real-time syntax checking, and other language related features. See our "),Ph={href:"https://ibm.github.io/zopeneditor-about/Docs/language_references.html",target:"_blank",rel:"noopener noreferrer"},Fh=o("documentation"),Rh=o(" for details. ("),Zh={href:"https://github.com/IBM/zopeneditor-about/issues/240",target:"_blank",rel:"noopener noreferrer"},Uh=o("Issue 240"),Th=o(")"),Dh=o("Added COBOL UTF-8-specific syntax elements in textmate grammar ("),Xh={href:"https://github.com/IBM/zopeneditor-about/issues/241",target:"_blank",rel:"noopener noreferrer"},Nh=o("Issue 241"),Hh=o(")"),Jh=o("Added an experimental COBOL code formatter that can be configured similar to Prettier with a yaml or json file. Find more details in our documentation ("),Vh={href:"https://github.com/IBM/zopeneditor-about/issues/31",target:"_blank",rel:"noopener noreferrer"},qh=o("Issue 31"),Wh=o(")"),Gh=e("li",null,"Updated HLASM Instructions to match the set that was shipped with IBM z16.",-1),jh=e("li",null,[o("Updated HLASM Macros to match the z/OS 2.5 SYS1.MACLIB. Switch the z/OS version back to 2.4 SYS1.MACLIB by using the user setting "),e("code",null,"zopeneditor.hlasm.zosMacrosVersion"),o(".")],-1),Yh=o("Added "),Qh=e("code",null,".macasm",-1),Kh=o(" and "),$h=e("code",null,".copyasm",-1),ec=o(" as default file extensions for HLASM. ("),oc={href:"https://github.com/IBM/zopeneditor-about/issues/220",target:"_blank",rel:"noopener noreferrer"},tc=o("Issue 220"),sc=o(")"),ic=o("Added "),nc=e("code",null,".bms",-1),rc=o(" as default file extensions for HLASM. ("),ac={href:"https://github.com/IBM/zopeneditor-about/issues/223",target:"_blank",rel:"noopener noreferrer"},lc=o("Issue 223"),dc=o(")"),hc=o("Fixed an error in the Problems View when a custom-defined problemMatcher was used when compiling HLASM code. ("),cc={href:"https://github.com/IBM/zopeneditor-about/issues/230",target:"_blank",rel:"noopener noreferrer"},uc=o("Issue 230"),_c=o(")"),pc=e("li",null,"Various fixes and refinements for HLASM syntax highlighting.",-1),fc=o("Added REXX include file support consistent with the other languages using Property Groups in ZAPP files. ("),gc={href:"https://github.com/IBM/zopeneditor-about/issues/172",target:"_blank",rel:"noopener noreferrer"},mc=o("Issue 172"),bc=o(")"),wc=o("Added a status bar item that displays the currently active Zowe profile used by Z Open Editor for remote include file resolution and IBM User Build. ("),Ic={href:"https://github.com/IBM/zopeneditor-about/issues/165",target:"_blank",rel:"noopener noreferrer"},yc=o("Issue 165"),vc=o(")"),xc=e("li",null,[o("Added support to filter the information displayed in the RSE CLI plugin command "),e("code",null,"zowe rse check jobs"),o(" that displays all active job address space information. This functionality is available in RSE API v1.0.9.")],-1),Sc=e("li",null,[o("Added support for use of passphrase in "),e("code",null,"change password"),o(" command with RSE API v1.0.9.")],-1),Bc=e("h2",{id:"_2-0-3-2022-05-20",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_2-0-3-2022-05-20","aria-hidden":"true"},"#"),o(" 2.0.3 - 2022/05/20")],-1),Ac=e("li",null,"Fixed a synchronization issue that when saving syntactically correct ZAPP files the editor sometimes would still report errors.",-1),Cc=o("Fixed an issue in User Build related to file upload operations in which Z Open Editor would not evaluate the .gitattributes file correctly, not following the Git standard for precedences. ("),Ec={href:"https://github.com/IBM/zopeneditor-about/issues/236",target:"_blank",rel:"noopener noreferrer"},kc=o("Issue 236"),Oc=o(")"),Lc=o("Updated how User Build parses .gitattributes files dealing with more file formats such as Windows CRLF files and added more logging for the encoding matches found or not found. ("),Mc={href:"https://github.com/IBM/zopeneditor-about/issues/235",target:"_blank",rel:"noopener noreferrer"},zc=o("Issue 235"),Pc=o(")"),Fc=o("Added support for using the "),Rc=e("code",null,"ZOWE_CLI_HOME",-1),Zc=o(" environment variable to specify an alternative location for global team configuration files to Zowe Explorer 2.0.2 and Z Open Editor. ("),Uc={href:"https://github.com/IBM/zopeneditor-about/issues/238",target:"_blank",rel:"noopener noreferrer"},Tc=o("Issue 238"),Dc=o(")"),Xc=o("Fixed various errors that prevented Zowe Explorer and Z Open Editor to run in Eclipse Che especially plugin containers with Nodejs 12. You can use these extensions now with secure credentials disabled as "),Nc={href:"https://ibm.github.io/zopeneditor-about/Docs/zowe_explorer_v2.html#eclipse-che",target:"_blank",rel:"noopener noreferrer"},Hc=o("documented here"),Jc=o("."),Vc=i('
       2.0.2 - 2022/04/25
      • Added full support for Zowe 2.0 in particular Zowe Explorer 2, Zowe CLI 7, Zowe API Mediation Layer 2. You can continue using your Zowe CLI 6.x profiles for backwards compatibility, but you must update Zowe Explorer to version 2 to do so. Review our Getting Started with Zowe 2.0 section in the Z Open Editor user documentation or the Zowe CLI documentation for how to migrate your 6.x profiles to the 7.x format.
      • Added support for auto-init of Team config files to the IBM RSE API Plugin for Zowe CLI. Use it when you have you RSE API host component registered with the API Mediation Layer.
      • Switched the minimal required version of Node JS for IBM RSE API Plugin for Zowe CLI to version 14 as version 12 is out of support now.
      • Added user setting zopeneditor.server.startupOptions for providing custom Java startup options for language servers. Can be used with tech support for troubleshooting.
       2.0.0 - 2022/03/15
      Z Open Editor is released as major version update to 2.0 to celebrate its availability in IBM Wazi Developer for Workspaces 2.0 that is now part of the IBM Z and Cloud Modernization Stack and fully supports running on OpenShift on Linux on Z. Note that because Zowe 2.0 was delayed to late April 2022, Z Open Editor has to be updated to support it once Zowe has been released. Other fixes and enhancements in this release:
      ',4),qc=o("Added missing DEBUG-ITEM variables in the COBOL language server. ("),Wc={href:"https://github.com/IBM/zopeneditor-about/issues/156",target:"_blank",rel:"noopener noreferrer"},Gc=o("Issue 156"),jc=o(")"),Yc=o("Added missing JNIENVPTR and JSON-STATUS variables in the COBOL TextMate grammar and the COBOL language server. ("),Qc={href:"https://github.com/IBM/zopeneditor-about/issues/156#issuecomment-912978046",target:"_blank",rel:"noopener noreferrer"},Kc=o("Issue 156"),$c=o(")"),eu=o("Fixed an issue in the COBOL language server not supporting a mixed case spelling of SQLCA and SQLDA. ("),ou={href:"https://github.com/IBM/zopeneditor-about/issues/208",target:"_blank",rel:"noopener noreferrer"},tu=o("Issue 208"),su=o(")"),iu=e("li",null,"Fixed an issue in the COBOL language server where the Rename Symbol feature was not renaming symbols that were spelled using a different character casing.",-1),nu=e("li",null,"Fixed an issue in the COBOL TextMate Grammar making the SCREEN keyword case insensitive.",-1),ru=o("Fixed an issue in the COBOL language server where parsing failed because of period in column 72 and standard sequence numbering present in the program. ("),au={href:"https://github.com/IBM/zopeneditor-about/issues/202",target:"_blank",rel:"noopener noreferrer"},lu=o("Issue 202"),du=o(")"),hu=o("Fixed an issue in the COBOL Language Sever where parsing failed with invalid error message in COPY REPLACING statements. ("),cu={href:"https://github.com/IBM/zopeneditor-about/issues/181",target:"_blank",rel:"noopener noreferrer"},uu=o("Issue 181"),_u=o(")"),pu=e("li",null,"Performance and reliability improvements for the COBOL and PL/I language servers by implementing cancellation support for requests that are no longer valid as well as optimizing handling of document-link requests for include files.",-1),fu=e("li",null,"Added new options to the truncation warning dialog for COBOL, PL/I, HLASM, REXX, and JCL files in Z Open Editor. Also, if only whitespaces are truncated the editor will not prompt anymore, it will just remove them automatically.",-1),gu=o("Fixed an issue in the PL/I language server where hover content for include files were not rendering in the correct format. ("),mu={href:"https://github.com/IBM/zopeneditor-about/issues/211",target:"_blank",rel:"noopener noreferrer"},bu=o("Issue 211"),wu=o(")"),Iu=e("li",null,"Fixed an issue in the HLASM language server where NullPointerException were logged while rendering hovers after a document change.",-1),yu=o("Fixed an issue where HLASM syntax highlighting was not correctly recognizing sequence numbers at the end of lines ("),vu={href:"https://github.com/IBM/zopeneditor-about/issues/192",target:"_blank",rel:"noopener noreferrer"},xu=o("Issue 192"),Su=o(")."),Bu=e("li",null,"Fixed an issue in the REXX language server where a trailing comma in a function parameter resulted in a syntax error.",-1),Au=e("li",null,"Improved the REXX language server performance and stability when editing large files.",-1),Cu=e("li",null,'Z Open Editor and Zowe Explorer now share the profiles loaded into memory via the Zowe Explorer Extensibility API. Now if you make changes to a profile in Zowe Explorer or use the Reload button to load changes from disk done via CLI, the changes will be immediately visible to Z Open Editor without the need to run "Reload Zowe profiles" from the command palette. This command now performs the same operation as clicking the Zowe Explorer Refresh button.',-1),Eu=o("Made the Zowe connection test in Z Open Editor more robust and fixed the issue of tests timing out for slow connections. ("),ku={href:"https://github.com/IBM/zopeneditor-about/issues/197",target:"_blank",rel:"noopener noreferrer"},Ou=o("Issue 197"),Lu=o(")"),Mu=e("li",null,'Fixed an issue preventing submission of JCL in Zowe Explorer via command palette option "Zowe Explorer: Submit JCL" using RSE API CLI Zowe profiles.',-1),zu=e("li",null,"Fixed an issue with token and base Zowe CLI profiles support for MVS connection tests for remote file resolving.",-1),Pu=e("li",null,"Added RSE API Zowe profile login and logout support for JSON Web Token authentication with the RSE API through Zowe Explorer.",-1),Fu=e("li",null,[o("Improved working with interactive TSO commands for RSE API Zowe profiles by adding the TSO command tag "),e("code",null,"shell-id"),o(", that can be used with RSE API server v1.0.8.")],-1),Ru=e("li",null,"User Build now works with Zowe CLI profiles that do not store credentials. User will be prompted to provide them when the build starts.",-1),Zu=o("Adopted the latest version of "),Uu={href:"https://github.com/IBM/dbb-zappbuild",target:"_blank",rel:"noopener noreferrer"},Tu=o("dbb-zappbuild"),Du=o(" for User Build that now considers file tags for processing. The JSON dependency file will now be uploaded as a UTF-8 file. If you are using an older version of dbb-zappbuild, please update with the latest changes from its main branch on GitHub."),Xu=e("li",null,[o("Fixed an issue that would show the command "),e("code",null,"IBM User Build: Run IBM User Build"),o(" for files with unsupported languages in the command palette.")],-1),Nu=e("li",null,"Fixed an issue that prevented recognizing ZAPP files running in Eclipse Che when workspaces folders were added or removed.",-1),Hu=e("li",null,"Reviewed and revised multiple user interface strings and dialogs.",-1),Ju=o("Updated code samples in "),Vu={href:"https://github.com/IBM/zopeneditor-sample/tree/wazi-main",target:"_blank",rel:"noopener noreferrer"},qu=o("https://github.com/IBM/zopeneditor-sample/tree/wazi-main"),Wu=o(" with Ansible playbooks and host variables for IBM Wazi Sandbox and the IBM Wazi as a Service tutorials."),Gu=e("h2",{id:"_1-4-1-2021-11-19",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-4-1-2021-11-19","aria-hidden":"true"},"#"),o(" 1.4.1 - 2021/11/19")],-1),ju=o("Fixed an issue with COBOL syntax highlighting of reference modifications ("),Yu={href:"https://github.com/IBM/zopeneditor-about/issues/177",target:"_blank",rel:"noopener noreferrer"},Qu=o("Issue 177"),Ku=o(")"),$u=o("Fixed the VS Code Toggle Line Comment (Cmd-/ or Ctrl-/) command for COBOL. You can now use it with the cursor being placed anywhere in the line as well as select a whole block of code and set or remove the comment symbol as a toggle. ("),e_={href:"https://github.com/IBM/zopeneditor-about/issues/157",target:"_blank",rel:"noopener noreferrer"},o_=o("Issue 157"),t_=o(")"),s_=o("Fixed several issues with HLASM syntax highlighting related to continuation lines, macro definitions, and substitution characters. ("),i_={href:"https://github.com/IBM/zopeneditor-about/issues/118",target:"_blank",rel:"noopener noreferrer"},n_=o("Issue 118"),r_=o(", "),a_={href:"https://github.com/IBM/zopeneditor-about/issues/185",target:"_blank",rel:"noopener noreferrer"},l_=o("Issue 185"),d_=o("). See our "),h_={href:"https://ibm.github.io/zopeneditor-about/Docs/knownissues.html",target:"_blank",rel:"noopener noreferrer"},c_=o("Known Issues"),u_=o(" page for problems not solved, yet."),__=o("Fixed various inconsistencies with the HLASM outline view. It will now show the first occurrences of CSECTs, DSECTs, MACROs, Branch Targets, and Labels. ("),p_={href:"https://github.com/IBM/zopeneditor-about/issues/148",target:"_blank",rel:"noopener noreferrer"},f_=o("Issue 148"),g_=o("). See our "),m_={href:"https://ibm.github.io/zopeneditor-about/Docs/knownissues.html",target:"_blank",rel:"noopener noreferrer"},b_=o("Known Issues"),w_=o(" page for problems not solved, yet."),I_=o("Enhanced HLASM outline view to now display all labels. See "),y_={href:"https://ibm.github.io/zopeneditor-about/Docs/customizing_the_outline_view.html",target:"_blank",rel:"noopener noreferrer"},v_=o("Customizing the outline view"),x_=o(" to change what is included in the outline view."),S_=e("li",null,"Added support to use all REXX keywords as variables, excluding the 'END' keyword as well as improved the readability of keyword-related syntax error messages.",-1),B_=o("Fixed an issue in which trying to load remote include files from MVS using an invalid Zowe CLI Profile password could lock user accounts due to too many failed attempts. Z Open Editor will now prompt for a new password to update the profile or allow canceling all requests. This fix also adds support for using Zowe CLI profiles that do not store credentials and you will be prompted when required. ("),A_={href:"https://github.com/IBM/zopeneditor-about/issues/142",target:"_blank",rel:"noopener noreferrer"},C_=o("Issue 142"),E_=o(")"),k_=o("Fixed an issue that prevented switching from Z Open Editor language servers to other languages. ("),O_={href:"https://github.com/IBM/zopeneditor-about/issues/164",target:"_blank",rel:"noopener noreferrer"},L_=o("Issue 164"),M_=o(")"),z_=e("li",null,"Fixed a regression in which a ZAPP file was not found when using it in an IBM RSE API for Zowe CLI command parameter or in Z Open Editor when specifying a file with zopeneditor.zowe.defaultRseConversionMappingsFile that was not in the current workspace.",-1),P_=e("li",null,"Fixed an issue with User Build where dependencies would not upload again after making a change inside VS Code settings or ZAPP file settings.",-1),F_=e("li",null,"Fixed an issue with User Build where remote dependencies were being uploaded on Windows.",-1),R_=e("li",null,"Enhanced User Build messages to be more informative and actionable.",-1),Z_=e("li",null,"Fixed security related logging issue.",-1),U_=i('
       1.4.0 - 2021/10/29
      • You can now use User Build without SSH when using IBM RSE API for Zowe CLI profiles. SSH Zowe CLI profiles are now required by z/OSMF only.
      • User Build speed is increased by sending additional dependency and metadata information to IBM Dependency Based Build on z/OS. Check the documentation for new dbb-zappbuild build script arguments.
      • When you save user or workspace settings, Z Open Editor will recognize and reload all Zowe CLI profiles, which is particularly useful when you add new profile names to the zopeneditor.zowe setting.
      • Support for ZAPP files with Z Open Editor is now also available when running in Eclipse Che, Red Hat CodeReady Workspaces, and IBM Wazi Developer for Workspaces.
      • Startup performance is faster with a smaller memory footprint due to significantly reduced language server sizes.
      • You can use the IBM Debug for z/OS High Level Assembler debug listing files with the language ID hlasmlst and the default file extension langx.
      • Fixed an issue in which a newly created ZAPP file was not recognized until the editor restarted.
      • Enhanced some UI strings for effectiveness including menus and Preferences names and descriptions.
      • New commands are added to IBM RSE API for Zowe CLI: 
        • zowe rse create data-set --like: Allocates a new data set with the same attributes as an existing data set specified by the --like option in IBM RSE API for Zowe CLI. The allocate-like functionality can now also be used with RSE profiles in Zowe Explorer. To use this feature, RSE API server 1.0.7 or later versions are required.
        • zowe rse check system-address-space: Displays all active system address space information in RSE CLI plug-in. To use this feature, RSE API 1.0.5 or later versions, and IBM Explorer for z/OS 3.2.0.16 or later versions are required.
        • zowe rse check job-address-space: Displays all active job address space information in RSE CLI plug-in. To use this feature, RSE API 1.0.5 or later versions and IBM Explorer for z/OS 3.2.0.16 or later versions are required.
       1.2.6 - 2021/08/19
      ',3),T_=o("Fixed an issue with PL/I compiler options for margins not being interpreted correctly in the editor. ("),D_={href:"https://github.com/IBM/zopeneditor-about/issues/135",target:"_blank",rel:"noopener noreferrer"},X_=o("Issue 135"),N_=o(")"),H_=o("Fixed an issue that encoded special characters incorrectly in include file hovers for all languages. ("),J_={href:"https://github.com/IBM/zopeneditor-about/issues/128",target:"_blank",rel:"noopener noreferrer"},V_=o("Issue 128"),q_=o(")"),W_=o("Fixed issues with HLASM code completion not appearing correctly in continuation and empty lines. ("),G_={href:"https://github.com/IBM/zopeneditor-about/issues/118",target:"_blank",rel:"noopener noreferrer"},j_=o("Issue 118"),Y_=o(")"),Q_=i("
    • Various fixes and improvements for REXX: 
      • Fixed issues with handling multi-line strings correctly for REXX.
      • Made code completion in REXX case-sensitive so that it preserves the casing style the user was using before initiating completion requests with Ctrl+Space.
      • Added an editor ruler at column 80 in REXX files. All editor rulers are customizable through the settings.
      • Added truncation warnings for characters after column 80 in REXX files. The column number is customizable through the settings.
      • Various REXX refinements that improve stability and performance of parsing and error messages.
    • Fixed an issue in IBM RSE API for Zowe CLI that prevented the use of the correct encoding for file uploads to USS, which also impacted uploads via Zowe Explorer using an RSE API profile. This fix requires Zowe Explorer 1.18.0 or newer.
    • Fixed an issue in User Build that prevented the use of the correct encoding as defined in .gitattributes to files uploaded via z/OSMF or RSE API profiles.
      • ",3),K_=o("Addressed the user request to allow the "),$_=e("code",null,"zopeneditor.zowe",-1),ep=o(" settings to be scoped for workspace settings. This will be useful for development teams who standardize the names of their Zowe CLI profiles for their projects and use them for build automation. ("),op={href:"https://github.com/IBM/zopeneditor-about/issues/143",target:"_blank",rel:"noopener noreferrer"},tp=o("Issue 143"),sp=o(")"),ip=e("li",null,[o("Adopted the new Zowe Explorer "),e("code",null,"zowe.files.temporaryDownloadsFolder.cleanup"),o(' setting to support the use of multiple VS Code windows showing the same files opened via Zowe Explorer, in order to see different parts of the same program on two different screens. Note that disabling the cleanup will result in files downloaded from z/OS not being removed when the editor is closed or restarted, so when you open a file via Zowe Explorer you may be viewing an outdated local version. Use the right-click "Pull from Mainframe" command to ensure you are working with the latest files.')],-1),np=e("li",null,"Adopted new Zowe Explorer APIs that require Zowe Explorer 1.15.0 or newer to be installed. This release has been tested with Zowe Explorer 1.18.0.",-1),rp=e("h2",{id:"_1-2-5-2021-06-18",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-2-5-2021-06-18","aria-hidden":"true"},"#"),o(" 1.2.5 - 2021/06/18")],-1),ap=o("Refined COBOL Renumber and Unnumber support making it configurable to work with columns 1-6 or 73-80 or both. If content other than numberic values is already present in these locations in a specific row then it will not update that location to preserve the content. ("),lp={href:"https://github.com/IBM/zopeneditor-about/issues/8",target:"_blank",rel:"noopener noreferrer"},dp=o("Issue 8"),hp=o(")"),cp=o("Fixed syntax highlighting for HLASM beyond column 16. There is still an issue with code completion that well be addressed in a later release. ("),up={href:"https://github.com/IBM/zopeneditor-about/issues/118",target:"_blank",rel:"noopener noreferrer"},_p=o("Issue 118"),pp=o(")"),fp=e("li",null,"Improved performance and reliability of downloading larger numbers of include files such as SYS1.MACLIB macros for the HLAMS editor hovers.",-1),gp=o("Removed the performance warning dialog for property groups and replaced it with log messages ("),mp={href:"https://github.com/IBM/zopeneditor-about/issues/115",target:"_blank",rel:"noopener noreferrer"},bp=o("Issue 15"),wp=o(")"),Ip=e("li",null,"User Build now writes its output into a separate log file for users to share and analyze.",-1),yp=e("li",null,"Adoption of new Zowe Explorer API ICommand to allow issuing of TSO commands using RSE profiles via Zowe Explorer 1.14.0 and higher.",-1),vp=e("li",null,[o("RSE CLI plug-in updates: "),e("ul",null,[e("li",null,[o("RSE CLI plug-in now prompts user for credentials for RSE profiles without user and password, during "),e("code",null,"zowe rse auth login"),o(" command to obtain JWT token, and if RSE API token is expired to obtain new token.")]),e("li",null,"Fixed a regression that broke uploading a file as a sequential data set.")])],-1),xp=e("h2",{id:"_1-2-1-2021-04-21",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-2-1-2021-04-21","aria-hidden":"true"},"#"),o(" 1.2.1 - 2021/04/21")],-1),Sp=i("
    • Made various improvements to our REXX language server and fixed defects: 
      • Added support for nested comments in REXX
      • Added support for keyword instructions as variables in REXX (excludes DO, IF, PARSE, SELECT, TRACE).
      • Fixed a find references bug in REXX where variables and functions with the same name matched
      • Fixed a find references bug in REXX where keywords could be used to find references
      • Refined the hover content and code completion detail in REXX to make the information more concise
      • Updated the hover content in IBM Documentation to point to the new IBM Documentation pages for the z/OS 2.4.0 TSO/E REXX Reference.
      • Standardized the syntax highlighting in REXX to color all keywords the same
      • Fixed a syntax highlighting bug in REXX where "value" following "address" was not displaying in color as a keyword
      • Fixed a syntax highlighting bug in REXX where the routine name following "call" was not displaying in color as a function
    • Reviewed and updated all output and log messages for the IBM RSE API Plug-in for Zowe CLI to ensure consistency. Locate the log file in ~/.zowe/zowe/logs/zowe.log.
      • ",2),Bp=o("Updated RSE API support for Zowe CLI "),Ap={href:"https://docs.zowe.org/stable/user-guide/cli-usingcli.html#base-profiles",target:"_blank",rel:"noopener noreferrer"},Cp=o("base profiles"),Ep=o(" for the "),kp={href:"https://docs.zowe.org/stable/user-guide/api-mediation/discovery-service-configuration.html#api-ml-configuration",target:"_blank",rel:"noopener noreferrer"},Op=o("Zowe API Mediation Layer (APIML)"),Lp=o(" Single Sign On (SSO) for User Build and using the RSE API behind the Zowe APIML. Refer to this "),Mp={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/joe-winchester1/2021/04/14/using-the-ibm-remote-system-explorer-apis-with-the",target:"_blank",rel:"noopener noreferrer"},zp=o("new blog post"),Pp=o(" for an overview about how to use RSE API with the Zowe API Mediation Layer."),Fp=e("h2",{id:"_1-2-0-2021-03-19",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-2-0-2021-03-19","aria-hidden":"true"},"#"),o(" 1.2.0 - 2021/03/19")],-1),Rp=o("REXX language server: in this release we added language support for TSO/E REXX for z/OS. This first version includes syntax highlighting, syntax errors, code completion, find references, outline view, and rich documentation hover features. See our docs for all the details. ("),Zp={href:"https://github.com/IBM/zopeneditor-about/issues/15",target:"_blank",rel:"noopener noreferrer"},Up=o("Issue 14"),Tp=o(")"),Dp=e("li",null,[o("Added full support for encoding conversions to/from UTF-8 to/from international EBCDIC code pages for all our z/OS MVS interactions that use RSE API "),e("ul",null,[e("li",null,"Introduced a new mapping file concept to ZAPP as well as standalone JSON files that allow specifying mappings to groups or individual data sets or even members."),e("li",null,"Added support for all RSE API CLI commands with new parameters as well as the ability to read mapping files that read and write to MVS."),e("li",null,"All Z Open Editor remote MVS read operations using RSE API to find include files now can use mappings defined in ZAPP or user-local mappings files."),e("li",null,"The Zowe Explorer integration with RSE API can also be configured to use mappings files for read and write operations of data set members.")])],-1),Xp=e("li",null,"Added EBCDIC conversion mappings for z/OS USS to User Build. Users can provide a standard .gitattributes file that specifies the encoding the program files should be converted to when uploaded to z/OS USS for a build.",-1),Np=o("Added context menus for COBOL with the ability to remove as well as renumber sequence numbers. ("),Hp={href:"https://github.com/IBM/zopeneditor-about/issues/8",target:"_blank",rel:"noopener noreferrer"},Jp=o("Issue 8"),Vp=o(")"),qp=e("li",null,[o("Made include file resolution case-insensitive by default to support users with lowercase filenames and property group path names on local case-sensitive file systems such as Linux. As this can lead potentially to ambiguity problems we also added a new user setting called "),e("code",null,"zopeneditor.enforceCaseSensitiveIncludeFileNames"),o(" to enable case sensitive matching, even on case-insensitive operation systems such as Windows.")],-1),Wp=e("li",null,[o("The command "),e("code",null,"Reload Zowe Profiles"),o(" that you can use when you changed your Zowe profiles, which was mainly introduced for User Build, now also restarts the language servers and retries loading any remote MVS include files with the updated profile information.")],-1),Gp=e("li",null,"Added a new Welcome page for new users that interactively checks for prerequisites and gives tips for getting started.",-1),jp=o("Added support for APIML SSO for remote include file resolution such as COBOL Copybooks located on MVS. ("),Yp={href:"https://github.com/IBM/zopeneditor-about/issues/107",target:"_blank",rel:"noopener noreferrer"},Qp=o("Issue 107"),Kp=o(")"),$p=o("Fixed an issue in which invalid Zowe CLI profile configurations could cause Z Open Editor to not activate. We now show error messages and the editor is still usable. ("),ef={href:"https://github.com/IBM/zopeneditor-about/issues/110",target:"_blank",rel:"noopener noreferrer"},of=o("Issue 110"),tf=o(")"),sf=e("h2",{id:"_1-1-3-2020-12-12",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-1-3-2020-12-12","aria-hidden":"true"},"#"),o(" 1.1.3 - 2020/12/12")],-1),nf=o("Fixed regression when resolving copybooks/include files with property groups that have multiple syslib/library entries. ("),rf={href:"https://github.com/IBM/zopeneditor-about/issues/105",target:"_blank",rel:"noopener noreferrer"},af=o("Issue 105"),lf=o(")"),df=e("h2",{id:"_1-1-2-2020-12-09",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-1-2-2020-12-09","aria-hidden":"true"},"#"),o(" 1.1.2 - 2020/12/09")],-1),hf=e("li",null,[o("Added support for "),e("code",null,"SYS1.MACLIB"),o(" macros to HLASM for code completion. If you have a valid Zowe Explorer connection, it will even retrieve the macro definition automatically and show you in rich hovers when you typed or completed the macro name. Ensure that you enable this feature in user settings before using it.")],-1),cf=e("li",null,"Improved the way that Z Open Editor is looking for your Java Runtime or SDK. Review our updated documentation for the search order in which it tries to locate Java, as well as how you can override it with user settings. Added official support for Java Runtimes, and an SDK is not required anymore.",-1),uf=o("RSE CLI plug-in has added an encoding field that you can specify when creating or editing a Zowe RSE API CLI profile. You can use this field with newly added encoding tags for the commands of uploading and downloading MVS and USS files. Resolving copybooks will now use this encoding tag as well for RSE API and z/OSMF connections. ("),_f={href:"https://github.com/IBM/zopeneditor-about/issues/82",target:"_blank",rel:"noopener noreferrer"},pf=o("Issue 82"),ff=o(")"),gf=o("RSE CLI plug-in now supports MVS binary downloads. ("),mf={href:"https://github.com/IBM/zopeneditor-about/issues/58",target:"_blank",rel:"noopener noreferrer"},bf=o("Issue 58"),wf=o(")"),If=o("To update to RSE CLI plug-in 1.1.2, follow "),yf={href:"https://ibm.github.io/zopeneditor-about/Docs/setup_integration.html#updating-the-ibm-rse-api-plug-in-for-zowe-cli",target:"_blank",rel:"noopener noreferrer"},vf=o("the instructions here"),xf=o(" for the optional migration."),Sf=e("h2",{id:"_1-1-1-2020-11-6",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-1-1-2020-11-6","aria-hidden":"true"},"#"),o(" 1.1.1 - 2020/11/6")],-1),Bf=o("Added full support for "),Af={href:"https://docs.zowe.org/stable/user-guide/cli-usingcli.html#base-profiles",target:"_blank",rel:"noopener noreferrer"},Cf=o("Zowe CLI Base Profiles"),Ef=o(" with "),kf={href:"https://ibm.github.io/zopeneditor-about/Blog/rse-october-110.html#use-json-web-tokens-jwt-for-authentication-with-the-host",target:"_blank",rel:"noopener noreferrer"},Of=o("RSE API JWT tokens"),Lf=o(" for CLI commands and well as Zowe Explorer 1.10.1 or newer. To use it also update the IBM RSE API Plugin for Zowe CLI 1.1.1 and follow "),Mf={href:"https://ibm.github.io/zopeneditor-about/Docs/setup_integration.html#updating-the-ibm-rse-api-plug-in-for-zowe-cli",target:"_blank",rel:"noopener noreferrer"},zf=o("the instructions here"),Pf=o(" for the optional migration."),Ff=o("Fixed issue for specifying the right PL/I margin with property groups compile option settings. Note, that the left margin must be at least 2 at the moment. ("),Rf={href:"https://github.com/IBM/zopeneditor-about/issues/87",target:"_blank",rel:"noopener noreferrer"},Zf=o("Issue 72"),Uf=o(")"),Tf=o("Added "),Df={href:"https://ibm.github.io/zopeneditor-about/Docs/setting_compiler_options.html",target:"_blank",rel:"noopener noreferrer"},Xf=o("new documentation"),Nf=o(" for the currently supported property group compile options."),Hf=o("Fixed issue with using "),Jf=e("code",null,"$",-1),Vf=o(", "),qf=e("code",null,"#",-1),Wf=o(", or "),Gf=e("code",null,"@",-1),jf=o(" in HLASM and PL/I include file names. COBOL will be addressed in a future release. ("),Yf={href:"https://github.com/IBM/zopeneditor-about/issues/86",target:"_blank",rel:"noopener noreferrer"},Qf=o("Issue 86"),Kf=o(")"),$f=e("h2",{id:"_1-1-0-2020-10-23",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-1-0-2020-10-23","aria-hidden":"true"},"#"),o(" 1.1.0 - 2020/10/23")],-1),eg=e("li",null,"ZAPP (Z APPlication) file support. Instead of mixing the configuration of your application with VS Code Preferences you can now specify property groups and IBM User Build configurations in a new simple yaml (or json) file located in your workspace that you can share with your team in Git. See our docs for a tutorial.",-1),og=o("Added support for the Zowe CLI Secure Credentials Plugins for all Z Open Editor operations such as resolving include files or running user build ("),tg={href:"https://github.com/IBM/zopeneditor-about/issues/66",target:"_blank",rel:"noopener noreferrer"},sg=o("Issue 66"),ig=o(")"),ng=o("Property Groups can now be scoped to one specific language making include file resolution more efficient as well as to support compiler options. ("),rg={href:"https://github.com/IBM/zopeneditor-about/issues/72",target:"_blank",rel:"noopener noreferrer"},ag=o("Issue 72"),lg=o(")."),dg=o("Added the ability to provide language-specific compiler options such as "),hg=e("code",null,"OR('!')",-1),cg=o(" to property groups to configure the editor ("),ug={href:"https://github.com/IBM/zopeneditor-about/issues/17",target:"_blank",rel:"noopener noreferrer"},_g=o("Issue 17"),pg=o(", "),fg={href:"https://github.com/IBM/zopeneditor-about/issues/61",target:"_blank",rel:"noopener noreferrer"},gg=o("Issue 61"),mg=o(")."),bg=o("Include file resolution for COBOL and PL/I ignores SQLCA and SQLDA ("),wg={href:"https://github.com/IBM/zopeneditor-about/issues/71",target:"_blank",rel:"noopener noreferrer"},Ig=o("Issue 71"),yg=o(")."),vg=o("Fixed issues with COBOL 6.3 support such as "),xg=e("code",null,">>if >>else >>end-if",-1),Sg=o(" ("),Bg={href:"https://github.com/IBM/zopeneditor-about/issues/65",target:"_blank",rel:"noopener noreferrer"},Ag=o("Issue 65"),Cg=o(")."),Eg=e("li",null,"The logger now provides more configuration information that will help in your interactions with tech support.",-1),kg=e("li",null,"Fixed issues managing Zowe Explorer favorites when using RSE API.",-1),Og=e("li",null,"Revised profile validation in Zowe Explorer when using RSE API.",-1),Lg=e("p",null,"We now include the IBM User Build VS Code Extension in IBM Z Open Editor. Changes since the 1.0.0 release:",-1),Mg=e("ul",null,[e("li",null,"In addition to COBOL we added support for building PL/I and HLASM programs with IBM Dependency-Based Build."),e("li",null,"Fixed an issue with corrupted DBB log files when downloaded from USS."),e("li",null,"User Build menus no longer appear for remote MVS or USS files opened via Zowe Explorer to avoid confusion about what can be built and what cannot."),e("li",null,"Added more detailed log messages in the IBM User Build Output window, such as the full ssh commands executed, as a summary of all the user and workspace settings being used for a build and more. The output will list all required and optional settings and their values before the user build script is executed. If any required settings are missing, user build will stop execution explaining which setting caused the problem."),e("li",null,"User Build can now run with files that contain spaces in their paths.")],-1),zg=e("h2",{id:"_1-0-3-2020-08-07",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-0-3-2020-08-07","aria-hidden":"true"},"#"),o(" 1.0.3 - 2020/08/07")],-1),Pg=o("Added support for specifying custom include file extensions. You can now use the IBM Z Open Editor Preferences page to add and remove the file extensions to be used when searching for local include files such as COBOL copybooks. Also consistently added the Data Sets settings for remote include files to the visual editor allowing users to remove the mappings they do not want mapped in the files.association setting ("),Fg={href:"https://github.com/IBM/zopeneditor-about/issues/16",target:"_blank",rel:"noopener noreferrer"},Rg=o("Issue 16"),Zg=o(")."),Ug=e("li",null,"Added branch targets to the HLASM Outline view.",-1),Tg=o('Fixed COBOL syntax highlighting that uses a "/" character for comments ('),Dg={href:"https://github.com/IBM/zopeneditor-about/issues/60",target:"_blank",rel:"noopener noreferrer"},Xg=o("Issue 60"),Ng=o(")."),Hg=o('Fixed HLASM syntax highlighting for macros starting with a "$" character ('),Jg={href:"https://github.com/IBM/zopeneditor-about/issues/69",target:"_blank",rel:"noopener noreferrer"},Vg=o("Issue 69"),qg=o(")."),Wg=o("Added a support for using the "),Gg=e("code",null,"java.home",-1),jg=o(" user setting for developers that install VS Code with the "),Yg={href:"https://code.visualstudio.com/docs/java/java-tutorial#_setting-up-visual-studio-code-for-java-development",target:"_blank",rel:"noopener noreferrer"},Qg=o("Microsoft Installer of VS Code for Java developer"),Kg=o(" or the Java Extension Pack."),$g=e("li",null,"Added a Zowe Profile validation routine that is called when adding and using RSE API profiles with Zowe Explorer 1.7 or newer.",-1),em=e("h2",{id:"_1-0-2-2020-06-30",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-0-2-2020-06-30","aria-hidden":"true"},"#"),o(" 1.0.2 - 2020/06/30")],-1),om=e("ul",null,[e("li",null,"Merged v0.5.2 with v1.0.1 to publish v1.0.2 to the VS Code Marketplace that now includes the language server for IBM High-Level Assembler (HLASM) for z/OS 2.4."),e("li",null,"Reorganized the language server packaging to reduce the size of the extension to less than half than it was before.")],-1),tm=e("h2",{id:"_1-0-1-0-5-2-2020-06-23",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-0-1-0-5-2-2020-06-23","aria-hidden":"true"},"#"),o(" 1.0.1/0.5.2 - 2020/06/23")],-1),sm=o("Fixed false positives in Java compatibility check that prevented newer Java SDK versions than 8 to be used. ("),im={href:"https://github.com/IBM/zopeneditor-about/issues/57",target:"_blank",rel:"noopener noreferrer"},nm=o("Issue 57"),rm=o(")"),am=e("h2",{id:"_1-0-0-2020-06-12",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-0-0-2020-06-12","aria-hidden":"true"},"#"),o(" 1.0.0 - 2020/06/12")],-1),lm=e("li",null,"This is our v1.0 release for which you will be able to purchase technical support from IBM.",-1),dm=e("li",null,"Added a language server for IBM High-Level Assembler (HLASM) for z/OS 2.4.",-1),hm=o("Currently only available here, because of VS Code Marketplace size restrictions: "),cm={href:"https://ibm.github.io/mainframe-downloads/downloads.html",target:"_blank",rel:"noopener noreferrer"},um=o("https://ibm.github.io/mainframe-downloads/downloads.html"),_m=e("h2",{id:"_0-5-0-2020-06-12",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_0-5-0-2020-06-12","aria-hidden":"true"},"#"),o(" 0.5.0 - 2020/06/12")],-1),pm=e("li",null,"Added syntax error checking for COBOL Copybooks.",-1),fm=e("li",null,"Added support for CICS 5.6 syntax.",-1),gm=e("li",null,"Rewrote the algorithm for searching for remote include files using Zowe CLI profiles.",-1),mm=e("li",null,"Added user settings for specifying which Zowe CLI profile to use for finding remote include files on MVS in case you use multiple z/OSMF or RSE API CLI profiles.",-1),bm=e("li",null,"Added Logger to analyze issues. Switch it on in the IBM Z Open Editor VS Code Preferences under User Settings.",-1),wm=o("Fixed bug with Unreachable Code Detection in COBOL EXECL SQL statements and switched default of the "),Im=e("code",null,'"zopeneditor.cobol.enableUnreachableCodeWarnings"',-1),ym=o(" Preferences setting back to true. ("),vm={href:"https://github.com/IBM/zopeneditor-about/issues/18",target:"_blank",rel:"noopener noreferrer"},xm=o("Issue 18"),Sm=o(")"),Bm=e("li",null,"Updated LSP4J language servers to baseline v0.9.0 and VS Code language clients to v6.1.3.",-1),Am=e("li",null,"Improved LSP startup times.",-1),Cm=e("li",null,"Added more Java runtime checks to ensure you are using a valid Java SDK with the Z Open Editor extension.",-1),Em=e("li",null,"Various enhancements and fixes for RSE API support such as Get JCL from the Zowe Explorer JES view as well as Migrate/Recall from the Zowe Explorer MVS view.",-1),km=o("Fixed rare race condition when starting language servers. ("),Om={href:"https://github.com/IBM/zopeneditor-about/issues/45",target:"_blank",rel:"noopener noreferrer"},Lm=o("Issue 45"),Mm=o(")"),zm=e("li",null,"Various stability fixes and refinements.",-1),Pm=e("h2",{id:"_0-4-9-2020-04-23",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_0-4-9-2020-04-23","aria-hidden":"true"},"#"),o(" 0.4.9 - 2020/04/23")],-1),Fm=e("ul",null,[e("li",null,"Fixed an issue when using RSE for the Zowe Explorer JES view."),e("li",null,"Fixed errors messages users saw when creating z/OSMF profiles in Zowe Explorer when Zowe CLI and/or the IBM RSE API Plugin for Zowe CLI was not installed.")],-1),Rm=e("h2",{id:"_0-4-7-2020-03-27",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_0-4-7-2020-03-27","aria-hidden":"true"},"#"),o(" 0.4.7 - 2020/03/27")],-1),Zm=o("Added Beta-level support for the new Remote System Explorer API (RSEAPI) REST servers that can be used as an alternative to z/OSMF for remote file operations as well as Zowe Explorer visual explorer views. If you run RSE already for IBM Developer for Z or IBM z/OS Explorer you can simply update. Go to "),Um={href:"https://ibm.github.io/zopeneditor-about",target:"_blank",rel:"noopener noreferrer"},Tm=o("https://ibm.github.io/zopeneditor-about"),Dm=o(" for more details."),Xm=e("li",null,"Reduced the memory consumption of the extension by starting language servers only if a program in a specifc language is opened for the first time. This will avoid that you are wasting valuable PC memory for languages that you do not use. In addition we added two optional commands that you can run to pause the COBOL or PL/I language server once you finished with one language and want to free up its memory. When you open a program of that language again the language server will restart.",-1),Nm=e("li",null,"Added code actions that provide suggestions for resolving COBOL copybooks and PL/I include files by linking to Online Help pages.",-1),Hm=e("li",null,"Removed MQ code templates for now as we ran into some language compatibility issues.",-1),Jm=i('
       0.4.5 - 2020/01/07
      • Added an additional 27 code snippets for MQ development with COBOL and 27 for MQ with PL/I.
       0.4.3 - 2019/12/18
      • Added more code snippets for COBOL, PL/I and JCL, which brings it to a total of 186. For COBOL we now provide 27 General COBOL language support snippets, 12 Embedded SQL snippets, 29 for CICS, 12 for IMS, and 8 for VSAM. Similarly, we provide for PL/I 12 General PL/I language support snippets, 29 CICS, 11 IMS, and 7 VSAM. Finally, we have 27 code snippets for JCL.
       0.4.1 - 2019/11/21
      ',5),Vm=e("li",null,"Language server updates to support IBM Enterprise COBOL v6.3 and PL/I v5.3.",-1),qm=o("Added all new sets of IBM field contributed code snippets for COBOL embedded SQL and CICS, PL/I embedded SQL, and various new JCL snippets. This is just the beginning of us curating a larger portfolio of high-value code snippets and incrementally releasing these in the coming months. Keep and eye out and "),Wm={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},Gm=o("let us know what you think of these snippets"),jm=o("."),Ym=e("li",null,"Added an import command for loading Code Snippets exported by the IBM Developer from z/OS. Do you have your own set of code snippets that you managed in the Snippets view in IDz? You can now export and import these into Z Open Editor.",-1),Qm=o("Switched off COBOL Unreachable Code warnings by default as there are cases in which it can provide false positives ("),Km={href:"https://ibm.github.io/zopeneditor-about/Docs/knownissues.html#limitations-of-cobol-program-files",target:"_blank",rel:"noopener noreferrer"},$m=o("see here"),e1=o(" for details). If you can accept the risk of a few false reports then you can enable it again by using the "),o1=e("code",null,'"zopeneditor.cobol.enableUnreachableCodeWarnings": true',-1),t1=o(" VS Code user or workspace setting."),s1=e("li",null,"Fixed a code completion bug for COBOL and PL/I that would erase text to the right of the cursor.",-1),i1=o("Fixed cases in which COBOL statements before the IDENTIFICATION DIVISION would break syntax checking. ("),n1={href:"https://github.com/IBM/zopeneditor-about/issues/9",target:"_blank",rel:"noopener noreferrer"},r1=o("Issue #9"),a1=o(")"),l1=o("Fixed exceptions thrown by the PL/I LSP when computing document links ("),d1={href:"https://github.com/IBM/zopeneditor-about/issues/13",target:"_blank",rel:"noopener noreferrer"},h1=o("Issue #13"),c1=o(")"),u1=o("Fixed issues with COBOL Unreachable Code warnings not being shown at all in some cases. ("),_1={href:"https://github.com/IBM/zopeneditor-about/issues/7",target:"_blank",rel:"noopener noreferrer"},p1=o("Issue #7"),f1=o(")"),g1=e("li",null,"Fixed an issue in which invalid PIC clauses would not be reported as syntax errors.",-1),m1=e("h2",{id:"_0-3-11-2019-09-27",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_0-3-11-2019-09-27","aria-hidden":"true"},"#"),o(" 0.3.11 - 2019/09/27")],-1),b1=e("li",null,'"Unreachable Code" is not reported as an error anymore, but is now a warning message in the Problems View.',-1),w1=e("li",null,[o('Switch off "Unreachable Code" detection completely with this new setting: '),e("code",null,'"zopeneditor.cobol.enableUnreachableCodeWarnings": false'),o(".")],-1),I1=o("We implemented GLOB pattern matching in Property Group settings for finding Copybooks on the local file system as requested in "),y1={href:"https://github.com/IBM/zopeneditor-about/issues/5",target:"_blank",rel:"noopener noreferrer"},v1=o("this issue"),x1=o(". Use with care as a very large search space will slow down the editor."),S1=o("We added support for "),B1={href:"https://code.visualstudio.com/docs/editor/multi-root-workspaces",target:"_blank",rel:"noopener noreferrer"},A1=o("VS Code Multi-root Workspaces"),C1=o(" allowing you to now specify Property Groups for finding Copybooks for a workspace comprising of many development project folders and Git repositories. To use it move your Property Groups to the Workspace File."),E1=o("We updated and revised our documentation for using Property Groups with patterns and workspaces in the "),k1={href:"https://ibm.github.io/zopeneditor-about/Docs/setting_propertygroup.html",target:"_blank",rel:"noopener noreferrer"},O1=o("Online Help"),L1=o(". We also added examples for using it on Windows versus Mac/Linux."),M1=e("li",null,"Fixed an issue with using the Tab key in Code Snippets and when using it for indentation in the editor.",-1),z1=i('
       0.3.9 - 2019/09/23
      • Just removed Preview flag in preparation for the announcement.
      • Stay tuned for more cool things to come.
       0.3.7 - 2019/09/17
      • Fixes to the documentation and hyperlinks.
      • Renamed extension preferences configuration name.
       0.3.5 - 2019/09/13
      • First public release evolving out of the Wazi technology preview. See README.md for details.
      ',6);function P1(F1,R1){const s=n("ExternalLinkIcon"),r=n("RouterLink");return a(),l(h,null,[_,p,e("ul",null,[e("li",null,[f,e("a",g,[m,t(s)]),b]),w]),I,y,v,e("ul",null,[e("li",null,[x,S,B,e("a",A,[C,t(s)]),E]),k,e("li",null,[O,e("a",L,[M,t(s)]),z]),P]),F,e("p",null,[R,Z,e("a",U,[T,t(s)]),D,e("a",X,[N,t(s)]),H]),e("ul",null,[J,e("li",null,[V,e("a",q,[W,t(s)]),G]),e("li",null,[j,e("a",Y,[Q,t(s)]),K,$,ee,oe,te]),se,e("li",null,[ie,e("a",ne,[re,t(s)]),ae]),e("li",null,[le,e("a",de,[he,t(s)]),ce]),ue,e("li",null,[_e,e("a",pe,[fe,t(s)]),ge]),me,be,we]),Ie,ye,ve,e("ul",null,[e("li",null,[xe,t(r,{to:"/Blog/advanced_custom_macros.html"},{default:d(()=>[Se]),_:1}),Be]),Ae,e("li",null,[Ce,e("a",Ee,[ke,t(s)]),Oe]),e("li",null,[Le,e("a",Me,[ze,t(s)]),Pe]),e("li",null,[Fe,e("a",Re,[Ze,t(s)]),Ue])]),Te,e("ul",null,[e("li",null,[De,e("a",Xe,[Ne,t(s)]),He]),Je,Ve,qe,We,Ge]),je,Ye,Qe,e("p",null,[Ke,e("a",$e,[eo,t(s)]),oo]),to,so,io,no,ro,e("ul",null,[e("li",null,[ao,e("a",lo,[ho,t(s)]),co]),e("li",null,[uo,e("a",_o,[po,t(s)]),fo]),e("li",null,[go,e("a",mo,[bo,t(s)]),wo]),Io,yo,e("li",null,[vo,e("a",xo,[So,t(s)]),Bo]),e("li",null,[Ao,e("a",Co,[Eo,t(s)]),ko])]),Oo,e("ul",null,[Lo,e("li",null,[Mo,zo,Po,e("a",Fo,[Ro,t(s)]),Zo])]),Uo,e("ul",null,[e("li",null,[To,e("a",Do,[Xo,t(s)]),No]),Ho,e("li",null,[Jo,e("a",Vo,[qo,t(s)]),Wo]),e("li",null,[Go,e("a",jo,[Yo,t(s)]),Qo]),Ko,e("li",null,[$o,e("a",et,[ot,t(s)]),tt]),e("li",null,[st,e("a",it,[nt,t(s)]),rt]),e("li",null,[at,lt,dt,e("a",ht,[ct,t(s)]),ut])]),_t,pt,ft,e("ul",null,[e("li",null,[gt,e("a",mt,[bt,t(s)]),wt]),e("li",null,[It,yt,vt,e("a",xt,[St,t(s)]),Bt]),At,e("li",null,[Ct,e("a",Et,[kt,t(s)]),Ot]),Lt,Mt]),zt,e("ul",null,[Pt,e("li",null,[Ft,e("a",Rt,[Zt,t(s)]),Ut]),e("li",null,[Tt,e("a",Dt,[Xt,t(s)]),Nt,e("a",Ht,[Jt,t(s)]),Vt])]),qt,Wt,Gt,e("p",null,[jt,e("a",Yt,[Qt,t(s)]),Kt]),$t,e("ul",null,[es,e("li",null,[os,ts,ss,e("a",is,[ns,t(s)]),rs]),e("li",null,[as,e("a",ls,[ds,t(s)]),hs]),cs,e("li",null,[us,e("a",_s,[ps,t(s)]),fs]),e("li",null,[gs,e("a",ms,[bs,t(s)]),ws]),Is]),ys,e("ul",null,[e("li",null,[vs,e("a",xs,[Ss,t(s)]),Bs]),As,Cs]),Es,e("ul",null,[e("li",null,[ks,Os,Ls,Ms,zs,e("a",Ps,[Fs,t(s)]),Rs]),e("li",null,[Zs,Us,Ts,e("a",Ds,[Xs,t(s)]),Ns]),e("li",null,[Hs,e("a",Js,[Vs,t(s)]),qs]),Ws,Gs,js]),Ys,e("ul",null,[Qs,e("li",null,[Ks,$s,ei,e("a",oi,[ti,t(s)]),si]),ii,e("li",null,[ni,e("a",ri,[ai,t(s)]),li]),di,hi]),ci,e("ul",null,[e("li",null,[ui,e("a",_i,[pi,t(s)]),fi]),e("li",null,[gi,mi,bi,e("a",wi,[Ii,t(s)]),yi]),e("li",null,[vi,xi,Si,Bi,Ai,e("a",Ci,[Ei,t(s)]),ki]),e("li",null,[Oi,e("a",Li,[Mi,t(s)]),zi]),e("li",null,[Pi,e("a",Fi,[Ri,t(s)]),Zi]),e("li",null,[Ui,e("a",Ti,[Di,t(s)]),Xi]),e("li",null,[Ni,e("a",Hi,[Ji,t(s)]),Vi]),e("li",null,[qi,e("a",Wi,[Gi,t(s)]),ji]),Yi,Qi,Ki,$i,e("li",null,[en,e("a",on,[tn,t(s)]),sn,e("a",nn,[rn,t(s)]),an]),ln,dn,e("li",null,[hn,e("a",cn,[un,t(s)]),_n]),e("li",null,[pn,e("a",fn,[gn,t(s)]),mn]),bn,wn,e("li",null,[In,e("a",yn,[vn,t(s)]),xn]),Sn,Bn,e("li",null,[An,Cn,En,kn,On,e("a",Ln,[Mn,t(s)]),zn]),Pn,e("li",null,[Fn,e("a",Rn,[Zn,t(s)]),Un]),Tn,Dn,Xn,Nn]),Hn,e("ul",null,[Jn,e("li",null,[Vn,qn,Wn,Gn,jn,Yn,Qn,e("a",Kn,[$n,t(s)]),er]),e("li",null,[or,e("a",tr,[sr,t(s)]),ir]),e("li",null,[nr,e("a",rr,[ar,t(s)]),lr]),dr,e("li",null,[hr,cr,ur,_r,pr,e("a",fr,[gr,t(s)]),mr]),e("li",null,[br,wr,Ir,e("a",yr,[vr,t(s)]),xr]),e("li",null,[Sr,e("a",Br,[Ar,t(s)]),Cr]),Er]),kr,e("ul",null,[e("li",null,[Or,e("a",Lr,[Mr,t(s)]),zr]),e("li",null,[Pr,e("a",Fr,[Rr,t(s)]),Zr]),Ur,Tr,Dr,e("li",null,[Xr,e("a",Nr,[Hr,t(s)]),Jr]),e("li",null,[Vr,e("a",qr,[Wr,t(s)]),Gr]),e("li",null,[jr,Yr,Qr,Kr,$r,e("a",ea,[oa,t(s)]),ta]),sa,e("li",null,[ia,e("a",na,[ra,t(s)]),aa,e("a",la,[da,t(s)]),ha]),e("li",null,[ca,e("a",ua,[_a,t(s)]),pa]),e("li",null,[fa,e("a",ga,[ma,t(s)]),ba,e("a",wa,[Ia,t(s)]),ya]),e("li",null,[va,e("a",xa,[Sa,t(s)]),Ba]),e("li",null,[Aa,Ca,Ea,e("a",ka,[Oa,t(s)]),La]),Ma,za,e("li",null,[Pa,e("a",Fa,[Ra,t(s)]),Za]),e("li",null,[Ua,Ta,Da,Xa,Na,e("a",Ha,[Ja,t(s)]),Va]),qa,e("li",null,[Wa,Ga,ja,Ya,Qa,e("a",Ka,[$a,t(s)]),el])]),ol,e("ul",null,[e("li",null,[tl,e("a",sl,[il,t(s)]),nl]),e("li",null,[rl,e("a",al,[ll,t(s)]),dl]),e("li",null,[hl,e("a",cl,[ul,t(s)]),_l]),e("li",null,[pl,e("a",fl,[gl,t(s)]),ml]),e("li",null,[bl,wl,Il,e("a",yl,[vl,t(s)]),xl]),e("li",null,[Sl,Bl,Al,Cl,El,e("a",kl,[Ol,t(s)]),Ll]),e("li",null,[Ml,e("a",zl,[Pl,t(s)]),Fl,Rl,Zl,Ul,Tl]),Dl,Xl,Nl,Hl]),Jl,Vl,e("p",null,[ql,e("a",Wl,[Gl,t(s)]),jl]),e("ul",null,[e("li",null,[Yl,e("a",Ql,[Kl,t(s)]),$l]),ed,od,e("li",null,[td,e("a",sd,[id,t(s)]),nd,e("a",rd,[ad,t(s)]),ld]),e("li",null,[dd,e("a",hd,[cd,t(s)]),ud])]),_d,e("ul",null,[e("li",null,[pd,fd,gd,e("a",md,[bd,t(s)]),wd]),Id,e("li",null,[yd,vd,xd,e("a",Sd,[Bd,t(s)]),Ad]),e("li",null,[Cd,e("a",Ed,[kd,t(s)]),Od]),e("li",null,[Ld,e("a",Md,[zd,t(s)]),Pd]),e("li",null,[Fd,e("a",Rd,[Zd,t(s)]),Ud]),Td,Dd,Xd]),Nd,e("ul",null,[e("li",null,[Hd,e("a",Jd,[Vd,t(s)]),qd]),e("li",null,[Wd,e("a",Gd,[jd,t(s)]),Yd]),Qd,Kd,$d,eh,e("li",null,[oh,e("a",th,[sh,t(s)]),ih,e("a",nh,[rh,t(s)]),ah]),lh,dh]),hh,e("ul",null,[e("li",null,[ch,e("a",uh,[_h,t(s)])]),e("li",null,[ph,e("a",fh,[gh,t(s)]),mh,e("a",bh,[wh,t(s)]),Ih]),yh,e("li",null,[vh,e("a",xh,[Sh,t(s)]),Bh]),e("li",null,[Ah,e("a",Ch,[Eh,t(s)]),kh]),Oh,Lh]),Mh,e("ul",null,[e("li",null,[zh,e("a",Ph,[Fh,t(s)]),Rh,e("a",Zh,[Uh,t(s)]),Th]),e("li",null,[Dh,e("a",Xh,[Nh,t(s)]),Hh]),e("li",null,[Jh,e("a",Vh,[qh,t(s)]),Wh]),Gh,jh,e("li",null,[Yh,Qh,Kh,$h,ec,e("a",oc,[tc,t(s)]),sc]),e("li",null,[ic,nc,rc,e("a",ac,[lc,t(s)]),dc]),e("li",null,[hc,e("a",cc,[uc,t(s)]),_c]),pc,e("li",null,[fc,e("a",gc,[mc,t(s)]),bc]),e("li",null,[wc,e("a",Ic,[yc,t(s)]),vc]),xc,Sc]),Bc,e("ul",null,[Ac,e("li",null,[Cc,e("a",Ec,[kc,t(s)]),Oc]),e("li",null,[Lc,e("a",Mc,[zc,t(s)]),Pc]),e("li",null,[Fc,Rc,Zc,e("a",Uc,[Tc,t(s)]),Dc]),e("li",null,[Xc,e("a",Nc,[Hc,t(s)]),Jc])]),Vc,e("ul",null,[e("li",null,[qc,e("a",Wc,[Gc,t(s)]),jc]),e("li",null,[Yc,e("a",Qc,[Kc,t(s)]),$c]),e("li",null,[eu,e("a",ou,[tu,t(s)]),su]),iu,nu,e("li",null,[ru,e("a",au,[lu,t(s)]),du]),e("li",null,[hu,e("a",cu,[uu,t(s)]),_u]),pu,fu,e("li",null,[gu,e("a",mu,[bu,t(s)]),wu]),Iu,e("li",null,[yu,e("a",vu,[xu,t(s)]),Su]),Bu,Au,Cu,e("li",null,[Eu,e("a",ku,[Ou,t(s)]),Lu]),Mu,zu,Pu,Fu,Ru,e("li",null,[Zu,e("a",Uu,[Tu,t(s)]),Du]),Xu,Nu,Hu,e("li",null,[Ju,e("a",Vu,[qu,t(s)]),Wu])]),Gu,e("ul",null,[e("li",null,[ju,e("a",Yu,[Qu,t(s)]),Ku]),e("li",null,[$u,e("a",e_,[o_,t(s)]),t_]),e("li",null,[s_,e("a",i_,[n_,t(s)]),r_,e("a",a_,[l_,t(s)]),d_,e("a",h_,[c_,t(s)]),u_]),e("li",null,[__,e("a",p_,[f_,t(s)]),g_,e("a",m_,[b_,t(s)]),w_]),e("li",null,[I_,e("a",y_,[v_,t(s)]),x_]),S_,e("li",null,[B_,e("a",A_,[C_,t(s)]),E_]),e("li",null,[k_,e("a",O_,[L_,t(s)]),M_]),z_,P_,F_,R_,Z_]),U_,e("ul",null,[e("li",null,[T_,e("a",D_,[X_,t(s)]),N_]),e("li",null,[H_,e("a",J_,[V_,t(s)]),q_]),e("li",null,[W_,e("a",G_,[j_,t(s)]),Y_]),Q_,e("li",null,[K_,$_,ep,e("a",op,[tp,t(s)]),sp]),ip,np]),rp,e("ul",null,[e("li",null,[ap,e("a",lp,[dp,t(s)]),hp]),e("li",null,[cp,e("a",up,[_p,t(s)]),pp]),fp,e("li",null,[gp,e("a",mp,[bp,t(s)]),wp]),Ip,yp,vp]),xp,e("ul",null,[Sp,e("li",null,[Bp,e("a",Ap,[Cp,t(s)]),Ep,e("a",kp,[Op,t(s)]),Lp,e("a",Mp,[zp,t(s)]),Pp])]),Fp,e("ul",null,[e("li",null,[Rp,e("a",Zp,[Up,t(s)]),Tp]),Dp,Xp,e("li",null,[Np,e("a",Hp,[Jp,t(s)]),Vp]),qp,Wp,Gp,e("li",null,[jp,e("a",Yp,[Qp,t(s)]),Kp]),e("li",null,[$p,e("a",ef,[of,t(s)]),tf])]),sf,e("ul",null,[e("li",null,[nf,e("a",rf,[af,t(s)]),lf])]),df,e("ul",null,[hf,cf,e("li",null,[uf,e("a",_f,[pf,t(s)]),ff]),e("li",null,[gf,e("a",mf,[bf,t(s)]),wf])]),e("p",null,[If,e("a",yf,[vf,t(s)]),xf]),Sf,e("ul",null,[e("li",null,[Bf,e("a",Af,[Cf,t(s)]),Ef,e("a",kf,[Of,t(s)]),Lf,e("a",Mf,[zf,t(s)]),Pf]),e("li",null,[Ff,e("a",Rf,[Zf,t(s)]),Uf]),e("li",null,[Tf,e("a",Df,[Xf,t(s)]),Nf]),e("li",null,[Hf,Jf,Vf,qf,Wf,Gf,jf,e("a",Yf,[Qf,t(s)]),Kf])]),$f,e("ul",null,[eg,e("li",null,[og,e("a",tg,[sg,t(s)]),ig]),e("li",null,[ng,e("a",rg,[ag,t(s)]),lg]),e("li",null,[dg,hg,cg,e("a",ug,[_g,t(s)]),pg,e("a",fg,[gg,t(s)]),mg]),e("li",null,[bg,e("a",wg,[Ig,t(s)]),yg]),e("li",null,[vg,xg,Sg,e("a",Bg,[Ag,t(s)]),Cg]),Eg,kg,Og]),Lg,Mg,zg,e("ul",null,[e("li",null,[Pg,e("a",Fg,[Rg,t(s)]),Zg]),Ug,e("li",null,[Tg,e("a",Dg,[Xg,t(s)]),Ng]),e("li",null,[Hg,e("a",Jg,[Vg,t(s)]),qg]),e("li",null,[Wg,Gg,jg,e("a",Yg,[Qg,t(s)]),Kg]),$g]),em,om,tm,e("ul",null,[e("li",null,[sm,e("a",im,[nm,t(s)]),rm])]),am,e("ul",null,[lm,dm,e("li",null,[hm,e("a",cm,[um,t(s)])])]),_m,e("ul",null,[pm,fm,gm,mm,bm,e("li",null,[wm,Im,ym,e("a",vm,[xm,t(s)]),Sm]),Bm,Am,Cm,Em,e("li",null,[km,e("a",Om,[Lm,t(s)]),Mm]),zm]),Pm,Fm,Rm,e("ul",null,[e("li",null,[Zm,e("a",Um,[Tm,t(s)]),Dm]),Xm,Nm,Hm]),Jm,e("ul",null,[Vm,e("li",null,[qm,e("a",Wm,[Gm,t(s)]),jm]),Ym,e("li",null,[Qm,e("a",Km,[$m,t(s)]),e1,o1,t1]),s1,e("li",null,[i1,e("a",n1,[r1,t(s)]),a1]),e("li",null,[l1,e("a",d1,[h1,t(s)]),c1]),e("li",null,[u1,e("a",_1,[p1,t(s)]),f1]),g1]),m1,e("ul",null,[b1,w1,e("li",null,[I1,e("a",y1,[v1,t(s)]),x1]),e("li",null,[S1,e("a",B1,[A1,t(s)]),C1]),e("li",null,[E1,e("a",k1,[O1,t(s)]),L1]),M1]),z1],64)}var T1=c(u,[["render",P1]]);export{T1 as default};
diff --git a/assets/new-releases.html.943c2e0c.js b/assets/new-releases.html.943c2e0c.js
deleted file mode 100644
index c0735e214..000000000
--- a/assets/new-releases.html.943c2e0c.js
+++ /dev/null
@@ -1 +0,0 @@
-const e={key:"v-7e9516cc",path:"/Blog/new-releases.html",title:"IBM Z Open Editor Releases",lang:"en-US",frontmatter:{},excerpt:"",headers:[{level:1,title:"IBM Z Open Editor Releases",slug:"ibm-z-open-editor-releases",children:[{level:2,title:"4.4.0 - 2024/08/12",slug:"_4-4-0-2024-08-12",children:[]},{level:2,title:"4.3.0 - 2024/06/18",slug:"_4-3-0-2024-06-18",children:[]},{level:2,title:"4.2.0 - 2024/05/16",slug:"_4-2-0-2024-05-16",children:[]},{level:2,title:"4.1.0 - 2024/03/28",slug:"_4-1-0-2024-03-28",children:[]},{level:2,title:"4.0.0 - 2024/03/15",slug:"_4-0-0-2024-03-15",children:[]},{level:2,title:"3.4.0 - 2024/02/29",slug:"_3-4-0-2024-02-29",children:[]},{level:2,title:"3.3.3 - 2023/12/15",slug:"_3-3-3-2023-12-15",children:[]},{level:2,title:"3.3.2 - 2023/11/28",slug:"_3-3-2-2023-11-28",children:[]},{level:2,title:"3.3.1 - 2023/11/07",slug:"_3-3-1-2023-11-07",children:[]},{level:2,title:"3.3.0 - 2023/10/25",slug:"_3-3-0-2023-10-25",children:[]},{level:2,title:"3.2.3 - 2023/10/11",slug:"_3-2-3-2023-10-11",children:[]},{level:2,title:"3.2.2 - 2023/09/15",slug:"_3-2-2-2023-09-15",children:[]},{level:2,title:"3.2.1 - 2023/07/19",slug:"_3-2-1-2023-07-19",children:[]},{level:2,title:"3.2.0 - 2023/06/16",slug:"_3-2-0-2023-06-16",children:[]},{level:2,title:"3.1.1 - 2023/03/30",slug:"_3-1-1-2023-03-30",children:[]},{level:2,title:"3.1.0 - 2023/03/10",slug:"_3-1-0-2023-03-10",children:[]},{level:2,title:"3.0.1 - 2023/01/18",slug:"_3-0-1-2023-01-18",children:[]},{level:2,title:"3.0.0 - 2022/11/22",slug:"_3-0-0-2022-11-22",children:[]},{level:2,title:"2.2.0 - 2022/09/20",slug:"_2-2-0-2022-09-20",children:[]},{level:2,title:"2.1.1 - 2022/08/14",slug:"_2-1-1-2022-08-14",children:[]},{level:2,title:"2.1.0 - 2022/06/14",slug:"_2-1-0-2022-06-14",children:[]},{level:2,title:"2.0.3 - 2022/05/20",slug:"_2-0-3-2022-05-20",children:[]},{level:2,title:"2.0.2 - 2022/04/25",slug:"_2-0-2-2022-04-25",children:[]},{level:2,title:"2.0.0 - 2022/03/15",slug:"_2-0-0-2022-03-15",children:[]},{level:2,title:"1.4.1 - 2021/11/19",slug:"_1-4-1-2021-11-19",children:[]},{level:2,title:"1.4.0 - 2021/10/29",slug:"_1-4-0-2021-10-29",children:[]},{level:2,title:"1.2.6 - 2021/08/19",slug:"_1-2-6-2021-08-19",children:[]},{level:2,title:"1.2.5 - 2021/06/18",slug:"_1-2-5-2021-06-18",children:[]},{level:2,title:"1.2.1 - 2021/04/21",slug:"_1-2-1-2021-04-21",children:[]},{level:2,title:"1.2.0 - 2021/03/19",slug:"_1-2-0-2021-03-19",children:[]},{level:2,title:"1.1.3 - 2020/12/12",slug:"_1-1-3-2020-12-12",children:[]},{level:2,title:"1.1.2 - 2020/12/09",slug:"_1-1-2-2020-12-09",children:[]},{level:2,title:"1.1.1 - 2020/11/6",slug:"_1-1-1-2020-11-6",children:[]},{level:2,title:"1.1.0 - 2020/10/23",slug:"_1-1-0-2020-10-23",children:[]},{level:2,title:"1.0.3 - 2020/08/07",slug:"_1-0-3-2020-08-07",children:[]},{level:2,title:"1.0.2 - 2020/06/30",slug:"_1-0-2-2020-06-30",children:[]},{level:2,title:"1.0.1/0.5.2 - 2020/06/23",slug:"_1-0-1-0-5-2-2020-06-23",children:[]},{level:2,title:"1.0.0 - 2020/06/12",slug:"_1-0-0-2020-06-12",children:[]},{level:2,title:"0.5.0 - 2020/06/12",slug:"_0-5-0-2020-06-12",children:[]},{level:2,title:"0.4.9 - 2020/04/23",slug:"_0-4-9-2020-04-23",children:[]},{level:2,title:"0.4.7 - 2020/03/27",slug:"_0-4-7-2020-03-27",children:[]},{level:2,title:"0.4.5 - 2020/01/07",slug:"_0-4-5-2020-01-07",children:[]},{level:2,title:"0.4.3 - 2019/12/18",slug:"_0-4-3-2019-12-18",children:[]},{level:2,title:"0.4.1 - 2019/11/21",slug:"_0-4-1-2019-11-21",children:[]},{level:2,title:"0.3.11 - 2019/09/27",slug:"_0-3-11-2019-09-27",children:[]},{level:2,title:"0.3.9 - 2019/09/23",slug:"_0-3-9-2019-09-23",children:[]},{level:2,title:"0.3.7 - 2019/09/17",slug:"_0-3-7-2019-09-17",children:[]},{level:2,title:"0.3.5 - 2019/09/13",slug:"_0-3-5-2019-09-13",children:[]}]}],git:{updatedTime:172304606e4,contributors:[{name:"Peter Haumer",email:"4391934+phaumer@users.noreply.github.com",commits:19},{name:"Peter Haumer",email:"phaumer@us.ibm.com",commits:18},{name:"kmaselli",email:"81706519+kmaselli@users.noreply.github.com",commits:6},{name:"Billie Jean Simmons",email:"billiejean.simmons@ibm.com",commits:5},{name:"PETER HAUMER",email:"phaumer@us.ibm.com",commits:5},{name:"Chun Hong Zheng",email:"chunhzh@cn.ibm.com",commits:3},{name:"Lauren Li",email:"45975633+lauren-li@users.noreply.github.com",commits:3},{name:"Hestia Zhang",email:"Hestia.Zhang@ibm.com",commits:2},{name:"KRISTINA MAYO",email:"ktopchi@us.ibm.com",commits:1},{name:"Lauren Li",email:"Lauren.Li@ibm.com",commits:1},{name:"Min Huang",email:"minhsh@cn.ibm.com",commits:1},{name:"Prasang-A-Prajapati",email:"Prasang.A.Prajapati@ibm.com",commits:1},{name:"Saile Daimwood",email:"sdaimwood@ibm.com",commits:1},{name:"Shi Kun Li",email:"shikunli@cn.ibm.com",commits:1},{name:"shikunli",email:"shikunli@cn.ibm.com",commits:1}]},filePathRelative:"Blog/new-releases.md"};export{e as data};
diff --git a/assets/new-releases.html.e21383d2.js b/assets/new-releases.html.e21383d2.js
new file mode 100644
index 000000000..ee3f96f6b
--- /dev/null
+++ b/assets/new-releases.html.e21383d2.js
@@ -0,0 +1 @@
+import{r as n,o as a,a as l,b as e,d as t,w as d,F as h,c as i,e as o}from"./app.daa93c96.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const u={},_=i('
       IBM Z Open Editor Releases
       4.5.0 - 2024/09/19
      • Added experimental context-menu command to expand the current COBOL program. It currently expands copybooks and opens an new editor tab with a temporary file showing the result. The expansion utilizes our language server and is currently limited, not providing evaluation of conditional compilation, yet.
      • Fix the bug that caused incorrect symbol names in the COBOL outline view for code lines with trailing comments and sequence numbers.
      • Fixed the issue where JCL code folding ranges were computed incorrectly for lines with trailing comments and the folding range for JCL JOB cards were missing sub-element, i.e. EXEC steps.
      • Fixed the issue where JCL code completion were giving incorrect suggestions when a statement starts with // DD by using DD as a label name for DD, EXEC or JOB statements.
      Advanced features:
      • Completed the MVS search capabilities in the z/OS Resources table by adding PDS member search. You can look for strings inside all your members of the data sets currently listed in the table or qualified by a naming pattern for the members. Results will be shown in the table and allow you to navigate to file locations with a simple click. Requires RSE API Zowe profiles.
      • Added UNIX System Services search capabilities in the z/OS Resources table allowing you to search files with name patterns as well as the contents of these files. Results will be shown in the table in the same ways as MVS search results allowing you to navigate to file locations with a simple click. Requires RSE API Zowe profiles.
      • Added preprocessor support for PL/I in addition to COBOL. Execute a processor that transform your custom code into valid PL/I locally on your workstation or on z/OS and continue editing your original program in Z Open Editor.
      • Various bug fixes for resolving HLASM custom macro definition and providing code completion in the editor.
      IBM RSE API Plug-in for Zowe CLI:
      • Performance improvement for retrieving all the member names of a data set with a large number of members.
      • Added --lc local encoding option for MVS and UNIX upload and download commands.
      • Added new command data-set-cross-lpar for copying datasets from one LPAR to other.
      • Added new change sub-command unix-file-encoding that updates the UNIX file target encoding.
       4.4.0 - 2024/08/12
      ',8),p=o("Fixed the issue where Java was not being found on Windows or Linux when Z Open Editor searched the user's system. ("),f={href:"https://github.com/IBM/zopeneditor-about/issues/420",target:"_blank",rel:"noopener noreferrer"},g=o("Issue 420"),m=o(")"),b=i("
    • Added code folding to our COBOL language server, which features folding for Divisions, Sections, Paragraphs, Data-items, and EXEC SQL/CICS statements. Also added code folding range support to JCL.
    • Improved the COBOL and JCL Outline views to include comments in the selection ranges when clicking an outline node.
    • Fixed the issue with the resolution order for the NAMES() compiler option in PL/I when it was listed before include file locations.
    • Added the file extension .dbd, .mfs, and .pcb to the defaults for our HLASM editor.
    • We now provide snippet style code completion for HLASM operations and macros. Use tab to fill out or remove various parameters when the operation or macro is selected from the code completion list. The editor will then also show syntax errors when manually typing operation parameters incorrectly.
    • Added Go to References support for HLASM Operations and Macros to see references within the same file for a selected operation.
    • Fixed the issue in JCL where an incorrect error was shown for DD statement: "JCL incorrectly highlights empty DD line as error".
    • Fixed the issue in JCL where an incorrect error was shown for EXEC DLI and XOPTS(DLI) statements.
    • Performance improvements for language server document requests when finding the copybooks/include files. The language server now prioritizes requesting the most recently opened documents.
    • Experimental: all Z Open Editor VS Code extension strings have been localized to French and German using IBM's AI machine translation. Let us know if you like these translations.
      • ",10),w=e("p",null,"Advanced features:",-1),I=e("ul",null,[e("li",null,"New feature: added filter and search operations to the z/OS Resources table. You can now search within the content of sequential data sets that are currently listed in your table; search requires using IBM's RSE API. We also added new filter options to the table for RSE API and z/OSMF to help you refine the list displayed for the Zowe query directly in the table. More search and filter capabilities will be added for RSE API users soon."),e("li",null,'Combined "last modified" date and "last modified" time columns into "last modified" in z/OSMF PDS member views of the z/OS Resources Table.'),e("li",null,"Fixed the issue where the z/OS Resources Table was not compatible with MVS date formats in RSE API v1.1.5."),e("li",null,"Various fixes, refinements and improvements for remote preprocessor support such as improved logging of the remote preprocessor execution output, better error handling, support for z/OSMF with TSO Zowe profiles, added the 'Compare preprocessor input and output files' command to remote preprocessor files as well as improvements for managing the output file."),e("li",null,"Added a progress bar and a Cancel button to user build operations. After clicking the Cancel button, user build will wait until any remote operation is completed and then stop.")],-1),y=e("p",null,"IBM RSE API Plug-in for Zowe CLI:",-1),v=o("We are now providing a variant of the RSE API CLI Plug-in that can be used for installation in air gapped development environments. Find "),x=e("code",null,"ibm-rse-api-for-zowe-cli-airgap-4.4.0.tgz",-1),S=o(" in our IBM Wazi for VS Code Zip file at "),A={href:"https://ibm.github.io/mainframe-downloads/downloads.html",target:"_blank",rel:"noopener noreferrer"},B=o("https://ibm.github.io/mainframe-downloads/downloads.html"),C=o("."),E=e("li",null,"Fixed the issue with multiple items included in data set filter search with RSE profiles.",-1),O=o("Fixed the issue reported using RSE CLI for downloading files when using Nodejs v20. ("),k={href:"https://github.com/IBM/zopeneditor-about/issues/427",target:"_blank",rel:"noopener noreferrer"},L=o("Issue 427"),M=o(")"),z=e("li",null,[o("Added a new "),e("code",null,"change"),o(" sub-command: "),e("code",null,"clear-tag"),o(" which clears the tags of the specified UNIX System Services file.")],-1),P=e("h2",{id:"_4-3-0-2024-06-18",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_4-3-0-2024-06-18","aria-hidden":"true"},"#"),o(" 4.3.0 - 2024/06/18")],-1),R=e("strong",null,"Note",-1),F=o(": Import update for the release of version 4.3.0 of IBM Z Open Editor: "),Z={href:"https://www.ibm.com/products/watsonx-code-assistant-z",target:"_blank",rel:"noopener noreferrer"},U=o("IBM watsonx Code Assistant for Z"),T=o(", which supports AI-assisted transformation of COBOL to Java for modernizing applications, has now been moved into it's own VS Code extension IBM watsonx Code Assistant for Z version 2.0.0. All functionality has been migrated into this new dedicated extension. Receive your copy of the Z Code Assistant via your Passport Advantage Online account. See the "),D={href:"https://www.ibm.com/docs/en/watsonx-code-assistant-4z",target:"_blank",rel:"noopener noreferrer"},X=o("Documentation"),N=o(" for more details."),J=e("li",null,"New advanced feature: run your custom COBOL preprocessor on z/OS directly from our editor and edit your files without any syntax errors caused by preprocessor statements. We now offer local preprocessor execution and editor integrations as well as remote execution via TSO commands on z/OS.",-1),H=o("All new JCL language server: with this release we add language support for "),V={href:"https://www.ibm.com/docs/en/SSLTBW_3.1.0/pdf/ieab600_v3r1.pdf",target:"_blank",rel:"noopener noreferrer"},q=o("z/OS MVS JCL"),W=i(". This first version includes the following features: 
      • Improved syntax highlighting
      • Real-time syntax errors
      • Code completion using Ctrl/Cmd + Space
      • Outline view
      • On-enter rules in Textmate grammar for JCL 
        • Auto prefix newline with // if previous line prefixed with // (except for in-stream declarations i.e. DD *). Indentation is inherited (up to column 16 for non-empty lines). JOB declarations are automatically indented to column 16
        • Auto comment continuation for lines prefixed with //*
      • Vertical rulers at significant JCL column numbers (2, 10, 11, 15, 16, 72, 80)
      • JCL Custom tabstops (Default tabstops are: [0, 2, 10, 15, 19, 29, 39, 49, 59, 71, 72])
      • Support for commenting and uncommenting highlighted selections using Ctrl/Cmd + /
      ",2),G=o("Completed support for PL/I v6.1 January 2024 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this "),j={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/di-hu1/2024/01/31/january-2024-documentation-refresh-for-enterprise",target:"_blank",rel:"noopener noreferrer"},Y=o("blog post"),Q=o(" for details. Additionally, support for the new "),K=e("code",null,"JSONIGNORE",-1),$=o(", "),ee=e("code",null,"JSONNULL",-1),oe=o(" keywords was added."),te=e("li",null,"Fixed the issue in the PL/I editor evaluating the names for include files differently than the compiler if the name includes special characters.",-1),se=o("Fixed the issue of false unreachable code warnings around EXEC CICS PERFORM + HANDLE statements. ("),ie={href:"https://github.com/IBM/zopeneditor-about/issues/52",target:"_blank",rel:"noopener noreferrer"},ne=o("Issue 52"),re=o(")"),ae=o("Fixed the issue of false unreachable code warnings around EXEC SQL WHENEVER statements. "),le={href:"https://github.com/IBM/zopeneditor-about/issues/63",target:"_blank",rel:"noopener noreferrer"},de=o("Issue 63"),he=o(")"),ce=e("li",null,[o("Fixed the issue in the REXX editor showing incorrect syntax errors for "),e("code",null,"ELSE"),o(" statements in certain scenarios.")],-1),ue=o("Fixed the issue in HLASM where optional operands were not correctly accounted for when evaluating the number of operands provided. ("),_e={href:"https://github.com/IBM/zopeneditor-about/issues/418",target:"_blank",rel:"noopener noreferrer"},pe=o("Issue 418"),fe=o(")"),ge=e("li",null,"Added support for double-byte character editing. The editor will decorate double-byte character strings using guillemets icons and display a byte counter in the status bar giving users information about how many bytes they have left for the current line to avoid truncation.",-1),me=e("li",null,"Extended the status bar information for the active Zowe profiles, making it an active button with options to change the profile selection. For RSE API profiles, it provides the option to update the z/OS password.",-1),be=e("li",null,"Fixed the issue where renaming sequential data sets using the z/OS resources tables would temporarily show empty attributes for the renamed data set.",-1),we=e("p",null,"IBM RSE API Plug-in for Zowe:",-1),Ie=e("ul",null,[e("li",null,"Added a check for Zowe CLI version compatibility that is executed by the RSE API plugin for Zowe CLI during installation."),e("li",null,"Uploading files to z/OS UNIX System Service using RSE API profiles can now automatically detect if the file is binary."),e("li",null,"Fixed the issue of showing an incorrect error message when no data sets were found that match a search pattern.")],-1),ye=e("h2",{id:"_4-2-0-2024-05-16",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_4-2-0-2024-05-16","aria-hidden":"true"},"#"),o(" 4.2.0 - 2024/05/16")],-1),ve=o("New advanced feature: custom macro resolution in HLASM programs with references to macros in local files. The HLASM editor shows hovers, document links, go to definition, and code completion for macros. This feature works with one to many macro declarations per include file, which is achieved by pre-scanning macro files if they can be found in local ZAPP property groups. For more information, see "),xe=o("Custom Macros for HLASM"),Se=o("."),Ae=e("li",null,[o("Improved advanced feature: the z/OS resources table is updated to also support UNIX System Services. You can browse, filter, sort, open, download, upload, create, and copy your unix folders and files with the same user experience as in our previous release for MVS and JES. In addition, you find many UX refinements and polish for all views of this table. We also fixed "),e("ul",null,[e("li",null,"presenting and sorting numbers and dates based on the user's locale."),e("li",null,"presenting DSNTYPE for MVS data sets, even if the value is not provided by z/OSMF.")])],-1),Be=o("Added support for COBOL User Defined Function Prototypes. See "),Ce={href:"https://www.ibm.com/docs/en/cobol-zos/6.4?topic=applications-using-function-prototypes",target:"_blank",rel:"noopener noreferrer"},Ee=o("COBOL documentation"),Oe=o(" for details."),ke=o("Fix the issue where formatting EXEC SQL statements resulted in incorrect syntax ("),Le={href:"https://github.com/IBM/zopeneditor-about/issues/400",target:"_blank",rel:"noopener noreferrer"},Me=o("Issue 400"),ze=o(")."),Pe=o("Reorganized our startup and restart code to avoid problems such as "),Re={href:"https://github.com/IBM/zopeneditor-about/issues/403",target:"_blank",rel:"noopener noreferrer"},Fe=o("Issue 403"),Ze=o("."),Ue=i('
      IBM RSE API Plug-in for Zowe:
      • Fixed the issue of spool files not being correctly exported when their record length exceeded that of the destination dataset, resulting in truncation.
      • Fixed typographical errors in the new common-properties commands.
      • Fixed the issue that is seen downloading all members of a data set.
      IBM watsonx Code Assistant for Z:
      • Added editing of local variable names during class generation that will then be used during Java method generation.
      • Added editing of method input parameters during class generation that will then be used during Java class and method generation.
      • Improved Java method generation by sanitizing the COBOL code, such as removing comments and contents from columns 1-6 and 73-80.
      • Fixed the issue where for some edge cases the Java method generation was returning an empty code block.
      • Fix the issue where Java classes and methods were not appearing in the watsonx Code Assistant for Z tree view when the COBOL program was located in the top-level workspace folder.
      • Fixed the issue of the editor opening the same Java file in multiple editor tabs when using the watsonx Code Assistant for Z tree view.
      • Added support for proxy servers for watsonx interactions utilizing the VS Code settings http.proxy, http.proxyStrictSSL, http.proxyAuthorization when http.proxySupport is switched to on.
      • Various fixes and refinements for the watsonx tree view interactions related to item and source code selection.
       4.1.0 - 2024/03/28
      ',5),Te=o("Fixed the issue where SETC values were causing the HLASM parser to fail in certain scenarios. ("),De={href:"https://github.com/IBM/zopeneditor-about/issues/396",target:"_blank",rel:"noopener noreferrer"},Xe=o("Issue 396"),Ne=o(")"),Je=e("li",null,"Added new options for listing additional job attributes in RSE API Plug-in for Zowe CLI.",-1),He=e("li",null,"Added ability to search files in UNIX System Services by file name or content in RSE API Plug-in for Zowe CLI.",-1),Ve=e("li",null,"Added new commands for storing and retrieving name/value pairs with RSE's Common Properties service in RSE API Plug-in for Zowe CLI.",-1),qe=e("li",null,"Fixed the issue of failed downloads from z/OS for some file types using RSE API profiles.",-1),We=e("li",null,"Fixed the issue where downloading spool files with RSE API profiles would be stored with invalid file extensions.",-1),Ge=e("p",null,"IBM watsonx Code Assistant for Z updates:",-1),je=e("ul",null,[e("li",null,"Added a walkthrough for new users to get a step-by-step guide on how to use watsonx Code Assistant for Z. You can access the walkthrough from the Z Open Editor Welcome page or from the VS Code Welcome page."),e("li",null,"Added a new CodeLens when editing generated Java code to view and navigate to the COBOL source that watsonx Code Assistant for Z was using to generate a Java method."),e("li",null,"COBOL files selected for Transformation in watsonx Code Assistant for Z will no longer open in read-only mode.")],-1),Ye=e("h2",{id:"_4-0-0-2024-03-15",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_4-0-0-2024-03-15","aria-hidden":"true"},"#"),o(" 4.0.0 - 2024/03/15")],-1),Qe=o("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 "),Ke={href:"https://ibm.biz/code-whatsnew",target:"_blank",rel:"noopener noreferrer"},$e=o("IBM Documentation"),eo=o("."),oo=e("p",null,"To emphasize, none of the other features that you were using in previous releases are impacted by the update. Previous features are still available for free and will still be maintained and enhanced as always. We are also still fully committed to supporting z/OSMF and RSE API for the free as well as advanced capabilities.",-1),to=e("p",null,"Only the following three new features require a license. Our goal is to provide more and more advanced features such as these to Z Open Editor in the future:",-1),so=e("ol",null,[e("li",null,"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."),e("li",null,"z/OS Resources table: an all-new feature rich 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."),e("li",null,"Advanced Dependency-Based user build error reporting: User build logs are now automatically downloaded, parsed, and presented in the editor's Problems view with 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.")],-1),io=e("p",null,"We reorganized the Z Open Editor Welcome page for you to see the status of your trial license. You can unlock the features by importing an activation kit or connecting to an RSE API server with configured IDzEE licenses.",-1),no=e("p",null,"Free languages updates:",-1),ro=o("Added support for the COBOL v6.4 February 2024 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this "),ao={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/dan-zhang1/2024/02/26/february-2024-documentation-refresh-for-enterprise",target:"_blank",rel:"noopener noreferrer"},lo=o("blog post"),ho=o(" for details."),co=o("Added support for the COBOL v6.4 October 2023 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this "),uo={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/jun-qian-zhou1/2023/10/31/october-2023-documentation-refresh-for-enterprise",target:"_blank",rel:"noopener noreferrer"},_o=o("blog post"),po=o(" for details."),fo=o("Added support for the PL/I v6.1 January 2024 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this "),go={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/di-hu1/2024/01/31/january-2024-documentation-refresh-for-enterprise",target:"_blank",rel:"noopener noreferrer"},mo=o("blog post"),bo=o(" for details."),wo=e("li",null,"Added support for the CICS v6.2 Beta Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features.",-1),Io=e("li",null,[o("Added support for the z/OS 3.1 default HLASM macros. z/OS 3.1 is now the default option. To change your z/OS level, search "),e("code",null,"zopeneditor.hlasm.zosMacrosVersion"),o(" in settings.")],-1),yo=o("Fixed the issue where the HLASM Language Server did not parse non-english characters correctly. ("),vo={href:"https://github.com/IBM/zopeneditor-about/issues/389",target:"_blank",rel:"noopener noreferrer"},xo=o("#389"),So=o(")"),Ao=o("Added the debug scheme to our language clients, enabling full language server support providing you with features such as Outline view, Go to Definition, Find All References even when running IBM Z Open Debug sessions. ("),Bo={href:"https://github.com/IBM/zopeneditor-about/issues/360",target:"_blank",rel:"noopener noreferrer"},Co=o("#360"),Eo=o(")"),Oo=e("p",null,"Free RSE API Plug-in for Zowe CLI updates:",-1),ko=i("
    • Z Open Editor extends the Zowe Explorer's Jobs view experience: open a spool file in Zowe Explorer and Z Open Editor will automatically provide JCL and messages syntax highlighting.
    • Added support for changing file tags on USS for RSE API profiles in Zowe Explorer.
    • Added support to show partitioned data set member attributes for RSE API profiles in Zowe Explorer.
    • Added support for creating a data sets for RSE API profiles using the new templates from Zowe Explorer.
    • Added support for Zowe profile encoding with DBB User Build download of log files.
    • Added new command issue unix-shell for RSE API profiles that utilizes a streaming command output and allows users to set environment variables for the executing shell.
    • Added new command export spool-file for RSE API profiles allowing export of job spool files to a sequential data set or data set members.
    • Added support for refreshToken and auto-refresh-token for RSE API profiles in Zowe Explorer.
    • Switched to using RSE API streaming for raw content when uploading to and downloading from MVS, UNIX System Services, and JES files.
    • Fixed the issue with creating a partitioned data set of the type LIBRARY for RSE API profiles did not work correctly.
    • Fixed the issue of command issue unix returning an incorrect exit code.
      • ",11),Lo=o("Fixed the error when submitting jobs using the "),Mo=e("code",null,"--wfo",-1),zo=o(" (wait for output) option using RSE API profiles. ("),Po={href:"https://github.com/IBM/zopeneditor-about/issues/385",target:"_blank",rel:"noopener noreferrer"},Ro=o("#385"),Fo=o(")"),Zo=e("h2",{id:"_3-4-0-2024-02-29",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-4-0-2024-02-29","aria-hidden":"true"},"#"),o(" 3.4.0 - 2024/02/29")],-1),Uo=o('Fixed the issue with Embedded EXEC CICS statements where EXEC CICS GET CHANNEL was marked with the error "RESP expected instead of this input". ('),To={href:"https://github.com/IBM/zopeneditor-about/issues/361",target:"_blank",rel:"noopener noreferrer"},Do=o("Issue 361"),Xo=o(")"),No=e("li",null,'Fixed the issue with Embedded CICS EXCI statements where CICS EXCI was marked with the error "RESP expected instead of this input".',-1),Jo=o('Fixed the issue with Embedded SQL statements where SQLCA symbols were not resolved when an "EXEC SQL INCLUDE SQLCA" statement was inside of a conditional compilation block. ('),Ho={href:"https://github.com/IBM/zopeneditor-about/issues/379",target:"_blank",rel:"noopener noreferrer"},Vo=o("Issue 379"),qo=o(")"),Wo=o('Fixed the issue of incorrectly showing an error about the absence of an end directive when the conditional compilation directive ">>define" was on the last line of a Copybook file. ('),Go={href:"https://github.com/IBM/zopeneditor-about/issues/374",target:"_blank",rel:"noopener noreferrer"},jo=o("Issue 374"),Yo=o(")"),Qo=e("li",null,'Fixed the issue where COBOL COPY statements with a "." but without a whitespace were marked with an error.',-1),Ko=o("Fixed the issue where document links were not resolving correctly when multiple documents were opened in parallel that pointed to the same include files in COBOL, PL/I, and HLASM files. ("),$o={href:"https://github.com/IBM/zopeneditor-about/issues/363",target:"_blank",rel:"noopener noreferrer"},et=o("Issue 363"),ot=o(")"),tt=o("Fixed an issue where document links would not remove the red underline for an include file after loading correctly in COBOL, PL/I, and HLASM files. ("),st={href:"https://github.com/IBM/zopeneditor-about/issues/363",target:"_blank",rel:"noopener noreferrer"},it=o("Issue 363"),nt=o(")"),rt=o("Fixed the issue where REXX syntax highlighting would break when an empty comment statement was present "),at=e("code",null,"/**/",-1),lt=o(". ("),dt={href:"https://github.com/IBM/zopeneditor-about/issues/384",target:"_blank",rel:"noopener noreferrer"},ht=o("Issue 384"),ct=o(")."),ut=e("p",null,"IBM watsonx Code Assistant for Z updates:",-1),_t=e("ul",null,[e("li",null,"Replaced the COBOL-centric class generation preview with a new Java-centric presentation for watsonx Code Assistant for Z. Users can now preview the Java classes to be generated in an expandable table view that outlines the variable and method member names next to their mapped COBOL names. They can click hyperlinks within the mapping view to navigate directly back to the COBOL source code files for comparison."),e("li",null,"Updated the watsonx Code Assistant for Z tree view to show a breakdown of method members per Java class that can be generated by the assistant's AI component. These methods are based on COBOL section and paragraph names and become available after the initial Java class generation step has been completed."),e("li",null,"Updated the watsonx Code Assistant for Z tree view to support a new workflow for reopening saved COBOL-to-Java mappings and regenerating Java code."),e("li",null,"Updated the watsonx Code Assistant for Z tree view with new icons and icon decorators that visualize which Java members mapped from COBOL paragraphs have already been generated and which not."),e("li",null,"Updated error handling, error message dialogs, and log file messages."),e("li",null,"Fixed the issue of the Welcome page checkbox for enabling/disabling watsonx Code Assistant for Z not being synchronized with the respective user setting.")],-1),pt=e("h2",{id:"_3-3-3-2023-12-15",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-3-3-2023-12-15","aria-hidden":"true"},"#"),o(" 3.3.3 - 2023/12/15")],-1),ft=o("Fixed the issue for COBOL where SKIP1, SKIP2, SKIP3, and EJECT tokens were not being handled correctly when placed within other statements to control white space. ("),gt={href:"https://github.com/IBM/zopeneditor-about/issues/307",target:"_blank",rel:"noopener noreferrer"},mt=o("Issue 307"),bt=o(")"),wt=o("Fixed the issue where conditional compilation statements were not being handled correctly when placed in a "),It=e("code",null,">>WHEN OTHER",-1),yt=o(" phrase. ("),vt={href:"https://github.com/IBM/zopeneditor-about/issues/366",target:"_blank",rel:"noopener noreferrer"},xt=o("Issue 366"),St=o(")"),At=e("li",null,"Fixed the issue where the COBOL parser could hang or crash when a file's final line ended with a character in column 7.",-1),Bt=o("Fixed the issue where a language server would start before all ZAPP files were processed missing settings such as compiler options. ("),Ct={href:"https://github.com/IBM/zopeneditor-about/issues/364",target:"_blank",rel:"noopener noreferrer"},Et=o("Issue 364"),Ot=o(")"),kt=e("li",null,"Fixed the issue where the RSE API plugin for Zowe CLI command to upload a file to a UNIX System Services directory would show an error.",-1),Lt=e("li",null,"Various bug and serviceability fixes as well as UI refinements for IBM watsonx Code Assistant for Z. Generate Java classes now by using the icon next to the COBOL program name or by using the context menu. When entering an API key you will now receive a confirmation message after a server-side validation check.",-1),Mt=e("h2",{id:"_3-3-2-2023-11-28",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-3-2-2023-11-28","aria-hidden":"true"},"#"),o(" 3.3.2 - 2023/11/28")],-1),zt=e("li",null,"Required security updates for third party dependencies.",-1),Pt=o("Fixed the COBOL parsing issue where intermediate data names would be using an incorrect context. ("),Rt={href:"https://github.com/IBM/zopeneditor-about/issues/362",target:"_blank",rel:"noopener noreferrer"},Ft=o("Issue 362"),Zt=o(")"),Ut=o("Fixed multiple issues related to COBOL conditional compilation that caused incorrect syntax error messages. ("),Tt={href:"https://github.com/IBM/zopeneditor-about/issues/154",target:"_blank",rel:"noopener noreferrer"},Dt=o("Issue 154"),Xt=o(", "),Nt={href:"https://github.com/IBM/zopeneditor-about/issues/329",target:"_blank",rel:"noopener noreferrer"},Jt=o("Issue 329"),Ht=o(")"),Vt=e("h2",{id:"_3-3-1-2023-11-07",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-3-1-2023-11-07","aria-hidden":"true"},"#"),o(" 3.3.1 - 2023/11/07")],-1),qt=e("ul",null,[e("li",null,"Corrected the default URL for the IBM watsonx Code Assistant for Z server setting.")],-1),Wt=e("h2",{id:"_3-3-0-2023-10-25",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-3-0-2023-10-25","aria-hidden":"true"},"#"),o(" 3.3.0 - 2023/10/25")],-1),Gt=o("New: IBM watsonx Code Assistant uses generative AI to accelerate code generation and increase developer productivity for application modernization. IBM watsonx Code Assistant for Z is now enabled in IBM Z Open Editor to drive the selective and incremental transformation of COBOL business services into well-architected high-quality Java code. It uses the inventory and analysis tools of IBM Application Discovery and Delivery Intelligence (ADDI) to support development teams in refactoring business services in COBOL, transforming COBOL code to Java code, and validating the resulting outcome. Learn more and sign up for a trial at "),jt={href:"https://www.ibm.com/products/watsonx-code-assistant-zos",target:"_blank",rel:"noopener noreferrer"},Yt=o("https://www.ibm.com/products/watsonx-code-assistant-zos"),Qt=o("."),Kt=e("p",null,"Other fixes and enhancements in this release:",-1),$t=i("
    • Added support for CICS v6.2 Beta to COBOL and PL/I language servers.
    • Added support for line and block comment shortcuts in PL/I and REXX.
    • Machine instruction statements in HLASM are now identified when the number of operands is incorrect. Assembler instructions are not supported at the moment.
    • Improved the parsing behavior of HLASM language servers, particularly around continuation lines. Symbols that are continued should now have that reflected when you hover over references. Symbols that are used in continuation lines now support language functionalities, such as hover, Go to Definition, and Find References.
    • Fixed the bug where lowercase and mixed-case macros were not correctly displaying document links in HLASM.
    • Added support for internal macros that are declared in an HLASM file. Macros that are declared in an HLASM file now support code completion, hover, and Go to Definition in the file. Note that macros declared with the same name as a default SYS1.MACLIB macro will take precedence over the default macro.
    • Added .mac as another default file extension for HLASM program files.
    • Improved syntax highlighting around %INCLUDE statements in REXX.
    • A ZAPP file will now be automatically generated if none can be found in any of your workspaces when a COBOL, PL/I, HLASM, or REXX file is opened for the first time. This ZAPP file will search in all your local folders for include files, such as copybooks, so you should modify it for a more specific path or remote MVS locations afterwards. This behavior can be disabled with the new user setting "zopeneditor.zapp.generateZappOnDemand". Include file statements in all of these languages now also have the Quick Fix menu entry to open ZAPP files for troubleshooting and to open the ZAPP documentation for quick reference.
      • ",9),es=o('Changed the behavior of the "Run user build with full upload" command to now upload also all files that are specified with '),os=e("code",null,"additionalDependencies",-1),ts=o(" in the ZAPP file. ("),ss={href:"https://github.com/IBM/zopeneditor-about/issues/297",target:"_blank",rel:"noopener noreferrer"},is=o("Issue 297"),ns=o(")"),rs=o("Fixed the issue where user build did not properly filter search results for logs. ("),as={href:"https://github.com/IBM/zopeneditor-about/issues/353",target:"_blank",rel:"noopener noreferrer"},ls=o("Issue 353"),ds=o(")"),hs=e("li",null,"Fixed the issue where user build related editor menu items and command palette items were displayed for COBOL and PL/I include files.",-1),cs=o("Fixed the issue where user build menu items and command palette items were not displayed for VS Code 1.76 and earlier versions. ("),us={href:"https://github.com/IBM/zopeneditor-about/issues/349",target:"_blank",rel:"noopener noreferrer"},_s=o("Issue 349"),ps=o(")"),fs=o("Fixed the issue where user build did not handle SSH keys for authentication in Zowe SSH profile. ("),gs={href:"https://github.com/IBM/zopeneditor-about/issues/355",target:"_blank",rel:"noopener noreferrer"},ms=o("Issue 355"),bs=o(")"),ws=i("
    • Fixed the issue with RSE API in Zowe Explorer where the user was prompted for username and password when using a token for authentication.
    • Added the ability to change owner, group, and permissions of Unix files on RSE CLI.
    • Added the ability to check a user's password expiration date with RSE CLI.
    • Fixed the issue where default RSE profiles were not displayed by default in Zowe Explorer's tree views when the team configuration profile did not contain z/OSMF profiles.
    • Added functionalities for RSE profiles, including copying files and directories in z/OS UNIX System Services, copying data sets, and cancelling jobs.
    • Added support for editing attributes in z/OS UNIX System Services for RSE profiles in Zowe Explorer.
    • Fixed the issue where RSE API Plug-in for Zowe CLI returned duplicate values when executing the list all members command using wildcard pattern parameters.
    • Fixed the issue where RSE API Plug-in for Zowe CLI did not return the correct error messages when executing the list or download all members command using incorrect parameters.
    • Fixed the issue where the Zowe profile status bar was not updated after edits were made to the team configuration profiles for RSE API profiles.
    • Added job timestamp to the output of the list jobs command for RSE API Plug-in for Zowe CLI when running commands against RSE API server v1.1.3.
      • ",10),Is=e("h2",{id:"_3-2-3-2023-10-11",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-2-3-2023-10-11","aria-hidden":"true"},"#"),o(" 3.2.3 - 2023/10/11")],-1),ys=o("Fixed the issue where Z Open Editor showed an incorrect warning about initializing secure credentials. ("),vs={href:"https://github.com/IBM/zopeneditor-about/issues/359",target:"_blank",rel:"noopener noreferrer"},xs=o("Issue 359"),Ss=o(")"),As=e("li",null,"Fixed the issue where RSE API profiles that were using token-based authentication stored token details incorrectly in certain situations.",-1),Bs=e("li",null,"Fixed the issue where building projects that were not managed with Git produced Git errors. The fix changes the behavior that when no Git repository can be found then all .gitattributes files are ignored.",-1),Cs=e("h2",{id:"_3-2-2-2023-09-15",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-2-2-2023-09-15","aria-hidden":"true"},"#"),o(" 3.2.2 - 2023/09/15")],-1),Es=o("Fixed the issue in COBOL where "),Os=e("code",null,"DEFINE(compilation-variable-name)",-1),ks=o(" was not applying the default value "),Ls=e("code",null,"B'1'",-1),Ms=o(". (part of "),zs={href:"https://github.com/IBM/zopeneditor-about/issues/154",target:"_blank",rel:"noopener noreferrer"},Ps=o("Issue 154"),Rs=o(")"),Fs=o("Fixed the issue in COBOL where COBOL keywords are not able to be used as compilation-variable-name before a "),Zs=e("code",null,">>DEFINE",-1),Us=o(" statement. (part of "),Ts={href:"https://github.com/IBM/zopeneditor-about/issues/154",target:"_blank",rel:"noopener noreferrer"},Ds=o("Issue 154"),Xs=o(")"),Ns=o("Fixed the issue where IBM User Build was not properly filtering search results for logs. ("),Js={href:"https://github.com/IBM/zopeneditor-about/issues/353",target:"_blank",rel:"noopener noreferrer"},Hs=o("Issue 353"),Vs=o(")"),qs=e("li",null,"Fixed the issue where RSE API plugin for Zowe CLI returned duplicate values for list all members.",-1),Ws=e("li",null,"Fixed the issue where the Zowe profile status bar field would not get updated after making edits to RSE API profiles in team configuration files.",-1),Gs=e("li",null,"Security fix limiting telemetry data volumes.",-1),js=e("h2",{id:"_3-2-1-2023-07-19",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-2-1-2023-07-19","aria-hidden":"true"},"#"),o(" 3.2.1 - 2023/07/19")],-1),Ys=e("li",null,[o("Added syntax and content assist support for the "),e("code",null,"LOCATION"),o(" options ("),e("code",null,"LOC24"),o(" and "),e("code",null,"LOC31"),o(") in the "),e("code",null,"GETMAIN64 EXEC CICS"),o(" embedded CICS command.")],-1),Qs=o("Fixed the issue where the PL/I "),Ks=e("code",null,"PROCESS MAR/MARGIN",-1),$s=o(" options did not accept a third parameter. ("),ei={href:"https://github.com/IBM/zopeneditor-about/issues/344",target:"_blank",rel:"noopener noreferrer"},oi=o("Issue 344"),ti=o(")"),si=e("li",null,[o("Fixed issues in the HLASM outline view to correctly handle duplicate elements such as "),e("code",null,"CSECTS"),o(" and "),e("code",null,"DSECTS"),o(" that are continued. Symbols that are reassigned will still point to the final declaration to prevent the outline from becoming overcrowded.")],-1),ii=o("Fixed the issue in User Build where menu items and commands were not available when VS Code 1.76 or earlier versions were used. ("),ni={href:"https://github.com/IBM/zopeneditor-about/issues/349",target:"_blank",rel:"noopener noreferrer"},ri=o("Issue 349"),ai=o(")"),li=e("li",null,"Fixed the issue in User Build for COBOL and PL/I where a copybook or include file with a name that was a substring of another copybook or include file name was not identified as a dependency correctly.",-1),di=e("li",null,"Fixed the issue that prevented the default RSE API Zowe CLI profiles to be displayed in Zowe Explorer's tree views at startup when Zowe team configuration profile files did not contain a z/OSMF profile.",-1),hi=e("h2",{id:"_3-2-0-2023-06-16",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-2-0-2023-06-16","aria-hidden":"true"},"#"),o(" 3.2.0 - 2023/06/16")],-1),ci=o("Added support for the COBOL v6.4 April 2023 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this "),ui={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/yuan-jie-song1/2023/04/28/april-2023-documentation-refresh-for-enterprise-co",target:"_blank",rel:"noopener noreferrer"},_i=o("blog post"),pi=o(" for details."),fi=o("Fixed the coloring of the keyword "),gi=e("code",null,"NOT",-1),mi=o(" in COBOL. ("),bi={href:"https://github.com/IBM/zopeneditor-about/issues/328",target:"_blank",rel:"noopener noreferrer"},wi=o("Issue 328"),Ii=o(")"),yi=o("Fixed the missing syntax errors when statements (such as "),vi=e("code",null,"COPY",-1),xi=o(") start to the left of Area A and overflowing data names (for example in "),Si=e("code",null,"USING",-1),Ai=o(" statements) start to left of Area B. ("),Bi={href:"https://github.com/IBM/zopeneditor-about/issues/340",target:"_blank",rel:"noopener noreferrer"},Ci=o("Issue 340"),Ei=o(")"),Oi=o("Fix the issue where comments were misinterpreted within a COPY statement when using an empty quoted pseudo text and the == identifier. ("),ki={href:"https://github.com/IBM/zopeneditor-about/issues/248",target:"_blank",rel:"noopener noreferrer"},Li=o("Issue 248"),Mi=o(")"),zi=o("Removed the ability to perform Number and Unnumber actions when COBOL Language Server is not running. ("),Pi={href:"https://github.com/IBM/zopeneditor-about/issues/189",target:"_blank",rel:"noopener noreferrer"},Ri=o("Issue 189"),Fi=o(")"),Zi=o("Fixed certain COBOL words not highlighting correctly when placed at the end of a line. ("),Ui={href:"https://github.com/IBM/zopeneditor-about/issues/346",target:"_blank",rel:"noopener noreferrer"},Ti=o("Issue 346"),Di=o(")"),Xi=o("Added support for the PL/I v6.1 March 2023 Refresh with updated syntax highlighting, outline view, content assist, real-time syntax checking, and other language related features. See this "),Ni={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/di-hu1/2023/03/09/march-2023-documentation-refresh",target:"_blank",rel:"noopener noreferrer"},Ji=o("blog post"),Hi=o(" for details."),Vi=o("Fixed the issue that caused PL/I comments to show a report when starting in column 1. ("),qi={href:"https://github.com/IBM/zopeneditor-about/issues/135",target:"_blank",rel:"noopener noreferrer"},Wi=o("Issue 135"),Gi=o(")"),ji=e("li",null,"Fixed the issue with PL/I code completion when a variable is in the same column with a DCL statement.",-1),Yi=e("li",null,"Added preview hovers and clickable hyperlinks to open include files in REXX.",-1),Qi=e("li",null,[o("Added support for jump targets as well as "),e("code",null,"RSECT"),o(", "),e("code",null,"LOCTR"),o(", and "),e("code",null,"COM"),o(" control sections in the HLASM outline view.")],-1),Ki=e("li",null,"Fixed the issue where preview hovers failed to load for HLASM COPY statements when the copied document was closed after previously being opened by using the hover's hyperlink.",-1),$i=o('Added the user settings "zopeneditor..disableProblems" for each language to enable/disable the Problems view and syntax errors shown within the editor while maintaining other language features. It will allow users to continue working in the program with some language features despite parsing issues. This will not work in all circumstances as some syntax errors will also break other language features. ('),en={href:"https://github.com/IBM/zopeneditor-about/issues/199",target:"_blank",rel:"noopener noreferrer"},on=o("Issue 199"),tn=o(" and "),sn={href:"https://github.com/IBM/zopeneditor-about/issues/203",target:"_blank",rel:"noopener noreferrer"},nn=o("Issue 203"),rn=o(")"),an=e("li",null,[o("Added the ability to define custom ZAPP variables in your personal user or workspace settings. Define variables in a new mappings table under "),e("code",null,"zopeneditor.zapp.variables"),o(" in the VS Code settings editor and then reference them in your ZAPP files with "),e("code",null,"${variable-name}"),o(". For example, define a variable here called "),e("code",null,"HLQ"),o(" with a value that represents your personal high-level qualifier on z/OS MVS. In your ZAPP file, reference it in a property group's location entry, such as "),e("code",null,"${HLQ}.COBOL.COPYBOOKs"),o(".")],-1),ln=e("li",null,"Fixed a copybook and include file watcher limitation about file precedence in remote and local non-syslib libraries.",-1),dn=o('Added the user setting "zopeneditor.zowe.maximumParallelFileDownloads" to specify how many parallel downloads Z Open Editor should perform when requesting include files from MVS. This will help minimize address spaces being allocated by z/OSMF. The default value of the setting is 5, and the maximum value is 10. Set it to 1 to disable parallel downloads. ('),hn={href:"https://github.com/IBM/zopeneditor-about/issues/134",target:"_blank",rel:"noopener noreferrer"},cn=o("Issue 134"),un=o(")"),_n=o('Added the user setting "zopeneditor.zowe.listBeforeDownload" to enable Z Open Editor to first search for the existence of a data set member before trying to download it when resolving include files. This will slow down performance, but will cause less logging on z/OS when using z/OSMF. The default is off to preserve performance. ('),pn={href:"https://github.com/IBM/zopeneditor-about/issues/134",target:"_blank",rel:"noopener noreferrer"},fn=o("Issue 134"),gn=o(")"),mn=e("li",null,"Fixed the issue where COBOL copybook requests were not sent in parallel in certain cases where Unix-style line endings were used on Windows.",-1),bn=e("li",null,"Fixed the issue where COBOL and PL/I include file requests were sometimes sent twice if a document could not be found.",-1),wn=o("Fixed the issue that language server errors and exceptions caused by a timing issue are displayed. ("),In={href:"https://github.com/IBM/zopeneditor-about/discussions/332",target:"_blank",rel:"noopener noreferrer"},yn=o("Issue 332"),vn=o(")"),xn=e("li",null,"Fixed the issue where COPY or INCLUDE statements using custom libraries were in some cases resolved with syslib libraries.",-1),Sn=e("li",null,"Improved the folder watching performance. When folders within the scope of the current ZAPP property groups are deleted or created, open program files will be re-parsed instead of a complete extension restart.",-1),An=o("Added the ability for User Build to automatically run the "),Bn=e("code",null,"git check-attr",-1),Cn=o(" command in the background to evaluate "),En=e("code",null,".gitattributes",-1),On=o(" in any folder of the workspace to upload files to UNIX System Services with the correct file encoding. If Git is not installed or cannot be found by the editor, Z Open Editor will continue trying to evaluate encoding itself. ("),kn={href:"https://github.com/IBM/zopeneditor-about/issues/331",target:"_blank",rel:"noopener noreferrer"},Ln=o("Issue 331"),Mn=o(")"),zn=i("
    • Fixed the issue in User Build where files specified in a ZAPP file as additionalDependencies were not converted and tagged correctly when being uploaded to UNIX System Services.
    • Fixed the issue where User Build failed to run when dbbLogDir does not exist on UNIX System Services.
    • Added a warning message to the User Build output view to inform the user when the language server is stopped, because the language server will then not be able to compute dependencies such as copybooks and cannot upload them to z/OS.
    • Fixed the issue where User Build would not download any log files when the logFilePatterns property was not specified in the ZAPP file. Added a default that will download all files that match the pattern *.log.
      • ",4),Pn=o("Fixed an issue where user build menu was not always hidden when user build was disabled via settings. ("),Rn={href:"https://github.com/IBM/zopeneditor-about/issues/347",target:"_blank",rel:"noopener noreferrer"},Fn=o("Issue 347"),Zn=o(")"),Un=e("li",null,"Fixed an issue where ZAPP and ZCodeFormat code snippets would not show when editing in multi-root workspaces.",-1),Tn=e("li",null,"Updated dependencies for security audits.",-1),Dn=e("li",null,"Added support for JCL symbols as a parameter for jobs on RSE CLI.",-1),Xn=e("li",null,"Fixed an issue when saving files to z/OS with Zowe Explorer using RSE API and resolving conflicts with changes done by other users to the same file. VS Code will now properly show the conflicts in its differences editor allowing you to merge and save.",-1),Nn=e("h2",{id:"_3-1-1-2023-03-30",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-1-1-2023-03-30","aria-hidden":"true"},"#"),o(" 3.1.1 - 2023/03/30")],-1),Jn=e("li",null,"Fixed an issue with COBOL language code completion where code completion was not working on the first line of a COBOL file.",-1),Hn=o("Added support for "),Vn=e("code",null,"$",-1),qn=o(" and "),Wn=e("code",null,"<",-1),Gn=o("/"),jn=e("code",null,">",-1),Yn=o(" to be used as pseudo-text boundaries for the REPLACING strings in COBOL copybooks. ("),Qn={href:"https://github.com/IBM/zopeneditor-about/issues/305",target:"_blank",rel:"noopener noreferrer"},Kn=o("Issue 305"),$n=o(")"),er=o("Fixed an issue where COBOL literals were not being highlighted correctly when single quotes and double quotes were mixed. ("),or={href:"https://github.com/IBM/zopeneditor-about/issues/308",target:"_blank",rel:"noopener noreferrer"},tr=o("Issue 308"),sr=o(")"),ir=o("Fixed an issue where the connection to the language server got disposed showing errors in the output view. ("),nr={href:"https://github.com/IBM/zopeneditor-about/discussions/332",target:"_blank",rel:"noopener noreferrer"},rr=o("Issue 332"),ar=o(")"),lr=e("li",null,"Fixed an issue where COBOL copybook requests did not download remote copybooks in parallel for non-syslib libraries.",-1),dr=o("Fixed an issue with "),hr=e("code",null,".gitattributes",-1),cr=o(" where "),ur=e("code",null,"*",-1),_r=o(" could not be used as a pattern for encoding the selection of files. ("),pr={href:"https://github.com/IBM/zopeneditor-about/issues/331",target:"_blank",rel:"noopener noreferrer"},fr=o("Issue 331"),gr=o(")"),mr=o("Fixed an issue where the Zowe team configuration's encoding property was not used when no "),br=e("code",null,".gitattributes",-1),wr=o(" file was present or no match was found. ("),Ir={href:"https://github.com/IBM/zopeneditor-about/issues/331",target:"_blank",rel:"noopener noreferrer"},yr=o("Issue 331"),vr=o(")"),xr=o("Fixed an issue where User Build on Windows uploaded remote copybooks to USS. ("),Sr={href:"https://github.com/IBM/zopeneditor-about/issues/333",target:"_blank",rel:"noopener noreferrer"},Ar=o("Issue 333"),Br=o(")"),Cr=e("li",null,"Updated Zowe and third-party dependencies addressing security scan results.",-1),Er=e("h2",{id:"_3-1-0-2023-03-10",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-1-0-2023-03-10","aria-hidden":"true"},"#"),o(" 3.1.0 - 2023/03/10")],-1),Or=o("Added support for the PL/I v6.1 October 2022 Refresh with updated syntax highlighting, outline view, real-time syntax checking, and other language related features. See this "),kr={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/di-hu1/2022/10/27/october-2022-documentation-refresh-for-enterprise",target:"_blank",rel:"noopener noreferrer"},Lr=o("blog post"),Mr=o(" for details."),zr=o("Added support for using comma in the DEFINE compiler option syntax for COBOL. ("),Pr={href:"https://github.com/IBM/zopeneditor-about/issues/278",target:"_blank",rel:"noopener noreferrer"},Rr=o("Issue 278"),Fr=o(")"),Zr=e("li",null,"Added code completion support for statements containing Unicode Strings in COBOL.",-1),Ur=e("li",null,"Added code completion support for Compiler Directing statements (Compiler Options) in COBOL.",-1),Tr=e("li",null,[o("Added code completion support for "),e("code",null,"ENABLE PROGAM"),o(" in "),e("code",null,"EXEC CICS"),o(" Statements in COBOL.")],-1),Dr=o("Fixed an issue with COBOL where CBL or PROCESS service directive was not being recognized. ("),Xr={href:"https://github.com/IBM/zopeneditor-about/issues/253",target:"_blank",rel:"noopener noreferrer"},Nr=o("Issue 253"),Jr=o(")"),Hr=o("Fixed an issue with COBOL language showing false syntax errors for not correctly handling condition expressions on compilation variables in boolean format compared with the constant b'0' or b'1'. ("),Vr={href:"https://github.com/IBM/zopeneditor-about/issues/321",target:"_blank",rel:"noopener noreferrer"},qr=o("Issue 321"),Wr=o(")"),Gr=o("Reverted syntax highlighting changes from last release for unsupported Boolean literals ("),jr=e("code",null,"b",-1),Yr=o(" and "),Qr=e("code",null,"bx",-1),Kr=o("). The IBM COBOL compiler currently does not support them. ("),$r={href:"https://github.com/IBM/zopeneditor-about/issues/308",target:"_blank",rel:"noopener noreferrer"},ea=o("Issue 308"),oa=o(")"),ta=e("li",null,[o("Added new option "),e("code",null,"alignToClauses"),o(" to "),e("code",null,"zcodeformat.yaml"),o(" files to support aligning TO clauses, aligning INTO clauses, and aligning TO clauses into column.")],-1),sa=o("Added file watching support for all languages so that programs with INCLUDE and COPY statements are now automatically re-parsed when local included files or copybooks are edited, created, or deleted. ("),ia={href:"https://github.com/IBM/zopeneditor-about/issues/108",target:"_blank",rel:"noopener noreferrer"},na=o("Issue 108"),ra=o("). See "),aa={href:"https://ibm.github.io/zopeneditor-about/Docs/knownissues.html",target:"_blank",rel:"noopener noreferrer"},la=o("Known Issues"),da=o(" for a limitation involving file precedence in remote and local non-syslib libraries."),ha=o("Improved performance for loading PL/I include files. Include files that are being downloaded from a remote z/OS system will now resolve much faster as download requests are performed in parallel to a maximum of five files at once. ("),ca={href:"https://github.com/IBM/zopeneditor-about/issues/269",target:"_blank",rel:"noopener noreferrer"},ua=o("Issue 269"),_a=o(")"),pa=o("Significantly improved performance for searching for local copybooks and include files via property groups that use glob patterns that expand to many results. ("),fa={href:"https://github.com/IBM/zopeneditor-about/issues/315",target:"_blank",rel:"noopener noreferrer"},ga=o("Issue 315"),ma=o(", "),ba={href:"https://github.com/IBM/zopeneditor-about/issues/293",target:"_blank",rel:"noopener noreferrer"},wa=o("Issue 293"),Ia=o(")"),ya=o("Fixed an issue with no hover content of the copybook when COBOL source contains any errors in the COBOL program. ("),va={href:"https://github.com/IBM/zopeneditor-about/issues/300",target:"_blank",rel:"noopener noreferrer"},xa=o("Issue 300"),Sa=o(")"),Aa=o("Fixed a bug where large copybooks and include files were not completely resolved, resulting in errors such as "),Ba=e("code",null,"Unable to resolve reference",-1),Ca=o(" to variables included from copybooks. ("),Ea={href:"https://github.com/IBM/zopeneditor-about/issues/313",target:"_blank",rel:"noopener noreferrer"},Oa=o("Issue 313"),ka=o(")"),La=e("li",null,"Fixed a bug when editing REXX programs with remote REXX include files, which were resolved and saved with an incorrect file extension.",-1),Ma=e("li",null,"Full support for all the new Zowe Explorer JES filtering options when using RSE API profiles.",-1),za=o("Fixed issue where user build logs in nested directories were not being found ("),Pa={href:"https://github.com/IBM/zopeneditor-about/issues/296",target:"_blank",rel:"noopener noreferrer"},Ra=o("Issue 296"),Fa=o(")."),Za=o("Updated the user build output view and log file formatter to include timestamps when Z Open Editor's log level ("),Ua=e("code",null,"zopeneditor.logger",-1),Ta=o(") is set to "),Da=e("code",null,"DEBUG",-1),Xa=o(" to help with trouble-shooting and measuring build times. ("),Na={href:"https://github.com/IBM/zopeneditor-about/issues/292",target:"_blank",rel:"noopener noreferrer"},Ja=o("Issue 292"),Ha=o(")"),Va=i("
    • Added support for path name specification for .gitattributes in IBM User Build.
    • Added new option for tagging files using working-tree-encoding os=zos in .gitattributes in IBM User Build as an alternative to zos-working-tree-encoding.
    • Addressed a concern that code snippets for ZAPP and ZCodeFormat files appeared in the code completion for all YAML files being edited. We therefore removed them from the Snippet Gallery and provided them as pure context-sensitive code completion items for <ctrl-space>.
      • ",3),qa=o("Z Open Editor is now available to install as a web extension with limited capabilities when using Visual Studio Code in a browser, such as "),Wa=e("code",null,"vscode.dev",-1),Ga=o(" or "),ja=e("code",null,"github.dev",-1),Ya=o(". Try it by going to "),Qa={href:"https://vscode.dev/github/IBM/zopeneditor-sample",target:"_blank",rel:"noopener noreferrer"},Ka=o("https://vscode.dev/github/IBM/zopeneditor-sample"),$a=o(" and confirming to install the recommended extensions."),el=e("h2",{id:"_3-0-1-2023-01-18",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-0-1-2023-01-18","aria-hidden":"true"},"#"),o(" 3.0.1 - 2023/01/18")],-1),ol=o("Performance improvements for loading COBOL copybooks. Copybooks that are being downloaded from a remote z/OS system will now resolve much faster as download requests are performed in parallel to a maximum of five files at once. PL/I will be updated with this capability in a later release. ("),tl={href:"https://github.com/IBM/zopeneditor-about/issues/269",target:"_blank",rel:"noopener noreferrer"},sl=o("Issue 269"),il=o(")"),nl=o('Fixed invalid "REDEFINES clause must begin in Area B" error shown in COBOL editor when using the REPLACING clause with a REDEFINES. ('),rl={href:"https://github.com/IBM/zopeneditor-about/issues/287",target:"_blank",rel:"noopener noreferrer"},al=o("Issue 287"),ll=o(")"),dl=o("Fixed issues with COBOL syntax highlighting when using literal delimiters. Respective language server fixes will be provided at a later date. ("),hl={href:"https://github.com/IBM/zopeneditor-about/issues/308",target:"_blank",rel:"noopener noreferrer"},cl=o("Issue 308"),ul=o(")"),_l=o("Fixed spelling in COBOL code snippets. ("),pl={href:"https://github.com/IBM/zopeneditor-about/issues/286",target:"_blank",rel:"noopener noreferrer"},fl=o("Issue 286"),gl=o(")"),ml=o("Fixed issue with "),bl=e("code",null,"%Replace",-1),wl=o(" in PL/I when using a minus sign in expression. ("),Il={href:"https://github.com/IBM/zopeneditor-about/issues/299",target:"_blank",rel:"noopener noreferrer"},yl=o("Issue 299"),vl=o(")"),xl=o("Fixed an issue in User Build evaluating file names with special characters, such as "),Sl=e("code",null,"$",-1),Al=o(", in command shell expression. The DBB Daemon might also be effected by this problem. Remove the "),Bl=e("code",null,"-DBB_PERSONAL_DAEMON",-1),Cl=o(" command line parameter from the ZAPP file if you still run into this problem. ("),El={href:"https://github.com/IBM/zopeneditor-about/issues/288",target:"_blank",rel:"noopener noreferrer"},Ol=o("Issue 288"),kl=o(")"),Ll=o("Fixed an issue with User Build not downloading log files for programs with lower or mixed case filenames, because "),Ml={href:"https://github.com/IBM/dbb-zappbuild",target:"_blank",rel:"noopener noreferrer"},zl=o("dbb-zappbuild"),Pl=o(" will automatically capitalize log file names. User Build will now also automatically capitalize the build file name when using the "),Rl=e("code",null,"${buildFile.basename}",-1),Fl=o(" variable under "),Zl=e("code",null,"logFilePatterns",-1),Ul=o(" in the ZAPP file."),Tl=e("li",null,"Fixed syntax error in ZAPP code snippet for the dbb user build profile.",-1),Dl=e("li",null,"Fixed issues in our RSE API support when using special characters in z/OS file or directory names.",-1),Xl=e("li",null,"Fixed bugs and improved the usability of the change password command in the IBM RSE API Plug-in for Zowe CLI.",-1),Nl=e("li",null,"Fixed error being thrown in Zowe Explorer when RSE API list of all members returns no members.",-1),Jl=e("h2",{id:"_3-0-0-2022-11-22",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_3-0-0-2022-11-22","aria-hidden":"true"},"#"),o(" 3.0.0 - 2022/11/22")],-1),Hl=e("h3",{id:"breaking-changes",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#breaking-changes","aria-hidden":"true"},"#"),o(" Breaking Changes")],-1),Vl=o("For more details on breaking changes and the required manual migration steps see our "),ql={href:"https://ibm.github.io/zopeneditor-about/Docs/zopeneditor_v3.html",target:"_blank",rel:"noopener noreferrer"},Wl=o("user documentation"),Gl=o("."),jl=o("Z Open Editor now requires as a minimum a Java 11 runtime for running language servers. Users must upgrade their installed Java 8 runtime or Z Open Editor's language capabilities will not be available. See the "),Yl={href:"https://ibm.github.io/zopeneditor-about/Docs/getting_started.html",target:"_blank",rel:"noopener noreferrer"},Ql=o("documentation"),Kl=o(" for the recommend Java Runtime Environments that you can use."),$l=e("li",null,'ZAPP files are now replacing various user settings and cannot be disabled enabled anymore. The user setting "zopeneditor.zapp.enabled" has been removed.',-1),ed=e("li",null,[o("Property Groups have been removed from VS Code user and workspace settings. The setting "),e("code",null,'"zopeneditor.propertygroups"'),o(" is no longer available. Users must now use ZAPP files for specifying locations for include files. When only using Zowe Explorer to edit program files you need create a workspace folder with a ZAPP file as well.")],-1),od=o("Property Groups have been updated to contain references to local files as well as remote MVS files in the same property group item applying the same compiler options to each. The schema for a property group item has changed and users must update their ZAPP files. Please, check the "),td={href:"https://ibm.github.io/zopeneditor-about/Docs/setting_propertygroup.html",target:"_blank",rel:"noopener noreferrer"},sd=o("documentation"),id=o(" for the details and our "),nd={href:"https://ibm.github.io/zopeneditor-about/Docs/zopeneditor_v3.html",target:"_blank",rel:"noopener noreferrer"},rd=o("migration page"),ad=o(" for how to upgrade."),ld=o("User Build settings have been updated to allow more configuration options such as allowing glob patterns to define files for uploading and downloading. See the "),dd={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-building-cobol-pli-hlasm-programs-user-build",target:"_blank",rel:"noopener noreferrer"},hd=o("IBM Wazi for VS Code User Build documentation"),cd=o(" for more details."),ud=e("h3",{id:"other-changes-and-fixes",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#other-changes-and-fixes","aria-hidden":"true"},"#"),o(" Other changes and fixes")],-1),_d=o("Fixed syntax of "),pd=e("code",null,"EXEC CICS INQUIRE SYSTEM MAXOPENTCBS",-1),fd=o(". ("),gd={href:"https://github.com/IBM/zopeneditor-about/issues/257",target:"_blank",rel:"noopener noreferrer"},md=o("Issue 257"),bd=o(")"),wd=i("
    • Added missing CICS v6.1 INQUIRE SYSTEM options: SRRTASKS, MEMLIMIT and MQCONN that used to cause syntax errors.
    • Fixed CICS v6.1 EXEC CICS CREATE DB2ENTRY ATTRIBUTES option incorrectly flagged as an error.
    • Fixed CICS v6.1 EXEC CICS SET TAGS REFRESH with NOHANDLE and RESP options incorrectly flagged as an error.
      • ",3),Id=o("Fixed an issue in COBOL syntax checking for a working storage variable starting with "),yd=e("code",null,"REMARKS",-1),vd=o(". It would be incorrectly identified as a REMARKS paragraph. ("),xd={href:"https://github.com/IBM/zopeneditor-about/issues/276",target:"_blank",rel:"noopener noreferrer"},Sd=o("Issue 276"),Ad=o(")"),Bd=o("Fixed an issue with COBOL Syntax Highlighting in the sequence number fields (1-6 and 73-80). ("),Cd={href:"https://github.com/IBM/zopeneditor-about/issues/193",target:"_blank",rel:"noopener noreferrer"},Ed=o("Issue 193"),Od=o(")"),kd=o("Fixed a NullPointerException caused by the PL/I Code Folding feature when opening copybook/include file from PL/I Editor. ("),Ld={href:"https://github.com/IBM/zopeneditor-about/issues/277",target:"_blank",rel:"noopener noreferrer"},Md=o("Issue 277"),zd=o(")"),Pd=o("Fixed a NullPointerException caused by the PL/I Code Folding feature when the currently selected word matches a code completion suggestion that would alter the outline view. ("),Rd={href:"https://github.com/IBM/zopeneditor-about/issues/283",target:"_blank",rel:"noopener noreferrer"},Fd=o("Issue 283"),Zd=o(")"),Ud=e("li",null,[o("Fixed an issue with syntax checking for PL/I related to function parameters of type File as well as a "),e("code",null,"DEFINE ORDINAL"),o(" containing signed integers in the VALUE attribute.")],-1),Td=e("li",null,"Added REXX syntax highlighting for matching pairs of parenthesis. Auto-close parenthesis when typing.",-1),Dd=e("li",null,"Fixed an issue with improper error logging regarding the list command in RSE CLI.",-1),Xd=e("h2",{id:"_2-2-0-2022-09-20",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_2-2-0-2022-09-20","aria-hidden":"true"},"#"),o(" 2.2.0 - 2022/09/20")],-1),Nd=o(`Fixed User Build and the RSE API CLI's upload command to correctly encode file names with special characters. Files such as "T@A#R$C" will now be correctly uploaded to USS. (`),Jd={href:"https://github.com/IBM/zopeneditor-about/issues/266",target:"_blank",rel:"noopener noreferrer"},Hd=o("Issue 266"),Vd=o(")"),qd=o("Performance improvements for the REXX language server via parser optimizations. ("),Wd={href:"https://github.com/IBM/zopeneditor-about/issues/256",target:"_blank",rel:"noopener noreferrer"},Gd=o("Issue 256"),jd=o(")"),Yd=e("li",null,"Updated the REXX hover hyperlinks to point to the z/OS 2.5.0 reference.",-1),Qd=e("li",null,"Improved performance and reliability for the HLASM language server by implementing cancellation support for requests that are no longer valid, as well as optimizing handling of document-link requests for macros.",-1),Kd=e("li",null,"Fixed a bug where mixed case variables were not handled correctly in HLASM.",-1),$d=e("li",null,"Fixed a bug where hovers sometimes did not show the correct code snippet for SYS1.MACLIB macros in HLASM.",-1),eh=o("Fixed a bug where document link underlines were not showing for HLASM macros when a file is first opened. Similar to a problem fixed for COBOL in ("),oh={href:"https://github.com/IBM/zopeneditor-about/issues/81",target:"_blank",rel:"noopener noreferrer"},th=o("Issue 81"),sh=o(") and ("),ih={href:"https://github.com/IBM/zopeneditor-about/issues/114",target:"_blank",rel:"noopener noreferrer"},nh=o("Issue 114"),rh=o(")."),ah=e("li",null,'Fixed a bug where "Failed to fetch COPYBOOK" errors were causing slowdowns across the HLASM language server.',-1),lh=e("li",null,"Added initial support for code folding for control statements to the PL/I language server.",-1),dh=e("h2",{id:"_2-1-1-2022-08-14",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_2-1-1-2022-08-14","aria-hidden":"true"},"#"),o(" 2.1.1 - 2022/08/14")],-1),hh=o("Added support for running User Builds with nested copybooks for COBOL. "),ch={href:"https://github.com/IBM/zopeneditor-about/issues/251",target:"_blank",rel:"noopener noreferrer"},uh=o("Issue 251"),_h=o("Fixed User Build issues with credential dialogs and storing credentials for remote include file resolution using z/OSMF or RSE API. ("),ph={href:"https://github.com/IBM/zopeneditor-about/issues/245",target:"_blank",rel:"noopener noreferrer"},fh=o("Issue 245"),gh=o(", "),mh={href:"https://github.com/IBM/zopeneditor-about/issues/255",target:"_blank",rel:"noopener noreferrer"},bh=o("Issue 255"),wh=o(")"),Ih=e("li",null,"Fixed User Build issues with credential dialogs and storing credentials for SSH commands when using z/OSMF.",-1),yh=o("Fixed User Build issues when attempting to build from workspaces with spaces in the file path. ("),vh={href:"https://github.com/IBM/zopeneditor-about/issues/252",target:"_blank",rel:"noopener noreferrer"},xh=o("Issue 252"),Sh=o(")"),Ah=o("Fixed various issues when using ZAPP and User Build in a multi-root workspace. You can now use multi-root workspaces as long as you use a single ZAPP file and provide it together with the application-conf folder in the same workspace as your program. Include files such as copybooks can be in many other multi-root workspace folders. The ZAPP file needs to specify property groups with a workspace folder relative path even for include files located in other workspaces. User Build with user settings in multi-root workspaces is not supported. Please, switch to ZAPP files. See our "),Bh={href:"https://github.com/IBM/zopeneditor-sample",target:"_blank",rel:"noopener noreferrer"},Ch=o("Sample GitHub repository"),Eh=i(" for more details and a examples for single-root workspaces, in the wazi-main branch as well as multi-root in the multiroot folder of the wazi-main branch. Also note, that for single as well as multi-root the value for the DBB buildScriptArgs parameter has changed for the --application parameter to be now just a relative path to the application-conf directory. So in most cases you can just use --application ., which makes it much easier as you do not have to provide the folder name of your workspace root in the ZAPP file anymore. Finally, the zopeneditor.userbuild.userSettings.localWorkspacePath user setting has been deprecated is not used anymore.",15),Oh=e("li",null,"Fixed an issue in the Z Open Editor output log not always reporting the correct Zowe profile management version in use.",-1),kh=e("li",null,"Fixed issue in the COBOL Code Formatter producing incorrect Area B alignments for USING statements.",-1),Lh=e("h2",{id:"_2-1-0-2022-06-14",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_2-1-0-2022-06-14","aria-hidden":"true"},"#"),o(" 2.1.0 - 2022/06/14")],-1),Mh=o("Added language support for COBOL v6.4, PL/I v6.1, and CICS v6.1 with updated syntax highlighting, outline view, real-time syntax checking, and other language related features. See our "),zh={href:"https://ibm.github.io/zopeneditor-about/Docs/language_references.html",target:"_blank",rel:"noopener noreferrer"},Ph=o("documentation"),Rh=o(" for details. ("),Fh={href:"https://github.com/IBM/zopeneditor-about/issues/240",target:"_blank",rel:"noopener noreferrer"},Zh=o("Issue 240"),Uh=o(")"),Th=o("Added COBOL UTF-8-specific syntax elements in textmate grammar ("),Dh={href:"https://github.com/IBM/zopeneditor-about/issues/241",target:"_blank",rel:"noopener noreferrer"},Xh=o("Issue 241"),Nh=o(")"),Jh=o("Added an experimental COBOL code formatter that can be configured similar to Prettier with a yaml or json file. Find more details in our documentation ("),Hh={href:"https://github.com/IBM/zopeneditor-about/issues/31",target:"_blank",rel:"noopener noreferrer"},Vh=o("Issue 31"),qh=o(")"),Wh=e("li",null,"Updated HLASM Instructions to match the set that was shipped with IBM z16.",-1),Gh=e("li",null,[o("Updated HLASM Macros to match the z/OS 2.5 SYS1.MACLIB. Switch the z/OS version back to 2.4 SYS1.MACLIB by using the user setting "),e("code",null,"zopeneditor.hlasm.zosMacrosVersion"),o(".")],-1),jh=o("Added "),Yh=e("code",null,".macasm",-1),Qh=o(" and "),Kh=e("code",null,".copyasm",-1),$h=o(" as default file extensions for HLASM. ("),ec={href:"https://github.com/IBM/zopeneditor-about/issues/220",target:"_blank",rel:"noopener noreferrer"},oc=o("Issue 220"),tc=o(")"),sc=o("Added "),ic=e("code",null,".bms",-1),nc=o(" as default file extensions for HLASM. ("),rc={href:"https://github.com/IBM/zopeneditor-about/issues/223",target:"_blank",rel:"noopener noreferrer"},ac=o("Issue 223"),lc=o(")"),dc=o("Fixed an error in the Problems View when a custom-defined problemMatcher was used when compiling HLASM code. ("),hc={href:"https://github.com/IBM/zopeneditor-about/issues/230",target:"_blank",rel:"noopener noreferrer"},cc=o("Issue 230"),uc=o(")"),_c=e("li",null,"Various fixes and refinements for HLASM syntax highlighting.",-1),pc=o("Added REXX include file support consistent with the other languages using Property Groups in ZAPP files. ("),fc={href:"https://github.com/IBM/zopeneditor-about/issues/172",target:"_blank",rel:"noopener noreferrer"},gc=o("Issue 172"),mc=o(")"),bc=o("Added a status bar item that displays the currently active Zowe profile used by Z Open Editor for remote include file resolution and IBM User Build. ("),wc={href:"https://github.com/IBM/zopeneditor-about/issues/165",target:"_blank",rel:"noopener noreferrer"},Ic=o("Issue 165"),yc=o(")"),vc=e("li",null,[o("Added support to filter the information displayed in the RSE CLI plugin command "),e("code",null,"zowe rse check jobs"),o(" that displays all active job address space information. This functionality is available in RSE API v1.0.9.")],-1),xc=e("li",null,[o("Added support for use of passphrase in "),e("code",null,"change password"),o(" command with RSE API v1.0.9.")],-1),Sc=e("h2",{id:"_2-0-3-2022-05-20",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_2-0-3-2022-05-20","aria-hidden":"true"},"#"),o(" 2.0.3 - 2022/05/20")],-1),Ac=e("li",null,"Fixed a synchronization issue that when saving syntactically correct ZAPP files the editor sometimes would still report errors.",-1),Bc=o("Fixed an issue in User Build related to file upload operations in which Z Open Editor would not evaluate the .gitattributes file correctly, not following the Git standard for precedences. ("),Cc={href:"https://github.com/IBM/zopeneditor-about/issues/236",target:"_blank",rel:"noopener noreferrer"},Ec=o("Issue 236"),Oc=o(")"),kc=o("Updated how User Build parses .gitattributes files dealing with more file formats such as Windows CRLF files and added more logging for the encoding matches found or not found. ("),Lc={href:"https://github.com/IBM/zopeneditor-about/issues/235",target:"_blank",rel:"noopener noreferrer"},Mc=o("Issue 235"),zc=o(")"),Pc=o("Added support for using the "),Rc=e("code",null,"ZOWE_CLI_HOME",-1),Fc=o(" environment variable to specify an alternative location for global team configuration files to Zowe Explorer 2.0.2 and Z Open Editor. ("),Zc={href:"https://github.com/IBM/zopeneditor-about/issues/238",target:"_blank",rel:"noopener noreferrer"},Uc=o("Issue 238"),Tc=o(")"),Dc=o("Fixed various errors that prevented Zowe Explorer and Z Open Editor to run in Eclipse Che especially plugin containers with Nodejs 12. You can use these extensions now with secure credentials disabled as "),Xc={href:"https://ibm.github.io/zopeneditor-about/Docs/zowe_explorer_v2.html#eclipse-che",target:"_blank",rel:"noopener noreferrer"},Nc=o("documented here"),Jc=o("."),Hc=i('
       2.0.2 - 2022/04/25
      • Added full support for Zowe 2.0 in particular Zowe Explorer 2, Zowe CLI 7, Zowe API Mediation Layer 2. You can continue using your Zowe CLI 6.x profiles for backwards compatibility, but you must update Zowe Explorer to version 2 to do so. Review our Getting Started with Zowe 2.0 section in the Z Open Editor user documentation or the Zowe CLI documentation for how to migrate your 6.x profiles to the 7.x format.
      • Added support for auto-init of Team config files to the IBM RSE API Plugin for Zowe CLI. Use it when you have you RSE API host component registered with the API Mediation Layer.
      • Switched the minimal required version of Node JS for IBM RSE API Plugin for Zowe CLI to version 14 as version 12 is out of support now.
      • Added user setting zopeneditor.server.startupOptions for providing custom Java startup options for language servers. Can be used with tech support for troubleshooting.
       2.0.0 - 2022/03/15
      Z Open Editor is released as major version update to 2.0 to celebrate its availability in IBM Wazi Developer for Workspaces 2.0 that is now part of the IBM Z and Cloud Modernization Stack and fully supports running on OpenShift on Linux on Z. Note that because Zowe 2.0 was delayed to late April 2022, Z Open Editor has to be updated to support it once Zowe has been released. Other fixes and enhancements in this release:
      ',4),Vc=o("Added missing DEBUG-ITEM variables in the COBOL language server. ("),qc={href:"https://github.com/IBM/zopeneditor-about/issues/156",target:"_blank",rel:"noopener noreferrer"},Wc=o("Issue 156"),Gc=o(")"),jc=o("Added missing JNIENVPTR and JSON-STATUS variables in the COBOL TextMate grammar and the COBOL language server. ("),Yc={href:"https://github.com/IBM/zopeneditor-about/issues/156#issuecomment-912978046",target:"_blank",rel:"noopener noreferrer"},Qc=o("Issue 156"),Kc=o(")"),$c=o("Fixed an issue in the COBOL language server not supporting a mixed case spelling of SQLCA and SQLDA. ("),eu={href:"https://github.com/IBM/zopeneditor-about/issues/208",target:"_blank",rel:"noopener noreferrer"},ou=o("Issue 208"),tu=o(")"),su=e("li",null,"Fixed an issue in the COBOL language server where the Rename Symbol feature was not renaming symbols that were spelled using a different character casing.",-1),iu=e("li",null,"Fixed an issue in the COBOL TextMate Grammar making the SCREEN keyword case insensitive.",-1),nu=o("Fixed an issue in the COBOL language server where parsing failed because of period in column 72 and standard sequence numbering present in the program. ("),ru={href:"https://github.com/IBM/zopeneditor-about/issues/202",target:"_blank",rel:"noopener noreferrer"},au=o("Issue 202"),lu=o(")"),du=o("Fixed an issue in the COBOL Language Sever where parsing failed with invalid error message in COPY REPLACING statements. ("),hu={href:"https://github.com/IBM/zopeneditor-about/issues/181",target:"_blank",rel:"noopener noreferrer"},cu=o("Issue 181"),uu=o(")"),_u=e("li",null,"Performance and reliability improvements for the COBOL and PL/I language servers by implementing cancellation support for requests that are no longer valid as well as optimizing handling of document-link requests for include files.",-1),pu=e("li",null,"Added new options to the truncation warning dialog for COBOL, PL/I, HLASM, REXX, and JCL files in Z Open Editor. Also, if only whitespaces are truncated the editor will not prompt anymore, it will just remove them automatically.",-1),fu=o("Fixed an issue in the PL/I language server where hover content for include files were not rendering in the correct format. ("),gu={href:"https://github.com/IBM/zopeneditor-about/issues/211",target:"_blank",rel:"noopener noreferrer"},mu=o("Issue 211"),bu=o(")"),wu=e("li",null,"Fixed an issue in the HLASM language server where NullPointerException were logged while rendering hovers after a document change.",-1),Iu=o("Fixed an issue where HLASM syntax highlighting was not correctly recognizing sequence numbers at the end of lines ("),yu={href:"https://github.com/IBM/zopeneditor-about/issues/192",target:"_blank",rel:"noopener noreferrer"},vu=o("Issue 192"),xu=o(")."),Su=e("li",null,"Fixed an issue in the REXX language server where a trailing comma in a function parameter resulted in a syntax error.",-1),Au=e("li",null,"Improved the REXX language server performance and stability when editing large files.",-1),Bu=e("li",null,'Z Open Editor and Zowe Explorer now share the profiles loaded into memory via the Zowe Explorer Extensibility API. Now if you make changes to a profile in Zowe Explorer or use the Reload button to load changes from disk done via CLI, the changes will be immediately visible to Z Open Editor without the need to run "Reload Zowe profiles" from the command palette. This command now performs the same operation as clicking the Zowe Explorer Refresh button.',-1),Cu=o("Made the Zowe connection test in Z Open Editor more robust and fixed the issue of tests timing out for slow connections. ("),Eu={href:"https://github.com/IBM/zopeneditor-about/issues/197",target:"_blank",rel:"noopener noreferrer"},Ou=o("Issue 197"),ku=o(")"),Lu=e("li",null,'Fixed an issue preventing submission of JCL in Zowe Explorer via command palette option "Zowe Explorer: Submit JCL" using RSE API CLI Zowe profiles.',-1),Mu=e("li",null,"Fixed an issue with token and base Zowe CLI profiles support for MVS connection tests for remote file resolving.",-1),zu=e("li",null,"Added RSE API Zowe profile login and logout support for JSON Web Token authentication with the RSE API through Zowe Explorer.",-1),Pu=e("li",null,[o("Improved working with interactive TSO commands for RSE API Zowe profiles by adding the TSO command tag "),e("code",null,"shell-id"),o(", that can be used with RSE API server v1.0.8.")],-1),Ru=e("li",null,"User Build now works with Zowe CLI profiles that do not store credentials. User will be prompted to provide them when the build starts.",-1),Fu=o("Adopted the latest version of "),Zu={href:"https://github.com/IBM/dbb-zappbuild",target:"_blank",rel:"noopener noreferrer"},Uu=o("dbb-zappbuild"),Tu=o(" for User Build that now considers file tags for processing. The JSON dependency file will now be uploaded as a UTF-8 file. If you are using an older version of dbb-zappbuild, please update with the latest changes from its main branch on GitHub."),Du=e("li",null,[o("Fixed an issue that would show the command "),e("code",null,"IBM User Build: Run IBM User Build"),o(" for files with unsupported languages in the command palette.")],-1),Xu=e("li",null,"Fixed an issue that prevented recognizing ZAPP files running in Eclipse Che when workspaces folders were added or removed.",-1),Nu=e("li",null,"Reviewed and revised multiple user interface strings and dialogs.",-1),Ju=o("Updated code samples in "),Hu={href:"https://github.com/IBM/zopeneditor-sample/tree/wazi-main",target:"_blank",rel:"noopener noreferrer"},Vu=o("https://github.com/IBM/zopeneditor-sample/tree/wazi-main"),qu=o(" with Ansible playbooks and host variables for IBM Wazi Sandbox and the IBM Wazi as a Service tutorials."),Wu=e("h2",{id:"_1-4-1-2021-11-19",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-4-1-2021-11-19","aria-hidden":"true"},"#"),o(" 1.4.1 - 2021/11/19")],-1),Gu=o("Fixed an issue with COBOL syntax highlighting of reference modifications ("),ju={href:"https://github.com/IBM/zopeneditor-about/issues/177",target:"_blank",rel:"noopener noreferrer"},Yu=o("Issue 177"),Qu=o(")"),Ku=o("Fixed the VS Code Toggle Line Comment (Cmd-/ or Ctrl-/) command for COBOL. You can now use it with the cursor being placed anywhere in the line as well as select a whole block of code and set or remove the comment symbol as a toggle. ("),$u={href:"https://github.com/IBM/zopeneditor-about/issues/157",target:"_blank",rel:"noopener noreferrer"},e_=o("Issue 157"),o_=o(")"),t_=o("Fixed several issues with HLASM syntax highlighting related to continuation lines, macro definitions, and substitution characters. ("),s_={href:"https://github.com/IBM/zopeneditor-about/issues/118",target:"_blank",rel:"noopener noreferrer"},i_=o("Issue 118"),n_=o(", "),r_={href:"https://github.com/IBM/zopeneditor-about/issues/185",target:"_blank",rel:"noopener noreferrer"},a_=o("Issue 185"),l_=o("). See our "),d_={href:"https://ibm.github.io/zopeneditor-about/Docs/knownissues.html",target:"_blank",rel:"noopener noreferrer"},h_=o("Known Issues"),c_=o(" page for problems not solved, yet."),u_=o("Fixed various inconsistencies with the HLASM outline view. It will now show the first occurrences of CSECTs, DSECTs, MACROs, Branch Targets, and Labels. ("),__={href:"https://github.com/IBM/zopeneditor-about/issues/148",target:"_blank",rel:"noopener noreferrer"},p_=o("Issue 148"),f_=o("). See our "),g_={href:"https://ibm.github.io/zopeneditor-about/Docs/knownissues.html",target:"_blank",rel:"noopener noreferrer"},m_=o("Known Issues"),b_=o(" page for problems not solved, yet."),w_=o("Enhanced HLASM outline view to now display all labels. See "),I_={href:"https://ibm.github.io/zopeneditor-about/Docs/customizing_the_outline_view.html",target:"_blank",rel:"noopener noreferrer"},y_=o("Customizing the outline view"),v_=o(" to change what is included in the outline view."),x_=e("li",null,"Added support to use all REXX keywords as variables, excluding the 'END' keyword as well as improved the readability of keyword-related syntax error messages.",-1),S_=o("Fixed an issue in which trying to load remote include files from MVS using an invalid Zowe CLI Profile password could lock user accounts due to too many failed attempts. Z Open Editor will now prompt for a new password to update the profile or allow canceling all requests. This fix also adds support for using Zowe CLI profiles that do not store credentials and you will be prompted when required. ("),A_={href:"https://github.com/IBM/zopeneditor-about/issues/142",target:"_blank",rel:"noopener noreferrer"},B_=o("Issue 142"),C_=o(")"),E_=o("Fixed an issue that prevented switching from Z Open Editor language servers to other languages. ("),O_={href:"https://github.com/IBM/zopeneditor-about/issues/164",target:"_blank",rel:"noopener noreferrer"},k_=o("Issue 164"),L_=o(")"),M_=e("li",null,"Fixed a regression in which a ZAPP file was not found when using it in an IBM RSE API for Zowe CLI command parameter or in Z Open Editor when specifying a file with zopeneditor.zowe.defaultRseConversionMappingsFile that was not in the current workspace.",-1),z_=e("li",null,"Fixed an issue with User Build where dependencies would not upload again after making a change inside VS Code settings or ZAPP file settings.",-1),P_=e("li",null,"Fixed an issue with User Build where remote dependencies were being uploaded on Windows.",-1),R_=e("li",null,"Enhanced User Build messages to be more informative and actionable.",-1),F_=e("li",null,"Fixed security related logging issue.",-1),Z_=i('
       1.4.0 - 2021/10/29
      • You can now use User Build without SSH when using IBM RSE API for Zowe CLI profiles. SSH Zowe CLI profiles are now required by z/OSMF only.
      • User Build speed is increased by sending additional dependency and metadata information to IBM Dependency Based Build on z/OS. Check the documentation for new dbb-zappbuild build script arguments.
      • When you save user or workspace settings, Z Open Editor will recognize and reload all Zowe CLI profiles, which is particularly useful when you add new profile names to the zopeneditor.zowe setting.
      • Support for ZAPP files with Z Open Editor is now also available when running in Eclipse Che, Red Hat CodeReady Workspaces, and IBM Wazi Developer for Workspaces.
      • Startup performance is faster with a smaller memory footprint due to significantly reduced language server sizes.
      • You can use the IBM Debug for z/OS High Level Assembler debug listing files with the language ID hlasmlst and the default file extension langx.
      • Fixed an issue in which a newly created ZAPP file was not recognized until the editor restarted.
      • Enhanced some UI strings for effectiveness including menus and Preferences names and descriptions.
      • New commands are added to IBM RSE API for Zowe CLI: 
        • zowe rse create data-set --like: Allocates a new data set with the same attributes as an existing data set specified by the --like option in IBM RSE API for Zowe CLI. The allocate-like functionality can now also be used with RSE profiles in Zowe Explorer. To use this feature, RSE API server 1.0.7 or later versions are required.
        • zowe rse check system-address-space: Displays all active system address space information in RSE CLI plug-in. To use this feature, RSE API 1.0.5 or later versions, and IBM Explorer for z/OS 3.2.0.16 or later versions are required.
        • zowe rse check job-address-space: Displays all active job address space information in RSE CLI plug-in. To use this feature, RSE API 1.0.5 or later versions and IBM Explorer for z/OS 3.2.0.16 or later versions are required.
       1.2.6 - 2021/08/19
      ',3),U_=o("Fixed an issue with PL/I compiler options for margins not being interpreted correctly in the editor. ("),T_={href:"https://github.com/IBM/zopeneditor-about/issues/135",target:"_blank",rel:"noopener noreferrer"},D_=o("Issue 135"),X_=o(")"),N_=o("Fixed an issue that encoded special characters incorrectly in include file hovers for all languages. ("),J_={href:"https://github.com/IBM/zopeneditor-about/issues/128",target:"_blank",rel:"noopener noreferrer"},H_=o("Issue 128"),V_=o(")"),q_=o("Fixed issues with HLASM code completion not appearing correctly in continuation and empty lines. ("),W_={href:"https://github.com/IBM/zopeneditor-about/issues/118",target:"_blank",rel:"noopener noreferrer"},G_=o("Issue 118"),j_=o(")"),Y_=i("
    • Various fixes and improvements for REXX: 
      • Fixed issues with handling multi-line strings correctly for REXX.
      • Made code completion in REXX case-sensitive so that it preserves the casing style the user was using before initiating completion requests with Ctrl+Space.
      • Added an editor ruler at column 80 in REXX files. All editor rulers are customizable through the settings.
      • Added truncation warnings for characters after column 80 in REXX files. The column number is customizable through the settings.
      • Various REXX refinements that improve stability and performance of parsing and error messages.
    • Fixed an issue in IBM RSE API for Zowe CLI that prevented the use of the correct encoding for file uploads to USS, which also impacted uploads via Zowe Explorer using an RSE API profile. This fix requires Zowe Explorer 1.18.0 or newer.
    • Fixed an issue in User Build that prevented the use of the correct encoding as defined in .gitattributes to files uploaded via z/OSMF or RSE API profiles.
      • ",3),Q_=o("Addressed the user request to allow the "),K_=e("code",null,"zopeneditor.zowe",-1),$_=o(" settings to be scoped for workspace settings. This will be useful for development teams who standardize the names of their Zowe CLI profiles for their projects and use them for build automation. ("),ep={href:"https://github.com/IBM/zopeneditor-about/issues/143",target:"_blank",rel:"noopener noreferrer"},op=o("Issue 143"),tp=o(")"),sp=e("li",null,[o("Adopted the new Zowe Explorer "),e("code",null,"zowe.files.temporaryDownloadsFolder.cleanup"),o(' setting to support the use of multiple VS Code windows showing the same files opened via Zowe Explorer, in order to see different parts of the same program on two different screens. Note that disabling the cleanup will result in files downloaded from z/OS not being removed when the editor is closed or restarted, so when you open a file via Zowe Explorer you may be viewing an outdated local version. Use the right-click "Pull from Mainframe" command to ensure you are working with the latest files.')],-1),ip=e("li",null,"Adopted new Zowe Explorer APIs that require Zowe Explorer 1.15.0 or newer to be installed. This release has been tested with Zowe Explorer 1.18.0.",-1),np=e("h2",{id:"_1-2-5-2021-06-18",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-2-5-2021-06-18","aria-hidden":"true"},"#"),o(" 1.2.5 - 2021/06/18")],-1),rp=o("Refined COBOL Renumber and Unnumber support making it configurable to work with columns 1-6 or 73-80 or both. If content other than numberic values is already present in these locations in a specific row then it will not update that location to preserve the content. ("),ap={href:"https://github.com/IBM/zopeneditor-about/issues/8",target:"_blank",rel:"noopener noreferrer"},lp=o("Issue 8"),dp=o(")"),hp=o("Fixed syntax highlighting for HLASM beyond column 16. There is still an issue with code completion that well be addressed in a later release. ("),cp={href:"https://github.com/IBM/zopeneditor-about/issues/118",target:"_blank",rel:"noopener noreferrer"},up=o("Issue 118"),_p=o(")"),pp=e("li",null,"Improved performance and reliability of downloading larger numbers of include files such as SYS1.MACLIB macros for the HLAMS editor hovers.",-1),fp=o("Removed the performance warning dialog for property groups and replaced it with log messages ("),gp={href:"https://github.com/IBM/zopeneditor-about/issues/115",target:"_blank",rel:"noopener noreferrer"},mp=o("Issue 15"),bp=o(")"),wp=e("li",null,"User Build now writes its output into a separate log file for users to share and analyze.",-1),Ip=e("li",null,"Adoption of new Zowe Explorer API ICommand to allow issuing of TSO commands using RSE profiles via Zowe Explorer 1.14.0 and higher.",-1),yp=e("li",null,[o("RSE CLI plug-in updates: "),e("ul",null,[e("li",null,[o("RSE CLI plug-in now prompts user for credentials for RSE profiles without user and password, during "),e("code",null,"zowe rse auth login"),o(" command to obtain JWT token, and if RSE API token is expired to obtain new token.")]),e("li",null,"Fixed a regression that broke uploading a file as a sequential data set.")])],-1),vp=e("h2",{id:"_1-2-1-2021-04-21",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-2-1-2021-04-21","aria-hidden":"true"},"#"),o(" 1.2.1 - 2021/04/21")],-1),xp=i("
    • Made various improvements to our REXX language server and fixed defects: 
      • Added support for nested comments in REXX
      • Added support for keyword instructions as variables in REXX (excludes DO, IF, PARSE, SELECT, TRACE).
      • Fixed a find references bug in REXX where variables and functions with the same name matched
      • Fixed a find references bug in REXX where keywords could be used to find references
      • Refined the hover content and code completion detail in REXX to make the information more concise
      • Updated the hover content in IBM Documentation to point to the new IBM Documentation pages for the z/OS 2.4.0 TSO/E REXX Reference.
      • Standardized the syntax highlighting in REXX to color all keywords the same
      • Fixed a syntax highlighting bug in REXX where "value" following "address" was not displaying in color as a keyword
      • Fixed a syntax highlighting bug in REXX where the routine name following "call" was not displaying in color as a function
    • Reviewed and updated all output and log messages for the IBM RSE API Plug-in for Zowe CLI to ensure consistency. Locate the log file in ~/.zowe/zowe/logs/zowe.log.
      • ",2),Sp=o("Updated RSE API support for Zowe CLI "),Ap={href:"https://docs.zowe.org/stable/user-guide/cli-usingcli.html#base-profiles",target:"_blank",rel:"noopener noreferrer"},Bp=o("base profiles"),Cp=o(" for the "),Ep={href:"https://docs.zowe.org/stable/user-guide/api-mediation/discovery-service-configuration.html#api-ml-configuration",target:"_blank",rel:"noopener noreferrer"},Op=o("Zowe API Mediation Layer (APIML)"),kp=o(" Single Sign On (SSO) for User Build and using the RSE API behind the Zowe APIML. Refer to this "),Lp={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/joe-winchester1/2021/04/14/using-the-ibm-remote-system-explorer-apis-with-the",target:"_blank",rel:"noopener noreferrer"},Mp=o("new blog post"),zp=o(" for an overview about how to use RSE API with the Zowe API Mediation Layer."),Pp=e("h2",{id:"_1-2-0-2021-03-19",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-2-0-2021-03-19","aria-hidden":"true"},"#"),o(" 1.2.0 - 2021/03/19")],-1),Rp=o("REXX language server: in this release we added language support for TSO/E REXX for z/OS. This first version includes syntax highlighting, syntax errors, code completion, find references, outline view, and rich documentation hover features. See our docs for all the details. ("),Fp={href:"https://github.com/IBM/zopeneditor-about/issues/15",target:"_blank",rel:"noopener noreferrer"},Zp=o("Issue 14"),Up=o(")"),Tp=e("li",null,[o("Added full support for encoding conversions to/from UTF-8 to/from international EBCDIC code pages for all our z/OS MVS interactions that use RSE API "),e("ul",null,[e("li",null,"Introduced a new mapping file concept to ZAPP as well as standalone JSON files that allow specifying mappings to groups or individual data sets or even members."),e("li",null,"Added support for all RSE API CLI commands with new parameters as well as the ability to read mapping files that read and write to MVS."),e("li",null,"All Z Open Editor remote MVS read operations using RSE API to find include files now can use mappings defined in ZAPP or user-local mappings files."),e("li",null,"The Zowe Explorer integration with RSE API can also be configured to use mappings files for read and write operations of data set members.")])],-1),Dp=e("li",null,"Added EBCDIC conversion mappings for z/OS USS to User Build. Users can provide a standard .gitattributes file that specifies the encoding the program files should be converted to when uploaded to z/OS USS for a build.",-1),Xp=o("Added context menus for COBOL with the ability to remove as well as renumber sequence numbers. ("),Np={href:"https://github.com/IBM/zopeneditor-about/issues/8",target:"_blank",rel:"noopener noreferrer"},Jp=o("Issue 8"),Hp=o(")"),Vp=e("li",null,[o("Made include file resolution case-insensitive by default to support users with lowercase filenames and property group path names on local case-sensitive file systems such as Linux. As this can lead potentially to ambiguity problems we also added a new user setting called "),e("code",null,"zopeneditor.enforceCaseSensitiveIncludeFileNames"),o(" to enable case sensitive matching, even on case-insensitive operation systems such as Windows.")],-1),qp=e("li",null,[o("The command "),e("code",null,"Reload Zowe Profiles"),o(" that you can use when you changed your Zowe profiles, which was mainly introduced for User Build, now also restarts the language servers and retries loading any remote MVS include files with the updated profile information.")],-1),Wp=e("li",null,"Added a new Welcome page for new users that interactively checks for prerequisites and gives tips for getting started.",-1),Gp=o("Added support for APIML SSO for remote include file resolution such as COBOL Copybooks located on MVS. ("),jp={href:"https://github.com/IBM/zopeneditor-about/issues/107",target:"_blank",rel:"noopener noreferrer"},Yp=o("Issue 107"),Qp=o(")"),Kp=o("Fixed an issue in which invalid Zowe CLI profile configurations could cause Z Open Editor to not activate. We now show error messages and the editor is still usable. ("),$p={href:"https://github.com/IBM/zopeneditor-about/issues/110",target:"_blank",rel:"noopener noreferrer"},ef=o("Issue 110"),of=o(")"),tf=e("h2",{id:"_1-1-3-2020-12-12",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-1-3-2020-12-12","aria-hidden":"true"},"#"),o(" 1.1.3 - 2020/12/12")],-1),sf=o("Fixed regression when resolving copybooks/include files with property groups that have multiple syslib/library entries. ("),nf={href:"https://github.com/IBM/zopeneditor-about/issues/105",target:"_blank",rel:"noopener noreferrer"},rf=o("Issue 105"),af=o(")"),lf=e("h2",{id:"_1-1-2-2020-12-09",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-1-2-2020-12-09","aria-hidden":"true"},"#"),o(" 1.1.2 - 2020/12/09")],-1),df=e("li",null,[o("Added support for "),e("code",null,"SYS1.MACLIB"),o(" macros to HLASM for code completion. If you have a valid Zowe Explorer connection, it will even retrieve the macro definition automatically and show you in rich hovers when you typed or completed the macro name. Ensure that you enable this feature in user settings before using it.")],-1),hf=e("li",null,"Improved the way that Z Open Editor is looking for your Java Runtime or SDK. Review our updated documentation for the search order in which it tries to locate Java, as well as how you can override it with user settings. Added official support for Java Runtimes, and an SDK is not required anymore.",-1),cf=o("RSE CLI plug-in has added an encoding field that you can specify when creating or editing a Zowe RSE API CLI profile. You can use this field with newly added encoding tags for the commands of uploading and downloading MVS and USS files. Resolving copybooks will now use this encoding tag as well for RSE API and z/OSMF connections. ("),uf={href:"https://github.com/IBM/zopeneditor-about/issues/82",target:"_blank",rel:"noopener noreferrer"},_f=o("Issue 82"),pf=o(")"),ff=o("RSE CLI plug-in now supports MVS binary downloads. ("),gf={href:"https://github.com/IBM/zopeneditor-about/issues/58",target:"_blank",rel:"noopener noreferrer"},mf=o("Issue 58"),bf=o(")"),wf=o("To update to RSE CLI plug-in 1.1.2, follow "),If={href:"https://ibm.github.io/zopeneditor-about/Docs/setup_integration.html#updating-the-ibm-rse-api-plug-in-for-zowe-cli",target:"_blank",rel:"noopener noreferrer"},yf=o("the instructions here"),vf=o(" for the optional migration."),xf=e("h2",{id:"_1-1-1-2020-11-6",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-1-1-2020-11-6","aria-hidden":"true"},"#"),o(" 1.1.1 - 2020/11/6")],-1),Sf=o("Added full support for "),Af={href:"https://docs.zowe.org/stable/user-guide/cli-usingcli.html#base-profiles",target:"_blank",rel:"noopener noreferrer"},Bf=o("Zowe CLI Base Profiles"),Cf=o(" with "),Ef={href:"https://ibm.github.io/zopeneditor-about/Blog/rse-october-110.html#use-json-web-tokens-jwt-for-authentication-with-the-host",target:"_blank",rel:"noopener noreferrer"},Of=o("RSE API JWT tokens"),kf=o(" for CLI commands and well as Zowe Explorer 1.10.1 or newer. To use it also update the IBM RSE API Plugin for Zowe CLI 1.1.1 and follow "),Lf={href:"https://ibm.github.io/zopeneditor-about/Docs/setup_integration.html#updating-the-ibm-rse-api-plug-in-for-zowe-cli",target:"_blank",rel:"noopener noreferrer"},Mf=o("the instructions here"),zf=o(" for the optional migration."),Pf=o("Fixed issue for specifying the right PL/I margin with property groups compile option settings. Note, that the left margin must be at least 2 at the moment. ("),Rf={href:"https://github.com/IBM/zopeneditor-about/issues/87",target:"_blank",rel:"noopener noreferrer"},Ff=o("Issue 72"),Zf=o(")"),Uf=o("Added "),Tf={href:"https://ibm.github.io/zopeneditor-about/Docs/setting_compiler_options.html",target:"_blank",rel:"noopener noreferrer"},Df=o("new documentation"),Xf=o(" for the currently supported property group compile options."),Nf=o("Fixed issue with using "),Jf=e("code",null,"$",-1),Hf=o(", "),Vf=e("code",null,"#",-1),qf=o(", or "),Wf=e("code",null,"@",-1),Gf=o(" in HLASM and PL/I include file names. COBOL will be addressed in a future release. ("),jf={href:"https://github.com/IBM/zopeneditor-about/issues/86",target:"_blank",rel:"noopener noreferrer"},Yf=o("Issue 86"),Qf=o(")"),Kf=e("h2",{id:"_1-1-0-2020-10-23",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-1-0-2020-10-23","aria-hidden":"true"},"#"),o(" 1.1.0 - 2020/10/23")],-1),$f=e("li",null,"ZAPP (Z APPlication) file support. Instead of mixing the configuration of your application with VS Code Preferences you can now specify property groups and IBM User Build configurations in a new simple yaml (or json) file located in your workspace that you can share with your team in Git. See our docs for a tutorial.",-1),eg=o("Added support for the Zowe CLI Secure Credentials Plugins for all Z Open Editor operations such as resolving include files or running user build ("),og={href:"https://github.com/IBM/zopeneditor-about/issues/66",target:"_blank",rel:"noopener noreferrer"},tg=o("Issue 66"),sg=o(")"),ig=o("Property Groups can now be scoped to one specific language making include file resolution more efficient as well as to support compiler options. ("),ng={href:"https://github.com/IBM/zopeneditor-about/issues/72",target:"_blank",rel:"noopener noreferrer"},rg=o("Issue 72"),ag=o(")."),lg=o("Added the ability to provide language-specific compiler options such as "),dg=e("code",null,"OR('!')",-1),hg=o(" to property groups to configure the editor ("),cg={href:"https://github.com/IBM/zopeneditor-about/issues/17",target:"_blank",rel:"noopener noreferrer"},ug=o("Issue 17"),_g=o(", "),pg={href:"https://github.com/IBM/zopeneditor-about/issues/61",target:"_blank",rel:"noopener noreferrer"},fg=o("Issue 61"),gg=o(")."),mg=o("Include file resolution for COBOL and PL/I ignores SQLCA and SQLDA ("),bg={href:"https://github.com/IBM/zopeneditor-about/issues/71",target:"_blank",rel:"noopener noreferrer"},wg=o("Issue 71"),Ig=o(")."),yg=o("Fixed issues with COBOL 6.3 support such as "),vg=e("code",null,">>if >>else >>end-if",-1),xg=o(" ("),Sg={href:"https://github.com/IBM/zopeneditor-about/issues/65",target:"_blank",rel:"noopener noreferrer"},Ag=o("Issue 65"),Bg=o(")."),Cg=e("li",null,"The logger now provides more configuration information that will help in your interactions with tech support.",-1),Eg=e("li",null,"Fixed issues managing Zowe Explorer favorites when using RSE API.",-1),Og=e("li",null,"Revised profile validation in Zowe Explorer when using RSE API.",-1),kg=e("p",null,"We now include the IBM User Build VS Code Extension in IBM Z Open Editor. Changes since the 1.0.0 release:",-1),Lg=e("ul",null,[e("li",null,"In addition to COBOL we added support for building PL/I and HLASM programs with IBM Dependency-Based Build."),e("li",null,"Fixed an issue with corrupted DBB log files when downloaded from USS."),e("li",null,"User Build menus no longer appear for remote MVS or USS files opened via Zowe Explorer to avoid confusion about what can be built and what cannot."),e("li",null,"Added more detailed log messages in the IBM User Build Output window, such as the full ssh commands executed, as a summary of all the user and workspace settings being used for a build and more. The output will list all required and optional settings and their values before the user build script is executed. If any required settings are missing, user build will stop execution explaining which setting caused the problem."),e("li",null,"User Build can now run with files that contain spaces in their paths.")],-1),Mg=e("h2",{id:"_1-0-3-2020-08-07",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-0-3-2020-08-07","aria-hidden":"true"},"#"),o(" 1.0.3 - 2020/08/07")],-1),zg=o("Added support for specifying custom include file extensions. You can now use the IBM Z Open Editor Preferences page to add and remove the file extensions to be used when searching for local include files such as COBOL copybooks. Also consistently added the Data Sets settings for remote include files to the visual editor allowing users to remove the mappings they do not want mapped in the files.association setting ("),Pg={href:"https://github.com/IBM/zopeneditor-about/issues/16",target:"_blank",rel:"noopener noreferrer"},Rg=o("Issue 16"),Fg=o(")."),Zg=e("li",null,"Added branch targets to the HLASM Outline view.",-1),Ug=o('Fixed COBOL syntax highlighting that uses a "/" character for comments ('),Tg={href:"https://github.com/IBM/zopeneditor-about/issues/60",target:"_blank",rel:"noopener noreferrer"},Dg=o("Issue 60"),Xg=o(")."),Ng=o('Fixed HLASM syntax highlighting for macros starting with a "$" character ('),Jg={href:"https://github.com/IBM/zopeneditor-about/issues/69",target:"_blank",rel:"noopener noreferrer"},Hg=o("Issue 69"),Vg=o(")."),qg=o("Added a support for using the "),Wg=e("code",null,"java.home",-1),Gg=o(" user setting for developers that install VS Code with the "),jg={href:"https://code.visualstudio.com/docs/java/java-tutorial#_setting-up-visual-studio-code-for-java-development",target:"_blank",rel:"noopener noreferrer"},Yg=o("Microsoft Installer of VS Code for Java developer"),Qg=o(" or the Java Extension Pack."),Kg=e("li",null,"Added a Zowe Profile validation routine that is called when adding and using RSE API profiles with Zowe Explorer 1.7 or newer.",-1),$g=e("h2",{id:"_1-0-2-2020-06-30",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-0-2-2020-06-30","aria-hidden":"true"},"#"),o(" 1.0.2 - 2020/06/30")],-1),em=e("ul",null,[e("li",null,"Merged v0.5.2 with v1.0.1 to publish v1.0.2 to the VS Code Marketplace that now includes the language server for IBM High-Level Assembler (HLASM) for z/OS 2.4."),e("li",null,"Reorganized the language server packaging to reduce the size of the extension to less than half than it was before.")],-1),om=e("h2",{id:"_1-0-1-0-5-2-2020-06-23",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-0-1-0-5-2-2020-06-23","aria-hidden":"true"},"#"),o(" 1.0.1/0.5.2 - 2020/06/23")],-1),tm=o("Fixed false positives in Java compatibility check that prevented newer Java SDK versions than 8 to be used. ("),sm={href:"https://github.com/IBM/zopeneditor-about/issues/57",target:"_blank",rel:"noopener noreferrer"},im=o("Issue 57"),nm=o(")"),rm=e("h2",{id:"_1-0-0-2020-06-12",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_1-0-0-2020-06-12","aria-hidden":"true"},"#"),o(" 1.0.0 - 2020/06/12")],-1),am=e("li",null,"This is our v1.0 release for which you will be able to purchase technical support from IBM.",-1),lm=e("li",null,"Added a language server for IBM High-Level Assembler (HLASM) for z/OS 2.4.",-1),dm=o("Currently only available here, because of VS Code Marketplace size restrictions: "),hm={href:"https://ibm.github.io/mainframe-downloads/downloads.html",target:"_blank",rel:"noopener noreferrer"},cm=o("https://ibm.github.io/mainframe-downloads/downloads.html"),um=e("h2",{id:"_0-5-0-2020-06-12",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_0-5-0-2020-06-12","aria-hidden":"true"},"#"),o(" 0.5.0 - 2020/06/12")],-1),_m=e("li",null,"Added syntax error checking for COBOL Copybooks.",-1),pm=e("li",null,"Added support for CICS 5.6 syntax.",-1),fm=e("li",null,"Rewrote the algorithm for searching for remote include files using Zowe CLI profiles.",-1),gm=e("li",null,"Added user settings for specifying which Zowe CLI profile to use for finding remote include files on MVS in case you use multiple z/OSMF or RSE API CLI profiles.",-1),mm=e("li",null,"Added Logger to analyze issues. Switch it on in the IBM Z Open Editor VS Code Preferences under User Settings.",-1),bm=o("Fixed bug with Unreachable Code Detection in COBOL EXECL SQL statements and switched default of the "),wm=e("code",null,'"zopeneditor.cobol.enableUnreachableCodeWarnings"',-1),Im=o(" Preferences setting back to true. ("),ym={href:"https://github.com/IBM/zopeneditor-about/issues/18",target:"_blank",rel:"noopener noreferrer"},vm=o("Issue 18"),xm=o(")"),Sm=e("li",null,"Updated LSP4J language servers to baseline v0.9.0 and VS Code language clients to v6.1.3.",-1),Am=e("li",null,"Improved LSP startup times.",-1),Bm=e("li",null,"Added more Java runtime checks to ensure you are using a valid Java SDK with the Z Open Editor extension.",-1),Cm=e("li",null,"Various enhancements and fixes for RSE API support such as Get JCL from the Zowe Explorer JES view as well as Migrate/Recall from the Zowe Explorer MVS view.",-1),Em=o("Fixed rare race condition when starting language servers. ("),Om={href:"https://github.com/IBM/zopeneditor-about/issues/45",target:"_blank",rel:"noopener noreferrer"},km=o("Issue 45"),Lm=o(")"),Mm=e("li",null,"Various stability fixes and refinements.",-1),zm=e("h2",{id:"_0-4-9-2020-04-23",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_0-4-9-2020-04-23","aria-hidden":"true"},"#"),o(" 0.4.9 - 2020/04/23")],-1),Pm=e("ul",null,[e("li",null,"Fixed an issue when using RSE for the Zowe Explorer JES view."),e("li",null,"Fixed errors messages users saw when creating z/OSMF profiles in Zowe Explorer when Zowe CLI and/or the IBM RSE API Plugin for Zowe CLI was not installed.")],-1),Rm=e("h2",{id:"_0-4-7-2020-03-27",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_0-4-7-2020-03-27","aria-hidden":"true"},"#"),o(" 0.4.7 - 2020/03/27")],-1),Fm=o("Added Beta-level support for the new Remote System Explorer API (RSEAPI) REST servers that can be used as an alternative to z/OSMF for remote file operations as well as Zowe Explorer visual explorer views. If you run RSE already for IBM Developer for Z or IBM z/OS Explorer you can simply update. Go to "),Zm={href:"https://ibm.github.io/zopeneditor-about",target:"_blank",rel:"noopener noreferrer"},Um=o("https://ibm.github.io/zopeneditor-about"),Tm=o(" for more details."),Dm=e("li",null,"Reduced the memory consumption of the extension by starting language servers only if a program in a specifc language is opened for the first time. This will avoid that you are wasting valuable PC memory for languages that you do not use. In addition we added two optional commands that you can run to pause the COBOL or PL/I language server once you finished with one language and want to free up its memory. When you open a program of that language again the language server will restart.",-1),Xm=e("li",null,"Added code actions that provide suggestions for resolving COBOL copybooks and PL/I include files by linking to Online Help pages.",-1),Nm=e("li",null,"Removed MQ code templates for now as we ran into some language compatibility issues.",-1),Jm=i('
       0.4.5 - 2020/01/07
      • Added an additional 27 code snippets for MQ development with COBOL and 27 for MQ with PL/I.
       0.4.3 - 2019/12/18
      • Added more code snippets for COBOL, PL/I and JCL, which brings it to a total of 186. For COBOL we now provide 27 General COBOL language support snippets, 12 Embedded SQL snippets, 29 for CICS, 12 for IMS, and 8 for VSAM. Similarly, we provide for PL/I 12 General PL/I language support snippets, 29 CICS, 11 IMS, and 7 VSAM. Finally, we have 27 code snippets for JCL.
       0.4.1 - 2019/11/21
      ',5),Hm=e("li",null,"Language server updates to support IBM Enterprise COBOL v6.3 and PL/I v5.3.",-1),Vm=o("Added all new sets of IBM field contributed code snippets for COBOL embedded SQL and CICS, PL/I embedded SQL, and various new JCL snippets. This is just the beginning of us curating a larger portfolio of high-value code snippets and incrementally releasing these in the coming months. Keep and eye out and "),qm={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},Wm=o("let us know what you think of these snippets"),Gm=o("."),jm=e("li",null,"Added an import command for loading Code Snippets exported by the IBM Developer from z/OS. Do you have your own set of code snippets that you managed in the Snippets view in IDz? You can now export and import these into Z Open Editor.",-1),Ym=o("Switched off COBOL Unreachable Code warnings by default as there are cases in which it can provide false positives ("),Qm={href:"https://ibm.github.io/zopeneditor-about/Docs/knownissues.html#limitations-of-cobol-program-files",target:"_blank",rel:"noopener noreferrer"},Km=o("see here"),$m=o(" for details). If you can accept the risk of a few false reports then you can enable it again by using the "),eb=e("code",null,'"zopeneditor.cobol.enableUnreachableCodeWarnings": true',-1),ob=o(" VS Code user or workspace setting."),tb=e("li",null,"Fixed a code completion bug for COBOL and PL/I that would erase text to the right of the cursor.",-1),sb=o("Fixed cases in which COBOL statements before the IDENTIFICATION DIVISION would break syntax checking. ("),ib={href:"https://github.com/IBM/zopeneditor-about/issues/9",target:"_blank",rel:"noopener noreferrer"},nb=o("Issue #9"),rb=o(")"),ab=o("Fixed exceptions thrown by the PL/I LSP when computing document links ("),lb={href:"https://github.com/IBM/zopeneditor-about/issues/13",target:"_blank",rel:"noopener noreferrer"},db=o("Issue #13"),hb=o(")"),cb=o("Fixed issues with COBOL Unreachable Code warnings not being shown at all in some cases. ("),ub={href:"https://github.com/IBM/zopeneditor-about/issues/7",target:"_blank",rel:"noopener noreferrer"},_b=o("Issue #7"),pb=o(")"),fb=e("li",null,"Fixed an issue in which invalid PIC clauses would not be reported as syntax errors.",-1),gb=e("h2",{id:"_0-3-11-2019-09-27",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#_0-3-11-2019-09-27","aria-hidden":"true"},"#"),o(" 0.3.11 - 2019/09/27")],-1),mb=e("li",null,'"Unreachable Code" is not reported as an error anymore, but is now a warning message in the Problems View.',-1),bb=e("li",null,[o('Switch off "Unreachable Code" detection completely with this new setting: '),e("code",null,'"zopeneditor.cobol.enableUnreachableCodeWarnings": false'),o(".")],-1),wb=o("We implemented GLOB pattern matching in Property Group settings for finding Copybooks on the local file system as requested in "),Ib={href:"https://github.com/IBM/zopeneditor-about/issues/5",target:"_blank",rel:"noopener noreferrer"},yb=o("this issue"),vb=o(". Use with care as a very large search space will slow down the editor."),xb=o("We added support for "),Sb={href:"https://code.visualstudio.com/docs/editor/multi-root-workspaces",target:"_blank",rel:"noopener noreferrer"},Ab=o("VS Code Multi-root Workspaces"),Bb=o(" allowing you to now specify Property Groups for finding Copybooks for a workspace comprising of many development project folders and Git repositories. To use it move your Property Groups to the Workspace File."),Cb=o("We updated and revised our documentation for using Property Groups with patterns and workspaces in the "),Eb={href:"https://ibm.github.io/zopeneditor-about/Docs/setting_propertygroup.html",target:"_blank",rel:"noopener noreferrer"},Ob=o("Online Help"),kb=o(". We also added examples for using it on Windows versus Mac/Linux."),Lb=e("li",null,"Fixed an issue with using the Tab key in Code Snippets and when using it for indentation in the editor.",-1),Mb=i('
       0.3.9 - 2019/09/23
      • Just removed Preview flag in preparation for the announcement.
      • Stay tuned for more cool things to come.
       0.3.7 - 2019/09/17
      • Fixes to the documentation and hyperlinks.
      • Renamed extension preferences configuration name.
       0.3.5 - 2019/09/13
      • First public release evolving out of the Wazi technology preview. See README.md for details.
      ',6);function zb(Pb,Rb){const s=n("ExternalLinkIcon"),r=n("RouterLink");return a(),l(h,null,[_,e("ul",null,[e("li",null,[p,e("a",f,[g,t(s)]),m]),b]),w,I,y,e("ul",null,[e("li",null,[v,x,S,e("a",A,[B,t(s)]),C]),E,e("li",null,[O,e("a",k,[L,t(s)]),M]),z]),P,e("p",null,[R,F,e("a",Z,[U,t(s)]),T,e("a",D,[X,t(s)]),N]),e("ul",null,[J,e("li",null,[H,e("a",V,[q,t(s)]),W]),e("li",null,[G,e("a",j,[Y,t(s)]),Q,K,$,ee,oe]),te,e("li",null,[se,e("a",ie,[ne,t(s)]),re]),e("li",null,[ae,e("a",le,[de,t(s)]),he]),ce,e("li",null,[ue,e("a",_e,[pe,t(s)]),fe]),ge,me,be]),we,Ie,ye,e("ul",null,[e("li",null,[ve,t(r,{to:"/Blog/advanced_custom_macros.html"},{default:d(()=>[xe]),_:1}),Se]),Ae,e("li",null,[Be,e("a",Ce,[Ee,t(s)]),Oe]),e("li",null,[ke,e("a",Le,[Me,t(s)]),ze]),e("li",null,[Pe,e("a",Re,[Fe,t(s)]),Ze])]),Ue,e("ul",null,[e("li",null,[Te,e("a",De,[Xe,t(s)]),Ne]),Je,He,Ve,qe,We]),Ge,je,Ye,e("p",null,[Qe,e("a",Ke,[$e,t(s)]),eo]),oo,to,so,io,no,e("ul",null,[e("li",null,[ro,e("a",ao,[lo,t(s)]),ho]),e("li",null,[co,e("a",uo,[_o,t(s)]),po]),e("li",null,[fo,e("a",go,[mo,t(s)]),bo]),wo,Io,e("li",null,[yo,e("a",vo,[xo,t(s)]),So]),e("li",null,[Ao,e("a",Bo,[Co,t(s)]),Eo])]),Oo,e("ul",null,[ko,e("li",null,[Lo,Mo,zo,e("a",Po,[Ro,t(s)]),Fo])]),Zo,e("ul",null,[e("li",null,[Uo,e("a",To,[Do,t(s)]),Xo]),No,e("li",null,[Jo,e("a",Ho,[Vo,t(s)]),qo]),e("li",null,[Wo,e("a",Go,[jo,t(s)]),Yo]),Qo,e("li",null,[Ko,e("a",$o,[et,t(s)]),ot]),e("li",null,[tt,e("a",st,[it,t(s)]),nt]),e("li",null,[rt,at,lt,e("a",dt,[ht,t(s)]),ct])]),ut,_t,pt,e("ul",null,[e("li",null,[ft,e("a",gt,[mt,t(s)]),bt]),e("li",null,[wt,It,yt,e("a",vt,[xt,t(s)]),St]),At,e("li",null,[Bt,e("a",Ct,[Et,t(s)]),Ot]),kt,Lt]),Mt,e("ul",null,[zt,e("li",null,[Pt,e("a",Rt,[Ft,t(s)]),Zt]),e("li",null,[Ut,e("a",Tt,[Dt,t(s)]),Xt,e("a",Nt,[Jt,t(s)]),Ht])]),Vt,qt,Wt,e("p",null,[Gt,e("a",jt,[Yt,t(s)]),Qt]),Kt,e("ul",null,[$t,e("li",null,[es,os,ts,e("a",ss,[is,t(s)]),ns]),e("li",null,[rs,e("a",as,[ls,t(s)]),ds]),hs,e("li",null,[cs,e("a",us,[_s,t(s)]),ps]),e("li",null,[fs,e("a",gs,[ms,t(s)]),bs]),ws]),Is,e("ul",null,[e("li",null,[ys,e("a",vs,[xs,t(s)]),Ss]),As,Bs]),Cs,e("ul",null,[e("li",null,[Es,Os,ks,Ls,Ms,e("a",zs,[Ps,t(s)]),Rs]),e("li",null,[Fs,Zs,Us,e("a",Ts,[Ds,t(s)]),Xs]),e("li",null,[Ns,e("a",Js,[Hs,t(s)]),Vs]),qs,Ws,Gs]),js,e("ul",null,[Ys,e("li",null,[Qs,Ks,$s,e("a",ei,[oi,t(s)]),ti]),si,e("li",null,[ii,e("a",ni,[ri,t(s)]),ai]),li,di]),hi,e("ul",null,[e("li",null,[ci,e("a",ui,[_i,t(s)]),pi]),e("li",null,[fi,gi,mi,e("a",bi,[wi,t(s)]),Ii]),e("li",null,[yi,vi,xi,Si,Ai,e("a",Bi,[Ci,t(s)]),Ei]),e("li",null,[Oi,e("a",ki,[Li,t(s)]),Mi]),e("li",null,[zi,e("a",Pi,[Ri,t(s)]),Fi]),e("li",null,[Zi,e("a",Ui,[Ti,t(s)]),Di]),e("li",null,[Xi,e("a",Ni,[Ji,t(s)]),Hi]),e("li",null,[Vi,e("a",qi,[Wi,t(s)]),Gi]),ji,Yi,Qi,Ki,e("li",null,[$i,e("a",en,[on,t(s)]),tn,e("a",sn,[nn,t(s)]),rn]),an,ln,e("li",null,[dn,e("a",hn,[cn,t(s)]),un]),e("li",null,[_n,e("a",pn,[fn,t(s)]),gn]),mn,bn,e("li",null,[wn,e("a",In,[yn,t(s)]),vn]),xn,Sn,e("li",null,[An,Bn,Cn,En,On,e("a",kn,[Ln,t(s)]),Mn]),zn,e("li",null,[Pn,e("a",Rn,[Fn,t(s)]),Zn]),Un,Tn,Dn,Xn]),Nn,e("ul",null,[Jn,e("li",null,[Hn,Vn,qn,Wn,Gn,jn,Yn,e("a",Qn,[Kn,t(s)]),$n]),e("li",null,[er,e("a",or,[tr,t(s)]),sr]),e("li",null,[ir,e("a",nr,[rr,t(s)]),ar]),lr,e("li",null,[dr,hr,cr,ur,_r,e("a",pr,[fr,t(s)]),gr]),e("li",null,[mr,br,wr,e("a",Ir,[yr,t(s)]),vr]),e("li",null,[xr,e("a",Sr,[Ar,t(s)]),Br]),Cr]),Er,e("ul",null,[e("li",null,[Or,e("a",kr,[Lr,t(s)]),Mr]),e("li",null,[zr,e("a",Pr,[Rr,t(s)]),Fr]),Zr,Ur,Tr,e("li",null,[Dr,e("a",Xr,[Nr,t(s)]),Jr]),e("li",null,[Hr,e("a",Vr,[qr,t(s)]),Wr]),e("li",null,[Gr,jr,Yr,Qr,Kr,e("a",$r,[ea,t(s)]),oa]),ta,e("li",null,[sa,e("a",ia,[na,t(s)]),ra,e("a",aa,[la,t(s)]),da]),e("li",null,[ha,e("a",ca,[ua,t(s)]),_a]),e("li",null,[pa,e("a",fa,[ga,t(s)]),ma,e("a",ba,[wa,t(s)]),Ia]),e("li",null,[ya,e("a",va,[xa,t(s)]),Sa]),e("li",null,[Aa,Ba,Ca,e("a",Ea,[Oa,t(s)]),ka]),La,Ma,e("li",null,[za,e("a",Pa,[Ra,t(s)]),Fa]),e("li",null,[Za,Ua,Ta,Da,Xa,e("a",Na,[Ja,t(s)]),Ha]),Va,e("li",null,[qa,Wa,Ga,ja,Ya,e("a",Qa,[Ka,t(s)]),$a])]),el,e("ul",null,[e("li",null,[ol,e("a",tl,[sl,t(s)]),il]),e("li",null,[nl,e("a",rl,[al,t(s)]),ll]),e("li",null,[dl,e("a",hl,[cl,t(s)]),ul]),e("li",null,[_l,e("a",pl,[fl,t(s)]),gl]),e("li",null,[ml,bl,wl,e("a",Il,[yl,t(s)]),vl]),e("li",null,[xl,Sl,Al,Bl,Cl,e("a",El,[Ol,t(s)]),kl]),e("li",null,[Ll,e("a",Ml,[zl,t(s)]),Pl,Rl,Fl,Zl,Ul]),Tl,Dl,Xl,Nl]),Jl,Hl,e("p",null,[Vl,e("a",ql,[Wl,t(s)]),Gl]),e("ul",null,[e("li",null,[jl,e("a",Yl,[Ql,t(s)]),Kl]),$l,ed,e("li",null,[od,e("a",td,[sd,t(s)]),id,e("a",nd,[rd,t(s)]),ad]),e("li",null,[ld,e("a",dd,[hd,t(s)]),cd])]),ud,e("ul",null,[e("li",null,[_d,pd,fd,e("a",gd,[md,t(s)]),bd]),wd,e("li",null,[Id,yd,vd,e("a",xd,[Sd,t(s)]),Ad]),e("li",null,[Bd,e("a",Cd,[Ed,t(s)]),Od]),e("li",null,[kd,e("a",Ld,[Md,t(s)]),zd]),e("li",null,[Pd,e("a",Rd,[Fd,t(s)]),Zd]),Ud,Td,Dd]),Xd,e("ul",null,[e("li",null,[Nd,e("a",Jd,[Hd,t(s)]),Vd]),e("li",null,[qd,e("a",Wd,[Gd,t(s)]),jd]),Yd,Qd,Kd,$d,e("li",null,[eh,e("a",oh,[th,t(s)]),sh,e("a",ih,[nh,t(s)]),rh]),ah,lh]),dh,e("ul",null,[e("li",null,[hh,e("a",ch,[uh,t(s)])]),e("li",null,[_h,e("a",ph,[fh,t(s)]),gh,e("a",mh,[bh,t(s)]),wh]),Ih,e("li",null,[yh,e("a",vh,[xh,t(s)]),Sh]),e("li",null,[Ah,e("a",Bh,[Ch,t(s)]),Eh]),Oh,kh]),Lh,e("ul",null,[e("li",null,[Mh,e("a",zh,[Ph,t(s)]),Rh,e("a",Fh,[Zh,t(s)]),Uh]),e("li",null,[Th,e("a",Dh,[Xh,t(s)]),Nh]),e("li",null,[Jh,e("a",Hh,[Vh,t(s)]),qh]),Wh,Gh,e("li",null,[jh,Yh,Qh,Kh,$h,e("a",ec,[oc,t(s)]),tc]),e("li",null,[sc,ic,nc,e("a",rc,[ac,t(s)]),lc]),e("li",null,[dc,e("a",hc,[cc,t(s)]),uc]),_c,e("li",null,[pc,e("a",fc,[gc,t(s)]),mc]),e("li",null,[bc,e("a",wc,[Ic,t(s)]),yc]),vc,xc]),Sc,e("ul",null,[Ac,e("li",null,[Bc,e("a",Cc,[Ec,t(s)]),Oc]),e("li",null,[kc,e("a",Lc,[Mc,t(s)]),zc]),e("li",null,[Pc,Rc,Fc,e("a",Zc,[Uc,t(s)]),Tc]),e("li",null,[Dc,e("a",Xc,[Nc,t(s)]),Jc])]),Hc,e("ul",null,[e("li",null,[Vc,e("a",qc,[Wc,t(s)]),Gc]),e("li",null,[jc,e("a",Yc,[Qc,t(s)]),Kc]),e("li",null,[$c,e("a",eu,[ou,t(s)]),tu]),su,iu,e("li",null,[nu,e("a",ru,[au,t(s)]),lu]),e("li",null,[du,e("a",hu,[cu,t(s)]),uu]),_u,pu,e("li",null,[fu,e("a",gu,[mu,t(s)]),bu]),wu,e("li",null,[Iu,e("a",yu,[vu,t(s)]),xu]),Su,Au,Bu,e("li",null,[Cu,e("a",Eu,[Ou,t(s)]),ku]),Lu,Mu,zu,Pu,Ru,e("li",null,[Fu,e("a",Zu,[Uu,t(s)]),Tu]),Du,Xu,Nu,e("li",null,[Ju,e("a",Hu,[Vu,t(s)]),qu])]),Wu,e("ul",null,[e("li",null,[Gu,e("a",ju,[Yu,t(s)]),Qu]),e("li",null,[Ku,e("a",$u,[e_,t(s)]),o_]),e("li",null,[t_,e("a",s_,[i_,t(s)]),n_,e("a",r_,[a_,t(s)]),l_,e("a",d_,[h_,t(s)]),c_]),e("li",null,[u_,e("a",__,[p_,t(s)]),f_,e("a",g_,[m_,t(s)]),b_]),e("li",null,[w_,e("a",I_,[y_,t(s)]),v_]),x_,e("li",null,[S_,e("a",A_,[B_,t(s)]),C_]),e("li",null,[E_,e("a",O_,[k_,t(s)]),L_]),M_,z_,P_,R_,F_]),Z_,e("ul",null,[e("li",null,[U_,e("a",T_,[D_,t(s)]),X_]),e("li",null,[N_,e("a",J_,[H_,t(s)]),V_]),e("li",null,[q_,e("a",W_,[G_,t(s)]),j_]),Y_,e("li",null,[Q_,K_,$_,e("a",ep,[op,t(s)]),tp]),sp,ip]),np,e("ul",null,[e("li",null,[rp,e("a",ap,[lp,t(s)]),dp]),e("li",null,[hp,e("a",cp,[up,t(s)]),_p]),pp,e("li",null,[fp,e("a",gp,[mp,t(s)]),bp]),wp,Ip,yp]),vp,e("ul",null,[xp,e("li",null,[Sp,e("a",Ap,[Bp,t(s)]),Cp,e("a",Ep,[Op,t(s)]),kp,e("a",Lp,[Mp,t(s)]),zp])]),Pp,e("ul",null,[e("li",null,[Rp,e("a",Fp,[Zp,t(s)]),Up]),Tp,Dp,e("li",null,[Xp,e("a",Np,[Jp,t(s)]),Hp]),Vp,qp,Wp,e("li",null,[Gp,e("a",jp,[Yp,t(s)]),Qp]),e("li",null,[Kp,e("a",$p,[ef,t(s)]),of])]),tf,e("ul",null,[e("li",null,[sf,e("a",nf,[rf,t(s)]),af])]),lf,e("ul",null,[df,hf,e("li",null,[cf,e("a",uf,[_f,t(s)]),pf]),e("li",null,[ff,e("a",gf,[mf,t(s)]),bf])]),e("p",null,[wf,e("a",If,[yf,t(s)]),vf]),xf,e("ul",null,[e("li",null,[Sf,e("a",Af,[Bf,t(s)]),Cf,e("a",Ef,[Of,t(s)]),kf,e("a",Lf,[Mf,t(s)]),zf]),e("li",null,[Pf,e("a",Rf,[Ff,t(s)]),Zf]),e("li",null,[Uf,e("a",Tf,[Df,t(s)]),Xf]),e("li",null,[Nf,Jf,Hf,Vf,qf,Wf,Gf,e("a",jf,[Yf,t(s)]),Qf])]),Kf,e("ul",null,[$f,e("li",null,[eg,e("a",og,[tg,t(s)]),sg]),e("li",null,[ig,e("a",ng,[rg,t(s)]),ag]),e("li",null,[lg,dg,hg,e("a",cg,[ug,t(s)]),_g,e("a",pg,[fg,t(s)]),gg]),e("li",null,[mg,e("a",bg,[wg,t(s)]),Ig]),e("li",null,[yg,vg,xg,e("a",Sg,[Ag,t(s)]),Bg]),Cg,Eg,Og]),kg,Lg,Mg,e("ul",null,[e("li",null,[zg,e("a",Pg,[Rg,t(s)]),Fg]),Zg,e("li",null,[Ug,e("a",Tg,[Dg,t(s)]),Xg]),e("li",null,[Ng,e("a",Jg,[Hg,t(s)]),Vg]),e("li",null,[qg,Wg,Gg,e("a",jg,[Yg,t(s)]),Qg]),Kg]),$g,em,om,e("ul",null,[e("li",null,[tm,e("a",sm,[im,t(s)]),nm])]),rm,e("ul",null,[am,lm,e("li",null,[dm,e("a",hm,[cm,t(s)])])]),um,e("ul",null,[_m,pm,fm,gm,mm,e("li",null,[bm,wm,Im,e("a",ym,[vm,t(s)]),xm]),Sm,Am,Bm,Cm,e("li",null,[Em,e("a",Om,[km,t(s)]),Lm]),Mm]),zm,Pm,Rm,e("ul",null,[e("li",null,[Fm,e("a",Zm,[Um,t(s)]),Tm]),Dm,Xm,Nm]),Jm,e("ul",null,[Hm,e("li",null,[Vm,e("a",qm,[Wm,t(s)]),Gm]),jm,e("li",null,[Ym,e("a",Qm,[Km,t(s)]),$m,eb,ob]),tb,e("li",null,[sb,e("a",ib,[nb,t(s)]),rb]),e("li",null,[ab,e("a",lb,[db,t(s)]),hb]),e("li",null,[cb,e("a",ub,[_b,t(s)]),pb]),fb]),gb,e("ul",null,[mb,bb,e("li",null,[wb,e("a",Ib,[yb,t(s)]),vb]),e("li",null,[xb,e("a",Sb,[Ab,t(s)]),Bb]),e("li",null,[Cb,e("a",Eb,[Ob,t(s)]),kb]),Lb]),Mb],64)}var Ub=c(u,[["render",zb]]);export{Ub as default};
diff --git a/assets/notices.html.e6f11260.js b/assets/notices.html.8c7eb4f7.js
similarity index 98%
rename from assets/notices.html.e6f11260.js
rename to assets/notices.html.8c7eb4f7.js
index 09a770024..1d322638a 100644
--- a/assets/notices.html.e6f11260.js
+++ b/assets/notices.html.8c7eb4f7.js
@@ -1 +1 @@
-import{c as e}from"./app.f6cb3ed9.js";import{_ as o}from"./plugin-vue_export-helper.21dcd24c.js";const t={},i=e('
       Notices
      This information was developed for products and services offered in the US. This material might be available from IBM\xAE in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it.
      IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user\u2019s responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
      IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
      IBM Director of Licensing, IBM Corporation, North Castle Drive, MD-NC119, Armonk, NY 10504-1785, US
      INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS\u201D WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
      This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
      Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.
      IBM may use or distribute any of the information you provide in any way it believes appropriate without incurring any obligation to you.
      The performance data and client examples cited are presented for illustrative purposes only. Actual performance results may vary depending on specific configurations and operating conditions.
      Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
      Statements regarding IBM\u2019s future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
      This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to actual people or business enterprises is entirely coincidental.
      COPYRIGHT LICENSE:
      This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS\u201D, without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.
      ',15);function r(n,a){return i}var c=o(t,[["render",r]]);export{c as default};
+import{c as e}from"./app.daa93c96.js";import{_ as o}from"./plugin-vue_export-helper.21dcd24c.js";const t={},i=e('
       Notices
      This information was developed for products and services offered in the US. This material might be available from IBM\xAE in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it.
      IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user\u2019s responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
      IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
      IBM Director of Licensing, IBM Corporation, North Castle Drive, MD-NC119, Armonk, NY 10504-1785, US
      INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS\u201D WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
      This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
      Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.
      IBM may use or distribute any of the information you provide in any way it believes appropriate without incurring any obligation to you.
      The performance data and client examples cited are presented for illustrative purposes only. Actual performance results may vary depending on specific configurations and operating conditions.
      Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
      Statements regarding IBM\u2019s future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
      This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to actual people or business enterprises is entirely coincidental.
      COPYRIGHT LICENSE:
      This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS\u201D, without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.
      ',15);function r(n,a){return i}var c=o(t,[["render",r]]);export{c as default};
diff --git a/assets/ocp-ssl-cert.html.a6eed13d.js b/assets/ocp-ssl-cert.html.9c458041.js
similarity index 99%
rename from assets/ocp-ssl-cert.html.a6eed13d.js
rename to assets/ocp-ssl-cert.html.9c458041.js
index a51c771f2..2d0f38871 100644
--- a/assets/ocp-ssl-cert.html.a6eed13d.js
+++ b/assets/ocp-ssl-cert.html.9c458041.js
@@ -1,4 +1,4 @@
-import{r as a,o as r,a as o,b as e,d as s,F as c,e as t,c as i}from"./app.f6cb3ed9.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";const d={},p=e("h1",{id:"ibm-wazi-developer-for-red-hat-codeready-workspaces-set-up-an-ssl-certificate-in-an-openshift-container-platform",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-wazi-developer-for-red-hat-codeready-workspaces-set-up-an-ssl-certificate-in-an-openshift-container-platform","aria-hidden":"true"},"#"),t(" IBM Wazi Developer for Red Hat CodeReady Workspaces: Set up an SSL Certificate in an OpenShift Container Platform")],-1),u=e("blockquote",null,[e("p",null,"by Arvin Bhatnagar")],-1),h=t("A number of cloud based applications that run on OpenShift\xAE Container Platform (OCP) uses a signed "),f={href:"https://www.ibm.com/docs/en/wdfrhcw/1.4.0?topic=guide-working-ssl",target:"_blank",rel:"noopener noreferrer"},m=t("SSL certificate"),b=t(" to provide encryption over the wire. For instance, "),g={href:"https://www.ibm.com/products/wazi-developer",target:"_blank",rel:"noopener noreferrer"},_=t("IBM\xAE Wazi Developer for Red Hat\xAE CodeReady Workspaces"),w=t(", a single integrated solution that delivers a cloud native development experience for z/OS\xAE, uses a signed SSL certificate for encryption by default. More information about IBM Wazi Developer for Red Hat CodeReady Workspaces can be found in the "),v={href:"https://www.ibm.com/docs/en/wdfrhcw/1.4.0",target:"_blank",rel:"noopener noreferrer"},x=t("IBM Documentation"),y=t("."),C=e("h2",{id:"why-a-signed-ssl-certificate-is-needed",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#why-a-signed-ssl-certificate-is-needed","aria-hidden":"true"},"#"),t(" Why a signed SSL certificate is needed")],-1),S=e("p",null,[t("Setting up an OpenShift Container Platform with a signed SSL certificate can present a number of challenges. The challenges are due to complex cloud architectures and the various formats and types of certificates to contend with. These complexities and the volume of information can make the overall process overwhelming to simply replace a default "),e("code",null,"self-signed"),t(" certificate with a "),e("code",null,"signed"),t(" certificate from a "),e("code",null,"trusted"),t(" CA server.")],-1),k=t("An OCP "),q={href:"https://docs.openshift.com/container-platform/4.3/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.html#configuring-ingress-cluster-traffic-ingress-controller",target:"_blank",rel:"noopener noreferrer"},O=t("Ingress Controller"),P=t(" accepts external web based requests and proxys them based on the configured routes. The default certificate for an Ingress Controller is a self-signed certificate used for all applications under the "),E=e("code",null,".apps",-1),A=t(" subdomain. Replacing the default certificate with one issued by a public Certificate of Authority (CA) allows incoming requests to connect securely to cloud based applications without the hassle of security warnings."),R=e("h2",{id:"how-to-set-up-a-signed-ssl-certificate",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#how-to-set-up-a-signed-ssl-certificate","aria-hidden":"true"},"#"),t(" How to set up a signed SSL certificate")],-1),I=e("p",null,"Request a certificate.",-1),L=t("The certificate for the Ingress Controller "),M=e("code",null,".apps",-1),N=t(" subdomain must be a wildcard certificate. For example, if the domain of the OCP is "),T=e("code",null,"openshift.ibm.com",-1),B=t(" then the wildcard would be "),D=e("code",null,"*.apps.openshift.ibm.com",-1),W=t(". A sample certificate server request using the "),F={href:"https://www.openssl.org/",target:"_blank",rel:"noopener noreferrer"},z=t("OpenSSL tool"),U=t(" would be something similar to the following:"),H=i(`
      openssl req -new -sha256 -nodes -out certserverrequest.csr -newkey rsa:2048 -keyout certserverkey.key -config <(
+import{r as a,o as r,a as o,b as e,d as s,F as c,e as t,c as i}from"./app.daa93c96.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";const d={},p=e("h1",{id:"ibm-wazi-developer-for-red-hat-codeready-workspaces-set-up-an-ssl-certificate-in-an-openshift-container-platform",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-wazi-developer-for-red-hat-codeready-workspaces-set-up-an-ssl-certificate-in-an-openshift-container-platform","aria-hidden":"true"},"#"),t(" IBM Wazi Developer for Red Hat CodeReady Workspaces: Set up an SSL Certificate in an OpenShift Container Platform")],-1),u=e("blockquote",null,[e("p",null,"by Arvin Bhatnagar")],-1),h=t("A number of cloud based applications that run on OpenShift\xAE Container Platform (OCP) uses a signed "),f={href:"https://www.ibm.com/docs/en/wdfrhcw/1.4.0?topic=guide-working-ssl",target:"_blank",rel:"noopener noreferrer"},m=t("SSL certificate"),b=t(" to provide encryption over the wire. For instance, "),g={href:"https://www.ibm.com/products/wazi-developer",target:"_blank",rel:"noopener noreferrer"},_=t("IBM\xAE Wazi Developer for Red Hat\xAE CodeReady Workspaces"),w=t(", a single integrated solution that delivers a cloud native development experience for z/OS\xAE, uses a signed SSL certificate for encryption by default. More information about IBM Wazi Developer for Red Hat CodeReady Workspaces can be found in the "),v={href:"https://www.ibm.com/docs/en/wdfrhcw/1.4.0",target:"_blank",rel:"noopener noreferrer"},x=t("IBM Documentation"),y=t("."),C=e("h2",{id:"why-a-signed-ssl-certificate-is-needed",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#why-a-signed-ssl-certificate-is-needed","aria-hidden":"true"},"#"),t(" Why a signed SSL certificate is needed")],-1),S=e("p",null,[t("Setting up an OpenShift Container Platform with a signed SSL certificate can present a number of challenges. The challenges are due to complex cloud architectures and the various formats and types of certificates to contend with. These complexities and the volume of information can make the overall process overwhelming to simply replace a default "),e("code",null,"self-signed"),t(" certificate with a "),e("code",null,"signed"),t(" certificate from a "),e("code",null,"trusted"),t(" CA server.")],-1),k=t("An OCP "),q={href:"https://docs.openshift.com/container-platform/4.3/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.html#configuring-ingress-cluster-traffic-ingress-controller",target:"_blank",rel:"noopener noreferrer"},O=t("Ingress Controller"),P=t(" accepts external web based requests and proxys them based on the configured routes. The default certificate for an Ingress Controller is a self-signed certificate used for all applications under the "),E=e("code",null,".apps",-1),A=t(" subdomain. Replacing the default certificate with one issued by a public Certificate of Authority (CA) allows incoming requests to connect securely to cloud based applications without the hassle of security warnings."),R=e("h2",{id:"how-to-set-up-a-signed-ssl-certificate",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#how-to-set-up-a-signed-ssl-certificate","aria-hidden":"true"},"#"),t(" How to set up a signed SSL certificate")],-1),I=e("p",null,"Request a certificate.",-1),L=t("The certificate for the Ingress Controller "),M=e("code",null,".apps",-1),N=t(" subdomain must be a wildcard certificate. For example, if the domain of the OCP is "),T=e("code",null,"openshift.ibm.com",-1),B=t(" then the wildcard would be "),D=e("code",null,"*.apps.openshift.ibm.com",-1),W=t(". A sample certificate server request using the "),F={href:"https://www.openssl.org/",target:"_blank",rel:"noopener noreferrer"},z=t("OpenSSL tool"),U=t(" would be something similar to the following:"),H=i(`
      openssl req -new -sha256 -nodes -out certserverrequest.csr -newkey rsa:2048 -keyout certserverkey.key -config <(
 cat <<-EOF
 [ req ]
 default_bits = 2048
diff --git a/assets/other_extensions.html.c1f9d46d.js b/assets/other_extensions.html.3b14f121.js
similarity index 98%
rename from assets/other_extensions.html.c1f9d46d.js
rename to assets/other_extensions.html.3b14f121.js
index f822e63bb..507a7a5a9 100644
--- a/assets/other_extensions.html.c1f9d46d.js
+++ b/assets/other_extensions.html.3b14f121.js
@@ -1 +1 @@
-import{r as n,o as i,a as r,b as e,d as s,F as a,e as t}from"./app.f6cb3ed9.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";const d={},c=e("h1",{id:"other-visual-studio-code-extensions",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#other-visual-studio-code-extensions","aria-hidden":"true"},"#"),t(" Other Visual Studio Code extensions")],-1),h=e("p",null,"In addition to IBM Z Open Editor and Zowe Explorer, there are some other Visual Studio Code extensions that provide added value and integrations with technology relevant for enterprise application developers. The following table shows some examples.",-1),_=e("p",null,"Note: These extensions are independent of IBM Z Open Editor and supported by the respective publishers according to their specific terms.",-1),u=e("thead",null,[e("tr",null,[e("th",{style:{"text-align":"center"}},"Extension name"),e("th",null,"Description")])],-1),p=e("td",{style:{"text-align":"center"}},"Ansible",-1),m=t("This extension adds language support for Ansible to Visual Studio Code. It can be used to write Ansible playbooks as well as "),f={href:"https://ibm.github.io/z_ansible_collections_doc/index.html",target:"_blank",rel:"noopener noreferrer"},g=t("Red Hat Ansible Certified Content for IBM Z"),x=t(". To install this extension, see "),b={href:"https://marketplace.visualstudio.com/items?itemName=redhat.ansible",target:"_blank",rel:"noopener noreferrer"},v=t("Ansible"),T=t("."),k=e("td",{style:{"text-align":"center"}},"GitLens",-1),w=t("This is the ultimate extension for using Visual Studio Code with Git providing graphical views and commands for almost all Git capabilities. To install this extension, see "),I={href:"https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens",target:"_blank",rel:"noopener noreferrer"},E=t("GitLens \u2014 Git supercharged"),M=t("."),y=e("td",{style:{"text-align":"center"}},"IBM Db2 for z/OS Developer Extension",-1),C=t("This is an extension for Visual Studio Code that provides language support for developing Db2 for z/OS SQL applications. To install this extension, see "),Z={href:"https://marketplace.visualstudio.com/items?itemName=IBM.db2forzosdeveloperextension",target:"_blank",rel:"noopener noreferrer"},S=t("IBM Db2 for z/OS Developer Extension"),B=t("."),O=e("td",{style:{"text-align":"center"}},"IBM Z Open Debug",-1),N=t("This extension provides a Debugger user interface in Visual Studio Code for COBOL and other languages using the IBM Z Debugger. It consists of two extensions: the core "),A={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopendebug",target:"_blank",rel:"noopener noreferrer"},D=t("IBM Z Open Debug"),L=t(" and the graphical "),V={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopendebug-profileui",target:"_blank",rel:"noopener noreferrer"},z=t("IBM Z Open Debug Profiles view"),P=t("."),F=e("td",{style:{"text-align":"center"}},"Todo Tree",-1),G=t("This is a popular extension for navigating and managing comment tags such as TODO in source code. To install this extension, see "),Y={href:"https://marketplace.visualstudio.com/items?itemName=Gruntfuggly.todo-tree",target:"_blank",rel:"noopener noreferrer"},R=t("Todo Tree"),H=t("."),J=e("td",{style:{"text-align":"center"}},"YAML",-1),Q=t("Z Open Editor uses YAML for configuration files such as ZAPP. The YAML extension provides comprehensive YAML language support to Visual Studio Code to read the JSON/YAML schema and provide code completion and validation. To install this extension, see "),j={href:"https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml",target:"_blank",rel:"noopener noreferrer"},q=t("YAML"),K=t("."),U=e("td",{style:{"text-align":"center"}},"Zowe Explorer Extension for FTP",-1),W=t("Zowe Explorer is loaded by Z Open Editor and supports RSE API and z/OSMF, but if you want to use FTP as a transfer protocol, you can install "),X={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.zowe-explorer-ftp-extension",target:"_blank",rel:"noopener noreferrer"},$=t("Zowe Explorer Extension for FTP"),ee=t("."),te=e("td",{style:{"text-align":"center"}},"Zowe Explorer for IBM CICS",-1),oe=t("This CICS Extension for Zowe Explorer adds additional functionality to the popular Visual Studio Code extension, Zowe Explorer. This extension allows interactions with CICS regions and programs and provides the ability to run commands against them. To install this extension, see "),se={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.cics-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},ne=t("Zowe Explorer for IBM CICS"),ie=t(".");function re(ae,le){const o=n("ExternalLinkIcon");return i(),r(a,null,[c,h,_,e("table",null,[u,e("tbody",null,[e("tr",null,[p,e("td",null,[m,e("a",f,[g,s(o)]),x,e("a",b,[v,s(o)]),T])]),e("tr",null,[k,e("td",null,[w,e("a",I,[E,s(o)]),M])]),e("tr",null,[y,e("td",null,[C,e("a",Z,[S,s(o)]),B])]),e("tr",null,[O,e("td",null,[N,e("a",A,[D,s(o)]),L,e("a",V,[z,s(o)]),P])]),e("tr",null,[F,e("td",null,[G,e("a",Y,[R,s(o)]),H])]),e("tr",null,[J,e("td",null,[Q,e("a",j,[q,s(o)]),K])]),e("tr",null,[U,e("td",null,[W,e("a",X,[$,s(o)]),ee])]),e("tr",null,[te,e("td",null,[oe,e("a",se,[ne,s(o)]),ie])])])])],64)}var he=l(d,[["render",re]]);export{he as default};
+import{r as n,o as i,a as r,b as e,d as s,F as a,e as t}from"./app.daa93c96.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";const d={},c=e("h1",{id:"other-visual-studio-code-extensions",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#other-visual-studio-code-extensions","aria-hidden":"true"},"#"),t(" Other Visual Studio Code extensions")],-1),h=e("p",null,"In addition to IBM Z Open Editor and Zowe Explorer, there are some other Visual Studio Code extensions that provide added value and integrations with technology relevant for enterprise application developers. The following table shows some examples.",-1),_=e("p",null,"Note: These extensions are independent of IBM Z Open Editor and supported by the respective publishers according to their specific terms.",-1),u=e("thead",null,[e("tr",null,[e("th",{style:{"text-align":"center"}},"Extension name"),e("th",null,"Description")])],-1),p=e("td",{style:{"text-align":"center"}},"Ansible",-1),m=t("This extension adds language support for Ansible to Visual Studio Code. It can be used to write Ansible playbooks as well as "),f={href:"https://ibm.github.io/z_ansible_collections_doc/index.html",target:"_blank",rel:"noopener noreferrer"},g=t("Red Hat Ansible Certified Content for IBM Z"),x=t(". To install this extension, see "),b={href:"https://marketplace.visualstudio.com/items?itemName=redhat.ansible",target:"_blank",rel:"noopener noreferrer"},v=t("Ansible"),T=t("."),k=e("td",{style:{"text-align":"center"}},"GitLens",-1),w=t("This is the ultimate extension for using Visual Studio Code with Git providing graphical views and commands for almost all Git capabilities. To install this extension, see "),I={href:"https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens",target:"_blank",rel:"noopener noreferrer"},E=t("GitLens \u2014 Git supercharged"),M=t("."),y=e("td",{style:{"text-align":"center"}},"IBM Db2 for z/OS Developer Extension",-1),C=t("This is an extension for Visual Studio Code that provides language support for developing Db2 for z/OS SQL applications. To install this extension, see "),Z={href:"https://marketplace.visualstudio.com/items?itemName=IBM.db2forzosdeveloperextension",target:"_blank",rel:"noopener noreferrer"},S=t("IBM Db2 for z/OS Developer Extension"),B=t("."),O=e("td",{style:{"text-align":"center"}},"IBM Z Open Debug",-1),N=t("This extension provides a Debugger user interface in Visual Studio Code for COBOL and other languages using the IBM Z Debugger. It consists of two extensions: the core "),A={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopendebug",target:"_blank",rel:"noopener noreferrer"},D=t("IBM Z Open Debug"),L=t(" and the graphical "),V={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopendebug-profileui",target:"_blank",rel:"noopener noreferrer"},z=t("IBM Z Open Debug Profiles view"),P=t("."),F=e("td",{style:{"text-align":"center"}},"Todo Tree",-1),G=t("This is a popular extension for navigating and managing comment tags such as TODO in source code. To install this extension, see "),Y={href:"https://marketplace.visualstudio.com/items?itemName=Gruntfuggly.todo-tree",target:"_blank",rel:"noopener noreferrer"},R=t("Todo Tree"),H=t("."),J=e("td",{style:{"text-align":"center"}},"YAML",-1),Q=t("Z Open Editor uses YAML for configuration files such as ZAPP. The YAML extension provides comprehensive YAML language support to Visual Studio Code to read the JSON/YAML schema and provide code completion and validation. To install this extension, see "),j={href:"https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml",target:"_blank",rel:"noopener noreferrer"},q=t("YAML"),K=t("."),U=e("td",{style:{"text-align":"center"}},"Zowe Explorer Extension for FTP",-1),W=t("Zowe Explorer is loaded by Z Open Editor and supports RSE API and z/OSMF, but if you want to use FTP as a transfer protocol, you can install "),X={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.zowe-explorer-ftp-extension",target:"_blank",rel:"noopener noreferrer"},$=t("Zowe Explorer Extension for FTP"),ee=t("."),te=e("td",{style:{"text-align":"center"}},"Zowe Explorer for IBM CICS",-1),oe=t("This CICS Extension for Zowe Explorer adds additional functionality to the popular Visual Studio Code extension, Zowe Explorer. This extension allows interactions with CICS regions and programs and provides the ability to run commands against them. To install this extension, see "),se={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.cics-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},ne=t("Zowe Explorer for IBM CICS"),ie=t(".");function re(ae,le){const o=n("ExternalLinkIcon");return i(),r(a,null,[c,h,_,e("table",null,[u,e("tbody",null,[e("tr",null,[p,e("td",null,[m,e("a",f,[g,s(o)]),x,e("a",b,[v,s(o)]),T])]),e("tr",null,[k,e("td",null,[w,e("a",I,[E,s(o)]),M])]),e("tr",null,[y,e("td",null,[C,e("a",Z,[S,s(o)]),B])]),e("tr",null,[O,e("td",null,[N,e("a",A,[D,s(o)]),L,e("a",V,[z,s(o)]),P])]),e("tr",null,[F,e("td",null,[G,e("a",Y,[R,s(o)]),H])]),e("tr",null,[J,e("td",null,[Q,e("a",j,[q,s(o)]),K])]),e("tr",null,[U,e("td",null,[W,e("a",X,[$,s(o)]),ee])]),e("tr",null,[te,e("td",null,[oe,e("a",se,[ne,s(o)]),ie])])])])],64)}var he=l(d,[["render",re]]);export{he as default};
diff --git a/assets/privacypolicy.html.0065f368.js b/assets/privacypolicy.html.a8014a83.js
similarity index 97%
rename from assets/privacypolicy.html.0065f368.js
rename to assets/privacypolicy.html.a8014a83.js
index 5451ee964..d3e31a362 100644
--- a/assets/privacypolicy.html.0065f368.js
+++ b/assets/privacypolicy.html.a8014a83.js
@@ -1 +1 @@
-import{r as a,o as n,a as r,b as e,d as i,F as s,e as o}from"./app.f6cb3ed9.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const l={},h=e("h1",{id:"privacy-policy-considerations",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#privacy-policy-considerations","aria-hidden":"true"},"#"),o(" Privacy policy considerations")],-1),f=e("p",null,'IBM\xAE Software products, including software as a service solutions, ("Software Offerings\u201D) may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user, or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering\u2019s use of cookies is set forth below.',-1),d=e("p",null,"This Software Offering does not use cookies or other technologies to collect personally identifiable information.",-1),p=e("p",null,"If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent.",-1),u=e("p",null,'For more information about the use of various technologies, including cookies, for these purposes, see IBM\u2019s Privacy Policy at http://www.ibm.com/privacy and IBM\u2019s Online Privacy Statement at http://www.ibm.com/privacy/details the section entitled "Cookies, Web Beacons and Other Technologies\u201D and the "IBM Software Products and Software-as-a-Service Privacy Statement\u201D at http://www.ibm.com/software/info/product-privacy.',-1),_=o("This doc site provides content search capability by using "),y={href:"https://docsearch.algolia.com/",target:"_blank",rel:"noopener noreferrer"},m=o("DocSearch by Algolia"),g=o(". For data that DocSearch collects, check "),b={href:"https://docsearch.algolia.com/docs/faq/#what-data-are-you-collecting",target:"_blank",rel:"noopener noreferrer"},w=o("DocSearch FAQ"),v=o(". This doc site is a subscriber of Aloglia's service, and you can refer to the applicable section of "),k={href:"https://www.algolia.com/policies/privacy/",target:"_blank",rel:"noopener noreferrer"},S=o("Privacy policy of Algolia"),I=o(".");function x(B,O){const t=a("ExternalLinkIcon");return n(),r(s,null,[h,f,d,p,u,e("p",null,[_,e("a",y,[m,i(t)]),g,e("a",b,[w,i(t)]),v,e("a",k,[S,i(t)]),I])],64)}var T=c(l,[["render",x]]);export{T as default};
+import{r as a,o as n,a as r,b as e,d as i,F as s,e as o}from"./app.daa93c96.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const l={},h=e("h1",{id:"privacy-policy-considerations",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#privacy-policy-considerations","aria-hidden":"true"},"#"),o(" Privacy policy considerations")],-1),f=e("p",null,'IBM\xAE Software products, including software as a service solutions, ("Software Offerings\u201D) may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user, or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering\u2019s use of cookies is set forth below.',-1),d=e("p",null,"This Software Offering does not use cookies or other technologies to collect personally identifiable information.",-1),p=e("p",null,"If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent.",-1),u=e("p",null,'For more information about the use of various technologies, including cookies, for these purposes, see IBM\u2019s Privacy Policy at http://www.ibm.com/privacy and IBM\u2019s Online Privacy Statement at http://www.ibm.com/privacy/details the section entitled "Cookies, Web Beacons and Other Technologies\u201D and the "IBM Software Products and Software-as-a-Service Privacy Statement\u201D at http://www.ibm.com/software/info/product-privacy.',-1),_=o("This doc site provides content search capability by using "),y={href:"https://docsearch.algolia.com/",target:"_blank",rel:"noopener noreferrer"},m=o("DocSearch by Algolia"),g=o(". For data that DocSearch collects, check "),b={href:"https://docsearch.algolia.com/docs/faq/#what-data-are-you-collecting",target:"_blank",rel:"noopener noreferrer"},w=o("DocSearch FAQ"),v=o(". This doc site is a subscriber of Aloglia's service, and you can refer to the applicable section of "),k={href:"https://www.algolia.com/policies/privacy/",target:"_blank",rel:"noopener noreferrer"},S=o("Privacy policy of Algolia"),I=o(".");function x(B,O){const t=a("ExternalLinkIcon");return n(),r(s,null,[h,f,d,p,u,e("p",null,[_,e("a",y,[m,i(t)]),g,e("a",b,[w,i(t)]),v,e("a",k,[S,i(t)]),I])],64)}var T=c(l,[["render",x]]);export{T as default};
diff --git a/assets/rse-march-120.html.620ce554.js b/assets/rse-march-120.html.d44ba81e.js
similarity index 99%
rename from assets/rse-march-120.html.620ce554.js
rename to assets/rse-march-120.html.d44ba81e.js
index 20a746aea..8df680009 100644
--- a/assets/rse-march-120.html.620ce554.js
+++ b/assets/rse-march-120.html.d44ba81e.js
@@ -1 +1 @@
-import{r as i,o as s,a as r,b as e,d as t,F as l,c as a,e as o}from"./app.f6cb3ed9.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const c={},h=a('
       Everything you need to know about IBM RSE API Plug-in for Zowe CLI 1.2.0
      by Billie Simmons
       Last updated: 17 March 2021
      We are excited to announce the release of IBM\xAE RSE API Plug-in for Zowe\u2122 CLI (RSE CLI plug-in) 1.2.0 with the following key updates:
       Support for encoding conversion for z/OS MVS
      Starting from RSE CLI plug-in 1.2.0, there are multiple ways to support encoding conversions for MVS. These ways follow the precedence rules below:
      ',6),p=e("li",null,[e("p",null,[o("Add the "),e("code",null,"--encoding"),o(" tag to the end of upload and download CLI commands.")])],-1),u=e("code",null,"--mappings-file",-1),m=o(" tag with location of a mappings file that follows the "),f={href:"https://ibm.github.io/zopeneditor-about/Docs/ebcdic_encoding.html#mappings-file-schema",target:"_blank",rel:"noopener noreferrer"},g=o("schema"),_=o(" set in place."),b=e("p",null,[o("The "),e("code",null,"--mappings-file"),o(" tag can be used via CLI command at the end of MVS upload and download commands to point to a mappings file that is saved locally and not in the default location within the "),e("code",null,"~/.zowe/profiles/rse"),o(" directory, or a ZAPP file that includes the MVS mappings schema.")],-1),w=o("An encoding found in the current workspace within the "),S={href:"https://ibm.github.io/zopeneditor-about/Docs/zapp.html",target:"_blank",rel:"noopener noreferrer"},y=o("ZAPP (Z APPlication) file"),I=o("."),v=e("p",null,"The ZAPP file is created in your development workspace's top-level directory. It can contain project-level property groups as well as other information. This file can be in JSON or YAML format.",-1),z=e("p",null,"An encoding found in the default mappings file.",-1),C=o("The default mappings file is a new file that can be downloaded from the RSE API host component using the CLI command "),k=e("code",null,"zowe rse check conversion-mappings",-1),x=o(". This default mappings file will then be downloaded to the "),E=e("code",null,"~/.zowe/profiles/rse",-1),L=o(" directory. To learn more about RSE CLI plug-in's mappings files, check out the documentation on "),P={href:"https://ibm.github.io/zopeneditor-about/Docs/ebcdic_encoding.html#capabilities",target:"_blank",rel:"noopener noreferrer"},M=o("MVS EBCIDIC code pages and mappings files"),A=o("."),V=e("li",null,[e("p",null,"An encoding set during RSE profile creation."),e("p",null,[o("When creating your RSE profile via CLI command, the "),e("code",null,"--encoding"),o(" tag can added to the command to set a default encoding that can be put in place while using that profile. When you create your RSE profile using Zowe Explorer, you will see an encoding option pop up to enter a default encoding value. In both cases, this value is optional and no default will be set in case you would prefer to use the host encoding settings set by a system administrator.")])],-1),D=e("li",null,[e("p",null,"Server default mappings.")],-1),R=e("h2",{id:"support-for-sso",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#support-for-sso","aria-hidden":"true"},"#"),o(" Support for SSO")],-1),T=o("Starting from 1.2.0, the RSE CLI plug-in has full support for SSO using JSON Web Tokens (JWT) that are provided by the RSE API host component and the use of a "),O={href:"https://docs.zowe.org/stable/user-guide/cli-usingcli.html#using-profiles",target:"_blank",rel:"noopener noreferrer"},Z=o("base profile"),N=o(". This support can also be used by "),B={href:"https://ibm.github.io/zopeneditor-about/Docs/setting_propertygroup.html#mvs-property-groups-using-zowe-profiles",target:"_blank",rel:"noopener noreferrer"},Y=o("IBM Z\xAE Open Editor remote file resolution"),U=o("."),W=a('
       Uploading and downloading MVS files as binary
      You can now add the --binary tag to the commands of uploading and downloading of MVS files. This tag was added to the following commands:
      • upload dir-to-pds
      • upload file-to-data-set
      • download data-set
      • download all-members
      MVS member filter search is supported starting from RSE CLI plug-in 1.2.0, and is realized as a tag to the CLI command zowe rse list all-members by adding --pattern <memberPattern> to the end of the list command.
      You can also use this feature in Zowe Explorer 1.12.0 or later versions by clicking the magnifying glass next to a profile's session name and entering a search pattern similar to HLQ.DATA.SET(*MEM).
       Copying and pasting PDS members
      You can copy and paste PDS members via CLI command and within the Zowe Explorer VS Code extension:
      • CLI command: Use the zowe rse copy data-set command to copy PDS members to a new member in another PDS as well as copy a Sequential data set to a new Sequential data set.
      • Zowe Explorer VS Code extension: Right-click on a PDS member to copy it, and right-click on a different PDS to paste and name the new member.
       Support for UNIX shell commands
      You can now issue UNIX shell commands by using a CLI command. The zowe rse issue unix <command> --cwd <workingDir> command can be issued via terminal, and a JSON that includes stdout and stderr will be returned.
       Changing your password on z/OS
      ',12),q=o("Starting from RSE CLI plug-in 1.2.0, you can change your password on z/OS via a CLI command, rather than green screen. You can now enter the CLI command "),J=e("code",null,"zowe rse change password",-1),X=o(" in a terminal to change your password on z/OS and update the profile's YAML file if the password is stored locally with or without the "),j={href:"https://docs.zowe.org/stable/user-guide/cli-scsplugin.html",target:"_blank",rel:"noopener noreferrer"},F=o("Secure Credential Store Plug-in for Zowe CLI"),H=o(" installed."),Q=o("You can check out all of the commands and their syntax at "),G={href:"https://ibm.github.io/zopeneditor-about/Docs/rse_cli_command.html",target:"_blank",rel:"noopener noreferrer"},K=o("IBM RSE API Plug-in for Zowe CLI commands"),$=o(".");function ee(oe,ne){const n=i("ExternalLinkIcon");return s(),r(l,null,[h,e("ol",null,[p,e("li",null,[e("p",null,[u,m,e("a",f,[g,t(n)]),_]),b]),e("li",null,[e("p",null,[w,e("a",S,[y,t(n)]),I]),v]),e("li",null,[z,e("p",null,[C,k,x,E,L,e("a",P,[M,t(n)]),A])]),V,D]),R,e("p",null,[T,e("a",O,[Z,t(n)]),N,e("a",B,[Y,t(n)]),U]),W,e("p",null,[q,J,X,e("a",j,[F,t(n)]),H]),e("p",null,[Q,e("a",G,[K,t(n)]),$])],64)}var ie=d(c,[["render",ee]]);export{ie as default};
+import{r as i,o as s,a as r,b as e,d as t,F as l,c as a,e as o}from"./app.daa93c96.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const c={},h=a('
       Everything you need to know about IBM RSE API Plug-in for Zowe CLI 1.2.0
      by Billie Simmons
       Last updated: 17 March 2021
      We are excited to announce the release of IBM\xAE RSE API Plug-in for Zowe\u2122 CLI (RSE CLI plug-in) 1.2.0 with the following key updates:
       Support for encoding conversion for z/OS MVS
      Starting from RSE CLI plug-in 1.2.0, there are multiple ways to support encoding conversions for MVS. These ways follow the precedence rules below:
      ',6),p=e("li",null,[e("p",null,[o("Add the "),e("code",null,"--encoding"),o(" tag to the end of upload and download CLI commands.")])],-1),u=e("code",null,"--mappings-file",-1),m=o(" tag with location of a mappings file that follows the "),f={href:"https://ibm.github.io/zopeneditor-about/Docs/ebcdic_encoding.html#mappings-file-schema",target:"_blank",rel:"noopener noreferrer"},g=o("schema"),_=o(" set in place."),b=e("p",null,[o("The "),e("code",null,"--mappings-file"),o(" tag can be used via CLI command at the end of MVS upload and download commands to point to a mappings file that is saved locally and not in the default location within the "),e("code",null,"~/.zowe/profiles/rse"),o(" directory, or a ZAPP file that includes the MVS mappings schema.")],-1),w=o("An encoding found in the current workspace within the "),S={href:"https://ibm.github.io/zopeneditor-about/Docs/zapp.html",target:"_blank",rel:"noopener noreferrer"},y=o("ZAPP (Z APPlication) file"),I=o("."),v=e("p",null,"The ZAPP file is created in your development workspace's top-level directory. It can contain project-level property groups as well as other information. This file can be in JSON or YAML format.",-1),z=e("p",null,"An encoding found in the default mappings file.",-1),C=o("The default mappings file is a new file that can be downloaded from the RSE API host component using the CLI command "),k=e("code",null,"zowe rse check conversion-mappings",-1),x=o(". This default mappings file will then be downloaded to the "),E=e("code",null,"~/.zowe/profiles/rse",-1),L=o(" directory. To learn more about RSE CLI plug-in's mappings files, check out the documentation on "),P={href:"https://ibm.github.io/zopeneditor-about/Docs/ebcdic_encoding.html#capabilities",target:"_blank",rel:"noopener noreferrer"},M=o("MVS EBCIDIC code pages and mappings files"),A=o("."),V=e("li",null,[e("p",null,"An encoding set during RSE profile creation."),e("p",null,[o("When creating your RSE profile via CLI command, the "),e("code",null,"--encoding"),o(" tag can added to the command to set a default encoding that can be put in place while using that profile. When you create your RSE profile using Zowe Explorer, you will see an encoding option pop up to enter a default encoding value. In both cases, this value is optional and no default will be set in case you would prefer to use the host encoding settings set by a system administrator.")])],-1),D=e("li",null,[e("p",null,"Server default mappings.")],-1),R=e("h2",{id:"support-for-sso",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#support-for-sso","aria-hidden":"true"},"#"),o(" Support for SSO")],-1),T=o("Starting from 1.2.0, the RSE CLI plug-in has full support for SSO using JSON Web Tokens (JWT) that are provided by the RSE API host component and the use of a "),O={href:"https://docs.zowe.org/stable/user-guide/cli-usingcli.html#using-profiles",target:"_blank",rel:"noopener noreferrer"},Z=o("base profile"),N=o(". This support can also be used by "),B={href:"https://ibm.github.io/zopeneditor-about/Docs/setting_propertygroup.html#mvs-property-groups-using-zowe-profiles",target:"_blank",rel:"noopener noreferrer"},Y=o("IBM Z\xAE Open Editor remote file resolution"),U=o("."),W=a('
       Uploading and downloading MVS files as binary
      You can now add the --binary tag to the commands of uploading and downloading of MVS files. This tag was added to the following commands:
      • upload dir-to-pds
      • upload file-to-data-set
      • download data-set
      • download all-members
      MVS member filter search is supported starting from RSE CLI plug-in 1.2.0, and is realized as a tag to the CLI command zowe rse list all-members by adding --pattern <memberPattern> to the end of the list command.
      You can also use this feature in Zowe Explorer 1.12.0 or later versions by clicking the magnifying glass next to a profile's session name and entering a search pattern similar to HLQ.DATA.SET(*MEM).
       Copying and pasting PDS members
      You can copy and paste PDS members via CLI command and within the Zowe Explorer VS Code extension:
      • CLI command: Use the zowe rse copy data-set command to copy PDS members to a new member in another PDS as well as copy a Sequential data set to a new Sequential data set.
      • Zowe Explorer VS Code extension: Right-click on a PDS member to copy it, and right-click on a different PDS to paste and name the new member.
       Support for UNIX shell commands
      You can now issue UNIX shell commands by using a CLI command. The zowe rse issue unix <command> --cwd <workingDir> command can be issued via terminal, and a JSON that includes stdout and stderr will be returned.
       Changing your password on z/OS
      ',12),q=o("Starting from RSE CLI plug-in 1.2.0, you can change your password on z/OS via a CLI command, rather than green screen. You can now enter the CLI command "),J=e("code",null,"zowe rse change password",-1),X=o(" in a terminal to change your password on z/OS and update the profile's YAML file if the password is stored locally with or without the "),j={href:"https://docs.zowe.org/stable/user-guide/cli-scsplugin.html",target:"_blank",rel:"noopener noreferrer"},F=o("Secure Credential Store Plug-in for Zowe CLI"),H=o(" installed."),Q=o("You can check out all of the commands and their syntax at "),G={href:"https://ibm.github.io/zopeneditor-about/Docs/rse_cli_command.html",target:"_blank",rel:"noopener noreferrer"},K=o("IBM RSE API Plug-in for Zowe CLI commands"),$=o(".");function ee(oe,ne){const n=i("ExternalLinkIcon");return s(),r(l,null,[h,e("ol",null,[p,e("li",null,[e("p",null,[u,m,e("a",f,[g,t(n)]),_]),b]),e("li",null,[e("p",null,[w,e("a",S,[y,t(n)]),I]),v]),e("li",null,[z,e("p",null,[C,k,x,E,L,e("a",P,[M,t(n)]),A])]),V,D]),R,e("p",null,[T,e("a",O,[Z,t(n)]),N,e("a",B,[Y,t(n)]),U]),W,e("p",null,[q,J,X,e("a",j,[F,t(n)]),H]),e("p",null,[Q,e("a",G,[K,t(n)]),$])],64)}var ie=d(c,[["render",ee]]);export{ie as default};
diff --git a/assets/rse-march-beta.html.8a9f3fcc.js b/assets/rse-march-beta.html.26161367.js
similarity index 99%
rename from assets/rse-march-beta.html.8a9f3fcc.js
rename to assets/rse-march-beta.html.26161367.js
index 539ee53dc..530e6f443 100644
--- a/assets/rse-march-beta.html.8a9f3fcc.js
+++ b/assets/rse-march-beta.html.26161367.js
@@ -1 +1 @@
-import{r as a,o as r,a as l,b as e,d as t,w as s,F as d,e as o,c as h}from"./app.f6cb3ed9.js";import{_ as c}from"./rse-help-web.56c77c6d.js";import{_ as u}from"./plugin-vue_export-helper.21dcd24c.js";var p="/zopeneditor-about/assets/rse-create-ds.33c30614.gif";const _={},m=e("h1",{id:"interacting-with-z-os-using-ibm-rse-api-plug-in-for-zowe-cli",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#interacting-with-z-os-using-ibm-rse-api-plug-in-for-zowe-cli","aria-hidden":"true"},"#"),o(" Interacting with z/OS using IBM RSE API Plug-in for Zowe CLI")],-1),w=e("blockquote",null,[e("p",null,[o("by Billie Simmons."),e("br"),o(" Last updated: 10 June, 2020")])],-1),f=e("p",null,[e("strong",null,"Update"),o(": As of 12 June, 2020 IBM RSE API Plug-in for Zowe CLI is generally available.")],-1),g=o("We are excited to announce the Beta release of "),b={href:"https://ibm.github.io/mainframe-downloads/downloads.html",target:"_blank",rel:"noopener noreferrer"},I=o("IBM RSE API Plug-in for Zowe CLI"),S=o(", which now comes packaged with the VS Code download for IBM Developer for z/OS Enterprise Edition. This plug-in allows you to interact with z/OS by using "),E={href:"https://ibm.github.io/mainframe-downloads/downloads.html/#aqua",target:"_blank",rel:"noopener noreferrer"},x=o("IBM Remote System Explorer API (RSE API)"),y=o(", which now comes packaged with IBM Explorer for z/OS. If you have already used the Remote System Explorer (RSE) with other IBM offerings such as IBM Developer for z/OS or IBM Explorer for z/OS, this plug-in was built just for you."),v=o("When using the IBM RSE API Plug-in for Zowe CLI with RSE API support, not only can you execute CLI operations, but you can also use the RSE protocol in combination with the "),R={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},C=o("Zowe Explorer"),B=o(" (v1.3.1 and above) and "),P={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},k=o("IBM Z Open Editor"),z=o(" VS Code extensions to graphically navigate and access file and job resources on your host system. The IBM Z Open Editor VS Code extension allows you to activate the use of the RSE plug-in profiles within Zowe Explorer in "),M={href:"https://code.visualstudio.com/",target:"_blank",rel:"noopener noreferrer"},Z=o("VS Code"),L=o(". You can use the RSE plug-in to perform the following tasks:"),A=e("ul",null,[e("li",null,"List, create, rename, delete USS files and directories and MVS data sets and members"),e("li",null,"Run JCL"),e("li",null,"Browse job spool files"),e("li",null,"Edit COBOL and PL/I files on z/OS by using the IBM Z Open Editor and Zowe Explorer VS Code extensions")],-1),O=o("All commands and actions using Zowe Explorer that the Zowe CLI Profile offers are available using the RSE Profile with a few exceptions that are documented in our "),U=o("Known Issues"),V=o(" page. For details about getting started with IBM RSE API Plug-in for Zowe CLI, check out our documentation on "),j=o("Interacting with z/OS\xAE using RSE API"),D=o("."),N=h('
       Using the RSE Plug-in via command line
      The RSE plug-in can be used in a command-line window on your development machine. Using it this way allows you to issue commands to perform the following tasks:
      • List, create, download, upload, and delete MVS data sets and members as well as USS files and directories.
      • Submit jobs, list jobs and spool files, download or view spool content, view job status, cancel a job, and delete a job.
      You can learn more about any command and all of its options simply by adding --help after the command. For instance, by typing zowe rse list --help, you can see all of the different items that can be listed using the RSE plug-in and a help response that gives details about the options as a response within the command-line window. You can also view help for all of the options through your web browser by adding --help-web after the command.
      Viewing Web Help
      ',5),T=o("For more information and a chart of all the available CLI commands IBM RSE API Plug-in for Zowe CLI has to offer at this time, take a look at our documentation on "),W=o("Using the RSE API CLI"),F=o("."),J=e("h2",{id:"using-an-rse-profile-with-the-zowe-explorer-vs-code-extension",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-an-rse-profile-with-the-zowe-explorer-vs-code-extension","aria-hidden":"true"},"#"),o(" Using an RSE profile with the Zowe Explorer VS Code extension")],-1),q=e("p",null,"Zowe Explorer now has an extensibility API that supports adding other protocols and IBM Z Open Editor includes such an extension utilizing the RSE CLI Plugin codebase. With this extensibility, having the IBM Z Open Editor VS Code extension allows you to use an RSE profile to connect to the host using Zowe Explorer to view a tree list of data sets and members in the DATA SETS view, UNIX files and directories in the UNIX SYSTEM SERVICES (USS) view, and jobs with spool files in the JOBS view.",-1),Y=e("p",null,"Within the Zowe Explorer views, you can perform the following tasks using the RSE plug-in:",-1),H=e("ul",null,[e("li",null,"Create, edit, save, rename, delete data sets, members, UNIX files, and directories on the host."),e("li",null,"Upload local files as a partitioned data set member or as a sequential data set."),e("li",null,"Submit JCL data sets or members as a job, delete jobs, download job spool files from the host to a local directory, and view job spool files in the text editor.")],-1),X=e("p",null,[e("img",{src:p,alt:"Creating a New Data Set"})],-1),G=o("If you would like to know more about managing data sets using the Zowe Explorer VS Code extension, see our documentation on "),K=o("Manipulating data sets"),Q=o("."),$=o("To learn how to use IBM RSE API Plug-in for Zowe CLI with Zowe Explorer and IBM Z Open Editor, check out our documentation on "),ee=o("Using RSE API in the Zowe Explorer VS Code extension"),oe=o("."),te=e("h2",{id:"getting-hands-on",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#getting-hands-on","aria-hidden":"true"},"#"),o(" Getting hands-on")],-1),ne=e("p",null,"Many developers learn best with hands-on experience, so we have developed a few exercises through which you can explore the different ways of using IBM RSE API Plug-in for Zowe CLI. Our tutorial covers three great approaches to managing z/OS resources with the plug-in:",-1),se=o("Using the Zowe Explorer VS Code extension"),ie=o("Using a command-line terminal"),ae=o("Using a script to automate command-line operations"),re=o("Ready to try out these hands-on approaches? Head over to the "),le=o("Tutorial"),de=o(" page, which will point you to a sample repository and get you started with creating your RSE profile."),he=e("p",null,"Take a look at my video tutorials that cover these three approaches:",-1),ce={href:"https://youtu.be/DU-1njRPcEA",target:"_blank",rel:"noopener noreferrer"},ue=o("IBM RSE API Plug-in for Zowe CLI: Using Command-line operations"),pe={href:"https://youtu.be/N9O508fUBgw",target:"_blank",rel:"noopener noreferrer"},_e=o("IBM RSE API Plug-in for Zowe CLI: Using VS Code"),me=e("h2",{id:"we-would-love-to-hear-from-you",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#we-would-love-to-hear-from-you","aria-hidden":"true"},"#"),o(" We would love to hear from you")],-1),we=o("Once you have tried out IBM RSE API Plug-in for Zowe CLI, we would love to hear what you think of it. For any questions, issues, or enhancement ideas, please do not hesitate to open an issue at our "),fe={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},ge=o("GitHub"),be=o(". We are always looking for ways to improve our product.");function Ie(Se,Ee){const i=a("ExternalLinkIcon"),n=a("RouterLink");return r(),l(d,null,[m,w,f,e("p",null,[g,e("a",b,[I,t(i)]),S,e("a",E,[x,t(i)]),y]),e("p",null,[v,e("a",R,[C,t(i)]),B,e("a",P,[k,t(i)]),z,e("a",M,[Z,t(i)]),L]),A,e("p",null,[O,t(n,{to:"/Docs/knownissues.html#ibm-rse-api-plug-in-for-zowe-cli"},{default:s(()=>[U]),_:1}),V,t(n,{to:"/Docs/setup_integration.html#setting-up-integrations-to-interact-with-z-os"},{default:s(()=>[j]),_:1}),D]),N,e("p",null,[T,t(n,{to:"/Docs/interact_zos_cli.html"},{default:s(()=>[W]),_:1}),F]),J,q,Y,H,X,e("p",null,[G,t(n,{to:"/Docs/interact_zos_zowe_explorer.html#example-how-to-manipulate-data-sets-with-zowe-explorer"},{default:s(()=>[K]),_:1}),Q]),e("p",null,[$,t(n,{to:"/Docs/interact_zos_zowe_explorer.html"},{default:s(()=>[ee]),_:1}),oe]),te,ne,e("ul",null,[e("li",null,[t(n,{to:"/Docs/rse_tutorial.html#approach-1-using-the-zowe-explorer-vs-code-extension-to-manage-z-os-resources"},{default:s(()=>[se]),_:1})]),e("li",null,[t(n,{to:"/Docs/rse_tutorial.html#approach-2-using-a-command-line-terminal-to-manage-z-os-resources"},{default:s(()=>[ie]),_:1})]),e("li",null,[t(n,{to:"/Docs/rse_tutorial.html#approach-3-using-a-script-to-automate-command-line-operations-against-z-os-resources"},{default:s(()=>[ae]),_:1})])]),e("p",null,[re,t(n,{to:"/Docs/rse_tutorial.html"},{default:s(()=>[le]),_:1}),de]),he,e("ul",null,[e("li",null,[e("a",ce,[ue,t(i)])]),e("li",null,[e("a",pe,[_e,t(i)])])]),me,e("p",null,[we,e("a",fe,[ge,t(i)]),be])],64)}var Re=u(_,[["render",Ie]]);export{Re as default};
+import{r as a,o as r,a as l,b as e,d as t,w as s,F as d,e as o,c as h}from"./app.daa93c96.js";import{_ as c}from"./rse-help-web.56c77c6d.js";import{_ as u}from"./plugin-vue_export-helper.21dcd24c.js";var p="/zopeneditor-about/assets/rse-create-ds.33c30614.gif";const _={},m=e("h1",{id:"interacting-with-z-os-using-ibm-rse-api-plug-in-for-zowe-cli",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#interacting-with-z-os-using-ibm-rse-api-plug-in-for-zowe-cli","aria-hidden":"true"},"#"),o(" Interacting with z/OS using IBM RSE API Plug-in for Zowe CLI")],-1),w=e("blockquote",null,[e("p",null,[o("by Billie Simmons."),e("br"),o(" Last updated: 10 June, 2020")])],-1),f=e("p",null,[e("strong",null,"Update"),o(": As of 12 June, 2020 IBM RSE API Plug-in for Zowe CLI is generally available.")],-1),g=o("We are excited to announce the Beta release of "),b={href:"https://ibm.github.io/mainframe-downloads/downloads.html",target:"_blank",rel:"noopener noreferrer"},I=o("IBM RSE API Plug-in for Zowe CLI"),S=o(", which now comes packaged with the VS Code download for IBM Developer for z/OS Enterprise Edition. This plug-in allows you to interact with z/OS by using "),E={href:"https://ibm.github.io/mainframe-downloads/downloads.html/#aqua",target:"_blank",rel:"noopener noreferrer"},x=o("IBM Remote System Explorer API (RSE API)"),y=o(", which now comes packaged with IBM Explorer for z/OS. If you have already used the Remote System Explorer (RSE) with other IBM offerings such as IBM Developer for z/OS or IBM Explorer for z/OS, this plug-in was built just for you."),v=o("When using the IBM RSE API Plug-in for Zowe CLI with RSE API support, not only can you execute CLI operations, but you can also use the RSE protocol in combination with the "),R={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},C=o("Zowe Explorer"),B=o(" (v1.3.1 and above) and "),P={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},k=o("IBM Z Open Editor"),z=o(" VS Code extensions to graphically navigate and access file and job resources on your host system. The IBM Z Open Editor VS Code extension allows you to activate the use of the RSE plug-in profiles within Zowe Explorer in "),M={href:"https://code.visualstudio.com/",target:"_blank",rel:"noopener noreferrer"},Z=o("VS Code"),L=o(". You can use the RSE plug-in to perform the following tasks:"),A=e("ul",null,[e("li",null,"List, create, rename, delete USS files and directories and MVS data sets and members"),e("li",null,"Run JCL"),e("li",null,"Browse job spool files"),e("li",null,"Edit COBOL and PL/I files on z/OS by using the IBM Z Open Editor and Zowe Explorer VS Code extensions")],-1),O=o("All commands and actions using Zowe Explorer that the Zowe CLI Profile offers are available using the RSE Profile with a few exceptions that are documented in our "),U=o("Known Issues"),V=o(" page. For details about getting started with IBM RSE API Plug-in for Zowe CLI, check out our documentation on "),j=o("Interacting with z/OS\xAE using RSE API"),D=o("."),N=h('
       Using the RSE Plug-in via command line
      The RSE plug-in can be used in a command-line window on your development machine. Using it this way allows you to issue commands to perform the following tasks:
      • List, create, download, upload, and delete MVS data sets and members as well as USS files and directories.
      • Submit jobs, list jobs and spool files, download or view spool content, view job status, cancel a job, and delete a job.
      You can learn more about any command and all of its options simply by adding --help after the command. For instance, by typing zowe rse list --help, you can see all of the different items that can be listed using the RSE plug-in and a help response that gives details about the options as a response within the command-line window. You can also view help for all of the options through your web browser by adding --help-web after the command.
      Viewing Web Help
      ',5),T=o("For more information and a chart of all the available CLI commands IBM RSE API Plug-in for Zowe CLI has to offer at this time, take a look at our documentation on "),W=o("Using the RSE API CLI"),F=o("."),J=e("h2",{id:"using-an-rse-profile-with-the-zowe-explorer-vs-code-extension",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-an-rse-profile-with-the-zowe-explorer-vs-code-extension","aria-hidden":"true"},"#"),o(" Using an RSE profile with the Zowe Explorer VS Code extension")],-1),q=e("p",null,"Zowe Explorer now has an extensibility API that supports adding other protocols and IBM Z Open Editor includes such an extension utilizing the RSE CLI Plugin codebase. With this extensibility, having the IBM Z Open Editor VS Code extension allows you to use an RSE profile to connect to the host using Zowe Explorer to view a tree list of data sets and members in the DATA SETS view, UNIX files and directories in the UNIX SYSTEM SERVICES (USS) view, and jobs with spool files in the JOBS view.",-1),Y=e("p",null,"Within the Zowe Explorer views, you can perform the following tasks using the RSE plug-in:",-1),H=e("ul",null,[e("li",null,"Create, edit, save, rename, delete data sets, members, UNIX files, and directories on the host."),e("li",null,"Upload local files as a partitioned data set member or as a sequential data set."),e("li",null,"Submit JCL data sets or members as a job, delete jobs, download job spool files from the host to a local directory, and view job spool files in the text editor.")],-1),X=e("p",null,[e("img",{src:p,alt:"Creating a New Data Set"})],-1),G=o("If you would like to know more about managing data sets using the Zowe Explorer VS Code extension, see our documentation on "),K=o("Manipulating data sets"),Q=o("."),$=o("To learn how to use IBM RSE API Plug-in for Zowe CLI with Zowe Explorer and IBM Z Open Editor, check out our documentation on "),ee=o("Using RSE API in the Zowe Explorer VS Code extension"),oe=o("."),te=e("h2",{id:"getting-hands-on",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#getting-hands-on","aria-hidden":"true"},"#"),o(" Getting hands-on")],-1),ne=e("p",null,"Many developers learn best with hands-on experience, so we have developed a few exercises through which you can explore the different ways of using IBM RSE API Plug-in for Zowe CLI. Our tutorial covers three great approaches to managing z/OS resources with the plug-in:",-1),se=o("Using the Zowe Explorer VS Code extension"),ie=o("Using a command-line terminal"),ae=o("Using a script to automate command-line operations"),re=o("Ready to try out these hands-on approaches? Head over to the "),le=o("Tutorial"),de=o(" page, which will point you to a sample repository and get you started with creating your RSE profile."),he=e("p",null,"Take a look at my video tutorials that cover these three approaches:",-1),ce={href:"https://youtu.be/DU-1njRPcEA",target:"_blank",rel:"noopener noreferrer"},ue=o("IBM RSE API Plug-in for Zowe CLI: Using Command-line operations"),pe={href:"https://youtu.be/N9O508fUBgw",target:"_blank",rel:"noopener noreferrer"},_e=o("IBM RSE API Plug-in for Zowe CLI: Using VS Code"),me=e("h2",{id:"we-would-love-to-hear-from-you",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#we-would-love-to-hear-from-you","aria-hidden":"true"},"#"),o(" We would love to hear from you")],-1),we=o("Once you have tried out IBM RSE API Plug-in for Zowe CLI, we would love to hear what you think of it. For any questions, issues, or enhancement ideas, please do not hesitate to open an issue at our "),fe={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},ge=o("GitHub"),be=o(". We are always looking for ways to improve our product.");function Ie(Se,Ee){const i=a("ExternalLinkIcon"),n=a("RouterLink");return r(),l(d,null,[m,w,f,e("p",null,[g,e("a",b,[I,t(i)]),S,e("a",E,[x,t(i)]),y]),e("p",null,[v,e("a",R,[C,t(i)]),B,e("a",P,[k,t(i)]),z,e("a",M,[Z,t(i)]),L]),A,e("p",null,[O,t(n,{to:"/Docs/knownissues.html#ibm-rse-api-plug-in-for-zowe-cli"},{default:s(()=>[U]),_:1}),V,t(n,{to:"/Docs/setup_integration.html#setting-up-integrations-to-interact-with-z-os"},{default:s(()=>[j]),_:1}),D]),N,e("p",null,[T,t(n,{to:"/Docs/interact_zos_cli.html"},{default:s(()=>[W]),_:1}),F]),J,q,Y,H,X,e("p",null,[G,t(n,{to:"/Docs/interact_zos_zowe_explorer.html#example-how-to-manipulate-data-sets-with-zowe-explorer"},{default:s(()=>[K]),_:1}),Q]),e("p",null,[$,t(n,{to:"/Docs/interact_zos_zowe_explorer.html"},{default:s(()=>[ee]),_:1}),oe]),te,ne,e("ul",null,[e("li",null,[t(n,{to:"/Docs/rse_tutorial.html#approach-1-using-the-zowe-explorer-vs-code-extension-to-manage-z-os-resources"},{default:s(()=>[se]),_:1})]),e("li",null,[t(n,{to:"/Docs/rse_tutorial.html#approach-2-using-a-command-line-terminal-to-manage-z-os-resources"},{default:s(()=>[ie]),_:1})]),e("li",null,[t(n,{to:"/Docs/rse_tutorial.html#approach-3-using-a-script-to-automate-command-line-operations-against-z-os-resources"},{default:s(()=>[ae]),_:1})])]),e("p",null,[re,t(n,{to:"/Docs/rse_tutorial.html"},{default:s(()=>[le]),_:1}),de]),he,e("ul",null,[e("li",null,[e("a",ce,[ue,t(i)])]),e("li",null,[e("a",pe,[_e,t(i)])])]),me,e("p",null,[we,e("a",fe,[ge,t(i)]),be])],64)}var Re=u(_,[["render",Ie]]);export{Re as default};
diff --git a/assets/rse-october-110.html.c685cff7.js b/assets/rse-october-110.html.eb06bfc1.js
similarity index 99%
rename from assets/rse-october-110.html.c685cff7.js
rename to assets/rse-october-110.html.eb06bfc1.js
index 9b7756136..2ba190c62 100644
--- a/assets/rse-october-110.html.c685cff7.js
+++ b/assets/rse-october-110.html.eb06bfc1.js
@@ -1,4 +1,4 @@
-import{r as n,o as i,a as r,b as o,d as a,w as s,F as h,c as d,e}from"./app.f6cb3ed9.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";var c="/zopeneditor-about/assets/rse-binary-dl.2362361f.png",u="/zopeneditor-about/assets/rse-bin-dl-example.1252e8b1.png",p="/zopeneditor-about/assets/rse-check-status.a3a1cd80.png",m="/zopeneditor-about/assets/rse-issue-command.762f18b1.gif";const f={},w=d(`
       What's new with IBM RSE API Plug-in for Zowe CLI 1.1.0
      by Billie Simmons.
       Last updated: 19 October, 2020
      There are some great new features in IBM RSE API Plug-in for Zowe CLI 1.1.0 that we are excited to share. With this release in conjunction with the release of IBM Remote System Explorer API (RSE API) 1.0.1, we will be introducing the following capabilities:
      These new features in the IBM RSE API Plug-in for Zowe CLI with RSE API support are introduced for execution as CLI operations.
       Download UNIX files as binary
      In this release, the binary tag for downloading UNIX files has been added as an option for downloading a USS file without translation via CLI command. You can find an example in the command help doc by issuing the following command:
      zowe rse download uss-file --help
+import{r as n,o as i,a as r,b as o,d as a,w as s,F as h,c as d,e}from"./app.daa93c96.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";var c="/zopeneditor-about/assets/rse-binary-dl.2362361f.png",u="/zopeneditor-about/assets/rse-bin-dl-example.1252e8b1.png",p="/zopeneditor-about/assets/rse-check-status.a3a1cd80.png",m="/zopeneditor-about/assets/rse-issue-command.762f18b1.gif";const f={},w=d(`
       What's new with IBM RSE API Plug-in for Zowe CLI 1.1.0
      by Billie Simmons.
       Last updated: 19 October, 2020
      There are some great new features in IBM RSE API Plug-in for Zowe CLI 1.1.0 that we are excited to share. With this release in conjunction with the release of IBM Remote System Explorer API (RSE API) 1.0.1, we will be introducing the following capabilities:
      These new features in the IBM RSE API Plug-in for Zowe CLI with RSE API support are introduced for execution as CLI operations.
       Download UNIX files as binary
      In this release, the binary tag for downloading UNIX files has been added as an option for downloading a USS file without translation via CLI command. You can find an example in the command help doc by issuing the following command:
      zowe rse download uss-file --help
 
      Download Binary OptionBinary Download Command Example
       Get system and application information from the host
      Another new feature is the Check Status command that can be used to confirm that the RSE API server is running, as well as to gather information about the RSE API server for diagnostic puposes. The command outputs properties of the RSE API server such as the RSE version, RSE API version, and the port the server is running on, as well as z/OS system information such as the z/OS version and the host name.
      zowe rse check status
 
      The output contains the following information:
      Check Status Output
       Issue TSO commands
      IBM RSE API plug-in for Zowe CLI now has TSO capabilities, allowing users to input TSO commands and get a response back from a TSO session. To use it, replace COMMAND with your TSO command in the CLI command example below.
      zowe rse issue command "COMMMAND"
 
      This command creates a TSO address space, issues the TSO command through the newly created address space, waits for the READY prompt to print the response, and then terminates the TSO address space after returning the response.
      Issue TSO Command
       Use JSON Web Tokens (JWT) for authentication with the host
      Last, but definitely not least, is the addition of the use of JSON Web Tokens (JWT) for authentication with the host. This feature allows you to connect to the RSE API Server authentication service and obtain a token. The token provides authentication to services that are supported by the RSE API. When you log in, the token is stored in your profile's local YAML file until you issue the logout command. Profiles store connection information, and are used if you do not supply connection information in a command. This addition brings in three new commands that include:
      • zowe rse auth login
        Log in to an authentication service to obtain a JWT Token.
      • zowe rse auth query
        Get back JWT Token information if it is not yet expired.
      • zowe rse auth logout
        Log out of the authentication service and retire the JWT Token.
      At this time, username and password are still required during creation of the profile using command line operations, but the order of precedence kicks in if a JWT token is present in the profile. The RSE CLI plug-in will first check for a token. If the token is not present, then it will then check for username and password to authenticate with the host.
       Trying out the latest release
      ',24),g=e("To get your hands on the latest release and try out the new features, head over to "),b=e("Setting up integrations to interact with z/OS"),S=e(" and see the documentation on how to get started. There, you can get the link to the download sites for IBM RSE API Plug-in for Zowe CLI and its host components."),T=e("There are some known issues for these new commands and they are documented in our "),y=e("Known issues"),I=e(" page.");function _(k,v){const t=n("RouterLink");return i(),r(h,null,[w,o("p",null,[g,a(t,{to:"/Docs/setup_integration.html"},{default:s(()=>[b]),_:1}),S]),o("p",null,[T,a(t,{to:"/Docs/knownissues.html#ibm-rse-api-plug-in-for-zowe-cli"},{default:s(()=>[y]),_:1}),I])],64)}var A=l(f,[["render",_]]);export{A as default};
diff --git a/assets/rse_cli_command.html.1e4311e9.js b/assets/rse_cli_command.html.1e4311e9.js
deleted file mode 100644
index aa6302464..000000000
--- a/assets/rse_cli_command.html.1e4311e9.js
+++ /dev/null
@@ -1 +0,0 @@
-import{r as c,o as a,a as s,b as e,d as l,F as i,c as o,e as t}from"./app.f6cb3ed9.js";import{_ as r}from"./plugin-vue_export-helper.21dcd24c.js";const n={},u=o('
       IBM RSE API Plug-in for Zowe CLI commands
      Refer to the following tables for commands that are available in the IBM\xAE RSE API Plug-in for Zowe\u2122 CLI (RSE CLI plug-in) and their equivalent Zowe CLI z/OSMF commands.
       z/OS UNIX System Services
      RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version available
      zowe rse ls uss "/u/user"zowe files ls uss "/u/user"List z/OS UNIX System Services files using a path to search.v1.0.0
      zowe rse create file "/u/user/newFile"zowe files create file "/u/user/newFile"--modeCreate a z/OS UNIX System Services file. --mode states the permissions of the file. If permissions are not entered, the default will be rwxrw-r--.v1.0.0
      zowe rse create dir "/u/user/newDirectory"zowe files create dir "/u/user/newDirectory"--modeCreate a z/OS UNIX System Services directory. --mode states the permissions of the directory. If permissions are not entered, the default will be rwxrw-r--.v1.0.0
      zowe rse del uss "/u/user/fileName"zowe files del uss "/u/user/fileName"Delete z/OS UNIX System Services files.v1.0.0
      zowe rse del uss "/u/user/directoryName"zowe files del uss "/u/user/directoryName"Delete z/OS UNIX System Services directories or folders.v1.0.0
      zowe rse dl uf "/path/to/fileName"zowe files dl uf "/path/to/fileName"-f, -b, --ecDownload a file from the host to local. To download files to a specific location on local, specify the option -f followed by a path and file name of location on local. Specify -b for binary download. The --ec command is to specify an encoding.v1.0.0
      zowe rse ul ftu "localFile.txt" "/u/user/fileName"zowe files ul ftu "localFile.txt" "/u/user/fileName"-b, --ecUpload a local file to z/OS UNIX System Services. Specify -b for binary download. The --ec command is to specify an encoding on the host.v1.0.0
      zowe rse ul dtu "/path/to/localDir" "/path/to/dirName"zowe files ul dtu "/path/to/localDir" "/path/to/dirName"-r, -b, --ecUpload a directory to z/OS UNIX System Services. To upload the directory recursively, specify the option -r. Specify -b for binary download. The --ec command is to specify an encoding on the host.v1.0.0
      zowe rse rename uss "/u/user/fileName" "newFileName"Rename a z/OS UNIX System Services file or directory.v1.0.0
      zowe rse change properties "/u/user/fileName"--owner, --group, --permissionChange properties of a z/OS UNIX System Services file or directory.v1.1.3
      zowe rse search uss "/u/user/fileName" "fileName"N/A--text, --regex-file-name, --regex-content, --case-sensitive-file-name, --case-sensitive-content, --path-results-onlySearch for UNIX files by specifying the path, file name, and text pattern.v1.1.4
      zowe rse change clear-tag "/u/user/fileName.txt"N/AClear the tag of the UNIX file specified.v1.0.1
       MVS
      RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version available
      zowe rse ls ds filterzowe files ls ds filter-aList data sets by using a filter to search, for example, name, name.*. To list the data set's attributes, specify the option -a.v1.0.0
      zowe rse ls am "hlq.dsname"zowe files ls am "hlq.dsname"--patternList all members of a PDS by using the data set name to search. The --pattern tag can be used for a member filter search on the data set.--pattern available with v1.0.1
      zowe rse create ds "hlq.dsname" --like "hlq.originaldszowe files create ds "hlq.dsname" --like "hlq.originalds--bs, --db, --dt, --rf, --rl, --ss, --vs, --au, --ab, --psAllocate a data set like another data set. Options include: block size (bs), device type (dt), directory blocks (db), record format (rf), record length (rl), secondary space (ss), allocation unit (au), average block (ab), primary (ps), and volume serial (vs). If no options are specified to overwritten, all attributes from the like data set will be used.v1.0.7
      zowe rse create ps "hlq.dsname"zowe files create ps "hlq.dsname"--bs, --db, --dt, --rf, --rl, --ss, --vs, --au, --ab, --psCreate a sequential data set (PS). Options include: block size (bs), device type (dt), directory blocks (db), record format (rf), record length (rl), secondary space (ss), allocation unit (au), average block (ab), primary (ps), and volume serial (vs). If no options are specified, a default option will be used.v1.0.0
      zowe rse create pds "hlq.dsname"zowe files create pds "hlq.dsname"--bs, --db, --dt, --rf, --rl, --ss, --vs, --au, --ab, --psCreate a partitioned data set (PO). Options include: block size (bs), device type (dt), directory blocks (db), record format (rf), record length (rl), secondary space (ss), allocation unit (au), average block (ab), primary (ps), and volume serial (vs). If no options are specified, a default option will be used.v1.0.0
      zowe rse create member "hlq.dsname(newmember)"Create a member for a partitioned data set.v1.0.0
      zowe rse del ds "hlq.dsname"zowe files del ds "hlq.dsname"Delete sequential (PS) and partitioned (PO) data sets or members.v1.0.0
      zowe rse dl ds "hlq.dsname(member)"zowe files dl ds "hlq.dsname(member)"-f, -b, --ec, -e, --mappings-fileDownload a PS data set or a single member of a PO data set from the host to local. Specify -f to indicate the path on local to download to. Specify -e to indicate the extension of the file downloaded on local; if the extension is not indicated, the file will be saved as a text file. Specify -b for binary download. The --ec command is to specify an encoding. The --mappings-file tag will specify location of a non-default mappings file.-b available with v1.0.3
      zowe rse dl am "hlq.dsname"zowe files dl am "hlq.dsname"-d, -b, --ec, -e, --mappings-fileDownload all members of a PO data set from the host to local. Specify -d to indicate the directory on local to download to. Specify -e to indicate the extension of the file downloaded on local; if the extension is not indicated, the file will be saved as a text file. Specify -b for binary download. The --ec command is to specify an encoding. The --mappings-file tag will specify location of a non-default mappings file.-b available with v1.0.3
      zowe rse ul ftds "localFile.txt" "hlq.dsname"zowe files ul ftds "localFile.txt" "hlq.dsname"--ec, -b, --mappings-fileUpload a local file to the host as a data set. The --ec command is to specify an encoding on the host. Specify -b for binary upload. The --mappings-file tag will specify location of a non-default mappings file.v1.0.0
      zowe rse ul dtp "localDirectory" "hlq.dsname"zowe files ul dtp "localDirectory" "hlq.dsname"--ec, -b, --mappings-fileUpload a directory to a PDS. The --ec command is to specify an encoding on the host. Specify -b for binary upload. The --mappings-file tag will specify location of a non-default mappings file.v1.0.0
      zowe rse rename data-set "hlq.dsname" "hlq.newdsname"Rename a data set.v1.0.0
      zowe rse rename data-set-member "hlq.dsname(memberName)" "newMemberName"Rename a data set member.v1.0.0
      zowe rse migrate data-set "hlq.dsname"zowe files migrate data-set "hlq.dsname"Migrate data sets.v1.0.0
      zowe rse recall data-set "hlq.dsname"zowe files recall data-set "hlq.dsname"Recall migrated data sets.v1.0.0
      zowe rse copy data-set fromDataSetName toDataSetNamezowe files copy data-set fromDataSetName toDataSetNameCopy a data set or data set member to another data set.v1.0.3
       JES
      RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version available
      zowe rse ls jszowe jobs ls js-o, -p, -s, -aList jobs on JES spool or queues. The option -o indicates the owner of the jobs. The option -p indicates the job's name prefix. The option -s indicates the status of the listed jobs (ALL, ACTIVE, OUTPUT, or INPUT). The option -a shows the additional job attributes of the listed jobs.v1.0.0
      zowe rse ls sfbj "jobId"zowe jobs ls sfbj "jobId"List the spool files (DDs) for a z/OS\xAE job on the JES or spool queues for a z/OS job ID.v1.0.0
      zowe rse delete job "jobId"zowe jobs delete job "jobId"Delete a single job by job ID.v1.0.0
      zowe rse dl o "jobId"zowe jobs dl o "jobId"-d, -e, --ojdDownload job output by job ID. Use the option -d to specify a local directory for the download. Use the option -e to specify a files extension to save the job output with. Use the option --ojd to save the output directly to the specified directory without creating a subdirectory named after the ID of the job.v1.0.0
      zowe rse submit data-set "hlq.datasetName(jclMember)zowe jobs submit data-set "hlq.datasetName(jclMember)--wfo , --wfa , --vasc , -d , -e, --jsSubmit a JCL job contained in a data set. The data set can be physical sequential or a PDS member.--js available with v1.0.9
      zowe rse submit local-file "path/to/local/file"zowe jobs submit local-file "path/to/local/file"--wfo , --wfa , --vasc , -d , -e, --jsSubmit a JCL job contained in a local file.--js available with v1.0.9
      zowe rse submit stdinzowe jobs submit stdin--wfo , --wfa , --vasc , -d , -e, --jsSubmit a JCL job passed to the command via the stdin stream.--js available with v1.0.9
      zowe rse view job-status-by-jobid JOB00123zowe jobs view job-status-by-jobid JOB00123-aView status details of a single z/OS job on spool or JES queues. The option -a shows the additional job attributes of the job.v1.0.0
      zowe rse view spool-file-by-id JOB00123 4zowe jobs view spool-file-by-id JOB00123 4View the contents of a spool file from a z/OS job on spool or JES queues.v1.0.0
      zowe rse cancel job JOB03456zowe jobs cancel job JOB03456Cancel a single job by job ID.v1.0.0
       System
      ',9),h=e("thead",null,[e("tr",null,[e("th",null,"RSE CLI plug-in command"),e("th",null,"Zowe CLI z/OSMF command"),e("th",null,"Options"),e("th",null,"Description"),e("th",null,"RSE API version available"),e("th",null,"z/OS Explorer version available")])],-1),p=e("tr",null,[e("td",null,[e("code",null,"zowe rse check status")]),e("td",null,[e("code",null,"zowe zosmf check status")]),e("td"),e("td",null,"Get system and API information."),e("td",null,"v1.0.1"),e("td",null,"v3.1.1.26")],-1),m=e("tr",null,[e("td",null,[e("code",null,"zowe rse auth login")]),e("td",null,[e("code",null,"zowe auth login")]),e("td"),e("td",null,"Log in to an authentication service to obtain a JSON Web Token."),e("td",null,"v1.0.0"),e("td",null,"v3.1.1.26")],-1),f=e("tr",null,[e("td",null,[e("code",null,"zowe rse auth query")]),e("td"),e("td"),e("td",null,"Get back JSON Web Token information if it is not yet expired."),e("td",null,"v1.0.0"),e("td",null,"v3.1.1.26")],-1),b=e("tr",null,[e("td",null,[e("code",null,"zowe rse auth logout")]),e("td",null,[e("code",null,"zowe auth logout")]),e("td"),e("td",null,"Log out of the authentication service and retire the JSON Web Token."),e("td",null,"v1.0.3"),e("td",null,"v3.1.1.26")],-1),q=e("td",null,[e("code",null,'zowe rse issue command ""')],-1),w=e("td",null,[e("code",null,'zowe tso issue command ""')],-1),v=e("td",null,[e("code",null,"--shell-id")],-1),y=t("Issue a TSO command. The "),z=e("code",null,"--shell-id",-1),S=t(" tag allows interactive TSO commands using an "),g={href:"https://www.ibm.com/docs/en/adfz/explorer-for-zos/3.2?topic=tasks-optional-interactive-ispf-gateway",target:"_blank",rel:"noopener noreferrer"},I=t("Interactive ISPF Gateway"),j=t("."),_=e("td",null,[t("v1.0.1, "),e("code",null,"--shell-id"),t(" available v1.0.8")],-1),N=e("td",null,"v3.1.1.26",-1),O=e("tr",null,[e("td",null,[e("code",null,'zowe rse issue unix "" --cwd "/uss/path/toIssue"')]),e("td"),e("td"),e("td",null,"Issue a UNIX command."),e("td",null,"v1.0.0"),e("td",null,"v3.1.1.26")],-1),x=e("tr",null,[e("td",null,[e("code",null,'zowe rse issue unix-shell "" --cwd "/uss/path/toIssue"')]),e("td"),e("td",null,"--env"),e("td",null,"Issue a UNIX command with streaming output. Use the option --env to specify a comma-separated list of environment variables for the executing shell."),e("td",null,"v1.0.5"),e("td",null,"v3.2.0.16")],-1),C=e("tr",null,[e("td",null,[e("code",null,"zowe rse check conversion-mappings")]),e("td"),e("td"),e("td",null,"Download Mappings file from RSE API server."),e("td",null,"v1.0.3"),e("td",null,"v3.1.1.26")],-1),D=e("tr",null,[e("td",null,[e("code",null,"zowe rse change password currentPassword newPassword")]),e("td"),e("td"),e("td",null,"Change z/OS User Password on the Host and update profile's yaml if saved locally."),e("td",null,"v1.0.2"),e("td",null,"v3.1.1.26")],-1),P=e("tr",null,[e("td",null,[e("code",null,"zowe rse check system-address-space")]),e("td"),e("td"),e("td",null,"Display active system address space information."),e("td",null,"v1.0.5"),e("td",null,"v3.2.0.16")],-1),k=e("tr",null,[e("td",null,[e("code",null,"zowe rse check job-address-space")]),e("td"),e("td",null,[e("code",null,"--asid"),t(", "),e("code",null,"--asidx"),t(", "),e("code",null,"--bytes"),t(", "),e("code",null,"--cpu"),t(", "),e("code",null,"--cpu%"),t(", "),e("code",null,"--description"),t(", "),e("code",null,"--dp"),t(", "),e("code",null,"--elapsed"),t(", "),e("code",null,"--frames"),t(", "),e("code",null,"--hvcomhwm"),t(", "),e("code",null,"--hvcomused"),t(", "),e("code",null,"--io"),t(", "),e("code",null,"--name"),t(", "),e("code",null,"--page"),t(", "),e("code",null,"--position"),t(", "),e("code",null,"--stepio"),t(", "),e("code",null,"--subtype"),t(", "),e("code",null,"--swapin"),t(", "),e("code",null,"--sysName"),t(", "),e("code",null,"--task"),t(", "),e("code",null,"--task%"),t(", "),e("code",null,"--type"),t(", "),e("code",null,"--userId")]),e("td",null,"Display all active job address space information. Option tags are used to filter the returned list of data."),e("td",null,"v1.0.5, filter options: v1.0.9"),e("td",null,"v3.2.0.16")],-1),U=e("tr",null,[e("td",null,[e("code",null,"zowe rse check password-expiry")]),e("td"),e("td"),e("td",null,"Displays expiration date of user id's password."),e("td",null,"v1.1.2"),e("td",null,"v3.1.1.26")],-1),T=o('
       RSE Common Properties
      RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version available
      zowe rse cm copy "global-ns" "backup-ns"--privateCopy a Common Properties namespace. Use the option --private to specify for private namespace.v1.1.3
      zowe rse cm create "global-ns"--privateCreate a Common Properties namespace. Use the option --private to specify for private namespace.v1.1.3
      zowe rse cm delete "global-ns" --path "/path/to/property"--path, --privateDelete a Common Properties namespace, or delete a property in the namespace indicated by the --path option. Use the option --private to specify for private namespace.v1.1.3
      zowe rse cm list--privateList all Common Properties namespaces. Use the option --private to specify for private namespace.v1.1.3
      zowe rse cm rename "global-ns" "backup-ns"--privateRename a Common Properties namespace. Use the option --private to specify for private namespace.v1.1.3
      zowe rse cm set "global-ns" "/path/to/property" "some-value"--private, --value-typeSet a property in the namespace. If the value is not a simple string but a number, boolean or JSON string, use --value-type to specify the type. Use the option --private to specify for private namespace.v1.1.3
      zowe rse cm view "global-ns" --path "/path/to/property"--path, --privateView all properties in a Common Properties namespace, or a property in the namespace specified by the --path option. Use the option --private to specify for private namespace.v1.1.3
      ',2);function L(E,M){const d=c("ExternalLinkIcon");return a(),s(i,null,[u,e("table",null,[h,e("tbody",null,[p,m,f,b,e("tr",null,[q,w,v,e("td",null,[y,z,S,e("a",g,[I,l(d)]),j]),_,N]),O,x,C,D,P,k,U])]),T],64)}var J=r(n,[["render",L]]);export{J as default};
diff --git a/assets/rse_cli_command.html.45be7e34.js b/assets/rse_cli_command.html.45be7e34.js
new file mode 100644
index 000000000..9e67f18f5
--- /dev/null
+++ b/assets/rse_cli_command.html.45be7e34.js
@@ -0,0 +1 @@
+const m={key:"v-4aeeafba",path:"/Docs/rse_cli_command.html",title:"IBM RSE API Plug-in for Zowe CLI commands",lang:"en-US",frontmatter:{},excerpt:"",headers:[{level:1,title:"IBM RSE API Plug-in for Zowe CLI commands",slug:"ibm-rse-api-plug-in-for-zowe-cli-commands",children:[{level:2,title:"z/OS UNIX System Services",slug:"z-os-unix-system-services",children:[]},{level:2,title:"MVS",slug:"mvs",children:[]},{level:2,title:"JES",slug:"jes",children:[]},{level:2,title:"System",slug:"system",children:[]},{level:2,title:"RSE Common Properties",slug:"rse-common-properties",children:[]}]}],git:{updatedTime:1726615592e3,contributors:[{name:"Billie Simmons",email:"billiejean.simmons@ibm.com",commits:19},{name:"Billie Simmons",email:"BillieJean.Simmons@ibm.com",commits:6},{name:"Nimma Likhitha",email:"Likhitha.Nimma@ibm.com",commits:4},{name:"Billie Jean Simmons",email:"billiejean.simmons@ibm.com",commits:3},{name:"Rudy Leonel Pichola Flores",email:"rudyflores@ibm.com",commits:3},{name:"Lauren Li",email:"Lauren.Li@ibm.com",commits:2},{name:"Min Huang",email:"minhsh@cn.ibm.com",commits:2},{name:"Patrick Tiu",email:"tiu@ca.ibm.com",commits:2},{name:"Alvin So",email:"alvinso@ca.ibm.com",commits:1},{name:"Benjamin Santos",email:"Benjamin.Santos@ibm.com",commits:1},{name:"Billie",email:"BillieJean.Simmons@ibm.com",commits:1},{name:"Chun Hong Zheng",email:"chunhzh@cn.ibm.com",commits:1},{name:"Hestia Zhang",email:"Hestia.Zhang@ibm.com",commits:1},{name:"Rudy Pichola Flores",email:"rudyflores@ibm.com",commits:1},{name:"Shi Kun Li",email:"shikunli@cn.ibm.com",commits:1},{name:"shikunli",email:"shikunli@cn.ibm.com",commits:1}]},filePathRelative:"Docs/rse_cli_command.md"};export{m as data};
diff --git a/assets/rse_cli_command.html.cbf3613e.js b/assets/rse_cli_command.html.cbf3613e.js
deleted file mode 100644
index 7c32d95ad..000000000
--- a/assets/rse_cli_command.html.cbf3613e.js
+++ /dev/null
@@ -1 +0,0 @@
-const m={key:"v-4aeeafba",path:"/Docs/rse_cli_command.html",title:"IBM RSE API Plug-in for Zowe CLI commands",lang:"en-US",frontmatter:{},excerpt:"",headers:[{level:1,title:"IBM RSE API Plug-in for Zowe CLI commands",slug:"ibm-rse-api-plug-in-for-zowe-cli-commands",children:[{level:2,title:"z/OS UNIX System Services",slug:"z-os-unix-system-services",children:[]},{level:2,title:"MVS",slug:"mvs",children:[]},{level:2,title:"JES",slug:"jes",children:[]},{level:2,title:"System",slug:"system",children:[]},{level:2,title:"RSE Common Properties",slug:"rse-common-properties",children:[]}]}],git:{updatedTime:1722517702e3,contributors:[{name:"Billie Simmons",email:"billiejean.simmons@ibm.com",commits:19},{name:"Billie Simmons",email:"BillieJean.Simmons@ibm.com",commits:6},{name:"Billie Jean Simmons",email:"billiejean.simmons@ibm.com",commits:3},{name:"Rudy Leonel Pichola Flores",email:"rudyflores@ibm.com",commits:3},{name:"Lauren Li",email:"Lauren.Li@ibm.com",commits:2},{name:"Min Huang",email:"minhsh@cn.ibm.com",commits:2},{name:"Patrick Tiu",email:"tiu@ca.ibm.com",commits:2},{name:"Alvin So",email:"alvinso@ca.ibm.com",commits:1},{name:"Billie",email:"BillieJean.Simmons@ibm.com",commits:1},{name:"Chun Hong Zheng",email:"chunhzh@cn.ibm.com",commits:1},{name:"Hestia Zhang",email:"Hestia.Zhang@ibm.com",commits:1},{name:"Nimma Likhitha",email:"Likhitha.Nimma@ibm.com",commits:1},{name:"Rudy Pichola Flores",email:"rudyflores@ibm.com",commits:1},{name:"Shi Kun Li",email:"shikunli@cn.ibm.com",commits:1},{name:"shikunli",email:"shikunli@cn.ibm.com",commits:1}]},filePathRelative:"Docs/rse_cli_command.md"};export{m as data};
diff --git a/assets/rse_cli_command.html.da0a133a.js b/assets/rse_cli_command.html.da0a133a.js
new file mode 100644
index 000000000..d236e1bad
--- /dev/null
+++ b/assets/rse_cli_command.html.da0a133a.js
@@ -0,0 +1 @@
+import{r as c,o as a,a as s,b as e,d as l,F as r,c as o,e as t}from"./app.daa93c96.js";import{_ as i}from"./plugin-vue_export-helper.21dcd24c.js";const n={},u=o('
       IBM RSE API Plug-in for Zowe CLI commands
      Refer to the following tables for commands that are available in the IBM\xAE RSE API Plug-in for Zowe\u2122 CLI (RSE CLI plug-in) and their equivalent Zowe CLI z/OSMF commands.
       z/OS UNIX System Services
      RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version available
      zowe rse ls uss "/u/user"zowe files ls uss "/u/user"List z/OS UNIX System Services files using a path to search.v1.0.0
      zowe rse create file "/u/user/newFile"zowe files create file "/u/user/newFile"--modeCreate a z/OS UNIX System Services file. --mode states the permissions of the file. If permissions are not entered, the default will be rwxrw-r--.v1.0.0
      zowe rse create dir "/u/user/newDirectory"zowe files create dir "/u/user/newDirectory"--modeCreate a z/OS UNIX System Services directory. --mode states the permissions of the directory. If permissions are not entered, the default will be rwxrw-r--.v1.0.0
      zowe rse del uss "/u/user/fileName"zowe files del uss "/u/user/fileName"Delete z/OS UNIX System Services files.v1.0.0
      zowe rse del uss "/u/user/directoryName"zowe files del uss "/u/user/directoryName"Delete z/OS UNIX System Services directories or folders.v1.0.0
      zowe rse dl uf "/path/to/fileName"zowe files dl uf "/path/to/fileName"-f, -b, --ec,--lcDownload a file from the host to local. To download files to a specific location on local, specify the option -f followed by a path and file name of location on local. Specify -b for binary download. The --ec command is to specify an encoding. The --lc command is to specify local encoding.v1.0.0
      zowe rse ul ftu "localFile.txt" "/u/user/fileName"zowe files ul ftu "localFile.txt" "/u/user/fileName"-b, --ec,--lcUpload a local file to z/OS UNIX System Services. Specify -b for binary download. The --ec command is to specify an encoding on the host. The --lc command is to specify local encoding.v1.0.0
      zowe rse ul dtu "/path/to/localDir" "/path/to/dirName"zowe files ul dtu "/path/to/localDir" "/path/to/dirName"-r, -b, --ec, --lcUpload a directory to z/OS UNIX System Services. To upload the directory recursively, specify the option -r. Specify -b for binary download. The --ec command is to specify an encoding on the host. The --lc command is to specify local encoding.v1.0.0
      zowe rse rename uss "/u/user/fileName" "newFileName"Rename a z/OS UNIX System Services file or directory.v1.0.0
      zowe rse change properties "/u/user/fileName"--owner, --group, --permissionChange properties of a z/OS UNIX System Services file or directory.v1.1.3
      zowe rse search uss "/u/user/fileName" "fileName"N/A--text, --regex-file-name, --regex-content, --case-sensitive-file-name, --case-sensitive-content, --path-results-onlySearch for UNIX files by specifying the path, file name, and text pattern.v1.1.4
      zowe rse change clear-tag "/u/user/fileName.txt"N/AClear the tag of the UNIX file specified.v1.1.4
      zowe rse convert unix-file-encoding "/u/user/fileName.txt" 'hostEncoding' 'targetEncoding'N/AConverts the encoding of the specified Unix file to target encoding.v1.0.1
       MVS
      RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version available
      zowe rse ls ds filterzowe files ls ds filter-aList data sets by using a filter to search, for example, name, name.*. To list the data set's attributes, specify the option -a.v1.0.0
      zowe rse ls am "hlq.dsname"zowe files ls am "hlq.dsname"--patternList all members of a PDS by using the data set name to search. The --pattern tag can be used for a member filter search on the data set.--pattern available with v1.0.1
      zowe rse create ds "hlq.dsname" --like "hlq.originaldszowe files create ds "hlq.dsname" --like "hlq.originalds--bs, --db, --dt, --rf, --rl, --ss, --vs, --au, --ab, --psAllocate a data set like another data set. Options include: block size (bs), device type (dt), directory blocks (db), record format (rf), record length (rl), secondary space (ss), allocation unit (au), average block (ab), primary (ps), and volume serial (vs). If no options are specified to overwritten, all attributes from the like data set will be used.v1.0.7
      zowe rse create ps "hlq.dsname"zowe files create ps "hlq.dsname"--bs, --db, --dt, --rf, --rl, --ss, --vs, --au, --ab, --psCreate a sequential data set (PS). Options include: block size (bs), device type (dt), directory blocks (db), record format (rf), record length (rl), secondary space (ss), allocation unit (au), average block (ab), primary (ps), and volume serial (vs). If no options are specified, a default option will be used.v1.0.0
      zowe rse create pds "hlq.dsname"zowe files create pds "hlq.dsname"--bs, --db, --dt, --rf, --rl, --ss, --vs, --au, --ab, --psCreate a partitioned data set (PO). Options include: block size (bs), device type (dt), directory blocks (db), record format (rf), record length (rl), secondary space (ss), allocation unit (au), average block (ab), primary (ps), and volume serial (vs). If no options are specified, a default option will be used.v1.0.0
      zowe rse create member "hlq.dsname(newmember)"Create a member for a partitioned data set.v1.0.0
      zowe rse del ds "hlq.dsname"zowe files del ds "hlq.dsname"Delete sequential (PS) and partitioned (PO) data sets or members.v1.0.0
      zowe rse dl ds "hlq.dsname(member)"zowe files dl ds "hlq.dsname(member)"-f, -b, --ec, -e, --mappings-file,--lcDownload a PS data set or a single member of a PO data set from the host to local. Specify -f to indicate the path on local to download to. Specify -e to indicate the extension of the file downloaded on local; if the extension is not indicated, the file will be saved as a text file. Specify -b for binary download. The --ec command is to specify an encoding. The --lc command is to specify local encoding. The --mappings-file tag will specify location of a non-default mappings file.-b available with v1.0.3
      zowe rse dl am "hlq.dsname"zowe files dl am "hlq.dsname"-d, -b, --ec, -e, --mappings-file, --lcDownload all members of a PO data set from the host to local. Specify -d to indicate the directory on local to download to. Specify -e to indicate the extension of the file downloaded on local; if the extension is not indicated, the file will be saved as a text file. Specify -b for binary download. The --ec command is to specify an encoding. The --mappings-file tag will specify location of a non-default mappings file. The --lc command is to specify local encoding.-b available with v1.0.3
      zowe rse ul ftds "localFile.txt" "hlq.dsname"zowe files ul ftds "localFile.txt" "hlq.dsname"--ec, -b, --mappings-file,--lcUpload a local file to the host as a data set. The --ec command is to specify an encoding on the host. Specify -b for binary upload. The --mappings-file tag will specify location of a non-default mappings file. The --lc command is to specify local encoding.v1.0.0
      zowe rse ul dtp "localDirectory" "hlq.dsname"zowe files ul dtp "localDirectory" "hlq.dsname"--ec, -b, --mappings-file, --lcUpload a directory to a PDS. The --ec command is to specify an encoding on the host. Specify -b for binary upload. The --mappings-file tag will specify location of a non-default mappings file. The --lc command is to specify local encoding.v1.0.0
      zowe rse rename data-set "hlq.dsname" "hlq.newdsname"Rename a data set.v1.0.0
      zowe rse rename data-set-member "hlq.dsname(memberName)" "newMemberName"Rename a data set member.v1.0.0
      zowe rse migrate data-set "hlq.dsname"zowe files migrate data-set "hlq.dsname"Migrate data sets.v1.0.0
      zowe rse recall data-set "hlq.dsname"zowe files recall data-set "hlq.dsname"Recall migrated data sets.v1.0.0
      zowe rse copy data-set fromDataSetName toDataSetNamezowe files copy data-set fromDataSetName toDataSetNameCopy a data set or data set member to another data set.v1.0.3
      zowe rse copy data-set-cross-lpar fromDataSetName toDataSetNamezowe files copy data-set-cross-lpar fromDataSetName toDataSetName--target-host, --target-port, --target-user, --target-password, --target-rse-p, --replaceCopy a data set or data set member to another data set on the same or different LPAR. Specify --target-host, --target-port, --target-user, --target-password for the target LPAR. Specify --target-rse-p for the target rse profile. Specify --replace in order to replace the existing targetDataset.v1.0.3
       JES
      RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version available
      zowe rse ls jszowe jobs ls js-o, -p, -s, -aList jobs on JES spool or queues. The option -o indicates the owner of the jobs. The option -p indicates the job's name prefix. The option -s indicates the status of the listed jobs (ALL, ACTIVE, OUTPUT, or INPUT). The option -a shows the additional job attributes of the listed jobs.v1.0.0
      zowe rse ls sfbj "jobId"zowe jobs ls sfbj "jobId"List the spool files (DDs) for a z/OS\xAE job on the JES or spool queues for a z/OS job ID.v1.0.0
      zowe rse delete job "jobId"zowe jobs delete job "jobId"Delete a single job by job ID.v1.0.0
      zowe rse dl o "jobId"zowe jobs dl o "jobId"-d, -e, --ojdDownload job output by job ID. Use the option -d to specify a local directory for the download. Use the option -e to specify a files extension to save the job output with. Use the option --ojd to save the output directly to the specified directory without creating a subdirectory named after the ID of the job.v1.0.0
      zowe rse submit data-set "hlq.datasetName(jclMember)zowe jobs submit data-set "hlq.datasetName(jclMember)--wfo , --wfa , --vasc , -d , -e, --jsSubmit a JCL job contained in a data set. The data set can be physical sequential or a PDS member.--js available with v1.0.9
      zowe rse submit local-file "path/to/local/file"zowe jobs submit local-file "path/to/local/file"--wfo , --wfa , --vasc , -d , -e, --jsSubmit a JCL job contained in a local file.--js available with v1.0.9
      zowe rse submit stdinzowe jobs submit stdin--wfo , --wfa , --vasc , -d , -e, --jsSubmit a JCL job passed to the command via the stdin stream.--js available with v1.0.9
      zowe rse view job-status-by-jobid JOB00123zowe jobs view job-status-by-jobid JOB00123-aView status details of a single z/OS job on spool or JES queues. The option -a shows the additional job attributes of the job.v1.0.0
      zowe rse view spool-file-by-id JOB00123 4zowe jobs view spool-file-by-id JOB00123 4View the contents of a spool file from a z/OS job on spool or JES queues.v1.0.0
      zowe rse cancel job JOB03456zowe jobs cancel job JOB03456Cancel a single job by job ID.v1.0.0
       System
      ',9),p=e("thead",null,[e("tr",null,[e("th",null,"RSE CLI plug-in command"),e("th",null,"Zowe CLI z/OSMF command"),e("th",null,"Options"),e("th",null,"Description"),e("th",null,"RSE API version available"),e("th",null,"z/OS Explorer version available")])],-1),h=e("tr",null,[e("td",null,[e("code",null,"zowe rse check status")]),e("td",null,[e("code",null,"zowe zosmf check status")]),e("td"),e("td",null,"Get system and API information."),e("td",null,"v1.0.1"),e("td",null,"v3.1.1.26")],-1),m=e("tr",null,[e("td",null,[e("code",null,"zowe rse auth login")]),e("td",null,[e("code",null,"zowe auth login")]),e("td"),e("td",null,"Log in to an authentication service to obtain a JSON Web Token."),e("td",null,"v1.0.0"),e("td",null,"v3.1.1.26")],-1),f=e("tr",null,[e("td",null,[e("code",null,"zowe rse auth query")]),e("td"),e("td"),e("td",null,"Get back JSON Web Token information if it is not yet expired."),e("td",null,"v1.0.0"),e("td",null,"v3.1.1.26")],-1),b=e("tr",null,[e("td",null,[e("code",null,"zowe rse auth logout")]),e("td",null,[e("code",null,"zowe auth logout")]),e("td"),e("td",null,"Log out of the authentication service and retire the JSON Web Token."),e("td",null,"v1.0.3"),e("td",null,"v3.1.1.26")],-1),q=e("td",null,[e("code",null,'zowe rse issue command ""')],-1),w=e("td",null,[e("code",null,'zowe tso issue command ""')],-1),v=e("td",null,[e("code",null,"--shell-id")],-1),y=t("Issue a TSO command. The "),z=e("code",null,"--shell-id",-1),g=t(" tag allows interactive TSO commands using an "),S={href:"https://www.ibm.com/docs/en/adfz/explorer-for-zos/3.2?topic=tasks-optional-interactive-ispf-gateway",target:"_blank",rel:"noopener noreferrer"},I=t("Interactive ISPF Gateway"),j=t("."),_=e("td",null,[t("v1.0.1, "),e("code",null,"--shell-id"),t(" available v1.0.8")],-1),N=e("td",null,"v3.1.1.26",-1),O=e("tr",null,[e("td",null,[e("code",null,'zowe rse issue unix "" --cwd "/uss/path/toIssue"')]),e("td"),e("td"),e("td",null,"Issue a UNIX command."),e("td",null,"v1.0.0"),e("td",null,"v3.1.1.26")],-1),x=e("tr",null,[e("td",null,[e("code",null,'zowe rse issue unix-shell "" --cwd "/uss/path/toIssue"')]),e("td"),e("td",null,"--env"),e("td",null,"Issue a UNIX command with streaming output. Use the option --env to specify a comma-separated list of environment variables for the executing shell."),e("td",null,"v1.0.5"),e("td",null,"v3.2.0.16")],-1),D=e("tr",null,[e("td",null,[e("code",null,"zowe rse check conversion-mappings")]),e("td"),e("td"),e("td",null,"Download Mappings file from RSE API server."),e("td",null,"v1.0.3"),e("td",null,"v3.1.1.26")],-1),C=e("tr",null,[e("td",null,[e("code",null,"zowe rse change password currentPassword newPassword")]),e("td"),e("td"),e("td",null,"Change z/OS User Password on the Host and update profile's yaml if saved locally."),e("td",null,"v1.0.2"),e("td",null,"v3.1.1.26")],-1),T=e("tr",null,[e("td",null,[e("code",null,"zowe rse check system-address-space")]),e("td"),e("td"),e("td",null,"Display active system address space information."),e("td",null,"v1.0.5"),e("td",null,"v3.2.0.16")],-1),P=e("tr",null,[e("td",null,[e("code",null,"zowe rse check job-address-space")]),e("td"),e("td",null,[e("code",null,"--asid"),t(", "),e("code",null,"--asidx"),t(", "),e("code",null,"--bytes"),t(", "),e("code",null,"--cpu"),t(", "),e("code",null,"--cpu%"),t(", "),e("code",null,"--description"),t(", "),e("code",null,"--dp"),t(", "),e("code",null,"--elapsed"),t(", "),e("code",null,"--frames"),t(", "),e("code",null,"--hvcomhwm"),t(", "),e("code",null,"--hvcomused"),t(", "),e("code",null,"--io"),t(", "),e("code",null,"--name"),t(", "),e("code",null,"--page"),t(", "),e("code",null,"--position"),t(", "),e("code",null,"--stepio"),t(", "),e("code",null,"--subtype"),t(", "),e("code",null,"--swapin"),t(", "),e("code",null,"--sysName"),t(", "),e("code",null,"--task"),t(", "),e("code",null,"--task%"),t(", "),e("code",null,"--type"),t(", "),e("code",null,"--userId")]),e("td",null,"Display all active job address space information. Option tags are used to filter the returned list of data."),e("td",null,"v1.0.5, filter options: v1.0.9"),e("td",null,"v3.2.0.16")],-1),U=e("tr",null,[e("td",null,[e("code",null,"zowe rse check password-expiry")]),e("td"),e("td"),e("td",null,"Displays expiration date of user id's password."),e("td",null,"v1.1.2"),e("td",null,"v3.1.1.26")],-1),k=o('
       RSE Common Properties
      RSE CLI plug-in commandZowe CLI z/OSMF commandOptionsDescriptionRSE API version available
      zowe rse cm copy "global-ns" "backup-ns"--privateCopy a Common Properties namespace. Use the option --private to specify for private namespace.v1.1.3
      zowe rse cm create "global-ns"--privateCreate a Common Properties namespace. Use the option --private to specify for private namespace.v1.1.3
      zowe rse cm delete "global-ns" --path "/path/to/property"--path, --privateDelete a Common Properties namespace, or delete a property in the namespace indicated by the --path option. Use the option --private to specify for private namespace.v1.1.3
      zowe rse cm list--privateList all Common Properties namespaces. Use the option --private to specify for private namespace.v1.1.3
      zowe rse cm rename "global-ns" "backup-ns"--privateRename a Common Properties namespace. Use the option --private to specify for private namespace.v1.1.3
      zowe rse cm set "global-ns" "/path/to/property" "some-value"--private, --value-typeSet a property in the namespace. If the value is not a simple string but a number, boolean or JSON string, use --value-type to specify the type. Use the option --private to specify for private namespace.v1.1.3
      zowe rse cm view "global-ns" --path "/path/to/property"--path, --privateView all properties in a Common Properties namespace, or a property in the namespace specified by the --path option. Use the option --private to specify for private namespace.v1.1.3
      ',2);function L(E,R){const d=c("ExternalLinkIcon");return a(),s(r,null,[u,e("table",null,[p,e("tbody",null,[h,m,f,b,e("tr",null,[q,w,v,e("td",null,[y,z,g,e("a",S,[I,l(d)]),j]),_,N]),O,x,D,C,T,P,U])]),k],64)}var J=i(n,[["render",L]]);export{J as default};
diff --git a/assets/rse_tutorial.html.8e8f3dc0.js b/assets/rse_tutorial.html.2bcfb7dd.js
similarity index 99%
rename from assets/rse_tutorial.html.8e8f3dc0.js
rename to assets/rse_tutorial.html.2bcfb7dd.js
index b8c0f9532..e60d5886f 100644
--- a/assets/rse_tutorial.html.8e8f3dc0.js
+++ b/assets/rse_tutorial.html.2bcfb7dd.js
@@ -1,4 +1,4 @@
-import{r as n,o as r,a as d,b as o,d as t,w as s,F as c,c as i,e}from"./app.f6cb3ed9.js";import{_ as p}from"./plugin-vue_export-helper.21dcd24c.js";var h="/zopeneditor-about/assets/vsc-zopeneditor-sample.ccb9b0c9.png",u="/zopeneditor-about/assets/vsc-allocate-jcl.96a95b47.png",m="/zopeneditor-about/assets/rse-zowe-explorer-view-profiles.6e22fb24.gif",g="/zopeneditor-about/assets/rse-upload-files-vsc.0fd6e0e7.gif",b="/zopeneditor-about/assets/rse-copy-ps.f4d7c98d.gif",f="/zopeneditor-about/assets/rse-download-local.48960b12.png",L="/zopeneditor-about/assets/rse-script.ad48c90f.gif";const S={},w=i('
       Managing z/OS resources with IBM RSE API Plug-in for Zowe CLI tutorial
      This tutorial demonstrates some features of IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in) and includes exercises to help you become familiar with managing z/OS resources via command-line operations and the Zowe Explorer VS Code extension.
       Learning objectives
      This tutorial does not cover all features of the RSE CLI plug-in, but demonstrates the approaches that you can apply when managing z/OS resources.
      By completing the tutorial, you learn about the following approaches to manage z/OS resources with the RSE CLI plug-in:
       Tutorial scenario
      The tutorial scenario is based on a fictitious company that has applications written in COBOL. The company does not have z/OSMF configured on z/OS. As an alternative, they have installed and configured IBM Remote System Explorer API (RSE API) on z/OS. They want to use the RSE CLI plug-in to interact with z/OS by using RSE API instead of using z/OSMF.
      In this scenario, you will:
      • Import application code to your local machine.
      • Submit JCL files to run jobs on z/OS.
      • List data sets.
      • Upload files to data sets.
      • Check job status.
      • Download output files of jobs.
       Time required
      It takes approximately 10 minutes to complete each approach. If you explore other features related to this tutorial, it can take longer to complete.
       Audience
      This tutorial is for mainframe developers who want to use the RSE API support provided by the RSE CLI plug-in as an alternative to using z/OSMF to manage z/OS resources.
       Prerequisites
      Before getting started with the tutorial, you must complete the following tasks:
      ',16),E=e("Create an RSE profile. For instructions, see "),v=e("Creating an RSE profile"),C=e(" via command line, or "),A=e("Setting up and using RSE profiles"),O=e(" to create the profile via Zowe Explorer."),_=e("Clone the "),T={href:"https://github.com/IBM/zopeneditor-sample.git",target:"_blank",rel:"noopener noreferrer"},z=e("sample repository"),y=e(" and switch to the "),x=o("code",null,"tutorial-complete",-1),P=e(" Git branch that has the final updated set of programs and support files to perform the tasks described in this tutorial by following these steps:"),R=i(`
      1. Clone the sample repository by issuing the following command in a command-line window:
        git clone git@github.com:IBM/zopeneditor-sample.git
+import{r as n,o as r,a as d,b as o,d as t,w as s,F as c,c as i,e}from"./app.daa93c96.js";import{_ as p}from"./plugin-vue_export-helper.21dcd24c.js";var h="/zopeneditor-about/assets/vsc-zopeneditor-sample.ccb9b0c9.png",u="/zopeneditor-about/assets/vsc-allocate-jcl.96a95b47.png",m="/zopeneditor-about/assets/rse-zowe-explorer-view-profiles.6e22fb24.gif",g="/zopeneditor-about/assets/rse-upload-files-vsc.0fd6e0e7.gif",b="/zopeneditor-about/assets/rse-copy-ps.f4d7c98d.gif",f="/zopeneditor-about/assets/rse-download-local.48960b12.png",L="/zopeneditor-about/assets/rse-script.ad48c90f.gif";const S={},w=i('
         Managing z/OS resources with IBM RSE API Plug-in for Zowe CLI tutorial
        This tutorial demonstrates some features of IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in) and includes exercises to help you become familiar with managing z/OS resources via command-line operations and the Zowe Explorer VS Code extension.
         Learning objectives
        This tutorial does not cover all features of the RSE CLI plug-in, but demonstrates the approaches that you can apply when managing z/OS resources.
        By completing the tutorial, you learn about the following approaches to manage z/OS resources with the RSE CLI plug-in:
         Tutorial scenario
        The tutorial scenario is based on a fictitious company that has applications written in COBOL. The company does not have z/OSMF configured on z/OS. As an alternative, they have installed and configured IBM Remote System Explorer API (RSE API) on z/OS. They want to use the RSE CLI plug-in to interact with z/OS by using RSE API instead of using z/OSMF.
        In this scenario, you will:
        • Import application code to your local machine.
        • Submit JCL files to run jobs on z/OS.
        • List data sets.
        • Upload files to data sets.
        • Check job status.
        • Download output files of jobs.
         Time required
        It takes approximately 10 minutes to complete each approach. If you explore other features related to this tutorial, it can take longer to complete.
         Audience
        This tutorial is for mainframe developers who want to use the RSE API support provided by the RSE CLI plug-in as an alternative to using z/OSMF to manage z/OS resources.
         Prerequisites
        Before getting started with the tutorial, you must complete the following tasks:
        ',16),E=e("Create an RSE profile. For instructions, see "),v=e("Creating an RSE profile"),C=e(" via command line, or "),A=e("Setting up and using RSE profiles"),O=e(" to create the profile via Zowe Explorer."),_=e("Clone the "),T={href:"https://github.com/IBM/zopeneditor-sample.git",target:"_blank",rel:"noopener noreferrer"},z=e("sample repository"),y=e(" and switch to the "),x=o("code",null,"tutorial-complete",-1),P=e(" Git branch that has the final updated set of programs and support files to perform the tasks described in this tutorial by following these steps:"),R=i(`
        1. Clone the sample repository by issuing the following command in a command-line window:
          git clone git@github.com:IBM/zopeneditor-sample.git
 
        2. cd into the zopeneditor-sample directory that was just cloned.
        3. Switch to the tutorial-complete Git branch with the command:
          git checkout tutorial-complete
 
        `,1),j=o("h2",{id:"approach-1-using-the-zowe-explorer-vs-code-extension-to-manage-z-os-resources",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#approach-1-using-the-zowe-explorer-vs-code-extension-to-manage-z-os-resources","aria-hidden":"true"},"#"),e(" Approach 1: Using the Zowe Explorer VS Code extension to manage z/OS resources")],-1),k=o("p",null,"This section describes the procedure of managing z/OS resources with the Zowe Explorer VS Code extension.",-1),I=e("To get set up with VS Code, ensure that IBM Z Open Editor VS Code extension and Zowe Explorer VS Code extension are installed. For more information, see "),M=e("Using RSE support in Zowe Explorer VS Code extension"),U=e("."),q=i('
        1. Open VS Code, select File > Open Folder (Windows) or File > Open... (Mac) from the top menu bar, and select the folder zopeneditor-sample that was cloned.
          zopeneditor-sample in VS Code
          In the lower left corner, make sure the Git branch that is selected is the tutorial-complete branch. If it is not on that branch, click the Git branch that is shown and select tutorial-complete or origin/tutorial-complete branch from the list of available branches.
        2. Open the JCL folder within VS Code and click ALLOCATE.jcl to edit the ALLOCATE.jcl file on line 16 and set the HLQ.
          ALLOCATE.jcl
        3. Click Terminal from the top VS Code menu bar, and then select New Terminal to open the terminal.
        4. Submit the local ALLOCATE.jcl file by entering this command in the terminal:
          zowe rse submit local-file "./JCL/ALLOCATE.jcl"
 
        5. After the job is submitted, click the Zowe icon on the left side of VS Code. In the DATA SETS view, click the + symbol to add the RSE profile to the view. Repeat this with the JOBS view.
          Once the RSE profile shows up in the view window, click the magnifying glass next to the RSE profile name and enter HLQ.SAMPLE* in the search bar. You need to replace HLQ with the modification to it as you did in ALLOCATE.jcl. The data sets created by ALLOCATE.jcl should be listed in the Data Sets View.
        6. You can check the job from the JCL that was submitted by clicking the magnifying glass next to the RSE profile in the JOBS view and entering the HLQ that was added to ALLOCATE.jcl into the search bar as the filter. You can view the spool files by opening the Job name ZDEALLC and clicking the spool file to open it in the Editor.
          Adding RSE profiles to Zowe Explorer and viewing Data Sets and Jobs
        7. Upload the COBOL and copybook files into the created data sets, HLQ.SAMPLE.COBOL, HLQ.SAMPLE.COBCOPY, and HLQ.SAMPLE.COPYLIB, after you replace HLQ with the value entered in ALLOCATE.jcl. Right-click the data set and select the member to upload. In the zopeneditor-sample directory that was cloned, choose the files in the COBOL directory for the HLQ.SAMPLE.COBOL data set and the files in the COPYBOOK directory for the HLQ.SAMPLE.COBCOPY data set.
          Upload Cobol and Copybook files into Data Sets Using VS Code
        8. Copy and paste the following files in the RESOURCES directory of zopeneditor-sample into the appropriate sequential data set with in the Zowe Explorer Data Sets View, replacing HLQ with the value entered in ALLOCATE.jcl. Save the files in Zowe Explorer Data Sets View so they can be uploaded to z/OS.
          • RESOURCES/SAMPLE.CUSTFILE into the sequential data set HLQ.SAMPLE.CUSTFILE
          • RESOURCES/SAMPLE.TRANFILE into the sequential data set HLQ. SAMPLE TRANFILE
          Copy and Paste Sequential Data Sets to Save on z/OS
        9. In the JCL directory of zopeneditor-sample, repeat the modification to the RUN.jcl on line 30 and set the HLQ with the same one used in ALLOCATE.jcl. You might or might not need to modify the other symbolics depending on the compile and link libraries your host system uses. You might or might not change the SPACE1 and SPACE2 symbolics, and save the file.
        10. Click Terminal from the top VS Code menu bar, then select New Terminal to open the terminal.
        11. Submit the local RUN.jcl file by entering this command in the terminal:
          zowe rse submit local-file "./JCL/RUN.jcl"
diff --git a/assets/samplefiles.html.3e8b1a83.js b/assets/samplefiles.html.0f622c14.js
similarity index 99%
rename from assets/samplefiles.html.3e8b1a83.js
rename to assets/samplefiles.html.0f622c14.js
index 9918dbd46..464b600b9 100644
--- a/assets/samplefiles.html.3e8b1a83.js
+++ b/assets/samplefiles.html.0f622c14.js
@@ -1,2 +1,2 @@
-import{r as a,o as s,a as n,b as e,d as t,w as r,F as l,e as o,c as d}from"./app.f6cb3ed9.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";const p={},u=e("h1",{id:"exploring-the-sample-files",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#exploring-the-sample-files","aria-hidden":"true"},"#"),o(" Exploring the sample files")],-1),m=e("p",null,"Within this documentation we refer to a set of sample files that you can use to explore the editor features. These samples are provided on Github.com.",-1),f=e("h2",{id:"get-the-sample-files",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#get-the-sample-files","aria-hidden":"true"},"#"),o(" Get the sample files")],-1),S=o("Assuming that you have Git installed as described in the "),b=o("Prerequisites"),g=o(", create a work directory somewhere on your machine and clone the sample repository:"),A=d(`
          git clone https://github.com/IBM/zopeneditor-sample.git
+import{r as a,o as s,a as n,b as e,d as t,w as r,F as l,e as o,c as d}from"./app.daa93c96.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";const p={},u=e("h1",{id:"exploring-the-sample-files",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#exploring-the-sample-files","aria-hidden":"true"},"#"),o(" Exploring the sample files")],-1),m=e("p",null,"Within this documentation we refer to a set of sample files that you can use to explore the editor features. These samples are provided on Github.com.",-1),f=e("h2",{id:"get-the-sample-files",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#get-the-sample-files","aria-hidden":"true"},"#"),o(" Get the sample files")],-1),S=o("Assuming that you have Git installed as described in the "),b=o("Prerequisites"),g=o(", create a work directory somewhere on your machine and clone the sample repository:"),A=d(`
          git clone https://github.com/IBM/zopeneditor-sample.git
 
          Then open the directory zopeneditor-sample using the File > Open... menu. The sample files in this directory will be referred to throughout the rest of the documentation.
           Understand the Git repository branches
          The sample Git repository contains seven branches with variants of our sample programs for different evaluation use cases.
          `,4),I=e("li",null,"main: provides code and configuration file examples that can be used with the basic IBM Z Open Editor installation obtains from the VS Code Marketplace.",-1),L=e("li",null,"tutorial_complete: extends the examples from the main branch with code changes that you can use to simulate a before and after view of making changes to source code.",-1),T=o("wazi-main: provides additional configuration file examples for commercial extensions to IBM Z Open Editor such as IBM Open Debug, User Build with IBM Dependency-Based Build, Red Hat Ansible Certified Content for IBM Z collection, and GitLab CI. The "),E={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=developing-wazi-vs-code",target:"_blank",rel:"noopener noreferrer"},_=o("IBM Documentation"),M=o(" has more details for using these tools and examples."),w=e("li",null,"wazi-tutorial-complete: provides an after-changes-view of the examples in wazi-main with the same advanced configurations files.",-1),y=o("devfile: contains a variant of wazi-main that can be used in Red Hat's Dev Spaces for OpenShift v3 environment. See a tutorial for trying Z Open Editor running in Dev Spaces on Red Hat's free Developer Sandbox "),C={href:"https://github.com/IBM/zopeneditor-about/tree/main/che",target:"_blank",rel:"noopener noreferrer"},R=o("in our GitHub repository"),v=o("."),x=d('
           Examine the sample files
          The sample application in the main and tutorial-complete branches consists of the following files:
          • COBOL programs: SAM1, SAM2, and SAM1LIB
            SAM1 reads in both the CUSTFILE and TRANFILE data files, and then performs different actions on the CUSTFILE based on transactions from the TRANFILE. Valid transactions are ADD, UPDATE, and DELETE. When an UPDATE transaction is processed, SAM1 calls SAM2 to perform the requested update.
            SAM2 includes some base code in place for CRUNCH transactions, which can be enhanced using Instructions provided later in this document . At the end of processing the TRANFILE, SAM1 generates a report on the transactions processed and produces an updated CUSTFILE.
            SAM1LIB is included to demonstrate the editor's ability to resolve copybooks that are part of a library. It is a copy of SAM1 with the exception of the library-based copybooks.
          • Copybooks: CUSTCOPY, REGISTRS, and TRANREC
          • Libraries Copybooks: DATETIME (local) and REPTTOTL (MVS). These copybooks demonstrate using the libraries option in a COPY <copybook> IN <library> statement for local and MVS copybooks
          • PL/I programs: PSAM1, PSAM2, and PSAM1LIB
            PSAM1 reads in both the PLI.CUSTFILE and PLI.TRANFILE data files, and then produces a report with customer information and a Totals summary section. Valid transactions are PRINT and TOTALS. A PRINT transaction prints the Customer records to the Customer section of the report. When PSAM1 reads in a TOTALS transaction, it generates the Totals Report section. The instructions, provided later in this document, guide you through making the necessary code changes to allow PSAM1 to process a new type of Customer record called a Product record and generate a new line for the Service Calls in the Totals Report section.
            PSAM1LIB is included to demonstrate the editor's ability to resolve includes that are part of a library. It is a copy of PSAM1 with the exception of the library-based includes.
          • Include files: BALSTATS and CUSTPLI
          • Libraries Includes: DATETIME (local) and REPTTOTL (MVS) - these includes demonstrate using the libraries option in an %INCLUDE <library> (<include>); statement for local and MVS includes
          • HLASM programs: ASAM1 and ASAM2
            ASAM1 reads the ASM.FILEIN data file and will write out the record number, column number heading records, and the input string to ASM.FILEOUT. Instructions provided later in this document will guide you through making the necessary code changes to have ASAM1 call ASAM2 which will take the input string, convert it to hexadecimal format and pass it back to ASAM1, which will then write the hex value for the string to the ASM.FILEOUT data file.
          • REXX program: RSAM1
            RSAM1 reads the REXX.FILEIN1 and REXX.FILEIN2 data files and will write out the records to REXX.FILEOUT. Instructions provided later in this document will guide you through making the necessary code changes to create a new subroutine in RSAM1 to have it read through REXX.FILEOUT and display all of the records.
          • JCL members that set up and run the applications: ALLOCATE, RUN, PLIALLOC, RUNPSAM1, ASMALLOC, RUNASAM1, and REXALLOC.
          • Data source files: CUSTFILE, TRANFILE, PLI.TRANFILE, PLI.CUSTFILE, ASM.FILEIN, REXX.FILEIN1, and REXX.FILEIN2.
          • Script Files:
            • zowecli-create-profiles.sh - This shell script will create Zowe CLI RSE and SSH profiles and then set them as the default profiles.
              • Parameters necessary to run the script: 
                • TSO USER ID and Password
                • Z host address
                • RSE API port number
                • SSH port number
            • zowecli-cobol-upload-run-simple.sh - This shell script will run the sample COBOL application.
              • Submits the JCL to allocate the required MVS datasets
              • Uploads the application components from the local directory to the MVS datasets
              • Submits the JCL to run the application
            • zowecli-cobol-upload-run-tutorial.sh - This shell script will run the sample COBOL application and download the output files.
              • Submits the JCL to allocate the required MVS datasets
              • Uploads the application components from the local directory to the MVS datasets
              • Submits the JCL to run the application
              • Downloads the output data files once the JES job is complete
            • zowecli-cobol-clean.sh - This shell script will delete the MVS data sets allocated and created during the execution of the sample application.
          ',3);function P(O,F){const c=a("RouterLink"),i=a("ExternalLinkIcon");return s(),n(l,null,[u,m,f,e("p",null,[S,t(c,{to:"/Docs/getting_started.html#prerequisites"},{default:r(()=>[b]),_:1}),g]),A,e("ul",null,[I,L,e("li",null,[T,e("a",E,[_,t(i)]),M]),w,e("li",null,[y,e("a",C,[R,t(i)]),v])]),x],64)}var U=h(p,[["render",P]]);export{U as default};
diff --git a/assets/setting_compiler_options.html.79ec5ce5.js b/assets/setting_compiler_options.html.c0208ac5.js
similarity index 99%
rename from assets/setting_compiler_options.html.79ec5ce5.js
rename to assets/setting_compiler_options.html.c0208ac5.js
index f239f52f2..1d7e42df2 100644
--- a/assets/setting_compiler_options.html.79ec5ce5.js
+++ b/assets/setting_compiler_options.html.c0208ac5.js
@@ -1,4 +1,4 @@
-import{r as t,o as r,a as c,b as e,d as o,F as i,c as s,e as a}from"./app.f6cb3ed9.js";import{_ as p}from"./plugin-vue_export-helper.21dcd24c.js";const l={},d=s('
           Setting compiler options
          Compiler options affect how the editor interprets your COBOL or PL/I programs for editing. You can specify compiler options in property groups in ZAPP files as well as inline in individual program files. The following sections provide references and examples for each language currently supported by the editor.
           COBOL
          Table 1. COBOL Compiler Options
          Aspect of your programCompiler optionsDefaultOption abbreviations
          Source languageCURRENCYNOCURRENCYCURR|NOCURR
           CURRENCY
          You can use the CURRENCY compiler option to provide an alternative default currency symbol to be used for COBOL program.
           Syntax
          'CURRENCY= NO |literal
          Default: CURRENCY= $
          CURRENCY=NO is the default option. CURRENCY abbreviations are CURR or NOCURR.
          literal Represents the default currency symbol that you want to use in your program. The literal must be an alphanumeric literal (optionally a hexadecimal literal) representing a 1-byte EBCDIC character that must not be any of the following items:
          ',12),u=s("
        12. Digits zero (0) through nine (9)
        13. Uppercase alphabetic characters: A B C D P R S V X Z
        14. Lowercase alphabetic characters a through z
        15. The space
        16. Special characters: \\* + - / , . ; ( ) = "
        17. Uppercase alphabetic character G, if the COBOL program defines a DBCS item with the PICTURE symbol G. The PICTURE clause will not be valid for that DBCS item because the symbol G is considered to be a currency symbol in the PICTURE clause.
        18. Uppercase alphabetic character N, if the COBOL program defines a DBCS item with the PICTURE symbol N. The PICTURE clause will not be valid for that DBCS item because the symbol N is considered to be a currency symbol in the PICTURE clause.
          19. ",7),h=a("Uppercase alphabetic character E, if the COBOL program defines an external floating-point item. The "),m=e("code",null,"PICTURE",-1),b=a(" clause will not be valid for the external floating-point item because the symbol E is considered to be a currency symbol in the "),g=e("code",null,"PICTURE",-1),f=a(" clause. For more details, see "),y={href:"https://www.ibm.com/docs/en/cobol-zos/6.3?topic=ecco-currency",target:"_blank",rel:"noopener noreferrer"},k=a("CURRENCY compiler option"),x=s(`
           Examples
          You can define the CURRENCY option in the source program as a suboption or in a property group compiler option.
          To define in the source program, use the following lines:
          cbl CURRENCY(\u20AC);\`
+import{r as t,o as r,a as c,b as e,d as o,F as i,c as s,e as a}from"./app.daa93c96.js";import{_ as p}from"./plugin-vue_export-helper.21dcd24c.js";const l={},d=s('
           Setting compiler options
          Compiler options affect how the editor interprets your COBOL or PL/I programs for editing. You can specify compiler options in property groups in ZAPP files as well as inline in individual program files. The following sections provide references and examples for each language currently supported by the editor.
           COBOL
          Table 1. COBOL Compiler Options
          Aspect of your programCompiler optionsDefaultOption abbreviations
          Source languageCURRENCYNOCURRENCYCURR|NOCURR
           CURRENCY
          You can use the CURRENCY compiler option to provide an alternative default currency symbol to be used for COBOL program.
           Syntax
          'CURRENCY= NO |literal
          Default: CURRENCY= $
          CURRENCY=NO is the default option. CURRENCY abbreviations are CURR or NOCURR.
          literal Represents the default currency symbol that you want to use in your program. The literal must be an alphanumeric literal (optionally a hexadecimal literal) representing a 1-byte EBCDIC character that must not be any of the following items:
          ',12),u=s("
        19. Digits zero (0) through nine (9)
        20. Uppercase alphabetic characters: A B C D P R S V X Z
        21. Lowercase alphabetic characters a through z
        22. The space
        23. Special characters: \\* + - / , . ; ( ) = "
        24. Uppercase alphabetic character G, if the COBOL program defines a DBCS item with the PICTURE symbol G. The PICTURE clause will not be valid for that DBCS item because the symbol G is considered to be a currency symbol in the PICTURE clause.
        25. Uppercase alphabetic character N, if the COBOL program defines a DBCS item with the PICTURE symbol N. The PICTURE clause will not be valid for that DBCS item because the symbol N is considered to be a currency symbol in the PICTURE clause.
          26. ",7),h=a("Uppercase alphabetic character E, if the COBOL program defines an external floating-point item. The "),m=e("code",null,"PICTURE",-1),b=a(" clause will not be valid for the external floating-point item because the symbol E is considered to be a currency symbol in the "),g=e("code",null,"PICTURE",-1),f=a(" clause. For more details, see "),y={href:"https://www.ibm.com/docs/en/cobol-zos/6.3?topic=ecco-currency",target:"_blank",rel:"noopener noreferrer"},k=a("CURRENCY compiler option"),x=s(`
           Examples
          You can define the CURRENCY option in the source program as a suboption or in a property group compiler option.
          To define in the source program, use the following lines:
          cbl CURRENCY(\u20AC);\`
 
          To define in property groups, add the following lines:
          propertyGroups:
   - name: cobol-settings
     language: cobol
diff --git a/assets/setting_disableproblems.html.951054d5.js b/assets/setting_disableproblems.html.1122c286.js
similarity index 96%
rename from assets/setting_disableproblems.html.951054d5.js
rename to assets/setting_disableproblems.html.1122c286.js
index 6cefe1c65..e8b5e6d02 100644
--- a/assets/setting_disableproblems.html.951054d5.js
+++ b/assets/setting_disableproblems.html.1122c286.js
@@ -1,2 +1,2 @@
-import{r as a,o as s,a as i,b as n,d as r,w as t,F as l,c as d,e}from"./app.f6cb3ed9.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const p={},b=d(`
           Enabling and disabling problems in IBM Z Open Editor
          IBM Z Open Editor performs real-time syntax checking and provides annotations that describe problems or errors in COBOL, HLASM, PL/I, REXX, and JCL code:
          • To see the annotations that describe a specific error, hover over the red underlined code in the editor.
          • To see annotations for all errors and warnings for all opened editors, open the Problems view by pressing Ctrl+Shift+M (on Windows) or Cmd+Shift+M (on Mac).
          You can enable or disable the showing of problems in your programs when you are maintaining other language features by using the settings provided by IBM Z Open Editor. The showing of problems is enabled by default. To disable the showing of problems in a specific language, specify the following preference setting:
          "zopeneditor.<language>.disableProblems": true
+import{r as a,o as s,a as i,b as n,d as r,w as t,F as l,c as d,e}from"./app.daa93c96.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const p={},b=d(`
           Enabling and disabling problems in IBM Z Open Editor
          IBM Z Open Editor performs real-time syntax checking and provides annotations that describe problems or errors in COBOL, HLASM, PL/I, REXX, and JCL code:
          • To see the annotations that describe a specific error, hover over the red underlined code in the editor.
          • To see annotations for all errors and warnings for all opened editors, open the Problems view by pressing Ctrl+Shift+M (on Windows) or Cmd+Shift+M (on Mac).
          You can enable or disable the showing of problems in your programs when you are maintaining other language features by using the settings provided by IBM Z Open Editor. The showing of problems is enabled by default. To disable the showing of problems in a specific language, specify the following preference setting:
          "zopeneditor.<language>.disableProblems": true
 
          `,5),g=n("strong",null,"Note",-1),h=e(": Disabling COBOL's problems will also disable unreachable code warnings. For more information, see "),m=e("Enabling and disabling unreachable COBOL code warnings"),u=e(".");function f(_,w){const o=a("RouterLink");return s(),i(l,null,[b,n("p",null,[g,h,r(o,{to:"/Docs/setting_unreachablecodewarnings.html"},{default:t(()=>[m]),_:1}),u])],64)}var B=c(p,[["render",f]]);export{B as default};
diff --git a/assets/setting_fileassociations.html.c145a7e0.js b/assets/setting_fileassociations.html.3121d46c.js
similarity index 99%
rename from assets/setting_fileassociations.html.c145a7e0.js
rename to assets/setting_fileassociations.html.3121d46c.js
index 30021cadf..62569ef4d 100644
--- a/assets/setting_fileassociations.html.c145a7e0.js
+++ b/assets/setting_fileassociations.html.3121d46c.js
@@ -1,4 +1,4 @@
-import{r as i,o as p,a as l,b as t,d as a,w as o,F as r,c as e,e as s}from"./app.f6cb3ed9.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const u={},d=e(`
           Setting file associations
          For local files, IBM Z Open Editor identifies the language of a file opened in the editor based on file extensions in both the default and customized files.associations user settings. This also applies to the include files by using a different user setting; zopeneditor.<language-id>.includeFileExtensions.
          For remote files, as MVS data sets do not have file extensions, IBM Z Open Editor uses zopeneditor.datasets.<language-id>Datasets user settings to configure the editor for MVS data sets.
           Local file associations
           Adding more file associations
          IBM Z Open Editor registers itself in VS Code with support for several languages. For each language, it also defines a set of file extensions that by default will be mapped to the registered languages as shown in the table below.
          LanguageVS Code Language IDDefault File Extensions
          Enterprise COBOLcobol.cbl .cpy .cob .copy .copybook .cobol .cobcopy
          Enterprise PL/Ipl1.pli .pl1 .pc .pci .plinc .pcx .inc .include
          Z High Level Assemblerhlasm.s .assemble .asm .hla .hlasm
          REXXrexx.rexx .rex
          JCLjcl.jcl .cntl .proc
          Table 1. IBM Z Open Editor default mapping of languages and file extensions
          When you open a file with one of these file extensions in Z Open Editor, then VS Code displays the mapped language in the language selector on the lower-right of the status bar. If you want to temporarily switch the opened editor to any other language available in VS Code, click this bar and enter the wanted language.
          If you want to use a file extension in addition to the defaults for any of these languages, you must define them yourself in the user or workspace settings by using either of the following approaches.
          • Option 1: Using the VS Code Preferences UI
            1. Click File > Preference > Settings and switch to either User or Workspace settings.
              Tip: Switch to Workspace settings if you want to define the mappings locally to the current project and store it in SCM with your programs.
            2. In the Search bar at the top type associations. It brings up the VS Code Files: Associations setting, which contains a list of the current non-default file associations defined.
              Note: The default associations that are shown in Table 1 are not listed here because they cannot be changed.
            3. Click the Add Item button to add another entry. It prompts for a Key, which is the file extension starting with the symbols *. such as *.cp1 and a Value entry that is the language identifier as listed in Table 1.
          • Option 2: Editing the settings.json file
            As an alternative to using the VS Code Preferences UI, you can also edit the JSON file of the user or workspace settings. The format is:
            "files.associations": {
+import{r as i,o as p,a as l,b as t,d as a,w as o,F as r,c as e,e as s}from"./app.daa93c96.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const u={},d=e(`
             Setting file associations
            For local files, IBM Z Open Editor identifies the language of a file opened in the editor based on file extensions in both the default and customized files.associations user settings. This also applies to the include files by using a different user setting; zopeneditor.<language-id>.includeFileExtensions.
            For remote files, as MVS data sets do not have file extensions, IBM Z Open Editor uses zopeneditor.datasets.<language-id>Datasets user settings to configure the editor for MVS data sets.
             Local file associations
             Adding more file associations
            IBM Z Open Editor registers itself in VS Code with support for several languages. For each language, it also defines a set of file extensions that by default will be mapped to the registered languages as shown in the table below.
            LanguageVS Code Language IDDefault File Extensions
            Enterprise COBOLcobol.cbl .cpy .cob .copy .copybook .cobol .cobcopy
            Enterprise PL/Ipl1.pli .pl1 .pc .pci .plinc .pcx .inc .include
            Z High Level Assemblerhlasm.s .assemble .asm .hla .hlasm
            REXXrexx.rexx .rex
            JCLjcl.jcl .cntl .proc
            Table 1. IBM Z Open Editor default mapping of languages and file extensions
            When you open a file with one of these file extensions in Z Open Editor, then VS Code displays the mapped language in the language selector on the lower-right of the status bar. If you want to temporarily switch the opened editor to any other language available in VS Code, click this bar and enter the wanted language.
            If you want to use a file extension in addition to the defaults for any of these languages, you must define them yourself in the user or workspace settings by using either of the following approaches.
            • Option 1: Using the VS Code Preferences UI
              1. Click File > Preference > Settings and switch to either User or Workspace settings.
                Tip: Switch to Workspace settings if you want to define the mappings locally to the current project and store it in SCM with your programs.
              2. In the Search bar at the top type associations. It brings up the VS Code Files: Associations setting, which contains a list of the current non-default file associations defined.
                Note: The default associations that are shown in Table 1 are not listed here because they cannot be changed.
              3. Click the Add Item button to add another entry. It prompts for a Key, which is the file extension starting with the symbols *. such as *.cp1 and a Value entry that is the language identifier as listed in Table 1.
            • Option 2: Editing the settings.json file
              As an alternative to using the VS Code Preferences UI, you can also edit the JSON file of the user or workspace settings. The format is:
              "files.associations": {
     "*.cp1": "cobol"
 }
 
              You can enter a full glob pattern as keys. With such flexible glob patterns, you can map files to a language by using file extensions and arbitrary substring mappings.
             Removing file associations
            If you remove some of the entries there that were added by IBM Z Open Editor at startup, such as "*.COBOL*": "cobol",, and save, they might reappear afterward. To prevent that see the details below on managing remote file associations that cause this behavior.
            Before you be able to remove any of the mappings from the files.associations, you must remove them first from the Datasets settings and Include File Extensions settings first. The reason is that IBM Z Open Editor tries to automatically add these two settings into files.associations to support its features.
             Defining include file associations
            `,15),h=s("The include files can be on the local file system or located in remote MVS data sets. After you define "),g=s("property groups"),f=s(" to tell IBM Z Open Editor where to look for include files such as COBOL copybooks, for the include files that are stored locally, you must define the default file extensions to identify a valid include file for each language. Without a valid file extension, IBM Z Open Editor cannot find include files and cannot open them correctly for editing."),b=e(`
            You can customize your own file extensions by using either of the following approaches.
            • Option 1: Using the VS Code Preferences UI
              1. Click File > Preference > Settings and switch to either User or Workspace settings.
                Tip: Switch to Workspace settings if you want to define the mappings locally to the current project and store it in SCM with your programs.
              2. On the left of Settings editor expand the Extensions group and select the entry IBM Z Open Editor.
              3. Scroll on the right to see all the different Z Open Editor settings available. There are three settings available for configuring include file extensions:
                • Cobol: Include File Extensions
                • Hlasm: Include File Extensions
                • Pl1: Include File Extensions
                • Rexx: Include File Extensions
                Each shows a list of the currently registered file extensions populated with a set of defaults.
              4. Click the Add Item button and enter the extension with a leading dot-character such as .cp1.
              5. Click the OK button to save it. You will see that your new extension has also been added automatically to the files.associations setting, which is discussed in file associations.
              6. If you remove an extension from the list, IBM Z Open Editor will not currently remove it from the files.associations however. You need to remove it there yourself.
            • Option 2: Editing the settings.json file
              As an alternative to using the VS Code Preferences UI, you can also edit the following properties in the JSON file of the user or workspace settings.
              • zopeneditor.cobol.includeFileExtensions
              • zopeneditor.hlasm.includeFileExtensions
              • zopeneditor.pl1.includeFileExtensions
              • zopeneditor.rexx.includeFileExtensions
              An example could be the following that adds .mac and .cpysrc to the default set of HLASM include file extensions:
              "zopeneditor.hlasm.includeFileExtensions": [
diff --git a/assets/setting_maximum_line_length.html.4cc75ee6.js b/assets/setting_maximum_line_length.html.5947d19c.js
similarity index 98%
rename from assets/setting_maximum_line_length.html.4cc75ee6.js
rename to assets/setting_maximum_line_length.html.5947d19c.js
index 854a01f1c..0eebac5a5 100644
--- a/assets/setting_maximum_line_length.html.4cc75ee6.js
+++ b/assets/setting_maximum_line_length.html.5947d19c.js
@@ -1,4 +1,4 @@
-import{r as s,o as i,a as o,b as n,d as r,w as l,F as m,c as t,e}from"./app.f6cb3ed9.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const c={},u=t(`
               Setting language-specific maximum line length
              You can set the maximum line length for COBOL, PL/I, HLASM, REXX, and JCL program files with IBM Z Open Editor so that a file that exceeds the maximum line length is not allowed to be saved.
              If a file that exceeds the maximum line length is being saved, the following warning is displayed:
              Truncation warning: You are trying to save a file that exceeds the maximum line length. You can configure the line length in Preferences. Saving the file will truncate all text after column 80. Do you want to continue?
+import{r as s,o as i,a as o,b as n,d as r,w as l,F as m,c as t,e}from"./app.daa93c96.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const c={},u=t(`
               Setting language-specific maximum line length
              You can set the maximum line length for COBOL, PL/I, HLASM, REXX, and JCL program files with IBM Z Open Editor so that a file that exceeds the maximum line length is not allowed to be saved.
              If a file that exceeds the maximum line length is being saved, the following warning is displayed:
              Truncation warning: You are trying to save a file that exceeds the maximum line length. You can configure the line length in Preferences. Saving the file will truncate all text after column 80. Do you want to continue?
 
              If you choose Yes, all text after column 80 or a column number that was specified in the preference settings will be removed by the editor.
              If you choose No, the file will not be saved. To continue saving the file, you can either change the maximum line length or remove the text after the column number that is specified in the preference settings.
              `,6),h=e("To configure the maximum line length, add "),p=n("code",null,"zopeneditor.language.maximumLineLength",-1),g=e(", such as "),x=n("code",null,"zopeneditor.cobol.maximumLineLength",-1),b=e(", in settings.json, and provide a 0-based column number to your user or workspace settings. For information about adding user or workspace settings, see "),f=e("Accessing settings for IBM Z Open Editor"),L=e("."),v=t(`
               Setting the COBOL maximum line length
              To configure the COBOL maximum line length, add zopeneditor.cobol.maximumLineLength in settings.json and provide 0-based column number to your user or workspace settings:
              "zopeneditor.cobol.maximumLineLength": 80
 
              The default maximum line length setting for COBOL is 80.
               Setting the PL/I maximum line length
              To configure the PL/I maximum line length, add zopeneditor.pl1.maximumLineLength in settings.json and provide 0-based column number to your user or workspace settings:
              "zopeneditor.pl1.maximumLineLength": 80
 
              The default maximum line length setting for PL/I is 80.
               Setting the HLASM maximum line length
              To configure the HLASM maximum line length, add zopeneditor.hlasm.maximumLineLength in settings.json and provide 0-based column number to your user or workspace settings:
              "zopeneditor.hlasm.maximumLineLength": 80
diff --git a/assets/setting_preferences.html.52fc78b8.js b/assets/setting_preferences.html.c7693b1e.js
similarity index 99%
rename from assets/setting_preferences.html.52fc78b8.js
rename to assets/setting_preferences.html.c7693b1e.js
index 9aa63002e..848a5045a 100644
--- a/assets/setting_preferences.html.52fc78b8.js
+++ b/assets/setting_preferences.html.c7693b1e.js
@@ -1 +1 @@
-import{r,o as i,a,b as t,d as s,w as c,F as d,c as p,e}from"./app.f6cb3ed9.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";const h={},f=p('
               Setting preferences
              Before using IBM Z Open Editor, you can set preferences to control the characteristics of your environment. Preferences can be defined in various places depending on their scope - from user-specific settings to team project settings for files being edited. Z Open Editor distinguishes between settings provided via VS Code Preferences with settings provided in ZAPP files that are scoped to the application level and stored with your source code files. Application-specific settings, such as build flags, are typically shared with your team in ZAPP files. Personal settings, such as which Zowe profile to use for the user build, are usually in VS Code user settings.
               Accessing VS Code settings for IBM Z\xAE Open Editor
              To open the settings for IBM Z Open Editor in VS Code, follow the steps below:
              1. In VS Code, open Settings.
                • On Windows, click File > Preferences > Settings.
                • On Mac, click Code > Preferences > Settings.
              2. To display the setting options for IBM Z Open Editor, expand the Extensions dropdown in the list on the left. Click on the entry IBM Z Open Editor.
              3. All the preferences shown in the visual editor are represented as JSON. Complex preferences that are not just simple values must be entered by using the JSON editor itself. To open it, select the scope tab first: User tab or Workspace tab, and then open the JSON view by clicking Edit in settings.json, or by clicking on the Open Settings (JSON) icon on the upper-right of the editor.
               VS Code user preferences versus workspace preferences
              In the editor panel, a list of preference groups is displayed, along with editor tabs for both the User and Workspace Preferences. Switch between these tabs to decide in which scope you want to add a preference.
               User preferences
              User preferences apply to the current user across different workspaces. They include not only typical user preferences related to accessibility, such as font sizes and editor behavior for code completion, but also Zowe Profiles defining z/OS\xAE host connection information and personal high-level qualifiers. The settings are stored for the user in their home directory, apply to all the open VS Code windows, and are not shared with other users.
               Workspace preferences
              Workspace preferences apply to the current workspace and are stored inside the .vscode directory at the root of the workspace. If you share the workspace with other users through Git, you would also share the settings if the intent is for them to be the same across users. For example, preference settings such as tab size or file extensions would apply regardless of who edits the files.
              Note: The workspace preferences always override user preferences.
              ',12),u=e("VS Code also supports the concept of "),g={href:"https://code.visualstudio.com/docs/editor/multi-root-workspaces",target:"_blank",rel:"noopener noreferrer"},w=e("multi-root workspaces"),_=e(" that can also be utilized for Z Open Editor. Multi-root workspaces allow you to work with multiple folders, each representing a workspace in Visual Studio Code. This is helpful when you are working on several related projects at one time. Each workspace can use a different Git repository and be located anywhere on your development machine. A multi-root workspace basically combines all the individual and independent folders into one tree view in the File Explorer. Settings are defined for the entire multi-root workspace in a "),m=t("code",null,".code-workspace",-1),b=e(" file, as well as for each individual workspace. In the case of a conflict, determining which setting has precedence over another depends on the setting type."),k=e("For more details and information on types of settings available to VS Code in general, refer to the "),v={href:"https://code.visualstudio.com/docs/getstarted/settings",target:"_blank",rel:"noopener noreferrer"},y=e("User and Workspace Settings"),S=e(" and "),x={href:"https://code.visualstudio.com/docs/editor/multi-root-workspaces#_settings",target:"_blank",rel:"noopener noreferrer"},C=e("Multi-root Workspaces: Settings"),O=e(" VS Code documentation pages."),P=t("p",null,[e("Details about specific Z Open Editor settings and behavior are provided in the following section, and also in the "),t("a",{href:"settings"},"Settings Reference"),e(".")],-1),E=t("h2",{id:"vs-code-user-preferences-versus-zapp-files",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#vs-code-user-preferences-versus-zapp-files","aria-hidden":"true"},"#"),e(" VS Code user preferences versus ZAPP files")],-1),Z=e("Some preferences in Z Open Editor are specific to the application under development and should be stored independent of the editor being used to edit the program files. Examples are the search path for folders in which include files such as COBOL copybooks are located, or what compiler options should be used to parse the programs to show syntax errors in the editor. These preferences are stored in a file called ZAPP (Z APPlication) file. The section "),V=e("Configure your applications with ZAPP files"),I=e(" provides a full overview.");function A(B,T){const o=r("ExternalLinkIcon"),n=r("RouterLink");return i(),a(d,null,[f,t("p",null,[u,t("a",g,[w,s(o)]),_,m,b]),t("p",null,[k,t("a",v,[y,s(o)]),S,t("a",x,[C,s(o)]),O]),P,E,t("p",null,[Z,s(n,{to:"/Docs/zapp.html"},{default:c(()=>[V]),_:1}),I])],64)}var M=l(h,[["render",A]]);export{M as default};
+import{r,o as i,a,b as t,d as s,w as c,F as d,c as p,e}from"./app.daa93c96.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";const h={},f=p('
               Setting preferences
              Before using IBM Z Open Editor, you can set preferences to control the characteristics of your environment. Preferences can be defined in various places depending on their scope - from user-specific settings to team project settings for files being edited. Z Open Editor distinguishes between settings provided via VS Code Preferences with settings provided in ZAPP files that are scoped to the application level and stored with your source code files. Application-specific settings, such as build flags, are typically shared with your team in ZAPP files. Personal settings, such as which Zowe profile to use for the user build, are usually in VS Code user settings.
               Accessing VS Code settings for IBM Z\xAE Open Editor
              To open the settings for IBM Z Open Editor in VS Code, follow the steps below:
              1. In VS Code, open Settings.
                • On Windows, click File > Preferences > Settings.
                • On Mac, click Code > Preferences > Settings.
              2. To display the setting options for IBM Z Open Editor, expand the Extensions dropdown in the list on the left. Click on the entry IBM Z Open Editor.
              3. All the preferences shown in the visual editor are represented as JSON. Complex preferences that are not just simple values must be entered by using the JSON editor itself. To open it, select the scope tab first: User tab or Workspace tab, and then open the JSON view by clicking Edit in settings.json, or by clicking on the Open Settings (JSON) icon on the upper-right of the editor.
               VS Code user preferences versus workspace preferences
              In the editor panel, a list of preference groups is displayed, along with editor tabs for both the User and Workspace Preferences. Switch between these tabs to decide in which scope you want to add a preference.
               User preferences
              User preferences apply to the current user across different workspaces. They include not only typical user preferences related to accessibility, such as font sizes and editor behavior for code completion, but also Zowe Profiles defining z/OS\xAE host connection information and personal high-level qualifiers. The settings are stored for the user in their home directory, apply to all the open VS Code windows, and are not shared with other users.
               Workspace preferences
              Workspace preferences apply to the current workspace and are stored inside the .vscode directory at the root of the workspace. If you share the workspace with other users through Git, you would also share the settings if the intent is for them to be the same across users. For example, preference settings such as tab size or file extensions would apply regardless of who edits the files.
              Note: The workspace preferences always override user preferences.
              ',12),u=e("VS Code also supports the concept of "),g={href:"https://code.visualstudio.com/docs/editor/multi-root-workspaces",target:"_blank",rel:"noopener noreferrer"},w=e("multi-root workspaces"),_=e(" that can also be utilized for Z Open Editor. Multi-root workspaces allow you to work with multiple folders, each representing a workspace in Visual Studio Code. This is helpful when you are working on several related projects at one time. Each workspace can use a different Git repository and be located anywhere on your development machine. A multi-root workspace basically combines all the individual and independent folders into one tree view in the File Explorer. Settings are defined for the entire multi-root workspace in a "),m=t("code",null,".code-workspace",-1),b=e(" file, as well as for each individual workspace. In the case of a conflict, determining which setting has precedence over another depends on the setting type."),k=e("For more details and information on types of settings available to VS Code in general, refer to the "),v={href:"https://code.visualstudio.com/docs/getstarted/settings",target:"_blank",rel:"noopener noreferrer"},y=e("User and Workspace Settings"),S=e(" and "),x={href:"https://code.visualstudio.com/docs/editor/multi-root-workspaces#_settings",target:"_blank",rel:"noopener noreferrer"},C=e("Multi-root Workspaces: Settings"),O=e(" VS Code documentation pages."),P=t("p",null,[e("Details about specific Z Open Editor settings and behavior are provided in the following section, and also in the "),t("a",{href:"settings"},"Settings Reference"),e(".")],-1),E=t("h2",{id:"vs-code-user-preferences-versus-zapp-files",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#vs-code-user-preferences-versus-zapp-files","aria-hidden":"true"},"#"),e(" VS Code user preferences versus ZAPP files")],-1),Z=e("Some preferences in Z Open Editor are specific to the application under development and should be stored independent of the editor being used to edit the program files. Examples are the search path for folders in which include files such as COBOL copybooks are located, or what compiler options should be used to parse the programs to show syntax errors in the editor. These preferences are stored in a file called ZAPP (Z APPlication) file. The section "),V=e("Configure your applications with ZAPP files"),I=e(" provides a full overview.");function A(B,T){const o=r("ExternalLinkIcon"),n=r("RouterLink");return i(),a(d,null,[f,t("p",null,[u,t("a",g,[w,s(o)]),_,m,b]),t("p",null,[k,t("a",v,[y,s(o)]),S,t("a",x,[C,s(o)]),O]),P,E,t("p",null,[Z,s(n,{to:"/Docs/zapp.html"},{default:c(()=>[V]),_:1}),I])],64)}var M=l(h,[["render",A]]);export{M as default};
diff --git a/assets/setting_propertygroup.html.f62b7e80.js b/assets/setting_propertygroup.html.34e159f2.js
similarity index 99%
rename from assets/setting_propertygroup.html.f62b7e80.js
rename to assets/setting_propertygroup.html.34e159f2.js
index 602ce5018..cc15b5783 100644
--- a/assets/setting_propertygroup.html.f62b7e80.js
+++ b/assets/setting_propertygroup.html.34e159f2.js
@@ -1,4 +1,4 @@
-import{r,o as i,a as l,b as s,d as n,w as o,F as c,c as a,e}from"./app.f6cb3ed9.js";import{_ as u}from"./plugin-vue_export-helper.21dcd24c.js";var d="/zopeneditor-about/assets/mvs-connection-test-flow-chart.48c3078a.png";const h={},m=a(`
               Setting property groups
              Property groups are required to define how the COBOL, PL/I, HLASM, and REXX editors search for copybooks and/or includes when you edit a program. Without loading these the language servers used by Z Open Editor will not be able to parse the programs correctly and show many syntax errors that are due to the missing definitions contained in these files. Property Groups can also be used to specify language-specific compiler options.
              To define a property group in your ZAPP file, you can use the VS Code snippets provided by Z Open Editor and then fill in the details. Specify if the file is a syslib include file or part of a library, then provide an array of potential local or remote locations to search in. These locations can be absolute, relative, or GLOB file patterns for a local directory path or MVS data set names to be searched on your z/OS system.
              Here is an example for a COBOL property group from a ZAPP file that defines a local search path for copybooks as well as remote and local location for library files. All these location will be search in oder top-down:
              propertyGroups:
+import{r,o as i,a as l,b as s,d as n,w as o,F as c,c as a,e}from"./app.daa93c96.js";import{_ as u}from"./plugin-vue_export-helper.21dcd24c.js";var d="/zopeneditor-about/assets/mvs-connection-test-flow-chart.48c3078a.png";const h={},m=a(`
               Setting property groups
              Property groups are required to define how the COBOL, PL/I, HLASM, and REXX editors search for copybooks and/or includes when you edit a program. Without loading these the language servers used by Z Open Editor will not be able to parse the programs correctly and show many syntax errors that are due to the missing definitions contained in these files. Property Groups can also be used to specify language-specific compiler options.
              To define a property group in your ZAPP file, you can use the VS Code snippets provided by Z Open Editor and then fill in the details. Specify if the file is a syslib include file or part of a library, then provide an array of potential local or remote locations to search in. These locations can be absolute, relative, or GLOB file patterns for a local directory path or MVS data set names to be searched on your z/OS system.
              Here is an example for a COBOL property group from a ZAPP file that defines a local search path for copybooks as well as remote and local location for library files. All these location will be search in oder top-down:
              propertyGroups:
   - name: cobol-copybooks
     language: cobol
     libraries:
diff --git a/assets/setting_tabstops.html.5806099a.js b/assets/setting_tabstops.html.48761a85.js
similarity index 98%
rename from assets/setting_tabstops.html.5806099a.js
rename to assets/setting_tabstops.html.48761a85.js
index 528d16ad6..6b16b8f6a 100644
--- a/assets/setting_tabstops.html.5806099a.js
+++ b/assets/setting_tabstops.html.48761a85.js
@@ -1,4 +1,4 @@
-import{c as n}from"./app.f6cb3ed9.js";import{_ as s}from"./plugin-vue_export-helper.21dcd24c.js";const a={},e=n(`
               Setting language-specific tab stops and rulers
              With VS Code, you can add tab stops and rulers in the editor depending on the language that you are using. You can customize the IBM Z Open Editor settings based on your own personal perference or organization standards.
               Setting tab stops for COBOL and HLASM
              You can set tab stops for COBOL, HLASM and JCL program files with IBM Z Open Editor so that the cursor stops when you press the Tab key.
              To configure COBOL tab stops, add zopeneditor.cobol.tabstops in settings.json and provide an array of 0-based column numbers to your user or workspace settings:
              "zopeneditor.cobol.tabstops": [
+import{c as n}from"./app.daa93c96.js";import{_ as s}from"./plugin-vue_export-helper.21dcd24c.js";const a={},e=n(`
               Setting language-specific tab stops and rulers
              With VS Code, you can add tab stops and rulers in the editor depending on the language that you are using. You can customize the IBM Z Open Editor settings based on your own personal perference or organization standards.
               Setting tab stops for COBOL and HLASM
              You can set tab stops for COBOL, HLASM and JCL program files with IBM Z Open Editor so that the cursor stops when you press the Tab key.
              To configure COBOL tab stops, add zopeneditor.cobol.tabstops in settings.json and provide an array of 0-based column numbers to your user or workspace settings:
              "zopeneditor.cobol.tabstops": [
     0,
     6,
     7,
diff --git a/assets/setting_unreachablecodewarnings.html.d2b1a2f9.js b/assets/setting_unreachablecodewarnings.html.b7f525ec.js
similarity index 97%
rename from assets/setting_unreachablecodewarnings.html.d2b1a2f9.js
rename to assets/setting_unreachablecodewarnings.html.b7f525ec.js
index 86e7b195b..2d0d50c6c 100644
--- a/assets/setting_unreachablecodewarnings.html.d2b1a2f9.js
+++ b/assets/setting_unreachablecodewarnings.html.b7f525ec.js
@@ -1,2 +1,2 @@
-import{r as a,o as r,a as s,b as e,d as t,w as i,F as c,e as n,c as d}from"./app.f6cb3ed9.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";const h={},p=e("h1",{id:"enabling-and-disabling-unreachable-cobol-code-warnings",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#enabling-and-disabling-unreachable-cobol-code-warnings","aria-hidden":"true"},"#"),n(" Enabling and disabling unreachable COBOL code warnings")],-1),b=e("p",null,"IBM Z Open editor performs real-time syntax checking and provides annotations that describe errors or warnings in COBOL code. To see the annotations that describe a specific error or warning, hover your mouse over the red or yellow underlined code in the editor. To see annotations for all errors and warnings for all opened editors, open the Problems view by pressing Ctrl+Shift+M (Windows) or Cmd+Shift+M (Mac).",-1),u=e("p",null,"IBM Z Open Editor provides settings to enable or disable unreachable code warnings in your COBOL program. Unreachable code in a program is code that can never be executed because there is no path to the code from the rest of the program.",-1),g=n("IBM Z Open Editor performs real-time checking for unreachable COBOL code, but there are currently some limitations to what can be detected and there can be false positives. See the "),f=n("Known issues and limitations"),m=n(" page for details. If you suffer from false warnings and want to disable the feature altogether, you can disable unreachable COBOL code warnings by specifying the following preference setting:"),_=d(`
              "zopeneditor.cobol.enableUnreachableCodeWarnings": false
+import{r as a,o as r,a as s,b as e,d as t,w as i,F as c,e as n,c as d}from"./app.daa93c96.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";const h={},p=e("h1",{id:"enabling-and-disabling-unreachable-cobol-code-warnings",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#enabling-and-disabling-unreachable-cobol-code-warnings","aria-hidden":"true"},"#"),n(" Enabling and disabling unreachable COBOL code warnings")],-1),b=e("p",null,"IBM Z Open editor performs real-time syntax checking and provides annotations that describe errors or warnings in COBOL code. To see the annotations that describe a specific error or warning, hover your mouse over the red or yellow underlined code in the editor. To see annotations for all errors and warnings for all opened editors, open the Problems view by pressing Ctrl+Shift+M (Windows) or Cmd+Shift+M (Mac).",-1),u=e("p",null,"IBM Z Open Editor provides settings to enable or disable unreachable code warnings in your COBOL program. Unreachable code in a program is code that can never be executed because there is no path to the code from the rest of the program.",-1),g=n("IBM Z Open Editor performs real-time checking for unreachable COBOL code, but there are currently some limitations to what can be detected and there can be false positives. See the "),f=n("Known issues and limitations"),m=n(" page for details. If you suffer from false warnings and want to disable the feature altogether, you can disable unreachable COBOL code warnings by specifying the following preference setting:"),_=d(`
              "zopeneditor.cobol.enableUnreachableCodeWarnings": false
 
              `,1);function w(v,O){const o=a("RouterLink");return r(),s(c,null,[p,b,u,e("p",null,[g,t(o,{to:"/Docs/knownissues.html#limitations-of-cobol-program-files"},{default:i(()=>[f]),_:1}),m]),_],64)}var k=l(h,[["render",w]]);export{k as default};
diff --git a/assets/settings.html.3f7de99b.js b/assets/settings.html.3f7de99b.js
deleted file mode 100644
index 6eda162fc..000000000
--- a/assets/settings.html.3f7de99b.js
+++ /dev/null
@@ -1 +0,0 @@
-const m={key:"v-8fabeeca",path:"/Docs/settings.html",title:"settings.json properties",lang:"en-US",frontmatter:{},excerpt:"",headers:[{level:1,title:"settings.json properties",slug:"settings-json-properties",children:[{level:2,title:"List of settings.json properties",slug:"list-of-settings-json-properties",children:[]}]}],git:{updatedTime:1718607473e3,contributors:[{name:"Shi Kun Li",email:"shikunli@cn.ibm.com",commits:16},{name:"Peter Haumer",email:"phaumer@us.ibm.com",commits:10},{name:"Chun Hong Zheng",email:"chunhzh@cn.ibm.com",commits:7},{name:"Lauren Li",email:"Lauren.Li@ibm.com",commits:6},{name:"Peter Haumer",email:"4391934+phaumer@users.noreply.github.com",commits:5},{name:"Bradley Knaysi",email:"bknaysi@ibm.com",commits:3},{name:"Ethan Mendel",email:"Ethan.Mendel@ibm.com",commits:3},{name:"Hestia Zhang",email:"Hestia.Zhang@ibm.com",commits:3},{name:"Lauren Li",email:"45975633+lauren-li@users.noreply.github.com",commits:2},{name:"Saile Daimwood",email:"sdaimwood@ibm.com",commits:2},{name:"Benjamin Santos",email:"Benjamin.Santos@ibm.com",commits:1},{name:"Billie Jean Simmons",email:"billiejean.simmons@ibm.com",commits:1},{name:"KRISTINA MAYO",email:"ktopchi@us.ibm.com",commits:1},{name:"Min Huang",email:"minhsh@cn.ibm.com",commits:1},{name:"Prasang Prajapati",email:"Prasang.A.Prajapati@ibm.com",commits:1},{name:"Saile",email:"sdaimwood@ibm.com",commits:1},{name:"kmaselli",email:"81706519+kmaselli@users.noreply.github.com",commits:1}]},filePathRelative:"Docs/settings.md"};export{m as data};
diff --git a/assets/settings.html.9d25b897.js b/assets/settings.html.9d25b897.js
new file mode 100644
index 000000000..3f8860507
--- /dev/null
+++ b/assets/settings.html.9d25b897.js
@@ -0,0 +1 @@
+const m={key:"v-8fabeeca",path:"/Docs/settings.html",title:"settings.json properties",lang:"en-US",frontmatter:{},excerpt:"",headers:[{level:1,title:"settings.json properties",slug:"settings-json-properties",children:[{level:2,title:"List of settings.json properties",slug:"list-of-settings-json-properties",children:[]}]}],git:{updatedTime:172669751e4,contributors:[{name:"Shi Kun Li",email:"shikunli@cn.ibm.com",commits:16},{name:"Peter Haumer",email:"phaumer@us.ibm.com",commits:10},{name:"Chun Hong Zheng",email:"chunhzh@cn.ibm.com",commits:7},{name:"Lauren Li",email:"Lauren.Li@ibm.com",commits:6},{name:"Peter Haumer",email:"4391934+phaumer@users.noreply.github.com",commits:5},{name:"Bradley Knaysi",email:"bknaysi@ibm.com",commits:3},{name:"Ethan Mendel",email:"Ethan.Mendel@ibm.com",commits:3},{name:"Hestia Zhang",email:"Hestia.Zhang@ibm.com",commits:3},{name:"Lauren Li",email:"45975633+lauren-li@users.noreply.github.com",commits:2},{name:"Saile Daimwood",email:"sdaimwood@ibm.com",commits:2},{name:"Benjamin Santos",email:"Benjamin.Santos@ibm.com",commits:1},{name:"Billie Jean Simmons",email:"billiejean.simmons@ibm.com",commits:1},{name:"KRISTINA MAYO",email:"ktopchi@us.ibm.com",commits:1},{name:"Min Huang",email:"minhsh@cn.ibm.com",commits:1},{name:"PETER HAUMER",email:"phaumer@us.ibm.com",commits:1},{name:"Prasang Prajapati",email:"Prasang.A.Prajapati@ibm.com",commits:1},{name:"Saile",email:"sdaimwood@ibm.com",commits:1},{name:"kmaselli",email:"81706519+kmaselli@users.noreply.github.com",commits:1}]},filePathRelative:"Docs/settings.md"};export{m as data};
diff --git a/assets/settings.html.0cfb3304.js b/assets/settings.html.a9d7c76c.js
similarity index 81%
rename from assets/settings.html.0cfb3304.js
rename to assets/settings.html.a9d7c76c.js
index 5bb7f35de..5fa481019 100644
--- a/assets/settings.html.0cfb3304.js
+++ b/assets/settings.html.a9d7c76c.js
@@ -1 +1 @@
-import{r as i,o as a,a as r,b as e,d as o,w as n,F as d,e as t,c}from"./app.f6cb3ed9.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";const u={},_=e("h1",{id:"settings-json-properties",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#settings-json-properties","aria-hidden":"true"},"#"),t(" settings.json properties")],-1),f=t("You can control the characteristics of your environment by setting the following preferences in "),m=e("code",null,"settings.json",-1),g=t(" by using the JSON editor. For more information, see "),p=t("Accessing settings for IBM Z Open Editor"),b=t("."),y=e("h2",{id:"list-of-settings-json-properties",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#list-of-settings-json-properties","aria-hidden":"true"},"#"),t(" List of settings.json properties")],-1),x=e("thead",null,[e("tr",null,[e("th",{style:{"text-align":"left"}},"Property"),e("th",{style:{"text-align":"left"}},"Description")])],-1),w=e("td",{style:{"text-align":"left"}},[e("code",null,"[cobol]")],-1),v={style:{"text-align":"left"}},S=t("Use "),z=e("code",null,'"[cobol]": {"editor.rulers": [',-1),L=e("em",null,"array",-1),O=e("code",null,"]}",-1),C=t(" to set rulers for COBOL in the editor. "),I=e("em",null,"array",-1),D=t(" is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see "),P=t("Setting language specific tab stops and rulers"),F=t("."),M=e("td",{style:{"text-align":"left"}},[e("code",null,"[hlasm]")],-1),A={style:{"text-align":"left"}},E=t("Use "),Z=e("code",null,'"[hlasm]": {"editor.rulers": [',-1),T=e("em",null,"array",-1),B=e("code",null,"]}",-1),q=t(" to set rulers for HLASM in the editor. "),k=e("em",null,"array",-1),R=t(" is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see "),N=t("Setting language specific tab stops and rulers"),U=t("."),H=e("td",{style:{"text-align":"left"}},[e("code",null,"[jcl]")],-1),V={style:{"text-align":"left"}},J=t("Use "),j=e("code",null,'"[jcl]": {"editor.rulers": [',-1),Y=e("em",null,"array",-1),W=e("code",null,"]}",-1),X=t(" to set rulers for JCL in the editor. "),G=e("em",null,"array",-1),Q=t(" is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see "),$=t("Setting language specific tab stops and rulers"),K=t("."),ee=e("td",{style:{"text-align":"left"}},[e("code",null,"[pl1]")],-1),te={style:{"text-align":"left"}},oe=t("Use "),se=e("code",null,'"[pl1]": {"editor.rulers": [',-1),ne=e("em",null,"array",-1),ie=e("code",null,"]}",-1),le=t(" to set rulers for PL/I in the editor. "),ae=e("em",null,"array",-1),re=t(" is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see "),de=t("Setting language specific tab stops and rulers"),ce=t("."),he=e("td",{style:{"text-align":"left"}},[e("code",null,"[rexx]")],-1),ue={style:{"text-align":"left"}},_e=t("Use "),fe=e("code",null,'"[rexx]": {"editor.rulers": [',-1),me=e("em",null,"array",-1),ge=e("code",null,"]}",-1),pe=t(" to set rulers for REXX in the editor. "),be=e("em",null,"array",-1),ye=t(" is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see "),xe=t("Setting language specific tab stops and rulers"),we=t("."),ve=e("td",{style:{"text-align":"left"}},[e("code",null,"files.associations")],-1),Se={style:{"text-align":"left"}},ze=t("Specifies file names, including data set and member names, that contain certain strings as the appropriate type of file. For detailed usage, see "),Le=t("Setting file associations"),Oe=t("."),Ce=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.cobol.enableUnreachableCodeWarnings")],-1),Ie={style:{"text-align":"left"}},De=t("Enables unreachable code warnings in the COBOL programs. For more information, see "),Pe=t("Enabling and disabling unreachable COBOL code warnings"),Fe=t("."),Me=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.cobol.disableProblems")],-1),Ae={style:{"text-align":"left"}},Ee=t("Disables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. It will also disable unreachable code warnings. The default value is "),Ze=e("code",null,"false",-1),Te=t(". For more information, see "),Be=t("Enabling and disabling problems in IBM Z Open Editor"),qe=t("."),ke=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.cobol.includeFileExtensions")],-1),Re={style:{"text-align":"left"}},Ne=t("Specifies a list of file name extensions for COBOL include files. For more information, see "),Ue=t("Defining Include file associations"),He=t("."),Ve=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.cobol.maximumLineLength")],-1),Je={style:{"text-align":"left"}},je=t("Provides a maximum line length for the COBOL editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see "),Ye=t("Setting language-specific maximum line length"),We=t("."),Xe=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.cobol.sequenceNumbers")]),e("td",{style:{"text-align":"left"}},[t("Choose which columns will have sequence numbers inserted and removed from a file by using the Renumber and Unnumber functions in the COBOL editor. The following values are allowed:"),e("ul",null,[e("li",null,[e("code",null,"zopeneditor.cobol.sequenceNumbers.column1"),t(": Numbering starts at column 1")]),e("li",null,[e("code",null,"zopeneditor.cobol.sequenceNumbers.column73"),t(": Numbering starts at column 73")]),e("li",null,[e("code",null,"zopeneditor.cobol.sequenceNumbers.column1and73"),t(": Numbering starts at column 1 and 73")])])])],-1),Ge=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.cobol.tabstops")],-1),Qe={style:{"text-align":"left"}},$e=t("Adds custom COBOL tab stops in the editor. For more information, see "),Ke=t("Setting language specific tab stops and rulers"),et=t("."),tt=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.datasets")],-1),ot={style:{"text-align":"left"}},st=t("Specifies data set names that should contain COBOL or PL/I programs, copybooks, include files, and JCL. For detailed usage, see "),nt=t("Setting file associations"),it=t("."),lt=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.enforceCaseSensitiveIncludeFileNames")]),e("td",{style:{"text-align":"left"}},[t("Enforce case-sensitive matching of local copybooks and include file names in property groups. Default is "),e("code",null,"false"),t(" to match files with all cases in the path. Set it to true to avoid ambiguous matching on case-insensitive file systems.")])],-1),at=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.disableProblems")],-1),rt={style:{"text-align":"left"}},dt=t("Disables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. The default value is "),ct=e("code",null,"false",-1),ht=t(". For more information, see "),ut=t("Enabling and disabling problems in IBM Z Open Editor"),_t=t("."),ft=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.enableResolvingMacros")],-1),mt={style:{"text-align":"left"}},gt=t("Enables the automatic resolution of "),pt=e("code",null,"SYS1.MACLIB",-1),bt=t(" macro files from MVS using your Zowe Explorer profiles. See the "),yt=t("Remote Macros"),xt=t(" section for more details. The default value is "),wt=e("code",null,"false",-1),vt=t(". To use this feature, you need to set it to "),St=e("code",null,"true",-1),zt=t("."),Lt=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.enableCustomMacrosWarnings")],-1),Ot={style:{"text-align":"left"}},Ct=t("Enables warnings under all custom macros that can not be found in your HLASM programs. The default value is true. For more information, see "),It=t("Custom Macros for HLASM"),Dt=t("."),Pt=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.includeFileExtensions")],-1),Ft={style:{"text-align":"left"}},Mt=t("Specifies a list of file name extensions for HLASM include files. For more information, see "),At=t("Defining Include file associations"),Et=t("."),Zt=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.instructionsFilePath")]),e("td",{style:{"text-align":"left"}},"Allows you to specify a custom HLASM instructions file. Contact IBM Support for questions about the format of such a file or updates to our out of the box file, for example, for a new hardware versions.")],-1),Tt=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.macrosFilePath")]),e("td",{style:{"text-align":"left"}},"Allows you to specify a custom macro definitions file. This option is currently used internally only, but the schema for this format will be provided in a future release so that users can provide their own custom macro references.")],-1),Bt=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.maximumLineLength")],-1),qt={style:{"text-align":"left"}},kt=t("Provides a maximum line length for the HLASM editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see "),Rt=t("Setting language-specific maximum line length"),Nt=t("."),Ut=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.reduceCustomMacroLogging")],-1),Ht={style:{"text-align":"left"}},Vt=t("Reduces the amount of logs that are sent between the HLASM language server and the Z Open Editor client. This increases the performance for scanning and resolving custom macro libraries. The default value is "),Jt=e("code",null,"false",-1),jt=t(". For more information, see "),Yt=t("Custom Macros for HLASM"),Wt=t("."),Xt=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.tabstops")],-1),Gt={style:{"text-align":"left"}},Qt=t("Defines custom HLASM tab stops in the editor. For more information, see "),$t=t("Setting language specific tab stops and rulers"),Kt=t("."),eo=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.zosMacrosVersion")],-1),to={style:{"text-align":"left"}},oo=t("Defines the version of z/OS to use for macro definitions. This allows for more accurate results for the hover and code completion features in HLASM. For more information, see "),so=t("Remote Macros"),no=t("."),io=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.JAVA_HOME")],-1),lo={style:{"text-align":"left"}},ao=t("Specifies a different Java for IBM Z Open Editor other than the default of your computer. For more information, see section Selecting the Java installation to use in "),ro=t("Getting started"),co=t("."),ho=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.jcl.maximumLineLength")],-1),uo={style:{"text-align":"left"}},_o=t("Provides a maximum line length for the JCL editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see "),fo=t("Setting language-specific maximum line length"),mo=t("."),go=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.jcl.tabstops")],-1),po={style:{"text-align":"left"}},bo=t("Defines custom JCL tab stops in the editor. For more information, see "),yo=t("Setting language specific tab stops and rulers"),xo=t("."),wo=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.jcl.disableProblems")],-1),vo={style:{"text-align":"left"}},So=t("Disables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. The default value is "),zo=e("code",null,"false",-1),Lo=t(". For more information, see "),Oo=t("Enabling and disabling problems in IBM Z Open Editor"),Co=t("."),Io=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.logger")],-1),Do={style:{"text-align":"left"}},Po=t("Enables a logging output. See "),Fo=t("Troubleshooting using log files"),Mo=t(" for details."),Ao=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.pl1.disableProblems")],-1),Eo={style:{"text-align":"left"}},Zo=t("Disables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. The default value is "),To=e("code",null,"false",-1),Bo=t(". For more information, see "),qo=t("Enabling and disabling problems in IBM Z Open Editor"),ko=t("."),Ro=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.pl1.includeFileExtensions")],-1),No={style:{"text-align":"left"}},Uo=t("Specifies a list of file name extensions for PL/I include files. For more information, see "),Ho=t("Defining Include file associations"),Vo=t("."),Jo=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.pl1.maximumLineLength")],-1),jo={style:{"text-align":"left"}},Yo=t("Provides a maximum line length for the PL/I editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see "),Wo=t("Setting language-specific maximum line length"),Xo=t("."),Go=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.rexx.disableProblems")],-1),Qo={style:{"text-align":"left"}},$o=t("Disables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. The default value is "),Ko=e("code",null,"false",-1),es=t(". For more information, see "),ts=t("Enabling and disabling problems in IBM Z Open Editor"),os=t("."),ss=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.rexx.maximumLineLength")],-1),ns={style:{"text-align":"left"}},is=t("Provides a maximum line length for the REXX editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see "),ls=t("Setting language-specific maximum line length"),as=t("."),rs=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.server.memoryAllocation")],-1),ds={style:{"text-align":"left"}},cs=t("Specifies the maximum value of the memory that language servers are allowed to allocate. For more information, see section Configuring the Java memory allocation in "),hs=t("Getting started"),us=t("."),_s=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.server.startupOptions")]),e("td",{style:{"text-align":"left"}},"Configure additional startup parameters for Java virtual machines started for running language servers. These might have been provided by tech support for troubleshooting. Leave blank by default.")],-1),fs=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.userbuild.enabled")]),e("td",{style:{"text-align":"left"}},"Enable User Build capabilities that utilize IBM Dependency Based Build. When enabled, you can run a user build to compile and link programs during coding and unit testing simply by right-clicking inside a COBOL, PL/I, or HLASM file.")],-1),ms=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.userbuild.userSettings")],-1),gs={style:{"text-align":"left"}},ps=t("Settings for IBM User Build. See the "),bs={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-setting-up-user-build",target:"_blank",rel:"noopener noreferrer"},ys=t("IBM Documentation"),xs=t(" for details."),ws=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.watsonx.watsonxCodeAssistantForZ.enable")]),e("td",{style:{"text-align":"left"}},"Enables and disables the IBM watsonx Code Assistant for Z feature.")],-1),vs=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.watsonx.watsonxCodeAssistantForZ.authenticationURL")]),e("td",{style:{"text-align":"left"}},"Overrides the IBM Cloud IAM Identity Services URL. Leave it unassigned to use the default service.")],-1),Ss=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.watsonx.watsonxCodeAssistantForZ.URL")]),e("td",{style:{"text-align":"left"}},"Overrides the URL to the IBM watsonx Code Assistant for Z service. Leave it unassigned to use the default service.")],-1),zs=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.watsonx.watsonxCodeAssistantForZ.logLevel")]),e("td",{style:{"text-align":"left"}},"Sets the logging level for IBM watsonx Code Assistant for Z. Technical support might instruct you to change this value for problem analysis.")],-1),Ls=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.watsonx.watsonxCodeAssistantForZ.timeout")]),e("td",{style:{"text-align":"left"}},"Overrides the timeout value in milliseconds for requests sent to IBM watsonx Code Assistant for Z.")],-1),Os=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.welcomePage.show")]),e("td",{style:{"text-align":"left"}},"Show the welcome page on VS Code startup.")],-1),Cs=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.zapp.useDefaultOnlineZappSchema")]),e("td",{style:{"text-align":"left"}},"Z Open Editor comes with the built-in ZAPP JSON schema. It can be used for YAML files using Red Hat's YAML VS Code extension, and for JSON files with the built-in editor. If you encounter issues locating this built-in schema on deployments like Eclipse Che, such as being unable to see syntax errors with the Red Hat YAML extension, enable this option to load the schema from the internet.")],-1),Is=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.zapp.customZappSchemaLocation")]),e("td",{style:{"text-align":"left"}},"When you work offline but have to provide a path to the ZAPP schema yourself, such as in a custom Che deployment, specify a valid HTTP or file URL to the location of the ZAPP JSON schema. If specified, the Use Default Online Zapp Schema option will be ignored.")],-1),Ds=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.zapp.generateZappOnDemand")]),e("td",{style:{"text-align":"left"}},"When you open a COBOL, PL/I, HLASM, or REXX program and none is found in all the open workspaces, a generic ZAPP file is automatically generated. This file will search for include files in all workspaces and folders.")],-1),Ps=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.zapp.variables")]),e("td",{style:{"text-align":"left"}},[t("Use to specify variable names with values that will be substituted in your ZAPP files. To reference a variable defined here in a ZAPP file, write "),e("code",null,"${variable-name}"),t(". For example, define a variable here called "),e("code",null,"HLQ"),t(" with a value that represents your personal high-level qualifier on z/OS MVS. In your ZAPP file, reference the variable in a property group's location entry like this: "),e("code",null,"${HLQ}.COBOL.COPYBOOKs"),t(". Do not use single or double-quote characters for variable names and values. Note that all users need to define all the variables in their user settings that are used by the ZAPP file to avoid errors. You can place these properties in VS Code user and workspace settings.")])],-1),Fs=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.zcodeformat.useDefaultOnlineZCodeFormatSchema")]),e("td",{style:{"text-align":"left"}},"Z Open Editor comes with the built-in zCodeFormat JSON schema. It can be used for YAML files using Red Hat's YAML VS Code extension, and for JSON files with the built-in editor. If you encounter issues locating this built-in schema on deployments like Eclipse Che, such as being unable to see syntax errors with the Red Hat YAML extension, enable this option to load the schema from the internet.")],-1),Ms=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.zcodeformat.customZCodeFormatSchemaLocation")]),e("td",{style:{"text-align":"left"}},"When you work offline but have to provide a path to the zCodeFormat schema yourself, such as in a custom Che deployment, specify a valid HTTP or file URL to the location of the zCodeFormat JSON schema. If specified, the Use Default Online zCodeFormat Schema option will be ignored.")],-1),As=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.zowe")],-1),Es={style:{"text-align":"left"}},Zs=t("The "),Ts=e("code",null,"zopeneditor.zowe",-1),Bs=t(" setting can be used at a user or workspace level. Typically every user specifies these in their user settings using their personal profile names. If defined in workspace settings then it is assumed that all users of this workspace have defined the same standardized profile names on their systems. If set at both levels, the user and workspace level, the workspace level will override the user level."),qs=t("Use "),ks=e("code",null,'"zopeneditor.zowe": {"defaultCliProfile": ""}',-1),Rs=t(" to specify the name of the profile you want to use for IBM Z Open Editor operations. If this is not defined, IBM Z Open Editor follows the precedence rules described in "),Ns=t("Setting up and using RSE profiles in IBM Z Open Editor"),Us=t(" to identify which CLI profile to use."),Hs=c("
            • Use "zopeneditor.zowe": {"defaultSshCliProfile": "<profile_name>"} to specify the name of the Zowe CLI SSH profile used for remote execution of commands on UNIX System Services of your z/OS system. If no valid profile name is provided, the default SSH profile will be used.
            • Use "zopeneditor.zowe": {"defaultRseConversionMappingsFile": "<absolute pathname>"} to specify the path to a valid RSE API mappings file or ZAPP file that contains RSE API mappings. These mappings will be used for Zowe Explorer MVS file content read/write operations for RSE API profiles. Note, that property groups for remote include file resolution and user build will not use this setting, but look for a workspace-local ZAPP file or if not found, a mappings file in the user's .zowe/profiles/rse directory.
            • Use the boolean setting "zopeneditor.zowe": {"listBeforeDownload": "<true-or-false>"} to modify Z Open Editor's behavior when requesting a file from MVS: - When the setting is set to true, the editor will first try to confirm that whether the requested file actually exists by performing a list operation for that file. If the requested file exists, the editor will send another request to download it. If the requested file does not exist, the editor will move on to test the next location listed in the property group. - When the setting is set to false, the editor will directly try to download the file from MVS without checking whether it actually exists. If the response from z/OS is a Not Found error, the editor will move on to the next location listed in the property group. In some cases when using z/OSMF as the protocol, this Not Found error will cause entries in z/OS log files, which you can avoid by specifying the value of the setting to true. However, this extra round-trip to the server to check the existence will have performance impact. Because the logging is not an issue when using the RSE API protocol and because of the performance advantage, the default value for this setting is false.
            • Use the integer setting "zopeneditor.zowe": {"maximumParallelFileDownloads": "<1-to-10>"} to specify how many parallel downloads Z Open Editor should perform when requesting include files from MVS. Downloading several files in parallel can significantly improve performance, especially when you edit programs with many include files. The downside is that some protocols such as z/OSMF will allocate more address spaces for the parallel requests, which causes more resources being used and more logging on the z/OS side. The RSE API protocol does not have that problem because it achieves scalability in other ways that are documented in the RSE documentation. The default value for this setting is 5, and the maximum value is 10. Set it to 1 to disable parallel downloads requesting one include file at the time.
              • ",4),Vs=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zowe.files.temporaryDownloadsFolder.cleanup")]),e("td",{style:{"text-align":"left"}},[t("The "),e("code",null,"zowe.files.temporaryDownloadsFolder.cleanup"),t(' setting is adopted from Zowe Explorer settings to support the use of multiple VS Code windows showing the same files opened via Zowe Explorer so you can see different parts of the same program on two different screens. Note that disabling the cleanup will result in files downloaded from z/OS not being removed when the editor is closed or restarted, so when you open a file via Zowe Explorer you may be viewing an outdated local version. Use the right-click "Pull from Mainframe" command to ensure you are working with the latest files.')])],-1),Js=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.advancedCapabilities.enableRseApiActivationCheck")],-1),js={style:{"text-align":"left"}},Ys=t("The "),Ws=e("code",null,"zopeneditor.advancedCapabilities.enableRseApiActivationCheck",-1),Xs=t(" setting is used to enable advanced capabilities activation using an RSE API server. To learn if you should enable this setting, read the "),Gs=t("documentation for advanced capabilities activation."),Qs=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.cobol.autoPreprocessor")]),e("td",{style:{"text-align":"left"}},[t("The "),e("code",null,"zopeneditor.cobol.autoPreprocessor"),t(" setting is used to specify when the COBOL preprocessor is invoked.")])],-1);function $s(Ks,en){const s=i("RouterLink"),l=i("ExternalLinkIcon");return a(),r(d,null,[_,e("p",null,[f,m,g,o(s,{to:"/Docs/setting_preferences.html"},{default:n(()=>[p]),_:1}),b]),y,e("table",null,[x,e("tbody",null,[e("tr",null,[w,e("td",v,[S,z,L,O,C,I,D,o(s,{to:"/Docs/setting_tabstops.html"},{default:n(()=>[P]),_:1}),F])]),e("tr",null,[M,e("td",A,[E,Z,T,B,q,k,R,o(s,{to:"/Docs/setting_tabstops.html"},{default:n(()=>[N]),_:1}),U])]),e("tr",null,[H,e("td",V,[J,j,Y,W,X,G,Q,o(s,{to:"/Docs/setting_tabstops.html"},{default:n(()=>[$]),_:1}),K])]),e("tr",null,[ee,e("td",te,[oe,se,ne,ie,le,ae,re,o(s,{to:"/Docs/setting_tabstops.html"},{default:n(()=>[de]),_:1}),ce])]),e("tr",null,[he,e("td",ue,[_e,fe,me,ge,pe,be,ye,o(s,{to:"/Docs/setting_tabstops.html"},{default:n(()=>[xe]),_:1}),we])]),e("tr",null,[ve,e("td",Se,[ze,o(s,{to:"/Docs/setting_fileassociations.html"},{default:n(()=>[Le]),_:1}),Oe])]),e("tr",null,[Ce,e("td",Ie,[De,o(s,{to:"/Docs/setting_unreachablecodewarnings.html"},{default:n(()=>[Pe]),_:1}),Fe])]),e("tr",null,[Me,e("td",Ae,[Ee,Ze,Te,o(s,{to:"/Docs/setting_disableproblems.html"},{default:n(()=>[Be]),_:1}),qe])]),e("tr",null,[ke,e("td",Re,[Ne,o(s,{to:"/Docs/setting_fileassociations.html#defining-include-file-associations"},{default:n(()=>[Ue]),_:1}),He])]),e("tr",null,[Ve,e("td",Je,[je,o(s,{to:"/Docs/setting_maximum_line_length.html"},{default:n(()=>[Ye]),_:1}),We])]),Xe,e("tr",null,[Ge,e("td",Qe,[$e,o(s,{to:"/Docs/setting_tabstops.html"},{default:n(()=>[Ke]),_:1}),et])]),e("tr",null,[tt,e("td",ot,[st,o(s,{to:"/Docs/setting_fileassociations.html"},{default:n(()=>[nt]),_:1}),it])]),lt,e("tr",null,[at,e("td",rt,[dt,ct,ht,o(s,{to:"/Docs/setting_disableproblems.html"},{default:n(()=>[ut]),_:1}),_t])]),e("tr",null,[ft,e("td",mt,[gt,pt,bt,o(s,{to:"/Docs/editor_codechanges_hlasm.html#remote-macros"},{default:n(()=>[yt]),_:1}),xt,wt,vt,St,zt])]),e("tr",null,[Lt,e("td",Ot,[Ct,o(s,{to:"/Docs/advanced_custom_macros.html"},{default:n(()=>[It]),_:1}),Dt])]),e("tr",null,[Pt,e("td",Ft,[Mt,o(s,{to:"/Docs/setting_fileassociations.html#defining-include-file-associations"},{default:n(()=>[At]),_:1}),Et])]),Zt,Tt,e("tr",null,[Bt,e("td",qt,[kt,o(s,{to:"/Docs/setting_maximum_line_length.html"},{default:n(()=>[Rt]),_:1}),Nt])]),e("tr",null,[Ut,e("td",Ht,[Vt,Jt,jt,o(s,{to:"/Docs/advanced_custom_macros.html"},{default:n(()=>[Yt]),_:1}),Wt])]),e("tr",null,[Xt,e("td",Gt,[Qt,o(s,{to:"/Docs/setting_tabstops.html"},{default:n(()=>[$t]),_:1}),Kt])]),e("tr",null,[eo,e("td",to,[oo,o(s,{to:"/Docs/editor_codechanges_hlasm.html#remote-macros"},{default:n(()=>[so]),_:1}),no])]),e("tr",null,[io,e("td",lo,[ao,o(s,{to:"/Docs/getting_started.html"},{default:n(()=>[ro]),_:1}),co])]),e("tr",null,[ho,e("td",uo,[_o,o(s,{to:"/Docs/setting_maximum_line_length.html"},{default:n(()=>[fo]),_:1}),mo])]),e("tr",null,[go,e("td",po,[bo,o(s,{to:"/Docs/setting_tabstops.html"},{default:n(()=>[yo]),_:1}),xo])]),e("tr",null,[wo,e("td",vo,[So,zo,Lo,o(s,{to:"/Docs/setting_disableproblems.html"},{default:n(()=>[Oo]),_:1}),Co])]),e("tr",null,[Io,e("td",Do,[Po,o(s,{to:"/Docs/locating_local_client_logs.html"},{default:n(()=>[Fo]),_:1}),Mo])]),e("tr",null,[Ao,e("td",Eo,[Zo,To,Bo,o(s,{to:"/Docs/setting_disableproblems.html"},{default:n(()=>[qo]),_:1}),ko])]),e("tr",null,[Ro,e("td",No,[Uo,o(s,{to:"/Docs/setting_fileassociations.html#defining-include-file-associations"},{default:n(()=>[Ho]),_:1}),Vo])]),e("tr",null,[Jo,e("td",jo,[Yo,o(s,{to:"/Docs/setting_maximum_line_length.html"},{default:n(()=>[Wo]),_:1}),Xo])]),e("tr",null,[Go,e("td",Qo,[$o,Ko,es,o(s,{to:"/Docs/setting_disableproblems.html"},{default:n(()=>[ts]),_:1}),os])]),e("tr",null,[ss,e("td",ns,[is,o(s,{to:"/Docs/setting_maximum_line_length.html"},{default:n(()=>[ls]),_:1}),as])]),e("tr",null,[rs,e("td",ds,[cs,o(s,{to:"/Docs/getting_started.html"},{default:n(()=>[hs]),_:1}),us])]),_s,fs,e("tr",null,[ms,e("td",gs,[ps,e("a",bs,[ys,o(l)]),xs])]),ws,vs,Ss,zs,Ls,Os,Cs,Is,Ds,Ps,Fs,Ms,e("tr",null,[As,e("td",Es,[Zs,Ts,Bs,e("ul",null,[e("li",null,[qs,ks,Rs,o(s,{to:"/Docs/interact_zos_zowe_explorer.html#setting-up-and-using-rse-profiles-in-ibm-z-open-editor"},{default:n(()=>[Ns]),_:1}),Us]),Hs])])]),Vs,e("tr",null,[Js,e("td",js,[Ys,Ws,Xs,o(s,{to:"/Docs/advanced_activation.html"},{default:n(()=>[Gs]),_:1})])]),Qs])])],64)}var sn=h(u,[["render",$s]]);export{sn as default};
+import{r as i,o as a,a as r,b as e,d as o,w as n,F as d,e as t,c}from"./app.daa93c96.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";const u={},_=e("h1",{id:"settings-json-properties",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#settings-json-properties","aria-hidden":"true"},"#"),t(" settings.json properties")],-1),f=t("You can control the characteristics of your environment by setting the following preferences in "),m=e("code",null,"settings.json",-1),g=t(" by using the JSON editor. For more information, see "),p=t("Accessing settings for IBM Z Open Editor"),b=t("."),y=e("h2",{id:"list-of-settings-json-properties",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#list-of-settings-json-properties","aria-hidden":"true"},"#"),t(" List of settings.json properties")],-1),x=e("thead",null,[e("tr",null,[e("th",{style:{"text-align":"left"}},"Property"),e("th",{style:{"text-align":"left"}},"Description")])],-1),w=e("td",{style:{"text-align":"left"}},[e("code",null,"[cobol]")],-1),v={style:{"text-align":"left"}},S=t("Use "),z=e("code",null,'"[cobol]": {"editor.rulers": [',-1),L=e("em",null,"array",-1),O=e("code",null,"]}",-1),I=t(" to set rulers for COBOL in the editor. "),C=e("em",null,"array",-1),P=t(" is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see "),D=t("Setting language specific tab stops and rulers"),F=t("."),M=e("td",{style:{"text-align":"left"}},[e("code",null,"[hlasm]")],-1),A={style:{"text-align":"left"}},E=t("Use "),Z=e("code",null,'"[hlasm]": {"editor.rulers": [',-1),T=e("em",null,"array",-1),B=e("code",null,"]}",-1),q=t(" to set rulers for HLASM in the editor. "),k=e("em",null,"array",-1),R=t(" is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see "),N=t("Setting language specific tab stops and rulers"),U=t("."),H=e("td",{style:{"text-align":"left"}},[e("code",null,"[jcl]")],-1),V={style:{"text-align":"left"}},J=t("Use "),j=e("code",null,'"[jcl]": {"editor.rulers": [',-1),Y=e("em",null,"array",-1),W=e("code",null,"]}",-1),X=t(" to set rulers for JCL in the editor. "),G=e("em",null,"array",-1),Q=t(" is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see "),$=t("Setting language specific tab stops and rulers"),K=t("."),ee=e("td",{style:{"text-align":"left"}},[e("code",null,"[pl1]")],-1),te={style:{"text-align":"left"}},oe=t("Use "),se=e("code",null,'"[pl1]": {"editor.rulers": [',-1),ne=e("em",null,"array",-1),ie=e("code",null,"]}",-1),le=t(" to set rulers for PL/I in the editor. "),ae=e("em",null,"array",-1),re=t(" is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see "),de=t("Setting language specific tab stops and rulers"),ce=t("."),he=e("td",{style:{"text-align":"left"}},[e("code",null,"[rexx]")],-1),ue={style:{"text-align":"left"}},_e=t("Use "),fe=e("code",null,'"[rexx]": {"editor.rulers": [',-1),me=e("em",null,"array",-1),ge=e("code",null,"]}",-1),pe=t(" to set rulers for REXX in the editor. "),be=e("em",null,"array",-1),ye=t(" is an array of numbers representing the column numbers at which you want a ruler to appear. For more information, see "),xe=t("Setting language specific tab stops and rulers"),we=t("."),ve=e("td",{style:{"text-align":"left"}},[e("code",null,"files.associations")],-1),Se={style:{"text-align":"left"}},ze=t("Specifies file names, including data set and member names, that contain certain strings as the appropriate type of file. For detailed usage, see "),Le=t("Setting file associations"),Oe=t("."),Ie=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.cobol.enableUnreachableCodeWarnings")],-1),Ce={style:{"text-align":"left"}},Pe=t("Enables unreachable code warnings in the COBOL programs. For more information, see "),De=t("Enabling and disabling unreachable COBOL code warnings"),Fe=t("."),Me=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.cobol.disableProblems")],-1),Ae={style:{"text-align":"left"}},Ee=t("Disables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. It will also disable unreachable code warnings. The default value is "),Ze=e("code",null,"false",-1),Te=t(". For more information, see "),Be=t("Enabling and disabling problems in IBM Z Open Editor"),qe=t("."),ke=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.cobol.includeFileExtensions")],-1),Re={style:{"text-align":"left"}},Ne=t("Specifies a list of file name extensions for COBOL include files. For more information, see "),Ue=t("Defining Include file associations"),He=t("."),Ve=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.cobol.maximumLineLength")],-1),Je={style:{"text-align":"left"}},je=t("Provides a maximum line length for the COBOL editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see "),Ye=t("Setting language-specific maximum line length"),We=t("."),Xe=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.cobol.sequenceNumbers")]),e("td",{style:{"text-align":"left"}},[t("Choose which columns will have sequence numbers inserted and removed from a file by using the Renumber and Unnumber functions in the COBOL editor. The following values are allowed:"),e("ul",null,[e("li",null,[e("code",null,"zopeneditor.cobol.sequenceNumbers.column1"),t(": Numbering starts at column 1")]),e("li",null,[e("code",null,"zopeneditor.cobol.sequenceNumbers.column73"),t(": Numbering starts at column 73")]),e("li",null,[e("code",null,"zopeneditor.cobol.sequenceNumbers.column1and73"),t(": Numbering starts at column 1 and 73")])])])],-1),Ge=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.cobol.tabstops")],-1),Qe={style:{"text-align":"left"}},$e=t("Adds custom COBOL tab stops in the editor. For more information, see "),Ke=t("Setting language specific tab stops and rulers"),et=t("."),tt=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.datasets")],-1),ot={style:{"text-align":"left"}},st=t("Specifies data set names that should contain COBOL or PL/I programs, copybooks, include files, and JCL. For detailed usage, see "),nt=t("Setting file associations"),it=t("."),lt=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.enforceCaseSensitiveIncludeFileNames")]),e("td",{style:{"text-align":"left"}},[t("Enforce case-sensitive matching of local copybooks and include file names in property groups. Default is "),e("code",null,"false"),t(" to match files with all cases in the path. Set it to true to avoid ambiguous matching on case-insensitive file systems.")])],-1),at=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.disableProblems")],-1),rt={style:{"text-align":"left"}},dt=t("Disables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. The default value is "),ct=e("code",null,"false",-1),ht=t(". For more information, see "),ut=t("Enabling and disabling problems in IBM Z Open Editor"),_t=t("."),ft=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.enableResolvingMacros")],-1),mt={style:{"text-align":"left"}},gt=t("Enables the automatic resolution of "),pt=e("code",null,"SYS1.MACLIB",-1),bt=t(" macro files from MVS using your Zowe Explorer profiles. See the "),yt=t("Remote Macros"),xt=t(" section for more details. The default value is "),wt=e("code",null,"false",-1),vt=t(". To use this feature, you need to set it to "),St=e("code",null,"true",-1),zt=t("."),Lt=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.enableCustomMacrosWarnings")],-1),Ot={style:{"text-align":"left"}},It=t("Enables warnings under all custom macros that can not be found in your HLASM programs. The default value is true. For more information, see "),Ct=t("Custom Macros for HLASM"),Pt=t("."),Dt=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.includeFileExtensions")],-1),Ft={style:{"text-align":"left"}},Mt=t("Specifies a list of file name extensions for HLASM include files. For more information, see "),At=t("Defining Include file associations"),Et=t("."),Zt=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.instructionsFilePath")]),e("td",{style:{"text-align":"left"}},"Allows you to specify a custom HLASM instructions file. Contact IBM Support for questions about the format of such a file or updates to our out of the box file, for example, for a new hardware versions.")],-1),Tt=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.macrosFilePath")]),e("td",{style:{"text-align":"left"}},"Allows you to specify a custom macro definitions file. This option is currently used internally only, but the schema for this format will be provided in a future release so that users can provide their own custom macro references.")],-1),Bt=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.maximumLineLength")],-1),qt={style:{"text-align":"left"}},kt=t("Provides a maximum line length for the HLASM editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see "),Rt=t("Setting language-specific maximum line length"),Nt=t("."),Ut=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.reduceCustomMacroLogging")],-1),Ht={style:{"text-align":"left"}},Vt=t("Reduces the amount of logs that are sent between the HLASM language server and the Z Open Editor client. This increases the performance for scanning and resolving custom macro libraries. The default value is "),Jt=e("code",null,"false",-1),jt=t(". For more information, see "),Yt=t("Custom Macros for HLASM"),Wt=t("."),Xt=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.tabstops")],-1),Gt={style:{"text-align":"left"}},Qt=t("Defines custom HLASM tab stops in the editor. For more information, see "),$t=t("Setting language specific tab stops and rulers"),Kt=t("."),eo=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.hlasm.zosMacrosVersion")],-1),to={style:{"text-align":"left"}},oo=t("Defines the version of z/OS to use for macro definitions. This allows for more accurate results for the hover and code completion features in HLASM. For more information, see "),so=t("Remote Macros"),no=t("."),io=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.JAVA_HOME")],-1),lo={style:{"text-align":"left"}},ao=t("Specifies a different Java for IBM Z Open Editor other than the default of your computer. For more information, see section Selecting the Java installation to use in "),ro=t("Getting started"),co=t("."),ho=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.jcl.maximumLineLength")],-1),uo={style:{"text-align":"left"}},_o=t("Provides a maximum line length for the JCL editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see "),fo=t("Setting language-specific maximum line length"),mo=t("."),go=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.jcl.tabstops")],-1),po={style:{"text-align":"left"}},bo=t("Defines custom JCL tab stops in the editor. For more information, see "),yo=t("Setting language specific tab stops and rulers"),xo=t("."),wo=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.jcl.disableProblems")],-1),vo={style:{"text-align":"left"}},So=t("Disables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. The default value is "),zo=e("code",null,"false",-1),Lo=t(". For more information, see "),Oo=t("Enabling and disabling problems in IBM Z Open Editor"),Io=t("."),Co=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.logger")],-1),Po={style:{"text-align":"left"}},Do=t("Enables a logging output. See "),Fo=t("Troubleshooting using log files"),Mo=t(" for details."),Ao=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.pl1.disableProblems")],-1),Eo={style:{"text-align":"left"}},Zo=t("Disables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. The default value is "),To=e("code",null,"false",-1),Bo=t(". For more information, see "),qo=t("Enabling and disabling problems in IBM Z Open Editor"),ko=t("."),Ro=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.pl1.includeFileExtensions")],-1),No={style:{"text-align":"left"}},Uo=t("Specifies a list of file name extensions for PL/I include files. For more information, see "),Ho=t("Defining Include file associations"),Vo=t("."),Jo=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.pl1.maximumLineLength")],-1),jo={style:{"text-align":"left"}},Yo=t("Provides a maximum line length for the PL/I editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see "),Wo=t("Setting language-specific maximum line length"),Xo=t("."),Go=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.rexx.disableProblems")],-1),Qo={style:{"text-align":"left"}},$o=t("Disables code problems in the Problems view and editor. It will keep other language features such as Outline view available if possible. The default value is "),Ko=e("code",null,"false",-1),es=t(". For more information, see "),ts=t("Enabling and disabling problems in IBM Z Open Editor"),os=t("."),ss=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.rexx.maximumLineLength")],-1),ns={style:{"text-align":"left"}},is=t("Provides a maximum line length for the REXX editor. This setting will allow the editor to truncate all text after the provided column number while saving a document. To disable truncation of characters, set maximum line length to -1. For more information, see "),ls=t("Setting language-specific maximum line length"),as=t("."),rs=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.server.memoryAllocation")],-1),ds={style:{"text-align":"left"}},cs=t("Specifies the maximum value of the memory that language servers are allowed to allocate. For more information, see section Configuring the Java memory allocation in "),hs=t("Getting started"),us=t("."),_s=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.server.startupOptions")]),e("td",{style:{"text-align":"left"}},"Configure additional startup parameters for Java virtual machines started for running language servers. These might have been provided by tech support for troubleshooting. Leave blank by default.")],-1),fs=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.userbuild.enabled")]),e("td",{style:{"text-align":"left"}},"Enable User Build capabilities that utilize IBM Dependency Based Build. When enabled, you can run a user build to compile and link programs during coding and unit testing simply by right-clicking inside a COBOL, PL/I, or HLASM file.")],-1),ms=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.userbuild.userSettings")],-1),gs={style:{"text-align":"left"}},ps=t("Settings for IBM User Build. See the "),bs={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-setting-up-user-build",target:"_blank",rel:"noopener noreferrer"},ys=t("IBM Documentation"),xs=t(" for details."),ws=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.watsonx.watsonxCodeAssistantForZ.enable")]),e("td",{style:{"text-align":"left"}},"Enables and disables the IBM watsonx Code Assistant for Z feature.")],-1),vs=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.watsonx.watsonxCodeAssistantForZ.authenticationURL")]),e("td",{style:{"text-align":"left"}},"Overrides the IBM Cloud IAM Identity Services URL. Leave it unassigned to use the default service.")],-1),Ss=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.watsonx.watsonxCodeAssistantForZ.URL")]),e("td",{style:{"text-align":"left"}},"Overrides the URL to the IBM watsonx Code Assistant for Z service. Leave it unassigned to use the default service.")],-1),zs=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.watsonx.watsonxCodeAssistantForZ.logLevel")]),e("td",{style:{"text-align":"left"}},"Sets the logging level for IBM watsonx Code Assistant for Z. Technical support might instruct you to change this value for problem analysis.")],-1),Ls=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.watsonx.watsonxCodeAssistantForZ.timeout")]),e("td",{style:{"text-align":"left"}},"Overrides the timeout value in milliseconds for requests sent to IBM watsonx Code Assistant for Z.")],-1),Os=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.welcomePage.show")]),e("td",{style:{"text-align":"left"}},"Show the welcome page on VS Code startup.")],-1),Is=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.zapp.useDefaultOnlineZappSchema")]),e("td",{style:{"text-align":"left"}},"Z Open Editor comes with the built-in ZAPP JSON schema. It can be used for YAML files using Red Hat's YAML VS Code extension, and for JSON files with the built-in editor. If you encounter issues locating this built-in schema on deployments like Eclipse Che, such as being unable to see syntax errors with the Red Hat YAML extension, enable this option to load the schema from the internet.")],-1),Cs=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.zapp.customZappSchemaLocation")]),e("td",{style:{"text-align":"left"}},"When you work offline but have to provide a path to the ZAPP schema yourself, such as in a custom Che deployment, specify a valid HTTP or file URL to the location of the ZAPP JSON schema. If specified, the Use Default Online Zapp Schema option will be ignored.")],-1),Ps=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.zapp.generateZappOnDemand")]),e("td",{style:{"text-align":"left"}},"When you open a COBOL, PL/I, HLASM, or REXX program and none is found in all the open workspaces, a generic ZAPP file is automatically generated. This file will search for include files in all workspaces and folders.")],-1),Ds=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.zapp.variables")]),e("td",{style:{"text-align":"left"}},[t("Use to specify variable names with values that will be substituted in your ZAPP files. To reference a variable defined here in a ZAPP file, write "),e("code",null,"${variable-name}"),t(". For example, define a variable here called "),e("code",null,"HLQ"),t(" with a value that represents your personal high-level qualifier on z/OS MVS. In your ZAPP file, reference the variable in a property group's location entry like this: "),e("code",null,"${HLQ}.COBOL.COPYBOOKs"),t(". Do not use single or double-quote characters for variable names and values. Note that all users need to define all the variables in their user settings that are used by the ZAPP file to avoid errors. You can place these properties in VS Code user and workspace settings.")])],-1),Fs=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.zcodeformat.useDefaultOnlineZCodeFormatSchema")]),e("td",{style:{"text-align":"left"}},"Z Open Editor comes with the built-in zCodeFormat JSON schema. It can be used for YAML files using Red Hat's YAML VS Code extension, and for JSON files with the built-in editor. If you encounter issues locating this built-in schema on deployments like Eclipse Che, such as being unable to see syntax errors with the Red Hat YAML extension, enable this option to load the schema from the internet.")],-1),Ms=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.zcodeformat.customZCodeFormatSchemaLocation")]),e("td",{style:{"text-align":"left"}},"When you work offline but have to provide a path to the zCodeFormat schema yourself, such as in a custom Che deployment, specify a valid HTTP or file URL to the location of the zCodeFormat JSON schema. If specified, the Use Default Online zCodeFormat Schema option will be ignored.")],-1),As=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.zowe")],-1),Es={style:{"text-align":"left"}},Zs=t("The "),Ts=e("code",null,"zopeneditor.zowe",-1),Bs=t(" setting can be used at a user or workspace level. Typically every user specifies these in their user settings using their personal profile names. If defined in workspace settings then it is assumed that all users of this workspace have defined the same standardized profile names on their systems. If set at both levels, the user and workspace level, the workspace level will override the user level."),qs=t("Use "),ks=e("code",null,'"zopeneditor.zowe": {"defaultCliProfile": ""}',-1),Rs=t(" to specify the name of the profile you want to use for IBM Z Open Editor operations. If this is not defined, IBM Z Open Editor follows the precedence rules described in "),Ns=t("Setting up and using RSE profiles in IBM Z Open Editor"),Us=t(" to identify which CLI profile to use."),Hs=c("
            • Use "zopeneditor.zowe": {"defaultSshCliProfile": "<profile_name>"} to specify the name of the Zowe CLI SSH profile used for remote execution of commands on UNIX System Services of your z/OS system. If no valid profile name is provided, the default SSH profile will be used.
            • Use "zopeneditor.zowe": {"defaultRseConversionMappingsFile": "<absolute pathname>"} to specify the path to a valid RSE API mappings file or ZAPP file that contains RSE API mappings. These mappings will be used for Zowe Explorer MVS file content read/write operations for RSE API profiles. Note, that property groups for remote include file resolution and user build will not use this setting, but look for a workspace-local ZAPP file or if not found, a mappings file in the user's .zowe/profiles/rse directory.
            • Use the boolean setting "zopeneditor.zowe": {"listBeforeDownload": "<true-or-false>"} to modify Z Open Editor's behavior when requesting a file from MVS: - When the setting is set to true, the editor will first try to confirm that whether the requested file actually exists by performing a list operation for that file. If the requested file exists, the editor will send another request to download it. If the requested file does not exist, the editor will move on to test the next location listed in the property group. - When the setting is set to false, the editor will directly try to download the file from MVS without checking whether it actually exists. If the response from z/OS is a Not Found error, the editor will move on to the next location listed in the property group. In some cases when using z/OSMF as the protocol, this Not Found error will cause entries in z/OS log files, which you can avoid by specifying the value of the setting to true. However, this extra round-trip to the server to check the existence will have performance impact. Because the logging is not an issue when using the RSE API protocol and because of the performance advantage, the default value for this setting is false.
            • Use the integer setting "zopeneditor.zowe": {"maximumParallelFileDownloads": "<1-to-10>"} to specify how many parallel downloads Z Open Editor should perform when requesting include files from MVS. Downloading several files in parallel can significantly improve performance, especially when you edit programs with many include files. The downside is that some protocols such as z/OSMF will allocate more address spaces for the parallel requests, which causes more resources being used and more logging on the z/OS side. The RSE API protocol does not have that problem because it achieves scalability in other ways that are documented in the RSE documentation. The default value for this setting is 5, and the maximum value is 10. Set it to 1 to disable parallel downloads requesting one include file at the time.
              • ",4),Vs=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zowe.files.temporaryDownloadsFolder.cleanup")]),e("td",{style:{"text-align":"left"}},[t("The "),e("code",null,"zowe.files.temporaryDownloadsFolder.cleanup"),t(' setting is adopted from Zowe Explorer settings to support the use of multiple VS Code windows showing the same files opened via Zowe Explorer so you can see different parts of the same program on two different screens. Note that disabling the cleanup will result in files downloaded from z/OS not being removed when the editor is closed or restarted, so when you open a file via Zowe Explorer you may be viewing an outdated local version. Use the right-click "Pull from Mainframe" command to ensure you are working with the latest files.')])],-1),Js=e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.advancedCapabilities.enableRseApiActivationCheck")],-1),js={style:{"text-align":"left"}},Ys=t("The "),Ws=e("code",null,"zopeneditor.advancedCapabilities.enableRseApiActivationCheck",-1),Xs=t(" setting is used to enable advanced capabilities activation using an RSE API server. To learn if you should enable this setting, read the "),Gs=t("documentation for advanced capabilities activation."),Qs=e("tr",null,[e("td",{style:{"text-align":"left"}},[e("code",null,"zopeneditor.autoPreprocessor")]),e("td",{style:{"text-align":"left"}},[t("The "),e("code",null,"zopeneditor.autoPreprocessor"),t(" setting is used to specify when the COBOL or PL/I preprocessor is invoked.")])],-1);function $s(Ks,en){const s=i("RouterLink"),l=i("ExternalLinkIcon");return a(),r(d,null,[_,e("p",null,[f,m,g,o(s,{to:"/Docs/setting_preferences.html"},{default:n(()=>[p]),_:1}),b]),y,e("table",null,[x,e("tbody",null,[e("tr",null,[w,e("td",v,[S,z,L,O,I,C,P,o(s,{to:"/Docs/setting_tabstops.html"},{default:n(()=>[D]),_:1}),F])]),e("tr",null,[M,e("td",A,[E,Z,T,B,q,k,R,o(s,{to:"/Docs/setting_tabstops.html"},{default:n(()=>[N]),_:1}),U])]),e("tr",null,[H,e("td",V,[J,j,Y,W,X,G,Q,o(s,{to:"/Docs/setting_tabstops.html"},{default:n(()=>[$]),_:1}),K])]),e("tr",null,[ee,e("td",te,[oe,se,ne,ie,le,ae,re,o(s,{to:"/Docs/setting_tabstops.html"},{default:n(()=>[de]),_:1}),ce])]),e("tr",null,[he,e("td",ue,[_e,fe,me,ge,pe,be,ye,o(s,{to:"/Docs/setting_tabstops.html"},{default:n(()=>[xe]),_:1}),we])]),e("tr",null,[ve,e("td",Se,[ze,o(s,{to:"/Docs/setting_fileassociations.html"},{default:n(()=>[Le]),_:1}),Oe])]),e("tr",null,[Ie,e("td",Ce,[Pe,o(s,{to:"/Docs/setting_unreachablecodewarnings.html"},{default:n(()=>[De]),_:1}),Fe])]),e("tr",null,[Me,e("td",Ae,[Ee,Ze,Te,o(s,{to:"/Docs/setting_disableproblems.html"},{default:n(()=>[Be]),_:1}),qe])]),e("tr",null,[ke,e("td",Re,[Ne,o(s,{to:"/Docs/setting_fileassociations.html#defining-include-file-associations"},{default:n(()=>[Ue]),_:1}),He])]),e("tr",null,[Ve,e("td",Je,[je,o(s,{to:"/Docs/setting_maximum_line_length.html"},{default:n(()=>[Ye]),_:1}),We])]),Xe,e("tr",null,[Ge,e("td",Qe,[$e,o(s,{to:"/Docs/setting_tabstops.html"},{default:n(()=>[Ke]),_:1}),et])]),e("tr",null,[tt,e("td",ot,[st,o(s,{to:"/Docs/setting_fileassociations.html"},{default:n(()=>[nt]),_:1}),it])]),lt,e("tr",null,[at,e("td",rt,[dt,ct,ht,o(s,{to:"/Docs/setting_disableproblems.html"},{default:n(()=>[ut]),_:1}),_t])]),e("tr",null,[ft,e("td",mt,[gt,pt,bt,o(s,{to:"/Docs/editor_codechanges_hlasm.html#remote-macros"},{default:n(()=>[yt]),_:1}),xt,wt,vt,St,zt])]),e("tr",null,[Lt,e("td",Ot,[It,o(s,{to:"/Docs/advanced_custom_macros.html"},{default:n(()=>[Ct]),_:1}),Pt])]),e("tr",null,[Dt,e("td",Ft,[Mt,o(s,{to:"/Docs/setting_fileassociations.html#defining-include-file-associations"},{default:n(()=>[At]),_:1}),Et])]),Zt,Tt,e("tr",null,[Bt,e("td",qt,[kt,o(s,{to:"/Docs/setting_maximum_line_length.html"},{default:n(()=>[Rt]),_:1}),Nt])]),e("tr",null,[Ut,e("td",Ht,[Vt,Jt,jt,o(s,{to:"/Docs/advanced_custom_macros.html"},{default:n(()=>[Yt]),_:1}),Wt])]),e("tr",null,[Xt,e("td",Gt,[Qt,o(s,{to:"/Docs/setting_tabstops.html"},{default:n(()=>[$t]),_:1}),Kt])]),e("tr",null,[eo,e("td",to,[oo,o(s,{to:"/Docs/editor_codechanges_hlasm.html#remote-macros"},{default:n(()=>[so]),_:1}),no])]),e("tr",null,[io,e("td",lo,[ao,o(s,{to:"/Docs/getting_started.html"},{default:n(()=>[ro]),_:1}),co])]),e("tr",null,[ho,e("td",uo,[_o,o(s,{to:"/Docs/setting_maximum_line_length.html"},{default:n(()=>[fo]),_:1}),mo])]),e("tr",null,[go,e("td",po,[bo,o(s,{to:"/Docs/setting_tabstops.html"},{default:n(()=>[yo]),_:1}),xo])]),e("tr",null,[wo,e("td",vo,[So,zo,Lo,o(s,{to:"/Docs/setting_disableproblems.html"},{default:n(()=>[Oo]),_:1}),Io])]),e("tr",null,[Co,e("td",Po,[Do,o(s,{to:"/Docs/locating_local_client_logs.html"},{default:n(()=>[Fo]),_:1}),Mo])]),e("tr",null,[Ao,e("td",Eo,[Zo,To,Bo,o(s,{to:"/Docs/setting_disableproblems.html"},{default:n(()=>[qo]),_:1}),ko])]),e("tr",null,[Ro,e("td",No,[Uo,o(s,{to:"/Docs/setting_fileassociations.html#defining-include-file-associations"},{default:n(()=>[Ho]),_:1}),Vo])]),e("tr",null,[Jo,e("td",jo,[Yo,o(s,{to:"/Docs/setting_maximum_line_length.html"},{default:n(()=>[Wo]),_:1}),Xo])]),e("tr",null,[Go,e("td",Qo,[$o,Ko,es,o(s,{to:"/Docs/setting_disableproblems.html"},{default:n(()=>[ts]),_:1}),os])]),e("tr",null,[ss,e("td",ns,[is,o(s,{to:"/Docs/setting_maximum_line_length.html"},{default:n(()=>[ls]),_:1}),as])]),e("tr",null,[rs,e("td",ds,[cs,o(s,{to:"/Docs/getting_started.html"},{default:n(()=>[hs]),_:1}),us])]),_s,fs,e("tr",null,[ms,e("td",gs,[ps,e("a",bs,[ys,o(l)]),xs])]),ws,vs,Ss,zs,Ls,Os,Is,Cs,Ps,Ds,Fs,Ms,e("tr",null,[As,e("td",Es,[Zs,Ts,Bs,e("ul",null,[e("li",null,[qs,ks,Rs,o(s,{to:"/Docs/interact_zos_zowe_explorer.html#setting-up-and-using-rse-profiles-in-ibm-z-open-editor"},{default:n(()=>[Ns]),_:1}),Us]),Hs])])]),Vs,e("tr",null,[Js,e("td",js,[Ys,Ws,Xs,o(s,{to:"/Docs/advanced_activation.html"},{default:n(()=>[Gs]),_:1})])]),Qs])])],64)}var sn=h(u,[["render",$s]]);export{sn as default};
diff --git a/assets/setup_integration.html.b808ca31.js b/assets/setup_integration.html.5653902f.js
similarity index 99%
rename from assets/setup_integration.html.b808ca31.js
rename to assets/setup_integration.html.5653902f.js
index adb184c2d..190f47176 100644
--- a/assets/setup_integration.html.b808ca31.js
+++ b/assets/setup_integration.html.5653902f.js
@@ -1,4 +1,4 @@
-import{r as l,o as r,a as d,b as o,d as n,w as i,F as c,e,c as a}from"./app.f6cb3ed9.js";import{_ as p}from"./plugin-vue_export-helper.21dcd24c.js";const h={},u=o("h1",{id:"setting-up-integrations-to-interact-with-z-os",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#setting-up-integrations-to-interact-with-z-os","aria-hidden":"true"},"#"),e(" Setting up integrations to interact with z/OS")],-1),g=e("You can use IBM Z Open Editor on your computer without connecting to a z/OS system and download files manually by using an FTP command or similar method. However, you can augment the capabilities of IBM Z Open Editor and enjoy a seamless integration of z/OS with IBM Remote System Explorer API (RSE API) or the "),m={href:"https://zowe.org/home/",target:"_blank",rel:"noopener noreferrer"},f=e("Zowe"),b=e(" open source project. The Zowe project provides great tools that work perfectly with the IBM Z Open Editor."),_=e("Note, that with Zowe Explorer 2.0 and Z Open Editor 2.0.2 some changes were introduced to the way this integration is configured that might require some migration from older versions. See the "),w=e("Getting started with Zowe Explorer v2.0"),I=e(" for an overview."),v=a("
              When using IBM Z Open Editor, you can choose how to interact with z/OS with regard to the following aspects:
              • Use RSE API or the Zowe default z/OSMF as the host component
              • Use the command line or graphical interface to interact with z/OS
              Next, you can use the following client-side tools based on your decision:
              Available host componentTo use command line, install...To use graphical interface, install...
              RSE API
              • Zowe CLI, and
              • IBM RSE API Plug-in for Zowe CLI
              		Zowe Explorer
              z/OSMFZowe CLIZowe Explorer
              Detailed information about these tools is as follows:
              ",5),z=e("IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in) enables you to interact with z/OS remotely via command line by using RSE API instead of using the Zowe default z/OSMF. See "),S=o("a",{href:"#installing-ibm-rse-api-plug-in-for-zowe-cli"},"Installing IBM RSE API Plug-in for Zowe CLI",-1),E=e(" to get started. To use RSE API on your client, see "),y=e("Using RSE API in Zowe Explorer"),q=e(" and "),C=e("Using RSE CLI plug-in commands"),L=e("."),x=e("Zowe CLI enables you to interact with z/OS remotely via command line. After installation, as described in "),Z=o("a",{href:"#installing-zowe-cli"},"Installing Zowe CLI",-1),k=e(", you must "),R=e("create a Zowe CLI z/OSMF user profile"),M=e(" that stores your personal connection information. To use Zowe CLI with IBM Z Open Editor, see "),A=e("Using Zowe CLI z/OSMF commands"),P=e("."),O=e("The Zowe Explorer VS Code extension (Zowe Explorer) provides you with graphical views to explore MVS, z/OS UNIX System Services, and JES remotely. When you install IBM Z Open Editor from the VS Code Marketplace into your VS Code, the latest version of the Zowe Explorer VS Code extension is automatically co-installed. For more information about its capabilities and usage, see "),B={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},j=e("Zowe Explorer in the VS Code Marketplace"),T=e(" and "),N={href:"https://docs.zowe.org/stable/user-guide/ze-install.html",target:"_blank",rel:"noopener noreferrer"},V=e("Zowe Docs"),D=e(". To use Zowe Explorer with IBM Z Open Editor, see "),F=e("Using the Zowe Explorer views"),U=e("."),J=o("h2",{id:"installing-zowe-cli",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#installing-zowe-cli","aria-hidden":"true"},"#"),e(" Installing Zowe CLI")],-1),W=o("p",null,"The prerequisites for installing Zowe CLI are as follows:",-1),Y=e("Client: Install "),G={href:"https://nodejs.org/",target:"_blank",rel:"noopener noreferrer"},H=e("Node.js"),X=e(" version 14, or a later version"),K=o("li",null,[e("Host (select one or both): "),o("ul",null,[o("li",null,"Configure z/OSMF if you plan to use Zowe CLI without RSE CLI plug-in"),o("li",null,[e("Install and configure "),o("a",{href:"#installing-the-requisite-ibm-rse-api-z-os-host-component"},"IBM Remote System Explorer API"),e(" if you plan to use Zowe CLI along with RSE CLI plug-in to extend Zowe CLI")])])],-1),$=o("p",null,"You can install Zowe CLI using one of the methods below:",-1),Q=e("Follow the Zowe documentation on "),ee={href:"https://docs.zowe.org/stable/user-guide/cli-installcli.html",target:"_blank",rel:"noopener noreferrer"},oe=e("Installing Zowe CLI"),ne=e(" to install Zowe CLI from the "),te={href:"https://www.zowe.org/download.html",target:"_blank",rel:"noopener noreferrer"},se=e("Zowe.org"),ie=e(" website or the "),ae={href:"https://www.npmjs.com/package/@zowe/cli",target:"_blank",rel:"noopener noreferrer"},le=e("npmjs.com"),re=e(" npm package registry."),de=e("Alternatively, you can get a certified IBM Zowe distribution from "),ce={href:"https://ibm.github.io/mainframe-downloads/downloads.html",target:"_blank",rel:"noopener noreferrer"},pe=e("IBM Mainframe DEV"),he=e(". You can also purchase technical support for Zowe from IBM for this distribution."),ue=a('
               Installing IBM RSE API Plug-in for Zowe CLI
               Prerequisites
              Before installing IBM RSE API Plug-in for Zowe CLI on your development machine, you must install Zowe CLI 7.26.1 or later. For more information about installing Zowe CLI, see Installing Zowe CLI.
               Installing the requisite IBM RSE API z/OS host component
              Confirm with your system administrator that the following host components are installed and configured on the z/OS host system:
              • The host component of z/OS Explorer 3.1.1 or 3.2, which is the prerequisite of the RSE API host component.
              • The RSE API host component, which provides a collection of REST APIs that allow a client to work with various components on the z/OS host system, including MVS data sets, z/OS UNIX files and commands, JES jobs, and more.
              ',6),ge=e("For information about installing and configuring the RSE API host component, see "),me={href:"https://www.ibm.com/docs/en/explorer-for-zos/3.3?topic=api-host-configuration-guide",target:"_blank",rel:"noopener noreferrer"},fe=e("RSE API documentation"),be=e("."),_e=o("p",null,[o("strong",null,"Note:"),e(" Even if your system administrator has previously installed RSE on your z/OS, an update is needed to get the capabilities described here.")],-1),we=o("h3",{id:"installing-the-ibm-rse-api-plug-in-for-zowe-cli",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#installing-the-ibm-rse-api-plug-in-for-zowe-cli","aria-hidden":"true"},"#"),e(" Installing the IBM RSE API Plug-in for Zowe CLI")],-1),Ie=o("p",null,"After installing and configuring the prerequisites and the host component, follow these steps to install the RSE CLI plug-in. You can choose to download the plug-in from",-1),ve=o("ul",null,[o("li",null,"IBM as a code-signed archive file for local and even air-gapped installations, i.e. not requiring an internet connection to public domains."),o("li",null,"a public repository at npmjs.com for a more convenient online installation. This repository is the same from which you might have installed Zowe CLI following instructions from the Zowe docs.")],-1),ze=o("h4",{id:"option-1-download-install-package-from-ibm",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#option-1-download-install-package-from-ibm","aria-hidden":"true"},"#"),e(" Option 1: Download install package from IBM")],-1),Se=e("Navigate to the "),Ee={href:"https://ibm.github.io/mainframe-downloads/downloads.html",target:"_blank",rel:"noopener noreferrer"},ye=e("Mainframe DEV"),qe=e(" website."),Ce=a(`
            • Click More info on the IBM Wazi Developer for Red Hat CodeReady Workspaces tab.
            • In the Code row, click VSCode.
            • You are then redirected to the Software License Agreement page. Review the License Agreement and click I Agree. You will be prompted to save or open a compressed .zip file in your browser.
            • Save the compressed .zip file to your workstation.
            • Extract the compressed .zip file on your workstation. You will find various files in the archive, including 2 different RSE API Plugin for Zowe CLI .tgz files, ibm-rse-api-for-zowe-cli-v.r.m.tgz and ibm-rse-api-for-zowe-cli-airgap-v.r.m.tgz. The ibm-rse-api-for-zowe-cli-airgap-v.r.m.tgz package has all dependencies included in the bundle for environments without network access.
            • Optionally, follow the instructions in the included README.txt file to verify the code signatures to ensure the files were signed against a trusted IBM certificate.
            • Install the desired RSE CLI plug-in variant by entering the following command in the terminal:
              zowe plugins install path/to/download/ibm-rse-api-for-zowe-cli-pkg.tgz
+import{r as l,o as r,a as d,b as o,d as n,w as i,F as c,e,c as a}from"./app.daa93c96.js";import{_ as p}from"./plugin-vue_export-helper.21dcd24c.js";const h={},u=o("h1",{id:"setting-up-integrations-to-interact-with-z-os",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#setting-up-integrations-to-interact-with-z-os","aria-hidden":"true"},"#"),e(" Setting up integrations to interact with z/OS")],-1),g=e("You can use IBM Z Open Editor on your computer without connecting to a z/OS system and download files manually by using an FTP command or similar method. However, you can augment the capabilities of IBM Z Open Editor and enjoy a seamless integration of z/OS with IBM Remote System Explorer API (RSE API) or the "),m={href:"https://zowe.org/home/",target:"_blank",rel:"noopener noreferrer"},f=e("Zowe"),b=e(" open source project. The Zowe project provides great tools that work perfectly with the IBM Z Open Editor."),_=e("Note, that with Zowe Explorer 2.0 and Z Open Editor 2.0.2 some changes were introduced to the way this integration is configured that might require some migration from older versions. See the "),w=e("Getting started with Zowe Explorer v2.0"),I=e(" for an overview."),v=a("
              When using IBM Z Open Editor, you can choose how to interact with z/OS with regard to the following aspects:
              • Use RSE API or the Zowe default z/OSMF as the host component
              • Use the command line or graphical interface to interact with z/OS
              Next, you can use the following client-side tools based on your decision:
              Available host componentTo use command line, install...To use graphical interface, install...
              RSE API
              • Zowe CLI, and
              • IBM RSE API Plug-in for Zowe CLI
              		Zowe Explorer
              z/OSMFZowe CLIZowe Explorer
              Detailed information about these tools is as follows:
              ",5),z=e("IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in) enables you to interact with z/OS remotely via command line by using RSE API instead of using the Zowe default z/OSMF. See "),S=o("a",{href:"#installing-ibm-rse-api-plug-in-for-zowe-cli"},"Installing IBM RSE API Plug-in for Zowe CLI",-1),E=e(" to get started. To use RSE API on your client, see "),y=e("Using RSE API in Zowe Explorer"),q=e(" and "),C=e("Using RSE CLI plug-in commands"),L=e("."),x=e("Zowe CLI enables you to interact with z/OS remotely via command line. After installation, as described in "),Z=o("a",{href:"#installing-zowe-cli"},"Installing Zowe CLI",-1),k=e(", you must "),R=e("create a Zowe CLI z/OSMF user profile"),M=e(" that stores your personal connection information. To use Zowe CLI with IBM Z Open Editor, see "),A=e("Using Zowe CLI z/OSMF commands"),P=e("."),O=e("The Zowe Explorer VS Code extension (Zowe Explorer) provides you with graphical views to explore MVS, z/OS UNIX System Services, and JES remotely. When you install IBM Z Open Editor from the VS Code Marketplace into your VS Code, the latest version of the Zowe Explorer VS Code extension is automatically co-installed. For more information about its capabilities and usage, see "),B={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},j=e("Zowe Explorer in the VS Code Marketplace"),T=e(" and "),N={href:"https://docs.zowe.org/stable/user-guide/ze-install.html",target:"_blank",rel:"noopener noreferrer"},V=e("Zowe Docs"),D=e(". To use Zowe Explorer with IBM Z Open Editor, see "),F=e("Using the Zowe Explorer views"),U=e("."),J=o("h2",{id:"installing-zowe-cli",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#installing-zowe-cli","aria-hidden":"true"},"#"),e(" Installing Zowe CLI")],-1),W=o("p",null,"The prerequisites for installing Zowe CLI are as follows:",-1),Y=e("Client: Install "),G={href:"https://nodejs.org/",target:"_blank",rel:"noopener noreferrer"},H=e("Node.js"),X=e(" version 14, or a later version"),K=o("li",null,[e("Host (select one or both): "),o("ul",null,[o("li",null,"Configure z/OSMF if you plan to use Zowe CLI without RSE CLI plug-in"),o("li",null,[e("Install and configure "),o("a",{href:"#installing-the-requisite-ibm-rse-api-z-os-host-component"},"IBM Remote System Explorer API"),e(" if you plan to use Zowe CLI along with RSE CLI plug-in to extend Zowe CLI")])])],-1),$=o("p",null,"You can install Zowe CLI using one of the methods below:",-1),Q=e("Follow the Zowe documentation on "),ee={href:"https://docs.zowe.org/stable/user-guide/cli-installcli.html",target:"_blank",rel:"noopener noreferrer"},oe=e("Installing Zowe CLI"),ne=e(" to install Zowe CLI from the "),te={href:"https://www.zowe.org/download.html",target:"_blank",rel:"noopener noreferrer"},se=e("Zowe.org"),ie=e(" website or the "),ae={href:"https://www.npmjs.com/package/@zowe/cli",target:"_blank",rel:"noopener noreferrer"},le=e("npmjs.com"),re=e(" npm package registry."),de=e("Alternatively, you can get a certified IBM Zowe distribution from "),ce={href:"https://ibm.github.io/mainframe-downloads/downloads.html",target:"_blank",rel:"noopener noreferrer"},pe=e("IBM Mainframe DEV"),he=e(". You can also purchase technical support for Zowe from IBM for this distribution."),ue=a('
               Installing IBM RSE API Plug-in for Zowe CLI
               Prerequisites
              Before installing IBM RSE API Plug-in for Zowe CLI on your development machine, you must install Zowe CLI 7.26.1 or later. For more information about installing Zowe CLI, see Installing Zowe CLI.
               Installing the requisite IBM RSE API z/OS host component
              Confirm with your system administrator that the following host components are installed and configured on the z/OS host system:
              • The host component of z/OS Explorer 3.1.1 or 3.2, which is the prerequisite of the RSE API host component.
              • The RSE API host component, which provides a collection of REST APIs that allow a client to work with various components on the z/OS host system, including MVS data sets, z/OS UNIX files and commands, JES jobs, and more.
              ',6),ge=e("For information about installing and configuring the RSE API host component, see "),me={href:"https://www.ibm.com/docs/en/explorer-for-zos/3.3?topic=api-host-configuration-guide",target:"_blank",rel:"noopener noreferrer"},fe=e("RSE API documentation"),be=e("."),_e=o("p",null,[o("strong",null,"Note:"),e(" Even if your system administrator has previously installed RSE on your z/OS, an update is needed to get the capabilities described here.")],-1),we=o("h3",{id:"installing-the-ibm-rse-api-plug-in-for-zowe-cli",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#installing-the-ibm-rse-api-plug-in-for-zowe-cli","aria-hidden":"true"},"#"),e(" Installing the IBM RSE API Plug-in for Zowe CLI")],-1),Ie=o("p",null,"After installing and configuring the prerequisites and the host component, follow these steps to install the RSE CLI plug-in. You can choose to download the plug-in from",-1),ve=o("ul",null,[o("li",null,"IBM as a code-signed archive file for local and even air-gapped installations, i.e. not requiring an internet connection to public domains."),o("li",null,"a public repository at npmjs.com for a more convenient online installation. This repository is the same from which you might have installed Zowe CLI following instructions from the Zowe docs.")],-1),ze=o("h4",{id:"option-1-download-install-package-from-ibm",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#option-1-download-install-package-from-ibm","aria-hidden":"true"},"#"),e(" Option 1: Download install package from IBM")],-1),Se=e("Navigate to the "),Ee={href:"https://ibm.github.io/mainframe-downloads/downloads.html",target:"_blank",rel:"noopener noreferrer"},ye=e("Mainframe DEV"),qe=e(" website."),Ce=a(`
            • Click More info on the IBM Wazi Developer for Red Hat CodeReady Workspaces tab.
            • In the Code row, click VSCode.
            • You are then redirected to the Software License Agreement page. Review the License Agreement and click I Agree. You will be prompted to save or open a compressed .zip file in your browser.
            • Save the compressed .zip file to your workstation.
            • Extract the compressed .zip file on your workstation. You will find various files in the archive, including 2 different RSE API Plugin for Zowe CLI .tgz files, ibm-rse-api-for-zowe-cli-v.r.m.tgz and ibm-rse-api-for-zowe-cli-airgap-v.r.m.tgz. The ibm-rse-api-for-zowe-cli-airgap-v.r.m.tgz package has all dependencies included in the bundle for environments without network access.
            • Optionally, follow the instructions in the included README.txt file to verify the code signatures to ensure the files were signed against a trusted IBM certificate.
            • Install the desired RSE CLI plug-in variant by entering the following command in the terminal:
              zowe plugins install path/to/download/ibm-rse-api-for-zowe-cli-pkg.tgz
 
              where path/to/download/ibm-rse-api-for-zowe-cli-pkg.tgz should be defined with your own file path to install the package.
              • `,7),Le=a(`
               Option 2: Install from npmjs.com
              1. Install the RSE CLI plug-in by entering the following command in the terminal:
                zowe plugins install @ibm/rse-api-for-zowe-cli
 
               Validating installation
              If the installation was successful, you can see the following message printed in the terminal:
              Installed plugin name = '@ibm/ibm-rse-api-for-zowe-cli'
 
diff --git a/assets/sharing_team_configuration_files.html.d1ee5fad.js b/assets/sharing_team_configuration_files.html.7464eef7.js
similarity index 97%
rename from assets/sharing_team_configuration_files.html.d1ee5fad.js
rename to assets/sharing_team_configuration_files.html.7464eef7.js
index 59e00bdbb..b2df52059 100644
--- a/assets/sharing_team_configuration_files.html.d1ee5fad.js
+++ b/assets/sharing_team_configuration_files.html.7464eef7.js
@@ -1 +1 @@
-import{r as a,o as n,a as r,b as o,d as s,F as c,c as t,e}from"./app.f6cb3ed9.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";const d={},h=t('
               Sharing team configuration files
              Team configuration files can be shared with others using a git project. For faster setup, a team lead can include a team configuration file with connection details in the code repository without any secure values. Each developer would enter their own secure values once they start using profiles. A team configuration file needs to be at the top level of project so that it can be read correctly in VS Code. An important thing to note is in order for the configuration profile to work properly the zowe.schema.json file needs to be included in the same folder as the team configuration profile.
              Take a look at the location where your team configuration file resides.
              • If you created a global zowe.config.json, it was placed in ~/.zowe folder.
              • If you created a user configuration file scoped to 1 repository zowe.config.user.json, it was placed inside that repository.
              In both cases, a zowe.schema.json file should have been automatically created and placed in the same folder. If the schema file is missing, team configuration files will not work. The schema file has definitions of the supported profile attributes. If you add an extender, such as RSE CLI plug-in, the extender will update the schema file to support new profile types. Therefore, make sure to share both the team configuration file and the zowe.schema.json file.
              ',5),f=e("For more information about methods for sharing team configuration files, see "),u={href:"https://docs.zowe.org/stable/user-guide/cli-using-sharing-team-config-files/",target:"_blank",rel:"noopener noreferrer"},p=e("Zowe documentation"),m=e("."),g=t('
               Troubleshooting tips
              You might run into situation wherethe zowe.schema.json file is not automatically updated by the extender, and extender profiles are not working. You can check by opening the schema file and looking for your extender defintions.
              • Use zowe config update-schemas to manually update the schema.
              • Use zowe config update-schemas --help for more options.
              If your schema file is missing, the easiest solution is to re-create the team configuration file by using Zowe Explorer or Zowe CLI, and then the schema file will be automatically created in the same location.
              ',4);function w(_,b){const i=a("ExternalLinkIcon");return n(),r(c,null,[h,o("p",null,[f,o("a",u,[p,s(i)]),m]),g],64)}var k=l(d,[["render",w]]);export{k as default};
+import{r as a,o as n,a as r,b as o,d as s,F as c,c as t,e}from"./app.daa93c96.js";import{_ as l}from"./plugin-vue_export-helper.21dcd24c.js";const d={},h=t('
               Sharing team configuration files
              Team configuration files can be shared with others using a git project. For faster setup, a team lead can include a team configuration file with connection details in the code repository without any secure values. Each developer would enter their own secure values once they start using profiles. A team configuration file needs to be at the top level of project so that it can be read correctly in VS Code. An important thing to note is in order for the configuration profile to work properly the zowe.schema.json file needs to be included in the same folder as the team configuration profile.
              Take a look at the location where your team configuration file resides.
              • If you created a global zowe.config.json, it was placed in ~/.zowe folder.
              • If you created a user configuration file scoped to 1 repository zowe.config.user.json, it was placed inside that repository.
              In both cases, a zowe.schema.json file should have been automatically created and placed in the same folder. If the schema file is missing, team configuration files will not work. The schema file has definitions of the supported profile attributes. If you add an extender, such as RSE CLI plug-in, the extender will update the schema file to support new profile types. Therefore, make sure to share both the team configuration file and the zowe.schema.json file.
              ',5),f=e("For more information about methods for sharing team configuration files, see "),u={href:"https://docs.zowe.org/stable/user-guide/cli-using-sharing-team-config-files/",target:"_blank",rel:"noopener noreferrer"},p=e("Zowe documentation"),m=e("."),g=t('
               Troubleshooting tips
              You might run into situation wherethe zowe.schema.json file is not automatically updated by the extender, and extender profiles are not working. You can check by opening the schema file and looking for your extender defintions.
              • Use zowe config update-schemas to manually update the schema.
              • Use zowe config update-schemas --help for more options.
              If your schema file is missing, the easiest solution is to re-create the team configuration file by using Zowe Explorer or Zowe CLI, and then the schema file will be automatically created in the same location.
              ',4);function w(_,b){const i=a("ExternalLinkIcon");return n(),r(c,null,[h,o("p",null,[f,o("a",u,[p,s(i)]),m]),g],64)}var k=l(d,[["render",w]]);export{k as default};
diff --git a/assets/sharingfiles.html.2003b9d7.js b/assets/sharingfiles.html.b4e52542.js
similarity index 96%
rename from assets/sharingfiles.html.2003b9d7.js
rename to assets/sharingfiles.html.b4e52542.js
index 5b0e13240..1bc850fe3 100644
--- a/assets/sharingfiles.html.2003b9d7.js
+++ b/assets/sharingfiles.html.b4e52542.js
@@ -1,4 +1,4 @@
-import{c as e}from"./app.f6cb3ed9.js";import{_ as s}from"./plugin-vue_export-helper.21dcd24c.js";const n={},t=e(`
               Sharing files between VS Code extensions
              In order to make use of files edited by the Zowe Explorer VS Code extension, a preference should be set specifying a local temp folder path. This will allow for remote files edited via the Zowe Explorer VS Code extension to be used by other installed extensions. For example, if this setting is specified, updates made to files such as copybooks, will automatically resolve with the up-to-date content.
              "Zowe-Temp-Folder-Location": {
+import{c as e}from"./app.daa93c96.js";import{_ as s}from"./plugin-vue_export-helper.21dcd24c.js";const n={},t=e(`
               Sharing files between VS Code extensions
              In order to make use of files edited by the Zowe Explorer VS Code extension, a preference should be set specifying a local temp folder path. This will allow for remote files edited via the Zowe Explorer VS Code extension to be used by other installed extensions. For example, if this setting is specified, updates made to files such as copybooks, will automatically resolve with the up-to-date content.
              "Zowe-Temp-Folder-Location": {
   "folderPath": "/path/to/local/directory"
 }
 
              Using this setting, you can navigate to the path specified, and see a downloaded copy of all remote files edited via the Zowe VS Code extension.
              Note: All files temp are deleted on startup and shutdown.
              `,5);function o(a,i){return t}var p=s(n,[["render",o]]);export{p as default};
diff --git a/assets/shortcut.html.d940e3c7.js b/assets/shortcut.html.6659b779.js
similarity index 96%
rename from assets/shortcut.html.d940e3c7.js
rename to assets/shortcut.html.6659b779.js
index 7a712b38a..7fbc05679 100644
--- a/assets/shortcut.html.d940e3c7.js
+++ b/assets/shortcut.html.6659b779.js
@@ -1 +1 @@
-import{c as t}from"./app.f6cb3ed9.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const e={},r=t('
               Keyboard shortcuts reference
              DescriptionWindowsMac
              Search for identifiers within the Outline view and go to symbolCtrl+Shift+OCmd+Shift+O
              Show the list of available code completionCtrl+SpaceCtrl+Space
              Open copybook/include files in a separate editorCtrl+ClickCmd+Click
              Change all occurrencesCtrl+F2Cmd+F2
              Find all referencesAlt+Shift+F12Option+Shift+F12
              Peek referencesShift+F12Shift+F12
              Go to definitionF12F12
              Peek definitionAlt+F12Option+F12
              Rename symbolsF2F2
              UndoCtrl+ZCmd+Z
              RedoCtrl+Shift+ZCmd+Shift+Z
              Open the VS Code command paletteCtrl+Shift+PCtrl+Shift+P
              Open the Problems viewCtrl+Shift+MCmd+Shift+M
              Open the Git viewCtrl+Shift+GCtrl+Shift+G
              Open the Terminal windowCtrl+Back quote1Ctrl+Back quote1
              Note:
              1. The back quote key is labeled as ` on your keyboard.
              ',4);function i(o,a){return r}var n=d(e,[["render",i]]);export{n as default};
+import{c as t}from"./app.daa93c96.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const e={},r=t('
               Keyboard shortcuts reference
              DescriptionWindowsMac
              Search for identifiers within the Outline view and go to symbolCtrl+Shift+OCmd+Shift+O
              Show the list of available code completionCtrl+SpaceCtrl+Space
              Open copybook/include files in a separate editorCtrl+ClickCmd+Click
              Change all occurrencesCtrl+F2Cmd+F2
              Find all referencesAlt+Shift+F12Option+Shift+F12
              Peek referencesShift+F12Shift+F12
              Go to definitionF12F12
              Peek definitionAlt+F12Option+F12
              Rename symbolsF2F2
              UndoCtrl+ZCmd+Z
              RedoCtrl+Shift+ZCmd+Shift+Z
              Open the VS Code command paletteCtrl+Shift+PCtrl+Shift+P
              Open the Problems viewCtrl+Shift+MCmd+Shift+M
              Open the Git viewCtrl+Shift+GCtrl+Shift+G
              Open the Terminal windowCtrl+Back quote1Ctrl+Back quote1
              Note:
              1. The back quote key is labeled as ` on your keyboard.
              ',4);function i(o,a){return r}var n=d(e,[["render",i]]);export{n as default};
diff --git a/assets/snippets.html.a3e40b12.js b/assets/snippets.html.b17f2d5b.js
similarity index 99%
rename from assets/snippets.html.a3e40b12.js
rename to assets/snippets.html.b17f2d5b.js
index 3157e29b5..2d4fddb26 100644
--- a/assets/snippets.html.a3e40b12.js
+++ b/assets/snippets.html.b17f2d5b.js
@@ -1 +1 @@
-import{r as s,o as p,a as r,b as e,d as i,F as a,e as t,c as n}from"./app.f6cb3ed9.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const l={},c=e("h1",{id:"using-and-managing-code-snippets",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-and-managing-code-snippets","aria-hidden":"true"},"#"),t(" Using and managing code snippets")],-1),h=e("p",null,"IBM Z Open Editor ships with a library of reusable code snippets for COBOL, PL/I, and JCL to help you improve your productivity, as well as to standardize on code patterns and best practices. In addition to these out-of-the-box snippets, you can also create your own snippets and import snippets from IBM Developer for z/OS.",-1),u=t("IBM Z Open Editor utilizes the Snippet facilities provided by VS Code. To learn more about this code snippet support, refer to the "),g={href:"https://code.visualstudio.com/docs/editor/userdefinedsnippets",target:"_blank",rel:"noopener noreferrer"},f=t("VS Code Online Help pages"),m=t("."),w=n('
               Using code snippets
              To explore and insert a code snippet that ships with IBM Z Open Editor, use either the VS Code Snippet picker or the code completion feature while editing a program file.
               Inserting a code snippet with a picker
              1. Place the cursor on Column 1 in the editor as COBOL snippets come with indentations based on that column.
              2. Open the VS Code command palette with Ctrl+Shift+P (Windows) or Cmd+Shift+P (Mac).
              3. Type Insert Snippet until the command appears, and select it.
              4. Based on the language that you are working with, it will then show a picker drop-down with the available snippets. All snippets are organized into a group of related snippets such as COBOL Embedded SQL or COBOL CICS. Each snippet also has a descriptive name and summary.
                1. Scroll down through the list or just type any substring of the snippet your are looking for.
                2. Select the snippet you want to insert and it will be added to the current cursor location.
              5. Many snippets have place holders for variables or terminals. You can use the Tab key or Shift-Tab to navigate between them.
              6. Type the new value to replace this and all other occurrences of the place holder and press Enter to finish.
               Inserting a code snippet using code completion
              1. When you edit a program, press Ctrl+Space to start code completion.
              2. In the drop-down list, you will see first the list of context-sensitive code completion suggestions provided by the language server assuming you are working either in COBOL or PL/I. If you scroll down, you see the list of code snippets below.
              3. Again, you can just type for any code snippet substring to search for a snippet that you are looking for to jump ahead in the drop-down.
              4. Select the snippet and it will be inserted at your current cursor location.
               Creating your own code snippets
              You can easily complement the list of code snippets with your own as follows.
              ',8),y=t("Follow the "),b={href:"https://code.visualstudio.com/docs/editor/userdefinedsnippets#_create-your-own-snippets",target:"_blank",rel:"noopener noreferrer"},_=t("VS Code instructions"),S=t(" to create your own snippets collection."),I=e("li",null,[e("p",null,[t("In the language drop-down, select type "),e("code",null,"cobol"),t(", "),e("code",null,"pl1"),t(", "),e("code",null,"hlasm"),t(", or "),e("code",null,"jcl"),t(" as the language identifiers to start a snippet collection in that language. VS Code will open an editor window with instructions for how to write your own snippets. The help page listed above will also provide you with detailed guidance.")])],-1),v=e("li",null,[e("p",null,"Once you have added your first snippet, save it. It will appear in the Snippet Picker described above placed before the IBM snippets.")],-1),x=n('
               Importing code snippets from IBM Developer for z/OS
              If you are using the IBM Developer for z/OS (IDz) and have created custom code snippets there, you can export these code snippets and import them into the Z Open Editor.
               Exporting code snippets in IDz
              1. To display the available snippets in IDz, use the menu Window > Show View > Snippets.
              2. Right-click anywhere in the Snippets view and select Customize...
              3. In the dialog, find the Snippet group you want to export and click the Export button.
              4. Specify the name and location for the export file, which will be an XML file.
               Importing IDz code snippets into IBM Z Open Editor
              1. In IBM Z Open Editor, open the VS Code command palette with Ctrl+Shift+P (Windows) or Cmd+Shift+P (Mac).
              2. Start typing IBM Z Open Editor: Import IBM Developer for Z Code Snippets until you see this command and select it.
              3. A drop-down picker appears asking you for the program language of the snippets you want to import. Select one from the drop-down menu.
              4. A file dialog appears. Navigate to and select the file that exported from IDz in the previous step.
              5. Then a final text drop down appears asking you for a prefix string for the imported snippets. This prefix will be placed in front of the name of every snippet to be imported, which allows you to group the snippets by name in the resulting Snippet picker. You can leave this value empty and/or edit it again after the import.
              If the import succeeds, it opens a JSON file editor with the imported snippets in the Microsoft VS Code format as documented in the help page listed above. You can now edit and make changes to polish the snippets and to add place holders.
              If there were errors during the import, those errors will be displayed in a separate JSON file. That file will show up only if there were indeed any errors.
              ',8);function C(O,k){const o=s("ExternalLinkIcon");return p(),r(a,null,[c,h,e("p",null,[u,e("a",g,[f,i(o)]),m]),w,e("ol",null,[e("li",null,[e("p",null,[y,e("a",b,[_,i(o)]),S])]),I,v]),x],64)}var M=d(l,[["render",C]]);export{M as default};
+import{r as s,o as p,a as r,b as e,d as i,F as a,e as t,c as n}from"./app.daa93c96.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const l={},c=e("h1",{id:"using-and-managing-code-snippets",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-and-managing-code-snippets","aria-hidden":"true"},"#"),t(" Using and managing code snippets")],-1),h=e("p",null,"IBM Z Open Editor ships with a library of reusable code snippets for COBOL, PL/I, and JCL to help you improve your productivity, as well as to standardize on code patterns and best practices. In addition to these out-of-the-box snippets, you can also create your own snippets and import snippets from IBM Developer for z/OS.",-1),u=t("IBM Z Open Editor utilizes the Snippet facilities provided by VS Code. To learn more about this code snippet support, refer to the "),g={href:"https://code.visualstudio.com/docs/editor/userdefinedsnippets",target:"_blank",rel:"noopener noreferrer"},f=t("VS Code Online Help pages"),m=t("."),w=n('
               Using code snippets
              To explore and insert a code snippet that ships with IBM Z Open Editor, use either the VS Code Snippet picker or the code completion feature while editing a program file.
               Inserting a code snippet with a picker
              1. Place the cursor on Column 1 in the editor as COBOL snippets come with indentations based on that column.
              2. Open the VS Code command palette with Ctrl+Shift+P (Windows) or Cmd+Shift+P (Mac).
              3. Type Insert Snippet until the command appears, and select it.
              4. Based on the language that you are working with, it will then show a picker drop-down with the available snippets. All snippets are organized into a group of related snippets such as COBOL Embedded SQL or COBOL CICS. Each snippet also has a descriptive name and summary.
                1. Scroll down through the list or just type any substring of the snippet your are looking for.
                2. Select the snippet you want to insert and it will be added to the current cursor location.
              5. Many snippets have place holders for variables or terminals. You can use the Tab key or Shift-Tab to navigate between them.
              6. Type the new value to replace this and all other occurrences of the place holder and press Enter to finish.
               Inserting a code snippet using code completion
              1. When you edit a program, press Ctrl+Space to start code completion.
              2. In the drop-down list, you will see first the list of context-sensitive code completion suggestions provided by the language server assuming you are working either in COBOL or PL/I. If you scroll down, you see the list of code snippets below.
              3. Again, you can just type for any code snippet substring to search for a snippet that you are looking for to jump ahead in the drop-down.
              4. Select the snippet and it will be inserted at your current cursor location.
               Creating your own code snippets
              You can easily complement the list of code snippets with your own as follows.
              ',8),y=t("Follow the "),b={href:"https://code.visualstudio.com/docs/editor/userdefinedsnippets#_create-your-own-snippets",target:"_blank",rel:"noopener noreferrer"},_=t("VS Code instructions"),S=t(" to create your own snippets collection."),I=e("li",null,[e("p",null,[t("In the language drop-down, select type "),e("code",null,"cobol"),t(", "),e("code",null,"pl1"),t(", "),e("code",null,"hlasm"),t(", or "),e("code",null,"jcl"),t(" as the language identifiers to start a snippet collection in that language. VS Code will open an editor window with instructions for how to write your own snippets. The help page listed above will also provide you with detailed guidance.")])],-1),v=e("li",null,[e("p",null,"Once you have added your first snippet, save it. It will appear in the Snippet Picker described above placed before the IBM snippets.")],-1),x=n('
               Importing code snippets from IBM Developer for z/OS
              If you are using the IBM Developer for z/OS (IDz) and have created custom code snippets there, you can export these code snippets and import them into the Z Open Editor.
               Exporting code snippets in IDz
              1. To display the available snippets in IDz, use the menu Window > Show View > Snippets.
              2. Right-click anywhere in the Snippets view and select Customize...
              3. In the dialog, find the Snippet group you want to export and click the Export button.
              4. Specify the name and location for the export file, which will be an XML file.
               Importing IDz code snippets into IBM Z Open Editor
              1. In IBM Z Open Editor, open the VS Code command palette with Ctrl+Shift+P (Windows) or Cmd+Shift+P (Mac).
              2. Start typing IBM Z Open Editor: Import IBM Developer for Z Code Snippets until you see this command and select it.
              3. A drop-down picker appears asking you for the program language of the snippets you want to import. Select one from the drop-down menu.
              4. A file dialog appears. Navigate to and select the file that exported from IDz in the previous step.
              5. Then a final text drop down appears asking you for a prefix string for the imported snippets. This prefix will be placed in front of the name of every snippet to be imported, which allows you to group the snippets by name in the resulting Snippet picker. You can leave this value empty and/or edit it again after the import.
              If the import succeeds, it opens a JSON file editor with the imported snippets in the Microsoft VS Code format as documented in the help page listed above. You can now edit and make changes to polish the snippets and to add place holders.
              If there were errors during the import, those errors will be displayed in a separate JSON file. That file will show up only if there were indeed any errors.
              ',8);function C(O,k){const o=s("ExternalLinkIcon");return p(),r(a,null,[c,h,e("p",null,[u,e("a",g,[f,i(o)]),m]),w,e("ol",null,[e("li",null,[e("p",null,[y,e("a",b,[_,i(o)]),S])]),I,v]),x],64)}var M=d(l,[["render",C]]);export{M as default};
diff --git a/assets/table-search-custcopy.aa1be4ee.gif b/assets/table-search-custcopy.aa1be4ee.gif
new file mode 100644
index 000000000..7167043c1
Binary files /dev/null and b/assets/table-search-custcopy.aa1be4ee.gif differ
diff --git a/assets/table-submit-job-view-spool-files.da1dd3a5.gif b/assets/table-submit-job-view-spool-files.da1dd3a5.gif
new file mode 100644
index 000000000..f9bd9b30c
Binary files /dev/null and b/assets/table-submit-job-view-spool-files.da1dd3a5.gif differ
diff --git a/assets/table-submit-members-as-jobs.987c9308.gif b/assets/table-submit-members-as-jobs.987c9308.gif
new file mode 100644
index 000000000..5b1d5f2dd
Binary files /dev/null and b/assets/table-submit-members-as-jobs.987c9308.gif differ
diff --git a/assets/table-uss-search-dbb-error.4f71e355.gif b/assets/table-uss-search-dbb-error.4f71e355.gif
new file mode 100644
index 000000000..0ca406129
Binary files /dev/null and b/assets/table-uss-search-dbb-error.4f71e355.gif differ
diff --git a/assets/trademarks.html.1200a3b5.js b/assets/trademarks.html.008e3827.js
similarity index 90%
rename from assets/trademarks.html.1200a3b5.js
rename to assets/trademarks.html.008e3827.js
index 1334f8939..976c63568 100644
--- a/assets/trademarks.html.1200a3b5.js
+++ b/assets/trademarks.html.008e3827.js
@@ -1 +1 @@
-import{r as t,o,a as s,b as e,d as n,F as i,e as r}from"./app.f6cb3ed9.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const c={},l=e("h1",{id:"trademarks",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#trademarks","aria-hidden":"true"},"#"),r(" Trademarks")],-1),m=r('IBM\xAE, the IBM logo, and ibm.com\xAE are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" '),h={href:"https://www.ibm.com/legal/copytrade",target:"_blank",rel:"noopener noreferrer"},_=r("here"),f=r("."),k=e("p",null,"Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.",-1),p=e("p",null,"Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.",-1),u=e("p",null,"Java\u2122 and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.",-1);function g(b,w){const a=t("ExternalLinkIcon");return o(),s(i,null,[l,e("p",null,[m,e("a",h,[_,n(a)]),f]),k,p,u],64)}var v=d(c,[["render",g]]);export{v as default};
+import{r as t,o,a as s,b as e,d as n,F as i,e as r}from"./app.daa93c96.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const c={},l=e("h1",{id:"trademarks",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#trademarks","aria-hidden":"true"},"#"),r(" Trademarks")],-1),m=r('IBM\xAE, the IBM logo, and ibm.com\xAE are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" '),h={href:"https://www.ibm.com/legal/copytrade",target:"_blank",rel:"noopener noreferrer"},_=r("here"),f=r("."),k=e("p",null,"Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.",-1),p=e("p",null,"Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.",-1),u=e("p",null,"Java\u2122 and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.",-1);function g(b,w){const a=t("ExternalLinkIcon");return o(),s(i,null,[l,e("p",null,[m,e("a",h,[_,n(a)]),f]),k,p,u],64)}var v=d(c,[["render",g]]);export{v as default};
diff --git a/assets/tutorial_assembler.html.93a6a76a.js b/assets/tutorial_assembler.html.7dcb0297.js
similarity index 99%
rename from assets/tutorial_assembler.html.93a6a76a.js
rename to assets/tutorial_assembler.html.7dcb0297.js
index 992cce1f3..39c4ddb16 100644
--- a/assets/tutorial_assembler.html.93a6a76a.js
+++ b/assets/tutorial_assembler.html.7dcb0297.js
@@ -1,3 +1,3 @@
-import{r,o as s,a as c,b as o,d as i,w as n,F as l,c as a,e}from"./app.f6cb3ed9.js";import{_ as d}from"./createbranch.c5e1488b.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";const p={},u=a('
               HLASM editing tutorial
               About this tutorial
              For the tutorial, you will assume the role of an HLASM developer who has received a requirement to enhance the output from ASAM1 to also write the hexedecimal value of a character string. The current version simply reads in a string from an input file, and writes the record number, column number headings, and the input string to an output file.
               Prerequisites
              ',4),m=e("Install IBM Z Open Editor and its prerequisites such as Java as described in "),g=e("Getting Started"),f=e("."),y=o("h2",{id:"procedure",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#procedure","aria-hidden":"true"},"#"),e(" Procedure")],-1),w=a(`
            • To enhance the report, you need to import the source code first.
              1. In VS Code, click Terminal > New Terminal to open a terminal.
              2. In the Terminal window, navigate to the desired directory for the source code by entering, for example, the following command:
                cd /c/Users/Public
+import{r,o as s,a as c,b as o,d as i,w as n,F as l,c as a,e}from"./app.daa93c96.js";import{_ as d}from"./createbranch.c5e1488b.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";const p={},u=a('
                 HLASM editing tutorial
                 About this tutorial
                For the tutorial, you will assume the role of an HLASM developer who has received a requirement to enhance the output from ASAM1 to also write the hexedecimal value of a character string. The current version simply reads in a string from an input file, and writes the record number, column number headings, and the input string to an output file.
                 Prerequisites
                ',4),m=e("Install IBM Z Open Editor and its prerequisites such as Java as described in "),g=e("Getting Started"),f=e("."),y=o("h2",{id:"procedure",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#procedure","aria-hidden":"true"},"#"),e(" Procedure")],-1),w=a(`
              3. To enhance the report, you need to import the source code first.
                1. In VS Code, click Terminal > New Terminal to open a terminal.
                2. In the Terminal window, navigate to the desired directory for the source code by entering, for example, the following command:
                  cd /c/Users/Public
 
                3. To clone the source code from the Git repository, enter the git repository of the sample files:
                  git clone https://github.com/IBM/zopeneditor-sample.git
 
                4. After the clone is completed, click File > Open Folder. Then, in the Open Folder window, select the C:/Users/Public/zopeneditor-sample directory that you cloned, and click Select Folder.
              4. Review the source code.
                The current sample application consists of one HLASM program (ASAM1), one copybook (REGISTRS), two JCL members to set up and run the application (ASMALLOC, RUNASAM1), and the input data file (FILEIN).
                ASAM1 reads in the FILEIN data file record as a character string, and then simply writes out the string to the output file FILEOUT.
              5. (Optional) As you view the source in VS Code, you can use the Outline view to efficiently explore and navigate the code of the program. Note that the Outline view can be used only after you have opened a file or program in VS Code.
                If the Outline view is not already expanded, you can open it by clicking View > Open view > Outline. By looking through the items in this view, you can get an idea of what the program does at a high level.
                Note: ASAM1.asm is a simple program to use in the editing tutorial. To see a more robust Outline view, you can open the IRR@XACS.asm file, an example from SYS1.SAMPLIB. The IRR@XACS.asm file serves as a better example to demonstrate the the Outline view and its capabilities, and you can further explore it as follows:
                • Expand and collapse sections such as Dummy Sections (DSECT) and Control Sections (CSECT), and Macros in the Outline View.
                • Go to a desired location in the code by clicking that section header in the view.
                • Sort by Position, Name, or Type.
                • See Customizing the Outline view to configure what types of symbols to appear in the Outline view.
              6. (Optional) In the ASAM1.asm file, you will see code syntax highlighting in the opened file, which helps you quickly distinguish between HLASM reserved words, comments, constants, and variables.
                To see all the syntax errors in the open files, click View > Problems or click the error and warning icon at the bottom in the status bar. Click the list item to directly go to the problem.
              7. (Optional) Another visual feature of the editor is the grey lines that help with formatting as you code. You will notice the column 72 for the continuation character and the line at column 16 to show where a continued line can begin.
              8. Modify the code in the ASAM1.asm file to also write the hexedecimal value of a character string to the output. When you enter code, the code completion capability provides you with matching lists from which you can select commands, defined variables, and code snippets.
                For example, place your cursor at the end of line 40, and hit the Enter key to begin a new line on line 41. Try typing the command BALR, and as you type, you can select from the lists of code completion suggestions that appear. You will also see a pop-up that displays the name of the command and the format of the command. Delete the new line you just typed on line 41 and continue with the tutorial.
                9. `,6),_=e("(Optional) The hover feature works on variables and copybooks. You can hover over a variable to see its definition. You can hover over a copybook after configuring your ZAPP file and the editor will resolve it and display it in a pop-up window. After the copybook is opened, you can press "),b=o("code",null,"Ctrl+Click",-1),v=e(" on Windows or "),S=o("code",null,"Cmd+Click",-1),A=e(" on Mac to open the copybook in an editor window. Alternatively, you can use "),C=o("code",null,"F12",-1),k=e(" or right click the copybook and select "),x=o("code",null,"Go to Definition",-1),M=e(". Copybook resolution is based on "),O=e("ZAPP file property groups"),T=e("."),F=a('
              9. (Optional) The editor can show you all references of a variable or section in your code. When you double-click a variable or section name to highlight the entire name and then right-click it, you can see the following available actions:
                • Click Change All Occurrences: Ctrl+F2 (Windows) or Cmd+F2 (Mac)
                  When you type the new name, all occurrences are changed simultaneously.
                  Note: In the scroll bar on the right side of the editor, each occurrence is noted with a location bar.
                • Click Find All References: Alt+Shift+F12 (Windows) or Option+Shift+F12 (Mac)
                  A Results References view for the variable or paragraph is displayed on the left side of the screen. Click any result to go to that location in the file.
                • Click Peek References: Shift+F12 (Windows and Mac)
                  A Results References view is displayed in the CodeLens box underneath the variable or paragraph. Click any result to go to that location in the file.
                • Click Go to Definition: F12 (Windows and Mac)
                  Go to the location where the variable or paragraph is defined. It opens the copybook or include if applicable.
                • Click Go to Symbol: Ctrl+Shift+O (Windows) or Cmd+Shift+O (Mac)
                  When you enter an object name in the search bar or you scroll through the items to select the object, the cursor is moved to that location.
                • Click Peek Definition: Alt+F12 (Windows) or Option+F12 (Mac)
                  This opens a CodeLens box that shows where the variable or paragraph was defined in the code.
              10. Examine your code to analyze the impact of the requirement you received to determine the modifications needed. As you are to modify ASAM1, you need to search for all components that refer to the program.
                To search for components referencing ASAM1, you can use the advanced search capabilities provided by the VS Code editor. Its Search view allows searching for strings and regular expressions across all files or a specific subset of files based on location or name patterns.
                In the Explorer view, right-click in the background of the zopeneditor-sample, not showing any particular file or folder to initiate a search on all files:
                1. Select Find in Folder...
                2. Input the search term ASAM1 and press Enter.
                  You can review some of the other search options such as using regular expressions and specifying patterns for files and folders to be excluded or included in the search.
                  For example, to perform a regular expression search, select the .* icon and change the search term to ASAM1.* and review the results. Results will appear in the Search panel.
                3. Click on the result to navigate to that location file in the Editor panel.
              11. Open the integrated Git in VS Code, and create an isolated branch called write-hex-value, where no one but yourself can access the source code before you push the changes to the origin repository.
                To create the branch:
                1. In VS Code on the lower left hand corner, click create branch.
                2. Then, from the drop-down menu that is displayed at the top of VS Code, click Create new branch.
                3. Specify a branch name of write-hex-value, and then press enter to confirm. The workspace is switched to the isolated write-hex-value branch now.
              12. Commit your changes into your write-hex-value branch.
                Now that you have performed various code changes and refinements you can commit this file version of the application to the SCM to preserve and share it.
                To commit your changes, click the Source Control icon on the left of VS Code. In the Source Control panel that opens, the changed program is listed in the CHANGES section. In the CHANGES section, hover on the ASAM1.asm program name and click the Stage changes (+) icon to move your changes to the staging area. In the Message text box, enter a comment for the changes such as Implemented Hex Value, and then click the Commit icon to commit your changes.
                13. ',4),I=e("(Optional) Z Open Editor also supports custom macros for HLASM as an advanced feature. You can hover over a macro after configuring your ZAPP file and the editor will resolve it and display it in a pop-up window. After the macro is opened, you can press "),E=o("code",null,"Ctrl+Click",-1),L=e(" on Windows or "),R=o("code",null,"Cmd+Click",-1),P=e(" on Mac to open the macro in an editor window. Alternatively, you can use "),N=o("code",null,"F12",-1),V=e(" or right click the macro and select "),G=o("code",null,"Go to Definition",-1),W=e(" . See "),D=e("Custom Macros for HLASM"),z=e(" for more information. To see an example of custom macros working in the zopeneditor-sample repository, follow these steps:"),H=a("
                1. Change your branch to wazi-main.
                2. Open the zapp.yaml in the root of the workspace. There is an entry for a library named maclib.
                3. Open /ASM/MASAM1.asm.
                4. Scroll throughout the program and notice the various custom macros that are used. Key macros to look for: MCLOSE, MOPEN, MPUT, MGET, and REGS.
                ",1),B=e("Congratulations on completing the tutorial. For a more comprehensive list of the available features for code editing, see "),q=e("Making code changes"),Y=e(".");function U(Z,j){const t=r("RouterLink");return s(),c(l,null,[u,o("p",null,[m,i(t,{to:"/Docs/getting_started.html"},{default:n(()=>[g]),_:1}),f]),y,o("ol",null,[w,o("li",null,[o("p",null,[_,b,v,S,A,C,k,x,M,i(t,{to:"/Docs/setting_propertygroup.html"},{default:n(()=>[O]),_:1}),T])]),F,o("li",null,[o("p",null,[I,E,L,R,P,N,V,G,W,i(t,{to:"/Docs/advanced_custom_macros.html"},{default:n(()=>[D]),_:1}),z]),H])]),o("p",null,[B,i(t,{to:"/Docs/editor_codechanges.html"},{default:n(()=>[q]),_:1}),Y])],64)}var Q=h(p,[["render",U]]);export{Q as default};
diff --git a/assets/tutorial_cobol.html.121d9584.js b/assets/tutorial_cobol.html.975f720a.js
similarity index 99%
rename from assets/tutorial_cobol.html.121d9584.js
rename to assets/tutorial_cobol.html.975f720a.js
index 22843af3b..ff9744be0 100644
--- a/assets/tutorial_cobol.html.121d9584.js
+++ b/assets/tutorial_cobol.html.975f720a.js
@@ -1,3 +1,3 @@
-import{r as s,o as c,a as l,b as e,d as t,w as a,F as d,e as o,c as n}from"./app.f6cb3ed9.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";const p={},u=e("h1",{id:"cobol-editing-tutorial",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#cobol-editing-tutorial","aria-hidden":"true"},"#"),o(" COBOL editing tutorial")],-1),g=e("h2",{id:"about-this-tutorial",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#about-this-tutorial","aria-hidden":"true"},"#"),o(" About this tutorial")],-1),m=o("For the tutorial, you will assume the role of COBOL developer who has received requirements to enhance the Daily Customer File Update Report of the SAM application located at "),f={href:"https://github.com/IBM/zopeneditor-sample",target:"_blank",rel:"noopener noreferrer"},b=o("https://github.com/IBM/zopeneditor-sample"),_=o("."),y=e("h2",{id:"prerequisites",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#prerequisites","aria-hidden":"true"},"#"),o(" Prerequisites")],-1),w=o("Install IBM Z Open Editor and its prerequisites such as Java as described in "),S=o("Getting Started"),v=o("."),C=e("h2",{id:"procedure",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#procedure","aria-hidden":"true"},"#"),o(" Procedure")],-1),T=e("p",null,"To enhance the report, you need to import the source code of the sample application first.",-1),A=n(`
              13. In VS Code, click Terminal > New Terminal to open a terminal.
              14. In the terminal window, navigate to the desired directory for the source code by entering, for example:
                cd /c/Users/Public
+import{r as s,o as c,a as l,b as e,d as t,w as a,F as d,e as o,c as n}from"./app.daa93c96.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";const p={},u=e("h1",{id:"cobol-editing-tutorial",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#cobol-editing-tutorial","aria-hidden":"true"},"#"),o(" COBOL editing tutorial")],-1),g=e("h2",{id:"about-this-tutorial",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#about-this-tutorial","aria-hidden":"true"},"#"),o(" About this tutorial")],-1),m=o("For the tutorial, you will assume the role of COBOL developer who has received requirements to enhance the Daily Customer File Update Report of the SAM application located at "),f={href:"https://github.com/IBM/zopeneditor-sample",target:"_blank",rel:"noopener noreferrer"},b=o("https://github.com/IBM/zopeneditor-sample"),_=o("."),y=e("h2",{id:"prerequisites",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#prerequisites","aria-hidden":"true"},"#"),o(" Prerequisites")],-1),w=o("Install IBM Z Open Editor and its prerequisites such as Java as described in "),S=o("Getting Started"),v=o("."),C=e("h2",{id:"procedure",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#procedure","aria-hidden":"true"},"#"),o(" Procedure")],-1),T=e("p",null,"To enhance the report, you need to import the source code of the sample application first.",-1),A=n(`
              15. In VS Code, click Terminal > New Terminal to open a terminal.
              16. In the terminal window, navigate to the desired directory for the source code by entering, for example:
                cd /c/Users/Public
 
              17. To clone the source code from the Git repository, enter the Git repository of the provided sample files:
                git clone https://github.com/IBM/zopeneditor-sample.git
 
                18. `,3),E=n("
                After the clone is completed, click File > Open Folder. Then, in the Open Folder window, select the C:/Users/Public/zopeneditor-sample directory that you cloned, and then click Select Folder. The folder is now opened in the Explorer view on the left of VS Code.
                The current sample application consists of the following files:
                • COBOL programs: SAM1 and SAM2
                • COPYBOOKS: CUSTCOPY and TRANREC
                • JCL that set up and run the application: ALLOCATE, RUN
                • Datasource files: CUSTFILE and TRANFILE
                ",3),x=o("As mentioned in the "),I={href:"https://ibm.github.io/zopeneditor-about/Docs/samplefiles.html",target:"_blank",rel:"noopener noreferrer"},O=o("Exploring the Sample Files"),k=o(" page, a program called "),M=e("code",null,"SAM1LIB",-1),L=o(" (a copy of "),F=e("code",null,"SAM1",-1),N=o(") is included to demonstrate the ability to resolve library-based copybooks, whether they be on a local file system or a remote Z host. "),R=e("code",null,"SAM1LIB",-1),P=o(" uses the COPYBOOKS, "),V=e("code",null,"DATETIME",-1),B=o(" (local), and "),U=e("code",null,"REPTTOTL",-1),D=o(" (MVS)."),Y=n("
                SAM1 reads in both the CUSTFILE and TRANFILE data files, then performs different actions on the CUSTFILE based on transactions from TRANFILE. Valid transactions are ADD, UPDATE, and DELETE. When encountering an UPDATE transaction, SAM1 will call SAM2 to perform the requested update.
                As you review SAM2, you will notice there is already some base code in place for CRUNCH transactions which will be enhanced later in the following exercise. At the end of processing the TRANFILE, SAM1 will then generate a report on the transactions processed and will also produce an updated CUSTFILE.
                ",2),q=n('
              18. Search for components that generate and reference the "Daily Customer File Update" with the advanced Search capabilities provided by the VS Code editor out of the box. Its Search view allows searching for strings as well as regular expression across all files or a specific subset of files based on location or name patterns.
                In the Explorer right-click in the background of the WAZI-SAMPLE, not showing any particular file or folder to initiate a search on all files:
                • Select Find in Folder...
                • Enter the search term CUSTOMER-FILE and start the search with the Return key.
                • Review some of the other search options such as using regular expression and specifying patterns for files and folders to be excluded or included in the search.
                • To perform a regular expression search select the .* icon and change the search term to CUST.*FILE and review the results.
                • Results will appear in the Search Panel.
                • Clicking on the result will allow the user to navigate to that location file in the Editor panel.
              19. Now that you have determined the file that need to be modified - SAM1.cbl. Open the SAM1.cbl program in the editor, you will see syntax highlighting in the program, which allows you to quickly distinguish between COBOL reserved words, comments, constants, and variables. You will also see unrecognized statements and expressions in red, which enables you to make quick corrections and reduce compile errors. Syntax checking also works for misspelled COBOL reserved words and unknown variable names. To see all the syntax errors in the open files, open the Problems view through the View menu or by clicking the error and warning icon at the bottom in the status bar. Click the list item to directly go to the problem.
                If you specified the filepath to the copybooks in your ZAPP file property groups to resolve the references, you can also preview the contents of a copybook by moving your mouse cursor over the copybook name in a COPY statement, for example COPY TRANREC, in the COBOL program without having to navigate away. This also applies to copybooks that reside in libraries and reference in COBOL programs as demonstrated in SAM1.cbl with the COPY DATETIME IN MYFILE (for local) and COPY REPTTOTL IN MYLIB (for MVS) statements.
              20. To understand this program at a high level and efficiently explore and navigate the code of the program, use the Outline view. If the Outline view is not automatically expanded, open it by clicking View > Open view > Outline. You can use this view to perform the following actions:
                • Expand and collapse sections such as Division Headings, Section Headings, and Variable Group Names in the Outline View.
                • Recognize includes, procedures, and loops quickly via the icons located by the various items.
                • Go to a desired location in the code by clicking that section header in the view.
                • Sort by Position, Name, or Type.
                Note: The Outline view can be used only after you have opened a file or program in VS Code.
              21. After efficiently navigating through the program, you know that you have to insert code in the SAM1.cbl program to fix the issue. Now, you can use the integrated Git in VS Code to create an isolated branch called update-report where no one but yourself can access the source code in it unless you push the changes to the origin repository. To create the branch:
                • In VS Code on the lower left hand corner, click the main branch at the lower left.
                • Then, from the drop-down menu that is displayed at the top of VS Code, click Create new branch.
                • Specify a branch name of update-report, and then press enter to confirm. The workspace is switched to the isolated update-report branch now.
              22. You are now ready to insert code. When you are entering code, code completion provides you with matching lists from which you can select commands, defined variable and paragraph names, and code snippets. For example, place your cursor at the end of line 216, and press Enter to begin a new line on line 217. Try typing the command ACCEPT CURRENT-TIME FROM TIME. As you type, note that you can select from the lists of code completion suggestions that appear.
                You can also use the code snippets that are shipped with IBM Z Open Editor. To use it, navigate to the File Control section of the SAM1.cbl program, press F1, select Insert Snippet, and then enter VSAM in the Search bar. You will see a list of VSAM snippets. For example, scroll to the VSAM: KSDS Select/Assign Clause snippet and press Enter. A pre-formatted SELECT/ASSIGN clause will be inserted.
              23. Now that you have performed code changes and refinements, you can commit your changes into your update-report branch to preserve it. To commit your changes, click the Source Control icon on the left of VS Code. In the Source Control panel that opens, the changed program is listed in the CHANGES section. In the CHANGES section, hover on the SAM1.cbl program name and click the Stage changes (+) icon to move your changes to the staging area. In the Message text box, enter a comment for the changes such as Implemented Update Report, and then click the Commit icon to commit your changes.
                24. ',6),G=o("Congratulations on completing the tutorial. For a more comprehensive list of the available features for code editing, see "),z=o("Making code changes"),H=o(".");function Z(K,W){const i=s("ExternalLinkIcon"),r=s("RouterLink");return c(),l(d,null,[u,g,e("p",null,[m,e("a",f,[b,t(i)]),_]),y,e("ol",null,[e("li",null,[w,t(r,{to:"/Docs/getting_started.html"},{default:a(()=>[S]),_:1}),v])]),C,e("ol",null,[e("li",null,[T,e("ul",null,[A,e("li",null,[E,e("p",null,[x,e("a",I,[O,t(i)]),k,M,L,F,N,R,P,V,B,U,D]),Y])])]),q]),e("p",null,[G,t(r,{to:"/Docs/editor_codechanges.html"},{default:a(()=>[z]),_:1}),H])],64)}var Q=h(p,[["render",Z]]);export{Q as default};
diff --git a/assets/tutorial_overview.html.f84e0fa1.js b/assets/tutorial_overview.html.5a8c9afe.js
similarity index 97%
rename from assets/tutorial_overview.html.f84e0fa1.js
rename to assets/tutorial_overview.html.5a8c9afe.js
index bf248c15f..6bc7a3ee0 100644
--- a/assets/tutorial_overview.html.f84e0fa1.js
+++ b/assets/tutorial_overview.html.5a8c9afe.js
@@ -1 +1 @@
-import{r as i,o as n,a as r,b as o,d as s,w as a,F as l,e as t}from"./app.f6cb3ed9.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const u={},d=o("h1",{id:"tutorial-overview",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#tutorial-overview","aria-hidden":"true"},"#"),t(" Tutorial overview")],-1),h=t("If you are new to Microsoft Visual Studio Code, you might want to first "),_=t("explore the user interface"),m=t(" to learn about its key user interface capabilities and views, which are most relevant for working with COBOL, PL/I, HLASM, and REXX program files."),f=t("If you are ready to get hands-on with IBM Z Open Editor, you can use the "),p=t("sample repository of COBOL, PL/I, HLASM, and REXX files"),w=t(" to walk through the tutorials and explore the features of IBM Z Open Editor."),g=t("Once you have the sample files, you can start by making code changes to "),v=t("COBOL"),I=t(", "),L=t("HLASM"),b=t(", and "),x=t("REXX"),O=t(" programs to learn about the editing capabilities."),y=o("p",null,"After you complete code changes on your machine, you might want to go ahead and manage z/OS resources. To learn more about how to interact with z/OS using IBM Z Open Editor and its integrations, refer to the following tutorials:",-1),E=t("Managing z/OS resources with IBM RSE API Plug-in for Zowe CLI tutorial"),S=t(": Provides examples on how to use Zowe Explorer, IBM RSE API Plug-in for Zowe CLI commands, and a script to interact with z/OS. This tutorial is relevant when RSE API is installed and configured on the host."),B=t("Submitting JCL to compile, link, and run jobs tutorial"),C=t(": Provides examples on how to use Zowe CLI commands and Zowe Explorer to submit JCL.");function M(k,P){const e=i("RouterLink");return n(),r(l,null,[d,o("p",null,[h,s(e,{to:"/Docs/userinterface.html"},{default:a(()=>[_]),_:1}),m]),o("p",null,[f,s(e,{to:"/Docs/samplefiles.html"},{default:a(()=>[p]),_:1}),w]),o("p",null,[g,s(e,{to:"/Docs/tutorial_cobol.html"},{default:a(()=>[v]),_:1}),I,s(e,{to:"/Docs/tutorial_assembler.html"},{default:a(()=>[L]),_:1}),b,s(e,{to:"/Docs/tutorial_rexx.html"},{default:a(()=>[x]),_:1}),O]),y,o("ul",null,[o("li",null,[s(e,{to:"/Docs/rse_tutorial.html"},{default:a(()=>[E]),_:1}),S]),o("li",null,[s(e,{to:"/Docs/zowe_submitjcl.html"},{default:a(()=>[B]),_:1}),C])])],64)}var A=c(u,[["render",M]]);export{A as default};
+import{r as i,o as n,a as r,b as o,d as s,w as a,F as l,e as t}from"./app.daa93c96.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const u={},d=o("h1",{id:"tutorial-overview",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#tutorial-overview","aria-hidden":"true"},"#"),t(" Tutorial overview")],-1),h=t("If you are new to Microsoft Visual Studio Code, you might want to first "),_=t("explore the user interface"),m=t(" to learn about its key user interface capabilities and views, which are most relevant for working with COBOL, PL/I, HLASM, and REXX program files."),f=t("If you are ready to get hands-on with IBM Z Open Editor, you can use the "),p=t("sample repository of COBOL, PL/I, HLASM, and REXX files"),w=t(" to walk through the tutorials and explore the features of IBM Z Open Editor."),g=t("Once you have the sample files, you can start by making code changes to "),v=t("COBOL"),I=t(", "),L=t("HLASM"),b=t(", and "),x=t("REXX"),O=t(" programs to learn about the editing capabilities."),y=o("p",null,"After you complete code changes on your machine, you might want to go ahead and manage z/OS resources. To learn more about how to interact with z/OS using IBM Z Open Editor and its integrations, refer to the following tutorials:",-1),E=t("Managing z/OS resources with IBM RSE API Plug-in for Zowe CLI tutorial"),S=t(": Provides examples on how to use Zowe Explorer, IBM RSE API Plug-in for Zowe CLI commands, and a script to interact with z/OS. This tutorial is relevant when RSE API is installed and configured on the host."),B=t("Submitting JCL to compile, link, and run jobs tutorial"),C=t(": Provides examples on how to use Zowe CLI commands and Zowe Explorer to submit JCL.");function M(k,P){const e=i("RouterLink");return n(),r(l,null,[d,o("p",null,[h,s(e,{to:"/Docs/userinterface.html"},{default:a(()=>[_]),_:1}),m]),o("p",null,[f,s(e,{to:"/Docs/samplefiles.html"},{default:a(()=>[p]),_:1}),w]),o("p",null,[g,s(e,{to:"/Docs/tutorial_cobol.html"},{default:a(()=>[v]),_:1}),I,s(e,{to:"/Docs/tutorial_assembler.html"},{default:a(()=>[L]),_:1}),b,s(e,{to:"/Docs/tutorial_rexx.html"},{default:a(()=>[x]),_:1}),O]),y,o("ul",null,[o("li",null,[s(e,{to:"/Docs/rse_tutorial.html"},{default:a(()=>[E]),_:1}),S]),o("li",null,[s(e,{to:"/Docs/zowe_submitjcl.html"},{default:a(()=>[B]),_:1}),C])])],64)}var A=c(u,[["render",M]]);export{A as default};
diff --git a/assets/tutorial_rexx.html.94025c05.js b/assets/tutorial_rexx.html.b7165cf6.js
similarity index 99%
rename from assets/tutorial_rexx.html.94025c05.js
rename to assets/tutorial_rexx.html.b7165cf6.js
index e834c4a0f..31a396f1a 100644
--- a/assets/tutorial_rexx.html.94025c05.js
+++ b/assets/tutorial_rexx.html.b7165cf6.js
@@ -1,3 +1,3 @@
-import{r,o as s,a as c,b as t,d as o,w as n,F as l,e,c as d}from"./app.f6cb3ed9.js";import{_ as h}from"./createbranch.c5e1488b.js";import{_ as p}from"./plugin-vue_export-helper.21dcd24c.js";const u={},g=t("h1",{id:"rexx-editing-tutorial",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#rexx-editing-tutorial","aria-hidden":"true"},"#"),e(" REXX editing tutorial")],-1),m=t("h2",{id:"about-this-tutorial",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#about-this-tutorial","aria-hidden":"true"},"#"),e(" About this tutorial")],-1),f=e("For the tutorial, you will assume the role of a REXX developer who has received a requirement to enhance the output from "),y=t("code",null,"RSAM1",-1),_=e(" to display the contents of the output file which is a combination of the two input files. The current version simply reads in two files and writes the records to an output file. The RSAM application is located at "),w={href:"https://github.com/IBM/zopeneditor-sample",target:"_blank",rel:"noopener noreferrer"},b=e("https://github.com/IBM/zopeneditor-sample"),v=e("."),x=t("h2",{id:"prerequisites",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#prerequisites","aria-hidden":"true"},"#"),e(" Prerequisites")],-1),k=e("Install IBM Z Open Editor and its prerequisites such as Java as described in "),S=e("Getting Started"),C=e("."),I=d(`
                 Procedure
                1. To enhance the report, you need to import the source code of the sample application first.
                  • In VS Code, click Terminal > New Terminal to open a terminal.
                  • In the terminal window, navigate to the desired directory for the source code by entering, for example:
                    cd /c/Users/Public
+import{r,o as s,a as c,b as t,d as o,w as n,F as l,e,c as d}from"./app.daa93c96.js";import{_ as h}from"./createbranch.c5e1488b.js";import{_ as p}from"./plugin-vue_export-helper.21dcd24c.js";const u={},g=t("h1",{id:"rexx-editing-tutorial",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#rexx-editing-tutorial","aria-hidden":"true"},"#"),e(" REXX editing tutorial")],-1),m=t("h2",{id:"about-this-tutorial",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#about-this-tutorial","aria-hidden":"true"},"#"),e(" About this tutorial")],-1),f=e("For the tutorial, you will assume the role of a REXX developer who has received a requirement to enhance the output from "),y=t("code",null,"RSAM1",-1),_=e(" to display the contents of the output file which is a combination of the two input files. The current version simply reads in two files and writes the records to an output file. The RSAM application is located at "),w={href:"https://github.com/IBM/zopeneditor-sample",target:"_blank",rel:"noopener noreferrer"},b=e("https://github.com/IBM/zopeneditor-sample"),v=e("."),x=t("h2",{id:"prerequisites",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#prerequisites","aria-hidden":"true"},"#"),e(" Prerequisites")],-1),k=e("Install IBM Z Open Editor and its prerequisites such as Java as described in "),S=e("Getting Started"),C=e("."),I=d(`
                     Procedure
                    1. To enhance the report, you need to import the source code of the sample application first.
                      • In VS Code, click Terminal > New Terminal to open a terminal.
                      • In the terminal window, navigate to the desired directory for the source code by entering, for example:
                        cd /c/Users/Public
 
                      • To clone the source code from the Git repository, enter the git repository of the provided sample files:
                        git clone https://github.com/IBM/zopeneditor-sample.git
 
                      • After the clone is completed, click File > Open Folder. Then, in the Open Folder window, select the C:/Users/Public/zopeneditor-sample directory that you cloned, and then click Select Folder. The folder is now opened in the Explorer view on the left of VS Code.
                        The current sample application consists of a REXX program, RSAM1, and JCL to set up the application files (REXALLOC), and the datasource files (FILEIN1 and FILEIN2).
                        RSAM1 reads in the FILEIN1 data file and writes the records to the FILEOUT datafile. It then reads in FILEIN2 and writes the records to FILEOUT.
                    2. (Optional) As you view the source in VS Code, you can use the Outline view to efficiently explore and navigate the code of the program. Note that the Outline view can be used only after you have opened a file or program in VS Code.
                      If the Outline view is not already expanded, you can open it by clicking View > Open view > Outline. By looking through the items in this view, you can get an idea of what the program does at a high level.
                      Note: The REXX Outline view only shows internal routines. RSAM1.rexx is a simple program to use in the editing tutorial so only two internal routines show up in the Outline view.
                    3. (Optional) In the RSAM1.rexx file, you will see code syntax highlighting in the opened file, which helps you quickly distinguish between comments, strings, constants, variables, keywords, labels, functions, comparison, and arithmetic.
                      Unrecognized statements and expressions are highlighted in red, with which you can make quick corrections accordingly and reduce compile errors. To see all the syntax errors in the open files, click View > Problems or click the error and warning icon at the bottom in the status bar. Click the list item to directly go to the problem.
                    4. Modify the code in the RSAM1.rexx file to add a new internal routine fileout, which will read through FILEOUT and display each record that is in the file.
                      For example, place your cursor on line 42 and hit the Enter key to begin a new line on line 43. Begin typing the command CALL fileout, and as you type, you can select from the lists of code completion suggestions that appear. You will also see a pop-up that displays the name of the command and the format of the command.
                    5. (Optional) The hover feature works on REXX keyword instructions. You can hover over a keyword to see its definition and format.
                    6. (Optional) The editor can show you all references of a variable or internal routine in your code. When you double-click a variable or internal routine name to highlight the entire name and then right-click it, you can see the following available actions:
                      • Click Find All References: Alt+Shift+F12 (Windows) or Option+Shift+F12(Mac)
                        A Results References view for the variable or paragraph is displayed on the left side of the screen. Click any result to go to that location in the file.
                      • Click Peek References: Shift+F12 (Windows and Mac)
                        A Results References view is displayed in the CodeLens box underneath the variable or paragraph. Click any result to go to that location in the file.
                    7. Open the integrated Git in VS Code, and create an isolated branch called display-fileout-content, where no one but yourself can access the source code before you push the changes to the origin repository.
                      To create the branch:
                      1. In VS Code on the lower left hand corner, click create branch.
                      2. Then, from the drop-down menu that is displayed at the top of VS Code, click Create new branch.
                      3. Specify a branch name of display-fileout-content, and then press enter to confirm. The workspace is switched to the isolated display-fileout-content branch now.
                    8. Commit your changes into your display-fileout-content branch.
                      Now that you have performed various code changes and refinements you can commit this file version of the application to the SCM to preserve and share it.
                      To commit your changes, click the Source Control icon on the left of VS Code. In the Source Control panel that opens, the changed program is listed in the CHANGES section. In the CHANGES section, hover on the RSAM1.rexx program name and click the Stage changes (+) icon to move your changes to the staging area. In the Message text box, enter a comment for the changes such as Display fileout content, and then click the Commit icon to commit your changes.
                    ',2),R=e("Congratulations on completing the tutorial. For a more comprehensive list of the available features for code editing, see "),T=e("Making REXX code changes"),E=e("."),O=e("The RSE CLI plug-in also has support for Interactive TSO commands, you can read more about this under "),F=e("Run interactive TSO commands"),A=e(".");function L(M,N){const a=r("ExternalLinkIcon"),i=r("RouterLink");return s(),c(l,null,[g,m,t("p",null,[f,y,_,t("a",w,[b,o(a)]),v]),x,t("ol",null,[t("li",null,[k,o(i,{to:"/Docs/getting_started.html"},{default:n(()=>[S]),_:1}),C])]),I,t("p",null,[R,o(i,{to:"/Docs/editor_codechanges_rexx.html"},{default:n(()=>[T]),_:1}),E]),t("p",null,[O,o(i,{to:"/Docs/interact_zos_cli.html#run-interactive-tso-commands"},{default:n(()=>[F]),_:1}),A])],64)}var q=p(u,[["render",L]]);export{q as default};
diff --git a/assets/uninstalling.html.a1faa6c5.js b/assets/uninstalling.html.18615d66.js
similarity index 97%
rename from assets/uninstalling.html.a1faa6c5.js
rename to assets/uninstalling.html.18615d66.js
index 7387a4a01..59f4ff3fa 100644
--- a/assets/uninstalling.html.a1faa6c5.js
+++ b/assets/uninstalling.html.18615d66.js
@@ -1,3 +1,3 @@
-import{c as n}from"./app.f6cb3ed9.js";import{_ as e}from"./plugin-vue_export-helper.21dcd24c.js";const i={},l=n(`
                     Uninstalling CLI plugins and VS Code extensions
                    Follow this procedure to uninstall IBM RSE API Plug-in for Zowe CLI and IBM Z Open Editor from your workstation.
                     Uninstalling RSE CLI plug-in
                    To uninstall IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in) from your development machine, complete the following steps:
                    1. Check that the RSE CLI plug-in is currently installed by running the following Zowe CLI command:
                      zowe plugins list
+import{c as n}from"./app.daa93c96.js";import{_ as e}from"./plugin-vue_export-helper.21dcd24c.js";const i={},l=n(`
                       Uninstalling CLI plugins and VS Code extensions
                      Follow this procedure to uninstall IBM RSE API Plug-in for Zowe CLI and IBM Z Open Editor from your workstation.
                       Uninstalling RSE CLI plug-in
                      To uninstall IBM RSE API Plug-in for Zowe CLI (RSE CLI plug-in) from your development machine, complete the following steps:
                      1. Check that the RSE CLI plug-in is currently installed by running the following Zowe CLI command:
                        zowe plugins list
 
                      2. Uninstall the RSE CLI plug-in by running the following command:
                        zowe plugins uninstall @ibm/rse-api-for-zowe-cli
 
                       Uninstalling Z Open Editor and Zowe Explorer
                      To uninstall IBM Z Open Editor and Zowe Explorer, complete the following steps:
                      1. In VS Code, navigate to the Extensions activity group by click the icon on the left toolbar or by clicking Code > Settings > Extensions.
                      2. From the Extensions: Installed list, select IBM Z Open Editor.
                      3. In the details view appearing on the right, click Uninstall.
                      4. From the list on the left, select Zowe Explorer.
                      5. In the details view appearing on the right, click Uninstall.
                      6. Quit and restart VS Code.
                      `,8);function t(s,o){return l}var d=e(i,[["render",t]]);export{d as default};
diff --git a/assets/userbuild-blog.html.b0a68b35.js b/assets/userbuild-blog.html.23b2eadd.js
similarity index 99%
rename from assets/userbuild-blog.html.b0a68b35.js
rename to assets/userbuild-blog.html.23b2eadd.js
index 373385fc3..87691934f 100644
--- a/assets/userbuild-blog.html.b0a68b35.js
+++ b/assets/userbuild-blog.html.23b2eadd.js
@@ -1 +1 @@
-import{r as n,o as r,a as l,b as e,d as i,F as d,e as t,c as s}from"./app.f6cb3ed9.js";import{_ as a}from"./plugin-vue_export-helper.21dcd24c.js";var u="/zopeneditor-about/assets/userbuild-diagram.1b51deb4.png",c="/zopeneditor-about/assets/userbuild-settings.eade3663.png",h="/zopeneditor-about/assets/userbuild-menus.821e6e23.png",p="/zopeneditor-about/assets/userbuild-finish-log.31f71f3d.png";const _={},g=e("h1",{id:"ibm-z\xAE-open-editor-makes-building-cobol-pl-i-and-hlasm-applications-easier-with-user-build",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z\xAE-open-editor-makes-building-cobol-pl-i-and-hlasm-applications-easier-with-user-build","aria-hidden":"true"},"#"),t(" IBM Z\xAE Open Editor makes building COBOL, PL/I, and HLASM applications easier with User Build")],-1),b=e("blockquote",null,[e("p",null,"by Kristina Mayo")],-1),f=e("p",null,"There is a new exciting feature in the IBM Z Open Editor VS Code extension, it's called User Build. User Build allows you as a z/OS\xAE developer who writes COBOL, PL/I, or HLASM to build your applications directly out of VS Code or CodeReady Workspaces.",-1),m=t("This feature is created for you if you are an "),w={href:"https://www.ibm.com/products/dependency-based-build#:~:text=IBM%20Dependency%20Based%20Build%20(DBB)%20provides%20capabilities%20to%20build%20traditional,be%20used%20on%20z%2FOS.",target:"_blank",rel:"noopener noreferrer"},B=t("IBM\xAE Dependency Based Build"),y=t(" user and would like to try developing in VS Code. User Build enables you to:"),v=s('
                      • Build applications without interrupting your workflow and going outside the IDE.
                      • Quickly compile code changes without opening a pull request or sharing the code with others.
                       Architectural overview
                      As an overview, User Build builds a program by performing the following tasks automatically:
                      • Uploads the application file to z/OS.
                      • Uploads the application's copybooks and include files to z/OS.
                      • Invokes the remote build script that you defined in User Build settings.
                      • Downloads build log files locally for easier viewing.
                      User Build diagram
                      Notes:
                      • User Build does not require Git to work.
                      • User can specify a custom script to execute for User Build, though DBB with zAppBuild solution is recommended.
                       Prerequisites
                      Before using the user build feature, ensure that the following host and client requirements are met.
                      Host requirements:
                      ',10),k={href:"https://www.ibm.com/products/dependency-based-build#:~:text=IBM%20Dependency%20Based%20Build%20(DBB)%20provides%20capabilities%20to%20build%20traditional,be%20used%20on%20z%2FOS.",target:"_blank",rel:"noopener noreferrer"},z=t("IBM Dependency Based Build"),S=t(" configured on z/OS"),O={href:"https://github.com/IBM/dbb-zappbuild",target:"_blank",rel:"noopener noreferrer"},U=t("zAppBuild"),x=t(" directory copied on z/OS and configured with data set references"),C=e("p",null,[e("strong",null,"Client requirements:")],-1),I=e("li",null,[e("p",null,"VS Code installed")],-1),L=e("li",null,[e("p",null,"Z Open Editor VS Code extension installed")],-1),V={href:"https://docs.zowe.org/v1-3-x/getting-started/cli-getting-started.html#creating-a-z/OSmf-profile",target:"_blank",rel:"noopener noreferrer"},M=t("Zowe\u2122 CLI profiles"),T=t(" created (to connect to z/OS)"),q=t("User Build utilizes open source "),D={href:"https://docs.zowe.org/stable/getting-started/overview.html",target:"_blank",rel:"noopener noreferrer"},A=t("Zowe technologies"),E=t(" to communicate with z/OS. For that reason, you need to have Zowe CLI profiles to tell User Build how to connect to z/OS."),N=e("h2",{id:"user-build-settings",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#user-build-settings","aria-hidden":"true"},"#"),t(" User build settings")],-1),F=t("Before running User Build, you need to configure it via settings to tell User Build where on z/OS to upload files and which build script to execute. The settings should be defined and store as JSON inside "),Z={href:"https://code.visualstudio.com/docs/getstarted/settings",target:"_blank",rel:"noopener noreferrer"},H=t("VS Code settings files"),P=t("."),R=t("User Build has 2 types of settings: workspace settings and user settings, though both can be placed inside workspace settings file for convenience. See "),j={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-setting-up-user-build",target:"_blank",rel:"noopener noreferrer"},G=t("user build docs"),J=t(" for detailed descriptions of each setting."),K=s('
                      The following example shows workspace and user settings are all stored inside zopeneditor-sample/.vscode/settings.json for convenience. User Build settings example
                       Running User Build
                      Once settings are filled out, right-click inside a file in the editor, select Run IBM User Build to execute remote script and see results directly in VS Code.
                      User Build menus inside VS Code
                      The user build log will be streamed in the Output panel inside VS Code. The build is successful when you see the message Build State: CLEAN in the output. The picture below shows successful zAppBuild output for a COBOL application and a log file.
                      User Build successful COBOL build
                       Trying out User Build
                      ',7),Q=t("To get started with User Build, follow this "),W={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=tutorial-building-cobol-pli-hlasm-applications",target:"_blank",rel:"noopener noreferrer"},X=t("hands-on tutorial"),Y=t(" to use IBM's sample code and the defined workspace settings in the repository."),$=t("For full documentation, refer to "),ee={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-setting-up-user-build",target:"_blank",rel:"noopener noreferrer"},te=t("Setting up the user build"),oe=t(".");function ie(se,ne){const o=n("ExternalLinkIcon");return r(),l(d,null,[g,b,f,e("p",null,[m,e("a",w,[B,i(o)]),y]),v,e("ul",null,[e("li",null,[e("a",k,[z,i(o)]),S]),e("li",null,[e("a",O,[U,i(o)]),x])]),C,e("ul",null,[I,L,e("li",null,[e("p",null,[e("a",V,[M,i(o)]),T]),e("p",null,[q,e("a",D,[A,i(o)]),E])])]),N,e("p",null,[F,e("a",Z,[H,i(o)]),P]),e("p",null,[R,e("a",j,[G,i(o)]),J]),K,e("p",null,[Q,e("a",W,[X,i(o)]),Y]),e("p",null,[$,e("a",ee,[te,i(o)]),oe])],64)}var de=a(_,[["render",ie]]);export{de as default};
+import{r as n,o as r,a as l,b as e,d as i,F as d,e as t,c as s}from"./app.daa93c96.js";import{_ as a}from"./plugin-vue_export-helper.21dcd24c.js";var u="/zopeneditor-about/assets/userbuild-diagram.1b51deb4.png",c="/zopeneditor-about/assets/userbuild-settings.eade3663.png",h="/zopeneditor-about/assets/userbuild-menus.821e6e23.png",p="/zopeneditor-about/assets/userbuild-finish-log.31f71f3d.png";const _={},g=e("h1",{id:"ibm-z\xAE-open-editor-makes-building-cobol-pl-i-and-hlasm-applications-easier-with-user-build",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#ibm-z\xAE-open-editor-makes-building-cobol-pl-i-and-hlasm-applications-easier-with-user-build","aria-hidden":"true"},"#"),t(" IBM Z\xAE Open Editor makes building COBOL, PL/I, and HLASM applications easier with User Build")],-1),b=e("blockquote",null,[e("p",null,"by Kristina Mayo")],-1),f=e("p",null,"There is a new exciting feature in the IBM Z Open Editor VS Code extension, it's called User Build. User Build allows you as a z/OS\xAE developer who writes COBOL, PL/I, or HLASM to build your applications directly out of VS Code or CodeReady Workspaces.",-1),m=t("This feature is created for you if you are an "),w={href:"https://www.ibm.com/products/dependency-based-build#:~:text=IBM%20Dependency%20Based%20Build%20(DBB)%20provides%20capabilities%20to%20build%20traditional,be%20used%20on%20z%2FOS.",target:"_blank",rel:"noopener noreferrer"},B=t("IBM\xAE Dependency Based Build"),y=t(" user and would like to try developing in VS Code. User Build enables you to:"),v=s('
                      • Build applications without interrupting your workflow and going outside the IDE.
                      • Quickly compile code changes without opening a pull request or sharing the code with others.
                       Architectural overview
                      As an overview, User Build builds a program by performing the following tasks automatically:
                      • Uploads the application file to z/OS.
                      • Uploads the application's copybooks and include files to z/OS.
                      • Invokes the remote build script that you defined in User Build settings.
                      • Downloads build log files locally for easier viewing.
                      User Build diagram
                      Notes:
                      • User Build does not require Git to work.
                      • User can specify a custom script to execute for User Build, though DBB with zAppBuild solution is recommended.
                       Prerequisites
                      Before using the user build feature, ensure that the following host and client requirements are met.
                      Host requirements:
                      ',10),k={href:"https://www.ibm.com/products/dependency-based-build#:~:text=IBM%20Dependency%20Based%20Build%20(DBB)%20provides%20capabilities%20to%20build%20traditional,be%20used%20on%20z%2FOS.",target:"_blank",rel:"noopener noreferrer"},z=t("IBM Dependency Based Build"),S=t(" configured on z/OS"),O={href:"https://github.com/IBM/dbb-zappbuild",target:"_blank",rel:"noopener noreferrer"},U=t("zAppBuild"),x=t(" directory copied on z/OS and configured with data set references"),C=e("p",null,[e("strong",null,"Client requirements:")],-1),I=e("li",null,[e("p",null,"VS Code installed")],-1),L=e("li",null,[e("p",null,"Z Open Editor VS Code extension installed")],-1),V={href:"https://docs.zowe.org/v1-3-x/getting-started/cli-getting-started.html#creating-a-z/OSmf-profile",target:"_blank",rel:"noopener noreferrer"},M=t("Zowe\u2122 CLI profiles"),T=t(" created (to connect to z/OS)"),q=t("User Build utilizes open source "),D={href:"https://docs.zowe.org/stable/getting-started/overview.html",target:"_blank",rel:"noopener noreferrer"},A=t("Zowe technologies"),E=t(" to communicate with z/OS. For that reason, you need to have Zowe CLI profiles to tell User Build how to connect to z/OS."),N=e("h2",{id:"user-build-settings",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#user-build-settings","aria-hidden":"true"},"#"),t(" User build settings")],-1),F=t("Before running User Build, you need to configure it via settings to tell User Build where on z/OS to upload files and which build script to execute. The settings should be defined and store as JSON inside "),Z={href:"https://code.visualstudio.com/docs/getstarted/settings",target:"_blank",rel:"noopener noreferrer"},H=t("VS Code settings files"),P=t("."),R=t("User Build has 2 types of settings: workspace settings and user settings, though both can be placed inside workspace settings file for convenience. See "),j={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-setting-up-user-build",target:"_blank",rel:"noopener noreferrer"},G=t("user build docs"),J=t(" for detailed descriptions of each setting."),K=s('
                      The following example shows workspace and user settings are all stored inside zopeneditor-sample/.vscode/settings.json for convenience. User Build settings example
                       Running User Build
                      Once settings are filled out, right-click inside a file in the editor, select Run IBM User Build to execute remote script and see results directly in VS Code.
                      User Build menus inside VS Code
                      The user build log will be streamed in the Output panel inside VS Code. The build is successful when you see the message Build State: CLEAN in the output. The picture below shows successful zAppBuild output for a COBOL application and a log file.
                      User Build successful COBOL build
                       Trying out User Build
                      ',7),Q=t("To get started with User Build, follow this "),W={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=tutorial-building-cobol-pli-hlasm-applications",target:"_blank",rel:"noopener noreferrer"},X=t("hands-on tutorial"),Y=t(" to use IBM's sample code and the defined workspace settings in the repository."),$=t("For full documentation, refer to "),ee={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-setting-up-user-build",target:"_blank",rel:"noopener noreferrer"},te=t("Setting up the user build"),oe=t(".");function ie(se,ne){const o=n("ExternalLinkIcon");return r(),l(d,null,[g,b,f,e("p",null,[m,e("a",w,[B,i(o)]),y]),v,e("ul",null,[e("li",null,[e("a",k,[z,i(o)]),S]),e("li",null,[e("a",O,[U,i(o)]),x])]),C,e("ul",null,[I,L,e("li",null,[e("p",null,[e("a",V,[M,i(o)]),T]),e("p",null,[q,e("a",D,[A,i(o)]),E])])]),N,e("p",null,[F,e("a",Z,[H,i(o)]),P]),e("p",null,[R,e("a",j,[G,i(o)]),J]),K,e("p",null,[Q,e("a",W,[X,i(o)]),Y]),e("p",null,[$,e("a",ee,[te,i(o)]),oe])],64)}var de=a(_,[["render",ie]]);export{de as default};
diff --git a/assets/userinterface.html.9d008bb5.js b/assets/userinterface.html.d4a7f7f6.js
similarity index 97%
rename from assets/userinterface.html.9d008bb5.js
rename to assets/userinterface.html.d4a7f7f6.js
index 3b30c1407..c17ad9a27 100644
--- a/assets/userinterface.html.9d008bb5.js
+++ b/assets/userinterface.html.d4a7f7f6.js
@@ -1 +1 @@
-import{r as o,o as r,a as n,b as e,d as a,F as s,e as i,c as l}from"./app.f6cb3ed9.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const d={},p=e("h1",{id:"exploring-the-user-interface",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#exploring-the-user-interface","aria-hidden":"true"},"#"),i(" Exploring the user interface")],-1),h=i("If you have not worked with Microsoft Visual Studio Code before, we recommend you orient yourself reviewing the editor's "),u={href:"https://code.visualstudio.com/docs/getstarted/tips-and-tricks",target:"_blank",rel:"noopener noreferrer"},f=i("Get Started"),m=i(" sections first."),g=l("
                      Then get familiar with the following key user interface capabilities and views that are most relevant for working with COBOL, PL/I, HLASM, REXX, and JCL program files:
                      • Activity bar: Groups different views. You can click the icons on the bar a second time to hide its views.
                      • Status bar: Displays the active Zowe CLI profile being used for z/OS actions such resolving remote include files or running user builds. It will pick profiles listed in user settings first, if not found any default RSE API profiles available next, and if not found the default z/OSMF profiles.
                      • File explorer: Manages your projects and files.
                      • Search: Provides various search capabilities.
                      • Git: Manages changes to the repository. This is the default SCM tool.
                      • Zowe Explorer: Lets you interact with z/OS.
                      • Problems: Displays errors of files. You can open the Problems view via the View menu or by clicking the error and warning icons in the editor status bar at the bottom.
                      • Terminal: Provides a command line interface that you can use to type any shell command, including advanced Git commands and Zowe Command Line operations to interact with z/OS. You can open the terminal through the Terminal menu or by pressing Ctrl+` (Windows and Mac).
                      • Edit and Selection: Provides essential operations for editing.
                      • Go: Provides essential navigation controls.
                      ",2);function _(v,w){const t=o("ExternalLinkIcon");return r(),n(s,null,[p,e("p",null,[h,e("a",u,[f,a(t)]),m]),g],64)}var x=c(d,[["render",_]]);export{x as default};
+import{r as o,o as r,a as n,b as e,d as a,F as s,e as i,c as l}from"./app.daa93c96.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const d={},p=e("h1",{id:"exploring-the-user-interface",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#exploring-the-user-interface","aria-hidden":"true"},"#"),i(" Exploring the user interface")],-1),h=i("If you have not worked with Microsoft Visual Studio Code before, we recommend you orient yourself reviewing the editor's "),u={href:"https://code.visualstudio.com/docs/getstarted/tips-and-tricks",target:"_blank",rel:"noopener noreferrer"},f=i("Get Started"),m=i(" sections first."),g=l("
                      Then get familiar with the following key user interface capabilities and views that are most relevant for working with COBOL, PL/I, HLASM, REXX, and JCL program files:
                      • Activity bar: Groups different views. You can click the icons on the bar a second time to hide its views.
                      • Status bar: Displays the active Zowe CLI profile being used for z/OS actions such resolving remote include files or running user builds. It will pick profiles listed in user settings first, if not found any default RSE API profiles available next, and if not found the default z/OSMF profiles.
                      • File explorer: Manages your projects and files.
                      • Search: Provides various search capabilities.
                      • Git: Manages changes to the repository. This is the default SCM tool.
                      • Zowe Explorer: Lets you interact with z/OS.
                      • Problems: Displays errors of files. You can open the Problems view via the View menu or by clicking the error and warning icons in the editor status bar at the bottom.
                      • Terminal: Provides a command line interface that you can use to type any shell command, including advanced Git commands and Zowe Command Line operations to interact with z/OS. You can open the terminal through the Terminal menu or by pressing Ctrl+` (Windows and Mac).
                      • Edit and Selection: Provides essential operations for editing.
                      • Go: Provides essential navigation controls.
                      ",2);function _(v,w){const t=o("ExternalLinkIcon");return r(),n(s,null,[p,e("p",null,[h,e("a",u,[f,a(t)]),m]),g],64)}var x=c(d,[["render",_]]);export{x as default};
diff --git a/assets/using_code_snippets.html.424b0956.js b/assets/using_code_snippets.html.7cb84f6c.js
similarity index 97%
rename from assets/using_code_snippets.html.424b0956.js
rename to assets/using_code_snippets.html.7cb84f6c.js
index a80dd0d18..e9e5e8d04 100644
--- a/assets/using_code_snippets.html.424b0956.js
+++ b/assets/using_code_snippets.html.7cb84f6c.js
@@ -1 +1 @@
-import{c as e}from"./app.f6cb3ed9.js";import{_ as o}from"./plugin-vue_export-helper.21dcd24c.js";const t={},c=e('
                       Explore code snippets
                      If you would like to explore using code snippets, you can add some complexity to this exercise. For instance, you can make the Customer File a VSAM file. The editor provides a full list of VSAM statments that can be inserted into your code. To start, you can navigate to the File Control section of SAM1.cbl, then F1, select Insert Snippet, then enter VSAM in the Search bar. You will see a list of VSAM snippets. Scroll to the VSAM: KSDS Select/Assign Clause snippet and hit Enter. A pre-formatted SELECT/ASSIGN clause will be inserted. Notice that hitting the TAB key will send the cursor to each variable/operand that needs to be defined.
                      From there, you can use the OPEN, READ, WRITE, REWRITE, and CLOSE VSAM snippets where appropriate.
                      You can also explore using subsystem snippets, such as CICS, IMS, and DB2. For instance, you need to create another COBOL subroutine which will be called by SAM1 to make DB2 updates. You can create a new file in your COBOL folder named SAM3.cbl, then insert the model subroutine snippet (Search for Model) which will give you a template for a new subroutine program. You can explore the various Embedded SQL snippets by searching for SQL in the list. You can insert code to declare a cursor, open a cursor, select records, update, etc. There is even a snippet for a generic DB2 error handling routine.
                      If you need to modify a CICS program, you can search for CICS snippets and you will notice all of the EXEC CICS statements available. Likewise, for IMS, you will see options for the many Working-Storage definition areas, as well as CALL statements with the many different functions available.
                      ',5);function d(a,n){return c}var i=o(t,[["render",d]]);export{i as default};
+import{c as e}from"./app.daa93c96.js";import{_ as o}from"./plugin-vue_export-helper.21dcd24c.js";const t={},c=e('
                       Explore code snippets
                      If you would like to explore using code snippets, you can add some complexity to this exercise. For instance, you can make the Customer File a VSAM file. The editor provides a full list of VSAM statments that can be inserted into your code. To start, you can navigate to the File Control section of SAM1.cbl, then F1, select Insert Snippet, then enter VSAM in the Search bar. You will see a list of VSAM snippets. Scroll to the VSAM: KSDS Select/Assign Clause snippet and hit Enter. A pre-formatted SELECT/ASSIGN clause will be inserted. Notice that hitting the TAB key will send the cursor to each variable/operand that needs to be defined.
                      From there, you can use the OPEN, READ, WRITE, REWRITE, and CLOSE VSAM snippets where appropriate.
                      You can also explore using subsystem snippets, such as CICS, IMS, and DB2. For instance, you need to create another COBOL subroutine which will be called by SAM1 to make DB2 updates. You can create a new file in your COBOL folder named SAM3.cbl, then insert the model subroutine snippet (Search for Model) which will give you a template for a new subroutine program. You can explore the various Embedded SQL snippets by searching for SQL in the list. You can insert code to declare a cursor, open a cursor, select records, update, etc. There is even a snippet for a generic DB2 error handling routine.
                      If you need to modify a CICS program, you can search for CICS snippets and you will notice all of the EXEC CICS statements available. Likewise, for IMS, you will see options for the many Working-Storage definition areas, as well as CALL statements with the many different functions available.
                      ',5);function d(a,n){return c}var i=o(t,[["render",d]]);export{i as default};
diff --git a/assets/uss-search-log-files.7b27b27c.png b/assets/uss-search-log-files.7b27b27c.png
new file mode 100644
index 000000000..0314a8be4
Binary files /dev/null and b/assets/uss-search-log-files.7b27b27c.png differ
diff --git a/assets/web-based-with-theia.html.e4c1a862.js b/assets/web-based-with-theia.html.80701632.js
similarity index 99%
rename from assets/web-based-with-theia.html.e4c1a862.js
rename to assets/web-based-with-theia.html.80701632.js
index d39815ce8..81ea75f4c 100644
--- a/assets/web-based-with-theia.html.e4c1a862.js
+++ b/assets/web-based-with-theia.html.80701632.js
@@ -1,4 +1,4 @@
-import{r as s,o as i,a as r,b as o,d as t,F as l,e,c as a}from"./app.f6cb3ed9.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const c={},h=o("h1",{id:"running-ibm-z\xAE-open-editor-in-the-browser-with-eclipse-theia",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#running-ibm-z\xAE-open-editor-in-the-browser-with-eclipse-theia","aria-hidden":"true"},"#"),e(" Running IBM Z\xAE Open Editor in the browser with Eclipse Theia")],-1),p=o("blockquote",null,[o("p",null,[e("by Peter Haumer."),o("br"),e(" Last updated: 4 December 2019")])],-1),u=e("VS Code has become so popular that there are other editors out there now that provide a compatibility API to also consume VS Code extensions. One of the most popular ones is the web-based "),m={href:"https://theia-ide.org/",target:"_blank",rel:"noopener noreferrer"},_=e("Eclipse Theia"),b=e(". Theia is also the default editor for the container-based "),g={href:"https://www.eclipse.org/che/",target:"_blank",rel:"noopener noreferrer"},f=e("Eclipse Che"),v=e(" platform as well. Hence, we develop IBM Z Open Editor not only for VS Code, but also Theia, which opens our editor up for an even larger community than VS Code already provides. In fact, Z Open Editor has actually evolved out of a Theia extension that we introduced in 2018. For more details, see the "),w={href:"https://www.youtube.com/watch?v=0XbfLBIoL0E",target:"_blank",rel:"noopener noreferrer"},k=e("Overview"),y=e(" or a "),x={href:"https://www.youtube.com/watch?v=pOulh-9OzT8",target:"_blank",rel:"noopener noreferrer"},T=e("demo showing both user experiences"),I=e("."),E=o("h2",{id:"api-compatibility",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#api-compatibility","aria-hidden":"true"},"#"),e(" API compatibility")],-1),O=e("Theia strives for full compatibility of the VS Code APIs. As Theia and VS Code evolve, the Theia team is keeping track of the status of the VS Code API implementation in Theia "),Z={href:"https://che-incubator.github.io/vscode-theia-comparator/status.html",target:"_blank",rel:"noopener noreferrer"},C=e("here"),S=e(". If new issues are found, the team accepts issue reports "),B={href:"https://github.com/eclipse-theia/theia/labels/vscode",target:"_blank",rel:"noopener noreferrer"},D=e("here"),q=e(" using the tag vscode."),V=a('
                       Building Theia and running IBM Z Open Editor in it
                      In this article, we will show you three different ways of building Theia and running it with IBM Z Open Editor and optionally Zowe Explorer that gives you access to z/OS\xAE resources:
                      1. Load it from npmjs.org
                      2. Load a Docker container
                      3. Build Theia from source
                      ',3),L=e("To run IBM Z Open Editor and optionally Zowe Explorer with Theia, you must first download the vsix file(s) of "),j={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},A=e("IBM Z Open Editor VS Code extension"),z=e(" and optionally "),N={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},M=e("Zowe Explorer VS Code extension"),P=e(' from the VS Code Marketplace using the "Download Extension" link on the right.'),F=o("h3",{id:"alternative-1-load-it-from-npmjs-org",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#alternative-1-load-it-from-npmjs-org","aria-hidden":"true"},"#"),e(" Alternative 1: Load it from npmjs.org")],-1),W=e("If you want to try out the user experience for editing COBOL or PL/I code in a browser, you can build a Theia editor instance with our extension on your development machine easily and then run the Theia web server from the command line window. The main prerequisite is to have "),Y={href:"https://nodejs.org/en/download/releases/",target:"_blank",rel:"noopener noreferrer"},$=e("Node.js V10"),R=e(" (not newer) and "),H={href:"https://yarnpkg.com/lang/en/",target:"_blank",rel:"noopener noreferrer"},G=e("yarn"),J=e(" installed on your development machine. It can run on Linux, Windows, or macOS."),U=e("Follow the "),X={href:"https://theia-ide.org/docs/composing_applications/",target:"_blank",rel:"noopener noreferrer"},K=e("instructions here"),Q=e(" to build a Theia instance using Node and Yarn with the two modifications described below."),ee=a(`
                    2. After pasting the contents for the package.json file, add the following additional entries into the dependencies object:
                       "@theia/plugin-dev": "next",
+import{r as s,o as i,a as r,b as o,d as t,F as l,e,c as a}from"./app.daa93c96.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const c={},h=o("h1",{id:"running-ibm-z\xAE-open-editor-in-the-browser-with-eclipse-theia",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#running-ibm-z\xAE-open-editor-in-the-browser-with-eclipse-theia","aria-hidden":"true"},"#"),e(" Running IBM Z\xAE Open Editor in the browser with Eclipse Theia")],-1),p=o("blockquote",null,[o("p",null,[e("by Peter Haumer."),o("br"),e(" Last updated: 4 December 2019")])],-1),u=e("VS Code has become so popular that there are other editors out there now that provide a compatibility API to also consume VS Code extensions. One of the most popular ones is the web-based "),m={href:"https://theia-ide.org/",target:"_blank",rel:"noopener noreferrer"},_=e("Eclipse Theia"),b=e(". Theia is also the default editor for the container-based "),g={href:"https://www.eclipse.org/che/",target:"_blank",rel:"noopener noreferrer"},f=e("Eclipse Che"),v=e(" platform as well. Hence, we develop IBM Z Open Editor not only for VS Code, but also Theia, which opens our editor up for an even larger community than VS Code already provides. In fact, Z Open Editor has actually evolved out of a Theia extension that we introduced in 2018. For more details, see the "),w={href:"https://www.youtube.com/watch?v=0XbfLBIoL0E",target:"_blank",rel:"noopener noreferrer"},k=e("Overview"),y=e(" or a "),x={href:"https://www.youtube.com/watch?v=pOulh-9OzT8",target:"_blank",rel:"noopener noreferrer"},T=e("demo showing both user experiences"),I=e("."),E=o("h2",{id:"api-compatibility",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#api-compatibility","aria-hidden":"true"},"#"),e(" API compatibility")],-1),O=e("Theia strives for full compatibility of the VS Code APIs. As Theia and VS Code evolve, the Theia team is keeping track of the status of the VS Code API implementation in Theia "),Z={href:"https://che-incubator.github.io/vscode-theia-comparator/status.html",target:"_blank",rel:"noopener noreferrer"},C=e("here"),S=e(". If new issues are found, the team accepts issue reports "),B={href:"https://github.com/eclipse-theia/theia/labels/vscode",target:"_blank",rel:"noopener noreferrer"},D=e("here"),q=e(" using the tag vscode."),V=a('
                       Building Theia and running IBM Z Open Editor in it
                      In this article, we will show you three different ways of building Theia and running it with IBM Z Open Editor and optionally Zowe Explorer that gives you access to z/OS\xAE resources:
                      1. Load it from npmjs.org
                      2. Load a Docker container
                      3. Build Theia from source
                      ',3),L=e("To run IBM Z Open Editor and optionally Zowe Explorer with Theia, you must first download the vsix file(s) of "),j={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},A=e("IBM Z Open Editor VS Code extension"),z=e(" and optionally "),N={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},M=e("Zowe Explorer VS Code extension"),P=e(' from the VS Code Marketplace using the "Download Extension" link on the right.'),F=o("h3",{id:"alternative-1-load-it-from-npmjs-org",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#alternative-1-load-it-from-npmjs-org","aria-hidden":"true"},"#"),e(" Alternative 1: Load it from npmjs.org")],-1),W=e("If you want to try out the user experience for editing COBOL or PL/I code in a browser, you can build a Theia editor instance with our extension on your development machine easily and then run the Theia web server from the command line window. The main prerequisite is to have "),Y={href:"https://nodejs.org/en/download/releases/",target:"_blank",rel:"noopener noreferrer"},$=e("Node.js V10"),R=e(" (not newer) and "),H={href:"https://yarnpkg.com/lang/en/",target:"_blank",rel:"noopener noreferrer"},G=e("yarn"),J=e(" installed on your development machine. It can run on Linux, Windows, or macOS."),U=e("Follow the "),X={href:"https://theia-ide.org/docs/composing_applications/",target:"_blank",rel:"noopener noreferrer"},K=e("instructions here"),Q=e(" to build a Theia instance using Node and Yarn with the two modifications described below."),ee=a(`
                    3. After pasting the contents for the package.json file, add the following additional entries into the dependencies object:
                       "@theia/plugin-dev": "next",
  "@theia/plugin-ext-vscode": "next"
 
                      As the name indicates, these commands will add VS Code Extension compatibility.
                    4. Then, use the plain yarn command to build everything.
                    5. Create a folder called plugins in the directory where you built Theia, and drop the downloaded vsix file(s) into that folder.
                    6. Start Theia with this augmented command:
                      yarn theia start --plugins=local-dir:./plugins
 
                      7. `,4),oe=e("Now open a web browser and navigate to "),ne={href:"http://localhost:3000",target:"_blank",rel:"noopener noreferrer"},te=e("http://localhost:3000"),ae=e("."),se=a(`
                      Theia will now load and you can create a workspace directory on your local drive with COBOL or PL/I files with Z Open Editor language support. If you also downloaded the Zowe Explorer VS Code extension, you can see the stylized Z icon on the left that you can click to see the Data Set, USS, and JES viewers.
                      Done. It is that easy.
                      If you are looking for code samples to try, clone our sample repository with the following command and open that folder by clicking File > Open....
                      git clone https://github.com/IBM/zopeneditor-sample.git
diff --git a/assets/whats-new-120.html.a46d7959.js b/assets/whats-new-120.html.6fee15fa.js
similarity index 99%
rename from assets/whats-new-120.html.a46d7959.js
rename to assets/whats-new-120.html.6fee15fa.js
index 52e321999..59eac4baf 100644
--- a/assets/whats-new-120.html.a46d7959.js
+++ b/assets/whats-new-120.html.6fee15fa.js
@@ -1 +1 @@
-import{r as s,o as a,a as i,b as o,d as t,w as l,F as d,e,c as h}from"./app.f6cb3ed9.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";var p="/zopeneditor-about/assets/remote-file-conversion.7896e76c.png",u="/zopeneditor-about/assets/welcome-page.fda6a575.png";const f={},_=o("h1",{id:"scaling-up-the-audience-with-ibm-z-open-editor-and-wazi-developer-1-2-0",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#scaling-up-the-audience-with-ibm-z-open-editor-and-wazi-developer-1-2-0","aria-hidden":"true"},"#"),e(" Scaling up the audience with IBM Z Open Editor and Wazi Developer 1.2.0")],-1),g=o("blockquote",null,[o("p",null,[e("by Peter Haumer"),o("br"),e(" 18 March 2021")])],-1),m=e("IBM Z\xAE Open Editor 1.2, together with its companion application Zowe\u2122 Explorer 1.13, and its packaging in IBM\xAE Wazi Developer 1.2 are available now. This is already our eighth major release since we started publishing the editor in the "),w={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},b=e("VS Code Marketplace"),v=e(" in September 2019. Since then, Z Open Editor has been installed almost 28.000 times by Enterprise Application developers and students from 85 different countries. We continue to add new features and refine the user experience based on the feedback we are getting. Therefore, several of the major capabilities added in this new release are some of the most frequently asked about enhancements, as well as address areas where we saw new users struggling. We hope that these capabilities will be attractive to users who have not considered our editor, yet. Here is a quick overview of the highlights."),y=o("h2",{id:"added-rexx-as-a-new-language",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#added-rexx-as-a-new-language","aria-hidden":"true"},"#"),e(" Added REXX as a new language")],-1),k=e("We set out devising Z Open Editor with the vision of creating a great editing experience for z/OS\xAE Enterprise languages that is really attractive to the next generation of developers. As we see big adoption numbers though educational offerings such as IBM's Master the Mainframe and the Open Mainframe Project's COBOL training classes, we also hear from experienced enterprise developers who use the editor and Zowe Explorer in their day-to-day activities. One request we heard from the experienced audience over and over is: can you support "),x={href:"https://www.ibm.com/docs/en/zos/2.4.0?topic=tsoe-zos-rexx-users-guide",target:"_blank",rel:"noopener noreferrer"},E=e("REXX"),z=e("?"),I=o("p",null,"With Z Open Editor 1.2, we are proud to announce that we are now shipping an all-new language server for REXX that gives you all the capabilities you expect: syntax errors and highlighting, code completion, outline view, navigate variable references etc. Plus, for all the enhancements that we added in the previous and current release around executing TSO and Unix commands for the IBM RSE API Plug-in for Zowe CLI, you can use them for your REXX development directly because they seamlessly integrate into the editor environment as a CLI.",-1),O=e("Our REXX support was realized by following the open "),S={href:"https://langserver.org",target:"_blank",rel:"noopener noreferrer"},C=e("language server"),B=e(" protocol, just like our language support for COBOL, PL/I and High-Level Assembler. Therefore, we are also able to ship it with our flagship offering "),Z={href:"https://www.ibm.com/products/developer-for-zos",target:"_blank",rel:"noopener noreferrer"},W=e("IBM Developer for z/OS 15.0.1"),M=e(" at the same time giving developers the choice of using either a VS Code or Eclipse-based editing experience for REXX."),R=e("To learn all about our REXX support, read our dedicated "),L={href:"https://ibm.github.io/zopeneditor-about/Blog/announcing-rexx.html",target:"_blank",rel:"noopener noreferrer"},T=e("Blog post"),D=e(" and "),A=o("a",{href:"../Docs/tutorial_rexx"},"Tutorial",-1),P=e("."),X=o("h2",{id:"full-support-of-international-ebcdic-code-pages-for-all-operations",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#full-support-of-international-ebcdic-code-pages-for-all-operations","aria-hidden":"true"},"#"),e(" Full support of international EBCDIC code pages for all operations")],-1),F=o("p",null,"Another frequent request from developers is better support for code page conversions. Because Z Open Editor and Zowe Explorer pull program files from z/OS to edit them locally, the program files will be converted to UTF-8 and converted back to EBCDIC when written back. Particularly for MVS\u2122, international users were asking for more options configuring the EBCDIC code pages to convert from and to.",-1),V=e("In previous releases of Zowe CLI, Zowe Explorer, and RSE API CLI plug-in, we added a parameter to specify the encoding to be used with your "),j={href:"https://docs.zowe.org/stable/web_help/index.html?p=zowe_profiles_create_zosmf-profile",target:"_blank",rel:"noopener noreferrer"},q=e("CLI profile"),N=e(" as well as specific "),H={href:"https://docs.zowe.org/stable/web_help/index.html?p=zowe_zos-files_upload_file-to-data-set",target:"_blank",rel:"noopener noreferrer"},U=e("upload"),Y=e(" and "),G={href:"https://docs.zowe.org/stable/web_help/index.html?p=zowe_zos-files_download_data-set",target:"_blank",rel:"noopener noreferrer"},K=e("download"),J=e(" commands. These parameters are available to z/OSMF as well as RSE API users. However, they only covered a subset of use cases that people were telling us about. What if you uploaded whole directories with a mix of program and binary files or what if you had data sets using different code pages?"),Q=h('
                      Converted special characters
                      Fig. 1: Z Open Editor converting special characters for EBCDIC code pages for remote MVS copybooks
                      With Z Open Editor 1.2, we added special support for conversions with RSE API that allows you to configure conversion mappings based on various criteria such as based on local file name extensions or the names of the data set, using wildcards, you are interacting with. You can define such mapping rules on the organizational level as server defaults, on a project-level by managing the mappings files with your source code, for example in an SCM, as well as individual level by having a mapping file in your home directory. This will allow you to define different code pages for data sets used only by you versus data sets used by a team or project down to the member name level including mapping files as binary versus text.
                      Conversion mappings can be used for all z/OS MVS interactions in Z Open Editor, Zowe Explorer, and RSE API CLI plug-in. For example, when you open a file in Zowe Explorer via an RSE API profile, when you resolve copybooks in COBOL programs using a remote property group, or executing a script using RSE API CLI plug-in commands. We also provide a similar mapping concept for USS when running Dependency-Based Builds using our User Build operations.
                      To learn more about conversion mappings, see this new RSE API CLI blog post for this release as well as our detailed documentation page.
                       A new onboarding experience for new developers
                      For this release, we also had another look at typical stumbling blocks for new users. Particularly, the areas of ensuring the correct prerequisites are installed and configured on the developer's machine as well as Zowe CLI profiles are created and configured. We also see that users might either not be aware or have problems with correctly configuring property groups for resolving include files and copybooks.
                      We decided to add a wizard in this release that welcomes new users, checks the installation and prerequisites, and makes recommendations for fixing. Plus, it provides pointers for getting started with various capabilities as well as how to provide feedback or ask questions. The Welcome page will open automatically the first time you install or upgrade to 1.2 and you can choose to disable or continue to see it at startup.
                      Z Open Editor Welcome page
                      Fig. 2: The new Welcome page for Z Open Editor 1.2
                       Better support for teams working on different platforms
                      Another area we saw users run into trouble with using include file resolution was specifying path and file names for include files, especially when different team members were working on different platforms. For example, a Windows user creating a COBOL copybook using a lowercase file name on the file system and in Git but referring to it in their programs with an uppercase spelling. This worked fine on case-insensitive Windows, but a user running Z Open Editor in Red Hat\xAE CodeReady Workspaces would see errors as the underlying Linux\xAE file system is case sensitive.
                      ',10),$=e("We changed the behavior of Z Open Editor to be case-insensitive by default now, but also added the option for developers or teams to make Z Open Editor "),ee=e("enforce the right casing"),oe=e(" as well. This is recommended to avoid potential issues such as files being created with the same name, but different cases in the same folder on Linux, which could lead to ambiguous behavior for COBOL copy statements."),te=o("h2",{id:"added-more-flexible-ways-to-deploy-in-your-organization",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#added-more-flexible-ways-to-deploy-in-your-organization","aria-hidden":"true"},"#"),e(" Added more flexible ways to deploy in your organization")],-1),re=o("p",null,"In addition to new product features, we are also addressing feedback about deploying our solutions in client organizations.",-1),se=e("We added more ways of getting our solution components by publishing our RSE API Zowe CLI plug-in in the public "),ne={href:"https://www.npmjs.com/package/@ibm/rse-api-for-zowe-cli",target:"_blank",rel:"noopener noreferrer"},ae=e("npmjs.com"),ie=e(" registry that allows you now to install the plug-in with a simple "),le=o("code",null,"zowe plugins install @ibm/rse-api-for-zowe-cli",-1),de=e(" command without the need to first download and extract the plug-in from the IBM site. Although, this option of downloading from the IBM site is still available as well."),he=e("We are also started publishing Z Open Editor at "),ce={href:"https://open-vsx.org/extension/IBM/zopeneditor",target:"_blank",rel:"noopener noreferrer"},pe=e("open-vsx.org"),ue=e(", which is an alternative to the Microsoft Marketplace that is based on open source software. open-vsx.org is now the default for other open source editors in which Z Open Editor can run such as "),fe={href:"https://theia-ide.org",target:"_blank",rel:"noopener noreferrer"},_e=e("Eclipse Theia"),ge=e(" or "),me={href:"https://vscodium.com",target:"_blank",rel:"noopener noreferrer"},we=e("VSCodium"),be=e(". Furthermore, organizations can install and host their "),ve={href:"https://github.com/eclipse/openvsx/wiki/Deploying-Open-VSX",target:"_blank",rel:"noopener noreferrer"},ye=e("own Open VSX servers"),ke=e(" in-house allowing them to have full control over which extensions developers can install and which not."),xe=e("We also improved the way that users can migrate to new releases of our IBM Wazi Developer for Workspaces offering more easily by allowing them to subscribe to simple OpenShift\xAE update feeds that that will "),Ee={href:"https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/2.3/html/installation_guide/upgrading-codeready-workspaces_crw",target:"_blank",rel:"noopener noreferrer"},ze=e("deploy the new versions of Wazi Developer and CodeReady Workspaces"),Ie=e(" and migrate their workspaces."),Oe=o("h2",{id:"new-ways-to-try-our-solutions",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#new-ways-to-try-our-solutions","aria-hidden":"true"},"#"),e(" New ways to try our solutions")],-1),Se=o("p",null,"Finally, we have new and improved ways of trying our solutions for evaluations.",-1),Ce=e('We provide a new version of the \u201CBring Your Own (BYO) IDE for Cloud Native Development" '),Be={href:"https://www.ibm.com/it-infrastructure/z/software-trials",target:"_blank",rel:"noopener noreferrer"},Ze=e("Z Trial"),We=e(" that walks you through a complete lifecycle and development pipeline with either VS Code or Eclipse-based tools."),Me=e("You can also easily try Red Hat OpenShift and CodeReady Workspaces with Z Open Editor and Zowe Explorer. To do that, sign-up for a trial account here at "),Re={href:"https://developers.redhat.com/developer-sandbox",target:"_blank",rel:"noopener noreferrer"},Le=e("https://developers.redhat.com/developer-sandbox"),Te=e(". This will give you access to OpenShift as well CodeReady Workspaces (check the docs and video on that site for details). Once you have CodeReady Workspaces up, you can just follow the instructions here in our public GitHub for deploying Z Open Editor and Zowe Explorer: "),De={href:"https://github.com/IBM/zopeneditor-about/tree/master/che",target:"_blank",rel:"noopener noreferrer"},Ae=e("https://github.com/IBM/zopeneditor-about/tree/master/che"),Pe=e(". To use a mainframe, you could create an account with Master the Mainframe and connect that via a Zowe profile."),Xe=e("Finally, we want to mention for developers who use "),Fe={href:"https://docs.zowe.org/stable/user-guide/sdks-using.html",target:"_blank",rel:"noopener noreferrer"},Ve=e("Zowe SDKs"),je=e(" to create their own developments tools that you can now also try the Zowe SDK with RSE API Plug-in for Zowe CLI as well. We have created a very simple example here that uses the TSO SDK showing how you can write Node.js scripts that use z/OSMF as well as RSE API interchangeably to execute TSE commands programmatically: "),qe={href:"https://github.com/phaumer/zowe-cli-tso-rse-sample",target:"_blank",rel:"noopener noreferrer"},Ne=e("https://github.com/phaumer/zowe-cli-tso-rse-sample"),He=e(". Let us know if you would like to see more example such as these."),Ue=e("We hope you enjoy all these new capabilities in IBM Z Open Editor and IBM Wazi Developer. Visit our site for more detailed information and to provide us with feedback on "),Ye={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},Ge=e("GitHub"),Ke=e(" or our "),Je={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/groups/topic-home/discussions?communitykey=856d8833-1c7c-4322-bf62-0644edb577e4&tab=discussions",target:"_blank",rel:"noopener noreferrer"},Qe=e("Wazi Developer Community page"),$e=e(".");function eo(oo,to){const r=s("ExternalLinkIcon"),n=s("RouterLink");return a(),i(d,null,[_,g,o("p",null,[m,o("a",w,[b,t(r)]),v]),y,o("p",null,[k,o("a",x,[E,t(r)]),z]),I,o("p",null,[O,o("a",S,[C,t(r)]),B,o("a",Z,[W,t(r)]),M]),o("p",null,[R,o("a",L,[T,t(r)]),D,A,P]),X,F,o("p",null,[V,o("a",j,[q,t(r)]),N,o("a",H,[U,t(r)]),Y,o("a",G,[K,t(r)]),J]),Q,o("p",null,[$,t(n,{to:"/Docs/setting_propertygroup.html#enforcing-case-sensitive-file-name-matching"},{default:l(()=>[ee]),_:1}),oe]),te,re,o("p",null,[se,o("a",ne,[ae,t(r)]),ie,le,de]),o("p",null,[he,o("a",ce,[pe,t(r)]),ue,o("a",fe,[_e,t(r)]),ge,o("a",me,[we,t(r)]),be,o("a",ve,[ye,t(r)]),ke]),o("p",null,[xe,o("a",Ee,[ze,t(r)]),Ie]),Oe,Se,o("p",null,[Ce,o("a",Be,[Ze,t(r)]),We]),o("p",null,[Me,o("a",Re,[Le,t(r)]),Te,o("a",De,[Ae,t(r)]),Pe]),o("p",null,[Xe,o("a",Fe,[Ve,t(r)]),je,o("a",qe,[Ne,t(r)]),He]),o("p",null,[Ue,o("a",Ye,[Ge,t(r)]),Ke,o("a",Je,[Qe,t(r)]),$e])],64)}var no=c(f,[["render",eo]]);export{no as default};
+import{r as s,o as a,a as i,b as o,d as t,w as l,F as d,e,c as h}from"./app.daa93c96.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";var p="/zopeneditor-about/assets/remote-file-conversion.7896e76c.png",u="/zopeneditor-about/assets/welcome-page.fda6a575.png";const f={},_=o("h1",{id:"scaling-up-the-audience-with-ibm-z-open-editor-and-wazi-developer-1-2-0",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#scaling-up-the-audience-with-ibm-z-open-editor-and-wazi-developer-1-2-0","aria-hidden":"true"},"#"),e(" Scaling up the audience with IBM Z Open Editor and Wazi Developer 1.2.0")],-1),g=o("blockquote",null,[o("p",null,[e("by Peter Haumer"),o("br"),e(" 18 March 2021")])],-1),m=e("IBM Z\xAE Open Editor 1.2, together with its companion application Zowe\u2122 Explorer 1.13, and its packaging in IBM\xAE Wazi Developer 1.2 are available now. This is already our eighth major release since we started publishing the editor in the "),w={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},b=e("VS Code Marketplace"),v=e(" in September 2019. Since then, Z Open Editor has been installed almost 28.000 times by Enterprise Application developers and students from 85 different countries. We continue to add new features and refine the user experience based on the feedback we are getting. Therefore, several of the major capabilities added in this new release are some of the most frequently asked about enhancements, as well as address areas where we saw new users struggling. We hope that these capabilities will be attractive to users who have not considered our editor, yet. Here is a quick overview of the highlights."),y=o("h2",{id:"added-rexx-as-a-new-language",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#added-rexx-as-a-new-language","aria-hidden":"true"},"#"),e(" Added REXX as a new language")],-1),k=e("We set out devising Z Open Editor with the vision of creating a great editing experience for z/OS\xAE Enterprise languages that is really attractive to the next generation of developers. As we see big adoption numbers though educational offerings such as IBM's Master the Mainframe and the Open Mainframe Project's COBOL training classes, we also hear from experienced enterprise developers who use the editor and Zowe Explorer in their day-to-day activities. One request we heard from the experienced audience over and over is: can you support "),x={href:"https://www.ibm.com/docs/en/zos/2.4.0?topic=tsoe-zos-rexx-users-guide",target:"_blank",rel:"noopener noreferrer"},E=e("REXX"),z=e("?"),I=o("p",null,"With Z Open Editor 1.2, we are proud to announce that we are now shipping an all-new language server for REXX that gives you all the capabilities you expect: syntax errors and highlighting, code completion, outline view, navigate variable references etc. Plus, for all the enhancements that we added in the previous and current release around executing TSO and Unix commands for the IBM RSE API Plug-in for Zowe CLI, you can use them for your REXX development directly because they seamlessly integrate into the editor environment as a CLI.",-1),O=e("Our REXX support was realized by following the open "),S={href:"https://langserver.org",target:"_blank",rel:"noopener noreferrer"},C=e("language server"),B=e(" protocol, just like our language support for COBOL, PL/I and High-Level Assembler. Therefore, we are also able to ship it with our flagship offering "),Z={href:"https://www.ibm.com/products/developer-for-zos",target:"_blank",rel:"noopener noreferrer"},W=e("IBM Developer for z/OS 15.0.1"),M=e(" at the same time giving developers the choice of using either a VS Code or Eclipse-based editing experience for REXX."),R=e("To learn all about our REXX support, read our dedicated "),L={href:"https://ibm.github.io/zopeneditor-about/Blog/announcing-rexx.html",target:"_blank",rel:"noopener noreferrer"},T=e("Blog post"),D=e(" and "),A=o("a",{href:"../Docs/tutorial_rexx"},"Tutorial",-1),P=e("."),X=o("h2",{id:"full-support-of-international-ebcdic-code-pages-for-all-operations",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#full-support-of-international-ebcdic-code-pages-for-all-operations","aria-hidden":"true"},"#"),e(" Full support of international EBCDIC code pages for all operations")],-1),F=o("p",null,"Another frequent request from developers is better support for code page conversions. Because Z Open Editor and Zowe Explorer pull program files from z/OS to edit them locally, the program files will be converted to UTF-8 and converted back to EBCDIC when written back. Particularly for MVS\u2122, international users were asking for more options configuring the EBCDIC code pages to convert from and to.",-1),V=e("In previous releases of Zowe CLI, Zowe Explorer, and RSE API CLI plug-in, we added a parameter to specify the encoding to be used with your "),j={href:"https://docs.zowe.org/stable/web_help/index.html?p=zowe_profiles_create_zosmf-profile",target:"_blank",rel:"noopener noreferrer"},q=e("CLI profile"),N=e(" as well as specific "),H={href:"https://docs.zowe.org/stable/web_help/index.html?p=zowe_zos-files_upload_file-to-data-set",target:"_blank",rel:"noopener noreferrer"},U=e("upload"),Y=e(" and "),G={href:"https://docs.zowe.org/stable/web_help/index.html?p=zowe_zos-files_download_data-set",target:"_blank",rel:"noopener noreferrer"},K=e("download"),J=e(" commands. These parameters are available to z/OSMF as well as RSE API users. However, they only covered a subset of use cases that people were telling us about. What if you uploaded whole directories with a mix of program and binary files or what if you had data sets using different code pages?"),Q=h('
                      Converted special characters
                      Fig. 1: Z Open Editor converting special characters for EBCDIC code pages for remote MVS copybooks
                      With Z Open Editor 1.2, we added special support for conversions with RSE API that allows you to configure conversion mappings based on various criteria such as based on local file name extensions or the names of the data set, using wildcards, you are interacting with. You can define such mapping rules on the organizational level as server defaults, on a project-level by managing the mappings files with your source code, for example in an SCM, as well as individual level by having a mapping file in your home directory. This will allow you to define different code pages for data sets used only by you versus data sets used by a team or project down to the member name level including mapping files as binary versus text.
                      Conversion mappings can be used for all z/OS MVS interactions in Z Open Editor, Zowe Explorer, and RSE API CLI plug-in. For example, when you open a file in Zowe Explorer via an RSE API profile, when you resolve copybooks in COBOL programs using a remote property group, or executing a script using RSE API CLI plug-in commands. We also provide a similar mapping concept for USS when running Dependency-Based Builds using our User Build operations.
                      To learn more about conversion mappings, see this new RSE API CLI blog post for this release as well as our detailed documentation page.
                       A new onboarding experience for new developers
                      For this release, we also had another look at typical stumbling blocks for new users. Particularly, the areas of ensuring the correct prerequisites are installed and configured on the developer's machine as well as Zowe CLI profiles are created and configured. We also see that users might either not be aware or have problems with correctly configuring property groups for resolving include files and copybooks.
                      We decided to add a wizard in this release that welcomes new users, checks the installation and prerequisites, and makes recommendations for fixing. Plus, it provides pointers for getting started with various capabilities as well as how to provide feedback or ask questions. The Welcome page will open automatically the first time you install or upgrade to 1.2 and you can choose to disable or continue to see it at startup.
                      Z Open Editor Welcome page
                      Fig. 2: The new Welcome page for Z Open Editor 1.2
                       Better support for teams working on different platforms
                      Another area we saw users run into trouble with using include file resolution was specifying path and file names for include files, especially when different team members were working on different platforms. For example, a Windows user creating a COBOL copybook using a lowercase file name on the file system and in Git but referring to it in their programs with an uppercase spelling. This worked fine on case-insensitive Windows, but a user running Z Open Editor in Red Hat\xAE CodeReady Workspaces would see errors as the underlying Linux\xAE file system is case sensitive.
                      ',10),$=e("We changed the behavior of Z Open Editor to be case-insensitive by default now, but also added the option for developers or teams to make Z Open Editor "),ee=e("enforce the right casing"),oe=e(" as well. This is recommended to avoid potential issues such as files being created with the same name, but different cases in the same folder on Linux, which could lead to ambiguous behavior for COBOL copy statements."),te=o("h2",{id:"added-more-flexible-ways-to-deploy-in-your-organization",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#added-more-flexible-ways-to-deploy-in-your-organization","aria-hidden":"true"},"#"),e(" Added more flexible ways to deploy in your organization")],-1),re=o("p",null,"In addition to new product features, we are also addressing feedback about deploying our solutions in client organizations.",-1),se=e("We added more ways of getting our solution components by publishing our RSE API Zowe CLI plug-in in the public "),ne={href:"https://www.npmjs.com/package/@ibm/rse-api-for-zowe-cli",target:"_blank",rel:"noopener noreferrer"},ae=e("npmjs.com"),ie=e(" registry that allows you now to install the plug-in with a simple "),le=o("code",null,"zowe plugins install @ibm/rse-api-for-zowe-cli",-1),de=e(" command without the need to first download and extract the plug-in from the IBM site. Although, this option of downloading from the IBM site is still available as well."),he=e("We are also started publishing Z Open Editor at "),ce={href:"https://open-vsx.org/extension/IBM/zopeneditor",target:"_blank",rel:"noopener noreferrer"},pe=e("open-vsx.org"),ue=e(", which is an alternative to the Microsoft Marketplace that is based on open source software. open-vsx.org is now the default for other open source editors in which Z Open Editor can run such as "),fe={href:"https://theia-ide.org",target:"_blank",rel:"noopener noreferrer"},_e=e("Eclipse Theia"),ge=e(" or "),me={href:"https://vscodium.com",target:"_blank",rel:"noopener noreferrer"},we=e("VSCodium"),be=e(". Furthermore, organizations can install and host their "),ve={href:"https://github.com/eclipse/openvsx/wiki/Deploying-Open-VSX",target:"_blank",rel:"noopener noreferrer"},ye=e("own Open VSX servers"),ke=e(" in-house allowing them to have full control over which extensions developers can install and which not."),xe=e("We also improved the way that users can migrate to new releases of our IBM Wazi Developer for Workspaces offering more easily by allowing them to subscribe to simple OpenShift\xAE update feeds that that will "),Ee={href:"https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/2.3/html/installation_guide/upgrading-codeready-workspaces_crw",target:"_blank",rel:"noopener noreferrer"},ze=e("deploy the new versions of Wazi Developer and CodeReady Workspaces"),Ie=e(" and migrate their workspaces."),Oe=o("h2",{id:"new-ways-to-try-our-solutions",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#new-ways-to-try-our-solutions","aria-hidden":"true"},"#"),e(" New ways to try our solutions")],-1),Se=o("p",null,"Finally, we have new and improved ways of trying our solutions for evaluations.",-1),Ce=e('We provide a new version of the \u201CBring Your Own (BYO) IDE for Cloud Native Development" '),Be={href:"https://www.ibm.com/it-infrastructure/z/software-trials",target:"_blank",rel:"noopener noreferrer"},Ze=e("Z Trial"),We=e(" that walks you through a complete lifecycle and development pipeline with either VS Code or Eclipse-based tools."),Me=e("You can also easily try Red Hat OpenShift and CodeReady Workspaces with Z Open Editor and Zowe Explorer. To do that, sign-up for a trial account here at "),Re={href:"https://developers.redhat.com/developer-sandbox",target:"_blank",rel:"noopener noreferrer"},Le=e("https://developers.redhat.com/developer-sandbox"),Te=e(". This will give you access to OpenShift as well CodeReady Workspaces (check the docs and video on that site for details). Once you have CodeReady Workspaces up, you can just follow the instructions here in our public GitHub for deploying Z Open Editor and Zowe Explorer: "),De={href:"https://github.com/IBM/zopeneditor-about/tree/master/che",target:"_blank",rel:"noopener noreferrer"},Ae=e("https://github.com/IBM/zopeneditor-about/tree/master/che"),Pe=e(". To use a mainframe, you could create an account with Master the Mainframe and connect that via a Zowe profile."),Xe=e("Finally, we want to mention for developers who use "),Fe={href:"https://docs.zowe.org/stable/user-guide/sdks-using.html",target:"_blank",rel:"noopener noreferrer"},Ve=e("Zowe SDKs"),je=e(" to create their own developments tools that you can now also try the Zowe SDK with RSE API Plug-in for Zowe CLI as well. We have created a very simple example here that uses the TSO SDK showing how you can write Node.js scripts that use z/OSMF as well as RSE API interchangeably to execute TSE commands programmatically: "),qe={href:"https://github.com/phaumer/zowe-cli-tso-rse-sample",target:"_blank",rel:"noopener noreferrer"},Ne=e("https://github.com/phaumer/zowe-cli-tso-rse-sample"),He=e(". Let us know if you would like to see more example such as these."),Ue=e("We hope you enjoy all these new capabilities in IBM Z Open Editor and IBM Wazi Developer. Visit our site for more detailed information and to provide us with feedback on "),Ye={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},Ge=e("GitHub"),Ke=e(" or our "),Je={href:"https://community.ibm.com/community/user/ibmz-and-linuxone/groups/topic-home/discussions?communitykey=856d8833-1c7c-4322-bf62-0644edb577e4&tab=discussions",target:"_blank",rel:"noopener noreferrer"},Qe=e("Wazi Developer Community page"),$e=e(".");function eo(oo,to){const r=s("ExternalLinkIcon"),n=s("RouterLink");return a(),i(d,null,[_,g,o("p",null,[m,o("a",w,[b,t(r)]),v]),y,o("p",null,[k,o("a",x,[E,t(r)]),z]),I,o("p",null,[O,o("a",S,[C,t(r)]),B,o("a",Z,[W,t(r)]),M]),o("p",null,[R,o("a",L,[T,t(r)]),D,A,P]),X,F,o("p",null,[V,o("a",j,[q,t(r)]),N,o("a",H,[U,t(r)]),Y,o("a",G,[K,t(r)]),J]),Q,o("p",null,[$,t(n,{to:"/Docs/setting_propertygroup.html#enforcing-case-sensitive-file-name-matching"},{default:l(()=>[ee]),_:1}),oe]),te,re,o("p",null,[se,o("a",ne,[ae,t(r)]),ie,le,de]),o("p",null,[he,o("a",ce,[pe,t(r)]),ue,o("a",fe,[_e,t(r)]),ge,o("a",me,[we,t(r)]),be,o("a",ve,[ye,t(r)]),ke]),o("p",null,[xe,o("a",Ee,[ze,t(r)]),Ie]),Oe,Se,o("p",null,[Ce,o("a",Be,[Ze,t(r)]),We]),o("p",null,[Me,o("a",Re,[Le,t(r)]),Te,o("a",De,[Ae,t(r)]),Pe]),o("p",null,[Xe,o("a",Fe,[Ve,t(r)]),je,o("a",qe,[Ne,t(r)]),He]),o("p",null,[Ue,o("a",Ye,[Ge,t(r)]),Ke,o("a",Je,[Qe,t(r)]),$e])],64)}var no=c(f,[["render",eo]]);export{no as default};
diff --git a/assets/whatsnew.html.2392e1ae.js b/assets/whatsnew.html.2392e1ae.js
new file mode 100644
index 000000000..7f0c3dd34
--- /dev/null
+++ b/assets/whatsnew.html.2392e1ae.js
@@ -0,0 +1 @@
+import{r as s,o as r,a as l,b as e,d as n,F as a,e as t}from"./app.daa93c96.js";import{_ as i}from"./plugin-vue_export-helper.21dcd24c.js";const d={},h=e("h1",{id:"updates-and-user-feedback",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#updates-and-user-feedback","aria-hidden":"true"},"#"),t(" Updates and user feedback")],-1),c=e("p",null,"IBM Z\xAE Open Editor and its related components are on continuous delivery. Check out the following resources to stay current:",-1),_=e("h2",{id:"versions-and-change-logs",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#versions-and-change-logs","aria-hidden":"true"},"#"),t(" Versions and change logs")],-1),u=e("thead",null,[e("tr",null,[e("th",null,"Component"),e("th",null,"Current version"),e("th",null,"Release date"),e("th",null,"Download"),e("th",null,"Change log")])],-1),p=e("td",null,"IBM Z Open Editor",-1),m=e("td",null,"4.5.0",-1),f=e("td",null,"19\xA0September 2024",-1),b={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},g=t("VS Code Marketplace"),k={href:"https://marketplace.visualstudio.com/items/IBM.zopeneditor/changelog",target:"_blank",rel:"noopener noreferrer"},w=t("Change log on VS Code Marketplace"),v=e("td",null,"IBM\xAE RSE API Plug-in for Zowe\u2122 CLI",-1),y=e("td",null,"4.5.0",-1),C=e("td",null,"19\xA0September 2024",-1),z={href:"https://www.npmjs.com/package/@ibm/rse-api-for-zowe-cli",target:"_blank",rel:"noopener noreferrer"},I=t("NPMjs"),M={href:"https://marketplace.visualstudio.com/items/IBM.zopeneditor/changelog",target:"_blank",rel:"noopener noreferrer"},x=t("Change log on VS Code Marketplace"),S=e("td",null,"Zowe Explorer",-1),B=e("td",null,"2.18.0",-1),V=e("td",null,"5\xA0September 2024",-1),Z={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},E=t("VS Code Marketplace"),N={href:"https://marketplace.visualstudio.com/items/Zowe.vscode-extension-for-zowe/changelog",target:"_blank",rel:"noopener noreferrer"},A=t("Change log on VS Code Marketplace"),L=e("td",null,"Zowe CLI",-1),O=e("td",null,"7.29.1",-1),G=e("td",null,"September 2024",-1),P={href:"https://docs.zowe.org/stable/user-guide/cli-installcli.html#methods-to-install-zowe-cli",target:"_blank",rel:"noopener noreferrer"},H=t("Zowe website"),j={href:"https://github.com/zowe/zowe-cli/blob/master/packages/cli/CHANGELOG.md",target:"_blank",rel:"noopener noreferrer"},F=t("Change log on Zowe CLI repository"),R=e("h2",{id:"other-updates-and-user-feedback",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#other-updates-and-user-feedback","aria-hidden":"true"},"#"),t(" Other updates and user feedback")],-1),q=t("Visit the "),D={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},K=t("GitHub repository"),T=t(" for the latest updates and to provide feedback."),U=t("Visit the "),Y={href:"https://ibm.github.io/zopeneditor-about/",target:"_blank",rel:"noopener noreferrer"},J=t("About page"),Q=t(" regularly for new resources such as blog posts or demo videos."),W=e("li",null,[e("p",null,[t("See "),e("a",{href:"./knownissues"},"Known issues and limitations"),t(" in this online help.")])],-1),X=t("See the GitHub Issues list for new open items that are filed by the community as well as previously "),$={href:"https://github.com/IBM/zopeneditor-about/issues?q=is%3Aissue+is%3Aclosed+sort%3Aupdated-desc",target:"_blank",rel:"noopener noreferrer"},ee=t("resolved items"),te=t("."),oe=t("Provide feedback by filling in a "),ne={href:"https://ibm.biz/zopeneditor-feedback",target:"_blank",rel:"noopener noreferrer"},se=t("short survey"),re=t(". Z Open Editor will also prompt you 30 days after installation to submit this survey via a pop-up dialog. You can ask the dialog to remind you again or to not prompt you anymore until you update to a new version of Z Open Editor.");function le(ae,ie){const o=s("ExternalLinkIcon");return r(),l(a,null,[h,c,_,e("table",null,[u,e("tbody",null,[e("tr",null,[p,m,f,e("td",null,[e("a",b,[g,n(o)])]),e("td",null,[e("a",k,[w,n(o)])])]),e("tr",null,[v,y,C,e("td",null,[e("a",z,[I,n(o)])]),e("td",null,[e("a",M,[x,n(o)])])]),e("tr",null,[S,B,V,e("td",null,[e("a",Z,[E,n(o)])]),e("td",null,[e("a",N,[A,n(o)])])]),e("tr",null,[L,O,G,e("td",null,[e("a",P,[H,n(o)])]),e("td",null,[e("a",j,[F,n(o)])])])])]),R,e("ul",null,[e("li",null,[e("p",null,[q,e("a",D,[K,n(o)]),T])]),e("li",null,[e("p",null,[U,e("a",Y,[J,n(o)]),Q])]),W,e("li",null,[e("p",null,[X,e("a",$,[ee,n(o)]),te])]),e("li",null,[e("p",null,[oe,e("a",ne,[se,n(o)]),re])])])],64)}var ce=i(d,[["render",le]]);export{ce as default};
diff --git a/assets/whatsnew.html.320005e4.js b/assets/whatsnew.html.320005e4.js
deleted file mode 100644
index 3fecfc0b7..000000000
--- a/assets/whatsnew.html.320005e4.js
+++ /dev/null
@@ -1 +0,0 @@
-const e={key:"v-37f5df26",path:"/Docs/whatsnew.html",title:"Updates and user feedback",lang:"en-US",frontmatter:{},excerpt:"",headers:[{level:1,title:"Updates and user feedback",slug:"updates-and-user-feedback",children:[{level:2,title:"Versions and change logs",slug:"versions-and-change-logs",children:[]},{level:2,title:"Other updates and user feedback",slug:"other-updates-and-user-feedback",children:[]}]}],git:{updatedTime:172304606e4,contributors:[{name:"Peter Haumer",email:"4391934+phaumer@users.noreply.github.com",commits:11},{name:"Peter Haumer",email:"phaumer@us.ibm.com",commits:7},{name:"Lauren Li",email:"Lauren.Li@ibm.com",commits:6},{name:"PETER HAUMER",email:"phaumer@us.ibm.com",commits:5},{name:"Min Huang",email:"minhsh@cn.ibm.com",commits:3},{name:"Hestia Zhang",email:"Hestia.Zhang@ibm.com",commits:1},{name:"Lauren Li",email:"45975633+lauren-li@users.noreply.github.com",commits:1},{name:"Prasang-A-Prajapati",email:"Prasang.A.Prajapati@ibm.com",commits:1}]},filePathRelative:"Docs/whatsnew.md"};export{e as data};
diff --git a/assets/whatsnew.html.98bdcc78.js b/assets/whatsnew.html.98bdcc78.js
new file mode 100644
index 000000000..bf29cb3b0
--- /dev/null
+++ b/assets/whatsnew.html.98bdcc78.js
@@ -0,0 +1 @@
+const e={key:"v-37f5df26",path:"/Docs/whatsnew.html",title:"Updates and user feedback",lang:"en-US",frontmatter:{},excerpt:"",headers:[{level:1,title:"Updates and user feedback",slug:"updates-and-user-feedback",children:[{level:2,title:"Versions and change logs",slug:"versions-and-change-logs",children:[]},{level:2,title:"Other updates and user feedback",slug:"other-updates-and-user-feedback",children:[]}]}],git:{updatedTime:1726695456e3,contributors:[{name:"Peter Haumer",email:"4391934+phaumer@users.noreply.github.com",commits:11},{name:"Peter Haumer",email:"phaumer@us.ibm.com",commits:7},{name:"Lauren Li",email:"Lauren.Li@ibm.com",commits:6},{name:"PETER HAUMER",email:"phaumer@us.ibm.com",commits:6},{name:"Min Huang",email:"minhsh@cn.ibm.com",commits:3},{name:"Hestia Zhang",email:"Hestia.Zhang@ibm.com",commits:1},{name:"Lauren Li",email:"45975633+lauren-li@users.noreply.github.com",commits:1},{name:"Prasang-A-Prajapati",email:"Prasang.A.Prajapati@ibm.com",commits:1}]},filePathRelative:"Docs/whatsnew.md"};export{e as data};
diff --git a/assets/whatsnew.html.e3e857ff.js b/assets/whatsnew.html.e3e857ff.js
deleted file mode 100644
index d4154043a..000000000
--- a/assets/whatsnew.html.e3e857ff.js
+++ /dev/null
@@ -1 +0,0 @@
-import{r as s,o as r,a as l,b as e,d as n,F as a,e as t}from"./app.f6cb3ed9.js";import{_ as i}from"./plugin-vue_export-helper.21dcd24c.js";const d={},h=e("h1",{id:"updates-and-user-feedback",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#updates-and-user-feedback","aria-hidden":"true"},"#"),t(" Updates and user feedback")],-1),c=e("p",null,"IBM Z\xAE Open Editor and its related components are on continuous delivery. Check out the following resources to stay current:",-1),_=e("h2",{id:"versions-and-change-logs",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#versions-and-change-logs","aria-hidden":"true"},"#"),t(" Versions and change logs")],-1),u=e("thead",null,[e("tr",null,[e("th",null,"Component"),e("th",null,"Current version"),e("th",null,"Release date"),e("th",null,"Download"),e("th",null,"Change log")])],-1),p=e("td",null,"IBM Z Open Editor",-1),f=e("td",null,"4.4.0",-1),g=e("td",null,"12\xA0August 2024",-1),m={href:"https://marketplace.visualstudio.com/items?itemName=IBM.zopeneditor",target:"_blank",rel:"noopener noreferrer"},b=t("VS Code Marketplace"),k={href:"https://marketplace.visualstudio.com/items/IBM.zopeneditor/changelog",target:"_blank",rel:"noopener noreferrer"},w=t("Change log on VS Code Marketplace"),v=e("td",null,"IBM\xAE RSE API Plug-in for Zowe\u2122 CLI",-1),y=e("td",null,"4.4.0",-1),C=e("td",null,"12\xA0August 2024",-1),z={href:"https://www.npmjs.com/package/@ibm/rse-api-for-zowe-cli",target:"_blank",rel:"noopener noreferrer"},I=t("NPMjs"),M={href:"https://marketplace.visualstudio.com/items/IBM.zopeneditor/changelog",target:"_blank",rel:"noopener noreferrer"},x=t("Change log on VS Code Marketplace"),B=e("td",null,"Zowe Explorer",-1),V=e("td",null,"2.17.0",-1),Z=e("td",null,"23\xA0July 2024",-1),E={href:"https://marketplace.visualstudio.com/items?itemName=Zowe.vscode-extension-for-zowe",target:"_blank",rel:"noopener noreferrer"},A=t("VS Code Marketplace"),S={href:"https://marketplace.visualstudio.com/items/Zowe.vscode-extension-for-zowe/changelog",target:"_blank",rel:"noopener noreferrer"},N=t("Change log on VS Code Marketplace"),L=e("td",null,"Zowe CLI",-1),O=e("td",null,"7.26.1",-1),G=e("td",null,"11\xA0June 2024",-1),P={href:"https://docs.zowe.org/stable/user-guide/cli-installcli.html#methods-to-install-zowe-cli",target:"_blank",rel:"noopener noreferrer"},H=t("Zowe website"),j={href:"https://github.com/zowe/zowe-cli/blob/master/packages/cli/CHANGELOG.md",target:"_blank",rel:"noopener noreferrer"},F=t("Change log on Zowe CLI repository"),J=e("h2",{id:"other-updates-and-user-feedback",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#other-updates-and-user-feedback","aria-hidden":"true"},"#"),t(" Other updates and user feedback")],-1),R=t("Visit the "),q={href:"https://github.com/IBM/zopeneditor-about/issues",target:"_blank",rel:"noopener noreferrer"},D=t("GitHub repository"),K=t(" for the latest updates and to provide feedback."),T=t("Visit the "),U={href:"https://ibm.github.io/zopeneditor-about/",target:"_blank",rel:"noopener noreferrer"},Y=t("About page"),Q=t(" regularly for new resources such as blog posts or demo videos."),W=e("li",null,[e("p",null,[t("See "),e("a",{href:"./knownissues"},"Known issues and limitations"),t(" in this online help.")])],-1),X=t("See the GitHub Issues list for new open items that are filed by the community as well as previously "),$={href:"https://github.com/IBM/zopeneditor-about/issues?q=is%3Aissue+is%3Aclosed+sort%3Aupdated-desc",target:"_blank",rel:"noopener noreferrer"},ee=t("resolved items"),te=t("."),oe=t("Provide feedback by filling in a "),ne={href:"https://ibm.biz/zopeneditor-feedback",target:"_blank",rel:"noopener noreferrer"},se=t("short survey"),re=t(". Z Open Editor will also prompt you 30 days after installation to submit this survey via a pop-up dialog. You can ask the dialog to remind you again or to not prompt you anymore until you update to a new version of Z Open Editor.");function le(ae,ie){const o=s("ExternalLinkIcon");return r(),l(a,null,[h,c,_,e("table",null,[u,e("tbody",null,[e("tr",null,[p,f,g,e("td",null,[e("a",m,[b,n(o)])]),e("td",null,[e("a",k,[w,n(o)])])]),e("tr",null,[v,y,C,e("td",null,[e("a",z,[I,n(o)])]),e("td",null,[e("a",M,[x,n(o)])])]),e("tr",null,[B,V,Z,e("td",null,[e("a",E,[A,n(o)])]),e("td",null,[e("a",S,[N,n(o)])])]),e("tr",null,[L,O,G,e("td",null,[e("a",P,[H,n(o)])]),e("td",null,[e("a",j,[F,n(o)])])])])]),J,e("ul",null,[e("li",null,[e("p",null,[R,e("a",q,[D,n(o)]),K])]),e("li",null,[e("p",null,[T,e("a",U,[Y,n(o)]),Q])]),W,e("li",null,[e("p",null,[X,e("a",$,[ee,n(o)]),te])]),e("li",null,[e("p",null,[oe,e("a",ne,[se,n(o)]),re])])])],64)}var ce=i(d,[["render",le]]);export{ce as default};
diff --git a/assets/zapp.html.e15d90b5.js b/assets/zapp.html.7b153c97.js
similarity index 99%
rename from assets/zapp.html.e15d90b5.js
rename to assets/zapp.html.7b153c97.js
index dfd024d65..787a2bcee 100644
--- a/assets/zapp.html.e15d90b5.js
+++ b/assets/zapp.html.7b153c97.js
@@ -1,4 +1,4 @@
-import{r,o as p,a as l,b as n,d as s,w as o,F as c,e,c as i}from"./app.f6cb3ed9.js";import{_ as u}from"./plugin-vue_export-helper.21dcd24c.js";const d={},h=n("h1",{id:"configuring-your-applications-with-zapp-files",tabindex:"-1"},[n("a",{class:"header-anchor",href:"#configuring-your-applications-with-zapp-files","aria-hidden":"true"},"#"),e(" Configuring your applications with ZAPP files")],-1),m=n("p",null,"Using ZAPP (Z APPlication) files is a new approach for simplifying how developers and teams of developers can configure their application code for editing in IBM Z\xAE Open Editor. As VS Code settings only provide limited support for editing highly structured data, typing JSON structures is highly error prone, as well as users in the past got easily confused managing the many settings for all the extensions installed into VS Code all in one central place, we decided to introduce a new configuration file specifically for z/OS Enterprise applications.",-1),f=n("p",null,[e("We created the new notion of a ZAPP file that describes your application in an independent representation, as YAML files as well as alternatively JSON. This file can be managed with your source code in an SCM and can be used by various editors and command-line tools in the future. This makes it possible, for example, for property groups to be reused outside of VS Code and used with other editors or IDEs, as well as even for command-line operations for building your programs and other similar use cases. The vision is for ZAPP files to become as useful for z/OS\xAE Enterprise Applications as Maven POM (Project Object Models) are for Java\u2122 or "),n("code",null,"package.json"),e(" files are for Node.js.")],-1),b=n("p",null,"Although this early version of ZAPP supports only a few Z Open Editor use cases, we are hoping that with feedback from the user community, we can evolve them over time by adding more specification items, supporting more tools, adding a command-line interface, and so on. Then, at some point we would like to provide extensibility APIs and open specifications that others can use to contribute to ZAPP as well.",-1),y=n("h2",{id:"zapp-use-cases",tabindex:"-1"},[n("a",{class:"header-anchor",href:"#zapp-use-cases","aria-hidden":"true"},"#"),e(" ZAPP use cases")],-1),g=n("p",null,"This early version of ZAPP is intended to provide a first impression to some of the ideas and to gather feedback. ZAPP files can currently be used to specify the following configurations:",-1),k=n("strong",null,"Property Groups for finding local or remote include files",-1),w=e(" providing a complete alternative to settings described in the section "),_=e("Setting property groups"),v=e("."),P=n("li",null,[n("strong",null,"Property Groups for defining language-specific compiler options"),e(" that impact how the IBM\xAE language servers interpret source code.")],-1),A=n("strong",null,"Code pages mappings for RSE API",-1),S=e(" defining mappings for file name patterns to how they should be uploaded to and downloaded from MVS, which is fully documented in the section "),x=e("MVS EBCDIC code pages and mappings files"),z=e("."),q=n("strong",null,"User build",-1),O=e(" for building your programs currently edited in Z Open Editor remotely with the IBM Dependency Based Build offering. (You can find detailed documentation for this feature in "),M={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-building-cobol-pli-hlasm-programs-user-build",target:"_blank",rel:"noopener noreferrer"},Z=e("IBM Documentation"),I=e(")."),B=n("strong",null,"Preprocessor support",-1),E=e(" to specify command lines for executing a preprocessor in the background and integrating the output with the editor. See more details in "),Y=e("Advanced Capabilities: Preprocessor support"),C=e("."),L=n("li",null,[n("strong",null,"Test case specification"),e(" utilized by IBM's z/OS test automation tools portfolio.")],-1),T=n("h2",{id:"getting-started-with-zapp-files",tabindex:"-1"},[n("a",{class:"header-anchor",href:"#getting-started-with-zapp-files","aria-hidden":"true"},"#"),e(" Getting started with ZAPP files")],-1),R=e("When you open a COBOL, PL/I, HLASM, or REXX program for the first time from a VS Code workspace and you do not have a ZAPP file, Z Open Editor will automatically create a "),V=n("code",null,"zapp.yaml",-1),N=e(" file for you. The file can be located in the top-level folder of your workspace. If you are using "),D={href:"https://code.visualstudio.com/docs/editor/multi-root-workspaces",target:"_blank",rel:"noopener noreferrer"},j=e("multi-root workspaces"),U=e(", you can find it in your first workspace. You can move the file to any other of your workspaces, but it must be located in the top-level folder. In case of multi-root workspaces, this file will search all directories in all your workspaces for the include files. For very large workspaces, the searching can slow down the editor's performance. Therefore, you are encouraged to edit the file after its creation to narrow down the location of the include files as described in "),H=e("Setting property groups"),F=e("."),G=i("
                      The top-level folder is the directory that typically contains your .git directory if you are using Git, and/or the top-level directory that you would open in VS Code with File > Open.... This directory typically contains your .vscode directory in which your workspace settings can be stored. Previously, this directory was also the home for property groups and user build settings that now need to be stored in ZAPP files instead. In case of a multi-root workspace setup, each workspace can have a ZAPP file and they can be used in combination with each other; for example, the include files defined in the ZAPP file of one workspace can be used by program files in another. See the details in the respective sections.
                      You can disable the automatic creation of the ZAPP file by setting zopeneditor.zapp.generateZappOnDemand to false. You can manually create a ZAPP file in your development workspace by going to File > New Text File.
                      You can choose to edit your ZAPP file as a YAML file or as a JSON file and create a file with either of the following names in your top-level directory. The file must be named exactly like that to enable YAML or JSON editors to recognize the schema to be used for validation.
                      • zapp.yaml
                      • zapp.json
                      ",4),J=e("If you decide to use YAML, which is the recommended format as it easier to write than JSON, you are suggested to install the "),W={href:"https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml",target:"_blank",rel:"noopener noreferrer"},$=e("Red Hat YAML VS Code Extension"),X=e(". This VS Code extension provides code completion, documentation, and formatting features, which are useful for ZAPP. Z Open Editor can recognize the installation of the Red Hat YAML extension automatically and configure the ZAPP schema for this extension in your VS Code user settings. Note, if you also have the Red Hat Ansible VS Code extension installed make sure that the language selected in VS Code for the ZAPP files is YAML and not Ansible, as both use the file extensions .yml and .yaml and you have tell the editor, which language is being edited."),K=n("p",null,"In addition, code snippets for ZAPP in YAML are provided, which makes you productive instantaneously. If you use JSON, the default VS Code JSON editor also provides code completion and formatting, but currently there are no snippets included in Z Open Editor. However, you could create your own custom snippets.",-1),Q=e("When Z Open Editor starts up it checks if the Red Hat YAML extension is installed. If it is, the editor will add links to the ZAPP JSON schema that is used for the YAML editor for validation automatically. If this extension is not installed, Z Open Editor will only add a schema link to the JSON editor. To verify that Z Open Editor has configured itself to work with the Red Hat YAML extension or VS Code JSON, look for entries as shown below in your VS Code user settings. The entries should be added after opening Z Open Editor. There might be other schema entries listed here such as the links to Z Open Editor's "),ee=e("zcodeformat"),ne=e(" schema or schemata used by third party extensions."),se=i(`
                      "yaml.schemas": {
+import{r,o as p,a as l,b as n,d as s,w as o,F as c,e,c as i}from"./app.daa93c96.js";import{_ as u}from"./plugin-vue_export-helper.21dcd24c.js";const d={},h=n("h1",{id:"configuring-your-applications-with-zapp-files",tabindex:"-1"},[n("a",{class:"header-anchor",href:"#configuring-your-applications-with-zapp-files","aria-hidden":"true"},"#"),e(" Configuring your applications with ZAPP files")],-1),m=n("p",null,"Using ZAPP (Z APPlication) files is a new approach for simplifying how developers and teams of developers can configure their application code for editing in IBM Z\xAE Open Editor. As VS Code settings only provide limited support for editing highly structured data, typing JSON structures is highly error prone, as well as users in the past got easily confused managing the many settings for all the extensions installed into VS Code all in one central place, we decided to introduce a new configuration file specifically for z/OS Enterprise applications.",-1),f=n("p",null,[e("We created the new notion of a ZAPP file that describes your application in an independent representation, as YAML files as well as alternatively JSON. This file can be managed with your source code in an SCM and can be used by various editors and command-line tools in the future. This makes it possible, for example, for property groups to be reused outside of VS Code and used with other editors or IDEs, as well as even for command-line operations for building your programs and other similar use cases. The vision is for ZAPP files to become as useful for z/OS\xAE Enterprise Applications as Maven POM (Project Object Models) are for Java\u2122 or "),n("code",null,"package.json"),e(" files are for Node.js.")],-1),b=n("p",null,"Although this early version of ZAPP supports only a few Z Open Editor use cases, we are hoping that with feedback from the user community, we can evolve them over time by adding more specification items, supporting more tools, adding a command-line interface, and so on. Then, at some point we would like to provide extensibility APIs and open specifications that others can use to contribute to ZAPP as well.",-1),y=n("h2",{id:"zapp-use-cases",tabindex:"-1"},[n("a",{class:"header-anchor",href:"#zapp-use-cases","aria-hidden":"true"},"#"),e(" ZAPP use cases")],-1),g=n("p",null,"This early version of ZAPP is intended to provide a first impression to some of the ideas and to gather feedback. ZAPP files can currently be used to specify the following configurations:",-1),k=n("strong",null,"Property Groups for finding local or remote include files",-1),w=e(" providing a complete alternative to settings described in the section "),_=e("Setting property groups"),v=e("."),P=n("li",null,[n("strong",null,"Property Groups for defining language-specific compiler options"),e(" that impact how the IBM\xAE language servers interpret source code.")],-1),A=n("strong",null,"Code pages mappings for RSE API",-1),S=e(" defining mappings for file name patterns to how they should be uploaded to and downloaded from MVS, which is fully documented in the section "),x=e("MVS EBCDIC code pages and mappings files"),z=e("."),q=n("strong",null,"User build",-1),O=e(" for building your programs currently edited in Z Open Editor remotely with the IBM Dependency Based Build offering. (You can find detailed documentation for this feature in "),M={href:"https://www.ibm.com/docs/en/developer-for-zos/16.0?topic=code-building-cobol-pli-hlasm-programs-user-build",target:"_blank",rel:"noopener noreferrer"},Z=e("IBM Documentation"),I=e(")."),B=n("strong",null,"Preprocessor support",-1),E=e(" to specify command lines for executing a preprocessor in the background and integrating the output with the editor. See more details in "),Y=e("Advanced Capabilities: Preprocessor support"),C=e("."),L=n("li",null,[n("strong",null,"Test case specification"),e(" utilized by IBM's z/OS test automation tools portfolio.")],-1),T=n("h2",{id:"getting-started-with-zapp-files",tabindex:"-1"},[n("a",{class:"header-anchor",href:"#getting-started-with-zapp-files","aria-hidden":"true"},"#"),e(" Getting started with ZAPP files")],-1),R=e("When you open a COBOL, PL/I, HLASM, or REXX program for the first time from a VS Code workspace and you do not have a ZAPP file, Z Open Editor will automatically create a "),V=n("code",null,"zapp.yaml",-1),N=e(" file for you. The file can be located in the top-level folder of your workspace. If you are using "),D={href:"https://code.visualstudio.com/docs/editor/multi-root-workspaces",target:"_blank",rel:"noopener noreferrer"},j=e("multi-root workspaces"),U=e(", you can find it in your first workspace. You can move the file to any other of your workspaces, but it must be located in the top-level folder. In case of multi-root workspaces, this file will search all directories in all your workspaces for the include files. For very large workspaces, the searching can slow down the editor's performance. Therefore, you are encouraged to edit the file after its creation to narrow down the location of the include files as described in "),H=e("Setting property groups"),F=e("."),G=i("
                      The top-level folder is the directory that typically contains your .git directory if you are using Git, and/or the top-level directory that you would open in VS Code with File > Open.... This directory typically contains your .vscode directory in which your workspace settings can be stored. Previously, this directory was also the home for property groups and user build settings that now need to be stored in ZAPP files instead. In case of a multi-root workspace setup, each workspace can have a ZAPP file and they can be used in combination with each other; for example, the include files defined in the ZAPP file of one workspace can be used by program files in another. See the details in the respective sections.
                      You can disable the automatic creation of the ZAPP file by setting zopeneditor.zapp.generateZappOnDemand to false. You can manually create a ZAPP file in your development workspace by going to File > New Text File.
                      You can choose to edit your ZAPP file as a YAML file or as a JSON file and create a file with either of the following names in your top-level directory. The file must be named exactly like that to enable YAML or JSON editors to recognize the schema to be used for validation.
                      • zapp.yaml
                      • zapp.json
                      ",4),J=e("If you decide to use YAML, which is the recommended format as it easier to write than JSON, you are suggested to install the "),W={href:"https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml",target:"_blank",rel:"noopener noreferrer"},$=e("Red Hat YAML VS Code Extension"),X=e(". This VS Code extension provides code completion, documentation, and formatting features, which are useful for ZAPP. Z Open Editor can recognize the installation of the Red Hat YAML extension automatically and configure the ZAPP schema for this extension in your VS Code user settings. Note, if you also have the Red Hat Ansible VS Code extension installed make sure that the language selected in VS Code for the ZAPP files is YAML and not Ansible, as both use the file extensions .yml and .yaml and you have tell the editor, which language is being edited."),K=n("p",null,"In addition, code snippets for ZAPP in YAML are provided, which makes you productive instantaneously. If you use JSON, the default VS Code JSON editor also provides code completion and formatting, but currently there are no snippets included in Z Open Editor. However, you could create your own custom snippets.",-1),Q=e("When Z Open Editor starts up it checks if the Red Hat YAML extension is installed. If it is, the editor will add links to the ZAPP JSON schema that is used for the YAML editor for validation automatically. If this extension is not installed, Z Open Editor will only add a schema link to the JSON editor. To verify that Z Open Editor has configured itself to work with the Red Hat YAML extension or VS Code JSON, look for entries as shown below in your VS Code user settings. The entries should be added after opening Z Open Editor. There might be other schema entries listed here such as the links to Z Open Editor's "),ee=e("zcodeformat"),ne=e(" schema or schemata used by third party extensions."),se=i(`
                      "yaml.schemas": {
   "file:///Users/user1/.vscode/extensions/ibm.zopeneditor-3.0.0/resources/zapp-schema-1.0.0.json": [
     "zapp.yaml"
   ]
diff --git a/assets/zcodeformatting.html.398b7274.js b/assets/zcodeformatting.html.02d19d48.js
similarity index 99%
rename from assets/zcodeformatting.html.398b7274.js
rename to assets/zcodeformatting.html.02d19d48.js
index 8c03f1ef3..db728a6a0 100644
--- a/assets/zcodeformatting.html.398b7274.js
+++ b/assets/zcodeformatting.html.02d19d48.js
@@ -1,4 +1,4 @@
-import{r as s,o as i,a as r,b as e,d as o,F as l,e as t,c as a}from"./app.f6cb3ed9.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const p={},d=e("h1",{id:"experimental-formatting-cobol-source-code",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#experimental-formatting-cobol-source-code","aria-hidden":"true"},"#"),t(" Experimental: Formatting COBOL source code")],-1),u=e("p",null,"IBM Z\xAE Open Editor v2.1.0 or newer provides an experimental COBOL source code formatting feature that allows developers to reformat the source code of an entire file, or the currently selected portion of the file, using the VS Code formatting menus and shortcuts. The rules of formatting are determined by a set of common defaults that can be customized along many criteria. The customizations of the default formatting rules are represented in a YAML or JSON file that can be stored in a version control system with the actual source code, in order to ensure that all developers in a project perform formatting consistently.",-1),h=t("The formatting customization files are called zcodeformat. They describe your structured formatting preferences defining only the changes you want to make to the defaults. The user experience working with these files was designed to be very consistent to how you work with "),m=e("a",{href:"zapp"},"ZAPP files",-1),f=t(" in Z Open Editor, but kept separate as ZAPP focuses on application properties independent of the presentation of the code. Our vision is for zcodeformat files to become as useful for z/OS\xAE Enterprise applications as formatting is with the popular "),y={href:"https://prettier.io/",target:"_blank",rel:"noopener noreferrer"},b=t("Prettier"),g=t(" tool that is available for many other languages."),k=a('
                      Currently, this capability is only available for COBOL.
                       Formatting your COBOL files
                      To format your COBOL file (programs file or copybook) you can either
                      • format the full document via the right-click "Format Document" context menu option or via the shortcut Shift+Option+F (Mac) or Shift+Alt+F (Windows).
                      • format the currently selected text range via the right-click "Format Selection" context menu option or via the shortcut Command-K Command-F (Mac) or Ctrl-K Ctrl-F (Windows).
                       Getting started with zcodeformat files
                      Create a zcodeformat file in your development workspace, in the top-level directory that contains your .git directory if you are using git, and/or the top-level directory that you would open in VS Code with File > Open.... This directory typically also contains your .vscode directory where your workspace settings are stored.
                      Note: The current version of zcodeformat supports only single-root VS Code and Eclipse Che/RedHat\xAE CodeReady Workspaces workspaces.
                      You can choose to edit your zcodeformat file as a YAML file or a JSON file, and create a file with either of the following names in your top-level directory. Only create one of these and name it exactly as shown below, using only lowercase characters.
                      • zcodeformat.yaml
                      • zcodeformat.json
                      ',9),w=t("If you decide to use YAML, which is the recommended format, installing the "),v={href:"https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml",target:"_blank",rel:"noopener noreferrer"},_=t("Red Hat VS Code Extension"),x=t(" is also recommended. This VS Code Extension provides code completion, documentation and formatting features that are useful for zcodeformat. Z Open Editor automatically recognizes the Red Hat YAML extension installation and configures the zcodeformat schema for it in your VS Code user settings. Note, if you also have the Red Hat Ansible VS Code extension installed make sure that the language selected in VS Code for the zcodeformat files is YAML and not Ansible."),z=a(`
                      Code snippets for zcodeformat in YAML are also available and help to immediately become productive. If you use JSON, the default VS Code JSON editor also provides code completion and formatting, but there is currently no support for code snippets.
                      When Z Open Editor starts up it checks if the Red Hat YAML extension is installed. If it is, the editor will add links to the zcodeformat JSON schema that is used for the YAML editor for validation automatically. If this extension is not installed, Z Open Editor will only add a schema link to for the JSON editor. To verify that Z Open Editor has configured itself to work with the Red Hat YAML extension or VS Code JSON, look for entries as shown below in your VS Code user settings. The entries should be added after opening Z Open Editor. There might be other schema entries listed here such as the links to the ZAPP schema.
                      "yaml.schemas": {
+import{r as s,o as i,a as r,b as e,d as o,F as l,e as t,c as a}from"./app.daa93c96.js";import{_ as c}from"./plugin-vue_export-helper.21dcd24c.js";const p={},d=e("h1",{id:"experimental-formatting-cobol-source-code",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#experimental-formatting-cobol-source-code","aria-hidden":"true"},"#"),t(" Experimental: Formatting COBOL source code")],-1),u=e("p",null,"IBM Z\xAE Open Editor v2.1.0 or newer provides an experimental COBOL source code formatting feature that allows developers to reformat the source code of an entire file, or the currently selected portion of the file, using the VS Code formatting menus and shortcuts. The rules of formatting are determined by a set of common defaults that can be customized along many criteria. The customizations of the default formatting rules are represented in a YAML or JSON file that can be stored in a version control system with the actual source code, in order to ensure that all developers in a project perform formatting consistently.",-1),h=t("The formatting customization files are called zcodeformat. They describe your structured formatting preferences defining only the changes you want to make to the defaults. The user experience working with these files was designed to be very consistent to how you work with "),m=e("a",{href:"zapp"},"ZAPP files",-1),f=t(" in Z Open Editor, but kept separate as ZAPP focuses on application properties independent of the presentation of the code. Our vision is for zcodeformat files to become as useful for z/OS\xAE Enterprise applications as formatting is with the popular "),y={href:"https://prettier.io/",target:"_blank",rel:"noopener noreferrer"},b=t("Prettier"),g=t(" tool that is available for many other languages."),k=a('
                      Currently, this capability is only available for COBOL.
                       Formatting your COBOL files
                      To format your COBOL file (programs file or copybook) you can either
                      • format the full document via the right-click "Format Document" context menu option or via the shortcut Shift+Option+F (Mac) or Shift+Alt+F (Windows).
                      • format the currently selected text range via the right-click "Format Selection" context menu option or via the shortcut Command-K Command-F (Mac) or Ctrl-K Ctrl-F (Windows).
                       Getting started with zcodeformat files
                      Create a zcodeformat file in your development workspace, in the top-level directory that contains your .git directory if you are using git, and/or the top-level directory that you would open in VS Code with File > Open.... This directory typically also contains your .vscode directory where your workspace settings are stored.
                      Note: The current version of zcodeformat supports only single-root VS Code and Eclipse Che/RedHat\xAE CodeReady Workspaces workspaces.
                      You can choose to edit your zcodeformat file as a YAML file or a JSON file, and create a file with either of the following names in your top-level directory. Only create one of these and name it exactly as shown below, using only lowercase characters.
                      • zcodeformat.yaml
                      • zcodeformat.json
                      ',9),w=t("If you decide to use YAML, which is the recommended format, installing the "),v={href:"https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml",target:"_blank",rel:"noopener noreferrer"},_=t("Red Hat VS Code Extension"),x=t(" is also recommended. This VS Code Extension provides code completion, documentation and formatting features that are useful for zcodeformat. Z Open Editor automatically recognizes the Red Hat YAML extension installation and configures the zcodeformat schema for it in your VS Code user settings. Note, if you also have the Red Hat Ansible VS Code extension installed make sure that the language selected in VS Code for the zcodeformat files is YAML and not Ansible."),z=a(`
                      Code snippets for zcodeformat in YAML are also available and help to immediately become productive. If you use JSON, the default VS Code JSON editor also provides code completion and formatting, but there is currently no support for code snippets.
                      When Z Open Editor starts up it checks if the Red Hat YAML extension is installed. If it is, the editor will add links to the zcodeformat JSON schema that is used for the YAML editor for validation automatically. If this extension is not installed, Z Open Editor will only add a schema link to for the JSON editor. To verify that Z Open Editor has configured itself to work with the Red Hat YAML extension or VS Code JSON, look for entries as shown below in your VS Code user settings. The entries should be added after opening Z Open Editor. There might be other schema entries listed here such as the links to the ZAPP schema.
                      "yaml.schemas": {
   "file:///Users/user1/.vscode/extensions/ibm.zopeneditor-2.1.0/resources/zcodeformat-schema-0.0.1.json": [
     "zcodeformat.yaml"
   ]
diff --git a/assets/zopeneditor_v3.html.ee59cc1d.js b/assets/zopeneditor_v3.html.30921b7b.js
similarity index 99%
rename from assets/zopeneditor_v3.html.ee59cc1d.js
rename to assets/zopeneditor_v3.html.30921b7b.js
index cefb66458..9681a8b81 100644
--- a/assets/zopeneditor_v3.html.ee59cc1d.js
+++ b/assets/zopeneditor_v3.html.30921b7b.js
@@ -1,4 +1,4 @@
-import{r as o,o as i,a as p,b as e,d as s,w as l,F as c,c as t,e as n}from"./app.f6cb3ed9.js";import{_ as u}from"./plugin-vue_export-helper.21dcd24c.js";const d={},h=t('
                       Migrating from Z Open Editor v2 to v3
                      This page is for users migrating from IBM Z Open Editor versions 1 or 2. Z Open Editor version 3 introduces some breaking changes and the removal and replacement of a few capabilities that require manual migration steps. Review the changes below.
                      Note: If you do not want to be surprised by a VS Code automatic update for this release and/or need more time to prepare a migration, we strongly recommend that you use the VS Code setting extensions.autoUpdate and switch it to false. If you don't want VS Code to even check for updates, you can set the extensions.autoCheckUpdates setting to false. However, this also prevents updates for other VS Code extensions from being installed.
                       Features that have been removed/replaced
                      ',4),b=e("strong",null,"Support for Java 8 removed",-1),m=n(": We compiled all of our language servers with Java 11 for this version of Z Open Editor. You will no longer be able to run the editor with a Java 8 runtime. You must upgrade to a Java 11 or newer runtime. For recommendations, see our updated "),k=n("Getting Started"),g=n(" section."),f=e("strong",null,[n("Property groups will no longer be supported as VS Code settings ("),e("code",null,"zopeneditor.propertygroups"),n(")")],-1),y=n(": We made the full switch to "),_={href:"https://ibm.github.io/zopeneditor-about/Docs/zapp.html",target:"_blank",rel:"noopener noreferrer"},w=n("ZAPP files"),v=n(" in this release. You need to move all your property groups from your user settings and/or workspace settings to a ZAPP file. Also see the next section for breaking changes for ZAPP property groups."),I=e("li",null,[e("strong",null,[n("User Build workspace setting will no longer be supported as VS Code settings ("),e("code",null,"zopeneditor.userbuild.workspaceSettings"),n(")")]),n(": We also made the switch to ZAPP here. The exception will be the user settings ("),e("code",null,"zopeneditor.userbuild.userSettings"),n("). Those will remain.")],-1),S=e("h2",{id:"breaking-feature-changes",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#breaking-feature-changes","aria-hidden":"true"},"#"),n(" Breaking feature changes")],-1),q=n("In addition to moving Property Groups and User Build settings to ZAPP, we also made schema changes that require updates to existing ZAPP files. All of these changes are driven by enhancement requests from the community at "),P={href:"https://github.com/IBM/zopeneditor-about",target:"_blank",rel:"noopener noreferrer"},L=n("https://github.com/IBM/zopeneditor-about"),B=n(", IBM customers, and technical representatives that work with our customers every day. Changes in v3.0.0 represent the first increment of changes and requires breakages and manual migration. Going forward, our plan is to build on these changes in future updates, without requiring more manual migrations."),E=e("p",null,"The following changes require manual updates to your current ZAPP files:",-1),x=t(`
                    7. Renamed properties: We fixed several places in which property names did not follow YAML/JSON naming conventions. We were aware of these issues, but did not update them in order to avoid migration. However, the required migration for version 3.0.0 created the ideal opportunity to fix them. The updated keywords below need to be replaced in your ZAPP files. Note that the first three properties in the table below are currently not used by Z Open Editor capabilities. They are planned to be used in future releases to support multiple ZAPP files and define relationships.
                      Old nameNew name
                      group-idgroupId
                      artifact-idartifactId
                      parent-idparentId
                      property-groupspropertyGroups
                    8. Simplified and refactored property groups: Based on suggestions in discussion threads and issues filed in our community GitHub repository, as well as other feedback from users, we refactored the property groups. The goal was to make writing property groups simpler and avoid redundancies, such as specifying compiler options multiple times. In the new structure you can create one property group per language and provide a list to local or remote locations for it. You can still create several property groups for the same language, if you prefer to. We also simplified the nesting of the location arrays to be less complex by eliminating the special property syslib and instead making it one of the possible name values. Here is an example for a PL/I property group using the new schema:
                      propertyGroups:
+import{r as o,o as i,a as p,b as e,d as s,w as l,F as c,c as t,e as n}from"./app.daa93c96.js";import{_ as u}from"./plugin-vue_export-helper.21dcd24c.js";const d={},h=t('
                       Migrating from Z Open Editor v2 to v3
                      This page is for users migrating from IBM Z Open Editor versions 1 or 2. Z Open Editor version 3 introduces some breaking changes and the removal and replacement of a few capabilities that require manual migration steps. Review the changes below.
                      Note: If you do not want to be surprised by a VS Code automatic update for this release and/or need more time to prepare a migration, we strongly recommend that you use the VS Code setting extensions.autoUpdate and switch it to false. If you don't want VS Code to even check for updates, you can set the extensions.autoCheckUpdates setting to false. However, this also prevents updates for other VS Code extensions from being installed.
                       Features that have been removed/replaced
                      ',4),b=e("strong",null,"Support for Java 8 removed",-1),m=n(": We compiled all of our language servers with Java 11 for this version of Z Open Editor. You will no longer be able to run the editor with a Java 8 runtime. You must upgrade to a Java 11 or newer runtime. For recommendations, see our updated "),k=n("Getting Started"),g=n(" section."),f=e("strong",null,[n("Property groups will no longer be supported as VS Code settings ("),e("code",null,"zopeneditor.propertygroups"),n(")")],-1),y=n(": We made the full switch to "),_={href:"https://ibm.github.io/zopeneditor-about/Docs/zapp.html",target:"_blank",rel:"noopener noreferrer"},w=n("ZAPP files"),v=n(" in this release. You need to move all your property groups from your user settings and/or workspace settings to a ZAPP file. Also see the next section for breaking changes for ZAPP property groups."),I=e("li",null,[e("strong",null,[n("User Build workspace setting will no longer be supported as VS Code settings ("),e("code",null,"zopeneditor.userbuild.workspaceSettings"),n(")")]),n(": We also made the switch to ZAPP here. The exception will be the user settings ("),e("code",null,"zopeneditor.userbuild.userSettings"),n("). Those will remain.")],-1),S=e("h2",{id:"breaking-feature-changes",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#breaking-feature-changes","aria-hidden":"true"},"#"),n(" Breaking feature changes")],-1),q=n("In addition to moving Property Groups and User Build settings to ZAPP, we also made schema changes that require updates to existing ZAPP files. All of these changes are driven by enhancement requests from the community at "),P={href:"https://github.com/IBM/zopeneditor-about",target:"_blank",rel:"noopener noreferrer"},L=n("https://github.com/IBM/zopeneditor-about"),B=n(", IBM customers, and technical representatives that work with our customers every day. Changes in v3.0.0 represent the first increment of changes and requires breakages and manual migration. Going forward, our plan is to build on these changes in future updates, without requiring more manual migrations."),E=e("p",null,"The following changes require manual updates to your current ZAPP files:",-1),x=t(`
                    9. Renamed properties: We fixed several places in which property names did not follow YAML/JSON naming conventions. We were aware of these issues, but did not update them in order to avoid migration. However, the required migration for version 3.0.0 created the ideal opportunity to fix them. The updated keywords below need to be replaced in your ZAPP files. Note that the first three properties in the table below are currently not used by Z Open Editor capabilities. They are planned to be used in future releases to support multiple ZAPP files and define relationships.
                      Old nameNew name
                      group-idgroupId
                      artifact-idartifactId
                      parent-idparentId
                      property-groupspropertyGroups
                    10. Simplified and refactored property groups: Based on suggestions in discussion threads and issues filed in our community GitHub repository, as well as other feedback from users, we refactored the property groups. The goal was to make writing property groups simpler and avoid redundancies, such as specifying compiler options multiple times. In the new structure you can create one property group per language and provide a list to local or remote locations for it. You can still create several property groups for the same language, if you prefer to. We also simplified the nesting of the location arrays to be less complex by eliminating the special property syslib and instead making it one of the possible name values. Here is an example for a PL/I property group using the new schema:
                      propertyGroups:
   - name: pl1-includes
     language: pl1
     compilerOptions: not(!)
diff --git a/assets/zos-resources-table-member-search-results.6177dd0d.png b/assets/zos-resources-table-member-search-results.6177dd0d.png
new file mode 100644
index 000000000..6ed5bd98f
Binary files /dev/null and b/assets/zos-resources-table-member-search-results.6177dd0d.png differ
diff --git a/assets/zowe_advanced_connection_scenarious.html.083a0c71.js b/assets/zowe_advanced_connection_scenarious.html.d4ce32c4.js
similarity index 98%
rename from assets/zowe_advanced_connection_scenarious.html.083a0c71.js
rename to assets/zowe_advanced_connection_scenarious.html.d4ce32c4.js
index 004f50ec9..27ed2a8f5 100644
--- a/assets/zowe_advanced_connection_scenarious.html.083a0c71.js
+++ b/assets/zowe_advanced_connection_scenarious.html.d4ce32c4.js
@@ -1 +1 @@
-import{r as n,o as r,a as s,b as o,d as t,w as c,F as h,e,c as l}from"./app.f6cb3ed9.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const u={},p=o("h1",{id:"supported-methods-of-authentication-for-z-os-using-zowe",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#supported-methods-of-authentication-for-z-os-using-zowe","aria-hidden":"true"},"#"),e(" Supported methods of authentication for z/OS using Zowe")],-1),g=e("Zowe CLI and it's plug-ins have numerous ways available for users to authenticate and secure credentials. "),f={href:"https://docs.zowe.org/stable/user-guide/cli-using-team-managing-credential-security",target:"_blank",rel:"noopener noreferrer"},w=e("Secure credential encryption"),_=e(" is now included in Zowe CLI, storing credentials and other values set by the user to be stored securely, using the local device's credential manager."),m=e("Types of authentication supported by Zowe include passwords, passphrases, JSON web token (JWT) authentication, single sign-on (SSO), and multi-factor authentication (MFA). Zowe CLI requires "),b={href:"https://docs.zowe.org/stable/user-guide/cli-using-integrating-apiml/",target:"_blank",rel:"noopener noreferrer"},x=e("authenticating with the Zowe API Mediation Layer (ML)"),S=e(" for SSO, JWT, and MFA support."),I=l('
                      The RSE CLI plug-in supports passwords, passphrases, and JWT authentication directly with the RSE API host component. If the RSE API host component is registered with the Zowe API ML, all of the methods of authentication supported by the API ML will be available for RSE profiles as well.
                       Single sign-on support
                      After an RSE profile is created and is accessible in Zowe Explorer, users can use single sign-on (SSO) for connecting to the RSE API host component in Zowe Explorer 1.22.0 and later versions. JWTs are stored securely in the profile's file. For RSE profiles connecting directly to the RSE API, follow the steps below:
                       Logging in to authentication service
                       Zowe Explorer UI:
                      1. Right-click the profile name in the Zowe Explorer tree view and click Login to Authentication Service.
                      2. Enter credentials for z/OS connection when prompted.
                      When the login is successful, you will receive the message Login to authentication service was successful. from Zowe Explorer.
                       Zowe CLI:
                      1. In the terminal, enter the command zowe rse auth login.
                      2. Enter credentials for z/OS connection when prompted.
                      When the login is successful, you will receive a message with information about the JWT, including the expiration date and time as well as the creation date and time of it.
                       Logging out of authentication service
                       Zowe Explorer UI:
                      Right-click on the profile name in the Zowe Explorer tree view and select Logout from Authentication Service.
                      When the logoff is successful, you will receive the message Logout from authentication service was successful. from Zowe Explorer.
                       Zowe CLI:
                      In the terminal, enter the command zowe rse auth logout.
                      When the logoff is successful, you will receive the message JWT Token has been retired..
                      ',17),v=e("If you are obtaining authentication tokens from the API Mediation Layer, see "),L={href:"https://docs.zowe.org/stable/user-guide/cli-using-integrating-apiml/",target:"_blank",rel:"noopener noreferrer"},y=e("Connecting profiles to API Mediation Layer"),E=e("."),z=e("For an example of the team configuration file with RSE profile authenticating with API Mediation Layer, see "),A=e("Single sign-on support for IBM RSE CLI plugin"),Z=e("."),k=o("h2",{id:"multi-factor-authentication",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#multi-factor-authentication","aria-hidden":"true"},"#"),e(" Multi-factor authentication")],-1),M=o("p",null,'You can do multi-factor authentication (MFA) and use Zowe team configuration profiles. MFA is supprted when API Meditation Layer is enabled on the host side. Zowe Explorer supports multi-factor authentication login. Simply use your temporary code as a password or choose the "Log into Authentication Service" option.',-1);function R(P,C){const i=n("ExternalLinkIcon"),a=n("RouterLink");return r(),s(h,null,[p,o("p",null,[g,o("a",f,[w,t(i)]),_]),o("p",null,[m,o("a",b,[x,t(i)]),S]),I,o("p",null,[v,o("a",L,[y,t(i)]),E]),o("p",null,[z,t(a,{to:"/Docs/setup_integration.html#single-sign-on-support-for-ibm-rse-cli-plug-in"},{default:c(()=>[A]),_:1}),Z]),k,M],64)}var F=d(u,[["render",R]]);export{F as default};
+import{r as n,o as r,a as s,b as o,d as t,w as c,F as h,e,c as l}from"./app.daa93c96.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const u={},p=o("h1",{id:"supported-methods-of-authentication-for-z-os-using-zowe",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#supported-methods-of-authentication-for-z-os-using-zowe","aria-hidden":"true"},"#"),e(" Supported methods of authentication for z/OS using Zowe")],-1),g=e("Zowe CLI and it's plug-ins have numerous ways available for users to authenticate and secure credentials. "),f={href:"https://docs.zowe.org/stable/user-guide/cli-using-team-managing-credential-security",target:"_blank",rel:"noopener noreferrer"},w=e("Secure credential encryption"),_=e(" is now included in Zowe CLI, storing credentials and other values set by the user to be stored securely, using the local device's credential manager."),m=e("Types of authentication supported by Zowe include passwords, passphrases, JSON web token (JWT) authentication, single sign-on (SSO), and multi-factor authentication (MFA). Zowe CLI requires "),b={href:"https://docs.zowe.org/stable/user-guide/cli-using-integrating-apiml/",target:"_blank",rel:"noopener noreferrer"},x=e("authenticating with the Zowe API Mediation Layer (ML)"),S=e(" for SSO, JWT, and MFA support."),I=l('
                      The RSE CLI plug-in supports passwords, passphrases, and JWT authentication directly with the RSE API host component. If the RSE API host component is registered with the Zowe API ML, all of the methods of authentication supported by the API ML will be available for RSE profiles as well.
                       Single sign-on support
                      After an RSE profile is created and is accessible in Zowe Explorer, users can use single sign-on (SSO) for connecting to the RSE API host component in Zowe Explorer 1.22.0 and later versions. JWTs are stored securely in the profile's file. For RSE profiles connecting directly to the RSE API, follow the steps below:
                       Logging in to authentication service
                       Zowe Explorer UI:
                      1. Right-click the profile name in the Zowe Explorer tree view and click Login to Authentication Service.
                      2. Enter credentials for z/OS connection when prompted.
                      When the login is successful, you will receive the message Login to authentication service was successful. from Zowe Explorer.
                       Zowe CLI:
                      1. In the terminal, enter the command zowe rse auth login.
                      2. Enter credentials for z/OS connection when prompted.
                      When the login is successful, you will receive a message with information about the JWT, including the expiration date and time as well as the creation date and time of it.
                       Logging out of authentication service
                       Zowe Explorer UI:
                      Right-click on the profile name in the Zowe Explorer tree view and select Logout from Authentication Service.
                      When the logoff is successful, you will receive the message Logout from authentication service was successful. from Zowe Explorer.
                       Zowe CLI:
                      In the terminal, enter the command zowe rse auth logout.
                      When the logoff is successful, you will receive the message JWT Token has been retired..
                      ',17),v=e("If you are obtaining authentication tokens from the API Mediation Layer, see "),L={href:"https://docs.zowe.org/stable/user-guide/cli-using-integrating-apiml/",target:"_blank",rel:"noopener noreferrer"},y=e("Connecting profiles to API Mediation Layer"),E=e("."),z=e("For an example of the team configuration file with RSE profile authenticating with API Mediation Layer, see "),A=e("Single sign-on support for IBM RSE CLI plugin"),Z=e("."),k=o("h2",{id:"multi-factor-authentication",tabindex:"-1"},[o("a",{class:"header-anchor",href:"#multi-factor-authentication","aria-hidden":"true"},"#"),e(" Multi-factor authentication")],-1),M=o("p",null,'You can do multi-factor authentication (MFA) and use Zowe team configuration profiles. MFA is supprted when API Meditation Layer is enabled on the host side. Zowe Explorer supports multi-factor authentication login. Simply use your temporary code as a password or choose the "Log into Authentication Service" option.',-1);function R(P,C){const i=n("ExternalLinkIcon"),a=n("RouterLink");return r(),s(h,null,[p,o("p",null,[g,o("a",f,[w,t(i)]),_]),o("p",null,[m,o("a",b,[x,t(i)]),S]),I,o("p",null,[v,o("a",L,[y,t(i)]),E]),o("p",null,[z,t(a,{to:"/Docs/setup_integration.html#single-sign-on-support-for-ibm-rse-cli-plug-in"},{default:c(()=>[A]),_:1}),Z]),k,M],64)}var F=d(u,[["render",R]]);export{F as default};
diff --git a/assets/zowe_explorer_v2.html.13e8d264.js b/assets/zowe_explorer_v2.html.6cf5ba2a.js
similarity index 99%
rename from assets/zowe_explorer_v2.html.13e8d264.js
rename to assets/zowe_explorer_v2.html.6cf5ba2a.js
index 7839decd4..23c411015 100644
--- a/assets/zowe_explorer_v2.html.13e8d264.js
+++ b/assets/zowe_explorer_v2.html.6cf5ba2a.js
@@ -1,4 +1,4 @@
-import{r,o as l,a as d,b as e,d as t,w as s,F as c,e as o,c as a}from"./app.f6cb3ed9.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";const u={},p=e("h1",{id:"getting-started-with-zowe-2-0",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#getting-started-with-zowe-2-0","aria-hidden":"true"},"#"),o(" Getting started with Zowe 2.0")],-1),f=e("h2",{id:"overview",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#overview","aria-hidden":"true"},"#"),o(" Overview")],-1),g=e("p",null,"Zowe Explorer 2.0.0 and Zowe CLI 7.0.1 add profile management support via a configuration file at a global and project level. IBM Z Open Editor and IBM RSE API Plugin for Zowe CLI version 2.0.2 add full support for the profiles as well.",-1),w=e("p",null,"These new configuration files replace the old Zowe CLI v6 profiles that were storing each connection in individual files, with central files that allow defining common properties such as host names, ports, protocols only once. They also distinguish user-specific properties from properties that define generic profiles for a project managed with application source in an SCM, such as Git, that all team members share for using the same development systems. In that case, personal properties such as username and passwords would be stored for the individual users on their development clients, and all other properties in a project configuration file.",-1),m=e("p",null,"For more information regarding configuration files in Zowe CLI and Zowe Explorer v2.0.0 review",-1),_=o("The Zowe CLI overview to "),b={href:"https://docs.zowe.org/stable/user-guide/cli-using-creating-global-team-profiles/",target:"_blank",rel:"noopener noreferrer"},v=o("Using Global Profile Configuration"),x=o("Zowe Explorer's documentation on "),Z={href:"https://docs.zowe.org/stable/user-guide/ze-profiles",target:"_blank",rel:"noopener noreferrer"},y=o("using configuration files"),z=e("h2",{id:"using-v1-profiles-with-z-open-editor-and-zowe-explorer",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-v1-profiles-with-z-open-editor-and-zowe-explorer","aria-hidden":"true"},"#"),o(" Using v1 profiles with Z Open Editor and Zowe Explorer")],-1),E=e("p",null,"Zowe Explorer 2.0.0, Z Open Editor, RSE API Plugin for Zowe CLI 2.0.2 still support the use of Zowe v1 profiles. Migrating to the new config file profile management is recommended, but not required.",-1),C=e("blockquote",null,[e("p",null,"Note if a new configuration file is in place v1 profile creation and use will not be available.")],-1),I=e("p",null,"In order to use v1 Zowe profiles in Z Open Editor and Zowe Explorer, the following steps must be performed:",-1),k=e("li",null,[e("p",null,[o("Issue the following command in your terminal "),e("code",null,"zowe scs revert --force"),o(".")])],-1),L=e("li",null,[e("p",null,[o("If the secure credential store plugin is installed, remove the plugin by running the following command: "),e("code",null,"zowe plugins uninstall @zowe/secure-credential-store-for-zowe-cli"),o(".")])],-1),S=o("Update any existing zowe plugins to their latest version. See "),T=o("here"),B=o(" for the instructions."),P=e("li",null,[e("p",null,"After performing steps 1 and 2, your v1 profiles should be ready to use in Zowe Explorer and Z Open Editor after upgrading.")],-1),M=e("h2",{id:"migration-overview",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#migration-overview","aria-hidden":"true"},"#"),o(" Migration overview")],-1),O=e("h3",{id:"semi-automatic-migration-of-zowe-cli-profiles",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#semi-automatic-migration-of-zowe-cli-profiles","aria-hidden":"true"},"#"),o(" Semi-automatic migration of Zowe CLI profiles")],-1),R=o("If you wish to migrate from Zowe v1 profiles to a Zowe v2 config file, please refer to the following documentation on "),N=o("migrating profiles"),U=o("."),F=e("h3",{id:"automated-migration-of-zowe-explorer-settings-in-vs-code",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#automated-migration-of-zowe-explorer-settings-in-vs-code","aria-hidden":"true"},"#"),o(" Automated migration of Zowe Explorer settings in VS Code")],-1),A=o("Zowe explorer settings have been changed to a consistent format for easier settings management as of Zowe Explorer v2.0.0. The migration of these settings from your old to new ones are all handled automatically upon upgrading from v1 to v2, for more information regarding this change view Zowe Explorer's documentation on "),V={href:"https://github.com/zowe/zowe-explorer-vscode/blob/main/docs/early-access/v2/Extenders.md#migration-of-old-settings-to-new-standardized-settings-in-zowe-explorer",target:"_blank",rel:"noopener noreferrer"},q=o("migrating your old Zowe settings"),j=o("."),G=o("For more information on Zowe Explorer and feature changes view the "),J={href:"https://docs.zowe.org/stable/getting-started/overview",target:"_blank",rel:"noopener noreferrer"},Y=o("Zowe Explorer docs"),D=o("."),H=e("h2",{id:"creating-zowe-v2-team-configuration-files",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#creating-zowe-v2-team-configuration-files","aria-hidden":"true"},"#"),o(" Creating Zowe v2 Team configuration files")],-1),K=e("p",null,"To get started using Zowe v2 configuration profiles in IBM User Build, the following steps must be performed:",-1),Q=e("ol",null,[e("li",null,[e("p",null,[o("Create a configuration file by clicking the "),e("code",null,"+"),o(" button in Zowe Explorer's tree view, and select "),e("code",null,"Create a New Team Configuration File"),o(" when prompted in the input box shown.")])]),e("li",null,[e("p",null,"Update host, port and other information in the config file and save. Refresh Zowe Explorer by either clicking the button in the notification message shown after creation, alt+z, or the Zowe Explorer: Refresh Zowe Explorer command palette option.")])],-1),W=o("For more details, see the Zowe CLI docs on "),X={href:"https://docs.zowe.org/stable/user-guide/cli-using-creating-global-team-profiles/",target:"_blank",rel:"noopener noreferrer"},$=o("Creating a configuration file"),ee=o("."),oe=a('
                       Configure your Zowe v2 profiles for IBM User Build
                      1. Set the profile you wish to use for IBM User Build in your VS Code user settings or ZAPP settings in the following setting zopeneditor.zowe.defaultCliProfile. If the profile type z/OSMF is used, an SSH profile must be specified in the zopeneditor.zowe.defaultSshCliProfile setting.
                      2. The team configuration file should now be ready to use in IBM User Build. Test it by performing a User Build against a supported language file and verifying the Zowe v2 profile is used in the output shown.
                       Known issues
                       Zowe Explorer and CLI Plugin Schema Integration
                      If you experience one of the following symptoms:
                      • RSE API CLI plugin profiles are not shown or cannot be added to a tree view in Zowe Explorer although you had added them to your configuration file and the profile even appears in the drop-down of profiles that can be added
                      • You do not get code completion suggestions for RSE API Plugin profile properties, but just for profile properties of other type.
                      Then you might have installed plugins and ran configuration commands in the wrong order, which is currently impacted by a known issue in Zowe Explorer that causes Zowe CLI's global config schema to not being updated correctly when a new extender registers with Zowe Explorer.
                      To workaround this issue, perform the following:
                      1. (Re)Install Zowe plugins through Zowe CLI in order for your schema to be updated with zowe plugins install <your plugin name>.
                      2. Run the following command to update the schema with newly registered plugins from extenders zowe config update-schemas.
                      ',9),te=o("To learn more about how to install a Zowe plugin through CLI, view Zowe CLI's documentation on "),ie={href:"https://docs.zowe.org/stable/user-guide/cli-installplugins/",target:"_blank",rel:"noopener noreferrer"},ne=o("installing Zowe CLI plugins"),re=a(`
                       Eclipse Che
                      Zowe CLI's secure credential store mechanism is not currently not supported with Eclipse Che.
                      You can store them either in the global configuration file in clear text, which is protected by Eclipse Che as it is stored in a user-specific Kubernetes Persistent Volume that other users cannot access. For many Cloud providers these volumes are also fully encrypted. However, depending on your Cloud setup and for extra security we currently recommend to not store them in your workspace and rather have Zowe Explorer prompt you for the password when you access profiles.
                      To be able to currently run Z Open Editor 2.0.2 and Zowe Explorer 2.0.0 at all in Eclipse Che you must tell Zowe CLI to disable the secure credentials mechanism completely. You do that by providing a settings files for your users in ~/.zowe/settings/imperative.json with the following content:
                      {
+import{r,o as l,a as d,b as e,d as t,w as s,F as c,e as o,c as a}from"./app.daa93c96.js";import{_ as h}from"./plugin-vue_export-helper.21dcd24c.js";const u={},p=e("h1",{id:"getting-started-with-zowe-2-0",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#getting-started-with-zowe-2-0","aria-hidden":"true"},"#"),o(" Getting started with Zowe 2.0")],-1),f=e("h2",{id:"overview",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#overview","aria-hidden":"true"},"#"),o(" Overview")],-1),g=e("p",null,"Zowe Explorer 2.0.0 and Zowe CLI 7.0.1 add profile management support via a configuration file at a global and project level. IBM Z Open Editor and IBM RSE API Plugin for Zowe CLI version 2.0.2 add full support for the profiles as well.",-1),w=e("p",null,"These new configuration files replace the old Zowe CLI v6 profiles that were storing each connection in individual files, with central files that allow defining common properties such as host names, ports, protocols only once. They also distinguish user-specific properties from properties that define generic profiles for a project managed with application source in an SCM, such as Git, that all team members share for using the same development systems. In that case, personal properties such as username and passwords would be stored for the individual users on their development clients, and all other properties in a project configuration file.",-1),m=e("p",null,"For more information regarding configuration files in Zowe CLI and Zowe Explorer v2.0.0 review",-1),_=o("The Zowe CLI overview to "),b={href:"https://docs.zowe.org/stable/user-guide/cli-using-creating-global-team-profiles/",target:"_blank",rel:"noopener noreferrer"},v=o("Using Global Profile Configuration"),x=o("Zowe Explorer's documentation on "),Z={href:"https://docs.zowe.org/stable/user-guide/ze-profiles",target:"_blank",rel:"noopener noreferrer"},y=o("using configuration files"),z=e("h2",{id:"using-v1-profiles-with-z-open-editor-and-zowe-explorer",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#using-v1-profiles-with-z-open-editor-and-zowe-explorer","aria-hidden":"true"},"#"),o(" Using v1 profiles with Z Open Editor and Zowe Explorer")],-1),E=e("p",null,"Zowe Explorer 2.0.0, Z Open Editor, RSE API Plugin for Zowe CLI 2.0.2 still support the use of Zowe v1 profiles. Migrating to the new config file profile management is recommended, but not required.",-1),C=e("blockquote",null,[e("p",null,"Note if a new configuration file is in place v1 profile creation and use will not be available.")],-1),I=e("p",null,"In order to use v1 Zowe profiles in Z Open Editor and Zowe Explorer, the following steps must be performed:",-1),k=e("li",null,[e("p",null,[o("Issue the following command in your terminal "),e("code",null,"zowe scs revert --force"),o(".")])],-1),L=e("li",null,[e("p",null,[o("If the secure credential store plugin is installed, remove the plugin by running the following command: "),e("code",null,"zowe plugins uninstall @zowe/secure-credential-store-for-zowe-cli"),o(".")])],-1),S=o("Update any existing zowe plugins to their latest version. See "),T=o("here"),B=o(" for the instructions."),P=e("li",null,[e("p",null,"After performing steps 1 and 2, your v1 profiles should be ready to use in Zowe Explorer and Z Open Editor after upgrading.")],-1),M=e("h2",{id:"migration-overview",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#migration-overview","aria-hidden":"true"},"#"),o(" Migration overview")],-1),O=e("h3",{id:"semi-automatic-migration-of-zowe-cli-profiles",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#semi-automatic-migration-of-zowe-cli-profiles","aria-hidden":"true"},"#"),o(" Semi-automatic migration of Zowe CLI profiles")],-1),R=o("If you wish to migrate from Zowe v1 profiles to a Zowe v2 config file, please refer to the following documentation on "),N=o("migrating profiles"),U=o("."),F=e("h3",{id:"automated-migration-of-zowe-explorer-settings-in-vs-code",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#automated-migration-of-zowe-explorer-settings-in-vs-code","aria-hidden":"true"},"#"),o(" Automated migration of Zowe Explorer settings in VS Code")],-1),A=o("Zowe explorer settings have been changed to a consistent format for easier settings management as of Zowe Explorer v2.0.0. The migration of these settings from your old to new ones are all handled automatically upon upgrading from v1 to v2, for more information regarding this change view Zowe Explorer's documentation on "),V={href:"https://github.com/zowe/zowe-explorer-vscode/blob/main/docs/early-access/v2/Extenders.md#migration-of-old-settings-to-new-standardized-settings-in-zowe-explorer",target:"_blank",rel:"noopener noreferrer"},q=o("migrating your old Zowe settings"),j=o("."),G=o("For more information on Zowe Explorer and feature changes view the "),J={href:"https://docs.zowe.org/stable/getting-started/overview",target:"_blank",rel:"noopener noreferrer"},Y=o("Zowe Explorer docs"),D=o("."),H=e("h2",{id:"creating-zowe-v2-team-configuration-files",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#creating-zowe-v2-team-configuration-files","aria-hidden":"true"},"#"),o(" Creating Zowe v2 Team configuration files")],-1),K=e("p",null,"To get started using Zowe v2 configuration profiles in IBM User Build, the following steps must be performed:",-1),Q=e("ol",null,[e("li",null,[e("p",null,[o("Create a configuration file by clicking the "),e("code",null,"+"),o(" button in Zowe Explorer's tree view, and select "),e("code",null,"Create a New Team Configuration File"),o(" when prompted in the input box shown.")])]),e("li",null,[e("p",null,"Update host, port and other information in the config file and save. Refresh Zowe Explorer by either clicking the button in the notification message shown after creation, alt+z, or the Zowe Explorer: Refresh Zowe Explorer command palette option.")])],-1),W=o("For more details, see the Zowe CLI docs on "),X={href:"https://docs.zowe.org/stable/user-guide/cli-using-creating-global-team-profiles/",target:"_blank",rel:"noopener noreferrer"},$=o("Creating a configuration file"),ee=o("."),oe=a('
                       Configure your Zowe v2 profiles for IBM User Build
                      1. Set the profile you wish to use for IBM User Build in your VS Code user settings or ZAPP settings in the following setting zopeneditor.zowe.defaultCliProfile. If the profile type z/OSMF is used, an SSH profile must be specified in the zopeneditor.zowe.defaultSshCliProfile setting.
                      2. The team configuration file should now be ready to use in IBM User Build. Test it by performing a User Build against a supported language file and verifying the Zowe v2 profile is used in the output shown.
                       Known issues
                       Zowe Explorer and CLI Plugin Schema Integration
                      If you experience one of the following symptoms:
                      • RSE API CLI plugin profiles are not shown or cannot be added to a tree view in Zowe Explorer although you had added them to your configuration file and the profile even appears in the drop-down of profiles that can be added
                      • You do not get code completion suggestions for RSE API Plugin profile properties, but just for profile properties of other type.
                      Then you might have installed plugins and ran configuration commands in the wrong order, which is currently impacted by a known issue in Zowe Explorer that causes Zowe CLI's global config schema to not being updated correctly when a new extender registers with Zowe Explorer.
                      To workaround this issue, perform the following:
                      1. (Re)Install Zowe plugins through Zowe CLI in order for your schema to be updated with zowe plugins install <your plugin name>.
                      2. Run the following command to update the schema with newly registered plugins from extenders zowe config update-schemas.
                      ',9),te=o("To learn more about how to install a Zowe plugin through CLI, view Zowe CLI's documentation on "),ie={href:"https://docs.zowe.org/stable/user-guide/cli-installplugins/",target:"_blank",rel:"noopener noreferrer"},ne=o("installing Zowe CLI plugins"),re=a(`
                       Eclipse Che
                      Zowe CLI's secure credential store mechanism is not currently not supported with Eclipse Che.
                      You can store them either in the global configuration file in clear text, which is protected by Eclipse Che as it is stored in a user-specific Kubernetes Persistent Volume that other users cannot access. For many Cloud providers these volumes are also fully encrypted. However, depending on your Cloud setup and for extra security we currently recommend to not store them in your workspace and rather have Zowe Explorer prompt you for the password when you access profiles.
                      To be able to currently run Z Open Editor 2.0.2 and Zowe Explorer 2.0.0 at all in Eclipse Che you must tell Zowe CLI to disable the secure credentials mechanism completely. You do that by providing a settings files for your users in ~/.zowe/settings/imperative.json with the following content:
                      {
   "overrides": {
     "CredentialManager": false
   }
diff --git a/assets/zowe_submitjcl.html.3d487255.js b/assets/zowe_submitjcl.html.052fc861.js
similarity index 99%
rename from assets/zowe_submitjcl.html.3d487255.js
rename to assets/zowe_submitjcl.html.052fc861.js
index ee928a520..028ff0561 100644
--- a/assets/zowe_submitjcl.html.3d487255.js
+++ b/assets/zowe_submitjcl.html.052fc861.js
@@ -1,4 +1,4 @@
-import{r as i,o as l,a as r,b as s,d as o,w as a,F as c,c as n,e}from"./app.f6cb3ed9.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const p={},u=n('
                       Submitting JCL to compile, link, and run jobs tutorial
                       About this tutorial
                      After you complete coding changes by using IBM Z Open Editor, you want to test your changes. In order to upload all the necessary files to z/OS and run jobs, you can use Zowe CLI commands, Zowe Explorer, or both for the operation.
                       Prerequisites
                      ',4),h=e("Install IBM Z Open Editor and its prerequisites such as Java as described in "),m=e("Getting Started"),b=e("."),g=e("Install Zowe CLI as described in "),f=e("Setting up integrations"),L=e("."),w=s("h2",{id:"procedure",tabindex:"-1"},[s("a",{class:"header-anchor",href:"#procedure","aria-hidden":"true"},"#"),e(" Procedure")],-1),S=n(`
                    11. To ensure that you have a working set of files, switch your local workspace to the tutorial-complete Git branch that has the final updated set of programs and support files through the branch icon at the lower left.
                    12. Allocate the data sets on z/OS. Sample JCL files such as ALLOCATE.jcl are provided to allocate the necessary files. Alternatively, you can use your own existing PDS, or create new data sets in the Data Sets view or with Zowe CLI commands.
                      Before you use a JCL file, adjust it for your user name with these steps:
                      1. Click the JCL file to open it in the editor.
                        Note: Language support for JCl is unavailable now. But JCL syntax highlighting is enabled.
                      2. Review the file. It creates data sets in the format HLQ.SAMPLE.*.
                      3. Modify the value for the symbolic HLQ to the high-level qualifier you want to use and save the file. For example, replace TSOUSER with your value.
                      4. Execute the JCL with one of the following methods:
                        • Zowe CLI command:
                         zowe jobs submit local-file "JCL/ALLOCATE.jcl"
+import{r as i,o as l,a as r,b as s,d as o,w as a,F as c,c as n,e}from"./app.daa93c96.js";import{_ as d}from"./plugin-vue_export-helper.21dcd24c.js";const p={},u=n('
                         Submitting JCL to compile, link, and run jobs tutorial
                         About this tutorial
                        After you complete coding changes by using IBM Z Open Editor, you want to test your changes. In order to upload all the necessary files to z/OS and run jobs, you can use Zowe CLI commands, Zowe Explorer, or both for the operation.
                         Prerequisites
                        ',4),h=e("Install IBM Z Open Editor and its prerequisites such as Java as described in "),m=e("Getting Started"),b=e("."),g=e("Install Zowe CLI as described in "),f=e("Setting up integrations"),L=e("."),w=s("h2",{id:"procedure",tabindex:"-1"},[s("a",{class:"header-anchor",href:"#procedure","aria-hidden":"true"},"#"),e(" Procedure")],-1),S=n(`
                      5. To ensure that you have a working set of files, switch your local workspace to the tutorial-complete Git branch that has the final updated set of programs and support files through the branch icon at the lower left.
                      6. Allocate the data sets on z/OS. Sample JCL files such as ALLOCATE.jcl are provided to allocate the necessary files. Alternatively, you can use your own existing PDS, or create new data sets in the Data Sets view or with Zowe CLI commands.
                        Before you use a JCL file, adjust it for your user name with these steps:
                        1. Click the JCL file to open it in the editor.
                          Note: Language support for JCl is unavailable now. But JCL syntax highlighting is enabled.
                        2. Review the file. It creates data sets in the format HLQ.SAMPLE.*.
                        3. Modify the value for the symbolic HLQ to the high-level qualifier you want to use and save the file. For example, replace TSOUSER with your value.
                        4. Execute the JCL with one of the following methods:
                          • Zowe CLI command:
                           zowe jobs submit local-file "JCL/ALLOCATE.jcl"
 
                          • The Submit Job option in Zowe Explorer
                            Take ALLOCATE.jcl as an example. To execute the job, take the following steps:
                            1. Switch to Zowe Explorer.
                            2. Click the USER1.SAMPLE.JCL(ALLOCATE) data set member you created to open it in the editor.
                            3. Copy and paste the contents of JCL/ALLOCATE.jcl in the file tree into the PDS member, and save the member.
                            4. From the Zowe Explorer view, right-click the ALLOCATE member of SAMPLE.JCL, and select Submit Job.
                            After you submit the job, a message box that shows the jcl was submitted and a job number in the lower right corner.
                            You can go to the JOBS view in Zowe Explorer to see the return code of the job. If the job does not exist in JOBS view, you might need to set the job owner to your USERID by right-clicking the zoweCLI line and selecting Set Owner.
                        5. Verify the creation of these data sets using your user name by refreshing your data sets view. You might see the following lines:
                          HLQ.SAMPLE.COBOL
 HLQ.SAMPLE.COBCOPY
 HLQ.SAMPLE.COPYLIB
diff --git a/index.html b/index.html
index cdfc29d0b..cd07ff3ed 100644
--- a/index.html
+++ b/index.html
@@ -41,11 +41,11 @@
                 }
             )();
             IBM Z® Open Editor
-    
+    
     
   
   
-    
                          IBM Z® Open Editor
                          IBM Z® Open Editor
                          IBM enterprise language support for COBOL, PL/I, HLASM, and REXX in VS Code”

                          IBM Z® Open Editor
                          A free modern editing experience for IBM Z Enterprise languages
                          Getting Started
                          About
                          IBM Z Open Editor is for developers interested in Z enterprise application development, especially those who prefer a modern development environment. By bringing IBM z/OS language support to one of today’s most popular code editors, Visual Studio Code (VS Code), IBM Z Open Editor gives developers the freedom to code in COBOL, PL/I, High-Level Assembler, REXX, or JCL using the same editor they can use for languages such as Java and JavaScript. IBM Z Open Editor is a FREE, easily downloadable extension in Visual Studio Code’s marketplace.
                          Features
                          vs code
                          zowe
                          explorers
                          explorers
                          explorers
                          Feedback
                           Your feedback is important to us. Tell us what you think about the experience by taking the survey or creating an issue in GitHub. Join the Wazi Developer Community and stay up-to-date with the latest news and discussions. 
                          
-    
+    
                          IBM Z® Open Editor
                          IBM Z® Open Editor
                          IBM enterprise language support for COBOL, PL/I, HLASM, and REXX in VS Code”

                          IBM Z® Open Editor
                          A free modern editing experience for IBM Z Enterprise languages
                          Getting Started
                          About
                          IBM Z Open Editor is for developers interested in Z enterprise application development, especially those who prefer a modern development environment. By bringing IBM z/OS language support to one of today’s most popular code editors, Visual Studio Code (VS Code), IBM Z Open Editor gives developers the freedom to code in COBOL, PL/I, High-Level Assembler, REXX, or JCL using the same editor they can use for languages such as Java and JavaScript. IBM Z Open Editor is a FREE, easily downloadable extension in Visual Studio Code’s marketplace.
                          Features
                          vs code
                          zowe
                          explorers
                          explorers
                          explorers
                          Feedback
                           Your feedback is important to us. Tell us what you think about the experience by taking the survey or creating an issue in GitHub. Join the Wazi Developer Community and stay up-to-date with the latest news and discussions. 
                          
+