BALAPY Job Failing: A Non-zero Code was Returned from Call to COBOL Batch Program CIPPBAPB: 2 (Doc ID 2228995.1)

Last updated on JANUARY 31, 2022

Applies to:

Symptoms

On RMB v2.4.0.1.0, BT - Batch

BALAPY job failing: A non-zero code was returned from call to COBOL batch program CIPPBAPB: 2

ERROR
-----------------------
submitjob.BALAPY.20161109113558463.25493688.log:

Line 1: - 2016-11-09 11:35:58,571 [main] INFO (api.batch.SubmitBatch) Command-line options for this run: -b BALAPY -d 2016-05-02 -p RMBUAT_NA -g YYYY -x MAX-ERRORS=9999,CIS-DIVISION=485,DIST-THD-POOL=RMBUAT_NA
Line 33: - 2016-11-09 11:35:58,677 [main] INFO (api.batch.SubmitBatch) com.splwg.batch.submitter.softParameter.MAX-ERRORS=9999
Line 108: - 2016-11-09 11:35:58,686 [main] INFO (api.batch.SubmitBatch) sun.java.command=com.splwg.base.api.batch.SubmitBatch -b BALAPY -d 2016-05-02 -p RMBUAT_NA -g YYYY -x MAX-ERRORS=9999,CIS-DIVISION=485,DIST-THD-POOL=RMBUAT_NA
Line 174: - 2016-11-09 11:35:58,697 [main] INFO (api.batch.SubmitBatch) IBM_JAVA_COMMAND_LINE=java -Xms16m -Xmx256m -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl -Djava.net.preferIPv4Stack=true -Dcom.splwg.submitBatch.showPropertiesForRun=true -Dcom.splwg.submitBatch.batchCodeVariableForPrompt=prompt -Dcom.splwg.submitBatch.batchCodePropertiesDir=/opt/spl/rmb/RMBUAT/scripts/cm -Dcom.splwg.standalone.logfile=/opt/sploutput/RMBUAT/submitjob.{batchCode}.{sysDateTime}.{pid}.log -Dlog4j.configuration=file:///opt/spl/rmb/RMBUAT/splapp/standalone/config/submitbatchlog4j.properties -cp /opt/spl/rmb/RMBUAT/splapp/standalone/config:/opt/spl/rmb/RMBUAT/splapp/standalone/config/cm::/opt/spl/rmb/RMBUAT/splapp/standalone/lib/antlr-2.7.7.jar:/opt/spl/rmb/RMBUAT/splapp/standalone/lib/asm-3.2.jar:/opt/spl/rmb/RMBUAT/splapp/standalone/lib/castor-1.3.2-core.jar:/opt/spl/rmb/RMBUAT/splapp/standalone/lib/castor-1.3.2-xml-schema.jar:/opt/spl/rmb/RMBUAT/splapp/standalone/lib/castor-1.3...
Line 401: - 2016-11-09 11:36:05,439 [main] INFO (shared.environ.ApplicationProperties) Default maximum number of replays (e.g. on connection failover) before failing the thread is not specified via property ouaf.batch.worker.errorRecovery.maxReplays, defaulting to 1
Line 415: - 2016-11-09 11:36:05,516 [main] INFO (api.batch.JobSubmitterConfiguration) MAX-ERRORS -> 9999
Line 419: - 2016-11-09 11:36:26,063 [main] ERROR (support.cluster.ClusteredNode)
Line 421: Threads with errors:
Line 447: Threads with errors:
Line 486: Threads with errors:
Line 524: - 2016-11-09 11:36:26,090 [main] ERROR (api.batch.BatchRunStatusHelper) This execution ended with Batch Run Tree status '30'
Line 525: - 2016-11-09 11:36:26,090 [main] ERROR (api.batch.StandaloneExecuter) The Batch Run Tree indicates an unsuccessful execution
Line 536: - 2016-11-09 11:36:26,093 [main] ERROR (api.batch.StandaloneExecuter) Error encountered in standalone executer
Line 536: - 2016-11-09 11:36:26,093 [main] ERROR (api.batch.StandaloneExecuter) Error encountered in standalone executer
Line 558: - 2016-11-09 11:36:27,098 [main] ERROR (api.batch.SubmitBatch) An exception was thrown - terminating this run with exit code 2

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, BALAPY not working and affecting work process.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.