× 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: bpcs 6.1 tuning / clearing work files
  • From: Geoff_Start@xxxxxxxxxx (Geoff Start)
  • Date: Wed, 16 Feb 2000 11:54:50 -0500

     Stating the obvious I know, but only clear ZPD records with 'PZ' in 
     the id field....Others hanging around may need investigating.


______________________________ Reply Separator _________________________________
Subject: bpcs 6.1 tuning / clearing work files
Author:  "Chick Doe" <Cdoe@barton-instruments.com> at Internet
Date:    15/02/00 18:06


i read with fascination the posting from Peggy Heritz about clearing several 
bpcs work files when the system is not being used. we have a nightly job that 
clears several of these files (CLRPFM   ECHW,ECLW,ZEF etc). we learned about 
these the hard way when we were having conflicts within the order entry system. 
     
i looked at our system and we are not clearing the following files. would it 
make sense to also clear these files each evening when the system is down and 
nobody is on it?
     
ZPD
EWR
ZQWAP
ZQWRP
ZQWSP
     
if these are truly work files i see no harm in clearing them each evening. does 
anybody have any cautions, concerns, or comments, for what it's worth we are 
using version 6.04 in mixed mode. all applications are green screen with the 
exception of order entry (uses the configurator) and CEA.
     
and finally, where or where might i find a discussion of topics such as this 
within the SSA literature?
     
thanks
     
chick doe
barton instrument systems
     
     
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com. 
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. 
| Questions should be directed to the list owner: dasmussen@aol.com
+---
Received: from ccgate.bausch.com ([161.242.3.9]) by ccgate.bausch.com with SMTP
  (IMA Internet Exchange 3.11) id 000010A5; Tue, 15 Feb 2000 21:40:05 -0500
Received: from 192.160.127.93 by ccgate.bausch.com (InterScan E-Mail VirusWall
NT); Tue, 15 Feb 2000 21:40:05 -0500 (Eastern Standard Time)
Received: (from uucp@localhost)
        by uucphost.mcs.net (8.9.3/8.8.8) with UUCP id UAA13108;
        Tue, 15 Feb 2000 20:39:44 -0600 (CST)
Received: (from majordom@localhost)
        by midrange.dynip.com (8.9.3/8.8.7) id UAA12839
        for bpcs-l-outgoing; Tue, 15 Feb 2000 20:10:14 -0600
Received: (from uucp@localhost)
        by midrange.dynip.com (8.9.3/8.8.7) with UUCP id UAA12822
        for BPCS-L@midrange.com; Tue, 15 Feb 2000 20:10:11 -0600
Received: from gwia (gwia.barton-instruments.com [209.241.17.166])
        by uucphost.mcs.net (8.9.3/8.8.8) with SMTP id UAA10192
        for <BPCS-L@midrange.com>; Tue, 15 Feb 2000 20:07:42 -0600 (CST)
Received: from GATEDOM-Message_Server by gwia
        with Novell_GroupWise; Tue, 15 Feb 2000 18:06:54 -0800
Message-Id: <s8a995be.073@gwia>
X-Mailer: Novell GroupWise 5.5
Date: Tue, 15 Feb 2000 18:06:25 -0800
From: "Chick Doe" <Cdoe@barton-instruments.com>
To: <BPCS-L@midrange.com>
Subject: bpcs 6.1 tuning / clearing work files
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by midrange.dynip.com id
UAB12822
Sender: owner-bpcs-l@midrange.com
Precedence: bulk
Reply-To: BPCS-L@midrange.com
X-List-Name: BPCS Users Mailing List (BPCS-L@midrange.com)

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.