Zowe Explorer for Visual Studio Code
IntroductionZowe Explorer for VS Code provides access to mainframe resources in Visual Studio Code. Zowe Explorer provides a modern, familiar, user-friendly interface that enables mainframe developers and system programmers to:
Zowe Explorer for VS Code is a Zowe® component that focuses on modernizing the mainframe experience. Zowe is hosted by the Open Mainframe Project™, a Linux Foundation® initiative. Contents
Prerequisite tasksUse various services to communicate with system resources and extract system data on the mainframe:
There are multiple extensions that offer additional protocols and functionality. See the Explorer for Visual Studio Code Zowe V3 section in the Zowe V2 and V3 Conformant Landscape for a complete list of conformant extensions. Getting startedConfigure Zowe Explorer for VS Code and confirm you are able to access the mainframe with your team configuration. Configuring Zowe Explorer for VS CodeConfigure Zowe Explorer for VS Code by changing the extension settings. For more information, see Configuring Zowe Explorer. Confirming your team configurationTeam configuration stores connection information to access the mainframe. Check that you have your team configuration in place. If you are missing your team configuration files,
Creating a team configuration fileA team configuration file stores connection information to mainframe services in profiles, making team configuration easy to maintain and share with others in your organization. Team configuration should be created by an administrator or team lead who understands what connection information is needed and can efficiently manage it. When setting up team configuration, it is important to understand your team's requirements for use and the options available to ensure these are met. Refer to Zowe Docs for documentation on understanding and implementing team configuration: Note: Team configuration can apply across three core components of the Zowe project, Zowe Explorer for VS Code, Zowe Explorer for IntelliJ IDEA, and Zowe CLI. Using profiles for the first timeThe first time a team configuration profile is used, you are prompted for a user name and password for the profile's connection. The term password is used loosely to represent all supported authentication secrets, such as passphrases, passtickets, Multifactor Authentication (MFA) tokens, etc. Updating securely stored credentialsSecure fields in the team configuration file are handled by the Zowe Imperative dependency. To update securely stored user names and passwords in Zowe Explorer:
Other authentication methodsZowe Explorer for VS Code supports multiple authentication methods including basic authentication, multi-factor authentication, tokens, and certificates. See Zowe Docs for more information about these other authentication methods. Usage tipsMake the best use of Zowe Explorer for VS Code with these usage tips. See Zowe Docs for a complete list of use cases explaining how to work with data sets, USS files, and jobs in Zowe Explorer for VS Code. Keyboard Shortcuts
Extending Zowe ExplorerYou 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 in the Zowe Explorer FTP extension documentation. Known issuesBidirectional languagesFiles 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](https://github.com/microsoft/vscode/issues/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
|
