|
[ Converted text/html to text/plain ] Greetings; 1: In the Distributed debugger, how can I add a qualified COBOL field name to the program monitor? I can't see the contents of the field, because I can't add it to the monitor. 2: How can I pass a packed number on a call to a program being debugged? I am calling the debugger from the Code/400 and putting in the parms, but I need to have the first be a number, and packed decimal. By the way, I would also like to have the debugger _automatically_ look for the "IN" or "OF" clauses when a COBOL program is being debugged. If it can tell that the identifier is not unique, look for the next word in the sentence and see if it is "IN" or "OF", regardless of how many levels of qualifiers there might be (In my case, mostly only 1, sometimes 2). System: IBM Thinkpad A21p Win 2000 Sp 2 256 Meg RAM 30 Gig Hard drive w/10 gig free AS/400 V4R5M0 IBM WebSphere Development Tools for iSeries Version: V5R1M0 Pathname: C:\WDT400\ Installation Date: 12/10/2001 The following list gives the service and configuration levels of each installed product component: Component: CODE/400 Service Level: 4 Component: Distributed Debugger Version: 9 Pathname: C:\IBMDEBUG Service Level: 1 Component: VisualAge for Java for Windows [Installed] Component: Webfacing Service Level: 4 Component: Base Service Level: 4 Component: SDK Service Level: 4 Component: ET400 [Not Installed] Component: VisualAge for RPG Service Level: 4 Component: WebSphere Studio Service Level: 4 Component: NetQuestion Program Folder: C:\IMNNQ_2K ---------------------------------------------------------- Jim Essinger Senior Programmer/Analyst Student Loan Fund of Idaho PO Box 730 Fruitland, ID 83619 208-452-4058 esinger@fmtc.com ------------------------------------------------------------
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.