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
Re: Debugging database procedures
"The way IDMS knows whether it's system mode or user mode is the way the
routine gets called. System mode, modules are loaded from the vector
table, user mode uses the appropriate dc call. And it's not that IDMS
actually makes a verdict, but it's the way the macro of the call
expands. the tce does have a usermode flag, that gets turned off and on
when crossing the threshholds and that's how idms knows later on down
the line whether it's running stuff in system or user mode and whether
the work to switch thressholds is required. You can however call a
system routine using a sysgenned program. This is the preferrable way to
invoke system exits for example. You can invoke an exit by program name
(a pde cum sysgen is required) or by entry point name.

Lutz Petzold

Outcomes