|Date: ||Tue, 5 Aug 1997 22:37:29 -0400|
|Reply-To: ||CICS List <CICS-L@UGA.CC.UGA.EDU>|
|Sender: ||CICS List <CICS-L@UGA.CC.UGA.EDU>|
|From: ||Kleyn <akleyn@ESCAPE.COM>|
|Subject: ||Re: Testing in intertest|
|Content-Type: ||text/plain; charset="iso-8859-1"|
Thank you for help, I did all fine.
I realy have version 5.4. Can you speak more detaily about bugs in this
Thank you, Aleks Kleyn
From: Stefan Raabe <Stefan_Raabe@GILLETTE.COM>
To: CICS-L@UGA.CC.UGA.EDU <CICS-L@UGA.CC.UGA.EDU>
Date: Monday, August 03, 1998 1:48 AM
Subject: Re: Testing in intertest
> start with the list transaction, select your program, (your source
> code will be displayed). type an "U" on front of the line to set an
> unconditional breakpoint.
> be sure your program is not excluded from monitoring.
> you may test this with the supplied demo transactions
> (dema,demc,demp - asmdemo, cobdemo, plidemo)
> you should not use cobol optimiziation when testing with intertest,
> because this will destroy the match between source and load module.
> this could cause breakpoints pop up even if they are not true.
> do you have version 5.4? there are some other bugs... cobol variables
e.g. account of account-record, account of display-record - this will not be
resolved when displaying variables or contents of variables.