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



Chuck,

Thanks. I thought CPYF could do this. What they want is a baseline
file in the morning, and updates/adds throughout the day. I use two
files, first for baseline, and second for adds/updates. But, they
want now (or seem to) is more frequent update files. Doesn't have to
make sense. More smaller files throughout the day. My thought was to
apply the first update to the baseline file prior to the next run.
File is DDS and currently does not have the UNIQUE keyword, although
the account number is a keyed field and is essentially unique. The
CPYF complained. I added UNIQUE and also FMTOPT(*NOCHK) result was
413 records copied 1094 records updated.

Simple.

John McKee

On Wed, May 30, 2012 at 12:19 PM, CRPence <CRPbottle@xxxxxxxxx> wrote:
On 30 May 2012 09:00, John McKee wrote:
We have a process that locates records meeting specified criteria.
Data is written to a file and sent to a vendor. Hours later, same
process is run again, but only new or updated records are sent.
Vendor now wants the second process run multiple times throughout
the day.

I know I can write a program to add new records and update existing
records in the morning file. Can CPYF do this? Is there a "better"
way to accomplish this?

Vendors want results yesterday, so it seems.


  CPYF can use MBROPT(*UPDADD) for a uniquely keyed file, to effect
replacing the old key with the new row, and adding any new keys\rows.

  However I am not sure I would interpret the vendor intent that way.
Might be best to seek clarification.

Regards, Chuck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.