11.01.2013 Views

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The ESS was the first <strong>of</strong> the Seascape architecture storage products to attach directly to <strong>IBM</strong><br />

<strong>System</strong> z and open system platforms. The Seascape architecture products come with<br />

integrated storage controllers. These integrated storage controllers allow the attachment <strong>of</strong><br />

physical storage devices that emulate 3390 Models 2, 3, and 9, or provide 3380 track<br />

compatibility mode.<br />

Powerful storage server<br />

The storage system is intelligent and independent, and it can be reached by channels or<br />

through the network. It is powered by a set <strong>of</strong> fast RISC processors.<br />

Snap-in building blocks<br />

Each Seascape product is comprised <strong>of</strong> building blocks, such as:<br />

► Scalable n-way RISC server, PCI-based. This provides the logic <strong>of</strong> the storage server.<br />

► Memory cache from RISC processor memory.<br />

► Channel attachments, such as FC-AL, SCSI, ESCON, FICON and SSA.<br />

► Network attachments, such as Ethernet, FDDI, TR, and ATM.<br />

► These attachments can also implement functions, that is, a mix <strong>of</strong> network interfaces (to<br />

be used as a remote and independent storage server) and channel interfaces (to be used<br />

as a storage controller interface).<br />

► S<strong>of</strong>tware building blocks, such as an AIX subset, Java applications, and Tivoli® Storage<br />

Manager. High level language (HLL) is more flexible than microcode, and is easier to write<br />

and maintain.<br />

► Storage adapters, for mixed storage devices technologies.<br />

► Storage device building blocks, such as serial disk (7133), 3590 tape (Magstar), and<br />

optical (3995).<br />

► Silos and robots (3494).<br />

Universal data access<br />

Universal data access allows a wide array <strong>of</strong> connectivity, such as z/<strong>OS</strong>, UNIX, Linux, and<br />

<strong>OS</strong>/400®, to common data. There are three types <strong>of</strong> universal access: storage sharing, data<br />

copy sharing, and true data sharing, as explained here.<br />

► Storage sharing<br />

Physical storage (DASD or tape) is statically divided into fixed partitions available to a<br />

given processor. It is not a s<strong>of</strong>tware function. The subsystem controller knows which<br />

processors own which storage partitions. In a sense, only capacity is shared, not data; one<br />

server cannot access the data <strong>of</strong> the other server. It is required that the manual<br />

reassignment <strong>of</strong> storage capacity between partitions be simple and nondisruptive.<br />

The benefits are:<br />

– Purchase higher quantities with greater discounts<br />

– Only one type <strong>of</strong> storage to manage<br />

– Static shifting <strong>of</strong> capacity as needed<br />

The drawbacks are:<br />

– Higher price for SCSI data<br />

– Collocation at 20 meters <strong>of</strong> the SCSI servers<br />

– No priority concept between z/<strong>OS</strong> and UNIX/NT I/O requests<br />

Chapter 8. Storage management hardware 451

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!