Re: Avoid CPF0864 by counting records and POSDBF: NOT WORKING! -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Avoid CPF0864 by counting records and POSDBF: NOT WORKING!
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Wed, 28 Apr 2010 14:48:51 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

If the ODP created by the OPNDBF is still active when the file needs to be deleted, then the request to CLOF [close file] that ODP before DLTF should allow that delete file request to complete without seeing the escape message CPF3220 OT1; i.e. given the implicit close [of the second\shared open] was effected previously, per having received the noted CPF0864.

Regards, Chuck

Dan wrote:

<<SNIP>> app deletes and recreates the E2VAULTDIR, and once I restored the OPNDBF and kept the file open, the statement to
delete the file after it was opened failed. <<SNIP>>

As an Amazon Associate we earn from qualifying purchases.

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