× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: SSA, BPCS, RISC and "HelpLine" and "last release supported...
  • From: DAsmussen@xxxxxxx
  • Date: Tue, 30 Sep 1997 19:55:58 -0400 (EDT)

John,

In a message dated 97-09-30 04:41:19 EDT, you write:

> The "From" box was a 300-2042 and the "To" box is a 500-2142. We were
>  led to beleive that things would be not quite twice as fast. Our
>  Inventory Inquiry went from an average of 11.2 sec to 11.5 seconds!
>  Everything else was pretty much the same timing wise.  

Ooooh.  You did a pretty much equivalent swap on boxes.  Most CISC-RISC that
I've heard of upgraded the target box significantly over its CISC equivalent.
 We went from a 320 with two processors to a 530 with four (and nearly twice
the DASD) with no performance degradation.  RISC runs batch jobs faster, and
interactive jobs slower.

>  IBM installed the box themselves, but can't seem to get it to operate
>  any faster. They've been in several times with no luck.  SSA hasen't
>  really tried to fix it yet, but they have committed to getting it
>  working right.

Yeah right!  SSA, who won't "certify" BPCS for RISC or security level 40, is
going to "fix" your performance problem.  Is this the SAME SSA that replaced
CHAIN statements with SQL single record FETCH statements to "improve
performance in the UNIX environment, no effect plus or minus on the AS/400"?

>  I haven't placed blame fully on SSA, but I do think that both IBM and
>  SSA need to come together here and figure things out!!!

You didn't mention your release level, but I would suspect SSA has something
to do with your performance problem.  Per earlier posts on MIDRANGE-L from
others, I'd also check the value of the QDYNPTYSLT (sp?) variable on the RISC
box.  The latter changes a job's priority at the system level based upon the
processor's perceived need, and DOES NOT show up in the job's viewable
priority.  I assume that you are NOT running factory presets for memory pool
allocation and subsystem pool assignments.  If you're running a query tool
and/or one of the SQL-intensive BPCS releases (5 or 6), you might also want
to check into activating SMP.

That's all I can offer on the information given.  Feel free to write directly
if you have more specific questions...

Regards!

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@AOL.COM

"The trouble with life in the fast lane is that you get to the other end in
an awful hurry." -- John Jensen
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to "BPCS-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe BPCS-L' in the body of your message.
| Questions should be directed to the list owner: dasmussen@aol.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.