Well, at least I consider them to be. Too bad I'll never see them here. === Generation data groups (GDGs) are limited to 255 or fewer generations. z/OS V2.2 will be designed to support a new data set type, generation data group extended (GDGE), which is planned to allow you to specify that up to 999 generations be kept when the function is enabled in an IGGCATxx member of parmlib. This new support is intended to support a larger number to make it easier to manage data sets that are created frequently. For example, it will be possible to specify that all of the generations created every day for a full year be kept. Additionally, IDCAMS and DFSMSdfp processing are planned to be enhanced to allow you to specify that unexpired generation data sets be deleted automatically when retaining them would result in the inability to create a new generation.
=== z/OS V2.2 JES2 and SDSF will be designed to support a new way to track job step completion codes. A new machine-readable data set is planned to contain job tracking information, including the completion codes for each job step. SDSF will be designed to extract and display step-level completion codes for batch jobs, and the z/OSMF Jobs REST API is planned to allow you to retrieve step-level completion codes. Also, this function is planned to support new optional SMF Type 30 information. This is intended to make it easier to interpret job output quickly and to provide the capability for later analyses of job step level information. === JES3 has long supported capabilities for informal, ad hoc batch scheduling. In JES3, these facilities are called deadline scheduling and dependent job control. z/OS V2.2 JES2 will be designed to provide similar functions, with some additional capabilities. A new SCHEDULE JCL statement is planned; STARTBY and HOLDUNTL keywords of SCHEDULE will be designed to make it easier for you to submit jobs intended for later execution without the need to log onto a system at the time you want the jobs to run. Other keywords will be designed to allow you to specify ordering and dependency information for groups of jobs, supporting both serial and parallel execution. Corresponding operator command support is planned to allow job groups to be held, released, modified, canceled, and purged. Corresponding support is also planned for SDSF, which will be designed to provide information about job group status and the status of jobs in a job group, and WLM, which will be designed to support this function with enhancements to Batch Initiator Management. Together, these new capabilities are intended to supplement those of production job scheduling products such as Tivoli Workload Scheduler for z/OS, by helping you simplify the scheduling of batch jobs and job groups that are run only when necessary and need not be added to production job schedules. === z/OS V2.2 ISPF is planned to provide a new option you can use to completely disable the use of ISPF Edit Pack. This function will be designed to allow you to help control CPU utilization for ISPF users by preventing the overhead of software compression and inflation for data sets used in conjunction with ISPF and ISPF services, and assure that newly created and unpacked data sets processed by ISPF can be easily processed by other programs. === Inline assembler statements support will be designed to allow you to insert assembler statements inlined with XL C and XL C++ code. This support will be designed to not require Metal C compilation and to allow you to easily use specialized instructions with your C and C++ objects. === z/OS V2.2 is planned to introduce a new z/OS Client Web Enablement Toolkit, designed to enable applications written in C/C++, COBOL, PL/I, and High Level Assembler to participate more easily as a client in a RESTful web application programming model. The toolkit is planned to provide a z/OS JSON parser able to process text coming from any source, to build new JSON text, or add to existing JSON text; and, an HTTP/HTTPS protocol enabler that uses interfaces similar to other industry-standard APIs. These components are also planned to be available for z/OS V2.1. The PTF for OA46575 is planned to include the z/OS JSON Parser and be made available in the first quarter of 2015. The PTF for OA46622 is planned to provide the z/OS HTTP enabler and to be closed by the z/OS V2.2 general availability date. === <statement of direction> IBM plans to add OpenSSH to z/OS and enhance it by providing Kerberos support, which is designed to enable single sign-on from Microsoft™ Windows™ domains, and also to leverage the capabilities of IBM zEnterprise Data Compression (zEDC). These capabilities are also planned to be made available in the version of OpenSSH that is part of IBM Ported Tools for z/OS. === -- While a transcendent vocabulary is laudable, one must be eternally careful so that the calculated objective of communication does not become ensconced in obscurity. In other words, eschew obfuscation. 111,111,111 x 111,111,111 = 12,345,678,987,654,321 Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
