Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
Abends with return code 0361 on some 'inauspicious ' days

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> IDMS/ADSO
View previous topic :: :: View next topic  
Author Message
Pjoe

New User


Joined: 22 Jul 2005
Posts: 17

PostPosted: Fri Jul 22, 2005 2:44 pm    Post subject: Abends with return code 0361 on some 'inauspicious ' days
Reply with quote

Hi All,
I have a job which abends with return code 0361 on some 'inauspicious ' days.
The error code details is " No record can be found for a pointer db-key. This is often caused by broken chains in the db due to incorrect recovery.".

This happens in a obtain last record within set-name statement .I am handling only on db-end-of-set. I can trap this error with on any-error-status . But the customer standards do not allow using on any-error-status. Please note that the record i am accessing is updated simultaneously by other programs also. If i get am getting a dead lock abend, i could have convinced the customer . Can any body explain the broken chain concept. I feel that this due some problem in pointers(next,prev etc) in the record.It will be of great help to me , if any body can throw some light on the root cause of this issue.

With regards,
Joe
Back to top
View user's profile Send private message

Puneet

New User


Joined: 27 Jun 2005
Posts: 9
Location: Chennai

PostPosted: Mon Sep 19, 2005 9:59 am    Post subject:
Reply with quote

HI Joe,

Sorry for sending the Reply quite Late.
According my understandings :The Broken chain happens in IDMS when a key stored in some Record(This key is used to access some other record in a different Area, for example Key Stored in Record A can be used to Obtain Record B using Sort keys ) is not able able to fetch a Record using this key value as sort key. This generally happens when the database refresh does not happen
correctly in different Areas.

Thanks,
Puneet
Back to top
View user's profile Send private message
shiv_swami

New User


Joined: 25 Aug 2006
Posts: 5

PostPosted: Fri Aug 25, 2006 11:11 pm    Post subject:
Reply with quote

0361 in online envirnment is quite strage. I suggest to put Retrival Lock on all ADS dialogs, so you would either get a deadlock or successful transaction but not a 0361.

0361 in a batch retrieval job is acceptable if other updates jobs are running. As you implicitly know that retrieval job would do "dirty read"s.
Back to top
View user's profile Send private message
visun_2010

New User


Joined: 16 Oct 2006
Posts: 1
Location: BANGALORE

PostPosted: Mon Oct 16, 2006 2:20 pm    Post subject:
Reply with quote

Hi,

It could be due to recent program has deleted the record which you are try to access, then also this problem can occur. Do you try to get the record using the db_key or walking the set? If possible send me the code list, it would be easy to fix.

Sundar
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> IDMS/ADSO All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Speed-up/reduce CPU use of code prino PL/I & Assembler 0 Tue Sep 26, 2017 12:05 am
No new posts Return a Non Numeric value from REXX Learncoholic CLIST & REXX 3 Fri Sep 01, 2017 8:33 pm
This topic is locked: you cannot edit posts or make replies. how to code for GDG in Rexx cvnlynn CLIST & REXX 13 Wed Aug 09, 2017 9:13 pm
This topic is locked: you cannot edit posts or make replies. rexx code to create a ps file Bharath Vikraman CLIST & REXX 4 Mon Aug 07, 2017 10:30 am
No new posts I want to retire TRX and use only Rex... Abhinav Sharma CLIST & REXX 6 Sat Jul 29, 2017 2:53 am

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us