Re: TCPIP PCOMM 658 Code
I thought I'd do a follow up on this problem for anyone who might be interested and who may have a similar setupto the onewe do. I was fairly confident that VM:Operator wasn't to blame for the problem but contactedCA anyway since the only error codes we ever got were from VM:Operator. AfterCA andIdiscounted him as the culprit I decided to focus on TCPIP as I always thought he was to blame. After reading through both the Planning and Configuration manual and the User's Guide I zeroed in on the POOLSIZE part of the PROFILE TCPIP. After issuing the NETSTAT POOLSIZE command I noticed that the system was trying to useSmallDataBufferwhich we had set to zero in the #Alloc column. I say the system was trying to use it only because there was a "1" in the Permit Size column. This was without anyone being logged on via TELNET. At any rate, setting the #Alloc to 10 on my test system seems to have fixed the problem. Logging on multiple users via TELNET and issuing NETSTAT POOLSIZE shows that the numbers in all the other columns do indeed change depending on the number of remote logons I have. For any production machines the #Alloc will be set to 100 as they have many more users. This was never a problem on our 43XX or 9221 systems nor our PC Server based P/390s but for some reason, the Integrated Servers we have are a rather sensitive lot. Either that or PCOMM is more sensitive than Communications Manager/2 but my money is still on TCPIP. One day I hope to be able to work on more modernsystems but for now I'm stuck trying to support unsupported hardware and software.Karl SeversonRaytheon CompanyEl Segundo, California
Re: TCPIP PCOMM 658 Code
That's okay. I'll be checking with Computer Associates tomorrow since the error message I was getting was from VM:Operator. I checked to make sure we were running the most recent version of VM:Manager and Operator and we appear to be. Somehow though I think it's a TCPIP problem but I don't really care as long as I can fix it. Karl SeversonRaytheon CompanyEl Segundo, California-The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote: -To: IBMVM@LISTSERV.UARK.EDUFrom: Alan Altmark [EMAIL PROTECTED]Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDUDate: 07/21/2008 10:19PMSubject: Re: TCPIP PCOMM 658 CodeSorry, I can't help you. Others here are far more familiar with the day-to-day operation of the Integrated Server.Alan Altmarkz/VM DevelopmentIBM Endicott
TCPIP PCOMM 658 Code
I was happy to see that others are using PCOMM so perhaps someone will be able to figure out my plight. I use the OS/2 flavor (4.21) and promptly each Saturday, my console and any other open sessions running VM go blank and there is a 658 code on the bottom of the frame of each open session. I don't think that there is anything special about Saturdays. No one is even working. I believe it has something to do with having to reboot the system every Monday to get the sessions back. So, something "fills up" or breaks 6 daysafter rebooting OS/2 and VM. When I was finally able to find out what a 658 code meant, it said that it was the session(s) attempting to initializethe TCPIP connection to the hardware management console. This makes sense as while VM is booting I notice that the sessions beep and display the VM logo around the same time as TCPIP is brought up. The actual error that I get is VMYIOD041T Permanent I/O error on console, SCSW=0009. This problem plagues all four of my IBM servers which are, obviously, all configured exactly alike. Thanks in advance for any insight anyone may have. Karl Severson IBM System Administrator Raytheon Company El Segundo, California
Re: TCPIP PCOMM 658 Code
Since when does a mainframe 'boot'? On VM, CP does an IPL. Phil Parmelee IBM Global Services VM/VSE Team Harrisburg, PA 717-526-1250 T/L 239-1250 [EMAIL PROTECTED]
Re: TCPIP PCOMM 658 Code
On Mon, Jul 21, 2008 at 2:35 PM, in message [EMAIL PROTECTED], Phillip Parmelee [EMAIL PROTECTED] wrote: Since when does a mainframe 'boot'? On VM, CP does an IPL. Since at least 1999, and probably before, in the IBM lab in Boeblingen. Some reason you feel the need to be so picky about terminology, when both terms are commonly used to mean the same thing? Mark Post
Re: TCPIP PCOMM 658 Code
On Monday, 07/21/2008 at 02:14 EDT, Karl J Severson [EMAIL PROTECTED] wrote: I was happy to see that others are using PCOMM so perhaps someone will be able to figure out my plight. I use the OS/2 flavor (4.21) and promptly each Saturday, my console and any other open sessions running VM go blank and there is a 658 code on the bottom of the frame of each open session. I don't think that there is anything special about Saturdays. No one is even working. I believe it has something to do with having to reboot the system every Monday to get the sessions back. So, something fills up or breaks 6 days after rebooting OS/2 and VM. When I was finally able to find out what a 658 code meant, it said that it was the session(s) attempting to initialize the TCPIP connection to the hardware management console. This makes sense as while VM is booting I notice that the sessions beep and display the VM logo around the same time as TCPIP is brought up. The actual error that I get is VMYIOD041T Permanent I/O error on console, SCSW=0009. This problem plagues all four of my IBM servers which are, obviously, all configured exactly alike. Thanks in advance for any insight anyone may have. I would guess that every weekend a firewall is rebooted. I don't understand about reboot the system every Monday to get the sessions back. Reboot what system? PCOMM will only try to reconnect if it receives a disconnect. And that will only happen (assuming you don't shutdown TCPIP on VM) if something between your workstation and VM causes it to happen. Alan Altmark z/VM Development IBM Endicott
Re: TCPIP PCOMM 658 Code
Perhaps we also need to rename the bootstrap record to the IPL record? -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Monday, July 21, 2008 2:44 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TCPIP PCOMM 658 Code On Mon, Jul 21, 2008 at 2:35 PM, in message [EMAIL PROTECTED], Phillip Parmelee [EMAIL PROTECTED] wrote: Since when does a mainframe 'boot'? On VM, CP does an IPL. Since at least 1999, and probably before, in the IBM lab in Boeblingen. Some reason you feel the need to be so picky about terminology, when both terms are commonly used to mean the same thing? Mark Post
Re: TCPIP PCOMM 658 Code
WHen you have to explain the procedure to management that doesn't underst and an 'Initial Program Load' and doesn't know that we once had to toggle in a 'bootstrap' program into the Play Computers of decades ago. /Tom Kern On Mon, 21 Jul 2008 14:35:25 -0400, Phillip Parmelee [EMAIL PROTECTED] wrote: Since when does a mainframe 'boot'? On VM, CP does an IPL. Phil Parmelee IBM Global Services VM/VSE Team Harrisburg, PA 717-526-1250 T/L 239-1250 [EMAIL PROTECTED]
Re: TCPIP PCOMM 658 Code
-The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote: -To: IBMVM@LISTSERV.UARK.EDUFrom: Alan Altmark [EMAIL PROTECTED]Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDUDate: 07/21/2008 11:45AMSubject: Re: TCPIP PCOMM 658 CodeI would guess that every weekend a firewall is rebooted. I don't understand about "reboot the system every Monday to get the sessions back". Reboot what system?PCOMM will only try to reconnect if it receives a disconnect. And that will only happen (assuming you don't shutdown TCPIP on VM) if something between your workstation and VM causes it to happen.Alan Altmarkz/VM DevelopmentIBM EndicottI guess I should have mentioned what servers I have. I have four 3006 Integrated Servers (P/390s) which run OS/2 and VM. By sessions I mean the PCOMM 3270 console screens which display VM:Operator and which can be used to log on to other VM accounts. The icons on the desktop call them Local P/390 Sessions or P/390 WS. By rebooting the system I mean that on each 3006 I have to end the P/390 session which crashes VM as I have no console to shut VM down nicely. I then start the P/390 software which brings up VM and all of the PCOMM 3270 sessions. I guess you'd have to be familiar with the P/390 to be able to picture what I'm describing but hopefully I'm giving you enough information to do so. As far as a firewall is concerned, this happens even if the system isn't hooked up to a network.Karl Severson - Raytheon Company
Re: TCPIP PCOMM 658 Code
On Monday, 07/21/2008 at 10:16 EDT, Karl J Severson [EMAIL PROTECTED] wrote: I guess I should have mentioned what servers I have. I have four 3006 Integrated Servers (P/390s) which run OS/2 and VM. By sessions I mean the PCOMM 3270 console screens which display VM:Operator and which can be used to log on to other VM accounts. The icons on the desktop call them Local P/390 Sessions or P/390 WS. By rebooting the system I mean that on each 3006 I have to end the P/390 session which crashes VM as I have no console to shut VM down nicely. I then start the P/390 software which brings up VM and all of the PCOMM 3270 sessions. I guess you'd have to be familiar with the P/390 to be able to picture what I'm describing but hopefully I'm giving you enough information to do so. As far as a firewall is concerned, this happens even if the system isn't hooked up to a network. Sorry, I can't help you. Others here are far more familiar with the day-to-day operation of the Integrated Server. Alan Altmark z/VM Development IBM Endicott
TCPIP PCOMM 658 Code
I was happy to see that others are using PCOMM so perhaps someone will be able to figure out my plight. I use the OS/2 flavor (4.21) and promptly each Saturday, my console and any other open sessions running VM go blank and there is a 658 code on the bottom of the frame of each open session. I don't think that there is anything special about Saturdays. No one is even working. I believe it has something to do with having to reboot the system every Monday to get the sessions back. So, something "fills up" or breaks 6 daysafter rebooting OS/2 and VM. When I was finally able to find out what a 658 code meant, it said that it was the session(s) attempting to initializethe TCPIP connection to the hardware management console. This makes sense as while VM is booting I notice that the sessions beep and display the VM logo around the same time as TCPIP is brought up. The actual error that I get is VMYIOD041T Permanent I/O error on console, SCSW=0009. This problem plagues all four of my IBM servers which are, obviously, all configured exactly alike. Thanks in advance for any insight anyone may have.Karl SeversonIBM System AdministratorRaytheon CompanyEl Segundo, California
