Issue with docs.zowe.org/stable/troubleshoot/launcher/launcher-error-codes/

[colinpaicemq]

Description

ZWEL0001I component zss started

Please clarify if this means the component has done step 1 of starting, or it has gone through all the start up steps and is ready for work.

ZWEL0007I components started

Please clarify if all the components have been kicked off ... or have all completed startup and are ready for work.
It feels like all components have been kicked off ... .but may not be ready for work, because I am getting

curl: (7) Failed to connect to 10.1.1.2 port 7554 after 2 ms: Couldn't connect to server

Is there a message saying all components have started, and zowe is ready for work? This would be useful so automation can be notified, ad so the display showing active subsystem can be updated to show zowe has started.

Pages to Update

Screenshots

Expected behavior

Additional context

[Martin-Zeithaml]

ZWEL0001I refers to a specific component was "kicked-off".
ZWEL0007I refers to all components (specified in configuration) were "kicked-off".

It does not mean, the components are operational, it is system/other components dependent. For checking if Zowe is operational, I would recommend this article.

[colinpaicemq]

I do not get the ZWEAM000I message on syslog or in job.JESYSMSG

I get

+ZWEL0021I Zowe Launcher starting                                         
+ZWEL0018I Zowe instance prepared successfully                            
+ZWEL0006I starting components                                            
+ZWEL0001I component gateway started                                      
+ZWEL0001I component zaas started                                         
+ZWEL0001I component api-catalog started                                  
+ZWEL0001I component discovery started                                    
+ZWEL0001I component app-server started                                   
+ZWEL0001I component zss started                                          
+ZWES1013I ZSS Server has started. Version '3.1.0+20250108' 64-bit        
+      "ZWEL0021I",                                                       
+      "ZWEL0018I",                                                       
+      "ZWEL0006I",                                                       
+      "ZWES1601I",                                                       
+      "ZWEL0008I",                                                       
+      "ZWEL0022I",                                                       
+      "ZWEL0001I",                                                       
+      "ZWEL0002I",     
+      "ZWEAM000I",                                                     
+      "ZWED0031I",                                                     
+      "ZWES1013I"              

In the sysprint I get
2025-05-05 12:07:00.282 ZWEAAC1:main:50332337
[35mCOLIN [0;39m [36mINFO [0;39m
((o.z.a.p.s.ServiceStartupEventHandler)) ZWEAM000I API
Catalog Service started in 98.596 seconds

But that does not come out in job log, so automation cannot pick it up.

It would also be better if the message description for

ZWEL0001I component app-server started
There will be a matching message ZWEAM000I when the component has completely started successfully.
( and make it a link)

The lack of messages on the job log looks a bit like a bug

[JoeNemo]

The best message to look for currently is "ZWES1601I"

https://github.com/zowe/zowe-install-packaging/blob/v3.x/staging/example-zowe.yaml#L336-L337

This is not as clear or well-documented as it should be.

[colinpaicemq]

Does ZWES1601I apply to all components? Because the message text for that message is Server is ready to accept JWT with(or without) fallback to legacy tokens