|
-----Original Message----- From: Winder Marcia <Marcia.Winder@CIBC.com> > >We are currently running V4R1 on our system, the software I asked about >though is 3rd party. One version of the 3rd party software must communicate >with our mainframe in a production environment. The other version is in a >test environment which does not need to communicate with the mainframe. >However, we must maintain the same file and library names in both >environments. The only way we figured to do this was to partion the disk. >ANY IDEAS??? Why do you have to have the same library names? Are they hard-coded in the programs or something? Typically this sort of thing is handled by putting the test versions in separate libraries and using different library lists. I don't really think there's another way to do it on the same machine until LPAR on V4R4, IF you have multi-processor machine. --- Dave Shaw, General Nutrition, Greenville, SC To subscribe to the MAPICS-l mailing list send email to MAPICS-L-SUB@midrange.com The opinions expressed may not be my employer's unless I'm sufficiently persuasive... +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.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.