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



If it is possible try to check how the write is implemented, its better write bigger chuck of data at once, instead writing byte at byte (buffering)?
Second can be, is this file open as TEXT file or binary, I mean, before write is performed a data conversion can be called EBCDIC -> ASCII (i.e.).
Or you can look which Type is this File, usually are all IFS files created as TYPE2 (performance enhancements) instead of TYPE1 ...
I think the best, will be to start a PEX session to see what happens in the job, this must not be an write() problem ?

Regards
Peter

-----Original Message-----
From: c400-l-bounces+peter.daransky=uc4.com@xxxxxxxxxxxx [mailto:c400-l-bounces+peter.daransky=uc4.com@xxxxxxxxxxxx] On Behalf Of Boris
Sent: Montag, 23. Mai 2011 16:44
To: c400-l@xxxxxxxxxxxx
Subject: [C400-L] Write to IFS file - high CPU

I have a program that copies a DB2 file into an IFS stream file.
It may process millions of records.
The problem is that the program consumes high CPU (more than 90%). I removed all the processing and only left the read from the DB2 file and write to the IFS file functions. The program stack shows the write function almost constantly so I assume the write function is the one to blame.
What is the best way to implement a solution like that?

Thanks
Boris.



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.