Clarification. What used to be MVS1 is now a front-end system that does not process the jobs addressed to MVS1. Instead, it distributes the work among two or more other machines, the ones I listed as MVS1A and MVS1B. There can, and probably will, be others in the future. The entire collection of machines behind the Front End appears as a single entity called MVS1 to RSCS. The only one that is currently connected to the NJE network is MVS1 (actually MVS1N - N for Network). Having set things up that way, the MVS JES2 guy is wondering if there was some way RSCS could use a back door to get jobs into at least one of the worker machines when MVS1N is down. They built a system having a single failure point and have experienced a failure. Now they are hoping for an easy, meaning VM, fix. The current return path is from the worker machines through MVS1N, which we know to be a choke point.
All of the RSCS links to MVS systems (we have many more that the MVS1-plex) are TCPNJE. (Les can probably attest to the amount of effort that it took to get there. I hope that the JES2 development and support folks gave him a gold star for his help.) Regards, Richard Schuh ________________________________ From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Wheeler Sent: Thursday, April 23, 2009 7:32 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: RSCS Connections > Date: Thu, 23 Apr 2009 21:59:41 -0400 > From: lg...@vnet.ibm.com > Subject: Re: RSCS Connections > To: IBMVM@LISTSERV.UARK.EDU > > >Following David Boyes' example= set up something like: > > > >LINKDEF MVS1A NODE MVS1 TYPE SNANJE LUNAME MVS1ALU ASTART RETRY > > > >PARM MVS1A BUFF=3D3840 > > > >LINKDEF MVS1B NODE MVS1 TYPE SNANJE LUNAME MVS1BLU ASTART RETRY > > > >PARM MVS1B BUFF=3D3840 > > > >ROUTE GROUP MVS1 TO MVS1A MVS1B > > > > I don't believe that will meet Richard's requirement. This defines > MVS1 as a group of two nodes, MVS1A and MVS1B. All files for > MVS1 will flow over these two links. > Looking at the documentation, I don't see a good automated way to > achieve Richard's goal. > > > Best Regards, > Les Geer > IBM z/VM and Linux Development I assumed (and we know what can happen when we assume) that MVS1(a) and MVS1(b) were in a shared MAS configuration. Richard will need to clarify. As an alternative, I wonder if DVIPA could be employed here? The RSCS system would use a TCPNJE link to "MVS1", whose IP address could move between MVS1(a) and MVS1(b). I confess that I don't know if JES TCPNJE can exploit DVIPA. A reason I suspect that this must be a share MAS configuration is that files need to be able to flow from JES to RSCS from either MVS1(x) system. Again, need clarification. Mark Wheeler ________________________________ Windows Live(tm) Hotmail(r):...more than just e-mail. Check it out.<http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_more_042009>
