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

Verify jcl input #3633

Open
1000TurquoisePogs opened this issue Oct 25, 2023 · 0 comments
Open

Verify jcl input #3633

1000TurquoisePogs opened this issue Oct 25, 2023 · 0 comments

Comments

@1000TurquoisePogs
Copy link
Member

1000TurquoisePogs commented Oct 25, 2023

The JCL in SAMPLIB can be run without intervention of zwe.
Some find this great, but currently zwe is the tool that can verify if the input to the JCL is even valid.

Further, #3634 wishes to move all JCL logic out of zwe, which previously would do validation before job submission. Without further action, we'd move from users not being able to use all our JCL, to users having no validation. We must have both JCL and validation.

I suggest using "configmgr-rexx", which is a tool currently in Zowe that can be used to read zowe.yaml from within rexx, and invoke schema validation upon it.

With configmgr-rexx, we could:

  • Reduce the amount of input to the JCL needed. Parameters can come directly from zowe.yaml
  • Verify the input before executing any system alterations

We don't NEED to get the parameters from zowe.yaml, if someone finds that bad, but if we don't then we have the problem of users typing information in twice, so I think its preferred.

The main goal though is to ensure that the JCL do not continue before verifying user input is okay.

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

1 participant