× 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: RPG Programming Question
  • From: MacWheel99@xxxxxxx
  • Date: Fri, 20 Oct 2000 05:06:04 EDT

A real programmer knows about EDTLIBL & rearanges library list of their 
current sign on for themselves without asking for this from someone else.  Is 
the question that this is being asked on behalf of everyone who uses BPCS?  
Potentially dangerous.

Take a look at your documentation for separate environments & library lists.

You should have a standard way to test BMRs, PTFs, Releases & your own 
internal modifications, that is setup by people who understand BPCS.

Then as each development person arrives on site, stuff is done in a 
consistent way that you know works.

We use a separate libraries for development work, keeping new files in 
different library than new programs, because the programs can share 
environments, but the files can not.  Then when we implement mods, we arrange 
things so that we can back them out if reality illustrates something 
unacceptable that was not discovered by the testing.

bennygene@usa.net writes:

> the programmer should explicitly place the overriding file to the
>  library which contains the bolt-on programs database file.

Well since I am now the only programmer, I am not too keen on this approach, 
because when the tests are satisfactory, I do not want to have to change the 
code to implement it in the live environment.  What I do is RTV object with 
parameter identifying library that it is in, then when test is OK, I rename 
the source in our library of approved modifications (rename not delete in 
case we later need to back out the mod) and copy the recently tested version 
into the approved mods library in our library list, so the RTV now gets a 
different library & the code not need to be changed.

You see, I know I do pretty good, but ANY TIME we change something, there is 
a chance of making a mistake.  Why test that it is perfect then have to 
change it again after testing to implement it?

Depending on nature of what is being tested, we either use test environment, 
or add test library to live environment via ADDLIBLE before & RMVLIBLE 
manually around the program step being tested.  Remember ADDLIBLE default is 
*FIRST.

Alister William Macintyre 

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