zowe/zowe-explorer-vscode

Visual Studio Code Extension for Zowe, which lets users interact with z/OS Data Sets, Unix System Services, and Jobs on a remote mainframe instance. Powered by Zowe SDKs.

Zowe Explorer

Welcome to Zowe Explorer! Zowe Explorer brings mainframe capabilities to modern IDEs, such as VS Code. Zowe is a project hosted by the Open Mainframe Project, a Linux Foundation project.

Join our Slack channel to connect with the Zowe community.

Requirements

Client-side prerequisites for development:

• Install Node.js v14.0 or later.
• Install Yarn Classic.

Host-side prerequisites for connection:

• 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.

Directory Structure

Zowe Explorer repository includes several folders with files that let you build and configure various aspects of the extension. The bulk of the Zowe Explorer source code is in the packages directory. The packages folder has the following structure:

• ├──packages — includes source code of Zowe Explorer, various Zowe Explorer-related extensions, and the extensibility API
  
  • ├──eslint-plugin-zowe-explorer — includes necessary files to configure ESLint plug-in for Zowe Explorer
  • ├──zowe-explorer-api — includes files to set up and use Extensibility API for Explorer. The API has two modules: Profiles API and Tree API.
  • ├──zowe-explorer-ftp-extension — includes files to set up and use the FTP extension for Zowe Explorer.
  • ├──zowe-explorer — core Zowe Explorer source files, ReadMe, Changelog, and more.

Build Locally

Ensure that you meet the software requirements before you build and test your Zowe Explorer.

Clone the repository, build a VSIX file, and start working with the extension.

1. Clone the repository by issuing the following command in your local command-line interface:

   git clone https://github.com/zowe/zowe-explorer-vscode.git

2. Change directories into the newly-cloned repository:

   cd vscode-extension-for-zowe

3. From your local copy of the repository, issue the following commands:

   yarn install && yarn run package

You can find the VSIX file in the dist folder.

Now install the extension to VS Code.

1. Navigate to the Extensions menu in VS Code and click the ... button in the top-left corner of the pane.
2. Select Install from VSIX and select the .vsix file that was created by the commands you issued earlier.
3. Restart Visual Studio Code.

You can now use the extension.

For more information on how to run tests for the extension, see Developer Setup.

Available Documentation

The current repository of the VS Code extension Zowe Explorer includes several ReadMes that highlight different aspects of using the extension.

Use the following list with the description and links to find the topics of your interest:

Core Zowe Explorer ReadMe — contains information about how to install, configure, and use Zowe Explorer. This ReadMe helps you to familiarize yourself with the basic features of the extension.

Zowe Explorer ESlint Plug-in ReadMe — contains information about how to install ESLint and configure ESLint rules. ESLint helps you to find and fix problems in your JavaScript code.

Zowe Explorer Extensibility API ReadMe — contains information about how to extend the capabilities of Zowe Explorer, using the extensibility API.

Zowe Explorer FTP Extension ReadMe — contains information about how to install and use the Zowe Explorer extension for FTP. The extension adds the FTP protocol to Zowe Explorer, enabling you to use z/OS FTP Plug-in for Zowe CLI profiles to connect and interact with z/OS USS and MVS.

Note: Zowe Explorer FTP extension is an example that shows how the extensibility API is used to add new capabilities to Zowe Explorer.

Zowe Explorer Developer Setup — contains information on how to install, build, and test Zowe Explorer.

Zowe Explorer Developing for Theia — contains information on how to develop for the Web-based IDE Eclipse Theia.

How to Contribute

We encourage you to contribute to Zowe Explorer!

Check the current open issues to choose where you can contribute. You can look for the help wanted-labeled issues to find issues that require additional input. If you are new to the project, you might want to check the issues with the good first issue label.

To report a bug or request a specific feature, please open a GitHub issue using the appropriate template. Feature requests will be added to our backlog after it receives 10 upvotes from the community.

Also, you can check our GitHub Projects board for a more convenient view of issues, which are organized by priority and work-in-progress status.

For more information on how to contribute, see Contributor Guidance.

External Links

Check out more about using Zowe Explorer and Zowe on Medium and Awesome Zowe.

Project Structure and Governance

Zowe Explorer is a component of the Zowe Open Mainframe Project, part of the Linux Foundation.

To learn more about how Zowe is structured and governed, see the Technical Steering Committee Structure and Governance documentation.

zowe-explorer-vscode's Issues

Tests and mocks are compiled with the build

Our tests and mocks are compiled with the build. This leads to us shipping our unit tests in the extension and also confuses jest with the mocks folder.

jest-haste-map: duplicate manual mock found:
  Module name: DatasetTree
  Duplicate Mock path: C:\Users\XXXXXXX\Documents\GitHub\vscode-extension-for-zowe\out\src\__mocks__\DatasetTree.js
This warning is caused by two manual mock files with the same file name.
Jest will use the mock file found in:
C:\Users\XXXXXXX\Documents\GitHub\vscode-extension-for-zowe\out\src\__mocks__\DatasetTree.js
 Please delete one of the following two files:
 C:\Users\XXXXXXX\Documents\GitHub\vscode-extension-for-zowe\src\__mocks__\DatasetTree.ts
C:\Users\XXXXXXX\Documents\GitHub\vscode-extension-for-zowe\out\src\__mocks__\DatasetTree.js

Add Sample Use Cases for USS Functionality to the README

Sample use cases for USS functionality should be added to the README so that folks can easily learn how to make use of related features.

Build output directory not cleared on each build

The out directory is not cleaned prior to each build run. This could lead to stale files left in the out directory that get shipped with the extension.

Jobs tree has no "remove profile" action

JOBS tree there is missing "Remove profile" action. Right clicking on the profile allows only to set prefix and owner.

I've also noticed for USS when right clicking on profile it allows "delete" action, which should probably be restricted to unix files.

80% code coverage not achieved by unit tests

Below is the current report of code coverage for unit tests:

----------------|----------|----------|----------|----------|-------------------|
File            |  % Stmts | % Branch |  % Funcs |  % Lines | Uncovered Line #s |
----------------|----------|----------|----------|----------|-------------------|
All files       |    81.22 |    80.27 |    58.33 |    86.06 |                   |
 DatasetTree.ts |    81.25 |    83.33 |    93.33 |    80.65 |... 81,182,183,185 |
 ZoweNode.ts    |    98.21 |    97.22 |      100 |    98.11 |                70 |
 extension.ts   |    78.26 |    72.41 |    43.14 |    85.03 |... 33,635,636,638 |
----------------|----------|----------|----------|----------|-------------------|

That brings up the following issues:

• extension.ts only has 78.26% of statements covered
• extension.ts only has 43.14% of functions covered
• overall only 58.33% of functions are covered

These must be addressed if this is officially to be a production application

Introduce Favorites functionality to USS extension

Favorites is a useful facility in USS

Merging of trees into single tree structure

To make a more complete user experience the three views for USS, Datasets and Jobs can be merged into a single explorer view allowing all z/OS aspects to be viewed together and support more advanced functionality across the different trees.

The main difference is that the root will be the z/OS connection or zowe profile rather than a single specific view and has expandable elements for the different data sections

This follows on from #61

VSCode extension: Merge Jobs extension with original

This is the item to include the Jobs extension into VSCode

VS Code on RedHat fails to load profile

Hi , I have added my zowe/bright profile and can do all sorts of things (listing DS, issuing commands etc) from the command line but when I try to add the profile to VSCODE it says :
Must have user & password OR base64 encoded credentials.

Any Ideas on how I can go about to test this ?

If I go see the zowe plugin logs I see:
imperative.log=====================================================================
[2019/01/23 16:18:24.749] [INFO] [AbstractProfileManager.js:325] Loading profile "LBI9" of type "zosmf"...
[2019/01/23 16:18:24.750] [DEBUG] [AbstractProfileManager.js:354] Load count for "type_name" key "zosmf_LBI9" is 1
[2019/01/23 16:18:24.752] [DEBUG] [AbstractProfileManager.js:365] Invoking the implementation to load profile "LBI9" of type "zosmf".
[2019/01/23 16:18:24.753] [DEBUG] [BasicProfileManager.js:246] Loading profile "LBI9" (load default: "false") of type "zosmf".
[2019/01/23 16:18:24.755] [INFO] [AbstractProfileManager.js:399] Validating profile "LBI9" of type "zosmf"...
[2019/01/23 16:18:24.758] [DEBUG] [CliProfileManager.js:326] Setting profile field host from command line option host
[2019/01/23 16:18:24.759] [DEBUG] [CliProfileManager.js:326] Setting profile field port from command line option port
[2019/01/23 16:18:24.760] [DEBUG] [CliProfileManager.js:326] Setting profile field user from command line option user
[2019/01/23 16:18:24.762] [DEBUG] [CliProfileManager.js:326] Setting profile field password from command line option password
[2019/01/23 16:18:24.768] [DEBUG] [CliProfileManager.js:326] Setting profile field rejectUnauthorized from command line option reject-unauthorized
[2019/01/23 16:18:24.770] [DEBUG] [CliProfileManager.js:326] Setting profile field basePath from command line option base-path
[2019/01/23 16:18:24.772] [INFO] [AbstractProfileManager.js:375] Load API completed for profile "LBI9" of type "zosmf".

and :
zowe.log=======================================================================
[2019/01/23 16:18:24.772] [DEBUG] [ZosmfSession.js:26] Creating a z/OSMF session from the profile named LBI9

VSCODE About:
Version: 1.30.2
Commit: 61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8
Date: 2019-01-07T22:49:48.319Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
OS: Linux x64 3.10.0-862.14.4.el7.x86_64

Retrieve data set attributes one by one rather than all at once

This is a suggestion for a potential enhancement by a user. Currently, when the user enters a data set pattern, we immediately list data sets and request data set attributes (the same REST request as done by the command zowe files ls ds "my.data.set" --attributes).

In order to mitigate errors encountered when listing data sets that are migrated or tracked by software such as Panvalet, we could wait to request attributes until we have gotten a list of data set names, and then make a request for attributes for each individual data set. Any data sets that encounter an error when listing attributes could then potentially be hidden, or displayed in the list with an [X] and an error tooltip. This would however result in more REST requests before the data set view would be usable so it might impact the performance of the extension.

Provide a refresh option for USS files

if you view a file on USS, then update it on z/OS (eg. its a log file and is constantly being updated by a server), then close and view the file again in VSC it shows a cached old copy.

Refresh could be performed by clicking on the item again or a dropdown menu item.

Customer contact: Mark Cocker IBM

Expect Error: Specify the USS file name when editing non USS file

When editing a non data set or USS file with the extension installed, the above error message displays. Introduced in 0.10.1

Prompt when adding profile to USS refer to Data Set Explorer

Clicking on the + sign to the right of "UNIX SYSTEM SERVICES (USS)" results in the prompt"Select a Profile to Add to the Data Set Explorer".

This should instead refer to UNIX SYSTEM SERVICES (USS).

By comparison clicking on + next to JOBS results in prompt "Select a Profile to Add to the Jobs Explorer".

Problems with local name of files.

When attempting to run a shell task, the following error occurs due to the profile name in square brackets:

Line: 1 Char: 114

• ... -extension-for-zowe-0.8.3\resources\temp\SIS.JGL.FTES(HELLOW)[zoszdt]

•                                                               ~
  

Array index expression is missing or not valid
+ CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingArrayIndexExpression

Opearating System is Windows 10

System tests require at least 2 .zowe profiles

Related to #6, the system tests will fail if there are not 2 profiles defined in the .zowe directory. This caught me by surprise while trying to test #1, so I added this constriction to the readme for now.

The final solution should be to make the system tests independent of the .zowe folder and give them the control to configure any file system needs.

Use USS local file structure for datasets

To avoid the unsightly THEFILE[mypofile] on the editor tab, remove the square bracket profile and add the profile name further up the local file directory structure

VSCode exploitation of new API for Add function for checking USS file tagging#362

Add function for checking USS file tagging#362

Your VS Code extension is affected by a security issue and have been blocked

Hi,

Kenneth here from the VS Code team.

Your extension is affected by https://code.visualstudio.com/blogs/2018/11/26/event-stream, and we have blocked your extension.

In order to enable your extension again the workflow is:

1. Fix the extension, submit an update to the marketplace
2. Send mail to [email protected] and [email protected] and notify us.
3. We will verify that the extension is okay
4. Our marketplace will publish the extension again and we'll remove the extension from the blocklist

/k

Merge with original VSCode extension

@Colin-Stone commented on Mon Apr 01 2019

Keep all of the Zowe VSCode extensions as one extension

---

@Colin-Stone commented on Mon Apr 01 2019

Consider creating a joined up taxonomy structured as follows:

Zowe
|
| ----Favorites
|
| ---- MyProfile 1
		|
		| ---- Datasets
		|		|
		|		| ---- MYUSER.TEST.JCL
		|		|	:	:
		|		| ---- MYUSER.PROD.JCL
						|
						| ---- COMPARE
						| ---- COPY
		|
		| ---- USS Files
		|		|
		|		| ---- /u/myuser
		|				|
		|				| ---- file1.txt
		|
		| ---- Jobs
				|
				| ---- AJOB1(INPUT)
				| ---- AJOB2(ACTIVE)
				| ---- TSU1(ABEND S222)

No way to specify where profiles are located within the extension

Right now, the extension is hardcoded to look in the ~/.zowe folder for profiles. This is not ideal.

There should be some sort of mechanism for the extension. At the very least it could also look for the zowe environment variable to determine where profiles are stored. A further item could be added to have vs code look for a config file in a project directory / user settings directory. This file could work similar to how the markdownlint.json, tsconfig.json, or tslint.json works.

Update Zowe VSCode extension

As Michelle, I want the Zowe VSCode Extension to work properly with profiles stored in plain text so that I can continue to make use of it to improve my interaction with z/OS datasets.

Update Zowe VSCode extension to work with profile credentials now stored in plain text under .zowe. Update documentation. No requirement to also work with securely stored profiles (eg 1.x).

Enhance error message to say that version is incompatible, please upgrade to the latest version.

*Accept feature with PM when complete (This & zowe/zowe-cli#16 both in this Sprint)
8 point story

Display data set attributes

It would be a cool enhancement to be able to right click a data set in the data set explorer and show a popup or another mechanism to display attributes such as volume, size etc. of the data set

VSCode extension: Merge USS extension with original

@Colin-Stone commented on Mon Apr 01 2019

Keep all of the Zowe VSCode extensions as one extension

---

@Colin-Stone commented on Mon Apr 01 2019

Consider creating a joined up taxonomy structured as follows:

Zowe
|
| ----Favorites
|
| ---- MyProfile 1
		|
		| ---- Datasets
		|		|
		|		| ---- MYUSER.TEST.JCL
		|		|	:	:
		|		| ---- MYUSER.PROD.JCL
						|
						| ---- COMPARE
						| ---- COPY
		|
		| ---- USS Files
		|		|
		|		| ---- /u/myuser
		|				|
		|				| ---- file1.txt
		|
		| ---- Jobs
				|
				| ---- AJOB1(INPUT)
				| ---- AJOB2(ACTIVE)
				| ---- TSU1(ABEND S222)

Interacting with services through APIML

When I attempt to interact with z/OSMF through the API Mediation Layer from the Zowe VSCode Extension (e.g. list data sets), I receive the following error message:

Retrieving response from zowe.List Error: z/OSMF REST API Error: Rest API failure with HTTP(S) status 404 messages: - messageType: ERROR messageNumber: MFS0103 messageContent: The endpoint you were looking for '/zosmf/restfiles/ds' could not be located

The endpoint does not include my basePath

Note that I can list data sets using the CLI to interact with z/OSMF via APIML in my integrated terminal.

Zowe Extension version 0.8.1
Zowe CLI version 2.0.0-next.201811131824

Incorrect path for profiles in submit JCL function

submitJCL function uses old location of profiles ".brightside" instead of ".zowe".

extension.ts:115
profileRootDirectory: path.join(os.homedir(), ".brightside", "profiles"),

Indication in dataset view that pattern didn't match any files

When I first started using the plugin, I had some difficulty understanding that I didn't have a pattern set for my dataset filters. This caused me some pain as I was able to see my zowe profiles but couldn't figure out why there were no datasets listed.

Perhaps there should be some indication that the pattern specified doesn't match anything on the mainframe. At the very least, there should be a more clear indication that you need to specify a pattern when it is missing.

When adding a new profile for USS, Data sets are referenced instead

Need contributing and developer docs

Right now there are no contributing or developer documentation present in the repo.

A docs folder should be created with a README and CONTRIBUTING guide.

The developer documentation present in the root README should be placed in the README of the docs folder.

System tests / unit tests need sustainability updates

The System and Unit tests need to be evaluated and re-written to be more sustainable.

This became apparent while developing #1. This change was a simple removal of code which turned into a nightmare for testing. This simple change caused cascading unit test failures to the point where we aren't really sure why. Most of this could be solved by making test cases much smaller than they currently are right now.

System tests require matching profile to be created in .zowe folder

The system tests are supposed to be isolated from any .zowe profile configuration. This is only partially true, as some tests require the profile name you specified in resources/testProfileTata.ts to exist in a .zowe profile.

This should not be the case, if the test needs stuff created in the .zowe profile, it should create profiles in an isolated place and have the system tests use those.

Create a validation build for the VSCode extension

Need a step that rebuilds and validates the extension for every new version of Zowe CLI

Extension not compatible with plugins that override CredentialManager

When plugin which overrides CredentialManager is installed, profiles cannot be retrieved. Used API gets securely stored fields from profiles as plain text.

Note form @AHumanFromCA on possible fix:
You will need to initialize the PluginManagementFacility to load the plugins and then you will need to pass some of the configuration variables into the OverridesLoader. There isn't a clean way to do this via the API.
The only advice I can give is that the VS code extension might just have to call Imperative.init and then everything might work.

Saving data sets and files begins to silently fail

This seems to happen to various users. We know a workaround for now that seems to resolve the problem, but don't know the root cause.

If you uninstall the extension, then go to your home directory (usually c:/users/youruserid on windows, ~ on linux/mac) /.vscode/extensions/ and delete the folders starting with "zowe". If you then reinstall the extension, the saving issue should be fixed.

URL for Zower CLI on Zowe Extension page causes a 404

I was configuring the Zowe Extension in references a URL that cannot be found.

https://zowe.github.io/docs-site/user-guide/cli-installcli.html#creating-a-zowe-cli-profile . should refer to
https://zowe.github.io/docs-site/latest/user-guide/cli-installcli.html#creating-a-zowe-cli-profile

Ideally, it should point to a versioned portion of the documentation in this cases 2.0.0

Missing USS functionality

The USS extension requires menu options for Create, Delete and Rename

"Expect Error: Required object must be defined" error on Save file

Some users have noticed a failure during Save operations in USS and Datasets. The issue is in some cases intermittent and has been reported on Windows platform only so far. Need to add more information to this issue when it becomes available.

The "Expect Error: Required object must be defined" error relates to a parameter of the save function being undefined.

Update Zowe VSCode extension

As Michelle, I want the Zowe VSCode Extension to work properly with profiles stored in plain text so that I can continue to make use of it to improve my interaction with z/OS datasets.

Update Zowe VSCode extension to work with profile credentials now stored in plain text under .zowe. Update documentation. No requirement to also work with securely stored profiles (eg 1.x).

Enhance error message to say that version is incompatible, please upgrade to the latest version. See comment below.

Depends on zowe/zowe-cli#7
'Replace Keytar - Store creds in plain text' in Zowe CLI repo

• Bump versions of zowe and imperative
  Status: Completed
  Assigned: @AHumanFromCA

• Remove calls to CredentialManager and keytar
  Status: Completed
  Assigned: @AHumanFromCA

• Initialize logger to prevent possible problems
  Status: Completed
  Assigned: @lyzla01

• Modify CliProfileManager calls to account for plaintext credentials
  Status: It just worked without any changes :)
  Assigned:

• Run system tests
  Status: Completed
  Assigned: @AHumanFromCA

• Update documentation
  Status:
  Assigned: @JamesBauman

*Accept feature with PM when complete (This & zowe/zowe-cli#16 both in this Sprint)
8 point story

USS file names should not end with the profile name

When loading a file in USS it gets open as a file with the name such as
/Users/user/resources/temp/profile/u/hlq/projects/COBOL/SAMPLE.cbl[profile]

This is a problem for the editor recognizing the filetype, e.g. it being a COBOL file as it does not end with a proper file extension. The file name needs to end with .cbl and nothing else.

Extension code needs more verbose documentation

Most of the extension code is lacking sufficient documentation to bring someone new to the project up to speed. We need to take a look at the code and structures used and add some more verbose code comments to help document some of the decisions made.

Need update for rolling logging

log4js config will need to be updated to enable rolling logs.

Complete Documentation and publish to VSCode extension marketplace

z/OS Jobs part of the extension is missing Zowe: "Add profile" action

Currently z/OS jobs extension is working only with the default profile. Changing profile requires setting new default profile and restarting VS Code.

Data sets and USS part of the extension allow to add another profile. It would be nice to have same functionality when working with Jobs.

I have also noticed that icons for "Zowe: Add profile" action are inconsistent. For "Data Sets" it's plus sign (+) and in case of "Unix System Services (USS)" it is ellipsis (…) for more actions.

Bundle VSCode extension with webpack

Microsoft recommends bundling VSCode extensions before publishing

https://code.visualstudio.com/api/working-with-extensions/bundling-extension

Need CI/CD

If this is to be a production app, there should be a CI/CD pipeline associated with it.

Perhaps @zFernand0 we can just build a from scratch ci/cd pipeline and use all of the knowledge we have gained in the course of the Zowe project to do it proper from the start. I don't want to keep hacking and slashing the same base CI/CD that we've been using due to flaws in the design.

Unit tests appears broken

Since adding the additional debug logs some of the unit tests are failing. Mock the appropriate missing function

USS files are downloaded without taking into account the file encoding tag extended attribute in zFS

I have a file that is encoded and tagged as ISO8859-1 (ASCII), eg notice the t ISO8859-1 and T=on:

/u/cicprov/mnt/CICPY000/bundles/cics-nodejs-invoke_1.0.0/META-INF:>ls -lAT
total 16
t ISO8859-1   T=on  -rw-r--r--   1 COCKERM  TSOUSER      338 Apr 25 11:24 cics.xml

/u/cicprov/mnt/CICPY000/bundles/cics-nodejs-invoke_1.0.0/META-INF:>cat cics.xml
<manifest xmlns="http://www.ibm.com/xmlns/prod/cics/bundle" bundleVersion="1" bundleRelease="0" id="cics-nodejs-invoke" bundleMajorVer="1" bundleMinorVer="0" bundleMicroVer="0"><define name="cics-nodejs-invoke" type="http://www.ibm.com/xmlns/prod/cics/bundle/NODEJSAPP" path="nodejsapps/cics-nodejs-invoke.nodejsapp"></define></manifest>

When I use the Zowe extension for Visual Studio Code to edit this file it is not shown correctly:
.

Unit tests do not pass on master

The following tests fail on master:

 ● Extension Unit Tests › Testing that saveFile is executed successfully

    expect(received).toBe(expected) // Object.is equality

    Expected value to be:
      3
    Received:
      0

      703 |         expect(dataSetList.mock.calls[0][0]).toEqual(session);
      704 |         expect(dataSetList.mock.calls[0][1]).toBe("testFile");
    > 705 |         expect(pathToDataSet.mock.calls.length).toBe(3);
      706 |         expect(pathToDataSet.mock.calls[0][0]).toEqual(session);
      707 |         expect(pathToDataSet.mock.calls[0][1]).toBe(testDoc.fileName);
      708 |         expect(pathToDataSet.mock.calls[0][2]).toBe("testFile");

      at Object.<anonymous> (__tests__/extension.test.ts:705:49)
      at fulfilled (__tests__/extension.test.ts:28:17)

  ● Extension Unit Tests › Testing that safeSave is executed successfully

    expect(received).toEqual(expected)

    Expected value to equal:
      [Error]
    Received:
      ""

    Difference:

      Comparing two different types of values. Expected object but received string.

      894 |
      895 |         expect(showErrorMessage.mock.calls.length).toBe(1);
    > 896 |         expect(showErrorMessage.mock.calls[0][0]).toEqual(Error(""));
      897 |
      898 |         openTextDocument.mockResolvedValueOnce("test");
      899 |         openTextDocument.mockResolvedValueOnce("test");

      at Object.<anonymous> (__tests__/extension.test.ts:896:51)
      at fulfilled (__tests__/extension.test.ts:28:17)

Include Jobs, USS and Datasets in same VSCode view container

The final item in the merging of USS, datasets and jobs involves putting the views in the same container. Thanks again to Andy @crshnburn for providing the relevant code snippet

"zoweZosJobs": [
        {
          "id": "zowe.jobs",
          "name": "Jobs"
        },
        {
          "id": "zowe.spool",
          "name": "Spool Files"
        },
        {
          "id": "zowe.explorer",
          "name": "Data Sets"
        },
        {
          "id": "zowe.uss.explorer",
          "name": "Unix System Services (USS)"
        }
      ]

which provides us with a result like this... Thumbs up to go for it..

Spool files to be part of Jobs tree

Would it be better if we have the spool file elements for a job as twisties off the jobname in the jobs view?. Could then remove the spool files view completely

Jobs tree profile refresh not working

In 0.14.0, The refresh button on the profile in the jobs tree does not seem to refresh the list after a job is deleted. The refresh button on the Jobs tree itself does the trick.