ca.portal.admin

Re:Re: IDMS / COBOL Debugging Tools

Discussion created by ca.portal.admin on Jun 24, 2009
Yeah, my all-time favorite Cobol debugging tool was ready trace. That
was on a project to convert GE Macro to Cobol, of a Demand Deposit
System, that the bank ran for other banks and got paid for the services.
In the days of one compile/link a day, and production runs in the middle
of the night, desk checking was important, and a trace in the dev
environment. But, leave it in the source code, then performance went to
pot.

Lutz Petzold
TDM UDB/IDMS Support
401-782-2265
Page 860 366 0865 or Telalert



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 =

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
"I worked with clients who had consultants building temp recs routinely in
production. They'd morph CAS records for other uses...made for some
interesting off hour calls - getting a s0c7 when encountering one of these
morphed recs and a numeric element had been used for text.

I never got into READY TRACE...I found it to be information overload.

One other trick for temporary messages/snaps is to prefix them with an IF
AGR-USER-ID EQ tester_id...Should it slip into production there shouldn't be
an impact.

Isaac Friedman
IDMS Consultant
Systems Consultants of America Inc.
248-470-0340

Outcomes