IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

IDMS error status:0077


IBM Mainframe Forums -> IDMS/ADSO
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Gautam Kaundinya

New User


Joined: 30 Apr 2012
Posts: 2
Location: India

PostPosted: Wed Jan 02, 2013 3:15 pm
Reply with quote

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
View user's profile Send private message
Nic Clouston

Global Moderator


Joined: 10 May 2007
Posts: 2455
Location: Hampshire, UK

PostPosted: Wed Jan 02, 2013 4:22 pm
Reply with quote

Not without reading the manual - a task that should be within your own capabilities.
Back to top
View user's profile Send private message
Gautam Kaundinya

New User


Joined: 30 Apr 2012
Posts: 2
Location: India

PostPosted: Wed Jan 02, 2013 5:11 pm
Reply with quote

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
View user's profile Send private message
PeterHolland

Global Moderator


Joined: 27 Oct 2009
Posts: 2476
Location: Netherlands, Amstelveen

PostPosted: Wed Jan 02, 2013 6:19 pm
Reply with quote

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
View user's profile Send private message
bvarun.

New User


Joined: 05 Jul 2013
Posts: 34
Location: India

PostPosted: Mon Sep 02, 2013 8:43 am
Reply with quote

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
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> IDMS/ADSO

 


Similar Topics
Topic Forum Replies
This topic is locked: you cannot edit posts or make replies. Sort card help to prepare status report DFSORT/ICETOOL 13
No new posts COOLGEN - DB2. -927 error while initi... DB2 8
No new posts SOC7 error with DFSORT DFSORT/ICETOOL 9
No new posts Secondary index error while loading d... IMS DB/DC 2
No new posts Error 0C1 Reason Code 1 with branch i... PL/I & Assembler 3
Search our Forums:

Back to Top