search

zowe / zowe-install-packaging

Packaging repository for the Zowe install scripts and files
Eclipse Public License 2.0
27 stars 51 forks source link

Error ZWEL0157E: Zowe dataset prefix (zowe.setup.dataset.prefix) is not defined #3411

Closed tsutter-wildfire closed 3 months ago

tsutter-wildfire commented 2 years ago

Down loaded the PSWI version of zowe 2.2. During this part of the install Properties for Workflow Step 3.1. Run the zowe install. I receive a return code of 3328. Looks like reading the zowe.yaml file is is not finding a variable . I've looked at this file and I think it looks ok

INSTALL ZOWE MVS DATA SETS

1. 2.

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Logs If applicable, add server logs collected at the time of your problem.

Details

**Web Browser Details (if the bug relates to Zowe

REST API client (in case of REST API issue):

Shell Environment Details (if the bug relates to CLI):

Additional context Add any other context about the problem here.

1000TurquoisePogs commented 2 years ago

did you define zowe.setup.dataset.prefix? Here's what it looks like by default https://github.com/zowe/zowe-install-packaging/blob/v2.x/master/example-zowe.yaml#L32-L42 if you defined it but are still having the error, maybe it's a syntax error? YAML is whitespace sensitive, so checking that the YAML is syntactically correct may be the solution.

tsutter-wildfire commented 2 years ago

Yes it was in the YAML file. I even got rid of all lines in the created YAML, that were either comment, or blanks. This YAML was created by the installation process, so I would have expected it to be correct. So far I’m not impressed with Zowe

From: 1000TurquoisePogs @.> Sent: Sunday, August 21, 2022 3:18 PM To: zowe/community @.> Cc: Sutter, Tim @.>; Author @.> Subject: Re: [zowe/community] Error ZWEL0157E: Zowe dataset prefix (zowe.setup.dataset.prefix) is not defined (Issue zowe/zowe-install-packaging#3411)

CAUTION: This email originated from outside of Cincom's email system. Do not click links or open attachments unless you recognize the sender and know the content is safe. Thanks - If in doubt, contact the Helpdesk at @.**@.> or your local IT personnel.

did you define zowe.setup.dataset.prefix? Here's what it looks like by default https://github.com/zowe/zowe-install-packaging/blob/v2.x/master/example-zowe.yaml#L32-L42 if you defined it but are still having the error, maybe it's a syntax error? YAML is whitespace sensitive, so checking that the YAML is syntactically correct may be the solution.

— Reply to this email directly, view it on GitHubhttps://github.com/zowe/zowe-install-packaging/issues/3411, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASTOE4B3EXIQLBH57RRNXTTV2J6GRANCNFSM56W5HBJA. You are receiving this because you authored the thread.Message ID: @.**@.>>

rjchavez commented 2 years ago

Having the same issue here. Is there a resolution or circumvention?

tsutter-wildfire commented 2 years ago

Not that I’ve been able to find. It looks like whatever software reads the zowe.yaml file is not doing it correctly, or the install process is not creating it properly I’ve searched for answers, but google returns so much crap it’s hard to find what you are looking for . Duckduckgo doesn’t return enough stuff

From: rjchavez @.> Sent: Thursday, August 25, 2022 1:37 PM To: zowe/community @.> Cc: Sutter, Tim @.>; Author @.> Subject: Re: [zowe/community] Error ZWEL0157E: Zowe dataset prefix (zowe.setup.dataset.prefix) is not defined (Issue zowe/zowe-install-packaging#3411)

CAUTION: This email originated from outside of Cincom's email system. Do not click links or open attachments unless you recognize the sender and know the content is safe. Thanks - If in doubt, contact the Helpdesk at @.**@.> or your local IT personnel.

Having the same issue here. Is there a resolution or circumvention?

— Reply to this email directly, view it on GitHubhttps://github.com/zowe/zowe-install-packaging/issues/3411, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASTOE4GOXLHROGMF3O4STM3V26VKLANCNFSM56W5HBJA. You are receiving this because you authored the thread.Message ID: @.**@.>>

rjchavez commented 2 years ago

In looking at the index.sh file that's used to run the script, it looks like a read_yaml command is used. I don't know if YAML is a requirement for USS installation but it's not stated anywhere in the doc.

rjchavez commented 2 years ago

I was able to get this to work from the SMP/E installation of Zowe and not from the convenience build

tsutter-wildfire commented 2 years ago

What did you do to make it work? I tried both versions with the same results

From: rjchavez @.> Sent: Friday, August 26, 2022 3:11 PM To: zowe/community @.> Cc: Sutter, Tim @.>; Author @.> Subject: Re: [zowe/community] Error ZWEL0157E: Zowe dataset prefix (zowe.setup.dataset.prefix) is not defined (Issue zowe/zowe-install-packaging#3411)

CAUTION: This email originated from outside of Cincom's email system. Do not click links or open attachments unless you recognize the sender and know the content is safe. Thanks - If in doubt, contact the Helpdesk at @.**@.> or your local IT personnel.

I was able to get this to work from the SMP/E installation of Zowe and not from the convenience build

— Reply to this email directly, view it on GitHubhttps://github.com/zowe/zowe-install-packaging/issues/3411, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASTOE4EJU7MAACLRX5AFZN3V3EJDNANCNFSM56W5HBJA. You are receiving this because you authored the thread.Message ID: @.**@.>>

struga0258 commented 2 years ago

I was able to generate this issue when my user didn't have enough cpu to run node, can you please check and see if you are able to run node or have enough memory under your user?

tsutter-wildfire commented 2 years ago

Yes I can start and run node on the id that I’m using for the zowe install

From: James Struga @.> Sent: Monday, September 26, 2022 9:58 AM To: zowe/community @.> Cc: Sutter, Tim @.>; Author @.> Subject: Re: [zowe/community] Error ZWEL0157E: Zowe dataset prefix (zowe.setup.dataset.prefix) is not defined (Issue zowe/zowe-install-packaging#3411)

CAUTION: This email originated from outside of Cincom's email system. Do not click links or open attachments unless you recognize the sender and know the content is safe. Thanks - If in doubt, contact the Helpdesk at @.**@.> or your local IT personnel.

I was able to generate this issue when my user didn't have enough cpu to run node, can you please check and see if you are able to run node or have enough memory under your user?

— Reply to this email directly, view it on GitHubhttps://github.com/zowe/zowe-install-packaging/issues/3411, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASTOE4F3I6WFRYCP3POUZWTWAGTWHANCNFSM56W5HBJA. You are receiving this because you authored the thread.Message ID: @.**@.>>

Dino390 commented 2 years ago

Hi team, new in Zowe installation, got the same trouble. Node seems to run fine on my z/OS V2.5 :

node --version Product registration data: Product Name: NODE.JS FOR Z/OS PID Name: 5655-NOE Major Version: 16 Product Owner: IBM CORP Feature Name: NODE.JS v16.14.2 but when doing zwe init mvs -c /...Zowe.yalm got

Initialize Zowe custom data sets

Error ZWEL0157E: Zowe dataset prefix (zowe.setup.dataset.prefix) is not defined in Zowe YAML configuration file.

This is true with Zowe lvl UO02050 and also lvl UO02052.

Any help would be appreciated.

chrismcgavic commented 2 years ago

Including a link for the yaml: https://docs.zowe.org/stable/appendix/zowe-yaml-configuration/#configure-component-app-server

I've been working on 2.3.0 zowe for the past week and have learned that the yaml is indeed sensitive to not only white space but the order in which parms are placed. See the link above, it shows the expected order and indentation of parms. This drive me crazy and of course still having issues with 2.3.0. Just opened a case.

chrismcgavic commented 2 years ago

Also, do not do as I did and believe that the order in the sample yaml is correct, its not. I had to move DNAME: above where it is commented out. I would also encourage you to set useConfigmgr: to true. Zowe will come up quicker and it does syntax checking based on the yaml link I sent above.

lnlyssg commented 2 years ago

I was getting a similar issue (albeit without the node message):

=============================================================================== 
>> INSTALL ZOWE MVS DATA SETS                                                   

  * Output:                                                                     
    Error: error reading input file: All collection items must start at the same
 column                                                                         
Error ZWEL0157E: Zowe dataset prefix (zowe.setup.dataset.prefix) is not defined 
in Zowe YAML configuration file.

After passing my YAML through an online syntax checker I discovered the issue was actually further down the file where I had removed some # comment prefixes but not the space before/after so everything was one character out (e.g. security: on line 66 needs to be in col 5, product: in col 7, admin: in col 9 etc.), once I corrected this I was able to run zwe install OK.

1000TurquoisePogs commented 2 years ago

Yes, YAML is sensitive to whitespace and also has a notion of hierarchy so where you put for example "prefix", does matter. For example:

zowe:
  setup:
    dataset:
      prefix: 'abc'

That's zowe.setup.dataset.prefix.

zowe:
  setup:
    dataset:
    prefix: 'abc'

That's zowe.setup.prefix

zowe:
  setup:
    dataset:
components:
    app-server:
      prefix: 'abc'

That's components.app-server.prefix.

And sure, you can have a propery named "prefix" in different places all of which could be valid, but only one of those is the specific property being asked for.

Zowe server install starting with 2.3 has a new mode that I'll call "configmgr mode" which when toggled on (opt-in in 2.3, expected to be default in 2.4) it will do more validation on your yaml files and should spot issues sooner & more accurately. You can give it a try here https://docs.zowe.org/stable/user-guide/configmgr-using#using-zwe-with-configuration-manager It won't solve all problems for everyone at once, but over time we'll be improving it more to give you much better clues on if your YAML is valid for Zowe, and where the invalid part is.

lnlyssg commented 2 years ago

I did try configmgr as according to https://docs.zowe.org/stable/appendix/zwe_server_command_reference/zwe/init/zwe-init-mvs it should work for the zwe init command but I'm guessing the docs are further ahead than the code as it didn't actually help:



------------------------------------------------------------------------------- 
>> Initialize Zowe custom data sets                                             

  * Output:                                                                     
    Error: error reading input file: All collection items must start at the same
 column                                                                         
Error ZWEL0157E: Zowe dataset prefix (zowe.setup.dataset.prefix) is not defined 
in Zowe YAML configuration file.
swelton commented 2 years ago

ZOWE 2.4, z/OS 2.5, Node.js v16 and it doesn't work. this is using a copy of the delivered example and just overtyping the dummy entries:

`/zwe init --config /zwe240/usr/lpp/zowe/zowe.yaml
===============================================================================
>> CONFIGURE ZOWE

-------------------------------------------------------------------------------
>> Check if need to update runtime directory, Java and/or node.js settings in Zowe YAML configuration

  * Output:
    Error: error reading input file: All collection items must start at the same column
These configurations need to be added to your YAML configuration file:

zowe:
  runtimeDirectory: "/zwe240/usr/lpp/zowe"

>> Please manually update "/zwe240/usr/lpp/zowe/zowe.yaml" before you start Zowe.

-------------------------------------------------------------------------------
>> Initialize Zowe custom data sets

  * Output:
    Error: error reading input file: All collection items must start at the same column
Error ZWEL0157E: Zowe dataset prefix (zowe.setup.dataset.prefix) is not defined in Zowe YAML configuration file.`

This means that either the example is incorrect or there are other problems with the installer. Just for info, my YAML has the following

  setup:                                           
    # MVS data set related configurations          
    dataset:                                       
      # **COMMONLY_CUSTOMIZED**                    
      # where Zowe MVS data sets will be installed 
      prefix: ZWE240.USER                          
...
  # This value is required by ZWESLSTC to know where is Zowe runtime.
  runtimeDirectory: "/zwe240/usr/lpp/zowe"                           
...
chrismcgavic commented 2 years ago

swelton I feel your pain! I'm sure you saw the few posts before yours but you're going to have to go over your yaml with a fine toothed comb, there must be something out of place. Don't place too much faith in the order of the parms early in the yaml, there is a hierarchy that must be followed and hopefully the yaml example can be changed to reflect a more proper order.

chrismcgavic commented 2 years ago

swelton, do you have zowe: in column one ahead of setup: in column three?

lnlyssg commented 2 years ago

this is using a copy of the delivered example and just overtyping the dummy entries

Did you un-comment any sections/lines too? If you've seen my post above that was where I slipped up as I had only removed the # character and not the additional space needed to get things in the right place. I would try pasting your current yaml file into a checker like https://yamlchecker.com/ which should highlight any issues.

swelton commented 2 years ago

It seemed to be a YAMl error. Although I used the original example and just overtyped fields and where they were commented out, I just used a space over the #, it actually needed these fields to have the # deleted and moved 2 spaces to the left! That worked but there are further errors later (RACF, VSAM, etc.) but things are slowly progressing although now it cannot import zOSMF certificates. Onward and forward, thanks for the pointers.

1000TurquoisePogs commented 1 year ago

For what its worth, the reason zwe init still has this issue is that it doesnt yet have configmgr code. I'm working on it https://github.com/zowe/zowe-install-packaging/pull/3135 but as it's a delicate part of automation code, it may take a while longer. I recently found that if you're a user of microsoft visual studio code, redhat has a plugin for it just named "yaml". Its supposed to have the ability to tell you if your yaml is syntactically valid, so it might be good to type up a yaml in there before proceeding, if it's already a tool in your belt.

Corzzab commented 1 year ago

Hi I'm new to Zowe/yaml. I found a work around for this issue. If you do a zwe install -h it give you the option below to install the dataset prefix. This help for me.

zwe install --ds-prefix ..***

muzikovam commented 7 months ago

The original issue was caused by the workflow incorrectly creating the yaml file. So the fixes in #3761 are only for those of you who used workflow ZWECONF.xml for the configuration.

jp669844 commented 3 months ago

No further comments, closing. If you still have an issue with the z/OSMF PSWI/Workflow method, please open a new issue.