Re: Odd sizes for tn3270 sessions
I sometimes also use odd sizes (particularly 43x133) in the way that Kris describes but there are a few applications (Ditto, VM:Operator) that do not like this and refuse to play. Colin Allinson Amadeus Data Processing Kris Buelens [EMAIL PROTECTED] wrote: I sometimes use odd screen-sizes from PCOMM over TELNET into VM. No problem whatsoever. VM supposrt this for ages (since the arrival of the 3290 gaspanel I think). The PCOMM GUI does not allow to enter odd values, but if you edit the .WS file you enter whatever. Kris, IBM Belgium, VM customer support
Re: Odd sizes for tn3270 sessions
62x140; same with VM:Operator not liking it, VMYCON155E userid screen size exceeds 43-line/80-column maximum. but VM:Backup resizes it to 24x80... How's that done or could it be done from REXX? Gregg No plan survives execution Colin Allinson [EMAIL PROTECTED] us.comTo Sent by: The IBM IBMVM@LISTSERV.UARK.EDU z/VM Operating cc System [EMAIL PROTECTED] Subject ARK.EDU Re: Odd sizes for tn3270 sessions 10/11/2006 04:57 Please respond to The IBM z/VM Operating System [EMAIL PROTECTED] ARK.EDU I sometimes also use odd sizes (particularly 43x133) in the way that Kris describes but there are a few applications (Ditto, VM:Operator) that do not like this and refuse to play. Colin Allinson Amadeus Data Processing
Re: Odd sizes for tn3270 sessions
Gregg Reed wrote: 62x140; same with VM:Operator not liking it, VMYCON155E userid screen size exceeds 43-line/80-column maximum. but VM:Backup resizes it to 24x80... How's that done or could it be done from REXX? Gregg resizing to 24 by 80 is done by the application using the write vs write alternate form of the command code. Don Russell
Re: Odd sizes for tn3270 sessions
On: Wed, Oct 11, 2006 at 07:27:26AM -0700,Don Russell Wrote: } Gregg Reed wrote: } 62x140; same with VM:Operator not liking it, VMYCON155E userid screen size } exceeds 43-line/80-column maximum. but VM:Backup resizes it to 24x80... } How's that done or could it be done from REXX? } Gregg } resizing to 24 by 80 is done by the application using the write vs } write alternate form of the command code. Correction Don, its erase write and erase write alternate. For the non-3270 internals folks, all 3270 displays (except model 2s (24x80)) have 2 sizes. 24x80 and another size. On real 3270s, there were only a few other sizes, such as 32x80 (model 3), 43x80 (model 4) or 27x?? (model 5). On PC based emulators, many other sizes are possible. On all of them, if an erase write command is recieved, the display reverts to 24x80, and if an erase write alternate command is recieved, the display goes to the other size. Since VM:Backup wants to display its screens on 24x80 screens, it sends an erase write first. When VM:Backup ends, either it or CP sends an erase write alternate to reset the screen to what you had before. ISTR that part of CP's response to the CLEAR key is to send an erase write alternate. -- Rich Greenberg N Ft Myers, FL, USA richgr atsign panix.com + 1 239 543 1353 Eastern time. N6LRT I speak for myself my dogs only.VM'er since CP-67 Canines:Val, Red, Shasta Casey (RIP), Red Zero, Siberians Owner:Chinook-L Retired at the beach Asst Owner:Sibernet-L
Re: Odd sizes for tn3270 sessions
Rich Greenberg wrote: On: Wed, Oct 11, 2006 at 07:27:26AM -0700,Don Russell Wrote: } Gregg Reed wrote: } 62x140; same with VM:Operator not liking it, VMYCON155E userid screen size } exceeds 43-line/80-column maximum. but VM:Backup resizes it to 24x80... } How's that done or could it be done from REXX? } Gregg } resizing to 24 by 80 is done by the application using the write vs } write alternate form of the command code. Correction Don, its erase write and erase write alternate. Yes, that's why I used ...form of the command. My point being there are multiple commands to write to the display, depending on what the application wants to do. Of course before issuing an EWA command the host should query the device to determine its capabilities. If one were to send an EWA to a device that didn't support alternate sizes, the result would be a PROG 4xx (404 I think). For the non-3270 internals folks, all 3270 displays (except model 2s (24x80)) have 2 sizes. 24x80 and another size. On real 3270s, there were only a few other sizes, such as 32x80 (model 3), 43x80 (model 4) or 27x?? (model 5). Mod 5 == 27 by 132
Odd sizes for tn3270 sessions
My tn3270 client (Seagull Software's Bluezone tn3270 client) offers me a chance to have a dynamic device that can be any size of terminal besides the usual models: 2, 3, 4, and 5. However, when I try to use a dynamic device and ask for a 43x100 screen size, I got an error message that the server doesn't support the requested device type. Before I contact Seagull, what should z/VM 4.4's TCP/IP stack and CP's LDEV support provide for this? Is 43x100 ever a supported screen size for a tn3270 session? Does tn3270e somehow make this possible if I hit the right combination of settings? Will Julie leave Fred for Bill even though she's carrying John's baby? Signed, Befuddled Deviant in Gaithersburg
Re: Odd sizes for tn3270 sessions
Never mind; if I don't say dynamic device but still say, 43x100, please?, I get 43x100. Nick I wrote: My tn3270 client (Seagull Software's Bluezone tn3270 client) offers me a chance to have a dynamic device that can be any size of terminal besides the usual models: 2, 3, 4, and 5. However, when I try to use a dynamic device and ask for a 43x100 screen size, I got an error message that the server doesn't support the requested device type. Before I contact Seagull, what should z/VM 4.4's TCP/IP stack and CP's LDEV support provide for this? Is 43x100 ever a supported screen size for a tn3270 session? Does tn3270e somehow make this possible if I hit the right combination of settings? Signed, Befuddled Deviant in Gaithersburg
Re: Odd sizes for tn3270 sessions
I sometimes use odd screen-sizes from PCOMM over TELNET into VM. No problem whatsoever. VM supposrt this for ages (since the arrival of the 3290 gaspanel I think). The PCOMM GUI does not allow to enter odd values, but if you edit the .WS file you enter whatever. Kris, IBM Belgium, VM customer support The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 10/10/2006 16:59:58: My tn3270 client (Seagull Software's Bluezone tn3270 client) offers me a chance to have a dynamic device that can be any size of terminal besides the usual models: 2, 3, 4, and 5. However, when I try to use a dynamic device and ask for a 43x100 screen size, I got an error message that the server doesn't support the requested device type. Before I contact Seagull, what should z/VM 4.4's TCP/IP stack and CP's LDEV support provide for this? Is 43x100 ever a supported screen size for a tn3270 session? Does tn3270e somehow make this possible if I hit the right combination of settings? Will Julie leave Fred for Bill even though she's carrying John's baby? Signed, Befuddled Deviant in Gaithersburg
Re: Odd sizes for tn3270 sessions
Just made a test
166x280 was refused ('not allowed over the current connection
66x180 was OK for TELNET but XEDIT and CP where confused
66x100 is perfect (except for my old eyes)
66x200 works too
So, there are some limits but there is great freedom
Re: Odd sizes for tn3270 sessions
Hummingbird allows custom settings of:
Rows (20 - 72)
Columns (80 - 200)
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Kris Buelens
Sent: Tuesday, October 10, 2006 11:51 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Odd sizes for tn3270 sessions
Just made a test
166x280 was refused ('not allowed over the current connection 66x180
was OK for TELNET but XEDIT and CP where confused 66x100 is perfect
(except for my old eyes) 66x200 works too So, there are some limits but
there is great freedom
If you are not an intended recipient of this e-mail, please notify the sender,
delete it and do not read, act upon, print, disclose, copy, retain or
redistribute it. Click here for important additional terms relating to this
e-mail. http://www.ml.com/email_terms/
