zowe profiles create zosmf-profile allow specification of --console-name

[MikeKoester]

When creating a zosmf profile it would be nice if it also supported allowing the user to specify the z/OS extended MCS console to direct the commands to. Right now it defaults to 6 characters of the user name with CN appended. If you have the same user name for all of your zosmf profiles (which is common as most systems you use the same userid) you will get IKJ error messages if the console name you are trying to go to is already active. The zowe zos-console issue command already allows you to be able to specify console name so the logic is already there in zowe. Thank You.

[github-actions]

Thank you for raising this issue.
The community has 30 days to upvote 👍 the issue.
If it receives 10 upvotes, we will move it to our backlog. If not, we will close it.

[MikeBauerCA]

@MikeKoester In our next major release, we will have support for Zowe team configuration which is a more scalable, maintainable approach to Zowe client configuration. In essence, an administrator creates a zowe.config.json file that can be easily shared with others. This config is also more flexible than profiles today. You can add any command option you want. @dkelosky demonstrates this use case in this blog -> https://medium.com/zowe/tip-how-to-store-zowe-cli-arguments-in-team-config-b96c7d366edc

For more details on getting started with team config in general, you can check out this doc.

We also have a V2 tech preview for Zowe Explorer that you could try. It is available in our releases. You can also follow this tip to get started - https://medium.com/zowe/zowe-explorer-tips-tricks-6ade4a2c738#d32f

[MikeBauerCA]

@zFernand0 do you know if the V2 tech preview of ZE supports custom profiles as I mentioned above? If not, we should make the change to support this and also consider adding the consoleName to the profile definition to get intellisense when editing zowe.config.json.

[MikeKoester]

Hi Mike,

the change I am asking for hopefully would be easy to implement for the existing zosmf profile creation. When I create it with the CLI or through the VSC Zowe explorer extension that would be the optimum place to have it as that is straight forward. Thank you for looking at this.

[zFernand0]

@zFernand0 do you know if the V2 tech preview of ZE supports custom profiles as I mentioned above? If not, we should make the change to support this and also consider adding the consoleName to the profile definition to get intellisense when editing zowe.config.json.

Hey Mike,
The ZE doesn't support custom profiles like mentioned in Dan's blog.
It doesn't deviate from the default properties defined by the schema file.

UPDATE:
Custom properties defined in a profile could be recognized in ZE by removing the Schema requirement (#1781)

[zFernand0]

After some discussion in the Zowe Explorer standup (Nov 8th, 2022) we decided to go with the following approach:

• Update the Imperative ProfileInfo APIs to return all values in the profile
  ProfileInfo: Add support for any properties specified in zowe.config.json imperative#899
• Forward all applicable values to the corresponding SDK methods

[recaph]

is there any ETA for this issue?

[t1m0thyj]

is there any ETA for this issue?

@recaph This enhancement will be published in the next feature release of Zowe Explorer (2.16.0).