RE: Does anybody know of anything funky going on with JDEfilesunderV5R3?

World: Original JDE, 5250-based, all apps are in RPG.  Fast & relatively
efficient.

OneWorld: "Client-server".  Database is about 98% the same as World, but
the app was re-written with a C code blower.  Multi-tier architecture
although you can do almost everything on iSeries.  Exceptions: Windows
is required for the Deployment Server, which manages objects for
development and promotion to the various environments like prototype &
production and the Java Generation machine, which takes the application
code and generates Java JAR/WAR files for the app server.  Users can
access via browser, Citrix, or "fat client" although fat clients are
best left to developers and app admins only as they chew through PC &
bandwidth resources.

EnterpriseOne: The latest version of OneWorld, renamed by PeopleSoft
when they acquired JD Edwards.  8.10 is, IIRC, the last version to
support Citrix clients; browser is recommended for users & fat client
for developers and maybe administrators.

When JDE came out with OW, they reduced the amount of new functionality
being developed for World.  Newer capabilities, like CRM, were added to
OW (and later E1) which World basically saw maintenance updates.  Psft &
later Oracle have taken decent care of World & OW to date, but it's
pretty clear E1 has the best future as long as Oracle maintains
ownership and establishes a migration path to their Fusion product that
will merge the Oracle ERPs to a single Java-based package.

Oracle still sells World & E1.  OW is basically dead except for support.


We use World for property management.  At the time we make the product
selection, JDE hadn't released the property management module for OW and
E1 didn't exist so our choice was clear.  We later added OW to the mix,
although we only use it for reporting as it included some canned reports
that were going to be difficult to write for World.  We feed data from
World to OW; there is no data entry in OW.

I'll point out that JDE had a shared database model called coexistence
within which World & OW could share the same database.  I believe
they've phased it out, though.  We never used it; we preferred to simply
replicate the data necessary to run our OW reports from the World db to
a smaller OW database.

We use E1 for other functions in addition to property management.
Things like project management.  In the very long run, we'll probably
create a second E1 instance and slowly migrate from World to E1 for our
base property management, but Oracle has pledged World support until at
least 2013 so we have time.

Other notes:
- The browser interfaces for OW & E1 run on top of WebSphere, so our
LPARs are running WAS Standard 5.0.
- OW & E1 produce PDFs as native output for reports; World produces
spool files.  For all environments we use a 3rd party tool to (for
World) convert to PDF and (for all) enhance the output with shading,
text boxes, color, etc.
- For OW & E1, the Deployment Server and Java Generation machine run
just fine on IxS cards, so you can easily keep the entire environment
within your iSeries frame.

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces+john.jones=am.jll.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+john.jones=am.jll.com@xxxxxxxxxxxx] On Behalf
Of Michael Ryan
Sent: Wednesday, June 14, 2006 7:37 AM
To: Midrange Systems Technical Discussion
Subject: Re: Does anybody know of anything funky going on with
JDEfilesunderV5R3?

Out of ignorance I ask: What's the difference between World, OneWorld
and EnterpriseOne, and why would one run all three?

On 6/14/06, Jones, John (US) <John.Jones@xxxxxxxxxx> wrote:

Which JDE are you referring to: World, OneWorld, or EnterpriseOne?

We run all three here (World A7.3 Cume 13, OneWorld 8.0, and E1 8.10) 
on V5R3, with World & OW in one LPAR and E1 in another.  I'm not sure 
of the service pack levels on OW & E1.  I don't recall any particular 
migration issues when we took World to V5R3.  E1 and OW were installed

at V5R3; World was migrated from V5R1 (and earlier from V4R5 etc. back

to V4R1 when it was originally installed).

IBM & Oracle have a specific page with links to info necessary to run 
JDPeopOracle apps on iSeries, including an APAR that lists 
required/recommended PTFs at 
www-03.ibm.com/servers/enable/site/events/jde_links.html. The PTF APAR

mostly lists the current cume & groups, but also mentions a few 
specific PTFs for certain issues.

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H H 
Lampert
Sent: Tuesday, June 13, 2006 6:54 PM
To: Midrange Systems Technical Discussion
Subject: Re: Does anybody know of anything funky going on with 
JDEfiles underV5R3?

"Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

I don't have JDE either but some of our customers do.  I heard from 
them that with release 8.10 of EnterpriseOne they have an option to 
switch their control tables (files) to Unicode (VARGRAPHIC - ccsid 
13488).

Hmm. Interesting, but I don't see how that could affect direct access 
to the data, or even QuestView's JDE Dictionary interface (which uses 
F9201, along with either F9210 or F9202, but no other 
dictionary-related files). I looked at a system in which we were able 
to duplicate the funky-meta-data crash-and-burn problem; F9201 and 
F9202 both look perfectly normal to me. Besides which, if they'd been 
changed to Unicode, the JDE Dictionary interface wouldn't work at all,

since it would crash trying to access those files.

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, 
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take 
a moment to review the archives at

http://archive.midrange.com/midrange-l.

This email is for the use of the intended recipient(s) only.  If you 
have received this email in error, please notify the sender 
immediately and then delete it.  If you are not the intended 
recipient, you must not keep, use, disclose, copy or distribute this 
email without the author's prior permission.  We have taken 
precautions to minimize the risk of transmitting software viruses, but

we advise you to carry out your own virus checks on any attachment to 
this message.  We cannot accept liability for any loss or damage 
caused by software viruses.  The information contained in this 
communication may be confidential and may be subject to the 
attorney-client privilege. If you are the intended recipient and you 
do not wish to receive similar electronic messages from us in the

future then please respond to the sender to this effect.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, 
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take 
a moment to review the archives at 
http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.



This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in the future then please respond to the sender to this effect.