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

Hi John

Once again, the IASP scenario seems to be closest to the functionality you
are looking for. I am not necessarily recommending the approach but I am
saying that it mimics what you seem to be used to.

In the situation you described:

- A product database lives in IASP PROD
- A copy of the database lives in IASP TEST
- Another version of the database lives in IASP DEV
- Programmer has a forensic or common library "MYSTUFF" in the *SYSBAS ASP

Program develops program FORENSIC1 in library MYSTUFF and develops against
the set of libraries in DEV by having the job running with the IASP set to
DEV

When ready to QA he sets the IASP of his job to TEST and runs the program
again - the program now runs using the libraries and programs contained in
IASP DEV; the environment has been completely changed.

If it passes QA and can be run against production then he changes the job to
run on the PROD IASP and the program runs against production data.

In each case the program FORENSIC1 in MYSTUFF in ASP *SYSBAS runs against a
different database with nothing except a change to the job environment. No
communication or other setup is required.

Obviously there are some other considerations: planning what lives where is
very important; promotion of objects to production; security of production
data. But you probably have that now.

Your alternative with LPARS would b to move the program objects onto the
remote machine. You could write a simple program to do this or use a HA
tool. You programmers would log onto the other system/LPAR to run their test
or production job.

Regards
Evan Harris


<SNIP>
OK, this I am used to. I.e. program running on system A can access a
database residing on system B.

What I am thinking of is this scenario. Our programmers normally log
onto the Dev system. That is where all their "personal tools" are. There
is a production problem. The programmer then logs onto the Pdn system
(this may be where my "problem" begins). But they want their "personal
tools", which may be things like some CL programs and "stuff" like maybe
notes. I guess for "notes" they could log on to both systems
simultaneously. But if they have a program which is a "forensic" program
that they want to run against a production database, would they log on
to Dev and run their program against the production database via
DDM/DRDA/whatever-it-is called? Is there any need/way for the programmer
to look at a SPOOL file on production?

Perhaps this is not the appropriate way to debug a production problem on
the i? I.e. I'm being unduly influenced by my z background and trying to
"do it the z way" on an i. Wouldn't surprise me if that is the case.

</SNIP>