Re: Excess BPCS file members

[fkolmann@xxxxxxxxxxxxx]

Chris Certz wrote:

> Using virtual devices on any version of BPCS can be a nightmare.
>
> I have written programs that load the workstation data area from a file by
> user profile. This way no matter what workstation you signon; your settings
> are the same.
> Also, I have gone to a new version of client access which allows named
> devices using TCP/IP.

Chris We too modified the setup of the Workstation data area, and the
remembered keys to be driven by user profile. We allow BPCS to do its thing
then slip in a program that retreives the settings by User Profile.
AND we also are using TCP/IP CA on a Novell Lan that allows fixed WS names.
Dont ask me how the PC boffins take care of all that.
ALSO we  had big problems with the way BPCS controls spool files.
A simple example follows.
Invoice printing should send invoices to a special printer.
Any exception reports go to another printer.
There seems to be no way to distribute reports to different queues within the
same job. Report distribution in BPCS is basically non existant. Took us a
while to rejig things to get something workable. Basically we have a control by
job/program/user and send the report to a specific queue using SNDNETF. The
details are rather messy.  BPCS has different names for the same job depending
on if it is run in batch or interactive. Also we need unique spool file names
for every report. This is usually the case with BPCS, some oy our inhouse
programs needed changing (they used QSYSPRT), and we had to clobber the BPCS
global OVRPRTF *PRTF.

A point I am making is that there seems to be much reinventing of identical
wheels as your and our mods to WS dtaaras shows.  Perhaps this can all by
synched with the wonders of the Internet.

+---
| 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
+---