Andrew McIntyre wrote:
No wait, I'm NOT limiting myself like you mentioned, except during
logon. Immediately thereafter, ISPF switches dynamically to the 60x160
size (you have to specify max on option 0). It's been doing this just
fine for oh, let me think, at least 20 years I've been doing this.
Ever since the days of the "universal" logmode (query bit) if I
remember right.
So your apar isn't really buying you anything that I can see, except
maybe during logon. Just use a query bit, no alternate screen size
logmode (like D4A32XX3) and you won't have any problems during your
ISPF session. Oh and of course, change your emulator to actually
report to the query a large screen size.
Not just logon. You miss out on other functions as well.
If you set your ISPF terminal type to "1. Data", you get to use your
primary screen size whenever conditions warrant. This can be an
extremely useful capability! But its usefulness is greatly reduced with
only 24 rows available in the primary size. OTOH, if you have the same
(or nearly the same) number of rows in both primary and alternate screen
sizes, you don't lose functionality or real-estate or have to make any
tough choices. You get the best of both geometries.
This is seen as an extremely attractive way to use 3270. So much so that
it's been relatively easy to convince the developers of various products
to which I've been exposed to support the concept of allowing query for
both sizes, not just one.
Do you disagree? Have you read either of my SHARE presentations on the
subject?
--
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
