IBM Mainframe Forum

[Tina Zhang]

Hello guys,

I got a problem while running a PL1-DB2 program. It failed with the oncode=8091. This program has not been changed or even recompiled in years. However, the program was not changed but is now failing. I did a lot of testing on this issue and found that such issue also happens on the new batch programs that have DB2 manipulation. I have tried manully bind also and make sure there's no errors with the bind. I think this failure is with a DB2 command. Please let me know what the next steps should be to get this problem resolved. Many thanks!

Here's the output of the error messages:

SYSTSPRT
********************************* TOP OF DATA ***********
READY
DSN SYSTEM(DSNP)
DSN
RUN PROG(COVSMS1) PLAN(COVBTCH) LIB('ISC.PROD.LOAD')
DSN ENDED DUE TO ERROR+
SYSTEM ABEND CODE 0C1 REASON CODE 00000001
******************************** BOTTOM OF DATA *********

SYSPRINT
********************************* TOP OF DATA ***
COVSMS1 PROCESSING TERMINATED
ONCODE = 8091
ONCHAR =
ONSOURCE =
ONLOC = COVSMS1
ONCOUNT = 0
ONFILE =
ONKEY =
******************************** BOTTOM OF DATA *
SYSOUT
********************************* TOP OF DATA **************************************************************************
'ERROR' condition was raised
Traceback of user routines:
Compile Unit Entry Statement CU offset Entry offset Address
COVSMS1 COVSMS1
CEE3195W The SNAP dump file could not be opened.
IBM0531S ONCODE=8091 Operation exception
From compile unit COVSMS1 at entry point COVSMS1 at compile unit offset -0D65F348 at entry offset -0D65F350
at address 00000000.
Possible Bad Branch: Statement: Offset: +000033AE
******************************** BOTTOM OF DATA ************************************************************************

[dick scherrer]

Hello and welcome to the forum,

It is quite possible that the 0c1 is only the symptom rather than the cause of the problem. I suspect that there is some "bad code" that only causes the problem when some particular data condition/combination exists.

Does the problem happen on the first interaction with the database?

Suggest you talk with your technical or database support to learn which diagnostic tools are available on your system. Diagnostic tools are site-specific so we don't know what might be available to use.

[cbhargavi]

Hi guys,

Even am facing the same issue ,getting 0C1 abend while running a PLI-DB2 program.
Did anybody get the solution. If so can you please provide me..

It is happening with first interaction with database.
It is executing PLI program but it is not connecting to database part.
Binding also went fine.

Thanks inadvance.

[prino]

Even am facing the same issue ,getting 0C1 abend while running a PLI-DB2 program.

Three years later you have the same problem?

The thread to which you attached your meaningless reply (no copies of error messages, sysprint, etc) never got a reply, so why do you think we can help you if you supply even less data?

[cbhargavi]

Hi...
am sorry for giving less info.
Actually we have an issue like 'select into' is not supporting in sub queries and when tried to rebind the package it is failing with -109 after database migrated to DBV9.
so we changed the the subquery in the program and compiled and bind it successfully.. after running the program it is giving Abend Soc1 reason code 000001.
and pli oncode= 8091.
It is failing at first interaction with database.Pli part is exectuing fine..I tried it making displays to confirm it.
I hope database is not connecting...I tried all the ways ..I didnt get any clue.

Can you please assists me here.

Here are the error messages:

ONCODE=8091 Operation exception
From entry point _ON_Begin_549_Blk_2 at compile unit offset -24075D28 at entry
00000000.
Possible Bad Branch: Statement: Offset: -FFFFE4CE

SYSTSPRT:
=================
READY
DSN SYSTEM(DB93)
DSN
RUN PROGRAM(TSRP16) PLAN(TSRTEST) LIBRARY('GBSDOM.PRODFIX.LOAD')
IKJ56641I DSN ENDED DUE TO ERROR+
IKJ56641I SYSTEM ABEND CODE 0C1 REASON CODE 00000001