Scalibilty check on mainframes.

[A Joglekar]

How do we do the scalibilty check on mainframes?

There is a bank1 which is going to merge with other bank. We are trying to guage if the current technology landscape of mainframe is capable for the extra load we might get after the merger. What are the question you think one can ask for such an engangement, as a start? Your help is appreciated.

[Robert Sample]

There should be someone doing capacity planning / performance analysis for both mainframe sites. Those people need to get together and determine the answer! Most merged sites start out by continuing to run both mainframes, often using one as a hot backup site for the other. Eventually (when the next upgrade is needed), the boxes can be combined if that is determined to be the best way to proceed.

Questions I'd want to know the answers to in such an adventure:
- Which version of z/OS does each site use?
- Are those versions supported?
- Which job entry subsystem does each site use?
- Which job scheduler does each site use?
- Which tape management system does each site use?
- Which disk storage system does each site use?
- Which archival product does each site use?
- What type of tape drives does each site use?
- How many LPARs does each site have?
- How many ICF, zIIP, zAAP, CP at each site?
- How many (test, QA, production) CICS regions at each site?
- How many (test, QA, production) DB2 subsystems at each site?
- How many (test, QA, production) IMS subsystems at each site?
- What other software does each site use (SAS, MXG, (E)JES, SDSF, RMF, OMEGAMON, MAINVIEW are a few of the MANY possible software products)?
- Which terminal emulator does each site use?

There are many other questions but those are enough to get you started.