Preview: z/OS V1.10 — Raising the bar and redefining scalability, performance, availability, and economics

IBM United States Software Announcement 208-042
February 26, 2008

 

 ENUS208042.PDF (112KB)

 

Table of contents  Document options  
TOC link At a glance TOC link Description
TOC link Overview TOC link Statement of direction
TOC link Key prerequisites TOC link Reference information
TOC link Planned availability  
 
Printable version Printable version

 
At a glance

Today IBM previews z/OS V1.10. This release of the z/OS operating system is planned to build on its leadership capabilities by not only enhancing time-tested technologies, but leveraging deep synergies with the new IBM System z10 Enterprise Class (z10 EC) server and IBM System Storage family of products. z/OS V1.10 supports new capabilities designed to provide:

  • Storage scalability. Extended Address Volume (EAV) initially plans to support up to 262,668 cylinders (223 GB of addressable storage) per volume (on z/OS V1.10 and System Storage DS8000, when available). EAV can help simplify storage management by providing the ability to manage fewer large volumes as opposed to many small volumes.
  • Application and data serving scalability. Up to 64 engines, up to 1.5 TB per server with up to 1.0 TB of real memory per LPAR, and support for large (1 MB) pages on the z10 EC can help provide scale and performance for your critical workloads.
  • Intelligent and optimized dispatching of workloads. HiperDispatch can help provide increased scalability and performance of higher n-way z10 EC systems by improving the way workload is dispatched within the server.
  • Low-cost, high-availability disk solution. A new Basic HyperSwap capability (to be enabled by TotalStorage Productivity Center for Replication Basic Edition for System z) plans to provide a low-cost, single-site, high-availability disk solution which allows the configuration of disk-replication services using an intuitive GUI from z/OS.1
  • Improved economics with more specialty engine exploiters. zIIP assisted z/OS Global Mirror (XRC), and additional z/OS XML System Services exploitation of zIIP and zAAP help make these workloads more attractive on System z.
  • Improved management of temporary processor capacity. A new Capacity Provisioning Manager planned for z/OS V1.10, and available on z/OS V1.9 with APAR OA20824, can monitor z/OS systems on z10 EC servers. Activation and deactivation of temporary capacity can be suggested or performed automatically based on user-defined schedules and workload criteria. RMF or equivalent function will be required to use the Capacity Provisioning Manager.
  • Improved network security. z/OS Communications Server introduces new defensive filtering capability. Defensive filters are evaluated ahead of configured IP filters, and can be created dynamically, for added protection and minimal disruption of services in the event of an attack.
  • Improved productivity. z/OS V1.10 is planned to provide improvements in or new capabilities for: simplifying diagnosis and problem determination; expanded Health Check Services: network and security management; automatic dump and re-IPL capability; as well as overall z/OS, I/O configuration, sysplex, and storage operations.

 
Back topBack to top
 
Overview

In today's world, Information Technology (IT) is woven into almost everything we do. The demands on IT solutions are greater than ever — often requiring the delivery of more service, value, or capabilities, in less time or with fewer resources. Accomplishing "more with less" can be achieved by adopting a platform solution that is designed to drive efficiencies and economies of scale; accommodate business needs through flexible, virtual, and autonomic capabilities; help reduce the risk of lost productivity, downtime, or security breaches; and enable business innovation through the extension of existing investments and adoption of newer technologies.

Get the most of your IT investment with z/OS®. The marriage of z/OS and the System z™ platform delivers advanced scalability, resiliency, security, workload management, and autonomic capabilities, while minimizing excesses and waste of system resources and operations. System z and z/OS redefine investment protection by going to great lengths to keep applications and data available, system resources secure, server utilization high, and programming environments adaptable.

Today IBM previews z/OS Version 1 Release 10. In this release of the z/OS operating system, IBM plans to build on its leadership capabilities by not only enhancing time-tested technologies, but leveraging deep synergies with the new IBM System z10 Enterprise Class (z10 EC) server and System Storage™ family of products.

z/OS V1.10 and the new z10 server together deliver tremendous economies of scale and adaptability of resources. With support for up to 642 engines in a single logical partition (also available on z/OS V1.9) and up to 1.0 terabyte (TB) of real memory per LPAR (also available on z/OS V1.8 and V1.9), your application and data serving requirements may not have to be partitioned on unnatural boundaries. In z/OS V1.10 (and available with z/OS V1.9), the memory architecture is extended to allow large (1 MB) pages to be used in addition to the existing 4 KB page size. This is expected to reduce memory management overhead for exploiting applications. Just as important as system scalability, is how it performs with that scalability. Planned for z/OS V1.10 and with the z10 server is HiperDispatch (also available on z/OS V1.7, and later), a capability that can provide intelligent dispatching of z/OS workloads, to help improve the performance for higher n-way systems. A new Capacity Provisioning Manager planned for z/OS V1.10, and available on z/OS V1.9 with APAR OA20824, can monitor z/OS systems on z10 servers. Activation and deactivation of temporary capacity can be suggested or performed automatically based on user-defined schedules and workload criteria1. RMF or equivalent function will be required to use the Capacity Provisioning Manager.

This release of z/OS and the IBM System Storage family of products together are designed to deliver improvements to scalability, availability, and productivity. Planned for z/OS V1.10 is Extended Address Volumes (EAV), a capability that enables support for over 54 GB of addressable storage, removing a limitation in place today. Initially EAV is planned to support up to 262,668 cylinders (up to 223 GB of addressable storage) per volume allowing you to simplify storage management by providing the ability to manage fewer, large volumes as opposed to many small volumes. In future releases EAV will continue to expand on this strategy. A new Basic HyperSwap™ capability (to be enabled by TotalStorage® Productivity Center for Replication Basic Edition for System z) plans to provide a low-cost, single-site, high-availability disk solution which allows the configuration of disk-replication services using an intuitive GUI from z/OS.1 The world-class z/OS Global Mirror disaster recovery solution is now enabled to exploit the System z10 and System z9™ Integrated Information Processor (zIIP) specialty engine. The zIIP essentially becomes a z/OS data mirroring engine that can provide better price performance and improved utilization of resources at the mirrored site. Availability is improved not only for storage and data. With z/OS V1.10, IBM plans to continue refining its error checking, fault tolerance, isolation, error recovery, and diagnostic capabilities by introducing improved console processing, JES2 Dynamic exit capability, automatic dump and re-IPL capability, new Health Check services, automatic restart of NJE connections, a new capability for tracking users of large amounts of fixed storage, as well as improvements in Parallel Sysplex® function.

z/OS V1.10 not only helps reduce the risk of downtime, but can help reduce the risk of security breaches as well. z/OS System Integrity — IBM's long-term commitment to protecting key z/OS system resources — together with enhancements to z/OS Security Server (RACF®), SSL, Public Key Infrastructure (PKI) Services, and encryption, make z/OS a highly secure hub for your data and applications. With z/OS V1.10, the z/OS Communications Server takes network security to the next level with its plans to provide improvements to policy-based networking components of NSS, IPSec, and AT-TLS. Building on its history of Intrusion Detection Services (IDS), the z/OS Communications Server also introduces new defensive filtering capability. Defensive filters are evaluated ahead of configured IP filters, and can be created dynamically, for added protection and minimal disruption of services in the event of an attack.

Productivity can be improved with simplified operations and z/OS V1.10 is planned to provide improvements in the areas of simplifying diagnosis and problem determination; network and security management; as well as overall z/OS, I/O configuration, sysplex, and storage operations. Planned improvements include: the Configuration Assistant for IBM z/OS Communications Server adds file import capabilities and support for IP address group definition to make the Configuration Assistant more responsive to networking needs; Health Checker provides not only more checks for RACF, z/OS UNIX System Services, XCF/XES, and CINET, but also support for log browse and saving data across IPLs, both of which can help improve analysis and problem determination; Hardware Configuration Manager is to include support for configuration packages and importing and exporting I/O configuration data similar to that of HCD, as well as improved named views support; and HCD will provide the ability to read and update an IODF by multiple users at the same time.

In z/OS V1.10, SMP/E is planned to help simplify the task of verifying required software fixes identified in Preventive Service Planning (PSP) buckets. PSP buckets identify required software fixes for new hardware devices, toleration and coexistence of new software releases, and enabling new functions. More specifically, IBM plans to consolidate the lists of required fixes from PSP buckets and produce SMP/E-consumable metadata in the form of HOLDDATA to identify those fixes. SMP/E will use the new HOLDDATA to identify what fixes are missing in a current software environment. In addition, SMP/E will help to simplify the task of selecting and installing the required fixes identified by the HOLDDATA.

Viewing the individual functional enhancements of z/OS over the years does not reflect the full scope of the holistic nature of the platform. Taken together, the improvements provided by z/OS V1.10, the z10, and DS8000™ can mean significant scalability, resiliency, security, workload management, and price performance capabilities for your workloads. For example, just to focus on DB2® for z/OS and IMS™, these workloads can benefit from improvements from many of the following: hashed DSAB searches; EAV; Basic HyperSwap; HiperDispatch; IBM System Storage DS8000 AMP (Adaptive Multi-stream Prefetching); and the z10 server's processors, memory, I/O, and network bandwidth. IBM DB2 V9.1 for z/OS (DB2 9) workloads can benefit from z/OS V1.10's additional XML exploitation of the zIIP specialty processor, and the z10 server's hardware implementation of decimal floating point functions. Of course, other applications and subsystems can benefit from the deep synergy of the System z platform too.

z/OS V1.10 is the next step in the evolution of the System z mainframe. It raises the bar and redefines scalability, performance, availability, and economics for the platform. It provides control over system resources, flexibility and autonomics for unforeseen demands, world-class security and availability, and deep synergies within the platform. z/OS provides a solid foundation for extending existing applications, adopting new technologies, and above all leveraging your IT investment.

1
All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.
2
The total number of processors defined in a z/OS logical partition is the sum of general-purpose processors (CPs), System z9 Application Assist Processors (zAAPs), and IBM System z9 Integrated Information Processors and IBM System z10 Integrated Information Processor (zIIPs). This support is also available on z/OS V1.9.

 
Back topBack to top
 
Key prerequisites

z/OS V1.10 will run on these IBM System z servers:

  • z10 EC
  • z9 BC
  • z9 EC
  • z900
  • z990
  • z800
  • z890

For a complete description of z/OS V1.10 software prerequisites, refer to z/OS Planning for Installation (GA22-7504), when available.
 
Back topBack to top
 

Planned availability

September 2008
 
Back topBack to top
 

Description

Ease of use

z/OS has embarked on a long-term commitment to simplify the z/OS platform. The past several releases of z/OS delivered improvements in the areas of simplifying diagnosis and problem determination; network and security management; as well as overall z/OS, I/O configuration, sysplex, and storage operations. These improvements can help simplify systems management, improve application programmer, system programmer, and operator productivity, and make the functions easier to understand and use. Updates planned for z/OS V1.10 include:

  • Configuration Assistant for z/OS Communications Server (a downloadable tool) is designed to simplify network and security management. For z/OS V1.10 the Configuration Assistant for z/OS Communications Server adds file import capabilities and support for IP address group definition to make the Configuration Assistant more responsive to networking needs.
  • IBM Health Checker for z/OS (in the base of z/OS) is intended to help you avoid problems. In z/OS V1.10, IBM Health Checker for z/OS provides not only more checks for RACF, z/OS UNIX® System Services, XCF/XES, and CINET, but also support for log browse and saving data across IPLs, both of which can help improve analysis and problem determination.
  • Hardware Configuration Manager (HCM) is intended to help simplify z/OS I/O configuration. For z/OS V1.10, HCM is planned to be updated to include support for configuration packages, importing and exporting I/O configuration data in a manner more similar to how it can be done using HCD, and improved saved views.
  • Hardware Configuration Definition (HCD) support is planned to allow multiple HCD users to display and update the same IODF at the same time.
  • z/OS V1.10 (and z/OS V1.9 with PTF for APAR OA20824) is planned to introduce the Capacity Provisioning Control Center, a tool for managing capacity provisioning for System z10 servers. It is designed to manage provisioning policies and domain configurations.
  • In z/OS V1.10 SMP/E is planned to help simplify the task of verifying, selecting, and installing required software fixes.
  • Additional ease of use enhancements are planned for system logger, DFSMSrmm™, DFSMShsm™, PDSE, ISPF, VARY command, and Language Environment®.

The goal for z/OS platform simplification is to eliminate, automate, and simplify tasks without sacrificing z/OS strengths; to deliver a z/OS management facility that's easy to learn and use with integrated task guidance; and to embrace IBM's converged systems management strategy.

Details on the ease of use enhancements intended for z/OS V1.10:

  • z/OS Communications Server plans to provide enhancements aimed at improving the user experience with installing, configuring, and operating:
    • Configuration Assistant: Policy Configuration File Import. The Configuration Assistant (CA) for z/OS Communications Server can help simplify the definition of IP security policies and provides a graphical user interface (GUI) for policy definition management. The CA exports those policy definitions to z/OS systems in the form of text configuration files which z/OS Policy Agent reads and installs into the stack. z/OS Communications Server and the CA are being enhanced for V1.10 to allow the CA to import existing policy text files into the GUI. This allows the CA to learn of and absorb manual changes that the system administrator may have made to the policy configuration text files since the last time they were exported.
    • Configuration Assistant: IP Address Groups. The z/OS Communications Server policy definitions include the specification of the IP addresses to which specific rules apply. IP Address Group definitions are used to define rules which apply to more than a single address. CA support for IP Address Groups is being expanded in V1.10 to support IP Address Group specifications for additional perspectives (for example, AT-TLS, IPSec). Also, the KeyExchangeRule is being enhanced for both the CA and the z/OS Policy Agent to support specification of an IP Address Group.
  • The following IBM Health Checker for z/OS enhancements are planned:
    • A new log browse service designed to enable an application to extract historical data from health check output written to a log stream. This is expected to be useful in helping an application establish historical views of values returned by various health checks.
    • Allow checks to save data across IPLs in a data set so it can be accessible to instances of the checks running later, even after IPL. This support is designed to benefit those check writers who need persistent check-related information to be saved across system IPLs.
    • In z/OS V1.10, XCF and XES plan to extend and enhance their existing health checks to provide new and improved checks to detect single points of failure for all types of couple data sets using the new IOSSPOF service, check for appropriate separation of different types of couple data sets, and check XCF signaling paths and structure sizes. Improved CF structure and duplexing checks are planned to help you avoid sysplex-related problems. New checks are planned for Sysplex Failure Manager action specifications to help you improve sysplex availability.
    • New health checks are also planned for z/OS UNIX and for RACF.
    • A health check is planned to be added for CINET environments to confirm whether the port range defined for use by the OMVS address space has been reserved in the TCP/IP stack definitions.
  • Language Environment support is planned to help you verify the syntax of CEEPRMxx members. Batch support to check one or more members is planned using a new CEEPRMCC program. Support for a CEEPRMCK CLIST is also planned. Syntax checking is expected to help you prevent errors from being made in CEEPRMxx parmlib members.
  • DFSMSrmm is planned to provide improved parmlib support for tape library and tape volume partitioning, improved reporting for DFSMShsm activity, and support for new media end-of-life management policies based on media errors, volume usage, and age. These new functions are intended to make tape management easier and improve administrator productivity.
  • DFSMShsm is planned to provide support for a NEWNAME parameter for data set backup. This new function is intended to allow you to create a backup version of the specified data set and make it look like a backup of the data set specified with the NEWNAME keyword. This simplifies the process used to convert backups of an online data set to DFSMShsm backups while preserving the availability of the original data set.
  • DFSMS plans to provide an enhanced DISPLAY SMS command with new options to display point-in-time PDSE cache information in real time (as opposed to SMF Records) and the overall effectiveness of PDSE caching. DFSMS will also display PDSE caching statistics at the data set level. PDSE members can be cached in Hiperspace™ to provide enhanced performance for those PDSE data sets that are considered important in a critical performance path. The new command and its displays are designed to help you determine whether changes to cache settings might improve system performance.
  • HCD usability improvements include support for multiuser update access to IODFs. This multiuser access capability is designed to allow you to specify that work IODFs be shared and provide serialization to allow different parts of them to be updated by different people using concurrent HCD sessions.
  • HCM usability improvements include:
    • Support for configuration packages similar to those supported by HCD, to allow a subset of a configuration to be created. For example, this support is designed to allow you to create and send a configuration package for a sysplex or a single site to another location.
    • Support for importing and exporting I/O configuration data, similar to that provided by HCD. This function is designed to allow you to create I/O configuration statements for processor, switch, or operating system configurations of an IODF, and to migrate existing data sets containing I/O configuration statements into an IODF.
    • Enhancements to the Named Views capability of HCM to save lists of selected objects, the current zoom factor, and the scrolling positions. This is designed to allow the same part of a diagram to be displayed when restoring a view as it appeared when saved.
  • In z/OS V1.10, IBM plans to introduce the Capacity Provisioning Control Center, a tool for managing capacity provisioning for System z10 servers. It is designed to manage provisioning policies and domain configurations. Provisioning policies specify the criteria for capacity increases and decreases, while domain configurations specify systems to be observed and servers to be managed.

    The Capacity Provisioning Control Center (CPCC) is planned to be available on z/OS V1.9 with PTF for APAR OA20824 (only on System z10 servers made available February 26, 2008) and z/OS V1.10, when available. Initial support is planned for a policy definition application which requires a workstation running Microsoft Windows® XP.

    Specifically, the Capacity Provisioning Control Center will provide the following functions:

    • Create and edit Capacity Provisioning policies
    • Create and edit Capacity Provisioning domain configurations
    • Connect to the Provisioning Manager; Display the status of the Provisioning Managers
    • Install Capacity Provisioning policies and domain configurations into the Provisioning Manager
  • A new z/OS specific function is added for the CIM Server, which allows the CIM Server configuration to be changed using the MODIFY system command, so operators no longer need to go to the z/OS UNIX System Services command prompt for making configuration changes.
  • These ease of use functions are planned for ISPF:
    • The ability to specify multiple targets for the ISPF EDIT move and copy line commands. This can help you eliminate repetitious use of these commands when copying or moving lines that will have multiple destinations.
    • A new ISPF service, DIRLIST, to display z/OS UNIX directory. Also, a new ISPF command, UDLIST, is planned to allow a directory to be listed.
    • Enhanced Screen Swapping. When using more than two logical screens, navigation among the screens can be supplemented by Point and Shoot fields at the bottom of the screen. This new support is intended to make it easier to navigate within an ISPF session and to supplement the existing SWAP LIST and SWAP NEXT support.
    • The ISPF Data Set List panel (Option 3.4) is enhanced to support block commands. This is intended to allow you to act on multiple data sets using fewer line commands; for example, using paired "DD" commands will specify that a block of data sets is to be deleted.
  • The VARY command is planned to be enhanced to support a new device attribute, UNAVAILABLE, for tape devices. This support, which supplements the OFFLINE status that can already be set for any device, allows you to specify that UNAVAILABLE devices be excluded from Recovery Allocation processing and from message IEF877E, which lists eligible devices that might be used to satisfy an allocation request.
  • In z/OS V1.10, SMP/E is planned to help simplify the task of verifying required software fixes identified in Preventive Service Planning (PSP) buckets. PSP buckets identify required software fixes for new hardware devices, toleration and coexistence of new software releases, and enabling new functions. More specifically, IBM will consolidate the lists of required fixes from PSP buckets and produce SMP/E-consumable metadata in the form of HOLDDATA to identify those fixes. SMP/E will use the new HOLDDATA to identify what fixes are missing in a current software environment. In addition, SMP/E will help to simplify the task of selecting and installing the required fixes identified by the HOLDDATA.
  • A new GRS ENQ Monitor REQTYPE=NCRESERVE filter is planned to be added which will allow the monitor to report only on unconverted hardware reserves (those which have not been converted to global ENQs). This is intended to make it easier for you to eliminate or reduce hardware reserves by helping identify candidates for reserve conversion.
  • Improvements are planned for the system logger administrative data utility to help you set up system logger resources and in problem determination involving log stream data sets. For example, it will be possible to continue execution of the utility after specification errors have been encountered, so that subsequent problems may also be seen and corrected.
  • When you start SMB, the SMB server will be designed to validate the syntax of the SMB environment variables. This can help you avoid errors and ensure that SMB uses the configuration options you intend.
  • A new environment variable, _IOE_SMB_TRANSPORTS, enables SMB clients to specify which port will handle SMB calls. The server is designed to respond on the enabled ports; the client software can chose to attempt one protocol prior to the other or both in parallel.

Scalability and performance

z/OS and its subsystems provide for scalability not only based on chip speeds, but on a single image, clustering, storage, and data handling basis as well. This holistic and balanced approach to scalability means your System z environment is capable of handling the growth of your user base, applications, business processes, and data processing needs.

Scalability improvements planned for z/OS V1.10 include:

  • Up to 64 processors per logical partition, and up to 60 LPARs per server are planned for z/OS V1.10 and System z10. With up to 64 processors per logical partition and as many as 32 z/OS logical partitions able to be configured in a Parallel Sysplex cluster, up to 2,048 engines' worth of processing capacity is available to application workloads.
  • Support for up to 4 TB of real memory on a single z/OS image (z/OS V1.8). This will allow for up to 1 TB of real memory on a single z/OS image for the z10 EC server, up to 512 GB of real memory on a single z/OS image on IBM System z9 servers, and up to 256 GB on z990 servers.

    Memory architecture is extended to support large (1 MB) pages. When large pages are used in addition to the existing 4 KB page size, they are expected to reduce memory management overhead for exploiting applications.

  • Architectural limit of hundreds of TB for DASD volumes, up from the current limit of approximately 54 GB per volume. Called Extended Address Volume (EAV), this function is planned to initially support 223 GB per volume on z/OS V1.10 and IBM System Storage DS8000, when available.

Just as important as the scale of the system, is how it performs with that scalability. Planned for z/OS V1.10 and with System z10 is HiperDispatch, a capability that can provide intelligent dispatching of z/OS workloads, to help improve the performance for higher n-way systems.

Many individual component enhancements intended to provide increased scalability, improved performance, and constraint relief are planned for z/OS V1.10, including improvements in DFSMShsm, IOS, Virtual Storage Management (VSM), Allocation, OAM, and XES/XCF.

Details on the scalability improvements intended for z/OS V1.10:

  • Starting with z/OS V1.10, up to 64 processors are supported in a single logical partition on z10 EC servers. This support is also available on z/OS V1.9.

    Note: The total number of processors defined in a z/OS logical partition is the sum of general-purpose processors (CPs), System z Application Assist Processors (zAAPs), and System z9 Integrated Information Processors (zIIPs).

  • A new function, HiperDispatch, can help provide increased scalability and performance of higher n-way System z10 servers by improving the way workload is dispatched within the server. HiperDispatch is designed to accomplish this by recognizing the physical processor topology, tracking where units of work have run, and attempting to redispatch them as close to the same physical processors as possible. This intelligent dispatching can help reduce the effects of memory latency to improve performance and reduce CPU time. HiperDispatch is available with new z10 EC and z/OS (z/OS V1.7 with the IBM zIIP Support for z/OS and z/OS.e V1R6/R7 Web deliverable and PTFs, z/OS V1.8 or V1.9 with PTFs, or z/OS V1.10). For more information, see the Preventive Service Planning bucket (PSP) for z10 EC, 2097DEVICE.
  • Exploiting the capabilities of a new 3390 device model on IBM System Storage DS8000 storage subsystems, EAV is designed to provide:
    • A new architectural limit of hundreds of TB per volume, up from the current limit of approximately 54 GB per volume (65,520 cylinders). z/OS V1.10 will support a maximum volume size of 223 GB (262,668 cylinders per volume).
    • Fully compatible access to data residing on cylinders below 65,520. Also, the existing 3390 device geometry (the track length and number of tracks per cylinder) is maintained on EAV.
    • In z/OS V1.10, support is planned for SMS and non-SMS managed VSAM data sets (ESDS, KSDS, RRDS, and LDS) at any location on an extended address volume. Non-VSAM data sets, catalogs, page data sets, and VSAM data sets with the KEYRANGE or IMBED attribute are restricted to the first 65,520 cylinders. With this initial support, space after the first 65,520 cylinders is intended to provide constraint relief for applications using large VSAM data sets, such as those used by DB2, CICS®, zFS file systems, SMP/E CSI data sets, and NFS mounted data sets.
    • A new dynamic volume expansion function designed to eliminate the need to copy volumes to increase their size.

    This new function is expected to provide substantial, immediate constraint relief for installations with a large number of large VSAM data sets. This is also expected to help improve storage management administration over time, as a relatively small number of large volumes are thought to be simpler to manage than a larger number of smaller ones. IBM recommends the IBM HyperPAV licensed function on the IBM System Storage DS8000 series be leveraged to help manage the number of paths to devices defined as EAV.

    In the future, IBM intends to expand support for EAV with larger volume sizes and support for additional data set types and access methods. For more information, refer to the Statement of direction section.

  • IOS is planned to be redesigned to allow Metro Mirror secondary devices to be defined in Subchannel Set One. This can in turn allow subchannels in Subchannel Set Zero previously used for this purpose to be reused to define additional devices. This supplements the support for defining PAV aliases in Subchannel Set One that was in z/OS V1.7 on z9 EC servers. This is intended to help alleviate the constraint due to the 64K device limit.
  • Support is planned for common storage above the 2 GB bar. A new virtual storage area, the High Common Storage Area (HCSA), is defined. Storage Management services and RMF™ support for HCSA are also planned. This new support provides the infrastructure required for many users of CSA and ECSA storage to move data above the bar. This is expected to lead to virtual storage constraint relief (VSCR) over time.
  • z/OS Communications Server is planned to provide virtual storage constraint relief by changing the inbound data path to no longer use ECSA to hold inbound data for processing, or when queueing the data to the application. The TN3270 Server will also be changed to reduce its ECSA usage for mapping of active sessions.
  • New support is planned for the Allocation component to create a hash table for use by the GETDSAB service. This is expected to substantially improve the retrieval time for Data Set Access Blocks (DSABs) when a large number of data sets have been allocated by a single address space.
  • OAM is planned to be enhanced to provide support for objects larger than the current maximum of 256M (268,435,456 bytes). The new maximum object size is 2000M (2,097,152,000 bytes), and it is stored, in parts, sequentially to the DASD level of the OAM storage hierarchy only. This is expected to reduce the need to separate large binary strings into multiple objects and to simplify the application interface as the application does not have to materialize the entire object first before it can be accessed.
  • In z/OS V1.10, improvements are planned to the way XES and XCF handle CF locking requests. With this support, Coupling Facility locking operations will be queued when I/O resources are not immediately available. This is designed to reduce processor utilization for locking-intensive workloads in CF link- and subchannel-constrained environments.
  • DFSMShsm control data set (CDS) backup processing is planned to be enhanced to reduce the delay for starting CDS backup due to the concurrent processing of other DFSMShsm functions. Reducing the delay for starting CDS backup can improve the availability of other DFSMShsm functions, most notably recall.
  • In z/OS V1.10, DFSMS is planned to support a new Virtual Concurrent Copy (VCC) function. VCC is designed to use a FlashCopy® relationship rather than a combination of storage control cache and z/OS dataspaces, and to perform point-in-time backup processing for large amounts of frequently-updated data while using less cache and memory resources. This new function is supported during DUMP and COPY operations on DS8000, ESS 800, and other storage controllers that support FlashCopy at a data set level.

Application integration

Like other operating systems, z/OS provides support for current application enablement technologies, but what sets z/OS apart is the ability to operate both new and existing applications within the same system, and in close proximity to the corporate data residing on z/OS. WebSphere® applications can run on the same z/OS system as the DB2 database, which can enable tight, security-rich local connections ideal for high-volume transactional throughput. Current CICS or IMS transactions can be extended with these new technologies to deliver value in new and innovative ways, without incurring the substantial cost required to rip and replace current core assets.

The z/OS platform supports many new application development technologies, such as Java™, Perl, PHP, XML, Unicode, HTML, SOAP, and other Web services. But z/OS continues to update its traditional application development tools too, with recent enhancements including the System REXX facility, METAL C facility, support for z10 EC hardware decimal floating point, and ISO standard based C/C++.

z/OS V1.10 is planned to enable additional XML processing to be made eligible for the zIIP and zAAP specialty processors. IBM middleware (such as DB2 9) and other products can benefit from this new functionality in addition to taking advantage of the z/OS XML System Services capabilities available today. These enhancements are expected to help improve the price performance of XML processing on z/OS and ultimately may help facilitate the decision to develop more XML-based applications on z/OS.

z/OS V1.10 plans include application development and application integration improvement updates for the following: Program Management Binder; dbx debugger; XL C/C++, HLASM, NFS Server and Client.

Details on the application development improvements intended for z/OS V1.10:

  • z/OS V1.10 is planned to enable additional XML processing to be made eligible for the zIIP and zAAP specialty processors. Enhancements in z/OS XML System Services and the XML Toolkit for z/OS (5655-J51) are planned to increase the amount of XML workload eligible for the zAAP and zIIP specialty engines. IBM middleware (such as DB2 9) and other products are expected to be able to benefit from this new functionality.
    • In z/OS V1.10, IBM intends to provide these functions in z/OS XML System Services:
      • Additional zIIP exploitation. z/OS XML System Services plans include additional zIIP exploitation, specifically enabling all z/OS XML parsing in enclave SRB mode to be eligible for zIIP. For example, with respect to DB2, z/OS XML processing may be partially directed to zIIPs when utilized as part of a distributed request (like DB2 DRDA®) today. This enhancement can help further benefit DB2 pureXML workloads by optionally directing all z/OS XML System Services parsing that is executed in enclave SRBs to the zIIP. This function is planned to be available on z/OS V1.8 and V1.9 with PTF for APAR OA23828. Delivery of this function satisfies the statements of direction in Hardware Announcement 107-190 , dated April 18, 2007, and Software Announcement 207-175 , dated August 7, 2007.
      • A validating parser. Validation support is designed to allow a program to determine whether an XML document meets the requirements expressed in an XML Schema Definition (XSD). z/OS XML System Services plans to add validating parsing. z/OS XML System Services validating parsing workload is to be eligible for zIIP and zAAP as well. Delivery of this function satisfies the statements of direction in Hardware Announcement 107-190 , dated April 18, 2007, and Software Announcement 207-175 , dated August 7, 2007.
      • Support for 19 additional code pages. This extends XML System Services processing to accommodate the character sets used in many additional languages. This function is also available on z/OS V1.7, V1.8, and V1.9 with PTF for APAR OA22777.
      • Source offset support. This is designed to make it easier to locate or extract specific data from within an XML document.
    • IBM plans to enhance the XML Toolkit for z/OS (5655-J51) so eligible workloads can use z/OS XML System Services. This allows eligible XML Toolkit processing for non-validating parse requests to exploit the zAAP. This function is planned to be available on the XML Toolkit for z/OS V1.9 with SPE. XML toolkit support for processing validating parse requests using z/OS XML System Services, with the appropriate offload of eligible work to zAAP, is planned at a future date.1 Delivery of this function satisfies the statements of direction in Hardware Announcement 107-190 , dated April 18, 2007, and Software Announcement 207-175 , dated August 7, 2007.
    • Additionally, Enterprise COBOL V4.1 (5655-S71) provides support for a new XMLPARSE compiler option to allow COBOL programs to use XML System Services for XML processing and take advantage of zAAP specialty processors. For more information, refer to Software Announcement 207-339 , dated December 11, 2007.
    • The following enhancements are planned for the application development stack in z/OS V1.10, including the Program Management Binder; Loader; dbx debugger; and XL C/C++ compiler, runtime, and class libraries:
      • Two new socket API options are introduced in this release that allow applications to indicate how long receive and send type socket API calls should block waiting for their operations to complete, to prevent indefinite blocking inside TCP/IP for these types of socket API calls. The socket options, SO_RCVTIMEO and SO_SNDTIMEO, are defined in the POSIX standards, and are included in the Single UNUX Specification (SUS) V3.
      • In z/OS V1.10, dbx is planned to support source-level debugging for High Level Assembler. This is expected to help you debug applications that include High-Level Assembler source parts.
      • Several enhancements to the AMBLIST program to allow it to be more easily used and to provide higher quality information for diagnosing problems found when developing or deploying program objects:
        • For LISTLOAD operations, the DLL Import/Export information from the B_IMPEXP class (information built by the binder in section IEWBCIE) will be formatted with MODLIST output. This new format will display the symbols, their attributes, and the DLLs they belong to, making it possible to determine dynamic bind problems which were not recognized when the module was initially built. (This information contained in this section is the same information which Language Environment uses to complete dynamic linking at run-time.)
        • For LISTLOAD operations, the information contained in the binder built module-level section X'0001', will be written with MODLIST output. This provides information about symbols which are referenced but are not used to update text, IDRU records (created by the user via the binder APIs), and the contents of the B_MAP class which contains general information about all the symbols within the module.
        • For LISTLOAD operations, the XREF output cross-reference information (both numerical and alphabetical) will be completely redesigned. This new design will align more closely to binder XREF output, and present the data in a much simplified, more intuitive format.
      • The binder GETD API and fast data GD API will be designed to work consistently. This is intended to help simplify conversion of applications to fast data APIs.
      • A new Java class is provided to allow Java programs to invoke the z/OS Communications Server FTP Client. This API support extends the existing z/OS Communications Server FTP Client API to support the Java programming language, and includes a sample Java program.
    • In z/OS V1.10, the function provided for Language Environment options by the CEEROPT module are extended to batch and AMODE 64 processing, in addition to the CICS and IMS environments.
    • Changes have been made to Language Environment designs that are intended to improve performance for:
      • I/O performance for multi-threaded C/C++ programs that use a single thread for I/O operations to any particular file.
      • HEAPPOOLS support for applications using 31-bit memory allocation (__malloc31) services in an AMODE 64 environment. This enhancement is being made available on z/OS V1.7, V1.8, and V1.9 with the PTF for APAR PK41618 or PK47298 (already available), or the PTF for PK49427, when available.
      • Additional decimal floating point support for the new hardware-based instruction processing on System z10 servers. This support is planned to be made available on z/OS V1.8 and later releases with the PTF for APAR PK54438 and its prerequisites.

      Also, Language Environment is planned to include new support for application IDs to login, password, and pthread security functions.

    • In z/OS V1.10, IBM plans to implement:
      • XL C support for mixed addressing modes (32 and 64) for the METAL option
      • Standard C++ Library enhancements including support for a subset of the ISO/IEC TR 19768, Technical Report on C++ Library Extensions
      • These functions are intended to improve performance:
        • New Prefetch Built-in Functions
        • Performance improvements to Standard C++ Library particularly with global placement new operators and the implementation of vector template class
        • Reduced Debugger bring-up time
    • In z/OS V1.10, z/OS UNIX System Services is planned to provide new shell commands.
      • The submit command will be designed to accept input from a data set, file, or stdin, and is expected to make it easier to initiate batch processing from within z/OS UNIX.
      • A new UNIX command, amblist, will be designed to provide the ability to invoke the AMBLIST program from the UNIX shell.
    • Support is planned to allow a program object stored in the file system to be loaded to a specified location in common storage (this function is often referred to as a "directed load").
    • The Network File System (NFS) is a distributed file system designed to provide transparent processing capability for data and information on worldwide and heterogeneous networks. The z/OS Network File System (NFS) provides the implementation that allows the z/OS platform to participate in these networks. In z/OS V1.10, NFS provides interoperability, continued NFS V4 support, constraint relief, and serviceability enhancements which build on previous support delivered in z/OS V1.7, V1.8, and V1.9:
      • Expanded platform support for z/OS NFS Clients and Servers to interoperate with Linux™ on System z NFS Servers and Clients.
      • Continued NFS Server and Client support for the NFS V4 standard (RFC3530):
        • NFS Client support for stronger authentication and network transmission protection for NFS data via the use of the RPCSEC_GSS security authentication flavor.
        • NFS Client and Server support for byte-range file locking using services provided by z/OS UNIX System Services for z/OS UNIX file systems. The NFS V4 locking protocol provides some improvements over NFS V2 and V3 as it incorporates the locking operations into the same protocol as other file access operations (open, close, read, write) and allows for files, file systems, or servers to be defined to use advisory locking rules.
        • NFS Client and Server support for remotely managing ACLs via the NFS V4 protocol to display and modify ACL values via the ACL attribute. The NFS Server will map ACL requests between the z/OS UNIX ACL definition and the NFS V4 protocol definition. The NFS Client will use UNIX APIs to manage ACLs on remote NFS servers via the NFS V4 protocol and will map ACL requests between the z/OS UNIX ACL definition and the NFS V4 protocol definition.
      • Improved storage constraint relief, via 64-bit support, for the NFS client enabling utilities (mvslogin, mvslogout, showattr) on other platforms (AIX®, Sun, Linux on POWER5™, Linux on System z).
      • Enhanced NFS Server message support with Japanese National Language Support (NLS).

Security

Security is a word that is almost synonymous with mainframe. The combination of time-proven z/OS technologies and z/OS system integrity — IBM's long term commitment to protecting key z/OS system resources — means z/OS is a natural choice if you want a platform that can help keep enterprise wide data and transactions secure. Time-proven z/OS technologies, such as RACF to manage authorization and access to z/OS resources, Public Key Infrastructure (PKI) to provide low cost Certificate Authority life-cycle management on z/OS, and DB2 use of z/OS multilevel security (MLS) designed to meet the stringent security requirements of multi-agency access to data, are constantly being updated to meet — even exceed — clients' needs.

For z/OS V1.10, the following security updates are planned: z/OS exploitation for RACF password phrases, additional RACF integration with IBM Tivoli® Directory Server for z/OS (LDAP), improved RACF administration, and new cryptographic support. System SSL is planned to be upgraded with recent SHA-2 technologies.

z/OS security capabilities do not stop at the server, but extend into the network as well. For z/OS V1.10 the z/OS Communications Server plans to provide improvements to its policy based networking components, NSS, IPSec, AT-TLS. Building on its history of Intrusion Detection Services (IDS), the z/OS Communications Server also introduces new defensive filtering capability. Defensive filters are evaluated ahead of configured IP filters, and can be created dynamically, for added protection and minimal disruption of services in the event of an attack.

Details on security enhancements intended for z/OS V1.10:

  • In z/OS V1.8, RACF Password Phrase support was introduced, with infrastructure to support password phrases from 14 to 100 characters in length in addition to the long-supported 1-8 character passwords. In z/OS V1.9, the RACF support was extended to include 9-13 character password phrases when an ICHPWX11 user exit is in use (and to provide a REXX-based sample), eliminating the gap between password length and password phrase length. In z/OS V1.10, IBM plans to provide support for password change logging and enveloping functions for password phrases, to provide password expiration warning for password phrases as is done for passwords, and to exploit password phrases when they have been enabled in RACF user profiles. These exploiting functions include:
    • TSO/E logon.
    • z/OS UNIX kernel.
    • z/OS UNIX Shell and Utilities su and passwd commands.
    • C run-time functions login(), __passwd(), pthread_security_np() and getpass().
    • Network Authentication Service support for Kerberos.
    • IBM Tivoli Directory Server (LDAP) for z/OS SDBM backend support for RACF password phrase envelope search capability and RACF password phrase change logging. With this enhancement, you can start to implement enterprise-wide password synchronization (using, for example, IBM Tivoli Directory Integrator) where RACF users can now effectively have longer passwords with fewer character restrictions, such as can currently exist on Windows and UNIX systems.
    • The OpenSSH function of IBM Ported Tools for z/OS (5655-M23) when used on z/OS V1.10.
  • Custom fields are planned for RACF USER and GROUP profiles, with corresponding administration support using RACF commands, ISPF panels, and LDAP. This support is designed to allow you to add fields using a new RACF CFIELD class to define the new fields to be added to USER or GROUP profiles and the labels you want to use for them. These fields are planned to be added to a new CSDATA segment of USER and GROUP profiles. Once the fields have been defined, the RACF commands used for user and group administration and the corresponding LDAP administration support can be used.
  • RACF password administration design will be changed to allow more selective authority for resetting passwords to be granted. This support is designed to allow you to grant individuals the capability to reset passwords for one or more users or the users that are members of one or more groups without having the system-wide RACF SPECIAL attribute or access to the system-wide IRR.PASSWORD.RESET profile in the FACILITY class. New RACF support adds the required control to enable the target users of password resets to be scoped by the owner of the RACF user or users that are within a selected group tree. This support is expected to provide you better controls for allowing help desk personnel to do password resets without granting them additional authorizations.
  • RACF intends to allow messages ICH70001I and ICH70002I to be returned to a RACROUTE REQUEST=VERIFY/X application which specifies MSGRTRN=YES and ACEE=. This relaxes a restriction from earlier releases.
  • RACDCERT and PKI Services are planned to be able to generate and display the IPv6 type Internet Protocol address (IP address), in addition to the IPv4 format, in the certificate Subject Alternate Name extension.
  • RACDCERT is planned to be able to generate and display the IPv6 type Internet Protocol address (IP address), in addition to the IPv4 format, in the certificate Subject Alternate Name extension.
  • The RACF RACDCERT command processor is planned to be modified to replace the BSAFE crypto provider that is presently imbedded in the command with the IBM Crypto Library in C (CLiC). The present BSAFE crypto provider is not capable of supporting RSA key lengths greater than 1024 bits in length. With CLiC, RACDCERT will be able to generate 4096-bit RSA keys through software, in addition to the hardware capability of generating keys with such length. Refer to ICSF enhancements for details.
  • Support for additional characters from the UTF8 character set for certificates supported by PKI Services is planned for z/OS V1.10, adding to the support made available in RACF in z/OS V1.9. Both are intended to improve interoperability with certificates created by other certificate authorities (CAs).
  • PKI Services is planned to support three additional Distinguished Name attribute types — Domain Component, Distinguished Name Qualifier, and User ID.
  • In z/OS V1.10, IBM plans to update the z/OS Cryptographic Services Integrated Cryptographic Services Facility (ICSF) with the functionality introduced in the Cryptographic Support for z/OS V1.7-V1.9 and z/OS.e V1.7-V1.8 Web deliverable.

    The highlights of the planned ICSF enhancements to z/OS are:

    • 4096-bit RSA key support. IBM plans to provide 4096-bit RSA support on System z servers. The servers must have the 4096-bit RSA signature generation and verification support available with feature 0863 installed, and the Crypto Express2 Coprocessor with microcode level MCL006-MCL009 on these servers:
      • z10 EC
      • z9 EC
      • z9 BC
    • Additional SHA hash algorithms are planned by IBM: SHA-224, SHA-384, and SHA-512. SHA-224 is supported on all hardware supported by z/OS V1.10. SHA-384 and SHA-512 are only available with System z10 servers.
    • Additional clear AES key algorithms are planned by IBM: AES-192 and AES-256. These algorithms are only available with System z10 servers.
    • ISO Format-3 PIN Block support that meets the ISO 9564-1 Banking standard is planned by IBM. Feature 0863 must be installed, and the Crypto Express2 Coprocessor with microcode level MCL006-MCL009 on these servers:
      • z10 EC
      • z9 EC
      • z9 BC
    • Long random number callable service is planned by IBM. The service can create random numbers that are longer than 8192 bytes in length. This service is available on all hardware versions supported by z/OS V1.10. Optimum performance is available when feature 0863 is installed and the Crypto Express2 Coprocessor with microcode level MCL006-MCL009 on these servers:
      • z10 EC
      • z9 EC
      • z9 BC

      Note: The Cryptographic Support for z/OS V1.7 through z/OS V1.9 and z/OS.e V1.7 through z/OS.e V1.8 Web deliverable is available. This Web deliverable supports z/OS V1.7 through z/OS V1.9 and z/OS.e V1.7 through z/OS.e V1.8. To obtain this Web deliverable, visit

      http://www.ibm.com/server/eserver/zseries/zos/downloads

  • In z/OS V1.10, support for these functional enhancements to System SSL is planned:
    • Utilize hardware support for RSA digital signature generate and verification and RSA encrypt and decrypt available on z10 EC, z9 EC, and z9 BC servers with feature 0863 installed with the latest Crypto Express2 Coprocessor with microcode level 3.30, which is provided by MCL006 — MCL009.
    • List command support in the command line version of gskkyman to help you to determine when certificates in key data base (kdb) files are due to expire and to obtain other information about the set of certificates in a key data base.
    • Completion of the SHA-256 support, along with support for SHA-224, SHA-384, and SHA-512. This support is designed to extend the prior Secure Hashing Algorithm support to include import, display, export, and key data base storage for certificates using SHA-224, SHA-256, SHA-384, and SHA-512 algorithms.
  • The RACF RACDCERT command processor is planned to be modified to replace the BSAFE crypto provider that is presently imbedded in the command with the IBM Crypto Library in C (CLiC). The present BSAFE crypto provider is not capable of supporting RSA key lengths greater than 1024 bits in length. With CLiC, RACDCERT will be able to generate 4096-bit RSA keys through software, in addition to the hardware capability of generating keys with such length. The software support requires z890, z990, or later server with feature 3863 installed. The hardware support will exploit the 4096-bit RSA key generation function available on z10 EC, z9 EC, and z9 BC servers with feature 0863 installed with the latest Crypto Express2 Coprocessor with microcode level 3.30, which is provided by MCL006 — MCL009.
  • In z/OS V1.10, IBM plans to provide an additional IBM Tivoli Directory Server for z/OS extended operation to support group access checking in addition to user access checking. This new function is planned to be made available on z/OS V1.8 and z/OS V1.9 with the PTF for APAR OA23078.
  • In z/OS V1.10, the IBM Tivoli Directory Server for z/OS plans to provide enhancements for IBM Tivoli Directory Server compatibility and support of new z/OS Security Server RACF function.

    The following planned enhancements provide additional compatibility with the IBM Tivoli Directory Server for z/OS:

    • Plug-in support. Configured plug-ins can be used to extend the capabilities of the IBM Tivoli Directory Server for z/OS. Pre-operation, post-operation, and client operation plug-ins are supported. HCD exploits this plug-in support for reading/updating IODF data.
    • Improved handling of SHA- and MD5-based user password attributes for better compatibility with IBM Tivoli Directory Server for z/OS.

    The following planned enhancements provide support of z/OS Security Server RACF function:

    • The IBM Tivoli Directory Server for z/OS SDBM backend support for the RACF custom user and group fields of the RACF CSDATA segment.
    • z/OS Security Server RACF password phrase:
      • Support for specifying a RACF password phrase for a simple bind or both native authentication and authentication to an IBM Tivoli Directory Server for z/OS SDBM backend. SDBM backend is also planned to support the SDBM backend will also support the RACF password phrase in the RACF Kerberos (KERB) segment.
      • Enhanced support in the IBM Tivoli Directory Server for z/OS SDBM backend has been provided for RACF password phrase envelope search capability and RACF password phrase change logging.
    • Support for making SASL external binds to an IBM Tivoli Directory Server for z/OS SDBM backend.
  • These network security enhancements are planned for z/OS Communications Server:
    • WebSphere DataPower integration: In z/OS V1.10, the Network Security Services (NSS) function is being extended to allow a z/OS NSS Server to provide centralized security services to attached WebSphere DataPower SOA appliance clients. These clients will be able to access SAF services at the z/OS system acting as the NSS Server to perform SAF based user ID authentication and access control checks without having to define the user IDs and access control rules in the appliance.
    • Defensive Filtering support is designed to provide a mechanism for users to block detected attacks by dynamically installing defensive filters in a TCP/IP stack. Defensive filters are a new kind of deny filter that are always placed in front of IP security filters. The defensive filters can be installed autonomically by an external security information and event manager, or manually by an authorized user.
    • IPSec RFC Currency: This line item implements a number of industry standards (RFCs 4301-4305, 4308) that are required by the US Department of Defense (DoD) for IPv6 certification, and by the National Institute of Standards and Technology (NIST) for general U.S. government use.
    • AT-TLS enablement for Load Balancing Advisor: The z/OS Load Balancing Advisor and Agent are enhanced to allow users to exploit the AT-TLS feature to secure connections that carry SASP flows. This will optionally allow you to control authentication, access control, and encryption for the load balancing protocols, using AT-TLS policies.
    • Additional application security controls are provided to let you restrict the use of listening ports and ephemeral ports to only those applications that have the appropriate authority, via SAF resource definitions. Also, new controls restrict the ability of applications to perform rpcbind registration and deregistration.
  • In z/OS V1.10, IBM plans to provide new, unauthorized Subsystem Interface (SSI) functions for SSI function codes 11, 75, 79, and 80 when used with JES3. These new functions are intended to allow programs to be written for user destination validation, sending messages to other users over the network, using the SYSOUT Application Programming Interface (SAPI), and obtaining detailed status information about jobs and SYSOUT in the JES queue. This function in JES3 is in addition to existing similar function in JES2.

Availability

There is more to "availability" than just the server being up — the application and the data must be available with good performance as well. For the System z platform this means hardware, connectivity, operating system, subsystem, database, and application availability too. z/OS, System z servers and System Storage disk working together can provide outstanding availability:

  • System z servers are designed to reduce planned and unplanned outages through the use of self-healing capabilities, redundant componentry, dynamic sparing, and the ability for concurrent upgrades and microcode changes. The z10 EC server provides additional microcode driver enhancements, and dynamic segment sparing for memory as well as a fixed Hardware System Area (HSA).
  • With every release, z/OS continues to refine its error checking, fault tolerance, isolation, error recovery, and diagnostic capabilities. z/OS V1.10 availability enhancements include designs for improved console processing, reduced need for JES2 restarts with JES2 Dynamic exit capability, support for automatic stand-alone dump and auto-IPL, and new health check services and checks.

z/OS also advances availability even beyond the z/OS image to include network and storage as well.

  • In this release, z/OS network availability improvements are planned. z/OS will be designed to restart JES2 NJE connections automatically, and introduce a new TCP/IP health check.
  • IBM intends to announce a new product, TotalStorage Productivity Center for Replication Basic Edition for System z V3.4 (Total Storage Productivity Center for Replication BE). A new Basic HyperSwap capability (to be enabled by TotalStorage Productivity Center for Replication BE) plans to provide a low-cost, single-site, high-availability disk solution which allows the configuration of disk-replication services using an intuitive GUI from z/OS. A future release of TotalStorage Productivity Center for Replication for System z intends to provide Basic HyperSwap administration as well.1
  • z/OS Global Mirror is enabled to exploit the zIIP speciality engine. With zIIP assisted z/OS Global Mirror, the zIIP essentially becomes a z/OS data mirroring engine that can provide better price performance and improved utilization of resources at the mirrored site.

Beyond single system availability is z/OS Parallel Sysplex clustering and GDPS™ disaster recovery. Parallel Sysplex is designed to provide your data sharing applications and data with not only continuous availability for both planned and unplanned outages, but also near-linear scalability and read/write access to shared data across all systems in the Parallel Sysplex for data sharing applications. z/OS V1.10 is planned to include enhancements in support of Parallel Sysplex: Load Balancing Advisor support of subplexes, XCF improvements, RACF improved data integrity, and more. This release of z/OS (and all other supported releases) is planned to support updated GDPS V3.5 as well.

Details on availability improvements intended for z/OS V1.10:

  • A new Basic HyperSwap capability (to be enabled by TotalStorage Productivity Center for Replication Basic Edition for System z) plans to provide a low-cost, single-site, high-availability disk solution which allows the configuration of disk-replication services using an intuitive GUI from z/OS. The intention is that with Basic HyperSwap function enabled, seamlessly swapping between primary and secondary disk volumes in the event of planned and unplanned outages such as hardware maintenance, testing, or device failure can be accomplished from z/OS.1

    Basic HyperSwap, to be enabled through TotalStorage Productivity Center for Replication BE, is intended to help you eliminate single disk failures as a source of application outages by allowing you to specify a set of storage volumes to be synchronously mirrored. For example, in the event of a permanent I/O error, I/O requests can be automatically switched to the secondary copy thereby masking the failure from the application and minimizing the need to restart the application (or system) after the failure. You can also initiate a planned failover to a secondary for the purpose of initiating hardware maintenance on primary storage controllers, or simply to periodically test the function. You can switch back to your preferred configuration via the GUI or operator commands.

    The prerequisites for TotalStorage Productivity Center for Replication BE are planned to be:

    • z/OS V1.9 with appropriate service, or z/OS V1.10 (when available).
    • A planned, new, no-charge product, IBM System Services Runtime Environment for z/OS — an environment that provides native Web services for z/OS. You may use WebSphere Application Server 6.1.0 for the IBM System Services Runtime Environment for z/OS.
    • DB2 V8 (or later). Customers without DB2 may use Apache Derby (planned to be available with TotalStorage Productivity Center for Replication BE).
    • IBM storage controller with the Advanced Copy Feature Metro Mirror — This includes IBM ESS Models 800, DS6000™, and DS8000.
  • GDPS/PPRC HyperSwap Manager (GDPS/PPRC HM) provides a robust continuous availability disk management solution, as well as an entry level disaster recovery solution when used across multiple sites. Basic HyperSwap will not be a replacement of GDPS/PPRC HyperSwap Manager. Customers desiring the comprehensive high-availability, multi-site, disaster-recovery capabilities of GDPS are still recommended to investigate one of the GDPS solutions.
  • IBM is announcing z/OS Global Mirror (formally known as Extended Remote Copy, XRC) that is enabled to exploit the zIIP specialty engine. The zIIP assisted z/OS Global Mirror function is designed to make most of the z/OS DFSMS System Data Mover (SDM) processing eligible to exploit the zIIP specialty engine. This capability is planned to be made available with any disk storage subsystem that supports z/OS Global Mirror and will be available via PTF (for APAR OA23174) for z/OS V1.8 and V1.9 and is planned to be included in z/OS V1.10.

    With zIIP assisted z/OS Global Mirror, the zIIP essentially becomes a z/OS data mirroring engine that can provide better price performance and improved utilization of resources at the recovery site. Most DFSMS system data mover (SDM) processing is eligible to be redirected to a zIIP processor, which can help lower server utilization at the recovery site, or create server "white space" to be used for other projects.

    z/OS Global Mirror provides an asynchronous, multi-site remote mirror solution across intercontinental distances for z/OS, zVM (with some configuration limitations), and Linux on System z data, and is one of the technologies that GDPS is based on. z/OS Global Mirror protects data consistency across all volumes that have been defined for mirroring and the volumes can reside on several different storage units. z/OS Global Mirror is also flexible, accommodating variable data volumes and network bandwidths, thus minimizing the possibility of data de-synchronization. Customers currently using z/OS Global Mirror or some other long-distance remote copy solution should consider zIIP assisted z/OS Global Mirror.

  • The first stage of a comprehensive overhaul for system message processing was made available as a feature for z/OS V1.4, and integrated in z/OS V1.5 and later releases. The overall objective of the Consoles Enhancements improvements is to improve system availability by enhancing the capacity and reliability of message delivery. To accomplish this, major changes to the message production and consumption flow help reduce the possibility of bottlenecks which can cause a backlog of undelivered messages. In z/OS V1.7, the next phase of Consoles Enhancements was made available, including support for deleting unused EMCS consoles, a new AMRF/ORE service routine, disassociating MONITOR messages from particular consoles, and support for enhanced recovery. In z/OS V1.8, the master console and console switch functions were removed, eliminating them as potential points of failure.

    In z/OS V1.10, IBM intends to deliver the final phase of Consoles Enhancements. In this final phase, consoles processing will be designed to reduce serialization contention by reducing the scope of serialization for many operations from a console class to an individual console. Additionally, support will be provided to increase the maximum number of MCS, SMCS, and subsystem consoles in a sysplex from 99 per sysplex to 99 active consoles per system; also, defining up to 250 consoles per system will be supported (of which up to 99 may be concurrently active), and wildcard support will be added for the DISPLAY CONSOLES command along with improved command response messages.

  • In July 2007, WLM exploitation of XCF signaling was changed in APAR OA20484 for z/OS V1.6-V1.9 in the following ways:
    • For asynchronous messages the sender no longer holds the sender latch.
    • The monitoring task and some other communication functions are able to detect long waits of asynchronous senders and are able to terminate these waits.
    • WLM is now able to actively find out that another system no longer communicates and is able to initiate recovery for it.
    This function is planned to be integrated in z/OS V1.10.
  • WebSphere for z/OS (5655-N01) 64-bit users have the capability to define very large heaps. Current processing dumps the heap ahead of the system and Language Environment thread stacks needed to debug. 64-bit storage is planned to be assigned a dump priority which allows the stacks to be dumped ahead of the heap.
  • In z/OS V1.10, RACF design is planned to be changed to help you preserve RACF database data integrity. When a new system either IPLs, goes into data sharing mode with an RVARY DATASHARE, or activates a database with RVARY ACTIVE, RACF will check for indications of data sharing mode and non-data sharing mode systems using the same database concurrently, and for multiple sysplexes in data sharing mode, using the same database. If a mismatch is detected, a WTOR is issued, asking for direction (for IPL, either FAILSOFT, CONTINUE, or NODATASHARE, for RVARY either CANCEL or CONTINUE). This is designed to help improve availability by eliminating potential causes of database corruption.
  • The Language Environment IPCS formatter is planned to be enhanced to format additional C run-time control blocks.
  • Currently file system lock recording is done at a module level. In z/OS V1.10, IBM plans on providing the ability to perform file system lock recording at a thread level.
  • A z/OS UNIX System Services function will be designed to allow you to change sysplex root data sets dynamically, without a sysplex-wide IPL. This new MODIFY OMVS,NEWROOT command is expected to eliminate a cause for planned outages and to facilitate migration of sysplex roots from HFS to zFS.
  • The System Diagnostic Work Area (SDWA) is planned to be moved into 31-bit storage above the 16 MB line for AMODE(64) Functional Recovery Routines (FRRs) in z/OS V1.10. SQA storage shortages can cause FRRs to be skipped when the SDWA is below the line. Moving them above the line is designed to help avoid one cause of abnormal address space termination.
  • To help verify optimal dump reading configuration, IPCS is planned to issue additional messages when a dump is initialized, checking both the control interval size and available space of the dump directory in use.

    Additionally, IPCS is planned to report on the amount of time taken by the dump process.

  • System Trace buffers are planned to move to 64-bit storage, allowing for significantly increased system trace capacity.
  • Function is planned to provide a migration path from a GRSRNL=EXCLUDE environment to full RNLs without requiring a sysplex-wide IPL for certain environments. GRSRNL=EXCLUDE is a special mode where GRS excludes most SYSTEMS (global) level ENQs to SYSTEM (local) level scope.
  • In z/OS V1.10, JES2 plans to improve availability with the following items:
    • New function supporting JES2 Dynamic Exits will be provided with a new $T EXIT command. Additional commands intended to support refreshing JES2 load modules are also planned. The new $ADD LOADmod, $DEL LOADmod, and $T LOADmod,REFRESH commands will be intended to refresh tables within a specified load module, existing exit points, and the list of routines associated with exit points without an IPL or JES2 restart.
    • New initialization parameters and updated commands are planned to allow you to specify that NJE connections that terminate unexpectedly should be restarted after a specified interval. This new support is intended to help you improve availability for these connections by automating their recovery.
  • AutoIPL support will provide the capability to request that the system automatically IPL stand-alone dump, z/OS, or both, when a disabled wait state is requested by a system component. This function is designed to be under the control of new parmlib parameters and a new Wait State Action Table (WSAT); together, they specify the actions, if any, to be taken for various disabled wait states. In a sysplex environment, the Sysplex Failure Manager (SFM) policy can result in actions that load disabled wait states on systems to be partitioned out of the sysplex, which can also trigger AutoIPL processing. New options on the VARY XCF operator command will allow you to request a SADMP, z/OS IPL, or both, after the indicated system has been removed from the sysplex. AutoIPL capability is intended to help you achieve faster failure data capture and recovery after system failures.
  • In z/OS V1.10, IOS is planned to provide a new IOSSPOF service designed to detect and report single points of failure in the I/O configuration for a single device or common points of failure between a pair of devices. The service is designed to be usable both by functions to perform such checks in real time, and by health checks.
  • GRS display support is planned for latch contention, to provide information intended to make it easier to see how long a latch has been held, how long contention has existed for it, and which units of work own or are waiting for a latch. This is expected to make it easier to diagnose latch contention problems on a running system.
  • In z/OS V1.9, limited support was added for reusing the ASIDs of address spaces with cross-memory connections when they end, so the ASIDs remain available for the system to assign to new address spaces. ASID reuse is intended to help you prevent planned and unplanned outages by avoiding exhaustion of usable address space slots on the system.

    To enable the use of this new function, specify REUSASID(YES) in an active DIAGxx member of parmlib. This will allow it to be used when certain options are specified on the START command or the ASCRE (address space create) macro for supported address spaces. Currently, these z/OS address spaces support ASID reuse: CATALOG, LLA, and VLF. In z/OS V1.10, the z/OS UNIX RESOLVER address space, the TCP/IP address spaces, the DFSMSrmm address space, and the TN3270 address spaces are also planned to support ASID reuse. Before enabling ASID reuse on a production system, IBM recommends you first enable it on a test system. For more information about enabling ASID reuse, see z/OS MVS™ Extended Addressability Guide (SA22-7614).

  • In z/OS V1.10, RRS will be designed to improve availability by allowing an application to request that RRS syncpoint processing be ended without completion. A new FORGET request will be supported by the ATRSRV function to allow another resource manager on any system in the sysplex to instruct RRS to discard an SDSRM's interest in a transaction. This is intended to allow the transaction to proceed to completion once other interests have been satisfied, which in turn can help you avoid SDSRM restarts.
  • RRS is designed to write to an optional archive log stream when a transaction is completed. To improve RRS performance, some installations disable the archive log. In z/OS V1.10, a new SETRRS ARCHIVELOGGING command will be designed to allow you to specify whether the archive log is to be used dynamically, without an RRS restart. This is expected to help you avoid planned outages for subsystems and applications that use RRS services.
  • IBM plans to provide increased availability of system logger log streams by allowing updates to duplexing attributes to be put into effect without noticeable disruption to the log stream exploiters.
  • In z/OS V1.10, the Load Balancing Advisor and Load Balancing Agent functions are planned to be enhanced to support the subplex functions introduced in z/OS V1.8. You can configure one Load Balancing Advisor per subplex, and each stack in the subplex will have a load balancing agent for that subplex. This allows load balancing for applications in one subplex to be independent of load balancing for applications in other subplexes, within a single sysplex.

Optimization and management capabilities

With the ability to intelligently manage workloads, re-prioritize work, and dynamically reallocate system resources between applications quickly and efficiently, z/OS and System z can handle unexpected workload spikes and improve your system's efficiency and availability, all while meeting your application and business priorities.

z/OS Workload Manager (WLM) is unsurpassed in the industry in delivering the management of mixed diverse workloads according to business goals including response time goals. The scope of the Workload Manager and its exploiters extends from managing the incoming TCP/IP and SNA traffic to managing requests for I/O. z/OS middleware like DB2, CICS, IMS, WebSphere MQ, and other WebSphere products can take advantage of WLM to manage the priority and execution of transaction requests across the z/OS system. For z/OS V1.10 WLM plans on the following: enhanced contention management, improved management of zIIP workloads, the ability to manage selected components in service class SYSTEM, and new Performance Block delays.

Data Facility Storage Management Subsystem (DFSMS) is a software suite that automatically manages data from creation to expiration. z/OS V1.10 plans many optimization and management capability enhancements for DFSMSrmm and DFSMShsm. These functions can provide monitoring and management capabilities that improve storage administrator productivity and simplify the storage management in a z/OS environment. Planned improvements for DFSMSrmm include: interaction with IBM TotalStorage Productivity Center and a better interaction with IBM Integrated Removable Media Manager; enhanced reporting capabilities; and new policies for tape scratch pool, retention, and expiration management.

Details on Optimization and Management enhancements planned for z/OS V1.10:

  • Global Resource Serialization (GRS) is planned to allow you to specify 32 bytes of 'userdata' that is associated with an ENQ via the ISGENQ service. This allows ISGENQ exploiters to provide more details about the ENQ and, via new ISGQUERY support, enables them to more easily find ENQs related to those details.
  • The following WLM enhancements are planned:
    • Contention Management Phase 3: WLM Contention Management has been redesigned for z/OS V1.10 to help addresses chronic or long lasting contention situations. Previously, WLM contention management could promote units of work that held resources requested by waiting units of work for short periods. WLM is now designed to promote units of work identified by exploiters for longer periods of time, and promote them to the priority of the highest-priority units of work waiting for a resource they are holding. This new support is expected to help prevent low-priority work from blocking higher-priority work while still managing the overall system in a way that is consistent with the goals you specify in the WLM policy. RMF support for this function is also planned to provide information about the service times for workloads that were promoted, contention, and delay states in the RMF Postprocessor Workload activity report.
    • CPU Management of zIIPs: Before z/OS V1.10, WLM algorithms for adjusting the dispatching priorities of work in each service class only considered CPs and zAAPs. To meet the needs of growing zIIP workloads, this processing is planned to be extended to include zIIP processors in z/OS V1.10. This is expected to provide better management for those workloads.
    • Better protect z/OS against high consumers of fixed storage: To help prevent critical real storage shortages, new WLM function is planned for z/OS V1.10. New detection functions have been designed to track sudden growth in fixed and pageable storage and react quickly to help you avoid system outages. This new function is intended to identify fixed storage shortages, identify address spaces with the greatest growth in storage consumption, and issue new messages to identify them. This can help you use new automation methods to terminate address spaces consuming unacceptable amounts of fixed and pageable storage. The system will also be designed to logically swap such address spaces and set nonswappable address spaces nondispatchable to avoid further storage consumption. Also, support is planned for an ENF signal to allow other products to react to these situations.
    • Manage selected components in service class SYSTEM: To prevent the inadvertent misclassification of system address spaces, in z/OS V1.10 WLM will be designed to manage these address spaces in the SYSTEM service class even if they are differently defined in the WLM policy: XCFAS, GRS, SMSPDSE, SMSPDSE1, CONSOLE, IEFSCHAS, IXGLOGR, SMF, and CATALOG; this is in addition to the *MASTER* and WLM address spaces that were already automatically classified in the SYSTEM service class. This is intended to prevent system problems from occurring during periods of high system utilization.
    • New PB Delays: WLM provides Performance Blocks for use in application state (or phase) reporting. In z/OS V1.10, support for representing 10 additional delay states with Performance Blocks is planned, bringing the number that can be used for reporting to 15. Also, WLM will be designed to allow applications to specify the delay state names, replacing the default names. These functions are intended to make it easier to determine which application phases are causing the greatest delays.
  • WLM is planned to support extracting the WLM service definition in XML format as well as installing and activating a WLM service definition in XML format via a CIM Server. Also, WLM plans to support providing information about the status of a z/OS system using a CIM Server.
  • In z/OS V1.10, SMS is planned to support new DATACLAS overrides for certain SPACE parameters specified in JCL and in IDCAMS DEFINE commands. These new data class attributes are intended to allow you to specify that the units to be used to allocate primary and secondary space quantities (for example, tracks, cylinders, blocks, or bytes) be set from the attributes you set in the applicable data class. The allocation units and the secondary space quantity will also be made available to ACS routines to allow them to make more intelligent decisions. Additionally another new data class attribute will allow you to specify that the system determine the block size, thereby overriding any user-provided block size. This new function is expected to help you better manage space in SMS-managed DASD storage, and to make it unnecessary to change a large number of batch jobs to achieve the same result.
  • In z/OS V1.10, these RMF enhancements are planned:
    • RMF Monitor III provides new reports about spin and suspend locks. The Spin Lock report will be designed to display the address spaces which hold locks and which are suspended. The Suspend Lock report displays how often global locks are held and who is spinning. Reporting of lock statistics is intended to help you analyze lock contention in the system.
    • The RMF Distributed Data Server will be designed to support IPv6 connections from clients requesting RMF Monitor III performance data.
    • RMF will be designed to save the actual device capacity in SMF 74 subtype 1 Device Activity records, including records involving Extended Address Volumes (EAVs).
  • DFSMSrmm optimization and management capability items include:
    • Exploitation of the SMI-S Storage Library profile by the DFSMSrmm CIM Agent which is designed to enable client systems to more easily connect to the DFSMSrmm CIM Agent and also allows IBM TotalStorage Productivity Center to report on volumes managed by DFSMSrmm.
    • Enhancements to DFSMSrmm CLI better enable IBM's Integrated Removable Media Manager for the Enterprise on System z (IRMM) to integrate for enterprise-wide tape management. In addition you no longer require WebSphere Application Server to host the DFSMSrmm Web service. These enhancements are also planned to be available for supported z/OS releases with APAR OA23266.
    • Enhancements to allow the use of DFSMSdss™ copy services and exploitation of Fast Replication services provided by DASD subsystems. This is designed to enable almost instantaneous copies of the control data set to be created, reducing recovery time objective.
    • Enhancements to allow forward recovery of the DFSMSrmm CDS, when no journal backups are available, from the DFSMSrmm audit SMF records.
    • Enhanced reporting capability with updates to the DFSMSrmm Report Generator to support keywords for assembler macros from which report types are derived and to add new built-in extract steps. This is in support of new SMF record types from DFSMSrmm and for DFSMShsm and DCOLLECT reporting.
    • New run-time options to select which DFSMSrmm records are extracted for reporting which should help reduce the resources required for tape reporting.
    • Support for optional policies to enable tape data sets deleted via normal disposition processing to be fast tracked back to the scratch pool.
    • New policies to DFSMSrmm which set expected levels of retention and expiration for tape data sets to help avoid accidental loss of data.
  • Global Resource Serialization (GRS) plans to improve performance in both GRS Latch and ENQ processing. GRS plans to improve Latch performance through reduced code path and improved hardware cache alignment. ENQ performance and resource consumption improvements are planned through CMSEQDQ lock contention reduction as well as reduced code path lengths for GQSCAN, ISGQUERY, and ENF 51 (contention monitoring) processing.
  • Using configuration packages with HCM

    A configuration package is a subset of a centrally maintained master IODF which is extracted from the master IODF and distributed for activation at specified target systems.

    In z/OS V1.10, HCM plans to implement the concept of configuration packages, as it is currently available in HCD. New dialogs are planned to help HCM users to define, edit, transmit, and delete configuration packages, corresponding to the existing HCD functionality.

  • Create and migrate I/O configuration statements

    In z/OS V1.10, HCM intends to implement new dialogs that let users perform the following tasks, which previously have been available in HCD only:

    • Export/build IOCP input data set
    • Export/build I/O configuration statements
    • Import/migrate IOCP input data or I/O configuration statements into an IODF

    For exporting, the intent is to allow users to select where to store the resulting output data, and for importing, to specify where the source data is located (either on the host or on the workstation).

  • DFSMShsm plans the following enhancements:
    • DFSMShsm — CDS backup improvements: In z/OS V1.10, long-running DFSMShsm functions on systems in a sysplex with XCF capabilities will be suspended to allow a CDS backup to proceed, and restarted afterward. This is expected to reduce the time required to complete a CDS backup.
    • DFSMShsm: NEWNAME parameter for data set backup: The DFSMShsm data set backup commands will be enhanced to allow you to specify certain attributes to be used when creating a backup version of a data set. The new keywords NEWNAME, DATE, and TIME will be added to the command to allow you to specify the data set name, date, and timestamp to be used for the backup data set when it is created. This can allow you to create multiple backup versions of the same data set using different names, dates, and timestamps.
    • DFSMSrmm/DFSMShsm: Reporting Improvements: DFSMSrmm and DFSMShsm have enhanced the DFSMSrmm Report Generator to include the ability to generate reports of DFSMShsm processing. Refer to the DFSMSrmm enhancements listed in this Optimization and management capabilities section for more details.

Networking

The z/OS Communications Server supports highly secure TCP/IP, SNA, and UNIX networking throughout an enterprise. It provides Application Programming Interfaces (APIs) and networking protocol support to enable SNA and TCP/IP applications running on z/OS to communicate with partner applications or users on the same system, on other systems within a single data center, or in distant locations. The z/OS Communications Server not only maintains and improves on existing communication, but also pushes z/OS into the forefront of networking technologies, by introducing such concepts as Application-transparent TLS, policy based networking, and centralized configuration of TCP/IP nodes.

z/OS Communications Server designs for z/OS V1.10 include:

  • Network TCP/IP stack performance improvements in multiple areas, including CPU consumption, cache line contention, and common storage utilization
  • New support to help you coordinate LU name assignments among TN3270 servers in sysplex
  • Enhancements to SNA networking functions
  • Several enhancements to the z/OS FTP Server and Client
  • New functions for network management and improvements to the network management APIs

Note: For more z/OS Communications Server enhancements, refer to the Security and Availability sections.

Details on networking enhancements intended for z/OS V1.10:

  • Improved Network Stack Performance: z/OS Communications Server will focus on TCP/IP stack performance improvements in multiple areas, with designs intended to reduce CPU consumption and memory access latency, and improve throughput for all TCP/IP workloads.
  • Virtual Storage Constraint Relief: To provide virtual storage constraint relief, z/OS Communications Server will change the inbound data path to no longer use ECSA to hold inbound data for processing, or when queueing the data to the application. The TN3270 Server will also be changed to reduce its ECSA usage for mapping of active sessions.
  • Multiple VLAN Support: z/OS Communications Server will allow you to configure multiple Virtual Local Area Networks (VLANs) from the same TCP/IP stack for a single OSA-Express QDIO port. Each TCP/IP stack supports a maximum of 8 VLANs per OSA per IP version. This eases OSA port consolidation, for example multiple 1G ports can be consolidated onto a single 10G port, without having to redesign the VLAN definitions in the IP network.
  • HiperSockets Multiple Write Facility: The IBM System z10 EC provides an enhancement for HiperSockets (Internal Queued Direct I/O) which is designed to improve the efficiency of the processing for internal LPAR-to-LPAR communications associated with large messages. The new HiperSockets Multiple Write Facility allows messages which span multiple output buffers to be transferred with a single write operation from the source LPAR. This enhancement will improve the HiperSockets throughput while also lowering the CPU cost related to the processing of transferring large messages from the source to the target LPAR. This function is also planned to be made available on z/OS V1.9 with a PTF in the second quarter of 2008.
  • TN3270E Telnet Server is planned to provide shared LU name management among a group of servers running on the same system or within the same Telnet sysplex or subplex. Prior to this enhancement, LU names had to be manually partitioned among the TN3270E Telnet Servers to prevent concurrent assignment of the same LU name to clients connected to different servers. With this enhancement, one TN3270E Telnet Server in the group acts as an LU Name Server and allocates shared LU names to other TN3270E Telnet Servers within the group. This allows load balancing across multiple TN3270E Telnet Servers with consistent configurations. High availability of the LU Name Server service is provided with automated takeover and recovery.
  • Path MTU discovery for Enterprise Extender (EE) allows VTAM® to dynamically learn of any Maximum Transmission Unit (MTU) size changes that occur in the underlying IP network associated with IPv4 and IPv6 EE connections. With this knowledge, VTAM can segment the data to the appropriate size and avoid IP packet fragmentation.
  • APPN® Extended Border Node (EBN) support is enhanced to let you restrict the searching capability of adjacent non-native nodes without having to code a directory services management exit. The AUTHNETS value on the ADJCP statement specifies the list of authorized NETIDs for the adjacent control point. Searches received from that control point will be rejected if the destination LU's NETID is not in the authorized NETID list.
  • z/OS Communications Server introduces a new High Performance Routing start option (HPRSESLM) to limit the number of sessions that are placed on each Rapid Transport Protocol (RTP) pipe. Once an RTP pipe reaches the specified session limit, another RTP pipe is chosen or created for new sessions. Limiting the number of sessions on a single RTP pipe can result in improved performance on multiprocessor systems by allowing concurrent traffic on multiple RTP pipes.
  • A number of functional enhancements to z/OS FTP support are planned for z/OS V1.10:
    • The FTP Daemon, Server, and Client will all provide APPLDATA for the TCP connections which they use. This allows you to easily distinguish the TCP connections used by FTP from those used by other applications. APPLDATA is displayed in NETSTAT output, is available in SMF records, and is passed across the Network Management Interface (NMI).
    • The FTP Server support of Implicit Secure FTP is enhanced to allow the system administrator to decide which protocol to use to establish the implicit secure connection: the z/OS default protocol, or the de facto industry standard protocol. Using the de facto industry standard protocol for Implicit Secure FTP connection activation may result in compatibility with a greater variety of FTP clients.
    • FTP Server is enhanced to give the administrator greater control over which users can login to the FTP Server. A new keyword can be specified to optionally allow the FTP server to verify if the user has READ authority to the SERVAUTH profile EZB.FTP.systemname.ftpdaemonname.PORTxxxx. If the new keyword is specified, and the user is not authorized, then the user's login fails.
    • The FTP Server and Client handling of data set contention is improved, to issue messages that help you identify the contention, and to automatically retry the transfer to allow you to resolve the contention before failing the FTP attempt.
    • The FTP Server is enhanced to restrict the amount of time it spends retrying activation of the data connection to the FTP client. In addition, keepalives are supported on the data connection, to allow it to remain active even during times of inactivity that can occur when using FTP for long-running DB2 queries or jobs.
  • z/OS Communications Server is planned to generate SMF records for IPSec events such as secure tunnel activation, deactivation, and refresh for IKE tunnels, dynamic tunnels, and manual tunnels. These SMF events will be reported over the real-time SMF interface of the Network Management Interface (NMI), as well as over the traditional MVS SMF Exit interface. These unsolicited notifications of key security events can be used in conjunction with the polling NMI for security.
  • z/OS Communications Server will be designed to be compliant with RFC 4293, RFC 4292, RFC 4022, and RFC 4133 for the SNMP version-neutral MIBs. These are the MIBs that represent IPv4 and IPv6 objects. Additionally, Communications Server plans to enhance the SNMP generic LinkUp and LinkDown traps as described by RFC 2863 to include the ifName of the interface in the trap.
  • In z/OS V1.10, the configuration of Traffic Regulation (TR) policy as part of the Quality of Service discipline will no longer be supported. All TR functionality will need to be configured under Intrusion Detection Services (IDS) policy, which was first made available in z/OS V1.8. This change only applies to the TR policy configuration. The TR functions themselves remain unaffected.

 
Back topBack to top
 
Statement of direction
  • Network Database (NDB) function: z/OS V1.10 is planned to be the last release in which z/OS Communications Server will support the Network Database (NDB) function. After z/OS V1.10, the function will be removed from the product. Customers who currently use or plan to use the NDB function should investigate the distributed data facility (DDF) provided by z/OS DB2, and the DB2 Run-Time Client. DDF allows client applications running in an environment that supports DRDA to access data at DB2 servers.
  • BIND DNS 4.9.3: z/OS V1.10 is planned to be the last release in which z/OS Communications Server will support BIND DNS 4.9.3. After z/OS V1.10, the function will be removed from the product. BIND DNS 9.2.0 has been available since z/OS V1.4, and customers should implement this version as a replacement for BIND DNS 4.9.3. Customers that use the load balancing Connection Optimization (DNS/Workload Manager) feature of BIND DNS 4.9.3 should investigate Sysplex Distributor, the Load Balancing Advisor, Automated Domain Name Registration (ADNR), or other solutions.
  • Boot Information Negotiation Layer (BINL): z/OS V1.10 is planned to be the last release in which z/OS Communications Server will support the Boot Information Negotiation Layer (BINL). After z/OS V1.10, the function will be removed from the product. Customers using this function should investigate the use of IBM Tivoli Provisioning Manager for OS Deployment for network based operating system installation services.
  • DHCP server: z/OS V1.10 is planned to be the last release in which z/OS Communications Server will support the DHCP server function. After z/OS V1.10, the function will be removed from the product. Customers who currently use or plan to use the z/OS DHCP server should investigate using a DHCP server on Linux for System z.
  • IBM intends to provide support within z/OS that will allow authorized applications to query, change, and perform basic operational procedures against the installed System z hardware base. This support will provide a set of new high-level APIs for data exchange and command requests. The functionality, called Base Control Program Internal Interface (BCPii), will be delivered in the base of the operating system. This new support will not only allow control of the hardware the APIs are executing on, but extends to other System z processors within the attached process control network. This support will not require communication on an IP network for connectivity to the SE/HMC.
  • Continuing the tradition of delivering high z/OS system availability, IBM intends to provide an innovative predictive failure infrastructure that can help proactively identify potential problems before they affect application or system availability. The initial exploiter of the predictive failure infrastructure is planned to be the capability to detect abnormal usage of common storage.
  • As part of its long-term commitment to simplifying z/OS and System z operations and management and increasing the efficiency of IT professionals, IBM intends to introduce an IBM z/OS Management Facility, which will be designed to provide the infrastructure, services, and user interfaces to support a browser-based graphical user interface needed to support a management console for z/OS. The z/OS Management Facility is intended to enable technology administrators and operators to more easily manage and administer a z/OS system. The OMEGAMON® z/OS Management Console provides important z/OS display and monitoring capabilities; it is planned to coexist and integrate with the z/OS Management Facility.
  • Extended Address Volume: In z/OS V1.10, IBM intends to provide support for Extended Address Volume (EAV), a volume with more than 65,520 cylinders and initially available on the IBM System Storage DS8000 series. With the initial release, EAV will support 262,668 cylinders per volume (223 GB of addressable storage) for SMS and non-SMS managed VSAM data sets (except for catalogs, page data sets, and data sets defined with KEYRANGE or IMBED attributes). Any type of data set can reside in the first 65,520 cylinders of the volume. Access is the same as with existing DASD volumes. Only VSAM data sets can reside in the cylinders after the first 65,520 cylinders. In the future, IBM intends to expand support for EAV with larger volume sizes and to allow additional data set types to reside in the cylinders after the first 65,520 cylinders.
  • z/OS V1.10 is planned to be the last release of z/OS which will support the Integrated Security Services LDAP Server. A new optimized LDAP server, called IBM Tivoli Directory Server for z/OS, was delivered in the base of z/OS V1.8. Customers who are currently using the Integrated Security Services LDAP Server should investigate migrating to the Tivoli Directory Server for z/OS, which was designed to allow greater consolidation of LDAP directories on z/OS to help simplify enterprise management and disaster recovery. Detailed migration procedures to the IBM Tivoli Directory Server for z/OS are described in IBM Tivoli Directory Server Administration and Use for z/OS.
  • The enhancements to System-Managed Coupling Facility (CF) Duplexing to streamline CF-to-CF synchronization protocols, as described in Software Announcement 207-175 , dated August 7, 2007, will not be available in first quarter 2008. Plans related to this capability will be communicated at a later date.

All statements regarding IBM's plans, directions, and intent are subject to change or withdrawal without notice.
 
Back topBack to top
 

Reference information

Software Announcement 207-175 , dated August 7, 2007 (IBM z/OS V1.9 delivers a highly secure infrastructure you need for your demanding data serving requirements)

Software Announcement 207-018 , dated February 6, 2007 (Preview: IBM z/OS V1.9 advanced infrastructure solutions for your business needs)

Software Announcement 206-190 , dated August 8, 2006 (IBM z/OS V1.8 — Extending the enterprise-wide role)

Software Announcement 206-191 , dated August 8, 2006 (IBM z/OS.e V1.8 — Affordability for mainframe enterprise and Web-based applications)

Business Partner information

If you are a Direct Reseller - System Reseller acquiring products from IBM, you may link directly to Business Partner information for this announcement. A PartnerWorld ID and password are required (use IBM ID).

BP Attachment for Announcement Letter 208-042

Trademarks

 
System z, System Storage, HyperSwap, System z9, DS8000, IMS, DFSMSrmm, DFSMShsm, Hiperspace, RMF, POWER5, GDPS, DS6000, MVS, and DFSMSdss are trademarks of International Business Machines Corporation in the United States or other countries or both.
 
z/OS, TotalStorage, Parallel Sysplex, RACF, AT, DB2, Language Environment, CICS, FlashCopy, WebSphere, DRDA, AIX, Tivoli, zSeries, eServer, Working Together, VTAM, APPN, OMEGAMON, and z/OS are registered trademarks of International Business Machines Corporation in the United States or other countries or both.
 
Windows is a registered trademark of Microsoft Corporation.
 
Java is a trademark of Sun Microsystems, Inc.
 
UNIX is a registered trademark of the Open Company in the United States and other countries.
 
Linux is a trademark of Linus Torvalds in the United States, other countries or both.
 
Other company, product, and service names may be trademarks or service marks of others.

Services

IBM provides many services that can help analyze, maintain, deploy, and/ or optimize your z/OS® environment. Here are some new services from IBM:

IBM Rapid Deployment

Increasing business demands have companies rethinking their approach to quickly delivering a responsive and secure environment. To facilitate this with the installation and implementation of z/OS and DB2®, IBM Systems and Technology Group (STG) Lab Services introduces the IBM Rapid Deployment of z/OS and DB2 services offering.

This new service is intended for customers new to z/OS who want a predefined, preintegrated, preconfigured, and pretested z/OS and DB2 environment and who want this environment deployed quickly. IBM STG Lab Services can have a new mainframe system operational and optimized for use as a data server within days. The data serving environment is defined using IBM best practices and is configured for high availability and high scalability.

The IBM Rapid Deployment service delivers an environment designed to support business workloads ranging from transactional to SAP and data warehousing. The result is a simplified, complete system for deploying your applications that incorporates enhanced features such as data sharing on IBM hardware in a pretested configuration.

IBM Implementation Services for Parallel Sysplex® Middleware — DB2 data sharing

To assist with the assessment, planning, implementation, testing, and backup and recovery of a System z™ DB2 data sharing environment, IBM Global Technology Services announced and made available the IBM Implementation Services for Parallel Sysplex Middleware — DB2 data sharing on February 19, 2008.

IBM Implementation Services for Parallel Sysplex Middleware — DB2 data sharing is designed for clients who want to:

  1. Enhance the availability of their data
  2. Enable applications to take full utilization of all servers' resources
  3. Share application system resources in order to meet business goals
  4. Manage multiple systems as a single system from a single point of control
  5. Respond to unpredicted growth by quickly adding computing power to match business requirements without disrupting their business
  6. Build on the current investments in hardware, software, applications, and skills while potentially reducing computing costs

The offering consists of six selectable modules; each is a stand-alone module that can be individually acquired. The first module is an infrastructure assessment module, followed by five modules which address the following DB2 data sharing disciplines:

  1. DB2 data sharing Planning
  2. DB2 data sharing Implementation
  3. Adding Additional data sharing Members
  4. DB2 data sharing Testing
  5. DB2 data sharing Backup and Recovery

For more information on this offering, you may visit the Web site below or contact your IBM representative.

IBM Data Mobility Services

In order to be flexible and adaptive to changing business needs, you need the freedom to move data easily — regardless of how and why it is moved. Whether you need to move data for storage consolidation or optimization, perform nondisruptive backups, replicate data for disaster recovery/business continuity, or create remote archives for data protection, you need the flexibility to perform all of these activities with minimal disruption.

IBM provides a wide range of data mobility solutions. Discovery, assessment and design, planning, implementation, and validation services are available for all of your data migration projects from simple to complex utilizing the Softek family of data mobility products:

  • Softek Logical Data Migration Facility (LDMF) enables you to consolidate data onto large-capacity, better-performing volumes without interruption to the 24 x 7 business environment. Since manual data-set-level migration is complex and disruptive, Softek LDMF is designed to perform migrations while data sets remain open, so applications remain available, reducing downtime. Softek LDMF is storage-vendor-independent, host-based software that enables data set migration across storage vendor arrays.
  • Softek Transparent Data Migration Facility (TDMF) z/OS enables you to migrate data without disrupting business applications. Softek TDMF z/OS is an industry-leading, host-based software solution for data migration, designed for data centers with multiple system images and the need for continuous application availability, and provides local or distance migration with no downtime required.
  • Softek Data Mobility Console for z/OS (DMCzOS) is an enterprise storage solution that addresses the required monitoring and management practices in conjunction with the migration challenges and core functions of today's enterprise storage manager. DMCzOS helps you create and manage data migration efforts across your enterprise throughout the entire migration cycle:
    • Assesses the environment by classifying your data into migration categories to ensure information is readily available to make the most effective migration decisions
    • Plans data migrations by allowing you to create a custom migration process from the centralized console
    • Moves and validates data via automatic interface with Softek TDMF z/OS
    • Manages data migrations via a centralized console with reporting capability for visibility and control across multiple systems

These products can provide you with enhanced flexibility in z/OS environments by moving data nondisruptively on-line at either the volume or data set level.

For more information on these services, visit the Web site below or contact your IBM representative.

GDPS™ V3.5 enhancements

The automation in GDPS can give your disaster recovery (DR) solution the added peace of mind of always being ready. Many companies practice disaster recovery testing, but a real disaster is not a test. Procedures may not be current or key people may be unavailable. Recovery from an actual disaster may take significantly longer than planned, which may affect bottom-line revenue for the business. GDPS helps remove these concerns by managing and monitoring remote copy disk when properly configured, combined with features designed to automate the recovery actions. In addition, GDPS provides automation capabilities for planned data center activities. This helps to remove people as a single point of failure.

With the planned general availability of GDPS V3.5 on March 31, 2008, GDPS V3.5 is designed to enhance heterogeneous data management, expand GDPS/XRC availability and scalability, and help improve usability. This can be achieved through new functions such as:

  • GDPS integration with Veritas Cluster Server (VCS) and Geographically Dispersed Open Clusters (GDOC). This is designed to provide coordinated disaster recovery across System z and non-System z servers if Veritas Cluster Server is already installed. Initial support will be for GDPS/PPRC and GDPS/XRC.
  • Enhanced GDPS/GM system management with a graphical user interface. The GUI has been available since March 2007 for GDPS/PPRC and GDPS/PPRC HM with GDPS V3.4.
  • Greater disk efficiency with support for Space Efficient FlashCopy®.
  • Improved scalability with z/OS Global Mirror Multiple Reader.
  • Increased availability with support for z/OS Global Mirror Incremental Resync available in 2008.

More detailed information on the GDPS service offerings is available at

Installation and customization

The Customized Offerings Driver (COD) is a prebuilt stand-alone driving system that can be used to drive the installation of z/OS using CBPDO or ServerPac if you do not have a driving system or your driving system does not meet the minimum driving system requirements. Effective March 21, 2008, the Customized Offerings Driver V2.4 (5655-M12) is planned to contain a subset of z/OS V1.8 and be service updated to support the System z10 EC. Effective September 2008, the Customized Offerings Driver V2.4.1 (5655-M12) is planned to be service updated to support the minimum driving system requirements for installing z/OS V1.10. Currently, the Customized Offerings Driver V2.3.1 contains a subset of z/OS V1.8 and meets the minimum driving system requirements for installing z/OS V1.9.

Fee-based software services offerings

IODF by host FTP now available

To send your I/O Definition File (IODF) for your SystemPac® order, you had to use your workstation Internet connection. Now, you can submit an IODF directly from your z/OS host using the CustomPac FTP utility. Sending an IODF using the host FTP option not only provides you with an alternate path to send your IODF files to IBM in case you can't connect to the IBM FTP server with your workstation, but this option does not require Java™ applets with your browsers.

For more information on CustomPac go to

Important Web sites

Reference information

Software Announcement 207-175 , dated August 7, 2007 (IBM z/OS V1.9 delivers a highly secure infrastructure you need for your demanding data serving requirements)

Software Announcement 207-018 , dated February 6, 2007 (Preview: IBM z/OS V1.9 advanced infrastructure solutions for your business needs)

Software Announcement 206-190 , dated August 8, 2006 (IBM z/OS V1.8 — Extending the enterprise-wide role)

Software Announcement 206-191 , dated August 8, 2006 (IBM z/OS.e V1.8 — Affordability for mainframe enterprise and Web-based applications)

Customized Offerings

Product deliverables are shipped only via Customized Offerings (for example, CBPDO, ServerPac, SystemPac).

CBPDO and ServerPac are offered for Internet delivery, where ShopzSeries product ordering is available. Internet delivery of ServerPac may help improve automation and software delivery time. For more details on Internet delivery, refer to the ShopzSeries help information at

Media type for this software product is chosen during the customized offerings ordering process. Based on your customer environment, it is recommended that the highest possible density tape media is selected. Currently offered media types are:

  • CBPDOs — 3480, 3480 Compressed, 3490E, 3590, 35923
  • ServerPacs — 3480, 3480 Compressed, 3490E, 3590, 35923
  • SystemPacs — 3480, 3480 Compressed, 3490E, 3590, 35923
3
3592 is highest density media. Selecting 3592 will ship the fewest number of media.

Trademarks

 
System z and GDPS are trademarks of International Business Machines Corporation in the United States or other countries or both.
 
DB2, Parallel Sysplex, FlashCopy, SystemPac, and Open Class are registered trademarks of International Business Machines Corporation in the United States or other countries or both.
 
Java is a trademark of Sun Microsystems, Inc.
 
Other company, product, and service names may be trademarks or service marks of others.

Back to topBack to top
 

 
Printable version Printable version