E1: PKG: Performance Issues When Build Packages From The Deployment Server - iSeries Platform

(Doc ID 631997.1)

Last updated on JULY 17, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version SP24 and later
Information in this document applies to any platform.

Goal

AS400 iSeries platform in all scenarios.

Scenario 1

Customer has recently added a processor, memory and disk space to their Deployment server, but the Client side of full package builds still takes about 9 hours, with poor performance. They've noticed that the job on the AS/400 continuously changes status from RUN to DEQW instead of running most of the time.
Is that normal or should it be in RUN status a higher percentage of the time? They're trying to figure out what is slowing this process down. Customer suspects that the Deployment server may be waiting on the AS/400.

Scenario 2

Package Taking a Long Time to Build on AS/400 - (i.e. gbrspec transfer taking 6 hours). Customer is building a full package for an AS/400 enterprise server and it's taking longer than normal to build. Looking at the logs it was taking 6hrs just to transfer the gbrspec.pak file from the deployment server to the enterprise server.

Scenario 3

Performance Issue on iSeries platform. Full Server Package Build on an AS400 server hangs after transfering a few .pak files from the deployment server to the enterprise server. There are no errors in the jde.log. A Server Update Package seems to work fine.

Scenario 4

Full Server Package Build on an AS400 server taking a really long time to copy spec table records from the build machine to the server spec repository Central Objects datasource or from the server spec repository Central Objects datasource to the build machine.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms