In a message dated 9/27/2006 9:26:56 A.M. Central Standard Time, [EMAIL PROTECTED] writes:
You're right. It turns out to be MAP (at least I think so) that is the killer -- the pseudo assembler listing (is that turned on by MAP?). I just took a look at a compile that I use as a standard benchmark for our virtual compiler (www.syspointusa.com if you're interested). I don't claim it is THE >> Yeah, guess we're really talking about two things as Jim Marshall indicates. One is speed of compiles and use of processor cycles for debuggging. Remember the days of desk checking and code review? Anyway, vendor code/shop standards whatever need to be assimilated into the mix. I've been in shops that required Listings and Maps of every production program. Sometimes it was paper, sometimes fiche, sometimes CD(Filetek) but hardcopy anyway. No matter how clean it runs in test, real data from real devices and real TP lines is subject to nefarious factors of physics and Murphy. I was standing in the checkout line in the super market last night as the high school clerk banged on the new color printer after a paper jam. Eventually causing the store server to lock up and reboot....only took about 45 minutes to buy juice, oatmeal and bottled water....not that that listing wouldn't come in handy%-) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
