SOA Testing Overview

Quarterly Software Upgrade Cycle Sysprog test LPARS Flash copy DEV LPARS Flash copy PROD LPARS DEV LPARS PROD LPARS IVPs, customisation, exits, limited regression testing Developer testing Developer tools Only ACCT envt “Business testing” Development “is production” Service variance once per quarter. Sat 8pm – 6am Midnight testing Change controlled

SOA Environment WAS AIX JVM MQ OTMA DDF DB2 IMS MPR SP ODBA Z/OS

SOA Testing AIX development environments connect to development mainframe systems No equivalent flash copy test systems Use the ‘offline leg’ instead DR “Mega test” –Connects offline leg to flash copy systems –Reduces production resiliency –Requires cross platform coordination, skill sets, etc –Still tests only a small percentage of applications

Flash copy Environment MQ OTMA DDF DB2 IMS MPR SP ODBA No distributed Systems to drive the mainframe!

SOA testing Development systems are production Developers geared towards testing new stuff Development work has business sponsorship Software upgrades seen as ‘keeping the lights on’ What is more important?

SOA testing Application reuse is good but People writing code don’t know what they are driving on the mainframe Difficult to get/find the right people for an application Errors are difficult to diagnose Especially true for out of hours testing