• Subject: Re: Creating new Environment
  • From: DAsmussen@xxxxxxx
  • Date: Thu, 1 Jul 1999 01:09:20 EDT


In a message dated 6/30/99 1:03:55 AM Eastern Daylight Time, 
davidavid30@hotmail.com writes:

> Does anyone have a list of steps that one needs to follow to create another 
>  BPCS environment on the same using the same programs, but different files.

Just off the top of my head, but here goes:

1.  Using either CPYLIB or RSTLIB to a different name, duplicate BPCSUSRF, 
BPCSF, and BPCSUSR into new names.
2.  CHGDTAARA SSASYS in its new library, position 170 for a length of 10, to 
point at the equivalent new work file library.  If your OUTQ and JOBQ library 
names don't already point to *LIBL in this data area, change them to their 
new equivalent.
3.  Change the three libraries in data area INLIBL to point to their new 
equivalents.  TAATOOL EDTDTAARA is quite useful for both this and step 2.
4.  Using WRKMSGF, change message ID L019301 in your new SSAZ03 to indicate 
the new BPCSF equivalent to indicate the new environment.
5.  Using DBU or DFU, change the "COMPANY" record in ZPAL01 as in 4.
6.  Edit BPCSMENU in the new library and change the hard coded library name 
to its new equivalent -- recompile in the new library.
7.  Change BPCSJOBD (or whatever job description you're using) in the new 
library to have the appropriate library list.

That's about it, although I may have left something out.  Pretty simple stuff.


Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-mail:  DAsmussen@aol.com
| 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

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].