BPCS file names & *LIBL RE: Missing CEA Accounts -- BPCS-L

You cannot block every boo boo, but you can block a lot of risks.
Here are some suggested semi-solutions.

We created a library just to receive user work files from query and 400 *OUTFILES and have several queries that people can copy from when creating their own similar functions. This means that, assuming users follow our suggested template, we are not going to have their creations earlier in the library list than BPCS potentially affecting all BPCS users, and if they do pick same name as a BPCS file, lower risk that this action wipe out BPCS file.

90% of our queries are in a generic library shared by the whole company. A few users are self conscious about other people seeing their unfinished work product, and some department data somewhat confidential from other departments. So we also have libraries for private query work, and the library list does not have them in front of BPCS files.

When we ADDLIBLE some library to our library list, the default 400 settings are to put that library in front of the BPCS library list. One could write a CL program which says *LAST instead of *FIRST for adding to library list anything that does not need to be first. We have MANY 400 commands to run from our BPCS menus via CL programs.

We have added some documents to BPCSDOC
One of them is called QRYTECHNIQ

It has write-ups how to do various things like date math; sort by absolute value, make dates look nice on screen (query default is YY,YYM,MDD) naming one or more of our queries that does this or that, which other people might want to transcribe the technique when you doing this for first time - Al Macintyre

, you wrote:

Thanks to those who responded to this.  We did find the issue late Monday. A
user had run a query to create a partial extract of the GCR file.
Unfortunately, the output file was also called GCR and she placed it in a
library that was earlier in her library list than the production files.
Therefore, CEA was using a bad GCR file and giving us strange results.
Renaming the file cleared up the issue.  We are now reexamining security on
our libraries!

Regards,

Jim Reinardy

- Al Macintyre http://www.ryze.com/go/Al9Mac Find BPCS Documentation Suppliers http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html BPCS/400 Computer Janitor at http://www.globalwiretechnologies.com/

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.