z/OS announcements, statements of direction, and notable changes

The following z/OS statements of direction are available below:

• February 26, 2008
• August 7, 2007
• February 6, 2007
• August 8, 2006
• February 28, 2006
• July 26, 2005
• February 15, 2005
• August 10, 2004
• February 10, 2004
• October 7, 2003
• May 13, 2003
• August 13, 2002
• February 19, 2002
• September 11, 2001
• February 27, 2001
• October 3, 2000

z/OS statement of direction
February 26, 2008

• 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.

z/OS statement of direction
August 7, 2007

• Support for the VSAM KEYRANGE attribute will not be withdrawn as stated in announcement IBM z/OS V1.6: Integrating new applications and Preview: z/OS V1.7, Software Announcement 204-180 , dated August 10, 2004. No supported release of z/OS allows you to define new VSAM data sets with the KEYRANGE attribute. On modern storage devices, KEYRANGE is generally detrimental to performance. For this reason, IBM recommends that you minimize or eliminate your use of KEYRANGE. Striped data sets are expected to provide better performance than KEYRANGE, and can be viewed as a good replacement for KEYRANGE data sets. To detect the KEYRANGE attribute on existing data sets, refer to INFO APAR II13894. Use the DFSMShsm ARCTOOLS (FINDKRDS) to detect this attribute for data sets migrated with DFSMShsm. Details on how to use this tool are in the z/OS V1R9.0 DFSMShsm Implementation and Customization Guide (SC35-0418-06).



• z/OS XML to be enabled for both zAAP and zIIP specialty engines.

  In z/OS V1.8, IBM introduced a new z/OS component, z/OS XML System Services (z/OS XML). z/OS XML is a system-level XML parser integrated with the base z/OS operating system. It is designed to deliver an optimized set of services for parsing XML documents. z/OS XML has also been made available on z/OS V1.7 via APAR OA16303. The initial beneficiaries of this system component were middleware and applications requiring high-performance nonvalidating XML parsing. z/OS XML may be accessed by an Assembler or C/C++ programming interface. One of the first exploiters is DB2 9 for z/OS with its pureXML capabilities.

  With z/OS V1.9, IBM is announcing that the z/OS XML component is enabled to take advantage of System z Application Assist Processors (zAAPs). This enhancement means that middleware and applications requesting z/OS XML System Services (for example, DB2 processing using a local connection) have the capability for a portion of z/OS XML System Services processing to execute on a zAAP. Specifically, z/OS XML System Services parsing executing in TCB mode may be eligible to be redirected to a zAAP, when present.

  In the future, IBM intends to enable z/OS XML to take additional advantage of IBM System z9 Integrated Information Processors (zIIPs). Today, z/OS XML processing running under DB2 9 can already be partially directed to zIIPs when part of a distributed request (like DB2 DRDA). In the future, IBM intends to direct all eligible z/OS XML System Services processing to a zIIP when it forms part of any zIIP eligible workload (like DRDA). Specifically, z/OS XML System Services parsing workload run in enclave service request block (SRB) mode is planned to be redirected to a zIIP, when present.

  IBM also intends to extend and expand on the use of z/OS XML System Services for additional enhancements:

  • IBM intends to enhance the XML Toolkit for z/OS so eligible workloads use z/OS XML. This allows eligible XML Toolkit processing to exploit zAAP specialty engines.
    
    
  • IBM intends to add validating parsing to z/OS XML System Services. This extends zAAP and zIIP exploitation to include XML validating parsing workload as well.
  
  
  
• IBM intends to remove support for CPU affinity. CPU affinity originally provided support for assigning work to the same CP. However, this predates PR/SM™, which introduced logical processors. CPU affinity has long been obsolete for z/OS partitions operating under PR/SM™, which makes the CP on which a piece of work executes unpredictable. z/OS V1.9 is planned to be the last release to provide support for the assignment of CPU affinity to a logical processor. Future releases will ignore any attempt to assign CPU affinity. For example, specifications for assigning a program to a specific logical processor or processors using the Program Properties Table (PPT) or a SCHEDxx member of parmlib will be ignored.
  
  

IBM intends to take the following actions in a future release:

• In a future release of z/OS, when DFSMShsm or DFSMSdss™ recalls or restores a VSAM data set with either IMBED or REPLICATE attribute or both, the attributes will be removed. No supported release of z/OS allows you to define new VSAM data sets or catalogs with the IMBED or REPLICATE attributes, and using them for existing data sets can waste DASD space and can often degrade performance. IBM recommends that you stop using these attributes. For information about how to detect IMBED and REPLICATE attributes on existing data sets and catalogs, refer to INFO APAR II13894.
  
  
• In a future release of z/OS, the Network Database (NDB) function will be removed from the z/OS Communications Server component. 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.
  
  
• In a future release of z/OS, the Dynamic Host Configuration Protocol (DHCP) server function will be removed from the z/OS Communications Server component. Customers who currently use or plan to use the z/OS DHCP server should investigate using a DHCP server on Linux for System z.
  
  
• In a future release of z/OS, the Boot Information Negotiation Layer (BINL) function will be removed from the z/OS Communications Server component. Customers using this function should investigate the use of IBM Tivoli Provisioning Manager for OS Deployment for network-based operating system installation services.

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

Key dates

• August 7, 2007: z/OS V1.9 CFSW configurator support for stand-alone path (5694-A01) and price proposal support.
  
  
• September 14, 2007: First date for ordering z/OS V1.9 ServerPac, SystemPac, CBPDO using CFSW configuration support, or ShopzSeries, the Internet ordering tool. Note that most z/OS media (executable code) is shipped only through Customized Offerings (ServerPac, SystemPac, and CBPDO).
  
  
• September 28, 2007: z/OS V1.9 planned general availability via ServerPac, CBPDO, and SystemPac.
  
  
• September 28, 2007: Planned general availability of System REXX Support for z/OS V1.8 and z/OS.e V1.8 Web deliverable. This Web deliverable will support z/OS V1.8 and z/OS.e V1.8.
  
  
• October 9, 2007: Recommended last date for submitting z/OS V1.8 orders via the entitled Customized Offerings (ServerPac and CBPDO). This date will allow for adequate order processing time.
  
  
• October 22, 2007: Last date for processing orders for z/OS V1.8 via ServerPac and CBPDO.
  
  
• November 15, 2007: Planned general availability of the Cryptographic Support for z/OS V1R7-R9 and z/OS.e V1R7-R8 Web deliverable. This Web deliverable will support z/OS V1.7 through z/OS V1.9 and z/OS.e V1.7 through z/OS.e V1.8.
  
  
• June 23, 2008: Recommended last date for submitting z/OS V1.8 orders via the fee Customized Offering SystemPac. This date will allow for adequate order processing time.
  
  
• July 21, 2008: Last date for processing orders for z/OS V1.8 via SystemPac.

To obtain the Web deliverables listed above, visit the z/OS downloads Web page.

The end of service for a Web deliverable occurs at end of service for the release on which it runs.

It is very important that you order the required z/OS release you need for migration and coexistence while it is still available.

For z/OS.e (5655-G52), z/OS.e V1.8 is the last release of the z/OS.e product. Refer to following recommendations for placing last orders.

• October 9, 2007: Recommended last date for submitting z/OS.e V1.8 orders via the Customized Offerings (ServerPac and SystemPac). This date will allow for adequate order processing time.
  
  
• October 22, 2007: Last date for ordering z/OS.e V1.8 via ServerPac and SystemPac.
  • Since z/OS.e V1.8 is the last release of z/OS.e, no new z/OS.e orders will be created after October 22, 2007, for either ServerPac or SystemPac.
    
    
  • In addition, the z/OS.e ServerPac and SystemPac product checklists will no longer exist after October 22, 2007.
    
    
  • To order any product that runs with z/OS.e, please use the z/OS product catalog in ShopzSeries. z/OS.e service ordering should also be done using the z/OS service path in ShopzSeries.
    
    
  • Products that are unavailable via CBPDO, ServerPac, or SystemPac, such as Lotus Domino (5655-B86), can also be separately ordered for use with z/OS.

ServerPac, CBPDO, and SystemPac are offered for electronic delivery, where ShopzSeries product ordering is available. For more details on electronic delivery, refer to the ShopzSeries help information.

As of October 31, 2007, the SWINFO Web site will be discontinued

Refer to the ShopzSeries Web site for product catalogs for the Customized Offerings

If a product catalog for your country is not available in ShopzSeries, please use one of the following countries, United States or Germany, and select English language for the most complete product catalogs for the Customized Offerings.

z/OS statement of direction
February 6, 2007

z/OS.e V1.8 (5655-G52) is planned to be the last release of z/OS.e. Marketing, ordering, support, and service for z/OS (5694-A01) remain unaffected.

z/OS.e V1.8 remains orderable until its planned withdrawal from marketing in October 2007. In accordance with the z/OS (5694-A01) and z/OS.e service policy (to provide service support for each release for three years following its general availability date), IBM intends to withdraw service for z/OS.e V1.8 in September 2009. For information about other z/OS.e releases, refer to the Related information section for withdrawal from service dates.

IBM plans to provide a new pricing alternative for z/OS, System z New Application License Charges (zNALC). zNALC will replace New Application License Charges (NALC) and z/OS.e, and is intended to be IBM's strategic z/OS offering for new workloads. zNALC is planned to be available March 16, 2007. Refer to Software Announcement 207-006 for additional information.

IBM plans to take this action during the first quarter of 2007:

• IBM intends to improve the availability date for the support of JES3 NJE communications using TCP/IP which is planned to be made available in z/OS V1.8. as originally planned and announced in the Software Announcement 206-190 from first half of 2007 to March 30, 2007. This function includes support for IPv6, secure sockets (SSL/TLS), and all the NJE constructs (ENDNODE, SUBNET, Store-and-Forward) supported by the owning JES. This new support is in addition to the SNA and BSC protocols currently supported by JES3. In order to use the NJE/TCP support, both sides of the connection are required to support NJE/TCP. In order to enable JES3 NJE over TCP/IP in z/OS V1.8, you must install the PTF for APAR OA16527 and its prerequisites.

IBM plans to take the following actions in a future release:

• IBM plans that z/OS V1.9 will be last release to support English and Japanese ISPF panels in DFSORT. There will be no replacement for this limited interactive facility. Support for JCL to sort, copy, or merge will continue to be available.
  
  
• z/OS V1.9 is planned to be the last release of z/OS Communications Server which will support the configuration of Traffic Regulation (TR) policy as part of the Quality of Service discipline. The TR configuration function remains supported, but IBM recommends that you implement it as part of the Intrusion Detection Services (IDS) policy configuration made available in z/OS V1.8. This change is only for the TR policy configuration. The TR policy functions themselves remain unaffected. For more information, refer to:
  • z/OS V1.8 Communications Server IP Configuration Guide, Chapter 16. Intrusion Detection Services (IDS)
    
    
  • z/OS V1.8 Communication Server IP Configuration Reference, Chapter 23. Intrusion Detection Services (IDS) policy

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

Key dates

• December 11, 2006: The z990 exploitation support for z/OS V1.4 and z/OS.e V1.4 Web deliverable became generally available. This Web deliverable replaces the z/OS V1.4 z990 Exploitation Support feature and the z/OS.e V1.4 z990 Coexistence Update feature.
  
  
• March 31, 2007: Withdrawal from service of:
  • z/OS V1.4 (5694-A01)
  • z/OS.e V1.4 (5655-G52)
  • z/OS V1.5 (5694-A01)
  • z/OS.e V1.5 (5655-G52)
• June 25, 2007: Recommended last date for submitting orders for z/OS V1.7 via the CustomPac family fee-based offering, SystemPac. This date will allow for adequate order processing time.
  
  
• June 30, 2007: Last date for Web download of the following Web deliverables:
  • z990 compatibility for selected releases Web deliverable (compatibility for z/OS.e V1.3, z/OS V1.3 and V1.2, and OS/390 V2.10)
    
    
  • SMP/E V3R3 Web deliverable
    
    
  • IBM Health Checker for V1R4/R5/R6 of z/OS and z/OS.e Web deliverable
• July 23, 2007: Last date for ordering z/OS V1.7 via the CustomPac family fee-based offering, SystemPac.
  
  
• September 30, 2007: Withdrawal from service of:
  • z/OS V1.6 (5694-A01)
  • z/OS.e V1.6 (5655-G52)

z/OS statement of direction
August 8, 2006

IBM plans to take the following actions effective with the general availability of z/OS V1.8:

• The APPC Application Suite is a set of common applications originally designed to enhance the value of SNA networks for end users. Since more full-featured alternative applications exist in modern integrated SNA/IP networks, z/OS V1.8 is planned to be the last release of z/OS Communications Server which will include the APPC Application Suite. After z/OS V1.8 the APPC Application Suite will no longer be shipped with the product, and will not be supported. However, note that APPC itself remains an integral part of z/OS Communications Server's SNA functions, and there are no plans to remove APPC from z/OS. For more information, refer to z/OS Communications Server Web site.

IBM plans to take the following actions in the future:

• Preview — Group capacity limit on IBM System z9 EC and z9 BC: IBM plans to make it possible to define a logical partition (LP) group capacity limit on System z9 servers. This function will be designed to allow you to specify a capacity limit to be defined for each LP, and to define a group of LPs on a server. This is expected to allow the system to manage the group in such a way that the sum of the LP capacity limits will not be exceeded.

  When available, support of group capacity limit will be exclusive to System z9 EC and z9 BC.

  
  
• Layer 3 Virtual MAC for z/OS and z/OS.e environments: When the associated OSA-Express function is available, the z/OS Layer 3 VMAC function will help to simplify the network infrastructure and facilitate load balancing when multiple operating system instances are sharing the same OSA port or Media Access Control (MAC) address. With Layer 3 VMAC, each operating system instance can now have its own unique “logical” or “virtual” MAC (VMAC) address. Instead of sharing the same physical MAC address, each TCP/IP stack and its associated IP addresses are accessible using their own VMAC addresses.

  Layer 3 VMAC is an improved virtualization technique which is designed to dedicate a Layer 3 VMAC to a single TCP/IP stack which can help:

  • Simplify network configuration
  • Improve IP workload balancing
  • Remove the dependency on Generic Routing Encapsulation (GRE) tunnels
  • Allow WebSphere Application Server content-based routing to interoperate with z/OS in an IPv6 network
  • Allow z/OS to use a “standard” interface ID for IPv6 addresses
  • Remove the need for PRIROUTER/SECROUTER function in z/OS

  Preview —When available, OSA Layer 3 VMAC is planned to be exclusive to z9 EC and z9 BC, and will be applicable to the OSA-Express2 features and to the OSA-Express features (Gigabit Ethernet LX and SX and 1000BASE-T Ethernet) when configured as CHPID type OSD (QDIO). OSA Layer 3 VMAC is required to exploit the support in z/OS V1.8.

  
  
• Network Traffic Analyzer: When the associated Open Systems Adapter (OSA) function is available, the Network Traffic Analyzer function will help to provide a new diagnostic trace facility, allowing OSA packet trace records to be sent directly to the host operating system. Using Network Traffic Analyzer, along with the existing z/OS tools and service aids, z/OS system administrators will be able to monitor (“sniff”) each OSA CHPID for the network traffic.

  Network Traffic Analyzer is designed to extend the serviceability features of OSA, helping provide system programmers and network administrators the capability to control, capture, and format OSA hardware packet trace information.

  Preview — When available, an enhancement to the QDIO architecture (OSA-Express Network Traffic Analyzer) will be designed to allow trace records to be sent to z/OS. This enhancement is planned to be exclusive to z9 EC and z9 BC, and will be applicable to the OSA-Express2 features when configured as CHPID type OSD (QDIO). OSA-Express Network Traffic Analyzer is required to exploit the support in z/OS V1.8.

  
  
• QDIO Diagnostic Synchronization: When the associated OSA function is available, the QDIO Diagnostic Synchronization function will help provide system programmers and network administrators the ability to coordinate and simultaneously capture both software (z/OS) and hardware (OSA-Express2) traces. This function is designed to allow z/OS to signal an OSA-Express2 feature (using a new Diagnostic Assist function) to stop traces and capture the current trace records.

  Preview — When offered on z9 EC and z9 BC, QDIO Diagnostic Synchronization is planned to be applicable to the OSA-Express2 features when configured as CHPID type OSD (QDIO). The z9 EC and z9 BC QDIO Diagnostic Synchronization support is required to exploit the support in z/OS V1.8.

  
  
• IBM plans to enhance the IBM Encryption Facility for z/OS (5655-P97) Encryption Services feature to use the OpenPGP standard, RFC 2440. This support will be designed to allow you to exchange an encrypted, compressed, and/or digitally signed file between your internal data centers using the Encryption Services feature in conjunction with your external partners and vendors who have an installed RFC 2440-compliant client running on z/OS and other operating systems. It is expected that IBM will implement the required functions of the OpenPGP standard, RFC 2440, that will allow Encryption Facility for z/OS to achieve compliance with the standard. The planned support includes, but is not limited to, symmetric encryption using AES and Triple-DES, asymmetric encryption of randomly generated symmetric keys using RSA and ElGamal algorithms, and working with DSA signatures.
  
  
• On October 25, 2005, IBM announced the IBM Communication Controller for Linux for System z9 and zSeries V1.2, which provides an X.25 NPSI enablement interface. This function allows a software vendor to deliver support for an X.25 over TCPIP network. It is IBM's intent to also release an IBM X.25 over TCPIP product which uses this X.25 NPSI enablement interface. Together, the Communication Controller for Linux on System z and X.25 over TCPIP products can help you modernize your networking infrastructure for Communications Server on z/OS.
  
  
• IBM intends to deliver enhancements to the consoles component in the future, not in 2007 as originally planned and announced in Software Announcement 206-039, dated February 28, 2006. These enhancements will be intended to provide enhanced reliability and availability of the sysplex-wide management of the operator console configuration by:
  • Reducing the amount of console configuration data passed around the sysplex under serialization. This change is expected to improve overall sysplex recovery time and reduce serialization delays during system startup and planned system shutdown activities.
    
    
  • Increasing the maximum number of MCS and SMCS consoles that can be defined and active in a configuration from 99 per sysplex to 99 per system in the sysplex.

These statements represent current intentions of IBM.

Any reliance on these statements of direction is at the relying party's sole risk and will not create any liability or obligation for IBM.

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

z/OS statement of direction
February 28, 2006

IBM plans to take the following actions effective with the general availability of z/OS V1.8:

• IBM intends to stabilize the prelinker. The prelinker was designed to process long names and support constructed reentrancy in earlier versions of the C compiler on the MVS and OS/390 operating systems. The prelinker, shipped with the z/OS C/C++ run-time library, provides output that is compatible with the linkage editor, shipped with the binder.
  
  The binder is designed to include the function of the prelinker, the linkage editor, the loader, and a number of APIs to manipulate the program object. Its functionality delivers a high level of compatibility with the prelinker and linkage editor, but provides additional functionality in some areas. For more information on the compatibility between the binder and the linker and prelinker, refer to z/OS MVS Program Management User's Guide and Reference .
  
  Further enhancements will not be made to the prelinker utility. Enhancements will be made only to the binder, the strategic tool for program object manipulation.
  
  
• z/OS V1.8 is planned to be the last release that supports host communication between HCM and Hardware Configuration Definition (HCD) elements via Advanced Program to Program Communication (APPC). Currently, for host communication either TCP/IP or APPC are supported. Starting with the z/OS release available in 2007, the host communication will be done exclusively via TCP/IP.
  
  
• z/OS V1.8 is planned to be the last release to include the C/C++ IBM Open Class (IOC) Dynamic Link Libraries (DLLs). Application development support for the C/C++ IOC Library was withdrawn in z/OS V1.5. The run-time support (DLLs) for applications that use the IOC Library is planned to be removed in the z/OS release available in 2007. Applications that are dependent on the IOC Library will not run starting with the z/OS release available in 2007.
  
  IBM has previously recommended that customers with application code that uses the IOC Library migrate to the Standard C++ Library. The publication IBM Open Class Library Transition Guide was published with z/OS V1.2 C/C++ as a reference for customers migrating their code from the IBM Open Class Library to the Standard C++ Library.

IBM plans to take the following actions in a future release:

• z/OS V1.6 Communications Server and subsequent releases include a stand-alone TN3270 Server. This stand-alone TN3270 Server is expected to provide increased flexibility, improved reliability, and simplified problem diagnosis as compared to the in-stack version of the TN3270 Server.
  
  In a future release of z/OS Communications Server, support for the in-stack version of the TN3270 Server is planned to be discontinued. In preparation for that change, customers should consider implementing the stand-alone TN3270 Server.
  
  For more information, visit the z/OS Communications Server Web site.
  
  
• IBM plans to replace the RMF LDAP backend in a future release of the operating system. The RMF LDAP interface currently allows access to RMF performance data from application programs. This functionality is planned to be replaced with a Common Information Model (CIM) Monitoring interface that is now part of z/OS V1.7.

IBM plans to enhance the IBM Encryption Facility for z/OS (5655-P97) Encryption Services feature to use the OpenPGP standard, RFC 2440. This support will be designed to allow you to exchange an encrypted, compressed, and/or digitally signed file between your internal data centers using the Encryption Services feature in conjunction with your external partners and vendors who have an installed RFC 2440-compliant client running on z/OS and other operating systems. IBM plans to give additional details on the specific OpenPGP functions at a later date.

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

z/OS statement of direction
July 26, 2005

IBM plans to take the following action effective in 2005:

• IBM intends to provide a new user interface for z/OS management that is planned to help the new generation of Information Technology workers by automating, eliminating, and simplifying many z/OS management tasks. The first phase of the new user interface (planned to be provided in a separate product) is planned to provide real-time health check information executed by the IBM Health Checker for z/OS and configuration status information for z/OS systems and sysplex resources. The new interface contains built-in automation and expert advice capabilities that provide detailed contextual information on alerts and corrective actions. This new interface is planned to be available in fourth quarter 2005.

IBM plans to take the following actions in the future:

• Scale up and scale out: z/OS V1.7 currently allows you to scale up in a single logical partition from 1 processor to 32 with good scalability (based on internal IBM lab measurements) and to scale out in a Parallel Sysplex for higher availability. IBM plans to support more than 32 processors in a single logical partition on the IBM System z9 109 (z9-109) in the future.
  
  
• IBM plans to announce a version of New Application License Charges (NALC) intended to help improve the price performance of z/OS in certain new workload environments by delivering subcapacity pricing. The offering and associated terms are targeted for availability in the second half 2006.
  
  
• IBM plans to introduce a new system component called z/OS XML System Services (z/OS XML) in a future release of z/OS. This component will be designed to provide an optimized set of services for parsing XML documents. It is expected to be of use to IBM, ISV, and customer middleware and applications having high performance or unique environmental XML parsing requirements, such as the ability to run in cross-memory and SRB modes. Initial support is planned to provide an assembler language interface; later, IBM plans to add C/C++ high-level language support.
  
  
• IBM intends to provide a VSAM Java database connectivity (JDBC) Connector in the future, not in 2005 as previously stated in Software Announcement 204-180, dated August 10, 2004. A JDBC Connector implements a Java application programming interface that is designed to allow you to write Java-based applications that read and write VSAM data without having to do VSAM programming or use copies of existing data. These applications are expected to be able to access VSAM data, at the same time as other applications, when deployed in WebSphere, DB2, and z/OS UNIX Systems Services environments. When used with the optional DFSMStvs (Transactional VSAM Services) feature, the VSAM JDBC Connector is intended to allow WebSphere applications to participate in coordinated commit processing.
  
  
• A new function in SMP/E, Internet Service Retrieval, is intended to simplify the acquisition of z/OS service. This function, which supplements existing service options in ShopzSeries, is planned to be available in September 2005. For more information about this new function, see the description of the SMP/E Internet Service Retrieval function in the SMP/E enhancements section.

Internet Service Retrieval and ShopzSeries now offer extensive options for service acquisition and delivery. To reduce the number of ordering interfaces and help assure timely delivery of new function, some older options for service delivery are being simplified or discontinued:

• Effective January 15, 2006, as previously announced in Software Announcement 205-034, dated February 15, 2005, the S/390 Service Update Facility (SUF) will be discontinued.
  
  
• Effective March 2006, new ESO and CBPDO (5751-CS8 and 5775-MVS) physical delivery subscriptions will not be accepted.
  
  
• Effective June 2006, CBPDO product orders will include service only for the products included in the order. Formerly, CBPDO product orders included service for other products licensed under the same customer number within the same SREL. To get service for other products, you can use SMP/E Internet Service Retrieval, ShopzSeries, or a fee service offering.
  
  
• Effective June 2006, Service-Only CBPDO (5751-CS3) orders will no longer be accepted. An improved option for ordering service by SREL, or for all licensed products under the same customer number, will continue to be supported in ShopzSeries. You can also get service based on what you have installed using SMP/E Internet Service Retrieval, ShopzSeries, or selected fee offerings. Note that CBPDO product orders are not affected by this change.
  
  
• Effective September 2006, existing ESO and CBPDO physical delivery subscriptions will be discontinued. You can use a job scheduling system and SMP/E Internet Service Retrieval to get service at any interval you find convenient, or use the Internet delivery subscription option available in ShopzSeries.
  
  

IBM recommends that you begin to use SMP/E Internet Service Retrieval, ShopzSeries, or one of these worldwide fee offerings before the above changes take effect:

• US — SoftwareXcel, Resolve
• Europe/Middle East/Africa — Enhanced Technical Support
• Canada — SupportLine
• Latin America — SupportLine
• Asia Pacific/South — SupportLine

For more information, visit the ShopzSeries Web site

• On February 15, 2005, IBM announced IBM Communication Controller for Linux on zSeries V1.1. This product is intended to provide a migration path for customers using SNA applications to communicate with business partners. In the next release of Communication Controller for Linux on zSeries, IBM intends to provide enhancements in network connectivity such as channel data link control (CDLC) using OSA-Express2 OSN (OSA for NCP), data-link switching (DLSw), and an open interface for X.25 (NPSI). For more information on this product, refer to the Communication Controller for Linux on zSeries Web site.
  
  
• Support for the following plug-ins for msys for Setup will be withdrawn in the release following z/OS V1.7: TCP/IP Services, z/OS UNIX System Services, Language Environment, Parallel Sysplex, ISPF, and RMF. When this support is withdrawn, you will not be able to use msys for Setup for function enablement, setup, or configuration of these areas of z/OS. The DB2 V8 msys for Setup plug-in is unaffected and remains available for enablement, setup, and configuration of DB2. The TCP/IP plug-in will continue to be available for download via the Web and will no longer require msys for Setup. IBM intends to continue to deliver improvements to help with z/OS setup and configuration in the future.
  
  
• z/OS V1.7 is planned to be the last release to support the z/OS msys for Operations element. It is IBM's intent to remove the z/OS msys for Operations element from the release following z/OS V1.7. IBM plans to transition many of the current msys for Operations functions to a new user interface and infrastructure in a future release of z/OS.

These statements represent current intentions of IBM.

Any reliance on these statements of direction are at the relying party's sole risk and will not create any liability or obligation for IBM.

z/OS and z/OS.e statement of direction
February 15, 2005

IBM plans to take the following actions effective with the general availability of z/OS V1.7 (from February 15, 2005 announcement letter):

• z/OS V1.7 is planned to be the last release to allow mounting zFS file systems contained in multi-file system aggregates that are to be shared across systems in a sysplex. IBM has previously recommended that these multi-file system aggregates not be shared in a sysplex environment. Once this support has been removed, attempts to mount zFS file systems contained in multi-file system aggregates will fail in a z/OS UNIX shared file system environment. Mounting zFS compatibility mode aggregates, which have a single file system per data set, will continue to be supported in all environments.
  
  
• z/OS V1.7 is planned to be the last release to include the Firewall Technologies component of the Integrated Security Services element. Many Firewall Technologies functions have been stabilized for some time and can be replaced using comparable or better functions provided by or planned for Communications Server, notably, IPSecurity. In addition, a functionally rich downloadable tool is planned to replace the IPSecurity and IP Filtering configuration GUI support. The following functions will be removed without replacement:
  • FTP Proxy services
  • Socks V4 services
  • Network Address Translation (NAT)
  • RealAudio™ support
  
  
  For more information about migration actions, refer to z/OS V1R7 Migration, when available.
  
  
• z/OS V1.7 is planned to be the last release in which z/OS Communications Server will support the following functions, after which they will be removed from the product:
  • TCP/IP configuration profile block definition statements:
    • ASSORTEDPARMS
    • ENDASSORTEDPARMS
    • KEEPALIVEOPTIONS
    • ENDKEEPALIVEOPTIONS
    
    
    Equivalent capability is provided for the ASSORTEDPARMS statements by the GLOBALCONFIG, IPCONFIG, TCPCONFIG, and UDPCONFIG statements. Equivalent capability is provided for the KEEPALIVEOPTIONS statements by INTERVAL and SENDGARBAGE on the TCPCONFIG statement. For information on TCP profile and configuration statements, refer to z/OS Communications Server IP Configuration Reference.
    
    
  • The SNMP Service Level Agreement (SLA) V1 MIB and the PAGTSNMP subagent. In z/OS V1.5, Communications Server provided a new SNMP SLA V2 MIB and NSLAPM2 subagent. IBM recommends that you migrate to the new V2 MIB and NSLAPM2.
    
    
  • The option of defining parallel Enterprise Extender TGs by specifying multiple SAP addresses. Beginning in z/OS V1.5, parallel EE TGs may be defined by using different EE VIPAs on one (or both) of the endpoints.
    
    
  • AnyNet. You may implement other IBM solutions such as Enterprise Extender (EE) as a replacement for AnyNet.
    
    
• z/OS V1.7 is planned to be the last release to support 1-byte Console IDs. With z/OS V1.7, support for 1-byte Console IDs and external interfaces supporting migration console IDs will be removed from the WTO, WTOR, and MCSOPER macros; and from operator commands. Programs compiled using older versions of the macros will continue to work. In the release following z/OS V1.7, however, all 1-byte Console ID support will be completely removed.

IBM plans to take the following actions effective in 2005 or later:

In an ongoing effort to simplify ordering, delivery, and installation of z/OS service, emphasis will continue to be on electronic delivery rather than physical shipment of service. The number of ordering interfaces will be reduced to establish a uniform service methodology and enable timely delivery of new function. The following change is being announced at this time:

Effective January 15, 2006, the S/390 Service Update Facility will be discontinued. If you have not already done so, we recommend that you begin using ShopzSeries or another service option before the above change take effect. For more information on ShopzSeries, visit the ShopzSeries Web site.

Existing electronic worldwide fee services offerings that deliver z/OS software service will continue to provide electronic delivery via:

• SoftwareXcel, Resolve (US)
• Enhanced Technical Support SupportLine (EMEA)
• SupportLine (AP, LA, CAN)

In a future release, IBM plans to withdraw support for zFS multi-file system aggregates. When this support is withdrawn, only zFS compatibility mode aggregates will be supported. (A zFS compatibility mode aggregate has a single file system per data set.)

These statements represent current intentions of IBM.

z/OS and z/OS.e statement of direction
August 10, 2004

IBM statement of direction update on SNA support in 2004 (from August 10, 2004 announcement letter):

• It is IBM's intent to support VTAM in z/OS Communications Server for the foreseeable future. Customers have a substantial investment in 3270 and SNA applications. We continue to support and enhance VTAM's capabilities while integrating it with new technologies. IBM has no plans at this time to discontinue SNA support in z/OS Communications Server. As of June 2004, customers can, for selected SNA workloads, use Communications Server products for Linux, Linux on zSeries, Microsoft Windows, and AIX to replace some of the old SNA infrastructure components, such as the IBM 3745/46 or other channel-attached SNA controllers. z/OS Communications Server can replace some SNA Network Interconnect (SNI) workloads using Enterprise Extender and Extended Border Node functions.
  
  It is IBM's intent to introduce an additional solution in 2005 that uses NCP (Network Control Program) software running within Linux on zSeries. The intent is to provide a migration path for customers who use traditional SNA (including SNA Network Interconnect (SNI)) to communicate with their business partners. This solution can allow them to continue using traditional SNA without a dependency on IBM 3745 and 3746 Communications Controller hardware.

Notable change: With z/OS V1.6, Text Search is no longer made available as a base element of z/OS. Instead, it will be made available for Web download as z/OS and z/OS.e Text Search under a restricted license. This is a change to the statement of direction made in Software Announcement 203-266, dated October 7, 2003, which stated that with z/OS V1.6, the Text Search base element would be removed and no replacement would be provided. The Text Search element has been removed from the z/OS product. However, the Text Search function is still required and licensed for use only for DB2 UDB Text Extender feature of DB2 Universal Database for z/OS, Program Number 5625-DB2, as a Web deliverable named z/OS and z/OS.e Text Search.

Before you use the DB2 UDB Text Extender feature, you must download and install the z/OS and z/OS.e Text Search Web deliverable on z/OS V1.6.

IBM plans to take the following actions effective with z/OS V1.7:

• Support for ISAM data sets will be withdrawn. When this support is withdrawn, you will no longer be able to process ISAM data sets other than to delete them. The ISAM Compatibility Interface will remain available to help you migrate applications to VSAM without application changes.
  
  
• Support for JES2 compatibility mode will be withdrawn. As of z/OS V1.7, JES2 will no longer support compatibility with pre-z/OS V1.2 systems. The $ACTIVATE command, which converts the JES2 checkpoint from z2 mode to R4 mode (compatibility mode), will be removed. Before installing z/OS V1.7, you will need to do one of the following:
  • Use the $ACTIVATE command to convert the JES2 checkpoint to z2 mode
    
    
  • Offload the SPOOL, cold start JES2 z/OS V1.7, and reload the jobs on the new SPOOL
  
  
• The z/OS Optional Source Code media features will not be offered in z/OS V1.7. The last release offering these materials will be z/OS V1.6 and z/OS.e V1.6. These features contain macros and source code for some programs in the z/OS BCP, BDT base, BDT SNA NJE, BDT File-to-File, DFSMS, MICR/OCR, BCP JPN, and Security Server RACF elements.
  
  
• Support for the STEPCAT and JOBCAT JCL statements will be withdrawn. There are other facilities in DFSMSdfp that allow catalog requests to be directed to specific catalogs, and the utility of these two JCL statements has been drastically reduced by the implementation of System-Managed Storage and the placement of Unit Control Blocks (UCBs) above the 16 MB line. When this support is withdrawn, any remaining JCL that uses these two statements will have to be changed.
  
  
• The OS/390 V2.10 C/C++ compiler is planned to be removed from the C/C++ without Debug Tool feature, leaving only the ISO C/C++ compiler. Since z/OS V1.2, the OS/390 V2.10 C/C++ compiler has been shipped in addition to the strategic ISO C/C++ compiler that is also provided with z/OS. This OS/390 V2.10 C/C++ compiler serves as a migration aid to the newest ISO C/C++ compiler.

IBM plans to take the following action effective in 2005:

• IBM intends to provide a VSAM Java database connectivity (JDBC) Connector. A JDBC Connector implements a Java application programming interface that is designed to allow you to write Java-based applications that read and write VSAM data without having to do VSAM programming or use copies of existing data. These applications can access VSAM data, at the same time as other applications, when deployed in WebSphere, DB2, and UNIX Systems Services environments. When used with the optional DFSMStvs (Transactional VSAM Services) feature, the VSAM JDBC Connector can allow WebSphere applications to participate in coordinated commit processing.

IBM plans to take the following actions in a future release:

• Support for the VSAM IMBED, REPLICATE, and KEYRANGE attributes will be withdrawn. No supported release of z/OS or OS/390 allows you to define new VSAM data sets with these attributes. Using them for existing data sets can waste DASD space and can often degrade performance. When this support is withdrawn, you will not be able to process data sets with these attributes.
  
  
• The English and Japanese ISPF panels will be removed from DFSORT. This limited function interactive facility will no longer be provided, and there will be no replacement. All other previously supported methods for invoking DFSORT will still be supported, such as batch invocation and invocation from a program.

These statements represent current intentions of IBM. Any reliance on these Statements of Direction are at the relying party's sole risk and will not create any liability or obligation for IBM.

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

z/OS and z/OS.e statement of direction
February 10, 2004

(from February 10, 2004 announcement letter)

IBM plans to take the following actions in the future.

• IBM intends to provide a 64-bit SDK 1.4 level Java product concurrently with the general availability of z/OS and z/OS.e V1.6.
  
  
• z/OS Communications Server will remove support for the BIND DNS 4.9.3 function in a future release. This is a change to the statement of direction made in Software Announcement 203-266 (RFA38767), dated October 7, 2003, which stated that z/OS V1.6 would be the last release to support BIND DNS 4.9.3. 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/WLM) feature of BIND DNS 4.9.3 should investigate Sysplex Distributor or alternative solutions.

These statements represent current intentions of IBM.

Any reliance on these Statements of Direction are at the relying party's sole risk and will not create any liability or obligation for IBM.

z/OS and z/OS.e statement of direction
October 7, 2003

(from October 7, 2003 announcement letter)

IBM is announcing the following statements of direction. These statements apply to both z/OS and z/OS.e unless otherwise indicated.

• Effective with z/OS V1.6, IBM plans to remove the base element, DCE Application Support, from z/OS. DCE application Support facilitated the interaction between DCE clients and CICS or IMS regions. With the continued evolution of technology and accompanying changes in the marketplace, there is no need for this support. If similar function is required, IBM recommends that customers use WebSphere.
  
  The DCE Base Services element, which provides services for developing and running client/server applications, is planned to continue to ship with z/OS and z/OS.e.
  
  Note: DCE Application Support is not functional and not licensed for use on z/OS.e.
  
  
• Effective with z/OS V1.6, IBM plans to remove the base element, Encina Toolkit Executive, from z/OS. Encina Toolkit Executive provided a set of tools for developing client components of distributed transactional applications. Over time, the marketplace has moved to other technologies. This element, an enabler for DCE Application Support, is another obsolete element of z/OS V1.6 and will no longer be provided. There will be no replacement.
  
  Note: Encina Toolkit Executive is not licensed for use with z/OS.e.
  
  
• Effective with z/OS V1.6, IBM plans to remove the base element, Text Search. There will be no replacement.
  
  
• z/OS V1.6 is planned to be the last release in which z/OS Communications Server will support BIND DNS 4.9.3. After z/OS V1.6, the function will be removed from the product. Customers should implement BIND DNS 9.2.0 as a replacement. BIND DNS 9.2.0 is included in the product beginning with z/OS V1.4. Customers exploiting the Connection Optimization (DNS/WLM) feature of BIND DNS 4.9.3 should investigate alternative solutions, such as the Sysplex Distributor function.
  
  
• z/OS V1.6 is planned to be the last release in which z/OS Communications Server will support OROUTED. After z/OS V1.6, the function will be removed from the product. Customers should use OMPROUTE as their dynamic routing daemon.
  
  
• In a future release of z/OS Communications Server, support for AnyNet is planned to be discontinued and the function will be removed from the product. Customers may implement Enterprise Extender (EE) as the replacement for AnyNet.
  
  
• Due to ISAM's limited functionality and the capabilities of VSAM, particularly VSAM data sets in extended format, z/OS V1.6 is planned to be the last release in which DFSMS ISAM. The utility program, IEBISAM, will be available. IBM has provided the ISAM interface which allows users to run an ISAM program against a VSAM KSDS data set. Details on using this interface and procedures for converting ISAM data sets to VSAM data sets can be found in Appendix E of the DFSMS Using Data Sets publication. The order numbers for editions of this book are as follows:
  
  
  • DFSMS/MVS Using Data Sets, SC26-4922
  • OS/390 V2R10.0 Using Data Sets, SC26-7339
  • z/OS DFSMS Using Data Sets, SC26-7410
  
  
  This interface program is planned to continue to be provided as part of DFSMS and will not be discontinued when ISAM is removed from DFSMS.
  
  
• In a future release of z/OS, IBM intends to certify z/OS to the Common Criteria Controlled Access Protection Profile (CAPP) at EAL3 and Labeled Security Protection Profile (LSPP) at EAL3+.

z/OS statement of direction
May 13, 2003

(from May 13, 2003 announcement letter)

These statements represent current intentions of IBM. IBM development plans are subject to change or withdrawal without further notice.

Any reliance on this statement of direction is at the relying party's sole risk and will not create any liability or obligation for IBM.

The following is planned to be made available on z/OS V1.4 and higher:

• IBM intends to support four logical channel subsystems in z/OS. The maximum number of channels supported per z/OS image will be 256. This support will require z/OS V1.4 or higher, and a z990 or future server.

The following action is planned to be effective with z/OS V1.5:

• The application development support (that is, the headers, source, sidedecks, objects, and samples from the Application Support Class and Collection Class libraries) is planned to be withdrawn from the C/C++ IBM Open Class(TM) Library (IOC). Runtime support for IOC is planned to be removed in a future release.

The following actions are planned to be effective with z/OS V1.6:

• IBM intends to support greater than 16 engines in a single image of z/OS. This support will increase the scale of a single z/OS image by taking advantage of the increased number of engines available on a z990 server.
  
  
• IBM intends to provide support for up to 60 logical partitions (LPARs) running z/OS on a single z990.
  
  
• Language Environment's use of Run Time Library Support (RTLS) will be withdrawn. This function is used primarily in run-time migration. Given the stability and the upward compatibility being provided by the Language Environment run-time library in recent releases of OS/390 and z/OS, this functionality is no longer required.
  
  
• IBM will modify support for the Euro Monetary Symbol. The base locales for the participating EU countries will be modified to contain the Euro Monetary Symbol as the default currency symbol. This change will require modifications to customer applications which currently display monetary amounts in both the local currency and the Euro. A new modifier called @preeuro is being created to allow applications to continue displaying monetary amounts in the local currency, since the default currency symbol in the affected locales will be the Euro symbol. Existing applications using only the @euro modifier will not be affected.
  
  
• The C/C++ ISPF panels which include panels for C/C++ foreground compiles, C/C++ background compiles, and help panels for these compiles, are planned to be removed. The z/OS C/C++ compiler can be invoked through UNIX System Services, using JCL, and under TSO.
  
  
• The Dynamic Link Library (DLL) Rename Utility, part of z/OS Language Environment, is used to package and redistribute IBM-supplied DLLs with applications. Since OS/390 V1.3, the C/C++ DLLs have been licensed with the OS/390 and z/OS base operating system. Therefore, the DLL Rename Utility is no longer required, and is planned to be removed.

The following actions are planned to be effective in a future release of z/OS:

• In a future release of z/OS, IBM plans to eliminate the one-byte console ID interface. With the advent of four-byte console IDs (in MVS/SP V4.1.0), customers and vendors have been encouraged to migrate away from the use of one-byte interfaces. To help prepare for the removal of this interface, tools will be provided in the z/OS V1.4 Consoles Enhancements feature that will identify uses of one-byte console ID interface in the environment.
  
  
• Since z/OS V1.2, the OS/390 V2.10 C/C++ compiler has been shipped in addition to the strategic ISO C/C++ compiler that is also provided with z/OS. This OS/390 V2.10 C/C++ compiler serves as a migration aid to the newest ISO C/C++ compiler. The OS/390 V2.10 C/C++ compiler is planned to be removed from the C/C++ feature leaving only the ISO C/C++ compiler.
  
  
• z/OS Communications Server support for the SMIv1 version of the SNMP IBM MVS TCP/IP Enterprise-specific MIB module will be eliminated. Support will continue for the SMIv2 version of this MIB module. For customers who want to continue using SMIv1, publically available tools can be used to convert an SMIv2 MIB module to an SMIv1 MIB module. Details of the SMIv1 MIB module elimination are planned to be communicated in a future z/OS announcement.

z/OS statement of direction
August 13, 2002

(from August 13, 2002 announcement letter)

IBM plans to take the following actions in the future.

• The next z/OS release, z/OS V1.5, is planned to be delivered in 1Q2004. The next release after z/OS V1.5 is planned to be available in September 2004. Starting with the September 2004 release, it is IBM's intention to deliver z/OS releases on an annual basis.
  
  
• IBM plans to remove Object Access Method (OAM) support for Filenet 9246 optical libraries, 9247 optical drives, and 12" optical media in z/OS 1.5. If optical is a requirement, these filenet devices and media can be replaced with IBM 3995 optical devices and media. If optical is not required, the data can be transitioned to any z/OS-supported tape media or to DB2 tables on standard disk devices.
  
  
• IBM's strategy is to provide entitled service ordering and service delivery capabilities for the z/OS and OS/390 platform products electronically using the Internet. IBM intends to position ShopzSeries as the primary ordering and delivery method for software service on these platforms. The S/390 Service Update Facility (SUF) is being stabilized and additional requirements will be addressed via ShopzSeries. Existing worldwide fee services offerings that deliver z/OS and OS/390 software service will continue to provide delivery via physical and electronic media.
  
  
• IBM plans to deliver 64-bit virtual storage addressing for the DB2 for z/OS product in a future release. The future release of DB2 for z/OS, with 64-bit virtual address support, will be able to execute only on IBM zSeries 900 (z900) and IBM zSeries 800 (z800), or equivalent, running z/OS V1.3 or later, not z/OS V1.2, as previously stated in Software Announcement 201-248 (RFA35427), dated September 11, 2001. DB2 V6 (5645-DB2) and V7 95675-DB2) already support 64-bit real storage addressing for data space buffers.

These statements represent current intentions of IBM. IBM development plans are subject to change or withdrawal without further notice.

Any reliance on this Statement of Direction is at the relying party's sole risk and will not create any liability or obligation for IBM.

z/OS statement of direction and notable changes
February 19, 2002

(from February 19, 2002 announcement letter)

Statement of direction

IBM plans to take the following actions in the future.

• IBM is developing new eLiza-driven technology that will help address the challenge of multiple heterogeneous security registries existing in and between enterprises. By managing the relationship between identities that are identified within multiple applications, platforms, and middle-ware, EIM services will make it possible for an application to use one registry for user authentication while using a different registry to associate users with resource access control rules. It is our intention to make EIM services available on a future release of z/OS.
  
  
• As of z/OS V1R2.0, the OS/390 V2R10 C/C++ compiler is shipped in addition to the strategic ISO C++ compiler that is also provided with z/OS. This serves as a migration aid to the newer ISO C++ compiler. In a future release, the OS/390 V2R10.0 C/C++ compiler is planned to be removed from the C/C++ feature leaving only the ISO C/C++ compiler.
  
  
• As of z/OS V1R2.0, the Application Support Class and Collection Class of the C/C++ IBM Open Class Library (IOC) were upgraded to be consistent with that shipped in VisualAge C++ for AIX V5.0. This was done to ease porting of applications from the AIX platform. Both the upgraded and previous levels of the IOC are shipped in z/OS V1R2.0 and z/OS V1R3.0. Starting with z/OS V1R4.0, the application development support (that is, the headers, source, sidedecks, objects, and samples from the Application Support Class and Collection Class libraries) is planned to be withdrawn from both levels of the IOC. Runtime support for IOC is planned to be removed from the C/C++ feature in a future release. For additional information, see the IBM Open Class Library Transition Guide.

These statements represent current intentions of IBM. IBM development plans are subject to change or withdrawal without further notice. Any reliance on this Statement of Direction is at the relying party's sole risk and will not create any liability or obligation for IBM.

Notable changes in z/OS V1R3.0

• WLM compatibility mode is no longer supported.
  
  
• The KEYRANGE specification on the IDCAMS DEFINE and IMPORT commands is now ignored for any data sets created with z/OS V1R3.0. Existing KEYRANGE data sets will continue to work without change.
  
  For additional information, refer to System Center Flash 10072. This Flash is available on the Internet at the Technical Support Technical Information Site. Once there, select Flashes then search on Flash10072.
  
  
• LANRES is no longer supported. For information on migration alternatives, please take a look at the Migration Roadmap for LANRES for OS/390 Customers — Where to go from here? white paper.

Notable changes in z/OS V1R4.0

Planned z/OS V1R4 changes will be made to the following functions:

• Application development support will be withdrawn for the IBM Open Class Library starting with z/OS V1R4.0. The headers source, and samples for the Application Support Class and Collection Class libraries of the IBM Open Class Library will be withdrawn in that release.

z/OS statement of direction and notable changes
September 11, 2001

Statement of direction

As stated in the September 11, 2001 IBM z/OS V1R2.0: Enabling and protecting your e-business and Preview: z/OS V1R3.0, IBM plans to deliver:

• 64-bit virtual storage addressing for the DB2 for z/OS product in a future release. The future release of DB2 for z/OS, with 64-bit virtual address support, can only execute on IBM zSeries 900 (z900), or equivalent, running z/OS V1R2, or later. DB2 V6 (5645-DB2) and V7 (5675-DB2) already support 64-bit real storage addressing for data space buffers.
  
  
• Enhancements to DB2 that will permit utilization of security features of the SecureWay Security Server of z/OS known as multilevel security. These enhancements are planned to be delivered through the service stream to DB2 for z/OS and OS/390 V7 (5675-DB2) and follow-on releases, if any.
  
  
• IBM plans to withdraw the RDBM backend from the LDAP Server in the z/OS release expected to be available in the second half of 2002. Because of its improved scalability and availability, customers are encouraged to migrate to the enhanced TDBM back end according to instructions in the LDAP Server Administration and Usage Guide.
  
  
• Architectural Level Sets (ALS) have recently been announced for OS/390 and z/OS. ALS 2 indicated that z/OS V1R1.0 would require architectural enhancements available in 9672 G5 and G6, MP3000, and z900 servers. No new Architectural Level Sets have been announced since then. In order to assist customers with their planning, IBM is advising that there will be no new Architectural Level Set with z/OS V1R4.0. Therefore, z/OS V1R4.0, expected to be available in the second half of 2002, will run on G5, G6, MP3000 and z900 Servers, or the equivalent. Information regarding future Architectural Level Sets will be provided in z/OS announcement letters when appropriate.

These statements represent current intentions of IBM. IBM development plans are subject to change or withdrawal without further notice. Any reliance on this Statement of Direction is at the relying party's sole risk and will not create any liability or obligation for IBM.

For further details, refer to the Notable Changes in z/OS V1R2.0 and the Notable Changes in z/OS V1R3.0 sections following below.

Notable changes in z/OS V1R2.0

The following elements, features, and functions are no longer included in z/OS starting with z/OS V1R2.0:

• LAN Server element
  
  
• Tivoli Management Framework element (Tivoli Management Framework, will only be available as a stand-alone product (5697-D10), for which we do not currently intend to charge a separate license fee.)
  
  
• Spanish language version of the Infoprint Server feature
  
  
• Communications Server Level 1 feature
  
  
• Communications Server Level 2 feature
  
  
• V4 Kerberos function from the Communications Server
  
  
• ISPF Library Management Facility (LMF) function
  
  
• Pre-Compiled Header files (PCH) function from the C++ compiler
  
  
• RMF Monitor II local 3270 display sessions function
  
  
• The SOMobjects for MVS Runtime Library (RTL) element and SOMobjects for MVS Application Development Environment (ADE), an optional feature. Service support is still available for this element and feature in previous releases of z/OS, and on OS/390 V2. No new functionality will be added to the element or feature in previous releases of z/OS or OS/390.
  
  There continues to be recognizable value in the ability to build COBOL Object-Oriented (OO) applications that can be deployed on the S/390 platform, and the COBOL OO technology is currently based upon SOMobjects. For that reason, IBM will continue to support SOM®-based COBOL OO applications on OS/390 V2 and z/OS V1R1.0.
  
  The Statement of Direction for SOMobjects as announced in Software Announce ment 200-352, dated October 3, 2000, included plans to incorporate the SOMobjects ADE as a part of the IBM COBOL for OS/390 and VM compiler product, and move a subset of the SOMobjects RTL to the Language Environment component of z/OS. Since this effort would not benefit our customers, while improved interoperability of COBOL with Java and with the WebSphere Application Server would, IBM will focus future enhancements to COBOL in this direction.
  
  It is strongly recommended that customers with programs which depend on SOM objects evaluate the WebSphere Family of products for replacement purposes. There is no detailed migration strategy from SOMobjects due to the many changes which have come about in the underlying technology.
  
  For further information about WebSphere, visit the WebSphere Web site.
  
  For further information about IBM COBOL for OS/390 & VM, visit the IBM COBOL Web site.
  
  
• Additional changes follow:
• The ISPF Data Compression function will remain in z/OS V1R2.0 and z/OS for the foreseeable future. However, many compression products are more capable and efficient and should be considered. The "Terse/MVS" function commonly used to compress FTP dumps is but one example. The ISPF Data Compression code will not be enhanced in any future release and is now considered functionally stable.
  
  
• Effective immediately, OS/390 and z/OS customers are no longer entitled to free downloads of the Host-on-Demand (HOD) Entry function. Customers interested in HOD Entry should contact their IBM representative.

Notable changes in z/OS V1R3.0

z/OS V1R3.0 changes will be made to the following functions:

• WLM compatibility mode will not be supported.
  
  
• It is the intent of IBM to ignore the KEYRANGE specification on the IDCAMS DEFINE and IMPORT commands for any data sets created beginning with z/OS V1R3. Existing KEYRANGE data sets will continue to work without change.
  
  For additional information, see System Center Flash 10072. You can find it by visiting the Technical Support Technical Information Web site Once there, select Flashes and search on Flash10072.
  
  Additionally, LANRES will not be supported. For information on migration alternatives, see the Migration Roadmap for LANRES for OS/390 customers white paper.

z/OS statement of direction
February 27, 2001

As stated in the February 27, 2001 Preview: IBM z/OS V1R2 announcement letter, IBM plans to take the following actions in the future. You are encouraged to consider these plans when making your own plans for system upgrades.

• ISPF Data Compression. The ISPF Data Compression function will remain in z/OS V1R2 and foreseeable future z/OS releases. However, the "terse" function used to compress FTP dumps is a more capable compression product. ISPF Data Compression will not be enhanced.
  
  
• Internet Protocol Version 6 (IPv6). IBM intends to provide an integrated IPv6 implementation that will enable application access via the new TCP/IP standard. Enterprise servers and networks must be IPv6-capable in order to deploy new technologies such as voice over IP and wireless Internet access.
  
  
• Multilevel security support. IBM intends to provide additional multilevel security in z/OS. This support will build on the existing multilevel security features that enabled MVS/SP V3R1.3 and RACF 1.9 to previously obtain an evaluation under the Trusted Computer Systems Evaluation Criteria.

These statements represent the current intentions of IBM. IBM development plans are subject to change or withdrawal without further notice. Any reliance on this Statement of Direction is at the relying party's sole risk and will not create any liability or obligation for IBM.

z/OS statement of direction
October 3, 2000

As stated in the October 3, 2000 IBM z/OS: An operating system solution for the future of your business announcement letter, IBM plans to take the following actions in the future. You are encouraged to consider these plans when making your own plans for system upgrades.

• HiperSockets provides high-speed memory-to-memory TCP/IP communication across partitions. This allows TCP/IP traffic to travel between partitions at memory speed rather than network speed.
  
  It will be provided in a later release of the operating system.
  
  
• S/390 Service Update Facility (SUF) Version 3, an Internet-based method for ordering and receiving S/390 or z/OS software service
  
  
• LANRES support in z/OS is planned to be functionally stabilized at the z/OS Version 1 Release 1 level

The following will be withdrawn with the z/OS release planned for the second half of 2001:

• The withdrawal of V4 Kerberos support from the Communications Server
  
  
• The withdrawal of Library Management Facility (LMF)
  
  
• The withdrawal of Pre-Compiled Header files (PCH) support in the C/C++ compiler
  
  
• The withdrawal of RMF Monitor II local 3270 display sessions
  
  
• The withdrawal of SOMobjects

These statements represent IBM's current intentions. IBM development plans and subject to change or withdrawal without further notice.

HiperSockets

HiperSockets provides high-speed memory-to-memory TCP/IP communication across partitions. This allows TCP/IP traffic to travel between partitions at memory speed rather than network speed.

This "network in the box" minimizes network latency and maximizes bandwidth capabilities between Linux for S/390, Linux for z/Series, and z/OS images. This enables optimized e-business and ERP solutions within a single CEC. These OS images can be:

• First level - directly under an LPAR
• Second level - under VM

Up to four separate cluster LANs can be configured within a CEC, allowing OS images to be grouped according to the function they provide These groupings are independent of sysplex affiliation.

S/390 Service Update Facility (SUF) Version 3

IBM intends to provide further enhancements to SUF to position it as the strategic method for S/390 software service delivery. Future enhancements will include:

• Elimination of the need for WebSphere Application Server
• Simplified communications through your firewall
• Security and data integrity enhancements
• Improved usability and performance
• Additional service options

Watch for future S/390 announcements, or visit the SUF Web site.

LANRES support

LANRES support in z/OS will be functionally stabilized at the z/OS Release 1 level. No enhancements are planned to either the host component or Netware server component of LANRES. It is IBM's intent to remove LANRES from a future release of z/OS.

Withdrawal of Version 4 Kerberos support

Version 4 Kerberos support will be withdrawn from the Communications Server element with a future z/OS release in favor of the more current Kerberos V5 support already provided as a part of OS/390. Any applications currently utilizing the Kerberos Version 4 support provided by the Communications Server should be modified to use the Kerberos Version 5 support provided by the OS/390 Security Server feature.

Withdrawal of Library Management Facility (LMF)

Library Management Facility (LMF) services such as LMPROM, LMHIER, LMREVIEW, LMACT, and LMDEACT are being withdrawn to take advantage of better and more modern library function in option 10 SCLM. All other LMxxxx services will remain.

If you need more information, contact Don Ingerslew

Withdrawal of Pre-Compiled Header (PCH) file support

The C/C++ compilers will no longer support the GENPCH and USEPCH compiler options for Pre-Compiled Header files (PCH), starting with the z/OS planned for second half of 2001. GENPCH and USEPCH served as a tactical initiative to reduce compile times. IBM will concentrate instead on improving compile times transparently for all users, without requiring any special set-up. We're doing this by building the compilers with successively higher levels of optimization from release to release, exploiting the ongoing optimization improvements made in the compilers.

Withdrawal of RMF Monitor II Local 3270 Display Session

RMF provides several options for a customer to view real-time performance data. The local display session requires a BTAM connection. Since IBM has announced end of service for BTAM, this RMF display option will be withdrawn. You will continue to have access to Monitor II information without an active TSO/TCAS subsystem by means of RMF Client/Server Enabling (RMFCS).

Withdrawal of SOMobjects for OS/390

Object Oriented (OO) technology has come a long way since IBM's introduction of SOMobjects in June of 1995. It is now the cornerstone of e-Business. SOMobjects provided an introduction to OO technology and a way to build applications which took advantage of everything the emerging technology had to offer coupled with the advantages of the S/390 platform. As the technology advanced, we made a decision to incorporate those advances into a new line of products called WebSphere, specifically aimed at the e-business environment and its requirements.

Given that product direction, IBM plans to remove the SOMobjects product from z/OS. The SOMobjects Application Development Environment (ADE) will no longer be available with z/OS after 1st half of 2001. We recognize that there continues to be value in the ability to build COBOL OO applications that can be deployed on the S/390 platform, and the COBOL OO technology is based upon SOMobjects.

For that reason, IBM plans to incorporate the necessary subset of the SOMobjects ADE into the top COBOL for OS/390 & VM compiler product. The SOMobjects run time library (RTL) is currently a component of z/OS. The subset of the SOMobjects RTL needed for OO COBOL applications will be incorporated into the Language Environment component of z/OS. This will allow COBOL customers to continue to maintain, enhance, and execute OO COBOL applications.