Andrew, If you use MAX, you get 60x160 for the screen size, however, you get "gutters" on the left and right when looking at FB 80 files (JCL, Asm, etc). If you apply the APAR's Ed mentions, you can use DATA, and get 51x80 now, or 62x80 with the logon APAR, full screen for JCL/ASM files, and 61x160 for SDSF, IPCS, etc. With DATA it will use the primary screen size, which is now queried, rather than forced to 24x80. Wayne Driscoll Product Developer JME Software LLC NOTE: All opinions are strictly my own.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Andrew McIntyre Sent: Tuesday, August 22, 2006 10:34 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: >27x132? 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. Edward Jaffe wrote: > Andrew McIntyre wrote: >> I just looked at your PMR and I believe the reason I have never run >> into this is because the D4A32XX3 logmode does NOT specify an >> alternate screen size, therefore TSO defaults to 24x80 during logon, >> and works ok. I think your logmode specifies an alternate screensize >> and so you are running into the problem that you describe. > > Exactly! You're limiting yourself to a 24x80 primary screen size. I'm > using a *much* larger size. For example, I use 62x80 when editing > assembler language source code or JCL and 62x132 (though I'm now > considering increasing that to 62x136 or even 62x142 based on other > comments) for viewing reports, operlog, etc. > > Though TSO/E supports very large screens, and -- with OA16111/ANCAS24 > -- even supports query of sophisticated 3270 emulators that allow > *both* primary and alternate sizes to be specified by the user, > getting past the logon screen with a primary size larger than 51x80 > was an issue that will be solved by OA17477. > > http://ew.share.org/client_files/callpapers/attach/SHARE_in_Baltimore/ > S2817EJ064923.pdf > > -- ------------------------------------------------------------------------ Andrew McIntyre - Consulting IT Specialist IBM System z(tm) Software Technical Sales SMPO (Software Migration Project Office) TMT (Tivoli Migration Team) 404-487-2477 or tie 546-2477 [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ------------------------------------------------------------------------ SMPO http://www.ibm.com/software/solutions/softwaremigration NetView for z/OS http://www.ibm.com/tivoli/products/netview-zos/resources/nv390-update.ht ml System Automation for z/OS http://www.s390.ibm.com/sa ------------------------------------------------------------------------ ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
