It can be used to generate where used (most) all fields in all files by all
programs, into what I call "door stop" reports. We do not use it because
SSA tech support told us the only way to make it work was to change the
ownership of BPCS files to everyone is a master security officer.
Instead I have one of those DSP cross-index to *OUTFILE created by GO
CMDREF, then use query/400 on object name to find out where it is
referenced. When you run that, be sure to include all libraries of all
software vs. BPCS, which may be more libraries than just where the files
are. We have some source code outside the standard library list.
This not help much with respect to what the heck those fields are used for,
what all the codes mean, and which ones we can use for other purposes,
without breaking BPCS. To answer that, you need either one of the good BPCS
reference manuals, or one of the good tech support places.
I said "(most) all".
The system kind of breaks down when the references are "soft coded", where
some software involved is specified at execution time, and not "hard coded"
in what can be REF'd.
[mailto:bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx] On Behalf Of Info
Sent: Wednesday, September 15, 2010 1:16 PM
Subject: [BPCS-L] BPCS File List
I saw somewhere on this mailing list that somebody has a complete file list
of BPCS in Excel. I?m currently at the starting point of planning a new
project with BPCS and need a the list of files to find some informations.
Please can somebody sent me the list to info(a)madaca.de?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.