Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zwe start does not start as zowe.setup.security.stcs.zowe #3950

Open
Martin-Zeithaml opened this issue Aug 22, 2024 · 1 comment
Open

zwe start does not start as zowe.setup.security.stcs.zowe #3950

Martin-Zeithaml opened this issue Aug 22, 2024 · 1 comment

Comments

@Martin-Zeithaml
Copy link
Contributor

Martin-Zeithaml commented Aug 22, 2024

zowe.yaml

No zowe.job.* coded.

Before defaults.yaml

zwe start -c zowe.yaml
>> STARTING ZOWE

-------------------------------------------------------------------------------
>> Job ZWELSTC is started successfully.

After defaults.yaml

  • zowe.job.name and zowe.job.prefix coded in defaults.yaml
  • The jobname is always set
zwe start -c zowe.yaml
>> STARTING ZOWE

-------------------------------------------------------------------------------
> Job ZWE1SV is started successfully.

Bonus: zowe.job.name and zowe.job.prefix are validated as strings, we can use already defined #ref & $anchor jobname.

@JoeNemo
Copy link
Contributor

JoeNemo commented Aug 28, 2024

@1000TurquoisePogs would like your comments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants