|
No, it is not impossible. The answer lies within the TELNET
parms used in the TCP/IP TN3270 server. These parms can be
customized by the system programmer responsible for TCP/IP.
Within the parms for the TN3270 server, VTAM logon mode
(logmode) tables are defined. They may look like this:
TELNETDEVICE 3278-2-E NSX32702 ; 24 line screen
TELNETDEVICE 3279-2-E NSX32702 ; 24 line screen
TELNETDEVICE 3278-3-E NSX32703 ; 32 line screen
TELNETDEVICE 3279-3-E NSX32703 ; 32 line screen
TELNETDEVICE 3278-4-E NSX32704 ; 43 line screen
TELNETDEVICE 3279-4-E NSX32704 ; 43 line screen
TELNETDEVICE 3278-5-E NSX32705 ; 132 col screen
TELNETDEVICE 3279-5-E NSX32705 ; 132 col screen
The key is to add the proper logmode for an application
defined alternate screen size to the various device type
entries (add the DYNAMIC entry also):
TELNETDEVICE 3278-2-E D4C32XX3 ; 24 line screen
TELNETDEVICE 3279-2-E D4C32XX3 ; 24 line screen
TELNETDEVICE 3278-3-E D4C32XX3 ; 32 line screen
TELNETDEVICE 3279-3-E D4C32XX3 ; 32 line screen
TELNETDEVICE 3278-4-E D4C32XX3 ; 43 line screen
TELNETDEVICE 3279-4-E D4C32XX3 ; 43 line screen
TELNETDEVICE 3278-5-E D4C32XX3 ; 132 col screen
TELNETDEVICE 3279-5-E D4C32XX3 ; 132 col screen
TELNETDEVICE DYNAMIC ,D4C32XX3 ; dynamic
The other pieces of the puzzle that must also support a
custom screen size are the emulation program (your TN3270E
client), the VTAM session manager (if used) and of course
the application. Since you were already using the custom
screen size in an SNA environment, it sounds like all the
pieces are already in place except the TCP/IP TELNET parms.
For more information on customizing TCP/IP on z/OS see:
IP Configuration Reference
IP Configuration Guide
|
