Re: Multi-processor machines.

Bob Larkin wrote (in part):

>The big question is ... Why does this job take so long?!?!?
>Improper design can cause a problem, but often very small changes can
>make a BIG difference. Just this week, I wrote a program wiith less then
>ten lines of executable code (COBOL). This program was added to the job
>stream of a job that ran 11 HOURS (660 minutes). The run time was
>reduced to 17 MINUTES. Rather dramatic :)
>Problem was that a RPG program was calling a COBOL program repeatedly.
>Due to the way the system handles program initiation/termination , a
>COBOL program encapsulating the process eliminated a BUNCH of overhead.
>One client regularly process 80 Million transaction batch jobs with
>heavy computation. Performance is greatly enhanced with the use of the
>Caching available through the system.



We've had a COBOL program at the top of our batch subsystems for years:  it
just does a CALL QCMD and ends.  This ensures that there's -always- a COBOL
program at the top of the invocation stack, which prevents problems with
RPG calling COBOL not ending properly because there's no COBOL at the top.

--Paul E Musselman
PaulMmn@ix.netcom.com


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *