eclipse-che4z / che-che4z-explorer-for-endevor

Explorer for Endevor is an extension that modernizes the way you interact with Endevor inventory locations and elements

Explorer for Endevor

The Explorer for Endevor VS Code extension modernizes the way you interact with Endevor and offers a user-friendly and convenient way to work with elements and inventory locations. Explorer for Endevor includes the following features:

• Work with multiple Endevor inventory locations
• Filter elements in the Endevor Elements view
• Fetch elements from up the Endevor map
• Add an element
• View an element
• Edit an element
• Move an element
• Retrieve an element with dependencies
• Create a package
• Cast and reset a package
• List and filter packages
• View element details
• View history of elements
• View the element diff in element history
• Check action reports
• Perform a Generate action
• Print a listing
• Read team configuration files and Zowe CLI profiles (including Zowe base profiles)
• Create and synchronize an Endevor workspace
• Leverage a basic SCL highlighter

Explorer for Endevor is a part of the Che4z open-source project. The extension is also part of Code4z, an all-round VS Code extension package that offers a modern experience for mainframe application developers, including tools for language support, data editing, testing, and source code management. For an interactive overview of Code4z, see the Code4z Developer Cockpit.

Table of Contents

• Prerequisites
• Getting Started
  • Get Started Walkthroughs
  • Create an Endevor Connection
  • Create an Endevor Inventory Location
• Token Authentication and PassTickets
• Workspace Synchronization
• Use Cases
• Base Profiles
  • Access Zowe API Mediation Layer
• Team Configuration File
• Reports View
• Packages View
• Manage the Extension Tree
• Configure Explorer for Endevor
• List of Limitations
• Contribute to Explorer for Endevor
• Eclipse Che4z
• Zowe Conformance Program
• Privacy Notice
• Technical Assistance and Support for Explorer for Endevor

Prerequisites

Ensure that you meet the following prerequisites before you use Explorer for Endevor:

Client-side prerequisites:

• Access to Endevor.
• Visual Studio Code version 1.58 or higher.

Host-side prerequisites:

• Endevor 18.0.12 or higher:

  • (Endevor 18.0.12) Install PTF SO09580.
  • (Endevor 18.1) Install PTF SO09581.
  • (Endevor 19.0)

• Endevor Web Services.

Getting Started

Create an Endevor connection and Endevor inventory location and review use cases to see how you can use the full potential of Explorer for Endevor. Alternatively, use your existing Zowe CLI Endevor profiles to get started.

Explorer for Endevor 1.7.0 includes the following new features and changes:

• Create, cast, and reset a package for multiple elements.

• Select the processor group before uploading an edited element back to Endevor.

• Split the element save and element upload functionalities. Now you can make changes in the element and choose when to upload the element back to Endevor.

• The default profiles from the team config files, if present, are now propagated to the top of the Endevor Elements view at the beginning of the Explorer for Endevor session.

With the 1.6.0 release, Explorer for Endevor introduces a number of features that further improve user experience.

• The Move command enables you to move (promote) elements one stage up the map.

• Report View tracks the session activity and provides the Execution and API reports.

• Ability to connect to API Mediation Layer (ML) and take advantage of microservices using your base profile.

• Ability to specify a processor group when you add or generate an element.

• Ability to view important information including available processor groups, definition details, and last action CCID by hovering over the Endevor location, element types, and elements.

Get Started Walkthroughs

VS Code enables you to review walkthroughs to get started with Explorer for Endevor. The walkthrough contains short guides that help you get familiar with the extension features.

1. Click Help in the menu bar.

2. Select Get Started from the drop-down menu.

3. Select the Get Started with Explorer for Explorer walkthrough or click More... to select the walkthrough if it is not displayed immediately.

4. Select a feature that you want to discover.

Create an Endevor Connection

Create an Endevor connection.

1. Click the Add a New Endevor Connection button to add an Endevor connection.

   Alternatively, select your existing Endevor connections.

2. Select Create a new Endevor Connection.

3. Enter a name for your connection.

4. Enter your Endevor Web Services URL in the http(s)://host:port/basePath format.

   • Depending on the Endevor connections you use, you can include EndevorService/api/v1, EndevorService/rest or EndevorService/api/v2 in basePath. If basePath is omitted, the default is EndevorService/api/v2.
   • Explorer for Endevor checks if the specified URL is accessible. If not, you are prompted to either change the specified value or proceed without changing the value.
   • You might be prompted to either accept or reject connections with self-signed certificates if the extension encounters an issue with the server certificate issuer validation in the connection testing phase. If no issues are found, the prompt does not appear and the value is set to reject.

5. (Optional) Enter your username and password to add your mainframe credentials to the connection.

   Adding your credentials to your connection enables you to access different inventory locations without the need to enter your credentials more than once.

   Notes:

   • If your connection does not include credentials during the first session of Explorer for Endevor, you are prompted to enter credentials.
   • Passwords with 9 or more characters are treated as a passphrase by the server and are case-sensitive.

Your new connection is now available in the Endevor Elements view.

Create an Endevor Inventory Location

Once you have an Endevor connection, you need to add an inventory location. An inventory location consists of an Endevor instance, Endevor path with environment, system, subsystem, stage number, element type, CCID, and Comment. Inventory locations enable you to view and work with elements of specified Endevor locations.

1. Click the + icon next to your Endevor connection to add a new inventory location.

2. Create a name for the inventory location and press Enter.

3. Select an instance from the drop-down menu and press Enter.

4. Enter the Endevor path and press Enter.

   The path has the environment/stagenumber/system/subsystem/type format.

   Notes:

   • If you are unsure about the system, subsystem, or type parameters, you can substitute any of these parameters with a \* wildcard.
   • The elements search function is executed with the Build using map Endevor list option.

5. (Optional) Enter CCID and press Enter.

6. (Optional) Enter a comment and press Enter.

   • If you want to skip the CCID and/or comment step, you can leave the inputs blank by pressing Enter.
   • You can cancel the creation of Endevor inventory location at any step by pressing Escape.

You successfully created an inventory location.

Token Authentication and PassTickets

The Explorer for Endevor Token Authentication feature attempts to use temporary tokens (PassTickets) that are generated by the Endevor Authentication to sign on to the Endevor Web Services. The feature is enabled by default. You can disable the feature, using the Use Token Authentication option in the extension settings.

Note: If the token support is not configured on the Endevor Web Services or the Use Token Authentication setting is disabled, a basic authentication with username and password is used instead.

For more information on PassTickets, check the Multi-Factor Authentication (MFA) in the Endevor documentation.

Workspace Synchronization

A synchronized Endevor workspace enables you to work with inventory locations locally and synchronize elements from and to Endevor on the mainframe. You can create an Endevor workspace in your VS Code by enabling the Workspace Sync setting in the extension settings. Synchronized elements appear in the selected folder and you can see them in the File Explorer panel. You can manage the workspace from VS Code with Explorer for Endevor extension installed.

Note: The feature is experimental in Explorer for Endevor v1.3.0, v1.4.0 and v1.5.0.

For more information on the setting, see Configure Explorer for Endevor in this Readme.

To learn more about the Endevor Workspace synchronization feature, read this article on Medium or review the extension walkthroughs in VS Code.

Use Cases

Review the following use cases to familiarize yourself with the basic Explorer for Endevor features:

• Filter elements: Filter one or multiple elements by names or last action CCID.
• Fetch elements from up the Endevor map: Fetch the first found elements from up the Endevor map.
• Add an element: Upload an element from your workstation to a chosen Endevor inventory location.
• View an element: View the contents, summary report, and source level information of the selected element.
• Move an element: Move an element up the map by using the Endevor move statement with such options as With History, Bypass Element Delete, Synchronize, Retain Signout, and Jump.
• View details: View the details of a chosen element. The details include the environment, stage, system, subsystem, element type, and the name and extension of the element.
• Show history: Review the history of a selected element.
• Generate all elements for a subsystem: Generate the elements that are allocated in place in the selected subsystem, using a proper type sequence. Additionally, produce a detailed report that contains build status.
• Review the Generate report: Review the C1MSGS1 Endevor batch execution report that is available to you once the Generate in Place or Generate with Copyback function is executed.
• Retrieve an element: Download the selected element.
• Retrieve an element with dependencies: You can download the selected element with dependencies.
• Create a package: You can create a package from multiple elements.
• Show packages: Show packages from an Endevor instance.
• Filter packages: Filter one or multiple packages by their status.
• Cast a package: You can cast a package using various cast options.
• Reset a package: The Reset action enables you to reset package back to the IN-EDIT status.
• Edit: The Edit action enables you to download an element to your workspace, edit, and upload the selected element step by step. Once you are done with editing the element, press CTRL+S or Command+S to upload the edited element back.
• Generate: Call the Generate action for an element to invoke the Generate Processor that creates an executable form of the element.
• Print a listing: Reveal the output of the performed Generate action.
• Sign out: Lock an Endevor element so that the element is only editable by you.
• Sign in: Let you unlock a locked element. You can only unlock the elements that were locked by you.

Filter Elements

You apply a filter or multiple filters to the Endevor elements that were fetched into the Endevor Elements view. Filters enable you to display the specified elements only.

1. Hover over an inventory location in the Endevor Elements view.

   The Filter an Inventory Location icon appears on the right side of the panel.

2. Click the Filter an Inventory Location icon to set a filter for one or more elements.

   The dialog with the following options appears:

   • Select the By Element Name option.

     The Explorer dialog appears. Type a name(s) to filter by. Use a comma to separate multiple values.

   • Select the By Type option.

     The Explorer dialog appears. Enter a type pattern to filter by. Use a comma to separate multiple values.

   • Select the By Element Last Action CCID option.

     The Explorer dialog appears. Type a last action CCID to filter by. Use a comma to separate multiple values.

3. Press Enter to confirm your choice.

   A Filtered row appears in the Endevor Elements view. You can expand the row to see what filters are applied to the inventory location.

4. (Optional) Edit or remove your filters by clicking the Edit filter or Clear filter value options respectively. The options appear when you hover over the filter names.

You successfully set a filter for your inventory location.

Fetch Elements from up the Map

Both Build using map and Return first found Endevor search element options are combined to fetch first found elements from up the map into the Endevor Elements view.

1. Hover over an inventory location in the Endevor Elements view.

   The Show Endevor elements from up the map icon appears on the right side of the panel.

2. Click the Show Endevor elements from up the map icon.

   The elements from up the Endevor map appear in the Endevor Elements view.

3. (Optional) You can switch back to the elements from the inventory location only view by clicking the Show Endevor elements in place.

You successfully fetched the elements from up the map.

Add an Element

You can upload a new element to your inventory location. Also, you can assign a processor group to your element in the process of uploading the element. The uploaded element appears under the selected type in the Endevor Elements view.

1. Hover over an inventory location in the Endevor Elements view.

   The Add an Element icon appears on the right side of the panel.

2. Click the Add an Element icon to upload a new element.

   The Explorer dialog appears. You can now select an element that you want to upload from your workstation.

3. Select an element that you want to upload from your workstation.

4. (Optional) Select an available processor group from the drop-down list.

You successfully added the element.

View an Element

You can view the contents, summary, and source level information of an element by clicking on the element in the Endevor Elements view. The chosen element appears in the editor area. Viewing the contents of the element allows you to determine if you want to retrieve and work with the element.

1. Hover over an element that you want to view.

2. Click the element to see the contents of the element.

   The contents of the element appear in the editor area.

Move an Element

Use the Move option against an element to move the selected element up the map. When the move is successful, the element is displayed in the next stage up the map. To see the result of the move, click the Show Endevor Elements Up The Map option that fetches the elements from up the map into the Endevor Elements view. By default, the up the map view is not enabled.

1. (Optional) Hover over your environment location in the Endevor Elements view and click the Show Endevor Elements Up The Map option.

   The up the map elements display in the Endevor Elements view.

2. Right-click the element you want to move and select the Move option.

3. Enter the CCID.

4. Enter the comment.

5. (Optional) Select the following Move options:

   • With History: The option preserves source element change history. If you move the element without history, Endevor searches through the element levels at the source location to find a matching level at the target location. Endevor then compares the two and creates a new level at the target location that reflects the differences.
   • Bypass Element Delete: Retains the element in the source stage after the move.
   • Synchronize: Compensates for differences between the base level of a source element and the current level of a target element. If differences are found, Endevor compares the two elements and creates a new level at the target that reflects the differences. If Endevor differences are not found, Endevor proceeds with a regular move action.
   • Retain Signout: The moved element retains the source location signout at the target location.
   • Jump: Moves an element even if the element exists at an intermediate stage, not on the map.

You successfully moved the element up the map.

View Details

The inventory location details of an element you want to view appear in the editor area in a separate tab.

1. Right-click an element.

2. Select the View Details option.

   The details of the element appear in the editor area.

Show History

The Show History feature enables you to review changes of the element. You can see a new view that is called Element History under the explorer tree. The view lists the history of changes for a selected element.

1. Right-click an element.

2. Select the Show History option.

   The history of the element appears in the editor area.

Review the Generate Report

You can retrieve the C1MSGS1 Endevor batch execution report that contains the detailed information of your generated elements.

1. Right-click an element.

2. Select the Generate in Place or Generate with Copyback option.

3. Enter CCID.

4. Enter a comment.

5. Click the Show Report button in the pop-up.

   The C1MSGS1 Endevor batch execution report appears in the editor area.

Generate All Elements for a Subsystem

• Generate All Elements enables you to generate all the elements within a subsystem.

1. Hover over a subsystem.

2. Click the Generate All Elements icon.

3. Enter CCID.

4. Enter a comment.

   The summary table for a C1MSGS1 Endevor batch execution report is produced in the event of error(s) while generating element(s). You can review the table in the editor area.

Retrieve an Element

You can download an element to your workspace and work with the element locally.

1. Right-click an element.

2. Select the Retrieve option.

   The extension downloads and places the element into your workspace. The contents of the element appear in the editor area. You can find the element in the workspace folder.

You successfully retrieved the element.

Retrieve an Element with Dependencies

You can download an element with dependencies to your workspace and work with the element and the dependencies locally.

1. Right-click an element.

2. Select the Retrieve with dependencies option.

   The extension downloads and places the element with dependencies into your workspace. The contents of the element appear in the editor area.

You successfully retrieved the element with dependencies.

Create a Package

Create a package from multiple elements. Select elements that you want to organize in a package and right-click on the selection to select the Create Package option.

1. Select an element or an array of elements by holding the CTRL/Command key and using the left mouse button.
2. Right-click the selected element(s) and select the Create Package option.
3. Enter a name for the package.
4. Enter a description for the package.
5. Select options for the package.
6. (Optional) Enter a CCID.
7. (Optional) Enter a comment.
8. Select Move command options for the package.

You successfully created the package.

You can find the package in the Endevor Packages view.

Show packages

Use the following ways to show packages from an Endevor instance.

• Select an Endevor instance from the Endevor Packages view:

  1. Hover over the Endevor Packages view toolbar and click Change Instance.
  2. Select connection and configuration.
  3. (Optional) Select a package status filter.

• Use Show Packages from the Endevor Element view:

  1. Right-click the Endevor inventory location in the Endevor Element view.
  2. Select the Show Packages option.
  3. (Optional) Select a package status filter.

You successfully displayed the packages.

Filter Packages

You can apply a status filter when listing packages in the Endevor instance for the first time. The filter reduces the number of packages that are pulled from Endevor based on the status.

1. Right-click the filter icon at the top of the list in the Endevor Element view and select the Change Filter option.

2. Select a status you want to filter.

   Note: If all statuses are selected, no packages are filtered out.

You successfully applied a filter to the listed packages.

Cast a Package

Use the Cast option against a package to prepare the package for review and subsequent execution.

1. Right-click the package you want to cast and select the Cast Package option.

2. (Optional) Select the following Cast options:

   • Backout Enabled: Indicates whether the backout facility is available for the selected package.
   • Components Validation (radio group):
     • Validate: Enables component validation. If component validation fails, the cast fails, as well.
     • Do not validate: Disables component validation for the package.
     • (Default) Validate with warnings: Enables component validation and generates a warning if component validation fails.

You successfully cast the package. You should see a notification pop-up with the Show Execution Report and Cancel options and the following message:

Cast package ... using configuration ... was successful. Would you like to see the report?

If the cast of the package fails, the execution report is displayed automatically.

Reset a Package

Use the Reset option against a package if you want to set status back to In-edit, which enables you to modify the package. You can use the Reset option against any package status type.

1. Right-click a package.
2. Select the Reset Package option.

You successfully performed the Reset Package action.

Edit

The Edit action lets you download an element, edit, and upload the element back.

1. Right-click an element.

2. Select the Edit option.

   The contents of the element appear in the editor area. You can now edit the element.

3. Press CTLR+S or Command+S when you want to save the edited element.

4. Specify any accessible Endevor path and a name for the element.

5. Enter a CCID.

6. Enter a comment.

7. (Optional) Resolve conflicts between the element versions if necessary.

   Notes:

   • The behavior of the conflict resolution feature differs in Theia.

   • (Theia only) When you resolve a conflict, open the Command Palette by pressing CTRL+SHIFT+P or CMD+SHIFT+P and use one of the following commands: Accept changes or Discard changes.

You successfully edited and saved the element.

Generate

The Generate action enables you to select a processor group and create an executable form of the element, together with any associated outputs such as listings, and has the following available options:

• Generate in Place enables you to generate the selected element in the same location where the element resides.

• Generate with Copyback enables you to copy the selected element back from up the map to the target location first and then generate the element in that location.

• Generate with No Source enables you to generate an element in the target location, using the source of the selected element from up the map. In this case, the source is not fetched to the target location and the sourceless element is created.

You can use the Generate in Place, Generate with Copyback, or Generate with No Source context menu options to perform the Endevor Generate action for a selected element.

1. Select one of the following options:

   • Right-click an element and select the Generate in Place option.

     
     
     

   • Right-click an element from up the map and select the Generate with Copy back option.

     
     
     

   • Right-click an element from up the map and select the Generate with No Source option.

   A successfully-performed Generate action shows a notification pop-up with the Print a listing and Cancel options and the following message:

   Successfully generated the elements: ... Would you like to see the listing?
   

2. (Optional) Select an available processor group from the drop-down list.

3. (Optional) Click Print a listing to see the Generate output.

   Note: You can always review the Generate output by selecting the Print a listing option.

You successfully performed the Generate action.

If Generate fails to process an element, the listing is displayed automatically.

Print a Listing

The Print a listing option enables you to display the most recently created listing.

1. Right-click an element.

2. Select the Print a listing option.

   The contents of the listing appear in the editor area.

You successfully printed the listing.

Sign Out

The Sign out option enables you to lock an element, which prevents other users from editing the element.

1. Right-click an element.
2. Select the Sign out option.
3. Enter a CCID.
4. Enter a comment.

You successfully signed out the element.

Sign In

The Sign in option enables you to unlock an element that earlier was signed out by you.

1. Right-click an element.
2. Select the Sign in option.

You successfully signed in the element.

Base Profiles

Explorer for Endevor enables you to use Zowe CLI base profiles. To make your default base profile work in the extension, ensure that you specify such parameters as username, password, host, port, and rejectUnauthorized in the base profile. For more information about how base profiles work, see the Base Profile section on Zowe Docs.

Access Zowe API Mediation Layer

The extension enables you to connect to Endevor Web Services that are integrated with the Zowe API Mediation Layer, using your existing base profile. Ensure that you log in to the Zowe API Mediation layer authentication service, using your credentials and edit your current Endevor location to include the API ML endpoint for Endevor Web Services.

1. Navigate to Zowe Explorer.

2. Right-click your profile in the Data Sets view and select the Manage Profile option.

3. Select the Edit Profile option from the drop-down menu.

   A team configuration file is opened.

4. Add a new Endevor connection with the following properties:

   {
     "$schema": "./zowe.schema.json",
     "profiles": {
       "base": {
         "type": "base",
         "properties": {
           "host": "api-ml-service.net", // specify your base URL for the Zowe API Mediation Layer
           "port": 8080, // specify the port of your Zowe API Mediation Layer
           "rejectUnauthorized": true,
           "tokenType": "apimlAuthenticationToken"
         },
         "secure": ["tokenValue"]
       },
       "endevor-via-apiml": {
         "type": "endevor",
         "properties": {
           "basePath": "/endevor/api/v2" // Specify the basePath of your Endevor Web Services integrated with the Zowe API Mediation Layer
         }
       }
     }
   }

   where host and port are the common endpoint of your Zowe API ML services, and basePath is the specific endpoint where your Endevor Web Services are deployed under the Zowe API ML.

5. Save your team configuration file.

For more information about Zowe API Mediation Layer, see Integrating with API Mediation Layer on Zowe Docs.

You successfully customized the API ML connection properties for your Endevor connection.

Team Configuration File

Explorer for Endevor supports reading a global team configuration (team config) file. A team configuration file enables you to manage your Endevor connection details efficiently in one location. You can use global team configs with your team members to share access to Endevor inventory locations. For more information about team config, see Using Team Profiles on Zowe Docs. The extension reads team configuration files only if the profile sync setting is enabled. To configure the setting, navigate to > Settings > Extensions > Explorer for Endevor > Profiles: Keep in sync.

As an application developer, you can obtain a shared global configuration file from your system administrator and use the file to access shared systems. As a system administrator, you need to have Zowe CLI 7.2.1 or higher on your workstation before you create a team configuration file.

Tip: You can convert your existing Zowe CLI profiles into team configuration files with the zowe config convert-profiles command. For more information about team config conversion, see Using Profiles on Zowe Docs.

Reports View

The extension enables you to monitor activity of the session in the Explorer for Endevor tab that you can access using the View tab. The Reports View feature helps you troubleshoot any errors that occur in the extension more efficiently.

Use Reports View to keep track of events that happen during an active session of the extension and review execution errors or API notification messages.

1. Navigate to the View tab in VS Code.

2. Click Command Palette....

   The command prompt is displayed.

3. Type Explorer for Endevor: Focus on Endevor Reports View and press Enter.

The Report View is displayed.

You can now click on events to expand them and access execution or API error reports.

To see a list of Endevor messages and codes that were reported, hover over records of the warning or error messages.

Packages View

The extension enables you to see the Endevor packages in a specified Endevor instance, to filter the packages and perform package-related actions.

You can perform the following actions to change the way packages are displayed and the order in which they are displayed:

• Show Packages Created by User: Click on the Show Packages Created by User icon in the Endevor Packages view toolbar to show only packages created by currently logged in user.

• Descending/Ascending Order by Package ID: Click on the Descending/Ascending Order by Package ID icon to toggle the order in which packages are shown.

• Change Instance: Click on the Change Instance icon to change the Endevor instance whose packages are displayed.

• Refresh Endevor Packages: Click on the Refresh Endevor Packages icon to retrieve packages information from Endevor, using the current Endevor instance and filter.

Manage the Extension Tree

You can perform the following actions to manage your connections and inventory locations in the extension tree:

• Delete a connection: Delete your connection permanently by right-clicking a connection node and selecting the Delete a connection option.

• Delete an inventory location: Delete your inventory location permanently by right-clicking an inventory location node and selecting the Delete an inventory location option.

• Hide a connection: If you do not want to list your connections in the Endevor Elements view, you can hide such connections. To hide a connection, right-click the connection node and select the Hide a connection option.

• Hide an inventory location: If you do not want to list your inventory locations in the Endevor Elements view, you can hide such locations. To hide an inventory location, right-click the location node and select the Hide an inventory location option.

• Edit an Endevor Connection: Edit your Endevor connection login details by right-clicking a connection node and selecting the Edit an Endevor Connection option.

  Note: The Hide a connection or Hide an inventory location actions do not permanently delete the information from the extension.

Configure Explorer for Endevor

You can configure the following settings of the extension:

• The number of parallel HTTP requests supported by Endevor.

• Automatic Signout. The signout function locks elements for you. If the option is enabled, retrieved or edited elements are signed out to you. If an element is signed out to somebody else, a notification asking whether to override the signout pops up. If the option is disabled, the extension retrieves or edits an element without signout.

• Telemetry level. You can disable or configure data that is collected by Telemetry in the VS Code Settings. Navigate to Settings > Application > Telemetry > Telemetry Level to do so. For more information, see Disable Telemetry in the VS Code documentation.

  Note: This setting applies not only to Explorer for Endevor but to all extensions in your VS Code.

• Profiles: Keep in Sync. The option enables you to use a team configuration file that stores your pre-saved Endevor configuration or Zowe CLI Endevor profiles with Endevor locations in the extension. By default, the setting is enabled, meaning that the extension reads your team configuration files on startup and displays profile information in the Endevor Elements view. If the option is disabled, the extension does not check the .zowe folder for available profiles.

  Notes:

  • You can use Endevor connections and inventory locations that are created in Explorer for Endevor in the extension only.

• File extension resolution. The option enables you to choose between the following methods of file extension resolution for the locally saved elements.

  • 'Element name only' method uses the element name to determine the file extension.

  • 'Endevor type file extension only' method uses the Endevor defined file extension for the type.

  • (Default) 'Endevor type file extension or type name' method uses the Endevor defined file extension for the type. The method also uses the Endevor type name as a fall-back option.

• (Experimental) Workspace Synchronization. The option enables the Endevor Workspace initialization that lets you create a synchronized Endevor workspace locally.

  Note: Experimental features might include undiscovered errors. Please, use this feature at your own discretion.

• Ask for Processor Group. The option enables selection of a processor group when you perform Generate, Add, or Upload actions. A selected processor group overrides the previously chosen processor group.

• Generate Subsystem. The option enables the extension to add the Generate all Elements feature. The option is disabled by default. Once enabled, the feature appears in the Endevor Elements view. You can then perform the Generate all Elements action against a susbystem node.

• The editor auto save setting is disabled by default.

  Note: Using the auto save feature with Explorer for Endevor might result in a bad user experience.

  To change the setting, navigate to the VS Code Settings and look for Files: Auto Save.

Access the Explorer for Endevor settings by clicking Settings > Extensions > Explorer for Endevor.

List of Limitations

This section lists notable limitations in the current version of Explorer for Endevor.

• Searching elements by comment and CCID is not supported.

  You can search using the instance, environment, stageNumber, system, subsystem, and type parameters.

• Only the UTF-8 character encoding is currently supported.

Contribute to Explorer for Endevor

We encourage you to share ideas to help improve Explorer for Endevor. You can also report issues in the extension, using the following link.

Share an idea or open an issue in our Git repository

Eclipse Che4z

Explorer for Endevor is included with Eclipse Che version 7.6.0 and above. For more information, see the Eclipse Che4z webpage.

Zowe Conformance Program

Explorer for Endevor is Zowe V2 Conformant. The Zowe Conformance Program ensures a high level of common functionality, interoperability, and user experience while using an extension that leverages Zowe. For more information, see Zowe Conformance Program.

Privacy Notice

The extensions for Visual Studio Code developed by Broadcom Inc., including its corporate affiliates and subsidiaries, ("Broadcom") are provided free of charge, but in order to better understand and meet its users’ needs, Broadcom may collect, use, analyze and retain anonymous users’ metadata and interaction data, (collectively, “Usage Data”) and aggregate such Usage Data with similar Usage Data of other Broadcom customers. Please find more detailed information in License and Service Terms & Repository.

This data collection uses built-in Microsoft VS Code Telemetry, which can be disabled, at your sole discretion, if you do not want to send Usage Data.

The current release of Explorer for Endevor collects anonymous data for the following events:

• Extension commands, such as Add, Retrieve, Sign in, Sign out, Edit, Generate, etc.
• Build the Endevor Elements view, refresh the view
• Filter elements
• Internal and Endevor errors

Note: Any sensitive information is filtered, so the extension gets only anonymous error messages and Endevor REST API error codes. The Endevor REST API error codes are collected for the purposes of determining errors in the extension lifecycle.

Each such event is logged with the following information:

• Event time
• Operating system and version
• Country or region
• Anonymous user and session ID
• Version numbers of Microsoft VS Code and Explorer for Endevor

Technical Assistance and Support for Explorer for Endevor

The Explorer for Endevor extension is made available to customers on the Visual Studio Code Marketplace in accordance with the terms and conditions contained in the provided End-User License Agreement (EULA).

If you are on active support for Endevor, you get technical assistance and support in accordance with the terms, guidelines, details, and parameters that are located within the Broadcom Working with Support guide.

This support generally includes:

• Telephone and online access to technical support
• Ability to submit new incidents 24x7x365
• 24x7x365 continuous support for Severity 1 incidents
• 24x7x365 access to Broadcom Support
• Interactive remote diagnostic support

Technical support cases must be submitted to Broadcom in accordance with guidance provided in “Working with Support”.

Note: To receive technical assistance and support, you must remain compliant with “Working with Support”, be current on all applicable licensing and maintenance requirements, and maintain an environment in which all computer hardware, operating systems, and third party software associated with the affected Broadcom software are on the releases and version levels from the manufacturer that Broadcom designates as compatible with the software. Changes you elect to make to your operating environment could detrimentally affect the performance of Broadcom software and Broadcom shall not be responsible for these effects or any resulting degradation in performance of the Broadcom software. Severity 1 cases must be opened via telephone and elevations of lower severity incidents to Severity 1 status must be requested via telephone.

---

Copyright © 2024 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.

che-che4z-explorer-for-endevor's Issues

Question: How to configure Endevor Web Services to get Elements encoded in UTF-8 when retrieve or browse action ?

Using the "Explorer for Endevor" extension in VSCode, we would like the information retrieved during a RETRIEVE or BROWSE to be encoded in UTF-8.

We tried to configure the Endevor Web Services (EWS) server with the options CharacterSet="UTF-8" / LFSEncoding="UTF-8", or with CharacterSet="UTF8" / LFSEncoding="UTF8", but this causes an error at EWS level during a RETRIEVE (but OK for BROWSE).

The only value that works for us is "ISO8859-1", which then causes errors on many characters and in particular French accented characters at VSCode.

<DataSource xmlns="http://scm.ca.com/endevor/CFG" xmlns:cfg="http://scm.ca.endevor" 
   Name="ENDEVOR" Status="Available" 
   Message="ENDEVOR Web Service" 
   Description="Endevor demo">
  <STC JobName="WSEWSSTC" 
     ProgramName="BC1PAPI0" 
     HostName="TMVS" 
     Comments="Welcome to ENDEVOR" 
     UserId="" Password="" EncryptedPassword="" 
     PoolInitSize="0" PoolIncrSize="1" PoolMaxSize="0" PoolReapTime="0" 
     UnusedTimeout="0" AgedTimeout="0" ConnectionTimeout="0" 
     ResponseTimeout="0" 
     KeepAlive="0" 
     ConnectionMaxWS="0" ConnectionMaxKBytes="0">
   <wsParameters Lang="EN" Locale="" TimeZone="GMT+0.0" 
      CharacterSet="UTF-8" CodePage="cp01147"   
      LFSEncoding="UTF-8" Encoding="cp01147"   
      ContentType="Text" 
      Trace="TestMonitorSTCPool" Traced="ALL" Version="" 
      Product=""/>
  </STC>
</DataSource>

Endevor for ZOWE plugin:

zowe endevor retrieve element COB0C7 --env ETU --sn 1 --sys SIRIS --sub S9 --typ COBOL -i ENDEVOR
[INFO] endevor action executed in location: ETU/1/SIRIS/S9 on element: COB0C7.COBOL
[INFO] Running on host: TMVS:8180 instance: ENDEVOR
Command Error:
[ERROR] return code: 0016 reason Code 0000
[ERROR] EWS1117I Request processed by SysID TMVS, STC WSEWSSTC - STC08595,!EWS1115E!

STC Tomcat (WSTOMSTC):

09:44:12.146 <http-nio-8180-exec-1> ERROR (c.c.e.j.EndevorSubmitCategoryL) [Internal error] STC: EWS1117I Request processed by SysID TMVS, STC WSEWSSTC - STC08595
09:44:12.146 <http-nio-8180-exec-1> ERROR (c.c.e.j.EndevorSubmitCategoryL) [Internal error] Read output file of list type : Unrecognized field "TYPE Â# ID" (class com.ca.endevor.jersey.csv2json.TypeInfo), not marked as ignorable (47 known properties: "REGR SEV", "UPDT DATE", "NEXT TYPE", "STG #", "FWD/REV CMPNT DELTA", "INCL DSN", "FWD/REV/IMG/LOG ELM DELTA", "COMPRESS BASE", "DFLT PROC GRP", "CONSOL LL", "CMPMT AUTO CONSOL LL", "DELTA DSN", "INCL DS TYPE", "UPDT USRID", "BASE DS TYPE", "FILE EXT", "CMPNT CONSOL LL", "AUTO CONSOL", "AUTO CONSOL LL", "COMPARE (T)", "DELTA DS TYPE", "STG NAME", "STG SEQ #", "SRC LNG", "CMPNT AUTO CONSOL", "DATA FORMAT", "LANG", "COMPARE (F)", "TYPE NAME", "ELEMENT RECFM", "STG ID", "BASE/IMAGE DSN", "ENV NAME", "SRC O/P DS TYPE", "PV/LB LANG", "EXPAND INCL", "DESCRIPTION", "SYS NAME", "RCD UPDT CNT", "REGR %", "SRC O/P DSN", "ELM NAME NOT ENCRYPTED", "REL ID", "SITE ID", "TYPE # ID", "UPDT TIME", "USS DELIMITER"])
 at [Source: (StringReader); line: 2, column: 32] (through reference chain: com.ca.endevor.jersey.csv2json.TypeInfo["TYPE Â# ID"])

add usage tip: How to validate an Endevor URL

In any browser, it's possible to access: http(s)://host:port/basePath (example: http://192.178.0.1:111/EndevorService/rest) and get a list of configurations available for that Endevor Web Service.

Output should be something like:

[{
  "description" : "Endevor Web Service",
  "message" : "ENDEVOR Web Service",
  "name" : "ENDEVOR",
  "status" : "Available",
  "jobName" : "JOBNAME",
  "programName" : "PROGNAME",
  "hostName" : "HOSTNAME",
  "comments" : "Access to ENDEVOR Instance",
  "userId" : "USERID",
  "password" : null,
  "poolInitSize" : 0,
  "poolIncrSize" : 0,
  "poolMaxSize" : 0,
  "poolReapTime" : 0,
  "unusedTimeout" : 0,
  "agedTimeout" : 0,
  "lang" : "EN",
  "timeZone" : "GMT",
  "characterSet" : "ISO8859-1",
  "codepage" : "cp1047",
  "contentType" : "Text",
  "traced" : "ALL"
}]

This can be used as a fast way to validate the URL outside of Explorer for Endevor or Zowe CLI with Endevor plugin

Add license to package.json for open vsix registry publishing

We need to add the license in the package.json as part of the new publishing process for the Open VSIX registry publishing.

VSCode - Listing files have the type as a filename suffix

When I use the VSCode extension "Print listing" option the listing is retrieved with a filename suffix of the type name. In our case the suffix is ".cobb" which causes the listing to be viewed with COBOL highlighting on. This highlighting gives some unusual colouring.

Shouldn't the listing filename have .txt as it's suffix?

Generate issue with the plugin Broadcom Explorer for Endevor

E4E is generating in place. If I have an element in Stage 2 and tried to generate it, I would expect that it would be generated and replaced in Stage 1.

"OPTION NOCC" on browse action

The "browse" action is a "PRINT ELEMENT ... OPTION BROWSE".
The result content is a "listing", not a "element".

I suggest that the "NOCC" option to be used, "PRINT ELEMENT ... OPTION BROWSE NOCC" to suppress header and the ASA code in column 1.

Declare the Endevor instance in the endevor profile rather than in the endevor-location profile

This issue is for the @broadcom/endevor-for-zowe-cli plugin. In the absence of a public GitHub site for this plugin, I declare it here.

It is not possible to declare an instance (--instance) by default at the endevor profile level. The instance to use can only be declared in the endevor-location profile or at the level of the zowe commands.

In general, there is only one Endevor instance declared at the Endevor Web Services server level, and this is a property of the Endevor Web Services configuration, so it would make sense that the endevor profile is the one carries this information rather than the endevor-location profile.

This may impact the operation of the Explorer for Endevor extension.

Move npx vsce package script to npm scripts in package.json

Also, add Lint check to the pipeline.

See Jenkinsfile and package.json

Choosing a workspace for retrieve elements

As a user, I would love to work with several root folders opened in VSCode with opened E4E.

There is an ability to choose the primary workspace folder in VSCode. I think E4E can use it, and also it can store user choice in memory to prevent asking all the time.

Full text search across the all elements in Endevor - Enhancement request

When using explorer for Endevor, I can browse all the elements defined in any particular Endevor system. However, when I work on resolving any customer case, I need to search for specific string across all the elements in the respective Endevor system to find all elements containing the searched string. This is not currently possible in explorer for Endevor so I need to run a batch job, executing program NDVRC1 and find the search results in the output of the job.

View all element in the map

I would like to have the ability to view all the element in the map. In v11, this feature is available.

Possible Solution: Allow wildcard in all fields in the Endevor Location.

Investigate Jenkins Error "line 1: npm: not found"

Error received in Jenkins after adding Test stage.

[Pipeline] sh
11:28:13 + npm run test
11:28:13 /home/jenkins/agent/workspace/endevorExplorer_PR-55@tmp/durable-4fb70ace/script.sh: line 1: npm: not found
[Pipeline] }
[Pipeline] // w

Will disable the stage until the error is fixed.

View action on Element

The "Explorer for Endevor" extension provides actions "Browse Element" (in fact "PRINT ELEMENT"), and "Retrieve Element" which sets a lock at Endevor level (Signout option).

The @zowe/endevor-for-zowe-cli plugin provides a "view" command to do a "retrieve no signout".

I suggest that a "View Element" action be added to the "Explorer for Endevor" extension to allow element retrieval without setting a lock in Endevor.

Accepts hostname and port without http/https in THEIA but same action is not working in VSCode

Description:
While creating a profile on THEIA i can enter hostname and port without http/https but if i do the same on VSCode it throws an error.

Steps to reproduce issue:

1. Click on create new profile
2. Enter profile name
3. Enter host and port (fakehost:1003)

Expected result:
Behavior should be same in VSCode and THEIA

Screenshot:
From VSCODE:

Profiles not shared across Explorer for Endevor and CLI/requires restart of workspace in Eclipse Che

There seems to be an issue that a profile created via the CLI or in the UI of Explorer for Endevor does not appear and is not available for use in the other. Please ensure that I can use one profile across both the extension and Zowe CLI in Eclipse Che.

Elements in Stage 2 are shown in the tree

I created a location profile and stated that my StageNumber is eq 1. When I view the tree, I am able to see elements from Stage 2. That is not good. I do not want to see elements from stage 2

Changing underlying profile requires you to restart VS Code

I hadn't used this extension in a while and ended up having to change my password in the endevor profile. After changing, that didn't appear to propagate to the extension in vs code as it was using the old credentials. Clicking the refresh button still used the old password. I ended up having to restart VS Code to get the change.

I'd prefer if the updates to the profile in use could be picked up by this extension.

Support for base profile

This issue is for the @broadcom/endevor-for-zowe-cli plugin. In the absence of a public GitHub site for this plugin, I declare it here.

As it stands, version 5.6.0, the @broadcom/endevor-for-zowe-cli plugin is not compatible with the use of a base profile.
A base profile is used to share some options between services profiles, such as user code, password, host machine, etc.

Ability to edit my element location & service values

As a user I would like to have the ability to edit my element location & Endevor service values via E4E

There is no ability to specify Zowe location

AS IS
As a user, I need to install Zowe globally, not in my preferable place.

TO BE
As u user, I can specify Zowe where I want to and just specify the details in the extension configuration.

Environment:
OS - MacOs Catalina
VS Code - 1.51.1
Endevor Explorer - 0.11.1
Zowe version - 6.24.5

Optional credentials in Endevor

Currently, Endevor doesn't allow you to create profiles with optional credentials (user/password).

So these should be made optional in the future.

Inconsistency on the "profile" property in the package.json file

When editing the settings of the "Explorer for Endevor" extension in VS Code, an anomaly in the properties structure is reported: a "profile" property is missing.

In the package.json file, at the properties description, the "profile" property is required, but in the settings.json file it is a "profileLabel" property that is used.

Fix Circular Dependencies

PR #61 is adding "madge" to detect circular dependencies.
Currently it's added as a separate npm script. Once all are fixed it should be added in the linting process as well.

Saving connection settings in the "user" settings.json

Using VS Code, by default the settings for connections to an Endevor configuration (EWS) are saved in the workspace's settings.json file, not in the user's settings.json file.

The connection settings contains information related to the user, which causes a problem when the workspace is a GIT repository: these settings are propagated to other users during GIT push / merge ...

The connections settings to an Endevor configuration should be saved in the user's settings.json file, or even differentiated between user-related settings, stored in the user's settings.json file, and context-related to Endevor settings (EWS Server), stored in the workspace settings.json file (shareable by all users).

Signout support

I would like the Edit feature to include signout support.
If an Endevor system requires signout in the system definition
SIGN-IN/SIGN-OUT OPTIONS:
ACTIVATE OPTION: Y (Y/N)
then retrieve the element for edit with signout. Whether retrieve with signout is used or not should be transparent to the user.
If the element is already signed out to another user then offer the option of overriding the signout.

The current version of the edit feature does not work for us because the add fails saying that the element is not signed out.

There is not quite understandable message during attempts to fetch Endevor instances after profile creation without opened folder

Basically, the flow is pretty simple:

1. Go into the Endevor Explorer extension
2. Create a new profile (pick a +)
3. Specify the name, connection host/port, userid, pass and etc.
4. The profile will be displayed in the sidebar
5. But the (+) button will be not active, and everything you can do - delete the session itself

AS IS:
After the point 5 from above list, you will get only not quite understandable messages about the workspace was not opened.

TO BE
The message can be more clear, like, 'please open something in the Editor tab'. Also, it would be great to have such info in the README

Environment:
OS - MacOs Catalina
VS Code - 1.51.1
Endevor Explorer - 0.11.1
Zowe version - 6.24.5

Issue listing elements with lowercase letters or long names

When viewing elements, if the element name has lowercase letters or has more than eight characters, the displayed element name is altered. I opened this issue against the CA Endevor plug-in for Zowe CLI and the feedback was that they needed to use the fullElmName field instead of the elmName field. There could likely be significant synergy and code reuse between these projects.

This issue does not occur in the Eclipse interface:

Explorer for Endevor and CA Endevor plug-in for Zowe CLI:

Not Showing proper lable for username while creating new profile on THEIA

Description:
Explorer for Endvor is not showing proper lable in THEIA like when we create a new profile and on the username inputbox it shows enter url.

Steps to Reproduce issue:

1. Click on create new profile
2. Enter profile name
3. Enter host and port (fakehost:1003)
4. Now see the username inpubox lable.

Expected Result:
It should display proper lable for username "Enter the user name for the connection. Leave blank to not store. (Press 'Enter' to confirm your input or 'Escape' to cancel)"

Screenshot:

Sort objects when creating a filter

As a user, I'd like to be able to sort the objects after I've created a filter. As an example, I have a lot of "No source" elements in my Endevor sandbox and want to be able to see only the edited components at the top of the list.

Right now, the extension shows all elements, but I cannot retrieve "No source" elements because it only displays the error "C1G0208 ELEMENT NOT FOUND".

Collapse all nodes after browser refresh

When any node in Explorer for Endevor is expanded and the page is refreshed, the credentials prompt pops-up even when the user works in a different tab or extension.

Steps to reproduce:

1. Login to E4E and open any node (Filters or Maps)
2. Refresh the page
3. Credentials dialog pops-up

Desired behaviour:
After browser refresh, all nodes collapse so that no login is required.

Error files.encoding generate � or � and that should be £

We have an issue when we browse or retrieve an element via Visual Studio Code and it change some character like the "£".
Visual Studio Code convert it on � or � 

Problem: E4E is currently supporting UTF-* encoding only
Solution: Have the ability to support other encoding

Readme does not appear on the open vsx registry

https://open-vsx.org/extension/BroadcomMFD/explorer-for-endevor

No readme :(

Specify workspace before creating repository.

I've installed the explorer for endevor plugin in visual studio code version 1.45.0.
The first thing I tried after it was installed is to create a new connection. But when I click that, the error message 'Specify workspace before creating repository' is shown. Can you guide me to what I'm suppost to do in this case?

Extension doesn't activate after I deleted a profile

Extension doesn't activate after I delete a profile (manuall from file system) but the details of that profile are still in settings.json

Steps to replicate:

1. Open extension and add a couple of profiles
2. Make sure they are in settings.json
3. delete a profile yaml file from .zowe/profiles/endevor
4. Reload VS Code
5. Receive error message:

Activating extension 'broadcomMFD.explorer-for-endevor' failed: Could not find profile named: [PROFILE_NAME]..

Retrieve functions not working with Bridge for Git repository

When I have a synchronized repository from Bridge for Git open in my editor and try to retrieve an element or retrieve with dependencies, the process runs but no files open in my editor and don't appear anywhere.

Can you ensure that this functionality works in concert with Bridge for Git?

Not able to create New Profile in THEIA

Description:
On theia, not able to create a new profile

Steps to Reproduce issue:

1. Click on create new profile
2. Enter all the details
3. In the last it is throwing an error "Error saving profile see output" but in theia i can't find output in terminal

Screenshot:

Collapse the node when login is cancelled by the user

Steps to reproduce:

1. Select E4E extension and expend a node (Filters or Maps)
2. Cancel the login (using ESC key)
3. Node stays expanded
4. After a page refresh it requires the login again...

Desired behavior:
When the user cancels the login, the node collapses so that after refresh it does not require login.

Error: Workspace

This error message is so vague:

I would like to ask for a better error message.

Fix Eslint error

PR #61 is switching from tslint to eslint. The rules are strict, but while implementing it, some code needed to be exluded from the rules.

This is to go back to source and fix all outstanding errors. Ideally we want to have no piece of code which is excluded. Where not possible, explanation in comments is welcomed.

'Add' element back to Endevor

Description:
As Michelle, I want to be able to safely add an element back to Endevor, so that my local changes can be uploaded to Endevor repository. If the element is existing or there are any problems, I would like to receive an error message so I could check and correct it.

The process for adding an element will be as follows:

1. Click the Add file Icon (Talk to UX) to trigger add element.
2. Choose/Select the element that I want to add in Endevor
3. Once I click okay, target location will be prompted > CCID > Comment (Similar to edit)
4. Add element API is triggered and the tree is updated with the new element
5. If there are duplicates/problems, a warning message will appear to allow me to check on those errors. 

Note: This feature will only add one element at a time. Adding of multiple elements is out of scope.

Tasks:

• Modify the existing Add Element API
• Add Element is added as a command
• VSCode API to get the files from the file system is added
• Refresh the tree after adding the element

Enhancement: Prefix commands with extension name

VSCode extension commands can be accessed by pressing 'F1' to open command palette, then typing the command title.

For example, for this extension, there's a command with the title 'New connection'. It can be accessed in VSCode by doing 'F1' -> type 'New connection' in the input box.

It is difficult to tell that this command actually is provided by Explorer.
Therefore I suggest adding a prefix to the command title. something like:
"Endevor-Explr: New Connection"

There are some commands that probably don't even make sense to be exposed to the command palette. For example 'browse element'. Probably wanna take those away from package.json.

Storage of Elements obtained by Retrieve in a path compatible with the Endevor Bridge for Git

During a RETRIEVE on an Element, this Element is stored in subfolder of VS Code Workspace, only named with the Element's type.
To be consistent with the management of Git repositories as provided by the Endevor Bridge for Git, the Elements should be stored in a folder with the name of the Endevor System and Subsystem.

Example:

• retrieve of Element TEXTXML, Type COBOL (extension .cbl), System SIRIS, Subsystem S9
• current storage: .\COBOL\TEXTXML.cbl
• expected storage compatible with the Endevor Bridge for Git: .\SIRIS\S9\COBOL\TEXTXML.cbl

Issue when using https

We recently changed the protocol of the Endevor web service to https. After making this change, we are no longer able to use the Explorer for Endevor. When entering a new connection, a message pops up that reads Waiting for https://host:port to respond.

I can successfully reach the service via the CA Endevor SCM Plug-in for Zowe CLI. When using the CLI plug-in, I do specify --reject-unauthorized false. The Explorer for Endevor does not present me with such an option so that may be related.

Version: 1.37.1
Commit: f06011ac164ae4dc8e753a3fe7f9549844d15e35
Date: 2019-08-15T16:17:25.463Z
Electron: 4.2.7
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 4.15.0-88-generic

Explorer for Endevor v0.9.1

extension doesn't properly load connections stored in settings.json

Upon adding several profiles in the tree, they are also added in settings.json under endevor.connections, but on any subsequent load of the extension, only the default profile is added back to the tree, where as the expected behavior is that all connections previously stored should be loaded automatically.

Enhancement request - Click the element to browse it by default

When I use VS Code explorer or Zowe plugin under VS Code to display MVS datasets and members, I just click the desired member or file and it is opened on the right panel so I can browse it immediately.

Using Explorer for Endevor, I need to first right-click the element and then select Browse Element. This is not so intuitive for me. I would expect the element to be opened in browse mode by default when I click it like the other explorers in VS Code work.

Compatibility with the @zowe/secure-credential-store-for-zowe-cli plugin

This issue probably concerns the plugin @broadcom/endevor-for-zowe-cli.

It seems that the "Explorer for Endevor" extension is not compatible with the @zowe/secure-credential-store-for-zowe-cli plugin: when this plugin is installed, "Explorer for Endevor" manages to display the "filters" and "maps", but fails to list the Elements.

When we uninstall the @zowe/secure-credential-store-for-zowe-cli plugin (and recreate the Endevor profile used), it becomes possible to list the Elements.

Add a New Profile - prompt doesn't disappear when clicking outside the prompt area

Opening the discussion to allow to cancel the action of adding a new profile in the tree by clicking outside the prompting area.

While checking the source code, I can see that the current behaviour is present on most (if not all) input boxes.

Option in case:

export interface InputBoxOptions {
    /**
    * Set to `true` to keep the input box open when focus moves to another part of the editor or to another window.
    */
    ignoreFocusOut?: boolean;

Define a path for storing execution reports for endevor for zowe cli in the endevor profile

This issue is for the @broadcom/endevor-for-zowe-cli plugin. In the absence of a public GitHub site for this plugin, I declare it here.

The execution reports of zowe endevor commands are stored in the current directory, and therefore probably never purged.

You should be able to declare a location for storing execution reports at the zowe endevor profile level, and even if it is possible to declare this location in an environment variable like "ZOWE_ENDEVOR_REPORTS_LOCATION".

This would allow for example to declare the temporary files folder as the storage location for Endevor execution reports, (on Windows the location% temp%).

NOTICE.md doesn't reflect current state of the project

https://github.com/eclipse/che-che4z-explorer-for-endevor/blob/master/NOTICE.md

Third-Party Content needs to be updated as follows:
(-) requests
(+) broadcom/endevor-for-zowe-cli
(+) zowe/imperative

Respect VSCode 'enabledTrash' setting during files deletion

AS IS:
If I have the setting 'files.enableTrash' activated globally or in the E4E folder, I have this error: Error: 'blahblah' to the recycle bin during the element uploading into Endevor. Element is still uploaded, but I have to close outdated tab in VSCode manually and the error message does not look great.

TO BE:
E4E should respect the setting about enabled trash and delete files without recycle bin at all. So there should be no error messages, outdated tabs should be closed accordingly.