zPDT features and functions

The zPDT creates a virtual System z architecture environment, with virtual I/O and devices as well. Some of the features for zPDT:

New for zPDT 1.4 (available 12/14/12)

• New zEC12 CPU Processor Architecture Support timely with the zEC12 GA, the most current zEnterprise server
  • Transactional Execution Facility for elimination of software locking overhead increasing parallelism
  • New PL/I compilers performance boost from enhancements to decimal format conversions
  • 2 GB page frames for performance improvements
  • Miscellaneous Instruction Extension Facility for Java code checking, and memory fetching efficiency
• Emulated Crypto Express 4S Support with stronger key wrapping, DUKPT for MAC encryption keys, support for EMV and other standards
• Enhanced Coupling Support (zEC12 CF18) with better serviceability
• Performance Enhancements
  • Enhanced time improvements when dynamically altering the entry/element ration or the size of the cache structure
  • DB2 conditional write to a group pool buffer (GPB)
  • Performance throughput enhancements for parallel cache castout processing
  • CF storage class and cast out contention avoidance
• Tested Linux x86_64 platforms include
  • SLES 11 SP2
  • OpenSUSE 11.0, 11.1, 11.2, 11.3,11.4 and 12.1
  • RHEL 6.0, 6.1, 6.2, 6.3
• Expanded number of Intel based x86_64 platforms tested to include:
  • Lenovo W510 and 530 Quadcore
  • IBM System X 3500 M4, 3650 M4 and 3755 M3
• Additional Operating Systems tested includes:
  • z/OS 1.12 and 1.13
  • z/VSE 5.1

zPDT Base

• IBM z/Architecture instruction* support, including:
  • Full 64-bit System z operation with both uniprocessor and multiprocessor configurations
  • Support for IBM z/OS®, IBM z/VM®, IBM z/VSE™ and Linux® for System z
• Memory
  • Greater than 2GB of System z memory
• Up to three virtual engines enabled by the 1090 USB hardware key:
  • The zPDT comes in three system sizes: one, two, or three virtual engines. The size of the virtual system is defined by the model of the 1090 USB hardware key (product number 1090-L01, 1090-L02, or 1090-L03, where the model number corresponds to the number of virtual engines).
  • Virtual engines can be configured as:
    • System z general-purpose processors (GPs)
    • System z Integrated Information Processor (zIIP)
    • System z Application Assist Processor(zAAP)
    • System z Coupling facility (CF available with zPDT V1.2.1)
    • System z Integrated Linux Facility(IFL)
  • Up to one instance per virtual engine, for example
    • zPDT with three virtual engines can be configured as:
      • A single instance with three engines
      • Three instances with a single engine each
      • Two instances, one with two engines and the other with one engine
    • The zVM operating system can be used to virtualize these configurations further and create any number of engines and engine types within an instance.
• Networking
  • Simulated OSA-Express2 adapter, in either QDIO or non-QDIO. This functionality is provided using standard Ethernet adapters on the host PC.
• Coupling Facility
  • Qualified ISVs can now use their zPDT systems to write applications and tools that take advantage of Parallel Sysplex. This capability is for virtual coupling only and uses z/OS guests under z/VM. The zPDT does not support physical coupling links and you cannot cluster multiple zPDT systems together.
  • Additional information on Coupling capability is provided in the Redbook.
• Disk devices
  • Simulated CKD disk
    • 3390 disk volumes (including variable sizes, and LARGE/EVA volumes)
    • 3380 disk volumes
    • A CKD versioning function that allows a 3390 (or 3380) volume to be quickly restored to a specified point in time.
  • Simulated FBA disk (as used by z/VM and z/VSE)
    • 9336, any model, > 2GB
  • Sharing of simulated CKD and FBA across instances
• Tape devices
  • Simulated 3420, 3422, 3480, 3490,3490E, and 3590 devices.
  • Selected SCSI-attached tape drives may be used directly by zPDT or through Linux staging functions. SCSI tape drives tested by IBM include:
    • IBM 3580 Ultrium (LTO)
    • IBM 3592 E05
    • IBM TS1120
    • Fujitsu M2488E
  • Data compression can be manually enabled for simulated tape devices or manually enabled for SCSI tape drives if the drive hardware supports compression
  • 3422 OMA simulated tape device can read TDF format
• Other System z devices (simulated)
  • IBM System z Crypto Express 4S (IBM 4764 PCI-X Crypto Coprocessor) – with zPDT V1.2
  • IBM 3088 CTC device - with zPDT V1.2
  • Card reader (2540) with functions to process both EBCDIC and ASCII data
  • 1403-N1 or 3211 printer, including FCB emulation for 3211 functions
  • Local 3270 (via an emulated 3274) connections. Extended data stream is supported if the 3270 client supports it
  • 3270 terminals
  • 3215 console, including several System z console interface functions
  • A 1090 device manager that allows Linux commands to be issued to the underlying Linux operating system from the System z operating system.

NOTE : System z functions not supported by zPDT are as follows:

• Physical parallel, IBM ESCON®, FCP and IBM FICON® channels and physical coupling links are not supported
• Clustering of zPDT systems in a Parallel Sysplex, is not supported. zVM is required to make use of the coupling facility function.
• System z instructions and functions that are not relevant to zPDT operation are not included. The excluded list includes list-directed IPL, external time reference (ETR), time of the day(TOD) steering, asynchronous data movers, Modified Indirect Data Address Word (MIDAWs) facility, logical channel subsystems, IBM HiperSockets, logical partitions(LPARs), multiple I/O paths, and some channel subsystems call(CHSC) functions
• IBM zEnterprise System function (such z/OS Discovery and Auto Configuration, hardware instructions) are not supported.

The most basic interface for most zPDT users are "local" 3270 terminals running in Linux windows. A TN3270 or TN3270E emulators is needed, and the x3270 program suite (available with many Linux distributions) is commonly used. These 3270 terminal windows provide traditional operator consoles and user sessions.

OSA provides Ethernet TCP/IP connectivity to the System z operating system and can be used for remote or local TN3270 or TM3270E, Telnet, Secure Shell(SSH), and so on connections.

z/OS data migration utility (a client/ server application) allows simplified migration of z/OS 3380 and 3390 volumes to the zPDT-based system essentially helping you to clone a big z/OS system to the zPDT-based system.

z/VM data migration utility (a client/ server application) allows simplified migration of z/VM 3380, 3390, and FBA volumes to the zPDT-based system essentially helping you to clone a big z/VM system to the zPDT-based system.

IBM does not provide specific performance numbers for zPDT, in MIPS, million service units (MSU), or large system performance reference (LSPR) metrics. Performance varies according to:

• The nature of the workload and on intermediate functions such as Linux disk cache operation
• The number of users. A reasonable number of users on a zPDT system, doing typical TSO development work, should experience subsecond response time
• The base machine being used for zPDT. For example, machines with faster processor speeds or machines with more cores (hex- and octo-cores) might expect higher performance as compared to slower,smaller base machines

Suggested IBM software pricing metrics for the three sizes of zPDT are available upon request. Metrics are for IBM software pricing purposes and not an indication of zPDT speed or size.

• For more information, contact the System z Developer Discount program: syszdd@us.ibm.com

• System z Personal Development Tool Volume 1: Introduction and Reference
• System z Personal Development Tool Volume 2: Installation and Basic Use
• System z Personal Development Tool Volume 3: Additional Topics
• System z Personal Development Tool Volume 4: Coupling and Parallel Sysplex