If your installation has not disabled or deleted them, IBM standard VTAMLST
defines a flexible log mode (D4C32XX3) that you can specify in the LOGON to
VTAM. I use this in a PCOMM script that I use to login to my employer's
systems:
logon applid=xxxxxxxx,logmode=D4C32XX3
Where "xxxxxxxx" is my employer's system name. This allows me to use a custom
screen size (50x160) from PCOMM.
My ISPF terminal settings are:
Screen format 3 (MAX)
Terminal Type 28 (3278L1 for code page setting 1047 which allows me to
use "real" EBCDIC square brackets X'AD' and X'BD')
HTH
Peter
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Seymour J Metz
Sent: Monday, December 6, 2021 9:16 AM
To: [email protected]
Subject: Re: What determines the effective terminal size?
EXTERNAL EMAIL
I forgot to mention that OSA-ICC is a TN3270 server that presents the
appearance of a local non-SNA controller, which means that there is no exchange
of BIND. What's in the LOGMODE that you're using?
--
Shmuel (Seymour J.) Metz
https://urldefense.com/v3/__http://mason.gmu.edu/*smetz3__;fg!!Ebr-cpPeAnfNniQ8HSAI-g_K5b7VKg!eyVjdivF1-lcxrN1dYmRRl-p0KULDqDn4ERbh-nY-ht2KWbO-pVz1GnFgv5nDAOVbMe-pQ$
________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of
Christian Svensson [[email protected]]
Sent: Monday, December 6, 2021 5:07 AM
To: [email protected]
Subject: What determines the effective terminal size?
Hi folks,
I am trying to go back to basics a bit and figure out some things that I have
always treated as magic.
Right now it is how a 3270 terminal connected to a z/OS determines the size of
the terminal. In this case through OSA-ICC (zBC12, OSA-Express5) and not TCPIP,
On systems where I have configured VTAM with TCPIP the terminal size seems to
almost always "just work".
Let's take a look at an example. I have configured X3270 with model "3279-4-E"
and oversize set to "133x60".
1) What does the z/OS VTAM screen look like?
Over OSA-ICC: 80x24
Over TCPIP: 80x24
So far so good.
2) What does the TSO screen look like?
Over OSA-ICC: 80x24
Over TCPIP: 80x24
Ok, no change.
3) What does the ISPF screen look like?
Over OSA-ICC: 80x24
Over TCPIP: 133x60
Oh! But why? I do not know! Also, after I exit ISPF back to TSO, the TSO screen
is now correctly filling the full screen!
I also note that z/VM's login screen seems to behave similarly. Over OSA-ICC
the size seems to be fixed at 80x24, but over TCPIP it follows what I
configured X3270 to use.
Dialing a z/OS VTAM terminal through the z/OS login screen (connected via
TCPIP) seems to result in a 133x60 screen both in TSO and ISPF. However if I
ATTACH an OSA-ICC terminal straight to a z/OS guest, ISPF gets 133x60 but TSO
only 80x24 - *but only if I reconnect to an existing user session.* If I log
out and try to log in again I get IKT00405I "Screen erase caused by error
recovery procedure".
As you can see I am a mess when it comes to understanding how this all fits
together! It seems pretty much random to me, except that TCPIP "almost always
works" and OSA-ICC "almost never works".
I would love to learn more, but I don't even know where to begin.
Regards,
--
This message and any attachments are intended only for the use of the addressee
and may contain information that is privileged and confidential. If the reader
of the message is not the intended recipient or an authorized representative of
the intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication
in error, please notify us immediately by e-mail and delete the message and any
attachments from your system.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
