• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Changing AS400s - What's the best way?

clewis

Member
Changing AS400s - What\'s the best way?

This is a MIME message. If you are reading this text, you may want to
consider changing to a mail reader or gateway that understands how to
properly handle MIME multipart messages.

--=_356EA2DC.1E7F1F8A
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

We have been testing One World Xe on a test AS400 for the past few months. =
We installed all environments on the test AS400, in coexistence mode, and =
went through a bunch of testing, which included customizing the Customer =
Inquiry programme, and then moving it through OMW and installing it in the =
Production Environment on the test AS400. We are now preparing to install =
One World on our production AS400, and I'm wondering about the best way of =
doing this. We want to end up with all environments pointing to the =
production AS400 - currently they all point to the test AS400. We also =
want to keep the modifications we've made to the Customer Inquiry =
programme.

My original thought was to wipe clean the Deployment Server and start =
again from scratch - that way I could be sure that no gremlins are left =
over from the previous install and testing. However, that won't keep the =
mods we've made. Is it possible to check out the mods to a client, wipe =
the deployment server and install everything pointing to the production =
AS400, and then somehow check the mods back in to the production AS400 =
from the client? (After changing the ODBC Data Sources on the client to =
point to the production AS400). How do we do the check-in without having =
done a check-out from the production AS400?

Is that the best way to go? Are there any other ways to accomplish the =
task?=20

Configuration:

Test AS400 - Model 720 running v4r5; Central Objects on the AS400. WinNT =
Deployment server with 2Gig RAM and 70+ Gig HD space. One World Xe in =
Coexistent environment

Want to end up with:

Production AS400 - Model 820 running v4r5; Central Objects on the AS400. =
WinNT Deployment server with 2Gig RAM and 70+ Gig HD space. One World Xe =
in Coexistent environment

Any suggestions??

Thanks,

Colin

--=_356EA2DC.1E7F1F8A
Content-Type: text/html
Content-Disposition: attachment; filename="TEXT.htm"
Content-Description: HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4134.600" name=GENERATOR></HEAD>
<BODY style="MARGIN-TOP: 2px; FONT: 10pt Arial; MARGIN-LEFT: 2px"
bgColor=#ffffff>
<DIV>We have been testing One World Xe on a test AS400 for the past few months.
We installed all environments on the test AS400, in coexistence mode, and went
through a bunch of testing, which included customizing the Customer Inquiry
programme, and then moving it through OMW and installing it in the Production
Environment on the test AS400. We are now preparing to install One World on our
production AS400, and I'm wondering about the best way of doing this. We want to
end up with all environments pointing to the production AS400 - currently they
all point to the test AS400. We also want to keep the modifications we've made
to the Customer Inquiry programme.</DIV>
<DIV></DIV>
<DIV>My original thought was to wipe clean the Deployment Server and start again
from scratch - that way I could be sure that no gremlins are left over from the
previous install and testing. However, that won't keep the mods we've made. Is
it possible to check out the mods to a client, wipe the deployment server and
install everything pointing to the production AS400, and then somehow check the
mods back in to the production AS400 from the client? (After changing the ODBC
Data Sources on the clientto point to the production AS400). How do we do
the check-in without having done a check-out from the production AS400?</DIV>
<DIV></DIV>
<DIV>Is that the best way to go? Are there any other ways to accomplish the
task? </DIV>
<DIV></DIV>
<DIV>Configuration:</DIV>
<DIV></DIV>
<DIV>Test AS400 - Model 720 running v4r5; Central Objects on the AS400.
WinNT Deployment server with 2Gig RAM and 70+ Gig HD space. One World Xe in
Coexistent environment</DIV>
<DIV></DIV>
<DIV>Want to end up with:</DIV>
<DIV></DIV>
<DIV>
<DIV>ProductionAS400 - Model 820 running v4r5; Central Objects on
the AS400. WinNT Deployment server with 2Gig RAM and 70+ Gig HD space. One World
Xe in Coexistent environment</DIV>
<DIV></DIV>
<DIV>Any suggestions??</DIV>
<DIV></DIV>
<DIV>Thanks,</DIV>
<DIV></DIV>
<DIV>Colin</DIV></DIV></BODY></HTML>

--=_356EA2DC.1E7F1F8A--
 
RE: Changing AS400s - What\'s the best way?

Try the Product Packaging Tool in XE.

Its supposed to be pretty good, except for a few extra things for which you
need to browse the KG.


Regards :),
Ashish Kalawadia
Sr. JDE Technical Consultant [CNC]
Advance Technology Services
SYSTIME COMPUTERS PVT. LTD.
Tel : +91-(22)-8290051
HandPhone : 9820216414
Email ID: ashish_kalawadia@systime.co.in
 

DRezanka

Reputable Poster
Re: Changing AS400s - What\'s the best way?

Colin,

This is theory, since I've never tried it, but you could probably do the reinstall of your DS, install your new prod AS400, and restore your Central Objects from backup. This would keep your mods. Backup your packages and you could recover those a whole lot quicker.

You could restore the Object Librarian tables to recover the Check Out status of the objects you wish to check back in.

An aside: You said you want to eliminate possible gremlins by reinstalling the DS, but you would probably reintroduce gremlins by checking mods in from a workstation at a previous install.

Have you installed the PD7333 environment yet? What if you were to add the PD environment with a different machine name? Then you might be able to wean yourself off the old machine one environment at a time.

Just some thoughts. Warning: a lot of theory.

Regards
Doug

Doug
dougrezanka@eaton.com

Xe SP13.1, AS400 V4R3, CO-Oracle806, Co-A73c10, Citrix, NT JAS
 
Re: Changing AS400s - What\'s the best way?

Also keep in mind that you software key is going to be for another machine
so you will need to call JDE and get a new software key for the new machine.

Don Bryant MIS Director mailto:donbryant@amalie.com



>From: DRezanka <dougrezanka@eaton.com>
>Reply-To: jdelist@jdelist.com
>To: jdelistml@jdelist.com
>Subject: Re: Changing AS400s - What's the best way?
>Date: Mon, 5 Mar 2001 05:26:30 -0800 (PST)
>
>Colin,
>
>This is theory, since I've never tried it, but you could probably do the
>reinstall of your DS, install your new prod AS400, and restore your Central
>Objects from backup. This would keep your mods. Backup your packages and
>you could recover those a whole lot quicker.
>
>You could restore the Object Librarian tables to recover the Check Out
>status of the objects you wish to check back in.
>
>An aside: You said you want to eliminate possible gremlins by reinstalling
>the DS, but you would probably reintroduce gremlins by checking mods in
>from a workstation at a previous install.
>
>Have you installed the PD7333 environment yet? What if you were to add the
>PD environment with a different machine name? Then you might be able to
>wean yourself off the old machine one environment at a time.
>
>Just some thoughts. Warning: a lot of theory.
>
>Regards
>Doug
>
>Doug
>dougrezanka@eaton.com
>
>Xe SP13.1, AS400 V4R3, CO-Oracle806, Co-A73c10, Citrix, NT JAS
>--------------------------
>Visit the forum to view this thread at:
>http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=6620
>*************************************************************
>This is the JDEList One World / XE Mailing List.
>Archives and information on how to SUBSCRIBE, and
>UNSUBSCRIBE can be found at http://www.JDELIST.com
>*************************************************************
>

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
 
Top