Error in JOB logs- A FORK OR SPAWN ERROR WAS ENCOUNTERED

[AdarshdeepCheema]

We are seeing below errors when starting the services using 2.4 ZOWE

1. in JES2:JESMSGLG job output file-> 15.45.05 STC03862 BPXP005I A FORK OR SPAWN ERROR WAS ENCOUNTERED. RETURN CODE 00000070 REASON CODE 0B150020 =>This error only occurs when useConfigmgr: true
2. in SYS00001 job output file -> JSON: write error, rc -1, return code 0, reason code 00000000

NOTE: these issues are not happening in 2.3 ZOWE.

To Reproduce Steps to reproduce the behavior: Install 2.4 zowe, and start the services.

Expected behavior No such errors in the logs

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

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context Add any other context about the problem here.

[1000TurquoisePogs]

when running 2.4 i dont see "A FORK OR SPAWN ERROR WAS ENCOUNTERED" but i do see JSON: write error. I think its two separate issues so I am splitting them.

[1000TurquoisePogs]

I also saw " JSON: write error" regardless of zowe.useConfigmgr=true/false, so its not that.

[1000TurquoisePogs]

i increased debugging and saw:

write buffer internal: text at 3D298530, len 1
00000000 C0 |{|
JSON: write error, rc -1, return code 0, reason code 00000000

"JSON: write error" can be ignored. Its some weird code about empty buffer writing But also only shows up with debug=true on launcher But launcher is debug=false starting in 2.5

[NayerNajafi]

I have the same issue with my Zowe 2.4. Actually, there are two BPXP005I messages in system log: BPXP005I A FORK OR SPAWN ERROR WAS ENCOUNTERED. RETURN CODE 00000070 REASON CODE 0B150020
BPXP005I A FORK OR SPAWN ERROR WAS ENCOUNTERED. RETURN CODE 00000070 REASON CODE 0BFC0000

[AdarshdeepCheema]

 15.41.58 STC03862 ---- THURSDAY,  27 OCT 2022 ----
 15.41.58 STC03862  IEF695I START ZWE2LST  WITH JOBNAME ZWE2SV   IS ASSIGNED TO USER ZWESVUSR, GROUP ZWEADMIN
 15.41.58 STC03862  $HASP373 ZWE2SV   STARTED
 15.41.58 STC03862  IEF403I ZWE2SV - STARTED - TIME=15.41.58
 15.45.05 STC03862  BPXP005I A FORK OR SPAWN ERROR WAS ENCOUNTERED.  RETURN CODE 00000070 REASON CODE 0B150020
 15.45.05 STC03862  BPXP005I A FORK OR SPAWN ERROR WAS ENCOUNTERED.  RETURN CODE 00000070 REASON CODE 0B150020
 15.45.05 STC03862  BPXP005I A FORK OR SPAWN ERROR WAS ENCOUNTERED.  RETURN CODE 00000070 REASON CODE 0BFC0000
 13.36.41 STC03862 ---- WEDNESDAY, 02 NOV 2022 ----
 13.36.41 STC03862  -                                      ----TIMINGS (MINUTES)-----                          -----PAGING COUNTS----
 13.36.41 STC03862  -STEPNAME PROCSTEP    RC   EXCP   CONN       TCB       SRB  CLOCK          SERV  WORKLOAD  PAGE  SWAP   VIO SWAPS
 13.36.41 STC03862  -         ZWELNCH     00   320K     44  3.427849  0.361983 8514.7      17661361  STC      15905     0     0     0
 13.36.41 STC03862  IEF404I ZWE2SV - ENDED - TIME=13.36.41
 13.36.41 STC03862  -ZWE2SV   ENDED.  NAME-                     TOTAL TCB CPU TIME= 3.427849 TOTAL ELAPSED TIME=8514.7 SUBSYS=STC
 13.36.41 STC03862  $HASP395 ZWE2SV   ENDED - RC=0000
0------ JES2 JOB STATISTICS ------
-  27 OCT 2022 JOB EXECUTION DATE
-            2 CARDS READ
-        9,864 SYSOUT PRINT RECORDS
-            0 SYSOUT PUNCH RECORDS
-          741 SYSOUT SPOOL KBYTES
-     8,514.71 MINUTES EXECUTION TIME

[1000TurquoisePogs]

You probably have ZWELNCH in a non-key 8 ppt entry. There's no reason to do that, so if you fix that it should make the error disappear.

[NayerNajafi]

Actually, I do not have ZWELNCH in the PPT list. According to Zowe doc, ZWESAUX and ZWESIS01 need to be added to PPT.

[bobbydixon]

I'm also working on a case where the client has upgraded to Zowe V2.16 and sees the following messages when trying to start ZWESLSTC:

BPXP005I A FORK OR SPAWN ERROR WAS ENCOUNTERED. RETURN CODE 00000070 REASON CODE 0B150020 BPXP005I A FORK OR SPAWN ERROR WAS ENCOUNTERED. RETURN CODE 00000070 REASON CODE 0BFC0000

It looks like the REASON CODE 0B150020 means JRForkExitRcParentBadEnv: Forking is not supported under the current parent environment.

We have confirmed they only have PPT entries in their SCHEDxx PARMLIB member for ZWESIS01 and ZWESAUX.

Any help would be appreciated...