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


  • Subject: Re: Maintaining current BMR's
  • From: MacWheel99@xxxxxxx
  • Date: Fri, 31 Dec 1999 08:24:46 EST

>  From:    ScottConsBPCS@aol.com

>  The BPCS BMR experience is a pain in the ### but, there are a couple of 
ways 
>  to make it easier.  As was mentioned earlier, only apply the bmr if you 
find 
>  the problem.  

> Also, when you order a bmr, you can do a DSPOBJD of the *PGM's 
>  in the bmr and the BPCSPTF library to an outfile and then use query to 
join 
>  the two files together via program name.  If the source dates are 
different, 
>  then those are the only programs that you have to test and then apply.  If 
>  the source dates are the same, then, the program you are currently running 
> is the one that is on the BMR tape.  

I have found PDM-54, which Bruce Barker told me about, to be invaluable, when 
merging source code of Bmr & our modifications.
You get to the source in PDM of the latest source from SSA, or your in-house 
modification, and option 54 compare it to the prior source from SSA, that we 
modified & we get a list of the lines of code that got changed ... so do that 
for theirs & ours to see which is the least lines of code to copy to the 
other,

>  The way the BMR explosion works is that you get EVERY program associated 
> with the BMR that you order.  In most cases (if you are not too far back on 
CUM 
>  tapes, you will be running the programs that are included in the bmr).  
>  
>  I agree it is a daunting task.  
>  
>  Jeff

I like the dump to *OUTFILE to QUERY idea ... I had been laboriously copying 
a list of objects in each BMR collection to a consolidated list of additions, 
then comparing that with our modifications library to find connections, and 
similarly comparing what came with a BMR to previous BMR libraries on our 
system to find overlaps.  This can get to be time consuming, but it avoids 
replacing a fix with an earlier version & not realizing it.

Al Macintyre  ©¿©
Y2K is not the end of my universe, but a re-boot of that old chinese curse.
The road to success is always under construction.
Sanity is the playground of the unimaginative.
Every software improvement comes with some new challenges.
When in doubt, read the manual.
+---
| 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 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.