Al Sherkow wrote: >Do you have a lot of JAVA and WebSphere in your shop? ABO will >be licensed based on those MSUs too.
Not always or even very often. For example, Solution Editions are outside scope (unless they have EC3/4-compiled COBOL -- rare but possible), and so are zIIP MSUs and non-peak MSUs. I'd offer this advice instead: Automatic Binary Optimizer (ABO) is likely attractive if you have at least "non-trivial" peak COBOL workloads compiled with Enterprise COBOL Version 3 and/or Version 4 in at least one z/OS "pricing-plex"(*) in your enterprise, and if you are not shifting most or all of those peak COBOL workloads relatively soon (or sooner) to Enterprise COBOL Version 5 or higher compiled code. ABO can also be attractive if you have CPU-bound batch COBOL workloads (compiled with Enterprise COBOL V3 and/or V4) and if you are looking to reduce batch processing times, and/or in a few rare cases when elapsed transaction times are critical (e.g. credit/debit card authorizations) -- again assuming you are not shifting relatively soon (or sooner) to Enterprise COBOL Version 5 or higher compiled code. Note that the EC3/4-compiled code can be vendor-supplied, in-house, or both. All EC3/4 COBOL run-times count, including COBOL stored procedures in DB2. Also take into account older COBOL code that is being migrated to EC3/4 (or should be, or will be). Sorry that's a bit wordy, but I think it's a reasonably comprehensive summary in one paragraph. "Java bad" for these purposes? No, that's oversimplified at least. Just focus on the EC3/4 COBOL (including vendor-supplied) and its contributions to peak, to batch elapsed time, and to elapsed transaction times. That's conceptually simple, too, but also better advice in my view. (*) This isn't *quite* right either. There are cases when less than a "pricing-plex" is enough, but now I'm really getting into the weeds. :) However, I'm tempted to put "LPAR" here for these reasons. "LPAR" is certainly enough for a "merits investigation" standard. -------------------------------------------------------------------------------------------------------- Timothy Sipples IT Architect Executive, Industry Solutions, IBM z Systems, AP/GCG/MEA E-Mail: [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
