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



     We developed a custom print distribution architecture that runs 
     alongside BPCS to handle this and avoid manual spool maintenance.  
     Contact me at 973-357-3431 to inquire.
     
     Kevin Catlin
     Cytec Industries


______________________________ Reply Separator _________________________________
Subject: Workstation Data Areas
Author:  BPCS-L@midrange.com at Internet
Date:    5/25/99 6:20 AM


I am currently working on an implementation of BPCS 6.0.04. One of the many 
problems that I have encountered is the use of work station names for 
assigning printer / writer device name. Due to nature of our AS400 network , 
work station names are dynamically allocated. As a result the work station 
names 'move' around different areas of our plant and consequently output 
should be directed to different printer. I would rather not have to train 
users to work with their spool files. Has anyone got a solution to this 
problem.
     
Kind regards,
Gordon.
+---
| 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 st.cytec.com (164.84.1.253) by stnt01.cytec.com with SMTP
  (IMA Internet Exchange 2.12 Enterprise) id 0013AA57; Tue, 25 May 99 08:37:36
-0400
Received: from gw.cytec.com (igw.cytec.com) by st.cytec.com (4.1/SMI-4.1)
        id AA11752; Tue, 25 May 99 08:40:41 EDT
Received: by gw.cytec.com; id IAA18024; Tue, 25 May 1999 08:37:53 -0400
Received: from kitten.mcs.com(192.160.127.90) by gw.cytec.com via smap (3.2)
        id xma017666; Tue, 25 May 99 08:36:44 -0400
Received: from uucphost.mcs.net (Uucp1.mcs.net [192.160.127.93]) by
Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id HAA20391; Tue, 25 May 1999 07:36:44
-0500 (CDT)
Received: (from uucp@localhost)
        by uucphost.mcs.net (8.8.8/8.8.8) id HAA20515;
        Tue, 25 May 1999 07:36:43 -0500 (CDT)
Received: (from majordom@localhost)
        by midrange.com (8.9.3/8.9.3) id HAA13890
        for bpcs-l-outgoing; Tue, 25 May 1999 07:15:37 -0500
Received: (from uucp@localhost)
        by midrange.com (8.9.3/8.9.3) with UUCP id HAA13800
        for BPCS-L@midrange.com; Tue, 25 May 1999 07:01:04 -0500
Received: from host241.abbott.com (host241.abbott.com [207.140.194.241])
        by uucphost.mcs.net (8.8.8/8.8.8) with SMTP id GAA18193
        for <BPCS-L@midrange.com>; Tue, 25 May 1999 06:19:39 -0500 (CDT)
Received: by host241.abbott.com id GAA20183
  (InterLock SMTP Gateway 3.0 for BPCS-L@midrange.com);
  Tue, 25 May 1999 06:19:38 -0500
Received: by host241.abbott.com (Internal Mail Agent-2);
  Tue, 25 May 1999 06:19:38 -0500
Received: by host241.abbott.com (Internal Mail Agent-1);
  Tue, 25 May 1999 06:19:38 -0500
From: "Coen,Gordon" <gordon.coen@abbott.com>
To: <BPCS-L@midrange.com>
Subject: Workstation Data Areas
Message-Id: <0055600012196326000002L062*@MHS>
Date: Tue, 25 May 1999 06:20:09 -0500
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-Mime-Autoconverted: from quoted-printable to 8bit by midrange.com id HAB13800
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.