Re: Sysplex Basic Question

Thanks Joel. That validates what the customer told me. They were doing DB2 datasharing.

Still no one has answered my first question, which I left quoted below. I'll try to rephrase it.

Can you set up a sysplex so that both machines have everything running on each CPU in the plex, and when one system crashes the other will automatically take over everything? Say you have SYSA and SYSB. Each has 10 CICS regions running. Half of the applications are routed to SYSA, and the other half to SYSB, but all 10 CICS regions are running on each system. If SYSA crashes, can all transactions now be routed to SYSB? I'm sure that any transactions on SYSA at the time of the crash will not finish, and have to be reentered, but I was under the impression that everything after the crash could then be routed to SYSB after the SYSA crash. I'm not sure if that could be done automatically by automation, or would take someone to look at it and type in a command.

Eric Bielefeld
Sr. Systems Programmer
Milwaukee, Wisconsin
414-475-7434


----- Original Message ----- From: "Joel Wolpert" <joel@xxxxxxxxxxxxxxxxxx>


If I recall correctly there is a big hit (10-20% overhead) for the first 2 systems in a sysplex when doing DB2 datasharing. After that the overhead drops drastically.
For other sysplex implementations the overhead can be much less.

Joel Wolpert
Performance and Capacity Planning consultant
On Tue, 8 Sep 2009 12:01:08 -0500, Eric Bielefeld <eric-ibmmain@xxxxxxxxx>
wrote:

I'm curious. If you have a sysplex with say 2 separate CPUs, can you set
that up so that if one CPU crashes, that the other can take over
immediately? I seem to remember reading about that long ago, where you can
have the same CICSs and DB2 regions all up on both boxes, but all
transactions are routed to one box or the other. Then, if one CPU would
die, the other could take over immediately, with no wait. Is that the way
it works, or am I not remembering correctly? If that is the way it works,
that would mean a lot to that other thread on EMC and PAVs.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.

Relevant Pages

  • Re: Cluster vote allocation question
    ... SYSC can talk to them only via the ... >that SYSA and SYSB will maintain a cluster, ... >the dedicated link for cluster communications. ...
    (comp.os.vms)
  • Remote Desktop hangs target system
    ... the target system for Remote Desktop hangs, ... I can RDC from SysA to SysB ... blank/black and it hangs. ...
    (microsoft.public.windowsxp.work_remotely)
  • HYPERPAV
    ... We have two systems - SYSA and SYSB that are in SYSPLEX1 and see all ... We have five CU in Static PAV and all the others are Dynamic ... Is there a way to activate HyperPAV on SYSA only, ... Or he has to separate them to be in one SYSPLEX? ...
    (bit.listserv.ibm-main)
  • Re: Crazy iptables question...
    ... > My Linux box has 3 interfaces. ... > I need to create a setup where sysA and sysB can have the same network ... Packets arriving on eth1 will be SNATted to 10.11.11.4 an then be ...
    (comp.os.linux.networking)