Why does the IDz 14.0/RDz 9.5.1 RSE daemon (RSED) job fail with RC=3840 and return code 127?
RSE Daemon start of the job ends with JOB ENDED - RC=3840 and the remaining job detail returns:
Starting RSE daemon... -- Mon Dec 12 18:31:43 2016
java: /usr/lpp/IBM/zexpl/bin/rsed.sh 533: FSUM7351 not found
RSE daemon ended -- return code 127 -- Mon Dec 12 18:31:43 2016
When the started task is run, it is not finding the correct rse.env and also the subsequent configuration files needed to define the environment.
Several issues were found with this configuration:
1) rse.env and all other customized files in samples need to be moved to /bin.
2) RSE_HOME should be set so that there is a "-" before the path such as RSE_HOME=${RSE_HOME:-/abcd/idz/usr/lpp/IBM/zexpl} Once corrected, the started task started, but abruptly stopped.
3) The path for RSE_HOME should not end in /.
RSE_HOME=${RSE_HOME:-/abcd/idz/usr/lpp/IBM/zexpl/}
The error in the job log for this was:
ERROR -- changing RSE_HOME is not supported correct value RSE_HOME="/abcd/idz/usr/lpp/IBM/zexpl" -- /abcd/idz/usr/lpp/IBM/rse.env updates RSE_HOME
RSE_HOME="/abcd/idz/usr/lpp/IBM/zexpl/"
With RDz 9.5.1 and IDz 14.0.0.x, only the rse.env and rdz.env or idz.env should be edited. All other files should not be altered.
The JCL run for the RSE daemon specifies values for RSE_HOME and RSE_CFG. RSE_HOME is repeated in rse.env. The startup scripts verify that RSE_HOME is the same in both locations.
Each of the *.env files has a specific function. Default values are set for idz.final.env, idz.init.env, idz.product.env, rse.final.env, rse.init.env, rse.product.env., so the customer-specific file (rse.env) is optional.
If edits need to be made to environment variables such as JAVA_HOME, only perform updates to the *.env/conf/properties files.
The *.env files in the bin directory are maintained by SMP/E, and will be overlayed with every PTF. They should NOT be altered for any reason. Only use rse.env or rse.override.env to make RDz/IDz changes if needed.
Also, look at the current space usage and maximum space available in the output of the job log. -------------------------------------------------------------
Address Space size limits
-------------------------------------------------------------
current address space size limit is 1695522816 (1617.0 MB)
maximum address space size limit is 2147483647 (2048.0 MB)
-------------------------------------------------------------
2 GB is optimum, but it is possible to run with less, such as 200-600 MB.
If your output is not complete or unexplained errors occur, increase the address space of the user id that is running the started task.
If you have a job exit such as IFEUSI that limits the amount of space available for a job and running with 64-bit JVM, you can add MEMLIMIT to the JCL to override. An example is //REGSIZE='2047M,MEMLIMIT=800M'