|
No limits are specified in "ILE application development Example" manual. You may try to reduce the number of variables by using DBGVIEW(*SOURCE) instead of *LIST. I have a program whose listing takes about 1000 pages and never found problem with ILE debugger: OPM compiler was unable to compile it. Ciao. regards Domenico Finucci -----Messaggio originale----- Da: geir.kildal@entra.no [mailto:geir.kildal@entra.no] Inviato: venerdì 9 giugno 2000 08.55 A: COBOL400-L@midrange.com Oggetto: Re: R: R: ILE debugger - problem displaying variables in structures(C OBO L) Hello. Thanks for your interest. I'll try to be more spesific: The variables I try to display, are all 05-level fields in a 01-level structure in WORKING-STORAGE. I read a record from a file into this structure(this is a working program), so the file itself is of no interest here. I haven't tried the very same structure in a smaller program, but I have tried to display level 05-fields in smaller 01-level stuctures(in smaller programs) and it works perfectly. That's why I suspect the ILE debugger to have a practical limit on the total numbers of fields it can handle within a 01-level structure, or a limit on total size of the data area inside the debugger? Or something like it. Mvh. Geir Finucci Domenico <finucci@Fiditalia. To: "'COBOL400-L@midrange.com'" it> <COBOL400-L@midrange.com> Sent by: cc: owner-cobol400-l@mi Subject: R: R: ILE debugger - problem displaying drange.com variables in structures(C OBO L) 08.06.00 15:10 Please respond to COBOL400-L You say that if you write down a small program with the same file structure and same action the ILE debugger correctly shows 05 level ? We're talking about a single record format file ? I mean, could the file contain different record format, could you watch one not yet used by the program ? For more help please send a sample of your COBOL pgm. Ciao Domenico Finucci Fiditalia, Milano, Italy -----Messaggio originale----- Da: geir.kildal@entra.no [mailto:geir.kildal@entra.no] Inviato: giovedì 8 giugno 2000 12.43 A: COBOL400-L@midrange.com Oggetto: Re: R: ILE debugger - problem displaying variables in structures(COBO L) Hello. The problem is, the strukture(eg file) IS open. I wonder if WORKING-STORAGE simply can be too big. This works on smaller programs. Mvh. Geir Finucci Domenico <finucci@Fiditalia. To: "'COBOL400-L@midrange.com'" it> <COBOL400-L@midrange.com> Sent by: cc: owner-cobol400-l@mi Subject: R: ILE debugger - problem drange.com displaying variables in structures(COBO L) 08.06.00 10:26 Please respond to COBOL400-L Good morning Is the level 05 relevant to a structure (i.e. file) not yet open ? Domenico -----Messaggio originale----- Da: geir.kildal@entra.no [mailto:geir.kildal@entra.no] Inviato: giovedì 8 giugno 2000 10.08 A: cobol400-L@midrange.com Oggetto: ILE debugger - problem displaying variables in structures(COBOL) Problem: Having compiled a COBOL-program(OPM) with *LSTDBG and started the debugger , I'm trying to display the contents of level 05-fields(level 01 is working OK!) in WORKING-STORAGE. When I f. ex. use the command 'eval CUSTNO of WSCUSTREC', the debugger just loops, and never comes back. If I try to display a level 05-field which do not need qualifying, I get the message 'Pointer not set for location.....', which is not true, the program is working. This is quite a big program, 10 000 lines. Navigation in the program is working all right. Can anyone help, please? Mvh. Geir +--- | This is the COBOL/400 Mailing List! | To submit a new message, send your mail to COBOL400-L@midrange.com. | To subscribe to this list send email to COBOL400-L-SUB@midrange.com. | To unsubscribe from this list send email to COBOL400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---END +--- | This is the COBOL/400 Mailing List! | To submit a new message, send your mail to COBOL400-L@midrange.com. | To subscribe to this list send email to COBOL400-L-SUB@midrange.com. | To unsubscribe from this list send email to COBOL400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---END +--- | This is the COBOL/400 Mailing List! | To submit a new message, send your mail to COBOL400-L@midrange.com. | To subscribe to this list send email to COBOL400-L-SUB@midrange.com. | To unsubscribe from this list send email to COBOL400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---END +--- | This is the COBOL/400 Mailing List! | To submit a new message, send your mail to COBOL400-L@midrange.com. | To subscribe to this list send email to COBOL400-L-SUB@midrange.com. | To unsubscribe from this list send email to COBOL400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---END +--- | This is the COBOL/400 Mailing List! | To submit a new message, send your mail to COBOL400-L@midrange.com. | To subscribe to this list send email to COBOL400-L-SUB@midrange.com. | To unsubscribe from this list send email to COBOL400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---END +--- | This is the COBOL/400 Mailing List! | To submit a new message, send your mail to COBOL400-L@midrange.com. | To subscribe to this list send email to COBOL400-L-SUB@midrange.com. | To unsubscribe from this list send email to COBOL400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---END
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.
midrange.com
