Re: FLEX-ES and z/VM 4 or z/VM 5
You guys put out some really good points there. We are a midsize company (growing fast!) and we put in a z800, running z/ VM as a hypervisor for Linux, and are porting the business apps over to it. Naturally, we could not do it the way everyone else does it... so it is taking longer than we would like, but the results - ah... they are fantas tic. But the fact that we can do this- and that we do not have to pay signifig ant monthly license costs to IBM, while good for us, is a killer for IBM's ca sh flow. They have not yet learned how to deal with customers our size. For example - when we bought the z, we purchased it on a TSO plan, and paid cash for the Z, Shark, tapes and the whole bundle. We still get thr ee or four invoices per month for it. The money and effort IBM wastes sendin g those out, not to mention the time and effort expended to correct the errors, is astronomical. They could afford it if we were sending them $130K/month in license fees, but ... IBM has to learn how to deal, profitably, with the thousands of companies our size and slightly smaller. They are always shooting themselves in the ir own foot. Another example, when we first contacted IBM about buying a new computer, I told our sales rep we were interested in a mainframe or a pSeries machine , knowing the entire time we wanted a mainframe. They showed up and told us we were too small for a mainframe. grin The truth was they could not find the proper people to sell us the mainframe, and the sales rep they first set us up with was unwilling to do the work to get a proper order placed. He felt that we should simply take whatever he said, at whatever he said the cost was going to be. He also did not think we had any idea what we were talking about using Linux. You don't want to know the stories about the printing people or what the printing people did -- I do believe they wound up disbanding the entire group... (*sigh*) On the other hand, individuals within IBM are some of the greatest people I have ever met. Most of them are truely out there to do the job, and a lot of them are interested in interesting things. What better group of people is there on the planet? I think they are nervous to no end about Hercules, to be honest. I do not think they beleived it could happen, and yet, it has. How can they protec t their revenue source? Restrictive license policies does work, but it als o has the capability of backfiring - people will move more and more to Linu x. And while Linux does not have the same VM capabilities in it as zVM does, that could also change. IBM's greatest nightmare would be people buying j ust zSeries hardware with no software at all. And there is a real possibility that could happen if they don't change their course a bit. And oh yeah, don't forget about the group inside IBM who is still convinc ed that the Mainframe is DEAD, and can be easily replaced with a coulpe pSer ies boxes. Of course that isn't so, but they are loud, vocal, and have just enough truth in their statements to make people listen. -Paul
Online Tutorial
I have just finished installing zVM for a company to run zLinux but they have no zVM experience at all and although they don't expect to do any zVM work they're still going to need some knowledge. I had previously done this for someone else and they used the following link which provided enough for them: http://www.vm.ibm.com/tutorial/ However it seems that this no longer exists. Is there anywhere else on the web with such information that I can pass on to them? Thanks, Seb
Re: performance question
Title: performance question Can anybody tell me how to get reports from PERFKIT that start at 00:01:00 and go to 23:59:00 ? I have tried everything I can find and all my reports start at 12:01:00 and end at 23:59:00. What am I missing? The times when counters should be reset in PerfKit are defined by arguments of the command 'FC MONCOLL RESET ...'. Entering the command without further arguments will tell you what your current settings are, and my guess is you have defined a reset at noon. Note that each automated 'print' request (i.e. P-suffix after the time) will automatically reset the corresponding counters, i.e. it will become the start of a new reporting period unless it is superseded by a later explicit 'hh:mm:ssR_P' reset specification. For automatic resetting at 00:01 and printing of reports at 23:59 you'd need just the statement 'FC MONCOLL RESET 00:01:00R_P 23:59:00P' Eginhard Jaeger
VSWITCH Controller failover issue on z/VM 5.2
This weekend the LAN team upgraded the CISCO router connected to the OSA card. The VSWITCH controller console shows the message: DTCOSD309W Received adapter-initiated Stop Lan after which it tries to fail over from the primary OSA to the backup OSA. Eventually I see: DTCOSD306I Received adapter-initiated Start Lan and the backup OSA addresses get started fine and assign all the IP addresses. There are several more iterations of Stop Lan and Start Lan, but it is always on the backup OSA addresses, never on the primary OSA addresses. So the question is: why didn't it ever try to restart on the primary OSA when the backup OSA received the Stop Lan? If both OSA cards were the same it might not matter that much, but the primary is a Gig-OSA and the backup is a Fast-OSA. - Oh, and just to make it more fun, lastly there is a Stop Lan, the various normal messages about stopping, attempting to restart, and: AMPX036I ASSERTION FAILURE CHECKING ERROR TRACE BACK OF CALLED ROUTINES ROUTINE STMT AT ADDRESS IN MODULE SPSM_BLKALLOCATE 3900D429D0 TCFPSM_FPSM INITDCB4800DA079A TCTOOSD_TOOSD TOOSDINIT 3300DA2DF4 TCTOOSD_TOOSD CALLINITRTN3000CB9506 TCPARSE_PARSETCP PROCESSSTARTSTOPSTATEMENT 3300CAE37E TCPARSE_PARSETCP PARSEOPTION 29200CB3C00 TCPARSE_PARSETCP RECEIVECONTROLLERMSGFROMCP 2500D9F010 TCTOOSD_TOOSD TOIUCV18000D3D580 TCTOIUC_TOIUCV Schedule 167000CFA118 MAIN-PROGRAM 1400C441FE TCPIP VSPASCAL 00E4D74A DTCOSD100E Insufficient Fixed Page Storage Pool storage after which it tries to shutdown and then goes into repeated: AMPX015I ADDRESSING EXCEPTION abends. Needless to say there were a lot of dump files in spool space. So, IBM will get a call on the abends. I could add more virtual storage to the controllers, but that will presumably only add cushion for more stops restarts before it runs out of storage again. Brian Nielsen
Re: VSWITCH Controller failover issue on z/VM 5.2
after the successful fail over from primary to backup RDEVs for the OSAs, what state was reported for the primary RDEVs? David -Original Message- From: The IBM z/VM Operating System on behalf of Brian Nielsen Sent: Mon 4/24/2006 1:39 PM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] VSWITCH Controller failover issue on z/VM 5.2 This weekend the LAN team upgraded the CISCO router connected to the OSA = card. The VSWITCH controller console shows the message: DTCOSD309W Received adapter-initiated Stop Lan after which it tries to fail over from the primary OSA to the backup OSA.= Eventually I see: DTCOSD306I Received adapter-initiated Start Lan and the backup OSA addresses get started fine and assign all the IP addresses. There are several more iterations of Stop Lan and Start Lan, but it is = always on the backup OSA addresses, never on the primary OSA addresses. So the question is: why didn't it ever try to restart on the primary OSA = when the backup OSA received the Stop Lan? If both OSA cards were the = same it might not matter that much, but the primary is a Gig-OSA and the = backup is a Fast-OSA. - Oh, and just to make it more fun, lastly there is a Stop Lan, the various= normal messages about stopping, attempting to restart, and: AMPX036I ASSERTION FAILURE CHECKING ERROR TRACE BACK OF CALLED ROUTINES ROUTINE STMT AT ADDRESS IN MODULE SPSM_BLKALLOCATE 3900D429D0 TCFPSM_FPSM INITDCB4800DA079A TCTOOSD_TOOSD TOOSDINIT 3300DA2DF4 TCTOOSD_TOOSD CALLINITRTN3000CB9506 TCPARSE_PARSETCP PROCESSSTARTSTOPSTATEMENT 3300CAE37E TCPARSE_PARSETCP PARSEOPTION 29200CB3C00 TCPARSE_PARSETCP RECEIVECONTROLLERMSGFROMCP 2500D9F010 TCTOOSD_TOOSD TOIUCV18000D3D580 TCTOIUC_TOIUCV Schedule 167000CFA118 MAIN-PROGRAM 1400C441FE TCPIP VSPASCAL 00E4D74A DTCOSD100E Insufficient Fixed Page Storage Pool storage after which it tries to shutdown and then goes into repeated: AMPX015I ADDRESSING EXCEPTION abends. Needless to say there were a lot of dump files in spool space. So, IBM will get a call on the abends. I could add more virtual storage = to the controllers, but that will presumably only add cushion for more = stops restarts before it runs out of storage again. Brian Nielsen
Re: VSWITCH Controller failover issue on z/VM 5.2
On Monday, 04/24/2006 at 12:39 EST, Brian Nielsen [EMAIL PROTECTED] wrote: There are several more iterations of Stop Lan and Start Lan, but it is always on the backup OSA addresses, never on the primary OSA addresses. So the question is: why didn't it ever try to restart on the primary OSA when the backup OSA received the Stop Lan? If both OSA cards were the same it might not matter that much, but the primary is a Gig-OSA and the backup is a Fast-OSA. There is no permanent association of primary and backup in the VSWITCH. There is just a list of available OSAs. The VSWITCH starts with the first one and fails over until it finds a working one. Whichever one is active is the primary. The others are backups. (You can see that in QUERY VSWITCH.) So, I'm not 100% sure I'm reading your post correctly, but I would have expected identical behavior vis a vis the decision to fail over, without regard to which OSA was active and which were backups. A StopLAN on the currently active OSA should have caused a failover. If none of the backups worked (i.e. all OSAs unplugged at the same time), I would have expected CP to come back to the OSA that is currently 'active' and sit and wait for StartLAN on the active OSA or one of the backups. At that point, whichever one comes up first would become the active OSA. Of course, with the abend in the controller, bizzare things were obviously going on. The Support Center definitely needs to look at it. FWIW, if you want it to go back to the first OSA in the list, set up some system automation to do a SET VSWITCH DISCONNECT followed by a SET VSWITCH CONNECT when you get an adapter-initiated StartLAN on the desired device (as seen on the controller's console). CP will go back to the beginning of the OSA list and start looking for a working device. Alan Altmark z/VM Development IBM Endicott
Re: GCCCMS for zVM
I have an interest in this because there is no budget for additional software for z/VM or Linux. I tried a version of your GCCCMS from the VM/370 group on my z/VM 5.1 system on a z890 IFL and it worked fine. A thought for future development would be to fix the runtime library to use CMS native processes and maybe some CP/CMS interface routines (DIAG 8 type things). Thanks for all your hard work. /Tom Kern --- Dave Wade [EMAIL PROTECTED] wrote: Thanks to the kind loan of access to a zVM system from Dave Jones @ V-Soft Software I now have a GCC323 that runs on VM, and generates traditional 370 assembler. There is also a minimal run time library so that CMS modules can be produced. Due to some of the MVS macros used it still uses the code runs RMODE 24/AMODE 31, but I am looking to fix this in the medium term. Is this likely to be of interest to any one, as I guess that most of you have IBMs C Compiler. If it is what would be the best way to package it. I assume a VMARC file would fine with most folks. Any other thoughts on this? Dave. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: VSWITCH Controller failover issue on z/VM 5.2
The primaries were listed as BACKUP. Brian Nielsen On Mon, 24 Apr 2006 14:21:11 -0400, David Kreuter [EMAIL PROTECTED] resources.com wrote: after the successful fail over from primary to backup RDEVs for the OSAs , what state was reported for the primary RDEVs? David -Original Message- From: The IBM z/VM Operating System on behalf of Brian Nielsen Sent: Mon 4/24/2006 1:39 PM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] VSWITCH Controller failover issue on z/VM 5.2 This weekend the LAN team upgraded the CISCO router connected to the OSA = card. The VSWITCH controller console shows the message: DTCOSD309W Received adapter-initiated Stop Lan after which it tries to fail over from the primary OSA to the backup OSA .= Eventually I see: DTCOSD306I Received adapter-initiated Start Lan and the backup OSA addresses get started fine and assign all the IP addresses. There are several more iterations of Stop Lan and Start Lan, but it is = always on the backup OSA addresses, never on the primary OSA addresses. So the question is: why didn't it ever try to restart on the primary OSA = when the backup OSA received the Stop Lan? If both OSA cards were the = same it might not matter that much, but the primary is a Gig-OSA and the = backup is a Fast-OSA. - Oh, and just to make it more fun, lastly there is a Stop Lan, the variou s= normal messages about stopping, attempting to restart, and: AMPX036I ASSERTION FAILURE CHECKING ERROR TRACE BACK OF CALLED ROUTINES ROUTINE STMT AT ADDRESS IN MODULE SPSM_BLKALLOCATE 3900D429D0 TCFPSM_FPSM INITDCB4800DA079A TCTOOSD_TOOSD TOOSDINIT 3300DA2DF4 TCTOOSD_TOOSD CALLINITRTN3000CB9506 TCPARSE_PARSETCP PROCESSSTARTSTOPSTATEMENT 3300CAE37E TCPARSE_PARSETCP PARSEOPTION 29200CB3C00 TCPARSE_PARSETCP RECEIVECONTROLLERMSGFROMCP 2500D9F010 TCTOOSD_TOOSD TOIUCV18000D3D580 TCTOIUC_TOIUCV Schedule 167000CFA118 MAIN-PROGRAM 1400C441FE TCPIP VSPASCAL 00E4D74A DTCOSD100E Insufficient Fixed Page Storage Pool storage after which it tries to shutdown and then goes into repeated: AMPX015I ADDRESSING EXCEPTION abends. Needless to say there were a lot of dump files in spool space. So, IBM will get a call on the abends. I could add more virtual storage = to the controllers, but that will presumably only add cushion for more = stops restarts before it runs out of storage again. Brian Nielsen = ===
Re: VSWITCH Controller failover issue on z/VM 5.2
Thanks. So whichever OSA does a Start Lan first becomes the current primary. Perhaps someone knows if there's a way to force the CISCO route r to start the preferred gig-OSA interface before the fast-OSA interface. I accomplished going back to the desired OSA by autologging DTCVSW1 (whic h is normally the active one, but had abended and was no longer logged on). Then forcing and autologging DTCVSW2 (which had taken over after DTCVSW1 abended). A side benefit was a clean virtual address space for each. Brian Nielsen On Mon, 24 Apr 2006 14:39:53 -0400, Alan Altmark [EMAIL PROTECTED] wrote: On Monday, 04/24/2006 at 12:39 EST, Brian Nielsen [EMAIL PROTECTED] wrote: There are several more iterations of Stop Lan and Start Lan, but it is always on the backup OSA addresses, never on the primary OSA addresses . So the question is: why didn't it ever try to restart on the primary O SA when the backup OSA received the Stop Lan? If both OSA cards were the same it might not matter that much, but the primary is a Gig-OSA and t he backup is a Fast-OSA. There is no permanent association of primary and backup in the VSWITCH. There is just a list of available OSAs. The VSWITCH starts wi th the first one and fails over until it finds a working one. Whichever on e is active is the primary. The others are backups. (You can see tha t in QUERY VSWITCH.) So, I'm not 100% sure I'm reading your post correctly, but I would have expected identical behavior vis a vis the decision to fail over, without regard to which OSA was active and which were backups. A StopLAN on the currently active OSA should have caused a failover. If none of the backups worked (i.e. all OSAs unplugged at the same time), I would have expected CP to come back to the OSA that is currently 'active' and sit a nd wait for StartLAN on the active OSA or one of the backups. At that poin t, whichever one comes up first would become the active OSA. Of course, with the abend in the controller, bizzare things were obvious ly going on. The Support Center definitely needs to look at it. FWIW, if you want it to go back to the first OSA in the list, set up som e system automation to do a SET VSWITCH DISCONNECT followed by a SET VSWIT CH CONNECT when you get an adapter-initiated StartLAN on the desired device (as seen on the controller's console). CP will go back to the beginning of the OSA list and start looking for a working device. Alan Altmark z/VM Development IBM Endicott =
