Explorer for Endevor

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

View an element
Retrieve an element with dependencies
View element details
Create Endevor profiles, including Endevor inventory location profiles
Use Zowe CLI base profiles
Perform an Edit action
Perform a Generate action
Print a listing

Explorer for Endevor is a part of the Che4z open-source project. The extension is also part of Code4z, an all-round package that offers a modern experience for mainframe application developers, including the HLASM Language Support, COBOL Language Support, Zowe Explorer, and Debugger for Mainframe extensions.

Prerequisites

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

Client-side prerequisites:

Install Zowe CLI v1-LTS
Install CA Endevor plug-in for Zowe CLI version 6.0.0
Access to CA Endevor

Host-side prerequisites:

CA Endevor version 18.0.12 or higher with the following PTFs applied:
- (v18.0.x only) PTFs SO09580, SO09581, SO10013, and SO11268
- (v18.1.x only) PTF SO11272
- (Optional)(Web Services with STC Pooling only) PTFs SO03928 and SO03929
CA Endevor Web Services v2 installed and configured.

Getting Started

Create an Endevor profile and inventory location profile and review use cases to see how you can use the full potential of Explorer for Endevor.

Create Endevor Profile

Explorer for Endevor uses endevor and endevor-location profiles for CA Endevor Plug-in for Zowe CLI to access Endevor inventory locations on the mainframe and work with elements. If you already have a CA Endevor plug-in Zowe CLI profile, you can access inventory locations immediately, using your profile in the tree.

If you do not have a profile, you can create one in Explorer for Endevor.

Follow these steps:

Click the Add a New Profile button to add a new Endevor profile.
Enter a name for your profile.
Enter your Endevor URL in the https://host:port format.
(Optional) Enter your username and password to add your mainframe credentials to the profile.

Adding your credentials to your profile lets you access different Endevor locations without having to enter your credentials more than once.

Note: If your profile does not include credentials during the first session of Explorer for Endevor, you are prompted to provide credentials.
Select one of the options that either accept or reject connections with self-signed certificates.

Your profile is now available in the tree. You can also reuse the same Endevor profile in Zowe CLI directly.

Create Endevor Location Profile

Once you have an Endevor profile, you need to add an Endevor location profile. Endevor location profiles consist of Endevor instance, Endevor path that includes environment, system, subsystem, stage number, and element type, CCID, and Comment. Endevor location profiles let you view and work with elements of specified Endevor locations.

Follow these steps:

Click the + icon next to your Endevor profile to add a new location profile.
Create a name for the Endevor location profile and press Enter.
Select an instance from the drop-down menu and press Enter.
Enter Endevor path and press Enter.

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

Note: If you are unsure about the system, subsystem, or type parameters, you can substitute any of these parameters with a * wildcard.
(Optional) Enter CCID and press Enter.
(Optional) Enter comment and press Enter.

Notes:
- 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 location profile at any step by pressing Escape.

You successfully created an Endevor profile.

If an existing endevor-location profile that you created in Zowe CLI does not have the instance, environment, and stage numbers parameters specified, the extension cannot reach the inventory location. In this case, recreate an inventory location profile with the entire location path so that Explorer for Endevor can access elements in the specified inventory.

Use Cases

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

View an element: You can view the contents, summary report, and source level information of the selected element.
View details: You can 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.
Retrieve an element: You can download the selected element.
Retrieve an element with dependencies: You can download the selected element with dependencies.
Edit: The Edit action enables you to download an element to your workspace, edit and upload the selected element step by step. All you need to do is edit an element and press CTRL+S or Command+S to upload the edited element back.
Generate: You can call the Generate action for an element to invoke the Generate Processor that creates an executable form of the element.
Print listing: You can reveal the output of the performed Generate action.

View an Element

You can view the contents, summary, and source level information of an element by clicking on the element in the tree. 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.

Follow these steps:

Hover over an element you want to view.
Click the element to see the contents of the element.

The contents of the element appear in the editor area.

View Details

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

Follow these steps:

Right-click on an element.
Select the View Details option.

The details of the element appear in the editor area.

Retrieve an Element

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

Follow these steps:

Right-click on an element.
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.

Follow these steps:

Right-click on an element.
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.

Edit

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

Follow these steps:

Right-click on an element.
Select the Edit option.

The contents of the element appear in the editor area. You can now edit the element.
Press CTLR+S or Command+S when you want to save and upload the edited element back.
Specify any accessible Endevor path and a name for the element.
Enter a CCID.
Enter a comment.

You successfully edited, saved, uploaded the element.

Generate

The Generate action creates an executable form of the element, together with any associated outputs such as listings. You can use the Generate option to run the CA Endevor Generate action for a selected element.

Follow these steps:

Right-click on an element.
Select the Generate option.

The successful Generate call shows a pop-up with two options Print listing and Cancel and the following message:
```
Generate successful! Would you like to see the listing?
```
(Optional) Click Print listing to see the Generate output.

Alternatively, click Cancel.

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

You successfully performed the Generate action.

If Generate is not successful, the listing is displayed automatically.

Print listing

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

Follow these steps:

Right-click on an element.
Select the Print listing option.

The contents of the listing appear in the editor area.

You successfully printed the listing.

Base Profiles

You can use your Zowe CLI default base profile in Explorer for Endevor if you do not have an Endevor profile. 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. You can run the zowe profiles list base-profiles --sc in the CLI to check if you have a base profile that you can use. If you do not have a base profile and want to create one, run the following Zowe CLI command:

zowe profiles create base <baseprofileName> --user <myusername123> --password<mypassword123> --host <myhost> --port <portnumber> --reject-unauthorized false

Ensure that you set your newly-created base profile as the default base profile. To do so, run the following command:

 zowe profiles set-default base-profile <baseprofileName>

For more information, see the Base Profile section on Zowe Docs.

Manage your Profiles

You can perform the following actions to manage your profiles:

Edit a profile: You can edit a profile or update your credentials, using the Zowe CLI and the zowe profiles update endevor-profile <profileName> and zowe profiles update endevor-location-profile <profileName> command. The commands enable you to update the details of existing profiles. If you use the CLI commands to update your profile, ensure that you click the refresh button in the extension so that the changes take effect.
Hide a profile: If you do not want to have some of your profiles in the tree, you can hide such profiles. To hide a profile, right-click on the profile and select Remove Profile option.

Note: The Remove Profile action does not permanently delete the profile.
Delete a profile: You can permanently delete your profile from the extension. To delete a profile, issue the CLI command zowe profiles delete endevor-profile <profilename>.

Environment Variables

You can define environment variables to execute Zowe CLI commands more efficiently. For more information, see Using Environment Variables on Zowe Docs.

Configure Explorer for Endevor

You can configure the following settings of the extension:

The location where the Edit command stores elements locally
Endevor locations that will be loaded at startup
The number of parallel HTTP requests supported by Endevor

To access the Explorer for Endevor settings, click Manage (the cog icon on the activity bar) > Settings > Extensions > Explorer for Endevor.

List of Limitations

See the list of limitations that the current version of Explorer for Endevor has to familiarize yourself with possible limitations or behavior of the extension. The list includes the following points:

Searching elements by comment and CCID is not supported.

You can search using the instance, environment, stageNumber, system, subsystem, and type parameters.
Zowe CLI Secure Credential Store is not supported.

If you have SCS-enabled Endevor profiles, you need to recreate the profiles to successfully use them in Explorer for Endevor.
Only the UTF-8 character encoding is currently supported.

Known Issues

The following topics contain information that can help you troubleshoot problems when you encounter unexpected behavior while using Explorer for Endevor:

Topic 1 — Removed profile persists in the tree.

Symptoms:

The deleted profile does not disappear from the tree after the deletion.

Cause:

This behavior occurs if you use the CLI command to delete your profile but do not delete the profile from the Explorer for Endevor settings.json file.

Solution:

To permanently delete the profile from the tree, use the extension settings.

Follow these steps:

Navigate to the VS Code settings.
Open Explorer for Endevor Settings and edit the settings.json file.
Delete the service and elementLocations properties of the profile you want to delete from the tree.
Save the settings.json file.

You successfully deleted your profile from the extension.

Contribute to Explorer for Endevor

We encourage you to contribute to Explorer for Endevor.

How can you improve Explorer for Endevor? 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.

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 CA 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 CA Support Online
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 CA 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 CA software and Broadcom shall not be responsible for these effects or any resulting degradation in performance of the Broadcom CA software. Severity 1 cases must be opened via telephone and elevations of lower severity incidents to Severity 1 status must be requested via telephone.

Name		Name	Last commit message	Last commit date
Latest commit History 315 Commits
.vscode		.vscode
packages		packages
.editorconfig		.editorconfig
.eslintignore		.eslintignore
.eslintrc.js		.eslintrc.js
.gitattributes		.gitattributes
.gitignore		.gitignore
.prettierignore		.prettierignore
.vscodeignore		.vscodeignore
CHANGELOG.md		CHANGELOG.md
CONTRIBUTING.md		CONTRIBUTING.md
Jenkinsfile		Jenkinsfile
LICENSE		LICENSE
NOTICE.md		NOTICE.md
README.md		README.md
package-lock.json		package-lock.json
package.json		package.json
tsconfig.json		tsconfig.json
yarn.lock		yarn.lock

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Explorer for Endevor

Table of Contents

Prerequisites