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
limited 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 Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: IDMS / COBOL Debugging Tools
"Bit of warning=20

Be sure to remove/comment out any and all debugging code added to any =
program.=20

I once told a fellow programmer of a debugging approach like this. He =
fixed the problem as assigned in record time, but left the debugging =
logic,

needless to say it hung the system.


Life and learn


Bob =20
----- Original Message -----=20
From: Isaac Friedman<mailTo:if_sys_cam@HOTMAIL.COM>=20
To: =
IDMSVENDOR-L@LISTSERV.IUASSN.COM<mailTo:IDMSVENDOR-L@LISTSERV.IUASSN.COM>=
=20
Sent: Wednesday, June 24, 2009 11:49 AM
Subject: Re: IDMS / COBOL Debugging Tools


You can use SNAP (in place of DISPLAY) and check the log (OLP)

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

-----Original Message-----
From: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM] =
On
Behalf Of Tim Gortner
Sent: Wednesday, June 24, 2009 11:45 AM
To: IDMS-L@LISTSERV.IUASSN.COM<mailTo:IDMS-L@LISTSERV.IUASSN.COM>
Subject: Re: IDMS / COBOL Debugging Tools

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
limited 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<mailTo:john.baloga@VOLVO.COM>>
To: IDMS-L@LISTSERV.IUASSN.COM<mailTo: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<mailTo:john.baloga@volvo.com>

No virus found in this incoming message.
Checked by AVG - www.avg.com<http://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
"Bit of warning

Be sure to remove/comment out any and all debugging code added to any program.

I once told a fellow programmer of a debugging approach like this. He fixed the problem as assigned in record time, but left the debugging logic,

needless to say it hung the system.


Life and learn


Bob
----- Original Message -----
From: Isaac Friedman<mailTo:if_sys_cam@HOTMAIL.COM>
To: IDMSVENDOR-L@LISTSERV.IUASSN.COM<mailTo:IDMSVENDOR-L@LISTSERV.IUASSN.COM>
Sent: Wednesday, June 24, 2009 11:49 AM
Subject: Re: IDMS / COBOL Debugging Tools


You can use SNAP (in place of DISPLAY) and check the log (OLP)

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

-----Original Message-----
From: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM] On
Behalf Of Tim Gortner
Sent: Wednesday, June 24, 2009 11:45 AM
To: IDMS-L@LISTSERV.IUASSN.COM<mailTo:IDMS-L@LISTSERV.IUASSN.COM>
Subject: Re: IDMS / COBOL Debugging Tools

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
limited 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<mailTo:john.baloga@VOLVO.COM>>
To: IDMS-L@LISTSERV.IUASSN.COM<mailTo: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<mailTo:john.baloga@volvo.com>

No virus found in this incoming message.
Checked by AVG - www.avg.com<http://www.avg.com/>
Version: 8.5.339 / Virus Database: 270.12.90/2198 - Release Date: 06/23/09
17:54:00
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: IDMS / COBOL Debugging Tools
"When I worked at Galileo, we had many DC-COBOL programs. I had the DBA
add a DC message that had variables that I could put literals in add map
to data elements for display - then I just did a WRITE LOG MESSAGE ID
message-id to display the message. Less extraneous data than a SNAP so
less stuff in the log.

Messages stored in the data dictionary can contain symbolic parameters.
Symbolic parameters, identified by an ampersand (&) followed by a
two-digit numeric identifier, can appear in any order within the
message. The WRITE LOG statement can specify replacement values for one
or more symbolic parameters


----- 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
"
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
"When I worked at Galileo, we had many DC-COBOL programs. I had the DBA
add a DC message that had variables that I could put literals in add map
to data elements for display - then I just did a WRITE LOG MESSAGE ID
message-id to display the message. Less extraneous data than a SNAP so
less stuff in the log.

Messages stored in the data dictionary can contain symbolic parameters.
Symbolic parameters, identified by an ampersand (&) followed by a
two-digit numeric identifier, can appear in any order within the
message. The WRITE LOG statement can specify replacement values for one
or more symbolic parameters


----- 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
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: IDMS / COBOL Debugging Tools
"Been there and done that...I used to tell my staff to embed funky words
(i.e. hotdog, ketchup mustard, or @@@) in temporary test error messages or
snaps. We'd create debugging messages like DISP TEXT '@hotdog1 - sub is out
of range' or SNAP TITLE IS '@@@HOTDOG at point 1...', etc.

The migration team would do a find on these funky words or @@@.

If they ever slipped in users or support would immediately know.

Outcomes