× 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.



It seems this tidbit of information originated back around mid-2002 on a
news group or website. The information originated from Karl Hanson of IBM
Rochester who works/worked on the debuggers for IBM.
The question seems to keep coming up about once every year or so.

-Bob Cozzi
www.RPGxTools.com
RPG xTools - Enjoy programming again.


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Leif Guldbrand
Sent: Tuesday, January 17, 2006 3:27 PM
To: RPG programming on the AS400 / iSeries
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?




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.