It can be done with 'ws' PROTERMCAP parameter as well. PKB says
Uses the device /dev /tty for the current port to determine the number of columns and rows for the terminal. Meaningful primarily for emulated terminals in a windowing system (that is, xterm). If successful, overrides co and li; otherwise, defaults to co and li. OpenEdge will not automatically resize if the size of the terminal changes after initialization.
I'm still not able to do 132 column, but I was able to do it with 48 rows.
I tried all the suggestions here but no luck.
Heres what I did.
1) I pointed my PROTERMCAP file in my .profile like this.
2) I modified protermcap2.dg many ways. I tried forcing 48 x 132, I tried ws, I tried both but no luck.
# note that we are assuming auto-wrap mode. # This terminal is Supported by PROGRESS. V1|vt100|vt100-80|vt100_series|DEC VT-100 running in ansi mode:\ blah blah blah :ws:\ #:co#80:\ #:co#132:\ blah blah blah #:li#24:\ #:li#48:\ blah blah blah :tc=v7kf:
3) I fired up my terminal emulator NetTerm Client using VT100 emulation. If I type stty, I see rows=48, col=132. But when I fire up _progress, the Progress Editor cuts the screen and columns back to 80.
I should also point out that I have to fire up _progres twice. The first time around, the screen is all messed up, not aligned and all that. So I quit out, and go back in and it comes out 48 x 80 neatly.
Ok, this seems to work if I start progress from scratch. What about switching modes during a session.
For example I have one screen that displays much better as a 132 column screen (no wrapping needed). But when I issue a 'terminal = "vt420w".' command within the application I get a 132 column screen with an 80 column frame.
It's not really about environment variables although TERM and PROTERMCAP are used to initialize the terminal type and location of protermcap when progress starts up. After startup they don't matter. The protermcap file itself contains entries for the various terminals that you might be running in a character session. Each entry consists of a series of "capabilities" such as "li", "co" and "ws" that describe how the terminal works.
My usual goal with protermcap is to reduce it to the smallest set of entries with the smallest set of capabilities that works for me. It's something that I futz with for some reason or other every couple of years. It's all rather arcane but something that we walking fossils like to fiddle with from time to time...