Hi Norman,
What I have problems understanding is CA-11 3.0 not supporting facilities
that Datacom seems to have had more than four years ago for Data Sharing in
a Sysplex? If MUFPLEX really exists and works why doesn't CA-11 recommend
and exploit it?
The operational aspect of CA-11 3.0 having the customer manage the
availability of a single instance of supporting started tasks doesn't seem
reasonable. Thank goodness for CA-OPSMVS which we use to patch up failings
in many products including this one.
>From Nov-1999
Title: CA-Datacom Release 10.0 Enhancements - Data Sharing
For the OS/390 Sysplex user, CA-Datacom Release 10.0 provides support for
full data-sharing within the Sysplex. This feature has been nicknamed the
"MUFPLEX". In a Sysplex that has multiple OS/390 images that have access to
a shared Sysplex Coupler Facility, clients are able to run up to seven
different physical Multi-User regions that can process database requests as
a single logical CA-Datacom environment (the MUFPLEX).
In the MUFPLEX, the user databases are available for full update processing
from any one of the "member" Multi-Users (MUFs) at any time. This gives the
client the flexibility of adding/removing MUFs as needed to support a wide
variety of processing requirements. Items such as re-cycling of OS/390
images and making changes to the individual MUFs can be accomplished while
still providing access to the user databases through the remaining active
MUFs.
Within the MUFPLEX, member MUFs all share the same CXX and LXX datasets.
Each member MUF has its own CBS index and SQL TTM database.
All shared locking and buffering requirements are provided through the
OS/390 Sysplex Coupling Facility. Each member MUF communicates the status of
its active tasks, locks, buffers etc. via the Coupler "List" and "Lock"
structures.
Utilizing multiple OS/390 images provides the client with a way to scale
processing requirements as well as support OS/390 batch workload balancing.
Enhancements to CA-Datacom/CICS Service Facility are planned which will
allow a CICS to connect to the MUFPLEX (via the coupler) in order to provide
workload balancing as well as 24x7 connectivity support. A CICS region
connected via the coupler to the MUFPLEX will remain able to process as long
as one of the member MUFs of the MUFPLEX remains active.
MUFPLEX support is a selectable MUF startup option. For clients who do not
have a need for the MUFPLEX support, there is no additional overhead when
this feature is not selected. For clients who select the MUFPLEX feature but
only have one active member MUF the overhead is minimal. This will allow
clients to run in a single member mode with very little cost until a need
arises for a second member MUF.
For example, presume that an IPL of the production MUF machine is required.
At that time, a second member MUF is started and the Sysplex Coupler
Facility is utilized to manage the databases that are now shared. Once the
second MUF is up, the workload can be shifted to the second MUF, the primary
MUF can be stopped, and the OS/390 image can be IPL'ed.
Watch for additional information on Data Sharing in future articles on the
CA-Datacom and CA-Ideal homepage.
------------------
Best Regards,
Sam Knutson, GEICO
Performance and Availability Management
mailto:[EMAIL PROTECTED]
(office) 301.986.3574
"Think big, act bold, start simple, grow fast..."
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Norman Hollander
Sent: Tuesday, May 17, 2005 2:07 PM
To: [email protected]
Subject: Re: CA-11 3.0 + CA-DATACOM + Sysplex
Importance: High
Let me see if I can help with some of this. I do understand some of the
challenges from the System Programming point of view.
CA is moving to the Management Data Base (MDB) solution for many of the
Infrastructure types of Products. This allows the usual types of Data to be
shared across many of the solutions already in use. Datacom was chosen due
to it performance characteristics. It does extremely well with the products
that already use it. This Datacom requirement is meant to be a Black Box
that is installed with associated products. Other than the normal Data
Backup requirements, you should NOT have to be a DBA to run this. You still
need to be aware of a Database product, just like you need to be aware that
Websphere/MQ is DB2 under the covers, and OAM requires a (separate) DB2
subsystem to run.
At one of our very large customers with large Sysplexes, a migration to CA11
R11 with Datacom went extremely smooth (without incident). The resulting
performance is extremely fast. In fact they are able to do the work that
CA11 previously did without Datacom, in less than half the time.
There are some issues I read in all of these threads that I have passed on
to the related Product Managers and Support. That is: the ease of
installation (or the lack thereof), and Recoverability/Failover Opertional
Procedures. I would expect a lot of enhancements to both of these as this
new process matures.
<>
====================
This email/fax message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution of this email/fax is prohibited. If
you are not the intended recipient, please destroy all paper and electronic
copies of the original message.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
