Ibm ZOS V1.12 User Manual

IBM United States Software Announcement

210-008, dated February 9, 2010

Preview: z/OS V1.12 - Heralding a new generation of smart operating systems

Table of contents

1	Overview	3	Description
2	Key prerequisites	27	Statement of general direction
3	Planned availability date	27	Product number
		29	Corrections

At a glance

IBM® previews z/OS® Version 1.12. With this latest release of z/OS, IBM heralds a new area of smart operating systems by creating an environment that can proactively work for you to help promote improved operations, availability, manageability, and security through innovative self-learning, self-managing, and self-optimization capabilities. Enhancements include:

•Predicting problems - z/OS Predictive Failure Analysis® (PFA) is planned to monitor the rate at which SMF records are generated. When the rate is abnormally high for a particular system, the system will be designed to issue an alert to warn you of a potential problem, potentially avoiding an outage.

•Real-time decision making in the event of a system problem - A new z/OS Run Time Diagnostics function is planned to help you quickly identify possible problems in as little as one minute.

•Automatic partitioning - GRS and XCF components are planned to automatically initiate actions to preserve sysplex availability to help reduce the incidence of sysplex-wide problems that can result from unresponsive critical components.

•Avoiding data fragmentation and planned outages for data reorganizations - With the new CA (Control Area) Reclaim capability, applications that use VSAM keysequenced data sets (KSDSs) can benefit from improved performance, minimized space utilization, and improved application availability though the avoidance of planned outages that used to be required to defragment and reorganize this data.

•Workload driven provisioning - Capacity Provisioning is planned to use CICS® and

IMSTM monitoring data to determine if additional resources are needed to meet service-level requirements for these workloads.

•Storage management and scaling - Extended Address Volumes are planned to support additional data set types, including sequential (both basic and large) data sets, partitioned (PDS/PDSE) data sets, catalogs, and BDAM data sets. Overall, EAV helps you relieve storage constraints as well as simplify storage management by providing the ability to manage fewer, large volumes.

•Advanced cryptography - z/OS is planned to support Elliptic Curve Cryptography (ECC), which is regarded by the U.S. National Security Agency (NSA) as a faster algorithm that requires a smaller key than RSA cryptography. This function is embedded into z/OS and is not a separately chargeable product.

Overview

Imagine, an IT system that knows your priorities and can make suggestions - even decisions - that can benefit your business. IBM previews z/OS V1.12. With this latest release of z/OS, IBM heralds a new direction of smart operating systems by creating an environment that can proactively work for you to help promote improved

IBM United States Software Announcement 210-008

IBM is a registered trademark of International Business Machines Corporation

operations, availability, and manageability through innovative self-learning, selfmanaging, and self-optimization capabilities.

z/OS is designed to learn heuristically from its own environment to anticipate and report on system abnormalities, predicting problems before they occur with its innovative Predictive Failure Analysis (PFA) capability. For example, PFA can be used during application testing to identify previously unknown potential problem areas before the application is put into production or can be used in production systems to help identify issues before they become serious.

In the event of an issue, z/OS can help you be responsive with real-time decision making assistance. A new z/OS Run Time Diagnostics function is planned to analyze key indicators on a running system quickly, and help identify the root causes of system degradations. The Run Time Diagnostics function is anticipated to run in as little as one minute, to return results quickly enough to help you choose between alternative corrective actions and help you maintain high levels of system and application availability.

In some situations, your operations may be so critical that human analysis and intervention may not be fast enough, and the system must have the ability to act quickly and decisively. In a Parallel Sysplex®, the GRS and XCF components are planned to have the ability to automatically initiate actions to preserve sysplex availability so as to help reduce the incidence of sysplex-wide problems that can result from unresponsive critical components. The system can take action to fence, or stop and start critical members automatically, preventing small problems from becoming major problems.

And in still other situations, z/OS keeps your system available automatically and transparently. z/OS will be designed to avoid data fragmentation and planned outages for data reorganizations. With the new CA (Control Area) Reclaim capability, applications that use VSAM key-sequenced data sets (KSDSs) can benefit from improved performance, minimized space utilization, and improved application availability though the avoidance of planned outages that used to be required to defragment and reorganize this data.

z/OS V1.12 can save you time and money. This ability to discover, decide, and resolve issues automatically and in a fraction of the time can keep your organization nimble and responsive to changing business needs.

Key prerequisites

z/OS V1.12 is planned to run on these IBM System z® servers:

•z10TM EC

•z10 BC

•z9TM EC

•z9 BC

•z990*

•z890*

•z900*

•z800*

* These products are withdrawn from marketing.

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

IBM United States Software Announcement 210-008

IBM is a registered trademark of International Business Machines Corporation

Planned availability date

September 2010

Previews provide insight into IBM plans and direction. Availability, prices, ordering information, and terms and conditions will be provided when the product is announced.

Description

Ease of use

Simplification of an IT system has many rewards. It can address the need for skills by making existing personnel more productive and by reducing the time needed for someone new to gain proficiency on the platform. It can address overall operational efficiency by reducing the components and steps for tasks, and by streamlining existing processes. And it can address quality of service and availability by reducing the time involved with addressing a problem, or by reducing the probability of the error even being introduced.

Ultimately, simplification can make your IT organization more responsive in meeting business needs because IT systems and processes are less apt to get in the way when action and agility are needed. This is IBM's long-term goal for mainframe simplification. More than a "screen scraper" or a pop-up installation shield and more than new layers of management processes, IBM has taken the long-term outlook by simplifying a mainframe system from the inside out and from end to end. IBM technologies are truly efficient and can help drive down the cost of complexity, reduce the cost from risk, and drive up user productivity and overall system agility.

IBM's commitment to mainframe simplification has been vast and has been delivered integrated into the platform stack. CICS Explorer provides CICS architects, developers, system programmers, and administrators a common tooling environment, with integrated access to a wide range of data and control capabilities. DB2® Data Studio provides an integrated set of tooling to support all phases

of the data management life cycle. IMS is planned to provide a new integrated development environment and operational console to accelerate the development time for new IMS applications and optimize collaboration between IMS DBAs, system programmers, and application developers. Rational® Developer for System z helps simplify collaboration, development, and delivery of business applications and integrate existing core business applications with Web services and SOA. Tivoli® Service Management Center provides a set of integrated solutions and building blocks that allows a business to implement an enterprise-wide service management and process automation hub on System z. These technologies have the power to reduce application development, deployment, and management times significantly.

z/OS has had many improvements in the area of simplification as well. The past several releases of z/OS delivered improvements in the areas of simplifying diagnosis and problem determination; network and security management;

and overall z/OS I/O configuration, sysplex, and storage operations. These improvements are designed to help simplify systems management; to improve application programmer, system programmer, and operator productivity; and to provide fewer opportunities for the introduction of human errors.

•The z/OS Management Facility (z/OSMF, 5655-S28) is the new face for z/OS and it provides support for a modern, Web-browser-based management console for z/OS. Automated tasks and wizards can guide users through tasks and help provide simplified operations. In z/OSMF V1.11, for example, tasks taking up to

20 minutes, such as collecting and packaging dump data, can now take as little as 30 seconds.

For its next release, z/OSMF V1.12 is planned to be expanded with the addition of z/OS Workload Manager Policy Editor functionality, enhancements to the already valuable Incident Log and Configuration Assistant for the z/OS Communications

IBM United States Software Announcement 210-008

IBM is a registered trademark of International Business Machines Corporation

Server functions, and the ability to add non-z/OSMF application launch points and links.

•IBM Health Checker for z/OS has a long history of helping to simplify and automate the identification of potential configuration problems before they impact system availability by comparing active values and settings to those suggested by IBM or defined by your installation. The z/OS Health Checker is extremely valuable not only in identifying exceptions to z/OS configurations, but also in identifying migration actions and checking that these migration actions are completed accurately. In addition, output reports from the z/OS Health Checker may be used to support your corporate compliance. For example, z/OS Health Checker reports can help identify unsecured resources that should be RACF® protected, can help validate the redundancy in a Parallel Sysplex configuration, and could be used as part of risk assessment exercises.

For z/OS V1.12 z/OS Health Checker is planned to be updated with the ability to write checks in Metal C, and with the addition of checks for Parallel Sysplex (such as best practices for coupling facility structure size, couple data set specification limits, Sysplex Failure Manager policies, and coupling facility allocation), SMB

server, DFSMSTM, I/O Supervisor, TCP/IP IPv4 and IPv6 usage, HFS to zFS migration, and still others.

•There are additional ease-of-use enhancements planned to help prevent JCL errors from duplicate temporary data set names, simplify Language

Environment® and zFS migration, simplify RMFTM processing, improve performance, and create a customized view for the Library Server.

Details on the ease-of-use and platform-simplification enhancements intended for z/ OS V1.12:

•The following functions are planned for z/OSMF V1.12:

–The z/OSMF Configuration Assistant for z/OS Communications Server is planned to:

--Support the configuration of IKE version 2.

--Enforce RFC4301 compliance for IPSec filter rules.

--Support the configuration of certificate trust chains and certificate revocation lists.

--Support the configuration of new crytographic algorithms for IPSec and IKE.

--Support the configuration of FIPS 140 cryptographic mode for IPSec and IKE.

–WLM Policy Editor functionality to be integrated into z/OSMF V1.12 will facilitate the creation and editing of WLM service definitions, installation of WLM service definitions, and activation of WLM service policies, and monitoring of the WLM status of a sysplex and the systems in a sysplex.

–A number of improvements for the Incident Log function including support for encryption of all incident files, including dumps, to be sent to IBM, breaking dumps into multiple data sets that can be sent via FTP in parallel to reduce transmission time, specifying additional data sets to an incident and adding free-form comments to new fields for problem descriptions and FTP destinations. Incident Log will also support the creation of diagnostic log snapshots based on the SYSLOG and LOGREC data sets, as well as the

OPERLOG and LOGREC sysplex log streams. These enhancements are intended to help you manage problem data more easily.

–An interface to allow the addition of non-z/OSMF launch points and links to the navigation tree.

–z/OSMF is planned to support Microsoft® Internet Explorer 7 and Internet Explorer 8, Mozilla Firefox 3.0, and Firefox 3.5.

•The Health Checker framework is enhanced to allow health checks to be registered without a message table and for them to issue messages directly without using a message table. This makes it easier to write health checks quickly.

•The Health Checker framework is planned to provide headers to enable you to write health checks using Metal C, in addition to existing support for High-Level Assembler and REXXTM. Providing high-level language support can make it easier

IBM United States Software Announcement 210-008

IBM is a registered trademark of International Business Machines Corporation

to write complex health checks. Additionally, sample health checks written in METAL C are planned.

•New health checks are planned for the Parallel Sysplex components, XCF and XES. They are designed to warn you when a coupling facility structure's maximum size as specified in the CFRM policy is more than double its initial size, when

any couple data set's (CDS's) maximum system limit is lower than the primary sysplex CDS's system limit, when shared CPs are being used for coupling facility partitions, when the CFRM message-based event management protocol can

be used for CFRM event management but the policy-based protocol is being used instead, when your Sysplex Failure Management (SFM) policy does not specify that automatic actions are to be taken to relieve hangs caused by the unresponsiveness of one or more of a CF structure's users, and when a CF does

not have a designated percentage of available space to allow for new CF structure allocation, structure expansion, or CF failover recovery. These checks can help you correct and prevent common sysplex management problems.

•SMB server is planned to add two health checks. The first is designed to detect SMB running in a shared file system environment and alert you that SMB cannot export zFS sysplex-aware read-write file systems in this environment, and the second to determine whether SMB is configured to support the RPC protocol (DCE/ DFS) and display a message to remind you that IBM plans to withdraw support for this protocol in a future release.

•DFSMS is planned to add new health checks for the communications and active configuration data sets (COMMDS and ACDS). One new check is designed to alert you that the COMMDS and ACDS are on the same volume. The other is intended to identify COMMDS and ACDS data sets that were defined without the REUSE attribute, which is recommended. These new checks can help you manage your SMS environment.

•New health checks are designed for the I/O Supervisor (IOS). IBM recommends using the relatively new MIDAWs and Captured UCB Protection functions introduced in recent releases, and locating eligible I/O-related control blocks above the 16 MB line. These health checks are designed to notify you when these functions are not being used, to help you manage system performance and the use of virtual storage.

•The Health Checker started task is planned to support running with an assigned user ID that has access to the BPX.SUPERUSER profile in the FACILITY CLASS. This will make it unnecessary to run the Health Checker address space with a user ID having UID(0).

•z/OS Communications Server is planned to enhance the z/OS Health Checker for z/OS by adding two new checks: one check for IPv4 routing and one check for IPv6 routing. The checks determine whether the total number of indirect routes in the TCP/IP stack routing table exceeds a maximum threshold (default 2000). When this threshold is exceeded, OMPROUTE and the TCP/IP stack can potentially experience high CPU consumption from routing changes.

Two new maximum threshold parameters are planned to override the default values for the total number of IPv4 and IPv6 indirect routes in a TCP/IP stack routing table before warning messages are issued.

•IBM recommends that you use zFS file systems for z/OS UNIX® System Services. In z/OS V1.12, a migration health check is planned to identify HFS file systems you should consider migrating to zFS file systems. This is intended to help you easily obtain and track the list of remaining file systems to be converted.

•When two or more jobs having the same job name begin to process within the same system clock second and specify the same temporary data set names, the second and subsequent jobs will fail with JCL errors while attempting to allocate data sets with duplicate names. In z/OS V1.12, you will be able to use a new parmlib option to specify that the system use the data set naming convention for unnamed temporary data sets instead, which substantially reduces the probability of this JCL error without the need to change JCL.

•In z/OS V1.7, Language Environment allowed overridable run-time options to be defined in a new CEEPRMxx member of parmlib. In z/OS V1.12, this is extended to add support for non-overridable (NONOVR) options. This new support can allow you to specify the options for Language Environment without user modifications, eliminating a repetitive migration task.

IBM United States Software Announcement 210-008

IBM is a registered trademark of International Business Machines Corporation

•DFSMSrmmTM is planned to be enhanced for z/OS V1.12. The reason why a DFSMSrmm retention limit was reached is planned to be added to the ACTIVITY file. This function is also available now for z/OS V1.10 and z/OS V1.11 with the PTF for APAR OA30881. New reports created from the ACTIVITY and extract files are planned to help you see why retention limits were triggered. Also,

OPENRULE ignore processing is planned to be available for duplicate tape volumes and support is planned to allow you to set a volume hold attribute to prevent expiration and to search and report on volumes which have the hold attribute. It is also planned that the DFSMSrmm ISPF dialog search results can be bypassed when using the CLIST option.

•DFSMS plans to provide a system option to control how the system handles multivolume tape label anomalies. This means that you can now prevent applications processing tape volumes out of sequence without coding an installation exit.

•The Interactive Storage Management Facility (ISMF), used to manage your SMS configuration, allows you to copy storage group definitions from one control data set (CDS) to another. In z/OS V1.12, ISMF is extended to allow you to specify that the volume list for pool-type storage groups be copied at the same time. This allows you to copy entire storage groups from one configuration to another without having to add their volumes to the destination CDS afterward.

•The JESXCF component is changed to allow you to log on to multiple systems within a sysplex using the same TSO/E user ID.

•DFSMSdfpTM is planned to allow a zFS data set to be recataloged with an indirect volume serial or system symbol. This is designed to allow the zFS file systems used for z/OS system software files (called version root file systems) to be cataloged using an indirect volume serial or a system symbol the same way as non-VSAM data sets to make cloning and migration easier.

•In prior releases, partial release operations for VSAM data sets supported releasing space only on the last volume containing data for each data set. In z/ OS V1.12, partial release is planned to be extended to support releasing unused volumes in addition to releasing space on the last volume of a multivolume VSAM data set that contains data.

•The IDCAMS DEFINE RECATALOG command is planned to be enhanced for multivolume and striped data sets. This new function will be designed to automatically create catalog entries with correctly ordered volume lists while eliminating any duplicate volumes that might have been specified. This will make it easier to recatalog multivolume and striped VSAM data sets.

•IDCAMS is planned to be enhanced to allow you to delete all members of a partitioned data set in a single operation by specifying a wildcard character (*) as the member name for a data set when using the DELETE command. This new support allows you to remove all members of a PDS or PDSE data set in a single command.

•The Capacity Provisioning Control Center is planned to support displaying provisioning reports supported by the Capacity Provisioning Manager. This is intended to simplify the investigation of Capacity Provisioning reports and operation of the Capacity Provisioning server.

•In z/OS V1.9, support was added to write SMF data to log streams. In z/OS V1.12, RMF is planned to be enhanced to read SMF records directly from a log stream. This is intended to allow you to eliminate any intermediate steps you currently use to unload SMF data from a log stream to a sequential data set for RMF postprocessing.

•The Capacity Provisioning Manager client is planned to be updated to provide support for Windows® Vista.

•Library Server is designed to improve performance when building new catalogs and supporting multiple users on heavily loaded systems. A new Personal BookCase function in Library Server is planned to allow you to create, use, and share your own subset of the documents from a Library Server catalog. This function is designed to allow you to configure a Personal BookCase that includes the shelves and documents, as well as the infocenters and topics, that you are interested in so you can have the reference documents you routinely use available quickly. Also, indexing is planned to capture the author's intended definition of primary nodes for an InfoCenter's Table of Contents, and planned administrative improvements include long filename support, programmatically checking for the

IBM United States Software Announcement 210-008

IBM is a registered trademark of International Business Machines Corporation

required level of JavaTM, and generation of a new Test and Diagnostics page for use by Library Server administrators and IBM support personnel.

Library Server usability enhancements are planned for user interfaces, including improved navigation between certain dialogs, modernized icons, and descriptive hover popups for documents on a shelf.

•SDSF is planned to augment the CK panel by displaying recorded checks on a new health check history panel. The default will be to display up to ten prior iterations of each check from the log stream, and support is planned to allow you to browse and print check output from the history panel as you can on the primary CK panel.

•SDSF is designed to support displaying information about printers for JES3, and to eliminate the requirement for WebSphere® MQ when displaying JES2 MAS-wide data on the initiator panel for JES2 once all systems in the MAS are at z/OS V1.12 JES2. Also, displaying MAS-wide data on the printer panel for JES2 is planned not to require WebSphere MQ when all systems in the JES2 MAS are at or above z/OS V1.11 JES2.

•In z/OS V1.12 a new DISPLAY XCF,REALLOCATE,TEST option is planned to simulate the reallocation process and provide information about changes the REALLOCATE command would attempt to make, and any errors that might be encountered if an actual REALLOCATE process were to be performed. This

capability is intended to provide information you can use to decide when to invoke the actual REALLOCATE process, and also whether you may need to make any coupling facility configuration changes before issuing the actual REALLOCATE command. A new DISPLAY XCF,REALLOCATE,REPORT command is also planned, to provide detailed information on the results experienced by a previously executed REALLOCATE command. This capability is intended to help you find such information without searching through the system log for REALLOCATE-related processing and exception messages.

•A number of enhancements are planned to be made to the processing of PROGxx parmlib members and to Link List Lookaside (LLA) processing. These include support in PROGxx for passing a specified parameter to a dynamic exit,

automatically including alias names for modules to be placed in Dynamic LPA, and specifying volumes on SYSLIB for data sets so they need not be cataloged in the master catalog; a REPLACE option for exits to assure there is no window during which an exit is unavailable; and a new SVCNUMDEC keyword to specify the SVC number to be added.

–Additionally, a new DEFAULTS statement is planned, so you can specify processing defaults intended to help prevent common errors. This includes allowing you to specify that LNKLST DEFINE always require COPYFROM, that it default to COPYFROM(CURRENT), and that it automatically process aliases for modules added to Dynamic LPA.

–LLA processing will be designed to support the use of dynamic LLA exits and to process multiple MODIFY commands in parallel.

•A new SUMMARY keyword of the DISPLAY SYMBOLS command is designed to provide summary information about symbols used on the system, including how many are in use. This can help you determine how many additional symbols can be defined.

•When a corrupt PDSE is detected in the link list during IPL, the system enters a wait state. In z/OS V1.12, the system will be designed to issue a message

identifying the corrupt PDSE prior to entering the wait state. This allows the user to attempt to restore the corrupt PDSE and re-IPL the system and avoid taking a standalone dump to debug the problem.

•System Logger is planned to be enhanced to correct the VSAM SHAREOPTIONS for new log stream data sets when it detects that they are not correctly set. Messages are planned to indicate that Logger has detected and corrected a data set's SHAREOPTIONS settings. This new function is intended to prevent data set access problems from arising when SHAREOPTIONS(3,3) has not been set in the data class used to allocate log stream data sets.

•System Logger is planned to be enhanced to support log data set sizes up to 4 GB (from the previous 2 GB limit). This applies to both OFFLOAD and STAGING data set types. As part of this support, System Logger is planned to add messages to show key data set characteristics at allocation and deletion time. This support is

IBM United States Software Announcement 210-008

IBM is a registered trademark of International Business Machines Corporation

planned to be made available for z/OS V1.9, z/OS V1.10, and z/OS V1.11 with PTFs for APAR OA30548 in February 2010.

Scalability and performance

The traditional view on scalability and performance has been to throw more hardware at something, or to wait and upgrade to faster hardware. This hardwarecentric approach has worked for many years with the introduction of ever-larger distributed clusters and storage arrays, and higher-speed and denser chip designs. But the industry has begun to hit fundamental physical limits for chip design. Largemagnitude CPU speed increases with each generation of chip are a thing of the past and capacity increases will increasingly come not from raw hardware capabilities, but from a deeper type of technical alignment.

IBM System z has long understood the balance between scalability and performance and efficiency of the platform. The major components of the system, the processors, storage, I/O, and software, work together and help manage system resources.

Essentially, z/OS and its subsystems provide for scalability not only based on faster chip speeds, but also via efficient single-image n-way processor growth, highly scalable sysplex clustering for horizontal growth, and scalable storage and data management as well.

z/OS has had many scalability/performance improvements over the past several releases. For example, z/OS V1.9 HiperDispatch can provide significant performance gains for large LPARs through smarter dispatching of workloads on higher n-way systems, and with z/OS V1.10 XL C/C++ workloads gained up to 8% performance improvements with new compiler options and System z10® prefetch capabilities.

•Parallel Sysplex is many clustering solutions in one. A single cluster can be used for scalability, performance, availability, software migrations, and disaster recovery. While other platforms are just beginning to grasp the cloud concept, Parallel Sysplex has been providing a dynamic cloud-like environment, where

resources and workloads can seamlessly move to where they are needed, for over a decade. Parallel Sysplex provides a large single system image, dynamic load balancing, fault tolerance, and automatic restart capabilities. No other technology can compare -- other coupling capabilities are implemented in software, or loosely linked with non-integrated tools. With z/OS V1.12, Parallel Sysplex technology is planned to be updated with support for larger coupling facility structures.

•The scale and efficiency of System z do not end with the server. The amount of data being stored by organizations is going up exponentially. Much of this has to do with the wide variety of data formats and streams that are available, but a good part of the explosion of data is probably from management (or mismanagement) of a tremendous amount of data. The more data there is, the greater the need for availability, scalability, security, and networking, and the higher the risk from storage outages. Data on z/OS can help alleviate these problems. Data Facility Storage Management Subsystem (DFSMS) is a software suite that automatically manages data from creation to expiration and provides

a consistent, policy-driven approach to storage management across the storage hierarchy. DFSMS provides allocation control for availability and performance, backup/recovery and disaster recovery services, space management, tape management, and reporting and simulation for performance and configuration tuning. DFSMS can help you drive storage utilization and efficiency up to well over 90%. With z/OS V1.12, DFSMS supports additional data set types in Extended Address Volumes (EAVs). EAVs can help relieve storage constraints as well as simplify storage management by providing the ability to manage fewer, large volumes as opposed to many small volumes.

•z/OS V1.12 also is planned to have updates for constraint relief for large volumes of DASD and tape data sets and concurrently open data sets, with new designs in the Program Management Binder, TSO/E, RACF, OAM, DFSMS, XCF, and InfoPrint® Server for z/OS. In addition, numerous improvements to dump management

are planned to address the continued growth in diagnostic data that comes from larger systems and larger programs using ever-larger amounts of memory. These improvements can help you keep dump time and dump transmission time under control.

IBM United States Software Announcement 210-008

IBM is a registered trademark of International Business Machines Corporation

Details on the performance and scalability enhancements intended for z/OS V1.12:

•DFSMS is planned to support additional data set types, including sequential (both basic and large) data sets, partitioned (PDS/PDSE) data sets, catalogs, and BDAM data sets in the extended addressing space (EAS) on an EAV. Support is also included for generation data groups (GDGs) and VSAM volume data sets (VVDSs). Overall, EAV helps you relieve storage constraints as well as simplify storage management by providing the ability to manage fewer, large volumes as opposed to many small volumes.

•Support is planned to make all data sets used by DFSMSrmm eligible for allocation in the extended addressing space of an EAV. This includes the DFSMSrmm journal and dynamically allocated temporary files.

•In z/OS 1.12, DFSMSrmm support for IPv6 is also planned.

•Language Environment provides support for C/C++ to access alternate indexes (AIXs) for extended format VSAM key-sequenced data sets (KSDSs) that reside in the EAS on an EAV.

•JES2 will be designed to allow both spool and checkpoint data sets to reside in the EAS on an EAV, making it possible to place both spool and checkpoint data sets anywhere on an EAV and to define spool data sets up to the maximum size of 1,000,000 tracks (approximately 56 GB).

•JES3 will be designed to allow spool, checkpoint, and Job Control Table (JCT) data sets to be placed anywhere on an EAV.

•Some workloads require an increasing number of open data sets. In z/OS V1.12, the BSAM, QSAM, and BPAM (basic and queued sequential, and basic partitioned access methods) and EXCP (execute channel program) processing will be designed to support the use of an extended task I/O table (XTIOT) with uncaptured UCBs, and support data set association blocks (DSABs) above the 16 MB line. This is expected to allow more data sets to be allocated by an address space and to provide virtual storage constraint relief for DASD and tape data sets.

•The SNAP/SNAPX services and dump processing (including that for SVC, SYSABEND, SYSMDUMP, and SYSUDUMP dumps), and the AMASPZAP program are planned to support XTIOT.

•The Program Management Binder will be designed to support data sets having XTIOT entries.

•TSO/E will be designed to XTIOTs, uncaptured unit control blocks (UCBs), and DSABs above 16 MB for data sets allocated by programs.

•RACF will be designed to support XTIOTs, uncaptured UCBs, and DSABs above 16 MB for data sets allocated by programs.

•DADSM and CVAF changes are planned to support XTIOTs, uncaptured UCBs, and DSABs above the 16 MB line. This is intended to help you take advantage of those functions to allow more concurrently open data sets and provide for virtual storage constraint relief.

•OAM is planned to provide API support for the Object Storage and Retrieval function (OSR) to run in a CICS threadsafe environment. This is intended to allow exploiters to take advantage of the improved multitasking and throughput capabilities provided by threadsafe programming. Additionally, the Volume Recovery utility will be designed to improve performance in certain situations when recovering object data stored on optical and tape media. Improvements are expected to be most noticeable when recovering a backup volume containing objects with primary copies in a large number of different collections on a large number of different volumes.

•Large (1 MB) pages were introduced in z/OS V1.10. In z/OS V1.12, the nucleus data area is planned to be backed using 1 MB pages. This is intended to reduce the overhead of memory management for nucleus pages and to free translation lookaside buffer (TLB) entries so they can be used for other storage areas. This is expected to help reduce the number of address translations that need to be performed by the system and help improve overall system performance.

•In z/OS V1.7, support was introduced in DFSMSdfp for large format sequential data sets (DSNTYPE=LARGE). In z/OS V1.8, Language Environment added support for these data sets using noseek (QSAM). Support for seek (BSAM) was limited to data sets no larger than 64K tracks on any volume when opened for read. In z/OS V1.12, seek (BSAM) support is planned to be extended to data sets

IBM United States Software Announcement 210-008

IBM is a registered trademark of International Business Machines Corporation

+ 20 hidden pages