ca.portal.admin

Re:Debugging database procedures

Discussion created by ca.portal.admin on Mar 29, 2007
What techniques are available for debugging database
procedures? I am talking here about the kind that are tied to
a record via the schema description.

We are getting D003 errors when trying to use DEBUG. Is DEBUG
supposed to work with database procedures?

My personal favorite technique for debugging online programs is
""displaying"" to the log via the WTL command. But you are not
supposed to make DML calls from a database procedure.

Any suggestions would be most welcome.

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov
This e-mail may contain confidential or privileged information. If
you think you have received this e-mail in error, please advise the
sender by reply e-mail and then delete this e-mail immediately.
Thank you. Aetna
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Antwort: Who is inside an Area in the database?
"Hi Mike,

try DCMT DISPLAY LOCK AREA areaname

It will give you a list with all the LTerms and users, who currently hold
locks on that area.

Best regards,

Juergen


|---------+---------------------------->
| | |
| | Mike Baker |
| | <mikebaker345@HOT|
| | MAIL.COM> |
| | Gesendet von: |
| | IDMS Public |
| | Discussion Forum |
| | <IDMS-L@LISTSERV.|
| | IUASSN.COM> |
| | |
| | 26.03.07 05:07 |
| | Uhr |
| | Bitte antworten |
| | an IDMS Public |
| | Discussion Forum |
| | |
|---------+---------------------------->
>-----------------------------------------------------------------------------------------------------------------|
| |
| |
| An: IDMS-L@LISTSERV.IUASSN.COM |
| Kopie: |
| Thema: Who is inside an Area in the database? |
>-----------------------------------------------------------------------------------------------------------------|





organiziQ.Clerk/Pro
Server: PRR0341
------------------------------------------------------------------------------------------------------------------------------

Sie waren als urspruenglicher Empfaenger der Nachricht eingetragen!

Diese Nachricht wurde weitergeleitet an Wolfgang
West/Sparkasse-Bremen@Sparkasse-Bremen,Egbert Kuhr/Sparkasse-Bremen.

------------------------------------------------------------------------------------------------------------------------------

Hi all,

I know that you can dTo: RET IMM, then OFF IMM, in order to kick everyone
out of a particular area, so that you can (for eg.) restructure it.

However, I am curious to know if there is a way of determining who exactly
is inside a specific area (eg. via DMLO, OLQ, etc).

Thanks.






----------------------------------------------
Die Sparkasse Bremen AG
Sitz Bremen
Amtsgericht Bremen HRB 21770
Vorsitzender des Aufsichtsrates: Gerhard Harder
Vorstand: Jürgen Oltmann (Vorsitzender), Dr. Tim Nesemann, Klaus Schöniger,
Dr. Heiko Staroßom

Am Brill 1-3, 28195 Bremen
Postfach 10 78 80, 28078 Bremen
Telefon 0421/179-0
mail@sparkasse-bremen.de
www.sparkasse-bremen.de
Bankleitzahl 29050101
Swift: SBRE DE 22
Ust-ID-Nr. DE 232135295

Wie Sie wissen, können über das Internet versandte E-Mails leicht unter
fremden Namen erstellt oder manipuliert werden. Aus diesem Grunde bitten
wir um Verständnis dafür, dass wir zu Ihrem und unserem Schutz die
rechtliche Verbindlichkeit der vorstehenden Erklärungen und Äußerungen
ausschließen.

As you are aware, e-mails sent via Internet can easily be prepared or
manipulated by third persons. For this reason we trust you will understand
that, for your own and our protection, we rule out the legal validity of
the foregoing statements and comments.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Debugging database procedures
"Kay,

I assume you know that when issuing DC commands in SYSTEM mode registers
are automatically saved by IDMS you have to tell it what to save. You
can only save R2 to R8 as R9 and R10 must never change R11 is always
saved R0 and R1 are used by the call so cannot be saved and R14 is
always from address and R15 to address.
Here is an example

#WTL MSGID=BSMSG,
MSGPREF='BS',
MSGDICT=NO,
PARMS=(BSMTEXT),
OVRIDES=MSGBOTH,
PLIST=STK2PLST,
RGSV=(R2-R8)

What I do is have 'debugging areas' in the procedure and at various
points in the code I store registers and or variables into one of the
debugging areas. So I may have 10 separate areas and would to a stores
at 10 points in the code.
I then use PMDC are similar product to display the load module in memory
and form the debugging bits I can normally see what it has gone wrong
and figure out my logic errors. This of course is only works if only you
are calling the procedure.

I always find it much harder debugging them when do not abend. With an
abend you have a dump so you can see what is wrong. It is when they do
not do what you expect and no abend it is tricky.

Hope this helps

Pete

Outcomes