Upgrade to V5R2

I've been reading a lot of the posts about upgrading from V5R1 to V5R2 and have a few questions.

Will a full package build have to be done after the upgrade for each of our environments?

I seem to recall reading (or hearing) about a database conversion. Is there some kind of conversion that will need to take place? We are running both One World (XE) and World (co-ex).

Thanks

tgore,

When we upgraded from V4R5 to V5R2, we did not have to build a new full package right away. I forget the step but there is an object conversion process that runs after the upgrade. It essentially upgrades your files from DB2 UDB (plus your current version) to DB2UDB for V5R2. When the process is complete you should be fine.

However, I would suggest building a full package as a test before you absolutely have to. If memory serves, you will need to change OS version numbers, etc in your server side JDE.INI in order to compile. It's better to get the kinks out before you are under the gun...

Good Luck.

Ryan Hunt

Do you have more information on this step ?

I just had our AS/400 upgrade from V5R1 to V5R2 - everything went fine as far as SQL Packages, seeing data etc - but when it came to the deployment server, a whole host of issues arose.

The Deployment Server is (yuck) an integrated card. It became totally corrupt - in the end I had to have the Integrated card completely reinstall the base OS (Win2K) and reinstalled the deployment server code and restore the old deployment server B7333 directories. Everything seemed fine until :

1. The deployment server now runs horribly slow - we thought it might be the antivirus software, but we disabled that and it still runs horribly slowly. It seems to be drive access speed rather than network speed - currently IBM is looking into it

2. Packages are no longer building. I am trying to run a full package build - it works fine on the client-side, and I had to change the server JDE.INI to reflect the V5R2 changes as per document OTM-00-0093 - I am still suffering from the server side build. Any suggestion would be great.

It seems there is no real document around that details the major changes between V5R1 and V5R2 - if someone forwards to me all the information they went through with their V5R2 upgrade, I'll happily create a document for JDEList.

Jon, can you elaborate on what exactly isn't working on the server side?
Can we assume that APAR II13384 as of June 14, 2004 has been successfully
completed, (cum, hiper's, database fix pack and CAE)?
_____

From: [email protected] [mailto:[email protected]] On
Behalf Of altquark
Sent: Saturday, July 24, 2004 6:25 PM
To: [email protected]
Subject: Re: Upgrade to V5R2


Do you have more information on this step ?

I just had our AS/400 upgrade from V5R1 to V5R2 - everything went fine as
far as SQL Packages, seeing data etc - but when it came to the deployment
server, a whole host of issues arose.

The Deployment Server is (yuck) an integrated card. It became totally
corrupt - in the end I had to have the Integrated card completely reinstall
the base OS (Win2K) and reinstalled the deployment server code and restore
the old deployment server B7333 directories. Everything seemed fine until :

1. The deployment server now runs horribly slow - we thought it might be the
antivirus software, but we disabled that and it still runs horribly slowly.
It seems to be drive access speed rather than network speed - currently IBM
is looking into it

2. Packages are no longer building. I am trying to run a full package build
- it works fine on the client-side, and I had to change the server JDE.INI
to reflec! t the V5R2 changes as per document OTM-00-0093 - I am still
suffering from the server side build. Any suggestion would be great.

It seems there is no real document around that details the major changes
between V5R1 and V5R2 - if someone forwards to me all the information they
went through with their V5R2 upgrade, I'll happily create a document for
JDEList.

Jon Steel OneWorld Technical Specialist erpSOURCING LLC - member of The
iConsortium http://www.erpsourcing.com [email protected] 24/7 Response Line -
(904) 382 5701



_____


The entire <http://www.jdelist.com/ubb/showflat.php?Cat=&Board=> JDELIST
thread is available for viewing.



This is the JDELIST EnterpriseOne Mailing List.
The instructions on how to unsubscribe from any JDELIST mailing list are
available here <http://www.jdelist.com/unsubscr.shtml> .
JDELIST is not affiliated with JDEdwardsR.

Re: RE: Upgrade to V5R2

This is the issue we're currently facing. It took me most of today to even get hold of someone from Peoplesoft, since they no longer have access to upload support calls from the website (even the new website - the old GSS are still using the old SAR System - what a joke)

1. We updated from V5R1 to V5R2
2. Everything (batch jobs etc) are working fine
3. Removed all SQL Packages prior to running package build (done this twice now)
4. Changed the Server JDE.INI (attached) to reflect V5R2 changes
5. Trying a full package build

Client part of the package works fine - but the server side of the package errors out. I have tried submitting the package both from the deployment server AND a Fat Client - both resulting in the same issues.

Server Build Log :
------------------
Server Build Log

Package NameY7333FF00
PathCodeY7333
Server Name:
Process ID: 1416 Thread ID: 1812
Build Date:7/25/2004
Build Time:125400

Sun Jul 25 18:39:00 2004 spkgeng.c128 PKG0000017 - Creation of Server Package Build Log successful.
Sun Jul 25 18:39:00 2004 spkgeng.c132 PKG0000019 - Initializing server header structure.
Sun Jul 25 18:39:00 2004 spkgeng.c181 PKG0000021 - Initializing server detail structures.
Sun Jul 25 18:39:00 2004 spkgclnt.c74 PKG0000020 - Begin communication with server OWENT01.
----------------

JDE.LOG Errors :
----------------

848/1304 Sun Jul 25 12:47:20 2004 spkgclnt.c364
PKG0001010 - An error occured on OWENT01
No file.

848/1304 Sun Jul 25 12:47:20 2004 spkginit.c901
PKG0002305 - Unable to load detail structures for package PY7333FF00

848/1304 Sun Jul 25 12:47:20 2004 spkginit.c590
PKG0002205 - Unable to load detail structures for package PY7333FF00

848/1304 Sun Jul 25 12:47:20 2004 spkgeng.c199
PKG0000022 - Package Build Failed for PY7333FF00: Unable to create package header structure.


1416/1812 Sun Jul 25 18:39:01 2004 spkgclnt.c364
PKG0001010 - An error occured on OWENT01
No file.

1416/1812 Sun Jul 25 18:39:01 2004 spkginit.c901
PKG0002305 - Unable to load detail structures for package PY7333FF00

1416/1812 Sun Jul 25 18:39:01 2004 spkgeng.c199
PKG0000022 - Package Build Failed for PY7333FF00: Unable to create package header structure.
-----------

Interesting areas of AS/400 JDE.INI :
-------------------------------------

[BSFN BUILD]
BuildArea=/OneWorld/packages
OptimizationFlags=(40)
DebugFlags=*ALL
InliningFlags=Y
DefineFlags=JDENV_AS400MUTEX PRODUCTION_VERSION JDBDB2400 AS400V5R2
CompilerFlags=*EXPMAC *NOSHOWINC
CompileOutput=*PRINT
OSReleaseLevel=*CURRENT
LinkFlags=*DUPPROC *DUPVAR *UNRSLVREF
LinkLibraries=JDELIB JDEKRNL OWVER
SimultaneousBuilds=0
QNAME=OWPACKAGE

[AS400]
DBGVIEW(*NONE) OPTIMIZE(40)
CRTCMOD2=DEFINE(JDENV_AS400MUTEX PRODUCTION_VERSION NO_SIGNALS) TGTRLS(*CURRENT)
CRTSRVPGM=CRTSRVPGM SRVPGM(%s/%s) MODULE(%s/*ALL) BNDSRVPGM(JDELIB JDEKRNL OWVER) EXPORT(*ALL) OPTION(*DUPPROC *DUPVAR *UNRSLVREF) ALWLIBUPD(*YES) TGTRLS(*CURRENT)
CRTDBPGM1=CRTPGM PGM(%s/%s) MODULE(DBDRVAG DBDRV DBDRV_AC DBDRV_CC DBDRV_CN
CRTDBPGM2=DBDRV_CH DBDRV_CP DBDRV_DT DBDRV_RQ DBDRVSQL DBMONCTL DBDRVCLI
CRTDBPGM3=DBSQL DBSQL_A DBSQL_D DBSQL_I DBSQL_M DBSQL_S DBSQL_U DBSQL_X)
CRTDBPGM4=BNDSRVPGM(JDEKRNL JDELIB JDEIPC QBFCPRCED) ACTGRP(%s) OPTION(*DUPPROC
CRTDBPGM5=*DUPVAR) ALWLIBUPD(*YES) AUT(*ALL) TGTRLS(*CURRENT)
PrintUBEJoblog=FALSE
PrintUBEJoblogOnError=FALSE

----------------------------------

I have even a JDEDEBUG.LOG which I attach as well.

If someone can point me in the right direction, I would be really grateful. Two sets of eyes would really help I guess !

Re: RE: Upgrade to V5R2

----------------
It seems there is no real document around that details the major changes<br>between V5R1 and V5R2 - if someone forwards to me all the information they went through with their V5R2 upgrade, I'll happily create a document for JDEList.
----------------
We really didn't have any problems with the upgrade. We upgraded Client Access. Applied all the PTFs per the IBM/JDE APAR. Deleted the SQL packages and everything built fine.

Almost seems like a communication error or an inability to create the .inf file on the deployment server or on the ifs on the AS400.

This is a good log:
Sat Apr 10 08:30:15 2004 spkgeng.c128 PKG0000017 - Creation of Server Package Build Log successful.
Sat Apr 10 08:30:15 2004 spkgeng.c132 PKG0000019 - Initializing server header structure.
Sat Apr 10 08:30:16 2004 spkgeng.c181 PKG0000021 - Initializing server detail structures.
Sat Apr 10 08:30:17 2004 spkgclnt.c74 PKG0000020 - Begin communication with server MYAS400.
Sat Apr 10 08:30:38 2004 spkgclnt.c453 PKG0000021 - Receive communication with server MYAS400.
Sat Apr 10 08:30:38 2004 spkginit.c928 PKG0000022 - Validating deployment server compression directory - MYAS400.
Sat Apr 10 08:30:38 2004 spkginit.c995 PKG0000024 - Creating Server.inf file.
Sat Apr 10 08:30:38 2004 spkginit.c1074 PKG0000025 - Create list of objects to build on server.
...
...
Grant

Re: RE: Upgrade to V5R2

Thanks Grant

It seems that we're having an issue actually creating the directory for the package on the IFS from the AS/400 side of things. I was able to capture this JDE.LOG on the server :

1991 Mon Jul 26 14:25:41 2004 spkgutil.c582
PKG0000700 - Unable to create PY7333FF00, failed with CPF21720

1991 Mon Jul 26 14:25:41 2004 spkgutil.c288
PKG0000603 - Invalid directory!…Unable to validate PY7333FF00

1991 Mon Jul 26 14:25:41 2004 spkginit.c3267
PKG0003004 - Unable to create library PY7333FF00 and it does not already exist

1991 Mon Jul 26 14:25:41 2004 spkgsvr.c312
PKG0004009 - Unable to initialize server directories.Package error No file.

1991 Mon Jul 26 14:25:41 2004 spkgutil.c1438
PKG0004200 - Package PY7333FF00 has not been initialized on this machine.


The problem is that the user id that runs these processes ("ONEWORLD") seems to have permission to create directories.

Re: RE: Upgrade to V5R2

Can you try shortening the name of the package and call it something simpler. I had this issue way back when I was working on the 400 and it had issues creating the package header I reduced the number of characters in the name and called it something like PYF72604 and it was able to create the package.

Re: RE: Upgrade to V5R2

Hmmm, I think your on the right track. Not sure what would have changed with the upgrade though. Grant

Re: RE: Upgrade to V5R2

Also, cpf2172 is an error in naming ASP's. Are you using multiple ASP's? Have you changed any command defaults to process ASP's?
Message ID . . . . . . . . . : CPF2172
Message file . . . . . . . . : QCPFMSG
Library . . . . . . . . . : QSYS

Message . . . . : ASPDEV value not valid with value specified for ASP.
Cause . . . . . : An ASP device (ASPDEV) value of *ASP is the only valid
value when ASP number (ASP) is any value except *ASPDEV.
Recovery . . . : Change the value of ASPDEV to *ASP or change the value of
ASP to *ASPDEV. Then try the request again.

Re: RE: Upgrade to V5R2

ok - we fixed it.

Evidently, when we were upgrading to V5R2, the IBM Engineer left behind some custom programs - including a custom CRTLIB program - I guess for auditing purposes. We realized this once we tried to manually create a library and it failed with the same error.

After removing the custom library, the RIGHT CRTLIB was being used, and everything kicked into gear again ! Definately a wierd one - and one that had me pulling my hair out all weekend !

Re: RE: Upgrade to V5R2

found this on the GSC if you want to add it to the list.

Title: Currency Problem in OneWorld® Applications on J.D. Edwards HTML Web Server with JIT Compiler for OS400 V5R1 and V5R2

Release(s): WebSphere Application Server

Platform(s): OS/400® (V5R1 and V5R2)

Issue: There is a problem with the JIT compiler for OS/400 V5R1 and V5R2. The JIT compiler problem causes currency errors in some OneWorld applications. The symptoms appeared when a user keyed in 100, it would show up as 10000 on the HTML application. The behavior was essentially moving the decimal place over two places. IBM has provided a fix for this problem.

Fix: If customers are experiencing application currency problems over HTML, then they should apply the following fixes as per their operating system platform releases:
V5R1 is fixed with PTF MF30704, and
V5R2 is fixed with PTF MF30784.