The whole combined versus separate TEST and PROD LPARs was interesting.  I 
can't imagine not having them separate (with shared DASD for at least the load 
libraries), but then it's just what I'm used to.

So here's a question...  Anyone out there have DEV/TEST not only in a separate 
LPAR, or even a separate machine, but in a separate data center?  We have our 
primary data center in Lakewood, CO (near Denver) and our "alternate data 
center" (DR site) in Scottsdale, AZ.  So about 1000 miles apart.  Management 
has the idea that we should move the applications development LPAR to the ADC.  
As an applications developer this makes me more than a bit nervous.  Does 
anyone do this?  Is a GDPS essentially required to make this workable?  We 
currently do DASD replication to our ADC using DS8100s.

One other thing I'm concerned about is TN3270 response time.  I feel that 
logging on to work from home is too slow, and I only live 8 miles away.

Thanks,
Frank


>>> 

The information contained in this electronic communication and any document 
attached hereto or transmitted herewith is confidential and intended for the 
exclusive use of the individual or entity named above.  If the reader of this 
message is not the intended recipient or the employee or agent responsible for 
delivering it to the intended recipient, you are hereby notified that any 
examination, use, dissemination, distribution or copying of this communication 
or any part thereof is strictly prohibited.  If you have received this 
communication in error, please immediately notify the sender by reply e-mail 
and destroy this communication.  Thank you.

-- 

Frank Swarbrick
Applications Architect - Mainframe Applications Development
FirstBank Data Corporation - Lakewood, CO  USA
P: 303-235-1403

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to