Re: Max size 3270 screen

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 appa

Re: Max size 3270 screen

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 simp

Re: Max size 3270 screen

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! ;-) Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions o

Re: Max size 3270 screen

Bingo! Even though I though I had checked TCPIP's 191 disk for a file, perhaps it was still open when I checked. The messages appeared near the bottom of the file on TCPIP's 191 disk: "TCPIPTRACDATA A". Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not

Re: Max size 3270 screen

I started this thread and I would contact the support center except that I am on z/VM 3.1 which is not long supported. /Fran --- On Fri, 23 Feb 2007 17:10:17 -0500 William Moy said: >Turns out these message are not behind a trace poin

Re: Max size 3270 screen

OK, Chuckie -- what have you done with Alan this time!? Obviously that trace message was a perfectly adequate typical self-documenting message. ;-) How about an even more useful message: DTCOCPxxxI Conn 2: Client 10.11.12.13 screen dimensions (66 x 160) too large for DATABUFFERSIZE (8192).

Re: Max size 3270 screen

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

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] * (personal)

Re: Max size 3270 screen

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

Re: Max size 3270 screen

Bill, That would be a good help (more later in a reply to Alan's post), but did not work. I got two files back in TCPMAINT reader: FILE: TCPIPMESSAGE A1 Hewitt Associates DTCUTI002E OBEY TRACE TELNET issued by TCPMAINT; return code 0 and FILE: TCPIPMESSAGE A1 Hewitt Associates

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 8192, > CharsScanned 2048, hbound(...) 8192. Killing c

Re: Max size 3270 screen

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. __

Re: Max size 3270 screen

Hi Mike, Well, you could do the following: Enable tracing of Telnet (for example: NETSTAT OBEY TRACE TELNET), Connect to the z/VM Telnet server and cause the disconnect, Get the TCPIP stack console (for example: NETSTAT CP SP CONS CLOSE) The resultant TCP/IP console shoul

Re: FCP SCSI support on z/VM in basic mode

Hi Don, What you have looks fine, though I have a few minor points to offer: - Newer IBM DASD contains an Access Control List that identifies which HOST WWPNs (associated with the FCP CHPID) can access which LUNs within the box, so you won't always be able to get to every LUN in the box as you

Re: Max size 3270 screen

Same 8K buffer here -- but since it is Friday I'll wait for our weekly Sunday evening IPL. Thanks! Next question: why don't we see any sort of error on the TCPIP console when the session is forcibly disconnected due the large screen size/buffer size disparity? Thus sort of thing gets REALLY h

Re: Max size 3270 screen

The 3290 was 160X62. Very cool for viewing listings! Stephen Frazier wrote: My recollection is that the largest 3270 like terminal that IBM ever made was 160x47. I never had one so I don't know exactly. I do remember 160 was the width. I don't remember the rows but I think it was 46 or 47. Bu

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 - On Fri, 23 Feb 2007 14:02:21 -0500 William Moy

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 . 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 HostExpl

Re: FCP SCSI support on z/VM in basic mode

I think I'm beginning to understand the use of a SCSI formatted SHARK. If I'm correct, the devices defined in the IOCP for the FCP chpids are actua lly just communications paths to the SHARK. Any address defined on the chpid can access any LUN on the SHARK. I think my steps would be: 1) Attach

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 PF3 in peek, at which time my terminal session went away. -- .~.Robert P. Nix Mayo Foundation /V\RO-

Re: Max size 3270 screen

And chiming in with results from a 62x160 TN3270E terminal using "IBM Personal Communications WorkStation Version 5.8 for Windows" with similar results. It enters PEEK (even on short, narrow files) without problems, PF3 or QUIT causes a disconnect. Trying from an SNA connection, goes into PEE

Re: Max size 3270 screen

My recollection is that the largest 3270 like terminal that IBM ever made was 160x47. I never had one so I don't know exactly. I do remember 160 was the width. I don't remember the rows but I think it was 46 or 47. But, it may have been 49. MVS and VM needed a PTF to support it. It sounds like s

Re: Max size 3270 screen

The IBM z/VM Operating System 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 . > > I have played with some smaller sizes but they di

Re: Max size 3270 screen

I have also noticed a problem with disconnects while using "Mod 5" sessions on my z/VM 5.2. I was waiting until I resolved more pressing matters before addressing the issue. I also thought it was my emulator. From: The IBM z/VM Operating System [mailto:[EMAIL PROT

Re: Max size 3270 screen

Same thing happens with z/VM 5.2 and HostExplorer 10. 49 x 160 works on my system. At a width of 160, rows of 50 or more, have the disconnect problem. I know this doesn't answer your question. But it seems to indicate that there is not a fix in the more recent z/VM and HostExplorer(?). -Orig