|
We just upgraded our development box to v5r2, and our production box is going to be at v4r5 until sometime next month. Since we have a time-consuming QA cycle, the last thing we want to do is to inadvertantly develop new code that doesn't compile at v4r5. Is using ChgCmdDft TgtRls(v4r5m0) for all of our compile commands the best way to "remind" us? Some of us are chomping at the bit to try out some new features that will make our job a lot easier, primarily the new error handling opcodes. When our production box is upgraded to v5r2, would we just issue another ChgCmdDft, this time using TgtRls(*Current), for all of our compile commands? TIA, Dan __________________________________________________ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.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.