RE: Source Debug in 132 column

["Mohondro, Kevin" <KMohondro@xxxxxxxxxxxxx>]

I actually thought I'd screwed up something when I got the 132 column debug
screen :).

It's an RPGLE program on V4R5M0 and it's STRDBG.

Yup, having a second session servicing the first pulls it up in 132 column.
I just figured there might be some way to have it display that way normally.

-Moe
-------------------------------------------------------
Kevin R Mohondro                kmohondro@salepoint.com
Software Engineer                         (858)373-2012
SalePoint Corporate Retail Solutions      San Diego, CA


> -----Original Message-----
> From: Bale, Dan [mailto:D.Bale@handleman.com]
> Sent: Thursday, August 30, 2001 2:37 PM
> To: midrange-l@midrange.com
> Subject: RE: Source Debug in 132 column
>
>
> 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