Unexpected behavior in TSO Commands

[zFernand0]

Describe the bug

This is a 3 part issue:

1. Inaccurate error message when the logonProc is invalid
2. ZE ignores the default TSO profile and always asks the user
3. User gets prompted for account number after cancelling TSO profile selection question

To Reproduce

For number #1:

1. Modify your TSO profile:

       "tso": {
           "type": "tso",
           "properties": {
               "account": "YOUR-ACCOUNT-NAME",
               "logonProcedure": "NON-EXISTENT-LOGON-PROC"
           }
       }

2. Run a TSO command like LISTUSER USERID
3. Check the Zowe TSO Command output channel

   > LISTUSER USERID
   IKJ56716I EXTRANEOUS INFORMATION WAS IGNORED: USERID
   IKJ56482I THE PROCEDURE NAME LISTUSER HAS NOT BEEN DEFINED FOR USE  
   IKJ56429A REENTER -

4. Notice that the first word of the command is used as the logonProc.
   • If you are curious, try a command like this <VALIDPROC> LISTUSER USERID when your logonProc is invalid 😋

---

For number #2:

1. Make sure you have a default TSO profile specified in your zowe.config.json
2. Also make sure to have more than one TSO profile 😋
3. Try to issue a TSO command
4. Noticed the prompt for TSO profiles

---

For number #3:

1. Follow steps for number #2
2. Hit escape to try and get out of the TSO profile selection question
3. Notice it prompts for the account number

Expected behavior

For number #1:

• Expected the IKJ56482I message to indicate that the NON-EXISTENT-LOGON-PROC is invalid, instead of the first word of the command (e.g. LISTUSER)

For number #2:

• Expected to use the default profile

For number #3:

• Expected not to asked for the account number

Desktop (please complete the following information):

• OS: Ubuntu 22.04 (Remote SSH)
• Zowe Explorer Version: 2.11.2
• (Optional) Zowe CLI Version: N/A
• (Optional) Are you using Secure Credential Store? No (unsecure profiles for testing purposes)

Additional context

This came up during the 23PI4 (day 1) Readout. The original ask was to allow users to change the logonProc whenever they interact with z/OS. For the purpose of TSO commands, Zowe Explorer already supports the logonProcedure property in the TSO profiles. However, if the desire is to change the logonProc used for interacting with other z/OSMF REST APIs (files, jobs, ...), it's possible that Zowe Explorer may not be able to change configuration on z/OS to make this happen.

[github-actions]

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.