Dear Chuckie, I must apologize for upsetting you so. It too was shocked, as in shocked and awe which escalated to shock and ah, S**T!!! What was I thinking? Upon encountering a problem when using the PEEK function from within a RDRLIST display, I should have immediately thought of my TCP/IP buffer specifications. The shame of it all. I promise to go out this weekend to my local bookstore and buy a copy of the "z/VM for Dummies" book, where upon I am sure I will find in the index: Problems with PROFPEEK XEDIT; see also TCPIP buffer definitions. I will also spend considerable time over the weekend pondering why, when I have my own private copy of PROFPEEK XEDIT on my 191 A-Disk, everything worked without giving any thought to TCPIP buffers. But, this will be an exercise left to the totally confused.
Now I have to go and close my PMR with those kind folks at IBM who went to the trouble to duplicate my problem and reported back to me to go change my TCPIP buffer definitions. I am off to modify my TCPIP buffer specifications. Now let's see, that's MegaDataBuffer, VeryLargeDataBuffer, LargeDataBuffer, StandardDataBuffer, DataBuffer, SmallDataBuffer, TinyDataBuffer and finally NanoDataBuffer. (did I miss any?? :-)) Oh, yes, I missed one - DataBufferForUsersWithLargeScreenDefintions. There, got them all. I would like to thank all of you who responded. I was really surprised at how the majority of you made the leap from using PEEK to TCPIP data buffers. HITACHI DATA SYSTEMS Raymond E. Noal Senior Technical Engineer Office: (408) 970 - 7978 -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Thursday, April 02, 2009 10:59 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Problem with PEEK Command - update On Thursday, 04/02/2009 at 08:19 EDT, Raymond Noal <raymond.n...@hds.com> wrote: > Upon further investigation I have found that the problem with the PEEK command > is associated with the user?s terminal screen size. I was using a terminal > emulation screen sizeof 62X 160.If I change the terminal characteristics to 43 > X 80, the problem does not occur. Please check your TCPIP console. You are probably getting a warning about "transparent mode buffer overrun". The default data buffer size is 8K -- not large enough to hold the 9K+ bytes of a 62x160 screen. Use the statement: DataBufferPoolSize 160 12K to increase it. Also make you you have defined TinyDataBuffers and SmallDataBuffers, too. Otherwise the stack will waste a lot of memory on short transactions. (And you may need a larger TCPIP server to handle the additional memory. Keep an eye on the console for a week or so.) I am shocked, shocked I say, that you overlooked the z/VM 5.4 update to the description of the DataBufferPoolSize statement in the TCP/IP Planning book that says "For Telnet connections, the size of regular data buffers may need to be increased in order to accommodate clients that use large screen sizes." ;-) Alan Altmark z/VM Development IBM Endicott
