View previous topic :: View next topic |
Author |
Message |
solitude bliss Beginner
Joined: 16 Jan 2004 Posts: 8 Topics: 3
|
Posted: Wed Apr 21, 2004 9:18 am Post subject: ADSO screen abort |
|
|
Hi,
we use IDMS/ADSO in our shop. Of late we have been experiencing a rather peculiar problem. When the end users try to update online on a particular screen, it is aborting. (the enter process for that dialog is aborting). Here is the abort message.. (for security reasons, I am forced to mask the dialog name.. Apologies)
IDMS DC466014 V145 Abort occurred in dialog XXXXXXXX process XXXXXXXX-Enter Process
IDMS DC466015 V145 At offset 11B60 source sequence number 00256900.
IDMS DC466004 V145 Unable to display source. Error status= 1494
The problem we are facing while trying to debug is that we are unable to replicate this error in TEST region. But it still is occuring in the production environment.
I need to know is there any way I can locate what line in the dialog the offset 11B60 is pointing to? I can see the line 00256900.. but it is not helping much. So, I need your help in finding what this offset is pointing to..
Thanks, |
|
Back to top |
|
|
kolusu Site Admin
Joined: 26 Nov 2002 Posts: 12376 Topics: 75 Location: San Jose
|
Posted: Wed Apr 21, 2004 10:07 am Post subject: |
|
|
Normal IDMS programming results in a four character error code being returned from each call
to IDMS (on any DML verb such as OBTAIN, MODIFY, STORE, BIND, READY, etc _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
|
shiv_swami Beginner
Joined: 29 Nov 2003 Posts: 68 Topics: 14
|
Posted: Wed Apr 21, 2004 3:46 pm Post subject: |
|
|
solitude bliss,
Check the Compile options of the dialog that you have moved to production.We had a similar problem in Production recently.When the Autostatus option on panel 1 of the ADSC screen was cleared.May be you can just ensure the compile options in effect in production are same as they are in Test region. _________________ Regards,
Shivprakash |
|
Back to top |
|
|
solitude bliss Beginner
Joined: 16 Jan 2004 Posts: 8 Topics: 3
|
Posted: Thu Apr 22, 2004 1:46 pm Post subject: |
|
|
We found out the problem. Strange enough...! it was not related to the error it was displaying. It was due to some security settigns of the user's logon id. Still unable to figure out how could that have caused the dialog abort.
Thanks for the help.. surely would post the exact reason for the abort when I find it.
Thanks,
Santhosh |
|
Back to top |
|
|
vkrishna2001 Beginner
Joined: 07 Aug 2003 Posts: 46 Topics: 18 Location: Danbury
|
Posted: Thu May 20, 2004 4:40 pm Post subject: |
|
|
Solitude Bliss,
You can run ADSO report on the dialog in test region to find the sequence number and instruction that caused the abend.
Vijay |
|
Back to top |
|
|
|
|