ca.portal.admin

Re:Re: IDMS / COBOL Debugging Tools

Discussion created by ca.portal.admin on Jun 24, 2009
It depends on whether it's on-line or batch DC-COBOL. With batch you
could use something like Xpediter, but for on-line I believe you are limite=
d to the on-line debugger.

Tim Gortner
Sr. Consultant - Sogeti USA
Medical Systems and Data Warehousing
Division of Data Management
Iowa Department of Human Services



----- Original message -----
From: ""Baloga John"" <john.baloga@VOLVO.COM>
To: IDMS-L@LISTSERV.IUASSN.COM
Date: Wed, 24 Jun 2009 17:10:35 +0200
Subject: IDMS / COBOL Debugging Tools

Hello Everyone,

One of our programmers contacted me asking about debugging a COBOL
IDMS/DC program. We have ADS-Alive and On-Line Bugger for dialogs
and IDMS/COBOL batch programs we have IDMS Trace. Is there any tools
or methods for debugging this type of program. Thanks for your help.


_________________________________________________
John N. Baloga
IDMS DBA, Global I & O
Volvo Information Technology
7825 National Service Road, Greensboro, NC 27409 United States of America

Telephone: 336-393-3425
Telefax: 336-393-4080
E-mail: john.baloga@volvo.com

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.12.90/2198 - Release Date: 06/23/09 =
17:54:00
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: IDMS / COBOL Debugging Tools
"Since LE moved into IDMS-DC the Cobol DISPLAY verb works fine. There's just a couple of hints that might help:

1) Always put the program name issuing the DISPLAY first - followed by the relevant debugging information - such as whether start/end of a routine and the input/output at the start and the end - and so forth
2) For Development (and QA) put a ""D"" in the Cobol Comment column and compile with the DEBUG option - when the program runs the DISPLAYs verbs will execute
3) For Production - leave the ""D"" for DISPLAY (actually for DEBUG) lines in but remove the DEBUG compile option - and the DISPLAYs will be bypassed.

Done in this manner it saves putting the DISPLAYs in and taking them out all of the time (and as mentioned in other posts you always miss at least one debugging statement) - while giving you useful debug information in your development environment and by not putting a whole lot of cr@p out in Production.

HTH - cheers - Gary


Gary Cherlet
Justice Technology Services
Department of Justice, SA Government
Telephone +61 (0)8 8226 5199
Facsimile +61 (0)8 8226 5311
Mobile +61 (0)41 333 1613
MailTo:cherlet.gary@saugov.sa.gov.au

This e-mail message and any attachments are qualified as follows: Addressing: If you have received this e-mail in error, please advise by reply e-mail to the sender. Please also destroy the original transmission and its contents. Confidentiality: This e-mail may contain confidential information which also may be legally privileged. Only the intended recipient(s) may access, use, distribute or copy this e-mail. Individual Views: Unless otherwise indicated, the views expressed are those of the sender, not Justice Technology Services. Computer Viruses: It is the recipient's responsibility to check the e-mail and any attached files for viruses.

Outcomes