Re: Dealing with CPE3029 in CPYFRMIMPF -- MIDRANGE-L

× 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: Dealing with CPE3029 in CPYFRMIMPF
From: Patrik Schindler <poc@xxxxxxxxxx>
Date: Fri, 29 Aug 2025 00:32:36 +0200
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Hello Mark,

Am 28.08.2025 um 22:13 schrieb mlazarus <mlazarus@xxxxxxxxxxxx>:

The situation is that there are .csv files in the IFS that might be open in Excel. All the program is attempting to do is copy the data into a PF. It seems to want an exclusive lock.

Another idea, inspired from Peter's reply.

Do you need those CSV files being writable by Excel? If no, why not make this folder/share readonly for users? If Excel sees the file being readonly, it presumedly can't or at least won't request an (exclusive) write lock on it.

:wq! PoC

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Dealing with CPE3029 in CPYFRMIMPF , mlazarus

This mailing list archive is Copyright 1997-2025 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.