Zowe Explorer Download
Roxann Monier
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.
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.
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.
In Zowe V1, you can permanently delete profiles by right-clicking the profile and selecting the Delete Profile option. The feature deletes the profile from your .zowe folder. In Zowe V2, right-click the profile, and select Delete Profile to open the configuration file and manually delete the profile.
Please note:
- Nightly builds are made available to allow preview and early distribution of in-progress work items which may be functionally incomplete and unstable. The coverage and successful execution of tests has not been guaranteed and the builds should be treated accordingly.
- The latest build status is available from #zowe-build Slack channel.
- A nightly build will be removed about 30 days after release.
Check out more Zowe blogs here. Or, ask a question and join the conversation on the Open Mainframe Project Slack Channel #zowe-cli or #zowe-onboarding or any of the other squads. If this is your first time using the Open Mainframe Slack Channel, register here.
The current state of this API is experimental, but the goal is provide a stabilized version that can be used for Zowe Conformance certifications in the future. See this issue for more details: -extension-for-zowe/issues/837.
The main API provided by the /profiles module is called ZoweExplorerApi. It defines a namespace for interfaces for implementing access to z/OS MVS, USS, and JES. You can see that the Zowe Explorer FTP Extension provides such an alternative implementation for USS using the FTP protocol in packages/zowe-explorer-ftp-extension/src/ZoweExplorerFtpApi.ts. The /profiles module itself contains Zowe Explorer's default implementation using z/OSMF in packages/zowe-explorer-api/src/profiles/ZoweExplorerZosmfApi.ts
Zowe Explorer itself exports a ZoweExplorerApi.IApiRegisterClient object that can be used for an alternative implementation to be registered with Zowe Explorer. You can find an example for doing this in packages/zowe-explorer-ftp-extension/src/extension.ts. To be able to do this, your VS Code extension must define a dependency to Zowe Explorer to ensure that VS Code extension activation is performed in the correct order. Therefore, your VS Code extension's package.json must contain
To get started with HLASM, reach out directly to Zowe developers on Slack or follow any number of write-ups on medium.com/zowe. Also, check out the sample REST API in the Zowe GitHub: -spring-boot-api-service.
Launch VS Code, use the Install from VSIX command in the Extensions view command drop-down, or the Extensions: Install from VSIX... command in the Command Palette, and point to the .vsix file (i.e. vscode-extension-for-zowe-2.6.0_vsixhub.com.vsix).
f448fe82f3