Chris Mason wrote:
It is APAR OA16111 which offers the flexibility Edward invites you to appreciate. You need this APAR in order for the presentation space dimensions to be set by specifications within a suitable 3270 emulator - not currently PCOMM, you'll need BlueZone or Vista - rather than the mode table entry with the X'7F' specification in the penultimate byte of the PSERVIC operand as given in the referenced post.
BlueZone and Vista are the only emulators so far (that I know of -- someone correct me if I'm wrong) in which the primary (default) screen size may be configured by the end user and passed back to the host via RPQ.
Configuring this in BlueZone is easy. You go to Session -> Configure... and click the "3270 Emulation" tab. There is a pull-down for "Default Screen Model Type". If you select "Custom Size" (the last choice), the resulting dialog box allows you to configure both primary and alternate sizes.
You might be a bit confused with Vista because it's not readily apparent where you're supposed to specify the primary size. Tom Brennan thought the new parameters would be confusing to "normal" users (his apprehension was understandable given that he implemented this functionality before anyone other than Phoenix Software was prepared to exploit it) and so he hid them a bit. You need to find the VISTA.INI file (wherever Windows stores that) and add the following line at the bottom and restart Vista. The Options "Misc" tab is where you can configure the primary size.
AllowDefaultSizeChange=1 With one of these emulators and APAR OA16111 (or the ANCAS24 usermod), you can use TSO/E with fully-customizable primary and alternate screen sizes using one of the D4x32XX0 logmodes shown at ftp://ftp.phoenixsoftware.com/pub/demo/logmodes.txt. Keep in mind that most 3270-based applications (TSO included) prefer 80-column primary screen sizes; it's highly recommended. What I was trying to say earlier was that you can get similar functionality _right now_ using other emulators, including PCOMM, without OA16111 by using one of the Pxxxxxxx logmodes shown (or your own similar one). Of course, this is highly problematic as a general solution because you need a logmode on the host for every possible size combination a user might desire and user-friendly mechanisms for communicating the names of those logmodes and for actually specifying which of them is to be used when establishing a session with TSO/E. This alternative *can* be made to work. It's just not ever going to be a mainstream solution. Allowing the end user to configure both sizes in their emulator's GUI configuration dialog is the only solution with any real potential for mainstream acceptance and pervasive implementation. It's an iterative process. Once *all* of the TSO/E support is generally-available "out-of-the-box", getting additional emulators (including PCOMM) to support this concept should be easy. -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
