We established our z/VSE strategy around 2000. It is still up-to-date and I see no need to change it in the future.
The z/VSE strategy is based on three keywords
... or it is as simple as PIE.
Protect existing customer investment, that is we design z/VSE improvements in a away, that existing
applications and system environments do not need to change. We work closely with vendors (ISVs) to ensure that the impact
to their products is kept to a minimum as well.
If we introduce new interfaces, we first verify, if such an interface is available on z/OS - and if so, we port it to z/VSE.
Timely hardware support helps to enable z/VSE customers grow and exploit the latest System z hardware and devices.
Integrate z/VSE into the larger IT network. z/VSE interoperability is supported by two complementary capabilities.
One includes priced middleware such as CICS Transaction Gateway, DB2 Client / Connect, or WebSphere MQ.
The second capability includes connectors and web services provided at no additional charge by z/VSE itself.
With connectors it is possible to access nearly all z/VSE resources from non-z/VSE platforms in a secure manner.
Extend core applications running on z/VSE with new application options not available on z/VSE,
for example WebSphere, Java, DB2 UDB, development tools.
We especially benefit from the Linux on System z environment, which allows to simplify the network infrastructure
and consolidation of workloads with the help of z/VM's virtualization capabilities.
More details are on our z/VSE Strategy page