RE: LPar, backup, standard procedures info.

I didn't mention SAVRSTxxx as it is my understanding that it will go away along 
with SNA.

Thus, I'd recommend setting something up that used TCP/IP now that way you 
won't have to worry about it later.

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx
> [mailto:midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx]On 
> Behalf Of
> Pete Helgren
> Sent: Thursday, June 23, 2005 11:55 AM
> To: Midrange Systems Technical Discussion
> Subject: Re: LPar, backup, standard procedures info.
> 
> 
> John,
> 
> I have a customer that has that exact setup.  They are a 
> school district 
> with their own small development staff.  We initially upgraded to the 
> i5, bringing everything over from the 720 and then we 
> restored a backup 
> of the "Production" partition to the "Development" partition.
> 
> First challenge was to quickly remove all source code from the 
> production side so that the programmers wouldn't accidentally 
> log on to 
> the wrong partition and update the wrong source.  Second we installed 
> and configured the licensed program 5722SS1 Option 22  OS/400 - 
> ObjectConnect.  That allows us to do SAVRSTOBJ, SAVRSTLIB between the 
> two partitions and, since we set up the routing to use the internal 
> virtual network adapter, the transfers scream.
> 
> They don't have a CMS, they just have versioning and naming 
> conventions 
> that help identify and apply changes to the production 
> objects. Again, 
> they are a small shop (their two programmers plus our 3 or 4 
> depending 
> upon the project we are helping them with).
> 
> HMC was the only challenge in the setup and it appears, for 
> now, that it 
> is stable (thankfully).
> 
> HTH,
> 
> Pete Helgren
> Timpanogos Technologies, Inc
> 
> 
>