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

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.