Re: ACR900 - too long

Hi Everyone - 

Genyphyr is correct in that the most likely issue with such a long runtime is 
database
I/O. There are many solutions to this type of problem but it would require more 
analysis
to identify all of the files involved, the number of logical files, the order 
of the data,
the access pattern of the application, etc. 

Centerfield has a long history with helping BPCS customers tune the application 
to the
environment and to the way the database is used.  We could certainly help with 
you with
this. 

All my best,
Jen
______________________________________________________
 Jenniefer Halverson  |  Director System i Client-Partners
                                507.287.8119 EX 101
                     jhalverson@xxxxxxxxxxxxxxxxxxxxxxxxx
  Centerfield Technology    Rochester, Minnesota   USA   55901
                   http://www.centerfieldtechnology.com


 

-----Original Message-----
From: bpcs-l-bounces+jen=centerfieldtechnology.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+jen=centerfieldtechnology.com@xxxxxxxxxxxx] On Behalf Of 
Genyphyr
Novak
Sent: Monday, March 20, 2006 10:39 AM
To: bpcs-l@xxxxxxxxxxxx
Subject: Re: [BPCS-L] ACR900 - too long

Hello, 

If you are on BPCS CD, the suggestion mentioned below by Davide is
irrelevant, as there is no SQL in that release of BPCS (unless you put
some in yourselves), it only works SQL releases. Have you checked for
duplicate records in all the affected files? Sometimes if these are
present it will cause jobs to run a lot longer and have abnormally high
I/O counts on the affected or related files. I suppose if you had SSA
support you would have already called this in to the support center for
analysis? So, if you do not have support and you do not have duplicate
records, you can always try using the AS/400 performance tools to
analyze the program to find the bottle neck, do some analysis and try to
change the code to suit yourselves. Or hire an SSA consultant to come
out to analyze the program for you to improve it.

Thanks,
Genyphyr Novak
Senior System Software Engineer
SSA Global R&D

-----Original Message-----
From: bpcs-l-bounces+genyphyr.novak=ssaglobal.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+genyphyr.novak=ssaglobal.com@xxxxxxxxxxxx] On
Behalf Of bpcs-l-request@xxxxxxxxxxxx
Sent: 18 March 2006 19:00
To: bpcs-l@xxxxxxxxxxxx
Subject: BPCS-L Digest, Vol 4, Issue 65

Send BPCS-L mailing list submissions to
        bpcs-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.midrange.com/mailman/listinfo/bpcs-l
or, via email, send a message with subject or body 'help' to
        bpcs-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
        bpcs-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific than
"Re: Contents of BPCS-L digest..."


*** NOTE: When replying to this digest message, PLEASE remove all text
unrelated to your reply and change the subject line so it is meaningful.

Today's Topics:

   1. Re: ACR900 - too long (Davide Roveda)


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

message: 1
date: Sat, 18 Mar 2006 17:22:13 +0100
from: "Davide Roveda" <Davide.Roveda@xxxxxxxxxxxxx>
subject: Re: [BPCS-L] ACR900 - too long

Hello

The way to make a real check of SQL performance is: Let Iseries do for
you: 

In this way: