|
There are many concepts used to run multiple versions of the same software on the AS/400. The most common method is library lists. I do not know your background of experience and what you are trying to accomplish. If you're a PC whiz then library lists may be compared to the DOS PATH statement. One of the biggest factors to consider is are libraries hardcoded in the program? For example we have multiple versions of SSA's BPCS on the same AS/400. Let's assume that your canned software for version 1 is in library CANNED1, version 2 is in CANNED2. Your mods are in MOD1 and MOD2. Your data would be in DATA1 and DATA2. Your library list, while working in version 1 might have: QGPL, DATA1, MOD1, CANNED1, QTEMP. Your library list while working in version 2 might have: QGPL, DATA2, MOD2, CANNED2, QTEMP. This works great if you do NOT hardcode library names. If you do hardcode library names, then stop and fix all of your programs. Otherwise then using multiple ASP's won't even buy you anything. You'll have to use logical partitioning under V4R4, which isn't out yet. Frankly using logical partitioning is a lot of overkill to overcome bad programming. +--- | 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.