All objects reside in "libraries" on the i
(think of PC-DOS directories that cannot be nested).
I should clarify that this refers to the traditional AS/400 file system.
The IBM i also hosts other file systems, called the Integrated File System
(IFS). This combines the traditional AS/400 file system (QSYS.LIB), Unix,
Linux, and POSIX type file systems (/Root) and (QOPENSYS), a document
library system (QDLS) for old style DCA documents, QFILESVR.400, QNETWARE,
QOPT, and QNTC. All of these are available on the system at the same time.
There's plenty to learn and to keep you confused!
Steve
Steven Morrison
Fidelity Express
smorrison@xxxxxxxxxxxxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
12/05/2008 04:09 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc
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).
Steven Morrison
Fidelity Express
903-885-1283 ext. 292
"McKown, John" <John.Mckown@xxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
12/05/2008 03:34 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc
Subject
YAIQ - Yet another ignorant question: multiple LPARs.
If/when we go from z/OS to an i, we plan to have three LPARs (probably
all on the same machine). The three will be: Production; Development &
QA; "sandbox" for software testing (OS and vendor, not application). On
z/OS we run these in a sysplex. That lets us safely share data directly.
I cannot see anything like this for the i. I get the impression that
data sharing on the i is done more like it is on UNIX or Windows. That
is, one system "owns" the data and if a job on another system needs
access to it, the I/O is done by the "owing" system and then sent
(TCPIP??) to the "requesting" system. I am aware that this is the method
that databases often use.
So, on an i, are the LPARs each separate with their own files, spool,
tapes, etc. What can be shared and how? A pointer to a manual would be
very appreciated.
Many thanks.
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.
midrange.com
