ZWEGENER could not load the configuration

[mainframe-JMF]

Hello,

I was trying to load the ZOWE configuration using JCL but it is ending up with the error message.

READY
ISPSTART CMD(%ZWEGEN00 generate verbose )
ISPF system data set allocation error - press Enter to continue.
Log file allocation error - ISPF will operate without a log data set.
Data set 'TECH.XXXXX.SPFLOG1.LIST' in use by another user, try later.
execio * diskr myschema (finis stem !contentToRead.
execio * diskr myschema (finis stem !contentToRead.
execio * diskr myconfig (finis stem !contentToRead.
ConfigMgr is about to add a configuration.
ConfigMgr added a configuration.
ConfigMgr is about to set trace level to 1.
ConfigMgr set trace level to 1.
ConfigMgr is about to load your schemas.
ConfigMgr loaded your schemas.
ConfigMgr is about to set the member name for parameter library.
ConfigMgr set the parameter library member name.
ConfigMgr is about to process your configuration.
ConfigMgr has processed your configuration.
ConfigMgr is about to load your configuration.
ConfigMgr could not load your configuration.
status = 2
ISPD117
The initially invoked CLIST ended with a return code = 8

======

CEE3608I The following messages pertain to the invocation command run-time optio
CEE3606I The string ' CELQPTBL' was too long and was ignored.JSON: write error, rc -1, return code 0, reason code 00000000
JSON: write error, rc -1, return code 0, reason code 00000000
JSON: write error, rc -1, return code 0, reason code 00000000

==============

overload mgr=0x1C4D3668 config=01C4D44F0 pathElement=0x5008695214
before read YAML mgr=0x1C4D3668 file=/u/xxxxx/zowe.yaml
yaml doc at 0x1B7DAC68, allowMissing=0 wasMissing=0
overlay = 0x50086956C4 tail=0x50086952A4 nullAllowed=0
before read YAML mgr=0x1C4D3668 file=/zowe/files/defaults.yaml
yaml doc at 0x1B7DACD8, allowMissing=0 wasMissing=0
Overload status = 0
returning evalblock at 0x1B537E30
00000000 00000000 00000022 00000001 00000000 F2000000 00000000 00000000 000000

Not sure what exactly is missing here due to which the configuration loading is failing. Is there a place to check where the configuration load trace can be found and see the place where it is failing ?

[Martin-Zeithaml]

Hello,

could you share the zowe.yaml file?

It might be a problem with templating, but I am not able to reproduce it on our system.

Regards, Martin

[mainframe-JMF]

Hello,

I am attaching the ZOWE.YAML file.
TEST.YAML.txt

[Martin-Zeithaml]

Hi, there are several problems:

• One of the problems is, that the status=2 is not helpful and there is no additional output to guide you to fix the problem
  • This is problem of our internal parser
• There are problems in the configuration itself:
  • Line 33: zowe:/zowe should be zowe:
  • Line 429: spaces before the last "r": certificateAuthorities: /zowe/keystore/local_ca/local_ca.ce r
  • Line 100+, if the certificate already exists, you can comment or remove entire zowe.setup.certificate section. Otherwise there are problems with incomplete properties and indentation, this is probably intended setup:

zowe:
  setup:
    certificate:
      # Type of certificate storage. Valid values are: PKCS12, JCERACFKS. APIML additionally supports: JCEKS, JCECCAKS, JCECCARACFKS, or JCEHYBRIDRACFKS
      type: PKCS12
      pkcs12:
        # **COMMONLY_CUSTOMIZED**
        # Keystore directory
        directory: /zowe/keystore
        # # Lock the keystore directory to only accessible by Zowe runtime user and group.
        lock: true
        # **COMMONLY_CUSTOMIZED**
        # # Certificate alias name. Optional, default value is localhost.
        # # Note: please use all lower cases as alias.
        # name: localhost
        # **COMMONLY_CUSTOMIZED**
        # # Keystore password. Optional, default value is password.
        # password: password
        # **COMMONLY_CUSTOMIZED**
        # # Alias name of self-signed certificate authority. Optional, default value is local_ca.
        # # Note: please use all lower cases as alias.
        # caAlias: local_ca
        # **COMMONLY_CUSTOMIZED**
        # # Password of keystore stored self-signed certificate authority. Optional, default value is local_ca_password.
        # caPassword: local_ca_password
      # # Distinguished name for Zowe generated certificates. All optional.
      dname:
        caCommonName: ""
        commonName: ""
        orgUnit: ""
        org: ""
        locality: ""
        state: ""
        country: ""
      # # Validity days for Zowe generated certificates
      validity: 3650
      # # Domain names and IPs should be added into certificate SAN
      # # If this field is not defined,  zwe init  command will use
      # #  zowe.externalDomains .
      san:
      #   # sample domain name
        - xxxx.xxxx.xxxx.xxxx
      #   # sample IP address
        - 10.x.x.x.x

Recommendation

Run zwe config validate before

I can recommend the shell command zwe config validate -c ./TEST.YAML.txt.yaml. This command will check the config and eventually prints the schema validation errors.

Directories

It is recommended to set the zowe.runtimeDirectory as read only. If you follow this recommendation, you need to set these directories "outside" the `/zowe':

logDirectory: /zoweout/logs
workspaceDirectory: /zoweout/workspace
extensionDirectory: /zoweout/extensions

[mainframe-JMF]

Hello,

Thank you so much it helped me. Now I am getting error in using pkcs12

ZWEL0318E - Couldn't parse file '/u/xxxx/zowe.yaml': while parsing a block ma
pping at line 106, column 9, did not find expected key at line 108, column 11.
Error: Could not load config for FILE(/u/xxxx/zowe.yaml):FILE(/zowe/files/def
aults.yaml), status=7

zowe..yaml file
000102 type: PKCS12
000103 pkcs12:
000104 # COMMONLY_CUSTOMIZED
000105 # Keystore directory
000106 directory: /zowe/keystore
000107 # # Lock the keystore directory to only accessible by Zowe runti
000108 lock: true
000109 # COMMONLY_CUSTOMIZED
000110 # # Certificate alias name. Optional, default value is localhost
000111 # # Note: please use all lower cases as alias.
000112 # name: localhost
000113 # COMMONLY_CUSTOMIZED
000114 # # Keystore password. Optional, default value is password.
000115 # password: password
000116 # COMMONLY_CUSTOMIZED
000117 # # Alias name of self-signed certificate authority. Optional, d

Prior running this , Should i be building the keystore ?

[Martin-Zeithaml]

Hi,
the error is probably caused by wrong indentation, YAML is sensitive about this:
I am guessing you have this in your config:

        directory: /zowe/keystore
        # # Lock the keystore directory to only accessible by Zowe runtime user and group.
          lock: true

The correct version is the lock in the same column as directory:

        directory: /zowe/keystore
        # # Lock the keystore directory to only accessible by Zowe runtime user and group.
        lock: true

Related to keystore, if the keystore does not exist, you will need one. Otherwise if it is already there, you can use existing one.

[mainframe-JMF]

Hello,

Instead of PKCS12 i tried using Scenario 3 and got this below message. Is there anything need to be looked in ?

# zwe config validate -c /u/xxxxxx/zowe.yaml                                   
Error: Validation of FILE(/u/xxxxxx/zowe.yaml):FILE(/zowe/files/defaults.yaml) 
against schema /zowe/schemas/zowe-yaml-schema.json:/zowe/schemas/server-common.json found invalid JSON Schema data                                              
Validity Exceptions(s) with object at                                           
  Validity Exceptions(s) with object at /zowe                                   
    Validity Exceptions(s) with object at /zowe/setup                           
      Validity Exceptions(s) with object at /zowe/setup/dataset                 
        unspecified additional property not allowed: 'certificate' at '/zowe/setup/dataset/certificate' 

[Martin-Zeithaml]

Hi,

the YAML syntax is case and indentation sensitive. This error message is reporting, that the zowe.setup.dataset.certificate is nested under zowe.setup.dataset, where it is not allowed. You need to move the certificate section to be under zowe.setup.

What editor are use using for modifying zowe.yaml file? I can recommend VSCode with Zowe Explorer Extension, where you can edit the USS files and there is a feature for (un)commenting multiple lines: if you are editing example-zowe.yaml file and use this feature (Ctrl + /), the properties are correctly shifted and you will more likely avoid the schema validation errors.

[mainframe-JMF]

Hello Is it possible to use ZOWE Explorer even without running ZOWE on mainframe? Editing is parallel?

…

On Wed, 19 Mar 2025, 14:07 Martin Zeithaml, ***@***.***> wrote: Hi, the YAML syntax is case and indentation sensitive. This error message is reporting, that the zowe.setup.dataset.certificate is nested under zowe.setup.dataset, where it is not allowed. You need to move the certificate section to be under zowe.setup. What editor are use using for modifying zowe.yaml file? I can recommend VSCode with Zowe Explorer Extension, where you can edit the USS files and there is a feature for (un)commenting multiple lines: if you are editing example-zowe.yaml file and use this feature (Ctrl + /), the properties are correctly shifted and you will more likely avoid the schema validation errors. — Reply to this email directly, view it on GitHub <#4240 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BPU4JXY7BTBC2AFVLBKNJ332VE6W3AVCNFSM6AAAAABZDJDFQSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENJUHE2TMNA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Martin-Zeithaml]

Yes, it is. All you need is to install Zowe CLI (local machine), Zowe Explorer (local machine too) and have access to z/OSMF:

• Zowe CLI
• Zowe Explorer

The Zowe server is not required for using Zowe Explorer in VSCode. Although all mentioned components are using "Zowe" in the name, they are independent.

When you are editing a USS file (or dataset member) in VSCode, it is updated on mainframe. From the user point of view, it looks like you are editing any other file.