Tuxedo ART 12.1.3 CICS and Batch: Program Execution Getting "File Does Not Exist" COBOL Error
(Doc ID 2022121.1)
Last updated on SEPTEMBER 19, 2023
Applies to:
Oracle Tuxedo Application Runtime for CICS and Batch - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
When the program is called, from the JCL, getting a dba_proc_called error on this region. The same JCL is working on other environments.
TestName\00002728\LOG\00002728.log
mw_trace DBConn
>> Program BEGIN : PROGRAM
Generate a dump file (TESTDIR/deploy/BATCH_RT/JESROOT/00002728/LOG/00002728.dumpinfo)
ERROR mi_ProgramExec: The program execution has an error (PROGRAM)
TestName\00002728\SYSOUT\ 00002728_FSCRIPT__SYSOUT_1
dba_proc_error : called
COBOL ERROR
TestDir/target_12182014/BATCH_Test/PROGRAM.cbl:0: File does not exist (STATUS = 35) COB_FILE: 'FNAME'.......................
TestDir/target_12182014/BATCH_Test/PROGRAM.cbl:0: libcob: File does not exist (STATUS = 35) COB_FILE: 'FNAME'
mw_trace DBConn
>> Program BEGIN : PROGRAM
Generate a dump file (TESTDIR/deploy/BATCH_RT/JESROOT/00002728/LOG/00002728.dumpinfo)
ERROR mi_ProgramExec: The program execution has an error (PROGRAM)
TestName\00002728\SYSOUT\ 00002728_FSCRIPT__SYSOUT_1
dba_proc_error : called
COBOL ERROR
TestDir/target_12182014/BATCH_Test/PROGRAM.cbl:0: File does not exist (STATUS = 35) COB_FILE: 'FNAME'.......................
TestDir/target_12182014/BATCH_Test/PROGRAM.cbl:0: libcob: File does not exist (STATUS = 35) COB_FILE: 'FNAME'
runb is working fine when run standalone (without Database related programs) . The cob library path is also pointing to correct paths in both environments.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |