RE: YAIQ - Yet another ignorant question: multiple LPARs.

["McKown, John" <John.Mckown@xxxxxxxxxxxxxxxxx>]

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of 
> smorrison@xxxxxxxxxxxxxxxxxxx
> Sent: Friday, December 05, 2008 3:57 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: YAIQ - Yet another ignorant question: multiple LPARs.
>
> John,
>
> All objects reside in "libraries"  on the i (think of PC-DOS 
> directories 
> that cannot be nested). These are associated with individual 
> hosts (either 
> physical systems or virtual partitions (LPAR)). I'm not 
> familiar with a 
> sysplex, so I can't make any comparisons.
>
> A common method of sharing data files between systems is by 
> creating a DDM 
> file (Distributed Data Management). This virtual DDM file 
> will point to a 
> physical file in another library, or on another system (physical or 
> virtual). The DDM file will provide access to the actual data on the 
> target system. The DDM connection is typically over a network 
> (typically 
> TCP/IP). The IBM i provides a virtual TCP/IP network between 
> LPARs on the 
> same physical system, with a speed of 100 GB. DDM files can be read, 
> updated and deleted from both the local and the remote 
> systems. Multiple 
> remote systems can point to the same target system.
>
> How would you control updates from your test or QA 
> environments to data in 
> a sysplex?
>
> There are also ways to share disk pools between physical and virtual 
> systems. Check into Shared ASP (Auxiliary Storage Pools).

Ah! that looks to be what I am really interested in. Maybe.

> Steven Morrison
> Fidelity Express 
> 903-885-1283  ext. 292


--
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)
Administrative Services Group
9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * (817)-961-6183 cell
john.mckown@xxxxxxxxxxxxxxxxx * www.HealthMarkets.com

Confidentiality Notice: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential or proprietary information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message.