IT Management

Pete Clark on z/VSE: z/VSE 4.1

2 Pages

On Jan. 9, 2007, IBM announced that March 16, 2007 is the official availability date for the latest and greatest z/VSE—z/VSE 4.1. Although there isn’t sufficient space here to cover all the details of the new functions and facilities contained in z/VSE 4.1, I will present some of the highlights. For more details on z/VSE 4.1, as well as the new software pricing options, visit the z/VSE Website at

z/VSE 4.1 Highlights

What is in z/VSE 4.1, why is it important, and what is its impact?

While z/VSE 4.1 should impact the pundits that have continually predicted z/VSE’s demise, it probably won’t affect them, as they may not view 4.1’s enhancements as being noteworthy. However, we know differently, and can appreciate support for the latest and greatest CPUs, disk drives, tape libraries, connection architecture, and communications facilities.

z/VSE 4.1 provides 64-bit real storage addressing, with up to 8GB real storage for a single z/VSE image. Now every z/VSE user I know can run z/VSE in real storage, doing away with the overhead and performance issues of paging.

Certainly hardware/software support for the Crypto facilities, including tape, remote communications, Secure Sockets Layer (SSL), etc. means that z/VSE is a current viable modern processing platform? Yes, I think so.

Well, if that’s not enough, how about Large Volume Support (LVS) 3390s with 64KB worth of cylinders, think 54GB (approximately) each and the ability to use the Tivoli Storage Manager to back up and restore data via a network. I sure hope that’s a broadband network, using Open Systems Adapter-Express2 1000BASE-T Ethernet and the new encryption support as well as the new VSAM Capture Exit for data synchronization.

If FTP is preferred, then support for Secure FTP (think SSL FTP) and AES for 128-bit keys will enhance transmission data security.

To further confuse the death pundits, z/VSE 4.1 delivers more than 35 user requirements for POWER enhancements, client authentication, IUI enhancements, VTAM 31 bit I/O buffer support, etc.

Enough already; we’ve confused the pundits beyond reason. How about some important details for current z/VSE users?

2 Pages