|
E-mail from Al Macintyre at boss's PC at work ____________________________________________ Central Industries of Indiana, Inc. www.cen-elec.com (812) 421-0231 I've been thinking about Dave's nightmare - what a monster job he has & what alternatives might be available that we have not yet considered? Reconstituting the files so that the create date is correct, and contains the desired data, and what is the business going to do in the mean time while you have this humongous assignment & how will you test the results? There are a whole bunch of us on BPCS_L who have successfully got to BPCS_L & our files do not have this create garbage. Consider a scenario, if our bosses & SSA approve. One of us BPCS 405 CD sites whose business is not in competition with you (industrial espionage temptation for Dave M co-workers looking at our files), send Dave M a tape containing a recent backup of our files, or just the library that contains our live BPCS files. Dave restore our library --- we are not using the vanilla BPCS naming convention for library --- but if you get this from some outfit whose library name is same as yours, then consider renting time at IBM offices or some consultant to work a library rename. Do that work station clean-up to get rid of distractions, ONLY in what you get from us. Now copy YOUR DATA into OUR FILES replacing our data with your data. Do you now have a clean data base in which the create dates are correct & your data is the only data there? Well just in case we are not using the same mix of modules, perhaps you should CLEAR our files before starting this. You had found the problem with general ledger & there may be others where you need to combine data into what should be *FIRST from what really is *FIRST. Is that the only file with that problem, or are there others? There is some IBM DSP*** I do not remember which one that might get you a report listing all the files that have more than one member. Perhaps DSPFD *ALL files *MBR only to *OUTFILE for Query evaluation. How do you go about combining the stuff? This analysis just tells you the files & the members involved that need combining. Also we have modified some files, not in layout but in content, such as DOC. There's all the data area settings & we have altered some literals & we have our own custom menus - off hand I do not remember which of that is in the software objects library & which is in with the files or user libraries. Some of it could be incorrect. Basically you are using OUR library, or one from some other BPCS 405 CD site that has clean files from perspective of create date, for purposes of a test library, until you think you have all the problems fixed, then wipe everything out of your live library & replace it with this cleaned one & also use it as a master to fix the problems in the conversion path. Dave M is probably not the only would be BPCS 405 CD site faced with this nightmare. I think that having a trusted consultant in the picture would make life easier for Dave M & the next site to encounter this challenge & whichever SSA client supplies the clean files. GOOD GUYS send their files, not to Dave M, but to HELPFUL CONSULTANTS. The helpful consultants, do the clearing of the good guy data & get the library name to something that is guaranteed not in conflict with SSA existing library names. They keep a copy of the cleaned set, so that Dave M can get this, and also the next site facing the same problem. Perhaps they also supply a separate library of tools to help with the repairs, so that Dave M & his future peers do not have to re-invent all the same wheels. Al.M +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
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.