Thomas, I'm sorry. I found this e-mail in my Drafts folder. If you still have a problem, it may help. If you don't have a problem any more, perhaps you can explain to us all how you solved it.
The original paper says "TSO applications will now automatically use the larger screen size whenever needed. For example, SDSF will display spool files in their full width of 132 characters while displaying nearly 50 lines of the file." What maybe it should have said was "TSO applications which are sensitive to variable screen dimensions will now automatically ...". Such "TSO applications" are the command line lists, ISPF, SDSF and the like. If you have some less flexible application it may not be able to cope with your new screen dimension. It may be insisting on the "model 4" size, 43x80, with which you usually work. If it has any flexibility at all it is likely that, at a minimum, it may work with the "model 2" size, 24x80. This is a normal design requirement for 3270 applications developed since the late 70's when the screen sizes larger that 24x80 became available. In order to check this out, if you can see in the REXX clist where the first output data stream is written, you should ensure that the "Erase Write" command is the first byte rather than the "Erase Write Alternate". With the standard IBM-supplied mode table entry, D4C32XX3, "Erase Write", 0xF5, instructs the display microcode or the emulator programming that the screen is to have 24 rows of characters in 80 columns while "Erase Write Alternate", 0x7E, instructs the display microcode or the emulator programming that the screen is to adopt whatever is the maximum of which it is capable. In the case of PCOM, the maximum is what you specified with the ScreenSize keyword. Note that the screen dimensions defined by PCOM are made known to the VTAM application, in our case TSO, by a required fancy exchange of information at the beginning of the SNA session. It may be you are using some REXX facilities with which I am not familiar in order to drive your screen application so I hope this is enough for you to sort out what might be wrong with it. You did hint that you suspected the byte values in your data stream. If your application works with "model 4", 43x80, dimensions, it tends to indicate there is nothing wrong with the byte values in your data stream. However, if it is attempting to build the data stream dynamically, some bugs might be revealed when it is trying to deal with untested screen dimensions. Chris Mason ----- Original Message ----- From: "Thomas Berg" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Monday, 31 October, 2005 8:55 PM Subject: VB: Creating dynamic 3270 screen size definitions for increased productivity TD102151 > I'm trying this now, but having some problems. > > I'm getting: > IKT00405I SCREEN ERASURE CAUSED BY ERROR RECOVERY PROCEDURE when e g running rexx that displays text containing characters with hexvalues below x'73' or even in the range x'74' - x'79'. (The same rexx is running and displaying without problems in my usual 43x80 "mode".) > > I suppose this has something to do with some character translation table for TSO or VTAM ? > > Any hints ? > > TIA > Thomas Berg > > -----Ursprungligt meddelande----- > Från: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] För Knutson, Sam > Skickat: den 13 oktober 2005 14:47 > Till: [email protected] > Ämne: Creating dynamic 3270 screen size definitions for increased productivity TD102151 > > > It's not new news around IBM-MAIN but I stumbled on this note in the WSC library which says the same thing Ed has said for many years about letting go of the real 3270 screen geometries. It might be useful to help convince others in your organization that this is really a good idea. > > Thanks, Sam > > http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TD102151 > > Document Author:Louis Wilen > Additional Author(s):John Hutchinson > > Document ID: TD102151 > Doc. Organization: Washington Systems Center > Document Revised: 01/24/2005 > > Product(s) covered: Communications Server for OS/390; Communications > Server for z/OS; VTAM; zSeries; z/OS > > Abstract: Creating dynamic 3270 screen size definitions for increased > productivity ---------------------------------------------------------------------- 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
