Danger of this becoming another ABO thread in disguise :-) The question of the testing of ABO is not entirely cultural, or not necessarily so. Nor necessarily "compliance". There can be a technical basis on which to make decisions, which cultural and compliance issues may make moot. I'm keen to poke for the technical basis, of which there are not much more than hints and generalisations for now :-)
It's like developing a strain of peas which pick themselves when ready, pack themselves and stack themselves in boxes on the trailer. So will stick to "the One True Way to cultivate peas", some will stick to "the only way the rules allow to cultivate peas". Some will get on with more interesting stuff whilst the peas look after themselves. That latter group will be small if there are no detailed instructions on the sacks of seed. IBM's intention going forward is that ABO and Enterprise COBOL are a complimentary package. New ARCH level, new compiler (or PTF to existing compiler), new ABO. You don't need to recompile everything to use the new instructions immediately, you can ABO (even perhaps "on the fly"). New development/maintenance uses the new compiler. "Migration" becomes... A cultural and real-world (compliance) impact for sure, but if the technical basis has no more known grounding than the Witchdoctory One True Way then it won't happen on any scale. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
