B4G RC=3000
Article ID: 250478
Updated On:
Products
Endevor
Issue/Introduction
Installed B4G application on Mainframe, found RC=3000 in the B4G log.
22.40.54 STC54352 ---- FRIDAY, 09 SEP 2022 ----
22.40.54 STC54352 IEF695I START B4G WITH JOBNAME B4G IS ASSIGNED TO U
22.40.54 STC54352 $HASP373 B4G STARTED
22.40.54 STC54352 IEF403I B4G - STARTED - TIME=22.40.54
12.22.17 STC54352 ---- FRIDAY, 16 SEP 2022 ----
12.22.17 STC54352 IEF404I B4G - ENDED - TIME=12.22.17
12.22.17 STC54352 $HASP395 B4G ENDED - RC=3000
Environment
Release : 18.1
Component : BRIDGE FOR GIT
Cause
It appears the RC=3000 is tied to the CEE5230S message, which shows that Tomcat timed out after reaching the CPU limit of 60 minutes.
When a SIGXCPU signal is received, the return code is set to 3000.
CEE5230S The signal SIGXCPU was received. ....
Resolution
ADD ("TIME=NOLIMIT") to the "//TOMCAT EXEC" statement in B4G JCL and restart the B4G server.
For example:
//* Start the Tomcat Server
//BRDG4GIT EXEC PGM=JVMLDM&VERSION,REGION=0M,TIME=NOLIMIT,
// PARM='&LEPARM/&LOGLVL &JAVACLS &SRVXML start'
Additional Information
Feedback
Yes
No
Powered by
