-
Notifications
You must be signed in to change notification settings - Fork 51
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 init mvs fails with complaint about zowe.yaml #4090
Comments
Hi Gene, do you have correctly set your variable for node.js? Btw. default values are more for an inspiration how the value should look like, you still have to fill in the values correctly so the installation will succeed. Also zowe.setup.dataset.prefix doesn't have a correct description (more about it in #4083) |
The variable for node is set here: The value is /usr/lpp/IBM/cnj/v18r0/IBM/node-latest-os390-s390x/bin The node program is operational.
Regarding prefixes: In "PSWI - Deployment - Deployment Checklist - Configure Deployment" we are required to specify dataset names. It simply states that they These datasets are created behind-the-scenes by generated JCL. After encountering permission errors with the default values, I modified the default pattern = ZWE.PSWI.AZWE003 to myUserId.ZWE.V3PSWI. Much later in "PSWI - Deployment - Workflows - Configuration of Zowe 3.0 - Define the main variables - Zowe setup MVS prefix" we are asked for another prefix with the following description. IBMUSER.ZWEV2 is a valid dataset prefix. I took the approach that if the Zowe PSWI wants to put data in that location, it is fine with me. No information is provided about what constitutes a "correct" value. I still do not know what value I should specify for the Zowe MVS Prefix. All I know is that the zwe init mvs command (which is run from generated JCL) fails with the error identified above. What constitutes a correct value for this Zowe MVS Prefix? Is it related to the earlier data set names? If so, how would I know that? |
After being directed to confirm the nodeJS home property, I found that I specified a path down to the 'bin' directory (/usr/lpp/IBM/cnj/v18r0/IBM/node-latest-os390-s390x/bin). The node HOME directory is one level above the 'bin' directory. After removing 'bin' from the end of the path, I no longer encountered this error. This issue can be closed. However, I feel that the error that is displayed: "Zowe dataset prefix (zowe.setup.dataset.prefix) is not defined in Zowe YAML configuration file." does not help the user look for the actual cause of the problem. |
I'll close this since we have another issue tracking the same misleading message in another execution context: #3426 . |
Describe the bug
A PSWI-generated workflow job does not like the zowe.yaml file that was also generated by the PSWI workflow.
To Reproduce
Run the step "PSWI - Deployment - Workflows - Configuration of Zowe 3.0 - Run the Zowe init"
The job fails with CC=3328 and displays the following error message:
The zowe.yaml file is generated by the PSWI workflow. Identifying an error in the yaml file does not relate to any action that the user performed.
By debugging the yaml file anyway, I find a path that looks exactly like what the error says is not defined.
Having to further speculate on what the error might be actually complaining about, I find that the dataset does not exist. Is that what the error is actually about?
I do not recall any doc instructing me to create such a dataset. I manually created a dataset by that name just to confirm that I am privileged to do so.
Expected behavior
Since the yaml file and the jobs are all generated behind the scenes, either the PSWI workflow has an error, or the doc does not have sufficient instructions for the user to set PSWI properties that will succeed when the workflow job is run.
The value 'IBMUSER.ZWEV2' is the default value in the step "PSWI - Deployment - Workflows - Configuration of Zowe 3.0 - Define the main variables - Zowe setup MVS prefix". I simply accepted the default value.
By the way, if that is a value which we recommend to customers, it should probably be named 'V3'.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: