Re: Field Lenth Question

No, it wasn't - imho.

The tip in the newsletter was *not* for VIP persons. 

Leif
----- Original Message ----- 
From: <rob@xxxxxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Sent: 17. januar 2006 22:30
Subject: Re: Field Lenth Question


> Was that a copyrighted newsletter?  I wouldn't want to get David in 
> trouble.
> 
> Rob Berendt
> -- 
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
> 
> 
> 
> 
> 
> "Leif Guldbrand" <Guldbrand@xxxxxxxxx> 
> Sent by: rpg400-l-bounces@xxxxxxxxxxxx
> 01/17/2006 04:26 PM
> Please respond to
> RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
> 
> 
> To
> "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
> cc
> 
> Fax to
> 
> Subject
> Re: Field Lenth Question
> 
> 
> 
> 
> 
> 
> Your right...
> 
> Scott's version:
> 2. DEBUGGING IN 132 COLUMN MODE, PART 2
> In the February 10, 2004, issue of this newsletter, I published a tip that 
> 
> explained how to set the ILE_DEBUGGER_1 environment variable to make it 
> possible to use STRDBG in 132 column mode.
> 
> After writing that newsletter, I received a suggestion from Leif Guldbrand 
> 
> that I wrap these ADDENVVAR and RMVENVVAR commands in a simple CL program 
> and call that program from a command. 
> 
> After considering his suggestion a little bit, I came up with the 
> following 
> command called DBGWIDE:
> 
>              CMD        PROMPT('Set Wide Debugging *ON/*OFF')
> 
>              PARM       KWD(SETTING) TYPE(*CHAR) LEN(4) RSTD(*YES) +
>                           DFT(*ON) VALUES(*ON *OFF) PROMPT('Wide +
>                           debugging setting')
> 
> That command will run the following CL program, which I called DBGWIDECL:
> 
> PGM PARM(&SETTING)
> 
>     DCL VAR(&SETTING) TYPE(*CHAR) LEN(4)
> 
>     IF (&SETTING *EQ '*ON') DO
>         ADDENVVAR ENVVAR(ILE_DEBUGGER_1) +
>                   VALUE(ALLOW_WIDE_SCREEN) +
>                   LEVEL(*JOB) REPLACE(*YES)
>     ENDDO
> 
>     ELSE DO
>         RMVENVVAR ENVVAR(ILE_DEBUGGER_1) LEVEL(*JOB)
>         MONMSG MSGID(CPFA981)
>     ENDDO
> 
> ENDPGM
> 
> After compiling these source members into my library list, I can switch my 
> 
> debugging to 132-column mode by typing the following command:
> 
>     DBGWIDE *ON
> 
> And when I'm done and would like to go back to 80-column mode, I type the 
> following:
>  
>     DBGWIDE *OFF
> 
> My version :-)
> www.Think400.dk/adhoc_1.htm
> 
> Best regards,
> Leif
> 
> ----- Original Message ----- 
> From: "Tony Carolla" <carolla@xxxxxxxxx>
> To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
> Sent: 17. januar 2006 21:29
> Subject: Re: Field Lenth Question
> 
> 
> > This is an interesting question.  I know you can modify some behavior of 
> the
> > debugger using environment variables.  At least you can change the 
> screen
> > width with the CL command:
> > 
> > ADDENVVAR ENVVAR(ILE_DEBUGGER_1) VALUE(ALLOW_WIDE_SCREEN) LEVEL(*JOB)
> > REPLACE(*YES)
> > 
> > I wonder if there is an environment variable for this default?  I think 
> it
> > was Scott K who told me about the above technique.  Scott?
> 
> 
> 
> -- 
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
> 
> 
> -- 
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
> 
> 
>