|
View previous topic :: View next topic
|
| Author |
Message |
Gautam Kaundinya
New User
Joined: 30 Apr 2012
Posts: 2
Location: India
|
|
|
|
A job abends with the below error with the IDMS program ABCD.
And as temporary fix we just restart the job from previous step where it deletes any existing input files or output report files used in the current step using the program ABCD.
RUN TIME SUBSCHEMA WAS XXXXXX
PROGRAM : ABCD
ERROR TYPE : IDMS
IDMS ERROR STATUS: 0077 ANY STATEMNT RUN-UNIT NOT BOUND OR BND 2
IDMS ERROR RECORD: record X
IDMS ERROR SET : Set X
IDMS ERROR AREA : AREA X
LAST GOOD RECORD : RECORD Y
LAST GOOD AREA : AREA Y
IDMS DML SEQUENCE: 0000000028
%ABEND%IDMS%ABCD
.RUN UNIT RELEASED DATABASE STATUS CANNOT BEDETERMINED
Any Idea what might be causing this?And how the restart solves the problem? |
|
| Back to top |
|
 |
Nic Clouston
Global Moderator
Joined: 10 May 2007
Posts: 2454
Location: Hampshire, UK
|
|
|
|
| Not without reading the manual - a task that should be within your own capabilities. |
|
| Back to top |
|
|
Gautam Kaundinya
New User
Joined: 30 Apr 2012
Posts: 2
Location: India
|
|
|
|
Hi Nick
Thank you for replying.
Could you tell me when this 0077 abend occurs?I mean what does RUN-UNIT NOT BOUND means? |
|
| Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
77 The run-unit has not been bound or has been bound twice. When
combined with a major code of 00, this code means either the program is no longer signed on to the subschema or the variable subschema tables have been overwritten. |
|
| Back to top |
|
|
bvarun.
New User
Joined: 05 Jul 2013
Posts: 34
Location: India
|
|
|
|
Do we have any solution to this issue. because i am facing same problem.
what i tried is i deleted the lnkbat of my cobol module and added new lnkbat component into endevor and generated it again. but still getting IDMS error status:0077,
please help me to fix this. |
|
| Back to top |
|
|
|
|
