View previous topic :: View next topic
|
Author |
Message |
PremaV
New User
Joined: 05 Mar 2010 Posts: 3 Location: hyderabad
|
|
|
|
Hi,
I am getting an abend in ADSO dialog. I read in one of the post that we can use DEBUG command
DEBUG DEBUG DIAL <dialog name>
I am able to initiate this dialog. but when i give the below command
QUALIFY PROC <processname>
I am getting a message that the process is not in the dialog. However it is available in the dialog.
Can anybody help me whether there is any syntax problem?
Thanks,
Prema |
|
Back to top |
|
|
Chinnadu
New User
Joined: 05 Mar 2009 Posts: 46 Location: Hyderabad
|
|
|
|
Hello Prema,
I'm not clear on what you are doing to debug the ADS/O dialog,,, however to the best of my knowledge, we can debug the dialog using ADSALIVE tool. Are you aware of this one? Let me know if you need any further assistance to debug the dialog using ADSALIVE. |
|
Back to top |
|
|
PremaV
New User
Joined: 05 Mar 2010 Posts: 3 Location: hyderabad
|
|
|
|
I am not aware of ADSALIVE. I tried to search in the internet, didnt get much help. If you could tell me how to use it (also to check whether my shop has it) it would be great.
However i analyse the dialogs and found out the reason for the abend. Still i would like to understand the debugging options in ADSO so that i can use them in future.
Reason for my abend - there was a loop in the READY statement, which was trying to ready the area which was already readied. I got a error status - 0928.
Thanks,
Prema. |
|
Back to top |
|
|
Chinnadu
New User
Joined: 05 Mar 2009 Posts: 46 Location: Hyderabad
|
|
|
|
Hello Prema,
Below would be usefull to you.
ADSALIVE comes with ADS/O product itself; it is not a third party tool.
How to use:
1)Type in command ‘ADSALIVE’ at ‘Enter next code option in IDMS CV.
Enter the required info (dialog name ,dictionary name and version of the dialog)and hit enter.
After this you will be getting list of processes available under that dialog, and you can select the required process. Hit enter after selecting the correct process to debug.
Now you should be able to see the source code of the selected process and you can debug it interactively (You can see line by line execution here). To do this you can use PF12 key to pass the control to next execution line.
Let me know if you still have any doubts. |
|
Back to top |
|
|
PremaV
New User
Joined: 05 Mar 2010 Posts: 3 Location: hyderabad
|
|
|
|
Hi,
I tried "ADSALIVE command, it is not working
So i typed "ADSA", it accepted it and it went to a screen which is same as ADSC - compilation screen.
Is ADSA and ADSALIVE are same?
Thanks,
Prema. |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
wouldn' t it be faster to ask Your IDMS/ADSO support ?
( about the customization done for Your environment ) |
|
Back to top |
|
|
Chinnadu
New User
Joined: 05 Mar 2009 Posts: 46 Location: Hyderabad
|
|
|
|
Hello Prema,
Looks like you don't have access to ADSALIVE, check with your team on this. ADSA and ADSALIVE are different. ADSA is application compiler, ADSC is dialog compiler,ADSALIVE is debugging tool and MAPC is map compiler. Options of ADSA,ADSC and MAPC looks almost similar but the components they compile are different. If you can let us know the error message that you got when you type in 'ADSALIVE', then we can help you. |
|
Back to top |
|
|
|