Why is the Tomcat STC unexpectedly ending with an RC=3000.
Also, see the message: CEE5230S The signal SIGXCPU was received.
It appears the RC=3000 is tied to the CEE5230S message, which shows that Tomcat timed out after reaching the CPU limit.
When a SIGXCPU signal is received, the return code is set to 3000 per IBM page: https://www.ibm.com/docs/en/zos/2.4.0?topic=messages-cee5230s
To resolve the problem in the Tomcat server procedure, add "TIME=NOLIMIT" to the "//TOMCAT EXEC" statement and restart the Tomcat server.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
...
//TOMCAT EXEC PGM=JVMLDM&VERSION,REGION=0M,MEMLIMIT=3G,TIME=NOLIMIT,
// PARM='&LEPARM/&LOGLVL &JAVACLS &SRVXML start'
....
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This parameter will remove all CPU time limits and prevent the SIGXCPU timeout signal.