RE: Source Debug in 132 column -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
What a treat to hear that you've seen the source debugger in 132 mode!

What release are you seeing this?  Are you using STRDBG or STRISDB?

I haven't tried this, but why not just do the same thing you do when
debugging a program during a batch job?  Start a service job on the
interactive job from another session.  Can't see why this wouldn't work.

Let us know.

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952
D.Bale@Handleman.com

> -----Original Message-----
> From: Mohondro, Kevin [SMTP:KMohondro@SalePoint.com]
> Sent: Thursday, August 30, 2001 5:17 PM
> To:   Midrange-L (E-mail)
> Subject:      Source Debug in 132 column
>
> Does anyone have any idea how to force the source debugger to run in
> 132
> column mode? I seem to get that mode when I'm running a service job
> debugging a batch program. However, I can't get it to do it on a
> normal
> interactive job.
>
> TIA
>
> -Moe

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.