Are you (also) asking how to identify candidate workloads that could be re-engineered, hopefully with little effort, to exploit zIIPs and/or zAAPs? If that's the question, here are a couple ideas:
1. Look for any Java code that may be executing, and classify those workloads according to the Java releases they use. Then start work on moving the biggest workloads running on the oldest Java releases to at least SDK 5 and preferably something much newer. Keep repeating this exercise to stay current on Java releases. IBM's SDKs for Java did not start to exploit zAAPs until 1.4.1-something or 1.4.2-something. 2. Review the current list of IBM and third-party zIIP and zAAP exploiters and their release levels, and see if any correspond to workloads you're running or could be running. Update accordingly. 3. Look for bulk data movements (notably FTPs) that could be re-engineered with more selective, direct data access. JDBC/ODBC access directly to DB2 (V8 and higher) exploits zIIPs, of course. There are typically strong security benefits and storage cost savings for this sort of re-engineering, too. Additionally, relatedly, consider adopting the DB2 Analytics Accelerator. -------------------------------------------------------------------------------------------------------- Timothy Sipples Resident Enterprise Architect (Based in Singapore) E-Mail: timothy.sipp...@us.ibm.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
