Re: Upgrade V4R4 to V5R1 - Performance Problems

["Mark Waterbury" <mark.s.waterbury@xxxxxxxxxxxxxxxx>]

You might also try this:

Submit a STROBJCVN for each user (not system) library, e.g.:

    SBMJOB CMD( STROBJCVN LIB(xxxxxxxxxx) +
        OBJTYPE(*ALL) ) JOB(xxxxxxxxxx) JOBQ(singlethread)

to run in batch. This will ensure that all objects in each library are
fully converted to work best with the latest release of OS/400 on
the box.  NOTE: you might want to run this in a single-threaded
job queue, so that you don't get too many of these jobs going at
once, as they will "fight" with each other for CPU etc.

That would tend to "clear up" the mysteries if objects are being
converted on "first touch", which could explain why things might
seem to run "slower" the first time you use any given object, after
the upgrade...

----- Original Message -----
From: "Vern Hamberg" <vhamberg@centerfieldtechnology.com>
To: <midrange-l@midrange.com>
Sent: Friday, November 15, 2002 11:15 AM
Subject: Re: Upgrade V4R4 to V5R1 - Performance Problems


> I think there were changes to file structures in V5R1 - do the open
queries
> run faster the second time?
>
> Vern
>
> At 10:35 AM 11/15/2002 -0600, you wrote:
> >Approximately 1 1/2 months ago, we made several changes to our AS/400,
> >knowing multiple changes was a risky thing to do.
> >
> >Changes:
> >
> >Moved from a 730 to 820
> >Upgraded from V4R4 to V5R1
> >Switched to EMC external DASD
> >
> >One problem we are focusing on with IBM is 'open queries' do not seem to
be
> >performing properly.  One job that used to take 30 minutes is taking 4-5
> >hours.
> >When the record is on the file, but the open query does not select that
> >record, it seems to run forever.
> >
> >I'm guessing we may have other performance issues, but not at the above
> >magnitude.
> >
> >Another problem, is restores seem to take longer on the new AS/400.
> >
> >Has anyone else experienced similarly problems?
> >
> >Thank you,
> >Michele
> >
> >
> >
> >
> >_______________________________________________
> >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> >To post a message email: MIDRANGE-L@midrange.com
> >To subscribe, unsubscribe, or change list options,
> >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> >or email: MIDRANGE-L-request@midrange.com
> >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@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>