|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Glad it worked for you! Yes, it is difficult to debug a large batch job with lots of records without STRSRVJOB. I'm glad IBM created that command! -----Original Message----- From: geir.kildal@entragroup.com [mailto:geir.kildal@entragroup.com] Sent: Wednesday, December 12, 2001 3:30 AM To: cobol400-l@midrange.com Subject: RE: Looping programs This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] . . Joel. I have performed a test on an OPM-pgm. It worked nicely! Just be sure to get the right jobname, userid and job# when the STRSRVJOB is run! When STRDBG is started on the testpgm, program control is given immediatly to my screen, From then, it's just like an ordinary debug session! When I leave the debug with F3, the program continues like nothing has happend. Just wonderful! Thanks a lot. Mvh. Geir "Stone, Joel" <IMCEAEX-_O=TREE+20OF+20LIFE_OU=US+5FMSP+5FGMW_CN=RECIPIENTS_CN=STONEJ@Treeo fLife.com> Sent by: cobol400-l-admin@midrange.com 10.12.01 18:42 Please respond to cobol400-l To: "'cobol400-l@midrange.com'" <cobol400-l@midrange.com> cc: Subject: RE: Looping programs This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Oops - I gave the wrong cmd - it is STRSRVJOB, (not STRSRVPGM). 1) Compile with debug = *list 2) Run batch job 3) DSPJOB to get user & job# 4) STRSRVJOB user job# 5) STRDBG progname 6) now you can set breakpoints and step thru the job just like an interactive debug session! I think the STRSRVJOB command was written by IBM to do just what you are wanting to accomplish. Let me know if it works out for you. -----Original Message----- From: geir.kildal@entragroup.com [mailto:geir.kildal@entragroup.com] Sent: Monday, December 10, 2001 1:49 AM To: cobol400-l@midrange.com Subject: RE: Looping programs This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Joel. This sounds more like what I'm looking for. Could you please give an example on how to use STRSRVPGM and say something about what this command does? Do I have to compile the 'problem-pgm' with debug options to make this work? I'll like to make a looping program and test this. Mvh. Geir "Stone, Joel" <StoneJ@GourmetAward.com> Sent by: cobol400-l-admin@midrange.com 07.12.01 17:20 Please respond to cobol400-l To: "'cobol400-l@midrange.com'" <cobol400-l@midrange.com> cc: Subject: RE: Looping programs This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Just curious, why not STRSRVPGM and STRDBG ? First run the job. When the problem occurs after thousands of records, start the debug process (STRSRVPGM and STRDBG) and view the variables that you want to see. -----Original Message----- From: geir.kildal@entragroup.com [mailto:geir.kildal@entragroup.com] Sent: Friday, December 07, 2001 7:29 AM To: cobol400-l@midrange.com Subject: Re: Looping programs This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Hello. I'm talking about an OPM-COBOL-program running on an AS/400(V4R4) only. Is it possible to stop a running program controlled, and have a formatted dump of the varables at the same time. I'm not talking of running a program in debug mode. The need described above can occur after the program has processed thousends of records in production environment, and starts to loop. I want, among other things, to see what certain variables contain at the that point. Maybe the only solution is to rerun the program in debug mode?? Mvh. Geir "IDNONADA" <idnonada@home.com> Sent by: cobol400-l-admin@midrange.com 07.12.01 13:49 Please respond to cobol400-l To: <cobol400-l@midrange.com> cc: Subject: Re: Looping programs I'll help you with this, but need more information. Is it Cross-Platform? Advise me of application scenarios & specifics and/or email Cobol source code, I can help nail down the problem and optimize program. Since I'm currently under-employed, I have spare time. Confidentiality is assured. Glad to be of assistance, if I may. Sincerely, Jim Walker ----- Original Message ----- From: <geir.kildal@entragroup.com> To: <cobol400-l@midrange.com> Sent: Wednesday, December 05, 2001 3:56 AM Subject: Looping programs > This is a multipart message in MIME format. > -- > [ Picked text/plain from multipart/alternative ] > Hello. > > Now and again, it happens that a program is looping in a production > system. Is there a way to stop it a little more controlled than just > killing it, and get a formatted dump at the same time(e.g. force it into a > dump)? > > > Mvh. > > Geir > > > _______________________________________________ > This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list > To post a message email: COBOL400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/cobol400-l > or email: COBOL400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/cobol400-l. > _______________________________________________ This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list To post a message email: COBOL400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/cobol400-l or email: COBOL400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-l. _______________________________________________ This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list To post a message email: COBOL400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/cobol400-l or email: COBOL400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-l. _______________________________________________ This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list To post a message email: COBOL400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/cobol400-l or email: COBOL400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-l. _______________________________________________ This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list To post a message email: COBOL400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/cobol400-l or email: COBOL400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-l. _______________________________________________ This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list To post a message email: COBOL400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/cobol400-l or email: COBOL400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-l. _______________________________________________ This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list To post a message email: COBOL400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/cobol400-l or email: COBOL400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-l.
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.