ZOWE 2.18 delayed start by 60 min

[dangherciu]

Hello,
On z/OS we have ZOWE v. 2.18.2+20250519 .
task start shows the correct time:
18.24.24 STC24530 IEF403I ZWESLSTC - STARTED - TIME=18.24.24

ZOWE task continue loading procedure and shows again:

2025-11-26 17:24:24.958 ZWELNCH:16910233 ZWESVUSR INFO ZWEL0021I Zowe Launcher starting

exactly one hour before in time, at this point the started task blocks and remains idle for 60 min. Passed the 60 min it will resume the start procedure.
We tried to force timezone with STDENV but no luck.
Any hint?

[balhar-jakub]

Hi, there is a known issue about the timezones settings across all of the Zowe components.

@hrishikesh-nalawade was looking at it on the API Mediation Layer side and so he may know more.

[Martin-Zeithaml]

The problem of displaying UTC vs local time is in the launcher from the beginning and I am not aware of any issue until today. The only "delay" feature in launcher is zowe.launcher.restartIntervals, but this is applied when the component failed to start.

Is this customized in your configuration?

zowe:
  launcher:
    restartIntervals:
      - 1
      - 2
      # ...

[dangherciu]

Hi Martin, in fact Intervals should apply when a component is failing but we only have a delayed start , after the 60 min everything starts as expected. I enabled debug mode to collect further information. Thank you

[dangherciu]

I activate the debug option, after initial start messages it remains as follow:
SYS00001 ZWESLSTC:
validate object pname=host
validateJSON top, value=0x500865E5AC, spec=0x50086D0364 value->type=1, spec->mask=0x10, ref=0x0 pthsz=2
path: /zOSMF/host
validate JSON value->type=1 specTypeMask=0x10
typeCode=4 shifted=0x10 mask=0x10
summing validity all=VC, any=VC, one=VC, not=VC simple=VC -> combined=VC
validate object pname=port
validateJSON top, value=0x500865E5F4, spec=0x50086D04E4 value->type=6, spec->mask=0x7f, ref=0x50086AAD0C pthsz=2
path: /zOSMF/port
resolveRef ref=£/$defs/port
validate JSON value->type=6 specTypeMask=0x40
typeCode=6 shifted=0x40 mask=0x40
summing validity all=VC, any=VC, one=VC, not=VC simple=VC -> combined=VC
validate object pname=applId
validateJSON top, value=0x500865E61C, spec=0x50086D07EC value->type=1, spec->mask=0x10, ref=0x0 pthsz=2
path: /zOSMF/applId
validate JSON value->type=1 specTypeMask=0x10
typeCode=4 shifted=0x10 mask=0x10
summing validity all=VC, any=VC, one=VC, not=VC simple=VC -> combined=VC
summing validity all=VC, any=VC, one=VC, not=VC simple=VC -> combined=VC
umming validity all=VC, any=VC, one=VC, not=VC simple=VC -> combined=VC
******************************* BOTTOM OF DATA *******************************************************************************

in sysprint:
applyEnviron setting ZWE_configs_security_certificate_keystore_genericClientKeyStore_
applyEnviron setting ZWE_configs_security_profilePrefix_super=IZP.SUPER
applyEnviron setting ZWE_configs_security_profilePrefix_admin=IZP.ADMIN
applyEnviron setting ZWE_configs_security_surrogateUser_super=IZPSRGSP
applyEnviron setting ZWE_configs_security_surrogateUser_admin=IZPSRGAD
applyEnviron setting ZWE_configs_security_surrogateGroup=IZPSRGRP
applyEnviron setting ZWE_configs_server_validation_validateAtStart=true
applyEnviron setting ZWE_configs_server_validation_shutDownOnFailure=false
******************************** BOTTOM OF DATA *************************************

with OMVS logs not created. so for the next 60 min it remains in this state, after it resume starting and finally all services are up.

[dangherciu]

all rc="0" with 0 ERRORS FOUND in task log

[Martin-Zeithaml]

Is this happening without UMS? Is it possible to run Zowe Server only?
I just started fresh instance for Zowe 2.18.2, there is also time difference, but the Zowe starts normally:

Same message with time difference

08.17.47 STC32796  +ZWEL0021I Zowe Launcher starting 

2025-11-27 13:17:47.604 <ZWELNCH:33884694> ZWESVUSR INFO ZWEL0021I Zowe Launcher starting 

[dangherciu]

it is happening with UMS, now we're trying your suggestion of removing it and start a standalone zowe server. What bothers me id no message error or delay warning is written even with debug on. Further more, on USS side the new log appServer-2025-11-27-*.log is created only after the 60 minutes, so we're blind.

[dangherciu]

Hi Martin, followed your suggestion and I confirm that 60 min delay disappeared. It is still slow (around 30 min to have all up) but at least it write the log as it suppose to.
So, the problem might be during UMS invoking?
Thank you

[Martin-Zeithaml]

30 minutes to be up is very slow, unless the system's resources are limited.

Is this set in your configuration? If not, I would strongly recommend this:

zowe:
  useConfigmgr: true

[dangherciu]

Hi Martin, yes it is enabled:
useConfigmgr: true
configmgr:
validation: "COMPONENT-COMPAT"

[Martin-Zeithaml]

Are you using app-server? Is there a message ZWED0211I in your log?

[dangherciu]

hello Martin, sorry for late reply ... , yes for app-server, and the message is:
ZWED:131520 ZWESVUSR INFO (_zsf.cluster,clusterManager.js:59) ZWED0211I - The number of processors is: 6

[Martin-Zeithaml]

Hi, I was off for 2 days.
6 CPUs seems like a sufficient power, I don't see a problem here.

We can try one more thing, could you share your Zowe (without USM) configuration?

Keep in mind, this is public site, anonymize any sensitive data, for java and node I need just the version, replace domains with example.com etc. and zowe.setup is not needed at all. I will try your configuration on our test system to see, if there is any delay.

Best via attachment to keep indentation.