I have a fix for the problem, but it forces a max of 64 lines (it works on
larger screens, but only *uses* 64 lines). A better fix requires reassembling
all of SHOW; I haven't been able to get to that yet.
So sit tight...
...phsiii
Phil's fix has been applied to SHOW VMARC on my download site:
http://zvm.sru.edu/~download
/Fran Hensler at Slippery Rock University of Pennsylvania USA for 43 years
[EMAIL PROTECTED] +1.724.738.2153
Yes, Virginia, there is a Slippery Rock
On Sat, 3 Mar 2007 08:53:39
I am home now, but I know I have source at work,
because I have local mods.
Would you like me to send it?
While on the topic of maintenance to SHOW,
what are the chances of adding support for VMARC
archives (I mean, who uses Cornell CARD today??) :-)
Shimon
Fran Hensler [EMAIL PROTECTED]
Shimon -
Phil Smith might be working on the problem.
I have source on my VM website:
http://zvm.sru.edu/~download
/Fran
On Fri, 2 Mar 2007 13:39:41 +0200 Shimon Lebowitz said:
I am home now, but I know I have source at
I've made 2 or 3 attempts over the years, but none were successful.
I'm unaware of any fix for that problem, but would like to be surprised!
cheers, wayne
Fran Hensler wrote:
After raising my TCPIP DATABUFFERPOOLSIZE to 12K and enjoying my big screens
I have found that SHOW will not work on
:02 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Max size 3270 screen SHOW
After raising my TCPIP DATABUFFERPOOLSIZE to 12K and enjoying my big
screens
I have found that SHOW will not work on a screen with more than 66
lines. I get:
DMSABE141T Addressing exception occurred at 808D6B6C
[EMAIL PROTECTED]
ext. 40441
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
On
Behalf Of Fran Hensler
Sent: Thursday, March 01, 2007 7:02 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Max size 3270 screen SHOW
After raising my TCPIP DATABUFFERPOOLSIZE
After raising my TCPIP DATABUFFERPOOLSIZE to 12K and enjoying my big screens
I have found that SHOW will not work on a screen with more than 66
lines. I get:
DMSABE141T Addressing exception occurred at 808D6B6C in routine SHOW
on a 67 x 81 screen.
Does anyone have a fix for this?
/Fran
List members determined that my problem with being disconnected when using
a 60 x 160 size 3270 screen was that my DATABUFFERPOOLSIZE was too small.
My PROFILE TCPIP had a DATABUFFERPOOLSIZE of 8K so I thought that 9K
would work but it didn't. I found a message in the TCPIP console log
that my
What is the maximum size a VM 3270 screen can be?
I like 66 x 160 and it works for most things in HostExplorer.
But it disconnects me when I use PEEK or NAMES when I hit Enter.
I have played with some smaller sizes but they disconnect too.
I'm running z/VM 3.1.
Is this a problem with z/VM or
or policies of Hewitt Associates.
Tim Joyce [EMAIL PROTECTED]
Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
02/23/2007 12:52 PM
Please respond to
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: Max size 3270 screen
I have also
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 02/23/2007
12:50:07 PM:
What is the maximum size a VM 3270 screen can be?
I like 66 x 160 and it works for most things in HostExplorer.
But it disconnects me when I use PEEK or NAMES when I hit Enter.
I have played with some
PROTECTED] On
Behalf Of RPN01
Sent: Friday, February 23, 2007 1:44 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Max size 3270 screen
I was able to duplicate the problem on zVM 5.2 and x3270 on Mac OSX, so
the problem is probably not in the terminal emulator.
49x160 worked, but 52x160 worked until I hit
(?).
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Fran Hensler
Sent: Friday, February 23, 2007 10:50 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Max size 3270 screen
What is the maximum size a VM 3270 screen can be?
I like 66 x 160 and it works for most
, 2007 10:50 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Max size 3270 screen
What is the maximum size a VM 3270 screen can be?
I like 66 x 160 and it works for most things in HostExplorer.
But it disconnects me when I use PEEK or NAMES when I hit Enter.
I have played with some smaller sizes
Operating System IBMVM@LISTSERV.UARK.EDU
02/23/2007 01:18 PM
Please respond to
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: Max size 3270 screen
Bill -
You guessed right, my DATABUFFERSIZE is 8K.
I won't be able to recycle TCP/IP until
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: Max size 3270 screen
Bill -
You guessed right, my DATABUFFERSIZE is 8K.
I won't be able to recycle TCP/IP until tomorrow.
I'll jack up the size and let you know the results.
Thanks for all the replies.
/Fran
Sufficient information, but if you have to kill a connection due to
resource exhaustion, probably the message should be displayed in the
console log without having to turn on tracing to see it. This is the
sort of thing that one would want to catch with automation, eg PROP,
etc.
On Friday, 02/23/2007 at 03:37 EST, William Moy/Endicott/[EMAIL PROTECTED]
wrote:
The resultant TCP/IP console should have in it msgs similar to the
following:
15:20:49 DTCOCP032I Conn 2: Transparent-mode data overruns buffer.
ToCpPos 8192,
CharsScanned 2048, hbound(...) 8192. Killing
by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
02/23/2007 02:37 PM
Please respond to
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: Max size 3270 screen
Hi Mike,
Well, you could do the following:
Enable tracing of Telnet
Mike -
I just discovered that I have TELNET tracing on all of the time.
I found the offending message after I did a NETSTAT CP CLOSE CONSOLE.
/Fran Hensler at Slippery Rock University of Pennsylvania USA for 43 years
[EMAIL PROTECTED] +1.724.738.2153
Yes, Virginia, there
]
Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
02/23/2007 02:37 PM
Please respond to
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: Max size 3270 screen
Hi Mike,
Well, you could do the following:
Enable tracing of Telnet
Turns out these message are not behind a trace point and are not
documented. Someone should please contact the IBM Support Center to get it
fixed with better messages. Thanks!
Best Regards,
Bill Moy
z/VM Development
@LISTSERV.UARK.EDU
cc
Subject
Re: Max size 3270 screen
On Friday, 02/23/2007 at 03:37 EST, William Moy/Endicott/[EMAIL PROTECTED]
wrote:
The resultant TCP/IP console should have in it msgs similar to the
following:
15:20:49 DTCOCP032I Conn 2: Transparent-mode data overruns buffer.
ToCpPos
Subject
Re: Max size 3270 screen
And do you have TRACE FILE... in your tcpip profile? Did you look on
tcpip's a-disk?
Mike Harding
EDS VM National Capability
134 El Portal Place
Clayton, Ca. USA 94517-1742
* phone: +01-925-672-4403
* Fax: +01-925-672-4403
* mailto:[EMAIL PROTECTED
On Friday, 02/23/2007 at 04:17 CST, Mike Walter [EMAIL PROTECTED]
wrote:
I'm on z/VM 5.1 and 5.2, and will open a PMR in Monday - after other
potential list members chime in with more ideas. Probably too late to
ship in z/VM 5.3, though! ;-)
If it were too late (it isn't), we would simply
Aria Bamdad sent me an email suggesting that since tracing is CPU
intensive I should turn it off. I went into PROFILE TCPIP and found
that I have: NOTRACE ALL
But every telnet connection appears in the console for TCPIP.
It also had the message about the DATABUFFERSIZE being too small.
So
27 matches
Mail list logo
