Skip to content

Latest commit

 

History

History
 
 

zowe-explorer

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
__mocks__
__mocks__
 
 
__tests__
__tests__
 
 
i18n/sample
i18n/sample
 
 
resources
resources
 
 
scripts
scripts
 
 
src
src
 
 
webviews/edit-attributes
webviews/edit-attributes
 
 
.eslintignore
.eslintignore
 
 
.markdownlint.json
.markdownlint.json
 
 
.mocharc.json
.mocharc.json
 
 
.prettierignore
.prettierignore
 
 
.vscodeignore
.vscodeignore
 
 
CHANGELOG.md
CHANGELOG.md
 
 
Jenkinsfile
Jenkinsfile
 
 
LICENSE
LICENSE
 
 
README.md
README.md
 
 
gulpfile.js
gulpfile.js
 
 
log4jsconfig.json
log4jsconfig.json
 
 
package.json
package.json
 
 
package.nls.json
package.nls.json
 
 
theia_tests.Jenkinsfile
theia_tests.Jenkinsfile
 
 
tsconfig-tests.json
tsconfig-tests.json
 
 
tsconfig.json
tsconfig.json
 
 
webpack.config.js
webpack.config.js
 
 

README.md

Zowe Explorer

version downloads codecov slack

With the removal of keytar shim from VS Code we will be replacing node-keytar with @zowe/secrets-for-zowe-sdk in the v2.10.0 release to avoid user interruptions. Extenders, please check out the usage documentation

v3 Pre-release coming soon with the removal of v1 profile support. Extenders, keep an eye on changes affecting extenders for the full list of changes

Introduction

Zowe Explorer is a sub-project of Zowe, focusing on modernizing mainframe experience. Zowe is a project hosted by the Open Mainframe Project, a Linux Foundation project.

The Zowe Explorer extension modernizes the way developers and system administrators interact with z/OS mainframes by:

  • Enabling you to create, modify, rename, copy, and upload data sets directly to a z/OS mainframe.
  • Enabling you to create, modify, rename, and upload USS files directly to a z/OS mainframe.
  • Providing a more streamlined way to access data sets, uss files, and jobs.
  • Letting you create, edit, and delete Zowe CLI zosmf compatible profiles.
  • Letting you leverage the API Mediation Layer token-based authentication to access z/OSMF.

Contents

Zowe Explorer is compatible only with Theia 1.18.0 or higher. We recommend using a Theia community release as Zowe Explorer could experience possible unexpected behaviors with the latest Theia releases.

Sample use cases

Review the following use cases and their procedures to understand how to work with data sets in Zowe Explorer. For the complete list of features including USS and jobs, see Zowe Explorer Sample Use Cases.

Prerequisite tasks

  • Configure TSO/E address space services, z/OS data set, file REST interface, and z/OS jobs REST interface. For more information, see z/OS Requirements.
  • Create a Zowe Explorer profile.

Getting started

This section includes steps for the tasks you need to complete to get started using Zowe Explorer.

Configure Zowe Explorer, create a team configuration file or a v1 profile (deprecated) for profile manangement, review the sample use cases to familiarize yourself with the capabilities of Zowe Explorer, and you are ready to use Zowe Explorer.

Configuring Zowe Explorer

You can configure Zowe Explorer by changing the extension settings. For more information, see Configuring Zowe Explorer.

When environment conditions do not support the Zowe CLI built-in Credential Manager, see Modifying the Secure Credentials Enabled Setting.

Multifactor authentication support (MFA)

Zowe Explorer supports the use of MFA tokens for authentication. When using zOSMF profiles it is required to connect through the Zowe API Mediation Layer (API ML). Suggested use case for MFA authentication using Zowe Explorer is by logging into the API ML via the right-click login action in Zowe Explorer and when prompted for password enter the MFA token in place of user password, the API will return a JSON token (JWT) that will be used for further authentication.

You can find more information regarding MFA support in Zowe's documentation on integrating with API Mediation Layer.

Create a team configuration file

  1. Navigate to the Side Bar.
  2. Hover over DATA SETS, USS, or JOBS.
  3. Click the + icon.
  4. Select Create a New Team Configuration File.
  5. If no workspace is open, a global configuration file is created. If a workspace is open, chose either a global configuration file or a project-level configuration file.
  6. Edit the config file to include the host and other connection information, and save.

Your team configuration file appears either in your .zowe folder if you chose the global configuration file option, or in your workspace directory if you chose the project-level configuration file option. The notification message that shows in VS Code after config file creation includes the path of the created file.

Create a v1 profile

v1 profiles are deprecated and planned to be removed in Zowe Explorer v3.0.0.

Note: If a team configuration file is in place, v1 profile creation and use will not be available.

  1. Navigate to the Side Bar.
  2. Hover over DATA SETS, USS, or JOBS.
  3. Click the + icon.
  4. Select Create a New Connection to z/OS. The user name and password fields are optional.
  5. Follow the instructions, and enter all required information to complete the profile creation.

New Connection

You can now use all the functionalities of the extension.

Using profiles for the first time

The first time profiles are used you will be prompted for user name and password for the profile's connection. The term password is used loosely to represent all supported authentication secrets like passphrases, passtickets, Multifactor Authentication (MFA) tokens, etc.

Updating securely stored credentials

Securing credentials for v1 profiles and secure fields in the team configuration file are handled by the Zowe Imperative dependency. To update securely stored user names and passwords in Zowe Explorer, the user can right click the profile and select Update Credentials. This prompts the user for the new credentials and the secure credentials vault is updated.

Editing team configuration file

  1. Navigate to the Side Bar.
  2. Hover over DATA SETS, USS, or JOBS.
  3. Click the + icon.
  4. If team configuration file is in place, the Edit Team Configuration File option displays. Edit Team Configuration File

  5. If only a global or project level config is in place, it opens to be edited. If both a global and project level config are in place, the user must select which file to edit. Edit Config Location Option

Profile validation

Note: The following information applies to Zowe CLI V1 profiles (one yaml file for each user profile) and Zowe CLI team profiles (Zowe CLI V2).

Zowe Explorer includes the profile validation feature that helps to ensure that the specified connection to z/OS is successfully established and your profile is ready for use. If a profile is valid, the profile is active and can be used.

By default, this feature is automatically enabled. You can disable the feature by right-clicking on your profile and selecting the Disable Validation for Profile option. Alternatively, you can enable or disable the feature for all profiles in the VS Code settings

  1. In VS Code, navigate to Settings.
  2. Navigate to Zowe Explorer settings.
  3. Check the Automatic Profile Validation checkbox to enable the automatic validation of profiles option. Uncheck to disable.
  4. Restart VS Code.

Use base profile and token with existing profiles

As a Zowe user, you can leverage the base profile functionality to access multiple services through Single Sign-on. Base profiles enable you to authenticate using the Zowe API Mediation Layer (API ML). You can use base profiles with more than one service profile. For more information, see Base Profiles.

Note: Before using the base profile functionality with v1 profiles, ensure that you have Zowe CLI v6.0.0 or higher installed.

  1. Zowe Explorer has a right click action for profiles to log in and log out of the authentication service for existing Base profiles. If a v1 Base profile hasn't been created, open a terminal and run the following Zowe CLI command: zowe auth login apiml.

  2. Follow the instructions to complete the login. A local base profile is created that contains your token.

    Note: For more information about the process, see Token Management.

  3. Open VS Code and select the Zowe Explorer icon in the Side Bar.

  4. Hover over DATA SETS, USS, or JOBS.

  5. Click the + icon.

  6. Select the profile you use with your base profile with the token.

    The profile appears in the tree and you can now use this profile to access z/OSMF via the API Mediation Layer.

For more information, see Integrating with API Mediation Layer.

Log in to the Authentication Service

If the token for your base profile is no longer valid, you can log in again to get a new token with the Log in to Authentication Service feature.

Notes:

  • The feature is only available for base profiles.
  • The feature supports only API Mediation Layer at the moment. Other extenders may use a different authentication service.

  1. Open VS Code and select the Zowe Explorer icon in the Side Bar.

  2. Right-click your profile.

  3. Select the Log in to Authentication Service option.

    You are prompted to enter your username and password.

The token is stored in the corresponding base profile file, YAML file for v1 Profiles, or the team configuration file.

If you do not want to store your token, you can request the server to end your session token. Use the Log out from Authentication Service feature to invalidate the token:

  1. Open Zowe Explorer.
  2. Hover over DATA SETS, USS, or JOBS.
  3. Click the + icon.
  4. Right-click your profile.
  5. Select the Log out from Authentication Service option.

Your token has been successfully invalidated.

Usage tips

  • Use the Add to Favorite feature to permanently store chosen data sets, USS files, and jobs in the Favorites folder. Right-click on a data set, USS file or jobs and select Add Favorite.

  • Syntax Highlighting: Zowe Explorer supports syntax highlighting for data sets. You can search for and install such extensions in VS Code Marketplace.

  • Update a profile: Right-click a profile, select the Update Profile option, and modify the information inside the profile.

  • Delete a profile: For Zowe V1 profiles, right-click a profile and select the Delete Profile option to permanently delete the profile and delete the profile from your .zowe folder.

    For Zowe V2 profiles, Delete Profile opens the zowe.config.json file for the user to delete the profile manually:

    Delete a V2 profile

  • Hide a profile: You can hide a profile from the profile tree by right-clicking the profile and selecting the Hide Profile option. To unhide the profile, click the + button and select the profile from the quick pick list.

  • Open recent members: Zowe Explorer lets you open a list of members you worked on earlier. You can access the list by pressing Ctrl+Alt+R (Windows) or Command+Option+R (Mac).

For the comprehensive Zowe Explorer documentation that also includes information about USS and Jobs interactions, see the Zowe Explorer documentation in Zowe Docs.

Keyboard Shortcuts

  • Restart Zowe Explorer

    • Windows: ctrl+alt+z
    • Mac: ⌘+⌥+z

  • Open Recent Member

    • Windows: ctrl+alt+r
    • Mac: ⌘+⌥+r

  • Search in all Loaded Items

    • Windows: ctrl+alt+p
    • Mac: ⌘+⌥+p

Extending Zowe Explorer

You can add new functionalities to Zowe Explorer by creating your own extension. For more information, see Extensions for Zowe Explorer.

Tip: View an example of a Zowe Explorer extension: Zowe Explorer FTP extension documentation.

Known Issues

Bidirectional languages

Files written in languages primarily read from right to left (Arabic, Hebrew, many Asian languages) can include portions of text that are written and read left to right, such as numbers.

These bidirectional (BiDi) languages are not currently supported in Visual Studio Code. (See Issue #86667 for more information.)

As a result, VS Code extensions like Zowe Explorer, Zowe Explorer CICS Extension, and Zowe Explorer FTP Extension are not able to support BiDi languages in files.

More information

  • For the complete Zowe Explorer documentation, see Zowe Docs.
  • Join the #zowe-explorer channel on Slack to stay in touch with the Zowe community.

Sample use cases extended

View data sets and use multiple filters

  1. Navigate to the Side Bar.
  2. Open the DATA SETS bar.
  3. Hover over the profile that you want to apply the filter to.
  4. Click the Search icon.
  5. Enter a pattern you want to create a filter for. The data sets that match your pattern(s) are displayed in the Side Bar.

Tip: To provide multiple filters, separate entries with a comma. You can append or postpend any filter with an * to apply wildcard searching. You cannot enter an * as the entire pattern.

View Data Set

Back to sample list

View data sets with member filters

  1. Navigate to the Side Bar.
  2. Open the DATA SETS bar.
  3. Hover over the profile that you want to apply the filter to.
  4. Click the Search icon.
  5. Enter a search pattern in the HLQ.ZZZ.SSS(MEMBERNAME) format to filter for and display the specified member in the tree.

View Data Set With Member Pattern

Note: You cannot favorite a data set or member that includes a member filter search pattern.

Back to sample list

Refresh the list of data sets

  1. Navigate to the Side Bar.
  2. Click Refresh All button (circular arrow icon) on the right of the DATA SETS explorer bar.

Back to sample list

Rename data sets

  1. Navigate to the Side Bar.
  2. Open the DATA SETS bar.
  3. Select a data set you want to rename.
  4. Right-click the data set and select the Rename Data Set option.
  5. Enter the new name of the data set.

Rename Data Set

Back to sample list

Copy data set members

  1. Navigate to the Side Bar.
  2. Open the DATA SETS bar.
  3. Select a data set member you want to copy.
  4. Right-click the member and select the Copy Member option.
  5. Right-click a data set that you want to paste the member to and select the Paste Member option.
  6. Enter the name of the copied member.

Copy Data Set

Back to sample list

Edit and upload a data set member

  1. Navigate to the Side Bar.

  2. Open the DATA SETS bar.

  3. Open a profile.

  4. Select the data set member you want to edit.

    Note: To view the members of a data set, click the data to expand the tree.

    The data set member is displayed in the text editor window of VS Code.

  5. Edit the document.

  6. Navigate back to the data set member in the explorer tree, and press Ctrl+S or Command+S (OSx) to upload the member.

    Your data set member is uploaded.

Note: If someone else has made changes to the data set member while you were editing it, you can merge your conflicts before uploading the member to the mainframe.

Edit

Back to sample list

Use the save option to prevent merge conflicts

  1. Navigate to the Side Bar.

  2. Open the DATA SETS bar.

  3. Open a member of a data set you want to edit.

  4. Edit the selected member.

  5. Press Ctrl+S or Command+S (OSx) to save the changes.

    If the original content in your local version no longer matches the same file in the mainframe, a warning message displays advising the user to compare both versions.

  6. If necessary, use the editor tool bar to resolve any merge conflicts.

Save

Back to sample list

Create a new data set and add a member

  1. Navigate to the Side Bar.
  2. Open the DATA SETS bar.
  3. Right-click on the profile where you want to create a data set and select Create New Data Set.
  4. Enter a name for your data set.
  5. From the drop-down menu, select the data set type that you want to create.
  6. Select +Allocate Data Set to create the data set.
  7. Right-click your newly-created data set and select Create New Member.
  8. Enter a name for your new data set member and press the Enter key. The member is created and opened in the workspace.

Back to sample list

Create data sets and specify the parameters

  1. Navigate to the Side Bar.

  2. Open the DATA SETS bar.

  3. Right-click the profile you want to create a data set with and select Create New Data Set.

  4. Enter a name for your data set and press Enter.

  5. From the drop-down menu, select the data set type that you want to create and press Enter.

  6. Select Edit Attributes in the drop-down menu and press the Enter key.

    The attributes list for the data set appears. You can edit the following attributes:

    • Allocation Unit

    • Average Block Length

    • Block Size

    • Data Class

    • Device Type

    • Directory Block

    • Data Set Type

    • Management Class

    • Data Set Name

    • Data Set Organization

    • Primary Space

    • Record Format

    • Record Length

    • Secondary Space

    • Size

    • Storage Class

    • Volume Serial

  7. Select the attribute you want to edit, provide the value in the Command Palette, and press the Enter key.

  8. (Optional) Edit the parameters of your data set.

  9. Select the + Allocate Data Set option to create the data set.

    The data set has been created successfully.

    Parameters

Back to sample list

Delete data sets and data set members

  1. Navigate to the Side Bar.

  2. Open the DATA SETS bar.

  3. Select one or more data sets and/or data set members.

    Tip: Hold the Ctrl/Cmd key while clicking data sets or data set members to select more than one item for deletion.

  4. Press the Delete key on your keyboard.

    Alternatively, right-click on the item and select the Delete Data Set or Delete Member option.

  5. Confirm the deletion by clicking Delete in the drop-down menu.

    Delete Data Sets and Members

Back to sample list

View and access multiple profiles simultaneously

  1. Navigate to the Side Bar.
  2. Open the DATA SETS bar.
  3. Click the + icon on the right of the DATA SET bar.
  4. Select a profile from the drop-down menu in the Command Palette. This adds the profile to the Side Bar, from where you can search for data sets.

Add Profile

Back to sample list

Submit a JCL

  1. Navigate to the Side Bar.
  2. Open the DATA SETS bar.
  3. Select the data set or data set member you want to submit.
  4. Right-click the data set or member and select the Submit Job option.
  5. If the extension setting "Jobs: Confirm Submission" matches the job that you are trying to submit, you will be presented with a submission confirmation dialog.
    • Click Submit within the dialog to confirm submission, or click Cancel to cancel the operation.
    • Otherwise, the job has been submitted.
  6. Once the job has been submitted, click on the hyperlink within the notification pop-up to view the submission (if desired).

Submit a JCL

Back to sample list

Allocate Like

  1. Navigate to the Side Bar.
  2. Open the DATA SETS bar.
  3. Right-click a data set and select the Allocate Like (New Data Set with Same Attributes) option.
  4. Enter a new data set name.

Allocate Like

Back to sample list