× 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.



Pat,
This is a rather small program that simply uses the DDM connection to move data between systems.  The DDM line/file is max'd out at 16M, and the stats on the line is such that it isn't even being used at 50%.  However This process runs constantly, and the job is submitted on Sunday nights and runs all week.  One thing the program does do is use the QCMDEXC command to update a *dtaara with the relative record number it processed every 100 records, so this QCMDEXC is getting called all the time.  Could this do it?
----- Original Message -----
From: Pat Barber
Sent: Thursday, August 09, 2001 9:58 AM
Subject: Re: Most efficient AS400 physical file building ?

There are two possible problems, A: The speed of the line between the
two boxes. B: The application that is "moving" the data.
 
You didn't state if the systems were in the same room
or different locations. This makes a big difference when
communications gets in the picture. What method is used to
connect the two systems ??


The other possible problem is the method used to move the data.

Is this a giant cpyf application or is this a RPG program reading
and writing the data ??? DDM does not perform well in moving large
volumes of data, but it is excellent for random reads on a remote
file. DDM requires a fair amount of tuning to get every element
working in the right way. You almost design your application
around DDM and what it can and can't do.

It can degrade system performance in a big way if done incorrectly.






> Tim Truax wrote:
>
> Hi All,
> There's a process that I am analyzing that involves large volumes of
> data records arriving in one (system A) AS400 physical file. Then
> another (system B) AS400 that is attached to this physical file on
> (system A) via a DDM file which resides on (system B).  This process
> that runs on (system B) then uses this DDM file and simply transfers
> the data that arrived in the physical file on (system A).
> Lately this process that transfers data between the two systems is
> lagging behind to the tune of millions of records.  These lags are
> happening at heavy system use times.
>
> I am wondering if there is an (overlooked by me) CRTPF option that I
> could add to the (system B) receiving physical file when it's built
> weekly that would minimize this lag on receiving data records?
> ..possibly ALLOCATING THE STORAGE or something?
>
> I have been directed to simply break the process in two (duplicate it)
> in order that the 2 duplicated jobs could run concurrently on (system
> B), and then the (system A) physical file would require 2 file members
> in order to attach two different DDM files to.
>
> FYI) These AS400's I am talking about are not farty little boxes they
> are big AS400's.
>
> Any suggestions or comments appreciated.
> Tim Truax  :-)
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.